chore: Remove old projects files

GitHub Issue: #
PR Type
What kind of change does this PR introduce?

Bugfix
Feature
Code style update (formatting)
Refactoring (no functional changes, no api changes)
Build or CI related changes
Documentation content changes
Other... Please describe:

Description

Removed old projects files.
PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Interface members are XML documented
[ ] Documentation (XML or comments) has been added and/or existing documentation has been updated
[ ] Architecture documents have been updated
[x] Tested on all relevant platforms

Other information

Internal Issue (If applicable):

Is it normale to remove the ApplicationTemplate.Shared

Yes, it was the one generated with .NET 6 heads. And we used it as a placeholder to make sure everything was working.


Hotfix: Minor Presentation Changes

Increase field limits
Fix CSS bugs
Improve layout
Migrate to card views

Coverage remained the same at 100.0% when pulling a4aa697870d71bad188af2edddaa1a3a53d87076 on hotfix/minor-presentation-changes into a5b41acc9ddb2ffdc45ef7e2deb9038604e7c8aa on master.


v1.1.20

Bug fixes

#531 - reload fixture list after add/delete fixture

Changes

#526 - add health check for seasons

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

301 of 301 (100.0%)  changed or added relevant lines in 18 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 96.098%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
7020

Relevant Lines:
7089

💛  - Coveralls


carousel autoplay

Hi
i have this carousel

<Carousel.PageTransition>

</Carousel.PageTransition>

i don't understand how to enable autoplay.
Thanks

Page transitions are only shown when content changes. If that should happen automatically, you can use a DispatcherTimer in your ViewModel.
Note: for questions like this please use discussions section or join the telegram or gitter chat. 🙏 Thanks.

Sorry and thanks


Update to yew 0.19.3

Coverage remained the same at 69.453% when pulling e6ea44ae534e3cce8a977d070b29a600ccdbeb72 on yew-0.19.3 into c5a5fb3d1edb5c1f9c8901a32bcebe463328cf13 on master.


[ibm.com/standards/web page]  Review Linda's recommended solution and propose a solution reviewed by Design

The problem
Users who are not working within IBM VPN will get an error page when they try to click on most of the links on this page -> ibm.com/standards/web
Suggested solution
So for all links on this page that send the user to w3 page, need to add to the card an indicator that it is for internal use.
An example is on this page:
https://www.ibm.com/design/language/ibm-logos/8-bar
under the Resources section.  It show message after title  (IBM id required)
Application/website
www.ibm.com/standards/web
Additional Information

