rustfmt development, versioning, distribution, etc.

During some recent discussions related to (unreleased) breaking changes in rustfmt, several distinct but related topics and questions were raised. Opening this to both summarize those items and track closure, though imagine some may spin off as separate issues and/or be moved elsewhere.
First, some salient points on the current state:

rustfmt is versioned independently of rustc (discussed in https://github.com/rust-lang/rfcs/pull/2437)

rustfmt v1.4.18 is the most recent version to hit nightly
rustfmt v1.4.16 the most recent on stable

Updates to rustfmt have to work within two strict constraints:

Formatting with default config options must align to the Style Guide which can and does change over time
The stability guarantee prevents any style/formatting changes within minor/patch updates (more detail in #4286), so we have to mentally attempt to determine if a given change to rustfmt could impact any formatting in any project, and if so that change has to be rejected or gated/made opt-in

Version gating (feature flag of sorts) has been used historically to try to avoid introducing formatting changes, but this often adds a lot of additional code and complexity that complicates maintenance
rustfmt is distributed and consumed through multiple channels:

rustup
from crates.io (as bin or lib) https://crates.io/crates/rustfmt-nightly
pre-built binaries for tier 1 platforms as artifacts on GitHub Releases, starting with next release

rustfmt is a submod in rust-lang/rust
rustfmt has a heavy reliance on rustc internals which are consumed via rustc-ap (primarily rustc_ast, rustc_span, and rustc_parse)
rustfmt is a dependency of rls which uses rustfmt as a lib

rls also depends on racer, which also uses the rustc-ap crates, so addressing breaking rustc-ap changes  has to be coordinated across three projects to keep the rustc-ap versions in sync within rust-lang/rust

The default branch in this repo has been the active/primary development branch for 8+ months accumulating unreleased bug fixes, features, and some breaking changes. The published 1.x versions of rustfmt have mostly been in maintenance mode during that window and have only received rustc-ap bumps as necessary and the backporting of fixes for some higher impact bugs.

Questions/topics
Below are some of the topics/questions/feedback from recent discussions, and I'll also add that the decision and outcome for several of these questions could directly impact the others.

Should rustfmt continue to be versioned independently from rustc?
Should rustfmt continue to be distributed and made consumable from crates.io?
Default edition for rustfmt versions should not vary from the distribution they ship with (rustc is still 2015 as of 1.45.0 so rustfmt should be as well)
Would the subtree approach work better than the submod approach within rust-lang/rust? (insert issue link here)

Big pro is the elimination of the rustc-ap reliance
Drawback is the loss of ability to distribute rustfmt via crates.io

Should style/formatting changes continue to be considered breaking changes?
When do we want to allow breaking changes (style/formatting, or otherwise) to be released?

How should breaking changes be shared in advance with the community? (we're working on documenting the current set of unreleased breaking changes already)

Finally, I'll add that one concern I have is that I think it's highly likely we'd end up in a scenario where rustfmt would be violating one or the other core constraints if those both remain in place, and rustfmt is not allowed to ship any new major versions outside of an Edition accompaniment. For example, certain changes to the Style Guide would require an update to default formatting in rustfmt that would in turn break the stability guarantee.

Should style/formatting changes continue to be considered breaking changes?
When do we want to allow breaking changes (style/formatting, or otherwise) to be released?
How should breaking changes be shared in advance with the community? (we're working on documenting the current set of unreleased breaking changes already)

One plausible mechanism here is to reduce the scope of the guarantee.
For example the guarantee could be reduced from "Changes to formatting/style are considered breaking"
to "Changes to formatting/style are considered breaking if the would cause code which was formatted by a previous version to be reformatted (Assuming no changes to config/edition)"
This is weaker because the reverse does not hold, IE: an old version for rustfmt might reformat code in the format output by the new version.
Then a new flag --strict could be introduced to reformat according to how the current version would like to see things formated.
Once an addition boundary occurs the scope of what is permitted can be culled.
So an upgrade path would look like this:
rustfmt_v1  # Code gets formatted according to standard 1
rustfmt_v2  # Does nothing because while standard 2 is prefered standard 1 is allowed so given that the code is compliant with it no changes are made.
rustfmt_v2 --strict  # Reformats all code according to standard 2.
rustfmt_2021 # Standard 2 is now mandatory.

"Changes to formatting/style are considered breaking if the would cause code which was formatted by a previous version to be reformatted (Assuming no changes to config/edition)"

This is weaker because the reverse does not hold, IE: an old version for rustfmt might reformat code in the format output by the new version.

Thanks for the input! However, that doesn't buy us much in practice, as it's essentially what we're already dealing with today (the reverse already exists in places, for example with newer syntax). The biggest issue by far is that we can't be in a scenario where a newer version of rustfmt formats the code differently than any previous version (i.e. we can never have a cargo fmt -- --check or rustfmt --check failing after an upgrade).

Once an addition boundary occurs the scope of what is permitted can be culled.
So an upgrade path would look like this:

Similarly, this isn't too far off from what has been in place historically since the 1.0 release of rustfmt and it actually adds more complexity with the additional cli flags. This approach ends up creating a mess within the rustfmt codebase over time. Short-lived feature flags work great, but the notion of having feature flags and code live 2-3+ years is just not viable IMO. Plus, don't forget that there's only ever one standard: the Style Guide, and it can evolve independently.
The whole objective with a major version release is to allow us to finally ship such breaking changes (which is in alignment with the original RFC on rustfmt versioning) so shipping a v2 of rustfmt that does the exact same thing as v1 doesn't buy us anything.

One plausible mechanism here is to reduce the scope of the guarantee.

IMO something is going to have to give. I understand why folks have raised concerns about a 2.0 version of rustfmt being released outside a major rust release, but I just don't see how rustfmt can be fully complaint with the stability guarantee (in its current form), and always directly aligned to the Style Guide, and only be allowed to make breaking changes (as currently defined) every few years, all at the same time.

Default edition for rustfmt versions should not vary from the distribution they ship with (rustc is still 2015 as of 1.45.0 so rustfmt should be as well)

The problem is that, unlike rustc, users often use rustfmt outside of the cargo context, and having 2015 as the default edition has been confusing to users. If we decide to sync the default edition in rustc and rustfmt, at least we should update rustfmt so that it respects the edition written in Cargo.toml even when it is run directly.

Should style/formatting changes continue to be considered breaking changes?
When do we want to allow breaking changes (style/formatting, or otherwise) to be released?

I have been thinking about removing the style/formatting changes from what we consider as breaking changes. If users need the formatting stability then they can pin to the specific release of rustup.
If this is possible then we can avoid making a major version release after 2.0 (or avoid 2.0 release altogether with some hassle).

I have a question regarding this: Unless I'm missing something, building Rust from source now always requires rustfmt.
This means, that Rust can no longer be built natively on platforms for which upstream doesn't provide binaries for rustfmt.
On sparc64, I previously could checkout the Rust source from git and build them with the locally installed rustc on a Debian box. This no longer works since the build process now always tries to download rustfmt for sparc64 which doesn't exist.
I have neither found a switch to disable rustfmt for a Rust build nor was I able to build rustfmt from source using the stable compiler provided by Debian.
How do I resolve this issue?

@glaubitz - if you have a question about compiling rustc, then that needs to be asked in https://github.com/rust-lang/rust.
Marking both of these comments as off topic

My reason to comment here was that there is no way to build rustfmt with a stable compiler and I think it would be a desirable feature for distribution.

@glaubitz - As noted in the rustfmt documentation, and other threads, a nightly compiler is required to build rustfmt just like most other official rust tooling. This has been the case for a long time, and isn't going to change any time soon.
Your previous question was explicitly asking about the process of compiling rustc after cloning the rust repo, which is still off topic both for this thread and this repo more generally. I'd provide an answer if I had one for you, but there's not much we can offer you around what issues you are seeing trying to compile rustc. You'll need to seek answers/assistance with rustc compilation issues in other forums as mentioned previously (you could try Zulip or Discord as well).
The nightly compiler requirement for building rustfmt is orthogonal to this thread, and troubleshooting build issues for rust-lang/rust is off topic.
Also marking these as OT

It has been a long time since I last posted; I'd like to summarize the current situation (to make sure I remember things correctly) and dump my thoughts.
The current master branch contains breaking changes since the latest release (1.4.22). The scope of breaking changes is broad:

Changing the default formatting style
Removing command line arguments
Removing configuration options
Updating rustfmt-as-a-library APIs
We need a major version update for a release containing these changes, as defined in RFC 2437.

However, a concern was raised that whether we should make a major version update of rustfmt, which happens to be an official tool, in the first place. As such, we should start by creating an RFC (or pre-RFC to the forum?) about the rustfmt 2.0 release. To be honest, I have been reluctant to do so, as I expect the amount of communication to be enormous, and I don't have enough energy and time to handle such communication.
Instead of, or in parallel with, preparing 2.0, we may restore breaking changes and release it as 1.5.

Undo breaking changes to command line arguments and configuration options, in particular, the version configuration option
Add Version::Three, and make it so that the breaking changes to the default formatting style is only usable when version is set to Version::Three.
Releasing the master branch as 1.5 is challenging. The number of breaking changes is massive, especially ones related to the default formatting style, so it is not feasible to use version gates as before. One way to do this is to split the rustfmt into separate crates (rustfmt_bin and rustfmt_lib), as we tried once before.

However, a concern was raised that whether we should make a major version update of rustfmt, which happens to be an official tool, in the first place. As such, we should start by creating an RFC (or pre-RFC to the forum?) about the rustfmt 2.0 release. To be honest, I have been reluctant to do so, as I expect the amount of communication to be enormous, and I don't have enough energy and time to handle such communication.

From what I've seen the questions about release 2.0 are more about doing so outside an edition release, and/or doing so without a substantive communication campaign. The latter of which I believe has generally universal agreement, as we wouldn't want to silently drop 2.0 on nightly with nothing but our changelog. I don't think this necessarily would require an RFC just for 2.0 release, but at a minimum we'd want a blog post (e.g. inside rust)
I think we'll want to revisit the stability guarantee more generally first, which would require an RFC (at least IMO), as that will definitely impact the release/versioning aspects.


Invalid refactor from isEqualTo(@Nullable Map) to containsExactlyInAnyOrderElementsOf

What happened?
I maintain a repo that has a helper method like this:
    private static void assertAttributesEqual(
            @Nullable Map<String, Map<String, String>> expected, @Nullable Object actual) {
        Map<String, Map<String, String>> actualAttrs = (Map<String, Map<String, String>>) actual;
        assertThat(actualAttrs).isEqualTo(expected);
    }

When assertj-automation comes around it attempts to reword that last statement to this instead:
        assertThat(actualAttrs).containsExactlyInAnyOrderEntriesOf(expected);

However this fails at test runtime with this exception:
java.lang.NullPointerException: Cannot invoke "java.util.Map.entrySet()" because "map" is null
	at org.assertj.core.api.AbstractMapAssert.toEntries(AbstractMapAssert.java:695)
	at org.assertj.core.api.AbstractMapAssert.containsExactlyInAnyOrderEntriesOf(AbstractMapAssert.java:690)
	at com.mypackage.MyClass.assertAttributesEqual(MyClass.java:38)

The problem is that if the expected parameter is null (as is declared via the @Nullable annotation) then the
What did you want to happen?
For expected values that have been annotated @Nullable, this refactor should be skipped.  Or changed to produce a valid refactor that still passes.
See https://github.com/palantir/assertj-automation/pull/631/files for desired behavior (no change)

I disagree -- when values are expected to be null, we should assertThat(value).isNull(); assertj-automation attempts to make asserts more precise, which is difficult when the original assertion is imprecise, sometimes it will cause tests to fail until they're updated with greater precision.

Fair enough.  I ended up rewriting the above assertThat to this:
        // if expected is null then check for null directly. containsExactlyInAnyOrderEntriesOf() fails when given a
        // null expected value, and assert-automation refactors continuously try to use that method, so we need to
        // branch here to avoid a null pointer exception.
        // See https://github.com/palantir/assertj-automation/issues/630
        if (expected == null) {
            assertThat(actual).isNull();
        } else {
            assertThat(actualAttrs).containsExactlyInAnyOrderEntriesOf(expected);
        }


[Bug]: Modify Report menu for The total population of city label

Is there an existing issue for this?

[X] I have searched the existing issues

Contact Name
Bobby Walters
Description of the bug?
label needs correcting
Version
Develop Branch
Steps to Reproduce the Error
24: 31 Population Of ACity
Remove the number before the begining on the reports 26 thru 32

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Successfully completed.


Application Insights Users/Count and Sessions/Count not returning data

Every time I try to make a graph with the Users/Count value (with the unique arrogation), I cannot return any data, it just returns NaN. I have attached a screenshot of what I am trying to configure

Thanks for reporting this. Unique is missing from the list of allowed aggregations. Will add it and get a release out.

@robertholz there is a new version of the plugin with this fix.


Pull github url from additional sources

With regard to #2163 and #3583: I really liked this feature set implemented :tada:
Still, there's a room for improvement:
project_urls dict argument of setuptools.setup() allows adding a list of additional urls. And some distributions have their url= set to the project's website/homepage, but still supply extra info using project_urls=.
I suggest also iterating over this extra dict and looking for github repo URLs there as well.
/cc: @AyumuKasuga @cheungnj @di @nlhkabu @dstufft @pradyunsg

@webknjaz We already do this, is there some reason why you think this isn't currently happening?

But yes, from PR #2163 it seems like it should work.

@webknjaz I see statistics on that project page. Since this happens on the client-side, it's possible that your IP has used up all it's allocated requests to the Github API. Could you try from a different IP? Your browser network console might show some details as well.


Predicate with .StartsWith fails.

String comparison using .Where(item => item.stringField.StartsWith("some string")) fails. It would be nice if it translated to WHERE instr(stringField, 'some string') > 0.

Hi @bmmptlgc,
the above predicate should be translated to WHERE stringField LIKE 'some string%'. Could you provide more details, please?

It seems to be that ksql doesn't support AND and  LIKE on the same query.

It seems you've come across this ksql issue. I tested it with streams, and it behaves as anticipated. Could be the below approach a viable workaround for you until the issue is addressed in ksqldb?
using  ksqlDB.RestApi.Client.KSql.Query.Functions;

.Where(item => K.Functions.Instr(item.stringField, "some string") > 0)

That works perfectly, thank.


Microsoft Teams emoji bug

Hi!
Microsoft Teams on desktop (Win + Mac) has problems with displaying emoji.
Teams:

Skype:

@dandriscoll can you assign this to someone on Teams?

Just wanted to offer a quick follow up:  Teams does not currently support emojis, but it is on the backlog.

Closing as this is not currently supported. If you want to discuss further, feel free to at-mention or open a new issue.


Eligibility for Hare protocol

The Motivation
We define the eligibility for Hare protocol
The Requirement
Hare eligibility rules consist of:

Activation and Difficulty
Hare beacon
Eligibility due to VRF

Nothing pending here


dfuse-eosio supports custom genesis account and system account prefix

I currently customize development based on EOSIO-eos. Compared with EOSIO-eos, the difference is the prefixes of custom genesis account and system account.
I would like to ask whether dfuse-eosio supports parameterized setting of genesis account and system account prefix? For eosio-eos doing baas, modifying the prefix of the genesis account and system account is also the most basic support.
For the existing settings, the default value can also be the current parameters of eosio-eos, and there will be no other impact

Indeed, we have eosio hard-coded at some places throughout the code. We are open for a PR that implement the feature of making the system account configurable, it’s something good for the product, just not a priority for us.
All chains we ever need to support so far still used the eosio system account in some ways. It never been a problem for us for far. Note that the ecosystem itself is not sometimes well supporting other system account name.
Turning this into a feature request and updating the title.


Improved runtime and interactive integration

@e-cal Todo list before it's ready to merge?

Nvm...this can just remain open as a marker of what's being worked on.


Create a conda-forge package for lightning-flash

🚀 Feature

Motivation

Hi there, I'd like to make it easier for users to install lightning-flash using the conda package manager! I noticed that only pip install is possible for lightning-flash v0.4.0 according to https://lightning-flash.readthedocs.io/en/0.4.0/installation.html, but would love to see a conda install option too!
Pitch

Make conda install -c conda-forge lighning-flash work.
Alternatives

Keep using pip install only :slightly_smiling_face:
Additional context

I'll be following the instructions at https://conda-forge.org/#add_recipe to add a new conda-forge recipe to lightning-flash, and will submit a Pull Request to https://github.com/conda-forge/staged-recipes. Before I do so though, I'd like to ask:

Who is interested to be a recipe maintainer for pytorch-lightning on conda-forge? (usually just involves pushing a button when a new version is released, as most things are automated)
Are there any complicated dependency issues I should be aware of? I'll just start with the base lightning-flash package for now, and maybe do lightning-flash[all] later.

I'm interested to contribute and work on this issue @weiji14 @aniketmaurya

Hi @LoopGlitch26, thanks for your interest! I've opened up a PR already at https://github.com/conda-forge/staged-recipes/pull/15917 to add lightning-flash to conda-forge. Once that is merged though, I suppose we'll need to update the installation documentation, would you like to open a PR to update installation.md with the conda install option?

Ok, lightning-flash is now available at https://anaconda.org/conda-forge/lightning-flash! However, this is just the base installation (i.e. what you get from pip install lightning-flash). There are a few more dependencies that need to be on conda-forge in order to run image/audio tasks. I'll focus on lightning-flash[image] since I'm mostly interested in computer vision :sunglasses:
Dependency list from https://github.com/PyTorchLightning/lightning-flash/blob/0.4.0/requirements/datatype_image.txt, :ballot_box_with_check: means available on conda-forge

[ ] pystiche (>=0.7.2 required)
[x] pycocotools 2.0.2
[ ] lightning-bolts (>=0.3.3 required, xref request at https://github.com/PyTorchLightning/lightning-bolts/issues/364)
[x] kornia 0.5.8
[x] Pillow 8.3.1
[ ] fiftyone
[x] timm 0.4.12

There are more dependencies on PytorchLightning's master branch, but let's take it one step at a time :grin:
https://github.com/PyTorchLightning/lightning-flash/blob/15bc77891856e06a111f8d410832a376d96d07b7/requirements/datatype_image.txt#L1-L10
Alternatively, the requirements could be relaxed somewhat (i.e. made optional) by modifying https://github.com/PyTorchLightning/lightning-flash/blob/2ec52e633bb3679f50dd7e30526885a4547e1851/flash/core/utilities/imports.py#L93-L102 otherwise people will get hit with an error like ModuleNotFoundError: Required dependencies not available. Please run: pip install 'lightning-flash[image]


rename VCD file

cache.vcd instead of uut.vcd
Can be used no matter whether or not the scope is limited to the unit under test.

Recently we began calling all vcd files of any project Unit Under Test (uut).
This has to do with future automation plans.
This PR is rejected.


One logger per module.

Not setting up a logging config; assuming varcode is only used as a library.
Fixes #196

This change is

Coverage increased (+0.7%) to 88.756% when pulling 56edb53f696a11fb8edc4931c335d0cd9e757175 on varcode-logger into d7383f95993d598d5385c57455c11823d1f15cb8 on master.

LGTM

Coverage increased (+0.06%) to 88.979% when pulling a6e4f99728f5ff3d592b5e3029652d40ab19a16e on varcode-logger into cdde05199851882c09d1e3ceb48a67be9ad0269a on master.


Add HiLo conversion method

Decimal type has FromHiLo constructor. The opposite method is required so the decimal type can be constructed / deconstructed. Also, ability to convert to {Hi, Lo} pair is important for integrations with other libraries which work with uint64 or uint128 types.

ability to convert to {Hi, Lo} pair is important for integrations with other libraries which work with uint64 or uint128 types

Can you elaborate why do you need to convert decimal to another data type? I think libraries that has uint128 is not that common

ability to convert to {Hi, Lo} pair is important for integrations with other libraries which work with uint64 or uint128 types

Can you elaborate why you need to convert decimal to another data type? I think libraries that has uint128 is not that common

Example - https://github.com/tigerbeetle/tigerbeetle
It works with uint128. It expects amounts will be represented as 128 bit integer, scaled to required precision. Because it is double entry accounting, internally it requires only Add function for amounts, and only positive values with same scale.
Another example - any external storage where you also want to be able to apply a simple functions like comparison, add, etc. I.e. scaled int is ideal. But int64 is too small. And udecimal in any case targets int128, so why not allow to export to this type?
Another reason is existing FromHiLo constructor. You can build udecimal from Hi/Lo pair... but you cannot deconstruct it back to Hi/Lo.

FromHiLo is mainly used for Fuzz and tbh I don't expect it to be utilized. Your use case is valid tho. However, I think the name should be ToHiLo. Also, can you add some examples to doc_test.go to keep the docs up-to-date?

FromHiLo is mainly used for Fuzz and tbh I don't expect it to be utilized. Your use case is valid tho. However, I think the name should be ToHiLo. Also, can you add some examples to doc_test.go to keep the docs up-to-date?

done


Docs/storybook

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


please update README.md to highlight potential windows error

I have added a common windows failure scenario, as well as the solution, to your README.
Thanks for the good work!
steve

@cixelsyd thank you for the patch, however proper DevKit installation (as RubyGems plugin) shouldn't require you to load devkitvars.bat
Is that the case? Please confirm so perhaps a better hook can be added to gem-compiler so no extra command is required.
Thank you.

@cixelsyd can you confirm the DevKit has been properly installed? As mentioned it shouldn't be required to load it independently since is a RubyGems plugin and that is automatically enabled when using RubyGems.
Thank you.

Hi Luis! I've installed ruby and ruby devkit before, and was reasonably sure I didn't make an error here.  Let me try to uninstall and re-install them and see what happens.

Hello @cixelsyd, I was able to confirm that gem-compiler was not able to compile gems on Windows even when DevKit was present.
Instead of document yet another thing in the README, decided to fix it in #21, which just merged.
Will be part of next release.
Thank you for your patience and bring this issue to my attention (and sorry for the delay on getting this solved).
Cheers.

Great, Luis!
Thank you!
On Sat, Apr 23, 2016 at 8:35 PM, Luis Lavena<EMAIL_ADDRESS>wrote:

Hello @cixelsyd https://github.com/cixelsyd, I was able to confirm that
gem-compiler was not able to compile gems on Windows even when DevKit was
present.
Instead of document yet another thing in the README, decided to fix it in
#21 https://github.com/luislavena/gem-compiler/pull/21, which just
merged.
Will be part of next release.
Thank you for your patience and bring this issue to my attention (and
sorry for the delay on getting this solved).
Cheers.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/luislavena/gem-compiler/pull/18#issuecomment-213858061

--
http://linkedin.com/in/cixelsydego
(508) 372-0005 (cell)


MarshalAs(UnmanagedType.LPUTF8Str) error

it reports that
requires non-trivial marshalling that is not yet supported by this compiler.

can this be supported?

Once somebody grabs this issue and submits a PR with the change that passes review, we will be happy to merge it to master.


Onion skin x-ray option

Which StoryLiner edition and version are you using?
Studio
Is your feature request related to a problem? Please describe.
Clearly, see what I'm drawing with onion skin on.
Describe the solution you'd like
It'd be good to have an 'x-ray' option to see through the onion skins.
Describe alternatives you've considered
I've used Onion Peel, which is a nice add-on, but sometimes I don't need all its features, only the X-ray option.
Additional context
Here is what I'm seeing: the red drawing is broken up, partially occluded by the lines from the onion skin in front in 3D space.
I'm sorry if I missed the solution. Maybe it's not a feature request, but I don't see any options in the onion skin tab of Storyliner.
Thanks.

Thank you for this idea. That would be interesting indeed.
I had plans to improve the onion skin, so I can add that to the list.


🚧 Added F13-F24 to rdev::Key

This will fix #127. This pull request currently works with Windows support. However, Mac and Linux need their key codes figured out and someone to test it on their machines. I manually tested and this pull request is working on Windows as I imported it into one of my own projects.

[x] Windows
[ ] MacOS
[ ] Linux

https://github.com/Narsil/rdev/blob/5b8d4127e6c9c08553d0188bf812343ae06b19a1/src/windows/keycodes.rs#L30
This repo references Windows documentation that states its keycodes. However, the Linux and macOS portions don't link to documentation that states the keycodes. Is this tested and found manually, or can we find the keycodes from an official source?


TransactionURI import & export feature

User should be able to export/import a transaction as a TransactionURI (see https://github.com/nemtech/symbol-uri-scheme ).

TransactionURI Export: On the transfer page, the send button should be changed into a dropdown action button (with preserving the default send button behaviour intact), as an optional action export to TransactionURI should be clicked and URI should be shown on a modal page to copy.

TransactionURI Import: Can be a modal page being opened by a Top bar menu item or can be another tab to the dashboard transfer tabs

As discussed with @evias, following changes has been applied to the design:

Instead of modal export transaction URI page, transaction URI is shown on the bottom of the transfer page and it gets updated live as the user fills the details.
When the user hovers over the link icon a Tooltip is shown and a Poptip is shown for the full version of the transaction URI when  user clicks the shortened transaction URI. A copy button for the user to easily copy the transaction URI.

@jabo38 could you also review and share your thoughts on this?
Following are the screenshots of the implementation:

My preference for exporting the transaction URI is to have it in small grey and truncated letters underneath the transaction.

This is this a very advanced feature on a page where more than 99% of people will be doing a simple thing, I'd suggest, having an little explainer button in the top right of the info box where people could understand just more what a transaction URI is for.
This would mean the send button is just a normal send button I guess then and won't have an arrow on it?
As per importing, I don't think it looks bad where it is at, and don't have any suggestion how to make it better.

I don't understand why the export transaction URI is on the send screen. In that scenario, I'm guessing the transaction still needs to be signed. So why would somebody take a transaction URI that they haven't signed, then import it into another wallet where they would have to sign it.
I think it makes more sense to put it in the screen where a person has already entered their password and are signing the tx.
So in theory, I would going to the confirm screen, entering my password, but instead of clicking "confirm", I would click on a drop down arrow on the confirm screen that would give the option to export tx as a URI.

And since this is a very advanced feature, but on a page where 99% of people won't be doing something advanced, it would be nice if they were clicking on signed tx as URI, that they were given a way to have an explainer of what they were doing or why they would want to do it.

As for import tx URI, it doesn't look bad where it is in the screen shots and I don't have any suggestions how to improve it.

I think URI Scheme Library doesn't support representing already signed transactions.
Because it says "URI Scheme library to serve Symbol transactions ready to be signed." in the library repo (https://github.com/nemtech/symbol-uri-scheme).


Where do we create standalone subscriptions?

I was trying to create a standalone subscription in the portal and I cannot seem to do so as I always have to associate it with a user.  What am I missing?

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

ID: 896691fb-064a-eaf8-f71f-53200149b48a
Version Independent ID: ff3e18ed-6d13-6fac-7b6c-f78f47b0f754
Content: Subscriptions in Azure API Management
Content Source: articles/api-management/api-management-subscriptions.md
Service: api-management
GitHub Login: @miaojiang
Microsoft Alias: apimpm

Hi @rscottwatson - Thank you for your feedback! We will review and update as appropriate.

I tried later and it worked.  Not sure why earlier it was always saying the user was mandatory.


[T5A2][W09-B3]Xiao Pu

Thanks for pointing out that the test cases need to be changed during tutorial ! pls close the issue @xpdavid


Illegal insertion "}"

Check for existing issues

[X] Completed

Describe the bug / provide steps to reproduce it
In Japanese input mode, if you enter more than three characters and then delete up to less than two characters without confirming the input, there is a bug that inserts "}".
Environment
Zed: v0.79.1 (stable)
OS: macOS 13.3.0
Memory: 24 GiB
Architecture: aarch64
If applicable, add mockups / screenshots to help explain present your vision of the feature
https://user-images.githubusercontent.com/17804838/229008935-bd016869-ea6e-4525-a884-398cf3f3c5ad.mov
If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.
If you only need the most recent lines, you can run the zed: open log command palette action to see the last 1000.
No response

It happens too when type in Chinese then press the delete key.

I had the same issue in Japanese.
Probably fixed in v105.

Has anyone tried this in preview (v0.105) and verified that it is fixed? If so, we can close the issue! :)


Name-sg, name-pl and Name-pl required only if needed

Since:

the capitalized form of a name can be derived from the lowercase form thanks to \text_titlecase:n,
the plural form of a name is often (at least in English, in French, in Spanish and, AFAICS, in Portuguese) derived from the singular form by adding a final “s”,

it would be nice for zref-clever to guess from the lowercase singular form (name-sg) of a name what are its capitalized and plural forms (Name-sg, name-pl and Name-pl), and would require the user to explicitly specify the latter only if the two rules above don't give the expected result.
Here is a MCE illustrating the feature.
\documentclass{article}
\usepackage{zref-clever}
\newtheorem{myconjecture}{Conjecture}[section]
\ExplSyntaxOn
\tl_gset:Nn \__conjecture_name_sg_tl {conjecture}
\tl_gset:Nn \__conjecture_name_pl_tl {\__conjecture_name_sg_tl s}

\zcRefTypeSetup{myconjecture}{
  Name-sg = \text_titlecase:n{\__conjecture_name_sg_tl} ,
  name-sg = \__conjecture_name_sg_tl ,
  Name-pl = \text_titlecase:n{\__conjecture_name_pl_tl} ,
  name-pl = \__conjecture_name_pl_tl ,
}
\ExplSyntaxOff
\begin{document}
\section{Section 1}
\begin{myconjecture}\zlabel{conjecture-1}
A conjecture.
\end{myconjecture}
\begin{myconjecture}\zlabel{conjecture-2}
A conjecture.
\end{myconjecture}
\begin{itemize}
\item \zcref[cap]{conjecture-1} and \zcref{conjecture-1,conjecture-2}.
\item \zcref[cap]{conjecture-1,conjecture-2} and \zcref{conjecture-1}.
\end{itemize}
\end{document}

Hi @dbitouze , thanks for the suggestions. I did consider both of them during development, and I think the choices I then made are still sound.
Let me start with the clearer case:

2. the plural form of a name is often (at least in English, in French, in Spanish and, AFAICS, in Portuguese) derived from the singular form by adding a final “s”,

The key word here is "often". Not even in English it is safe to generate a plural just by appending an "s". And the rules are language dependent, typically less regular than English.
And the result of trying to automate this is that zref-clever would "think" it knows the plural when it doesn't, so instead of getting a warning if something is amiss, just appending an "s" could potentially generate straight out wrong results, and quietly so.
So, there's no way I'm venturing in these waters. Plurals must be given explicitly.

the capitalized form of a name can be derived from the lowercase form thanks to \text_titlecase:n,

Here there is a trade-off. The casing macros are safer, but not completely safe, depending on the content of the argument. So I went with a known redundancy to be sure we are not tripped by the casing macros. I think that call still stands.
Besides, I expect the language files to cover most use cases. And the cost of doing it once there is pretty small, I'd say. And we get a cleaner infrastructure in exchange.

Hi @dbitouze !

BTW, the glossaries-extra (and glossaries) and acro packages use an “s” by default for plurals.

I know but, imho, not the best choice.

But the LaTeX team took care to avoid any trap with case macros (see p. 275 of interface3.pdf).

I've been following this from afar and I'm aware things have improved in this area in the kernel. But I think "avoid any trap" is an optimistic assessment, the problem is notoriously difficult. Granted, as far as I know, things should be pretty solid. Still, it is an added complexity.
There are also some technical complications on zref-clever's side. zref-clever is not very typical in option handling. Instead of the traditional "last set value is used", zref-clever works with four option scopes (general, type-specific, language and type specific, and language specific defaults, plus a fifth internal fallback), and there is a precedence rule which decides which one prevails. This is done at typesetting time, or rather while the reference is being processed, and whether the lower levels get the chance depends on if the higher precedence ones are set or not. I'm not sure it was the wisest decision I've made, but it was done on behalf of user flexibility. Anyway, during initial development I actually did try to derive the capitalized names from the regular ones, but it complicated the precedence level handling. After all, at a given level, if the capitalized version is missing, should I go to the next level, of "fill it in"? I could make this change at the time the option is set, but it's the same thing in the end, the precedence for each option scope will be tripped, since the higher level may prevail for a given option, even when it was not set.

Indeed, no. But I'm working on a LaTeX class that will be used by LaTeX beginners who can define their own “theorems”, thanks to a redefinition on my part of the "newtheorem" command that relies on a key-value interface. And I would like to minimize the "fields" that these users will have to fill in.

I'm happy to hear that. But it's the same thing for users in general, isn't it? zref-clever already offers theorem, lemma, corollary, proposition, definition, proof, result, remark, example, exercise, and solution for "theorem-like" environments. I hope this covers a good number of the most frequent use cases, for which the user doesn't need to set any names. For other cases, yes, they typically need to fill in four. If they use cap, or a language which sets allcaps, they may get away with two. If they require abbreviations, they may need to provide a full set of 8. However, whatever the case may be, it is always clear what option was set or not, it is also always clear if an name is missing, generating a corresponding warning. We are also sure never to automatically provide a wrong form which, if it occurred, would happen silently.
All in all, I'm still not convinced the added convenience -- which, granted, exists, but in my view is small -- is worth the added complexity.

OK, thanks for you nice and detailed answers! :smile:


Revert "Removing elements from an array is very costly."

Reverts vespa-engine/vespa#10569
@bratseth PR revert to narrow down what caused performance drop in 1 test

👍


macros: ASSERT() enhancements

Description:
This changes the ASSERT(condition) macro to put the condition in an unevaluated context if ASSERTS are disabled. Essentially, the ASSERT() becomes a static check that its argument is an expression whose value can be statically casted to a bool. This means the condition doesn't just disappear, but the compiler still doesn't emit any code. The biggest benefit of this change is keeping compilation success/failure independent of whether ASSERTS are enabled, which has bitten me a few times. Therefore, I also did a rough and probably incomplete codemod that deletes UNREFERENCED_PARAMETER() calls that are no longer necessary.
Further, both ASSERT() and RELEASE_ASSERT() are now wrapped in do { ... } while(false). In terms of this PR , the main consequence is fixing a couple spots where ASSERT statements don't have semicolons.
Risk Level: Low
Testing: Local building in opt and dbg. Otherwise, waiting for CI
Docs Changes: N/A
Release Notes: N/A

@jsedgwick looks like OSX compile issues. IPv6 test is spurious network error.

Oh this is fantastic! I've been bitten by this more than once and it hadn't even occurred to me we could have an automated fix.  Wohoo!
Side note, there's a new conflict with source/common/ext_authz/ext_authz_impl.cc so this will need a master merge.

New approach, PTAL.
This works for any expression*, including those containing lambda subexpressions, by ditching the "unevaluated context" approach and instead tricking the compiler into letting us put non-constexpr expressions into a constexpr declaration. Specifically, the short circuiting is guaranteed at compile time and so the compiler doesn't care if expr is actually constexpr in false && expr.
I hate C++.

well, at least any expression in Envoy, which is good enough for us if contbuild agrees

Whoa, does anyone know what this error on all the CI builds is?
remote: Counting objects: 37919, done.
remote: Compressing objects: 100% (121/121), done.
remote: Total 37919 (delta 37), reused 36 (delta 7), pack-reused 37788
Receiving objects: 100% (37919/37919), 13.05 MiB | 0 bytes/s, done.
Resolving deltas: 100% (28564/28564), done.
Checking connectivity... done.
Warning: Permanently added the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts.

remote: Counting objects: 76, done.
remote: Compressing objects: 100% (2/2), done.
remote: Total 76 (delta 69), reused 69 (delta 69), pack-reused 5
Unpacking objects: 100% (76/76), done.
From github.com:envoyproxy/envoy
 * [new ref]         refs/pull/2924/head -> origin/pull/2924
fatal: Could not parse object 'd3a5ff3c3465225080a116b6993ef9daecb55a76'.
Exited with code 128


Possible regression about closing tabs/sessions.

System: Linux Mint 19.1 Cinnamon x64
Terminus: 1.0.69
Shell: /bin/bash, no persistence.
Frontend: hterm.
Behaviour:
Having few tabs open, when I'll do 'reboot' or 'shutdown -h now' on mentioned hosts, in some cases Terminus freezes completly. No tabs, no acces, no dev console, the only succesful option is to kill a process.
Expected behaviour:
Not to hang on session/tab closing.

Ping

ping

Please capture DevTools console logs at the time of the issue: https://github.com/Eugeny/terminus/wiki/Debug-logs

Will do

Version 1.0.88, when doing 'shutdown' on remote host, all tabs are gone, devtools:

This happens to me frequently when closing tabs, usually by exiting the shell with "exit"
System: Windows 10 Pro Version 10.0.18980 Build 18980
Terminus: 1.0.91
Shell: CMD (clink) and ssh sessions
Use ConPTY: Yes or No (does not matter)
I get a out of memory crash and then I have to terminate the process manually.
log.txt

@ihenry42 various memory related issues are possible with hterm - it's deprecated in favor of xterm

That seems to work for me as well, multiple hangs when exiting a shell (especially ssh connections)
Change the config file
From
terminal:
  frontend: hterm

To
terminal:
  frontend: xterm


Permissons fixed

This changes permissions raised in  #10

Thanks for taking the time to contribute.
There are some spacing issues, can you please run it through the gofmt?

The spacing issues are now fixed, gofmt is a really cool tool.


Print code coverage report on CI

Description
Print code coverage report on CI
Type of change

New feature (non-breaking change which adds functionality)

Testing steps
Done on CI
Checklist

[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary

Codecov Report

Merging #117 (7fbec51) into main (809d1b1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #117   +/-   ##
=======================================
  Coverage   90.50%   90.50%
=======================================
  Files          10       10
  Lines         200      200
=======================================
  Hits          181      181
  Misses         13       13
  Partials        6        6

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 809d1b1...7fbec51. Read the comment docs.


Unit test gitlab api

Closes #228

Codecov Report

Merging #343 into master will increase coverage by 10.52%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           master     #343       +/-   ##
===========================================
+ Coverage   81.38%   91.91%   +10.52%
===========================================
  Files          24       24
  Lines        1526     1522        -4
  Branches      259      258        -1
===========================================
+ Hits         1242     1399      +157
+ Misses        284      123      -161

Impacted Files
Coverage Δ

lib/api/gitlab.js
99.54% <100%> (+72.18%)
:arrow_up:

Continue to review full report at Codecov.

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


Regression Test Plan

Regression Test Plan
We need a regression test plan for going to production
DOD

[x] Update QA Master Document to indicate which cases are automated
[x] Identify specific automated test cases to spot check
[x] Divide up remaining test cases among business team
[ ] Business team to set up their own dummy tests for testing
[x] Meet with Sachin to go over test plan
[ ] Confirm testing requirements, if any, with Abin for when we switch to PROD enviro. Factor into release timeline

@lmullane @mpilchar let me know if there's any other dod that needs to be added to this task

plan has been presented to team, closing this issue


Dual Device Switch

Nice work you got here, Sean,
I'm currently using Version <IP_ADDRESS> and I couldn't find where to send you tips for functions to add so here I am. I'd love the possibility to bind a single hotkey command to two devices. (Combinding speakers with table mic and headset with headset mic.)
and again, Great work!

This is already an open feature request for this in v2.
https://github.com/xenolightning/AudioSwitcher_v1/issues/1969


[3.x] Prevent use of Opaque Pre-Pass's threshold on top of Alpha Scissor

In SpatialMaterials and ShaderMaterials, both Alpha Scissor and Opaque Pre-Pass can discard fragments (== create fully-transparent pixels), but Opaque Pre-Pass has a hardcoded threshold of 0.1 that the end-developer cannot modify.
This PR makes SpatialMaterials use the alpha scissor threshold instead of Opaque Pre-Pass's own threshold whenever Alpha Scissor is in use. This prevents the strange behavior where any fragment with an ALPHA value under 0.1 would be discarded, no matter what Alpha Scissor value you set.
Using blue noise for ALPHA_SCISSOR and a radial gradient:

Scene in image: PrepassTesting.zip
Related: #45288
Do tell me if this breaks the intent of Opaque Pre-Pass.

Hi, sorry I missed this. I like the proposed change, it makes sense to have the alpha scissor override the depth-prepass threshold.
That being said, the reason that the current behaviour hasn't changed, despite being awkward, is that small tweaks to how the depth prepass work have big impacts on performance, and visuals. It is very easy to accidentally break everyone's scenes when we introduce changes.
So before a change like this is considered, we need to be absolutely sure that it is going to completely break real scenes.

@clayjohn I've been using this change in a custom Godot build for a few weeks now and haven't found issues as of yet, and I couldn't find any collisions with the "depth-prepass + blending" behavior, but I do understand there could be edge cases that I missed (or am completely unaware of), so I share the same worry. 😅

Do you mind testing the MRP in #36669 with your custom build?

Were some of the problems in that issue fixed? Because 3.2.4 RC4 has these problems, but my custom build doesn't
https://user-images.githubusercontent.com/29317321/111005838-db6d5380-838b-11eb-8bce-1909bf6f005a.mp4

Thanks!

PS: If anyone has time, please check the behavior in master to make sure it's consistent with the new behavior in 3.x.


docs: fix /api/config_test; document /api/backup

Review status: :shipit: all files reviewed, all discussions resolved, all commit checks successful.
Reviewed files:

docs/api.md @ r1

Comments from the review on Reviewable.io


[Feature]: add a waitBeforeRetry option to jest.retryTimes

🚀 Feature Proposal
It would be nice to be able to tell Jest to wait some amount of time before retrying tests. I think for most use cases, just a static number of milliseconds would be sufficient.
Motivation
The use case that I am running into is: I have a test that modifies some data, and then a subsequent tests that query the data and then ensure that data is the updated data. However, since there is some caching for the queries (on the back-end), I sometimes need to wait a little bit to get the updated data. So the sequence I would want is:

Test 1: update data
Test 2: get updated data - fails because cached data is returned
Wait some amount of time (e.g. 10 seconds)
Test 2 retry: get updated data - succeeds because cached data is no longer returned

Another case I could see benefitting from this is network errors or other temporary issues, but I think most of the time, that type of case can and should be handled by putting retry logic in the client that is making the network request.
Example
describe('Updating item', () => {
  const originalItem: Item = { ... }
  const updatedItem: Item = { ... }

  test('should succeed', async () => {
    await updateItem(originalItem.id, updatedItem)
  })

  describe('subsequent queries', () => {
    jest.retryTimes(3, { waitBeforeRetry: 10e3 })

    test('getting item should show updates', async () => {
      const item = await getItem(originalItem.id) // Might return cached results
      expect(item).toEqual(updatedItem)
    })

    test('item list should show updates', async () => {
      const items = await listItems() // Might return cached results
      expect(items).toContainEqual(updatedItem)
    })
  })
})

Pitch
The reason I want this in jest.retryTimes is because cached data doesn't cause the request itself to fail, it just causes one of the following expect assertions to fail. So the necessary retry logic must be put in the test suite.
To be honest, I am not sure there are many cases where I would use jest.retryTimes without a waitBeforeRetry option since most of the time if there is an error that an immediate retry would solve, I would prefer to implement that retry logic in the underlying client or service. To me, jest.retryTimes should mostly be used when there is not an error in the request but rather in the expect assertions (generally due to caching or eventual consistency).

Hi guys this is my first time here,
Happy to contribute to the jest community.
I've created a sample PR as per my understanding of the repository.
I'm not sure where to add tests to support this new feature, would be happy to do so if someone could point me in the right direction.

Keep the issue open

Keep the issue open


Preview Redirects To Login When Session Is Lost

Description
The preview frame appears to redirect to the login page if a user loses their session before hitting preview on a page.
To recreate:

Sign-in and navigate to a private page with a text box (eg. PR)
Delete cookies
Press "Preview"

Gitea Version
try.gitea
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots

Git Version
No response
Operating System
No response
How are you running Gitea?
try.gitea
Database
None

Should not redirect in this case, but display an error box related to the outcome of the HTTP request.

It's not a redirect, it just embedded the responded "login" page content into the preview panel.
That's a longstanding problem, not only here, the AJAX requests which fill the responded HTML into current page all have such problem.
And even worse, in this case, the "submit" action will lose the content.

Could just stop issueing a redirect and send a 401 error instead when a fetch/xhr request is dected via presence of HTTP origin header.

Another option would be to error on redirect in the JS. I think this is only possible via fetch API:
https://developer.mozilla.org/en-US/docs/Web/API/fetch#redirect


ComboBox Asynchronous Loading initialSelectedKeys only work if the key is in the first fetch

🙋 Documentation Request
Combo Asynchronous Loading's example for having an initialSelectedKeys works only if that key is in the first page.
If the value is in the first page, it is correctly selected. If it's after the first page, the box remains empty.
"Luke Skywalker" ✅
"C-3PO" ✅
"BB8" ❌
https://codesandbox.io/s/react-spectrum-combo-box-issue-cg5f9g?file=/src/App.tsx:1558-1585

Looks like there is room for an improvement here, potentially if we pass initialSelectedKeys into the async function.
In the meantime, you could work around this by keeping the initial search term outside and if filterText is empty you could set the search to your external value. Probably need some logic around if it's on the first search or a later one as well. But here's the general idea.
https://codesandbox.io/s/react-spectrum-combo-box-issue-forked-9tjv8g?file=/src/App.tsx:344-354


App Service: Web app & deployment slots

The issues discussed are addressed, except the following:

getPfxFromKeyVault
getPfxPasswordFromKeyVault

Key vault access requires separate access policy to set on the vault, and creating a Key Vault data plane client, and query the data. It can be implemented in the near future.

Stil better to not list the constants on the method. They’re obvious when people see the enum. Someday these enums will have other constants. Not great for maintenance.
From: Jianghao Lu<EMAIL_ADDRESS>Sent: Friday, November 18, 2016 2:19 PM
To: Azure/azure-sdk-for-java<EMAIL_ADDRESS>Cc: Martin Sawicki<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [Azure/azure-sdk-for-java] App Service: Web app & deployment slots (#1267)
@jianghaolu commented on this pull request.

In azure-mgmt-website/src/main/java/com/microsoft/azure/management/website/WebAppBase.javahttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-sdk-for-java%2Fpull%2F1267&data=02|01|marcins%40microsoft.com|679d95c0789a424638bb08d41000f6c3|72f988bf86f141af91ab2d7cd011db47|1|0|636151043702236505&sdata=8Iqyz49Zelf9zKjsnPz5lM%2BjitkqfbDy8UDUnyNVDTA%3D&reserved=0:

UsageState usageState();

/**

* @return true if the site is enabled; otherwise, false

*/

boolean enabled();

/**

* @return host names for the web app that are enabled

*/

Set enabledHostNames();

/**

* @return management information availability state for the web app.

*

* Normal means that the site is running correctly and that

For auto-generated enums this is the only way right now - Swagger doesn't allow documentations for enums.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-sdk-for-java%2Fpull%2F1267&data=02|01|marcins%40microsoft.com|679d95c0789a424638bb08d41000f6c3|72f988bf86f141af91ab2d7cd011db47|1|0|636151043702236505&sdata=8Iqyz49Zelf9zKjsnPz5lM%2BjitkqfbDy8UDUnyNVDTA%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAA10ZwgSHCeforcrGsjCkEc80_FVN2biks5q_iRwgaJpZM4KtE-W&data=02|01|marcins%40microsoft.com|679d95c0789a424638bb08d41000f6c3|72f988bf86f141af91ab2d7cd011db47|1|0|636151043702246514&sdata=PQ%2Fx7akY%2B%2F0xgx2W3BX8V2DZecPKmdG7fbbMCsRH%2BvI%3D&reserved=0.


rtsp source ERR: sdp: invalid syntax c=

Which version are you using?
v0.12.0
Which operating system are you using?
Linux
Describe the problem
when start rtsp-simple-server,there is error:
2020/11/10 12:00:01 [0/0/0] rtsp-simple-server v0.12.0
2020/11/10 12:00:01 [0/0/0] [UDP/RTP server] opened on :8000
2020/11/10 12:00:01 [0/0/0] [UDP/RTCP server] opened on :8001
2020/11/10 12:00:01 [0/0/0] [TCP server] opened on :8554
2020/11/10 12:00:01 [0/0/0] [path tv01] rtsp source started
2020/11/10 12:00:01 [0/0/0] [path tv01] connecting to rtsp source
2020/11/10 12:00:01 [0/0/0] [path tv01] rtsp source ERR: sdp: invalid syntax `c=`
2020/11/10 12:00:06 [0/0/0] [path tv01] connecting to rtsp source
2020/11/10 12:00:06 [0/0/0] [path tv01] rtsp source ERR: sdp: invalid syntax `c=`

config file:
logDestinations: [stdout]
logFile: rtsp-simple-server.log
protocols: [udp, tcp]
rtspPort: 8554
rtpPort: 8000
rtcpPort: 8001
readTimeout: 10s
writeTimeout: 10s
authMethods: [basic, digest]
metrics: no
pprof: no
runOnConnect:
runOnConnectRestart: no
paths:

  tv01:
    source: rtsp://<IP_ADDRESS>/PLTV/88888892/224/3221225983/10000100000000060000000000176932_0.smil

Did you attach a network dump?
yes
test.zip

Hello, thanks for reporting the issue, this SDP is now fully supported in master and will be supported in the next release.

added in v0.12.1

yes,it works fine,many thanks!


Create an existing project succeeds

We should first check if a project name already exists in the createProject modal dialog.

Resolved.


Ryzen/ZEN DYNAMIC_ARCH support is broken

Building from source from 20a413e154948d8b7fc47e7a6d9f13cae98e3856 on Ubuntu 16.04 (gcc 5.4.1) with 4.10.1 kernel.
Zen is not autodetected, the machine is detected as Barcelona instead. Trying to manually specify OPENBLAS_CORETYPE=Zen results in Prescott kernels being used.
Removing DYNAMIC_ARCH=1 results in a ZEN kernel. So static detection works (but see next issue, performance is worse than with HASWELL kernel...).
processor       : 15
vendor_id       : AuthenticAMD
cpu family      : 23
model           : 1
model name      : AMD Ryzen 7 1700 Eight-Core Processor
stepping        : 1
microcode       : 0x8001105
cpu MHz         : 1550.000
cache size      : 512 KB
physical id     : 0
siblings        : 16
core id         : 7
cpu cores       : 8
apicid          : 15
initial apicid  : 15
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves clzero irperf arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic overflow_recov succor smca
bugs            : fxsave_leak sysret_ss_attrs null_seg
bogomips        : 7163.90
TLB size        : 2560 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 48 bits physical, 48 bits virtual
power management: ts ttp tm hwpstate eff_freq_ro [13] [14]

AMD Ryzen support is currently very sketchy, please see the notes in PR #1133 if you haven't already. Instead of setting OPENBLAS_CORETYPE=Zen I suspect building with TARGET=ZEN would have worked better ? (Not sure why the DYNAMIC_ARCH build would fallback to BARCELONA unless you disallowed avx - did you get a fallback warning  from the code ?)

No fallback warnings. As explained in the original post, making a static target works (but is useless for me).

Also obviously AVX is working because OPENBLAS_CORETYPE=Haswell works fine.

https://github.com/xianyi/OpenBLAS/blob/develop/driver/others/dynamic.c#L395
This check should've been for "exfamily" instead. I'll patch this up and prepare a pull request.

Right, thanks. I obviously missed that typo when I committed his PR, and did (do) not have the hardware to notice its effect, sorry.

Setting OPENBLAS_CORETYPE=Zen still makes this default to Prescott, so there's more fixes to be done. (Unsetting makes it autodetect correctly)

That appears to be in force_coretype (driver/others/dynamic.c as well) - the for loop that compares corenames runs to 22 only...

Updated the pull request with a fix for that too.


please double check square

please double check square because these are not working correctly
square kilometers
square centimeters
square millimeters
square micrometers

Same with cubic in volume

:tada: This issue has been resolved in version 4.4.3 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


[MariaDB] Can't run migrations with foreign key constraints (SQLSTATE[HY000]: General error: 1025 Error on rename)

Description:
php artisan migrate command fails for MariaDB, but working fine for MySQL.
I'd tried to migrate from MySQL to MariaDB and I stuck because I can't execute Laravel migrations.
Each migration contains code like
    Schema::create('articles', function (Blueprint $table) {
            $table->bigIncrements('id');
            $table->unsignedBigInteger('user_id');

            $table->foreign('user_id')
                ->references('id')
                ->on('users')
                ->onDelete('cascade');
        });

Fails with error like
  SQLSTATE[HY000]: General error: 1025 Error on rename of './db/articles' to './db/#sql2-1-11c' (errno: 168 "Unknown (generic) error from engine") (SQL: alter table `articles` add constraint `articles_user_id_foreign` foreign key (`user_id`) references `users` (`id`) on delete cascade)
This can be fixed by wrapping all the code above with:
 Schema::disableForeignKeyConstraints();
// all the code above
 Schema::enableForeignKeyConstraints();

which is not so good, but something.
But in the next migration file, I have a code like
Schema::create('article_tag', function (Blueprint $table) {
            $table->unsignedBigInteger('article_id');
            $table->unsignedBigInteger('tag_id');

            $table->primary(['article_id', 'tag_id']);

            $table->foreign('article_id')
                ->references('id')
                ->on('articles')
                ->onDelete('cascade');

            $table->foreign('tag_id')
                ->references('id')
                ->on('tags')
                ->onDelete('cascade');
        });

Which fails with a different error
SQLSTATE[HY000] [2002] Connection refused (SQL: alter table `article_tag` add primary key `article_tag_article_id_tag_id_primary`(`article_id`, `tag_id`))
And laradock_mariadb_1 container crashes and I have to remove .laradock/data/mariadb folder to get it working again
Expected Behavior:
Alter SQL queries for MariaDB working as expected, the same as for MySQL, so that it's possible to use MariaDB
Context information:
Output of git rev-parse HEAD
c670d5f98b88aedae8fff4db77790203c0a9cbca

Output of docker version
Client: Docker Engine - Community
 Version:           19.03.5
 API version:       1.40
 Go version:        go1.12.12
 Git commit:        633a0ea
 Built:             Wed Nov 13 07:22:37 2019
 OS/Arch:           windows/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.5
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.12
  Git commit:       633a0ea
  Built:            Wed Nov 13 07:29:19 2019
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.2.10
  GitCommit:        b34a5c8af56e510852c35414db4c1f4fa6172339
 runc:
  Version:          1.0.0-rc8+dev
  GitCommit:        3e425f80a8c931f88e6d94a8c831b9d5aa481657
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Output of docker-compose version
docker-compose version 1.25.4, build 8d51620a
docker-py version: 4.1.0
CPython version: 3.7.4
OpenSSL version: OpenSSL 1.1.1c  28 May 2019

System info: Mac, Windows or Linux. Include which disto/version
Windows 10

Steps to reproduce the issue:

Create a project based on laradock + Laravel 6.2 with MySQL DB
Change DB_HOST to mariadb, change  PMA_DB_ENGINE to mariadb
3. docker-compose up -d nginx mariadb phpmyadmin
create db using artisan command or using PhpMyAdmin
php artisan migrate

Stacktrace & Additional info:
1) **Laravel version**: 6.2
2) The same behavior if I run queries using PhpMyAdmin
3) MariaDB image version 10.4.12, also tried next versions: 10.1, 10.2, 10.5.1-bionic
4) logs

laradock_mariadb_1.log
laradock_mariadb_1_rename.log

SQLSTATE[HY000] [2002] Connection refused
run docker-compose logs mariadb check db log

@bestlong Please find a log
laradock_mariadb_1.log

Might be related to https://github.com/docker/for-win/issues/5604

My issue has been resolved with Docker upgrade to <IP_ADDRESS> version, so I'll close the issue


Added (Python) KMP string matching algorithm

🛠 Issue (Number)

Issue no #138
👨💻 Changes proposed

Added implementation for KMP string matching algorithm in Python.
✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers

📷 Screenshots
Outputs:

@Kumar-laxmi @072arushi @zugzwang03 @siddhi-244
Requesting reviews. Thank you.


Update npm package dependencies

Update npm package dependencies to the latest.
Keeping vue-loader the same at 15.9.7.
Needed to modify webpack.config.js to get css-loader 6.2.0 working - see css-loader CHANGELOG

fronted check fails

There is more work to be done here, like new eslint rule additions, svg rebuild, eslint rule additions, lint error fixes and possibly more stuff based on the changelogs of the affected modules. I can probably follow up with a more complete PR soon.

I am unable to get eslint to resolve path to module 'monaco-editor'  (import/no-unresolved) in features/codeeditor.js

I guess the ESM exports of monaco-editor may have changed or something, I can't find anything in the changelog thought.

PR that should solve everything: https://github.com/go-gitea/gitea/pull/16708


Is that possible to submit to groups via API ?

Either while publishing or after published is it possible via API ?
Ty very much

Not currently, we will be adding it at some point when we update the mobile apps to support groups.


Can I append other blend files object？

I make some PRman render before. Can i link those object back to my new renderman render? Seems all RenderMan Nodetree lost due to append.

This seems related to issue #143. You can import materials its just that you must also import the node-tree separately. Sorry about this but it is related to the material copying. At least there is a workaround for the moment.

Closed because it is possible to link objects and materials seamlessly now.

I should note that I think appending still doesn't work unless you copy
over the node trees manually.
On Fri, May 6, 2016 at 7:29 PM, MWY3510<EMAIL_ADDRESS>wrote:

Closed #177 https://github.com/bsavery/PRMan-for-Blender/issues/177.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/bsavery/PRMan-for-Blender/issues/177#event-653320634

--
<EMAIL_ADDRESS>508-274-8700


Test project build error when installing via VPM

When building any test example, I get an error:
C:\Users\zerg17\.vmodules\rgbcube\color\test.v is defined as module `main`
    1 | import rgbcube.color
      | ~~~~~~~~~~~~~~~~~~~~

The installation was performed by the command "v install RGBCube.color"

The library currently doesn't work because of some compiler bugs:
https://github.com/vlang/v/issues/16473
https://github.com/vlang/v/issues/16496
I am waiting for those to be resolved, then it should work in theory

Also, will fix this asap

Should be fixed in https://github.com/RGBCube/color.v/commit/d820ca3501053772549ed3bba8682b5d09c40934

The error has changed, but it's still in the same place. Why is it necessary to use a pointer there?
C:/Users/zerg17/.vmodules/rgbcube/color/src/paintbrush.v:33:10: notice: interface field `rgbcube.color.BrushImpl.fg` must be initialized
   31 |
   32 | pub fn new_brush_pointer(p BrushParams) &Brush {
   33 |     return &BrushImpl{
      |             ~~~~~~~~~~
   34 |         ...new_brush(p)
   35 |     }

hmm, weird, also it needs a pointer since the method will return a pointer

i think i can't do this as new brush returns an interface

In the example from the documentation, an array of interfaces is created and pointers are not used. I don't see the point in them. https://github.com/vlang/v/blob/master/doc/docs.md#interfaces

Oh, i forgot to make the render method use a pointer, could you PR that? and bump the version

Oh, i forgot to make the render method use a pointer, could you PR that? and bump the version


Upgrade go 1.21

Upgraded go to 1.21

Closing in favor of https://github.com/operator-framework/helm-operator-plugins/pull/242


Latest version doesn't contain a binary for Windows

In rubygems, version <IP_ADDRESS> doesn't have binary packages:
<IP_ADDRESS> - April 20, 2019 (390 KB)
<IP_ADDRESS> - February 06, 2018 x64-mingw32 (6.35 MB)
<IP_ADDRESS> - February 06, 2018 x86-mingw32 (6.07 MB)
<IP_ADDRESS> - February 06, 2018 (390 KB)

This has happened for the past two releases, is this intentional?

11 months on and still no builds?  What's going on ?

It seems that we won't be able to use unf_ext until this is fixed.
This commit (https://github.com/knu/ruby-unf_ext/commit/90fd38bfd32784bfc5f7a7d74d70da7707fa56a2) from @knu claims that there are Windows binaries for 2.6, but they are not in RubyGems?

Just pushed <IP_ADDRESS>!

This is done -- can be closed.


use MAX_REP_LENGTH

use MAX_REP_LENGTH everywhere in implode.c + fix a typo

Merging, thanks for the fix.


[ICU-720] Clear imageContainerStyle on image load

Summary
Clear imageContainerStyle on image load

This is to prevent fix height at center view whenever RHS is expanded.

Ticket Link
Jira ticket: ICU-720
Checklist

[x] Ran make check-style to check for style errors (required for all pull requests)
[x] Ran make test to ensure unit and component tests passed

@jwilander I've updated the PR, making the calculation raised to 100x just to increase precision and make it closer to CSS dynamic dimension.

That feels like magic to me but I'm no CSS expert so if @stephenkiers is OK it with I am too


Update youtube-downloader extension

Description
Added WAV support for audio downloads
closes #14895

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Thanks for the enhancement @ridemountainpig
@vimtor can you check this?

@vimtor, I have moved the option to the format dropdown. Please check it. Thanks.


System.Reflection.TargetInvocationException: 'Exception has been thrown by the target of an invocation.'

Describe the bug
Made a new cross platform app with Android, and Desktop projects. I used to start Desktop project, but after a few changes i ran Android project to see if it looks like the same. So when i start the android project it builds successfull, and splashscreen appears on emulator/physical device but then immediatly gets an error.
Error:
System.Reflection.TargetInvocationException: 'Exception has been thrown by the target of an invocation.'
StackTrace:
0xFFFFFFFFFFFFFFFF in Android.Runtime.JNIEnv.monodroid_debugger_unhandled_exception	C#
0x1A in Android.Runtime.JNINativeWrapper._unhandled_exception at /Users/runner/work/1/s/xamarin-android/src/Mono.Android/Android.Runtime/JNINativeWrapper.g.cs:12,5	C#
0x1E in Android.Runtime.JNINativeWrapper.Wrap_JniMarshal_PPL_V at /Users/runner/work/1/s/xamarin-android/src/Mono.Android/Android.Runtime/JNINativeWrapper.g.cs:122,26	C#
0x29 in System.Reflection.ConstructorInvoker.InterpretedInvoke	C#
0x4 in System.Reflection.ConstructorInvoker.InlinedInvoke	C#
0xBD in System.RuntimeType.CreateInstanceMono	C#
0x3 in System.RuntimeType.CreateInstanceOfT	C#
0xF in System.Activator.CreateInstance<My.App.App>	C#
0x0 in Avalonia.AppBuilder.<>c__49<My.App.	C#
0x62 in Avalonia.AppBuilder.SetupUnsafe	C#
0x65 in Avalonia.AppBuilder.Setup	C#
0x8 in Avalonia.AppBuilder.SetupWithLifetime	C#
0x61 in Avalonia.Android.AvaloniaMainActivity<My.App.App>.InitializeApp	C#
0x1 in Avalonia.Android.AvaloniaMainActivity<My.App.App>.OnCreate	C#
0x11 in Android.App.Activity.n_OnCreate_Landroid_os_Bundle_ at /Users/runner/work/1/s/xamarin-android/src/Mono.Android/obj/Release/net7.0/android-33/mcw/Android.App.Activity.cs:2816,4	C#
0x9 in Android.Runtime.JNINativeWrapper.Wrap_JniMarshal_PPL_V at /Users/runner/work/1/s/xamarin-android/src/Mono.Android/Android.Runtime/JNINativeWrapper.g.cs:121,5	C#

Ohh. One more thing:
Disabled Xaml Hot Reload on Android/iOS projects because found similar issue fixed with it.
To Reproduce
Unfortunately i don't know what caused the error. Other projects run on Android
Expected behavior
After splashscreen, MainView screen appears on Android
Avalonia version
11.0.9, 11.0.10
OS
Android
Additional context
No response

If hard to tell what's wrong here without any code to run and debug.
One moment that looks suspicious is Activator.CreateInstance<My.App.App> in the stacktrace.
How do you initialize your project, specifically AppBuilder part? Is it default from the template? CreateInstance shouldn't be used there.

Thanks for fast answer
I made a new cross-platform solution with VS2022. (Avalonia Extension installed)
I got a similar solution what you get with "dotnet new avalonia.xplat"
In the main project (where you write the shared code) i have this in App.xaml.cs
public override void Initialize()
{
    AvaloniaXamlLoader.Load(this);
}

the OnFrameworkInitializationCompleted() still in App.xaml.cs
public override void OnFrameworkInitializationCompleted()
{
    // set FIRST view
    _frame.NavigateTo(new LoginViewModel());

    if (ApplicationLifetime is IClassicDesktopStyleApplicationLifetime desktop)
    {
        desktop.MainWindow = new MainWindow
        {
            DataContext = _frame
        };
    }
    else if (ApplicationLifetime is ISingleViewApplicationLifetime singleViewPlatform)
    {
        singleViewPlatform.MainView = new FrameView
        {
            DataContext = _frame
        };
    }

    base.OnFrameworkInitializationCompleted();
}

I have another solution where this OnFrameworkInitializationCompleted() runs, so i don't think thats the problem.
In the Android project i have this:
public class MainActivity : AvaloniaMainActivity<App>
{
    protected override AppBuilder CustomizeAppBuilder(AppBuilder builder)
    {
        return base.CustomizeAppBuilder(builder)
            .WithInterFont()
            .UseReactiveUI();
    }
}

I don't see any obvious issue with this code.


Implement hpct-managers library and add sync statuses

This pull request makes the following changes:

Use new hpct-managers library.
Have local manager classes inherit from UbuntuManager.
Drop apt and systemd charm libraries since functionality is now included in UbuntuManager and SystemdManager.
Add sync statuses for slurm-client-ready, auth-munge, slurm-compute, and slurm-controller relations.

I will take the merge request for now and will revisit once Jon and I speak.


Segmentation fault/access violation using Intero on Windows

this produces the bug for me at least for LTS > 8.0:

delete global-project/.stack-work
create a single .hs file in an empty folder
visit the file in Emacs

Intero will start to download/compile its components and once finished I will get this:
Configuring GHCi with the following packages:
Intero 0.1.20 (GHC 8.0.2)
Type :intro and press enter for an introduction of the standard commands.

Segmentation fault/access violation in generated code

---

This is the buffer where Emacs talks to intero. It's normally hidden,
but a problem occcured.

TROUBLESHOOTING

It may be obvious if there is some text above this message
indicating a problem.

If you do not wish to use Intero for some projects, see
https://github.com/commercialhaskell/intero#whitelistingblacklisting-projects

The process ended. Here is the reason that Emacs gives us:

  exited abnormally with code 1

For troubleshooting purposes, here are the arguments used to launch intero:

  stack ghci --with-ghc intero "--docker-run-args=--interactive=true --tty=false" --no-build --no-load --ghci-options -odir=d:/Stack/global-project/.stack-work/intero/intero456D2x --ghci-options -hidir=d:/Stack/global-project/.stack-work/intero/intero456D2x

...

This is on Windows10

just a heads up: same error in VS.code/Haskero

Update: this seems to be luck-based if I restart intero (or call it in the first place) often enough it will work from time to time :(

Update: Intero 0.1.18 build against GHC 8.0.1 using LTS-7.5 resolver (the only additional/different packages that got pulled for this where ghc-paths-<IP_ADDRESS>, syb-0.6, intero-0.1.18) works on the same system without this issue

Not much to do here.

just a follow up on this issue - meanwhile it got a lot worse and yesterday someone gave me a hint on reddit.
This is actually caused by a virus scanner (Hitman.pro which was bought by sophos and runs as part of their exploit prevention) - this one seems to inject dlls into starting processes and those cause GHC, intero, stack, psc-ide and quite a few other tools build with newer GHC versions to segfault randomly on start (seems to be a timing issue - hence the luck involved).
To make it short: I could not find a way to deactivate hitman so I just deinstalled the damn thing and alas everything works fine.
Sorry to bother you here.


WIP: build on Windows

@jbweston

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Add support for code lens to the ruby-lsp

The code lens request allows us to attach a command to a piece of code. The main use case we want to support is running and debugging tests. We can add two commands to each discovered test (run | debug).
Additionally, we can populate VS Code's test interface using the same request. By using a middleware, we can retrieve test cases discovered, populate the test interface and provide similar options to run or debug examples.
Documentation: https://microsoft.github.io/language-server-protocol/specification#textDocument_codeLens

It should be possible to borrow the code lens implementation to try it out.
In terms of the debug integration, it should just be a matter of writing a VS Code command that launches that test with the debugger. Given that RDBG exports a Task already, it should be straight forward.


The react-scripts package provided by Create React App requires a dependency:

There might be a problem with the project dependency tree.
It is likely not a bug in Create React App, but something you need to fix locally.
The react-scripts package provided by Create React App requires a dependency:
"babel-eslint": "9.0.0"
Don't try to install it manually: your package manager does it automatically.
However, a different version of babel-eslint was detected higher up in the tree:
C:\Users\chawki\node_modules\babel-eslint (version: 6.1.2)
Manually installing incompatible versions is known to cause hard-to-debug issues.

Looks like you have that package installed globally. Please try to uninstall it and try again.


Throws warning for valid style property resizeMode

On the image element, resizeMode (resize-mode) is a valid property, but I get a warning:

However, this is a perfect valid property for the Image element.

I don't see this css property documented anywhere. Do you mean resize?

It is specific to react-native.
On Mon, Apr 16, 2018 at 4:04 PM Matt Bierner<EMAIL_ADDRESS>wrote:

I don't see this css property documented anywhere. Do you mean resize?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/typescript-styled-plugin/issues/45#issuecomment-381777152,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABE4A6NhldYP0pTo1ONAftj6sR6AZB3ks5tpSN2gaJpZM4TH1tM
.

Merging into #58


TyphoonAssemblyActivator

Users can still use this class if they wish. However:
Drivers

TyphoonComponentFactory is an extra concept that needs to be learned and read in the documentation. This doesn't need to be the case.
TyphoonComponentFactory being public API increases cost + overhead in maintaining the docs. Especially as we now have Swift version and ObjC version.
Casting between factory and assembly does not work in Swift.

Implementation:
Add the following to Typhoon assembly:

/*
* Returns NO. Facade to the TyphoonComponentFactory method (which returns YES).
*/
@property(nonatomic, readonly) BOOL isBuilt;

/**
* Raises 'not built' exception. Facade to the TyphoonComponentFactory method
*/
- (id) componentForType:(id)classOrProtocol;

Create the following class:
@interface TyphoonAssemblyActivator

@property(nonatomic, copy, readonly) NSArray *assemblies;

- (instancetype) initWithAssemblies:(NSArray *)assemblies;

- (void) build;

@end

The build method will cause the array of non-built assemblies to be replaced with built assemblies.

Before using TyphoonAssemblyActivator, TyphoonAssembly returns TyphonDefinitions (recipes to build instnaces).
After using TyphoonAssemblyActivator, the assembly returns actual built instances.
Everything with TyphoonComponentFactory happens behind the scenes.
No issues with casting in Swift.

Reviewed.
:+1: Nice work!


Can I use jsprit in order to matching trajectories?

Hi All,
My project is a carpooling application (web and mobile) like Blablacar but for  a short distance.
Our Search section do his work but we want improve the routing matching algorithm.
Users (passengers) have to fill this required fields when they search a trip:

Origin,
Destination (postigis coordinates),
max waiting time
max walking distance
time window (day and hour).

The users (Drivers), instead, offers their rides filling this fields:

Origin,
Destination,
seats available,
trip preferences (smoke, music, etc.. number from 1 to 5),
time window (day and hour).

Every user's profile contains trip preferences by default and can be changed every moment.
Our target is return an optimal list of trip offers with trajectory, time window and especially preferences when a user search a particular trip in our search section.
Sprit can we help?
Sincerely,
Gianluca

Sounds like a nice project - would you mind using our forum for questions instead of the issues? https://discuss.graphhopper.com

Thanks - is now asked here: https://discuss.graphhopper.com/t/can-i-use-jsprit-in-order-to-matching-trajectories/562


New Theme and Front Page Layout

We would like to redesign Data Package Registry front page to make it look more elegant and aligned with the brand identity of the site (frictionless: simple, powerful and elegant).
A new design was created (see mockup).
Now we need to implement it using provided images and information(fonts, colours, etc.).
Context and problems

Start implementing in the temporary github repo so others can preview in gh-pages.

Analysis

Create a basic html document according to the mockup - should have header, jumbotron and section for the mockup's second part.
Customize Bootstrap-Sass
Include all required assets
Work on additional stylings for assets
Move to DPR-API

Tasks
Overall estimate: [8h]

[x] Create basic html document [1.5h]

[x] header element [0.5h]

[x] navbar
[x] logo

[x] jumbotron element [0.5h]

[x] background image
[x] main and secondary text
[x] frontground images
[x] sign up button

[x] section element [0.5h]

[x] searchbox
[x] grid for text with boxes
[x] elephant with numbers image

[x] Customize Bootstrap-Sass [1h]

[x] fonts [0.5h]
[x] necessary variables - colours, backgrounds [0.5h]

[x] Include all assets and work on sylings [4h]

[x] work on sizing and placing [2h]
[x] work on general layout staylings [2h]

[x] Move to DPR-API [1.5h]

[x] integrate with DPR-API templates [1h]
[x] replace old stylesheets with new one [0.5h]

FIXED in https://github.com/frictionlessdata/dpr-api/pull/279
Everything from the issue's description was achieved. Now we are using a new layout for the front page:

The issues found:

Search box is not working.
Signup in front page not working.
Navbar

Does not have search box.
Publish data tab does not work.
Find data tab does not work.
Data package tab does not work.
navbar-header class should point to / instead of #

FIXED in https://github.com/frictionlessdata/dpr-api/pull/285 and https://github.com/frictionlessdata/dpr-api/pull/286


[todo] Global beacon import indicator

We will have an indicator in the header that will indicate be update periodically and will display when beacons are being imported.
We will need to have a table a log table that will keep an information about number of imported beacons. Periodically we will read the latest records of the table and we will update the indicator. We could use Plotly for rendering the indicator.
Ref:

Closing - we move to Grafana


Items not dragging properly

Hey Philip,
I noticed dragging didn't work the same, when the change from pixels to matrix3d transforms was made (so, <IP_ADDRESS> works, but 0.0.4 doesn't).
The older, working version:

The lastest version:

I tried seeing what the motivation was for the change (#74), but couldn't get a clear picture of it. Any ideas on how to proceed?

cc @janober

:+1:

One idea I had was to have the way it drags configurable, since it seems like there are a few use cases for dragging. Similar to what I did in #105 for debug logging, we could have a configuration option to drag in pixels, or to do a transform. In that case, the ngDraggable provider could return the CSS for movement, depending on which method was chosen.

@imcnally your issue looks like a simple CSS issue. Try setting the z-index on your dragging element or maybe set it to fixed.
Additional there is already an option of disabling transform movement. data-allow-transform="false"

Uh sorry for the issues! Does the solution from above work?
The reason I made the change was that before it broke (the item had an offset) when a parent element had a matrix3d transform on it which for example famo.us uses a lot.

@fatlinesofcode z-index is set to 999999 by the drag directive, so manually setting it did nothing. By "set it to fixed", do you mean position: fixed?
Also, disabling the transform didn't help. The draggable item simply disappears when I click on it.

+1

Do you have a fiddle example?
On 19/03/2015 9:17 am, "Juha Karttunen"<EMAIL_ADDRESS>wrote:

+1
—
Reply to this email directly or view it on GitHub
https://github.com/fatlinesofcode/ngDraggable/issues/103#issuecomment-83205878
.

I tried making one but couldn't replicate the issue. I'll keep trying.
On Wed, Mar 18, 2015 at 6:31 PM, Philip Andrews<EMAIL_ADDRESS>wrote:

Do you have a fiddle example?
On 19/03/2015 9:17 am, "Juha Karttunen"<EMAIL_ADDRESS>wrote:

+1
—
Reply to this email directly or view it on GitHub
https://github.com/fatlinesofcode/ngDraggable/issues/103#issuecomment-83205878
.

Reply to this email directly or view it on GitHub:
https://github.com/fatlinesofcode/ngDraggable/issues/103#issuecomment-83209922

Looks like removing overflow: auto from direct parent helps on my case

Okies, seems like this is of course expected browser behaviour, CSS transforms should not be drawn outside container with overflow:hidden.

@jkarttunen you were right about overflow: auto. Demo here: http://codepen.io/imcnally/pen/ByvaeK

Not sure how to fix this other than using position : fixed and coordinates instead transform ... :/

using data-allow-transform="false" fixes this.
Lets add that to the readme, pretty please.

I tried allow-transform on the pen and it throws off position on other elements.

@imcnally Not sure what you mean by 'throws off position on other elements' ?

If you start dragging them item in the example I posted, you'll notice the
drop area shifting down while dragging.
On Wed, Mar 18, 2015 at 7:18 PM, Juha Karttunen<EMAIL_ADDRESS>wrote:

@imcnally https://github.com/imcnally Not sure what you mean by 'throws
off position on other elements' ?
—
Reply to this email directly or view it on GitHub
https://github.com/fatlinesofcode/ngDraggable/issues/103#issuecomment-83221364
.

--
best,
Ian

On Safari yes, not on Chrome or FF.

I guess rolling back is best. Does not seem like there is an easy and good solution. Also nobody else seems to use "matrix3d transform" anyway. So rolling back my change makes the most sense.

Are you using bootstrap?  If so I had a similar issues regarding rows and columns an was able to overcome it by adding css position: relative; on the dragging element.
[ng-drag].dragging {
  position: relative;
}

Thanks @josephlavin. That fixed my issue with it hiding behind a bootstrap column.

Just add position absolute to the dragging object
[ng-drag].dragging {
position: absolute;
}

I have the same problem. Does anybody know how to solve this?

@amuste that didn't solve the issue for me.
position: absolute didn't resolve this for me. I've heard the same from others I've spoken to about this.
transform3D doesn't abide by z-index.

@dbounds  See the plunker
http://plnkr.co/edit/bWQ7JEei3O5AIr2tW1g9?p=preview
in style.cs find .listbox-content > ul > li.dragging {} and remove
"position: absolute ". to see the result behaviour.

I have the same issue with angular-bootstrap-calendar, the element hides it itself when dragging to other view or scroll div. I tried ngDraggable but it didn't work either. None of the solutions above helped me =/
http://stackoverflow.com/questions/42928979/event-hiding-on-dragging-to-parent-view-in-angular-bootstrap-calendar

is there any solve this???


Align docstring

Using the docstring detection, would it be possible to perform formatting to match https://github.com/bbatsov/clojure-style-guide#align-docstring-lines ?

Thanks for the suggestion!  It is always interesting to know what people are looking for.
It would help me to know in more detail what you are asking so that I know whether or not what I can do would in fact be useful to you.
I could certainly ensure that there is a minimum indent, and turn this:
(defn foo
  "Foo does this and that, and sometimes
 with the right inputs, does other things too."
  [a b c]
  ...)

into this:
(defn foo
  "Foo does this and that, and sometimes
  with the right inputs, does other things too."
  [a b c]
  ...)

However, going the other direction, there is a problem distinguishing this:
(defn foo
  "Foo does this and that, and sometimes
            with the right inputs, does other things too."
  [a b c]
  ...)

from this
(defn foo
  "Foo does this and that, and sometimes
  with the right inputs, does other things too.
    Inputs:
      a     good stuff
      b     bad stuff
      c     stuff
    Returns:
      Some things that you wouldn't believe"
  [a b c]
  ...)

so if I try to move things from the right over to the left, I can end up with this:
(defn foo
  "Foo does this and that, and sometimes
  with the right inputs, does other things too.
  Inputs:
  a     good stuff
  b     bad stuff
  c     stuff
  Outputs:
  Some things that you wouldn't believe"
  [a b c]
  ...)

which in my view messes up the original authors good intentions in order to make a change that probably is rarely necessary.
So, while it is a certain amount of work (some of which i've already done to put specs into the docstrings), if you would be satisfied with the original "ensure that there is a minimal ident" I would be happy to put that on the list of things to implement.  If you wanted more radical transformations, then I'd like to know specifically what you have in mind (and how you imagine that I might distinguish when the more radical transformation were justified).  Some examples would be helpful to illustrate what you have in mind.
Thanks again for the suggestion!

You're right, this is difficult to do, particularly as there's so few standards around this. I think a minimum indent would be helpful, some people simply forget. I do sometimes see alignment like this too:
(defn x
  "Foo
   Bar"
  [baz] …)

I'm wondering if detection for the case where all the lines have an additional indentation of +1 would be valuable also.

Sounds reasonable, I think I could figure out how to remove the +1 indentation (and let +2 and greater stay).  It may be a while before I can get to this, but I'll put it on the to-do list.  Thanks for the idea!

Thanks for taking the time to consider it
Dominic
On 13 Jun 2017 3:25 am, Kim Kinnear<EMAIL_ADDRESS>wrote:
Sounds reasonable, I think I could figure out how to remove the +1 indentation (and let +2 and greater stay). It may be a while before I can get to this, but I'll put it on the to-do list. Thanks for the idea!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


instance of suspicious comments

Greetings,
I am a security researcher, who is looking for security smells in Ansible scripts.
I found instances where certain keywords such as TODO, HACK, FIXME, bug repository IDs, in comments within Chef scripts.
According to the Common Weakness Enumeration organization this is a security weakness
(CWE-546: Suspicious Comment https://cwe.mitre.org/data/definitions/546.html).
I am trying to find out if you agree with the findings. I think it is possible to have a nuanced perspective. Any feedback is appreciated.
Any feedback is appreciated.
source: https://github.com/openshift/openshift-tools/blob/prod/openshift/installer/vendored/openshift-ansible-3.5.127/playbooks/common/openshift-cluster/upgrades/v3_5/validator.yml

Since the file that you mentioned does not exist anymore, can you point out what exactly you were looking for and what you found?

/lifecycle stale

/close


Re-work site layout using css grid

Experimental?
https://alistapart.com/article/practical-grid
What's the browser support look like for this?
Is it still too early?

Definitely too early to implement but i'm looking forward to more browser adoption bc this is gonna be the besssttttttt

browser versions weighted by global usage

Thanks


fix: correct get_view_names for older sqlalchemy

fix bug

AttributeError: 'Connection' object has no attribute 'exec_driver_sql'

add schema support.

BEGIN_COMMIT_OVERRIDE
fix: add schema support to get_view_names
END_COMMIT_OVERRIDE

just notice,
Superset does not support sqlalchemy 1.4 and newer,
so does not support  exec_driver_sql
so for new version  sqlalchemy,
s = f"SELECT table_name FROM information_schema.tables WHERE table_type='VIEW' and table_schema=%s "
schema = schema if schema is not None else "main"
rs = connection.exec_driver_sql(s % schema)

and for old version, should
s = f"SELECT table_name FROM information_schema.tables WHERE table_type='VIEW' and table_schema=? "
schema = schema if schema is not None else "main"
rs = connection.execute(s ,schema)
``

or view will not show.

Which old versions of sqlalchemy are you trying to support?

It looks like the current superset version only supports >=1.4
https://github.com/apache/superset/blob/master/setup.py#L118

I've merged most of these changes in another pr, #404 so thanks for those. The remaining changes don't seem to be required and in fact introduce a potential security issue
The fixes will be released shortly


Create and  Implement login endpoint

Implementing Login Endpoint in Express using JWT
Description
Create an Express.js endpoint for user login, using JSON Web Tokens (JWT) for authentication. This login functionality will provide a secure authentication mechanism for user sessions.
POST  /login
Tasks

[ ] Implement a route for user login that verifies the provided credentials and generates a JWT for authenticated users. This should be under controller
[ ] Create a middleware function to verify the JWT for protected routes. create a directory middleware and implement the function in auth.js
[ ] Test the login endpoint using tools like Postman or curl.
[ ] Document the implementation process and provide usage examples.

Related Links

JWT.io - JSON Web Tokens Introduction

I would like to work on this under hacktoberfest!


features: can we email data on the basis of login rights

I think if we have features to restrict data on the basis of users' login rights to store and also if to send all data to users.
So I think if we can have features that can handle both.

Closing no need for now.