LABS

Grant Application Checklist

[x] The application-template.md has been copied, renamed ( "project_name.md") and updated.
[x] A BTC address for the payment of the milestones is provided inside the application.
[x] The software of the project will be released under the Apache license version 2.0 as specified in the terms and conditions.
[x] The total funding amount of the project is below CHF 30k at the time of submission.
[x] The initial PR contains only one commit (squash if needed before submitting your PR).

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: Dev@labsgroup.io:x<EMAIL_ADDRESS>seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

This is the third time you've submitted an incomplete application. If you want to participate in the Grants Program, please submit a filled-out template, else your user will be blocked from our repos.


DOC/REL: prepare 0.15.0 changelog and release

We accumulated a few important bug fixes and new features, so it seems time for a release.
@dnicolodi I set the date to today - in case it gets merged later, that date should be updated right before the merge.

@rgommers Thanks for working on this. The changelog entries for other releases use the present tense, but the ones for 0.15.0 used the past tense. I took the freedom to fix them to use the present tense and to do some rewording PTAL.

Thanks @dnicolodi, LGTM! Let me just bump the date once more, and then I'll get this release done.

Thanks @rgommers. The changelog in the present tense reads a bit strange to me too, but this is how it was started, and I think there is value in keeping it all in the same form.

Yes, agreed. We may want to change it at some point, but let's consider it only if we make other changes like adding change categories (bug fix, enhancement, backwards compatibility, etc.).


[RTBF] error

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I remove or skip any mandatory* field

Checklist

[X] I'm reporting a broken site
[X] I've verified that I'm running yt-dlp version 2022.08.19 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
Europe
Provide a description that is worded well enough to be understood
downloaded mp4/dash can't be decoded since today
ffprobe of mp4 file:
[h264 @ 000000daa93150c0] top block unavailable for requested intra mode -1
[h264 @ 000000daa93150c0] error while decoding MB 0 0, bytestream 405
[h264 @ 000000daa93150c0] concealing 8160 DC, 8160 AC, 8160 MV errors in I frame
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'demain.mp4':
Metadata:
major_brand : iso6
minor_version : 0
compatible_brands: iso6dash
Duration: 00:29:11.10, start: 0.040000, bitrate: 5221 kb/s
Stream #0:00x1: Video: h264 (Main) (avc1 / 0x31637661), yuv420p(progres
sive), 1920x1080 [SAR 1:1 DAR 16:9], 5192 kb/s, 50 fps, 50 tbr, 600 tbn (default
)
Metadata:
handler_name : USP Video Handler
vendor_id : [0][0][0][0]
encoder : AVC Coding

decrypting error
[0831/204315:INFO:demuxer.cc(89)] Demuxer::Run() on file 'demain.mp4'.
[0831/204315:INFO:demuxer.cc(155)] Initialize Demuxer for file 'demain.mp4'.
[0831/204325:ERROR:demuxer.cc(356)] Failed to process sample 256 5 (FILE_FAILURE
): Fail to write to file in BufferWriter
[0831/204325:ERROR:mp4_media_parser.cc(889)] Failed to process the sample.
[0831/204325:ERROR:packager_main.cc(554)] Packaging Error: 8 (PARSER_FAILURE): C
annot parse media file demain.mp4
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8 (No VT), erro
r utf-8 (No VT), screen utf-8 (No VT)
[debug] yt-dlp version 2<IP_ADDRESS> [48c88e088]
[debug] Lazy loading extractors is disabled
[debug] Plugins: ['SamplePluginIE', 'SamplePluginPP']
[debug] Python 3.8.2 (CPython 64bit) - Windows-8.1-6.3.9600-SP0
[debug] Checking exe version: ffmpeg -bsfs
[debug] Checking exe version: ffprobe -bsfs
[debug] exe versions: none
[debug] Optional libraries: certifi-2022.06.15, sqlite3-2.6.0, websockets-10.3
[debug] Proxy map: {}
[debug] Loaded 1667 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releas
es/latest
Latest version: 2022.08.19, Current version: 2<IP_ADDRESS>
yt-dlp is up to date (2<IP_ADDRESS>)

sample download url
G:\yt-dlp-rtbf>yt-dlp.cmd --cookies-from-browser firefox -f video=5642 --trim-fi
lenames 6 --allow-u https://www.rtbf.be/auvio/detail_demain-nous-appartient?id=2
933646

works with bento mp4decrypt


T-001 Geno data object. Check and write/edit documentation for it.

See https://r-pkgs.org/data.html#documenting-data for a good overview of how to document data.

Add rownames to Geno to match I_meta

Add NAs to the data to check all the functions handle missing data properly. Make sure there is at least one NA genotype within the first few individuals and first few loci

This looks all done to me!


Add raw request URI property to IHttpRequestFeature

Path and PathBase might lose some information. Expose the raw, unaltered request URI via the new property.
Related: https://github.com/aspnet/KestrelHttpServer/issues/594
This will also mitigate the loss of information in https://github.com/aspnet/KestrelHttpServer/issues/709 and https://github.com/aspnet/KestrelHttpServer/issues/666.

@blowdart because we always freak out with regard to security and so-called "raw" URLs. I'm personally a fan of giving raw access to data, but URLs can be dangerous unless you really, really, really know what you're doing.

Yes, sufficiently so that I'd considered making it its own feature, but that seem a little excessive.

I should add a corollary to my earlier comment:
It is a well-known fact that when it comes to URLs, no one knows what they're doing.

I have no real objection to them being exposed. However we mustn't use them anywhere ourselves. We must always operate on the canonicialized string.
The doc comments should reflect the danger of using URLs in their RAW forms.

Can we add an attribute that makes using that field a compiler warning you need to suppress? Obsolete(Warning)?

I think marking Raw URL getter deprecated/obsolete would be very misleading considering we have no plans to expose the same data in a newer/better API.

I know Obsolete isn't ideal, but it's the only one I'm aware of that triggers a compiler warning. Are there others?

Please don't mark is as obsolete. There is no other attribute that does this. Either we add the property and it's a real property, or we don't add it at all.

@cesarbs Let's do this in 1.0


Add new modular template

Hello everybody,
I don't know if I'm in the right place to ask my question... but I don't know where to ask it.
I want to add a template in modular section that I named "inserts" and that is based on "features".
For this, in my theme, I have created or modified the following files :

in templates/modular : I created inserts.html.twig
in blueprints/modular: I created inserts.yaml
in scss/theme: I modified _onepage.scss
in css: I add my new css in custom.css

In the administration interface everything is displayed correctly, in my inserts.md too.
But in my online page only the content (text) is displayed but not my equivalent of "features".
Would you have a solution, a research track to help me?
Thanks

I have resolved my problem, i have forgotten a few “s” in my .yaml


Added AsRef implementation for TextStyle

Objective
Make using parameter structs less annoying.
This is a cool feature of Rust that I recently found out about. If you are making a function that takes in a struct with defining info like TextStyle, you will probably think that taking a borrow is better than ownership. But that depends on the use case. Sometimes the user will create the struct beforehand and will pass out references to it. Or sometimes he initiates the struct directly in the argument with something like ::new().
fn foo (style: &TextStyle) {
   style.do_something()
}

foo(&style);
foo(TextStyle::new()); // Doesnt compile, forced to add "&"

In the latter case, he is used to write "&TextStyle::new()" instead of just "TextStyle::new()", which is bothersome. But the other case is taking an ownership, which if he used it like the first example, he would need to do .clone() which is even worse.
But what if there is a way to do both at once?
We can implement the AsRef<TextStyle> to the struct and change the function a bit.
fn foo (style: impl AsRef<TextStyle>) {
   style.as_ref().do_something()
}

foo(&style);
foo(TextStyle::new()); // Works just fine

It allows us to leave out the "&" where it is not needed. You might think it is an unnecessary change, but I think it's quite nice UX improvement without any sacrafice (Maybe it's less clear what impl AsRef<TextStyle> but thats about it)
I have been using this in Bevy-Lunex for a while and it's quite pleasant.
I suggest we implement this trait to every parameter struct that is being massively passed like this.

Hmm, I think I can see the appeal, but I'm a little nervous to merge this without a motivating in-engine use case or clearly-improved example. Is there a place in bevy_ui currently where this pattern would be nice?

You can use Borrow<T> instead which is already implemented for all T.
fn foo (style: impl Borrow<TextStyle>) {
   style.borrow().do_something()
}

foo(&TextStyle::new());
foo(TextStyle::new());

You can use Borrow<T> instead which is already implemented for all T.
fn foo (style: impl Borrow<TextStyle>) {
   style.borrow().do_something()
}

foo(&TextStyle::new());
foo(TextStyle::new());

Haa, this makes this PR obsolete. I removed AsRef and AsMut and changed function parameters in text.rs to Borrow<>. And I updated the text2d.rs example to not use .clone() after each style usage. So now it's just an update to text example and 2 functions.