Dev issue (#7565 )
Link to repo for changes:  https://github.ibm.com/webstandards/standards-website
Page where the edits will be needed: https://github.ibm.com/webstandards/standards-website/blob/master/src/gatsby-theme-carbon/templates/Homepage.js.

Acceptance Criteria

[ ] Linda's recommended solution and additional options are reviewed
[ ] Design solution is reviewed with the DDS designers for input
[ ] Dev issue is updated with the final design

Don't need this design story.


[Doc] update README for Qwen chat

Type of Change
feature or bug fix or documentation or others
API changed or not
not
Description
add qwen chat to README
detail description
JIRA ticket: xxx
Expected Behavior & Potential Risk
the expected behavior that triggered by this PR
How has this PR been tested?
how to reproduce the test (including hardware information)
Dependency Change?
any library dependency introduced or removed

Do we really need "Chat with" section in the main README for each model with chat support?


Command 'Terminal API: Attach data listener' resulted in an error

Hi,
when I run terminal-sample, attach data listener fail, how to fix it?
Command 'Terminal API: Attach data listener' resulted in an error (Running the contributed command: 'terminalTest.onDidWriteTerminalData' failed.)

This is a proposed API so it won't work unless you're on Insiders with proposed enabled. Additionally the plan is not to stabilize this so it's probably a waste of time experimenting with it.


Create uam.txt

Universidad Americana For Students

@VictorRC Pull request merged. Thank you!
Just for the reference: this university has an official website at http://www.uam.edu.ni, and the domain uam.net.ni is registered for the university according WHOIS service at www.nic.ni.


playbook-ztp-conf-generate.yml is not creating directory structure

Directory structure is not well creating in some cases

Playbook:
---
### Setup Local directory structure to store files locally
- name: Init ZTP directory strucutre to store local files
  hosts: ztp-servers
  connection: local
  become_user: root
  become_method: sudo
  gather_facts: no
  vars_files:
    - "group_vars/ztp-servers/ztp.yaml"
  tasks:
    - name: build path
      debug:
        msg: "Build directory {{ build_dir }}"
    - name: remove host build temp directory
      file: path={{ build_dir }} state=absent
    - name: create host build temp directory
      file: path={{ build_dir }} state=directory mode=0777
    - name: create host build softwares directory
      file: path={{ build_dir }}/softwares/ state=directory recurse=yes mode=0777
    - name: create host build configlet directory
      file: path={{ build_dir }}/configlet/ state=directory recurse=yes mode=0777

Execution:
ansible-playbook -i hosts.ini playbook-ztp-init.yml

PLAY [Init ZTP directory strucutre to store local files] ***********************

TASK [build path] **************************************************************
ok: [ztp01] => {
    "msg": "Build directory conf/ztp/"
}

TASK [remove host build temp directory] ****************************************
changed: [ztp01]

TASK [create host build temp directory] ****************************************
changed: [ztp01]

TASK [create host build softwares directory] ***********************************
changed: [ztp01]

TASK [create host build configlet directory] ***********************************
changed: [ztp01]

PLAY RECAP *********************************************************************
ztp01                      : ok=5    changed=4    unreachable=0    failed=0

And Directory structure is not created eve if playbook says it is OK
[tom@spy01 ansible-junos-ztp (stagging ✗)]$ ls conf -l
total 0
[tom@spy01 ansible-junos-ztp (stagging ✗)]$

Ansible version:
# ansible --version
ansible <IP_ADDRESS>
  config file = /home/tom/.ansible.cfg
  configured module search path = Default w/o overrides

Solved by using a specific group to manage local actions


High (in terms of absolute cosine similarity) similarity scores between two completely irrelevant / random pairs.

Describe the bug
E5-small/base/large v1/v2
Hi unilm team,
Thank you so much for the great project! We try to replace sentence-transformer with E5. When using the official example scripts with E5-small/base/large v1/v2 models, the cosine/inner product similarity between two completely irrelevant sentences is still over 0.7. This occurs even when using query/paragraph prefixes. As a result, there are no pairs of sentences with scores significantly lower than 0.7.
While the relevant pairs' similarity scores' are indeed relatively higher than the irrelevant pairs' score (e.g. around 0.8), but the issue is the negative pairs' score in absolute  value are still pretty high. This high similarity between irrelevant pairs makes Approximate KNN retrieval ineffective and difficult to use in search retrieval applications.
As a result, the performance of the E5 model is worse for our application compared to other models with worse benchmark results, such as all-MiniLM-L6-v2.
We are wondering if you have any advice or suggestions to work around this high baseline similarity score issue. Thank you so much!
Expected Behavior: The similarity between irrelevant pairs should be significantly lower, ideally below 0.5 or even lower. Alternatively, it may be necessary to use a different similarity measurement other than inner product or cosine similarity.

This is a known and expected behavior. For tasks like text retrieval or semantic similarity, what matters is the relative order of the scores instead of the absolute values, so this is generally not an issue.
Can you provide more information about your application? For example, what type of tasks are you dealing with? And do E5 models perform worse than all-MiniLM-L6-v2 even with exhaustive vector search?
If it is indeed an issue, you can use whitening operation to make the embeddings distribute more uniformly as described in the paper https://arxiv.org/abs/2103.15316, but this would add additional complexity.

@intfloat I haven't looked up what whitening means, but would simply rescaling the score not be adequate? That is, given a score X in [0.7, 1.0], take as score 1.0 - (1 - X)/0.7.

@intfloat I haven't looked up what whitening means, but would simply rescaling the score not be adequate? That is, given a score X in [0.7, 1.0], take as score 1.0 - (1 - X)/0.7.

Sure, you can do something like that. But this does not really affect the rankings...

@intfloat I haven't looked up what whitening means, but would simply rescaling the score not be adequate? That is, given a score X in [0.7, 1.0], take as score 1.0 - (1 - X)/0.7.

Sure, you can do something like that. But this does not really affect the rankings...

Now I am confused. I thought the relative rankings were fine, so why would you want to affect them?

I ran a small experiment with whitening vs not whitening, and whitening was rather disappointing. My dataset was tiny, n=100, so maybe that was the reason?
The experiment was simple:

labelled data
hold out some
train the whitening bias and kernel on the training data
transform the test data
look up the nearest embedding in the training set, and output its class
check for accuracy of guessed label vs known label

Running whitened vs unwhitened embeddings through that, unwhitened performed generally better, given many different hyper params.
One thing that worked amazing for classification was to create a new embedding for each class containing the average embedding of that class. This really boosted accuracy.
Another accuracy booster has been adding a simple FFNN with Tanh outputs onto the stack, doing supervised learning, and transforming the embeddings that way. Again, this is for classification. Training a NN on a small dataset is essentially going to rebias the original sentence transformer away from generality, but, for a known number of labels, that's ok.
Please others, report what works/doesn't work well for you to squeeze more out of text embeddings!

I still don't understand why the relative rankings are fine,
From my understanding, relative rankings will only tell what is more similar and what is less similar.
But how to filter out the irrelevant ones?
For example:
There are 5 passages.  Only 1 of them are relevant. but other 4 are not relevant.
I want to only have 1 result and filter out the rest (which are not relevant).
Or even worse case scenario. All of them are not relevant.
There should be nothing returned as relevant.
How to do that?

@aalinazar to put a finer point on it, if your document pool has 3 matches, search should surface 3 matches. If it has 100 matches, then 100. 0 then 0. Otherwise we place an arbitrary threshold on the search.
These models can't handle that, but I recall reading somewhere about " flows" you can use during training to encourage cos_sim to go to 0 for dissimilar items. Please let me know if you end up solving this!

@aalinazar I totally agree, relative scoring is still a problem if you need a threshold, otherwise you can get irrelevant results.
Right now I'm using models from SBert but they have small context size and wanted a larger context size.
BTW OpenAI embedding also has the same issue.
Were you able to solve this?

does anybody has any ideas to try out for this issue? I am also facing the similar issue where I dont want irrelevant results in my output.


loss and grad_norm are NaN

When training on my own dataset (including mini-imagenet), both loss and grad_norm will become NaN after several iterations (with a batch size of 32 for two card training in various model configurations). Have you encountered a similar problem, or do you have any possible solutions? Is it possible that the batch size is too small? Thank you!

When SSM_FORWARDTYPE='v2 ', the forward function is self. forward_core=partial (self. forward_corev2, force_fp32=True, SelectiveScan=SelectiveScanCore).  So before inputting into SS2D, the relevant tensors were already of float32 type, but I still encountered this problem.
According to my understanding, setting SSM_FORWARDTYPE to v2 or v3 should not be considered as the model you mentioned ‘use fp16 selective scan’, so this issue should not exist.

When I encountered NaN in training, I would try figuring out where the NaN or Inf first come into place, and check what operation results in the error.
I hope these suggestions will help you.

Hello! I met the same problem. Have you solved the problem yet?


[Search] Migrate documentation comments to TSDoc

Run rushx lint to see if the linting report has complains about comments. Fix issues by following the tags syntax: https://tsdoc.org/pages/tags/alpha/

Closing as this got resolved in #13060


[Bug]: API client is incorrectly configured for remote use

Contact Details
No response
What happened?
The API client is configured for localhost:8000, which won't work when tunarr is on another machine.
https://github.com/chrisbenincasa/tunarr/blob/8858db40d0cfc4b6e5908fffb9fcf744f33b9461/web/src/external/api.ts#L356
Version
0.1.0
What browser did you experience the the problem on?
No response
What operating system are you using?
No response
Relevant log output
No response

Yea, this makes some assumptions at the moment -- namely that the webapp is running alongside the backend. I think there is a bit of a larger effort here to allow for configuring the endpoint client-side and saving that to your local storage (like we do with dark mode)

Maybe I'm not describing this correctly - when I view the guide page on a remote system, my browser tries to hit localhost:8000 for lineups, version, events and they all fail.

The API client is configured for localhost:8000, which won't work when tunarr is on another machine.

What I mean here is that the API client will not work when tunarr (backend and frontend - in my case one docker container) are on a different machine than the browser you use to access tunarr.

Yep I understand! Opened https://github.com/chrisbenincasa/tunarr/issues/326 as a more generalized tracking bug.


Add new logos

SauceLabs is a user of standard. Just confirmed it myself.

I also noticed these new users:

Aragon
Automattic
Fastify
GoDaddy
Heroku
Scuttlebutt
Solid (Tim Berners Lee's project)
WebStorm

Fixed by: https://github.com/standard/standard/commit/b8c7b331b2c534be8d57d5dbd7caac23a0a907e7


Incomplete regular expression WORKFORCE_AUDIENCE_PATTERN

My repository( (hankei6km/gdrive-act-share ) contains the code that bundles googleapis/google-auth-library-nodejs. And my repositry is enabled CodeQL.
CodeQL has detected that it has not escaped the meta-character.

This string, which is used as a regular expression here, has an unescaped '.' before 'googleapis.com/locations/', so it might match more hosts than expected.

https://github.com/googleapis/google-auth-library-nodejs/blob/54cfaaf5a44070fa12fb2a3ba5d7d1549d780c42/src/auth/baseexternalclient.ts#L61-L62
Environment details

OS: Docker Container(mcr.microsoft.com/vscode/devcontainers/typescript-node:16-bullseye)
Node.js version: v16.14.0
npm version: 8.3.1
google-auth-library version<EMAIL_ADDRESS>
Steps to reproduce
I checked it in the cloned repository.
I Added //iam.googleapisXcom/locations/global/workforcePools/workloadPools/providers/oidc to this test.
it('should not throw on valid service account impersonation url', () => {

})

https://github.com/hankei6km/test-google-auth-library-nodejs/blob/b5f091b2b304645e7039e6eb778130ad88fb6842/test/test.baseexternalclient.ts#L285-L286
It was not thrown.
https://github.com/hankei6km/test-google-auth-library-nodejs/runs/5672358984?check_suite_focus=true#step:8:820
After fixing it, it was thrown.
const WORKFORCE_AUDIENCE_PATTERN =
  '//iam\\.googleapis\\.com/locations/[^/]+/workforcePools/[^/]+/providers/.+';

https://github.com/hankei6km/test-google-auth-library-nodejs/blob/7fd8372539d77c69552848c1e3e95d76d44a8e30/src/auth/baseexternalclient.ts#L60-L62

Thanks for filing! I've created a PR to resolve.


max_age::Duration type to replace time crate’s.

This PR introduces a max_age::Duration type to use with Cookie::max_age (& related). It is part of an effort to resolve #109, and a building block towards making #213 truly additive.
I opted for a new type, rather than using std::time::Duration, because the latter is just far larger (u64 seconds instead of u32) and far more precise (nanoseconds) than what’s arguably needed for the purpose of cookies (see the new type’s docs for full motivation). @SergioBenitez, if you instead prefer std::time::Duration here I’m perfectly happy to make that change (I could add some conveniences like from_mins & as_hours in a max_age::DurationExt trait).
If we do go ahead with this max_age::Duration type I can add some more of the typical operator trait implementations (Add, Sub, etc.) and arithmetic methods (checked_add, saturating_add, etc.).
One downside of this change with respect to time::Duration I’d like to note here is that the set_max_age methods that take an impl Into<max_age::Duration> no longer work with a plain time::Duration — instead of .set_max_age(time_duration) users would need to call e.g. .set_max_age(Some(time_duration.into())) (i.e. converting into max_age::Duration and wrapping in a Some).

Hey! Thanks for doing this. I'm really looking forward to getting something like this merged.

I opted for a new type, rather than using std::time::Duration, because the latter is just far larger (u64 seconds instead of u32) and far more precise (nanoseconds) than what’s arguably needed for the purpose of cookies (see the new type’s docs for full motivation). @SergioBenitez, if you instead prefer std::time::Duration here I’m perfectly happy to make that change (I could add some conveniences like from_mins & as_hours in a max_age::DurationExt trait).

While it's nice to optimize for size, I don't think it's a strong enough argument for us to reimplement functionality available elsewhere. While this type might be relatively simple to reimplement, implementing DateTime functionality will be anything but, and in general I consider implementing anything time-related outside the scope of this crate. And if we use an external crate to implement our internal DateTime, then we win nothing by implementing Duration ourselves.
My suggestion would be to pick one of chrono or time and build our types around those. IE:
pub mod time {
    pub struct DateTime(chrono::DateTime<chrono::Utc>);

    pub struct Duration(chrono::Duration);

    #[cfg(feature = "chrono")]
    impl<T> From<chrono::DateTime<T>> for DateTime<T> { .. }

    #[cfg(feature = "time")]
    impl From<time::OffsetDateTime> for DateTime<T> { .. }
}

Which one we pick I'm open to.  Are they more often depending on time or chrono?
See which one is being used more in the wild (dependents, downloads/time, big crates, etc.).
See which one results in cookie compiling faster.
See which one makes our implementation more robust/simpler.

My guess is that the answer to most of these is chrono, except for the final one where you'd need to take a closer look. If it's clear one or the other makes our implementation significantly more simple or less error-prone (i.e, consider panics - we definitely want to not panic, ever.), we should go with that one.

Glad to get positive feedback! Sure thing, I’ll refactor and use an existing Duration type.
To peek ahead a little, this is essentially what I’ve done with the DateTime type on a branch I’ve been working on that iterates on #213, where I’m either using time::OffsetDateTime or chrono::DateTime<chrono::FixedOffset> depending on which feature is enabled, and using the former if both are enabled (in that case the chrono feature basically only provides some conversions for convenience):
#[cfg(any(feature = "time", feature = "chrono"))]
pub mod expiration {
    pub struct DateTime(
        #[cfg(feature = "time)]
        time::OffsetDateTime,
        #[cfg(all(feature = "chrono", not(feature = "time")))]
        chrono::DateTime<chrono::FixedOffset>,
    );
}

If it’s OK with you, I’ll do something similar with Duration — use the type from either time or chrono if either or both of those features are enabled, and otherwise fall back to std::time::Duration so that at least the Max-Age parameter can still be used:
pub mod max_age {
    pub struct Duration(
        #[cfg(not(any(feature = "time", feature = "chrono"))]
        std::time::Duration,
        #[cfg(feature = "time")]
        time::Duration,
        #[cfg(all(feature = "chrono", not(feature = "time")))]
        chrono::Duration,
    );
}

To peek ahead a little, this is essentially what I’ve done with the DateTime type on a branch I’ve been working on that iterates on #213, where I’m either using time::OffsetDateTime or chrono::DateTime<chrono::FixedOffset> depending on which feature is enabled, and using the former if both are enabled (in that case the chrono feature basically only provides some conversions for convenience):

Nice! This is pretty neat.
My suggestion is similar, with the caveat that I was suggesting having no wrapper methods of any kind. Instead, just re-export time and/or chrono and provide only the From impls. This is fairly similar to what we have today, except of course that today there is no chrono option.
The other difference is that I was suggesting always using one of the two, and converting to the other. In other words, choosing one of them to be our "native" representation and the other as a foreign conversion: the struct would always contain the native type, irrespective of enabled features, and we'd convert as needed. The advantage here is a much simpler and less error-prone implementation: we don't have to write and test functionality we use internally twice. The disadvantage is that if a consumer enables only the foreign feature, both crates will be compiled in.
I think we can take a hybrid approach that largely negates the disadvantages I present above:
enum DateTime {
    #[cfg(feature = "chrono")]
    Chrono(chrono::DateTime<Utc>),
    #[cfg(feature = "time")]
    Time(time::OffsetDateTime),
}

This way, there's never any conversion from one type to the other necessary. We still need to write the functionality we use internally twice, but even then we should have more clarity.
To summarize:

Use an enum as above.
Distill internal usage of date/time in cookie into a private API that multiplexes based on the enabled features. For example, the parse_date()  function in parse.rs should become a method of DateTime, with the four calls in parse_inner() rolled into that method, implemented twice, and then called from parse_inner().
For tests, choose whichever, and then just cfg gate the test appropriately. We should never see any cfg!() related to time outside of this internal time module.
The only public API should be via From and Into impls, and perhaps PartialEq, Eq, Hash, etc. as needed. Everything else should be done by the client via the native time and chrono types.

Using this outside of cookie would look like:
use cookie::time;
use cookie::chrono;

let a = Cookie::build("foo", "bar").expires(time::OffsetDateTime::now_utc());
let b = Cookie::build("foo", "bar").expires(chrono::Utc::now());
assert_eq!(a, b);

Also, you can use this trick to group all the of the respective impls:
#[cfg(feature = "chrono")]
mod chrono_impls {
    use super::*;

    impl From<chrono::Foo> for DateTime { .. }

    impl From<DateTime> for chrono::Foo {
        fn from(v: DateTime) -> chrono::Foo {
            match v {
                DateTime::Chrono(v) => v,
                #[cfg(feature = "time")]
                DateTime::Time(v) => chrono::Foo::from(v.timestamp()).utc(),
            }
        }
    }

    impl PartialEq<chrono::Foo> for DateTime { .. }
    impl PartialOrd<chrono::Foo> for DateTime { .. }

    fn parse_cookie_date(..) -> Result<Self> { .. }
}

#[cfg(feature = "time")]
mod time_impls {
    use super::*;

    impl From<time::Foo> for DateTime { .. }
    impl From<DateTime> for time::Foo { .. }
    impl PartialEq<time::Foo> for DateTime { .. }
    impl PartialOrd<time::Foo> for DateTime { .. }

    fn parse_cookie_date(..) -> Result<Self> { .. }
}

#[cfg(any(feature = "time", feature = "chrono"))]
impl DateTime {
    pub(crate) fn parse_cookie_date(string: &str) -> Result<Self> {
        #[cfg(all(feature = "time", not(feature = "chrono")))]
        chrono_impl::parse_cookie_date(string)

        #[cfg(all(feature = "chrono", not(feature = "time")))]
        time_impl::parse_cookie_date(string)

        #[cfg(all(feature = "chrono", feature = "time"))]
        chrono_impl::parse_cookie_date(string)
    }
}

Was coding up those last two commits while you made that last comment, causing a bit of cross-talk there… what you’re suggesting sounds good after a quick read! I’ll dig deeper once I can get back to this.

if a consumer enables only the foreign feature, both crates will be compiled in.

This is the one thing I wanted to avoid, but I think that’s achievable using your enum.

I’ve pushed more changes both to this PR and to the chrono-additive branch. Right now I’m pretty happy with where I’ve been able to take things, but I’m hitting one final hiccup: I can’t get the Cookie::build("foo", "bar").expires(time/chrono::…) syntax to work.
The problem is that there is already that impl<T: Into<Option<DateTime>>> From<T> for Expiration { … } that conflicts with any of my attempts to do something like impl<T: Into<DateTime>> From<T> for Expiration { … }. I can see two ways around it: either remove that former impl (and require .set_expires(Expiration::Session) instead of .set_expires(None)), or add set_expires_datetime<T: Into<DateTime>>(…) methods (to Cookie and CookieBuilder. Or maybe you see another way?
By the way, you’ll note that I haven’t yet done much of the refactoring you suggested (the mod time/chrono_impl { … }, or the enum DateTime { … }, etc.). I don’t think it’ll help us with the mentioned hiccup, and if we do resolve that the result is essentially working. Part of me feels the refactoring might be a lot of work for little gain (i.e. just cosmetic code changes). Please let me know how important it would be to you (and if you might be willing to take it on yourself?).

I spent some time coming up with a "scaffold" of sorts for how I think this should be implemented. Please check out the time-chrono branch.

Closing due to inactivity.


[BUG] --debug not working?!

Describe the bug
following the raspibolt guide command with --debug in the systemctl startup script is not working. took some time to figure out ^^
checked with your guide and found that enabling Debug=true in .env didn't help also.
2024-04-18 23:53:52.077 | DEBUG    | lnbits.settings:<module>:531 - lnbits_allow_new_accounts: True
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/lnbits/.cache/pypoetry/virtualenvs/lnbits-Me3QFGJB-py3.9/lib/python3.9/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
  File "/home/lnbits/.cache/pypoetry/virtualenvs/lnbits-Me3QFGJB-py3.9/lib/python3.9/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
  File "/home/lnbits/.cache/pypoetry/virtualenvs/lnbits-Me3QFGJB-py3.9/lib/python3.9/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/lnbits/.cache/pypoetry/virtualenvs/lnbits-Me3QFGJB-py3.9/lib/python3.9/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
  File "/home/lnbits/.cache/pypoetry/virtualenvs/lnbits-Me3QFGJB-py3.9/lib/python3.9/site-packages/click/decorators.py", line 33, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/home/lnbits/lnbits/lnbits/server.py", line 65, in main
    config = uvicorn.Config(
TypeError: __init__() got an unexpected keyword argument 'debug'

To Reproduce
Steps to reproduce the behavior:

Go to this point in your guide
run poetry run lnbits --port 9000 --host <IP_ADDRESS> --debug
See error above

Expected behavior
it should work and give me more output
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

LNbits version: 0.12.5

hello! debug should be used within the .env just set DEBUG=true


When the content in the tabs component is a component, the content component will be rendered n times (n equals the number of items)

Environment
"nuxt": "^3.11.2",
"@nuxt/ui": "^2.17.0"
Version
3.11.2
Reproduction
https://stackblitz.com/edit/nuxt-starter-cqb61v
Description
When the content in the tabs component is a component, the content component will be rendered n times (n equals the number of items)
Additional context
No response
Logs
No response

Hi @wyf1992
Have you tried something like this? I believe the <template #item> is intended as the slot for each item in the list:
  <UTabs
    :items="tabItems"
    v-model="selected"
    @change="onChange"
    :default-index="0"
    class="flex flex-col items-center"
  >
  </UTabs>
  <component :is="compTabs[selected]"></component>


Sets Envoy Proxy Image to v1.25

Hardcodes the proxy image to v1.25. This should be automated for future releases.
xref: #957
Signed-off-by: danehans<EMAIL_ADDRESS>

Codecov Report

Merging #958 (f845cb0) into main (a3a80d3) will increase coverage by 0.02%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #958      +/-   ##
==========================================
+ Coverage   62.07%   62.09%   +0.02%
==========================================
  Files          55       55
  Lines        8546     8546
==========================================
+ Hits         5305     5307       +2
+ Misses       2886     2884       -2
  Partials      355      355

Impacted Files
Coverage Δ

internal/ir/infra.go
63.82% <ø> (ø)

internal/provider/kubernetes/helpers.go
80.40% <0.00%> (-0.68%)
:arrow_down:

internal/provider/kubernetes/controller.go
50.90% <0.00%> (+0.33%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Delay applying 'slick-active' & 'slick-current' classes

There seems to be a delay applying the current and active classes when reaching the last slide and using the infinite option. This creates an issue if there are css animations depending on this classes.
Video example: http://bit.ly/2AkXU5v

Have the same Issue: #3259


Types and event.target.files

Hey everyone,
I'm trying to statically type a change event handler on a file input. My JavaScript looks like this:
const getFileFrom = (element: HTMLInputElement): Promise<File> =>
    new Promise((resolve, reject) => {
        element.addEventListener('change', (event: Event & { target: HTMLInputElement }) => {
            resolve(event.target.files[0]);
        });
    });

However I get this, semi cryptic error message:
[flow] call of method addEventListener (Function cannot be called on any member of intersection type intersection Member 1: function type Error: string This type is incompatible with the expected param type of string enum Member 2: function type Error: string This type is incompatible with the expected param type of string enum Member 3: function type Error: string This type is incompatible with the expected param type of string enum Member 4: function type Error: string This type is incompatible with the expected param type of string enum Member 5: function type Error: string Expected string literal wheel, got change instead string literal wheel Member 6: function type Error: string This type is incompatible with the expected param type of string enum Member 7: function type Error: string This type is incompatible with the expected param type of string enum Member 8: function type Error: string This type is incompatible with the expected param type of string enum Member 9: function type Error: function This type is incompatible with union: object type | EventHandler)
Looking through the flow source, I can't seem to find any example of what I'm trying to do. Does anyone else have experience with this? Any help is greatly appreciated, thanks!

I am on v0.49.1 and I'm also unable to figure out how to use event.target in event listeners without triggering Flow errors. Can't seem to figure out any configuration that doesn't trigger errors. Some documentation about this would be very nice.

I declared it like this:
(event: UIEvent & { target: HTMLInputElement & { files: Array<string> } })

@Satyam  it still trigger errors. Im using version 0.60.1

@MarcoNicolodi Sorry I can't help.  I gave up on Flow. One reason it didn't complain on my supposed fix was that Flow had bailed out earlier, which led me to assume I got this right.
I also tried: event: SyntheticInputEvent<> and it seemed to work, though it might be due to the same failure to report.

This seemed to work for me: event: SyntheticInputEvent<HTMLInputElement> :+1:

Hey everyone,
I'm trying to statically type a change event handler on a file input. My JavaScript looks like this:
const getFileFrom = (element: HTMLInputElement): Promise<File> =>
    new Promise((resolve, reject) => {
        element.addEventListener('change', (event & { target: HTMLInputElement }) => {
            resolve(event.target.files[0]);
        });
    });

However I get this, semi cryptic error message:
[flow] call of method addEventListener (Function cannot be called on any member of intersection type intersection Member 1: function type Error: string This type is incompatible with the expected param type of string enum Member 2: function type Error: string This type is incompatible with the expected param type of string enum Member 3: function type Error: string This type is incompatible with the expected param type of string enum Member 4: function type Error: string This type is incompatible with the expected param type of string enum Member 5: function type Error: string Expected string literal wheel, got change instead string literal wheel Member 6: function type Error: string This type is incompatible with the expected param type of string enum Member 7: function type Error: string This type is incompatible with the expected param type of string enum Member 8: function type Error: string This type is incompatible with the expected param type of string enum Member 9: function type Error: function This type is incompatible with union: object type | EventHandler)
Looking through the flow source, I can't seem to find any example of what I'm trying to do. Does anyone else have experience with this? Any help is greatly appreciated, thanks!

Don't put the type of event


basic image - works fine. Is there a way to make the rendering faster somehow? It's not a huge issue though, so this is mostly just feedback

Hey there Andy,
I just tested the display of an image, based on the plenty
examples you offer.
I managed to get this to work on the first run \o/
Image screenshot:
https://i.imgur.com/xyVUCFQ.png
(Yes, this is unfinished; I just copy/pasted form.rb
and modified it ... I just wanted to see whether I can
get it to work and I can, which is good! I am a noob
tester; if I can get it to work others can as
well. :D)
Anyway I'll continue with this, but there is one thing
I noticed that is ... hmm, not a problem, but perhaps
not perfect either.
You mentioned that in the comments, that this is slow.
And indeed, on a re-draw, it takes a few seconds before
it is re-rendered.
The testing code I used was something along those
lines:
this_image = '/home/x/programming/ruby/src/backup_paradise/lib/backup_paradise/images/BACKUP_IMAGE.png'
area {
  on_draw { |area_draw_params|
    image(this_image, 96, 96)
  }
}

So, not sure if it can be made faster. But if you
have some idea, perhaps you could either add an
example or show how to fast-render an image if that
is possible. It works for my use cases already (I
only need a simple image to give a visual cue to
the elderly person on windows ... I have not tested
it on windows yet but will do so later, or tomorrow.
First I have to finish the rest) - but of course
nobody minds more speed.
I had a look at basic_image5.rb too
https://github.com/AndyObtiva/glimmer-dsl-libui/blob/master/examples/basic_image5.rb
and it uses ChunkyPNG which I suppose I could use as
well. But right now I don't know whether this approach
my be faster. If it is then perhaps I would use it,
but as I don't know right now I just stick to area {}
and image().
Perhaps at a later time I may look at basic_table_image.rb
and use a table-layout instead anyway. But right now
I just keep it simple: a single image.
If there are faster alternatives then this would be great
of course, but for my use case it suffices as-is. I can
designate the initial window size as-is via window()
so that's not a problem; resizing doesn't need to be
done. I can just add a link from the desktop on Win10
to the ruby application; I know that this works because
I tested it before on my win10 laptop. \o/
Pretty cool that libui works well on windows - that is
actually even simpler than web-apps too, because I'd
have to set up a webserver or add a lot of javascript
which I don't want to do on other people's win10
computers.

Actually, I could perhaps use your Computer Science computational geometry knowledge to help me with this.
The main issue is that libui does not natively support images/pixels yet, so in order to draw an image on an area, you need to specify the colors of "each pixel", meaning thousands, but for bigger images, millions. Now, to do that with libui, you would have to construct a rectangle per pixel since it does not have a pixel construct alternative. That means, it has to process millions of structs (and in Ruby, objects) for bigger images.
One optimization I implemented to significantly decrease the number of rectangle objects rendered through libui was by looking into each scanline in an image and see if there were pixels that shared the same exact color value, and then grouping them together into one rectangle. That ended up cutting down the number of pixels from 9,216 for a 96x96 image to about 923 shapes to render as reported by examples/basic_image5.rb, which is doing the work of the image control manually.
Now, I worked very hard on trying to do a similar optimization by vertically, but grouping multiple scanlines or even similarly-colored pixels vertically. Unfortunately, the logic needed to calculate such similarity on the fly turned out to be such a processor intensive task that it negated the vertical optimization. As such, I only kept the horizontal pixels into lines optimization for now.
If you can come up with a better algorithm, I would be happy to add to Glimmer DSL for LibUI. The logic for the image control shapes is at the bottom of this file calculate_shapes method: https://github.com/AndyObtiva/glimmer-dsl-libui/blob/master/lib/glimmer/libui/control_proxy/image_proxy.rb
Otherwise, here are a few tips for your situation that should work for the time being:

Decrease the size of your image from 96x96 to something much smaller like 24x24
Remove the image and paint it with a few vector-graphics shapes utilizing area shapes and text like using circle and text/string.
Remove part of the image only that you could recreate with area shapes and text, and keep the part that is not easily recreatable like perhaps the "disks", which would superimpose on top of the shapes with a very tiny image for the "disks" alone.

I hope that was helpful. Let me know what works for you.


Have ShowUI work on NPUs

Given the increasing prevalence of NPUs for Windows AI computers. Could ShowUI be modified to use those instead of CUDA?

@khairm Thanks for comments, I am not sure as I am not familiar with NPU.
But I have found a post about how to run huggingface LLM on NPU: https://huggingface.co/blog/bconsolvo/llava-gemma-2b-aipc-npu.
As our model is also integrated into huggingface codebase.
I think you can try to refer this :)

Hi,
The repo specifies that CUDA is a requirement... Which I believe is NVIDIA only
A Neural Processing Unit (NPU) is a specialized computer chip that's designed to speed up artificial intelligence (AI) tasks, such as those involving.
New Intel, AMD and Qualcomm processors now have these alongside the usual CPUs and GPUs.


Upgrade to PHP 7.4

zip extension handling change based on https://stackoverflow.com/a/48700777/2803757


Python 3.x compatibility

Hi, I've run your code on Python 3.6; however; it showed the error
len() of unsized object numpy somewhere in Loader.py
In Python 2.x, it works well (except that show APIs are replaced in the newer version of Tensorflow - I have a plan to update the code).

Hello, I could try to fix it, can some one assign this to me?


My blog doesn't build with current master

I don't know if this helpful or not but it may help to spot what is going on.
I tried to build my blog with the current master,  the process blocked at some point and never finished and logs didn't show any error or warning message only the INFO ones.
I tried to go down several commits and reach one that I know that it had been working but it didn't either finish.
Because I did all this process with the new go release 1.6, I wanted to see if that also happened with 1.5.3 and I've realised that current master, with Go 1.5.3, finishes the process without any issue.
Do you have any idea what is happening?

This fits better on https://discuss.gohugo.io/

OK, I notice you mention "process being blocked" ... Reopen.

It is reproduced by using @ifraixedes blog source on my machine and found where it was blocked. https://github.com/spf13/hugo/blob/master/hugolib/site.go#L1372 is there. It sends an error via a channel but it is not listened by anywhere.
I forgot the related issue but in Go 1.6, template is treated more strictly and it causes a template error. I saw a following error in this investigation.
&errors.errorString{s:"html/template: cannot redefine \"_internal/shortcodes/ref.html\" after it has executed"}

The code itself could hit this problem but in Go 1.5 or earlier, it is luckily avoided.

The blocking issue is resolved in commit e985364 but it stops rendering the site with a template error. Need more investigation.

It's the `/content/rss/index.html' that makes this fail. I have questioned this logic before. I guess the solution is to create a clone of s.Tmpl before any execution, then use that in:
https://github.com/spf13/hugo/blob/master/hugolib/site.go#L1372

@bep, I agree with you. This is the issue discussed at #1470. And one more, shortcode templates are rendered before calling RenderPages() so any redefinition at https://github.com/spf13/hugo/blob/master/hugolib/site.go#L1372 may violate the redefinition rule introduced in golang/go@12dfc3b.
As you mentioned, one of the solution is creating clone before executing templates or if the IsRenderable check block is really unneeded today, just removing this also seems to be OK.

The IsRenderable is used by some (the blog in this issue is one), so a clone may be simplest.

I'm sorry but I don't have that much knowledge of the hugo code base to fully understand your discussion, so I cannot to contribute, so far, that much in fixes.
After e985364   as @tatsushid the blocking issues is solved, but the site still not rendering.
I've been investigating which was the problem and I found that it was complaining about one of the shortcuts that my theme has, whose name (youtube) collides with one provided by hugo.
I renamed it, but I'm still not able to render the site, because hugo collides with a default template which I override in the theme (themes/fraixedes/layouts/_default/list.html).
The error log message was:
Error building site: Error(s) rendering pages: html/template: cannot redefine "theme/_default/list.html" after it has executed

@ifraixedes as a temp fix until we get a fix out for this for GO 1.6 is to remove /content/rss/index.html.

OK, my changes broke a lots of test ... will have to revisit this later.


Introduce shoot webhook controller

How to categorize this issue?

/area ops-productivity
/kind enhancement
/priority normal
What would you like to be added:
@mandelsoft proposed to add a new controller (sitting in a dedicated component next to the Shoot's control plane), that will reconcile webhooks in the shoot, that will be problematic for different shoot operations (e.g. maintenance, hibernation, scale-up, ...). (ref https://github.com/gardener/gardener/issues/3122, https://github.com/gardener/gardener/pull/1642 and similar)
It should check all webhooks in the shoot, check if they are problematic and then either add

a namespaceSelector excluding the kube-system namespace

namespaceSelector:
  matchExpressions:
  - key: gardener.cloud/purpose
    operator: NotIn
    values:
    - kube-system

or an objectSelector excluding objects managed by gardener (labelled with origin=gardener) (only supported by k8s v1.16+, I think)

Endusers should be able to opt out of this behaviour, if they have setup their webhooks properly (multiple backing replicas, PDBs and so on), for example by adding a special label to the webhook.
The controller should also annotate the webhooks it touches and explain what was changed / how to opt out.
We might think about adding more controllers to this new component in the future, so we should keep this in mind (e.g. also for naming...).
Why is this needed:
We often see endusers configuring problematic webhooks, which lead to issues for the mentioned shoot operations causing a lot of ops effort. The gardener operator shouldn't be concerned with such problematic user behaviour, so we should invest into some kind of automation to workaround those problems.

I still believe that a shoot problem detector, analogue to the node problem detector, is a real and a more independent alternative to add such checks.

So, are you saying, that we shouldn't automatically add selectors to the problematic webhooks and just detect such webhooks and only put some additional conditions on the shoot?
Or is this only about the naming?

Yes, agreed, it makes sense to do it in a separate project and untangle it from the Gardener lifecycle. Again, already the naming (NPD and SPD) suggests that the approach proposed by @timuthy is right.

So, are you saying, that we shouldn't automatically add selectors to the problematic webhooks and just detect such webhooks and only put some additional conditions on the shoot?

Yes, only conditions because, mainly because:

We wouldn't need to touch the shoot owner's setup
We wouldn't need another exception / opt-out mechanism ("The controller should also annotate the webhooks it touches and explain what was changed / how to opt out.")
Components are free to decide how the condition is evaluated

In another chat including @rfranzke and @timuthy, we found that we are not sure, what would be the best approach for this. Both approaches have their pros and cons:
Option a:
We detect problematic webhooks and set special conditions (or constraints) in the Shoot's status (similar to what we have already in place with the current constraints) but don't act on the problematic webhooks, which is similar to the node-problem-detector.

+ We wouldn't need to touch the shoot owner's setup
+ We wouldn't need another exception / opt-out mechanism ("The controller should also annotate the webhooks it touches and explain what was changed / how to opt out.")
+ Components are free to decide how the condition is evaluated (e.g. Dashboard can show warning to the Shoot owners)
- Dashboard is an optional component and users might not get aware of the configuration problems in case the dashboard is not available to them

Option b:
We do a) and additionally "fix" the problematic webhook configurations by adding label selectors as proposed above.

+ problematic configs can be automatically resolved, leading to less ops effort
o can just act upon the condition/constraint from a) and thus be placed in a separate component/project/...

Notes regarding both options:

unclear, how to detect webhooks that are configured to include system-components on purpose: maybe the backing webhook server is setup properly and the webhook isn't actually problematic

Happy to hear some additional opinions!
@vlerenc @ialidzhikov @vpnachev @mandelsoft

In more syncs we decided to go for option b) and allow the users to opt-out of this automatism of they need it. The whole feature should be optional and it should also be possible to disable it entirely for a shoot or maybe even a project.

In more syncs we decided to go for option b) and allow the users to opt-out of this automatism of they need it. The whole feature should be optional and it should also be possible to disable it entirely for a shoot or maybe even a project.

Considering how much this problem is a nuisance to Gardener (see topic of VPN reversal where not even a proper web hook setup with PDBs and such would have helped...; then again, one could argue, that we could do the VPN reversal in two phases instead of one, which would be backward-compatible), and that all despite even Kubernetes' clear statement in https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/#avoiding-operating-on-the-kube-system-namespace, I would also welcome option b), though I see @timuthy 's point clearly.
Some thoughts:

Both topics, informing (a) and remediating (let's call it b'), should be separated, so that we can switch on the former and later the latter
To not break anything accidentally, we can put down into the "breaking changes" section that activating b' must be done with care (on our landscapes we can use the information from a to proactively approach all offenders before switching on b')
Then there is the topic of fighting controllers, ours vs. possibly an end user controller that both change the web hook configuration back and forth: here I would suggest to store in memory a hash of the original web hook configuration and not patch it again, if it was already seen with that hash in the past. It's not perfect, but if we shy away from something more persistent, it's already a huge relief in the sense that while the controller is running, it will modify a web hook configuration only once until it gets restarted, so we at least don't end up in a vicious cycle fighting over the web hook configuration and keeping the API server busy

Hope that makes sense or WDYT?

It looks like the community is working on a feature allowing some webhooks to work on other webhooks.
Then we can add a validating webhook for validating and mutating webhooks that will reject create/update requests if they are affecting resources in the kube-system namespace. Our validating webhook might have an object selector so that users can skip this validation if they put a well-known label.
The webhook itself can be a sidecar container to the kube-apiserver deployment similar to the current apiserver-proxy-pod-mutator
Ref:

https://github.com/kubernetes/kubernetes/issues/101794
https://github.com/kubernetes/kubernetes/pull/101815

/close since there are no plans to introduce such controller any more

@rfranzke Since this is an issue that is constantly causing trouble, what is the plan to help here? Gardener is sensitive to "wrong" web hooks, so what are we doing? Improving the UI https://github.com/gardener/dashboard/issues/1144 is then all we do or are there other tickets/plans?

The ticket is open since very long and nobody is currently working on it. Given this, the fact that there are doubts, and that I recently heard you saying (or writing) that "we don't want noisy" controllers, I decided to close the issue for now. Do you suggest to reopen it and implement such controller?
I think that the "webhook intercepting webhooks" feature linked by @vpnachev above would be a sustainable solution for our scenario, but unfortunately it seems the community closed the work on this topic (due to inactivity).

/reopen @Rafael Franzke suggested to now implement auto-remediation in the care controller as this is a really annoying problem. The condition will still reflect such broken web hooks, even if auto-remediated, so showing that condition prominently (in the Dashboard) is still desired to avoid ongoing races between "their" and "our" controllers around such misbehaving web hook configurations.

second attempt, reopen should be the right command
/reopen


Automatic caching of multi_index instances and a convenient way to get the appropriate multi_index instance

An alternative (and recommended) way for developers to get a reference to a multi_index instance in order to get access to the appropriate tables in EOSIO persistent state is to call an overloaded static member function get in the multi_index class which returns a reference to the appropriate multi_index instance.
If the multi_index::get(uint64_t code, uint64_t scope) overload is called, the function would return a const reference to the appropriate multi_index instance, which disallows (at compilation time) use of the emplace, modify, and erase methods  which could potentially modify the EOSIO persistent state.
If the multi_index::get(uint64_t scope) overload is called, the function would return a reference to the appropriate multi_index instance where the code was automatically selected to be the current receiver. This overload would be used when the developer wants to have a multi_index instance that allows them to modify the EOSIO persistent state, in which case they must be using the current receiver as the code anyway because they are not allowed to modify state in other code.
With this new interface of getting a reference to the appropriate multi_index instance, we can introduce convenient automatic caching of multi_index instances so that developers don't have to do it manually themselves (for example see the exchange contract). However, they would still be allowed to implement their own solution if they wish (although it wouldn't be the recommended path) since they would still be allowed to call the constructor of multi_index.

