Firebase config variables are not available when deploying functions

Bug, feature request, or proposal:
I'm experiencing a bug in which I can't deploy the firebase functions due to firebase config variables not being available. This might be a problem with unsupported package versions. See below for more information.
What is the expected behavior?
$ npm run deploy

From within firebase/functions should run successfully
What is the current behavior?
When running the deploy script, firebase errors out with the error:
Error: Error occurred while parsing your function triggers. Please ensure you have the latest firebase-functions SDK by running "npm i --save firebase-functions@latest" inside your functions folder.

Error: Firebase config variables are not available. Please use the latest version of the Firebase CLI to deploy this function.
    at init (/Users/pascalprecht/projects/machinelabs/machinelabs/firebase/functions/dist/node_modules/firebase-functions/lib/config.js:51:15)
    at Object.config (/Users/pascalprecht/projects/machinelabs/machinelabs/firebase/functions/dist/node_modules/firebase-functions/lib/config.js:29:9)
    at Object.<anonymous> (/Users/pascalprecht/projects/machinelabs/machinelabs/firebase/functions/dist/invocation-processor/database.js:5:42)
    at Module._compile (module.js:662:30)
    at Object.Module._extensions..js (module.js:673:10)
    at Module.load (module.js:575:32)
    at tryModuleLoad (module.js:515:12)
    at Function.Module._load (module.js:507:3)
    at Module.require (module.js:606:17)
    at require (internal/module.js:11:18)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>deploy: `npm run build && firebase deploy && npm run clean_dist`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>deploy script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/pascalprecht/.npm/_logs/2018-03-24T10_04_32_198Z-debug.log

This is very likely caused by those lines of code:
const serviceAccount = functions.config().fb_service_account;

if (serviceAccount) {
  conf.credential = admin.credential.cert(<any>{
    private_key: serviceAccount.private_key,
    client_email: serviceAccount.client_email
  });
}

So I went ahead and double checked my config variables with
$ firebase functions:config:get

which outputs my configured client_email and private_key. Both are correct.
Which version of MachineLabs (or the package) is affected ?
@machinelabs/firebase-functions@27d92f19
Is there anything else we should know?
I digged a bit further and ran into https://github.com/firebase/firebase-tools/issues/609#issuecomment-359042237, which suggests that firebase-tools and firebase-functions SDK need to be both on latest.
Which makes me think a possible reason for this issue is that I haven't done any firebase deployments with my current setup so far (new laptop, and we didn't introduce any changes to functions/rules etc), however, I'm running on<EMAIL_ADDRESS>(globally), which might not be compatible anymore with<EMAIL_ADDRESS>That's the version that currently gets installed.
I will have to try older versions of firebase-tools to verify whether this is causing this or not.
Sidenote: On that note, we might want to consider switching to npx for firebase-tools as well?
Anyways, would be great if anyone can try it out by installing the latest firebase-tools and verifying whether this is reproducable or not.

Okay, I can confirm that this is not a problem when downgrading firebase-tools to 3.16.0.
This means there was probably a breaking change 3.17.x. I'll investigate further and try to figure out what implications it has and what changes are needed if we'd wanna be on firebase-tools@latest.
The other option would be to agree on 3.16.x but I'd rather vote for executing firebase through npx as well and nail the version down in very package.
Opinions welcome!

Alright, so we can get back to a non-breaking environment when upgrade firebase-functions to latest but also firebase-admin.
<EMAIL_ADDRESS>requires<EMAIL_ADDRESS>which requires<EMAIL_ADDRESS>So as mentioned earlier, we can either now go ahead and update firebase-functions and firebase-admin but this probably breaks the current environment for anyone who doesn't have<EMAIL_ADDRESS>installed. Or, we use npx and add firebase-tools as an explicit dependency of every package.
Another thing we can do is agreeing on<EMAIL_ADDRESS>installed globally, which I'm not a big fan of. I can go ahead an create a PR for the npx option if everybody agrees.

I'm definitely more fan of npx to be honest. We should get rid of all globally installed packages if possible to make sure we all run the same versions. The more contributors we get over time, the more likely it is that people have other (older) versions installed because they use that version at their work for example. That is exactly what happened with yarn. At work, we used another version of yarn then I used here for MachineLabs. That's pretty annoying so I'm glad we got rid of that and agreed on using npx.

Thanks for your feedback @SamVerschueren !
I agree going npx all in sounds like a reasonable way of dealing with these issues. We just need to keep in mind to change all of our deploy scripts as well.
/cc @cburgdorf

I agree that we should run firebase through ngx to ensure everyone is on the same version.


[Feature Request] Add “Hide SponsorBlock Button”

Any way you could put an option in CercubePlus settings to hide the iSponsorBlock icon on the navigation bar?
It just looks so ugly and I would really really appreciate it.

I readed your suggestion and thought I could do it but based on the commits I’ve done, I pretty much failed to add the ability to hide the SponsorBlock button but I’ll still try to add it in.

It seems so simple, but is probably harder to do. I really appreciate you trying!
Also, out of all the tweaked YouTube apps, I like this one 100%, thanks a lot.

No problem! I didn’t want CercubePlus gone but glad I kept the forked repository!

Dayanch96 has added the option, use the latest release to be able to use it! v18.04.3-5.3.11


Settings using data attribute

Configuring slick using an attribute on the element, instead of calling it settings as mentioned in issue https://github.com/kenwheeler/slick/issues/91 I called it slick to avoid potential collisions. For the sake of documentation I've also added a little demo to index.html.

+1

This is in, but I did it a little differently


Allow more elements inside a label of .btn-group

Hello,
Currently, the script doesn't allow placing other elements inside  element of a .btn-group. That is, for example, we can't use glyphicon as a label for a button inside a button groups like this:

            <input type="checkbox" checked="checked">

when the span element receives a click event, the function incorrectly decides that the label is the span element itself leading to an error further on.
This change would allow to correctly respond to an event on any direct child of a label, thus, allowing to use the said glyphicons as labels, which seems to be a popular thing.

In fact the script needs better event delegation, I'll investigate and post a fix as soon as I can.

If it's important to handle an event on any nested element, there two other ways and both seem inefficient to me:

Attach an event listener to every label element inside the button group instead of using one for the whole group. This way event.currentTarget will be the label, but it uses additional listeners.
Iterate over all labels looking for the one containing the event.target. The easiest way would be using Node.contains() but that's additional multiple calls to DOM.

Thus, I ended up with the current code: checking the target element and it's parent for label (common case scenario) and checking for input existence in case elements are nested deeper.

I have a solution for this, unfortunately, as you can see my contribution graph, I've been quite full.
My solution is similar to the way the alert handler works, it even works with later added alerts. So it's known issue. I should close this PR because your suggestion is not the best, but I'll keep it as a reminder.
Thanks for the heads up :)

My solution is similar to the way the alert handler works, it even works with later added alerts.

You mean by adding a listener to the whole document? Well, that will sure make for fewer listeners and it is what jQuery does for bubbling events, but on every click you'll have to check the target if it's a button eligible for toggling, that add's another DOM call or two for every click. Personally, I would rather prefer to avoid it, but it's your call.

I mean by adding an 'eventListener' to the entire btn-group, with proper event delegation. The question is: would we need this to work with later added btn-group items (in order to bind the handler to the whole DOM)?

I mean by adding an 'eventListener' to the entire btn-group, with proper event delegation.

Isn't it what's happening now?
			if (this.btn.classList.contains('btn-group')) {
				this.btn.addEventListener('click', this.toggle, false);
			}

