29 - Cannot Resume

When logging in with BCeID Basic, and hit "Resume" There is a 500 Error.
Page: login page
https://bcgov.sharepoint.com/:i:/r/teams/04708/Shared Documents/Research/Usability Testing/Screenshots/29 - Resume Error.png?csf=1&web=1&e=VZOQ2r

This should be solved, but lets keep an eye on it and we can re-open if required.


feat: Adding save_option column to Database Model

SUMMARY
We are adding a new enum column to the Database model that identifies which method was used in its' creation or updating.
Reason
This column is necessary so that front end components know what information to present to the user when they are editing a database.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN
Coming Soon.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

@AAfghahi it might be better leaving this PR as draft until the one with the logic is implemented and ready to merge. Then you can also link them to each other in the description.

@AAfghahi it might be better leaving this PR as draft until the one with the logic is implemented and ready to merge. Then you can also link them to each other in the description.

converted!

LGTM, but will let @betodealmeida do the approval

Hi I think this change may have introduced a bug on the front end, i get this error when adding a new database
"An error occurred while creating databases: (configuration_method) Missing data for required field."

hey, I think that issue is set to be fixed via this: https://github.com/apache/superset/pull/14583
which creates a new database edit. @betodealmeida @eschutho I can make this field optional till then?

@jmistry I pushed up a change to make it optional for the time being: https://github.com/apache/superset/pull/14668


io.read_timeseries improvements

Allow read_timeseries to read files that don't follow naming convention
Forward **kwargs to TimeSeriesDict.read()
closes #27

Could also add a strict kwarg that enforces the files follow naming nomenclature


Generate consts

c:type parsed but unused, name used only for check for ignoring.
On build some warning about overflowing pub const G_MININT8:i8 = 128; etc.
Not sure about names checker functions for GStatus.
May be better remove only_for_gtk as it contains only GTK_ENTRY_BUFFER_MAX_SIZE

Fixed escaping

Thanks!
@homu r+

:pushpin: Commit 9defa38 has been approved by gkoz

:hourglass: Testing commit 9defa38 with merge 011f499...

:sunny: Test successful - status


Lambda layers don't support build options

Describe the bug
I tried using build options with a Lambda layer so I can use babel. I currently do this for my Lambda functions as well. It is set up the same way as the documentation. Whenever I run amplify push, the script for my Lambda layer in package.json doesn't get executed at all. It works fine for my Lambda functions. Its hard for me to move my functions duplicate code into a lambda layer because of this.
Amplify CLI Version
4.24.3
To Reproduce
Try using build options with lambda layers.
Expected behavior
I expect the script in package.json to be run before amplify push.

See https://github.com/aws-amplify/amplify-cli/issues/4916. I think this is by design for now. You have to put all your compiled code in lambda layer, not install or processing is done.

Yes this is the current intended behavior but a possible enhancement. Closing as a duplicate of #4916


Bootstrap v5

https://getbootstrap.com/docs/5.0/migration/

Looking into this, I have a couple of questions:

What's the best way to test changes? I can see manually importing the package to an app that relies on it, but is there a better way to make sure all customizations are working right? Is it worth extending the docs (color theme) page to utilize every customized style? I realize there would still be breaking changes that effect the way core bootstrap works in a given app.
I see that docs/index.html gets it's bootstrap from "https://assets.cdn.fso.arizona.edu/fso-bootstrap/bootstrap.css". What is publishing it there? Can we get it to use the compiled bootstrap from this package itself?

First things first, there shouldn't be a lot to do or test here. If you're moving to Bootstrap 5, then I would drop every change except for color scheme. There's no reason to customize any more than that. I've already cut a lot of the customization out of this package.

What's the best way to test changes?

You probably want npm-link if you're developing in an app. The customizations left here are pretty minimal/cosmetic though.

Is it worth extending the docs (color theme) page to utilize every customized style?

I think it's pretty thorough already; again, there should only be color changes.

I see that docs/index.html gets it's bootstrap from "https://...." What is publishing it there?

It used to be set up in CI before we were using the package registry.

Can we get it to use the compiled bootstrap from this package itself?

You can't do it directly because the CSS is being built in CI, that's why I was using the package in S3. Unfortunately its not as simple now that the package is in the GPR.

I'll also say, migrating existing apps to a newer Bootstrap version should be pretty low impact and thus pretty low priority.


Switch async-storage repository

Details
The package @react-native-community/async-storage is deprecated from @react-native-community repo
It's moved and maintained as @react-native-async-storage/async-storage
There are some improvements that have happened since then
There are no breaking changes listed
This PR needs to be updated with the correct Onyx hash https://github.com/Expensify/react-native-onyx/pull/85 is merged
Fixed Issues

Related to #2667
Tests
Since storage affects everything a general tests for regressions should be carried
QA Steps
Since storage affects everything a general tests for regressions should be carried
Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[x] iOS
[x] Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

Cool, thanks! I think trying out the next storage will be fine to do.

I've put this comment on the wrong place, so I'm posting it again here
I've run the 3 version against E.cash and here is a short summary
Median times for 7 app startups per each AsyncStorage version

The app is launched
The initial chat is always the same - a conversation with 200+ messages
Timings are captured after the app stops loading

Timing for Onyx.get

1.12.1
1.15.5
1.15.5 next

avg call time
131.55ms
140.95ms
134.90ms

total call time
32862.34ms
35175.71ms
33552.87ms

total calls count
529
529
529

note: a lot of the calls are resolved from Onyx cache, the actual hard reads vary from 200 to 1000ms

More data is available here:
https://docs.google.com/spreadsheets/d/1ABHCzs9yZIXmHxMJnDboyyMw8ICjQQ3sxIP_23c7Lws/edit?usp=sharing

This is approved, but I am adding a [HOLD] to the title so that it's not merged until the hash for react-native-onyx is updated.

Updated react-native-onyx hash

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to production         in version: 1.0.77-5🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Unauthenticated thrown when calling requireAdminUser and is authenticated

If the user is logged in and navigates to a state with requireAdminUser applied, unauthenticated is thrown, whereas I'd expect unauthorized to be.

requireUserWithRoles's catch block is indiscriminate; it should check for unauthorized errors and re-throw them.


[kafka] remove KRaft mode support workarounds

Remove update_run.sh script as it is no longer needed. KRaft mode configuration is now built-in (etc/confluent/docker/configure etc/confluent/docker/ensure) in the latest confluentinc/cp-kafka:7.4.0-1-ubi8 image.
Resolves #879

[ ] CHANGELOG.md updated to document new feature additions
[ ] Appropriate documentation updates in the [docs][]
[ ] Appropriate Helm chart updates in the [helm-charts][]

Hello @styblope,
Could you add a change log please?


Automator: update istio/client-go@master dependency in istio/istio@master

Generated by Automator - 2024-06-27T01:18:28+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-helm_istio
b8c34599484a28806b26f8809d32f163f56a1e3a
link
true
/test integ-helm

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-sigs/prow repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-helm_istio
c6d031f33475a25b6e82a7b3f94dd7a74fcd3e64
link
true
/test integ-helm

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-sigs/prow repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-helm_istio
60f7765c80184d3b7da9cf6893ceb565ade7aa05
link
true
/test integ-helm

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-sigs/prow repository. I understand the commands that are listed here.


Suggestion： Error notification

Hi！ I want the button “Report this issue” from the error notification link to Github , not Files UWP

@XSH-Hero This issue should be resolved when we release the next update.


{Core} Add US Gov cloud endpoint for synapse

Description

Add US Gov cloud endpoint for synapse
Modify the resource id for synapse in mooncake

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

Hi @haroldrandom , The CI failed in "Test Extensions Loading Python36" step, from the logs
Request to https://azurecliprod.blob.core.windows.net/cli-extensions/stack_hci-0.1.1-py3-none-any.whl failed with 500
we can see that it is due to storage issue, could you please double check and fix this?

This is a known issue. I have re-run the task. But still, we'd better find a permanent solution.

This is a known issue. I have re-run the task. But still, we'd better find a permanent solution.

This is a known issue. I have re-run the task. But still, we'd better find a permanent solution.

This is a known issue. I have re-run the task. But still, we'd better find a permanent solution.

Thanks~


Update to latest dependencies.

This PR updates cargo-component to the latest dependencies.
In doing so, wit-bindgen has been updated to generate based on a "world" rather than bindings per import/export.
As such, this is a breaking change with user code as now there's a singular "bindings" crate that gets generated.

Open to anyone that wants, or has the time, to review 😄


Want to add our Contributor page in the website

Details
Is your feature request related to a problem? Please describe.
Our Contributors page in the website
Describe the solution you'd like
We can add a Contributors page in the website. which is shows the name and the profile image of the contributor.and the number of commits is done by the contributor

Hi
I am interested in doing this issue
so kindly assign me this
I will do my best to reach your expectations
Thank You  : )

This is already added


Updating Property node instead of append new if key already exists

In case of setting property which originally was in property file, Property node will be replaced with new value.

Could you add a test for this please? It'll clarify what the issue is, too.

Ok. I'll try to do it tomorrow. Are there any ways how to load properties from string instead of a file? (Properties.load() for string).

load() takes any readable stream, so you can use io.StringIO.

You can try to run this test for previous version (without my changes). This test will fail, because str(props) will contain two entries

key = value
key = another_value

instead of only one

key = another_value

Looks good.
Can you squash the two commits please, and while you're at it respect the CONTRIBUTING.md guidelines on commit messages ;)

Better?

Yep. I'll test it tomorrow but lgtm.


Mobile layout for sidebars