@wanderingbort @arhag @heifner I am pretty sure that this is either already incorporated and wasn't tracked or else it is OBE.  If I do not hear any thing I will presume that is the case.

@brianjohnson5972: No, this has not yet been implemented. Although it really belongs in eosio.cdt now so I am closing this issue anyway.


Breadcrumb updates

Moving some files to match updated folder structure for more accurate breadcrumbs

Docs Build status updates of commit 6eff658:
:clock10: Pending: waiting for processors (11 builds ahead of you)
:warning: Docs Build is busy, currently there are 11 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 6eff658:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/consume-packages/install-use-packages-powershell.md
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.md
:white_check_mark:Succeeded
View

docs/archive/project-json-archive.md
:white_check_mark:Succeeded
View

docs/consume-packages/Overview-and-Workflow.md
:white_check_mark:Succeeded
View

docs/consume-packages/install-use-packages-visual-studio.md
:white_check_mark:Succeeded
View

docs/consume-packages/media/ConsolidateTab.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/InstallPreviewDialog.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/ManagePackagesSolutionUICommand.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/ManagePackagesUICommand.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/Options.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerConsoleControls.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerConsoleControls1.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerConsoleControls2.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerConsoleControls3.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerConsoleInstall.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerUIAutoReferenced.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerUIOptions.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageSourceDropDown.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageSourceSettings.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/References.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/Search.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/SolutionPackagesUI.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/UninstallPackage.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/UpdatePackages.png
:white_check_mark:Succeeded
View