The listener is attached to the .btn-group and it's as proper as it gets, from the looks of it. The whole question was about the way of determining what exact label/button received the click. You can simplify that process by attaching a listener to every label, but that will increase the amount of listeners, and I think it would be less performant than the current solution.

The question is: would we need this to work with later added btn-group items (in order to bind the handler to the whole DOM)?

That's what I was talking about in the previous message. You'd mentioned that you want to handle it like the way Alert does it, and Alert attaches its listener to the document:
document.addEventListener('click', this.close, false); //delegate to all alerts, including those inserted

While doing it for buttons would sure make for fewer listeners, and you don't need to manually instantiate them, it will capture every click inside the document and make DOM calls checking if it's a button and it still leaves the problem of nested elements inside the button.

I have a solution: I will do some stuff as soon as I get to my PC.
Please, if you can or know how, do some testing with require / bower / npm stuff, I have no idea on this, I'm a total n00b.

I checked and your code looks fine, no error and event is properly handled, merging now and repacking all files.


Need to create different sized logos for the app launcher icons

Currently the default app launcher icon is the flutter icon. We need to create the appropriate corresponding icons for various screen sizes

@alielzei @shrestharosy we need the app icons to be done asap for the release

Open PR here


want to add Become an Ethical Hacker

Hello Sir,
I am Deepika Kumari with GitHub id - deep2002deepika
I want to contribute to your repository by adding a course "Become an Ethical Hacker".
Kindly consider my contribution. I'll be very thankful to you for this opportunity.
Regards,
Deepika Kumari

please check contributing.md file to contribute


One-click unsubscribe from newsletters and announcements

It would be cool to have a link in the footer of the emails able to unsubscribe from newsletters and announcements with just a single click.
I guess a unique token generated "at some point" valid for a certain user until the next announcement/newsletter when it will be re-generated.
I guess something 16 chars should be enough to cover most of the concerns for people trying to guess them just to prank on someone else.
Adding to the 1.1 radar for consideration.

We did add an unsubscribe link to notification emails, somewhere in 1.1 3da2132 8b01f91 459cb37


QA fix for phpstan

Q
A

Documentation
no

Bugfix
no

BC Break
no

New Feature
no

RFC
no

QA
yes

Small return type hint update to stop phpstan complaining.
It can return false when the array is empty, we check on that in the code, but because the type hint does not contain false, phpstan complains that the condition is always true (which it isn't in reality)

Actually, we are going to use pslam, you can just rename the PR title

Actually, we are going to use pslam, you can just rename the PR title

We are using phpstan in our project, and it complains about it.
I'll change it to bool.

Any more changes needed or are we good here?


[Core] Regional Fallback

Add regional fallback to azure core.

This was already implemented in https://github.com/Azure/azure-sdk-for-js/pull/23269 but rejected as a feature by the architects in https://github.com/Azure/azure-sdk/issues/5032
Let's not cost or plan work that our architects will not approve.


Changed one small boi to fix video sizing on larger screens

Fixes the issues seen in the screenshot in #5. Seems to happen on larger screens or weird window sizes.

This definitely fixes the overlay issue, but brings up a new issue when you load and resize certain widths:

I don't see it? Is it the aspect ratio of the video you're talking about?

Yes. The video gets scrunched or stretched when you resize

After messing around I think we have to choose one or another. I think the video is expanding outside the hero in order to maintain it's aspect ratio which is what cover does.

Since it does expand outside of the hero, could we use a low z-index for the video so any expansion is underneath the content below?

It seemed to be an even simpler fix...just adding a background color to main so it covers up the video.

But the video is still being stretched?

 It should work now.


Change voice list format

This addresses issue #6
I did add the gender of the voice model, since some thought this property was important to include.
@vaibhavagoel do you think this format will be OK with all the stakeholders?
English (en-ES): Michael (male)

I think the format is ok.  Not sure if we need '(en-US)'.  Maybe say 'US English: Michael (male)'  and 'UK English: Kate (female)' ?

leave the en-US it it's part of the voice id, we don't want to use US in the UI and as en-US in the back-end.

Ok, sure, sounds good.


Make Child Lists use GridLayoutManager?

I'm trying to use the snapshot, and I followed the instructions exactly, yet I still get the error Failed to resolve: com.bignerdranch.android:expandablerecyclerview:3.0.0-SNAPSHOT
What's up??

@MattS8 Sorry for the delay in response, I thought I pushed the snapshot but had a typo in the word SNAPHSOT, it should be available now though per #175, I'm going to close this issue but would love if you can confirm/deny your ability to download in #175
Thanks!


Unique graph index does not work with class hierarchies when using moveToClass

Unique indexes do not always work when dealing with sub-classes.  For example, if you have the following schema:

Friend (base class) - has property uid (long) with unique index
User (sub class of Friend)

In a multi-threaded environment, if you create a Friend and then convert the Friend to a User using moveToClass, you will often wind up with duplicate Users that have the same uid property.

which OrientDB version?

2.1-rc5.   Thanks.
On Thu, Jul 9, 2015 at 5:12 AM, luigidellaquila<EMAIL_ADDRESS>wrote:

which OrientDB version?
—
Reply to this email directly or view it on GitHub
https://github.com/orientechnologies/orientdb/issues/4515#issuecomment-119883076
.

@jbkielis Please could you try with 2.1.2?


Import more then 3 months of data

Note: for support questions, please join our Discord server

I'm submitting a ...
[X ] help request

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc)

I want to import more then 3 months of data. I think I read something about it somewhere, but I'm not managing to find out where.
I've tried loading three months of data, then for the same currency and assets load another 3 months of data, but that doesn't seem to do the trick.

Oh really? I taught the maximum was 3 months! my bad. I'll try your solution!

:)


Allow casts from a type to itself

Fixes #1241

Just want to double check this wording for:
struct s {}
void f(inout s a) { a = (s)a; }

or:
enum e {  a, b, c };
void f(inout e a) { a = (e)a; }

You explicitly list parsers and extern but not compounded (struct, headers, header_unions) types or non-serializable enums.
I don't mind either way. just wanting to make sure those get clarified because even though they can't be targets of a cast, the compounded type initializer looks like a cast so folks might try it ...


Using Exodiff with tolerance file

I'm interested in leveraging the exodiff function you kindly shared, in conjunction with a tolerance file.
exodiff(exofile1,exofile2,tolerance_file)
I think the exodiff command is structured as follows:
exodiff -f tolerance.cmd exofile1.e exofile2.e
I greatly appreciate your assistance with this.

@JTHesse if you upgrade to Exodus.jl v0.8.2 this capability "should" be functional now. I've tried out a few simple examples and added some unit tests but they don't cover all possibilities in the tolerance command file and I'm sure there's some error handling I haven't covered properly yet.
The new exodiff method will return true/false for whether the two files are "equal".
The new syntax is the following
exodiff(ex_1, ex_2; component_file=<some_file>)

where ex_1 and ex_2 are the paths to your exodus files.
Let me know if you run into any issues.

Perfect, exactly what I needed. Thank you!


[Log](Java UDF) add log when array item type not matches

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall

run buildall

run p0

run buildall


ENH Replace record in Permission Table if GroupID already exist

Description
Duplicate Permission records are not created after calling Permission::grant
Override record if a provided GroupId with provided Code already exist in Permission table.
Parent Issue

#10147

@sabina-talipova Can you please add the ENH prefix to the beginning of your commit message? You can change a commit message using git commit --amend

Before this PR, what happens if