I've read about Borrow in the docs, and looking at that PR description, unless I'm mistaken I think it's misusing it, so I'm against this change.
Borrow is designed to borrow a type as another type, like borrow a String as a str. It's not designed to make value and reference be accepted for the same type.
What this change does is obfuscating the semantic of the function (we don't know if it wants a reference or a value), and doing so via a trait which will probably incur a virtual call. That's a lot to avoid a single & character.

Borrow is designed to borrow a type as another type, like borrow a String as a str. It's not designed to make value and reference be accepted for the same type.

If this was the case then std would not have a blanket impl of Borrow<T> for &T.
Quoting these docs:

Unlike AsRef, Borrow has a blanket impl for any T, and can be used to accept either a reference or a value.

It seems very much like the intended use-case.

doing so via a trait which will probably incur a virtual call.

There's definitely no runtime cost to using traits unless you're explicitly doing dynamic stuff.


Additional attributes for the derived table agreements_custom_property

A few additional attributes for the derived table agreements_custom_property. In particular, the ID for linking to the subscription_agreement table.

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

Apparently there is a problem with an attribute in invoice_voucher_lines_fund_distributions.sql . Please fix it.


SD TTNN: TtDownsample2D

Implement subgraph TtDownsample2D and make two tests: one for 256x256 image size and one for 512x512 image size.
Have one test file named something like test_downsample_2d.py and inside it two tests test_downsample_2d_256x256 and test_downsample_2d_512x512. Tests should be parametrized with following input shapes:

[ ] Shape 1:  256x256

[ ] hidden_states case 1: [2, 320, 32, 32]
[ ] hidden_states case 2: [2, 640, 16, 16]
[ ] hidden_states case 3: [2, 1280, 8, 8]

[ ] Shape 2:  512x512

[ ] hidden_states case 1: [2, 320, 64, 64]
[ ] hidden_states case 2: [2, 640, 32, 32]
[ ] hidden_states case 3: [2, 1280, 16, 16]

Downsampled2D and the two tests for 256x256 image size and for 512x512 image size is done.
Here is the commit link: commit
When attempting to preprocess the model parameters using preprocess_model_parameters, a runtime error occurred in the ttnn.conv operation with the message RuntimeError: Transpose conv weights?.
As a workaround, we proceeded by manually loading weights and biases.

Issue created at #4878 for conv

Corresponding PR - #5090
Currently, working on using ttnn.Conv2D instead of fallback_ops for conv.

PR is merged, hence closing the ticket.


Azure AD Deployment plans

Aka.ms link name
https://aka.ms/DeploymentPlans
Category (Optional. Select None to auto-select)
azuread

Thank you for submitting aka.ms/DeploymentPlans. Your link already exists at akaSearch.net. 🙏✅


[Bug]: Module '"input-otp"' has no exported member 'OTPInputContext'.ts(2305)

Describe the bug
Since the last commit, I noticed that there is a new context being imported from input-otp.
I tried reinstalling this module but I still get the error that this context is not exported from the package.
Affected component/components
InputOTP
How to reproduce

Open project in apps/www/registry/default/ui/input-otp.tsx
See this error:

Codesandbox/StackBlitz link
N/A
Logs
No response
System Info
MacOS, VSCode

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

hi @flixlix make sure you have ran npm i input-otp@-latest to ensure it's the latest version.
let me know if that works?

yep, that fixed it, thanks!


Log unrecongnized resource quota parts instead of returning an error

Fixes #1137
An alternate solution (or possible addition to this change) would be to capture the resource quota parts that were triggering the error. The parts in question are not useful to me and I'm not sure if they are generally useful so I didn't make that change.

I'm missing the full context on this, but I think not erroring is correct. I also think that not warning may also be correct. What is the value of warning? Would you also warn if an undocumented response header came back from the service?

FWIW, the warning is there mostly out of excessive caution, just in case it happens to be useful to someone, because I'm relatively unfamiliar with this code. I have zero objections to removing it.

BTW, we squash-merge so your fork's main will be different than the upstream main. I recommend always creating a topic branch in your fork and open a PR to merge that into main, such that your main is always in sync - if not behind, but fast-forwardable - with upstream main.


Invalid metadata causes crash in gRPC (triggers an assert)

What version of gRPC and what language are you using?
Language: C++
Version: 1.18.0
What operating system (Linux, Windows,...) and version?
Ubuntu 16.04.5 LTS
x86_64
What runtime / compiler are you using (e.g. python version or version of gcc)
gcc (Ubuntu 5.4.0-6ubuntu1~16.04.11) 5.4.0 20160609
What did you do? What did you expect to see? What did you see instead?
In gRPC C++, placing invalid metadata causes an assert to be triggered, which is crashing our entire app in production. Here is a repro:
    std::string target = "";
    auto grpc_channel = grpc::CreateChannel(target, grpc::InsecureChannelCredentials());
    std::shared_ptr<SeDatastoreRpc::Stub> stub = SeDatastoreRpc::NewStub(grpc_channel);
    auto request = SeDatastoreGetReq();
    auto response = new SeDatastoreObject();

    ClientContext context;
    context.AddMetadata("version", "\272\253\001\000\000\000\000\060\062\071) 2019-01-11 10:08:05 UTC");
    stub->Get(&context, request, response);

I would expect this to error out gracefully and not crash the app.  But instead, we see a crash from triggering an assert:
E0326 22:23:55.723905898   18932 call.cc:897]                validate_metadata: {"created":"@1553639035.723888113","description":"Illegal header value","file":"src/core/lib/surface/validate_metadata.cc","file_line":43,"offset":0,"raw_bytes":"ba ab 01 '...'"}
E0326 22:23:55.724043413   18932 call_op_set.h:872]          assertion failed: GRPC_CALL_OK == g_core_codegen_interface->grpc_call_start_batch( call_.call(), ops, nops, core_cq_tag(), nullptr)
Aborted

Ideally gRPC would simply discard this invalid metadata and send the RPC without it. Or it would return an error saying that the metadata is invalid. However, I feel that crashing in this case is not ideal.
If this assert absolutely must exist, then perhaps it would be ideal to have an option to silence all asserts at compile time.

Any thoughts on this?

You're tripping on the assert because you're using the API incorrectly.
https://github.com/grpc/grpc/issues/18536#issuecomment-477684270 explains why an assert is required.


Binary Strings

Strings have some bad memory segments, probably related to array allocation and concatenation mid write.
many are spliced with: ﮷�

is this still a bug?

String related test vectors were cleared from the skiplist by https://github.com/amzn/ion-js/pull/461


'Follow link' on href of xsl:import does not work

I have attached a zip of a simply project. master.xslt which includes properties.xlst (in the same folder)
If I Ctrl+Click on the href, I get an error message:

The path in the error message is the correct path to the file.
test.zip

Thanks for reporting this issue. I'll provide an update as soon as I've investigated further.

Just to confirm, I can reproduce this issue on my test Windows machine. The path seems to be treated as a URI when being resolved from a relative path.

The problem was that the file path string was not being correctly converted to a URI string before being parsed to a URI type. This issue has now been fixed in Release v0.2.2


Feature/load config from server

This allows the user to configure the widget on the server and load the config from there. (additionally to the local props)
ref #84

(ups, there is an old commit in this PR)

merging this as we are experimenting with the embedding


Verify the content of dummy page loaded in BrowserPanel

When a contact is selected in the PersonListPanel, a dummy "search" page
now shows up on the BrowserPanel. Tests that checks the BrowserPanel
currently verifies only the URL loaded by the BrowserPanel.
As we now control the dummy page, we could strengthen such tests, by
ensuring that the content of the dummy page is as what we expected.
Let's enhance the tests involving BrowserPanel to ensure that the
content of the dummy page actually loads properly.

I don't think this would be very useful, since students won't be using the dummy search page in their actual product.
The method that is used to verify the content in the dummy search page would also very likely fail in the more dynamic websites that students use.

I'm Ok to close this issue.


General: SPIKE - check out asyncclick

Could be useful for speeding up parts of the application
https://github.com/click-contrib/asyncclick

duplicates: #842


arara.sh is behaving wrong

when using arara.sh from TexWorks, using the command option:
/usr/local/texlive/2019/texmf-dist/scripts/arara/arara.sh
it raise an error about command not found
it is examping basename as arara.sh
If I change the script name and put simply arara it is working again.
I'm using Texlive from a tlmgr installation, not using the Distribution package.
Regards
Carlo D.

TeX Live creates symbolic links in the bin architecture sub-path to applications in scripts with the extension omitted. For example, /usr/local/texlive/2019/bin/x86_64-linux/arara is a symlink to /usr/local/texlive/2019/texmf-dist/scripts/arara/arara.sh. This means that you simply have to type arara not arara.sh on the command line because the PATH environment variable should include the bin/arch path not the scripts path. In general, it's best to use the bin path rather than the scripts path if you have to specify the full pathname. (This isn't specific to arara. There are other bash scripts that also expect to be called via the symbol link.)
@cereda Perhaps
scriptname=`basename "$0"`

should be changed to
scriptname=`basename "$0" .sh`

OK, sorry for the inconvenience, I have followed a hints on activating arara for TexWorks, and this hint used the path in the scripts and not those in the bin dir.
Regards
Carlo D.

It's useful to have a record here in case anyone else has the same problem.

Ciao, Carlo!
Thanks for the report, it's much appreciated!
I am almost sure this issue is connected to this message of mine in the TeX Live mailing list.
We will investigate further. Grazie mille! :wink:
@nlct I still believe TeXworks is the culprit here, as in not our fault :wink:. We could raise the concern with Karl and Norbert and check if they have any pointers for us...

I'm not clear enough in the last message.
I've resolved using the invocation of arar in Texwork using:
arara without specifing the path
and putting
$basename
in the "Arguments" frame (hope this is the exact translation, I'm using an Italian localized version of Texwroks)
Hope it will be useful, maybe to write in the wiki some hint about the use of arara in Texworks.
Using Arch Linux (ArtixLinux to be exact) for TexWorks, it is not heavily patched (relatively to some other distributions).
Regards
Carlo D.

Thanks, Carlo! The previous version had a section in the user manual for editor integration. It seems it would be great to bring it back. :wink:
I think I use $fullname in TeXworks, but I will investigate.
For now, thank you very much for the report!

In version 5.0 (in MikTeX and TL pretest) the suggested change from https://github.com/cereda/arara/issues/135#issuecomment-585638437 has been integrated (see ece4b038f841e3de1245730e2c84da2986bd4c6d). Does this fix your issue?

I'll close that issue for now. If it isn't fixed in version 5.0.2, please reopen and describe what's not working.


[WFLY-17814] Connector: log exception thrown during a failed deployme…

…nt of a resource adapter module
https://issues.redhat.com/browse/WFLY-17814

Thanks @tadamski


scylla_repository: patch systemctl calls out of install.sh

extend fix from https://github.com/scylladb/scylla-ccm/commit/424dd4445b6fc0c678e9505b00a0df0cdb39939b to
all install.sh scripts inside the unifed-package.
Fix: https://github.com/scylladb/scylla-dtest/issues/3060

testing in:
https://jenkins.scylladb.com/job/scylla-staging/job/fruch/job/new-dtest-pytest-parallel/279

Test passed in:
https://jenkins.scylladb.com/job/scylla-staging/job/fruch/job/new-dtest-pytest-parallel/280/


Rank-reduced models?

Do you publish the rank-reduced models anywhere?

We dont release them but they are taking the standard huggingface models and apply the right reduction. The list of optimal reduction is in Table 3 of the paper https://arxiv.org/pdf/2312.13558.pdf.
I suppose it can be a good feature to add to get the reduced LLM model with these pre-selected choices for people to reproduce our results. I am making a list of features for the upcoming refactoring. I'll add this to it.
Let me know if you have more questions.

Related to #9

How much memory requirement can we reduce if we store weights in SVD format?

If you have a mxn matrix then your memory is mn. If you reduce the rank down to k using SVD, then you will store mk + k^2 + kn. Imagine k=1, then this comes down to just m + n + 1. If you reduce it to 1% of the max rank (and say m > n and so max rank is n), then you have k=n/100 and you get mn/100 + (n/100)^2 + n^2/100 <= mn/50 + mn/(10000) ~ mn/50, so about 50 times shrinkage.


Suggest adding T.absurd when it's trivially possible

Problem

This program already exhausts all the cases:
# typed: true
class A; end
class B; end

extend T::Sig

sig {params(ab: T.any(A, B)).void}
def foo(ab)
  case ab
  when A
    puts 'A'
  when B
    puts 'B'
  end
end

→ View on sorbet.run
Proposed solution
We could add an error (or autocorrect!) to add else T.absurd(ab) to the end of the case statement.
It's unclear when we should do this, and it could potentially be pretty noisy. Off the top of my head, I would think we should do it only for case statements (not if statements) that don't have an else. We'd have to see how much of a breaking change that would be.

There is already precedent for this; I made a change similar to this on a branch that was never pushed or reviewed when I was driving up adoption of T.absurd internally on Stripe's monorepo.

Relates to #3634


crash when accessing configuration

get crash when trying to access stores>configuration on M2.3.4 also error on 2.3.2 it seems shown here https://magento.stackexchange.com/questions/284817/how-can-i-show-full-breadcrumbs-category-path-on-product-page-in-magento-2-3

Install this module also, https://github.com/EaDesgin/eacore
And try again ;)