docs/create-packages/Creating-a-Package.md
:white_check_mark:Succeeded
View

docs/faqs/NuGet-FAQ.md
:white_check_mark:Succeeded
View

docs/hosting-packages/Local-Feeds.md
:white_check_mark:Succeeded
View

docs/hosting-packages/Overview.md
:white_check_mark:Succeeded
View

docs/install-nuget-client-tools.md
:white_check_mark:Succeeded
View

docs/quickstart/install-and-use-a-package-in-visual-studio.md
:white_check_mark:Succeeded
View

docs/release-notes/NuGet-1.4.md
:white_check_mark:Succeeded
View

docs/tools/PowerShell-Reference.md
:white_check_mark:Succeeded
View

docs/tools/nuget-exe-CLI-Reference.md
:white_check_mark:Succeeded
View

docs/tools/ps-ref-add-bindingredirect.md
:white_check_mark:Succeeded
View

docs/tools/ps-ref-find-package.md
:white_check_mark:Succeeded
View

docs/tools/ps-ref-get-package.md
:white_check_mark:Succeeded
View

docs/tools/ps-ref-get-project.md
:white_check_mark:Succeeded
View

docs/tools/ps-ref-install-package.md
:white_check_mark:Succeeded
View

docs/tools/ps-ref-open-packagepage.md
:white_check_mark:Succeeded
View