grant is called after deny had already been called?
deny is called after grant had already been called?

In each of those cases, do permission checks pass or fail?

So I've looked at what happens currently (without this PR). Deny is currently 'sticky' - it overrides any grants. As soon as a permission is denied at the moment, there's no way to grant it.
e.g:

If you grant and then deny a permission, all permission checks will fail because the permission was denied.
If you deny and then grant a permission, all permission checks will fail as though the call to grant() was never called. The deny takes precedence and is not removed or overridden in the database.

Looking at Permission::permissions_for_member() that is very intentional. We can see that any permission that is denied is not returned as a permission that member can have:
https://github.com/silverstripe/silverstripe-framework/blob/70f1dc8841ac70fb5b029676c4baa9d028bdd6ea/src/Security/Permission.php#L302-L333
I think however that this is intended to mean "If the member has any groups which deny this permission, we cannot allow that member to have the permission" (notice the focus on member). In other words, because members can have multiple groups, a denied permission should take precedence for that member over a granted permission.
This is still true for this PR, except it allows for a previously denied permission for a group to be granted to that group later on. This seems like it is fixing a problem, and while a change in behaviour, the previous behaviour was accidental and incorrect rather than intended.

@sabina-talipova Sorry, I just noticed that the branch this is targeting doesn't match the pulls/4.9 from the PR branch. Just want to double check that you did intent to target 4? Could go either way, since it is a bugfix with no new API but it is also kinda "Improvements of existing functionality (with no API changes)".
Happy either way just want to make sure it's targetting the branch you intended before I merge.

Sabina has confirmed over slack that this was the intended branch. Merging.


Delete gh-readonly-queue branches

There are a slew of branches on the main repository prefixed with gh-readonly-queue. These branches appear to be left over from Github's merge queue bot. The newest of these branches is 8 months old, so I believe the bot is no longer creating these spare branches (or now deletes them afterward).
If these branches are no longer necessary, can they be deleted?

There are also many other stale branches that could also be deleted, but those are technically out of scope of this issue.

apply-deferred
stray-cargo
create-pull-request/patch
gh-pages (unused after #10892)
debug-framecount

I've cleaned up the incidental "I made a branch on the main repo" branches now, but most of the gh-read-only-queue branches could not be deleted. I'm not sure why; I'll file a ticket with customer support.

Awesome! It's weird that you could not delete them. Did you try using Github on the web or through git?
Additionally, did gh-pages not let you delete it, or are you keeping it for another reason?

On the web. I wasn't confident about gh-pages so I left it for now.

Support update:

Thank you for bringing this issue to our attention. I have escalated this to engineering to remove the lock from this branch and will let you know as soon as I have an update from them.

Customer support has come through for me: these are now deleted. Thanks!


cmd/cue/cmd: add go tag for or expressions

This adds a new Go tag which allows the use of OR expressions when generating Cue based on Go.
I'm aware that this change might not be the desired way of resolving the lack of having OR expressions available based on tags in cue tags in Go structs.
If that is the case, take this PR as more of a discussion on how to properly implement this.
I've got the need for this feature, as it'll allow me and my team to generate CUE schemas purely based on our Go structs with the desired defaults that we intend to have on those fields.
A more concrete example is the following:
type Module struct {
	Org string `json:"org,omitempty" yaml:"org,omitempty" cue_or:"*\"org_name\""`
}

#Module: {
	org?: string | *"org_name" @go(Org)
}

Where as the only tag available today cue only supports AND expressions.

Our thinking in this space is to provide the opposite of cue get go, so that you can define your schemas in CUE as the source of truth, and generate Go types which approximate the shapes well enough so that you can decode CUE values into Go.
This is ultimately the most flexible approach, as you can define as many constraints on the CUE side as you want, without having to somehow fit everything into Go struct field tags. We also find that to be more consistent, because we tend to want to write CUE validation and other logic alongside the schema definition, so it's a bit odd if the schema's source of truth is in a Go file separate from the rest of the CUE.
I'm currently working on this as we need it ourselves - the first version will be experimental and fairly simple, but I believe we can extend it to support most use cases.

And I forgot to say - thank you for contributing!

Our thinking in this space is to provide the opposite of cue get go, so that you can define your schemas in CUE as the source of truth, and generate Go types which approximate the shapes well enough so that you can decode CUE values into Go.
This is ultimately the most flexible approach, as you can define as many constraints on the CUE side as you want, without having to somehow fit everything into Go struct field tags. We also find that to be more consistent, because we tend to want to write CUE validation and other logic alongside the schema definition, so it's a bit odd if the schema's source of truth is in a Go file separate from the rest of the CUE.
I'm currently working on this as we need it ourselves - the first version will be experimental and fairly simple, but I believe we can extend it to support most use cases.

This is exactly the route we wanted to go in the first place, but realized that it wasn't entirely possible yet.
Hence why this is our approach currently, but we'd be excited to switch over to having CUE be our source of truth later on.


fix(zk): fix bug on the PR #302

In this PR, code changes that made code, which should not operate in parallel, to run in parallel was reverted.

This PR should be merged after #305.

I changed the description - please reflect the changed wording in the commit description as well~
The commit name would be more aptly named as "fix bug in PR#302"


Fix panic when detected SDK does not have a bin directory

Due to old versions of Visual Studio having been installed in the past, my computer has an instance of the Windows 8.1 SDK detected as such:
KitsRoot81    REG_SZ    C:\Program Files (x86)\Windows Kits\8.1\

Maybe because of a failed uninstallation or some other unknown reason, this directory does not contain a bin subdirectory, so p.join("bin").read_dir().unwrap() panics and causes the project's build to fail.
This PR fixes this panic by removing the call to unwrap() and reworks the loop logic to only iterate through entries that don't yield an error.
There are a few other uses of unwrap that could potentially cause problems, so I'm probably going to send some more PR's to refactor those.

Thanks for the commit.


Add support for RTX RTOS

Hey,
In our team we are working with the MBED  framework for embedded development.
MBED is coupled with RTX RTOS, and we would love to work with your extension, which as stated currently supporting FreeRTOS and AzureRTOS only.
Many thanks

I agree this suggestion and l am using RTX5 also.
RTX has provided SVD file in ARM CMSIS-RTOS2.

Hi @liadekel, @orzcyt, we are currently investigating where on the backlog we can place this and when we'll have bandwidth for this, I wanted to let you all know that it is on our minds. Thanks for your feedback!


Support for rgb() / rgba()

It would be nice if this library supported animating between rgb / rgba color functions.

pretty sure you can supply those. react simple animate it just sugar syntax on top of CSS animation. give it a try.


[C++] Don't allow the inclusion of passwords (storage account keys) in Auzre ABFS URLs

Describe the enhancement requested
Outline
The Azure Blob File System (ABFS) support in Apache Arrow, implemented in C++ API by #18014 and integrated into Python API by #39968, currently allows embedding a storage account key as a password in an ABFS URL.
https://github.com/apache/arrow/blob/r-16.1.0/cpp/src/arrow/filesystem/azurefs.h#L138-L144
However, I strongly recommend stopping this practice for two reasons.
Security
An access key of a storage account is practically a "root password," giving full access to the data in the storage account.
Microsoft repeatedly emphasises this point in various places in the documentation and encourages the protection of account keys in a secure place like Azure Key Vault.

Protect your access keys
Storage account access keys provide full access to the storage account data and the ability to generate SAS tokens. Always be careful to protect your access keys. Use Azure Key Vault to manage and rotate your keys securely.
https://learn.microsoft.com/en-us/azure/storage/common/storage-configure-connection-string#protect-your-access-keys