Once we have our new layout components in the design system, there is a bug on the mobile experience with the existing components that it would be great to address.
Backstory!
Right now the layout on desktop view consists of sidebar on the right and a pageContent section on the left that contains both the main part of the page and a footer along the bottom. The height of the page content is  height: calc(100vh - #{$ui-header-height} - #{$ui-navbar-height}); (seen in app/javascript/researcher/new_project_builder/layout/base_page.scss). Then the footer just sits beneath.
This causes an issue on safari mobile, because 100vh does not mean exactly the same thing it means on desktop 😅
See https://nicolas-hoizey.com/articles/2015/02/18/viewport-height-is-taller-than-the-visible-part-of-the-document-in-some-mobile-browsers/
Why is this an issue? Since 100vh extends past the actual viewport, it causes there to be a scroll bar on the main part of the page to scroll down to the footer. That by itself is not the end of the world, but it becomes a problem because that extra scroll bar prevents you from scrolling the inner content, the main part of the page!
It happens on a few of our pages that are still not using the new layout components, one example being the Recruit participants page. You have to be on mobile safari to see the issue:

But basically the inner content (the table of participants) has many rows, but is not scrollable at all on mobile 😮 .
So in the new layout components, to get around this issue and not use 100vh, we ended up just making the Footer a fixed position div along the bottom, with the main content of the page not having any height specified.
See app/javascript/researcher/new_project_builder/layout/base_page.scss and app/javascript/common/new_layout/footer/footer.scss for where this override for the mobile case happens.
This works for the most part, but the problem arises that the content is still scrollable when the sidebar navigation is expanded. Like maybe you can see in this screenshot, I expanded the mobile sidebar and then scrolled up, and the page content peaks out at the bottom:

This is the main issue right now, that we don't want the sidebar to be scrollable at all when expanded on mobile. But there may be a few ways to solve this, including addressing the crux of the issue (the 100vh differences on mobile) in a different way.

Not relevant today.


Broken link for filter jobs via UI & API

The "Jobs Type" section had broken link for viewing the jobs list from the User interface and through API. Corrected those links to point to proper pages as above.

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Deploy preview for docsdocker ready!
Built with commit 542b0420793cf911c2d31f85f080ec1b3e918a63
https://deploy-preview-7932--docsdocker.netlify.com


Apply delay penalty on transducer

This PR supports to apply delay penalty on transducer loss, to encourage the streaming models (e.g., time-masking conformer and lstm) to emit symbols earlier.
It requires https://github.com/k2-fsa/k2/pull/976 in k2.
See https://github.com/k2-fsa/k2/issues/955 and https://arxiv.org/pdf/2211.00490.pdf for more details.

You could apply the delay penalty on streaming models, and calculate the symbol delay during decoding as in https://github.com/k2-fsa/icefall/pull/598.

2

Please fix the CI errors.

Will fix that tomorrow.


parse_block_html for Markdown in VS Code?

Is there something similar to kramdowns parse_block_html: true [1] in Visual Studio Code?
Right now something like this:
<div class="message">
Caution: This might at times cause problems with `foo` commands ...
</div>

is not parsed as markdown both in the editor and preview.
[1] https://kramdown.gettalong.org/parser/kramdown.html#option-parse-block-html

VSCode's built-in markdown extension uses markdown-it. To my knowledge markdown-it does not have an equivalent setting to kramdown's, but an extension may be able to contribute a markdown-it plugin that adds this: https://code.visualstudio.com/docs/extensionAPI/api-markdown#_adding-support-for-new-syntax-with-markdownit-plugins
Closing as extension candidate


feat(multicluster): add weight to RemoteCluster

Signed-off-by: Allen Leigh<EMAIL_ADDRESS>
Description:
Add weight attribute to remote cluster spec. This PR prepares for implementing locality based routing.

Affected area:

Functional Area

New Functionality
X

Documentation
[ ]

Install
[ ]

CLI Tool
[ ]

Certificate Management
[ ]

Control Plane
[ ]

Ingress
[ ]

Egress
[ ]

Networking
[ ]

Observability
[ ]

SMI Policy
[ ]

Sidecar Injection
[ ]

Security
[ ]

Upgrade
[ ]

Tests
[ ]

CI System
[ ]

Demo
[ ]

Performance
[ ]

Other
[ ]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project?

Did you notify the maintainers and provide attribution?

No

Is this a breaking change?
No

Codecov Report

Merging #3685 (9952123) into main (f9dc7b9) will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #3685      +/-   ##
==========================================
+ Coverage   67.44%   67.45%   +0.01%
==========================================
  Files         181      181
  Lines        8772     8772
==========================================
+ Hits         5916     5917       +1
+ Misses       2823     2822       -1
  Partials       33       33

Flag
Coverage Δ

unittests
67.45% <ø> (+0.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

...icate/providers/certmanager/certificate_manager.go
87.90% <0.00%> (+0.80%)
:arrow_up:

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 f9dc7b9...9952123. Read the comment docs.


ENH: Allow providing an int to chunksizes

@LennartGevers

Ok, you were quick

Yes exactly. Seems like the most likely thing a new user would try (I think).

Yeah and now its more consistent to how executors can be specified among Outputs


Proposal: Additional JS pre-processing on module build

As started in #5103, would like to propose a bit more of module processing than v2 is intended to have.
My first impression on module build was "finally, the same build for all the code!", but as I see it is not actually true, @gaearon explained that modules should be in a valid JavaScript format already.
Our use case: several projects depend on "core" package which was decided to use as a node module via git (not a git submodule for couple of reasons on convenience). Now have to build "core" project files with a separate script and Babel setup. It has some components, helpers, etc. And we want to have ability to use flat imports mainly. Components use JSX, which is not supported by module build as it figured out.
Proposal: Additional JS pre-processing on module build
Let's have couple options I see for the consideration:

Ability to "turn on" same preprocessing for modules as current project already has.
Ability to add something to Babel "plugins" section (like "transform-react-jsx").

Both options would probably have a better use with ability to specify this for the "list of modules/mask", or "per module".

Things that need to be worked out:

How do packages opt into being "raw"? Is the list specified in the application package? Or in packages themselves?
What about transitive dependencies? Where do we list them? In the application, or in the packages that import them? Are dependencies of "raw" dependency packages implicitly "raw" too?
Should a dependency be able to introduce a "raw" transitive dependency in a minor version? If the allowed list is inside the app, this wouldn't be possible unless it's implicitly transitive.
Upgrading the app can break the dependencies because the tooling has changed. How to mitigate this? How to make it an informed choice? What if the same "raw" dependency is used from apps with incompatible compiler versions? How does a "raw" dependency specify which "hosts" it's compatible with?
How does this affect ejecting?
How does this affect testing and linting? Do we automatically run tests or lint for other "raw" packages too? Only for the app? How would we set up a "raw" package test suite in this case? If it uses different tooling, there's a risk of different behavior.
If we later add support for monorepos, would we assume that every package in a monorepo is "raw" by default? If yes, how to opt out? If no, do all apps in a monorepo have to specify the same list of "raw" dependencies (potentially with transitive ones)? Does it mean that adding a new "raw" dependency (or a transitive one) takes a lot of effort? Should the "raw" list be centralized? Should it be config or code?

Using "raw" could be for "all" or "specific", in both cases responsibility relies on application. As out-of-the-box it is "off", applying this kind of behavior should be aware.
Let's check the main goal here: for me it is ability to build packages with same kind of sources the same way.
Transitive dependencies by default is probably "as is"; also could be included if required. New dependencies in this case are also on application. Usually if I use a library, like material-ui, I check it's sources so can see it's ready for my build system (maybe with some extra sugar), but don't really dig into it's dependencies if they are commonly used.
Not sure how ejecting works right now, but I suppose this could just extend configuration for modules from the config. A good question anyway.
I'd not extend testing wider that app itself, usually packages have own tests which are used before releases, in own CI pipelines etc. Same for watch mode: usually you stop it before upgrade.
Can't say about monorepo, didn't work with it yet in a context.
About public/private: I'd not care, to be honest. Plus, there already are repos with 2 kinds of export including "next", just sources etc, and you choose what suits better.
Module can export ES5, but you will be able to use their sources with flat imports to make build actually better than that if you build for modern browsers only.

I'm a monorepo user using a slight fork of react-scripts to make it sure. Here are my quick answers:

Things that need to be worked out:

How do packages opt into being "raw"? Is the list specified in the application package? Or in packages themselves?

It could support the config format for the tools that manage monorepos, like lerna and yarn. For yarn these are all already listed in workspaces.packages in package.json. Look for a package.json in a parent directory, and try to read the package list from there.

What about transitive dependencies? Where do we list them? In the application, or in the packages that import them? Are dependencies of "raw" dependency packages implicitly "raw" too?

I wouldn't think so. I'd treat only files underneath the explicit packages as "raw".
For what it's worth, in my react-scripts fork I removed the line which only includes files underneath src for babel, include: paths.appSrc: https://github.com/facebook/create-react-app/blob/master/packages/react-scripts/config/webpack.config.prod.js#L276. That change alone was good enough when using yarn workspaces.
Curiously it works with exclude: /node_modules/. Yarn adds all your packages as symlinks inside the root node_modules folder, which is why everything can find each other. I guess webpack resolves those symlinks or something and the final path it tests in excludes is the resolve version (which is outside of node_modules).
Not sure what the right solution here is though. I understand wanting the include restriction.

Should a dependency be able to introduce a "raw" transitive dependency in a minor version? If the allowed list is inside the app, this wouldn't be possible unless it's implicitly transitive.

If we're thinking just of monorepos, I don't think this is an issue. If you're trying to find a slightly more general solution though, these questions are harder. For monorepos I think only ever sticking to the packages list would work.

Upgrading the app can break the dependencies because the tooling has changed. How to mitigate this? How to make it an informed choice? What if the same "raw" dependency is used from apps with incompatible compiler versions? How does a "raw" dependency specify which "hosts" it's compatible with?

If you stick with monorepos + an explicit package list this isn't a problem. You're only ever dealing with packages that you own so it's up to you to upgrade.

How does this affect ejecting? How to avoid complicating the configs for this?

Not sure

How does this affect testing and linting? Do we automatically run tests or lint for other "raw" packages too? Only for the app? How would we set up a "raw" package test suite in this case? If it uses different tooling, there's a risk of different behavior.

I don't have enough context to answer some these other questions, but it you only support monorepos & local packages that you own with this these answers seem to have easy answers (yes, support running tests for those packages)

If we later add support for monorepos, would we assume that every package in a monorepo is "raw" by default? If yes, how to opt out? If no, do all apps in a monorepo have to specify the same list of "raw" dependencies (potentially with transitive ones)? Does it mean that adding a new "raw" dependency (or a transitive one) takes a lot of effort? Should the "raw" list be centralized? Should it be config or code?

Yes, assume it's raw by default. Why would you want to opt out? I don't think that necessarily has to be a feature.

Is it allowed to publish a "raw" dependency on public npm? That's dangerous for the ecosystem. But perhaps we want to allow publishing them to a private registry? How to enforce this, and is it a useful thing to enforce? What about dependencies that are neither on npm nor in a monorepo?

Not sure about this one. I don't publish mine. I would discourage publishing raw to npm for now though.

How should watching mode work? Do we automatically rebuild all "raw" dependencies? Do we run the watcher in other folders if they're linked? Does the watcher lint them with parent project settings? What happens when a "raw" dependency wants to get its own build step?

Do you need to run the watcher in older folders? Right now watching "just works" for me by using the exclude: /node_modules/ instead of include. I think webpack will pick it all up correctly based on the dependency graph.
If a "raw" dependency wants its own build step, it's probably for a different environment (where you have to compile less or more features), and I'd ignore it and say that create-react-app will always import the raw version.

What do other tools do? How do we converge on common behavior with them? Does it matter?

This is a largely unsolved problem, so I think you should find whatever is the best for create-react-app. My only experience is with lerna which tries to run multiple processes per packages to build them separately and it gets quite messy.

While I'm not able to answer every question explicitly. My approach, in a monorepo, is that the sibling packages have a babel.config.js file in the root that define the plugins needed to transform the source down to more generic ES5. Of course, this does get difficult in that you would have to rely on/trust published packages converting down to a generic common ancestor. Most packages do this now through their build step. There is also room for a specific entry key in the package.json of the dependency that points to the 'raw' input, while maintaining the existing tooling around the current 'main' key that points to a pre-transpiled ES5 entry.
While you can set constraints/policy for an internal dependency, things get dramatically complex when considering the wider ecosystem. Though this is a very important conversation to have as everyone in the greater node/babel community will need to orchestrate this transition together. It will certainly be a huge push and may need coordination between node/npm/babel and other leaders in the community.

Ok

It could support the config format for the tools that manage monorepos, like lerna and yarn. For yarn these are all already listed in workspaces.packages in package.json. Look for a package.json in a parent directory, and try to read the package list from there.

We actually tried that and it ended up being a bad decision. People can have monorepos but not want to compile stuff inside of them with host app setup because they might already have a different compile step for a subset of packages. And similarly, people sometimes want to get "raw" packages from a private npm registry rather than a monorepo, in which case putting them in monorepo config wouldn't work or make sense.

People can have monorepos but not want to compile stuff inside of them with host app setup

It seems like in that case they could do import foo from "other-package/lib/file.js" which is a pre-built file. CRA might build it again but wouldn't do anything. If you want the raw file you do import foo from "other-package/src/file.js", so src and lib disambiguate whether it's raw or not.
For the case of packages from a private registry, that seems like a hard problem to solve without allowing raw packages from the public registry as well.
I am very much entrenched in my view as a user of a specific setup though. I have no idea what the right path is for CRA, but I'm always happy to put forth what my setup is for feedback.

Added a reference to #5164 (pre-processing for modules in tests) into description.

Just a thought and question regarding this proposal. There is a definitely a use-case where people would want to create separate ES6 modules and import them (non-transpiled) into a CRA2 module (ala yarn workspaces). What is the possibility of this proposal being worked on to address this need?

My proposal :

packages that want to share babel transpilation rules can be written in /src. They share the same rules as the main project (need https://github.com/facebook/create-react-app/pull/6056 to avoid eslint warnings about node_modules inside src)
packages with specific rules are managed outside of src. If you write this kind of package, you know how to use separate tools

both type of packages are managed using workspaces


Remove duplicated Holidays

This PR removes duplicated holidays in two countries:

USA : Juneteenth National Independence Day(Jun 19th)
Angola : Dia do Heroi Nacional (Sep 17th)

This PR should close #505 and fix #488

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.0009%) to 98.69%

Totals

Change from base Build<PHONE_NUMBER>:
-0.0009%

Covered Lines:
5222

Relevant Lines:
5225

💛  - Coveralls

Thank you! 👍


Archimedes ships + Exo Suit crash

Attempting to right click a ship's helm while wearing the exo suit causes the client to crash.
I'm also getting a strange zoom out effect while equipping the armor, not entirely sure why my fov changes while wearing the armor.
Crash log: http://pastebin.com/vKQTT4HJ

@PsionicArchon can you re-test this?

Archimedes' Ships does not exist past Minecraft 1.7.


CVE-2023-28840: Update LTS to github.com/docker/docker v20.10.24+incompatible

Description
https://nvd.nist.gov/vuln/detail/CVE-2023-28840 is a high severity vulnerability fixed in github.com/docker/docker v20.10.24+incompatible.
The main branch has already moved on to github.com/docker/docker v23.0.x+incompatible.  This is the minimal change needed to address this vulnerability in LTS.

Thanks!

@roidelapluie
I know you just dropped 2.37.7.   When do you think you'll publish 2.37.8 with this in it?

There is already a PR. Probably for Saturday


Get PandA PCAP working

The PandA is now configured to save position encoder values to an h5 value in the specified panda directory. Hyperion is already configured to do this, we just haven't tested it yet. We may need to set the filename at some point in our plan. This would be via the signal panda.data.hdf_file_name

We would like the positions to be saved next to the diffraction data e.g. /dls/i03/data/2024/cm37235-3/TestProteinaseK/protk_1
We then probably want a comparison script that confirms https://github.com/DiamondLightSource/hyperion/issues/1474 is working, this can just be an offline script rather than part of hyperion

Looks like the PandaHDFWriter already sets the requisite PV using the path obtained from the DirectoryProvider, therefore should just be a matter of analysing the generated data


opensearch_monitor reports changes in query_level_trigger.id and query_level_trigger.actions.*.id after creation

What is the bug?
opensearch_monitor reports changes in query_level_trigger.id and query_level_trigger.actions.*.id after creation
How can one reproduce the bug?
create resource opensearch_monitor with triggers and actions definition as below; "terraform apply" to create the resource; "terraform plan" will show a change
  ...     triggers = [         {           query_level_trigger = {             actions = [               { ... }             ]           }         }     ] ...
What is the expected behavior?
no changes should be reported after opensearch_monitor creation.
What is your host/environment?
MacOS Monterey, 12.2.1
Do you have any screenshots?

+1 I am seeing similar behavior using version 2.0.0 of the provider with Opensearch 2.9 cluster


Show version number in app bar and remove from the side nav

Currently we only show the version number in the side navigation area - which does not appear on all screens - only those with a side nav - e.g.
e.g. appears here:

but not here:

With the removal of the cluster tools button (moved as Tools under Cluster nav item), the version number looks odd and out of alignment with the 'About' text in the side bar:

(Note this shows a dev version number, which is an 8 character commit hash)
My suggestion is:

Remove the version number from the side navigation
For a released version, instead of 'About', show the version number

For a .0 minor release, we should abbreviate so that for v2.9.0 we show v2.9
For all other versions, we show the full version number, e.g. v2.10.11

For a development build, we continue to show 'About' - the commit is available from the about page

@edenhernandez-suse I think I discussed this with you and you thought this was reasonable - can you confirm?

@edenhernandez-suse I think I discussed this with you and you thought this was reasonable - can you confirm?

There might even have another issue, but I can't remember. I'm happy with this, the number is kind of a problem without the Cluster Tools button (and the addition of the "Collapse all" button), and it's not useful in production builds.
We need to test worst case scenario, though, something like v10.10.10 to check that it fits correctly.

@edenhernandez-suse Thanks - for longer versions, we can reduce the font size slightly to fit.

e2e tests are sufficient. moving to done @izaac


build: Add vendor prefixes to css rules

CRA includes the vendor prefixes with help of autoprefixer hence for excalidraw app it was getting added by default
Added the same to include the vendor prefixes in the npm package.
try here
fixes #3474

You're the best ❤

He He thank you so much ❤


Update config to use server instead of api_url

The api_url of the configuration file has currently no effect. The way to change the server has documented on the  datadog-api-client-go is to set the site property, see https://github.com/DataDog/datadog-api-client-go#changing-server
I thought it would be easier to rename the current configuration property from api_url to server has multiple values are possible (datadoghq.com us3.datadoghq.com us5.datadoghq.com datadoghq.eu ddog-gov.com).

Hey @francois2metz , thanks for the bug report and PR!
We've decided to fix this in a separate PR (https://github.com/turbot/steampipe-plugin-datadog/pull/8), keeping the api_url config arg for several reasons:

We wanted to avoid a breaking change/deprecation cycle by changing an argument name
We also wanted to remain consistent with Terraform's Datadog provider (https://registry.terraform.io/providers/DataDog/datadog/latest/docs#optional), which uses the api_url argument

We'll be releasing a new version with fixes for the api_url argument later today. If you're still seeing issues with that new version, please let us know!


Why does PasswordValidator.ValidateAsync() require a user in the input?

Here's a link to the corresponding function:
https://github.com/aspnet/Identity/blob/5a2eb3becdf6e25601f984542fc2f95a780314f0/src/Core/PasswordValidator.cs#L39
My understanding is that this function checks whether a password is valid (regardless of the user). As far as I can tell, the input TUser user isn't used anywhere in the function. Using ValidateAsync(UserManager manager, string password) would be less verbose than the current ValidateAsync(UserManager manager, TUser user, string password).
I'm using this function in my API to check whether passwords match complexity requirements. As it stands, I have to create a dummy new TUser() to run it.
Thanks for taking a look!

Yes its meant to validate the password for a particular user, the default implementation doesn't use the user, but there were requests to make it possible to do things like password history requirements which may required access to the user, so its relevant to some validators, you can just ignore it if you don't need it in your validator


Add Physics Property panel

Physics properties are currently missing when using the Panda 3D render engine. As a work-around, the Blender Render render engine's physics properties can be used. However, only rigid body options work.

b28a54f056dda1cd7e5879e0b51b813ca9cdd1ed adds some panels


linux: Connection settings,local file System,cannot access other directories

Describe the bug
I use snap to install vott,I cannot access other directories ，because the owners of these directories are different from vott’s 。I changed the user group and permissions can not be resolved。
To Reproduce
Steps to reproduce the behavior:

snap run vott
into " local File System"
Select directories with the same user group but different owners
error ：permission denied

Desktop (please complete the following information):

OS: Ubuntu 18.04
Version 2.0

Only support files with the same file owner and vott owner


Not able to install latest version on github using npm and issues with installing using git url for repo.

Prerequisites

I have read the documentation;
In the case of a bug report, I understand that providing a SSCCE example is tremendously useful to the maintainers.

Description
I am trying to use latest code in my project. But currently version 0.40 is being installed which is not pointing to latest code in master branch. I have also directly tried to install this plugin using git url as dependency. But that is only downloading pacakge.json and README.md. I can manually install it and use it but that would defeat the purpose of using package manager to set dependency and install everywhere.
Steps to Reproduce
a) Case where package is being installed directly using npm

npm install react-jsonschema-form@latest --save
check the version of package in package.json and check the code inside that package, it will be what is in 0.40.0 tagged version not the latest master.

b) Case where directly using github url is only installing package.json and README.md not any other file