docs/tools/ps-ref-sync-package.md
:white_check_mark:Succeeded
View

docs/tools/ps-ref-uninstall-package.md
:white_check_mark:Succeeded
View

docs/tools/ps-ref-update-package.md
:white_check_mark:Succeeded
View

docs/what-is-nuget.md
:white_check_mark:Succeeded
View

docs/consume-packages/install-use-packages-powershell.md

Line 143: [Warning] Invalid file link:(~/consume-packages/nuget-exe-CLI-reference.md).
Line 170: [Warning] Invalid file link:(~/consume-packages/nuget-exe-cli-reference.md).
Line 14: [Suggestion] Illegal link: `<a href="#using-the-nugetexe-cli-in-the-console">Using the nuget.exe CLI in the console</a>` -- missing bookmark. The file consume-packages/install-use-packages-powershell.md doesn't contain a bookmark named using-the-nugetexe-cli-in-the-console.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit d15ef92:
:clock10: Pending: waiting for processors (20 builds ahead of you)
:warning: Docs Build is busy, currently there are 20 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit d15ef92:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/reference/cli-reference/cli-ref-config.md
:warning:Warning
View
Details

docs/reference/cli-reference/cli-ref-delete.md
:warning:Warning
View
Details

docs/reference/cli-reference/cli-ref-environment-variables.md
:warning:Warning
View
Details

docs/reference/cli-reference/cli-ref-install.md
:warning:Warning
View
Details

docs/reference/cli-reference/cli-ref-locals.md
:warning:Warning
View
Details

docs/reference/cli-reference/cli-ref-mirror.md
:warning:Warning
View
Details

docs/reference/cli-reference/cli-ref-pack.md
:warning:Warning
View
Details

docs/reference/cli-reference/cli-ref-push.md
:warning:Warning
View
Details

docs/reference/cli-reference/cli-ref-restore.md
:warning:Warning
View
Details

docs/reference/cli-reference/cli-ref-spec.md
:warning:Warning
View
Details

docs/reference/cli-reference/cli-ref-trusted-signers.md
:warning:Warning
View
Details

docs/reference/cli-reference/cli-ref-update.md
:warning:Warning
View
Details

docs/reference/ps-reference/ps-ref-add-bindingredirect.md
:warning:Warning
View
Details

docs/reference/ps-reference/ps-ref-find-package.md
:warning:Warning
View
Details

docs/reference/ps-reference/ps-ref-get-package.md
:warning:Warning
View
Details

docs/reference/ps-reference/ps-ref-get-project.md
:warning:Warning
View
Details

docs/reference/ps-reference/ps-ref-install-package.md
:warning:Warning
View
Details

docs/reference/ps-reference/ps-ref-open-packagepage.md
:warning:Warning
View
Details

docs/reference/ps-reference/ps-ref-register-tabexpansion.md
:warning:Warning
View
Details

docs/reference/ps-reference/ps-ref-sync-package.md
:warning:Warning
View
Details

docs/reference/ps-reference/ps-ref-uninstall-package.md
:warning:Warning
View
Details

docs/reference/ps-reference/ps-ref-update-package.md
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.md
:white_check_mark:Succeeded
View

docs/api/overview.md
:white_check_mark:Succeeded
View

docs/archive/project-json-archive.md
:white_check_mark:Succeeded
View

docs/consume-packages/Finding-and-Choosing-Packages.md
:white_check_mark:Succeeded
View

docs/consume-packages/Overview-and-Workflow.md
:white_check_mark:Succeeded
View