Embedding a storage account key in an ABFS URL, which is usually not considered confidential information, may lead to unexpected exposure of the key.
Interoperability with other file system implementations
For historical reasons, the syntax of the Azure Blob File System (ABFS) URL is inconsistent between different file system implementations.
Original implementations by Apache Hadoop's hadoop-azure package link

<EMAIL_ADDRESS>
This syntax is widely used, particularly by Apache Spark.
Python adlfs for fsspec link

Hadoop-compatible URL syntax , and
az://<container>/path/to/file
adfs[s]://<container>/path/to/file

Rust object_store::azure link

Hadoop-compatible URL syntax
adlfs-compatible URL syntax , and
azure://<container>/path/to/file
https://<account>.blob.core.windows.net/<container>/path/to/file
https://<account>.dfs.core.windows.net/<container>/path/to/file

DuckDB azure extension link

adfss://<container>/path/to/file
adfss://<account>.dsf.core.windows.net/<container>/path/to/file

Apache Arrow link

Hadoop-compatible URL syntax , and
<EMAIL_ADDRESS><EMAIL_ADDRESS>abfs[s]://[<account[:<password>]@]<host[.domain]>[<:port>]/<container>/path/to/file
abfs[s]://[<account[:<password>]@]<container>[/path]

This inconsistency of the syntax already causes problems in applications using different frameworks, including additional overhead to translate ABFS URLs between different syntax. It may also lead to unexpected behaviours due to misinterpretation of the same URL by different file system implementations.
I believe a new file system implementation should respect the existing syntax of a URL scheme and SHOULD NOT invent new ones. As far as I understand, no other ABFS file system implementation allows embedding storage account keys in ABFS URLs.
Component(s)
C++, Python

Could you clarify your suggestion?
The followings?

We should reject URLs that have :password in the "userinfo" URI part
We should reduce supported URL patterns

BTW, it seems that you misinterpreted supported formats:

Apache Arrow link
* Hadoop-compatible URL schemes, and
*<EMAIL_ADDRESS>* adfs[s]://<account>.dsf.core.windows.net/<container>/path/to/file
*<EMAIL_ADDRESS>

Hadoop-compatible URL schemes (2. in the Arrow source), and
<EMAIL_ADDRESS>(2. in the Arrow source)
adfs[s]://<account>.dsf.core.windows.net/<container>/path/to/file (1. in the Arrow source and Azure Data Lake Storage Gen2 compatible)
<EMAIL_ADDRESS>(: before <password> is missing and this is same as the above pattern)

All of them listed by you are compatible with https://learn.microsoft.com/en-us/azure/storage/blobs/data-lake-storage-introduction-abfs-uri .
"3." and "4." in the Arrow source are missed.
"3." is for Azurite. It's helpful for development.
"4." is for compatibility with adlfs, object_store::azure and DuckDB.

@Tom-Newton Could you take a look at this?

@kou
Thank you very much for your answer and correction.

We should reject URLs that have :password in the "userinfo" URI part
We should reduce supported URL patterns

I suggest only the first point. Regarding the second point, I don't have a strong objection as long as a file system implementation supports the Hadoop-compatible syntax.
However, as having storage account keys in ABFS URLs is a new practice invented by Apache Arrow and has security concerns, I suggest removing this feature.

BTW, it seems that you misinterpreted supported formats:

You are right. I have updated the issue description, and let me copy-paste the original comment in the source code.
  /// 1<EMAIL_ADDRESS>  ///    [/\<container\>[/\<path\>]]
  /// 2<EMAIL_ADDRESS>  ///     [/path]
  /// 3. abfs[s]://[\<account[:\<password\>]@]\<host[.domain]\>[\<:port\>]
  ///    [/\<container\>[/path]]
  /// 4. abfs[s]://[\<account[:\<password\>]@]\<container\>[/path]

In my view, only the second pattern (without password) is Hadoop-compatible. 1 and 3 do not include the container (file system) name in the authority part of the patterns. 4 has a different syntax for the authority part.
But as I explained above, I don't have strong objections against these patterns except for having passwords in URLs.

To be honest I think I will struggle to find time to work on this. Personally I'm in favour of removing some of this extra URL parsing functionality, including passwords, but I'm also not especially concerned about it. It is common practice to use SAS tokens in blob storage URLs.

I'm neutral for this proposal.
If we reject the password value, users can't use account key based authentication with the URI interface. It'll useful for local development with Azurite.
FYI: The Arrow's Azure filesystem doesn't send the URI specified by an user to somewhere and Azure SDK for C++ doesn't send raw account key to Azure. Azure SDK for C++ uses account key to generate hash value for authentication.
Could you share bad scenarios you think?

Could you start a discussion on the<EMAIL_ADDRESS>mailing list too to collect more feedback for this?
See also: https://arrow.apache.org/community/#mailing-lists

If we reject the password value, users can't use account key based authentication with the URI interface. It'll useful for local development with Azurite.

I use Apache Arrow mainly in Python code. Let me explain by using PyArrow as an example.
When working with the PyArrow API, we have two methods to specify a file system.

Create a FileSystem instance and explicitly set it as an argument.
Let PyArrow infer a file system from a file path URL.

import pyarrow.parquet as pq

# Explicitly set
s3 = fs.S3FileSystem(..)
pq.read_table("my-bucket/data.parquet", filesystem=s3)

# Infer from a URL
pq.read_table("s3://my-bucket/data.parquet")

For 1, we don't need to embed a storage account key or any other credentials for file system access in a file path URL as long as we can set them when we create a file system instance.
s3 = fs.S3FileSystem(access_key=...)

For 2, many existing file system libraries provide an interface to configure credentials for file system access in a global context.

Hadoop HDFS: core-site.xml etc. in a classpath
Python fsspec:  fsspec.config.conf link
Rust object_store: environment variables
DuckDB: secret manager link
Apache Arrow: S3FileSystem and GcsFileSystem  try to obtain credentials from environment variables or standardized locations in the local file system

Even if it looks convenient, embedding credentials in a file path URL is generally unnecessary. Other file system implementations work well without this method.
In Azure, EnvironmentCredential used by DefaultAzureCredential defines a set of environment variables to configure credentials

https://learn.microsoft.com/en-us/python/api/azure-identity/azure.identity.environmentcredential

There is no standardized environment variable for setting storage account keys but AZURE_STORAGE_ACCOUNT and AZURE_STORAGE_KEY are widely used (example).
We should consider these common practices instead of inventing new URL syntax.

Could you share bad scenarios you think?

There are several Azure Blob File System implementations in Python, and we frequently need to use multiple implementations in the same code. However,

Most ABFS implementations, except for Arrow's AzureFileSystem, do not assume that ABFS URLs can contain confidential information like storage account keys.
It is not always clear which implementation is actually used in a library.