Add support for Roborock S7 maxV

Just tried installing the plugin with Roborock s7 maxV, but getting this error in the logs :
[Roborock S7 maxV] WAR changedSpeed | roborock.vacuum.a27 | Speed was changed to 106%, this speed is not supported

Thanks to @khad, https://github.com/homebridge-xiaomi-roborock-vacuum/homebridge-xiaomi-roborock-vacuum/releases/tag/v0.22.0 will now support this model.


Tile caching has hardcoded ParkInfo wording in it

MapCtrl.js has "ParkInfo" hardcoded, and this is really not good.

Now it properly connects the tileload event to the layer which triggered it, instead of to a hardcoded layer name.


Using appcenter-cli version: 3.0.0 Error: Failed to create release upload for build/app/outputs/flutter-apk/app-blastgolf-release.apk. Backend response: Not found. Correlation ID: 6d547d0e-497e-4231-8aa4-a9ca8641fdf2

Description
I am getting the following error in gitlab ci logs
Using appcenter-cli version: 3.0.0
Error: Failed to create release upload for build/app/outputs/flutter-apk/app-blastgolf-release.apk. Backend response: Not found. Correlation ID: 6d547d0e-497e-4231-8aa4-a9ca8641fdf2
**Here is the code **
flutter_build_android:
when: manual
stage: build
before_script:
- flutter clean
- flutter packages get
- flutter gen-l10n
- npm install -g appcenter-cli@latest
script:
- |
if [ $FLAVOR == "blastgolf" ]; then
FLAVOR_PATH="blastgolf"
FLAVOR_TARGET="lib/blast_golf/main_blast_golf_staging.dart"
APP_NAME="Blast Golf"
elif [ $FLAVOR == "blastbaseball" ]; then
FLAVOR_PATH="blastbaseball"
FLAVOR_TARGET="lib/blast_baseball/main_blast_baseball.dart"
APP_NAME="Blast Baseball"
else
echo "No Flavour provided"
fi
flutter build apk --release --target $FLAVOR_TARGET --flavor $FLAVOR_PATH
echo "FLAVOR_PATH: $FLAVOR_PATH"
echo "APP_NAME: $APP_NAME"
APK_PATH="build/app/outputs/flutter-apk/app-$FLAVOR_PATH-release.apk"
#APK_PATH="build/app/outputs/apk/blastgolf/release/app-$FLAVOR_PATH-release.apk"
echo "APK PATH: $APK_PATH"
- echo "logs"
- appcenter login --token $token
# - appcenter distribute release -f "$APK_PATH" -g "Android-QA" -a admin-bjzg/NextGen-Blast-Golf-Android --release-notes "Version $buildNumber" --debug
- FILE_URL="https://gitlab.thewitslab.com/wil-workspace/wil-blastmotion/blastgolf-mobile-flutter/-/jobs/${CI_JOB_ID}/artifacts/build/app/outputs/flutter-apk/app-blastgolf-release.apk"
- echo "$FILE_URL"
- echo "FILE_URL success"
- |
#  curl -X POST -H 'Content-Type: application/json' 'https://chat.googleapis.com/v1/spaces/AAAAZiRX1w8/messages?key=AIzaSyDdI0hCZtE6vySjMm-WEfRq3CPzqKqqsHI&token=QP9r_pPftBcn_haF4K2k6lpsc_sA97FhZBYofaN3jDI' -d '{"text": "'"${APK_NAME}"' Android Build\nBuild executed by: '"${GITLAB_USER_NAME}"'\nBuild Name: '"${BUILD_NAME}"'\n'"${FILE_URL}"'"}' -exportPath ./build
# - echo "Success chat"
- appcenter distribute release -f "$APK_PATH" -g "Android-QA" -a admin-bjzg/NextGen-Blast-Golf-Android --release-notes "Version $buildNumber" --debug
- echo "appcenter distribute chat"
artifacts:
paths:
- build/app/outputs/flutter-apk/

Hello @eekesh2thapa thank you for reaching out. Have you tried using any of the previous versions of the cli, does the issue occur then?  Could you please enable additional debug logging  by setting the environment variable like this and post the output here to further analyze it.
DEBUG="appcenter-cli:commands:distribute:release" appcenter distribute release ...

Closing due inactivity.


Found an issue on parsing the Messages

Using the Live-Data it couldn't parse a Message when it had more than 28 Buffer Length
I had to use this instead, maybe there is a better to do this
// in the parseBoneTransform Function
	if len(data) <= 28 {
		return nil, InvalidBufferLengthError{Length: len(data), Expected: []int{28}}
	}

Oh that is interesting. According to spec, it should be exactly 28 bytes long, 7 floats, each 4 bytes long.
And further, for UDP messages, it's said they should be self-contained, meaning one UDP packet should contain a single OSC message with the proper size.
So the sending app might not follow the spec here, maybe 🤔.
Could you tell me the length of the actual data (should be in the error message)? I'm curious how long it is, and what might be the additional data. Also, if you don't mind, could you pass the raw data on that it is failing? Perhaps in hex or as a file.
If it is a rather fixed length, like always 4, 8 or 12 extra bytes, then it might be some extra argument. If it always changes, the app possibly sends 2 messages in a single payload.

Had a look at the official VMC for Unity repo, and they expect exactly 8 values as well, first 1 string, then 7 floats: link. Didn't look at how they parse the OSC message, so they might just drop any trailing data when parsing.
But, after we find out what the data is, I can of course change all the length checks to be more permissive. Not requiring an exact length, but instead only check that it's at least long enough to contain the expected data. That way, it will not care about any trailing data anymore.

I just went ahead and changed the parsing, so it'll accept (or rather ignore) any trailing data, and just ensures that there is at least enough data to read parse the expected fields.
Still, would be great to figure out what the trailing data is.

Could you tell me the length of the actual data (should be in the error message)?

2022-07-03T14:52:31+02:00 | FATAL | failed to parse VMC message: got 1496 bytes of data, expected exactly 28
there were bytes from Position 0 to 27 but after that everything is just 0
after checking my code - it seems that I didn't used the already sliced Array of filledBuffer := buf[:n] but instead used buf as argument to vmc.ParseMessage ... yep that explains it :D  - sorry for wasting your time


Homepage Results/Sort by/Explainer - Designs for Review

@scottofletcher @plscully @dethe Here are a couple of options for the homepage results.
Generally, how do we feel about listing "results" instead of "pages"?
Specifically:
Option 1 shows our usual treatment, but adds "Sort by" to the far right. Also adds "First, Previous, Next, Last" text with arrows. Currently there's no way to skip to the end of the results, not sure if this matters - thoughts?
Option 2 adds an explainer under the "all" tab (as discussed in this issue: https://github.com/participedia/usersnaps/issues/182). Also shows the "Sort by" menu open and positioned above the line, on the same hierarchical level as cases/methods/orgs (open menu has same visual treatment as clicking your avatar and seeing profile/sign out options). @scottofletcher Are these the options we want to sort by: Date submitted & Last edited ?
Option 3 shows the pagination at the bottom left after the results, back to an earlier design that was never implemented.
OPTION 1

OPTION 2

OPTION 3

@jesicarson Thank you, this is very helpful! I like Option 2 the best, although the explainer doesn't look as nice as the rest of the page. I think we need something like this, but it looks a bit squeezed in. And my sense is that it is not only because Option 2 needs two lines to include it.

Good point, thanks @plscully. I'll keep working on how the explainer can look. I'm not convinced it fits in that position after all, as we also display text results of searches there, ie, in the space below the tabs, this search displays  :  1 result of 1 for "democ" (page 1 of 1)
Also thinking we can get away with just arrows <<  <  >  >>, rather than the words "first, previous, next, last" and a sort button maybe (taking cues from Google):

I like Option 2 as well but I still think we need to reword the 'explainer' to fit with our "new" approach -- include words/phrases like 'wiki', 'crowdsourced', 'community created content', etc. I'm not sure the "stories" really fits here anymore since, like Wikipedia, we (ideally) want descriptive accounts with secondary/academic sources to back up the information. Our guidelines make this pretty clear and I think Pat and I have been pretty consistent in including it in our communiques with collaborators/coapplicants/RAs

I think the conversation about language, tying into overall vision for Participedia is important and should be continued. Lets find a way to do that... Maybe a focused discussion at the next all team meeting?
But for now I'm just going to focus on the design side :)
Another couple versions (i guess this would be options 4-7) showing the explainer for "all" and "case" above the tabs, in the same type size as headings in the case narrative. Its a lot of real estate, but maybe important as that was some of the most emphatic feedback - what is this thing??!!
OPTION 4 (all)

OPTION 4 (case)

OPTION 5 (case)

OPTION 6 (case)

OPTION 7 (case)

Pat and I talked I've actually come around the the "A global community...etc." tag-line that you, Paolo, and I made up like over a year ago :)
As for the new mockups
I like the ones w/explainers, (not necessarily the wording -- we should stick to the wording our tagline uses: public participation) but we can discuss that later
I also like having results rather than pages
I'll leave the nitty-gritty design details up to you and amber (although I'm most partial to option 7 -- what would it look like if the vertical paragraph line was red?)