docs/consume-packages/Package-Restore.md
:white_check_mark:Succeeded
View

docs/consume-packages/Reinstalling-and-Updating-Packages.md
:white_check_mark:Succeeded
View

docs/consume-packages/configuring-nuget-behavior.md
:white_check_mark:Succeeded
View

docs/consume-packages/install-use-packages-dotnet-cli.md
:white_check_mark:Succeeded
View

docs/consume-packages/install-use-packages-nuget-cli.md
:white_check_mark:Succeeded
View

docs/consume-packages/install-use-packages-powershell.md
:white_check_mark:Succeeded
View

docs/consume-packages/install-use-packages-visual-studio.md
:white_check_mark:Succeeded
View

docs/consume-packages/installing-signed-packages.md
:white_check_mark:Succeeded
View

docs/consume-packages/managing-the-global-packages-and-cache-folders.md
:white_check_mark:Succeeded
View

docs/consume-packages/media/ConsolidateTab.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/InstallPreviewDialog.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/ManagePackagesSolutionUICommand.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/ManagePackagesUICommand.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/Options.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerConsoleControls.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerConsoleControls1.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerConsoleControls2.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerConsoleControls3.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerConsoleInstall.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerUIAutoReferenced.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerUIOptions.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageSourceDropDown.png
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.

docs/reference/cli-reference/cli-ref-config.md

Line 14: [Warning] Invalid file link:(~/reference/reference/nuget-config-file.md).
Line 14: [Warning] Invalid file link:(~/reference/consume-packages/configuring-nuget-behavior.md).
Line 25: [Warning] Invalid file link:(~/reference/reference/nuget-config-file.md).

docs/reference/cli-reference/cli-ref-delete.md

Line 14: [Warning] Invalid file link:(~/reference/nuget-org/policies/deleting-packages.md).

docs/reference/cli-reference/cli-ref-environment-variables.md