PyArrow has native AzureFileSystem implementation since Arrow 16.0.0. However, delta-io implemented on Arrow uses Rust object_store.
Pandas initially used the fsspec's ABFS implementation but silently started using Arrow's native implementation after the release of Arrow 16.0.0 (#41496).
DuckDB has native ABFS support. But Rust object_store is eventually used when reading Delta Lake into DuckDB by using ibis API.

Because of 2, an Arrow's style ABFS URL containing a storage account key can be accidentally passed to a different ABFS implementation. However, the different implementation usually does not assume the passed URL contains a storage account key, as explained in 1.
This leads to the rejection of the URL and an error message like the one below exposed to error logs, etc.
Invalid file path: abfs://my-container:(plain text of a storage account<EMAIL_ADDRESS>
Having storage account keys in ABFS URLs can cause this kind of interoperability issue with other ABFS implementations.

Certainly account key is more concerning but it is common practice to use SAS tokens in blob storage URLs.
This is true, but a blob URL containing an SAS token is usually (and should be) treated as confidential information that must be carefully handled to avoid unexpected leaks.
We cannot apply the same practice to file paths in general that appear in many places in a code.

Could you start a discussion on the<EMAIL_ADDRESS>mailing list too to collect more feedback for this? See also: https://arrow.apache.org/community/#mailing-lists

@sugibuchi Could you do this with the additional information?

The discussion thread on<EMAIL_ADDRESS>https://lists.apache.org/thread/mhwr2lvtxvjcqos12k7hr4cqkdofrxxo

Issue resolved by pull request 44220
https://github.com/apache/arrow/pull/44220


null before API URL on verb section

I've upgraded cypress-plugin-api from v1.7.1 to v2.1.0, using npm i cypress-plugin-api@latest -D, and now there's a null just before the API URL on the verb section, as you can see on the image below.

And here's the project on GitHub, in case you want to reproduce the issue https://github.com/wlsf82/cy-api-coursify.
Note: Look for the cypress-plugin-api-v2 branch.
Cc @filiphric.

great catch, thanks for reporting! I’ll fix it right away!


Metadata alignment

Align on https://github.com/opentracing/specification/blob/master/semantic_conventions.md vs,
https://github.com/census-instrumentation/opencensus-specs/blob/master/trace/HTTP.md
https://github.com/census-instrumentation/opencensus-specs/blob/master/trace/gRPC.md
https://github.com/census-instrumentation/opencensus-specs/blob/master/resource/StandardResources.md

https://docs.google.com/spreadsheets/d/1FTLt781AGU6wnWLy7ESoHR5rPpSyeSSB0G5VzJMj0N8/edit?usp=sharing

What changes we may need in current codebase:

[ ] Add component or type attribute definition. (The software package, framework, library, or module that generated the associated Span. E.g., "grpc", "django", "JDBI".)
[ ] Add DB metadata:  db.instance, db.statement, db.type, db.user
[ ] Add message_bus.destination. (An address at which messages can be exchanged. E.g. A Kafka record has an associated "topic name" that can be extracted by the instrumented producer or consumer and stored using this tag.)
[ ] Peer (remote service) tags perhaps needs to be natively supported. Mentioned here https://github.com/census-instrumentation/opencensus-specs/issues/135
[ ] Add producer and consumer for span kind: https://github.com/census-instrumentation/opencensus-specs/issues/54

Merging:

[ ] OT error attribute should be reflected as one of span errors
[ ] I suggest moving sampling.priority to tracestate
[ ] Attribute span.kind already in Span as a strongly-typed value.

For log attributes:

error.kind, error.object, stack - may be covered with exception type suport instead of log https://github.com/census-instrumentation/opencensus-specs/issues/154 Question - are those have to be annotations and not a separate event?
event and message are taken care of in https://github.com/bogdandrutu/openconsensus/issues/16

For sampling.priority why do we need that in the Tracestate? That implies is propagated, and not everyone needs that.

I think if one want sampling.priority - tracestate should be the mechanism to propagate it. @carlosalberto @yurishkuro is it used only for individual span in attributes or typically propagated?

@SergeyKanzhelev sampling.priority is usually used per individual Spans, as far as I know. @yurishkuro happen to know more about this one?

sampling.priority is usually used to programmatically force sampling for a given trace based on conditions known to application/instrumentation only (not to the tracer). It is theoretically can be used to disable sampling either, but I haven't seen that usage pattern (although do vaguely recall some discussion with one of the user groups).

@yurishkuro so if it forces decision for a trace - I'd assume you need to propagate it and tracestate should be a better place for it.

TODO: write these out as constants in code. :)

From Dynatrace I got this document which can be very useful as a starting point: https://docs.google.com/spreadsheets/d/1H0S0BROOgX7zndWF_WL8jb9IW1PN7j3IeryekhX5sKU/edit?usp=gmail#gid=0


(PUP-5284) Make test skip reasons explicit

Update acceptance tests to make the reasons for their status as 'skipped' explicit.

CLA signed by all contributors.


Gh 2380 re run release

Related Issue

Resolve #2380

Codecov Report

Merging #2381 (f4df325) into develop (3fe0943) will decrease coverage by 0.44%.
The diff coverage is 80.95%.

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

Codecov Report

Merging #2381 (f4df325) into develop (3fe0943) will decrease coverage by 0.44%.
The diff coverage is 80.95%.

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


Organization of the repository

Many of the Searching and Sorting solutions in different languages are separated in completely different folders with the same name and are not located in just one folder as they should be. This issue needs to be solved asap because it is confusing for new contributors.

I would like to give my contribution to solve this issue.


Publishing fork under a new name

First let me thank you for your amazing work on this fork.
It would be nice that all of this effort gets more recognition. It's actually not that straightforward to land on this repository.
Have you considered publishing this package under a new name?
Regards,

I'm open to change it, do you have a better name? 😄

@aladdin-add Hello Man i loved your work, i have also been working on bringing this project back to live.
Are you interested in a chat? I think @Fedeorlandau is right, it would be best to bring the changes and improvements under a new name as it will be simpler to distinguish. How about TS-build? actually I have been playing around esbuild trying to implement something like tsdx but when I saw your fork I thought it's better to learn and contribute here only.
Btw I think it's best to ditch parcel for the example playground as it's bringing some issues and breaking HMR.

Due to this issue, i decided to replace it with Vite, a build tool which uses esBuild and rollup both. and with a few changes, the dev server including HMR works like a charm

How about TS-build?

:+1 SGTM!
let's chat here: https://discord.gg/fMDeSvvm2p

ts-publish (tsp) is my recommendation since this is for publishing ts packages lol

ts-publish, and ts-builder has been taken. 😢
@sidwebworks recommended ts-build but it was already taken, and tsdx is not just building. so, we prefer dts-cli(dts). it has two meanings:

develop typescript
develop + test + ship

just let me know what you think. :)

Sounds great!

Alright guys, got the first PR going! let's see how it goes

dts-cli v0.17.0 was released. :🎉


(FACT-2727) add load averages for Solaris

jenkins please test this on all

CLA signed by all contributors.

am i reading this right, that bsd doesn't need a specialisation, but Solaris does?

Solaris and BSD need the same load_averages resolver. So I moved it to /lib/facter/resolvers where we have all the common resolvers, which are shared by multiple platforms. These resolvers are loaded for every platform.


KAFKA-7360 Fixed code snippet

Fixed code snippet in documentation to make it syntactically correct.
Ref. https://kafka.apache.org/20/documentation/streams/developer-guide/processor-api.html#accessing-processor-context
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@halorgium @astubbs @alexism @glasser Please review the PR.

@junrao Please review the PR.


Bump Standard Notes version and update repository information

Bump Standard Notes version from v3.22.11 to v3.23.21. Additionally, Standard Notes made their desktop repository archive status and migrated their desktop application to their standardnotes/app repository.

[x] I have read the Contributing Guide.

Thanks for your PR! I've made a few changes and running checks now

/verify

@tech189 Thanks for the assistance in the PR. Did not pick up on the URL encoding characters -- noted for the future.

No problem!


How to override default (optional) start, stop parameters?