@jesicarson I agree that you should focus on the design and not worry about the text.

I very much like that we will have an overall explainer as well as one for each category of content.
I also like results instead of pages, and the just arrows << < > >> design is also nice
If you want to start using new, briefer text, you use the ones below for the time being. I'm inclined to just use them and see how people respond rather than go through another long process of wordsmithing. The cases, methods, orgs text are abbreviated versions of the text on our "about" page.
@scottofletcher  If you have different ideas about wording, you & I can work it through on Slack
(no need to say "PPedia is a ...") Global Collaboration to Map New Forms of Participatory Politics and Governance
Cases are events of participatory politics and governance of all shapes and sizes (Delete “and instances”)
Methods are processes used to guide participatory politics and governance (Delete “the” & “and procedures”)
Organizations are groups that design, implement, or support innovations in participatory politics and governance (Delete “profiles of formal and informal”)

Thanks for the feedback, that's great. Will have Amber take a look at the designs next time we chat.

Thanks @dethe! Good point, I will add pagination to the bottom of the page in the design guidelines #853.
Regarding directionality of sorting, that would be a @scottofletcher question :)
Regarding design, when Amber reviewed these, she suggested that our feature tour / tool tips #624 would negate the need for permanent explainers. Once it is implemented, you all can test it and see if you agree.

More requests for a permanent explainer on the homepage. See: https://github.com/participedia/usersnaps/issues/274
I think we should implement option 4, but to keep things simple maybe not change the explainers for case/ method/ org tabs (just leave the main "Participedia is" explainer permanently above the tabs).
The other thing, @dethe, is that Andrea didn't provide any mockups for the feature tour, so I can't show people what it would be like - do you have it accessible to take a few screenshots by any chance?

@plscully not sure about 'participatory politics' - I think "public participation and democratic innovation" better captures what we're about

The text is in the copy deck (under About and Footer):
https://docs.google.com/document/d/1eUVXSBHN_QqR5O_MCNHpiplAAr51K3EM5yOo8w05I5k/edit#
I would keep it as is, and (if you must) add "and democratic innovation" to
the end:
Participedia: A global community sharing knowledge and stories about public

participation and democratic innovation

Or, if you're going to change anything, take a cue from Wikipedia and add:
"...that anyone can edit"  :P
JESI CARSON BDes - IxD, MDes
Graphics, Spaces, Interaction
604-729-9133
Portfolio http://cargocollective.com/jesicarson | Facebook
https://www.facebook.com/jesi.carson | Twitter
http://www.twitter.com/jesicarson | Instagram
http://www.instagram.com/jesicarson | Pinterest
http://www.pinterest.com/jesi | LinkedIn
https://ca.linkedin.com/in/jesicarson
*Design & Communities Coordinator, *Participedia https://participedia.xyz/
*Project Lead & Design Thinking Facilitator, *Vancouver Design Nerds
https://vancouver.designnerds.org
On Mon, Nov 19, 2018 at 8:27 AM Scott Fletcher<EMAIL_ADDRESS>wrote:

Email from Pat: "OK with me to use public participation and democratic
innovation".
Final text: "Participedia is a collaborative effort to document public
participation and democratic innovation around the world." ça va?
@jesicarson https://github.com/jesicarson where is this text kept? I
don't see it in this Doc
https://docs.google.com/document/d/10rSFF1n3sEAfcPlfWlEkEQxvZE3fr-8WR-jwaJEejsk/edit
And I agree with not changing the explainer on each of the tabs because 1)
Jaskiran and I are working hard to make titles less ambiguous (ie. you can
pretty much assume what a case is from a title like "Citizen Participation
in the 2015-2019 Strategic Plan of Kadikoy, Turkey"), and 2) if people are
curious about definitions, I'm sure they'll seek out the 'About' or 'Help'
pages.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/participedia/frontend/issues/838#issuecomment-439954042,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AM7q0rxpGS44Ihx6PtJY0Q4RlY_jCFisks5uwtvkgaJpZM4UlLXU
.

Ok, so we're going to scrap the case/method/tool/technique/org explainers except for those on the About page and in this doc?
And actually that last point is good but I still think the "sharing knowledge and stories" leaves out 1) the collaborative nature of the project (ie. I can share my story or my knowledge but it's still mine, I'm the 'owner'), and 2) the documentary aspect (knowledge and stories are documented vs delivered persuasively (as most students/academics are used to)).

The explainers for all the things are going to be in a few places - on the about page, on the quick submit page and on the FAQs under the help & contact menu.
Re: tag line wording - I think “community” is important. And “stories” are personal and welcoming. Adding “collaborative” could be interesting. At any rate, why are we thinking of changing it now? So far, people seem to like the wording we all decided on last year, they just want to see it more prominently displayed on the home page.

All good points! I'm going to mull this over a bit so we get the right balance.
The need for change is due to the overwhelming number of people that don't seem to understand what PPedia is. I met numerous people at the NCDD Conference who had gone to our site but didn't understand what it was about. Some people thought cases were scheduled events; others thought we had led the events; others thought they were articles in the academic sense of the term (ie. not collaborative) etc. The second I tell them we're "like Wikipedia but for public participation and democratic innovation" they get it.


throughtput

Any way to add throughput results?
P.S. Also which tool do you use to make plots like this?

+1

Is it possible to get the throughput info for all the model on LMSYS chatbot arena leaderboard?
I have also raised this feature request on Fastchat. https://github.com/lm-sys/FastChat/issues/2849

By throughput do you mean ratelimit/concurrent requests?

@richardliaw thank you for the reply.
By throughput do you mean ratelimit/concurrent requests? - No. Ratelimit/concurrent requests information is available for most of the proprietary LLMs/ commercialised LLM endpoints.
What I'm interested in is, Are there any benchmark(s) this project has around how many tokens can be generated over period of time for a given LLM, for the given fix GPU type. Something like below which vllm generates as part of the log.
[llm_engine.py:649] Avg prompt throughput: 30.5 tokens/s, Avg generation throughput: 61.1 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.6%, CPU KV cache usage: 0.0%

[llm_engine.py:649] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 79.2 tokens/s, Running: 3 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 2.6%, CPU KV cache usage: 0.0%

[llm_engine.py:649] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 77.9 tokens/s, Running: 3 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 2.7%, CPU KV cache usage: 0.0%

[llm_engine.py:649] Avg prompt throughput: 122.4 tokens/s, Avg generation throughput: 72.4 tokens/s, Running: 3 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 2.2%, CPU KV cache usage: 0.0%

[llm_engine.py:649] Avg prompt throughput: 138.9 tokens/s, Avg generation throughput: 71.6 tokens/s, Running: 3 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 2.0%, CPU KV cache usage: 0.0%

Along with LLM evaluation benchmark the above throughput numbers will also help the community to further optimise. I'm open to contribute.

@rickyyx Thank you for taking this up and raising pull request.

+1


unable to start mobile web tests on MCloud

unable to parse non W3C capabilities during mobile web tests startup on MCloud (Android+Chrome)

potential fix is available in ce-SNAPSHOT core build.
PR: https://github.com/qaprosoft/carina/pull/1395

fixed and tested on real use-case


chore: upgrade to marshmallow 3

This rolls frontend onto marshmallow 3. After this, only gremlin is left to upgrade.
Disclaimer: Marshmallow3 is more strict than its predecessor (e.g. by default does not accept unknown keys) and unless we override that globally - which I do not recommend - there may be API differences that go uncaught in testing. Unlike metadata/search, frontend makes more use of marshmallow so there is more potential for problems.
Testing
Have started up frontend and clicked around to confirm no obvious problems.
CheckList
Make sure you have checked all steps below to ensure a timely review.

[x] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[x] PR includes a summary of changes, including screenshots of any UI changes.
[x] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[x] In case of new functionality, my PR adds documentation that describes how to use it.

All the public python functions and the classes in the PR contain docstrings that explain what it does

[x] PR passes all tests documented in the developer guide

nothing more to add in terms of the code - lgtm. just thinking out loud but some kind of integration test in amundsen repo would be useful for these kind of changes - we could easily spot issues with dependency issues, model incompatibilities, etc.


Add support for configuring a GoogleAdsClient using environment variables

Also added support for configuring linkedCustomerId from a config
file, properties, or an environment variable.

Note to reviewers:
I considered multiple approaches here, but having a private GoogleCredentials.Builder was the cleanest approach I could find that satisfied all of the following requirements:

Support merging values from environment variables, a config file, properties, and setter invocations.
Do not make any breaking changes to the public interface of the client or its builder.
Support either setting credentials explicitly via setCredentials(Credentials) or configuring credentials from a file, properties, or environment variables.
Play nice with AutoValue. An unfortunate result of this requirement is that I had to mark getCredentials() on the client as @Nullable. There were alternatives to doing so, but they were all considerably less pleasant.

Heads up @nwbirnie and @devchas : I was able to find a way to implement "last one wins" logic for the 3rd requirement:

Support either setting credentials explicitly via setCredentials(Credentials) or configuring credentials from a file, properties, or environment variables.

With the latest commit, users who previously took the following steps in either order will see the same behavior as always:

Call setCredentials(Credentials).
Call fromProperties(...).

That is, the last step they performed will configure their credentials. My prior commits on this PR would have made either sequence throw an exception, which would have been a breaking change.

LGTM pending open comments

I merged from master at d632e3ae in preparation for merging this. Please use Jump to to look at the two files that actually changed: GoogleAdsClient.java and GoogleAdsClientTest.java.


Document buffer format for audio processors.

There is a comment in the example https://github.com/raysan5/raylib/blob/d6f16b76649944f65491633a75ad648a6ddfdacf/examples/audio/audio_mixed_processor.c#L26 about this, but it is more discoverable in the API docs.

From the stream effects example https://github.com/raysan5/raylib/blob/d6f16b76649944f65491633a75ad648a6ddfdacf/examples/audio/audio_stream_effects.c#L154 it seems that this applies to AttachAudioStreamProcessor() too, should I add the note also there?

@AlbertoGP thanks for the review!


flutter run should not sign iOS apps with Mac certificates

Steps to Reproduce
Connect iOS device and flutter run.
Multiple valid development certificates available (your choice will be saved):
  1) Mac Developer<EMAIL_ADDRESS>(7DGS4ZGNBJ)
  2) iPhone Developer: Google Development (3F4Y5873JF)
  3) iPhone Developer: Alex Jackson (5SXPVWLENR)
  a) Abort
