Update Linter for Windows

I was having some problems getting the gfortran-based linter to work on Windows 10 so I took a stab at fixing the problems.
Issues:

If no include paths are specified in fortran.includePaths then gfortran to complains about no input files and exits
errorRegex fails to match gfortran output so no errors are displayed

Changes:

Modified the getIncludeParams function in src/lib/helper.ts to check for the paths variable having a length of 0. In this case the function returns "" instead of "-I ". The empty argument will then be removed by constructArgumentList in src/features/linter-provider.ts.
Modified errorRegex in src/features/linter-provider.ts to allow for upper and lowercase drive names on Windows and to match all space between output lines via \s+ instead of just \n. The change to matching space should allow the regex to work regardless of the operating system using carriage returns or not.

I ran the extension tests on my Windows 10 computer and all 13 passed. Unfortunately, I don't have quick access to a linux system for testing, but I can create a VM if necessary.

This sounds quite good to me.


Web app doesn't pause after Audible sending PlaybackPaused event

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:

We ask weather when playing Audible. The Audible paused on device but the web app still showing playing Audible.
From Log, we send a pause event in listening status but the icon on web app doesn't change to pause.

############################
Listening...
############################
2018-04-30 04:00:33.587 [  6] 0 AudioPlayer:executeProvideState:sendToken=true,stateRequestToken=5
2018-04-30 04:00:33.589 [  6] 0 ContextManager:updateStateLocked:action=updatedState,namespace=AudioPlayer,name=PlaybackState
2018-04-30 04:00:33.592 [  4] 0 ContextManager:buildContextSuccessful
2018-04-30 04:00:33.593 [  a] 0 AudioPlayer:onFocusChanged:newFocus=BACKGROUND
2018-04-30 04:00:33.593 [  6] 1 AudioPlayer:executeOnFocusChanged:from=FOREGROUND,to=BACKGROUND,m_currentActivity=PLAYING
2018-04-30 04:00:33.594 [  6] 1 AudioPlayer:executeOnFocusChanged:action=pauseMediaPlayer
2018-04-30 04:00:33.610 [  b] 0 AudioPlayer:onPlaybackPaused:id=6
2018-04-30 04:00:33.611 [  6] 1 AudioPlayer:executeOnPlaybackPaused:id=6
2018-04-30 04:00:33.611 [  6] 1 AudioPlayer:sendEventWithTokenAndOffset:eventName=PlaybackPaused
2018-04-30 04:00:33.612 [  6] 9 HTTP2Transport:enqueueRequest
2018-04-30 04:00:33.612 [  6] 0 AudioPlayer:changeActivity:from=PLAYING,to=PAUSED
2018-04-30 04:00:33.613 [  6] 0 AudioPlayer:executeProvideState:sendToken=false,stateRequestToken=0
2018-04-30 04:00:33.613 [  7] 9 HTTP2Transport:enqueueRequest
2018-04-30 04:00:33.613 [  6] 0 ContextManager:updateStateLocked:action=updatedState,namespace=AudioPlayer,name=PlaybackState
2018-04-30 04:00:33.622 [  6] 1 AudioPlayer:notifyObserver:playerActivity=PAUSED
2018-04-30 04:00:33.648 [  8] 0 HTTP2Transport:processNextOutgoingMessage:jsonContent={"event":{"header":{"namespace":"AudioPlayer","name":"PlaybackPaused","messageId":"e13aca1a-969d-4247-a1b5-e16675a08f44"},"payload":{"token":"amzn1.as-ct.v1.AudibleClientId#ACRI#url#ACRI#playq:audiobook/audible;mv=Audible,c53b9497-3f3d-4451-9d64-3b247d721366#6","offsetInMilliseconds":418000}}}

Did I miss any event or wrong flow?
Full log can be found here.
audible_webapp_no_pause.txt
What is the expected behavior?

Audible should pause on web app when speaking weather.
What behavior are you observing?

The web app still shows playing Audible when speaking weather.
Provide the steps to reproduce the issue, if applicable:

Alexa, Play Audible.
(Wait for playing Audible)
Alexa, What's the weather.
(Audible pause and speak weather but the web app still in playing status)
Tell us about your environment:

What version of the AVS Device SDK are you using?
    <1.4.0>

Tell us what hardware you're using:

[ ] Desktop / Laptop
[ ] Raspberry Pi
[X] Other - tell us more: ARM A7

Tell us about your OS (Type & version):

[ ] Linux
[ ] MacOS
[ ] Raspbian Stretch
[ ] Raspbian Jessy
[X] Other - tell us more: Linux OpenWRT

Hi @mynewsty23,
Does this also reproduce on the mobile app?
Fede

Hi @frozenberg ,
We also got some issues while playing audible books or Kindle.
To follow this case, may I say may mobile APP behavior is different from web APP ?
for example, while I interrupt the audible book playing and resume, the progress bar will become different between mobile and web APP (sometimes, mobile APP will be correct).

Hi @zeusshuang,
Yes, it seems that the behaviors of the web app and the mobile app aren't always consistent. Does that answer your question?
Fede

Hi @frozenberg
Yes, this problem is the same as mobile app.

Can you reproduce this problem?

I'll close this one out.  As @frozenberg mentioned, this is a known issue which AVS will be continuing to address, and is not caused by the client implementation on the device, it is related to how various cloud infrastructures interact with AVS.


Fix implicit subjects mocked/stubbed not detected

This PR fixes #818.
Implicit Subject had not been detected by the Rspec/SubjectStub, which reported false negative cases.
As suggested by @pirj, there are solutions to recursively traverse through AST (either upward or downward). However, to the best of my knowledge, they might require a fair amount of changes how the cop is currently working and impact the runtime performance.
I've chosen the somewhat safe fix that reports the defaut :subject if there is no named nor unnamed subject declared.
Since it's my first PR, any suggestions and feedback are more than welcome.

Before submitting the PR make sure the following are checked:

[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Added an entry to the changelog if the new code introduces user-observable changes.
[x] The build (bundle exec rake) passes (be sure to run this locally, since it may produce updated documentation that you will need to commit).

New push to resolve conflicts 😁

I feel this way we do unnecessary iterations. The only issue is that when there is no explicit subject definition, we never call find_subject_expectation, while the message_expectation? matcher search not only for whatever name we give, but also for subject.
This is an optimization we can tackle separately though

I feel this way we do unnecessary iterations. The only issue is that when there is no explicit subject definition, we never call find_subject_expectation, while the message_expectation? matcher search not only for whatever name we give, but also for subject.
This is an optimization we can tackle separately though

From my understanding, it happens not only to implicit subjects but also to the unnamed subjects which are out of the scope of this PR.


default AZ for the region

@segmentio/infra
This adds a mapping of default availability zones for each AWS region, that way when a stack module is instantiated, only the region can be specified and the config dynamically figures out what AZ to use.
Note that the AZ may be changing from time to time so we'll likely have to edit these values in the future.

one note about the different az-counts, lgtm otherwise!

I revisited the implementation, gave up on trying to generate stuff dynamically and instead added documentation to help understand what needs to be set.
We're really pushing terraform to its edges here unfortunately, I'd rather avoid increasing the internal complexity when the work around is quite simple (simply setting a couple more properties to change the region).

Sounds fair to me. Yeah, I wouldn't want to break too many of the abstractions just to handle this other case


Also clear preferredPosition for TooltipOverlay

Signed-off-by: Tomas Slusny<EMAIL_ADDRESS>

taken in 33865d1ca1cd54426468be5a80393d4e9b0926c4


Customize the editable grid control (Preview)

The link Customize the editable grid control (Preview) in the first paragraph is marked as preview. The linked page is not marked as preview.

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

ID: 225f1305-7aea-3fdd-9a46-e0f258c670ff
Version Independent ID: 225f1305-7aea-3fdd-9a46-e0f258c670ff
Content: Customized editable grid - Power Apps
Content Source: powerapps-docs/developer/component-framework/sample-controls/customized-editable-grid-control.md
Service: powerapps
Sub-service: pcf
GitHub Login: @jasongre
Microsoft Alias: jasongre

Thanks for your comment, @darshSWL. This issue has been assigned to the doc author for review.

@darshSWL
Thanks for your feedback.
I removed the (Preview) text from the link.


Accessing outputs from a step

Where are the output's getting stored.

Warning: Unexpected input(s) 'file', 'key-path', valid inputs are ['repository', 'ref', 'token', 'clean', 'submodules', 'lfs', 'fetch-depth', 'path'] - I am getting this warning and unable to see the Output (not printing).

Hey @preethidh, I hope this clears things up. outputs is an attribute of the step id that is using read-yaml. You must specify an id attribute on the step in order to access the outputs which has the data about which would be the value at the key you have given. I am not very good at explaining things to people so please don't hesitate to ask another question if this helps but you would take a look at the example on the readme and see how the step that we are calling read-yaml on has an id attribute (I hope you know what I mean by "attribute") and then in the following step we are using that attribute to access .outputs.data (this will always be constant).

Hi @KJ002, Thanks for your response.
I am new to Github actions & below is my yaml file,
name: "Read Yaml"
on:
push:
branches:
- master
pull_request:
branches:
- master
jobs:
test-yaml-reader:
name: 'Test read-yaml'
runs-on: ubuntu-latest
steps:
  - name: Run read-yaml action
    uses: actions/checkout@v1
    with:
      file: './dev.yaml'
      key-path: '["chart", "name"]'

  - name: Get read-yaml output
    run: echo "${{ steps.yaml-data.outputs.data }}"

were as i need to get data from dev.yaml & i observe below error. Am I doing it right? or any modification required.
Warning: Unexpected input(s) 'file', 'key-path', valid inputs are ['repository', 'ref', 'token', 'clean', 'submodules', 'lfs', 'fetch-depth', 'path']

One slight modification needs to be made.
name: "Read Yaml"

on:
  push:
    branches:
      - master
  pull_request:
    branches:
      - master

jobs:
  test-yaml-reader:
    name: 'Test read-yaml'
    runs-on: ubuntu-latest

    steps:
      - name: Checkout
        uses: actions/checkout@v1

      - name: Run read-yaml action
        uses: KJ002/read-yaml@main
        id: chart-name
        with:
          file: './dev.yaml'
          key-path: '["chart", "name"]'

      - name: Get read-yaml output
        run: echo "${{ steps.chart-name.outputs.data }}"

I haven't tried it but this hopefully should work.

works good now!! Thank you :)

Now i am trying to get 2 values from same yaml file, but nothing is printing now.
name: "Read Yaml"
on:
push:
branches:
- master
pull_request:
branches:
- master
jobs:
test-yaml-reader:
name: 'Test read-yaml'
runs-on: ubuntu-latest
steps:
  - name: Checkout
    uses: actions/checkout@v1

  - name: List
    run : ls -laR ./.github/workflows/

  - name: Run read-yaml action - name
    uses: repo@master
    id: chart-name
    with:
      file: './dev.yaml'
      key-path: '["chart", "name"]'

  - name: Run read-yaml action - version
    uses: repo@master
    id: chart-version
    with:
      file: './dev.yaml'
      key-path: '["chart", "version"]'

  - name: Get read-yaml output
    run: echo "${{ steps.chart-name.outputs.data }}"

You're using repo@master not KJ002/read-yaml@main

yeah, i am trying to replicate same in my Github repo.

Unless your repo is located at https://github.com/repo then this isn't going to work, you need to be using my repo for me to be able to provide help.

its located in https://github.com/repo - for example lets take KJ002/read-yaml@main as an example and the yaml should read multiple data and print it.

I was alluding to that it isn't possible for this to be a valid action repo@master

Let me give the .yaml file here,
name: "Read Yaml"
on:
push:
branches:
- master
pull_request:
branches:
- master
jobs:
test-yaml-reader:
name: 'Test read-yaml'
runs-on: ubuntu-latest
steps:
  - name: Checkout
    uses: actions/checkout@v1

  - name: Run read-yaml action - App name
    uses: PD/POC@master
    id: chart-name
    with:
      file: './dev.yaml'
      key-path: '["chart", "name"]'

  - name: Run read-yaml action - Version
    uses: PD/POC@master
    id: chart-version
    with:
      file: './dev.yaml'
      key-path: '["chart", "targetRevision"]'

  - name: Get read-yaml output
    run: echo "${{ steps.chart-name.outputs.data }}"

    Be it any repo in place of KJ002/read-yaml@main

i am trying to get two values using this github action but prints only the "name" but not "version". Am I doing it right or anything needs to be modified.

There is no public repo with called POC under the user PD, it needs to be public.

okay lets take your repo as an example,
will i be able to read and print 2 values from a .yaml file.

yes

that's what actually i am trying and unable to print the 2 one (value).

Try time
name: "Read Yaml"

on:
  push:
    branches:
      - master
      - main
  pull_request:
    branches:
      - master
      - main

jobs:
  test-yaml-reader:
    name: 'Test read-yaml'
    runs-on: ubuntu-latest

    steps:
      - name: Checkout
        uses: actions/checkout@v1

      - name: Run read-yaml action - App name
        uses: KJ002/read-yaml@main
        id: chart-name
        with:
          file: './dev.yaml'
          key-path: '["chart", "name"]'

      - name: Run read-yaml action - Version
        uses: KJ002/read-yaml@main
        id: chart-version
        with:
          file: './dev.yaml'
          key-path: '["chart", "targetRevision"]'

      - name: Get read-yaml output
        run: echo "${{ steps.chart-name.outputs.data }}"

Still below is not working as expected,
  - name: Run read-yaml action - Version
    uses: KJ002/read-yaml@main
    id: chart-version
    with:
      file: './dev.yaml'
      key-path: '["chart", "targetRevision"]'

I have just tried accessing two variables in this repo's test github action and it seems to work completely fine

This is what I have for this repositories github action and it seems to work fine

on: [ push, pull_request ]

