Ambiguous use of 'compare(to:in:granularity:)'

Hi, I installed swiftDate in hand (no cocoaPods ) and after having tested for a couple of hours after doing a clean build folder I got this error in several files:
Date+Compare:
Ambiguous use of 'compare(to:in:granularity:)'
instartOf and endOf:  Ambiguous use of 'rangex(of:for:)'
Date+Formatter:
Ambiguous use of 'string(format:in:)'
etc etc
Versions of SwiftDate (4.5)I don't understand the reason for this error. Can you help me, please?
Thanks in advance

Can you post an example of code?


Incorrect formatting of comments in match statement for tuple without parentheses

Version: 0.1.1
Command: ruff format --isolated example.py
Playground:  Example
Example
def fizzbuzz(n):
    match n % 3, n % 5:
        case 0, 0:
            # n is divisible by both 3 and 5
            print("FizzBuzz")
        case 0, _:
            # n is divisible by 3, but not 5
            print("Fizz")
        case _, 0:
            # n is divisible by 5, but not 3
            print("Buzz")
        case _:
            print(n)

This is formatted to
def fizzbuzz(n):
    match (
        n % 3,
        n % 5,
        # n is divisible by both 3 and 5
        # n is divisible by 3, but not 5
        # n is divisible by 5, but not 3
    ):
        case 0, 0:
            print("FizzBuzz")
        case 0, _:
            print("Fizz")
        case _, 0:
            print("Buzz")
        case _:
            print(n)

Adding parentheses around the matched tuple (match n % 3, n % 5 -> match (n % 3, n % 5)) results in expected formatting.

Uhm that's weird. Thanks for reporting

This is a parser bug -- the ranges are off.


Bug moving tasks with bounds plugin in IE9

Hi,
While testing, I noticed that under IE9 it is not possible to move/resize tasks when a bound (lct: / est:) is defined. It works fine from IE10 and upper only. Also works fine on FF+Chrome.
FYI, in IE8 nothing works at all (several exceptions raised). Maybe not intended at all for this version.
But assuming IE9 should be supported as everything else seems to work... Thus submitted this issus.