Please select a certificate for code signing [1|2|3|a]: 2

I think it should have defaulted to an iPhone Developer certificate and not shown me the Mac developer one, since I'm building for iOS.
(Why I have a developer certificate for Alex Jackson is a long story.)
flutter doctor
[✓] Flutter (on Mac OS X 10.12.5 16F73, locale en-US, channel unknown)
    • Flutter at /Users/jackson/git/flutter
    • Framework revision 4d6298d486 (3 days ago), 2017-07-10 04:18:44 -0700
    • Engine revision 8ad1576f27
    • Tools Dart version 1.25.0-dev.4.0

[✓] Android toolchain - develop for Android devices (Android SDK 26.0.0)
    • Android SDK at /Users/jackson/Library/Android/sdk/
    • Platform android-26, build-tools 26.0.0
    • ANDROID_HOME = /Users/jackson/Library/Android/sdk/
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_112-release-b06)

[✓] iOS toolchain - develop for iOS devices (Xcode 8.3.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 8.3.3, Build version 8E3004b
    • ios-deploy 1.9.1
    • CocoaPods version 1.2.1

[✓] Android Studio (version 2.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Java version OpenJDK Runtime Environment (build 1.8.0_112-release-b06)

[✓] IntelliJ IDEA Community Edition (version 2017.1.4)
    • Flutter plugin version 15.0
    • Dart plugin version 171.4694.29

[✓] Connected devices
    • Jacksonphone • 9030c4fbeb16a1981b3e685fbf21521d79ed6ac1 • ios • iOS 10.3.2

cc @xster

Note to future self: it doesn't seem like security find-identity has a category for target types. It'll have to be a manual name filter.

And what if i build for mac?

Right, the intent of the bug is to show macos certificates when building for macos and ios certificates when building for ios.

Apple Developer for all platforms is the type to use in Xcode 11 and later, though you can still generate the other types.  This problem will mostly go away.

is the norm now, this problem

Since there's been a way to create Apple Development signing keys for a few years now, I'm going to assume this isn't worth investing time in.


libncurses5 no longer available on Ubuntu23.10

Hi,
libncurses5 has been removed from ubuntu (and I believe debian).
Any chance you can make it work with libncurses6?

We're working on this--with any luck, we'll be able to remove the ncurses dependency entirely.

libroadrunner 2.5.0 now doesn't require libncurses at all!  If you update, you should get the latest from pypi.


remove disabled SIMD.js tests

Resolves #3031
Resolves #3032
Resolves #3034

@dotnet-bot test Ubuntu static_ubuntu_linux_release

:shipit:


Each subsequent (CoordinateOperation) transform will fail after exception

If a TransformException occurs when executing the transform method, each subsequent call results in the same error. It seems that certain state is not being cleaned up properly. In this situation we are now forced to create a new instance of CoordinateOperation. This is of course undesirable in the context of performance.
The issue can be reproduced with the code below (PROJ9 & latest PROJ-JNI code).
// WKT transformation for ETRS89 height -> Dutch NAP height
// The transformation will only succeed for points within the RD bounding box else an TransformException "Coordinate to transform falls outside grid" will be thrown by PROJ
CoordinateOperation operation = (CoordinateOperation) Proj.createFromUserInput("COORDINATEOPERATION[\"ETRS89 to ETRS89 + NAP height (2)\",VERSION[\"NSGI-Nld 2018\"],SOURCECRS[GEOGCRS[\"ETRS89\",ENSEMBLE[\"European Terrestrial Reference System 1989 ensemble\", MEMBER[\"European Terrestrial Reference Frame 1989\", ID[\"EPSG\",1178]], MEMBER[\"European Terrestrial Reference Frame 1990\", ID[\"EPSG\",1179]], MEMBER[\"European Terrestrial Reference Frame 1991\", ID[\"EPSG\",1180]], MEMBER[\"European Terrestrial Reference Frame 1992\", ID[\"EPSG\",1181]], MEMBER[\"European Terrestrial Reference Frame 1993\", ID[\"EPSG\",1182]], MEMBER[\"European Terrestrial Reference Frame 1994\", ID[\"EPSG\",1183]], MEMBER[\"European Terrestrial Reference Frame 1996\", ID[\"EPSG\",1184]], MEMBER[\"European Terrestrial Reference Frame 1997\", ID[\"EPSG\",1185]], MEMBER[\"European Terrestrial Reference Frame 2000\", ID[\"EPSG\",1186]], MEMBER[\"European Terrestrial Reference Frame 2005\", ID[\"EPSG\",1204]], MEMBER[\"European Terrestrial Reference Frame 2014\", ID[\"EPSG\",1206]], ELLIPSOID[\"GRS 1980\",6378137,298.257222101,LENGTHUNIT[\"metre\",1,ID[\"EPSG\",9001]],ID[\"EPSG\",7019]], ENSEMBLEACCURACY[0.1],ID[\"EPSG\",6258]],CS[ellipsoidal,3,ID[\"EPSG\",6423]],AXIS[\"latitude (Lat)\",north,ANGLEUNIT[\"degree\",0.0174532925199433,ID[\"EPSG\",9102]]],AXIS[\"longitude (Lon)\",east,ANGLEUNIT[\"degree\",0.0174532925199433,ID[\"EPSG\",9102]]],AXIS[\"Ellipsoidal height (h)\",up,LENGTHUNIT[\"metre\",1,ID[\"EPSG\",9001]]],ID[\"EPSG\",4937]]],TARGETCRS[COMPOUNDCRS[\"ETRS89 + NAP height\",GEOGCRS[\"ETRS89\",ENSEMBLE[\"European Terrestrial Reference System 1989 ensemble\", MEMBER[\"European Terrestrial Reference Frame 1989\", ID[\"EPSG\",1178]], MEMBER[\"European Terrestrial Reference Frame 1990\", ID[\"EPSG\",1179]], MEMBER[\"European Terrestrial Reference Frame 1991\", ID[\"EPSG\",1180]], MEMBER[\"European Terrestrial Reference Frame 1992\", ID[\"EPSG\",1181]], MEMBER[\"European Terrestrial Reference Frame 1993\", ID[\"EPSG\",1182]], MEMBER[\"European Terrestrial Reference Frame 1994\", ID[\"EPSG\",1183]], MEMBER[\"European Terrestrial Reference Frame 1996\", ID[\"EPSG\",1184]], MEMBER[\"European Terrestrial Reference Frame 1997\", ID[\"EPSG\",1185]], MEMBER[\"European Terrestrial Reference Frame 2000\", ID[\"EPSG\",1186]], MEMBER[\"European Terrestrial Reference Frame 2005\", ID[\"EPSG\",1204]], MEMBER[\"European Terrestrial Reference Frame 2014\", ID[\"EPSG\",1206]], ELLIPSOID[\"GRS 1980\",6378137,298.257222101,LENGTHUNIT[\"metre\",1,ID[\"EPSG\",9001]],ID[\"EPSG\",7019]], ENSEMBLEACCURACY[0.1],ID[\"EPSG\",6258]],CS[ellipsoidal,2,ID[\"EPSG\",6422]],AXIS[\"latitude (Lat)\",north],AXIS[\"longitude (Lon)\",east],ANGLEUNIT[\"degree\",0.0174532925199433,ID[\"EPSG\",9102]],ID[\"EPSG\",4258]],VERTCRS[\"NAP height\",VDATUM[\"Normaal Amsterdams Peil\",ID[\"EPSG\",5109]],CS[vertical,1,ID[\"EPSG\",6499]],AXIS[\"Gravity-related height (H)\",up],LENGTHUNIT[\"metre\",1,ID[\"EPSG\",9001]],ID[\"EPSG\",5709]],ID[\"EPSG\",9286]]],METHOD[\"Geog3D to Geog2D+GravityRelatedHeight (gtx)\",ID[\"EPSG\",1088]],PARAMETERFILE[\"Geoid (height correction) model file\",\"nlgeo2018.gtx\",ID[\"EPSG\",8666]],PARAMETER[\"EPSG code for Interpolation CRS\",4258,ID[\"EPSG\",1048]],OPERATIONACCURACY[0.001],ID[\"EPSG\",9597]]");

// Coordinate within RD bounding box
double[] coordinateInside = {
    53.106038193, 5.255859149,  345.4981
};

// first transform
operation.getMathTransform().transform(
    coordinateInside, 0,
    coordinateInside, 0,
    1);

// Coordinate outside RD bounding box
double[] coordinatesOutside = {
    45.25635676, -2.00693553, 208.6062
};

// second transform results in TransformException 'Coordinate to transform falls outside grid' as expected
try {
  operation.getMathTransform().transform(
      coordinatesOutside, 0,
      coordinatesOutside, 0,
      1);
} catch (TransformException exception) {
  log.error("Expected transformException!",exception);
}

// Any subsequent transformation after the second transformation on the same `CoordinateOperation` instance is failing unexpectedly
operation.getMathTransform().transform(
    coordinateInside, 0,
    coordinateInside, 0,
    1);

A quick report on current status. I could not yet reproduce the issue with PROJ 8.2.1 (the version provided by my Fedora Linux distribution) because that version of PROJ seems to return a NULL object for that coordinate operation. I previously thought that NULL objects would be returned by the C/C++ API only when running out of memory, but there is apparently other possible reasons. The Java exception has been changed in #62 for reflecting that new assumption.
I'm lazily waiting for the Fedora distribution to upgrade to PROJ 9 before to test again. If it takes too long, I may try to compile locally later.

I finally could reproduce. No state were kept in Java code or in JNI bindings, we only have a pointer to PROJ PJ object. We would need to test directly in C/C++ to confirm if this is a PROJ bug or if we missed something else. Or maybe it is part of PROJ contract to not use a PJ object any more after an error. The fix applied in Java code is to unconditionally discard the native PJ object after an error instead of recycling it for next operations.

Actually it seems that a better fix was already applied in a fork: https://github.com/interactive-instruments/PROJ-JNI/commit/c3b7e3b587ca19b307a6b6f47e441d8fc0f0a03e
Waiting for #63 to be fixed before to try the better fix.

Reverted previous fix and use proj_errno_reset(pj) instead.


Incorrect default in custom field action enablement collection type pulldown menu.

This default is 'None' not 'Array'.  This used to be correct - regressed somehow.

Regression from last refactor.  Not sure how you wanted to handle default select.  It should be "None" in this case.


Redirect after login

Hello,
I'm using angular 1 ui-router 1.0.0-beta.3 and I have a route declaration like:
angular
  .module(name, [... ])
  .run(handleTransitionErrors)
  .config(configureRoutes)

function handleTransitionErrors ($state) {
  $state.defaultErrorHandler(function (error) {
    switch (error) {
      case 'AUTH_REQUIRED':
        $state.go('auth.login');
        break
    }
  })
}

function configureRoutes($stateProvider){
$stateProvider
    .state('auth', {
      url: '/auth',
      component: 'auth',
    })
    .state('user', {
      url: '/user',
      redirectTo: 'user.profile',
      resolve: {
        currentUser: ['$auth',
          $auth => $auth.getUser().then((user) => new Promise((done, err) => {
            if (user) done(user)
            else err('AUTH_REQUIRED')
          }))
        ]
      }
    })
   .state('user.profile', {
      url: '/profile',
      component: 'userProfile',
    })
}

So if a user who is not logged in visits /user he will be redirected to /auth to login.
Now after the login, I want to redirect the user back to the route he was requesting.
However, the name of the $state.$current().name in the error handler callback is empty.
I've currently solved this by creating a history service like:
function listenToChanges($history, $state, $transitions) {
  $transitions.onStart({}, function (transition) {
     $history.push(fransition.to());
  });
}

export default angular
  .module(name, [...])
  .service("$history", HistoryService)
  .run(listenToChanges);

But I'm wondering if this can be done simpler or better?

The Transition object contain two key pieces of information:

the from state:
https://ui-router.github.io/docs/latest/classes/transition.transition-1.html#from

the Transition object which was redirected (causing the current Transition):
https://ui-router.github.io/docs/latest/classes/transition.transition-1.html#redirectedfrom

The Sample App has a login state which uses this information to build a  "returnTo" resolve value (which is a TargetState object)
After successful login, the login state does a $state.go() to the returnTo TargetState
Read over this code: https://github.com/ui-router/sample-app-ng1/blob/master/app/main/app.states.js#L44-L83
For this to work, you should use a transition hook to perform auth (do not use resolve unless you're fetching data)
Read the requiresAuth hook in the Sample App:  https://github.com/ui-router/sample-app-ng1/blob/master/app/global/requiresAuth.hook.js#L1-L28 .  The hook uses data: { requiresAuth: true } on a state definition to trigger the hook.
Closing because I believe I've answered the question

Even though i understand how the examples shows how to redirect to a state after authenticating, i don't see a solution for a "complex" state which has a few parameters. With that setup, they are lost.
When i was using 0.4.2 we build a service that kept the last "valid" redirectable state, but with 1.0 i'm strungling to find the right object to get/store.
Any chance you have more information / best practice regarding this issue?


Only remove prop types in a production build.

Disable 'babel-plugin-transform-react-remove-prop-types'
plugin during a development build. Some libraries
expect prop types to be available during a development
build.
Semantic UI React uses prop types during development
for validation. Issue 1869 has some additional context.

@reznord  I am not sure I fully understand how they are used, but it is a part of the AutoControlledComponent validation logic here. I don't fully understand it, and perhaps it is only useful when are you developing a component for Semantic-UI-React. I recently switched from react to preact, which is when the error started, so I decided to submit a PR.


Improve MedDRA cross-references in EFO

To keep track of the issue opened to EFO to improve the MedDRA/EFO coverage.

EFO has imported over 2000 high confidence MedDRA x-refs into EFO where the MedDRA label and the EFO/Orphanet label are the same.
They will be gradually importing the less confident ones to elucidate whether the x-refs are broad, exact, narrow or related.
As EFO dynamically imports MONDO, DOID, and HP terms, these xrefs have to be assessed by them, and not by EFO. So the corresponding issues have been opened:

Request to MONDO
Request to DOID
Request to HP

All ontologies but MONDO have completed the task as today. No action is required on our side


[camera] support for camera stream on web

This PR aims to provide support for strartImageStream on Web.
#92460
Pre-launch Checklist

[X] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[X] I read and followed the relevant style guides and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/plugins repo does use dart format.)
[X] I signed the CLA.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I listed at least one issue that this PR fixes in the description above.
[ ] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.
[ ] I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style.
[ ] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@ditman Can you do the primary review here?

Update from triage: @ditman hasn't had time to review this yet, but it's still on his radar.

We've just completed the migration of the plugin code to the flutter/packages repository, as described in https://flutter.dev/go/flutter-plugins-repo-migration, and this repository is now being archived. Unfortunately that means that all in-progress PRs here must be moved to flutter/packages.
Please see our instructions for an explanation of how to move your PR, and if you have any issues moving your PR please don't hesitate to reach out in the #hackers-ecosystem channel in Discord.
Our apologies that your PR was caught in this one-time transition. We're aware that it's disruptive in the short term, and appreciate your help in getting us to a better long-term state!


Analyze: exclude useless secrets to reduce execution time

Please provide a description of this PR:
Fix #45458
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Ambient
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[X] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[X] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

@fatedier: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
bde12d0ba4aa10f7bde4dd20546e208927cc3d5a
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@fatedier: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
d4538c1a62f29e01b19f50c32f1f376f1d67401f
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@fatedier: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
d4538c1a62f29e01b19f50c32f1f376f1d67401f
link
true
/test lint

gencheck_istio
d4538c1a62f29e01b19f50c32f1f376f1d67401f
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@fatedier: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
d4538c1a62f29e01b19f50c32f1f376f1d67401f
link
true
/test gencheck

lint_istio
247ffa3d825b5151f348785fd8c1a2c62f71ece2
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@fatedier: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
247ffa3d825b5151f348785fd8c1a2c62f71ece2
link
true
/test lint

gencheck_istio
247ffa3d825b5151f348785fd8c1a2c62f71ece2
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Add setup.py

The setup.py is useful to integrate the repository as sub module or dependency in other repository. As I wanted to use the project I created a setup.py and hope you are interested in it.
I open to discuss the matter or make changes if necessary.

Isn't Python Poetry the more modern way to go?


Accessing merged params in request on form-url-encoded content type

Laravel Version
9.52.9
PHP Version
8.2
Database Driver & Version
No response
Description
When merge an extra param in request and send request body in form-url-encoded type, merged param is not accessible on request but it is accessible on request helper
Steps To Reproduce
<?php

namespace App\Rules;

use Illuminate\Contracts\Validation\Rule;

class HasAvailableProviderRule implements Rule
{
    /**
     * Create a new rule instance.
     *
     * @return void
     */
    public function __construct()
    {
        //
    }

    /**
     * Determine if the validation rule passes.
     *
     * @param  string  $attribute
     * @param  mixed  $value
     * @return bool
     */
    public function passes($attribute, $value)
    {
        ...
        request()->merge(['bank_provider_id' => $bankProvider->id]);
        ...
    }
}

//in my controller
$request->input('bank_provider_id'); //this line return null
request()->bank_provider_id; //this line return the merged value

Unfortunately there was a breaking change in Symfony which made us implement https://github.com/laravel/framework/pull/47838. So this will probably stay, sorry.


Where do you document methods directly on formContext like getAttribute?

Pretty major oversight...

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

ID: 9b9a6b58-70b1-1dd1-8f1e-d354fef4b06a
Version Independent ID: 8f1f0c3c-b7f6-0c56-3a64-ec439c5f1f24
Content: Client API form context in Dynamics 365 for Customer Engagement apps
Content Source: ce/developer/clientapi/clientapi-form-context.md
Service: crm-online
GitHub Login: @KumarVivek
Microsoft Alias: kvivek

@rdegrove Thanks for your feedback. We are working on this feedback, and the content will be updated soon.


Remove player heads from /ja

Would save on the massive lag spikes caused by /ja on large snitches, and resolve #29 . And really, player heads on /ja are nothing more than a neat little design addition

Alternatively some kind of batching / caching of heads to make it much smarter

Alternatively some kind of batching / caching of heads to make it much smarter

Dunno exactly how the skin-getting stuff works but from discord:

caching - not having to ask a server for a file you already have is faster
lazy "initialization"/skin download - don't get skins for heads that wouldn't be visible on the current page of the UI
load skins async, update the item accordingly - Basically do something similar to Swing/AWT Graphics.drawImage(..., ImageObserver) where you draw "what you have" of an image (ie use a placeholder item of some sort) then once the rest of the image (skin) is available/loaded, redraw the image (update the item).


Configure ports

Similar to #2, would be nice if we can customize the ports used in the stack. This is especially useful if I have a running stack (e.g. the mainnet node). An easy way is to let user to define environment variables to change the ports, and in the e2e test scripts, it can load it from dotenv.

It is already possible. I will update documentation about config options


Can't import plist as Domain User

Using a postinstall pkg script- dockutil is not installing an icon for the current logged in user:
The pkg succeeds but the log shows this error I get this on 10.8.5.
Dec 30 09:46:24 maccomp.global.domain.net.: ./postinstall: Sorry, user root is not allowed to execute '/usr/bin/defaults import /Users/grimml/Library/Preferences/com.apple.dock.plist /private/tmp/PKInstallSandbox.MXi7di/tmp/tmpKi7r0h' as grimml:LL\Domain Users on maccomp.global.domain.net.
Script:
!/bin/bash
Add My.app icons to existing users Dock
/usr/local/bin/dockutil --add '/Applications/Utilities/My.app' --allhomes
Sorry, user root is not allowed to execute '/usr/bin/defaults import /Users/grimml/Library/Preferences/com.apple.dock.plist /tmp/tmp4QBRZU' as grimml:LL\Domain Users on maccomp.global.domain.net.
Can you advise me on a solution?
Thanks very much

Closing this old inactive issue.  Please retest with latest dockutil and report back if you are still having the issue.


Unable to download sonarqube official image

Expected behavior
Download and start a container with sonarqube image
Actual behavior
Unable to download sonarqube official image, 401 error.
Information about the Issue
Steps to reproduce the behavior

run Kitematic
search "sonar"
Download sonarqube official image
Error 401.

what do you get when you run:
docker pull sonarqube from a terminal?

Closing this issue due to lack of update/activity - Feel free to re-open if appropriate.


feat: Proposed fix dialog

Hey, I just made a Pull Request!
Fixes https://github.com/backstage/backstage/issues/17136

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Waiting on https://github.com/backstage/backstage/pull/17563

@jamieklassen do you wanna have a flick through this? :pray:

@jamieklassen and I will review in a meeting on thursday

@mclarke47 nice!

@jamieklassen ready for review again


Gii view.php creates HTML for Buttons incorrectly

When generating models, the screen where one enters the model information contains a "PREVIEW" button. The button is missing a < ... value="Preview" ...> attribute in the  tag. The result is that "Preview" is missing in the resulting $_POST array.  Because of this the controller action code cannot advance the generation process. It is stuck in the viewing process. This is because the IF statement checking for Preview or Generate can never be true (in the inital form the generate button is not displayed.
    public function actionView($id)
    {
        $generator = $this->loadGenerator($id);
        $params = ['generator' => $generator, 'id' => $id];
        if (isset($_POST['preview']) || isset($_POST['generate'])) {
            if ($generator->validate()) {
                $generator->saveStickyAttributes();
                $files = $generator->generate();
                if (isset($_POST['generate']) && !empty($_POST['answers'])) {
                    $params['hasError'] = !$generator->save($files, (array) $_POST['answers'], $results);
                    $params['results'] = $results;
                } else {
                    $params['files'] = $files;
                    $params['answers'] = isset($_POST['answers']) ? $_POST['answers'] : null;
                }
            }
        }

        return $this->render('view', $params);
    }

I will send a pull request shortly for this issue.

There shouldn't be any issue, even without value attribute submitted button's name should be in the $_POST keys (with value of "").

@apyii Did you encounter the problem? The code has been like this from the very beginning, and we have yet to receive any issue report.

@qiangxue yes, I definitely had this problem. That's what I found to be strange. This is such a central part of the software that it should have been discovered long ago.
There are two ways that this can be fixed:

change the parameters as I've suggested in the pull request
change the call of html:submitButton(...) to be html::submitInput(...), submitInput generates the value attribute even though it is not specified.

This comment from the documentation of submitInput(...) is also interesting:

The value attribute. If it is null, the value attribute will not be generated.

Now, I realize that comment is for the submitInput() method (which I was not using) and the parameters don't quite match up either ($label <> value). However, the description caught my eye because it describes what I was experiencing.
Is it possible that the underlying methods have gotten confused or perhaps my installation is somehow messed up?

Not sure how to proceed, if this is not a problem, then there is no need to merge the request. But I definitely had the problem. Maybe I'll just have to find out what's wrong with my installation.

I've finally gotten to the bottom of this.
The value attribute is definitely NOT being generated by html::submitButton( ... ). I've also check the complete revision history of BaseHtml.php as well as Gii's view.php. Nothing I saw there indicates that the software was ever different in this regard.
I ran across (this thread at stack overflow) http://stackoverflow.com/questions/11380816/html-form-button-value-is-not-posted-in-safari-and-chrome, which shed some light on the problem. It seems that under certain circumstances some browsers infact do not post the value of a  tag if the value attribute is missing. This would lead to the error I'm having. So I decided to test this out in a few different browsers. I'm using a linux system (opensuse 13.1), here are the results.
Google Chrome (Version 39.0.2171.95 (64-bit)): Error as I described
Firefox (34.0.5): Error as I described
Opera (12.16): No Error, Success as expected
So in the end it seems all of us were correct: @qiangxue, yes the code has always been the way it is, @CthulhuDen, as long as the browser doesn't have a bug the value will be posted.
So, as long as the correct browsers are used there is no need to merge this pull request. However, one could avoid problems in the future (or present) for people using Chrome, Firefox and others, where the problem occurs. Who knows when this will be corrected. Also the change does not harm the functionality. That being said it might be better to refactor the submitButton method to automatically include the value attribute the same way the submitInput method does. But as these are central methods used overall in yii, I'm not sure what the best option is.

Can you try it on Windows or MacOS? The stackoverflow post is a bit different because it is calling form.submit() to submit the form, which is known  to have this problem.

I've tried it from my Windows-XP Laptop. My server is a local Linux server (opensuse). The result is that Windows and Internet Explorer bot exhibited the Error behavior.
I HAVE NO PROBLEM WITH CLOSING THIS ISSUE If it were a problem in the Yii(Gii) core it would have been noticed by many people, but that is obviously not the case. There must be something unique about my setup that is causing this. I'll keep any eye open if I notice something. But for now I'l consider this issue closed.

I got the exactly same error.
I just follow straight the install guide from the oficial website. the instalation was success.But when i try to use the gii. the same error happens.


Minor grammar changes

This fixes some grammar issues in the CONTRIBUTING and README file.

@3kh0 please re-commit using conventional commits, as it helps generate the changelog. You can use yarn commit to generate an appropriate commit message with an interactive CLI.

Gonna redo the changes


'ALT' doesn't fit on a single line.

Describe the bug
Running in Firefox Nightly, the 'ALT' text on images is wrapped on 2 lines.
To Reproduce
Steps to reproduce the behavior:

Open eg. https://staging.bsky.app/profile/ashleywillis.bsky.social/post/3jvsiuljthq2k

Expected behavior
ALT should be ALT, but it is
AL
T

Screenshots

Details

Platform: Firefox Nightly, Ubuntu Linux 23.04
Platform version: Gecko 115
App version:

Additional context

Should be fixed by https://github.com/bluesky-social/social-app/pull/618 (unfortunately screenshots got nuked when the repo went public). Please reopen if not fixed by the next major release

Should be fixed by #618 (unfortunately screenshots got nuked when the repo went public). Please reopen if not fixed by the next major release

Cool. When can we expect the next release?

it kind of varies, we tend to do 2 or 3 a week


[Feature Request] Upload to X instead of having to  save as

Would encode to a temp directory or whatever and then remove it once uploaded.
Would be nice if it supported Imgur, gfycat, etc

We don't need another ShareX, IMHO.

Pretty much every gif I make goes straight on imgur, it's the only thing missing from this great app :(

Not that I do not understand this request. But see: It starts with Imgur, than the next one comes and wants GDrive, AS3, DropBox, Sendspace.... and so on and so on...
Just my vote: Let's keep that out.
But it is of course up to @NickeManarin to decide where he wants to go...

@SoftwUser I understand that I should focus on some other primary feature requests and bug fixes.
@Partixel Your feature request is valid and it's on my personal to-do list, on the other hand, there's some key features that I need to implement first.

My +1 to this idea, I like what pastebinit does but for image upload services instead.
The problem for my case where this would be helpful because some gifs of 1.5MB and larger cant be attached to most forum boards, so getting a capture saved/uploaded and a direct link returned to clipboard would be ideal and a time saver.

Yeah, that's what I use i for. :)

In my opinion, this would be a great addition if it can be implemented using a plugin infrastructure. In this case, users can install the desired uploaders if they need one. The community can provide the necessary uploaders (I am thinking about an upload directly into our TFS to help with bug reports).


feat(): Angularfire auth guards

Checklist

Issue number for this PR: #nnn (required)
Docs included?: (yes/no; required for all API/functional changes)
Test units included?: (yes/no; required)
In a clean directory, yarn install, yarn test run successfully? (yes/no; required)

Description
Allow developers to protect routes in their Angular application using Firebase authentication.

TODOs

[ ] Get test coverage
[ ] Polish the documentation

Code sample
Basic example
import { AngularFireAuthGuard } from '@angular/fire/auth-guard';

export const routes: Routes = [
    { path: '',      component: AppComponent },
    { path: 'items', component: ItemListComponent, canActivate: [AngularFireAuthGuard] },
]

Use our pre-built pipes for common tests
import { AngularFireAuthGuard, hasCustomClaim, redirectUnauthorizedTo, redirectLoggedInTo } from '@angular/fire/auth-guard';

const adminOnly = hasCustomClaim('admin');
const redirectUnauthorizedToLogin = redirectUnauthorizedTo(['login']);
const redirectLoggedInToItems = redirectLoggedInTo(['items']);
const belongsToAccount = (next) => hasCustomClaim(`account-${next.params.id}`);

export const routes: Routes = [
    { path: '',      component: AppComponent },
    { path: 'login', component: LoginComponent,        canActivate: [AngularFireAuthGuard], data: { authGuardPipe: redirectLoggedInToItems }},
    { path: 'items', component: ItemListComponent,     canActivate: [AngularFireAuthGuard], data: { authGuardPipe: redirectUnauthorizedToLogin },
    { path: 'admin', component: AdminComponent,        canActivate: [AngularFireAuthGuard], data: { authGuardPipe: adminOnly }},
    { path: 'accounts/:id', component: AdminComponent, canActivate: [AngularFireAuthGuard], data: { authGuardPipe: belongsToAccount }}
];

Increase readability with our canActivate helper
import { canActivate } from '@angular/fire/auth-guard';

export const routes: Routes = [
    { path: '',             component: AppComponent },
    { path: 'login',        component: LoginComponent,    ...canActivate(redirectLoggedInToItems) },
    { path: 'items',        component: ItemListComponent, ...canActivate(redirectUnauthorizedToLogin) },
    { path: 'admin',        component: AdminComponent,    ...canActivate(adminOnly) },
    { path: 'accounts/:id', component: AdminComponent,    ...canActivate(belongsToAccount) }
];

Compose your own pipes
import { pipe, of } from 'rxjs';
import { map, switchMap } from 'rxjs/operators';
import { customClaims } from '@angular/fire/auth-guard';

const editorOnly = pipe(customClaims, map(claims => claims.role === "editor"));
const redirectToProfileEditOrLogin = map(user => user ? ['profiles', user.uid, 'edit'] : ['login']);
const onlyAllowSelf = (next) => map(user => !!user && next.params.userId === user.uid);
const accountAdmin = (next) => pipe(customClaims, map(claims => claims[`account-${next.params.accountId}-role`] === "admin"));

@davideast feel free to start poking at this. Going to work on the test coverage and documentation in the meantime. Targeting 5.2 release.

FYI this has been released for testing on @next as of 5.2.0-beta.3

wow, so convinent :D thank you so much

Assigning @davideast for API review. @jhuleatt if you could give a quick code review.

FYI tests and docs need more work.

Any idea when there will be a new release with the merged PR?

@svzi you can give this a try now with the beta 4 release. npm i --save @angular/fire@next.
I'm hoping to release 5.2 stable early next week.

@jamesdaniels Thanks a lot! But it seems like I'm missing something, or there is something not working right now:
ERROR in node_modules/@angular/fire/auth-guard/auth-guard.d.ts(11,5): error TS2416: Property 'canActivate' in type 'AngularFireAuthGuard' is not assignable to the same property in base type 'CanActivate'.
  Type '(next: ActivatedRouteSnapshot, state: RouterStateSnapshot) => Observable<boolean | UrlTree>' is not assignable to type '(route: ActivatedRouteSnapshot, state: RouterStateSnapshot) => boolean | UrlTree | Observable<boolean | UrlTree> | Promise<boolean | UrlTree>'.
    Type 'Observable<boolean | UrlTree>' is not assignable to type 'boolean | UrlTree | Observable<boolean | UrlTree> | Promise<boolean | UrlTree>'.

@svzi which version of typescript / Ng?

@jamesdaniels Angular 7.2.0 (CLI 7.3.9) and TypeScript 3.2.2.

I'll look into this. Will track here #2086

Thanks a lot, appreciate your support!


GEODE-9079: downsize non-intentensive CI instances

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[X] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[X] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[X] Is your initial contribution a single, squashed commit?

[X] Does gradlew build run cleanly?

[X] Have you written or updated unit tests to verify your changes?

[n/a] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

@jdeppe-pivotal , can I get a few minutes of your time?

Sorry I completely missed this


Added reactive state property to the upload instance object returned by files.insert()

New feature satisfying my feature request: #56
Like the title states, this adds a reactive state variable to the upload instance object returned by files.insert().
It has four states:

active - file is currently actively uploading
paused - file upload is paused
aborted - file upload has been aborted and can no longer be completed
completed - file has been successfully uploaded

This is useful in easily maintaining consistent state, rather than having to infer it from a variety of factors.
I have not meddled in the existing onPause state variable, however state renders it redundant.  @dr-dimitru may want to update the package to replace onPause with state if this request is accepted.

Hi @jdmswong thank you for PR.
Could you please add this to the docs (readme)?

my pleasure @dr-dimitru, I've updated the readme

@jdmswong I wouldn't remove onPause in favour of backward compatibility
Thank you, once again, for contribution.
I'll test it, then publish to atmosphere
Do not forget to share this package and star on both GitHub and Atmosphere


fix product layout in manufacturer action

1. Why is this change necessary?
the manufacturer listing shows the wrong productbox layout
example: main category has layout "minimal" but the manufacturer listing shows the "basic" layout. If infinite scrolling is activated, the reloaded templates are the correct "minimal" ones
2. What does this change do, exactly?
sets the productBoxLayout field in the $sCategoryContent array according to the selected layout of the main category
3. Describe each step to reproduce the issue or behaviour.
see 1.
4. Please link to the relevant issues (if any).
https://issues.shopware.com/issues/SW-20234
I already did a pr for this but I accidentally deleted the old commit... (was https://github.com/shopware/shopware/pull/1306)
5. Which documentation changes (if any) need to be made because of this PR?
6. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-20667
Please use this issue to track the state of your pull request.


If SelectableText set a height value,Text will scroll when crossing the border

For example
SelectableText(
      "SelectableText",
       style: TextStyle(
       fontSize: 16,
             height: 2,
      ),
),

It's a bug or a feature?

Hi @rs5173
I'm quite sure that the behavior you are describing is a bug
or it's even related to the height parameter.
Does this code represent the situation you are describing?
Thank you

Yes.This bug will happen when the height value is greater than the default value.

Flutter version is v1.9.1+hotfix.2

Hi again @rs5173
as mentioned before the behavior you are describing matches the definition of  SelectableText
The SelectableText widget displays a string of text with a single style.
The string might break across multiple lines
or might all be displayed on the same line depending on the layout constraints.

If you are proposing an implementation of a different behavior
could you please can you please explain in details.
Thank you

CC @chunhtai

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.


maliput_sparse: 0.2.3-1 in 'foxy/distribution.yaml' [bloom]

Increasing version of package(s) in repository maliput_sparse to 0.2.3-1:

upstream repository: https://github.com/maliput/maliput_sparse.git
release repository: https://github.com/ros2-gbp/maliput_sparse-release.git
distro file: foxy/distribution.yaml
bloom version: 0.11.2
previous version for package: 0.2.2-1

maliput_sparse
* Relies on GetClosestPoint for the GetClosestPointUsing2dProjection method. (#53 <https://github.com/maliput/maliput_sparse/issues/53>)
* Stores linestring's points in a kdtree. (#52 <https://github.com/maliput/maliput_sparse/issues/52>)
* Precomputes linestring's segments intervals (#51 <https://github.com/maliput/maliput_sparse/issues/51>)
* Contributors: Franco Cipollone

CC: @tfoote @j-rivero


Decommission device name from all loggers

we override log4j loggers using obsolete and primitive approach. This use-case has some problems and moreover block movement of carina to modern logger versions.
Please, review the code and remove all code related to the device name detection and appending them in log messages

During the testing run any mobile test over mCloud (Android or iOS) and review console logs. All kind of messages like PASSED at or FAILED at shouldn't contain inside console log info about device name and udid


Standalone quasi-random sampling.

This is a neat library, but I don't have the extra disk space to convert my highly complex torch Dataset into ffcv format. My bottleneck is disk-io, so what I would really like is just a simple standalone quasi-random sampling dataloader that works with existing torch datasets. The idea would be to sample items into a memory pool as fast as possible and sample from the current data in the pool. Each sample in the pool keeps a count of the number of times it's been sampled, and the most used data is kicked out when the pool gets too big. This way the dataloader itself can read from memory and bypass disk overhead for a penalty in batch diversity.

I don't think that would be possible as we use the file format itself to enable good performance with QUASI_RANDOM. Each dataset file is cut into pages/blocks (default 8MB) and generates an random order that makes sure that we only ever need BATCH_SIZE pages in RAM at any time. Moreover we use the fact that we know ahead of time in which order we will need this pages to pre-load them and compensate for slow disk io.
Unfortunately I don't see how we could make this possible without assuming the structure of the dataset file. What you suggest is a very different strategy. I suggest that you look into webdataset's implementation of shuffle. It seems that it's closer to what you want and also should work without converting your dataset.


Feature/cubed sphere structured functionspace

This is the followup to #58. For fairly obvious reasons, it cannot go in until that one does.
I've made a functionspace CubedSphereCellCoumns which adds a handful of methods to CellColumns which allow (i, j, t) indexing of the functionspace. It should make operations like interpolation significantly simpler. CubedSphereCellCoumns inherits two classes: CellCoumns and CubedSphereUtility. The idea is that I should be able to make similar specialisations of NodeColumns and possibly EdgeColumns using the utility class.
The new functionspace adds two important methods:

idx_t index(idx_t i, idx_t j, idx_t t) which converts an (i, j, t) triplet into a functionspace index.

void for_each(const functor& f, bool include_halo = false) which traverses the functionspace, possibly skipping halos, and applies a functor. The functor should have the signature f(idx_t index, idx_t i, idx_t j, idx_t t).

If you're feeling a bit old fashioned, you could also perform a triple loop of (i, j, t) and skip elements where index(i, j, t) == invalid_index().
closes #59

This PR will be replaced shortly.


persistent data

Hello,
is there a way to make the testrpc data persistent?
I'm especially interested in being able to reuse my existing contracts after restarting testrpc.
Thank you,

Not yet, but this is a feature we've been exploring and hope to implement
soon.
On Apr 3, 2016 12:00 PM, "Jean-Marc Le Roux"<EMAIL_ADDRESS>wrote:

Hello,
is there a way to make the testrpc data persistent?
I'm especially interested in being able to reuse my existing contracts
after restarting testrpc.
Thank you,
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/ethereumjs/testrpc/issues/55

OK. Then I guess I'll have to create a script to re-mine all my contracts when using testrpc then.
Thanks for the fast answer!

You could also write tests in Truffle and it'll do all that for you.
Disclaimer: I wrote Truffle.
On Apr 3, 2016 12:02 PM, "Jean-Marc Le Roux"<EMAIL_ADDRESS>wrote:

OK. Then I guess I'll have to create a script to re-mine all my contracts
when using testrpc then.
Thanks for the fast answer!
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/ethereumjs/testrpc/issues/55#issuecomment-205035386

OK. But (unit) tests are not my only use case for testrpc.
I want to use it mainly during development right now.

Any idea about the date for this feature?

Deploying is one of Truffle's main use cases.
No, no date set.
On Apr 3, 2016 1:45 PM, "Jean-Marc Le Roux"<EMAIL_ADDRESS>wrote:

Any idea about the date for this feature?
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/ethereumjs/testrpc/issues/55#issuecomment-205051622

I was thinking we might leave this open to discuss the matter further. Possible workaround and implementations for example.
My first question would be: would it be foolish to think we could just save the serialized transactions in a file and then replay all of them when testrpc starts? Sure, it's not the best way to do it, but it sounds super easy to do.
Persistent data would be an option, so this startup cost would not impact much existing users.

My proposal would be to implement a PersistentDataProvider and instantiate/add it to the engine:
https://github.com/ethereumjs/testrpc/blob/master/lib/server.js#L157
This new PersistentDataProvider would do two things:

at run time, it would record each receveid payload in a file ;
at init time, it would open that file, load all previously recorded payloads and "replay" them (=> pass them to the next provider).

@tcoulter, do you thing that's the right way to do it?

Hey @promethe42. This is definitely a very important feature. I don't think I made that clear in my responses. Also, your proposal in the comment above somehow missed my eyeballs (could be that I have so many unread messages in my inbox).
I think your proposal is a good one. Most of us who maintain this are very busy, and I know we're always looking for community support. How's your JS skills? I would love to have you take a shot at this, and if you submitted a PR I would give it serious consideration.
I like your approach though. Would be happy to include it.

I will give it a shot then.

@tcoulter could we use evm_snapshot for this?

Answering my own question: no, we can't use evm_snapshot for this. The "snapshot" feature only saves the blocknumber so that we can revert the head of the chain to his block when calling evm_revert.

Are there updates on this? Would really like this feature as well!

I am not restarting testrpc. I just restart my application. Still data stored in my previous run are not there.
Example:- If i have pushed some data into array.It is not present after restarting application.
Is this the way it is supposed to work?

There is quite a large PR I made with this feature. Collaborators welcome!

I can collaborate on doing this. Let me know where to get started.

@raga2560 So the current branch is currently working, whats left to do is for @tcoulter to review the code and maybe discuss alternative implementation strategy as the old testrpc was not designed to work persistently.
You can start by testing it on your machine and start using it and may report on bugs.

Closing this, as this feature is implemented now.