Roll Flutter Engine from f5c1650c7acc to ba78bb310ee6 (7 revisions)

https://github.com/flutter/engine/compare/f5c1650c7acc...ba78bb310ee6
2023-07-21<EMAIL_ADDRESS>Roll Dart SDK from 6e79151ce988 to 921613a055ff (1 revision) (flutter/engine#43892)
2023-07-21<EMAIL_ADDRESS>Roll Skia from 3dd45617581b to 8388ec4d242c (1 revision) (flutter/engine#43891)
2023-07-21<EMAIL_ADDRESS>Roll ANGLE from b60068009dca to 2e190280f5c5 (2 revisions) (flutter/engine#43890)
2023-07-21<EMAIL_ADDRESS>Roll ANGLE from f2e0f8a0b236 to b60068009dca (1 revision) (flutter/engine#43887)
2023-07-21<EMAIL_ADDRESS>Roll Dart SDK from 8662af7d9aa3 to 6e79151ce988 (2 revisions) (flutter/engine#43885)
2023-07-21<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from -SaPL-46jpiYbnCAu... to WH3AaCa4DtVERww1v... (flutter/engine#43884)
2023-07-21<EMAIL_ADDRESS>Roll Skia from 4857e876d8cf to 3dd45617581b (1 revision) (flutter/engine#43883)
Also rolling transitive DEPS:
fuchsia/sdk/core/mac-amd64 from -SaPL-46jpiY to WH3AaCa4DtVE
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC bdero@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

AutoRoller is stopped; closing the active roll.


Fix/small files refactor a

refactor of a few smaller files and added in a console to test issue of zone not loading properly on start on .org

Your review app has been deployed and is available at 'http://<IP_ADDRESS>:80'.Learn More about how to test and provide feedback for the app.

Your review app has been deployed and is available at 'http://<IP_ADDRESS>:80'.Learn More about how to test and provide feedback for the app.


conda install -c conda-forge keras

conda install -c conda-forge keras gives me
PackageNotFoundError: Packages missing in current channels:

keras

We have searched for the packages in the following channels:

https://conda.anaconda.org/conda-forge/win-64
https://conda.anaconda.org/conda-forge/noarch
https://repo.continuum.io/pkgs/free/win-64
https://repo.continuum.io/pkgs/free/noarch
https://repo.continuum.io/pkgs/r/win-64
https://repo.continuum.io/pkgs/r/noarch
https://repo.continuum.io/pkgs/pro/win-64
https://repo.continuum.io/pkgs/pro/noarch
https://repo.continuum.io/pkgs/msys2/win-64
https://repo.continuum.io/pkgs/msys2/noarch

Even though it is listed under the search

FYI, this command just worked for me on macOS 10.12.4, so it's likely windows specific.
Though I wasn't able to locate keras at https://repo.continuum.io/pkgs/free/osx-64/. Maybe I looked in the wrong place.

Strike that. I'm encountering that same error message as OP when I run "conda create --name env python=3 keras" on my macOS 10.12.4 machine.
This is despite the fact that "conda install -c conda-forge keras" exited successfully.

In the end, I got keras installed within a conda environment by running the following three commands in order:
conda create --name env python=3
source activate env
conda install -c conda-forge keras
That may or may not be helpful for you.

Seems the server was just temporarily down


Create comparer plugin for enum values

These changes have been added and published to Nuget - https://www.nuget.org/packages/BorsukSoftware.Testing.Comparison.Core/1.0.3


Episode #260 - Missing template error

I am trying to run chatter-after just as I cloned it from repo, faye running on thin just as described. Unfortunately, after visiting http://localhost:3000/ and hitting "Send" button, HTTP 500 is returned from rails (and 200 from faye):
Template is missing
Missing template messages/create with {:handlers=>[:erb, :rjs, :builder, :rhtml, :rxml], :formats=>[:html], :locale=>[:en, :en]} in view paths "/home/ernest/programming/sandbox/ruby/episode-260/chatter-after/app/views"

I've fixed 260 episode, look at the episodi at my repository, only you have to update the app to rails 3.1
https://github.com/rderoldan1/railscasts-episodes/tree/to-rails-3.1/episode-260

@vezu tell me  the error please

#hola


Can this tool read/write KeyFile?

I don't find anything related to KeyFile in the documents....
The previous project qd-cae-python has it.
Will this capability be added into lasso-python?

No we don't have it and no contributor has so far intended to do so. If someone wants to do it, it would be great though.
Most people do input file manipulation only based on a few string operations and don't need a fully capable key file composer so it is very niche. Another hurdle is, that parsing the key files is difficult as the format is very arbitrary such as varying field lengths or additional fields are all of a sudden present, so one has to go through the entire manual and program every edge case. And even then with every new version things might break due to alterations when new fields are added (seomtimes also undocumented). But hey we did the same pain with d3plot.


ASA03 - Change Password for Existing User

ID: ASA03
System: AMYCA
Use Case: Change Password for Existing User
Actor: System Admin
Precondition: User Logged in

MSS:

Amyca: Request for command
User: Enter command cp user-Id
Amyca: Request for new password
User: Enter new password
Amyca: Request for new password again
User: Enter password again
Amyca: Confirm updated
use case end

Extension:
2a. Amyca: Error! Wrong user-ID/wording
use case step: 1 to 2 again until accepted command
6a. Error! Password not match
use case step: 3 to 6 repeat until password match

It has been completed


AppVeyor build is broken

Do we fix it? So we remove it?

I was never fond of it, so if you would like to remove it, let's get rid of it.


post data for file

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 80.645%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sis_provisioner/views/api.py
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
600

Relevant Lines:
744

💛  - Coveralls


Fix CachingSdkResolverService concurrency.

The documentation for ConcurrentDictionary.GetOrAdd() states:

If you call GetOrAdd simultaneously on different threads, valueFactory may be called multiple times, but only one key/value pair will be added to the dictionary.

In all of my testing, a particular SDK was never resolved more than once so I didn't think we had a problem.  However, on an NGen'd MSBuild, I noticed that an SDK was being resolved multiple times.  This is because the GetOrAdd() method does not guarantee that a method is only called once.  Instead, it guarantees that if multiple threads call the method simultaneously they will all receive the same return value.
So the fix is to return a Lazy<T> instead.  This means that multiple threads could new up multiple instances of Lazy but all threads will receive the same Lazy.  They will all wait for the same result when accessing Value so the SDK will only be resolved once and the value is then cached for subsequent calls.
Fixes #4798

I was able to devise a test which I ran against master and it fails. So this definitely fixes it!


204 dataframe dataset

Dataframe to dataset conversion utility (xarray function wrapper).
Closes #204

Codecov Report

Merging #205 into master will decrease coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #205      +/-   ##
==========================================
- Coverage   74.59%   74.57%   -0.02%
==========================================
  Files          68       67       -1
  Lines        9006     8995      -11
==========================================
- Hits         6718     6708      -10
+ Misses       2288     2287       -1

Impacted Files
Coverage Δ

cate/ops/xarray.py
100% <100%> (ø)
:arrow_up:

cate/core/workspace.py
71.51% <0%> (ø)
:arrow_up:

cate/ops/__init__.py
100% <0%> (ø)
:arrow_up:

cate/ops/pandas.py

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 1994bc2...ef21e6f. Read the comment docs.

I prefer overloading most of our operations so that they can work on both (Geo)DataFrames and xr.Datasets. This is also more pythonic.


Enable Theming

Remove CSS mixins (we may need to expose some states of dates in the calendar for it to be possible to replace existing mixins in the new theme)
Define themable parts (document!)
Extend Vaadin.ThemableMixin
Add a default theme (align with text-field, button etc. default theme)
Add a theming demo with bootstrapish look


fix(userspace/libsinsp): solve data race and segfault in logger

What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area libsinsp
Does this PR require a change in the driver versions?
What this PR does / why we need it:
Some refactors related to the logger and the switch to string views caused this couple of issues.
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
NONE

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

uhm it seems one of these commits should go in a 0.14.2 and the other no. I will use milestone 0.14.2

LGTM label has been added.  Git tree hash: 4368d1dcbfd976620cdc4f99344a387c6520103b

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Get Updated Upto PHP 7.2

Get Updated from Base Repo Upto PHP 7.2
Will do PHP 8 compatibility after this.
@jkudish FYI

It looks like the original repo already supports 7.2, doesn't it?

@jkudish Yes, that's why I've created the Update PR to our fork from the Original Repo. So that we can add PHP-8 on top of it.


Added support for 10.90 & 10.91. Fixed a small launch client bug. Cha…

…nged the size of ClientChooser window.

otserv not work more?

Really need a update to 10.00 or tibia 11!!

Hey, someone can update for 10.00 ?


Allow transposition from and to minor keys

The library already has a relative key table, so to enable minor to minor transpositions, the given key can be checked for minorness and apply the appropriate relative key transformations before and after transposition.

This feature has been added in the latest commit. toKey now handles minor key signatures.


Update Dockerfile

peer

'only last space is editied

Why is there a PR that just adds a space to the end of the Dockerfile?


MCEdit Crashing

MCEdit Unified bug report template. For MCEdit 2.0 bugs see here : https://github.com/mcedit/mcedit2
Description of Issue:whenever i try to get on mcedit when i go onto a world it says unhandled exeption
MCEdit Version:version 14
Minecraft Version the world was last opened in:13.1
Operating System:
A screenshot or full text of the error from the console:MCEdit version: 2.0.0-beta14
Python version: 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC v.1500 32 bit (Intel)]
Platform: win32
System version: Windows-10-10.0.17134
Processor: Intel64 Family 6 Model 58 Stepping 9, GenuineIntel
Obtained a GL context with this format:
Valid: True
Version: 4.6
Hardware Accelerated: True
Depth buffer: True, 24
Double buffer: True
Rendering profile: PySide.QtOpenGL.QGLFormat.OpenGLContextProfile.CompatibilityProfile
Driver info:
GL_VERSION: 4.6.0 NVIDIA 388.13 (4, 6)
GL_VENDOR: 'NVIDIA Corporation'
GL_RENDERER: 'GeForce GTX 650/PCIe/SSE2'

Unhandled Exception
Traceback (most recent call last):
File "mcedit2\editorsession.py", line 1643, in viewOffsetChanged (self is a EditorTab)
File "mcedit2\worldview\minimap.py", line 187, in currentViewMatrixChanged (self is a MinimapWorldView)
File "mcedit2\util\raycast.py", line 30, in rayCastInBounds
File "mcedit2\util\profiler.py", line 73, in _wrapper (self is a Profiler)
File "mcedit2\util\raycast.py", line 77, in rayCast
File "mcedit2\util\raycast.py", line 215, in advanceToChunk
File "mceditlib\worldeditor.py", line 831, in getChunk (self is a WorldEditorDimension)
File "mceditlib\worldeditor.py", line 499, in getChunk (self is a WorldEditor)
File "mceditlib\cachefunc.py", line 77, in call
File "mceditlib\worldeditor.py", line 477, in _getChunkDataRaw (self is a WorldEditor)
File "mceditlib\anvil\adapter.py", line 922, in readChunk (self is a AnvilWorldAdapter)
AnvilChunkFormatError: [Errno Error loading chunk: KeyError('Key Blocks not found.',)] None: <traceback object at 0x1074A8C8>
How to reproduce:after downloading open mcedit2-win32 open it in win rar and select mcedit2-win32, then take mcedit2.exe and mcedit2files and select them both and bring them onto your home screen. then go to minecrafts file location and next to minecraft and desktop.ini make a new folder called mcedit. then  take mcedit2.exe and mcedit2files from before and put them in that folder.
then open minecraft go onto a world, then run mcedit, select the world to  edit and then the error will show up.
Read before submitting
If we are not able to reproduce the error, we may ask for you to submit a world so we can test it. Same process for schematics.
If you have included enough information for each section, please delete the above header and all the text below.

This is a bug with MCEdit 2.0 which is a separate project. Please report it at the correct GitHub repository: https://github.com/mcedit/mcedit2


Provide example for Strict-Transport-Security (HSTS)

Hello,
Can you provide an example how we can implement HSTS using an rule engine in combination with Azure Front door.
Thanks,

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

ID: b449587c-dcda-ceb5-8c19-8a1f42c8698f
Version Independent ID: d7e52b54-e8f8-af1b-7944-03d127f94c9d
Content: Azure Front Door
Content Source: articles/frontdoor/front-door-security-headers.md
Service: frontdoor
GitHub Login: @megan-beatty
Microsoft Alias: mebeatty

@ward0 Thanks for the feedback! To achieve HSTS, you will need to have HTTPS redirection, and add the HSTS header.
We do not have a single doc to outline the full process, so I am assigning the issue to the content author to evaluate and update as appropriate.

@TravisCragg-MSFT  Thanks for the link to the HSTS header page, that helped us further a lot 👍

@ward0 We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


cgroup2 CI

Fedora 32 Vagrant is used for testing cgroup2.
Currently the test is executed with RUNC_FLAVOR=crun.

Does the Vagrantfile need to be in the root?

Yes AFAIK


Improve test helpers and related documentation

Following up the #275 (Add render_view test helper).
Improving render_view helper method:

Now the render_view do not depend on ActionView::TestCase::TestController, making it Rails independent.
controller is memoized
If application doesn't have Nokogiri, MissingTestDependency will be raised with explanation message.
More tests was added
Testing docs has now 3 pages:

Getting Started
RSpec
Minitest

Minitest page has "Asserting with Capybara" with "Coming Soon" alert, because we need to define a page method in our helper to Capybara match against it. This will be done in another PR.

Where did all of these docs go?


Clojure deref operator (@) missing

(Original issue 824 created by OttoAllmendinger on 2012-12-10T16:35:06.303471+00:00)
example use: http://clojure.org/refs
Suggested patch attached

(Original issue 824 last updated on 2012-12-25T10:18:54.283461+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)

(Original comment by birkenfeld on 2012-12-25T10:18:54.276982+00:00)
Closes #824: add clojure "deref" operator, a single @.
→ <>


Use shorter namespace prefixes.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: ozevren
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pkg/OWNERS [ozevren]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: nmittler, ozevren
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pkg/OWNERS [nmittler,ozevren]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ozevren: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
af07db5b18e39e76e01fa1e5e79f1a0820cf84a3
link
/test istio-pilot-multicluster-e2e

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

@ozevren: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
af07db5b18e39e76e01fa1e5e79f1a0820cf84a3
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
af07db5b18e39e76e01fa1e5e79f1a0820cf84a3
link
/test istio-integ-k8s-tests

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

@ozevren: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
af07db5b18e39e76e01fa1e5e79f1a0820cf84a3
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
af07db5b18e39e76e01fa1e5e79f1a0820cf84a3
link
/test istio-pilot-multicluster-e2e

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


Changelog / History file?

Hi,
Looking to upgrade passport from 0.1.17 to latest. Couldn't find any release changelog or history files. Can you point me in the right direction?
:cake:

+1
Please.

I ended up here again when looking for changes between 0.2.2 —> 0.3.0
By semver that means new features, but no breaking changes. Fingers crossed?

+1

@simison not quite it seems #400

Other issues that should be closed/combined into this one:
#206
#202
#265

Same question with v3 -> v4. What changed? I would rather [not read the diff](https://github.com/jaredhanson/passport/compare/v0.3.2...v0.4.0.

Yep, ended up here again yesterday. Pretty please?
I tried to read commit logs but it wasn't so easy. Ended up crossing my fingers and just trusting our test automation handling it.

3 years later and here I am looking for a changelog too. Please?


More informative alert when attempting to message non-v3 users

(Short-term fix before https://github.com/ephemeraHQ/converse-app/issues/60)
From Peter:
I  observed something last night a few times: when people downloaded the new app, they went to make a group, then searched and added people they knew. Both saw the "" which confused them as they both said, "I thought they had used XMTP".
Maybe in the early state, we could add more language to the alert like. "<username needs to be on the latest version of Converse to be added to a group">.
Slack Message

In components/Search/NavigationChatButton.tsx when canGroupMessage is not allowed, update the text we are using
Make sure to place it in translations file as well


helm3: --debug output sent to STDERR - results in pipeline engine marking stage as failed

When utilizing the --debug flag with helm3, the output is sent to STDERR.  This will result in most (if not all) pipeline engines deciding "something went wrong!" and marking the stage as failed causing the pipeline to abort.  In actuality, nothing went wrong.
To confirm that debug content is sent to STDERR:
$ helm3beta3 upgrade --namespace ns-dev --install --recreate-pods --force --values deployment/helm/values/dev-current.yml --wait --atomic project-ns-dev deployment/helm/chart --debug 2> stderr.txt
NAME: project-ns-dev
LAST DEPLOYED: 2019-09-19 14:42:13.887290836 -0400 EDT m=+5.527301829
NAMESPACE: ns-dev
STATUS: deployed
Release "project-ns-dev" has been upgraded. Happy Helming!
NAME: project-ns-dev
LAST DEPLOYED: 2019-09-19 14:42:13.887290836 -0400 EDT
NAMESPACE: ns-dev
STATUS: deployed

$ cat stderr.txt
history.go:52: [debug] getting history for release project-ns-dev
upgrade.go:79: [debug] preparing upgrade for project-ns-dev
upgrade.go:88: [debug] creating upgraded release for project-ns-dev
upgrade.go:94: [debug] performing update for project-ns-dev
client.go:140: [debug] checking 29 resources for changes
wait.go:50: [debug] beginning wait for 29 resources with timeout of 5m0s
upgrade.go:101: [debug] updating status for upgraded release for project-ns-dev

This causes Azure DevOps (ADO) to mark the stage as failed with the message
2019-09-19T18:17:28.6285116Z ##[error]history.go:52: [debug] getting history for release project

Have not tested this out with other pipeline engines, but if I remember correctly, they behave similarly.
Should the debug output really be sent to STDERR?

Output of helm version:
$ helm3beta3 version
version.BuildInfo{Version:"v3.0.0-beta.3", GitCommit:"5cb923eecbe80d1ad76399aee234717c11931d9a", GitTreeState:"clean", GoVersion:"go1.12.9"}
Output of kubectl version:
$ oc version
oc v3.11.0+8de5c34
kubernetes v1.10.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO
Server https://ocp-console.dev.company.internal:443
openshift v3.11.104
kubernetes v1.11.0+d4cacc0
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
OpenShift on VMWare

POSIX defines the standard error stream as "for writing diagnostic output". The GNU C standard library defines it similarly as "used for error messages and diagnostics issued by the program". So, it's an issue with Azure DevOps reporting incorrectly; output on stderr should not be considered an error.

I agree.  Talked with some of my peers and they pointed out the POSIX standards as well.
Cheers!

I believe #7409 was in relation to this issue. If using v3.1.0-rc.1 or newer, should have the changes such that ADO does not mark it as failed.  I haven't personally tested this yet, but sharing my follow-up investigation on this issue :)

@hhellbusch This should have been delivered in 3.0.3

@hickeyma , what has been delivered in 3.0.3? Since my current build pipeline still fails only when I enable --debug.
I'm using Helm 3.1.0

The fix #7409 mentioned in https://github.com/helm/helm/issues/6461#issuecomment-584809517 by @hhellbusch was delivered  in 3.0.3

@hickeyma so the cause for this issue itself is not solved then right (adding --debug causes the build to fail due to writing to STDERR)?
Just that seperate issue was resolved?

This issue was closed with the description in https://github.com/helm/helm/issues/6461#issuecomment-534122634

@devedse there is a feature flag in Azure Devops bash tasks that will prevent builds from failing when there's output present on STDERR. If you enable that feature, the issue will go away.
https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/bash?view=azure-devops#yaml-snippet
From that example, you should have
- task: Bash@3
  inputs:
    failOnStderr: false

Hey @bacongobbler I've tried that on a similar task to skip stderr output. Does that also ignore actual errors?

Azure devops should still fail in those cases as Helm will return with a non-zero exit code.


Default concurrency causing issues.

Hi!
I don't know if this is related to #411 , but we are having some issues that seems to be related to the concurrency flag
When running without specifying --concurrency in sync or apply , we are seeing a bunch of errors like this:
Upgrading <path-to-chart-1>
UPGRADE FAILED
ROLLING BACK
Error: release: "<name-of-chart-2>.<some-version>" already exists
Error: UPGRADE FAILED: release: "<name-of-chart-2>" already exists

As far as I can tell, it looks like it is mixing up charts and values from different entries in our helmfile (we have about 9 releases in this particular helmfile). Going with any value other than concurrency 1 seems to give the errors.

@amardomingo are you defining the same release multiple times?  I have somewhere between 2-3 dozen releases and I have not seen any concurrency issues except for my box slowing to a crawl.  I typically run it with 8 concurrency.

@sstarcher unless I am absolutely blind, no. I have a bunch of releases with similar names (for example, I have "istio", "istio-init", "cassandra-istio" and so on), but I don't have any duplicated releases.
Anyhow, I have changed the binary of helmfile from direct downloading it from the releases page to installing it with homebrew, and I don't seem to be able to replicate the problem again. I know that does not make much sense (if any at all), but it's the only thing I've changed about helmfile lately.
Should I close  the issue?

@amardomingo Hey! Thanks for the report.
You shouldn't close this! As myself being a helmfile user, I'll report here if I get to reproduce this. Hard to say reinstalling or changing the source of helmfile binary makes difference, but worth noting as we have no idea why this is happening yet.

This sounds similar to an issue we had when running diff with concurrency set to 3 (https://github.com/roboll/helmfile/issues/410), after updating everything this just seemed to stop so I closed the issue but I never found the root cause, I'm just mentioning this since it might help with the debugging.

@amardomingo Btw, which version of helmfile are you using?

Currently I'm using v0.45.3 in Mac, installed with homebrew.
When I created the issue I was using a direct download from the releases page, I think it migth have been v0.45.2, but when I ran "helmfile -v" it only said "version". I currently can't replicate that behaviour, so I'm starting to think that there was something wrong with my system.
I just downloaded all v0.45.x versions from he releases page in a colleague's Mac and he has not been able to replicate that behaviour either :-(

@amardomingo Thanks for confirming! I guess it's fixed in recent versions of helmfile then.
I've heard about possible concurrency-related bugs like yours before. I wasn't aware of the exact issue, but hoping to fix it altogether, I've refactored all the duplicated code/logics around the concurrency feature as a part of #442, which has released as part of v0.43.0. So probably helmfile, starting v0.43.0, won't see the issue.
Regarding your helmfile -v output, perhaps it may be due to that it was installed via go get. We have a dedicated issue for #304, but have no solution at the moment (yet).

Closing this as already fixed. Please feel free to reopen if you still encounter this using recent versions of helmfile!


daemon/graphdriver/zfs fix lint errrors/warnings

Addresses #14756
Signed-off-by: Srini Brahmaroutu<EMAIL_ADDRESS>Not sure if this package is already listed or not.

I think it needs to be added to the list.

@vdemeester  Update as per your comments.

LGTM

LGTM


Update faq.md to fix error of clearing contents

$getRoot need to be called to return a root node.
error screenshot:

If you can accept the CLA we'll get this merged.

Thanks, I've signed the CLA but it seems the bot hasn't update the label.


Google Authenticator tokens not working (sometimes...)

I'm having trouble using Google Authenticator tokens.  I have a couple local development versions of the server (Django's built in and a couple QA servers nearly identical to my prod environment).  On every setup other than my prod server (an AWS Ubuntu instance), Google tokens work fine.  On that particular server, Google tokens are always rejected as invalid ("Entered token is not valid").  I have another Ubuntu (non-AWS) server running the exact same code, same server configuration files, etc. and it works fine.
I really don't know anything about how this token generator works.  I did some digging into this code (and the django_otp code), but I can't see anything glaring that would cause this problem.
Does anyone have any idea what would cause the Google Authenticator tokens to be rejected in this context?  Or perhaps where I should be looking or variables I should tweak?  My first reaction is that it's a configuration error with my server, but I'm not sure what I would've screwed up that could cause this error.
Thanks for any help or information!

Wow, do I ever feel dumb.  I have spent more than a few hours trying to figure out what was going on here...
So it looks like my server's time was out of sync.  I kind of assumed that Ubuntu probably did some sort of fancy time syncing auto-magically.  A simple:
ntpdate -s time.nist.gov
and I was on my way with everything working as expected.
I apologize for creating an issue when the solution was right in front of me.  I'm going to go ahead and close this one.

I was also thinking of a clock synchronisation issue as well. I'm glad you found the solution as well!

I am having a problem this morning all my users cant use token every time message is invalid token, I truncate table and start process again but in new process of new token error message is the same. What is going on I dont know.

Have you looked into the solution listed in this question; thus checking if the local server's time is synced with UTC?


🐛 BUG: Failed to find "undefined" in https://github.com/cloudflare/worker-template-router.git

Which Cloudflare product(s) does this pertain to?
Wrangler
What version of Wrangler are you using?
2.8.0
What operating system are you using?
node.js VSCode Dev Env
Describe the Bug
When I run wrangler generate my-app https://github.com/cloudflare/worker-template-router, I get the following message:
⛅ wrangler 2.8.0
-------------------
Creating a worker in my-app from https://github.com/cloudflare/worker-template-router

✘ [ERROR] Failed to find "undefined" in https://github.com/cloudflare/worker-template-router.git.

Can you help?

Hey! 👋 I'm unable to reproduce this. Which operating system are you using? What is the output of --version?

Hi! I came here specifically for this issue, since I have exactly the same one. I had wrangler 2.7.1 and now I tried to update to 2.9.1 and get the same error. Windows 10, tried in Powershell, Command Prompt, and the new Terminal (which is still powershell I guess). No dice, I got exactly the same error as above:
F:\cloudflare\workers>wrangler generate my-ts-project https://github.com/cloudflare/worker-typescript-template
 ⛅ wrangler 2.9.1
-------------------
Creating a worker in my-ts-project from https://github.com/cloudflare/worker-typescript-template

X [ERROR] Failed to find "undefined" in https://github.com/cloudflare/worker-typescript-template.git

If you think this is a bug then please create an issue at https://github.com/cloudflare/wrangler2/issues/new/choose

Interesting point however, I tried to visit https://github.com/cloudflare/worker-typescript-template , curious as to what might be undefined here, and it now says:

⚠ Warning: This template is no longer maintained

For something that's directly linked and used from the workers dev, that's worrying - perhaps someone might update https://developers.cloudflare.com/workers/get-started/quickstarts/ to reflect whatever current methodology should be used? Apparently using "wrangler init" but the page linked from that github doesn't talk about init, just about installing.
From the perspective of a user trying to get into workers, this is a pretty difficult experience to navigate!


All tests always run for cargo

Hi!
Thank you for awesome plugin, it realy helpful!
All project tests always run regardless of the command I run.

Yes, the cargo vim-test runner currently doesn't handle test files or nearest tests. I assume that's because cargo test didn't support this functionality at the time of writing. Has this changed?

Yes. You can pass any part of full test name (module::[all modules inside]::test_name) as argument to cargo test and it will run all matched tested

Ok, I don’t have time to work on vim-test anymore, but I’ll gladly merge pull requests.

I'm not experienced with VimL, myabe you can show some example in existing code that can help me?

I believe the mocha runner might provide a good template.
The build_position function is the one that builds command-line arguments based on whether the user executed :TestSuite, :TestFile, or :TestNearest command. https://github.com/janko/vim-test/blob/fc4f15e99e45fcb24ef9069a0726ceca5bd601ee/autoload/test/javascript/mocha.vim#L10-L23
Since Mocha doesn't support line numbers but supports regexes, the nearest test is determined by parsing the current buffer using regexes: https://github.com/janko/vim-test/blob/fc4f15e99e45fcb24ef9069a0726ceca5bd601ee/autoload/test/javascript.vim#L1-L4
The test#base#nearest_test function already exists for searching files, you just need to supply the regexes. Hopefully the documentation of that method will shed some more light on how it works: https://github.com/janko/vim-test/blob/fc4f15e99e45fcb24ef9069a0726ceca5bd601ee/autoload/test/base.vim#L50-L79

@sivakov512 let me know if you'd like a hand with this, I am happy to help


Attempting to drag in Safari and IE selects text on page

When I drag an item in Safari or IE 11, the text on other areas of the page that my mouse travels by gets selected. It's as if the browser doesn't know I'm dragging but thinks my mouse went down for the purpose of highlighting text on the page.
Great hoc! I definitely appreciate your work! :D

Firefox and IE both have the same problem of a drag causing selection.
The solution I found is just two steps:-

Define the following css  class :-

 .noselect {
 -webkit-touch-callout: none; /* iOS Safari */
   -webkit-user-select: none; /* Safari */
    -khtml-user-select: none; /* Konqueror HTML */
      -moz-user-select: none; /* Firefox */
       -ms-user-select: none; /* Internet Explorer/Edge */
           user-select: none; /* Non-prefixed version, currently
                                 supported by Chrome and Opera */
}

Apply the css class on your SortableItem component (div or li which you will drag) like so :-

const SortableItem = SortableElement(({value,SortableItemClassName}) =>

{value}

);

Check both the reproduced problem and its solution  by opening the sandbox in Firefox  :-
https://codesandbox.io/s/G6jPqD9oy
The source of solution is from Overflowstack

@wahabshah Unfortunately it doesn't work.
Here is my solution. Add the special sort start event handler to your sortable container:
const SortableList = SortableContainer(/* your container here */);

ReactDOM.render(
    React.createElement(SortableList, {
        items = [], // your list items
        onSortStart = (_, event) => event.preventDefault(), // it does the trick
        onSortEnd = () => {} // your sort end handler
    }),
    document.getElementById('app')
);

technically these aren't really solutions but more work-arounds.
I think the real problem is because the framework decides to copy the element to the bottom of the body and hides the original one instead of actually changing the element.

By the way this behavior is completely different on safari. (Just try to do a select all on safari).
Safari for some reason selects the background as well as the text this is why there is some weird behavior when using this in safari (even when you use user-select: none)

Almost two years passed, and the issue is still there.

I also have this problem. Would be nice with a proper fix for this.

Does the Console in the Developer Tools show a "Possible Unhandled Promise Rejection" error?
If yes, your trouble might be related to https://github.com/clauderic/react-sortable-hoc/issues/525, it was in our case.
We needed to polyfill Array.prototype.find() by using for example core-js or (in our case it's a create-react-app) react-app-polyfill.

If you want to use delay or distance, you could try something like this:
updateBeforeSortStart={() => {     function disableselect() {return false}     document.onselectstart = disableselect;     document.onmousedown = disableselect; }} onSortEnd={() => {     document.onselectstart = null;     document.onmousedown = null; }}

If you want to use pressDelay and distance and solution of @denis-lukin did not work for you. You can try something like this:
updateBeforeSortStart={() => {
    document.body.classList.add('not-selectable');
}}
onSortEnd={() => {
    document.body.classList.remove('not-selectable')
}}


Change HydroShare iRODS to do soft delete

In HydroShare code, change all occurances of iRODS iCommand "irm -rf" to "irm -r"; and "irm -f" to "irm"
Confirm this works first on usersdev for hydroshareuserdevZone on beta, then on hydroshareuserZone to implement in production.
This is only one interim step towards implementing a comprehensive consideration of how deleted resources in HydroShare are handled from the UI to django to iRODS.
This issue is related to: https://github.com/hydroshare/hydroshare/issues/2712

@rayi113 @aphelionz I can implement this pretty easily. However, I think this has to be accompanied with a periodic job to call irmtrash to purge files as needed. irmtrash has a parameter --age that seems to allow to specify age in minutes which I assume would only delete collection over the specified age in the user's trash can. Should we do this periodic trash purge as a Jenkins job or as a periodic celery task? What is the age we should use to purge trashed collections? A month? Looping in @phuongdm and @cbcunc as well in case we want to go with the Jenkins route for trash purge.

I propose setting the age at 2 months so we can manually visit any user deletion patterns on HydroShare dev calls by manually looking at the iRODS trash area, and also see if we can infer HydoShare user deletion patterns from Kibana.

@phuongdm I also thought about what you suggested here as an alternative, however, this will have implications on quota since setting isDeleted flag in Django db will not really delete the files in iRODS, which will not reduce user's quota as a result of resource deletion. Also, users could only delete a file without deleting the whole resource, which may require to add isDeleted and purgeData on ResourceFile field as well if we want to support restoring accidentally deleted files from HS UI. Unless we resolve these two implications, I don't think this alternative approach would be viable. Thanks for bringing up this alternative approach on the table, though.

@hyi,

About files restore, I think you have your solution with isDeleted on ResourceFile
About quota, the usage should be: the real usage (get from iRODS) - sum of size of files in ResourceFile which has isDeleted on

@phuongdm What you suggested involves making changes to Django DB models to add the needed fields to mark resources or resource files for deletion, which will involve code changes on most if not all resource or resource file related functions to exclude marked-for-deletion resources and files. We also need periodic job to purge deleted resources and files. So basically this approach involves making changes only on Django side without touching iRODS by marking resources and files for deletion without really deleting them. This does make deleted file restore easier since we just need to set isDeleted flag in Django db accordingly.


Broadcast command don't work with multiple words

Working a intended.  Put your entire sentence in quotes.  fr34ky, might recommend taking this out for the broadcast command only if possible.

Hmmm, ok.

Mhm, how should people change the color then?
Wouldnt /broadcast  [message] [more words] confuse them?

/broadcast [color] [messages...]

Fixed. Changing /broadcast to [color]


Add refresh tokens and use npm for passport-local-mongoose

I need to fix up some tests in the morning, but otherwise ready for review.


Cannot read property 'clearFocus' of null

Issue Id: 820d0beb-87a6-9998-b755-6c191539a1c3Versions - 1.9.1-  fcac9b686abe4292e69a774f61c8c4ce17768bf5-  58506618c7c4b5f220139081a7c132e5994a7dd4Stack TypeError: Cannot read property 'clearFocus' of null/vs/workbench/parts/preferences/browser/preferencesEditor.ts#L178:112 (clearFocus)/vs/base/common/callbackList.ts#L63:26 (apply)/vs/base/common/event.ts#L118:26 (call)/vs/workbench/parts/preferences/browser/preferencesEditor.ts#L1379:30 (fire)/vs/workbench/parts/preferences/browser/preferencesEditor.ts#L1208:26 (clear)/vs/workbench/parts/preferences/browser/preferencesEditor.ts#L1166:64 (onMouseMoved)/vs/base/common/event.ts#L217:12 (apply)/vs/base/common/eventEmitter.ts#L314:9 (func)/vs/base/common/eventEmitter.ts#L182:4 (safeInvoke1Arg)/vs/base/common/eventEmitter.ts#L201:8 (_emitToSpecificTypeListeners)

Fixed in insiders


GUI should not allow buckets >128 to be specified.

The GUI permits the user to specify any number of buckets, however a value >128 is already caught by the application and an exception thrown if passed as an argument.
When trying to specify buckets > 128 in the Windows GUI, the plot will fail to start with the following exception:
Caught plotting error: Maximum buckets is 128
[19136] Failed to execute script chia
Traceback (most recent call last):
File "chia\cmds\chia.py", line 80, in
File "chia\cmds\chia.py", line 76, in main
File "click\core.py", line 829, in call
File "click\core.py", line 782, in main
File "click\core.py", line 1259, in invoke
File "click\core.py", line 1259, in invoke
File "click\core.py", line 1066, in invoke
File "click\core.py", line 610, in invoke
File "click\decorators.py", line 21, in new_func
File "chia\cmds\plots.py", line 134, in create_cmd
File "chia\plotting\create_plots.py", line 176, in create_plots
RuntimeError: Unknown exception
The GUI should not enable the user to specify a value which is going to cause the plot to fail to start.

Thanks :) nice catch. I will add this limit

The maximum value will change in the short run. I will add this limit after this change


Vulkan: Normal map on MeshInstance2D doesn't work anymore

Godot version
v4.0.alpha d26442e70
System information
Win10, Vulkan API 1.2.189  GeForce GTX 1060
Issue description
The normal map for MeshInstance2D in Godot 4.0 doesn't work:

Displayed correctly in 3.3.2

mesh_instance_2d.cpp Line 35-43:
Is it not being used?

void MeshInstance2D::_notification(int p_what) {
switch (p_what) {
case NOTIFICATION_DRAW: {
if (mesh.is_valid()) {
draw_mesh(mesh, texture);
}
} break;
}
}

Steps to reproduce

Create a new Scene
Add a MeshInstance2D
Set the Mesh/Texture/Normalmap properties of MeshInstance2D
Add a PointLight2D to the Scene
Can't see any effects of the Normal Map

Minimal reproduction project
Test.zip

Should use a CanvasTexture?
https://github.com/godotengine/godot/commit/84d734da0e4dc4f0076c61a7178d8ad7b9f3b616

Refactored 2D shader and lighting system
-Removed normal/specular properties from nodes
-Create CanvasTexture, which can contain normal/specular channels
-Refactored, optimized and simplified 2D shaders
-Use atlas for light textures.
-Use a shadow atlas for shadow textures.
-Use both items aboves to make light rendering stateless (faster).
-Reorganized uniform sets for more efficiency.

Should I use a CanvasTexture?

Yes, but I don't know if MeshInstance3D properly supports them.

I can confirm I have the same problem with normal maps but with 2D Sprite

I can confirm I have the same problem with normal maps but with 2D Sprite

Which Godot version are you using? Can you upload a minimal reproduction project?


Temporarily run git describe on CI to debug #8043

bors r+
changelog skip

Run git describe --tags
fatal: No names found, cannot describe anything.


Could not load file or assembly 'stdole' or one of its dependencies

My Bot Not Working Because of this error after publish on my domain Could not load file or assembly 'stdole' or one of its dependencies. Strong name signature could not be verified.  The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)
Please help

I don't believe the Bot Framework has a "stdole.dll" file, but if you want to prevent ASP.NET from opening the file while compiling the contents of the bin directory, you can use a solution like this (different cause, possibly the same solution):
http://blog.willportnoy.com/2011/07/badimageformatexception-with-aspnet-and.html

You can also use the Fusion log to get more detail on assembly load errors. https://msdn.microsoft.com/en-us/library/e74a18c4(v=vs.110).aspx

Closing this as it's not really related to the Bot Framework. There are some suggestions above but since it's not our area of expertise, I don't think we'll be able to help much past that. Please open a new issue if you find there is something specific to Bot Framework we need to address. Thanks


"Plevna" is listed in the drop-down menu

Description:
"Plevna" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Plevna" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Plevna, CĂLĂRAȘI (Lupșanu)".


**/*.jsx is matching test.js

Doing a pattern match for /**/*.jsx and change events are firing for *.js on windows
Where exactly is the pattern match validating the file?

To say in a different way.
filename.js matches for pattern filename.jsx So the change event is actually on filename.jsx

More information. I was able to track this bug down into libuv of node.
See: https://github.com/nodejs/node/issues/4351 and pull request https://github.com/nodejs/node/pull/4429
In order to complete this fix in chokidar we would need to filter the file names coming out of the fs.watch as they will not exactly match the pattern.
At this point if you are watching fs.watch('**/*.jsx') a change event for filename.js may come through but unlike before the pull-request at least it will accurately say filename.js instead of mistakenly saying filename.jsx even though that wasn't the file you changed.

Interesting.
Would you be able to send us a PR that would fix this behavior (w tests)?

I will try to send a PR with fix of this bug. At first I will try to repeat bug on my machine, and then fix. I will be back in one or two days with the results)

Some additional resources on the actual fix inside of libuv https://github.com/libuv/libuv/pull/682
This is mainly an issue with libuv on windows but still may need some defensive code added to chokidar to ensure compatibility.

I am successfully reproduce the error. Now i am trying to found where we get the files that fit the pattern, then i think about adding additional check for fitting the pattern and test for it. What do you think @jsheely ,@paulmillr ,any advices, opinions?

@sashashakun Last I looked into this the issue is that chokidar assumes if a watch event is fired it must be on the right file and does not check what file is being reported as changed. (Since if libuv was working correctly it would have to be the correct file).
I believe the issue starts to cascade from here. https://github.com/paulmillr/chokidar/blob/master/lib/nodefs-handler.js#L37
My patch to libuv will output what file was changed which will not match what is being watched by chokidar but an event will still come through all the same.
I haven't gotten any activity on my pull-request yet, which is just a band-aide to the problem. In an ideal world libuv would never output an event if it doesn't match the wildcard file name.
But if my band-aide is the only viable option then post processing the file being reported will be needed.

@sashashakun my advice is to try something like
if (process.platform === 'win32' && this._isIgnored(path)) return;

at the top of FSWatcher.prototype._emit

Thank everyone for advices, will try this things

Ok, I have some results. At first look, I am agree with @jsheely ,bug in libuv itself, I mean that native node API that used in nodefs-handler#L37:
fs.watch(path, options, handleEvent);
return information that .jsx file was changed, but in fact .js was. So may be we can wait for fix in libuv for this, and add some additional checking after that?
@es128 I made that you said, but it didnt help(

Yeah if both files are within the watch paths and the event is being misreported from a lower level then my suggestion would be ineffective (and there likely isn't anything we can do here).
In the original issue report it was suggested that paths are being filtered with a glob pattern like *.jsx, and events were coming out for paths that shouldn't have even been watched. In this case, an approach like I suggested might be effective for suppressing those events, but the side effect would be completely missed events.
So waiting for a fix at libuv is probably the only thing we can do.

@sashashakun yep, libuv folks should review the code and merge the PR. Other fixes are ineffective.
https://github.com/libuv/libuv/pull/682

Hi all again, checked out conversation here https://github.com/libuv/libuv/pull/682 and also saw this PR https://github.com/libuv/libuv/pull/858
Am I right that it will solve this issue or we need two add some internal checking in chokidar?
(sorry, my C knowledge is very poor)

Based on the considered changes to https://github.com/libuv/libuv/pull/682 chokidar will have to post process the event to ensure which file was matched meets the fuzzy wild card search.
As it stands right now chokidar assumes that if an event comes out fs.watch then it must have been for one of the files that it setup a watch for.

@jsheely as I described before, following through on your suggestion won't really fix the problem. Either the incorrect event will be filtered out instead of being misreported, so the true event will still be missed, or if both file paths are being watched there will be no change in behavior. There does not appear to be a possible workaround that can be added to chokidar to fix for the libuv bug.

@es128 Agreed. We have to wait for the libuv bug to be fixed.
For anyone monitoring this issue. The real fix is to just try and not put your jsx and js files in the same folder. If you follow the standard: ./src and ./build folder structure this won't be a problem on windows.

This may be fixed in Node v7.1.0 as it uses libuv 1.10.0 which includes a fix for this issue. Can someone test on a Windows machine to confirm?

I've tested on a Windows machine now, with Node 6.9.1 (reproduces the issue) and Node 7.1.0 (works as expected).
The bug was in libuv, part of the Node.js core. It is fixed as of libuv 1.10.0, which ships with Node 7.1.0.

Thanks @UltCombo!


Cannot get matrix view to open

I tried opening the matrix view but nothing happens. From the demo in the README, it seems like I should just left-click the np array data in the "content" column. If I do that, nothing happens. I tried this for both python2 and python3 kernels, using this simple cell of code:
import numpy as np
matrix = np.random.randn(10,10)

I don't see any errors in the terminal in which I started jupyter lab.
Screenshot:

Using Ubuntu 16.04, Firefox 62, jupyter lab 0.35.0, and latest master from this repo build with nodejs 10.12. Also tried with Chrome 69.
By the way: great work on this plugin! I really believe it adds great value to Jupyter! Hopefully it will evolve into a rich variable inspector like we know from Matlab :)

Hi, after installing everything it displays column headers in blank matrix although values were assigned to variables. regards thanks in advance

It's working! only required to do was refresh by right clicking in Variable Inspector window and reload contents accordingly. Cheers!

Works! It turned that you need to install both pandas and numpy to get it to work. I thought installing numpy (without pandas) would be enough for showing matrix view for numpy, but it itsn't. It will only work if both are installed. Also, for python2 kernel you'll need pandas/numpy for python2, and for python3 you need them for python3. E.g. install like this:
sudo -H python2 -m pip install numpy pandas
sudo -H python3 -m pip install numpy pandas

this still feels like buggy behaviour. seems like a big ask to require pandas in a situation like this. is there something about the implementation that requires pandas as a dependency for even non-df objects...?

I am having issues with this. I click in the contents field of the dataframe I want to inspect, and nothing happens.
I tried the above suggestion of right clicking and re-loading and nothing happened, either.
Any suggestions?
MacOS 10.12.6
Python 3.6
JupyterLab 0.35.0
Pandas 0.23.0
NumPy 1.14.3

I am having issues with this. I click in the contents field of the dataframe I want to inspect, and nothing happens.
I tried the above suggestion of right clicking and re-loading and nothing happened, either.
Any suggestions?
MacOS 10.12.6
Python 3.6
JupyterLab 0.35.0
Pandas 0.23.0
NumPy 1.14.3

you should write 'import pandas as pd' literally in code!
I had the same problem with you but soon after i import pandas and click 'view contents' it worked just fine.
hope it helps


.env files, OPcache and restarting FrankenPHP

Hi
I updated my api-platform project from v3.1.14 to v3.2.10 with the new FrankenPHP instead of Caddy and I'm experiencing some stability problems after deploying it in production.
I'm not sure 100% that it's all frankenphp related as it's also a new PHP and Symfony version but I suspect it is, maybe caching OPcache related?
My main problem is that I use symfony/ldap to authenticate. It works ok but so far ~every 1 to 2 days it will lock up and throw:
"message": "Uncaught PHP Exception Symfony\\Component\\Ldap\\Exception\\ConnectionException: \"Can't contact LDAP server\" at Connection.php line 86",
on every request until I recreate the PHP container.
I know it's not the ldap server as it worked before, the port is accessible from inside the container and it goes back to working once I recreate the container.
I would appreciate it if you could point me in some direction on how to troubleshoot this more since I wasn't able to reproduce the problem in my test environment.
While trying to investigate I encounter 2 other things regarding OPcache and FrankenPHP.
First, looking online on how to clear the OPcache in a container the only thing I found that worked (without recreating the container) was running kill -USR2 1. On the old Caddy container it worked nicely. The edits in the php files were loaded and the container stayed up.
The Caddy service for example:
/srv # ps aux -o user,group,comm,pid,ppid,pgid,etime,nice,rgroup,ruser,time,tty,vsz,sid,stat,rss,args
USER     GROUP    COMMAND          PID   PPID  PGID  ELAPSED NI    RGROUP   RUSER    TIME  TT     VSZ  SID   STAT RSS  COMMAND
root     root     caddy                1     0     1 24:43       0 root     root      0:05 ?      1.2g     1 S     56m caddy run --config /etc/caddy/Caddyfile --watch

Doing the same in the new PHP container, the frankenphp service doesn't reload the cache ignoring the signal, if I try a more aggressive kill 1 the container fails and recreated (as expected).
The FrankenPHP service for example:
/srv # ps aux -o user,group,comm,pid,ppid,pgid,etime,nice,rgroup,ruser,time,tty,vsz,sid,stat,rss,args
USER     GROUP    COMMAND          PID   PPID  PGID  ELAPSED NI    RGROUP   RUSER    TIME  TT     VSZ  SID   STAT RSS  COMMAND
root     root     frankenphp           1     0     1  4:40       0 root     root      0:03 136,0  1.7g     1 S    285m frankenphp run --config /etc/caddy/Caddyfile

Can I clear the OPcache in FrankenPHP like in Caddy?
Second, in the old version, modifying the ".env" or ".env.local.php" the changes are immediately picked up (I assume there is somewhere an exception for the env files for the caching?), but in the new version, the changes are not reflected.
The more bizarre part is that if I send some requests (like holding F5 for 2 seconds) the changes to the env files are partially loaded. like the system now has something like multiple versions cached so if you refresh it will loop on some pattern like updated, updated, updated, old config, old config. It loops like that on every request until recreating the container (or probably restarting FrankenPHP/OPcache but I don't know how to test it).
Help will be appreciated as I hope to avoid migrating everything back to the old version.
Thank you.

I noticed a few points in your issue that I'd like to address individually to provide clearer assistance.
LDAP
Your query about connecting to LDAP is important, and several methods exist. It would be helpful to know which method you're using. Are you utilizing an extension, and if so, is it a custom one or the built-in PHP one, or the one that comes with FrankenPHP? It's worth noting that the built-in PHP LDAP extension isn't compatible with ZTS and is reportedly being phased out from PHP. Alternatively, if you're using the LDAP extension built into FrankenPHP, it's designed to be thread-safe, as far as I know. (I don't use it but there was #203)
Let's focus on potential solutions assuming you're using the latter and operating in worker mode. One aspect to consider is whether the LDAP library you're using automatically attempts to reconnect after losing a connection. It's possible that you might need to implement additional code to handle reconnections, or this could be an oversight in the library that needs addressing.
Opcache
Regarding your question on Opcache in worker mode: indeed, in this mode, the code is loaded once and stays in memory. PHP, to my knowledge, doesn't support hot-reloading of scripts in memory. This means that to reflect any changes in your code, you would need to restart the server process when running in worker mode.
Strange Behavior
You're correct in noting that each worker operates with its own memory/environment. This isolation can lead to situations where, if files or the environment are changed before a worker's initial startup, different workers may perceive different 'versions' of the application. It's a critical point to consider when managing workers and deploying changes.

Thank you, so what I did is basically take the api-platform template.
To Dockerfile added ldap:
RUN set -eux; \
    install-php-extensions \
		ldap \

to security.yaml added Symfony LDAP Provider and Http Basic.
For authorization, I limited the access to authenticated users (the access to the "/docs"):
    access_control:
        - { path: ^/, roles: ROLE_USER }

and put roles in the entities like shown in https://api-platform.com/docs/core/security/
The only custom thing I made is this code that gets the roles but I don't see how would it corrupt the connection https://github.com/symfony/symfony/issues/51225#issuecomment-1715703896
If I understand the PR you linked we should remove all the dependency installation in https://github.com/api-platform/api-platform/blob/main/api/Dockerfile and use this "static-builder" to install them in a different way?

In worker mode, it is nearly 100% certain that, at some point, whatever external resource you connect to will eventually disconnect. Thus, you will need to be able to handle that error and reconnect before continuing.

If I understand the PR you linked we should remove all the dependency installation in https://github.com/api-platform/api-platform/blob/main/api/Dockerfile and use this "static-builder" to install them in a different way?

I think I misread the original issue, and the LDAP extension is thread-safe, so it should be fine.

I added some file_put_contents to https://github.com/symfony/ldap/blob/6.4/Adapter/ExtLdap/Connection.php on bind() and __destruct() to log what happens.
In old dev, old prod and new dev images I see on every request:

Making a new connection.
Using existing connection.
Using existing connection.
Dispose.

Only on the new prod image, I see on every request:

Making a new connection.
Using existing connection.
Using existing connection.

Dose __destruct() not supposed to run in this new worker mode or is something going wrong somewhere?

In worker mode (which you can disable, btw, and use regular ole' cgi-mode) an object exists beyond a single request. Every request shares bootstrapped resources so that, for example, your LDAP library only has to connect once per worker, instead of once per request. This has some pretty significant performance impacts, however, if your libraries aren't designed to be running on workers and are expecting to only exist for a single request ... they'll probably break (which is what I suspect is happening here).


Update dependencies

Short description

It seems we have the weird CircleCI errors again - probably the pip cache is somehow broken again.
To refresh the cache, we could update all dependencies (this is probably a good idea anyway).

Thanks, I tested it and there seems no issues. However, I got some deprecation warnings afterwards. See

Thanks for the hint, I'm not sure whether the warnings are a problem, but just to be sure I downgraded autoprefixer to version 10.4.5.


Log deserialized ENR for boot nodes

In #387 I removed a log that contained the boot node IP address and mistakenly thought that info was covered by other logs. We should add this log back, and preferably in a nicely formatted way.

Maybe the preferred solution here is to log both the encoded ENR and the IP/port in the log that starts like "About to spawn History Network with boot nodes" (currently in trin-history/src/lib.rs). Currently it's just showing the encoded version.


Different forwarder based on source IP address that makes DNS query

Hi all.
It will be nice if in unbound is possible to specify different forwarder (forward-addr) based on the source IP that makes the query.
For example:
Leave <IP_ADDRESS> and <IP_ADDRESS> as default forward-addr
Specify as forward-addr <IP_ADDRESS> if the source IP are <IP_ADDRESS> and <IP_ADDRESS>
Specify as forward-addr <IP_ADDRESS> if the source IP are <IP_ADDRESS> and <IP_ADDRESS>
Specify as forward-addr <IP_ADDRESS> if the source Network IP is <IP_ADDRESS>/24
Is it already possible to do that?
Thank you!

Is it already possible to do that?

The selection of the forward address to use based on the client source address is currently not supported in Unbound.
We, for some time already, have the idea to extend the current view support with stub- and forward-zones to make this possible. This is, however, quite a big feature to implement, as this requires to have a cache per view. Implementing this is not something we have currently scheduled for the near future.

The feature is cool, Hope it can be used in the near future.

@ralphdolmans @wcawijngaards
guys any news about that?
Many thanks for you work!!

Hello, any news about this feature ?

I also would like this feature to be implemented. Unbound is the DNS resolver used in pfSense, and using this feature would make safe family filtering much easier to setup.

:+1:

This feature would help me to implement Unbound as the backbone DNS in our company.
For example: Unbound would forward queries send by remote clients, to the VPN DNS server and If queries come from within the local LAN, it would forward the queries to the other DNS server, returning non VPN IP-Addresses.

3 years have passed, are there already plans?

Vague future plans for improvement in allowing more configuration options exist. This can be found on plans into the further future developments.


Major changes

[x] Remove get_item and set_item, instead do it like scala where arr(n) gets the nth element. This means adding an update function.
[ ] Allow juxtaposition of function arguments as top level expression: print "some string". This is related to the first point because it sidesteps an ambiguity with array indexing and literals.
[ ] #36
[ ] Add blocks (potentially evaluating to the last element)
[ ] Add lambdas
[x] Remove the trailing colon in switch/case
[x] Add tuples

a language designed to be predictable, behave in sane ways, not allow coding practices that lead to undefined or poorly legible behavior, within a small talk-python-lua-vbscript-c conceptual space?
absolutely radical and based, every bit of unconscious grey matter i have to commit to learning arcana is brainpower i probably can’t commit to building systems consciously, although i doubt programmers would understand this cognitive workload paradigm


https://falco.org/docs/grpc/#certificates is supposed to tell how to generate certs but its not showing

https://falco.org/docs/grpc/#certificates is supposed to tell how to generate certs but its not showing

There is not a label identifying the kind of this issue.
Please specify it either using /kind <group> or manually from the side menu.

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

Hey @jitendrazkumar, that snippet of documentation was moved to another page in December 2022. The content is now a link deeper: https://falco.org/docs/grpc/grpc-config/#certificates.
Could you share where you have found the link to correct it?

I identified the blog post had the incorrect link. If there isn't any other page with the same issue, the PR #941 should fix this issue.


Implement infinity/NaN maths operators

Implement the literals "TOKEN_INFINITY" and "TOKEN_NAN", and add its conversion in asString() and error in asBool()

In REPL:
1 / 0 = inf
-1 / 0 or -(1 / 0) = -inf
0 / 0 = nan


Deprecate public methods and variables that contain 'master' terminology in 'test/framework' directory

Description
To support inclusive language, the master terminology is going to be replaced by cluster manager in the code base.
This PR deprecate public and protected methods/variable that contains master terminology in the name in test/framework directory, and create alternatives.
List of public methods in test/framework directory that renamed in this PR:
public static String blockMasterFromFinalizingSnapshotOnIndexFile(final String repositoryName) {
public static String blockMasterOnWriteIndexFile(final String repositoryName) {
public static void blockMasterFromDeletingIndexNFile(String repositoryName) {
public static String blockMasterFromFinalizingSnapshotOnSnapFile(final String repositoryName) {
public Client masterClient() {
public Client nonMasterClient() {
public boolean isMasterEligible() {
public synchronized <T> T getCurrentMasterNodeInstance(Class<T> clazz) {
public <T> Iterable<T> getDataOrMasterNodeInstances(Class<T> clazz) {
public <T> T getMasterNodeInstance(Class<T> clazz) {
public synchronized void stopCurrentMasterNode() throws IOException {
public synchronized void stopRandomNonMasterNode() throws IOException {
public String getMasterName() {
public String getMasterName(@Nullable String viaNode) {
public List<String> startMasterOnlyNodes(int numNodes) {
public List<String> startMasterOnlyNodes(int numNodes, Settings settings) {
public int numMasterNodes() {
public static Settings masterNode()
public static Settings masterNode(final Settings settings)
public static Settings masterOnlyNode()
public static Settings masterOnlyNode(final Settings settings)
public static Settings nonMasterNode()
public static Settings nonMasterNode(final Settings settings)
public abstract int numDataAndMasterNodes();
public Version masterVersion()

List of public variables in test/framework directory that renamed in this PR:
(all in org.opensearch.test.InternalTestCluster)
public static final int DEFAULT_LOW_NUM_MASTER_NODES
public static final int DEFAULT_HIGH_NUM_MASTER_NODES
public static final int REMOVED_MINIMUM_MASTER_NODES

public that not renamed in this PR:
public static MasterService createMasterService(ThreadPool threadPool, ClusterState initialClusterState)
public static MasterService createMasterService(ThreadPool threadPool, DiscoveryNode localNode)
public abstract int numDataAndMasterNodes();

Reason for the above are not deprecated and renamed:

The class MasterService is not deprecated, and needs to find a solution to deal with deprecating this class in the return value.
abstract methods will be deprecated in a separate PR.

Issues Resolved
A part of issue https://github.com/opensearch-project/OpenSearch/issues/3544
Check List

[ ] New functionality includes testing.

[x] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

In build 901:

REPRODUCE WITH: ./gradlew ':server:test' --tests "org.opensearch.indices.replication.SegmentReplicationTargetServiceTests.testReplicationOnDone" -Dtests.seed=4F4E8AB47EE2BD5 -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=sr -Dtests.timezone=Cuba -Druntime.java=17

org.opensearch.indices.replication.SegmentReplicationTargetServiceTests > testReplicationOnDone FAILED
    org.mockito.exceptions.verification.TooFewActualInvocations:
    segmentReplicationTargetService.onNewCheckpoint(
        ReplicationCheckpoint{shardId=[index][0], primaryTerm=54, segmentsGen=3, seqNo=-1, version=9},
        <any>
    );
    Wanted 2 times:
    -> at org.opensearch.indices.replication.SegmentReplicationTargetServiceTests.testReplicationOnDone(SegmentReplicationTargetServiceTests.java:236)
    But was 1 time:
    -> at org.opensearch.indices.replication.SegmentReplicationTargetServiceTests.testReplicationOnDone(SegmentReplicationTargetServiceTests.java:230)
        at __randomizedtesting.SeedInfo.seed([4F4E8AB47EE2BD5:1E3A38668D12C477]:0)
        at app//org.opensearch.indices.replication.SegmentReplicationTargetServiceTests.testReplicationOnDone(SegmentReplicationTargetServiceTests.java:236)

Codecov Report

Merging #3978 (b00b5d0) into main (b08a2b8) will increase coverage by 0.02%.
The diff coverage is 29.76%.

@@             Coverage Diff              @@
##               main    #3978      +/-   ##
============================================
+ Coverage     70.56%   70.58%   +0.02%
+ Complexity    56780    56774       -6
============================================
  Files          4573     4573
  Lines        273323   273360      +37
  Branches      40086    40086
============================================
+ Hits         192859   192962     +103
+ Misses        64239    64150      -89
- Partials      16225    16248      +23

Impacted Files
Coverage Δ

...arch/repositories/blobstore/BlobStoreTestUtil.java
76.21% <0.00%> (ø)

...earch/snapshots/AbstractSnapshotIntegTestCase.java
0.00% <0.00%> (ø)

...a/org/opensearch/test/OpenSearchIntegTestCase.java
58.22% <0.00%> (+1.22%)
:arrow_up:

...ch/test/disruption/BlockMasterServiceOnMaster.java
0.00% <0.00%> (ø)

...h/test/disruption/BusyMasterServiceDisruption.java
0.00% <0.00%> (ø)

...pensearch/test/rest/yaml/ClientYamlTestClient.java
0.00% <0.00%> (ø)

...test/rest/yaml/ClientYamlTestExecutionContext.java
30.55% <0.00%> (-0.44%)
:arrow_down:

...k/src/main/java/org/opensearch/test/NodeRoles.java
75.38% <33.33%> (-7.67%)
:arrow_down:

.../java/org/opensearch/test/InternalTestCluster.java
60.89% <36.36%> (-1.59%)
:arrow_down:

...re/OpenSearchBlobStoreRepositoryIntegTestCase.java
91.36% <100.00%> (+2.69%)
:arrow_up:

... and 506 more

Help us with your feedback. Take ten seconds to tell us how you rate us.

@kotwanikunal Thank you so much for reviewing this large PR! 👍👍


Link tickets in Palantir Changelog

So things like HDFS-9276 are easily clickable
https://github.com/palantir/hadoop/blob/branch-2.8.0/PALANTIR-CHANGELOG.md

Fixed


request:  Add documentation how to use FlutterFire packages the old way without this tool

Is there an existing feature request for this?

[X] I have searched the existing issues.

Command
No response
Description
Please add documentation how to continue using FlutterFire without this tool i.e. the old way. There are several unclear items like do I need to put something to .gradle files in this case.
Reasoning
I don't want to use this tool in my project. There were not any issues in the old way of downloading manually the required config files from Firebase and updating the files when needed (which is very rarely actually). This tool only adds complexity to my project and I will consider it also as a security risk.
Detected problems:

The new generated files firebase_options.dart and firebase_app_id_file.json are not useful at least in Android / iOS projects. The same information is already available in the files google-services.json (Android) and GoogleService-Info.plist (iOS) which you cannot remove anyway, because at least Crashlytics and the plugin google_sign_in require them. I would bet at least 95% of the Flutter/Firebase apps use both Crashlytics and the plugin google_sign_in.

Flavors are not supported and maintaining existing flavor implementation gets even more complex (due to the new required file firebase_app_id_file.json in the fixed location).

It is much more clear and easier to maintain the project if the required information is in one place / platfrom i.e. google-services.json (Android) and GoogleService-Info.plist (iOS) and the application is initialized with await Firebase.initializeApp() without any parameters.

The tool seems to create applications to Firebase without even confirming it from the user. This already happened to me when I tried the tool for the first time (the tool did not recognize the correct package id / bundle id from my project so it decided to add new applications to Firebase without any questions). Luckily it was only my Development project in Firebase. I don't want this kind of tool connecting to my production project in Firebase, not even with read access. That's why I say this tool is currently a security risk as the tool can even modify my Firebase projects. It is also unclear what it exactly does and when, and all this can be changed at any time when you update the tool.

Additional context and comments
Maybe the tool is useful for new developers trying Flutter/Firebase and to get started quickly, but for real-world production apps the tool it is currently only a new problem and a security risk.
I could consider using this tool again if you:

Totally remove need for  google-services.json and GoogleService-Info.plist, but I am not sure if it is technically possible.
Allow using the tool in read-only mode (quaranteed that it does not modify any Firebase projects), or even offline.

Just sharing our experience.

Totally remove need for google-services.json and GoogleService-Info.plist, but I am not sure if it is technically possible.

In our case, Android build failed to run without google-services.json. The app saw a fatal error at onResume() handler, where I suppose some Analytics data collection mechanics is present, by saying (native) Firebase SDK has not been initialized. Usually such initialization is automatically performed in FirebaseInitProvider using the default parameter values derived from google-services.json (in fact, Firebase Gradle plug-in converts it into a bundle of string resources and embed it into the app.)
To avoid such error without the presence of google-services.json, we need to explicitly initialize native Firebase SDK using parameter values defined in firebase_options.dart at an earlier stage of the execution of the app, way before Dart main() is executed. Although I have not tried it by myself, it would be theoretically possible by implementing onCreate() handler in MainActivity to initiate such explicit initialization. It involves execution of Dart code from inside the native part of the app, though.
In my opinion,  generating firebase_options.dart was a failed experiment and shall be obsoleted because:

The native Firebase SDKs for both iOS / Android suggest the automatic initialization based on  google-services.json and GoogleService-Info.plist is the primary way to go.

https://firebase.google.com/docs/android/setup
https://firebase.google.com/docs/ios/setup

Each set of these initialization parameters is inherently platform-dependent, there would be little reasoning on keeping it in platform-independent Dart code.

In my opinion, generating firebase_options.dart was a failed experiment and shall be obsoleted because:

Exactly. Failed experiment and pretty much waste of time. I am 99% sure Crashlytics (same for Analytics?) must be initialized much earlier before any Dart code is executed and this alone is a showstopper issue for even considering to implement this kind of tool. Using google-services.json and GoogleService-Info.plist works great and what's most important allows keeping important things under the developer's control without all the risks this tool is causing to your Firebase project.

Activate the latest FF CLI using dart pub global activate flutterfire_cli . The service files are now written for android & iOS. We're thinking of removing the Dart init code for android and iOS to clear up the confusion. If you want docs for manual steps, they're archived here


arch/risc-v/espressif: Add full GPIO support

Summary
Add full GPIO and Buttons support for ESP32-C3/C6/H2 using the Espressif HAL.
Impact
None on existing code. Support for new peripherals when using the Espressif HAL.
Testing
Tested on ESP32-C3-DevKitC.

GPIO interrupts used to be enabled by a specific Kconfig option, disabled by default:
https://github.com/apache/nuttx/blob/5e7ce13b3e8365de4475226ebcbdd5043982d5a8/arch/xtensa/src/esp32/Kconfig#L811-L815
This PR seems to change this behavior. Please confirm whether this is indeed an intended move.

GPIO interrupts used to be enabled by a specific Kconfig option, disabled by default:
https://github.com/apache/nuttx/blob/5e7ce13b3e8365de4475226ebcbdd5043982d5a8/arch/xtensa/src/esp32/Kconfig#L811-L815
This PR seems to change this behavior. Please confirm whether this is indeed an intended move.

Yes, it is. From now on we will follow the same approach as the other chips/boards.

GPIO interrupts used to be enabled by a specific Kconfig option, disabled by default:
https://github.com/apache/nuttx/blob/5e7ce13b3e8365de4475226ebcbdd5043982d5a8/arch/xtensa/src/esp32/Kconfig#L811-L815
This PR seems to change this behavior. Please confirm whether this is indeed an intended move.

Yes, it is. From now on we will follow the same approach as the other chips/boards.

Ok, but besides that is there any stronger reason for doing so?
I believe the initial motivation for having it disabled by default is to avoid the unnecessary memory overhead if GPIO interrupts are not required.
Enabling GPIO interrupts directly affects NR_IRQS, which is used as the size of the NuttX interrupt vector table:
https://github.com/apache/nuttx/blob/5e7ce13b3e8365de4475226ebcbdd5043982d5a8/sched/irq/irq_initialize.c#L52
https://github.com/apache/nuttx/blob/5e7ce13b3e8365de4475226ebcbdd5043982d5a8/sched/irq/irq.h#L57-L71
So, considering that ESP32-C3 contains 22 IRQ-capable pins, this move may increase RAM usage by at least 176 bytes.

besides the RAM overhead (2023).
// that's true overhead for nothing ->  (should be chased everywhere)
- gpioinfo("Attach %p\n", irqhandler);
- gpioinfo("Enabling the interrupt\n");

+ gpioinfo(
+     "Attach %p\n"
+     "Enabling the interrupt\n"
+   , irqhandler
+ );

@gustavonihei Me, @tmedicci and @acassis debated about this and decided that there weren't many applications where disabling the GPIO IRQs would be beneficial. So, for the sake of simplicity and consistency, we decided to remove it.

Is there any application on NuttX that use GPIO by polling? Particularly, I don't see any benefits of keeping GPIO support without IRQs.

@gustavonihei I think the "overhead" is too small and normally people will need to use GPIO with interrupt. Another alternative could be to keep the Kconfig entry but enable it by default because normally it will be needed 99% of the time when people are using GPIO.

there weren't many applications where disabling the GPIO IRQs would be beneficial

Is there any application on NuttX that use GPIO by polling? Particularly, I don't see any benefits of keeping GPIO support without IRQs.

normally people will need to use GPIO with interrupt

There is one trivial scenario that you (@tmedicci @lucasssvaz @acassis) seem to ignore is that there are many applications that don't work with the processor pins in general-purpose function at all. Take a look at how many defconfigs define CONFIG_ESP32_GPIO_IRQ=y, just a fraction. A practical example is a gateway device, like the newly release Espressif Thread Border Router board, which most probably won't need any externally generated GPIO interrupts at the simplest form.

I think the "overhead" is too small

At the driver level any overhead should be minimized. It is up to the application developer to quantify the size of the overhead and decide whether the price is worth paying.

there weren't many applications where disabling the GPIO IRQs would be beneficial

Is there any application on NuttX that use GPIO by polling? Particularly, I don't see any benefits of keeping GPIO support without IRQs.

normally people will need to use GPIO with interrupt

There is one trivial scenario that you (@tmedicci @lucasssvaz @acassis) seem to ignore is that there are many applications that don't work with the processor pins in general-purpose function at all. Take a look at how many defconfigs define CONFIG_ESP32_GPIO_IRQ=y, just a fraction. A practical example is a gateway device, like the newly release Espressif Thread Border Router board, which most probably won't need any externally generated GPIO interrupts at the simplest form.

I think the "overhead" is too small

At the driver level any overhead should be minimized. It is up to the application developer to quantify the size of the overhead and decide whether the price is worth paying.

You're right about the applications that don't use GPIOs at all... So, let's re-think the problem: considering GPIO is being used, should we provide an option to not use the GPIO with IRQs just for the sake of saving a couple of bytes? Are there any practical applications that could be built relying on that?
I agree that this PR doesn't consider this and should be fixed.

I' enjoy to be ignored when I infused debate.
1- the overhead is not argument ; when you are ready to abuse console messaging... what else
2- the vast majority is not argument
why because it will be different in few months, next year from now, it is moving fast, people should keep going, especially for less than 1k in 2023, get real. I like arguments till it acknowledges reality. (To know I was used to work on 8-bit mu, I have never been an ayatollah of bytes Q.E.D)

I've added the toggle back but kept it enabled as the default. If needed the GPIO IRQs can be disabled.
Now everyone can be happy.


Print instructions on how to access ArgoCD UI

We can improve user experience of using ArgoCD by making it easier for users to get the default admin credentials.
We can either printing the ArgoCD admin password to stdout or print the instructions on how to get the password e.g. kubectl -n argocd get secret argocd-initial-admin-secret -o jsonpath="{.data.password}" | base64 -d
Whenever I spin up a new cluster, I have to search the command history to get the password and it gets a bit too annoying for me.

good idea!

Ideally we should get such information using the idp client and new commands:
./idpbuilder package list
./idpbuilder package show argocd
url: https://argocd.<IP_ADDRESS>.nip.io
user: admin
pwd: <password>
etc
./idpbuilder package show gitea
url: https://gitea.<IP_ADDRESS>.nip.io
user: admin
pwd: <password>
etc


changing the mailing provider.

I have been trying to find out how to change the mail provider from Sendgrid to  something we are using internally. I'm not a Terraform guy but can't really find out how they plug into each other.

Hey @kelcheone, as you're using an internal mail provider you would probably have to create your own terraform module (which if you're not confident/familiar with I wouldn't suggest you do).
But if you've already got the mail server up and running, with the email sender created and verified, I'd suggest removing the SendGrid module and sendgrid variables (lines 72-85 and lines 195-211) as well as modify the remaining smtp variables (host/port/password/etc) accordingly to your internal server.
Once you've done that you should be all good to go (assuming I haven't forgotten something).


NaN for Temperature, Humidity and Battery Level from MS100EU

Hello and happy new year.
I get a lot of "NaN" Errors from my Temperature and Humidity Sensors that are working over the MSH300 hub (Firmware 4.1.35 and hardware 4.0.0)
Sometimes I get less and sometimes a lot more of them, is there any reason for those Errors? In the Meross App itself everything looks normal.
Here are some Logs:
[02/01/2023, 16:12:53] [homebridge-meross] This plugin generated a warning from the characteristic 'Battery Level': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[02/01/2023, 16:22:52] [homebridge-meross] This plugin generated a warning from the characteristic 'Current Temperature': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[02/01/2023, 16:22:52] [Meross] [Kellersensor] current temperature [NaN°C].
[02/01/2023, 16:22:52] [homebridge-meross] This plugin generated a warning from the characteristic 'Current Relative Humidity': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[02/01/2023, 16:22:52] [Meross] [Kellersensor] current humidity [NaN%].
[02/01/2023, 16:22:52] [homebridge-meross] This plugin generated a warning from the characteristic 'Battery Level': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[02/01/2023, 16:27:52] [homebridge-meross] This plugin generated a warning from the characteristic 'Current Temperature': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.

Hi @Tongo91
Can you update to the beta version of the plugin and show me this logging again? you should see more red entries this time (they are not actually errors).
I need to be able to see these red entries.
Thanks!

Hi, thanks for the fast reply, I did the update now and waiting for the NaN Error.
Currently everything is reporting normal since a few hours, as I said above sometimes it works and then I get those errors over a few hours.
I will update as soon as I see the NaN Logs again including the red entries then :)

[04/01/2023, 07:04:11] [Meross] {"id":"120027D2980F","status":1,"onoff":0,"lastActiveTime":1672812104,"ms100":{"latestTime":1672812104,"latestTemperature":139,"latestHumidity":810,"voltage":2862}}
[04/01/2023, 07:04:11] [Meross] {"id":"120027D23B71","status":1,"onoff":0,"lastActiveTime":1672812196,"ms100":{"latestTime":1672812196,"latestTemperature":102,"latestHumidity":670,"voltage":2716}}
[04/01/2023, 07:04:11] [Meross] {"id":"120027D22FF1","status":2}
[04/01/2023, 07:09:11] [Meross] {"id":"120027D2980F","status":1,"onoff":0,"lastActiveTime":1672812413,"ms100":{"latestTime":1672812413,"latestTemperature":139,"latestHumidity":810,"voltage":2862}}
[04/01/2023, 07:09:11] [Meross] {"id":"120027D23B71","status":1,"onoff":0,"lastActiveTime":1672812484,"ms100":{"latestTime":1672812484,"latestTemperature":102,"latestHumidity":670,"voltage":2716}}
[04/01/2023, 07:09:11] [Meross] {"id":"120027D22FF1","status":1,"onoff":0,"lastActiveTime":1672812257,"ms100":{"latestTime":1672812257}}
[04/01/2023, 07:09:11] [homebridge-meross] This plugin generated a warning from the characteristic 'Current Temperature': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[04/01/2023, 07:09:11] [Meross] [Schlafzimmer] current temperature [NaN°C].
[04/01/2023, 07:09:11] [homebridge-meross] This plugin generated a warning from the characteristic 'Current Relative Humidity': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[04/01/2023, 07:09:11] [Meross] [Schlafzimmer] current humidity [NaN%].
[04/01/2023, 07:09:11] [homebridge-meross] This plugin generated a warning from the characteristic 'Battery Level': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[04/01/2023, 07:14:11] [Meross] {"id":"120027D2980F","status":1,"onoff":0,"lastActiveTime":1672812722,"ms100":{"latestTime":1672812722,"latestTemperature":139,"latestHumidity":810,"voltage":2862}}
[04/01/2023, 07:14:11] [Meross] {"id":"120027D23B71","status":1,"onoff":0,"lastActiveTime":1672812773,"ms100":{"latestTime":1672812773,"latestTemperature":102,"latestHumidity":670,"voltage":2716}}
[04/01/2023, 07:14:11] [Meross] {"id":"120027D22FF1","status":1,"onoff":0,"lastActiveTime":1672812257,"ms100":{"latestTime":1672812257}}
[04/01/2023, 07:14:11] [homebridge-meross] This plugin generated a warning from the characteristic 'Current Temperature': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[04/01/2023, 07:14:11] [Meross] [Schlafzimmer] current temperature [NaN°C].
[04/01/2023, 07:14:11] [homebridge-meross] This plugin generated a warning from the characteristic 'Current Relative Humidity': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[04/01/2023, 07:14:11] [Meross] [Schlafzimmer] current humidity [NaN%].
[04/01/2023, 07:14:11] [homebridge-meross] This plugin generated a warning from the characteristic 'Battery Level': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[04/01/2023, 07:19:11] [Meross] {"id":"120027D2980F","status":1,"onoff":0,"lastActiveTime":1672813031,"ms100":{"latestTime":1672813031,"latestTemperature":139,"latestHumidity":810,"voltage":2862}}
[04/01/2023, 07:19:11] [Meross] {"id":"120027D23B71","status":1,"onoff":0,"lastActiveTime":1672813062,"ms100":{"latestTime":1672813062,"latestTemperature":102,"latestHumidity":670,"voltage":2716}}
[04/01/2023, 07:19:11] [Meross] {"id":"120027D22FF1","status":1,"onoff":0,"lastActiveTime":1672812257,"ms100":{"latestTime":1672812257}}
[04/01/2023, 07:19:11] [homebridge-meross] This plugin generated a warning from the characteristic 'Current Temperature': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[04/01/2023, 07:19:11] [Meross] [Schlafzimmer] current temperature [NaN°C].
[04/01/2023, 07:19:11] [homebridge-meross] This plugin generated a warning from the characteristic 'Current Relative Humidity': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[04/01/2023, 07:19:11] [Meross] [Schlafzimmer] current humidity [NaN%].
[04/01/2023, 07:19:11] [homebridge-meross] This plugin generated a warning from the characteristic 'Battery Level': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
Here are the latest logs with the red entries around the NaN Errors, I hope that helps.

Hi @bwp91 do you need any further information?

I will revert my version for the stable version now, to clean up my logs and stop the excessive logging.
If you need any further information, I am ready for updating to the beta again.

Hi @Tongo91
sorry the delay in replying. thanks for the logs - please check the latest version of the plugin i have just released :)

Hi @bwp91
no problem, thank you for looking into it.
I updated my version now, thank you.

please let me know if you see any more messages like this. i’m starting to doubt my fix now 😅

You are right 😂 I just checked the logs right now and the NaN message still exists.

Newest version should properly fix this now!

Hi @bwp91,
looks good, I can't see any NaN errors anymore.
But the red additional logging is still active, maybe you should disable that again for the stable version?
Thanks a lot for the ongoing great work!

You are correct - sorry - forget these things when I don't own the device myself. Please see newest version!

That worked and no more errors. Thank you!

Amazing! thanks for reporting this 👍


Add HTS Precompile tests for token check methods

Signed-off-by: nikolay<EMAIL_ADDRESS>Description:

Related issue(s):
Fixes #411
Notes for reviewer:

Checklist

[ ] Documented (Code comments, README, etc.)
[ ] Tested (unit, integration, etc.)

Codecov Report

Merging #468 (48092b0) into main (224cb65) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #468   +/-   ##
=======================================
  Coverage   76.46%   76.46%
=======================================
  Files          12       12
  Lines         922      922
  Branches      143      143
=======================================
  Hits          705      705
  Misses        165      165
  Partials       52       52

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


c# referencesCodeLens ain't _work _when _working _with _workspaces

VSCode Version: Code 1.19.3 (7c4205b5c6e52a53b81c69d2b2dc8a627abaa0ba, 2018-01-25T10:36:34.867Z)
OS Version: Windows_NT x64 10.0.16299
Extensions:

Extension
Author (truncated)
Version

Bookmarks
ale
0.18.1

bracket-pair-colorizer
Coe
0.10.14

supersharp
cra
0.1.4

tslint
eg2
1.0.24

code-runner
for
0.8.7

vscode-firefox-debug
hbe
1.1.0

beautify
Hoo
1.3.0

path-autocomplete
ion
1.8.1

csharpextensions
jch
1.3.0

vscode-nuget-package-manager
jmr
1.1.6

ng-bootstrap-snippets
ktr
1.0.0

vscode-todo-parser
min
1.9.1

mssql
ms-
1.3.0

csharp
ms-
1.13.1

vs-keybindings
ms-
0.1.7

debugger-for-chrome
msj
4.1.0

material-icon-theme
PKi
3.2.2

csharp2ts
raf
0.0.21

code-settings-sync
Sha
2.8.7

open-in-browser
tec
1.1.0

bootstrap4-vscode
the
3.0.0

quokka-vscode
Wal
1.0.96

html-css-class-completion
Zig
1.16.1

if working with c# projects (folders) referencesCodeLens  works perfectly, but as soon as I save multiple folders to be as workspace it disappear.

Steps to Reproduce:

save multiple folders as workspaces
open that workspace and try to find any referencesCodeLens

Reproduces without extensions: Yes

Reading your description it seems that the issue originates from an extension and not VS Code itself. Thereby I will close this issue and kindly ask you to report this issue against the extension repository.
Most extensions are on GitHub as well so it should be easy to file it against the extension. If you open an extension on the market place, click on the Support link to find out more.

Thanks again for your feedback!

Oh right that was so obvious. Thank you for using gentle words.


Add PascalCase check in boilerplate setup script

📖 Description
We had a check to make sure an argument was passed to the boilerplate-setup.sh script, but it was still possible to enter an invalid value (if you didn’t know it needed to be a PascalCase term).
What would happen if you ran ./boilerplate-setup.sh foo instead of ./boilerplate-setup.sh Foo? The mix.exs would be like this:
defmodule foo.Mixfile do
  use Mix.Project
…

And obviously it couldn’t compile. So now we make sure the first character is an uppercase letter.
📝 Notes
We don’t actually make sure it’s a valid Elixir module term but I think it’s good enough for now.

🦀 Requesting reviewers for this pull request:

@gcauchon (contributor with 4 commits in the last 90 days and 26 commits overall)
@Boubalou (expert reviewer for the elixir stack)


DHO My Profile - Wallet Address (M)

Summary:
As a DHO user I would like to my contact info in my wallet.
Description:
URL: https://dho.hypha.earth/#/@accountname
Acceptance Criteria
The following items should be displayed:

[ ] Headline "Wallet Address"
[ ] Subheadline "Only visible to you"
[ ] Bitcoin Icon, Headline "Bitcoin", Adress Field, Toggle
[ ] ETH Icon, Headline "ETHEREUM" , Address Field, Toggle
[ ] EOS Icon, Headline "EOS", EOS Address FIeld, EOS Memo Field, Toggle
[ ] Edit icon

Notes:

one of the toggles needs to be on (mandatory)
this content is only visible to the user, other people that visit the profile should not see this

Ressources:
Designs: https://xd.adobe.com/view/27bc7fff-1845-449c-913a-4ecfb3c9461c-72ef/screen/3ab31a34-1500-4fa3-8a4a-bcb0845f108c/

@pugakn here are the icons as svg


[JavaToolInstallerV0] Default value for the "versionSpec" parameter

Required Information
Question, Bug, or Feature?
Type: Feature
Enter Task Name: JavaToolInstaller
Issue Description
Since there were questions regarding which versions of JDK are available on Microsoft-hosted agents it makes sense to add a default value for versionSpec parameter if it's not specified by the user. The default value should contain the latest version of JDK that available at the moment. As an alternative print installed versions - if specified version not found as preinstalled.
Also, we can investigate the possibility replace "versionSpec" input field by the dropdown list with the actual versions of preinstalled JDK's.

Not stale