jobs:
  test-yaml-reader:
    runs-on: ubuntu-latest
    name: Test read-yaml
    steps:
      - uses: actions/checkout@v1

      - name: Run read-yaml action
        id: using
        uses: ./
        with:
          file: './action.yml'
          key-path: '["runs", "using"]'

      - name: Run read-yaml action
        id: desc
        uses: ./
        with:
          file: './action.yml'
          key-path: '["output", "data", "description"]'

      - name: Get read-yaml using output
        run: echo "${{ steps.using.outputs.data }}"

      - name: Get read-yaml description output
        run: echo "${{ steps.desc.outputs.data }}"
        ```

let me try this

This works fine any possibility to print both values in same step,
I tried with again got error
  - name: Get read-yaml Name output
    run: |
      echo "${{ steps.chart-name.outputs.data }}"
      echo "${{ steps.chart-targetRevision.outputs.data }}"

This should work perfectly fine. I have tried and tested this myself and it works fine, I don't understand what you are missing or not doing.

I am trying to print this in github actions and again print in .md files


"Ambiguous usage" when calling HUD.hide()

The problem is we have two hide() methods with fully optional set of arguments. Because of that compiler can't decide which one to use for HUD.hide() call.

+1


Show how to run tests in notebooks

This requires Elixir v1.12 latest though, so we should
probably wait until the next RC to merge this.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


Add automated UI tests

Since Xcode 7, the XCTest framework has support for automated user interface testing. This should be used to convert at least parts, if not all, of the manual test scripts in the TESTING document into automated tests.
Some things that might be difficult to solve

Starting tests with a well-defined state. Unlike unit tests, UI testing tests the full application, which means that the app may write state such as an NSCoding archive, an .sgf file and user preferences at various points during test execution.
Testing the three different layouts that the app currently supports (iPhone regular devices, iPhone Plus devices, iPad devices).
Testing user interfaces orientations.
Testing what is on the board.

Commits up until now are more or less an initial proof of concept. The next steps will have to provide at least some answers to the difficult issues raised in the issue description.

An initial set of a few UI tests exists now. The difficulties mentioned in the issue description are mostly solved, and there is sufficient infrastructure to write more UI tests in the future. Closing this issue now because there is no point in keeping it open until all UI tests have been written - this is a process that will take substantial time and effort.


I Have Uploaded the Python and tableau file

I Have Uploaded the Python and tableau file

I have Upated The Work-Life Balance and Engagement Analysis Dashboard & Report with analysis


[stable/spark-history-server] Add service annotations

Add service annotations
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

All commits are signed. I don't know why DCO check failed.

@vvbogdanov87 Have you run the commands mentioned here? They should fix your DCO issue.

@yuchaoran2011 Could you please review.


Removes code and rewrites docs for lambda-cfn v2

With the release of lambda-cfn v2 users no longer need to use a parent Patrol repo with its own CloudFormation stack to deploy Patrol rules. I've removed all of the code and code related files (e.g. .travis.yml) to reflect this change. This repo is now an issue and documentation only repo that links to other Patrol repos.
I also updated the README.md and GETTING-STARTED.md docs to reflect the "one rule, one stack" (1r1s) update with lambda-cfn v2.
During this process I may have removed some useful technical content - please feel free to re-add later. My goal with this PR was to provide a quick, timeboxed rewrite of the main Patrol docs to reflect the major changes in lambda-cfn v2.
Noting that after we merge this PR we should also disable Travis on this repo.
/cc @ianshward @zmully

Thanks for catching that typo @ianshward! I'm going to 🚢  this now.
I also changed the Travis settings on this repo to only run tests if there's a .travis.yml file. This should also us to view past tests but not run new tests going forward.


Ellipsis repository icon is spinning on refresh

In the repository tab if a repository name is truncated with the ellipsis icon it will spin if clicked to refresh the repository :)

@Madsim Can you please tell which version are you using? I tried this on master build
ersion: 1.41.0
Commit: Unknown
Date: Unknown
Electron: 6.1.5
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Darwin x64 19.0.0
and
Version: 1.40.2
Commit: f359dd69833dd8800b54d458f6d37ab7c78df520
Date: 2019-11-25T14:52:45.129Z
Electron: 6.1.5
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Darwin x64 19.0.0
but could not reproduce the issue

@s-surineni sure, sorry for not including this in the first place.

@misolori Already fixed this in master.

@joaomoreno Still happening in 1.41.0 on Push press in Git press.

Please see https://github.com/microsoft/vscode/issues/86423. There were some cases where the sync icon still got truncated, we now have set a min width on the icons so this doesn’t happen.


create CoreOS image with samsung docker installed

in the spirit of leaving CoreOS unmodified after it hits a node we should be creating our own CoreOS image with docker pre-installed

Note that I am currently installing docker in the same way that the cni pluggins are installed, so if we decide to do this, then it might make sense to bake those in as well. One advantage of doing so is that node start time will be reduced, though probably not by much. A more significant advantage is that for some deployments an air-gapped solution is necessary for high availability, regulatory reasons, etc. We will need to consider the on going maintenance cost required to maintain self hosted system images, as well as the benefits and drawbacks of various artifact management systems. The latter of these may be customer specific.

FWIW, CNI plugins will be delivered through a k8s manifest, not through a systemd unit moving forward.  https://github.com/projectcalico/canal/issues/32 hints to that.

this is too much work.  not needed.


Release v2<IP_ADDRESS>

Release Note:

Fix cross browser hashtag compatibility https://github.com/pingcap/tidb-dashboard/pull/1123
Update the year of copyright https://github.com/pingcap/tidb-dashboard/pull/1124
Tweak Top SQL UX https://github.com/pingcap/tidb-dashboard/pull/1122
Add E2E test https://github.com/pingcap/tidb-dashboard/pull/1109

@breeswish PTAL, thanks!

Codecov Report

:exclamation: No coverage uploaded for pull request base (release@18087fc). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             release   #1126   +/-   ##
=========================================
  Coverage           ?   6.88%
=========================================
  Files              ?      33
  Lines              ?    1990
  Branches           ?       0
=========================================
  Hits               ?     137
  Misses             ?    1842
  Partials           ?      11

Flag
Coverage Δ

be_integration_test_v4.0.1
6.88% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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

Will this change cause your frontend to change?
https://github.com/pingcap/tidb/pull/31378

No.

Merged. Please follow up PD updates.


Couldn't upload FASTA file

Hello, I cannot upload a single protein FASTA file titled hdac7.fasta as below which is a direct download from Uniprot:
>sp|Q8WUI4|HDAC7_HUMAN Histone deacetylase 7 OS=Homo sapiens OX=9606 GN=HDAC7 PE=1 SV=2
MDLRVGQRPPVEPPPEPTLLALQRPQRLHHHLFLAGLQQQRSVEPMRLSMDTPMPELQVG
PQEQELRQLLHKDKSKRSAVASSVVKQKLAEVILKKQQAALERTVHPNSPGIPYRTLEPL
ETEGATRSMLSSFLPPVPSLPSDPPEHFPLRKTVSEPNLKLRYKPKKSLERRKNPLLRKE
SAPPSLRRRPAETLGDSSPSSSSTPASGCSSPNDSEHGPNPILGSEALLGQRLRLQETSV
APFALPTVSLLPAITLGLPAPARADSDRRTHPTLGPRGPILGSPHTPLFLPHGLEPEAGG
TLPSRLQPILLLDPSGSHAPLLTVPGLGPLPFHFAQSLMTTERLSGSGLHWPLSRTRSEP
LPPSATAPPPPGPMQPRLEQLKTHVQVIKRSAKPSEKPRLRQIPSAEDLETDGGGPGQVV
DDGLEHRELGHGQPEARGPAPLQQHPQVLLWEQQRLAGRLPRGSTGDTVLLPLAQGGHRP
LSRAQSSPAAPASLSAPEPASQARVLSSSETPARTLPFTTGLIYDSVMLKHQCSCGDNSR
HPEHAGRIQSIWSRLQERGLRSQCECLRGRKASLEELQSVHSERHVLLYGTNPLSRLKLD
NGKLAGLLAQRMFVMLPCGGVGVDTDTIWNELHSSNAARWAAGSVTDLAFKVASRELKNG
FAVVRPPGHHADHSTAMGFCFFNSVAIACRQLQQQSKASKILIVDWDVHHGNGTQQTFYQ
DPSVLYISLHRHDDGNFFPGSGAVDEVGAGSGEGFNVNVAWAGGLDPPMGDPEYLAAFRI
VVMPIAREFSPDLVLVSAGFDAAEGHPAPLGGYHVSAKCFGYMTQQLMNLAGGAVVLALE
GGHDLTAICDASEACVAALLGNRVDPLSEEGWKQKPNLNAIRSLEAVIRVHSKYWGCMQR
LASCPDSWVPRVPGADKEEVEAVTALASLSVGILAEDRPSEQLVEEEEPMNL

After the upload, I immedietely receive the pop-up like:

Disconnected from the server.
Reload

I tried several times from Chrome 130.0.6723.92 (Win).

Skill issue

Hey, I just tried uploading the file and it worked for me.
I created a new file using a text editor, pasted the sequence, and saved it on my Desktop.

Maybe creating a new file will already resolve it for you, if not please reach out!


Appstudio update test-component-pac-dafe

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-component-pac-dafe-on-pull-request-
creating pipelinerun test-component-pac-dafe-on-pull-request- in namespace build-e2e-nabq-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI/test-component-pac-dafe-on-pull-request has failed.

StatusDurationName

✅ Succeeded
16 seconds
init

✅ Succeeded
24 seconds
clone-repository

✅ Succeeded
46 seconds
build-container

✅ Succeeded
41 seconds
sast-snyk-check

✅ Succeeded
29 seconds
inspect-image

✅ Succeeded
9 seconds
deprecated-base-image-check

❌ Failed
36 seconds
clair-scan

✅ Succeeded
45 seconds
clamav-scan

✅ Succeeded
12 seconds
sbom-json-check

✅ Succeeded
4 seconds
show-sbom

✅ Succeeded
4 seconds
show-summary

Failure reasontask clair-scan has the status "TaskRunImagePullFailed":
The step "get-vulnerabilities" in TaskRun "test-component-pac-dafe-on-pull-request-fp5q2-clair-scan" failed to pull the image "". The pod errored with the message: "Back-off pulling image "quay.io/redhat-appstudio/clair-in-ci:latest"."


Cleanup initial condition logic

Earth-2 MIP Pull Request
Description
Big cleanup of various pieces related to channel names and the initial conditions. Most importantly, I removed the ChannelSet.
I formalized the DataSource interface, making it return numpy.ndarray rather than xarray and provide the needed metadata like lon, lat as attributes. This is more robust/static then getting this from Dataset objects. I then refactored all the get functions to be DataSources and made a factory method.
inference_ensemble now works with general TimeLoop interface. #60 was most of the work, but channel_set was still used in a few places.
Resolves #56 #14.
Could probably some more involved testing, but the CI is passing, and this is a refactor rather than adding new features. Since there is no automated script to run all the examples and notebooks perhaps we can defer more manual testing until pre-release QA.
Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.
[x] The CHANGELOG.md is up to date with these changes.
[x] An issue is linked to this pull request.

Dependencies

/blossom-ci

/blossom-ci

@NickGeneva the tests are failing because the CI doesn't have CDS auth. Can we give it this? If not, are there any env variables that will allow us to manually detect if we are in the CI environment and skip the test?

Can we add a check for the .cdsapi file for that pytest that will skip it?
That or we could add my API key into the CI pipeline.
https://github.com/ecmwf/cdsapi/blob/0ad7f77f83e5b66fa5e048328cf254f79e6fcd51/cdsapi/api.py#L288

/blossom-ci

/blossom-ci

/blossom-ci


ERROR: aws-serverless-express connection error with every requests

"aws-serverless-express": "3.2.0",
<EMAIL_ADDRESS>It working fine in yesterday.
CloudWatch log
a0c895f5-fe7c-11e8-b3ae-4f8962debec2 ERROR: aws-serverless-express connection error
1544667186190,/aws/lambda/function,2018-12-13T02:13:06.190Z a0c895f5-fe7c-11e8-b3ae-4f8962debec2 { Error: socket hang up    at createHangUpError (_http_client.js:299:15)    at Socket.socketOnEnd (_http_client.js:391:23)    at emitNone (events.js:111:20)    at Socket.emit (events.js:208:7)    at endReadableNT (_stream_readable.js:1064:12)    at _combinedTickCallback (internal/process/next_tick.js:138:11)    at process._tickDomainCallback (internal/process/next_tick.js:218:9) code: 'ECONNRESET' }

@brettstack No, nothing change. We have 2 stages on aws, both gets the same issue.

The same error is occurring in our service.
"aws-serverless-express": "3.3.5",
"serverless": "1.32.0",

Thanks for reporting. If you could provide additional information such as how you're implementing the handler (e.g is it wrapped in a promise?); Which version of Node.js runtime you're using, that might help.

@brettstack
this is my handler, LambdaNode ver 8.10, I am using Typescript
exports.handler = (event, context, callback) => {
  try {
    context.callbackWaitsForEmptyEventLoop = false;
    context.succeed = (response) => {
      callback(null, response);
    };
    console.log("START REQUEST", event);
    return awsServerlessExpress.proxy(server, event, context);
  } catch (e) {
    console.info("===> Handler Error: ", e);
  }
};

@brettstack
We are using the runtime of Node.js 8.10.
Here is our handler.
We also use TypeScript.
const server = awsServerlessExpress.createServer(app, undefined, binaryMimeTypes);

export const expressHandler = async (
  event: lambda.APIGatewayEvent,
  context: lambda.Context,
  callback: lambda.Callback,
) => {
  context.callbackWaitsForEmptyEventLoop = false;

  return new Promise((resolve) => {
    awsServerlessExpress.proxy(
      server,
      event,
      {
        ...context,
        succeed: process.env.IS_OFFLINE ? context.succeed : resolve,
      },
    );
  });
};

Only request include Authorization in header has been crash.
my authorize function is working fine.

Thanks for the additional details. Is it 100% failure rate for those?

@brettstack Yup! it is 100%

Which region(s)?

I notice you both use context.callbackWaitsForEmptyEventLoop = false; and are overriding context.succeed. Might be relevant. We are investigating.

@shwetaskatdare My region ap-northeast-1
I am going to try remove callbackWaitsForEmptyEventLoop  setting

@brettstack You can take a test on AWS env with a request what include a long header like that
{
"Content-Type": "application/json",
"testheader": "suntinculpaquiofficiadeseruntmollitanimidestlaborum.eyJzdWIiOiJlMTg4YTJiZC0zNzAzLTRhMDYtODA2YS0yYzU2OTNjODlhZjQiLCJldmVudF9pZCI6IjRiYTgxN2UzLWZlYWItMTFlOC1hZTA2LTIzMTY1ZWVkMmYzYSIsInRva2VuX3VzZSI6ImFjY2VzcyIsInNjb3BlIjoiYXdzLmNvZ25pdG8uc2lnbmluLnVzZXIuYWRtaW4iLCJhdXRoX3RpbWUiOjE1NDQ2ODcyMjksImlzcyI6Imh0dHBzOlwvXC9jb2duaXRvLWlkcC5hcC1ub3J0aGVhc3QtMS5hbWF6b25hd3MuY29tXC9hcC1ub3J0aGVhc3QtMV9FNXJuZ1RGZXYiLCJleHAiOjE1NDQ2OTA4MjksImlhdCI6MTU0NDY4NzIyOSwianRpIjoiNTFkMzU0YzItZDMyZC00NWRmLTlhYzUtYzU4MjJjOTc3ZmNlIiwiY2xpZW50X2lkIjoiMWhqa3A0ZGRqZTN1aWVjbDcxcDU1amIyNDYiLCJ1c2VybmFtZSI6InRoaW5oYmcifQ.PzbFkSa11PvIbM-bVQ94YGpqr1U2vu5H2lWeknUSGrhad2ptwKKm_nj6lOHdmSjgkrzEGRcd8mvHsjmKHidq68bC5tG_R3wNBstbV9luu_SeM-3WMIZ3PyXzIpszbQKdzbz3o3pXj1in6E1RUb7C-wgob9r6GbmVIVqtND1Bbxk4RFopt4nUU4VmfizOB0e_anKq8qMKNS6FMYVMxr_6xB-E0TB1fraDLur1pAP9ilpJALgfYX1nSzEMnSi6VgtDrXcuGjEfIUSG49kf6LOsWCJUD2-qF_X3xoS9TCIIY_Jmsv_Qe1CicI6A-i0n0XbziYcMQFC6tt3Mhfz6TsNtAg"
}

testheader header value is a string with length is 937

It is also 100% failure for us as of today (13/12/2018), no code changes since yesterday. Using Amplify library to create the lambda function / express.
My current 'workaround' is switching all lambdas to use Node 6.10 (they are now working).

Same here, with nodejs 8.10, version 3.3.5 in eu-west-1, also no code change.
100% failure rate, app down. We are going to test a few things from now and report if we find a work around.

Same issue here since few hours.
nodejs 8.10, eu-west-1, 3.3.5 too.
Are you guys using your Lambda behind API Gateway (and using a JS frontend, like React)?
It looks like here when we send a request using Chrome (version 70 or 71) it fails. Firefox is fine.
Can't this be a change related to AWS Lamba itself? :disappointed:

Same here in EU-WEST-1

we have 3 stages deploy in eu-west-1.. only staging works.. Using API Gateway with Cloudfront

Same here again in eu-west-1. TypeScript -> node 8.10

Same here, with nodejs 8.10, version 3.3.5 in eu-west-1.

Same here, with nodejs 8.10, version 3.3.5 in eu-west-1 as well

Same here eu-west-1b  !
Ionic 3 =>API Gateway => Lambda = DynamoDB was working like a charm :(

So I guess we'll receive service credit for this outage? This is a long time for a major outage.
Is anyone investigated what changed on AWS side?

same, with nodejs 8.10, version 3.3.5 in eu-west-1.

Minimally reproducible testcase - upload this lambda:
Archive.zip
With this invoke payload:
https://gist.github.com/cianclarke/7a2d284747f6323e348f0012401f566b
Also reproducible locally, but using Node 8.14. Run testcase.js in same repo:
Cians-MacBook-Pro-2:deleteme cianclarke$ nvm use 8.14
Now using node v8.14.0
Cians-MacBook-Pro-2:deleteme cianclarke$ node testcase.js
9781
h1
h2
h3
h4
h5
h6
h7
h8
h9
h10
h11
reqerr
{ Error: write EPIPE
    at WriteWrap.afterWrite [as oncomplete] (net.js:868:14) errno: 'EPIPE', code: 'EPIPE', syscall: 'write' }
ERROR: aws-serverless-express connection error
{ Error: write EPIPE
    at WriteWrap.afterWrite [as oncomplete] (net.js:868:14) errno: 'EPIPE', code: 'EPIPE', syscall: 'write' }
succeed
{ '0': { statusCode: 502, body: '', headers: {} } }

Same here with a TS +Babel => node 8.10 config

We involved AWS Lambda to investigate. They are working on a fix.

anyone start working?

so looks like things are starting to come alive in eu-west-1 again for us anyway

Seems to be resolved? Anyone have any information what happened? Does this count as an official outage? Will it happen again?

Thanks everyone for reporting and providing instructions which helped Lambda diagnose the problem. We'll provide a detailed response after further investigation.

working in ap-northeast-1. Thank you.

Looking forward to the response. The "socket hang up" error seems to stem from the UNIX domain socket between aws-serverless-express and the actual Express app.

Same here, eu-west-1.

It's resolved for us, thanks for fixing the issue, we are looking forward to the report about the root cause.

@brettstack Are there any news regarding this issue? I just want to make sure how I can avoid this in the future

@brettstack any update for this issue? we have a similar issue now.

@fgcui1204 what's the similar issue? Is it a new regression?

@all Has everyone's problem been solved yet? How to solve it?

running into similar issues on local development. Have isolated it to be related to the cookie size in our case (maybe overall header size?)

I'm now able to reproduce the error consistently
After line https://github.com/awslabs/aws-serverless-express/blob/cb3b17d5fcfad911669e33433c191bb558945ed9/src/index.js#L136
i.e. when the request is initialized in forwardRequestToNodeServer, I watch the size of the header. Whenever JSON.stringify(req.getHeaders()).length >= 8180 the request fails with one of the errors below.
It might depend on the request itself a little bit, but the result seems to be consistent with https://nodejs.org/docs/latest-v8.x/api/http.html#http_http_maxheadersize which defaults to 8KB.
Most of the header size comes from headers['x-apigateway-event'] and headers['x-apigateway-context'], i.e. the hack to attach the event context to the request.
Possible Errors:
{ Error: socket hang up
    at createHangUpError (_http_client.js:342:15)
    at Socket.socketOnEnd (_http_client.js:437:23)
    at emitNone (events.js:111:20)
    at Socket.emit (events.js:208:7)
    at endReadableNT (_stream_readable.js:1064:12)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickDomainCallback (internal/process/next_tick.js:219:9) code: 'ECONNRESET' }

{ Error: write EPIPE
    at WriteWrap.afterWrite (net.js:868:14) errno: 'EPIPE', code: 'EPIPE', syscall: 'write' }

I get this error intermittently after switching my API Gateway's custom domain to a regional endpoint. This is to support a multi-region, latency-based routing policy. Maybe the headers are different between an edge optimized and a regional endpoint?? @zoellner I'm using your fork and it seems to fix this issue. Thanks!

I get this error today.
After I tried to change the header in API Gateway from json to html and updated the zip file in lambda, then I got the error.

Also got this error. I was able to work around it by changing my node version from v8.15 to v8.10. Not exactly the best fix, but it will allow you to get your work done.

I've run into this with serverless-offline, trying to upload a file via a POST. Ended up switching to https://github.com/dougmoscrop/serverless-http with which this error is not showing.

FWIW, I was getting this intermittently (~5% of the time under load). Removed serverless-offline and the problem went away.

This is still happening to me ~ .5% of requests. Not good.

Someone already tried nodejs10.x ? https://github.com/awslabs/aws-serverless-express/issues/234#issuecomment-492559413

Hi, sorry to up this again, I'm running a TS +Babel => node 8.10 config on eu-west-1 and I'm currently getting this error :
ERROR: aws-serverless-express connection error
{ Error: socket hang up
at createHangUpError (_http_client.js:299:15)
at Socket.socketOnEnd (_http_client.js:391:23)
at emitNone (events.js:111:20)
at Socket.emit (events.js:208:7)
at endReadableNT (_stream_readable.js:1064:12)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickDomainCallback (internal/process/next_tick.js:218:9) code: 'ECONNRESET' }

Am I the only one concerned ?

I try to link the dialog flow and AWS using the lambda function, but an error occurs.
Tell me how to fix it.
{
"errorType": "Runtime.ImportModuleError",
"errorMessage": "Error: Cannot find module 'aws-serverless-express'",
"trace": [
"Runtime.ImportModuleError: Error: Cannot find module 'aws-serverless-express'",
"    at _loadUserApp (/var/runtime/UserFunction.js:100:13)",
"    at Object.module.exports.load (/var/runtime/UserFunction.js:140:17)",
"    at Object. (/var/runtime/index.js:36:30)",
"    at Module._compile (internal/modules/cjs/loader.js:776:30)",
"    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)",
"    at Module.load (internal/modules/cjs/loader.js:653:32)",
"    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)",
"    at Function.Module._load (internal/modules/cjs/loader.js:585:3)",
"    at Function.Module.runMain (internal/modules/cjs/loader.js:829:12)",
"    at startup (internal/bootstrap/node.js:283:19)"
]
}

@seeheee probably your uploaded lambda function does not include the aws-serverless-express dependency

How do you include it?

@seeheee how do you deploy your lambda function?
via AWS UI?
Claudia.js?
serverless?
CloudFormation?
SAM?

I deploy your lambda function via AWS UI

so probably you haven’t included node_modules/aws-serverless-express

I don't know how to include a moduleㅠㅠ

Create a zip of your whole app
Il giorno 29 lug 2019, alle ore 14:22, seeheee <notifications<EMAIL_ADDRESS>ha scritto:
I don't know how to include a moduleㅠㅠ
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/awslabs/aws-serverless-express/issues/199?email_source=notifications&email_token=AAIJF4UVWYYBL5AEYOZBRRLQB3ORXA5CNFSM4GKDTF42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3ARCKQ#issuecomment-515969322, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAIJF4VSEHHY5DCZ5V5FFFLQB3ORXANCNFSM4GKDTF4Q.

any resolutions for this?  I am using node 10.X and I am getting this issue as well.  I am using serverless deploy to deploy the lambda function.  Any suggestions?

Same issue!! Any resolution?

I have the same issue. It was working fine while I was using nodejs8.10 but on node10 I get the socket hang-up 100% of the time.  I tried @zoellner fork but it did not work for me. I've reverted my function back to 8.10 which is going EOL very soon :(

I'm seeing the same issue with node10. No code changes just move the lambda function from 8.10 to 10. 8.10 is EOL soon. Does anyone have a resolution?

I'm seeing the same issue with node10. No code changes just move the lambda function from 8.10 to 10. 8.10 is EOL soon. Does anyone have a resolution? Thanks

perhaps give serverless-http a try....
Seems also more performant: https://github.com/fastify/aws-lambda-fastify#some-basic-performance-metrics

@emmanuel-omegaalexis you mentioned previously you're having issues with my fork. Can you let me know what the issue is and a snippet showing how you're calling the library?
I'm using my fork with node 8/10/12 without any problems. Note that my fork doesn't have any of the legacy resolver modes but just the promise mode.

Hi @zoellner, I have seen others have had success with your fork so I assume it is my implementation.
const awsServerlessExpress = require('aws-serverless-express');
const app = require('./app');
const server = awsServerlessExpress.createServer(app);

 exports.handler = (event, context) => awsServerlessExpress.proxy(server, event, context, {
     apiGatewayEventWhitelist: ['requestContext']
	 });

I changed to serverless-http and it is working @adrai  Thank you.

i encountered this issue when running sls offline
finally resolve it by installing aws cli
After installation go to cmd, type "aws configure"
enter AWS Access Key Id,AWS Secret Access Key, region
And the error is gone, the key value can be fake
See if it can help

Had the same issue, for me the issue was quite a tricky one, so I hope I'll save someone a bit time,
I had typescript export miss match, so my export default app;
had to be used as const server = awsServerlessExpress.createServer(app.default) and not const server = awsServerlessExpress.createServer(app)
the latter caused the socket timeout.


Cask request: PowerShell

Cask details
Name - PowerShell
Homepage - https://github.com/powershell/powershell
License - MIT https://github.com/PowerShell/PowerShell/blob/master/LICENSE.txt
Download URL - https://github.com/PowerShell/PowerShell/releases/download/v6.0.0-alpha.9/powershell-6.0.0-alpha.9.pkg
Description -

Microsoft PowerShell for Mac.  This is the full PowerShell and can connect with Windows or other systems running PowerShell (Linux or Mac).

More links:
https://msdn.microsoft.com/powershell
https://blogs.msdn.microsoft.com/powershell/2016/08/18/powershell-on-linux-and-open-source-2/
Guys, I don't recognize this universe.  Microsoft open-sourced (MIT License?!) PowerShell and ported it to Linux and Mac.  I feel dizzy.

Shouldn't this be a normal brew formula as the source is available to download, so brew can compile it on install?

@Hipska, you're right, in the long run, a Formula will definitely be a better option. Currently though, you first need to install the .pkg to even be able to build from source.

Indeed, I just saw that when reading the compiling instructions.


Update specs2-core, specs2-scalacheck to 4.10.3

Updates

org.specs2:specs2-core
org.specs2:specs2-scalacheck

from 4.8.3 to 4.10.3.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.specs2" } ]

labels: test-library-update, semver-minor

Coverage remained the same at 95.205% when pulling 1cad5cca1ac803f9031f64f0db6c3a953fb4ab6f on scala-steward:update/specs2-core-4.10.3 into 155c4ca5596b44cd9855dcca95406c1c19b512a6 on iheartradio:master.

Superseded by #138.

Superseded by #138.


On Page reload current template should be autoselected

Can you please elaborate the issue.

This issue have been fixed


Set test failing

Added Tests for Get-TargetResouce, Test-TargetResource, Set-TargetResource.  There is one failing test when running the test that sets IsEnabled.

Hi @matthewhatch, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

close pull request open, I'll reopen targeting dev branch


Bug: schedule sync workflow not running

github action not being executed by the schedule trigger. The synchronization workflow  is not periodically being executed to bring the changes from the upstream repo.

closed by #38


No response from the AC

Describe The Bug:
My Hisense AC does show up in the Home app, but it's unavailable.
To Reproduce:

Install plugin
Configure plugin
Open Home app in iOS/macOS device
Try to interact with the AC

Expected behavior:
AC shows up in HomeBridge and in the Home app on iOS/macOS
Logs:
[04/07/2024, 23:50:32] [homebridge-connectlife-ac] This plugin threw an error from the characteristic 'Current Temperature': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'cookieValue'). See https://homebridge.io/w/JtMGR for more info.
[04/07/2024, 23:50:32] [homebridge-connectlife-ac] This plugin threw an error from the characteristic 'Active': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'cookieValue'). See https://homebridge.io/w/JtMGR for more info.
[04/07/2024, 23:50:32] [homebridge-connectlife-ac] This plugin threw an error from the characteristic 'Cooling Threshold Temperature': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'cookieValue'). See https://homebridge.io/w/JtMGR for more info.
...
(logs from other plugins)
...
[04/07/2024, 23:50:35] [homebridge-connectlife-ac] This plugin slows down Homebridge. The read handler for the characteristic 'Swing Mode' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[04/07/2024, 23:50:35] [homebridge-connectlife-ac] This plugin slows down Homebridge. The read handler for the characteristic 'Heating Threshold Temperature' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[04/07/2024, 23:50:35] [homebridge-connectlife-ac] This plugin slows down Homebridge. The read handler for the characteristic 'Temperature Display Units' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[04/07/2024, 23:50:38] [homebridge-connectlife-ac] This plugin threw an error from the characteristic 'Swing Mode': Unhandled error thrown inside read handler for characteristic: Request failed with status code 429. See https://homebridge.io/w/JtMGR for more info.
[04/07/2024, 23:50:38] [homebridge-connectlife-ac] This plugin threw an error from the characteristic 'Heating Threshold Temperature': Unhandled error thrown inside read handler for characteristic: Request failed with status code 429. See https://homebridge.io/w/JtMGR for more info.
[04/07/2024, 23:50:38] [homebridge-connectlife-ac] This plugin threw an error from the characteristic 'Temperature Display Units': Unhandled error thrown inside read handler for characteristic: Request failed with status code 429. See https://homebridge.io/w/JtMGR for more info.
wakeUntilAPIReady: try 10
[04/07/2024, 23:51:10] [homebridge-connectlife-ac] This plugin threw an error from the characteristic 'Current Temperature': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'cookieValue'). See https://homebridge.io/w/JtMGR for more info.
[04/07/2024, 23:51:13] [homebridge-connectlife-ac] This plugin slows down Homebridge. The read handler for the characteristic 'Active' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[04/07/2024, 23:51:13] [homebridge-connectlife-ac] This plugin slows down Homebridge. The read handler for the characteristic 'Swing Mode' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[04/07/2024, 23:51:13] [homebridge-connectlife-ac] This plugin slows down Homebridge. The read handler for the characteristic 'Cooling Threshold Temperature' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[04/07/2024, 23:51:13] [homebridge-connectlife-ac] This plugin slows down Homebridge. The read handler for the characteristic 'Heating Threshold Temperature' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[04/07/2024, 23:51:13] [homebridge-connectlife-ac] This plugin slows down Homebridge. The read handler for the characteristic 'Temperature Display Units' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[04/07/2024, 23:51:15] [homebridge-connectlife-ac] This plugin threw an error from the characteristic 'Active': Unhandled error thrown inside read handler for characteristic: Request failed with status code 429. See https://homebridge.io/w/JtMGR for more info.
[04/07/2024, 23:51:15] [homebridge-connectlife-ac] This plugin threw an error from the characteristic 'Temperature Display Units': Unhandled error thrown inside read handler for characteristic: Request failed with status code 429. See https://homebridge.io/w/JtMGR for more info.
[04/07/2024, 23:51:15] [homebridge-connectlife-ac] This plugin threw an error from the characteristic 'Heating Threshold Temperature': Unhandled error thrown inside read handler for characteristic: Request failed with status code 429. See https://homebridge.io/w/JtMGR for more info.
[04/07/2024, 23:51:15] [homebridge-connectlife-ac] This plugin threw an error from the characteristic 'Cooling Threshold Temperature': Unhandled error thrown inside read handler for characteristic: Request failed with status code 429. See https://homebridge.io/w/JtMGR for more info.
[04/07/2024, 23:51:15] [homebridge-connectlife-ac] This plugin threw an error from the characteristic 'Swing Mode': Unhandled error thrown inside read handler for characteristic: Request failed with status code 429. See https://homebridge.io/w/JtMGR for more info.
Plugin Config:
{
"name": "Living Room AC",
"deviceNickName": "SplitAC",
"loginID"<EMAIL_ADDRESS>"password": "removed",
"debugMode": 1,
"platform": "ConnectLifeAcPlugin"
}
Screenshots:

(just to prove that the device nickname is correct)

Environment:

Plugin Version: 1.3.2 (tried with 1.3.0 as well)
Homebridge Version: 1.8.3
Node.js Version: 20.13.1
NPM Version: 10.5.2
Operating System: Debian 12 (bookworm) on Raspberry Pi 3B+

Hi, thanks for your issue report. (sorry for this late response)
Can you specify the answer for the following questions:

Your split AC model?
Your Raspberry PI is connected to network and have internet access? (can you ping the following hostnames: accounts.eu1.gigya.com, oauth.hijuconn.com, api.connectlife.io, connectlife.bapi.ovh ?)

Thanks for your confirmation.
Can I know if you use OAuth (Google, Apple or Microsoft) ?
After this answer, if you say no, then I will implement an advanced debug to be able to see what's going on and what response you receive from the APIs.

Sorry for the late reply, I read the notification e-mail and I forgot that there was a question for me to answer :)
No, I just log in to ConnectLife with e-mail and password, I don't use OAuth.


Bump version to fix 3rd-party components' vulnerabilities

This PR is to bump version to fix 3rd-party components' vulnerabilities found from BDBA and Snyk scan.

verified locally

verified locally

Thanks for your help!


[3.x] Improve user communication in the Add Item Type dialog

3.x version of https://github.com/godotengine/godot/pull/55927. It's bigger than the master PR because I took this opportunity to sync up some code that was different due to different featureset in 4.0. But this way it's easier to maintain and pick fixes/enhancements, so it makes sense to have parity.
Should be okay for 3.4, though it's not really a fix of any kind.

Thanks!

I prefer to skip for 3.4 unless it ends up being needed as prerequisite for some bugfixes. Less changes mean less risks of introducing bugs in the stable branch.


About the batch norm layer

Hi, why you set learning rate of the batch norm layer as zeros?
``layer {
name: "first_conv_bn"
type: "BatchNorm"
bottom: "first_conv"
top: "first_conv"
param {
lr_mult: 0
decay_mult: 0
}
param {
lr_mult: 0
decay_mult: 0
}
param {
lr_mult: 0
decay_mult: 0
}
}

look at issue #2


is vehicle_visual_odometry the same as vehicle_vision_position?

Hello,
I am using a motion capture system (mocap optitrack) to track the position of my drone indoors. When I am looking at the logs in flightplot I can only find a bunch of vehicle_visual_odometry fields in the list. Is this supposed to be the same thing as vehicle_vision_position?
log here: https://drive.google.com/open?id=1l4K-gR95Y18OR-Y5cK7DbhAv_2HAxofR

Yes.


Segmentation fault

atmosphere_gm$ ../harbored-mod/bin/hmod
Loading config file 'hmod.cfg'
Writing documentation to ./doc
Collecting data for table of contents
Excluded module atmosphere.catmosphere
Excluded module atmosphere.internal
Segmentation fault: 11

OS X (latest)
Project: https://github.com/9il/atmosphere_gm
Docs: http://9il.github.io/atmosphere_gm/doc/atmosphere.html
hmod master worked correctly 24 hours ago.
Timestamp: Tuesday, 06-Jan-15 11:15:15 UTC

Forgot to commit a change; should work now.

Thanks!


Add link to feedex for content item details page

Trello card
Background

As a Content Designer, I want the number of ‘support contacts’ shown on the content items details page to link through to the respective content item page in FeedEx, so that I can begin to explore and understand the issues that have been raised in more detail.

This is the super-simple MVP to link straight to the relevant page in FeedEx for a given page.
Before

After

Thanks for your review @pmanrubia. Have addressed what you have highlighted. Let me know if you spot anything else.

@pmanrubia I updated the wrong commit earlier. All should be as you asked now.

👍


code -r opens a new VSCode instance every time

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.87.2
OS Version: Windows 10 22H2 19045.4046

I'm having a weird issue trying to open my files from terminal in VSCode on windows. As far as I know using -r should force opening a file in the same instance of VSCode, but no matter how my settings is setup I still get a new instance opening up every time!
Already googled solutions and searched through stackoverflow, tried "window.openFilesInNewWindow": "off" and "window.openWithoutArgumentsInNewWindow": "off", no effects. I'm assuming this to be a bug, or am I missing something?

note: working on a Django project repo if it helps.

Steps to Reproduce:

Open a new terminal (PowerShell) in your workspace.
cd to your desired directory
Run code -r yourfile.py
A new instance of VSCode will pop up opening yourfile.py instead of yourfile.py opening in the same VSCode instance

Additional comments from someone trying to help me on stackoverflow:
Q: Is the behavior the same whether you're using Terminal or just a Command-Prompt console window?
A: Haven't checked it before, just tried and the result is the same. However just found out right after it opens a new instance, if I try to open any other files it actually uses the newly opened VSCode instance! but the main one where I'm at my workspace doesn't grab the file!

Found the culprit!
In case anyone else happen to have the same issue:
For some weird reason, if I run the executable from the command line, it would grab code -r filename.ext just fine. But if I open the executable using windows explorer it somehow gives me some sort of a local instance that terminal doesn't grab, even though both executables are running under the same username and privileges. Can't figure out why and how, but at least I've got a decent workaround for the moment thanks to this guy who's pointed me in the right direction on stackoverflow :)

@theparham could I suggest not closing this? I feel like this should be considered a bug... Or at least that if the maintainers think it isn't, a bit of explanation for this design would be nice.


[Question] Switch picker without leaving fzf-window

Info
Not related
Description
First of all thanks for making such a great plugin. fzf-lua is fast, responsive, and feature-rich, I cannot use neovim without it.
I sometimes find myself using the wrong picker only after I have typed several words in the search prompt, e.g. I was meant to live grep patterns in the project but I opened fzf files picker. In this case I want to switch to the live grep picker without leaving fzf window and perserve the previous cwd and the contents in the search prompt, but I haven't found a good way to achieve that.
Currently, I can map <C-_> in the on_create callback to fzf.builtin to switch picker without leaving fzf window, like this:
local fzf = require('fzf-lua')

fzf.setup({
  winopts = {
    on_create = function()
      vim.keymap.set('t', '<C-_>', fzf.builtin, { buffer = true })
    end,
  },
})

But this method has two drawbacks:

It does not preserve the contents in the search prompt
It does not keep previous search cwd

Could you please give me some hints or guidance on how to achieve this? Thanks!

First of all thanks for making such a great plugin. fzf-lua is fast, responsive, and feature-rich, I cannot use neovim without it.

Ty for your kind words @Bekaboo!
Your request is possible but it would require a bit more involved code as you’ll need to pass the new options to the new provider.

It does not preserve the contents in the search prompt

You can access the last query with require('fzf-lua').get_info().last_query.

It does not keep previous search cwd

While a bit more hacky, the last cwd (and all other call options) can be found in the last resume options require('fzf-lua').config.__resume_opts.cwd

Hi thanks for your reply, after searching in the source code I find another function require('fzf-lua').get_last_query() is it the suggested way of getting the last query than require('fzf-lua').get_info().last_query()?
I tried them both but none of them seems to work, here is my config:
local fzf = require('fzf-lua')

fzf.setup({
  winopts = {
    on_create = function()
      vim.keymap.set('t', '<C-_>', function()
        -- fzf.builtin()
        -- vim.api.nvim_feedkeys('', 'n', true)
        local info_last_query = fzf.get_info().last_query
        local last_query = fzf.get_last_query()
        local resume_opts = fzf.config.__resume_opts
        print('info_last_query: ' .. vim.inspect(info_last_query))
        print('last_query: ' .. vim.inspect(last_query))
        print('resume_opts: ' .. vim.inspect(resume_opts))
      end, { buffer = true })
    end,
  },
})

All three values (info_last_query, last_query, and resume_opts) are nil after I press <C-_> in fzf window. I've tried to call fzf.builtin() first and close the fzf window first but that does not help. What am I doing wrong here?

You’re correct get_last_query is better, I think info doesn’t even have the last query, my bad :)
The issue we have here is that you’re opening the builtin interface which also overrides the last query, there is also config.__resume_map which has resume values per provider but that means you’ll need to know which was the last interface used, I’ll think of something and do some testing and let you know how we can achieve what you’re after.

Another issue I see here is that you’re using a mapping in winopts.on_create, this abruptly closes the interface and opens another instead which also prevents the last query from being stored, this is better done via an action mapping.

The below adds the functionality you're after for all files providers, if you wish to do that for buffers as well you'd need to also configure actions.buffers:
local fzf = require('fzf-lua')
local actions = fzf.actions

fzf.setup({
  actions = {
    files = {
      ["default"] = actions.file_edit_or_qf,
      ["ctrl-s"]  = actions.file_split,
      ["ctrl-v"]  = actions.file_vsplit,
      ["ctrl-t"]  = actions.file_tabedit,
      ["alt-q"]   = actions.file_sel_to_qf,
      ["alt-l"]   = actions.file_sel_to_ll,
      ["ctrl-_"]  = {
        function()
          local opts = {
            query = fzf.config.__resume_data.last_query,
            cwd = fzf.config.__resume_data.opts.cwd,
          }
          fzf.builtin({
            actions = {
              ["default"] = function(selected)
                fzf[selected[1]](opts)
              end,
            }
          })
        end
      },
    },
  },
})

Thanks, it works incredibly well!

I encountered a similar problem, but with a slight difference. I attempted to create a finder that displays the MRU list when the query is empty, and shows the results from fd when the query is not empty.
I wasn't sure how to handle this 'switcher' with fzf-lua, so I ended up implementing it using the vanilla junegunn/fzf, using --bind=change:reload(dynamic_fzf_source.sh)
If possible, could anyone offer me some suggestions?

@hexh250786313, you are tryin to mix and match a “live” reload mechanism with fuzzy matching, while possible it’s a bit tricky, if we ignore for a second displaying the MRU on backspace you can change back to fuzzy with enable-search:
--bind "change:reload(fd …)+unbind(change)+change-prompt(fd> )+enable-search"

It might be possible to create go back to the MRU on backspace with a condition that tests the query with {q} but that means you can’t unbind change. This is just atop of my head, I might be able to come up with something better if I think about this longer :)

@hexh250786313
I have been searching far and wide for this behavior, by any chance could you share your dotfiles for this?

@ibhagwan is it possible to achieve this kind of thing within fzf-lua?

@ibhagwan is it possible to achieve this kind of thing within fzf-lua?

Not really sure what you’re asking, this is an old issue, by “this kind of thing” do you mean the OP/title or something else? Whatever the question may be it probably is possible depending on how much effort you’re willing to invest.

@ibhagwan apologies I mean the MRU/files switch that @hexh250786313 was asking about

@dan-cooke, my answer https://github.com/ibhagwan/fzf-lua/issues/974#issuecomment-1873990328 still stands, I can also think of another solution using the Linux headless wrapper used by fzf-lua, take a look at rg_glob_fn from #373, but then again it won’t be fuzzy search since it’s for live_grep.
I can think of many different approaches, all requires to make use of fzf’s change:… event, if you’re serious about it you’ll have to do some reading of the fzf manual and issues to understand how to use it and what’s possible, anything that can be done with vanilla fzf can be done with fzf-lua (with richer functionality), once you have basic code that does what you want I can help you refine it.

@ibhagwan thanks so much for your helpful replies! I am quite new to Lua/Neovim plugins so I wasn't quite sure how to call the underlying fzf from neovim.
I had a look at @hexh250786313 's dotfiles and I think I'm on the right track.
I will post my solution in here when I'm done!

@ibhagwan so I have this
vim.keymap.set('n', '<C-p>', function()
	fzf.oldfiles({
		prompt = 'Recently Used > ',
		path_shorten = true,
		file_name_only = true,
		cwd_only = true,
		keymap = {
			-- These override the default tables completely
			-- no need to set to `false` to disable a bind
			-- delete or modify is sufficient
			builtin = {
				-- neovim `:tmap` mappings for the fzf win
				["<F1>"]     = "toggle-help",
				["<F2>"]     = "toggle-fullscreen",
				-- Only valid with the 'builtin' previewer
				["<F3>"]     = "toggle-preview-wrap",
				["<F4>"]     = "toggle-preview",
				-- Rotate preview clockwise/counter-clockwise
				["<F5>"]     = "toggle-preview-ccw",
				["<F6>"]     = "toggle-preview-cw",
				["<S-down>"] = "preview-page-down",
				["<S-up>"]   = "preview-page-up",
				["<S-left>"] = "preview-page-reset",
				["<C-p>"]    = "down",
				["<C-S-p>"]  = "up",
			},
			fzf = {
				-- fzf '--bind=' options
				["ctrl-z"]     = "abort",
				["ctrl-u"]     = "unix-line-discard",
				["ctrl-f"]     = "half-page-down",
				["ctrl-b"]     = "half-page-up",
				["ctrl-a"]     = "beginning-of-line",
				["ctrl-e"]     = "end-of-line",
				["alt-a"]      = "toggle-all",
				["change"]     = "reload(fd …)+unbind(change)+change-prompt(fd> )+enable-search",
				-- Only valid with fzf previewers (bat/cat/git/etc)
				["f3"]         = "toggle-preview-wrap",
				["f4"]         = "toggle-preview",
				["shift-down"] = "preview-page-down",
				["shift-up"]   = "preview-page-up",
				["ctrl-p"]     = "down",
				["ctrl-n"]     = "up"
			},
		},

	})
end)

But there is a problem, the fd search results are always empty

Any ideas?

But when I switch from oldfiles to fd - the old files is not updated with the entry I select, is there something I can do about that?

That’s because the shada file isn’t written to disk when you open a file, it is online added to the shada when you exit neovim.

 include_current_session = true

This is a good solution, another way would be to an autocmd that updates the shada file on BufReadPost.

This is great info, thanks @ibhagwan !
For any future people like me when you start a new sessions and you try find a buffer, but you havent opened it yet, you can switch to the file picker with CTRL+k like this (also includes switching back to buffers again with <Ctrl+k>):
        actions = {
            buffers = { -- When on :buffers, pressing <Ctrl-k> will resume with files
                ["ctrl-k"]  = {
                    function()
                        local opts = {
                            query = fzf.config.__resume_data.last_query,
                            cwd = fzf.config.__resume_data.opts.cwd,
                        }
                        fzf.files(opts)
                    end
                },
            },
            files = { -- When on :files, pressing <Ctrl-k> will resume with buffers
                ["ctrl-k"]  = {
                    function()
                        local opts = {
                            query = fzf.config.__resume_data.last_query,
                            cwd = fzf.config.__resume_data.opts.cwd,
                        }
                        fzf.buffers(opts)
                    end
                },
            },
        },

Ty @mangelozzi, btw, I’ve made the last query more accessible from actions:

["ctrl-k"]  = function(sel, opts)
  print('q:', opts.last_query)
end

Ty @mangelozzi, btw, I’ve made the last query more accessible from actions:

Thanks! I made it more compact with your suggestion:
        actions = {
            buffers = { -- When on :buffers, pressing <Ctrl-Space> will resume with files
                ["Ctrl-Space"] = function(_, opts) fzf.files({ query = opts.last_query }) end, -- _ = sel
            },
            files = { -- When on :files, pressing <Ctrl-Space> will resume with buffers
                ["Ctrl-Space"] = function(_, opts) fzf.buffers({ query = opts.last_query }) end, -- _ = sel
            }
        },

Looks great @mangelozzi!