npm install --save https://github.com/mozilla-services/react-jsonschema-form#6551d5ec8ca2857135060bef9c572988fe60d6ed
check react-jsonschema-form folder in node_modules, you will find that it only has package.json, ReadMe.md and local node_modules.

Expected behaviour
Latest code should be updated on npm and whenever there is major change or minor change. version should be updated.
Actual behaviour
No new version is set and npm repo is not in sync with what is on github master.
Version
0.40.0
Actual way it is written in package.json
dependency: {
"react-jsonschema-form": "^0.40.0"
}

Please wait for the next release. Thanks for your understanding.

But what about the other issue where I am using git url instead. After install it is showing package.json and README.md. And when next release is going to be take place.

After install it is showing package.json and README.md.

I had this problem too, and I couldn't find out why. When npm installing the latest master branch from Github, it only installs those 2 files instead of the entire repo. I think it should be possible to install the latest development branch in a project instead of the latest release version, so it would be nice if someone with a better understanding of npm could fix that.

I investigated this problem, found that this repo on github is that it just has source. If you build the project using command "npm run dist" you would be able to generate dist and lib folder. As they are missing in this git repo they are not getting downloaded when installed using git url.
To solve this maintainer of this repo, can add generated files as well to repo rather than ignoring it, then while installing it with git url we will get dist and lib folder as well.

Ah I see, the problem is the "files": ["dist", "lib"] mention in package.json. A solution would be to fork this repo and remove the "files" rule from package.json for your own usage. (Then, of course, you are responsible for keeping up to date by merging new versions of this package to your fork.)


update link to preview nuget

@dabutvin,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Request API_BASE environment variables setting support

For some reason, the default url https://api.openai.com/v1 needs to be changed to a custom URL.

I see. It could be useful for people interested in using the Azure OpenAI API, for example. I'll look into adding support for setting the API_BASE environment variable soon. Thank you for bringing this to my attention!

Thank you for your prompt reply. Currently, I modified the target_url in the opanai.rb to use my own URL.

I uploaded 1.8.1 with the "Base URL" option. Thanks again for your suggestion!


Enhance Login Page Usability: Resizing, Redesigning & Adding Key Features

What would you like to share or ask?
Footer Visibility & Important Links:
Problem: The footer is obscured due to the login page layout, causing essential links to be inaccessible or hidden.
Solution: Restructure and resize the login container to ensure the footer remains fully visible. Adjust the page elements to allow space for the footer without crowding, and apply a mobile-responsive layout if necessary.
Lack of Hover Effects on Important Links:
Problem: Important links on the login page are less intuitive due to the absence of hover effects, impacting user experience.
Solution: Apply subtle hover effects (e.g., color change, underline) to highlight the links on interaction, making them more noticeable and enhancing navigation.
Insufficient FAQs for Product Understanding:
Problem: Users may struggle to find information about products due to a limited FAQ section.
Solution: Expand the FAQ section to address common queries and product details, making it easier for users to understand product functionalities and features. Consider placing a FAQ preview or direct link on the login page to enhance accessibility.

Checklist

[X] I have checked the existing issues.
[X] I have read the Code Of Conduct
[X] The changes don't break the code
[X] Please attach the screenshots and video of the development work once it is done

@swaraj-das Kindly assign this task ..surely i will solve it


CI Test environment has no desktop installed

The CI doesn't install a desktop into the default test environment, hence the lack of  desktop-file-utils
This can cause desktop applications that assume rather than properly depend on a desktop or one of its dependencies to fail.
see here
Our correct behaviour is to wait for the upstream packaging to pass the CI as-is.  Other behaviours are possible (in forks) , but "fixing" the CI environment to add a minimal desktop   (e.g. install ubuntu-desktop-minimal ) could be considered.