I'd like to override the default start, stop parameters and provide start: v.timeRangeStart, stop: v.timeRangeStop instead (in Grafana v8.5.5.).
Based on the function type signature of schema.measurementTagValues() function, I understand that start, stop parameters are optional. I understand that they have a default value and are not required. It also means (for me) that I can also change them to different than default values. However, if I try to add them to the call like that:
import "influxdata/influxdb/schema"

schema.measurementTagValues(bucket: "<bucket>", measurement: "<measurement>", tag: "<tag>", start: -15d)

I have the following error message:
invalid: type error @3:1-3:120: found unexpected argument start

If I try to add them to the call like that:
import "influxdata/influxdb/schema"

schema.measurementTagValues(bucket: "<bucket>", measurement: "<measurement>", tag: "<tag>", ?start: -15d)

I have the following error message:
invalid: compilation failed: error at @3:108-3:120: unexpected token for property key: QUESTION_MARK (?)

How can one override the optional default parameters?
Relevant URLs

https://docs.influxdata.com/flux/v0.x/stdlib/influxdata/influxdb/schema/measurementtagvalues/
https://docs.influxdata.com/flux/v0.x/function-type-signatures/

@PeterMilovcik These functions in the schema package were updated with configurable start and stop parameters in Flux 0.155.0. What version of InfluxDB are you using. It could be that the version of Flux packaged with your specific version of InfluxDB doesn't support the updated/added parameters on the schema functions.

Hi, we are using official docker image influxdb:2.0.8.

Just updated to InfluxDB 2.3.0. and it works great. Thank you.


[Enhancement] Ability to better visually distinguish environments

Insomnia supports coloring the environment, however that creates a tiny dot that i think can be overlooked pretty easily.
Could you add an option for the color to be used more visibly?

What do you suggest?

I like that it's prominent across the entire app window. It might not look great on the default theme though. However, it's good inspiration! Thanks for that awesome mockup 😄

Well, that is where the color support comes in, as it allows you to choose any color. Sure there are colors that won't look good on dark theme and colors that won't work on default, but you usually won't change a theme once you set it, so you just choose colors that work for you.

hmm

That's a good point. And your screenshot doesn't actually look that bad (compared to my intuition) 👍

This feature was available until the last update, has it been removed?

I would love to see this feature returned.


Vendor.js bundle is 1.5 mb already. How to reduce it ?

I am using the Vue hackernews as a boilerplate for a project. I just realized the vendor.js bundle size is over 1.5 mb in total it contains many packages that the browser doesn't need like "mime-db", "bn.js" (big number), "bluebird.js", "tweetnacl", "elliptic", etc. Some of them are used by the express which is used only on the server side, but most of the packages are included to the browser vendor.js bundle.
I installed the Webpack bundle analyzer and I saw there are so many redundancies as well. Any help to remove them out from the vue-hackernews 2.0 boilerplate.

I was able to reduce the entire chunks including vendor.js to 1.5 mb
But still, the vendor.js file has 1.4 mb and I have no clue why? Any explanation with mime-db and mime-type is required in frontend ?

Hi Thanks! I checked for Firebase. My code doesn't use firebase. I searched throughout all the files. Firebase was also removed from the package.json dependencies.
I can only see that firebase is indeed installed and shown in the yarn.lock but otherwise, my code doesn't use firebase anymore.

Also keep in mind Webpack's tree-shaking only applies to production bundles. It's not perfect, but it should cut down on the bloat significantly.
This repository is also incredibly outdated, there's new versions of almost every dependency, including Webpack. I suggest taking this discussion to a more appropriate venue, such as Discord or Forum.

Today I decided to take another look at this issue. It seems it was my fault by installing request-promise npm. That library alone is over 1 MB. After I replaced request-promise with node-fetch, I got less than 380kb in total.


Fixes bug 1149355 - shows Vidyo room info on summary and review page

@peterbe please review this

Excellent!! So good to see you back in the game!


Wrong variant select in multi module different build type project

First: Thank you for this plugin, I was looking for something like this for a long time! 🙂
I have have a small issue:

The project uses multiple modules, multiple flavors (let's say A, B and C) and multiple build types (debug, release, test)
Some library modules are not flavored and only contain debug and release build type
The app module uses all three flavors and all three build types (so there are 9 different variants in total)
Some modules also use the three flavors but only two build types (debug, release).

When I select flavor A for the app module and test as build type, I need to select release (because basically test is just a release version with some things on top) for the library modules and flavor A + release for the modules which use flavors but don't have the test build type.
So I set release, aTest and aRelease in the variant helper plugin. The result is everything is changed to release build variant, so the flavor selection works correctly but the test build type is not selected but release instead.
If you need more information or a test project just let me know.

A test project would be great to help with the debugging. I think I know where to look, but making sure I'm not hunting the wrong thing would be best.

A test project would be great to help with the debugging. I think I know where to look, but making sure I'm not hunting the wrong thing would be best.

https://gitlab.com/PhilippNowak/varianthelpertest
Clone and open this project and try to set these variants:

The app module will be set to firstRelease too instead of firstSystest @gtcompscientist

https://gitlab.com/PhilippNowak/varianthelpertest
Clone and open this project and try to set these variants:

The app module will be set to firstRelease too instead of firstSystest @gtcompscientist

https://github.com/PandoraMedia/variant-helper-plugin/pull/3
If you would like to test your main project against this PR, that would verify the fix before I publish.

https://github.com/PandoraMedia/variant-helper-plugin/pull/3
If you would like to test your main project against this PR, that would verify the fix before I publish.

variant-helper-plugin-1.1.0.zip
For easier testing, unzip and import the variant-helper-plugin-1.0.0.jar to your IDE and let me know!

variant-helper-plugin-1.1.0.zip
For easier testing, unzip and import the variant-helper-plugin-1.0.0.jar to your IDE and let me know!

Works perfectly, thank you! :)

Works perfectly, thank you! :)


Axios package security vulnerability issue

This should be resolved with an update in the package.json
warning magento-api-rest ><EMAIL_ADDRESS>Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410

Hi,
Have updated the packages and published the latest version to npm.

Hi,
Have updated the packages and published the latest version to npm.


Something went wrong while trying to load the full version of this site.

When tring to access https://discuss.flarum.org/ I get the above error message lately. I am using Chrome on Win 10 64x

Sorry to hear that. We recently updated to the latest dev version.
Please try deleting your cookies for the site, and loading it again.

Does not work any more. I tried clearing the cookies.

Please also try clearing your browser's cache.
FYI, this is the issue tracker for the flarum.org website, so it's not the best place to seek support for issues you're experiencing with the forums. If you need such support, you'll get better (and quicker!) results by asking via Gitter chat.

I am closing this due to inactivity.
Feel free to report back if you still have issues - we'd also be interested to hear whether what @dcsjapan suggested did help you.

It corrected itself but clearing the cache  did not work.


Added missing repository url in README

I had trouble finding the source code for chunkdot, added missing repository url in README so it should appear in Pypi.
Added some classifiers.

Thanks Flo


import fails on Linux due to missing library libcrypto.so.10

torchvision is seeing CI failures on Linux for a missing extension loaded by torchdata. I can reproduce with docker:
docker run python:3.7 bash -c \
    'pip install --pre torch torchdata --extra-index-url https://download.pytorch.org/whl/nightly/cpu && python -c "import torchdata"'

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/local/lib/python3.7/site-packages/torchdata/__init__.py", line 7, in <module>
    from torchdata import _extension  # noqa: F401
  File "/usr/local/lib/python3.7/site-packages/torchdata/_extension.py", line 34, in <module>
    _init_extension()
  File "/usr/local/lib/python3.7/site-packages/torchdata/_extension.py", line 31, in _init_extension
    from torchdata import _torchdata as _torchdata