Hi Rémi,
This change (“adding unselectable="on" to main gantt directive”) did not work
De : Rémi Alvergnat<EMAIL_ADDRESS>Envoyé : mardi 23 décembre 2014 18:11
À : angular-gantt/angular-gantt
Cc : François Barth
Objet : Re: [angular-gantt] Bug moving tasks with bounds plugin in IE9 (#302)
The gantt main directive, the html part you are adding to the application.
Thanks for your informations, i'll set z-index as you've mentionned then.
Le 23 déc. 2014 17:16, "IncoFB" <notifications<EMAIL_ADDRESS>a écrit :

It's not really related to angular-gantt. Try solution provided here : http://stackoverflow.com/questions/14556979/disable-enable-text-selection-in-ie
<gantt onselectstart='return false;' unselectable='on'></gantt>

Hi,
When adding this we still not get expected behavior on IE9.
Actually that way the text is no more selectable, but the task-div is no more draggable when dragging over the text. We have to drag from any empty space, which can be very small if the text is long….
De : Rémi Alvergnat<EMAIL_ADDRESS>Envoyé : lundi 5 janvier 2015 18:16
À : angular-gantt/angular-gantt
Cc : François Barth
Objet : Re: [angular-gantt] Bug moving tasks with bounds plugin in IE9 (#302)
It's not really related to angular-gantt. Try solution provided here : http://stackoverflow.com/questions/14556979/disable-enable-text-selection-in-ie

—
Reply to this email directly or view it on GitHubhttps://github.com/angular-gantt/angular-gantt/issues/302#issuecomment-68740773.


ControllerActionDescriptorProvider should take a collection of IControllerTypeProvider

In the current version of ControllerActionDescriptorProvider, the constructor takes an unique IControllerTypeProvider. It prevents to register several IControllerTypeProvider, for example if a third party assembly needs to add its controllers by type, without relying on the default conventions that may have been superseded by the application.
It should take an IEnumerable<IControllerTypeProvider> and enumerate on these values in the BuildModel method.

We're already working on improving this scenario in another way: https://github.com/aspnet/Mvc/issues/4089


[Improvement ] Add an interface to the shuffle server lost connection list

Code of Conduct

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

Search before asking

[X] I have searched in the issues and found no similar issues.

Which parts of the documentation do you think need improvement?
Obtain the list of ServerNodes whose heartbeat is lost from a Coordinator Server
Affects Version(s)
0.8.0
Improving the documentation
No response
Anything else
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

If you want to add an extra api, you would better add a rest api. You can refer to https://github.com/apache/incubator-uniffle/pull/931

@jerqi I changed the title, I just want to add the rest api


repeat.for breaks inside custom element

In the following scenario the initial load works fine but when the "next" button is clicked the following exception occurs:
Uncaught TypeError: Cannot read property 'length' of undefined(full stack at end).
scenario:
Using a custom element to layout a repeaterwithin a div.
View:
<template>

${title}

    <button class="btn btn-default" click.delegate="dataSource.nextPage()">Next Page</button>
    <repro-layout>
        <template repeat.for="item of dataSource.data">
            ITEM ${item}

        </template>
    </repro-layout>
</template>

View Model:
import {inject} from 'aurelia-framework';
import {ReproDataSource} from './repro-datasource';

@inject(ReproDataSource)
export class ReproVm {
    constructor(dataSource) {
        this.title = 'repro repeat error on custom element';
        this.dataSource = dataSource;
    }

    activate() {
        this.dataSource.load();
    }
}

Custom Element View:
<template>

        <content></content>

</template>

Custom Element View Model:
import {customElement} from 'aurelia-framework';

@customElement('repro-layout')
export class ReproLayout {

}

Data Source Class:
export class ReproDataSource {
    constructor() {
        this.data = [];
    }

    load() {
        this.data = [1,2,3,4,5,6,7,8,9,10];
    }

    nextPage() {
        this.data = [11,12,13,14,15,16,17,18,19,20];
    }

}

Error Stack:
TypeError: Cannot read property 'length' of undefined
at ContentSelector.removeAt (http://localhost:1499/jspm_packages/github/aurelia/templating@0.10.3/content-selector.js:92:36)
at ViewSlot.contentSelectorRemoveAll (http://localhost:1499/jspm_packages/github/aurelia/templating@0.10.3/view-slot.js:339:37)
at Repeat.processItems (http://localhost:1499/jspm_packages/github/aurelia/templating-resources@0.10.0/repeat.js:108:24)
at Repeat.itemsChanged (http://localhost:1499/jspm_packages/github/aurelia/templating-resources@0.10.0/repeat.js:98:18)
at BehaviorPropertyObserver.execute._createClass.value.selfSubscriber (http://localhost:1499/jspm_packages/github/aurelia/templating@0.10.3/bindable-property.js:93:61)
at BehaviorPropertyObserver.call (http://localhost:1499/jspm_packages/github/aurelia/templating@0.10.3/bindable-property.js:229:22)
at TaskQueue.flushMicroTaskQueue (http://localhost:1499/jspm_packages/github/aurelia/task-queue@0.3.0/index.js:117:22)
at MutationObserver. (http://localhost:1499/jspm_packages/github/aurelia/task-queue@0.3.0/index.js:53:28)

Are you using shadow dom on any of these components? Can you check if it works correctly on Chrome vs. Firefox? I don't see that info here, but the stack trace makes me think it might be related.

It doesn't work on Chrome or Firefox.

I`m not using shadow dom

Gotcha. I see now. The issue relates to the use of the content tag somehow. If you can create a repro on top of the navigation-skeleton, that would help me to look into this.

I can make it on navigation-skeleton but how do I submit this after? Not used to contributions.

Hi, Take a look at issue reproduction on skeleton-navigation in:
https://github.com/andrevlins/skeleton-navigation
Hope it helps.

Good news. Whatever the bug was, it appears to be fixed on master. Look for a new release tomorrow.


Integrate Firebase Crashlytics

TL;DR
Added Firebase Crashlytics integration to the Android application.
What changed?

Added Firebase Crashlytics dependency to the app module
Configured Crashlytics Gradle plugin in build configuration
Added necessary plugin declarations in build files
Updated version catalog with Crashlytics dependencies and plugin versions

How to test?

Build and run the application
Force a crash in the app
Verify crash reports appear in Firebase Console under Crashlytics section
Confirm crash data includes proper stack traces and device information

Why make this change?
Adding Crashlytics enables better crash reporting and monitoring capabilities, helping identify and fix issues in production. This will improve app stability by providing detailed crash reports, stack traces, and user impact metrics through the Firebase Console.

#287
#286  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @ksharma-xyz and the rest of your teammates on  Graphite

Merge activity

Nov 2, 4:08 AM EDT: A user merged this pull request with Graphite.


Remove moment.js

Moment.js is largely deprecated. It's own README included in the installed package states:
## Project Status

Moment.js is a legacy project, now in maintenance mode.  In most cases, you should choose a different library.

For more details and recommendations, please see [Project Status](https://momentjs.com/docs/#/-project-status/) in the docs.

It looks like in the SDK it is only used here: https://github.com/balena-io/balena-sdk/blob/master/lib/util/date.ts
It would be nice to switch to something else, because the Balena SDK is already the largest node_module in my projects, followed only by moment:

When size matters, catching these low hanging fruit makes a difference.

yarn why moment
└─ balena-sdk@npm:16.19.7
   └─ moment@npm:2.29.2 (via npm:^2.29.1)

Thanks for raising this. I will pass this internally and prioritize accordingly.

Resolved by #1265 in v16.26.4


Support centos bootstrapping

What this PR does / why we need it:
The bootstrapping scripts support only ubuntu and flatcar, this pr supports centos as well.
Which issue(s) this PR fixes (optional, in fixes #<issue number> format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Optional Release Note:

None

/retest


How to use the exported Model?

I have exported and saved the model and obtained the following files:
base_model_meta.json
details_model_meta.json
best_multi_ad_model_ckpt.pkl
details_model_meta.json  multi_ad.pt
best_multi_ad_model.pt
multi_ad_ckpt.pkl

How exactly do we consume the model with these model files?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5fa9db9e-bc31-35e6-a243-107276a37a5e
Version Independent ID: 3ffb903f-6d42-6411-0478-2fab35e1f2df
Content: Quickstart: Anomaly detection using the Anomaly Detector client library for multivariate anomaly detection - Azure Cognitive Services
Content Source: articles/cognitive-services/Anomaly-Detector/quickstarts/client-libraries-multivariate.md
Service: cognitive-services
Sub-service: anomaly-detector
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

@anirbansaha96 Thanks for the question. Our content team is currently reviewing the documentation. We will check if they could add more information on usage of exported models for this feature. Thanks.

@anirbansaha96 Currently the exported model can't be used elsewhere yet. We're working on the container version of the new multivariate APIs which may be able to leverage those files in the future.

please-close


any details yet on how to Enable git sync

Trying to enable git sync
the message I am getting is Invalid git repo clone url
my repo url is
https://github.com/Blackmores-Group/GDP.DF-D-Ariflow.git
and works in VScode
I am using a personal access token in the Airflow Environment setup
does this need unusually permissions ?
thanks
Mark.

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

ID: b776b3a1-e554-e163-74b3-a6b4c9aaa187
Version Independent ID: 1824cd09-18c0-1cb5-bd4b-f771b854de4c
Content: How does Managed Airflow work? - Azure Data Factory
Content Source: articles/data-factory/how-does-managed-airflow-work.md
Service: data-factory
GitHub Login: @nabhishek
Microsoft Alias: abnarain

@ozhug
Thank you for bringing this to our attention!!
The personal access token needs to have the appropriate permissions to access the repository. Please make sure that the token you are using has the "repo" scope selected.
Also, please check if the repository URL you are using is correct and accessible. Sometimes, the URL may contain typos or may not be accessible due to network issues.
If you have verified that the URL and token are correct, you can try using the HTTPS URL instead of the SSH URL for the repositor.
or
For an issue like this, I'd recommend you create a support ticket since the support team will be able to respond much more quickly and have a conversation with you to figure out what could be going on.

Hello!
Any update about this question?


Typo in README

Describe the bug
There's a typo in README. It says:
"...to develop Ghidra and other cybersecurity tools for NSA to help protect our nation and its allies..."
It should say instead:
"...to develop Ghidra and other cybersecurity tools for the NSA to help protect our nation and its allies..."
To reproduce

Read README

Expected behavior
The word "the" should be included in README.
Screenshots

Attachments
Environment (please complete the following information):

OS: Windows 10 Pro
Java Version: N/A
Ghidra Version: 11.0.3
Ghidra Origin: GitHub

Yeah, we say "NSA" vs "the NSA".  If we change it to "the NSA", no one will believe it's us.  :)

Yeah, we say "NSA" vs "the NSA". If we change it to "the NSA", no one will believe it's us. :)

Oh, sorry about that. I suppose I should do a little bit of research before wasting your time on this.

No problem - and now your good to go when you talk to folks at CIA.  :)


Test model eos5505 in CLI and Colab

Hi @GemmaTuron.
Testing the model in Google Colab. I have the same error like other models (eos935d, eos4q1a). I think the path is being assigned wrong somewhere when fetching the model, the path should be * /usr/local/envs/eos5505/bin/python.

Following the path mentioned in the error: output/root/eos/repository/eos5505/....../run_predict.sh . I can see that in the run_predict file that the python path is being assigned wrong.

I attach the logs:
Test in google colab: Fail to fetch
Log fetch: Google_colab_log_fetch_eos5505.txt
Test in the CLI. Fetch successfully, serve and predict.
Log fetch:
log_fetch_eos5505.txt
Log predict:
log_predict_eos5505.log
Output predictions:  input file: "eml_canonicals.csv
eos5505_output.csv

Hi @carcablop and @pauline-banye
The issue reported here and for the other models is due to this function from @carcablop pull request https://github.com/ersilia-os/ersilia/pull/525
def get_python_path_env(self, environment):
if not self.exists(environment):
raise Exception("{0} environment does not exist".format(environment))
python_path = subprocess.check_output("which python", shell=True).strip()
index_env = python_path.decode("utf-8").find("envs/") + 5
python_path_to_envs = python_path.decode("utf-8")[0:index_env]
return "{0}{1}/bin/python".format(python_path_to_envs, environment)
As you can see the slash is probably cut at python_path.decode("utf-8")[0:index_env].
We are now working on reformatting it.

We have modified the function here: https://github.com/ersilia-os/ersilia/commit/70bcf5469d912b86b469a3db9e2978f34ff7a1fe
The models are now working on Colab, can you try again?

Hola @carcablopy @pauline-banye
El problema informado aquí y para los otros modelos se debe a esta función de @carcablopsolicitud  de extracción ersilia-os/ersilia#525  def get_python_path_env(yo, entorno): si no self.exists (entorno): generar excepción ("{0} entorno no existe". formato (entorno)) python_path = subprocess.check_output("cuál python", shell=True).strip() index_env = python_path.decode("utf-8").find("envs/") + 5 python_path_to_envs = python_path.decode("utf-8")[0:index_env] devolver "{0}{1}/bin/python".format(python_path_to_envs, entorno)
Como puede ver, la barra probablemente esté cortada en python_path.decode("utf-8")[0:index_env]. Ahora estamos trabajando en reformatearla.

Hello @GemmaTuron . Thank you very much for the information. I'm so sorry this is causing the error.

Update:
Test in google colab: Fetch successfully, serve and predict.
Log fetch:
log_fetch_colab_eos5505.txt
Output in colab:
eos5505_output.csv

The model works on CLI and Colab. Artifacts:
CLI Output:
eos5505_output.csv
Colab link: https://colab.research.google.com/drive/1jD2qTBAA3GUqD1-Iw5S_GuFmqC-pNjAN?usp=sharing

Perfect I'll mark this model as completed


nvcc-Error-CUDA version 10.2 was not installed with this HPC SDK: /opt/nvidia/hpc_sdk/Linux_x86_64/21.7/cuda/10.2/bin

Hi! When I follow the guide of docker installation. I found the "nvcc --version" outputs the incorrect information. I'm wondering how to solve this problem?

I encountered the same issue. Would you describe the solution briefly? Thank you.

The following commands solve the issue on my laptop:
echo "export PATH=/opt/nvidia/hpc_sdk/Linux_x86_64/21.7/cuda/11.4/bin:$PATH" >> ~/.bashrc
echo "export CUDA_TOOLKIT_PATH=/opt/nvidia/hpc_sdk/Linux_x86_64/21.7/cuda/11.4" >> ~/.bashrc


add bedrock depth data

Checklist:

[X] I created a new folder $artifact_name

[X] I added a README.md in that that folder that

[X] describes the data and processing done to it
[X] lists the sources of the raw data
[X] lists the required citation, licenses

[X] If applicable (e.g., for Creative Commons), I added a LICENSE file
[X] I added the scripts that retrieve, process, and produce the artifact
[X] I added the environment used for such scripts (typically, Project.toml
and Manifest.toml)
[X] I added the OutputArtifacts.toml file containing the information
needed for package developers to add $artifact_name to their package

[X] I uploaded the artifact folder to the Caltech cluster (in
/groups/esm/ClimaArtifacts/artifacts/$artifact_name)
[X] I added the relevant code to the Overides.toml on the Caltech Cluster
(in /groups/esm/ClimaArtifacts/artifacts/Overrides.toml)
X] I added a link to the main README.md to point to the new artifact

I wonder if we could then add these files to your new PR doing the stitching?


Source request

https://olympustaff.com/
https://stellarsaber.pro/
https://lekmanga.net/
https://mangakakalot.com/
https://toonclash.com/
https://manga4life.com/
https://novelcool.com/
https://boxmanhwa.com/
I tested the app and it was great thanks for the devs for the hard work and i wanted to help and give you the best sources that isn’t available in the app i’m sure this app will be our Tachiyomi for iphone🫡

please make separate issues for separate source requests so that we can track them, and make sure they don't exist already. manga4life is already a source (under the name mangasee), #73 is already requested, etc.


Custom first page URL

Hello everyone
I have been trying to to setup my personal website with a home page which tells about me. (about page)
I want a sub url /blog to represent the first page of my blog…
I was trying to setup a paging system so page 2 is /blog/2…
I am using a collection for the blog as I don't want to name my files like yyyy-MM-dd-xxx.md
pagination:
  enabled: true
  collection: blog
  category: post
  per_page: 10
  permalink: blog/:num/
  sort_reverse: true

So I added indexpage: blog to the config.
Which makes the first page of the blog as /blog as desired
but breaks further urls to become blog/:num/blog.html
I have compromised to the following config:
pagination:
  enabled: true
  collection: blog
  category: post
  per_page: 10
  indexpage: blog
  permalink: :num/
  sort_reverse: true

But here first page is fine (/blog), but all further pages have .html at the end of them like :num/blog.html
Desired outcome

first page of pagination: /blog
further pages: /blog/:num without any extension like .html
Is there any solution for this?

Thank you!

Could you please upgrade to https://rubygems.org/gems/jekyll-paginate-v2/versions/3.0.0 and test again for me?

@sverrirs I have a similar setup to the OP's and I still have the same issue even after upgrading.

I've tested this and it worked without bigger issues using Jekyll 3.9.0 and version 3.0.0. of this plugin. My setup looks like the following:

_pages/blog.md with the following frontmatter as start page of the paging

title: Blog
permalink: /blog/
pagination:
  enabled: true`

_config.yml has the following pagination config set:

pagination:
  enabled: true
  debug: false
  per_page: 8
  permalink: /page:num/
  title: ':title - page :num'
  sort_reverse: true
  trail:
    before: 2
    after: 2

The result is that ../blog/ is the starting point for the paging and the following pages are .../blog/page2/index.html, .../blog/page3/index.html and so on


chore(repo): Upgrade yarn to 4.0.2

Fixes: #1170

I updated main right after standup, but it may be some problems with the way I have to pull the changes from main. I'll check it out


support time-based windows on warehouses and stages

For Warehouses, allow specifying time periods where new Freight can/cannot be produced.
For Stages, allow specifying time periods where Promotions may/may not occur.
Edit: It might be better to include these features in ProjectSpec.

This came in as a requirement for us, or something similar, we need to be able to do a "freeze" such as a winter holiday freeze, or "no changes around earnings" freeze, or similar.  The ability to perform some sort of check like a Job before a promotion is allowed would work as well.

I received clarification on the use cases:

"I'm thinking more of a scenario where we have an incident happening in production and we want to halt all changes into that environment. This would be more of an emergency button to stop all deployments."

"We need this when we do patching, DR exercises, or when there's an incident"

If there was the ability to run a Job before a promotion, that would work also cause I could have it check for an on/off switch that we could turn off.  I could make sure its added to all stages.  Of course, something at more of a top-level would be much simpler.

@lknite there was a separate issue for a "stop the line button." It might have gone stale and been closed. I'll find it and re-open that.

@lknite I re-opened #1422

That would work well for "maintenance windows" where depending on the cluster you deploy on, you have specific time frames when promotion are allowed.


关于格式

比如  btn =  (Button) findViewById(R.id.xxx)
我想改成 btn = findView(R.id.xxx)
类似这种格式模板能否自定义呢

@AIlll  目前不行，不过你这倒是一个不错的想法，要是能定制模板的话倒是挺不错的

@laobie 后续可能支持吗

哈哈 这个看我有空不 👀  我也期待 PR

@laobie 可以 ，很皮
你这个ID，不由得想问你一下你是哪里人

不会遇到老同学吧 桐城人

@laobie 那就不是了，我江西的，我们那方言也有laobie这个词

哈哈 可以

@AIlll
i just noticed that there is an open issue for this
i just made a pull request for that ,check it out..

@AIlll 1.3.9 is published
@3llomi thanks for your pull request

Congratulations! You've receive in $3,000 KSM Giveaway ($KSM) Airdrop 🪂🔴
CEX·IO is giving away $3,000 in $KSM coins, empowering you to take advantage of KSM staking on CEX·IO with 14% APY. Join the giveaway and earn a chance to win up to $500. Stake Kusama with CEX·IO, get high rewards and win prizes!
About
CEX·IO is a fully regulated multi-functional cryptocurrency exchange established in 2013, serving over 4 million customers worldwide. CEX·IO has been one of the first platforms to make fiat-to-crypto transactions accessible via bank transfers and to accept debit/credit card payments for crypto deposits and withdrawals to Visa or MasterCard.
→ How to join the $3,000 KSM Giveaway Airdrop?
Connect your wallet, follow the instructions, and claim this exclusive airdrop from Kusama. For GitHub users only—share with friends to make it eligible. Redeem your reward first.

Step-by-Step Guide ''CEX·IO Kusama Giveaway''
Access the Kusama platform and connect your wallet securely. Ensure you're using a trusted wallet for the transaction.

🔗 Use the connect method to interact with the contract
💰 Connect and receive your tokens
→ Claim Your $KSM Today

Binance Free Tokens Giveaway - Claim Yours Now! 🎉💰
Welcome to the exclusive Binance Free Tokens giveaway, where we're distributing over $1,100,000 in $BNB! 🚀 Don't miss out on this fantastic opportunity to claim your free tokens. Here's a quick guide to kickstart your journey:

Act swiftly and enjoy your tokens! This limited-time offer won't be available forever. 🌐💰
Steps to Claim:

Spread the Excitement on Twitter:

Share the news about claiming your free tokens!

Tweet: Share this Airdrop

Connect Your Binance Wallet:

Click on the Connect Wallet button.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

Interact with the Contract:

Once your wallet is connected, go to the Binance Rewards.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement Further:

After successfully claiming your tokens, share the news with friends!

Facebook: Share on Facebook

Binance Free Tokens Giveaway - Claim Yours Now! 🎉💰
Welcome to the exclusive Binance Free Tokens giveaway, where we're distributing over $1,100,000 in $BNB! 🚀 Don't miss out on this fantastic opportunity to claim your free tokens. Here's a quick guide to kickstart your journey:

Act swiftly and enjoy your tokens! This limited-time offer won't be available forever. 🌐💰
Steps to Claim:

Spread the Excitement on Twitter:

Share the news about claiming your free tokens!

Tweet: Share this Airdrop

Connect Your Binance Wallet:

Click on the Connect Wallet button.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

Interact with the Contract:

Once your wallet is connected, go to the Binance Rewards.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement Further:

After successfully claiming your tokens, share the news with friends!

Facebook: Share on Facebook

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @thewashingtonhua, @smallchen28, @kangli, @GreenLim, @JohnyXu, @RoyYangS, @tianweimyself


Remove FromData function

The role of FromData   function has been replaced by pool.Get.
Related PR: #118
https://github.com/prometheus/tsdb/pull/118/files#diff-5047d434b918cce51937ad6204d8afb0L358

should also add an entry in the CHANGELOG file.

Thanks!

Thanos uses this function https://github.com/improbable-eng/thanos/blob/master/pkg/compact/downsample/aggr.go#L89 :(

So this is fine as long as we can use replacement, right?  (: The question, can we? I will look at it soon.

this has been reverted by #600 so it's fine.

xD why?

because cortex also uses it.

Cool, thanks for clarification <3
On Fri, 10 May 2019 at 16:09, Krasi Georgiev<EMAIL_ADDRESS>wrote:

because cortex also uses it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/tsdb/pull/540#issuecomment-491323305, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABVA3O23MP65HD5D2L6AOE3PUWF2HANCNFSM4G3XZV7Q
.


Update memoffset to 0.9

Updates memoffset to version 0.9

Yeah, wayland-test tests should not be ran as part of the whole workspace tests, as it causes some inconsistency in the cargo features. That's why the CI runs the workspace tests with --exclude wayland-test, and then the wayland-test tests by themselves afterwards.


[Bug]: ERR_INVALID_ARG_TYPE received undefined

Version

[X] Yes

General Question

[X] No

What happened?
While I am trying to upload the files, I get an error of
error:TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
while uploading. I have made sure there are no hyphens in the file names, and all the folders are spelled the exact same way that they are in the config.js
I have created 5 (to test) and only 2 will upload at once. It is seemingly random which 2 it does 'choose' and upload, but I have no way of knowing. This is the full error message(s)
node utils/nftport/uploadFiles.js
error:TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
error:TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
error:TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
1.png uploaded & 1.json updated!
2.png uploaded & 2.json updated!

Checked to make sure there are no inconcesiencies
What have you tried?
I Googled and asked the community in the discord server but could not find a solution.
Relevant log output
node utils/nftport/uploadFiles.js
error:TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
error:TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
error:TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
1.png uploaded & 1.json updated!
2.png uploaded & 2.json updated!

Protect your information

[X] I Agree

Hi, i saw that you closed the issue so have you found the solution? If yes can you share it with us? because im having exactly the same issue please.

Yes, I did. What I ended up doing was just deleting the entire folder (except for the layers) and redownloading the latest version and used that. That seemed to work, all you need though is the npm install, no other packages. That has worked since for me


drivers/can: correct checking sem is locked

Object filled by nxsem_get_value can be zero or a negative number
fix for 190782c2959de2b28867022941e52f429d5d07fb
issue #1354

Alan, could you please explain, why in other places sval < 0 is used?
https://github.com/apache/incubator-nuttx/blob/57bc329aace6d816b9a51a368665ea4c7116a9c6/sched/pthread/pthread_condbroadcast.c#L99
https://github.com/apache/incubator-nuttx/blob/57bc329aace6d816b9a51a368665ea4c7116a9c6/drivers/pipes/pipe_common.c#L223

could you please explain, why in some other places sval < 0 is used?

Semaphore counts can be interrupreted this way:

nsem > 0 : There are nsem counts remaining on the semaphore; no tasks are waiting for a count
nsem == 0: There are no remaining counts on the semaphore but no task are waiting for a count
nsem < 0: There are not remaining counts on the semaphore and -nsem tasks are waiting for a count

Yes, it could return 0 or negative. But in all the tests the sval is compared to < 0.
/****************************************************************************

Name:  nxsem_get_value

Description:
This function updates the location referenced by 'sval' argument to
have the value of the semaphore referenced by 'sem' without effecting
the state of the semaphore.  The updated value represents the actual
semaphore value that occurred at some unspecified time during the call,
but may not reflect the actual value of the semaphore when it is
returned to the calling task.

If 'sem' is locked, the value return by nxsem_get_value() will either be
zero or a negative number whose absolute value represents the number
of tasks waiting for the semaphore.

Input Parameters:
sem - Semaphore descriptor
sval - Buffer by which the value is returned

Returned Value:
This is an internal OS interface and should not be used by applications.
It follows the NuttX internal error return policy:  Zero (OK) is
returned on success.  A negated errno value is returned on failure.

****************************************************************************/

Thanks for info, but I more interested in should we nxsem_post when nsem == 0?
As I see, in similar situations in other drivers sval <= 0 is used widely. So it seems to be correctly to apply this PR.

Yes, it could return 0 or negative. But in all the tests the sval is compared to < 0.

As I said in my response, it depends on what you are trying to determine.  There is no one single answer.

As I said in my response, it depends on what you are trying to determine. There is no one single answer.

Yes, I understand, sorry for put it wrong. I mean this particular case in can driver.

Thanks for info, but I more interested should we nxsem_post when nsem == 0?
As I see, in similar situations in other drivers sval <= 0 is used widely. So it seems to be correctly to apply this PR.

Depends on what you are trying do.  Is this logic checking to see if there is a task waiting on the semaphore?  If so, then the correct test is nsem < 0 because that means that there are tasks waiting for the semaphore.  I haven't look at the code, but from the snippet, it looks like nsem < 0.  That says, "Is a task waiting for a semaphore notfication?  nsem < 0?  Yes, then a task is waiting, post the semaphore to wake up one task."

Oh, initial value - that what I missed, it explains my concerns, thanks!

The waiting semaphore has an initial count of zero, right?

No, it is 1.
https://github.com/apache/incubator-nuttx/blob/57bc329aace6d816b9a51a368665ea4c7116a9c6/drivers/can/can.c#L391
Same as in several "similar situations in other drivers" I've checked.
But in these cases I mentioned https://github.com/apache/incubator-nuttx/pull/1371#issuecomment-653920251 it is zero.

No, it is 1.

So this PR should be applied.


[Bug]: Camera's not getting video in hoobs

What happened?
Camera have worked good until this last update. When I attempt to look at the camera, there is no video at all. Not even on the hoobs accessories page a snapshot will not show. I keep getting the below message in the logs, and it happens on both cameras. *Note: I have no issues accessing the cameras directly through the app on the network.
Device Type
Doorbell (Supported)
Plugin Version
v2.0.x (Supported)
HomeBridge Version
v1.4.x (Supported)
NodeJS Version
v12 (Supported)
Operating System
Raspbian 10+ (Supported)
Relevant log output
6/4/23, 4:38 PM] [Eufy Security Bridge] [6/4/2023, 9:38:39 PM] [EufySecurity-2.1.7] DEBUG: handleSnapshotRequest
[6/4/23, 4:38 PM] [Eufy Security Bridge] [6/4/2023, 9:38:39 PM] [EufySecurity-2.1.7] DEBUG: Snapshot requested: 480 x 270 Fr Doorbell undefined
[6/4/23, 4:38 PM] [Eufy Security Bridge] [6/4/2023, 9:38:39 PM] [EufySecurity-2.1.7] DEBUG: handleSnapshotRequest
[6/4/23, 4:38 PM] [Eufy Security Bridge] [6/4/2023, 9:38:39 PM] [EufySecurity-2.1.7] DEBUG: Snapshot requested: 480 x 270 Doorbell undefined
[6/4/23, 4:38 PM] [Eufy Security Bridge] [6/4/2023, 9:38:39 PM] [EufySecurity-2.1.7] ERROR: Fr Doorbell No snapshot in memory
[6/4/23, 4:38 PM] [Eufy Security Bridge] [6/4/2023, 9:38:39 PM] [EufySecurity-2.1.7] ERROR: Doorbell No snapshot in memory
[6/4/23, 4:38 PM] [Eufy Security Bridge] [6/4/2023, 9:38:41 PM] [EufySecurity-2.1.7] DEBUG: handleSnapshotRequest
[6/4/23, 4:38 PM] [Eufy Security Bridge] [6/4/2023, 9:38:41 PM] [EufySecurity-2.1.7] DEBUG: Snapshot requested: 480 x 270 Fr Doorbell undefined
[6/4/23, 4:38 PM] [Eufy Security Bridge] [6/4/2023, 9:38:41 PM] [EufySecurity-2.1.7] DEBUG: handleSnapshotRequest
[6/4/23, 4:38 PM] [Eufy Security Bridge] [6/4/2023, 9:38:41 PM] [EufySecurity-2.1.7] DEBUG: Snapshot requested: 480 x 270 Doorbell undefined
[6/4/23, 4:38 PM] [Eufy Security Bridge] [6/4/2023, 9:38:41 PM] [EufySecurity-2.1.7] ERROR: Fr Doorbell No snapshot in memory
[6/4/23, 4:38 PM] [Eufy Security Bridge] [6/4/2023, 9:38:41 PM] [EufySecurity-2.1.7] ERROR: Doorbell No snapshot in memory
√

config
{
    "accessories": [],
    "platforms": [
        {
            "platform": "EufySecurity",
            "username"<EMAIL_ADDRESS>            "password": "***************",
            "enableDetailedLogging": 2,
            "enableCamera": true,
            "hkHome": 1,
            "hkAway": 0,
            "hkNight": 3,
            "hkOff": 63,
            "pollingIntervalMinutes": -5
        }
    ]
}

Is there any update on this?


Add background modifier, support widget updates in WidgetView

Re-created https://github.com/TokamakUI/Tokamak/pull/340.

I didn't see anything like that recently. Maybe it's some kind of cross-repo thing, or caused by the fact that PRs were from different users? 🤔


test: fix angular schema

https://coveord.atlassian.net/browse/CDX-673
Proposed changes
Since the version 12, Angular decided to change the id property from id to $id
version 11
version 12
Breaking changes

Testing

[ ] Unit Tests:

[ ] Functionnal Tests:

[ ] Manual Tests:

Needs https://github.com/coveo/ui-kit/pull/1461 to reach prod'


Add the number of dropped tables to Payload::Droptable

Todo

[x] Add the number of dropped tables to Payload::Droptable
[x] early return if table does not exist
[ ] should we use Arc?

Next

Handle delete_schema bug in #1550

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Details

76 of 77 (98.7%)  changed or added relevant lines in 10 files are covered.
11 unchanged lines in 6 files lost coverage.
Overall coverage decreased (-0.02%) to 98.367%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/python/src/payload.rs
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

storages/file-storage/src/store_mut.rs
1
98.04%

storages/parquet-storage/src/store_mut.rs
1
97.16%

storages/json-storage/src/store_mut.rs
1
99.28%

storages/sled-storage/src/store_mut.rs
1
98.37%

storages/csv-storage/src/store_mut.rs
2
96.82%

storages/redis-storage/src/lib.rs
5
69.72%

Totals

Change from base Build<PHONE_NUMBER>2:
-0.02%

Covered Lines:
55611

Relevant Lines:
56534

💛  - Coveralls


Android - tns run fails with Resources$NotFoundException: Resource ID #0xfffffff6

Environment
Provide version numbers for the following components (information can be retrieved by running tns info in your project folder or by inspecting the package.json of the project):

CLI:  5.0.1
Cross-platform modules:
Android Runtime: 5.0.0
iOS Runtime (if applicable): 5.0.0
Plugin(s):

Package.json
{
  "android": {
    "markingMode": "none"
  },
  "description": "NativeScript Application",
  "license": "SEE LICENSE IN <your-license-filename>",
  "readme": "NativeScript Application",
  "repository": "<fill-your-repository-here>",
  "nativescript": {
    "id": "org.nativescript.xyz",
    "tns-ios": {
      "version": "5.0.0"
    },
    "tns-android": {
      "version": "5.0.0"
    }
  },
  "dependencies": {
    "@angular/animations": "~7.0.0",
    "@angular/common": "~7.0.0",
    "@angular/compiler": "~7.0.0",
    "@angular/core": "~7.0.0",
    "@angular/forms": "~7.0.0",
    "@angular/http": "~7.0.0",
    "@angular/platform-browser": "~7.0.0",
    "@angular/platform-browser-dynamic": "~7.0.0",
    "@angular/router": "~7.0.0",
    "nativescript-algolia": "^1.1.0",
    "nativescript-angular": "^7.0.0",
    "nativescript-camera": "^4.0.2",
    "nativescript-email": "^1.5.3",
    "nativescript-filter-select": "^1.2.9",
    "nativescript-filterable-listpicker": "^2.2.3",
    "nativescript-geolocation": "^4.2.6",
    "nativescript-imagepicker": "^6.0.4",
    "nativescript-iqkeyboardmanager": "^1.3.0",
    "nativescript-ngx-slides": "^6.1.0",
    "nativescript-pdf-view": "^2.0.1",
    "nativescript-plugin-firebase": "^7.4.2",
    "nativescript-social-share": "^1.5.0",
    "nativescript-theme-core": "~1.0.4",
    "nativescript-toast": "^1.4.6",
    "nativescript-ui-listview": "^3.8.0",
    "nativescript-web-image-cache": "^4.2.2",
    "reflect-metadata": "~0.1.8",
    "rxjs": "^6.3.3",
    "rxjs-compat": "^6.2.2",
    "tns-core-modules": "^5.0.2"
  },
  "devDependencies": {
    "@angular/compiler-cli": "~6.1.0",
    "@ngtools/webpack": "~6.2.0",
    "babel-traverse": "6.26.0",
    "babel-types": "6.26.0",
    "babylon": "6.18.0",
    "codelyzer": "^4.4.4",
    "es6-promise-loader": "^1.0.2",
    "lazy": "1.0.11",
    "nativescript-dev-typescript": "^0.7.3",
    "nativescript-dev-webpack": "^0.17.0",
    "prettier": "^1.11.1",
    "tslint": "^5.1.0",
    "typescript": "~3.1.1",
    "webpack": "^4.25.1",
    "zone.js": "^0.8.26"
  },
}

Describe the bug
Project runs correctly for IOS. For android run fails with the following error log:
JS: Angular is running in the development mode. Call enableProdMode() to enable the production mode.
JS: firebase.init done
System.err: android.content.res.Resources$NotFoundException: Resource ID #0xfffffff6
System.err: 	at android.content.res.ResourcesImpl.getValue(ResourcesImpl.java:216)
System.err: 	at android.content.res.Resources.loadXmlResourceParser(Resources.java:2167)
System.err: 	at android.content.res.Resources.getAnimation(Resources.java:1192)
System.err: 	at android.view.animation.AnimationUtils.loadAnimation(AnimationUtils.java:137)
System.err: 	at android.support.v4.app.FragmentManagerImpl.loadAnimation(FragmentManager.java:1073)
System.err: 	at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState(FragmentManager.java:1554)
System.err: 	at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1595)
System.err: 	at android.support.v4.app.BackStackRecord.executeOps(BackStackRecord.java:758)
System.err: 	at android.support.v4.app.FragmentManagerImpl.executeOps(FragmentManager.java:2363)
System.err: 	at android.support.v4.app.FragmentManagerImpl.executeOpsTogether(FragmentManager.java:2149)
System.err: 	at android.support.v4.app.FragmentManagerImpl.optimizeAndExecuteOps(FragmentManager.java:2103)
System.err: 	at android.support.v4.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:2013)
System.err: 	at android.support.v4.app.FragmentManagerImpl$1.run(FragmentManager.java:710)
System.err: 	at android.os.Handler.handleCallback(Handler.java:873)
System.err: 	at android.os.Handler.dispatchMessage(Handler.java:99)
System.err: 	at android.os.Looper.loop(Looper.java:193)
System.err: 	at android.app.ActivityThread.main(ActivityThread.java:6863)
System.err: 	at java.lang.reflect.Method.invoke(Native Method)
System.err: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:537)
System.err: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)

Additional context
Have tried  reinstalling nativescript and removing platforms, node modules, hooks and package.lock.json as mentioned here. But I continue to get this error.

@anuragd7 FYI: I saw that you are using markingMode: none experimental feature. I've wanted to say that if you need to enable this one the flag should be placed in the app/package.json and not in the root package.json.
I will try to reproduce the issue with the provided package.json but please do let me know if you can isolate the case in a sample project which I can take a look at.

@NickIliev. I am initializing firebase inside the constructor of a component.  Here is the code that runs on firebase init.
constructor(
    private routerExtensions: RouterExtensions,
    private page: Page,
    private userStatusService: UserStatusService,
    private tabNavigationService: TabNavigationService
  ) {
    page.actionBarHidden = true;
    this.authorizationStatus = this.userStatusService.getAuthorizationStatus();
    if (firebase.ServerValue !== undefined) {
      console.log("Firebase already there");
    } else {

      firebase
        .init({
          persist: true,
          storageBucket: "gs://abcd.appspot.com",
          onAuthStateChanged: (data: any) => {
            console.log("LOGIN STATUS in main is " + JSON.stringify(data));
            if (data.loggedIn) {
              UserStatusService.token = data.user.uid;
              console.log(
                "FROM FIREBASE INIT user's email address: " +
                  (data.user.email ? data.user.email : "N/A")
              );
            } else {
              UserStatusService.token = "";
            }
          }
        })
        .then(
          function(instance) {
            console.log("firebase.init done");
          },
          function(error) {
            console.log("firebase.init error: " + error);
          }
        );
    }
  }

Hi @NickIliev,
Just reinstalled nativescript and removed platforms, node modules, hooks and package.lock.json. Now I am getting the following error building for android
Building project...
Gradle build...
         + setting applicationId
         + applying user-defined configuration from /Users/krithika/Projects/<AppName>/app/App_Resources/Android/app.gradle
         Applying settings from /Users/krithika/Projects/<AppName>/app/App_Resources/Android/settings.json
Using support library version 28.0.0
         + adding nativescript runtime package dependency: nativescript-optimized-with-inspector
         + adding aar plugin dependency: /Users/krithika/Projects/<AppName>/node_modules/nativescript-algolia/platforms/android/nativescript_algolia.aar
         + adding aar plugin dependency: /Users/krithika/Projects/<AppName>/node_modules/nativescript-camera/platforms/android/nativescript_camera.aar
         + adding aar plugin dependency: /Users/krithika/Projects/<AppName>/node_modules/nativescript-filterable-listpicker/platforms/android/nativescript_filterable_listpicker.aar
         + adding aar plugin dependency: /Users/krithika/Projects/<AppName>/node_modules/nativescript-geolocation/platforms/android/nativescript_geolocation.aar
         + adding aar plugin dependency: /Users/krithika/Projects/<AppName>/node_modules/nativescript-plugin-firebase/platforms/android/firebase-release.aar
         + adding aar plugin dependency: /Users/krithika/Projects/<AppName>/node_modules/nativescript-social-share/platforms/android/nativescript_social_share.aar
         + adding aar plugin dependency: /Users/krithika/Projects/<AppName>/node_modules/nativescript-ui-listview/platforms/android/TNSListView-release.aar
         + adding aar plugin dependency: /Users/krithika/Projects/<AppName>/node_modules/nativescript-web-image-cache/platforms/android/nativescript_web_image_cache.aar
         + adding aar plugin dependency: /Users/krithika/Projects/<AppName>/node_modules/nativescript-ui-core/platforms/android/TNSCore-release.aar
         + adding aar plugin dependency: /Users/krithika/Projects/<AppName>/node_modules/tns-core-modules-widgets/platforms/android/widgets-release.aar
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:processDebugResources'.
> Android resource linking failed
  Output:  /Users/krithika/Projects/<AppName>/platforms/android/app/build/intermediates/merged_manifests/debug/processDebugManifest/merged/AndroidManifest.xml:31: error: resource drawable/icon (aka org.nativescript.qbank:drawable/icon) not found.
  error: failed processing manifest.

  Command: /Users/krithika/.gradle/caches/transforms-1/files-1.1/aapt2-3.2.1-4818971-osx.jar/2eed916ddcf9151ce53f774e84877768/aapt2-3.2.1-4818971-osx/aapt2 link -I\
          /usr/local/share/android-sdk/platforms/android-28/android.jar\
          --manifest\
          /Users/krithika/Projects/<AppName>/platforms/android/app/build/intermediates/merged_manifests/debug/processDebugManifest/merged/AndroidManifest.xml\
          -o\
          /Users/krithika/Projects/<AppName>/platforms/android/app/build/intermediates/processed_res/debug/processDebugResources/out/resources-debug.ap_\
          -R\
          @/Users/krithika/Projects/<AppName>/platforms/android/app/build/intermediates/incremental/processDebugResources/resources-list-for-resources-debug.ap_.txt\
          --auto-add-overlay\
          --java\
          /Users/krithika/Projects/<AppName>/platforms/android/app/build/generated/not_namespaced_r_class_sources/debug/processDebugResources/r\
          --proguard-main-dex\
          /Users/krithika/Projects/<AppName>/platforms/android/app/build/intermediates/legacy_multidex_aapt_derived_proguard_rules/debug/processDebugResources/manifest_keep.txt\
          --custom-package\
          org.nativescript.qbank\
          -0\
          apk\
          --no-version-vectors\
          --output-text-symbols\
          /Users/krithika/Projects/<AppName>/platforms/android/app/build/intermediates/symbols/debug/R.txt\
          --no-version-vectors
  Daemon:  AAPT2 aapt2-3.2.1-4818971-osx Daemon #0
  Output:  /Users/krithika/Projects/<AppName>/platforms/android/app/build/intermediates/merged_manifests/debug/processDebugManifest/merged/AndroidManifest.xml:31: AAPT: error: resource drawable/icon (aka org.nativescript.qbank:drawable/icon) not found.

  error: failed processing manifest.
  Command: /Users/krithika/.gradle/caches/transforms-1/files-1.1/aapt2-3.2.1-4818971-osx.jar/2eed916ddcf9151ce53f774e84877768/aapt2-3.2.1-4818971-osx/aapt2 link -I\
          /usr/local/share/android-sdk/platforms/android-28/android.jar\
          --manifest\
          /Users/krithika/Projects/<AppName>/platforms/android/app/build/intermediates/merged_manifests/debug/processDebugManifest/merged/AndroidManifest.xml\
          -o\
          /Users/krithika/Projects/<AppName>/platforms/android/app/build/intermediates/processed_res/debug/processDebugResources/out/resources-debug.ap_\
          -R\
          @/Users/krithika/Projects/<AppName>/platforms/android/app/build/intermediates/incremental/processDebugResources/resources-list-for-resources-debug.ap_.txt\
          --auto-add-overlay\
          --java\
          /Users/krithika/Projects/<AppName>/platforms/android/app/build/generated/not_namespaced_r_class_sources/debug/processDebugResources/r\
          --proguard-main-dex\
          /Users/krithika/Projects/<AppName>/platforms/android/app/build/intermediates/legacy_multidex_aapt_derived_proguard_rules/debug/processDebugResources/manifest_keep.txt\
          --custom-package\
          org.nativescript.qbank\
          -0\
          apk\
          --no-version-vectors\
          --output-text-symbols\
          /Users/krithika/Projects/<AppName>/platforms/android/app/build/intermediates/symbols/debug/R.txt\
          --no-version-vectors
  Daemon:  AAPT2 aapt2-3.2.1-4818971-osx Daemon #0

Closing the original issue and creating a new issue here.

I am still facing this issue and am unable to migrate my project to NS 5.

@NickIliev on comparing my project with the test project that you shared I note that the project directory structure is different and the src folder has been introduced and the app folder is moved into this folder.
My project was originally created using NS 2.0 and I have been migrating it to different versions as they were introduced. My project does not have a src folder.
Could this be a problem? Any suggestions that I could try?

@anuragd7 the issue doesn't seem related to the src folder but to a missing specific file that comes from a native Android library. Can you post the content of your app.gradle and also let me know which Firebase functionalities are enabled in the project?  There was this issue with Crashlytics which should be fixed with 7.4.2 version of the plugin. Still currently using your package.json is not reproducing an error on my side so it must be related to a native library that is being added in your porject (that's why we need the app.gradle content if there is a custom content there and also to know which firebase libraries you are using)
Another approach I would suggest is to create a brand new project and then install all the dependencies from your project just to check out if you can build an empty project with the list of plugins and which plugin will cause the build issue.

@NickIliev here are the contents of the app.gradle from app/App_Resources/Android
// Add your native dependencies here:
dependencies {
    compile 'com.facebook.android:facebook-android-sdk:4.6.0'
    // compile 'com.google.android.gms:play-services-auth:8.4.0'

    // compile('com.twitter.sdk.android:twitter:1.13.2@aar') {
    //     transitive = true
    // }
    configurations.all {
    resolutionStrategy.eachDependency { DependencyResolveDetails details ->
        def requested = details.requested
        if (requested.group == 'com.android.support') {
            if (!requested.name.startsWith("multidex")) {
                details.useVersion '25.3.1'
            }
        }
    }
}
}

// Uncomment to add recyclerview-v7 dependency
//dependencies {
//	compile 'com.android.support:recyclerview-v7:+'
//}

android {
  compileSdkVersion 28
  defaultConfig {
    generatedDensities = []
    applicationId = "org.nativescript.qbank"
    multiDexEnabled true

    //override supported platforms
    // ndk {
    //       abiFilters.clear()
    //   		abiFilters "armeabi-v7a"
 		// }

  }
  aaptOptions {
    additionalParameters "--no-version-vectors"
  }

  project.ext {
    googlePlayServicesVersion = "15.0.1"
  }
}

def settingsGradlePath

if(project.hasProperty("appResourcesPath")){
    settingsGradlePath = "$project.appResourcesPath/Android/settings.gradle";
} else {
    settingsGradlePath = "$rootDir/../../app/App_Resources/Android/settings.gradle";
}

def settingsGradleFile = new File(settingsGradlePath);

if(settingsGradleFile.exists())
{
    apply from: settingsGradleFile;
}
// project.ext.supportVersion = "26.0.0.-alpha1"

There was this issue with Crashlytics which should be fixed with 7.4.2 version of the plugin.

I am aware of the issue with crashlytics and was hoping my issue was similar, however I have upgraded upgraded the plugin to 7.4.2 and the error continues.

Another approach I would suggest is to create a brand new project and then install all the dependencies from your project just to check out if you can build an empty project with the list of plugins and which plugin will cause the build issue.

Have tried building a new project with an identical Package.json - As mentioned by you that does not give any error. Also the same project continues to work perfectly with NS 4.2.4!!

I am also facing the same issue , here is my package.json
{
  "nativescript": {
    "id": "au.com.ft.dev",
    "tns-ios": {
      "version": "5.0.0"
    },
    "tns-android": {
      "version": "5.0.0"
    }
  },
  "description": "NativeScript Application",
  "license": "SEE LICENSE IN <your-license-filename>",
  "repository": "<fill-your-repository-here>",
  "dependencies": {
    "@angular/animations": "~7.0.0",
    "@angular/common": "~7.0.0",
    "@angular/compiler": "~7.0.0",
    "@angular/core": "~7.0.0",
    "@angular/forms": "~7.0.0",
    "@angular/http": "~7.0.0",
    "@angular/platform-browser": "~7.0.0",
    "@angular/platform-browser-dynamic": "~7.0.0",
    "@angular/router": "~7.0.0",
    "nativescript-angular": "^7.0.1",
    "nativescript-camera": "^4.1.1",
    "nativescript-drawingpad": "^3.0.3",
    "nativescript-geolocation": "^4.3.1",
    "nativescript-google-maps-sdk": "^2.6.1",
    "nativescript-iqkeyboardmanager": "^1.3.0",
    "nativescript-loading-indicator": "^2.4.0",
    "nativescript-theme-core": "~1.0.4",
    "nativescript-ui-autocomplete": "^3.10.2",
    "nativescript-ui-listview": "^4.0.0",
    "nativescript-ui-sidedrawer": "^5.0.0",
    "reflect-metadata": "~0.1.8",
    "rxjs": "~6.3.0",
    "rxjs-compat": "^6.3.3",
    "tns-core-modules": "^5.0.3",
    "tns-platform-declarations": "^5.0.3",
    "zone.js": "^0.8.26"
  },
  "devDependencies": {
    "@angular/compiler-cli": "~7.0.0",
    "@nativescript/schematics": "~0.4.0",
    "@ngtools/webpack": "~7.0.0",
    "nativescript-dev-typescript": "~0.7.0",
    "nativescript-dev-webpack": "^0.18.0",
    "typescript": "^3.1.6"
  },
  "hooks": [
    {
      "type": "before-livesync",
      "script": "before-livesync.js"
    }
  ]
}

@anuragd7 @nmongiya I am able to build successfully while using this test app (dependencies the same as in @nmongiya example above).
The only thing I've needed to do is to create before-plugins.gradle to export the needed googlePlayServicesVersion as 15.0.1
before-plugins.gradle
android {
  project.ext {
      googlePlayServicesVersion = "15.0.1"
  }
}

I have Android SDK 28 installed withy Android build tools 28.0.3 (mandatory versions for NativeScript) + google play services and android support repository updated to latest

@NickIliev - Please take a look here - seems to be the same error

@anuragd7 yes it is the same error related to some navigation scenarios and the fakeID resource. Closing this one as a duplicate to the following issues
https://github.com/NativeScript/NativeScript/issues/6698
https://github.com/NativeScript/NativeScript/issues/6633
https://github.com/NativeScript/NativeScript/issues/6510
All of the issues seem related to the same problem and are under investigation from the modules team.

@NickIliev - I see that the issue referenced above are all closed. have just tried updating to the tns-core-modules 5.1.1 and am still facing the same issue. Is there something else I need to try? If not,please consider reopening this issue.

@anuragd7 the thing is that the error seems to manifest due to different reasons from the one fixed in the issues. However, so far no reproducible steps were reported - can you please share if you have a stable way/steps to hit the issue?

@NickIliev ,
I setup a fresh project to isolate this issue but was not able to replicate it their. However using my complete project and launching it in debug mode the I managed to track the error down to frame.android.js. It occurs during the execution of the getAttachListener function and in the debug console shows up as
Error evaluating getter - [object Object]
the function is reproduced below:
function getAttachListener() {
    if (!exports.attachStateChangeListener) {
        var AttachListener = (function (_super) {
            __extends(AttachListener, _super);
            function AttachListener() {
                var _this = _super.call(this) || this;
                return global.__native(_this);
            }
            AttachListener.prototype.onViewAttachedToWindow = function (view) {
                var owner = view[ownerSymbol];
                if (owner) {
                    owner._onAttachedToWindow();
                }
            };
            AttachListener.prototype.onViewDetachedFromWindow = function (view) {
                var owner = view[ownerSymbol];
                if (owner) {
                    owner._onDetachedFromWindow();
                }
            };
            AttachListener = __decorate([
                Interfaces([android.view.View.OnAttachStateChangeListener])
            ], AttachListener);
            return AttachListener;
        }(java.lang.Object));
        exports.attachStateChangeListener = new AttachListener();
    }
    return exports.attachStateChangeListener;
}

Is this helpful in trying to identify the underlying cause? Let me know.

@NickIliev - Thanks for the prompt response.

Can you tell me if you are hitting the issue in 100% ratio or is it happening on a random occasion?

I can confirm that this happens 100% of the time and not at random.

Also, let me know if there are some user interactions (e.g. like opening a page, drawer, modal, resuming app or else) that needs to be executed in a specific order (or are you hitting this one on app start?).

Happens on app startup

If it is possible to share the affected project with me, you can contact me personally in the community slack channel (username: niliev)

Its a pretty large project and I can't share it in its entirety. Tried the approach of building a new minimal version using the cli but am not able to replicate in that.  The alternate approach of carving out something shareable from the existing project is not working yet - but I am continuing to try and ping will ping you on slack if I succeed.
Here is some additional information that might be helpful. In my project I have set up a default component called SplashComponent that basically replicates the splash screen that is shows on app startup, in this component I initialize firebase and check if the user is logged in and then redirect to the appropriate screen (code below):
import { Component, OnInit } from "@angular/core";
import { Page } from "ui/page";
import { RouterExtensions } from "nativescript-angular/router/router-extensions";

import { UserStatusService } from "./services/userStatus.service";
import * as firebase from "nativescript-plugin-firebase";

import { TabNavigationService } from "./services/tab-navigation.service";

@Component({
  moduleId: module.id,
  selector: "app-splash",
  template: `
            <StackLayout backgroundColor="white" verticalAlignment="center">
            <Image src="res://launchpage" height="25%"></Image>
            </StackLayout>
    `
})
export class SplashComponent implements OnInit {
  public authorizationStatus: string;

  constructor(
    private routerExtensions: RouterExtensions,
    private page: Page,
    private userStatusService: UserStatusService,
    private tabNavigationService: TabNavigationService
  ) {
    page.actionBarHidden = true;
    this.authorizationStatus = this.userStatusService.getAuthorizationStatus();
    if (firebase.ServerValue !== undefined) {
      console.log("Firebase already there");
    } else {
      //   setTimeout(() => {
      firebase.init({
          // Optionally pass in properties for database, authentication and cloud messaging,
          // see their respective docs.
          persist: true,
          storageBucket: "gs://quest-a4d78.appspot.com",
          onAuthStateChanged: (data: any) => {
            console.log("LOGIN STATUS in main is " + JSON.stringify(data));
            if (data.loggedIn) {
              UserStatusService.token = data.user.uid;
              console.log(
                "FROM FIREBASE INIT user's email address: " +
                  (data.user.email ? data.user.email : "N/A")
              );
            } else {
              UserStatusService.token = "";
            }
          }
        })
        .then(
          function(instance) {
            console.log("firebase.init done");
          },
          function(error) {
            console.log("firebase.init error: " + error);
          }
        );
      //   }, 1000);
    }
  }

  ngOnInit() {
    console.log(
      "In Splash Component the authorization status is: " +
        this.authorizationStatus
    );
    if (this.authorizationStatus === "authorized") {
      this.tabNavigationService.goToTab0(0);
    } else if (this.authorizationStatus === "registration-pending") {
      this.routerExtensions.navigate(["registration"], { clearHistory: true });
    } else {
      this.routerExtensions.navigate(["login"], { clearHistory: true });
    }
  }
}

From trying to debug further I find that the error is thrown in image.android.js  during the execution of the following method
function initializeImageLoadedListener() {
    if (ImageLoadedListener) {
        return;
    }
    var ImageLoadedListenerImpl = (function (_super) {
        __extends(ImageLoadedListenerImpl, _super);
        function ImageLoadedListenerImpl(owner) {
            var _this = _super.call(this) || this;
            _this.owner = owner;
            return global.__native(_this);
        }
        ImageLoadedListenerImpl.prototype.onImageLoaded = function (success) {
            var owner = this.owner;
            if (owner) {
                owner.isLoading = false;  <------"***********ERROR THROWN AFTER THIS
                                                                                STATEMENT*************"
            }
        };
        ImageLoadedListenerImpl = __decorate([
            Interfaces([org.nativescript.widgets.image.Worker.OnImageLoadedListener])
        ], ImageLoadedListenerImpl);
        return ImageLoadedListenerImpl;
    }(java.lang.Object));
    ImageLoadedListener = ImageLoadedListenerImpl;
}

On inspecting the owner variable in the debug console I see the following.
owner
Image {_observers: Object, _onLoadedCalled: true, _onUnloadedCalled: false, _cssState: CssState, pseudoClassAliases: Object, …}
__nativeView: Object {defaultPaddings: Object, listener: Object}
_androidView: Object {defaultPaddings: Object, listener: Object}
_context: Object {constructor: , isNativeScriptActivity: true, _callbacks: ActivityCallbacksImplementation}
_cssState: CssState {view: Image, _onDynamicStateChangeHandler: , _matchInvalid: false, …}
_defaultPaddingBottom: 0
_defaultPaddingLeft: 0
_defaultPaddingRight: 0
_defaultPaddingTop: 0
_domId: 8
_gestureObservers: Object {}
_hasFragments: false
_isAddedToNativeVisualTree: true
_isClickable: false
_isLoaded: true
_isPaddingRelative: false
_manager: null
_observers: Object {}
_onLoadedCalled: true
_onUnloadedCalled: false
_rootManager: null
_style: Style {_observers: Object, view: Image, Symbol(height:valueSourceKey): 3, …}
_styleScope: StyleScope {_css: "", _localCssSelectors: Array(0), _localCssSelectorVersion: 0, …}
_suspendedUpdates: Object {}
_suspendNativeUpdatesCount: 0
android: Object
automationText: undefined
background: "undefined undefined undefined undefined"
backgroundColor: undefined
backgroundImage: undefined
bindingContext: undefined
borderBottomColor: undefined
borderBottomLeftRadius: 0
borderBottomRightRadius: 0
borderBottomWidth: Object
borderColor: undefined
borderLeftColor: undefined
borderLeftWidth: Object
borderRadius: 0
borderRightColor: undefined
borderRightWidth: Object
borderTopColor: undefined
borderTopLeftRadius: 0
borderTopRightRadius: 0
borderTopWidth: Object
borderWidth: Object
class: undefined
className: undefined
col: 0
color: undefined
colSpan: 1
css: ""
cssClasses: Set(0) {}
cssPseudoClasses: Set(0) {}
cssType: "image"
decodeHeight: Object
decodeWidth: Object
effectivePaddingBottom: 0
effectivePaddingLeft: 0
effectivePaddingRight: 0
effectivePaddingTop: 0
height: Object
horizontalAlignment: "stretch"
id: undefined
imageSource: undefined
ios: undefined
iosOverflowSafeArea: false
iosOverflowSafeAreaEnabled: true
isEnabled: true
isLayoutRequired: true
isLayoutValid: false
isLoaded: true
isLoading: true
isUserInteractionEnabled: true
left: Object
loadMode: "sync"
margin: Object
marginBottom: Object
marginLeft: Object
marginRight: Object
marginTop: Object
meta: Object {skipAddToDom: false}
minHeight: Object
minWidth: Object
modal: undefined
nativeView: Object
nativeViewProtected: Object {defaultPaddings: Object, listener: Object}
nodeName: "Image"
nodeType: 1
opacity: 1
originX: 0.5
originY: 0.5
page: Page
parent: StackLayout {_observers: Object, _onLoadedCalled: true, _onUnloadedCalled: false, …}
parentNode: StackLayout
pseudoClassAliases: Object {highlighted: Array(2)}
rotate: 0
row: 0
rowSpan: 1
scaleX: 1
scaleY: 1
src: "res://launchpage"
stretch: "aspectFit"
style: Style
Symbol(isLoading:propertyKey): true
Symbol(src:nativeDefaultValue): undefined
Symbol(src:propertyKey): "res://launchpage"  <-------"THIS IS THE IMAGE USED in SPLASH
                                                                                COMPONENT"
tintColor: undefined
top: Object
translateX: 0
translateY: 0
typeName: "Image"
useCache: true
verticalAlignment: "stretch"
visibility: "visible"
width: "auto"
__proto__: ImageBase {constructor: , createNativeView: , initNativeView: , …}

Hope the above context is useful.. Will keep trying to replicate the error in a shareable project.

@NickIliev - Have shared a project replicating this error with you on the community slack channel.

Hey @anuragd7 I am not seeing a ping or any direct message to my slack username (niliev)

Had DM'd 'niliev' but seems that didn't get through. Anyhow glad that I was
able to respond to your message on the community Slack. Hoping for a
resolution soon :-)
On Tue, 25 Dec, 2018, 12:44 PM Nick Iliev<EMAIL_ADDRESS>wrote:

Hey @anuragd7 https://github.com/anuragd7 I am not seeing a ping or any
direct message to my slack username (niliev)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NativeScript/android-runtime/issues/1212#issuecomment-449815165,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE2PtiKiCtIXJ8yp8HWfLQ1WdXBSngH1ks5u8dBRgaJpZM4YnUON
.

@anuragd7 we reviewed your project and found the reason for the exception.
In your app/App_Resources/Android/app.gradle you have the following snippet that downgrades the support library dependencies:
dependencies {
   compile ‘com.facebook.android:facebook-android-sdk:4.6.0’
   // compile ‘com.google.android.gms:play-services-auth:8.4.0’

   // compile(‘com.twitter.sdk.android:twitter:1.13.2@aar’) {
   //     transitive = true
   // }
   configurations.all {
   resolutionStrategy.eachDependency { DependencyResolveDetails details ->
       def requested = details.requested
       if (requested.group == ‘com.android.support’) {
           if (!requested.name.startsWith(“multidex”)) {
               // remove this and your app will work
               details.useVersion ‘25.3.1’ // <-- this downgrades support library deps
           }
       }
   }
}
}

However, with https://github.com/NativeScript/NativeScript/pull/6129 NativeScript 5.0 and all later versions do not support older support library versions any more (any version prior to 26 will throw exception). We are now using and rely on the latest support library version 28.0.0 that contains all fixes from Google and we are only testing NativeScript against it.
Hope this helps.


HoloMap to grid and dimension order

When displaying a HoloMap as a grid, the order of the dimensions is ignored:
hmap = hv.HoloMap({(0,5):hv.Image(np.random.randn(5,5)),
            (0,50):hv.Image(np.random.randn(50,50)),
           (1,5):hv.Image(np.random.randn(5,5)),
            (1,50):hv.Image(np.random.randn(50,50)),}, kdims=['K1','K2'])

The result is the same for both:
hmap.grid(dimensions=['K1','K2'])

hmap.grid(dimensions=['K2','K1'])

I also agree the supplied dimension order should be respected here.


|Wip Extending Date.Local

Changes for #38

Contribute, and get free tricks from Alfonso. Nice :)
Time to clean it up!

márc. 20. 4:37 du. ezt írta ("Alfonso Garcia-Caro" <
notifications@github.com>):

@alfonsogarciacaro commented on this pull request.
In src/Date/Local.fs
https://github.com/fable-compiler/fable-powerpack/pull/42#discussion_r175814488
:

       Time =

         { AM = "AM"
           PM = "PM" } }

let french =

let getFrench() =

In F# there's a trick to compile something as a function but make it look
as value: adding a generic parameter, so you can use let french<'t> =
instead.
REPL
http://fable.io/repl/#?code=let foo<'T> %3D 5
let bar %3D 5

printfn "%25i" foo
printfn "%25i" bar
&html=<html><body><%2Fbody><%2Fhtml>9
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/fable-compiler/fable-powerpack/pull/42#discussion_r175814488,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAziK8ecUvcJXzOv0IkphDw0ZfmQAti0ks5tgSJIgaJpZM4Sx8sM
.

I guess it is ready.
One last thing I may add is a helper to format date with locale default date format. Writing something like let formatDate date = Date.Format.localFormat localXX localXX.Date.DefaultFormat date in application code feels a bit redundant. But of course that's just one line. What do you think?

Thanks @AkosLukacs! Let's merge and publish this :+1: We can then collect some feedback from users and add helpers if necessary :)


404 is the result!

Followed the instructions, and server started (easy part) and localhost 3000 says 404 This page could not be found. Hmm.... I must have missed something?

Oh yes the README.md has the wrong URL and has been corrected.
Just go to http://localhost:3000/api/news and you can see the news

Thank you very much, YAY! This has helped me very much. Great Job, keep up the good work.


Implement cupy.fill_diagonal()

Related to #1294
http://docs.scipy.org/doc/numpy-1.11.0/reference/generated/numpy.fill_diagonal.html

LGTM except the comments.

I fixed the above problems. Please check it.

Thanks. LGTM

@beam2d I fixed the problems you have mentioned. Please check it.

LGTM! (sorry for being late)


feat: use chainguard for OpenEBS images - feedback

Manual workflow runs:
https://github.com/replicatedhq/embedded-cluster/actions/runs/10063827939
https://github.com/replicatedhq/embedded-cluster/actions/runs/10063882917
PRs created by running the workflow manually
https://github.com/replicatedhq/embedded-cluster/pull/812
https://github.com/replicatedhq/embedded-cluster/pull/811

Not waiting for e2e tests here as they are irrelevant


Add Map Element

Here's a basic structure showing how a Map Elements work. Greater customization included soon. (eg. Annotations and Reverse Geocoding, Annotations with a Custom Callout, Overlays of Population by US State, Callout Accessory Views, Region and Zoom Limits, Animated Polyline Overlays, Displaying Place Data by PlaceID, and Search Filtering)
A few questions...

Can JS be rendered into it's own file?
Can this code be improved using Ignite Components?

return Group {
            loadMapScript
            mapScript

            """

            """
}
.id("map-container")
.attributes(attributes)
.render(context: context)

Additional Opinions Welcome

Sorry for taking so long to reply, and thank you for this contribution! We can look to improve the code as appropriate once it's merged in. In the meantime, I have two questions:

What is that huge token string?
If someone places two maps, do we run that JS twice? I wonder if it could be included only once, similarly to how the icons work.

MapKit JS typically has two scripts.
The first is standard and reusable containing authorizations required by Apple. It includes JS libraries, also required.

The second script, a module, includes parameters necessary for Maps which may include interactive elements or external file calls.

Sorry, I should have been clearer: there's already a huge token in the code. What is that exact token? I'm wary about putting actual tokens into source control, although at this point it's in GitHub's history regardless. Shouldn't we perhaps make it a required thing, or perhaps ask users to enter it in at the site level to avoid having them repeat themselves?
Based on what you've said, it sounds like when we have any map, we need to include one piece of JavaScript to download the actual Maps code. We then include the second piece of JavaScript on a per-map basis, so that second one could be included three, four, five times, etc. Does that sound about right?

Yes, that token I shouldn't have submitted was non-domain specific. Being temporary, it expires after seven days. MapKit JS supports domain specific tokens which IgniteSamples can use. You may create a separate token via your developer account, due to restrictions on domains, it's not worrisome having it as public knowledge.
///  Domain Restricted Token - Solely works with https://ignitesamples.hackingwithswift.com
public let exampleSiteMapKitJSToken: String = "eyJraWQiOiI0UkRRVVRIMjJOIiwidHlwIjoiSldUIiwiYWxnIjoiRVMyNTYifQ.eyJpc3MiOiIyTVA4UVdLN1I2IiwiaWF0IjoxNzI1NTk4NDM2LCJvcmlnaW4iOiJpZ25pdGVzYW1wbGVzLmhhY2tpbmd3aXRoc3dpZnQuY29tIn0.UgaNnmSfiQsD6D23LC7-_5mEY2p_hvtM_nPOfwtV48UWl1YPX5o2YgvAJpTdjMzEQZ-IPapuIXJ7DJ4N4kdo8w"

Regarding the JavaScript, what's being figured now answers the question whether that initial code can call multiple libraries which then are divvied throughout the site or at least page.

Currently any token can be added within the Map call site. Would it be preferable (it may be easier with implementation) that that token be added within the Main Site struct via the Site protocol as an optional variable?

Yes, I definitely think adding a token each time is a bit much. If we can centralize that it would be great!
Where did you get to with loading the JavaScript a bit less? Could you also run SwiftLint on this commit? It seems there are various whitespace changes again.
Thank you!

Implementing JavaScript will mirror how PR 108 solves it. At least map initialization will take place on a site level with libraries + variables happening within specific pages.

Forgive me, I didn't mean for this PR's closure. I'm not sure if I can restore this or PR 108


xSQLServerMemory: Should Be Cluster Aware

Details of the scenario you tried and the problem that is occurring:
When the SQL Instance is an FCI and the configuration is pushed to every node of the FCI, each of the resources that reach into the Instance execute multiple times per "cycle".
For example, if I have a 2-node FCI and have xSQLServerMemory defined, both nodes will reach into the instance and set the memory regardless if it is the owner node. This could result in the server memory being configured twice every 15 minutes.
In the case where new servers are being added to the FCI that have a different memory configuration, this will result in the new node's configuration fighting with the old nodes causing the memory configuration to flip-flop between the correct memory allocations for each server. This scenario has been observed in a real-life environment when using dynamic memory allocation.
The DSC configuration that is using the resource (as detailed as possible):
The following configuration is applied on two or more nodes of a Failover Cluster Instance (FCI):
node localhost
{
    xSQLServerMemory Set_SQLServerMaxMemory_ToAuto
    {
        Ensure               = 'Present'
        DynamicAlloc         = $true
        SQLServer            = 'SQLServer'
        SQLInstanceName      = 'DSC'
        PsDscRunAsCredential = $SysAdminAccount
    }
}

Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
Any
What module (SqlServer or SQLPS) and which version of the module the DSC Target Node is running:
Any
Version of the DSC module you're using, or 'dev' if you're using current dev branch:
Any

I propose that if the node that is executing the configuration is not the active owner of the FCI, it should write a verbose message stating that, and then silently exit.

I can see this being a problem, where you have two different memory configurations in 2-or-more-node cluster. I agree that in those cases the user need to specify the same configuration in all the nodes. and that the Test-TargetResource should silently exit after writing a verbose message.
Test-DscConfiguration will always return $true since it silently exists. It will expect that the configuration is in desired state when the node does not own the instance.
But...

Should this behavior only apply when configuration is dynamic allocation?
How should the Get-TargetResource do when Get-DscConfiguration is called? It should go out an fetch the actual memory configuration?

Those are excellent questions.
I would hope that if static memory allocations are defined adequate memory would be available on all nodes. However, in reality I can see scenarios where the secondary node may be shorted resources due to budgetary constraints (purely non-technical reasons). I think that memory is node specific, so we should allow for different configurations per node.
For the get, is it important to evaluate the validity of a component that is not currently present on the node? I would argue no. Therefore, I think get should not bother gathering the memory configuration if the current node is not hosting the instance.

I could agree on supporting different configurations for both static and dynamic memory allocation. For a static memory allocation, then the state would practically never be in desired state for the node not owning the instance.
Regarding Get. I understand your point, and can agree on it, but that would make it stray from normal behavior for a resource. It there were something dependent on the configuration from the get (like an automation) and all of the sudden the resource return null values it would be very strange, and that node would not feel like it would be in desired state. I rather see Get always getting the current values from the instance regardless of ownership.
So, to conclude. I agree this need to be done for both dynamic and static memory allocation. But in my opinion we should make Get-TargetResource always returning current state.

Makes sense to me!

To resolve this issue, a parameter called ProcessOnlyOnActiveNode should be created on the Set-TargetResource and Test-TargetResource functions.
The Get-TargetResource function will execute the helper function Test-ActiveNode to determine if the current node is actively hosting the SQL instance and return the result via the read-only property IsActiveNode.
The Test-TargetResource function will use the value of ProcessOnlyOnActiveNode and IsActiveNode to determine if it should continue. If ProcessOnlyOnActiveNode is $true and IsActiveNode is $false, Test-TargetResource will return $true.
I put together this gist as a guide to updating the resource.
Also, see the xSQLServerAlwaysOnAvailabilityGroup resource for a completed example.

Starting this next


Ability to choose install location

Is your feature request related to a problem? Please describe.
Having the choice to choose installation location in case you want to install to another drive.
Describe the solution you'd like
Possibly have a button option for "Default" or change drive button.

Why do you need the app to install to a different location? The app itself is only about 250MB. It shouldn't be much of a problem. And as for the model file(s), you can put it wherever you want to. However, if you are very very low on storage, then I can use the classic windows setup installer instead of the one-click installer for the next release.

classic windows setup sounds nice


Add keys tree

Problem
Right now the FS is being loaded by looking up a keyName in keystore-idb. This will not work across browsers and IDB could be cleared by the browser and the user would lose access to their files
Solution

Add a /keys tree to the root of the filesystem
Add a shareWith function to the filesystem that encrypts the root key of a filesystem for a DID's public key and adds it to /keys/${did}
Share filesystem with self when creating
when loading a filesystem fromCID, check if a key has been shared with the user's DID, decrypt it, and load the private tree with that key
reorganized some of the functions in core as we're adding more DID functions

Open questions
Each user has a read key and a write key. We're storing the write key in dns. How do we publicize public read keys? Two separate DNS entries?
How to we give sub access to a user? Instead of just a key stored in /keys, we can also include the related cid. Add this feature now? Or in the future?

@expede this one is really about half done. It currently only shares the root of a filesystem, not a private subtree. And it only has logic for the "shared be me" key tree not the "shared with me" tree.
I'd use this branch for context & ideas, but don't merge it without a decent rewrite (which will probably take place after restructuring the FS)

Closing due to FS rewrite


MINOR: Fix build failure in genConnectOpenAPIDocs

We bumped the swagger-gradle-plugin version in https://github.com/apache/kafka/commit/d1ad1d7b7013ea2c24a3f71c485a2a914adf1348
This breaks the genConnectOpenAPIDocs task:
> Task :connect:runtime:genConnectOpenAPIDocs FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':connect:runtime:genConnectOpenAPIDocs'.
> io.swagger.v3.jaxrs2.integration.SwaggerLoader.setSkipResolveAppPath(java.lang.Boolean)

We've had a similar breakage in the past when swagger-gradle-plugin and swaggerAnnotations/swaggerJaxrs2 used different versions.
As far as I can tell swaggerAnnotations and swaggerJaxrs2 are stuck with 2.2.8 as it's the last version that supports Java 8. I get the build working using swagger-gradle-plugin 2.2.10 but it's probably safer, at least for now, to keep these versions aligned.
Committer Checklist (excluded from commit message)

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

One potential option to prevent such breakages in the future could be to use this workaround and set a common Swagger version in the gradle.properties that is used in both the plugins section (for the swagger-gradle-plugin) as well as the dependencies section (for swaggerAnnotations / swaggerJaxrs2 )?

Yes it would be good to have the version in a single place to avoid these issues. I created https://issues.apache.org/jira/browse/KAFKA-15521 to track that work.
I'll merge that now to fix the build.


Aggregator: does it double-count the secondary replica it received twice?

No – when we merge the AggregatorInternalRecord we do some casting to Set() that filters out duplicate results.
We should test it at the app level as well.

Closing as WONTFIX, not important enough.


Status bar change when i open a new tab

Self-Diagnosis

[x] I have searched the issues for an answer to my question.
[x] I have reviewed the NERDTree documentation. :h NERDTree
[x] I have reviewed the Wiki.
[x] I have searched the web for an answer to my question.

Environment (for bug reports)

[x] Operating System:  MacOS

[x] Vim/Neovim version :echo v:version:

[x] NERDTree version, found on 1st line in NERDTree quickhelp ?: 6.9.9

[x] vimrc settings
vimrc.txt

[ ] NERDTree variables

Other NERDTree-dependent Plugins

[ ] jistr/vim-nerdtree-tabs
[ ] ryanoasis/vim-devicons
[ ] tiagofumo/vim-nerdtree-syntax-highlight
[x] Xuyuanp/nerdtree-git-plugin
[ ] Others (specify):

[x] I've verified the issue occurs with only NERDTree installed.

Steps to Reproduce the Issue

Open a tab

Current Result (Include screenshots where appropriate.)
my status bar change or dissapear

Expected Result
Keep my status bar

Check out :h 'laststatus'. In Vim, default is 1, which hides the status line when there is only one window. In Neovim, the default is 2, which always shows the status line. In your .vimrc, you can add the line
set laststatus=2

to always see your status line.

Yes, it works


Create androidx support

Platforms
Android
Versions
Android: compileSDK 28, buildTools 28.0.3
lottie-react-native: 2.5.11
react-native: 0.58.3
Description/Current Behaviour
I have enabled AndroidX support for my app and upon building i face the following error:
error: package android.support.v4.view does not exist
The package should enable androidx support as it is going to be the default support library from API 28 onwards.
Expected Behaviour
App should build successfully
Steps to Reproduce
See description

This comes down to upgrading to lottie-android to at least 2.8.0.
I tried to do this myself but it becomes more complicated than I expected.
In the mean time, I suppose changing the 8th line in
node_modules/lottie-react-native/src/android/src/main/java/com/airbnb/android/react/lottie/LottieAnimationViewManager.java
from
import android.support.v4.view.ViewCompat;
to
import androidx.core.view.ViewCompat;
should do the trick.

HI @ThierryVC any chance you could make a PR of your attempt to update to android 2.8.0? I'm also working on this so maybe we could benefit from each other's work.

Sorry for the delay (and lack of talent with RN & lottie).
I simply changed the version in build.gradle file to
implementation 'com.airbnb.android:lottie:3.0.0-beta1'
and then removed functions and variables about 'cacheStrategy' and 'useHardwareAcceleration' in the two files going by: src/android/src/main/java/com/airbnb/android/react/lottie/LottieAnimationView*.java
but still had trouble with
view.setAnimation(new JsonReader(new StringReader(animationJson)));
in LottieAnimationViewPropertyManager.java
giving me: error: no suitable method found for setAnimation(JsonReader)
Changing it to :
view.setAnimation(animationJson);
would build, but then crash when I have a Lottie View with Json.
Looking forward to see this work as it would fix a few problems with recent android versions (8.0+).

Looking at this, I do not understand why it doesn't allow JsonReader anymore.
https://github.com/airbnb/lottie-android/blob/master/lottie/src/main/java/com/airbnb/lottie/LottieAnimationView.java
Should it then be "translated" into an Animation Object ?

To quote lottie-android's CHANGELOG.md :
2.7.0
Features and Improvements
Removed deprecated LottieCompositionFactory APIs. If you were using JsonObjects, switch to Strings (#959).
No more Json? But the Doc seems to say we can? I'm confused.

Yeah, it's a bit confusing. I will check with the guys in lottie-android

This is now even more urgent since RN 0.59 has now been released which depends on supportLibVersion 28.0.0 which is now blocking any upgrades for those that depend on this lib.  I am going to take a stab at it

@kdawgwilk yes I'm experiencing the same issue

A temporary workaround that worked for me was to add:
api 'com.android.support:appcompat-v7:28.0.0' inside the dependencies section in:
node_modules/lottie-react-native/src/android/build.gradle.
@emilioicai Would it be helpful if I created a PR with just this fix and bump the version(not sure if bugfix version bump would be appropriate here or if it could affect other things) while larger AndroidX fixes get addressed so we can upgrade to RN 59 without needing to make changes inside our node_modules?

@bondparkerbond it would be really helpful so please. go ahead and let me know if you need any help on it.

@bondparkerbond it would be really helpful so please. go ahead and let me know if you need any help on it.

I made a PR, but wasn't sure what kind of version bump this would need so I haven't bumped any versions: https://github.com/react-native-community/lottie-react-native/pull/455#issue-261347676

I'm using lottie-react-native 2.6.0 in an app (with react native 59.1). Without androidx enabled it builds. If I enable androidx, it's failing like this:
node_modules/lottie-react-native/src/android/src/main/java/com/airbnb/android/react/lottie/LottieAnimationViewManager.java:8: error: package android.support.v4.view does not exist
import android.support.v4.view.ViewCompat;
                              ^
node_modules/lottie-react-native/src/android/src/main/java/com/airbnb/android/react/lottie/LottieAnimationViewManager.java:118: error: cannot find symbol
> Task :lottie-react-native:compileDebugJavaWithJavac FAILED
            if (ViewCompat.isAttachedToWindow(view)) {
                ^
  symbol: variable ViewCompat

node_modules/lottie-react-native/src/android/src/main/java/com/airbnb/android/react/lottie/LottieAnimationViewManager.java:144: error: cannot find symbol
            if (ViewCompat.isAttachedToWindow(view)) {
                ^
  symbol: variable ViewCompat

I've got android.enableJetifier=true in gradle.properties, but it's not able to automatically fix up this code since it's just some java files in node_modules, not an aar.
Looking at this issue and the above PR, I guess that's expected.

I didn't really know anything about androidx before today, so others might be able to offer better ideas than these:

Instead of bundling java in the node module, publish aars somewhere (allowing jetifier to fix them automatically).
Just supporting androidx would leave behind anyone still using the support lib.
Provide two java source trees under node_modules/ (perhaps using symlinks and/or a post install script?) and the gradle build could somehow pick the right one.
Build an aar locally and then it can maybe get fixed up with jetifier.

Another possibility:

Add a script to this project's repo that allows node_modules/ to be patched up to work with/without androidx enabled. Users can then choose whether to configure their app's package.json with a postinstall script that invokes your script based on whether they are using androidx or not. This project would choose whether it wants to default to support lib or androidx based on which is more popular, changing to androidx when it becomes most popular.

Another possibility:

Add a script to this project's repo that allows node_modules/ to be patched up to work with/without androidx enabled. Users can then choose whether to configure their app's package.json with a postinstall script that invokes your script based on whether they are using androidx or not. This project would choose whether it wants to default to support lib or androidx based on which is more popular, changing to androidx when it becomes most popular.

Here's one example of such script - In my case I had an issue with react-native-gesture-handler relying on the old android.support.v4 library while the rest of the project was configured to work with androidX.
I was able to resolve the issue by adding the following to the end of the app-level build.gradle file:
preBuild.doFirst {     ant.replaceregexp(match:'import android.support.v4.util.', replace:'import androidx.core.util.', flags:'g', byline:true) {         fileset(dir: '../../node_modules/react-native-gesture-handler/android/src/main/java/com/swmansion/gesturehandler/react/', includes: '*.java')     } }

@ktsoukanov did you manage to make thats] script work with lottie-react-native? I keep getting strange errors if I add it.

According to release notes, current version of lottie should work with RN=>0.59 just fine out of the box. Most likely the errors in your build are not related to androidX.
If you still get androidX-related errors, try the following:
preBuild.doFirst {     ant.replaceregexp(match:'import android.support.v4.view.', replace:'import androidx.core.view.', flags:'g', byline:true) {         fileset(dir: '../../node_modules/lottie-react-native/src/android/src/main/java/com/airbnb/android/react/lottie/', includes: '*.java')     } }
lottie, as of version 2.6.1 uses only one class from the legacy support lib: android.support.v4.view.ViewCompat, this script moves that import to androidX namespace.

I have the same issue.

RN 59 does not enable androidX support, default androidX support is coming in RN 0.60. I think we only solved app compatibility issues for 59+, but still don't have androidX support.

Building on what @ktsoukanov suggested. I had luck with adding the following to my app-level build.gradle:
subprojects {         if (project.name.startsWith("lottie-react-native")) {             preBuild.doFirst {                 ant.replaceregexp(match: 'import android.support.v4.view.', replace: 'import androidx.core.view.', flags: 'g', byline: true) {                     fileset(dir: './src/main/java/com/airbnb/android/react/lottie/', includes: '*.java')                 }             }         } }

@200even modifying sub-projects is a good work around, but especially with RN 60 and default AndroidX support around the corner, you might want a more robust solution for Jetifying your RN Android dependencies to support AndroidX such as this one. It allows you to Jetify(convert) all support lib dependencies into AndroidX dependencies and also allows going in reverse if you have a library that has already migrated and you're not ready to do so. It also works on npm dependencies and not just .arr files like the original Android Jetifier tool did.

Use this script  migrate to androidx.

this script worked for me: jetifier

this script worked for me: jetifier

which script @mazenchami ? the script that @shouhuori posted?

@brenohq not the one @shouhuori posted, its using the jetifier library...
1 .Convert your app to AndroidX via the [standard AndroidX migration](https://developer.android.com/jetpack/androidx/migrate)
2. npm install --save-dev jetifier
3. npx jetify
4. npx react-native run-android (your app should correctly compile and work)
5. Call npx jetify run in the postinstall target of your package.json (Any time your dependencies update you have to jetify again)


Move perf tests to js/perf/

This restructures how the perf tests import noms (by doing require('../../../') instead of require('@attic/noms') which solves the dependency issue.

@mikegray @sunglim PTAL
This makes me realize that we should probably just change the whole js structure around to:
js/
  noms/  (old js dir)
  perf/
  eslintrc/
  webpack-config/

do samples/js then move into js/samples too?

lgtm with a few minor nits/questions

Lame... that worked locally. I'll just do the big move instead.