Morphic resonance. Further automated test failures for desktop apps because there's no minimal desktop support in the test environment.  I think the software is telling me to rethink and just fix the test.


Top-level function declarations using the lambda syntax

I propose to implement support for and promote the following syntax for top-level definitions:
sum : Int -> Int -> Int =
  \a b -> a + b

which is the same as
sum : Int -> Int -> Int
sum a b = a + b

Reasons:

Solves the annoyance of having to type the name of the function twice. Removes one refactoring task as well.
A single unified syntax for lambdas and top-level functions.
Solution to the problem of beginners misperceiving them as different things, which they aren't.
It's completely backward-compatible. This will allow to apply the promotion strategy of gradually introducing the new syntax into the docs and tutorials.

Elm syntax has generally followed the "there's exactly one way to do it" philosophy, because of your third bullet point: with this philosophy, things that look different, are different. One exception is that your second code block is really sugar for
sum : Int -> Int -> Int
sum = \a b -> a + b

But it's such a nice sugar that we keep is around. I agree rewriting function names is a bit of a pain, but one that can be solved by tooling (e.g. smartly generate sum a b =  after typing the annotation).

It may be simply solved by code-snippets

This is interesting, but I don't have any plans to do something like this soon.
There are a bunch of ideas for "task syntax" that may be nice with this, but it is a number of releases away and perhaps will never happen. So we'll consider it again at a more appropriate time.


[5.1 06/12][ConstraintSystem] Detect and diagnose missing generic arguments

Explanation: Introduce a fix to detect and diagnose situations when omitted
generic arguments couldn't be deduced by the solver based on
the enclosing context.

Example:
struct S<T> {
}

_ = S() // There is not enough context to deduce `T`

Issue: rdar://problem/51203824, rdar://problem/50512161

Scope: Diagnostics, in subset of cases where solver couldn't resolve some of the arguments for generic parameters

Risk: Low.

Testing: Added compiler regression tests and adjusted existing ones.

Reviewed by: @DougGregor, @slavapestov

Resolves: rdar://problem/51203824
Resolves: rdar://problem/50512161
(cherry picked from commit bfe19872b79e9d487054ec5e0c092665dacb5ef5)

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - fafdcf00d61eaa3b70785a7d2f1719bf2096a9a0

@swift-ci please test macOS platform


Fix TypeError in write_csv function

Bug description:
write_csv encounters TypeError when metadata is provided in dict format.
Solution:
edited write_csv function that features press_element function that loops over each element and handles lists, dicts, and strings, or "return as is".
Error message:
TypeError                                 Traceback (most recent call last)
 in <cell line: 2>()
1 # Save the corpus as a .csv file locally
----> 2 Dutch_corpus.write_csv(path = "Dutch_corpus.csv")
8 frames
/usr/local/lib/python3.10/dist-packages/sktalk/corpus/write/writer.py in (x)
52         norm = pd.json_normalize(data=metadata, sep="_")
53         df = pd.DataFrame(norm)
---> 54         df[:] = np.vectorize(lambda x: ', '.join(
55             x) if isinstance(x, list) else x)(df)
56         return df
TypeError: sequence item 0: expected str instance, dict found
Key Changes:
Added process_element function: This function handles three cases:
List: Joins the elements with ', '.
Dictionary: Converts the dictionary to a JSON string using json.dumps. Alternatively, you could convert the dictionary to a custom string format, e.g., by joining key-value pairs with a colon.
Other types: Returns the value as-is.
Replaced lambda with process_element: The np.vectorize now applies this more robust function to each element in the DataFrame.
This approach should resolve the TypeError by correctly handling cases where elements in the DataFrame are dictionaries.

does fixing this issue mean we need a new release to get it out?

Yes but for pypi that is not too bad


Use indexOf instead of startsWith

This fixes an IE11 regression and closes #3755

Should we move it to the canary branch over the master branch?

@oliviertassinari fair point, forgot to check which branch it was pointing to 😓 Yes we should


Allow for crimsonq settingst to be on a host machine volume for easy edit access

Exposed on "/" in the docker container, and is already mapped on docker file to the /CrimsonQ folder on host machine. After first run should be accessible and can be edited.


LDAP Authentication: Unknown user

Context

I am having troubles getting my mailserver setup with OpenLDAP. When trying to login, I get this in the logs:
Jul 12 06:44:11 mail dovecot: auth: ldap(weilun.tong@fancydomain.tld,<IP_ADDRESS>,<xYPdsMdwcousFgAC>): unknown user (SHA1 of given password: 2bd931)
I've tried running testsaslauthd -u "weilun.tong" -r fancydomain.tld -p "password" and the results were successful, it returned 0: OK "Success."
My docker-compose.yml looks like this:
version: "3"

services:
  rainloop:
    image: hardware/rainloop:latest
    restart: always
    volumes:
      - /srv/mailserver/client/rainloop:/var/www/rainloop/data
    networks:
      - myNetwork

  mail:
    image: tvial/docker-mailserver:latest
    restart: always
    hostname: mail
    domainname: fancydomain.tld
    container_name: mail
    ports:
      - "25:25"
      - "143:143"
      - "587:587"
      - "993:993"
    volumes:
      - /srv/mailserver/server/data/mail/data:/var/mail
      - /srv/mailserver/server/data/mail/state:/var/mail-state
      - /srv/mailserver/server/config/:/tmp/docker-mailserver/
      - /etc/letsencrypt:/etc/letsencrypt:ro
    environment:
      - ENABLE_SPAMASSASSIN=1
      - ENABLE_CLAMAV=1
      - ENABLE_FAIL2BAN=1
      - ENABLE_POSTGREY=1
      - SSL_TYPE=manual
      - SSL_CERT_PATH=/etc/letsencrypt/live/mail.fancydomain.tld/fullchain.pem
      - SSL_KEY_PATH=/etc/letsencrypt/live/mail.fancydomain.tld/privkey.pem

      # >>> SASL Authentication
      - ENABLE_SASLAUTHD=1
      - SASLAUTHD_LDAP_SERVER=openldap
      - SASLAUTHD_LDAP_PROTO=
      - SASLAUTHD_LDAP_BIND_DN=cn=admin,dc=fancydomain,dc=tld
      - SASLAUTHD_LDAP_PASSWORD=password
      - SASLAUTHD_LDAP_SEARCH_BASE=dc=fancydomain,dc=tld
      - SASLAUTHD_LDAP_FILTER=(&(uid=%U)(objectClass=person))
      - SASLAUTHD_MECHANISMS=ldap
      # <<< SASL Authentication

      # >>> Postfix Ldap Integration
      - ENABLE_LDAP=1
      - LDAP_SERVER_HOST=openldap
      - LDAP_SEARCH_BASE=dc=fancydomain,dc=tld
      - LDAP_BIND_DN=cn=admin,dc=fancydomain,dc=tld
      - LDAP_BIND_PW=password
      - LDAP_QUERY_FILTER_USER=(&(objectClass=user)(mail=%s))
      - LDAP_QUERY_FILTER_GROUP=(&(objectclass=group)(mail=%s))
      - LDAP_QUERY_FILTER_ALIAS=(&(objectClass=user)(otherMailbox=%s))
      - LDAP_QUERY_FILTER_DOMAIN=(&(|(mail=*@%s)(mailalias=*@%s)(mailGroupMember=*@%s))(mailEnabled=TRUE))
      # <<< Postfix Ldap Integration

      # >>> Kopano Integration
      - ENABLE_POSTFIX_VIRTUAL_TRANSPORT=1
      - POSTFIX_DAGENT=lmtp:kopano:2003
      # <<< Kopano Integration

    cap_add:
      - NET_ADMIN
    networks:
      - myNetwork
networks:
  myNetwork:
    external: true

I'm not sure where to go from here to test and look for an issue. Any help troubleshooting is greatly appreciated.

I have also run doveadm user '*' to check out if a user was being placed in there properly. It listed weilun.tong should it be that or should it be<EMAIL_ADDRESS>Since I'm not sure I've also tried logging in with weilun.tong instead of the full email but I still get the same error: Jul 14 01:41:43 mail dovecot: auth: ldap(weilun.tong,<IP_ADDRESS>,<OgHcsutwnMSsFgAC>): unknown user (SHA1 of given password: 2bd931)