Line 17: [Warning] Invalid file link:(~/reference/reference/msbuild-targets.md#restore-properties).
Line 26: [Warning] Invalid file link:(~/reference/consume-packages/managing-the-global-packages-and-cache-folders.md).
Line 28: [Warning] Invalid file link:(~/reference/consume-packages/managing-the-global-packages-and-cache-folders.md).
Line 35: [Warning] Invalid file link:(~/reference/reference/errors-and-warnings/NU3028.md).

docs/reference/cli-reference/cli-ref-install.md

Line 19: [Warning] Invalid file link:(~/reference/consume-packages/configuring-nuget-behavior.md).
Line 47: [Warning] Invalid file link:(~/reference/consume-packages/managing-the-global-packages-and-cache-folders.md).
Line 52: [Warning] Invalid file link:(~/reference/consume-packages/package-restore.md).
Line 54: [Warning] Invalid file link:(~/reference/consume-packages/configuring-nuget-behavior.md).

docs/reference/cli-reference/cli-ref-locals.md

Line 14: [Warning] Invalid file link:(~/reference/consume-packages/managing-the-global-packages-and-cache-folders.md).
Line 45: [Warning] Invalid file link:(~/reference/consume-packages/managing-the-global-packages-and-cache-folders.md).

docs/reference/cli-reference/cli-ref-mirror.md

Line 29: [Warning] Invalid file link:(~/reference/hosting-packages/nuget-server.md).
Line 37: [Warning] Invalid file link:(~/reference/consume-packages/managing-the-global-packages-and-cache-folders.md).

docs/reference/cli-reference/cli-ref-pack.md

Line 14: [Warning] Invalid file link:(~/reference/reference/msbuild-targets.md).
Line 47: [Warning] Invalid file link:(~/reference/create-packages/Symbol-Packages-snupkg.md).
Line 47: [Warning] Invalid file link:(~/reference/create-packages/Symbol-Packages.md).

docs/reference/cli-reference/cli-ref-push.md

Line 15: [Warning] Invalid file link:(~/reference/api/nuget-protocols.md).
Line 19: [Warning] Invalid file link:(~/reference/consume-packages/configuring-nuget-behavior.md).
Line 40: [Warning] Invalid file link:(~/reference/consume-packages/configuring-nuget-behavior.md).

docs/reference/cli-reference/cli-ref-restore.md

Line 38: [Warning] Invalid file link:(~/reference/consume-packages/managing-the-global-packages-and-cache-folders.md).
Line 45: [Warning] Invalid file link:(~/reference/consume-packages/package-restore.md).
Line 47: [Warning] Invalid file link:(~/reference/consume-packages/configuring-nuget-behavior.md).

docs/reference/cli-reference/cli-ref-spec.md

Line 14: [Warning] Invalid file link:(~/reference/create-packages/creating-a-package.md).

docs/reference/cli-reference/cli-ref-trusted-signers.md

Line 15: [Warning] Invalid file link:(~/reference/reference/nuget-config-file.md).

Line 41: [Warning] Invalid file link:(~/reference/reference/nuget-config-file.md#config-section).

docs/reference/ps-reference/ps-ref-open-packagepage.md

Line 12: [Warning] Invalid file link:(~/reference/consume-packages/install-use-packages-powershell.md).

docs/reference/ps-reference/ps-ref-register-tabexpansion.md

Line 12: [Warning] Invalid file link:(~/reference/ps-reference/package-manager-console.md).

docs/reference/ps-reference/ps-ref-sync-package.md

Line 12: [Warning] Invalid file link:(~/reference/consume-packages/install-use-packages-powershell.md).
Line 35: [Warning] Invalid file link:(~/reference/reference/nuget-config-file.md#config-section).

docs/reference/ps-reference/ps-ref-uninstall-package.md

Line 12: [Warning] Invalid file link:(~/reference/consume-packages/install-use-packages-powershell.md).

docs/reference/ps-reference/ps-ref-update-package.md

Line 12: [Warning] Invalid file link:(~/reference/consume-packages/install-use-packages-powershell.md).
Line 41: [Warning] Invalid file link:(~/reference/consume-packages/reinstalling-and-updating-packages.md).
Line 43: [Warning] Invalid file link:(~/reference/reference/nuget-config-file.md#config-section).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 05c2d1a:
:clock10: Pending: waiting for processors (24 builds ahead of you)
:warning: Docs Build is busy, currently there are 24 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 05c2d1a:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/reference/ps-reference/ps-ref-install-package.md
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.md
:white_check_mark:Succeeded
View

docs/api/overview.md
:white_check_mark:Succeeded
View

docs/archive/project-json-archive.md
:white_check_mark:Succeeded
View

docs/consume-packages/Finding-and-Choosing-Packages.md
:white_check_mark:Succeeded
View

docs/consume-packages/Overview-and-Workflow.md
:white_check_mark:Succeeded
View

docs/consume-packages/Package-Restore.md
:white_check_mark:Succeeded
View

docs/consume-packages/Reinstalling-and-Updating-Packages.md
:white_check_mark:Succeeded
View

docs/consume-packages/configuring-nuget-behavior.md
:white_check_mark:Succeeded
View

docs/consume-packages/install-use-packages-dotnet-cli.md
:white_check_mark:Succeeded
View

docs/consume-packages/install-use-packages-nuget-cli.md
:white_check_mark:Succeeded
View

docs/consume-packages/install-use-packages-powershell.md
:white_check_mark:Succeeded
View

docs/consume-packages/install-use-packages-visual-studio.md
:white_check_mark:Succeeded
View

docs/consume-packages/installing-signed-packages.md
:white_check_mark:Succeeded
View

docs/consume-packages/managing-the-global-packages-and-cache-folders.md
:white_check_mark:Succeeded
View

docs/consume-packages/media/ConsolidateTab.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/InstallPreviewDialog.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/ManagePackagesSolutionUICommand.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/ManagePackagesUICommand.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/Options.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerConsoleControls.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerConsoleControls1.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerConsoleControls2.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerConsoleControls3.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerConsoleInstall.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerUIAutoReferenced.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerUIOptions.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageSourceDropDown.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageSourceSettings.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/References.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/Search.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/SolutionPackagesUI.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/UninstallPackage.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/UpdatePackages.png
:white_check_mark:Succeeded
View

docs/create-packages/Creating-a-Package.md
:white_check_mark:Succeeded
View

docs/create-packages/Prerelease-Packages.md
:white_check_mark:Succeeded
View

docs/create-packages/Sign-a-Package.md
:white_check_mark:Succeeded
View

docs/faqs/NuGet-FAQ.md
:white_check_mark:Succeeded
View

docs/hosting-packages/Local-Feeds.md
:white_check_mark:Succeeded
View

docs/hosting-packages/NuGet-Server.md
:white_check_mark:Succeeded
View

docs/hosting-packages/Overview.md
:white_check_mark:Succeeded
View

docs/install-nuget-client-tools.md
:white_check_mark:Succeeded
View

docs/quickstart/create-and-publish-a-package-using-visual-studio-net-framework.md
:white_check_mark:Succeeded
View

docs/quickstart/create-and-publish-a-package-using-visual-studio.md
:white_check_mark:Succeeded
View

docs/quickstart/install-and-use-a-package-in-visual-studio.md
:white_check_mark:Succeeded
View

docs/reference/PowerShell-Reference.md
:white_check_mark:Succeeded
View

docs/reference/Signed-Packages-Reference.md
:white_check_mark:Succeeded
View

docs/reference/cli-reference/cli-ref-add.md
:white_check_mark:Succeeded
View

docs/reference/cli-reference/cli-ref-config.md
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.

docs/reference/ps-reference/ps-ref-install-package.md

Line 41: [Warning] Invalid file link:(~/reference/reference/nuget-config-file.md#config-section).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 0d6fbd4:
:clock10: Pending: waiting for processors (24 builds ahead of you)
:warning: Docs Build is busy, currently there are 24 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 0d6fbd4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.md
:white_check_mark:Succeeded
View

docs/api/overview.md
:white_check_mark:Succeeded
View

docs/archive/project-json-archive.md
:white_check_mark:Succeeded
View

docs/consume-packages/Finding-and-Choosing-Packages.md
:white_check_mark:Succeeded
View

docs/consume-packages/Overview-and-Workflow.md
:white_check_mark:Succeeded
View

docs/consume-packages/Package-Restore.md
:white_check_mark:Succeeded
View

docs/consume-packages/Reinstalling-and-Updating-Packages.md
:white_check_mark:Succeeded
View

docs/consume-packages/configuring-nuget-behavior.md
:white_check_mark:Succeeded
View

docs/consume-packages/install-use-packages-dotnet-cli.md
:white_check_mark:Succeeded
View

docs/consume-packages/install-use-packages-nuget-cli.md
:white_check_mark:Succeeded
View

docs/consume-packages/install-use-packages-powershell.md
:white_check_mark:Succeeded
View

docs/consume-packages/install-use-packages-visual-studio.md
:white_check_mark:Succeeded
View

docs/consume-packages/installing-signed-packages.md
:white_check_mark:Succeeded
View

docs/consume-packages/managing-the-global-packages-and-cache-folders.md
:white_check_mark:Succeeded
View

docs/consume-packages/media/ConsolidateTab.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/InstallPreviewDialog.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/ManagePackagesSolutionUICommand.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/ManagePackagesUICommand.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/Options.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerConsoleControls.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerConsoleControls1.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerConsoleControls2.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerConsoleControls3.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerConsoleInstall.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerUIAutoReferenced.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageManagerUIOptions.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageSourceDropDown.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/PackageSourceSettings.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/References.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/Search.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/SolutionPackagesUI.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/UninstallPackage.png
:white_check_mark:Succeeded
View

docs/consume-packages/media/UpdatePackages.png
:white_check_mark:Succeeded
View

docs/create-packages/Creating-a-Package.md
:white_check_mark:Succeeded
View

docs/create-packages/Prerelease-Packages.md
:white_check_mark:Succeeded
View

docs/create-packages/Sign-a-Package.md
:white_check_mark:Succeeded
View

docs/faqs/NuGet-FAQ.md
:white_check_mark:Succeeded
View

docs/hosting-packages/Local-Feeds.md
:white_check_mark:Succeeded
View

docs/hosting-packages/NuGet-Server.md
:white_check_mark:Succeeded
View

docs/hosting-packages/Overview.md
:white_check_mark:Succeeded
View

docs/install-nuget-client-tools.md
:white_check_mark:Succeeded
View

docs/quickstart/create-and-publish-a-package-using-visual-studio-net-framework.md
:white_check_mark:Succeeded
View

docs/quickstart/create-and-publish-a-package-using-visual-studio.md
:white_check_mark:Succeeded
View

docs/quickstart/install-and-use-a-package-in-visual-studio.md
:white_check_mark:Succeeded
View

docs/reference/PowerShell-Reference.md
:white_check_mark:Succeeded
View

docs/reference/Signed-Packages-Reference.md
:white_check_mark:Succeeded
View

docs/reference/cli-reference/cli-ref-add.md
:white_check_mark:Succeeded
View

docs/reference/cli-reference/cli-ref-config.md
:white_check_mark:Succeeded
View

docs/reference/cli-reference/cli-ref-delete.md
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@karann-msft Karan, do you want to run any checks on this before prior to merge? This moves files out of the old Tools folder for better breadcrumbs.

@Mikejo5000 - this seems to have conflicts with master. Please tag me when resolved.

@karann-msft Yes, I'm working on those right now.


streamAvailable not read changes

Hello Dude, I have a problem with streamAvailable (), because sometimes it is recognized and sometimes not a change in firebase.
I'm leaving a video on YT to better express my problem.
https://youtu.be/tx65G-tifaA
LOOP:
`
if (firebaseData.streamAvailable())
{
Serial.println("STREAM PATH: " + firebaseData.streamPath());
Serial.println("EVENT PATH: " + firebaseData.dataPath());
Serial.println("DATA TYPE: " + firebaseData.dataType());
Serial.println("EVENT TYPE: " + firebaseData.eventType());
    String eventPath = firebaseData.dataPath();
    Serial.println("EVENT PATH: " + firebaseData.dataPath());

    if (eventPath == "/CheckTemperature")
        disableCheckTest();

}
`

The stream data reading  in loop may be interrupted by your other codes e.g. delay and some hidden delay used in third party libs or the problem with internet access that's why you'll see the stream time out message.

After the stream was resumed, you'll see the stream data with event path "/" which return from the new stream connection.

Depois que o fluxo foi retomado, você verá os dados do fluxo com o caminho do evento "/" que retornam da nova conexão de fluxo.

Yes.
Problem is when he does not recognize the new change, it is not a problem with internet and delay (), because I did a test using only his lib and wifi.
new video
https://youtu.be/-M_GlnHc-JM

part my cod teste
`
class Credentials
{
public:
//Wifi
const String WIFI_SSID = "....";
const String WIFI_PASSWORD = "....";
//Firebase
const String FIREBASE_HOST = "....";
const String FIREBASE_AUTH = "....";

};
class Paths
{
public:
const String PATH = "/sensor01/";
const String CHECK_TEMPERATURE = PATH + "/CheckTemperature/value";
};
#include "FirebaseESP8266.h"
#include <ESP8266WiFi.h>
Paths paths;
Credentials credentials;
FirebaseData firebaseData;
void setup() {
Serial.begin(115200);
wifiConnect();

Firebase.begin(credentials.FIREBASE_HOST, credentials.FIREBASE_AUTH);

if (!Firebase.beginStream(firebaseData, paths.PATH))
{
    Serial.println("------------------------------------");
    Serial.println("Can't begin stream connection...");
    Serial.println("REASON: " + firebaseData.errorReason());
    Serial.println("------------------------------------");
    Serial.println();
}

Firebase.setBool(firebaseData, paths.CHECK_TEMPERATURE, false);

}
void loop()
{
if (!WiFi.isConnected())
{
Serial.println("Desconectado, reconectando...");
wifiConnect();
}
if (!Firebase.readStream(firebaseData))
{
    Serial.println("------------------------------------");
    Serial.println("Can't read stream data...");
    Serial.println("REASON: " + firebaseData.errorReason());
    Serial.println("------------------------------------");
    Serial.println();
    return;
}

if (firebaseData.streamTimeout())
{
    Serial.println("Stream timeout, resume streaming...");
    Serial.println();
}

if (firebaseData.streamAvailable())
{
    Serial.println("STREAM PATH: " + firebaseData.streamPath());
    Serial.println("EVENT PATH: " + firebaseData.dataPath());
    Serial.println("DATA TYPE: " + firebaseData.dataType());
    Serial.println("EVENT TYPE: " + firebaseData.eventType());

    String eventPath = firebaseData.dataPath();
    Serial.println("EVENT PATH: " + firebaseData.dataPath());

    if (eventPath == "/CheckTemperature")
        disableCheckTest();
}

}
void wifiConnect()
{
WiFi.begin(credentials.WIFI_SSID, credentials.WIFI_PASSWORD);
Serial.print("\nconectando");
while (WiFi.status() != WL_CONNECTED)
{
Serial.print(".");
delay(500);
}
Serial.print("\nconectado: ");
Serial.println(WiFi.localIP());
}
void disableCheckTest()
{
Firebase.setBool(firebaseData, paths.CHECK_TEMPERATURE, false);
Serial.println("CHECKPATH" + paths.CHECK_TEMPERATURE);

}`

Remove this code from the loop, it can't help you to reconnect as just call WiFi begin again.
   if (!WiFi.isConnected()){
        Serial.println("Desconectado, reconectando...");
        wifiConnect();
    }

You need to disconnect and let the WiFi library auto reconnect for you.  Which this reconnect feature already done by the library since you use Firebase.reconnectWiFi(true) and above lines of code is not necessary.
I see the code that you use one Firebase Data object for stream and normal Firebase calls e.g. get/set/push/update.
This kind of usage will interrupt the stream when you call setBool. The stream connection will be close and open the new connection to set the boolean and then resume the stream again.
If you want to stream operate continuously, you need to use other Firebase Data object to do other works.
Please follow the stream examples.

Firebase.reconnectWiFi(true)

THankss,
seems to have improved, but I still suffer from double clicks or even single clicks on the APP.
Now I use a new instance:
FirebaseData firebaseDataSet;
void disableCheckTest (){
     Firebase.setBool (firebaseDataSet, paths.CHECK_TEMPERATURE, false);
     Serial.println ("CHECKPATH" + paths.CHECK_TEMPERATURE);
}

video:
https://youtu.be/ARWuQH5f09w

Your algorithm is the problem.
You make a recursive operation like a echo which you should avoid when you use the result of the change to trigger it change.
Please redesign your algorithm and the database.

I lock the conversation because its too much and not a library issue.
You can reply the Email if you want me for further help or open the new issue for bugs, questions and improvement.


Clean up enumerations with duplicate mime types

User Story:
As a RS developer, I want to prevent having duplicate information about file formats (including mime types) in different enums.
Description/Use Case
In the Pull Request for changes in #7402, Carlos pointed out that we have mime types in both Sender.Format and Report.Format. This ticket involves consolidating those two Format enums to prevent that info from being stored in two locations.
Risks/Impacts/Considerations

Automated tests should verify that these changes don't impact functionality
It's possible some unit tests will become redundant, depending on how these structures are consolidated

Dev Notes:

See Sender.Format and Report.Format
This looks like duplication of code, so will need to refactor in order to use a common set of mime types.

Acceptance Criteria

Mime types for file formats are listed in one place in the code.

MIME types are not in a new enum class MimeFormat
where possible, we're using MIME constants from fhir library we're already using
everything looking for Sender.Format or Report.Format now points to MimeFormat


v3 SDK link broken in README.md

Please tell me the correct link to put in the v3 SDK link in the README.md because it's broken
🥂

Closing via #116


Allow devices with spaces in their names

I haven't tested this because I can't find this corresponding file on my installation, but this should work.  I can run my script like this:
./etekcity_control.sh 'game cube' powerstate set false
and it works.  My log however shows that the script is being called with:
./etekcity_control.sh game cube powerstate set false
because $1 just has "game".

It works.  I found the file.  I missed a number of places I needed to add quotes.  All instances of this:
command += " " + that.name + "
must be replaced with:
command += " '" + that.name + "'
When you make this change, it's a lot easier to use with Siri.

I have added quotes to all the inclusions of device name on the command line now.  This now reflects the version I'm running on my Raspberry Pi.


Improve stable diffusion doc

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


[Android]: FFImageLoading image appears too wide

I have the following very simple layout. If I use a stock XF Image, everything is all right. If I use an FFImageLoading CachedImage, the image display will be wider than the carousel page, on both sides. This extra image strip will stay there when I swipe to another page, and won't go away until the next swipe touch.
<cards:CarouselView Items="{Binding Categories}" VerticalOptions="FillAndExpand" IsViewCacheEnabled="True" MaxChildrenCount="4" DesiredMaxChildrenCount="4" IsCyclical="True" IsClippedToBounds="True">
  <cards:CarouselView.ItemTemplate>
    <DataTemplate>
      <ContentView>
        <Grid>
          <ff:CachedImage Source="{Binding imagePath}" Aspect="AspectFill" />
          or
          <Image Source="{Binding imagePath}" Aspect="AspectFill" />

The bitmap has a different aspect ratio than the page, so that's the bitmap that I can see to the left and right, no problem with that, but in the Image case it's cropped as normal using AspectFill.

Hi, it seems to be Ffimageloading bug  https://github.com/luberda-molinet/FFImageLoading/issues/1086
@Daniel-luberda

https://github.com/luberda-molinet/FFImageLoading/releases
Check release notes of 2.3.6
Perhaps, it can be useful to try to set FixOnMesureBehavior to false or try to enable/disable fast renderer

I tried another trick that seems to work: I put the FF image inside an extra Grid that has its dimensions bound to the page width and height. But this means that the bug should have been fixed already, we're at 2.4.3 now.

Got it.. strange issue..

OK, the fast renderer seems to be the final culprit. Without it, there is no need for either the FixWhatever static field nor the extra Grid. Did you try without the fast one? I'll note it in Daniel's issue if that's the case.

I'm only allowed by GitHub to do that once.  Haha

Anyway, thanks for the help and nice catch, I wrote about it there (as I mentioned you, GH had to notify you by now).

Very well!


Updates for dependencies

Probably wait on https://github.com/bulkan/robotframework-requests/issues/243 if they are going to move on it in the next day or so


Unable to setup an Apache + Passenger config - 404 "Not found: /"

Hi,
I'm trying to reproduce what you've done here : http://port.us.org/docs/setups/4_portus_and_registry_on_the_same_fqdn.html
In both on config files below, I commented the rewrite rules, I didn't need them for WebUI testing.
If I use this config file for Apache, the WebUI actually works at https://my.domain.com/
<VirtualHost *:443>

   ServerName my.domain.com
   DocumentRoot /srv/Portus/public
   SSLEngine on
   SSLCertificateFile /certs/my.domain.com.pem
   SSLCertificateKeyFile /private/my.domain.com.fr.key

 #  RewriteEngine On

#   RewriteCond %{REQUEST_URI} !^/portus.*$
#   RewriteRule ^/(.*)$ "http:\/\/127\.0\.0\.1\:5000\/$1" [P,L]

#   Alias /portus /srv/Portus/public
#   <Location /portus>
     PassengerBaseURI /
     PassengerAppRoot /srv/Portus
#   </Location>
     PassengerLogLevel 3
   <Directory "/srv/Portus/public">
   Options FollowSymLinks
   AllowOverride None
   Order allow,deny
   Allow from all
   Options -MultiViews
   # Uncomment this if you're on Apache >= 2.4:
   Require all granted
      SetEnv GEM_PATH /usr/local/lib/ruby/gems/2.1.0/gems:/usr/local/lib/ruby/gems
      SetEnv PASSENGER_COMPILE_NATIVE_SUPPORT_BINARY 0
      SetEnv PASSENGER_DOWNLOAD_NATIVE_SUPPORT_BINARY 0
      PassengerAppEnv development
   </Directory>
</VirtualHost>

But with the one you give, I can't get it to work at https://my.domain.com/portus, I keep on getting 404 errors. Things that change are between *** (which obvisoulsy, are not included in the real config file)
BUT I can still go to Portus WebUI on https://my.domain.com/
<VirtualHost *:443>

   ServerName my.domain.com
   DocumentRoot /srv/Portus/public
   SSLEngine on
   SSLCertificateFile /certs/my.domain.com.pem
   SSLCertificateKeyFile /private/my.domain.com.key

 #  RewriteEngine On

#   RewriteCond %{REQUEST_URI} !^/portus.*$
#   RewriteRule ^/(.*)$ "http:\/\/127\.0\.0\.1\:5000\/$1" [P,L]

   *** Alias /portus /srv/Portus/public ***
   *** <Location /portus> ***
     *** PassengerBaseURI /portus ***
          PassengerAppRoot /srv/Portus
   *** </Location> ***
     PassengerLogLevel 3
   <Directory "/srv/Portus/public">
   Options FollowSymLinks
   AllowOverride None
   Order allow,deny
   Allow from all
   Options -MultiViews
   # Uncomment this if you're on Apache >= 2.4:
   Require all granted
      SetEnv GEM_PATH /usr/local/lib/ruby/gems/2.1.0/gems:/usr/local/lib/ruby/gems
      SetEnv PASSENGER_COMPILE_NATIVE_SUPPORT_BINARY 0
      SetEnv PASSENGER_DOWNLOAD_NATIVE_SUPPORT_BINARY 0
      PassengerAppEnv development
   </Directory>
</VirtualHost>

I got nothing in my Passenger logs nor Nginx'
Thing weird is that I can still get static files (like robots.txt at the https://my.domain.com/portus/robots.txt). For me, that actually means that Apache is correctly responding to HTTP requests but Passenger isn't retrieving anything.

I dropped Passenger. I also want to drop Apache but I can't. I'm on a Apache + Thin setup.
That is actually working except Apache is unable to launch as a demon, is unable to proxy/lb with unix sockets, and is just crashing no matter what after 5 minutes, even if I don't make a single request to Portus...

Did you get this working? Running into the same problem.

I'm actually workin on an Apache + Unicorn setup. I's workin,  but i still can't push/pull, even if authentication is successful.
Just try to launch your passenger app as a production app and precompile the assets. You can also try to serve static files from your httpd, insted of your ruby app server.
Tell me if it's workin !


Remove github pages publishing of docs

Currently, the documentation is published on two different servers. we should only keep https://nlu.rasa.com - we can't just redirect to the version hosted by ghpages, as it
doesn't allow us to use SSL certificates at the moment.
@amn41 how is the documentation build on the nlu.rasa.com server, is it build from scratch, or is it using the documentation build by travis and pushed to the gh-pages branch?

the server just git pulls the gh-pages branch

Alright, we need to make it pull from a branch with a different name, e.g docs - I’ll create a PR


Nice2Have: Define a function for output inside of DNSLogger instead of print, would make it easy to send to custom loggers

Not an issue as such, but
Needed to attach a custom logger to DNSLogger, format was fine, but needed to overload every method as print was used...
It would have been so much better if there was a log_print or _print or _output method in the DNSLogger class instead.
Then using a customer logger w/o format change would be much simpler.
If you could implement this would be great. :) Great code, btw!
https://github.com/paulc/dnslib/blob/729a655b069303de089a9ca3904378b15dd17ff1/dnslib/server.py#L178-L302

That's a really good idea, thanks. I've added logf parameter in the DNSLogger constructor and released a new version (https://pypi.org/project/dnslib/0.9.19/)

Thank you! Thank you very much!


Fix race condition in an async test which was triggering failures (SR-2332)

When the system running these tests is under load, the assumptions that these tests were making about dates and ordering weren't holding. This could cause test_immediatelyTrueDelayedFalsePredicateAndObject_passes to fail intermittently, and test_delayedTruePredicateAndObject_passes to not be verifying the situation it was written to target.
This removes these tests' dependency on dates, increasing reliability.
Resolves: https://bugs.swift.org/browse/SR-2332
@mike-ferris-apple @parkera

@swift-ci please test and merge

@swift-ci Please test

Awesome, thanks @briancroom! Do you think similar changes need to be made for other similar async tests, such as this one?

I agree that the technique in this diff might be good to use in other places where we're relying on dates and timing to test similar stuff.
The specific test you reference seems less likely to be an issue immediately because of the different time values involved, though it does seem the same theoretical issues could be avoided with the same sort of technique.
Assuming the tests pass, though, let's get this merged.

Our tests seemed to have passed, so in it goes. We'll need to pick this change into swift-3.0-branch.


Enable typescript compatibility

This is to enable volto sites to use typescript. Nothing changes for who doesn't want to use TS.
I will add a section in the documentation with instructions on how to use typescript before merging.

Ok, I tested things and read some documentation about typescript and razzle and I'm currently writing the needed documentation. It should be done by tomorrow.

@pnicolli ^^ I hope it's fine for you!

@pnicolli ^^ I hope it's fine for you!

Yes, absolutely. Thanks for taking care of that, I had no time in the previous days and I was catching up right now.


task_wdt: Add auto init and syswq monitoring

This patch adds two new features to the task watchdog subsystem:

Automatic initialization of the task watchdog on SYS_INIT
Monitoring of the system work queue

The automatic initialization feature is enabled by the new Kconfig option TASK_WDT_AUTO_INIT. When enabled, the task watchdog will be initialized automatically on SYS_INIT. This is useful for applications that want to use the task watchdog but do not want to manually initialize it.
The system work queue monitoring feature is enabled by the new Kconfig option TASK_WDT_SYSWQ_STALL. When enabled, the task watchdog will monitor the system work queue. If the system work queue is stalled for longer than the specified timeout, the task watchdog will trigger a system panic.
The system work queue stall timeout is specified by the new Kconfig option TASK_WDT_SYSWQ_STALL_TIMEOUT_MS. This option specifies the maximum time in milliseconds that the system work queue is allowed to be stalled before the task watchdog triggers a system panic.

Sounds like a good idea!


API Lifecycle Weekly - February 17th, 2022

This is a weekly public meeting to discuss the different areas of the API lifecycle and governance, push forward discussions around how the API lifecycle applies to OpenAPI and AsyncAPI, and work on extensions, platform ops collections, tooling, and blueprints that will help the community be more successful.
Agenda:

Blueprint - Moving forward blueprints, elements, and creating content, workshops, and curriculum.

Elements Board - Organizing elements.
Blueprints Board - Organizing blueprints.
Solutions - Working with solutions.

Platform Ops (Specifications, Design, Mocking, Documentation, Environments, Testing, Security, Monitoring, Discovery, Workspaces, Client, Source Control, CI/CD, Gateway, APM, Orchestration, Observability, Governance, Analytics, Teams,Change, Automation)

OpenAPI Linting API - Check in on the OpenAPI Linting API and what is next.
OpenAPI Security Scanner API - Check in on the OpenAPI Security Scanner API.

Platform Governance (Workspace) - Move forward with storytelling around linting rules.

Platform - Support in API builder coming as part of wider security releases.

Please add any agenda items you’d like to discuss below, and we will meet weekly, and push forward projects, stories, collections, and tools to support our work.
Meeting:

February 17th, 2022 - 8:00 AM PST
Zoom

Issues -  Good issues to start. Typical things.
Usual scenarios - Opinionated.

Dungeons & Dragons -- Create books and guides.
Meena Suggested Thoughtworks - https://www.thoughtworks.com/radar