ImportError: libcrypto.so.10: cannot open shared object file: No such file or directory

#399 might be the offender. #415 did not make it into yesterday's nightly.

I think @ejguan  is on it https://github.com/pytorch/text/pull/1729#issuecomment-1128886947

I think I found the issue: the Linux wheel build is running in a specific container
https://github.com/pytorch/data/blob/f80d07b0670ca2c68f06e4dfe236a6dbe6dd1b28/.github/workflows/_build_test_upload.yml#L55
which has a different version of libcrypto than ubuntu:
$ docker run quay.io/pypa/manylinux2014_x86_64 bash -c 'ls -l /usr/lib64 | grep libcrypto'
lrwxrwxrwx  1 root root      19 Apr 18 12:29 libcrypto.so.10 -> libcrypto.so.1.0.2k
-rwxr-xr-x  1 root root 2520920 Mar 28 15:42 libcrypto.so.1.0.2k

$ docker run ubuntu:22.04 bash -c 'ls -l /usr/lib/x86_64-linux-gnu | grep libcrypto'
-rw-r--r--  1 root root 4447536 Mar 16 08:35 libcrypto.so.3

I was unable to install libcrypto.so.10 on Ubuntu through vanilla apt.
Thus, if we depend on this specific version, we probably need to ship it with wheel.

@pmeier Thanks for reporting this. I will take a deeper look.

I think openssl-static in https://github.com/pytorch/data/blob/f80d07b0670ca2c68f06e4dfe236a6dbe6dd1b28/.github/workflows/_build_test_upload.yml#L92 is culprit. Let me give it a try.

I think openssl-static in [...] is culprit

Nope. As you can see above, libcrypto.so.10 is already present in the vanilla image without installing anything else.
$ docker run -it quay.io/pypa/manylinux2014_x86_64 bash
$ ls -l /usr/lib64 | grep libcrypto
lrwxrwxrwx  1 root root      19 Apr 18 12:29 libcrypto.so.10 -> libcrypto.so.1.0.2k
-rwxr-xr-x  1 root root 2520920 Mar 28 15:42 libcrypto.so.1.0.2k
$ yum -y install openssl-devel openssl-static curl-devel zlib-devel
[...]
$ ls -l /usr/lib64 | grep libcrypto
-rw-r--r--  1 root root 4697014 Mar 28 15:42 libcrypto.a
lrwxrwxrwx  1 root root      19 May 18 13:57 libcrypto.so -> libcrypto.so.1.0.2k
lrwxrwxrwx  1 root root      19 Apr 18 12:29 libcrypto.so.10 -> libcrypto.so.1.0.2k
-rwxr-xr-x  1 root root 2520920 Mar 28 15:42 libcrypto.so.1.0.2k

@ejguan Thanks for looking into this.
The specific issue is currently breaking TorchVision's CI for new PRs, which can cause some confusion to contributors. As Philip clarified, the issue only appears on Linux. Do you have any idea on when the fix will land? Do you recommend us to turn off the test until this is done? Thanks!

The problem is that the AWS package pulls in libcrypto, but we don't statically link against it. Thus, when trying to import the package it looks for libcrypto.so.10 on the system and errors out if it doesn't find that.
If we want to depend on the compiled AWS package, we need ship libcrypto as well. Note that this of course has some license implications. Furthermore, this is only needed for wheels, since on conda we can simply depend on another package to provides libcrypto.
Looking at the CMakeLists.txt of the AWS package, libcrypto is mentioned two times:

https://github.com/aws/aws-sdk-cpp/blob/c1df81935a08232b853e2d7eae6fd8c70f99d459/CMakeLists.txt#L51
https://github.com/aws/aws-sdk-cpp/blob/c1df81935a08232b853e2d7eae6fd8c70f99d459/CMakeLists.txt#L191

@ejguan Thanks for the update. Can you provide a very rough estimate on when you believe this will become available? We are trying to figure out if we should disable the specific CI job or leave it be. A rough estimate will help us decide this easier.

All nightly should be updated https://github.com/pytorch/data/actions/runs/2353439246

@ejguan Thanks a lot for the help. As far as I can tell, this fixed the problem. If no additional action is required on your side, I think we can close the issue.

@ejguan Thanks a lot for the help. As far as I can tell, this fixed the problem. If no additional action is required on your side, I think we can close the issue.

@datumbox
Thank you for confirmation. Let's keep this issue opened until I fix AWS binary.

Closing this issue as #421 has landed.


This template does not work

I am using Visual Studio 2017 and I have tried the steps above. When I try to build the project, with a valid website as a url it doesn't work and give me the error:
Severity	Code	Description	Project	File	Line	Suppression State
Error		Project must have a reference to an application. Please add a reference under the 'Applications' node in the Solution Explorer.	PatternBlockDemo.Uwp1	C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Microsoft\DesktopBridge\Microsoft.DesktopBridge.targets	173
Any ideas?

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

ID: c306f3b9-d287-beba-eb3b-513e58df2440
Version Independent ID: 787855c5-24d2-b772-e4c3-ce43118e5adb
Content: Tailor your PWA for Windows - Microsoft Edge Development
Content Source: microsoft-edge/progressive-web-apps/windows-features.md
Product: microsoft-edge
GitHub Login: @MSEdgeTeam
Microsoft Alias: msedgedevrel

I am getting the same error

I'm getting the same issue on build.

If you're on an older version of Visual Studio, you need to use a different project template. It's confusing since they have the same name.
For instance, I'm on Visual Studio 2017, and I needed to use the "Hosted Web App (Universal Windows)" project template.

While that might be true, the new version doesn't even have the type that we are talking about. The "Hosted Web App (Universal Windows)" appears to now be depreciated. Even though this article says to use it. So it's pretty unclear what you are supposed to do.

There appears to be only one template where this error doesn't happen:
Other Languages -> JavaScript -> Progressive Web App (Universal Windows).

is there any work around to by pass this error?
i'm using the last Visual Studio 2019

Hi! The Hosted Web App / Progressive Web App template is only available with Visual Studio 2017, we removed support for it in Visual Studio 2019. We renamed it from Hosted Web App (HWA) to Progressive Web App (PWA) during the life of VS2017 but it is the exact same template.
Regarding the error you have, I've not sure exactly when you have it. Is it right after creating the project in VS2017? After running the solution? Did you create a JavaScript -> Windows Universal -> Progressive Web App (Universal Windows) project?

i have fixed the issue using this solution :
https://github.com/MicrosoftDocs/edge-developer/issues/252#issuecomment-598139288

Apologies for this issue having gotten stale. I have read through the comments, and I don't think there is something actionable to do here anymore. So I will be closing this issue, but please feel free to re-open a new one if there is still an issue with the Edge documentation site regarding the above discussion.


Add unit tests for tgbot

Need to add unit tests for new functionality in leetty-tg-bot

in #7 added many new functions, but its all not tested.


When trying to write a test I get 'Error: Call to undefined function Tests\onNext()'

Hi,
I'm trying to write a test for an observable in my code. In there I have this code:
$observable = new HotObservable(
            $scheduler,
            [
                onNext('foo'),
                onNext('bar')
            ]
        );

Unfortunately this gives the error that onNext does not exist.
How do I solve this?

Make sure that you're loading the test helper functions in composer:
https://github.com/ReactiveX/RxPHP/blob/master/composer.json#L38-L41