Today I added an "email" attribute to my user. Turns out that's equivalent to the "mail" attribute the docker-compose was using to filter ldap users. Now when I run postmap -q<EMAIL_ADDRESS>ldap:/etc/postfix/ldap-users.cf it returns<EMAIL_ADDRESS>but I'm still getting the same error when trying to login, which is, `Jul 14 20:26:16 mail dovecot: auth: ldap(weilun.tong@fancydomain.tld,<IP_ADDRESS>,): unknown user (SHA1 of given password: 2bd931)

I'm still here, I disabled ldap by commenting it out on the docker-compose so that I can use the setup.sh email list again.
When I type in ./setup.sh email list it returns<EMAIL_ADDRESS>as expected, but when I try doveadm user '*' it does not list<EMAIL_ADDRESS>when I have LDAP enabled on docker-compose.yml. When I comment out everything LDAP related, the doveadm command lists<EMAIL_ADDRESS>I want my UID to remain weilun.tong because I also have GitLab setup with LDAP and it uses that, so I tried changing a few LDAP filters:
# First I tried adding the Dovecot filters
- DOVECOT_PASS_FILTER="(&(objectClass=mailAccount)(mail=%n))"
- DOVECOT_USER_FILTER="(&(objectClass=mailAccount)(mail=%n))"

but it seemed to have no effect. I judge this by trying doveadm user '*' again, but it just returns the usual "weilun.tong".
# I tried changing the SASLAUTH filter next
- SASLAUTHD_LDAP_FILTER=(&(mail=%U)(objectClass=person))

I really hoped changing "uid" to "mail" here would chane the output of doveadm user '*' but it did not, again only returning "weilun.tong" instead of<EMAIL_ADDRESS>as I hoped.
# Finally, I tried changing the SASLAUTH again and also the Dovecot filters
- SASLAUTHD_LDAP_FILTER=(&(mail=%s)(objectClass=person))
- DOVECOT_PASS_FILTER="(&(objectClass=mailAccount)(mail=%s))"
- DOVECOT_USER_FILTER="(&(objectClass=mailAccount)(mail=%s))"

I'm not sure on what the %s or the %u or the %n does so I was hoping that maybe changing it to %s to mirror the ldap query filters would change the output of doveadm user '*', again the output was just "weilun.tong"

Could it be a particular schema that's required by Dovecot which is not already on osixia/docker-openldap?

I use this ldap server with this project: https://hub.docker.com/r/jsmitsnl/docker-openldap-postfix-book/

Thanks @johansmitsnl! I'll give that a shot ASAP. It'll probably end up being early tomorrow though.

So I used your image @johansmitsnl and it worked! I can now log into my account on LDAP via RainLoop, but now I cannot seem to send or receive any emails... When trying to send I get an Authentication failure from RainLoop not unlike issue #1002 that I figured out the problem to. However, during that issue I learned that I could send and receive emails via Google's Gmail Android app, so I tried that this time, but I'm getting what seems to be issues validating smtp settings... The app says "Couldn't open connection to server" It doesn't look like I'm receiving any login attempts according to the docker logs. I wouldn't quote me on that though, Also, when successfully logging in via RainLoop, I see something like this:
Jul 29 16:06:20 mail dovecot: imap-login: Login: user=<weilun.tong>, method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=25365, TLS, session=<41KPhiVy+J+sFgAC>
Jul 29 16:06:20 mail dovecot: imap(weilun.tong): Logged out in=549 out=2427

and I can't really recollect if that's normal behavior, when it logs in but instantly logs out in the backend.
It really feels like one step forward but 10 steps back XD XD but hey! Thanks to you Johansmitsnl I can at least login to the mail server with LDAP!

So I noticed the SASLAUTHD_LDAP_SEARCH_BASE=ou=people,dc=localhost,dc=localdomain is an error, I fixed that to be SASLAUTHD_LDAP_SEARCH_BASE=ou=people,dc=fancydomain,dc=tld and I cn at least sign in to my account via Google's Android Gmail app (both outgoing and incoming mail settings pass authentication), but I still can't send or receive emails.
When trying to send an email to my personal gmail I get this in the logs:
Aug  3 19:47:10 mail dovecot: imap-login: Login: user=<weilun.tong>, method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=25580, TLS, session=<7POEMY1y6ZlrTawd>
Aug  3 19:47:11 mail dovecot: imap(weilun.tong): Connection closed (LIST finished 0.181 secs ago) in=50 out=1171
Aug  3 19:47:11 mail postfix/submission/smtpd[25517]: connect from mobile-107-77-172-29.mobile.att.net[<IP_ADDRESS>]
Aug  3 19:47:11 mail postfix/submission/smtpd[25517]: Anonymous TLS connection established from mobile-107-77-172-29.mobile.att.net[<IP_ADDRESS>]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
Aug  3 19:47:12 mail postfix/submission/smtpd[25517]: 752BA2B8038A: client=mobile-107-77-172-29.mobile.att.net[<IP_ADDRESS>], sasl_method=PLAIN<EMAIL_ADDRESS>Aug  3 19:47:12 mail postfix/sender-cleanup/cleanup[25520]: warning: dict_ldap_lookup: Search error 2: Protocol error
Aug  3 19:47:12 mail postfix/sender-cleanup/cleanup[25520]: warning: ldap:/etc/postfix/ldap-aliases.cf lookup error for<EMAIL_ADDRESS>Aug  3 19:47:12 mail postfix/sender-cleanup/cleanup[25520]: warning: 752BA2B8038A: virtual_alias_maps map lookup problem for<EMAIL_ADDRESS>-- message not accepted, try again later

I tried looking into aliases on the wiki, is this necessary if I'm not forwarding emails<EMAIL_ADDRESS>is receiving?

The issue seemed to be that empty "query_filter = " line found in /etc/postfix/ldap-domain.cf, I found out because I removed it just to test and see if the mail server would work. That's going to reappear every time my container restarts though right? How do I make it so it doesn't when I restart the container?

hey you can fill that line in with LDAP_QUERY_FILTER_DOMAIN envvar

Hi @hijak! Thanks it works!


System GNOME Shell extensions installed via the gnome-extensions module not showing up in Extension Manager

What the title says. The system-wide extensions are being installed:

But somehow they're not showing up anyway:

Hmm, I'm not sure what's up with that.
I know that another user installed Vitals extension from this module & it works for him.
metadata.json is the file which is responsible for showing extensions in GUI.
Can you tell me if that file exists & if it exists, does it have sufficient 0644 permissions?

it seems to

Maybe try to rebuild the image now & update the system, to check if issue would go away just in case.

Maybe try to rebuild the image now & update the system, to check if issue would go away just in case.
When you do that, please show me rpm-ostree status output if it's still not working

Turns out they were being shadowed by the same extensions also being installed as user extensions, from before i rebased to my own image


stringify and escape jwt options before sending to generator

with this change, the test suite outputs the serialized and escaped JSON to the exec command instead of [object Object]

looks good


Format-block component

What have changed

Added a component format-block. Takes t and locale as params.

t is required
locale is optional

Why

Enabled us to build more complex translations, and use helpers and components in our translations.

This is literally my first time working with add-ons in Ember, so I apologies if this is not the way to do it. Let me know what your thoughts are.

Thank you for submitting this pull request, however I do not see a valid CLA on file for you. Before we can merge this request please visit https://yahoocla.herokuapp.com/ and agree to the terms. Thanks! :smile:

Paging @taheilo

Sorry about the late response.
I have been looking into the failing test not ok 46 PhantomJS 1.9 - component:format-block: should throw error if no key but it passes for me locally. Do you have any pointers as to what I might be doing wrong?
The request from yahoocla has already been done.

Left a question above since I don't think I understand the use case.

This is the scenario I needed it for:
I have a post with a bunch of editors. The translation for this would in english be:
Edited by Paul, Brian, Brad +4 with the +4 indicating that there are 4 more. The +4 is wrapped in a tooltip component so they show up on hover. It could however be pretty much anything you put in the yield.

@taheilo I need to think more about this.  I'm actually in the process of moving around the internals and would like to revisit once that is complete.  Should be within the next two-weeks.
The gist is I plan to make the message compiler swappable for others that do not support the ICU message syntax for translations.  And in doing so, will make https://github.com/jasonmit/ember-intl/pull/377/files#diff-fa056eb2fd4f3b51ff7bd33831c63070R30 not compatible with this approach since that could interfere with message syntax for non-ICU.


Apache Spark issue with istio

Bug description
I tried to install Spark using bitnami chart with default values in istio enabled namespace:
https://github.com/bitnami/charts/tree/master/bitnami/spark
spark workers cannot communicate with master using spark rpc protocol.
workers envoy access logs:
2020-10-12T23:19:46.484430533Z 2020-10-12T23:19:46.484180Z	info	Envoy proxy is ready
2020-10-12T23:19:49.597606234Z [2020-10-12T23:19:49.589Z] "- - -" 0 UH "-" "-" 0 0 7 - "-" "-" "-" "-" "-" - - <IP_ADDRESS>:7077 <IP_ADDRESS>:45878 - -
2020-10-12T23:19:59.60201629Z [2020-10-12T23:19:55.583Z] "- - -" 0 UF,URX "-" "-" 0 0 18 - "-" "-" "-" "-" "<IP_ADDRESS>:7077" outbound|7077||spark-master-svc.default.svc.cluster.local - <IP_ADDRESS>:7077 <IP_ADDRESS>:45938 - -
2020-10-12T23:20:09.601992159Z [2020-10-12T23:20:01.564Z] "- - -" 0 UF,URX "-" "-" 0 0 2 - "-" "-" "-" "-" "<IP_ADDRESS>:7077" outbound|7077||spark-master-svc.default.svc.cluster.local - <IP_ADDRESS>:7077 <IP_ADDRESS>:45992 - -
2020-10-12T23:20:09.602059689Z [2020-10-12T23:20:07.581Z] "- - -" 0 UF,URX "-" "-" 0 0 4 - "-" "-" "-" "-" "<IP_ADDRESS>:7077" outbound|7077||spark-master-svc.default.svc.cluster.local - <IP_ADDRESS>:7077 <IP_ADDRESS>:46048 - -
2020-10-12T23:20:19.602430225Z [2020-10-12T23:20:13.564Z] "- - -" 0 UF,URX "-" "-" 0 0 3 - "-" "-" "-" "-" "<IP_ADDRESS>:7077" outbound|7077||spark-master-svc.default.svc.cluster.local - <IP_ADDRESS>:7077 <IP_ADDRESS>:46102 - -
2020-10-12T23:20:19.602460947Z [2020-10-12T23:20:19.580Z] "- - -" 0 UF,URX "-" "-" 0 0 10 - "-" "-" "-" "-" "<IP_ADDRESS>:7077" outbound|7077||spark-master-svc.default.svc.cluster.local - <IP_ADDRESS>:7077 <IP_ADDRESS>:46160 - -
2020-10-12T23:20:59.604970891Z [2020-10-12T23:20:52.589Z] "- - -" 0 UF,URX "-" "-" 0 0 4 - "-" "-" "-" "-" "<IP_ADDRESS>:7077" outbound|7077||spark-master-svc.default.svc.cluster.local - <IP_ADDRESS>:7077 <IP_ADDRESS>:46532 - -
2020-10-12T23:21:29.606355696Z [2020-10-12T23:21:25.572Z] "- - -" 0 UF,URX "-" "-" 0 0 3 - "-" "-" "-" "-" "<IP_ADDRESS>:7077" outbound|7077||spark-master-svc.default.svc.cluster.local - <IP_ADDRESS>:7077 <IP_ADDRESS>:46898 - -
2020-10-12T23:21:59.60615571Z [2020-10-12T23:21:58.593Z] "- - -" 0 UF,URX "-" "-" 0 0 9 - "-" "-" "-" "-" "<IP_ADDRESS>:7077" outbound|7077||spark-master-svc.default.svc.cluster.local - <IP_ADDRESS>:7077 <IP_ADDRESS>:47242 - -
2020-10-12T23:22:39.607634311Z [2020-10-12T23:22:31.589Z] "- - -" 0 UF,URX "-" "-" 0 0 6 - "-" "-" "-" "-" "<IP_ADDRESS>:7077" outbound|7077||spark-master-svc.default.svc.cluster.local - <IP_ADDRESS>:7077 <IP_ADDRESS>:47594 - -
2020-10-12T23:23:09.608354321Z [2020-10-12T23:23:04.591Z] "- - -" 0 UF,URX "-" "-" 0 0 6 - "-" "-" "-" "-" "<IP_ADDRESS>:7077" outbound|7077||spark-master-svc.default.svc.cluster.local - <IP_ADDRESS>:7077 <IP_ADDRESS>:47936 - -
2020-10-12T23:23:39.607643696Z [2020-10-12T23:23:37.589Z] "- - -" 0 UF,URX "-" "-" 0 0 5 - "-" "-" "-" "-" "<IP_ADDRESS>:7077" outbound|7077||spark-master-svc.default.svc.cluster.local - <IP_ADDRESS>:7077 <IP_ADDRESS>:48308 - -
2020-10-12T23:24:19.607935687Z [2020-10-12T23:24:10.584Z] "- - -" 0 UF,URX "-" "-" 0 0 11 - "-" "-" "-" "-" "<IP_ADDRESS>:7077" outbound|7077||spark-master-svc.default.svc.cluster.local - <IP_ADDRESS>:7077 <IP_ADDRESS>:48668 - -
2020-10-12T23:24:49.609418102Z [2020-10-12T23:24:43.587Z] "- - -" 0 UF,URX "-" "-" 0 0 8 - "-" "-" "-" "-" "<IP_ADDRESS>:7077" outbound|7077||spark-master-svc.default.svc.cluster.local - <IP_ADDRESS>:7077 <IP_ADDRESS>:49034 - -
2020-10-12T23:25:19.610426859Z [2020-10-12T23:25:16.590Z] "- - -" 0 UF,URX "-" "-" 0 0 5 - "-" "-" "-" "-" "<IP_ADDRESS>:7077" outbound|7077||spark-master-svc.default.svc.cluster.local - <IP_ADDRESS>:7077 <IP_ADDRESS>:49408 - -

workers app logs:
2020-10-12T23:26:23.515216868Z  23:26:23.51
2020-10-12T23:26:23.51614386Z  23:26:23.51 Welcome to the Bitnami spark container
2020-10-12T23:26:23.517086864Z  23:26:23.51 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-spark
2020-10-12T23:26:23.517997868Z  23:26:23.51 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-spark/issues
2020-10-12T23:26:23.519027225Z  23:26:23.51
2020-10-12T23:26:23.524658485Z  23:26:23.52 INFO  ==> ** Starting Spark setup **
2020-10-12T23:26:23.536920006Z  23:26:23.53 INFO  ==> Generating Spark configuration file...
2020-10-12T23:26:23.540673381Z  23:26:23.54 INFO  ==> ** Spark setup finished! **
2020-10-12T23:26:23.540689587Z
2020-10-12T23:26:23.548148905Z  23:26:23.54 INFO  ==> ** Starting Spark in worker mode **
2020-10-12T23:26:23.558059753Z starting org.apache.spark.deploy.worker.Worker, logging to /opt/bitnami/spark/logs/spark--org.apache.spark.deploy.worker.Worker-1-spark-worker-0.out
2020-10-12T23:26:23.639031571Z Spark Command: /opt/bitnami/java/bin/java -cp /opt/bitnami/spark/conf/:/opt/bitnami/spark/jars/* -Xmx1g org.apache.spark.deploy.worker.Worker --webui-port 8081 spark://spark-master-svc:7077
2020-10-12T23:26:23.639052558Z ========================================
2020-10-12T23:26:24.174937694Z Using Spark's default log4j profile: org/apache/spark/log4j-defaults.properties
2020-10-12T23:26:24.184237867Z 20/10/12 23:26:24 INFO Worker: Started daemon with process name<EMAIL_ADDRESS>2020-10-12T23:26:24.201074938Z 20/10/12 23:26:24 INFO SignalUtils: Registered signal handler for TERM
2020-10-12T23:26:24.201824717Z 20/10/12 23:26:24 INFO SignalUtils: Registered signal handler for HUP
2020-10-12T23:26:24.201995203Z 20/10/12 23:26:24 INFO SignalUtils: Registered signal handler for INT
2020-10-12T23:26:24.529713443Z 20/10/12 23:26:24 WARN NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
2020-10-12T23:26:24.580617888Z 20/10/12 23:26:24 INFO SecurityManager: Changing view acls to: spark
2020-10-12T23:26:24.581465592Z 20/10/12 23:26:24 INFO SecurityManager: Changing modify acls to: spark
2020-10-12T23:26:24.583364011Z 20/10/12 23:26:24 INFO SecurityManager: Changing view acls groups to:
2020-10-12T23:26:24.583837749Z 20/10/12 23:26:24 INFO SecurityManager: Changing modify acls groups to:
2020-10-12T23:26:24.584703005Z 20/10/12 23:26:24 INFO SecurityManager: SecurityManager: authentication disabled; ui acls disabled; users  with view permissions: Set(spark); groups with view permissions: Set(); users  with modify permissions: Set(spark); groups with modify permissions: Set()
2020-10-12T23:26:24.913880578Z 20/10/12 23:26:24 INFO Utils: Successfully started service 'sparkWorker' on port 40001.
2020-10-12T23:26:25.084691474Z 20/10/12 23:26:25 INFO Worker: Starting Spark worker <IP_ADDRESS>:40001 with 1 cores, 6.6 GiB RAM
2020-10-12T23:26:25.089845121Z 20/10/12 23:26:25 INFO Worker: Running Spark version 3.0.1
2020-10-12T23:26:25.090382436Z 20/10/12 23:26:25 INFO Worker: Spark home: /opt/bitnami/spark
2020-10-12T23:26:25.107156574Z 20/10/12 23:26:25 INFO ResourceUtils: ==============================================================
2020-10-12T23:26:25.108372044Z 20/10/12 23:26:25 INFO ResourceUtils: Resources for spark.worker:
2020-10-12T23:26:25.108420995Z
2020-10-12T23:26:25.108773081Z 20/10/12 23:26:25 INFO ResourceUtils: ==============================================================
2020-10-12T23:26:25.233558835Z 20/10/12 23:26:25 INFO Utils: Successfully started service 'WorkerUI' on port 8081.
2020-10-12T23:26:25.268689284Z 20/10/12 23:26:25 INFO WorkerWebUI: Bound WorkerWebUI to <IP_ADDRESS>, and started at http://spark-worker-0.spark-headless.default.svc.cluster.local:8081
2020-10-12T23:26:25.274713863Z 20/10/12 23:26:25 INFO Worker: Connecting to master spark-master-svc:7077...
2020-10-12T23:26:25.37374162Z 20/10/12 23:26:25 INFO TransportClientFactory: Successfully created connection to spark-master-svc/<IP_ADDRESS>:7077 after 50 ms (0 ms spent in bootstraps)
2020-10-12T23:26:25.409149141Z 20/10/12 23:26:25 WARN TransportChannelHandler: Exception in connection from spark-master-svc/<IP_ADDRESS>:7077
2020-10-12T23:26:25.409174852Z java.io.IOException: Connection reset by peer
2020-10-12T23:26:25.409180555Z 	at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
2020-10-12T23:26:25.409185388Z 	at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
2020-10-12T23:26:25.409189732Z 	at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
2020-10-12T23:26:25.40919409Z 	at sun.nio.ch.IOUtil.read(IOUtil.java:192)
2020-10-12T23:26:25.409198553Z 	at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:377)
2020-10-12T23:26:25.409203093Z 	at io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:253)
2020-10-12T23:26:25.409207467Z 	at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1133)
2020-10-12T23:26:25.40921176Z 	at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:350)
2020-10-12T23:26:25.409216114Z 	at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:148)
2020-10-12T23:26:25.409220621Z 	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:714)
2020-10-12T23:26:25.409225304Z 	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650)
2020-10-12T23:26:25.409229816Z 	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576)
2020-10-12T23:26:25.409234265Z 	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
2020-10-12T23:26:25.409249603Z 	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
2020-10-12T23:26:25.409254598Z 	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
2020-10-12T23:26:25.409259072Z 	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
2020-10-12T23:26:25.409263625Z 	at java.lang.Thread.run(Thread.java:748)
2020-10-12T23:26:25.4102625Z 20/10/12 23:26:25 ERROR TransportResponseHandler: Still have 1 requests outstanding when connection from spark-master-svc/<IP_ADDRESS>:7077 is closed
2020-10-12T23:26:25.41756288Z 20/10/12 23:26:25 WARN Worker: Failed to connect to master spark-master-svc:7077
2020-10-12T23:26:25.417584108Z org.apache.spark.SparkException: Exception thrown in awaitResult:
2020-10-12T23:26:25.417588372Z 	at org.apache.spark.util.ThreadUtils$.awaitResult(ThreadUtils.scala:302)
2020-10-12T23:26:25.41759168Z 	at org.apache.spark.rpc.RpcTimeout.awaitResult(RpcTimeout.scala:75)
2020-10-12T23:26:25.417594879Z 	at org.apache.spark.rpc.RpcEnv.setupEndpointRefByURI(RpcEnv.scala:101)
2020-10-12T23:26:25.417597975Z 	at org.apache.spark.rpc.RpcEnv.setupEndpointRef(RpcEnv.scala:109)
2020-10-12T23:26:25.417601004Z 	at org.apache.spark.deploy.worker.Worker$$anon$1.run(Worker.scala:277)
2020-10-12T23:26:25.417604091Z 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
2020-10-12T23:26:25.417619978Z 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
2020-10-12T23:26:25.417624191Z 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
2020-10-12T23:26:25.417627353Z 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
2020-10-12T23:26:25.417630457Z 	at java.lang.Thread.run(Thread.java:748)
2020-10-12T23:26:25.4176334Z Caused by: java.io.IOException: Connection reset by peer
2020-10-12T23:26:25.41763646Z 	at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
2020-10-12T23:26:25.417639532Z 	at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
2020-10-12T23:26:25.417642551Z 	at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
2020-10-12T23:26:25.417645525Z 	at sun.nio.ch.IOUtil.read(IOUtil.java:192)
2020-10-12T23:26:25.417648478Z 	at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:377)
2020-10-12T23:26:25.417651484Z 	at io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:253)
2020-10-12T23:26:25.417654509Z 	at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1133)
2020-10-12T23:26:25.417666034Z 	at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:350)
2020-10-12T23:26:25.417669745Z 	at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:148)
2020-10-12T23:26:25.417680601Z 	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:714)
2020-10-12T23:26:25.417695032Z 	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650)
2020-10-12T23:26:25.417698886Z 	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576)
2020-10-12T23:26:25.417702075Z 	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
2020-10-12T23:26:25.417705177Z 	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
2020-10-12T23:26:25.417708344Z 	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
2020-10-12T23:26:25.417712263Z 	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
2020-10-12T23:26:25.417715465Z 	... 1 more
2020-10-12T23:26:33.28301265Z 20/10/12 23:26:33 INFO Worker: Retrying connection to master (attempt # 1)
2020-10-12T23:26:33.283675082Z 20/10/12 23:26:33 INFO Worker: Connecting to master spark-master-svc:7077...
2020-10-12T23:26:33.285029889Z 20/10/12 23:26:33 INFO TransportClientFactory: Found inactive connection to spark-master-svc/<IP_ADDRESS>:7077, creating a new one.
2020-10-12T23:26:33.287335156Z 20/10/12 23:26:33 INFO TransportClientFactory: Successfully created connection to spark-master-svc/<IP_ADDRESS>:7077 after 2 ms (0 ms spent in bootstraps)
2020-10-12T23:26:33.290964099Z 20/10/12 23:26:33 WARN TransportChannelHandler: Exception in connection from spark-master-svc/<IP_ADDRESS>:7077
2020-10-12T23:26:33.290989631Z java.io.IOException: Connection reset by peer

master envoy access logs:
2020-10-12T23:28:45.635604665Z [2020-10-12T23:28:40.007Z] "- - -" 0 UF,URX "-" "-" 0 0 7 - "-" "-" "-" "-" "<IP_ADDRESS>:7077" inbound|7077|cluster|spark-master-svc.default.svc.cluster.local - <IP_ADDRESS>:7077 <IP_ADDRESS>:40782 - -
2020-10-12T23:28:45.635677332Z [2020-10-12T23:28:45.289Z] "- - -" 0 UF,URX "-" "-" 0 0 1 - "-" "-" "-" "-" "<IP_ADDRESS>:7077" inbound|7077|cluster|spark-master-svc.default.svc.cluster.local - <IP_ADDRESS>:7077 <IP_ADDRESS>:34914 - -
2020-10-12T23:28:55.636260462Z [2020-10-12T23:28:45.989Z] "- - -" 0 UF,URX "-" "-" 0 0 1 - "-" "-" "-" "-" "<IP_ADDRESS>:7077" inbound|7077|cluster|spark-master-svc.default.svc.cluster.local - <IP_ADDRESS>:7077 <IP_ADDRESS>:40860 - -
2020-10-12T23:28:55.636330126Z [2020-10-12T23:28:52.000Z] "- - -" 0 UF,URX "-" "-" 0 0 1 - "-" "-" "-" "-" "<IP_ADDRESS>:7077" inbound|7077|cluster|spark-master-svc.default.svc.cluster.local - <IP_ADDRESS>:7077 <IP_ADDRESS>:40924 - -
2020-10-12T23:29:05.636224878Z [2020-10-12T23:28:57.980Z] "- - -" 0 UF,URX "-" "-" 0 0 0 - "-" "-" "-" "-" "<IP_ADDRESS>:7077" inbound|7077|cluster|spark-master-svc.default.svc.cluster.local - <IP_ADDRESS>:7077 <IP_ADDRESS>:40992 - -
2020-10-12T23:29:35.637224934Z [2020-10-12T23:29:31.302Z] "- - -" 0 UF,URX "-" "-" 0 0 1 - "-" "-" "-" "-" "<IP_ADDRESS>:7077" inbound|7077|cluster|spark-master-svc.default.svc.cluster.local - <IP_ADDRESS>:7077 <IP_ADDRESS>:35422 - -
2020-10-12T23:29:35.637295762Z [2020-10-12T23:29:33.001Z] "- - -" 0 UF,URX "-" "-" 0 0 1 - "-" "-" "-" "-" "<IP_ADDRESS>:7077" inbound|7077|cluster|spark-master-svc.default.svc.cluster.local - <IP_ADDRESS>:7077 <IP_ADDRESS>:41372 - -

master app logs:
2020-10-12T23:19:22.133670797Z  23:19:22.13
2020-10-12T23:19:22.134625845Z  23:19:22.13 Welcome to the Bitnami spark container
2020-10-12T23:19:22.135525431Z  23:19:22.13 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-spark
2020-10-12T23:19:22.136876464Z  23:19:22.13 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-spark/issues
2020-10-12T23:19:22.140935814Z  23:19:22.13
2020-10-12T23:19:22.144890379Z  23:19:22.14 INFO  ==> ** Starting Spark setup **
2020-10-12T23:19:22.156922639Z  23:19:22.15 INFO  ==> Generating Spark configuration file...
2020-10-12T23:19:22.160977024Z  23:19:22.16 INFO  ==> ** Spark setup finished! **
2020-10-12T23:19:22.160992687Z
2020-10-12T23:19:22.168267251Z  23:19:22.16 INFO  ==> ** Starting Spark in master mode **
2020-10-12T23:19:22.181434131Z starting org.apache.spark.deploy.master.Master, logging to /opt/bitnami/spark/logs/spark--org.apache.spark.deploy.master.Master-1-spark-master-0.out
2020-10-12T23:19:22.249463647Z Spark Command: /opt/bitnami/java/bin/java -cp /opt/bitnami/spark/conf/:/opt/bitnami/spark/jars/* -Xmx1g org.apache.spark.deploy.master.Master --host spark-master-0.spark-headless.default.svc.cluster.local --port 7077 --webui-port 8080
2020-10-12T23:19:22.249484593Z ========================================
2020-10-12T23:19:22.843147562Z Using Spark's default log4j profile: org/apache/spark/log4j-defaults.properties
2020-10-12T23:19:22.853526449Z 20/10/12 23:19:22 INFO Master: Started daemon with process name<EMAIL_ADDRESS>2020-10-12T23:19:22.868808815Z 20/10/12 23:19:22 INFO SignalUtils: Registered signal handler for TERM
2020-10-12T23:19:22.869902188Z 20/10/12 23:19:22 INFO SignalUtils: Registered signal handler for HUP
2020-10-12T23:19:22.870005644Z 20/10/12 23:19:22 INFO SignalUtils: Registered signal handler for INT
2020-10-12T23:19:23.159750646Z 20/10/12 23:19:23 WARN NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
2020-10-12T23:19:23.207397422Z 20/10/12 23:19:23 INFO SecurityManager: Changing view acls to: spark
2020-10-12T23:19:23.20777644Z 20/10/12 23:19:23 INFO SecurityManager: Changing modify acls to: spark
2020-10-12T23:19:23.208152724Z 20/10/12 23:19:23 INFO SecurityManager: Changing view acls groups to:
2020-10-12T23:19:23.20855362Z 20/10/12 23:19:23 INFO SecurityManager: Changing modify acls groups to:
2020-10-12T23:19:23.208993032Z 20/10/12 23:19:23 INFO SecurityManager: SecurityManager: authentication disabled; ui acls disabled; users  with view permissions: Set(spark); groups with view permissions: Set(); users  with modify permissions: Set(spark); groups with modify permissions: Set()
2020-10-12T23:19:23.513487975Z 20/10/12 23:19:23 INFO Utils: Successfully started service 'sparkMaster' on port 7077.
2020-10-12T23:19:23.53576886Z 20/10/12 23:19:23 INFO Master: Starting Spark master at spark://spark-master-0.spark-headless.default.svc.cluster.local:7077
2020-10-12T23:19:23.540343238Z 20/10/12 23:19:23 INFO Master: Running Spark version 3.0.1
2020-10-12T23:19:23.672044996Z 20/10/12 23:19:23 INFO Utils: Successfully started service 'MasterUI' on port 8080.
2020-10-12T23:19:23.719952202Z 20/10/12 23:19:23 INFO MasterWebUI: Bound MasterWebUI to <IP_ADDRESS>, and started at http://spark-master-0.spark-headless.default.svc.cluster.local:8080
2020-10-12T23:19:23.869948708Z 20/10/12 23:19:23 INFO Master: I have been elected leader! New state: ALIVE

Steps tested:

tried to change port name on spark-master-svc (http, http2, grpc, tcp...) nothing worked.
disabled mTLS on namespace and created DestinationRule to service not to use mTLS (did not work)
Without sidecar injection everything works fine.

Note: I am running this helm chart with default values.
Please help to solve this issue, or suggest any workaround for it. I need it ASAP
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
Workers should communicate and register with master.
Steps to reproduce the bug
Version (include the output of istioctl version --remote and kubectl version --short and helm version if you used Helm)\
istioctl version --remote
client version: 1.7.3
control plane version: 1.7.3
data plane version: 1.7.3 (4 proxies)

kubectl version --short
Client Version: v1.19.2
Server Version: v1.18.3

helm version
version.BuildInfo{Version:"v3.3.4", GitCommit:"a61ce5633af99708171414353ed49547cf05013d", GitTreeState:"clean", GoVersion:"go1.14.9"}

How was Istio installed?
default profile
Environment where bug was observed (cloud vendor, OS, etc)
GKE, minikube
cluster_state_archive.zip

Any help or response please

I have the same issue. Any comments on the above?

I ran into the same issue and for now I have bypassed redirection by adding the following annotation to the master
traffic.sidecar.istio.io/excludeInboundPorts: "7077"

And the following annotation to the workers
traffic.sidecar.istio.io/excludeOutboundPorts: "7077"

@auswells Yes but in that case we cant get telemetry data in kiali because the traffic is never logged. :(

I'm trying to figure out this same thing. I honestly don't grok why setting it to tcp wouldn't fix it--shouldn't it then be just passing the traffic verbatim and be pretty much compatible with any tcp protocol?

After looking into this further, it seems it's related to the fact that the spark master doesn't listen on localhost, but Istio requires it. There was recently a PR (#28178) that makes the sidecar configurable in such a way that this can work, though it wasn't included in either of the most recent releases (1.7.5 or 1.8.0) that were released after the commit.
Is there a rough timeline for when this fix will make into a released version of Istio (or expected version)?

After looking into this further, it seems it's related to the fact that the spark master doesn't listen on localhost, but Istio requires it. There was recently a PR (#28178) that makes the sidecar configurable in such a way that this can work, though it wasn't included in either of the most recent releases (1.7.5 or 1.8.0) that were released after the commit.
Is there a rough timeline for when this fix will make into a released version of Istio (or expected version)?

Can Spark masters be configured to listen on localhost? That might be simpler.

After looking into this further, it seems it's related to the fact that the spark master doesn't listen on localhost, but Istio requires it. There was recently a PR (#28178) that makes the sidecar configurable in such a way that this can work, though it wasn't included in either of the most recent releases (1.7.5 or 1.8.0) that were released after the commit.
Is there a rough timeline for when this fix will make into a released version of Istio (or expected version)?

Can Spark masters be configured to listen on localhost? That might be simpler.

Confirmed that the Bitnami Spark installation (or any Spark standalone setup) will work in Istio 1.8.1 just fine if you set SPARK_MASTER_HOST to localhost. Workers are able to register and jobs are distributed.
master:
    extraEnvVars:
     - name: SPARK_MASTER_HOST
       value: "<IP_ADDRESS>"

Confirmed that the Bitnami Spark installation (or any Spark standalone setup) will work in Istio 1.8.1 just fine if you set SPARK_MASTER_HOST to localhost. Workers are able to register and jobs are distributed.
master:
    extraEnvVars:
     - name: SPARK_MASTER_HOST
       value: "<IP_ADDRESS>"

If the issue is just the bind, this will work out of the box in a future Istio version. See https://docs.google.com/document/d/1j-5_XpeMTnT9mV_8dbSOeU7rfH-5YNtN_JJFZ2mmQ_w/edit# for info

This should be fixed by #30226. If you still see issues on master (https://github.com/istio/istio/wiki/Dev Builds) please reopen!

Thanks I've followed above comments and added the env variable. Post that, the spark streaming job submitted in cluster/client mode fails exactly after an hour of running. The application is getting into "Finished" status. I have the latest istio 1.9 installed with spark 2.4.6
Logs:
2021-05-19 06:09:06,975 [dispatcher-event-loop-1] WARN  (Logging.scala:66) - Connection to <IP_ADDRESS>:7077 failed; waiting for master to reconnect...
2021-05-19 06:09:06,977 [dispatcher-event-loop-1] WARN  (Logging.scala:66) - Disconnected from Spark cluster! Waiting for reconnection...
2021-05-19 06:09:06,984 [SIGTERM handler] ERROR (SignalUtils.scala:43) - RECEIVED SIGNAL TERM
2021-05-19 06:09:07,618 [dispatcher-event-loop-0] ERROR (Logging.scala:70) - Lost executor 2 on spark-worker-1.spark-headless.nuance-preprod-neap.svc.cluster.local: Remote RPC client disassociated. Likely due to containers exceeding thresholds, or network issues. Check driver logs for WARN messages.
2021-05-19 06:09:07,623 [dispatcher-event-loop-0] ERROR (Logging.scala:70) - Lost executor 1 on spark-worker-2.spark-headless.nuance-preprod-neap.svc.cluster.local: Remote RPC client disassociated. Likely due to containers exceeding thresholds, or network issues. Check driver logs for WARN messages.
2021-05-19 06:09:07,623 [dispatcher-event-loop-0] ERROR (Logging.scala:70) - Lost executor 0 on spark-worker-0.spark-headless.nuance-preprod-neap.svc.cluster.local: Remote RPC client disassociated. Likely due to containers exceeding thresholds, or network issues. Check driver logs for WARN messages.
2021-05-19 06:09:07,636 [dispatcher-event-loop-0] WARN  (Logging.scala:66) - No more replicas available for rdd_41_30 !
Any suggestions would be greatly appreciated.

2021-05-19 06:09:06,977 [dispatcher-event-loop-1] WARN (Logging.scala:66) - Disconnected from Spark cluster! Waiting for reconnection...

These suggestions are guesses but may be worth a try:

Increase spark.network.timeout or other timeouts. Also have more retries. If you are using the default Dockerfile provided in spark distribution, you can add something like this(in entrypoint.sh):      # Execute the container CMD under tini for better hygiene
      retries=5
      if [ -n "$SPARK_ENVOY_RETRIES" ]; then
          retries=$SPARK_ENVOY_RETRIES
      fi
      while [[ ${retries} -ge 0 ]]
      do
        /usr/bin/tini -s -- "${CMD[@]}" && break
        ((retries-=1))
        echo "Failed to start ${SPARK_K8S_CMD}. ${retries} reties left"
        sleep 15
      done

Destination rules that can be tweaked.
https://istio.io/latest/docs/reference/config/networking/destination-rule/#ConnectionPoolSettings

Thanks I've followed above comments and added the env variable. Post that, the spark streaming job submitted in cluster/client mode fails exactly after an hour of running. The application is getting into "Finished" status. I have the latest istio 1.9 installed with spark 2.4.6
...
Any suggestions would be greatly appreciated.

I encountered something similar to do with Istio terminating long running connections after an hour. I found this StackOverflow question helpful in that it directed me to this answer about adding an EnvoyFilters for the inbound and outbound connections.


vcpkg freeze after sucessfully building ffmpeg

Platform: Windows
Package: ffmpeg:x64-windows & ffmpeg:x86-windows
Vcpkg version: 2018.11.23-nohash
Description:
I was trying to install ffmpeg (4.1.0) with vcpkg on Windows 10. The build seems to succeed, but after that vcpkg freezes and won't quit. I can still use ffmpeg after I force it to quit. While this is not quite a problem on my local machine, the CI builds will be blocked by this and won't continue.
Command Line:
vcpkg install ffmpeg:x86-windows
Command Line Output:
  The following packages will be built and installed:
      ffmpeg[core]:x86-windows
  Starting package 1/1: ffmpeg:x86-windows
  Building package ffmpeg[core]:x86-windows...
  A suitable version of git was not found (required v2.20.0). Downloading portable git v2.20.0...
  Downloading git...
    https://github.com/git-for-windows/git/releases/download/v2.20.0.windows.1/PortableGit-2.20.0-32-bit.7z.exe -> C:\Tools\vcpkg\downloads\PortableGit-2.20.0-32-bit.7z.exe
  Extracting git...
  A suitable version of 7zip was not found (required v18.1.0). Downloading portable 7zip v18.1.0...
  Downloading 7zip...
    https://www.nuget.org/api/v2/package/7-Zip.CommandLine/18.1.0 -> C:\Tools\vcpkg\downloads\7-zip.commandline.18.1.0.nupkg
  Extracting 7zip...
  -- Downloading http://ffmpeg.org/releases/ffmpeg-4.1.tar.bz2...
  -- Extracting source C:/Tools/vcpkg/downloads/ffmpeg-4.1.tar.bz2
  -- Applying patch C:/Tools/vcpkg/ports/ffmpeg/create-lib-libraries.patch
  -- Applying patch C:/Tools/vcpkg/ports/ffmpeg/detect-openssl.patch
  -- Applying patch failed. This is expected if this patch was previously applied.
  -- Applying patch C:/Tools/vcpkg/ports/ffmpeg/configure_opencv.patch
  -- Applying patch failed. This is expected if this patch was previously applied.
  -- Downloading https://www.tortall.net/projects/yasm/snapshots/v<IP_ADDRESS>.g1962/yasm-<IP_ADDRESS>.g1962.exe...
  -- Installing: C:/Tools/vcpkg/downloads/tools/yasm/<IP_ADDRESS>/yasm.exe
  -- Acquiring MSYS2...
  -- Downloading http://repo.msys2.org/distrib/x86_64/msys2-base-x86_64-20181211.tar.xz...
  gpg: /etc/pacman.d/gnupg/trustdb.gpg: trustdb created
  gpg: no ultimately trusted keys found
  gpg: starting migration from earlier GnuPG versions
  gpg: porting secret keys from '/etc/pacman.d/gnupg/secring.gpg' to gpg-agent
  gpg: migration succeeded
  gpg: Generating pacman keyring master key...
  gpg: key A39EF6BBA7C712F1 marked as ultimately trusted
  gpg: directory '/etc/pacman.d/gnupg/openpgp-revocs.d' created
  gpg: revocation certificate stored as '/etc/pacman.d/gnupg/openpgp-revocs.d/612A00C94159FBB38363F9E4A39EF6BBA7C712F1.rev'
  gpg: Done
  ==> Updating trust database...
  gpg: marginals needed: 3  completes needed: 1  trust model: pgp
  gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
  ==> Appending keys from msys2.gpg...
  ==> Locally signing trusted keys in keyring...
    -> Locally signing key D55E7A6D7CE9BA1587C0ACACF40D263ECA25678A...
    -> Locally signing key 123D4D51A1793859C2BE916BBBE514E53E0D0813...
    -> Locally signing key B91BCF3303284BF90CC043CA9F418C233E652008...
    -> Locally signing key 9DD0D4217D75A33B896159E6DA7EF2ABAEEA755C...
  ==> Importing owner trust values...
  gpg: setting ownertrust to 4
  gpg: setting ownertrust to 4
  gpg: setting ownertrust to 4
  gpg: inserting ownertrust of 4
  ==> Updating trust database...
  gpg: marginals needed: 3  completes needed: 1  trust model: pgp
  gpg: depth: 0  valid:   1  signed:   4  trust: 0-, 0q, 0n, 0m, 0f, 1u
  gpg: depth: 1  valid:   4  signed:   3  trust: 0-, 0q, 0n, 4m, 0f, 0u
  gpg: depth: 2  valid:   3  signed:   0  trust: 3-, 0q, 0n, 0m, 0f, 0u
  :: Synchronizing package databases...
  downloading mingw32.db...
  downloading mingw32.db.sig...
  downloading mingw64.db...
  downloading mingw64.db.sig...
  downloading msys.db...
  downloading msys.db.sig...
  :: Starting core system upgrade...
  resolving dependencies...
EXEC : warning : terminate other MSYS2 programs before proceeding [C:\projects\igme750-dsengine\src\DSEngine\DSEngineFramework\DSEngineFramework.vcxproj]
  looking for conflicting packages...

  Packages (2) filesystem-2018.12-1  pacman-5.1.2-2

  Total Download Size:   14.34 MiB
  Total Installed Size:  46.14 MiB
  Net Upgrade Size:       1.13 MiB

  :: Proceed with installation?
  :: Processing package changes...
  upgrading filesystem...
  upgrading pacman...
EXEC : warning : terminate MSYS2 without returning to shell and check for updates again [C:\projects\igme750-dsengine\src\DSEngine\DSEngineFramework\DSEngineFramework.vcxproj]

  -- Acquiring MSYS2... OK
  -- Acquiring MSYS Packages...
  -- Acquiring MSYS Packages... OK
  -- Building Options: --enable-asm --enable-yasm --disable-doc --enable-debug --disable-ffmpeg --enable-runtime-cpudetect --disable-openssl --disable-ffplay --disable-ffprobe --disable-libx264 --disable-opencl --disable-lzma --extra-cflags=-DHAVE_UNISTD_H=0 --disable-static --enable-shared
  -- Building ffmpeg for Release
  -- Building ffmpeg for Debug
  -- Generating C:\Tools\vcpkg\packages\ffmpeg_x86-windows\debug\lib\avcodec.lib
  -- Generating C:\Tools\vcpkg\packages\ffmpeg_x86-windows\debug\lib\avdevice.lib
  -- Generating C:\Tools\vcpkg\packages\ffmpeg_x86-windows\debug\lib\avfilter.lib
  -- Generating C:\Tools\vcpkg\packages\ffmpeg_x86-windows\debug\lib\avformat.lib
  -- Generating C:\Tools\vcpkg\packages\ffmpeg_x86-windows\debug\lib\avutil.lib
  -- Generating C:\Tools\vcpkg\packages\ffmpeg_x86-windows\debug\lib\swresample.lib
  -- Generating C:\Tools\vcpkg\packages\ffmpeg_x86-windows\debug\lib\swscale.lib
  -- Generating C:\Tools\vcpkg\packages\ffmpeg_x86-windows\lib\avcodec.lib
  -- Generating C:\Tools\vcpkg\packages\ffmpeg_x86-windows\lib\avdevice.lib
  -- Generating C:\Tools\vcpkg\packages\ffmpeg_x86-windows\lib\avfilter.lib
  -- Generating C:\Tools\vcpkg\packages\ffmpeg_x86-windows\lib\avformat.lib
  -- Generating C:\Tools\vcpkg\packages\ffmpeg_x86-windows\lib\avutil.lib
  -- Generating C:\Tools\vcpkg\packages\ffmpeg_x86-windows\lib\swresample.lib
  -- Generating C:\Tools\vcpkg\packages\ffmpeg_x86-windows\lib\swscale.lib
  -- Performing post-build validation
  -- Performing post-build validation done
  Building package ffmpeg[core]:x86-windows... done
  Installing package ffmpeg[core]:x86-windows...
  Installing package ffmpeg[core]:x86-windows... done
  Elapsed time for package ffmpeg:x86-windows: 32.08 min

  Total elapsed time: 32.08 min

After that vcpkg freezes. The build was running for two hours when I copied the log.

I'm also hitting this. I've been trying to track it down for a couple days now. It happens with both upstream, and my own trimmed down ffmpeg port. Once I've isolated the change I'll report more. You can sorta follow my (very messy) diagnosis so far at: https://github.com/CorsixTH/CorsixTH/pull/1515

Weirdly, even though the problem only happens when building ffmpeg, it still happens when reverting the ffmpeg port to a known good version (while keeping the rest of vcpkg on the latest version). This (combined with the behaviour of just freezing) makes the issue rather hard to diagnose.

Weirdly, even though the problem only happens when building ffmpeg, it still happens when reverting the ffmpeg port to a known good version (while keeping the rest of vcpkg on the latest version). This (combined with the behaviour of just freezing) makes the issue rather hard to diagnose.

Thank you for this! I already gave up since this is beyond my knowledge.
Also, for your information, if this is helpful, my Appveyor CI build will always freeze, but not my Azure Pipelines, so I stopped using Appveyor temporarily. You can check my Azure Pipelines log here.

Some ideas - let me know and I'll delete this comment if I'm way off the mark.

Try the build again on AppVeyor and log into the build box to debug via https://www.appveyor.com/docs/how-to/rdp-to-build-worker/

Change the build config temporarily to make it build the bare minimum ffmpeg to see if the freeze is resolved, or at least make the build much faster to debug

@shurunxuan are you able to share your appveyor.yml or any scripts you're using? I'd like to replicate the build and see if it freezes for me as well.

@voltagex Sure.
version: 1.0.{build}
image: Visual Studio 2017
configuration:
  - Debug
  - Release
platform:
  - x86
  - x64
before_build:
  - nuget restore src/DSEngine/DSEngine.sln
install:
  - cd C:\Tools\vcpkg
  - git pull
  - .\bootstrap-vcpkg.bat
  - cd %APPVEYOR_BUILD_FOLDER%
  - vcpkg integrate install
  - vcpkg update
  - vcpkg upgrade --no-dry-run
  - cmd: if "%platform%"=="Win32" set VCPKG_ARCH=x86-windows
  - cmd: if "%platform%"=="x86"   set VCPKG_ARCH=x86-windows
  - cmd: if "%platform%"=="x64"   set VCPKG_ARCH=x64-windows
  - vcpkg install boost:%VCPKG_ARCH%
  - vcpkg install ffmpeg:%VCPKG_ARCH%
build:
  project: src/DSEngine/DSEngine.sln
  verbosity: minimal
cache: c:\tools\vcpkg\installed\

I've switched my appveyor to just cloning vcpkg, installing, and building ffmpeg in a powershell script. With my own minimal ffmpeg that means I can reproduce in ~7min, but for bisecting I'd rather just use the the upstream port.
As far as RDPing into Appveyor, I tried that but I didn't see anything interesting. I saved a dump from process explorer while it was stuck. Nothing stands out to me, but maybe someone here sees something? If there's something else in particular I should look at I'll run RDP again; otherwise I'll continue with my bisect.

As the TheCycoOne points out msys2 change, appears to introduce gpg 2.1 which launches gpg-agent daemon process. The appveyor builds appear to be lingering awaiting that process to die. Our script for CorsixTH, I altered with a Stop-Process -Force -Name "gpg-agent" for a quick test just before it exits and the process continued as expected.
Though running locally I didn't see the same as @shurunxuan.


Updates For Issue #6

@datavorous Sorry took me a bit of time, here are the list of the following updates i did.

Added Rate Limit Handling
Added Error Handling
Added Logging
Added More Ways to Export Results
Fixed And Updates Documentation
Added Unit Tests for YARS.py and Utils.py

Tanks to @CoolCat467 for user agent rotation :)

Why did you delete the pre-commit config file?

@CoolCat467 This is a mistake from my end, I reviewed the pr in a haste.
I was thinking about shifting from poetry to uv for dependency management.
If you would like to resolve the conflicts and discuss further please join this discussion server.
Thank you for understanding.