[New game]: Catch the Ball

🎮 Game Request
A ball will be thrown form the top, and we will have to use arrow keys, to prevent it from reaching the bottom of the screen.
Point down the features
There will be a paddle at the bottom of the screen, which will be controlled using the left and right keys on the keyboard. If it catches the ball, a new ball will appear on the top.
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @VijaySamant4368 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign

Hey @VijaySamant4368 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Help with passing parameters to bash

I am trying to pass and read the parameters from websocketd to bash. Can anyone give me a sample on how it works. new to websockets

Do you need params passed same on each start or different depending on what sent from browser?
From the browser you could not do actual bash params. You have Environment variables and input. You could use them to construct new params and exec subsequent process with them. It's just all more complex that way.
If you could re-phrase, describing what you tried and what you could not achieve, it would be easier to provide help.


OracleRouter Cleanup

We added a new OETHOracleRouter for the new launch. It is correct for OETH.  We still have the old OracleRouter. However changes that were made in in the base code, make the non-eth router contract neither compatible with the current deployed OUSD code, nor correct for a new deploy of the new shared vault code for OUSD.
- We should move the price impl from OETHOracleRouter to OracleRouter
- We should get rid of the no longer needed price impl in OracleRouterBase and just have an empty method.

We may not need two separate oraclerouters. Might be a tiny bit more gas efferent to do so, but I think it's small.


Quality control vignette review

Here is feedback on the quality control vignette:

[ ] 1. I was surprised by the work flow to run tab_completeness without running read_results and read_dqo.  The vignette makes it sound like this would be the preferred work flow, but I think the standard work flow would be the opposite - to run read_results then read_dqos then tab_completeness.  That would be a clear work flow for people to understand.
[ ] 2. Just to confirm, I assume you are still planning to create a single function that will run the full QC Review report, which would internally use the tab_completeness function.  So users would not have to run the tab_completeness function by itself.
[x] 3. In the completeness summary table, I think we do need a Hit/Miss column because users won't always be printing in color.
[x] 4. In the completeness summary table, remember to leave a user-fillable column for Number of Censored Records.
[x] 5. In the description of the frequency summary table, you mention "the percentage of observations in the results file that satisfy the checks".  Instead, I would describe this as "the number of quality control checks that were performed as a percentage of total observations".
[x] 6. I assume you are still building the frequency summary table that shows a separate row for each QC type and parameter, with Number of Dups/Blanks/Spikes.

@ben-wetherill can you please review the text in the updated QC vignette?  It has updated text for the frequency and completeness checks.
And yes, when I'm done writing all the core functions, I will roll them all into a single QC function to generate all output together.  It will follow a workflow similar to your first bullet point above.

It's looking good.  Here are some suggestions:

The section labeled "Quality Control for Frequency and Completeness" can be removed, and you could move most of the text to the Frequency section.  It is not valid for the Completeness section because completeness is not about the number of QC samples.  It is only about the number of qualified samples.
In the Frequency summary table, I think we want to divide the Lab Spikes section into two sections - one for lab samples and one for in-situ instrument readings ("Instrument Checks").  Lab Spikes doesn't make sense for instruments.  The differentiation would be based on characteristic name.  I think this is safe, with the exception of dissolved oxygen maybe.  I will send an updated version of the parameter mapping file with this distinction.
I made two small changes directly in the vignette.  Did you see them?

@ben-wetherill I think I've got the lab spike and instrument checks separated correctly in qcMWRfre and tabMWRfre.  They're separated based on the activity type and I applied the Spike/Check Accuracy values to both in creating the summary table.  The frequency table is the same, just not separating the two.

Ideally, we would only want to list the characteristics that are relevant for lab spikes or calibration checks.  Each characteristic should only be under one or the other (Lab Spike or Instrument Check).  So, I think we do need to use the Method column in the Parameter Mapping file to distinguish.
I noticed that qcMWRfre() lists three rows now:  Lab Spike, Instrument Check, and Spike/Check Accuracy.  I'm thinking that you don't need to do this, because Spike/Check Accuracy would just be the sum of the first two.

@ben-wetherill @carrjill I think I've got the all of the core functions done for the QC checks - accuracy, frequency, and completeness.  The latest addition is the accuracy checks.  So, when able, please review the vignette for the QC workflow: https://massbays-tech.github.io/MassWateR/ Please add your comments to this issue thread.
Once we're satisified with the functionality and we're sure it's doing what we intend, I can build out the functions for compiling the results in a report.

The vignette looks good.

Do you want to simplify the code for accchk to use "Instrument Checks" instead of "Instrument Checks (post sampling)"?
The % Acceptance (pass_thr) for tabMWRacc() should be equal to the % Completeness threshold in the DQOCompleteness file.  It's not exactly the same thing, but the value should be the same.  For example, if the completeness target for Nitrate is 80% of records not qualified, then the acceptance rate for Nitrate QC checks should be 80% of QC checks pass.  pass_thr should not default to 90%.
For the cases where accuracy is calculated based on log values (e.g. E.coli), I'm thinking we need to make this clear in the tabMWRacc(individual) output, to avoid confusion.  Can we write "logRPD" instead of "RPD" when the calculation is based on log?
Don't forget about using the Method column to distinguish between Lab Spikes and Instrument Checks in tabMWRfre() to filter the list of parameters in each.

This issue thread is starting to get very long and hard to keep track of what has been resolved and what hasn't.

All look good, except #4 using the Method column to distinguish between Lab Spikes and Instrument Checks.

#4 looks good now


[Table config] Add SQL query editor functions in SQL Expression box

Just killed myself trying to edit my SQL formula for a metric in the SQL expression box. Would be really helpful to have the syntax checking/linting/autocompletes of columns from the table - especially with end quotes and parentheses in this box.
Make sure these boxes are checked before submitting your issue - thank you!

[ ] I have checked the superset logs for python stacktraces and included it here as text if any
[ ] I have reproduced the issue with at least the latest released version of superset
[ ] I have checked the issue tracker for the same issue and I haven't found one similar

Superset version
Expected results
Actual results
Steps to reproduce

Not sure if this issue is still relevant as, in the sql editor, there are:

autocomplete on a lot of stuff
auto end quotes
auto closing parenthesis

and various others. Am I missing something ?

I think this refers to the SQL Expression box(es), either in the "table editor" or the "metric editor" in the explore view.

Not sure if the original issue was about the the boxes in the new edit datasource react UI popup or the legacy edit datasources jinja form.
The issue seems older than the creation of the react popup but i am unable to assess how frequently the legacy UI is still in use.

@yousoph related to SQL Expression Validator component project

Moved this to https://github.com/apache/superset/issues/12899


ERROR   Network request failed  Android

Description
Unable to make any fetch requests. Getting Network request failed Error on Android. Works fine on iOS. Tried various solutions from other threads and issues. Nothing helped. Any help appreciated!
React Native version:
Run react-native info in your terminal and copy the results here.
0.63.1
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

Make a remote https fetch request on emulator Android 10.0 Google API 29

Expected Results
Describe what you expected to happen.
Successful request with data.

fixed TypeError: Network request failed when upload file to http not https with Android debug builds


Feature/order blog posts

👷 Deploy Preview for cg-eleventy-blog processing.

Name
Link

🔨 Latest commit
e15423ea660c239c2d9b4796a4827395cdc46318

🔍 Latest deploy log
https://app.netlify.com/sites/cg-eleventy-blog/deploys/65d1042c9005af0008be808f