FFmpeg not found even when installed.

Hello,
I've been trying to test the new feature you've implemented (and customizing it a bit for a different purpose [fixing the Reddit-hosted videos being downloaded with no audio]), but it appears that it doesn't want to work for me because it cannot locate FFmpeg. Tried it on Windows and Linux (EndeavourOS), but it didn't work anywhere.
On Windows 10, it was installed by extracting FFmpeg's files somewhere on the disk and pointing them out in the Environment Variables (PATH).
On Linux (EndeavourOS), it was installed through the package manager (sudo pacman -S ffmpeg, but more or less just updated because it comes pre-installed).
On both systems, I ran npm install ffmpeg at the root directory of where I extracted the program's files.
Where should FFmpeg be installed?

Closing this issue, my script writing skills are awful. The feature works almost OK, videos are downloaded with a low quality preset.
Can I make a repo with my code edits available for everyone, while crediting the original? Will be distributed with the similar license (MIT License)


enhancement lazy-open necessary partitions when load

Previously, when loading data, NodeChannel would open all tablets in all partitions when opening. This could cause a large number of useless tablets to be opened and empty rowsets to be created. In this commit, we only open tablets in a partition when they are actually written.
Test Result (reuse regression case test_datev2_partition):
create table with 8 partitions, 10 buckets per partition:
        CREATE TABLE `${tblName1}` (
        `TIME_STAMP` datev2 NOT NULL COMMENT '采集日期'
        ) ENGINE=OLAP
        DUPLICATE KEY(`TIME_STAMP`)
        COMMENT 'OLAP'
        PARTITION BY RANGE(`TIME_STAMP`)
        (PARTITION p20221214 VALUES [('2022-12-14'), ('2022-12-15')),
        PARTITION p20221215 VALUES [('2022-12-15'), ('2022-12-16')),
        PARTITION p20221216 VALUES [('2022-12-16'), ('2022-12-17')),
        PARTITION p20221217 VALUES [('2022-12-17'), ('2022-12-18')),
        PARTITION p20221218 VALUES [('2022-12-18'), ('2022-12-19')),
        PARTITION p20221219 VALUES [('2022-12-19'), ('2022-12-20')),
        PARTITION p20221220 VALUES [('2022-12-20'), ('2022-12-21')),
        PARTITION p20221221 VALUES [('2022-12-21'), ('2022-12-22')))
        DISTRIBUTED BY HASH(`TIME_STAMP`) BUCKETS 10
        PROPERTIES (
        "replication_allocation" = "tag.location.default: 1"
        );

Then load data into 7 partitions:
insert into ${tblName1} values ('2022-12-14'), ('2022-12-15'), ('2022-12-16'), ('2022-12-17'), ('2022-12-18'), ('2022-12-19'), ('2022-12-20')

We get only 7x10 writer opened instead of 8x10, which proves it is effective:
I0413 16:11:22.265318 1381484 tablets_channel.cpp:283] OOXXOO: _s_tablet_writer_count=10
I0413 16:11:22.265527 1381484 tablets_channel.cpp:283] OOXXOO: _s_tablet_writer_count=20
I0413 16:11:22.265574 1381484 tablets_channel.cpp:283] OOXXOO: _s_tablet_writer_count=30
I0413 16:11:22.265642 1381484 tablets_channel.cpp:283] OOXXOO: _s_tablet_writer_count=40
I0413 16:11:22.265681 1381484 tablets_channel.cpp:283] OOXXOO: _s_tablet_writer_count=50
I0413 16:11:22.265719 1381484 tablets_channel.cpp:283] OOXXOO: _s_tablet_writer_count=60
I0413 16:11:22.265754 1381484 tablets_channel.cpp:283] OOXXOO: _s_tablet_writer_count=70
I0413 16:11:22.270346 1381484 tablets_channel.cpp:48] OOXXOO: _s_tablet_writer_count=0

Proposed changes
Issue Number: close #18092
Problem summary
Describe your changes.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

very very great PR...

Already merged in https://github.com/apache/doris/pull/18874


added timestamps to metadata

Create and update timestamps were added to the dataset message in the metadata proto.
Closes #626.

Can we close in favor of https://github.com/ga4gh/schemas/pull/690 ? It implements the same timestamps across the board and uses the much less painful created and updated field names. Sorry for the confusion!

I agree. Close this and the pull requests in compliance and server.

+1 for https://github.com/ga4gh/schemas/pull/690

Also close 682, 568, and 685.

Closing this in favour of #690.


Moving TopQueries to TrendsOverview, only show Queries for the US

Only showing TopQueries when selected country is US. Moving the component back to TrendsOverview, as this allows simpler country-specific selection.
Fixing small error with Query import.

Component still looking good from my end after these changes! 👍


Add Magento 2 data image

Fixed comments and added an image-builder.sh script for building. @punkstar, could you give this another look?


Add custom isError to AuthUI Components passwordField, EmailField

General Info

[X] I installed the latest version of Supabase Kt
[X] I checked for similar feature requests

Feature request
The isError of the fields should be available to set it from outside without rules to display an error.
Usecase
E.g. When the login fails because the password was wrong I want to set it on error state

Yea, we probably can just add a isError parameter defaulting to null (so by default its handled automatically)


nixStatic: build with withAWS option

In the current version, the nixStatic package is built without aws support.
After looking at the code, I realized that there is a withAWS option, which is disabled for static builds:
https://github.com/NixOS/nixpkgs/blob/368b2d71b474364c86a67f09b5aeb8e56ebbbeb3/pkgs/tools/package-management/nix/common.nix#L75
Tell me, would it be difficult to enable this option?

I'm assuming the parameter is set that way for a reason. You should be able to do something like this:
# default.nix
pkgs.nixStatic.override { withAWS = true; }

I'm assuming the parameter is set that way for a reason. You should be able to do something like this:
# default.nix
pkgs.nixStatic.override { withAWS = true; }

Thanks for the answer.
But if you do this, the assembly breaks with errors like:
(.text+0x2e1): undefined reference to `aws_channel_slot_upstream_message_overhead'
/nix/store/w9dk8id4zmvmwqy42dyqc2k56nf14qvb-x86_64-unknown-linux-musl-binutils-2.40/bin/x86_64-unknown-linux-musl-ld: /nix/store/fh84xs2cq9ss5xwrly1dim6w6xwpsr71-aws-crt-cpp-static-x86_64-unknown-linux-musl-0.20.3/lib/libaws-crt-cpp.a(ChannelHandler.cpp.o): in function `Aws::Crt::Io::ChannelHandler::ScheduleTask(std::function<void (Aws::Crt::Io::TaskStatus)>&&)':
(.text+0x549): undefined reference to `aws_channel_schedule_task_now'

full.log

Pinging maintainers @edolstra, @lovesegfault, and @Artturin.


[1755] Add prod section to database.yml

Context
This is for the new environment that we are deploying tonight.
Checklist

[ ] Make sure all information from the Trello card is in here
[ ] Attach to Trello card
[ ] Rebased master
[ ] Cleaned commit history
[ ] Tested by running locally

 Deploy production environment


Added new Math functions

I added the log2, hypot, cbrt, gamma, lgamma, erf, erfc functions. I wrote some tests but that could be followed up

@ThakeeNathees I don't know why the test keeps failing. It worked fine on my machine
assert(cbrt(27) == 3)

Hi @victorakpan-dev It's been a long time and the codebase become unmaintained (I've explained here: https://github.com/ThakeeNathees/pocketlang/issues/168#issuecomment-1083429850) anyways thanks for the implementations.


Swagger doc fixes

What does this PR do?
Fixes #(issue_number)
Which TC components are affected by this PR?

[X] Documentation
[ ] Grove
[ ] Traffic Analytics
[ ] Traffic Monitor
[ ] Traffic Ops
[ ] Traffic Ops ORT
[ ] Traffic Portal
[ ] Traffic Router
[ ] Traffic Stats
[ ] Traffic Vault
[ ] Other _________

What is the best way to verify this PR?
$ cd traffic_ops/traffic_ops_golang/swaggerdocs/v13
$ docker-compose up
Check all that apply

[ ] This PR includes tests
[X] This PR includes documentation updates
[ ] This PR includes an update to CHANGELOG.md
[ ] This PR includes all required license headers
[ ] This PR includes a database migration (ensure that migration sequence is correct)
[ ] This PR fixes a serious security flaw. Read more: www.apache.org/security

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/2392/
Test FAILed.


Multi line view booleanfix

Q
A

Bug fix?
yes?

New sample?
no?

Related issues?
None

What's in this Pull Request?
The JSON for 'hideSelection' and 'hideColumnHeader' were using "String" values for what I believe should be actual Boolean. Updated the properties to use actual Boolean. Simple update hopefully. :)
Thanks for your contribution! Sharing is caring.

Great catch, thanks!


event to indicate end of file?

is there an event to denote end of file, like '.on()'

.on('finish', function(){
// do stuff
});
Thanks


[Feature request] Add favorites countries option for country selector

I would like to define some favorites countries so that my application users can find the mostly used countries in top of the list.
Already started to implements that on my own.
Does this sound like a valuable feature for you ?

You can already do that with the countries  property of the country selector navigator

From what I understand, the countries property give the available countries. What I mean is to let all the countries available but specify those that are mostly used to be displayed on top of others.

IE: you sort the array of countries given to the navigator. That is why it is here in the first place, it gives more freedom than a favorite property. You can sort, remove some countries etc.

I had not thought of this use, although less practical IMHO ;)

Yes you cannot display a line or any visual delimitation between countries. I actually hesitated between the two implementations when implementing but decided to let the user specify the array directly as it gives more freedom (I had a feature request asking for only a subset of countries).
Two options I see:

In the CountrySelector widget have a favorite countries property, that would display the favorites at the top with a delimitation then all countries.
a builder ?

I have already implemented your first idea (not finished properly). The screenshot is a running example on my current real app. Will push the code ASAP so you can see the code ;)

Is the delimiter color the default one ? It seems a bit light, if it's not the default could you match it with the search bar ?

You can check this branch for the changes : https://github.com/emri99/phone_form_field/tree/add-favorites-countries

Is the delimiter color the default one ? It seems a bit light, if it's not the default could you match it with the search bar ?

The screenshot is extracted from my real app which uses custom theme values.
I did not change anything explicitly in the code, so it should not be a problem.

The top padding above the favorites seems to be off as well

I did not change the padding neither.
I have make myself the same remark on the original code.
My commit doesn't fix this point, this may be changed in another commit.

Yeah a pull request would be appreciated

PR created https://github.com/cedvdb/phone_form_field/pull/26


[Question] Would this be a good candidate for an RTS game? EOM

I am making a game called density wars: https://www.youtube.com/watch?v=i7tdJpf6Pnc
using babylonjs.
I've been delaying for a while and want to get the game up and running.
https://github.com/QuantumInformation/Density-Wars

Yes! You might want to go with interpolation sync method rather than extrapolation in this use case.  Also,  I saw that you're using Babylon js. We have experience working with  three js,  but as Incheon is game and renderer agnostic,  this means you can hook into your own Babylon  renderer. It's a bit more work but doable.
You're welcome join us on slack to discuss this
http://slack.incheon.gg/


add an option to disable SSL certificate verification in GitHub webhooks

When a system property jenkins.ghprb.webhook.insecure is set to true,
GitHub webhooks created by GHPRB will have SSL certificate verification
disabled. This is useful in case the Jenkins server is available via HTTPS
with a self-signed or corporate CA issued certificate.
Resolves #694

Build failed because

You have 2 Checkstyle violations.

Yea, I've seen that in the Windows build and it's weird:
[INFO] There are 2 errors reported by Checkstyle 6.7 with C:\Jenkins\workspace\Plugins_ghprb-plugin_PR-695-77EFRTEZWVPGRJ62PGBABFBIUAFKXTQJLPXGSHCN2DWFRCCKW6TA/checkstyle.xml ruleset.
[ERROR] src\main\java\org\jenkinsci\plugins\ghprb\jobdsl\GhprbCancelBuildsOnUpdateContext.java:[0] (misc) NewlineAtEndOfFile: File does not end with a newline.
[ERROR] src\main\java\org\jenkinsci\plugins\ghprb\jobdsl\GhprbExtensionContext.java:[0] (misc) NewlineAtEndOfFile: File does not end with a newline.

In my clone on my Linux machine, the GhprbExtensionContext.java file does end with a newline, and the GhprbCancelBuildsOnUpdateContext.java file doesn't even exist.

This would be useful.  I have use a GitHub Enterprise deployment with a self-signed certificate and am unable to import certificate chains into it.  I'd like to disable this by default.

Right now I’m traveling for Jenkins World.  I have not forgotten about this patch (I promise!).  I’ll take a look at this again this upcoming week.

I’m going to close and re-open to retrigger the CI build.

I simply can't make sense of those Checkstyle errors. Moreover, I didn't even touch any of those files in this PR.

Yeah, I reached out to the CI owners to see if they can make sense.  I agree it’s not related to anything you did.

Thank you very much!


Option to only build certain dependencies

Expected Behavior
There sould be an posibility to build only certen Dependencies and not onyl all
Current Behavior
it is only possible to ignore some dependencies in dev mode
Context

UI5 Module Version (output of ui5 --version when using the CLI): 1.2.1

Affected components (if known)

[X] ui5-builder
[ ] ui5-server
[ ] ui5-cli
[ ] ui5-fs
[ ] ui5-project
[ ] ui5-logger

The originated problem is that we have a shim for @babel/polyfill
specVersion: "1.0"
kind: extension
type: project-shim
metadata:
    name: babel-polyfills
shims:
    configurations:
        "@babel/polyfill": # name as defined in package.json
            specVersion: "1.0"
            type: module # Use module type
            metadata:
                name: "babel-polyfills"
            resources:
                configuration:
                    paths:
                        /lib/babel/: "dist"

when building we want to build this shim but not all other dependencies. that way we could just zip the dist folder and upload that to the SAP Gateway

This makes sense. We could add a CLI parameter like --build-dependency="@babel/polyfill". Would that match your expectation?

yea that would be nice but also somehow an configuration option in the yaml file would be nice because when adding another parameter in the end we will have and unreadable npm command.

So this dependency can be understood as something the application can't work without?
If yes, I agree that a ui5.yaml configuration would make sense as well. It could define a list of dependencies that must be built when the main project is being built (e.g. via ui5 build).

also it would be nice since this dependencie is now allocated via the component namescpce. That it would be included in the Component-preload.js

@sebbi08 Is there a workaround you are currently using when deploying from Web IDE to an ABAP repo?

our workaround was to delete all the unwanted dependencies inside the dist folder before deploying this was only possible with using grunt and from runt utilize the ui5 tooling

@sebbi08 Ok. I played around a bit with the builder extensions and now I'm copying the defined shims to the dist folder (I'm using core-js-bundle as polyfill):
ui5.yaml:
---
specVersion: '1.0'
kind: extension
type: task
metadata:
  name: copy-shims
task:
  path: lib/copyShims.js
---

copyShims.js:
const log = require('@ui5/logger').getLogger('builder:customtask:copy-shim');

/**
 * Custom task example
 *
 * @param {Object} parameters Parameters
 * @param<EMAIL_ADDRESS>parameters.workspace DuplexCollection to read and write files
 * @param<EMAIL_ADDRESS>parameters.dependencies Reader or Collection to read dependency files
 * @param {Object} parameters.options Options
 * @param {string} parameters.options.projectName Project name
 * @param {string} [parameters.options.configuration] Task configuration if given in ui5.yaml
 * @returns {Promise<undefined>} Promise resolving with undefined once data has been written
 */
module.exports = async function ({workspace, dependencies, options}) {
    const shims = await dependencies.byGlob('/resources/thirdparty/*.js');
    await Promise.all(shims.map((resource) => {
        log.info(`Writing file ${resource.getPath()}`);
        workspace.write(resource);
    }));
};

manifest.json:
"resources": {
    "css": [
        {
            "uri": "css/style.css"
        }
    ],
    "js": [
        {
            "uri": "resources/thirdparty/minified.js"
        }
    ]
}

This could of course be improved but it works for me right now. Maybe useful for you too.

Looks like a valid workaround. But we are definitely looking into providing a better solution for such use cases.
@jonaszuberbuehler: I think you missed a return statement when writing the files (return workspace.write(resource);), so that the Promise.all will wait for that.

@matz3 True, thx, good catch!

@jonaszuberbuehler that's a nice workaround 👍
Thanks for raising our attention again on this issue. Various people also requested this feature on UI5con last Friday (cc @srenwickblum).
We discussed this with some of the team today and think a ui5.yaml configuration would make sense.
Proposal
ui5.yaml:
specVersion: '1.0'
metadata:
  name: my-app
type: application
requiredProjects: # <------------------
  - babel-polyfills # metadata.name of the project
---
specVersion: "1.0"
kind: extension
type: project-shim
metadata:
    name: babel-polyfill-shims
shims:
    configurations:
        "@babel/polyfill":
            specVersion: "1.0"
            type: module
            metadata:
                name: babel-polyfills
            resources:
                configuration:
                    paths:
                        /lib/babel/: "dist"

package.json:
{
  "name": "my-app",
  "dependencies": {
    "@babel/polyfill": "^7.4.4",
<EMAIL_ADDRESS>"^1.67.1",
<EMAIL_ADDRESS>"^1.67.1",
    "@openui5/themelib_sap_fiori_3": "^1.67.1"
  }
}

ui5 build: Builds my-app and babel-polyfills
ui5 build --all: Builds my-app, babel-polyfills, sap.m, sap.ui.core and themelib_sap_fiori_3

@RandomByte Nice!
Two questions:

We probably shouldn't be using babel/polyfill anymore (deprecated since 7.4.0 https://babeljs.io/docs/en/babel-polyfill), right?
Do we have to specify the shim in manifest.json as js resource (the way I did it)? This is somehow unclear to me. What are best practices here?

We probably shouldn't be using babel/polyfill anymore (deprecated since 7.4.0 https://babeljs.io/docs/en/babel-polyfill), right?

Yes, I saw that as well. I just wanted to stick to the example given by Sebastian.

Do we have to specify the shim in manifest.json as js resource (the way I did it)? This is somehow unclear to me. What are best practices here?

No. This is up to how you want to load the resource. The manifest.json configuration will simply lead to the resources being loaded synchronously upon Component initialization. If you want that, use it. However, I would recommend loading the resource asynchronously using our require APIs somewhere in your application or by other means (i.e. script tag in index.html).
The manifest.json resources configuration does not lead to the referenced resources being bundled.

@RandomByte Thanks for the clarification!

In the documented example
specVersion: "1.0"
type: application
metadata:
  name: my.application
--- # Everything below this line could also be put into the ui5.yaml of a standalone extension module
specVersion: "1.0"
kind: extension
type: project-shim
metadata:
  name: my.application.thirdparty
shims:
  configurations:
    lodash: # name as defined in package.json
      specVersion: "1.0"
      type: module # Use module type
      metadata:
        name: lodash
      resources:
        configuration:
          paths:
            /resources/my/application/thirdparty/: "" # map root directory of lodash module

what is not pointed out is that EVERYTHING is copied across and not just the main file declared in the lodash package.json:
...
  "main": "lodash.js",
  "name": "lodash",
...

The paths can save a lot of boilerplate code in some cases, but I doubt very much that developers wish to include every js file found in a node_module. It would be nice if I could specifically (instead of a 'catch-all' path) have a "files" section. E.g.
specVersion: "1.0"
type: application
metadata:
  name: my.application
--- # Everything below this line could also be put into the ui5.yaml of a standalone extension module
specVersion: "1.0"
kind: extension
type: project-shim
metadata:
  name: my.application.thirdparty
shims:
  configurations:
    lodash: # name as defined in package.json
      specVersion: "1.0"
      type: module # Use module type
      metadata:
        name: lodash
      resources:
        configuration:
          files:
            /resources/my/application/thirdparty/lodash/lodash.js: "/lodash.js"

I also like the idea that the file defined in the thirdparty's package.json as the main file, is included by default. In otherwords, when resources section in the ui5.yaml is omitted. Then ui5-tooling creates the minified + -dbg.js versions so when not in debug mode, its business as usual (everything minified) but when developers need to debug, all files are readable, including the thirdparty libraries.
I had also hoped for a way to optionally include this single file from the thirdparty library in the component-preload to optimise the loading times in cases where I'm sure I need the library early during startup. It would of course be nice when I have control to choose whether this is bundled in the preload or not.
Right now my only practical choice is to manually copy the specific files I need from node_modules and drop them in a "libs" folder which is automatically swallowed up by the build process. But for me this kinda defeats the purpose of ui5Tooling-build - at least a major aspect of it.

Hey @srenwickblum,
I think this is a bit off-topic. However, you should be able to use the builder.resources.excludes configuration to exclude everything but lodash.js. With this, when using ui5 serve (= development) you would still have all resources of the lodash module available.
We don't make much use of package.json configuration because it might mean something different depending on the package. Yet it would add another layer of complexity to a projects configuration.

In https://github.com/SAP/ui5-builder/pull/380 @kristian contributed a low level API that might resolve some use cases related to this topic.
The question now is how we expose this on a CLI and/or ui5.yaml level. I have compiled the following proposal which combines a new ui5.yaml configuration with new CLI parameters to hopefully allow solving most use cases. Any feedback would be greatly appreciated.
Proposal
New ui5.yaml configuration builder.requiredProjects
As proposed earlier, all listed projects are always built when the project is being built.
This is useful for scenarios where a dependency is exclusively used by the project itself (no reuse) and can therefore be viewed as being a part of the project.
New CLI parameters --include-dependency, --include-dependency-regexp, --exclude-dependency, --exclude-dependency-regexp
Similar to the already existing --include-task/--exclude-task parameters, they can include or exclude dependencies from the build.
This can be used to craft custom builds where some dependencies might not be required or are already given by the environment.
--all will act as an alias for --include-dependency="*" (including all dependencies). Omitting it is an alias for --exclude-dependency="*" (excluding all dependencies).
The [...]-regexp= variants allow specifying a regex that will be matched with the metadata.name property of the projects. This allows to include or exclude groups of dependencies based on their namespace.

We discussed this in the team today and came up with a change and an enhancement to the initial concept:

The change is in regards to the ui5.yaml configuration. Instead of providing a new builder configuration requiredProjects we would rather offer a settings configuration where defaults for the CLI parameters can be set. A similar configuration is already available for the server.
For example if a project wants to always have its dependency "shimmed.thirdparty.library" built, it can configure it in the ui5.yaml like this:
builder:
  settings:
     includeDependencies:
      - shimmed.thirdparty.library

The enhancement is coming from a use case we have with the JSDoc generation in the OpenUI5 project. There, JSDoc is built in a central "testsuite" application which defines dependencies to all OpenUI5 libraries. If a developer makes changes in one of the libraries, all need to be rebuilt because of the lack of this feature. However, since the JSDoc of one library might refer to the JSDoc of a dependency, often this dependency needs to be built as well.
To solve this we would like to include the possibility to specify that a  transitive dependencies should be built as well. Two possible solutions are outlined in this picture. We eventually want to go with one or the other, not both:

While Solution 1 is similar to Mavens --also-make CLI parameter, I'm leaning towards Solution 2 since it allows a finer control over which subtrees should be built. It also allows for use in the ui5.yaml settings configuration without interfering with additionally passed CLI parameters.

Bonus question: Should we only respect the ui5.yaml settings configuration of the root project? I.e. if a dependency also defines includeDependencies settings, should they be followed or ignored? I think they should be followed in order to align with an earlier statement from me that "this dependency can be understood as something the application can't work without"

If possible to specify multiple --include-depdenency-subtree Solution 2 is definitely the more flexible one, as w/ Solution 1 it would become ambiguous, which dependencies should be built w/o building the subtree, e.g. you'd like to build single dependencies w/ the subtree of another dependency, this would be only supported w/ Solution 2 and a combination of the --include-dependency and --include-dependency-subtree parameters.
I would also like to suggest renaming --include-dependency-subtree to --include-dependency-tree, as for my perception tree would include the root, whereas subtree doesn't. In other words:
--include-dependency-tree=sap.m equals --include-dependency=sap.m and --include-dependency-subtree=sap.m
So for he --include-dependency-tree is always the expected option to choose. For your bonus question, if possible I would definitely aswer it as "yes", as I guess the goal of this excersie is to make builds reproducible, which can only be guranteed if also the sub-projects ui5.yaml settings are respected. However the command line parameters should overrule any settings in sub-projects ui5.yamls, e.g. if I specify to --exclude-dependency-tree=sap.m, and a downstream project is using sap.m, it should not be built. That way you could override the behaviour of your bonus question, if needed. I can think of that beeing a use case, in case e.g. you would not like to inlude a certain library into your build, even if a downstream project requires it to be build with it.
Hope this helps and provides some suitable input for the discussion.

@sebbi08 not sure whether this help you, but I've been using a module I'd created for similar use cases:
https://www.npmjs.com/package/ui5-task-copy-resources
ui5.yaml config would be something like:
builder:
  customTasks:
  - name: ui5-task-copy-resources
    afterTask: uglify
    configuration:
      includeDependencies: true
      resources:
        - "/lib/babel/**"


Disable initial load refresh

Hi, Thanks for good component.
How to disable pull refresh loading on initial load view ??
i want refresh when drag form.
thanks.

the same  problem

the same problem ， how to fix？


Add endian support for SerializationService

Current SerializationService only works with BIG_ENDIAN but it should be able to work with both LITTLE_ENDIAN and BIG_ENDIAN.

fixed by #724


Istio dashboard - kiali and jaeger should not be active after disabling in v2 charts

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
Istio chart version: rancher-istio:1.7.601-rc02

Spin up rancher 2.5-head [v2.5-24c32a358229e3027a72ce619541e09e46a9424b-head]
Create a cluster
Enable monitoring and istio by enabling kiali/jaeger
Uninstall istio and re-install it by disabling kiali and jaeger
Once the istio is installed succefully, we still see Kiali and jaeger active eventhough disabled from step4.
This happens if the same version of istio is uninstalled and re-installed again. If we install a new version of istio rather than what was used from step3 issue is not seen.

Result:
Istio shouldn't have kiali and jaeger active if they are disabled while installing
Other details that may be helpful:
After uninstalling istio:

Re-installing istio:

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):
Installation option (single install/HA): Single

Rancher | v2.5-24c32a358229e3027a72ce619541e09e46a9424b-head
User Interface | v2.5-dev
Helm | v2.16.8-rancher1
Machine | v0.15.0-rancher49

@brendarearden can you see if this is API or UI issue

This does not appear to be a UI issue. The kiali and jaeger services are sticking around after uninstalling istio, so when you install istio again, those services already exist regardless of if you enabled them or not. This is what is causing the urls to be active since the UI is checking for those services. A solution is to ensure uninstalling the istio chart also removes the dependencies that it installed with it.

So after looking into this a bit more, this is occurring if you uninstall the rancher-kiali-server-crd prior to uninstalling the rancher-istio installation. If you select both of them to delete at the same time, since the crd chart is smaller, it ends up getting removed first resulting in rancher-istio not having the definitions it needs to finish deleting. To resolve this issue, ensure you are always removing rancher-istio PRIOR to deleting the rancher-kiali-server-crd. The resolution for this issue will be to add documentation to the chart and rancher docs.

Reproduced this issue with Rancher server rancher\rancher:v2.5-head version 03b8153
Steps:
Create a cluster on Rancher v2.5-head
Install Monitoring
Install Istio. Enable Kiali and Jaeger

Observe Kiali and Jaeger in Istio Overview
Uninstall rancher-istio and rancher-kiali-server-crd at the same time
Reinstall Istio without Kiali and Jaeger enabled

Result:
Kiali and Jaeger are still active in Istio overview:

Other information:
Noticed an error when uninstalling rancher-istio and rancher-kiali-server-crd at the same time.

Encountered this issue using the following steps:
Create a cluster on Rancher v2.5-head
Install Monitoring
Install Istio. Enable Kiali and Jaeger
Observe Kiali and Jaeger in Istio Overview
Uninstall rancher-istio FIRST
Uninstall rancher-kiali-server-crd
No error is seen when uninstalling in this order
Reinstall Istio without Kiali and Jaeger enabled
Result:
Kiali and Jaeger are still active in Istio overview.

@aaronRancher did you see any error messages from helm in the terminal when you uninstalled rancher-istio?

@aaronRancher did you see any error messages from helm in the terminal when you uninstalled rancher-istio?

When uninstalling rancher-istio first, I did not see any errors.

Was able to see kiali and jaeger inactive by using the following steps:
Create a cluster on Rancher v2.5-head
Install Monitoring
Install Istio. Enable Kiali and Jaeger
Observe Kiali and Jaeger in Istio Overview
Uninstall rancher-istio FIRST
Wait for all services to be deleted.
Uninstall rancher-kiali-server-crd
No error is seen when uninstalling in this order
Reinstall Istio without Kiali and Jaeger enabled
Result:
Kiali and Jaeger are unavailable.

Additional details:
I had uninstalled rancher-kiali-server-crd right after I saw a success in helm uninstall of rancher-istio. I should have waited a little longer for all the services to delete. In our logs, we start the deletion of kiali and jaeger services, but do not notify when they are deleted.

So fix was to wait between deleting main chart and CRD chart ?

That is what worked for me.


Feature/1598 add config for filter aggregation

Related issues
Additional config params needed for ES filter-aggregation #1598
Short description and why it's useful
At the moment each filter can have up to 10 options due to the default configurations of ES. With this configuration, users can choose for each attribute how many options to see in frontend.
(Tested in production with 90 filter options without excessive loss of performance)
Config docs updated
Screenshots of visual changes before/after

Upgrade Notes and Changelog

[x] No upgrade steps required (100% backward compatibility)
[ ] I've updated the Upgrade notes and Changelog on how to port existing VS sites with this new feature

Oh my god. I was trying to merge in master 👎 just opened a clean PR


fixed refactor bug

Codecov Report

Merging #6 (311fcb8) into master (8e89938) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Current head 311fcb8 differs from pull request most recent head 398e9b2. Consider uploading reports for the commit 398e9b2 to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff            @@
##            master        #6   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           12        12
  Lines          203       201    -2
=========================================
- Hits           203       201    -2

Impacted Files
Coverage Δ

ellar_throttler/exception.py
100.00% <100.00%> (ø)

ellar_throttler/module.py
100.00% <100.00%> (ø)

ellar_throttler/throttler_guard.py
100.00% <100.00%> (ø)

ellar_throttler/throttler_module_options.py
100.00% <100.00%> (ø)

ellar_throttler/throttler_storage_options.py
100.00% <100.00%> (ø)

ellar_throttler/throttler_storage_record.py
100.00% <100.00%> (ø)


Not able to run Managed Server container

Hi Team,
I have Admin and managed server container which is saved in images and trying to run same image in another server.
I am successfully able to run Admin server from image.
But while starting managed server container it gets stopped at particular location.
Note :[i have defined volume mount where my wars are present]
Managed server container logs ==>
Domain Home is:  /u01/oracle/user_projects/domains/base_domain
Managed Server Name:  csqManagedSvr1
NodeManager Name:
----> 'weblogic' admin password: w3bl0g1c
Waiting for WebLogic Admin Server on wlsadmin:7001 to become available...
WebLogic Admin Server is now available. Proceeding...
Setting NodeManager
----> No NodeManager Name set
Node Manager Name:  Machine_csqManagedSvr1
Node Manager Home for Container:  /u01/oracle/user_projects/domains/base_domain/Machine_csqManagedSvr1
NODEMGR_HOME_STR:  NODEMGR_HOME="/u01/oracle/user_projects/domains/base_domain/Machine_csqManagedSvr1"
NODEMGRHOME_STR:  NodeManagerHome=/u01/oracle/user_projects/domains/base_domain/Machine_csqManagedSvr1
DOMAINSFILE_STR:  DomainsFile=/u01/oracle/user_projects/domains/base_domain/Machine_csqManagedSvr1/nodemanager.domains
LOGFILE_STR:  LogFile=/u01/oracle/user_projects/domains/base_domain/Machine_csqManagedSvr1/nodemanager.log
Starting NodeManager in background...
NodeManager started.
/u01/oracle/createServer.sh: line 68: [: -eq: unary operator expected
==> /u01/oracle/log_csqManagedSvr1.nm <==
tail: cannot open '/u01/oracle/user_projects/domains/base_domain/servers/csqManagedSvr1/logs/*.out' for reading: No such file or directory
==> /u01/oracle/log_csqManagedSvr1.nm <==
NODEMGR_HOME is already set to /u01/oracle/user_projects/domains/base_domain/Machine_csqManagedSvr1
CLASSPATH=/usr/java/jdk1.8.0_191/lib/tools.jar:/u01/oracle/wlserver/server/lib/weblogic.jar:/u01/oracle/wlserver/../oracle_common/modules/thirdparty/ant-contrib-1.0b3.jar:/u01/oracle/wlserver/modules/features/oracle.wls.common.nodemanager.jar::/u01/oracle/wlserver/..:/u01/oracle/wlserver/modules/features/oracle.wls.common.grizzly.jar

/usr/java/jdk1.8.0_191/bin/java -server -Djava.security.egd=file:/dev/./urandom -Djdk.tls.ephemeralDHKeySize=2048 -Dcoherence.home=/u01/oracle/wlserver/../coherence -Dbea.home=/u01/oracle/wlserver/.. -Dweblogic.RootDirectory=/u01/oracle/user_projects/domains/base_domain -Djava.system.class.loader=com.oracle.classloader.weblogic.LaunchClassLoader -Djava.security.policy=/u01/oracle/wlserver/server/lib/weblogic.policy -Dweblogic.nodemanager.JavaHome=/usr/java/jdk1.8.0_191 weblogic.NodeManager -v
<Mar 28, 2019 12:38:48 PM GMT>  <Loading domains file: /u01/oracle/user_projects/domains/base_domain/Machine_csqManagedSvr1/nodemanager.domains>
<Mar 28, 2019 12:38:48 PM GMT>   <Setting NodeManager properties version to <IP_ADDRESS>.0>
<Mar 28, 2019 12:38:48 PM GMT>   <Saving upgraded NodeManager properties to '/u01/oracle/user_projects/domains/base_domain/Machine_csqManagedSvr1/nodemanager.properties'>
<Mar 28, 2019 12:38:48 PM GMT>  <Loading domains file: /u01/oracle/user_projects/domains/base_domain/Machine_csqManagedSvr1/nodemanager.domains>
<Mar 28, 2019 12:38:48 PM GMT>  <Loaded NodeManager configuration properties from '/u01/oracle/user_projects/domains/base_domain/Machine_csqManagedSvr1/nodemanager.properties'>
Node manager v<IP_ADDRESS>.0

Configuration settings:
DomainsFile=/u01/oracle/user_projects/domains/base_domain/Machine_csqManagedSvr1/nodemanager.domains
LogLimit=0
DomainsDirRemoteSharingEnabled=true
AuthenticationEnabled=true
LogLevel=FINEST
DomainsFileEnabled=true
ListenAddress=
NativeVersionEnabled=true
ProcessDestroyTimeout=20000
ListenPort=5556
LogToStderr=true
weblogic.StartScriptName=startWebLogic.sh
SecureListener=false
LogCount=1
LogAppend=true
weblogic.StopScriptEnabled=false
StateCheckInterval=500
CrashRecoveryEnabled=true
weblogic.StartScriptEnabled=false
LogFile=/u01/oracle/user_projects/domains/base_domain/nodemanager/nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
coherence.StartScriptEnabled=false
ListenBacklog=50
NodeManagerHome=/u01/oracle/user_projects/domains/base_domain/Machine_csqManagedSvr1
RestEnabled=false
weblogic.startup.JavaHome=/usr/java/jdk1.8.0_191
weblogic.startup.MW_Home=
coherence.startup.JavaHome=/usr/java/jdk1.8.0_191
coherence.startup.MW_Home=
Domain name mappings:
base_domain -> /u01/oracle/user_projects/domains/base_domain
<Mar 28, 2019 12:38:48 PM GMT>  <<IP_ADDRESS>.0>
<Mar 28, 2019 12:38:48 PM GMT>
<Mar 28, 2019 12:38:48 PM GMT>  <Server Implementation Class: weblogic.nodemanager.server.NMServer$ClassicServer.>
<Mar 28, 2019 12:38:48 PM GMT>  <Plain socket listener started on port 5556>

I am able to see container is running but Managed server is not created yet

Hi Team,
Could you pls let us know why it gets stuck there . I tried it in many ways but still getting above error.
Thanks in advance !!

I found the solution but because of root user i am not able to edit it.
Can you please let us know as i am completely blocked here.
In File : container-scripts/createserver.sh
Block 1 ==> here it checks NM first time , as i am using same image in another server so it will be failed
If log.nm does not exists, container is starting for 1st time
So it should start NM and also associate with AdminServer, as well Managed Server
Otherwise, only start NM (container is being restarted)
if [ ! -f /u01/oracle/log_$MS_NAME.nm ]; then
ADD_SERVER=1
fi
Block 2 ====> here it fails the condition. **

I need to comment the if condition here to solve my issue

**
if [ $ADD_SERVER -eq 1 ]; then
wlst /u01/oracle/add-machine.py
wlst /u01/oracle/add-server.py
fi

@aivl2018 What sample did you use to create the domain image?


Still some extraneous bash notation

There are some bash    notations left over from when we removed those, which aren't rendering properly, so we should remove them and replace them with simple backticks.
Here's a sampling:
https://github.com/weaveworks/weave/blob/master/site/weavedns.md
https://github.com/weaveworks/weave/blob/master/site/weavedns/load-balance-fault-weavedns.md

fixed


Add github action for qs-observability

Summary
Follow-up to #754
Adds the observability chart to github actions
Also updates the docs
Details and comments

I don't discard to rethink the naming for both charts 😅


Implemented SIPickleDataInterfaces

This PR adds the SIPickleRecordingExtractorInterface and SIPickleSortingExtractorInterface.
This allows to process the data in the SI pipeline (e.g. synchronizing the recording and curating the sorting). Using the se.load_extractor_from_pickle() function, the converter is now capable of retrieving the state of the processed extractors and save it to NWB.
@bendichter @CodyCBakerPhD @luiztauffer what do you guys think?

Would it make more sense to inherit from https://github.com/catalystneuro/nwb-conversion-tools/blob/master/nwb_conversion_tools/baserecordingextractorinterface.py?

I looked into it, but not really because the pickle loader doesn't really have an RX, and the input is only the pkl_file

It makes sense though to have a BaseSIPickleDataInterface, since the get_metadata_schema is the same.

I'll check through this, add that magic function we talked about, and refactor stuff within the next 24 hours so we can get this through and cleared off the ToDo stack.


Don't require a root node up-front

First I want to say this is a great library! However I ran into a little snag which is that you require creating a root node up front. That feels a little inelegant (you don't need to insert the first element into a Vec when you create it) and I imagine it won't match how most people use it.
For example I'm parsing a format which gives you a series of tags like OPEN_NODE, SET_VALUE, OPEN_NODE, SET_VALUE, SET_VALUE, CLOSE_NODE, CLOSE_NODE.
The root node is just the first OPEN_NODE. If I weren't required to set one up front then the code would be much simpler; as it is I have a load of if is_first_node {} checks.

I had a look at cleaning up the code and one thing that seemed weird is you used NonZeroUsize for the node IDs. Is there a reason for that? The only thing I can think of is to make Option<NodeId> smaller?

I had a look at cleaning up the code and one thing that seemed weird is you used NonZeroUsize for the node IDs. Is there a reason for that? The only thing I can think of is to make Option<NodeId> smaller?

Is because of the Root, so all the children start at 1, also smaller help!.

... root node up front.

Yeah, that is a small limitation. I always create a Node::Root for my parsers so was the easiest thing to do. It also have the nice property that I can be certain to have something from the start.


Remove version: taers232c.GAMADV-XTD3 version 6.72.01

This version is older than what has been set in max-versions-to-keep by the publisher.
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/taers232c/GAMADV-XTD3/releases/download/v6.72.01/gamadv-xtd3-6.72.01-windows-x86_64.msi
OK
(Automated message - build 910)


Mongo 5.0.0 crashes but 4.4.6 works

EDIT: conclusion here https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

Already tried too many things and 5.0.0 (or latest) won't work on my Debian distro but it works fine on WSL2 (also Debian) for some reason. If I specify the 4.4.6 version it works great.
The latest version wont go up and will go on a restart loop. Docker logs are empty as well so I couldn't see what was happening.

My docker-compose.yml:
version: "3.8"
services:
 mongodb:
  image : mongo:latest
  container_name: mongodb
  environment:
  - PUID=1000
  - PGID=1000
  volumes:
  - /home/roadside/mongodb/database:/data/db
  ports:
  - 27017:27017
  restart: unless-stopped

Sounds like the same issue as https://github.com/docker-library/mongo/issues/484
Though I'm not able to reproduce, and without logs it's hard to narrow it down any further than something in the host environment seems to be involved
$ uname -mrv
4.19.0-14-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30) x86_64

$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

$ docker-compose up -d
Creating network "mongo_default" with the default driver
Pulling mongodb (mongo:latest)...
latest: Pulling from library/mongo
Digest: sha256:f4ff7bb4291eb5d3f530a726fc524ba8e4318d652e64f2d58560ff87d083a84c
Status: Downloaded newer image for mongo:latest
Creating mongodb ... done

$ docker ps
CONTAINER ID   IMAGE          COMMAND                  CREATED          STATUS          PORTS                                           NAMES
b44e7fa4219a   mongo:latest   "docker-entrypoint.s…"   11 minutes ago   Up 11 minutes   <IP_ADDRESS>:27017->27017/tcp, :::27017->27017/tcp   mongodb

 docker logs
$ docker logs mongodb
{"t":{"$date":"2021-07-16T15:28:46.345+00:00"},"s":"I",  "c":"CONTROL",  "id":23285,   "ctx":"-","msg":"Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'"}
{"t":{"$date":"2021-07-16T15:28:46.346+00:00"},"s":"I",  "c":"NETWORK",  "id":4915701, "ctx":"main","msg":"Initialized wire specification","attr":{"spec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":13},"incomingInternalClient":{"minWireVersion":0,"maxWireVersion":13},"outgoing":{"minWireVersion":0,"maxWireVersion":13},"isInternalClient":true}}}
{"t":{"$date":"2021-07-16T15:28:46.352+00:00"},"s":"W",  "c":"ASIO",     "id":22601,   "ctx":"main","msg":"No TransportLayer configured during NetworkInterface startup"}
{"t":{"$date":"2021-07-16T15:28:46.352+00:00"},"s":"I",  "c":"NETWORK",  "id":4648601, "ctx":"main","msg":"Implicit TCP FastOpen unavailable. If TCP FastOpen is required, set tcpFastOpenServer, tcpFastOpenClient, and tcpFastOpenQueueSize."}
{"t":{"$date":"2021-07-16T15:28:46.356+00:00"},"s":"W",  "c":"ASIO",     "id":22601,   "ctx":"main","msg":"No TransportLayer configured during NetworkInterface startup"}
{"t":{"$date":"2021-07-16T15:28:46.356+00:00"},"s":"I",  "c":"REPL",     "id":5123008, "ctx":"main","msg":"Successfully registered PrimaryOnlyService","attr":{"service":"TenantMigrationDonorService","ns":"config.tenantMigrationDonors"}}
{"t":{"$date":"2021-07-16T15:28:46.356+00:00"},"s":"I",  "c":"REPL",     "id":5123008, "ctx":"main","msg":"Successfully registered PrimaryOnlyService","attr":{"service":"TenantMigrationRecipientService","ns":"config.tenantMigrationRecipients"}}
{"t":{"$date":"2021-07-16T15:28:46.357+00:00"},"s":"I",  "c":"CONTROL",  "id":4615611, "ctx":"initandlisten","msg":"MongoDB starting","attr":{"pid":1,"port":27017,"dbPath":"/data/db","architecture":"64-bit","host":"b44e7fa4219a"}}
{"t":{"$date":"2021-07-16T15:28:46.357+00:00"},"s":"I",  "c":"CONTROL",  "id":23403,   "ctx":"initandlisten","msg":"Build Info","attr":{"buildInfo":{"version":"5.0.0","gitVersion":"1184f004a99660de6f5e745573419bda8a28c0e9","openSSLVersion":"OpenSSL 1.1.1f  31 Mar 2020","modules":[],"allocator":"tcmalloc","environment":{"distmod":"ubuntu2004","distarch":"x86_64","target_arch":"x86_64"}}}}
{"t":{"$date":"2021-07-16T15:28:46.357+00:00"},"s":"I",  "c":"CONTROL",  "id":51765,   "ctx":"initandlisten","msg":"Operating System","attr":{"os":{"name":"Ubuntu","version":"20.04"}}}
{"t":{"$date":"2021-07-16T15:28:46.357+00:00"},"s":"I",  "c":"CONTROL",  "id":21951,   "ctx":"initandlisten","msg":"Options set by command line","attr":{"options":{"net":{"bindIp":"*"}}}}
{"t":{"$date":"2021-07-16T15:28:46.359+00:00"},"s":"I",  "c":"STORAGE",  "id":22297,   "ctx":"initandlisten","msg":"Using the XFS filesystem is strongly recommended with the WiredTiger storage engine. See http://dochub.mongodb.org/core/prodnotes-filesystem","tags":["startupWarnings"]}
{"t":{"$date":"2021-07-16T15:28:46.359+00:00"},"s":"I",  "c":"STORAGE",  "id":22315,   "ctx":"initandlisten","msg":"Opening WiredTiger","attr":{"config":"create,cache_size=485M,session_max=33000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),builtin_extension_config=(zstd=(compression_level=6)),file_manager=(close_idle_time=600,close_scan_interval=10,close_handle_minimum=250),statistics_log=(wait=0),verbose=[recovery_progress,checkpoint_progress,compact_progress],"}}
{"t":{"$date":"2021-07-16T15:28:46.892+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"[1626449326:892958][1:0x7fc195dc4c80], txn-recover: [WT_VERB_RECOVERY | WT_VERB_RECOVERY_PROGRESS] Set global recovery timestamp: (0, 0)"}}
{"t":{"$date":"2021-07-16T15:28:46.893+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"[1626449326:893279][1:0x7fc195dc4c80], txn-recover: [WT_VERB_RECOVERY | WT_VERB_RECOVERY_PROGRESS] Set global oldest timestamp: (0, 0)"}}
{"t":{"$date":"2021-07-16T15:28:46.898+00:00"},"s":"I",  "c":"STORAGE",  "id":4795906, "ctx":"initandlisten","msg":"WiredTiger opened","attr":{"durationMillis":539}}
{"t":{"$date":"2021-07-16T15:28:46.898+00:00"},"s":"I",  "c":"RECOVERY", "id":23987,   "ctx":"initandlisten","msg":"WiredTiger recoveryTimestamp","attr":{"recoveryTimestamp":{"$timestamp":{"t":0,"i":0}}}}
{"t":{"$date":"2021-07-16T15:28:46.905+00:00"},"s":"I",  "c":"STORAGE",  "id":4366408, "ctx":"initandlisten","msg":"No table logging settings modifications are required for existing WiredTiger tables","attr":{"loggingEnabled":true}}
{"t":{"$date":"2021-07-16T15:28:46.906+00:00"},"s":"I",  "c":"STORAGE",  "id":22262,   "ctx":"initandlisten","msg":"Timestamp monitor starting"}
{"t":{"$date":"2021-07-16T15:28:46.908+00:00"},"s":"W",  "c":"CONTROL",  "id":22120,   "ctx":"initandlisten","msg":"Access control is not enabled for the database. Read and write access to data and configuration is unrestricted","tags":["startupWarnings"]}
{"t":{"$date":"2021-07-16T15:28:46.908+00:00"},"s":"W",  "c":"CONTROL",  "id":22178,   "ctx":"initandlisten","msg":"/sys/kernel/mm/transparent_hugepage/enabled is 'always'. We suggest setting it to 'never'","tags":["startupWarnings"]}
{"t":{"$date":"2021-07-16T15:28:46.909+00:00"},"s":"I",  "c":"STORAGE",  "id":20320,   "ctx":"initandlisten","msg":"createCollection","attr":{"namespace":"admin.system.version","uuidDisposition":"provided","uuid":{"uuid":{"$uuid":"922d5d62-54fb-4f84-8e44-daaa4b09d46d"}},"options":{"uuid":{"$uuid":"922d5d62-54fb-4f84-8e44-daaa4b09d46d"}}}}
{"t":{"$date":"2021-07-16T15:28:46.925+00:00"},"s":"I",  "c":"INDEX",    "id":20345,   "ctx":"initandlisten","msg":"Index build: done building","attr":{"buildUUID":null,"namespace":"admin.system.version","index":"_id_","commitTimestamp":null}}
{"t":{"$date":"2021-07-16T15:28:46.926+00:00"},"s":"I",  "c":"REPL",     "id":20459,   "ctx":"initandlisten","msg":"Setting featureCompatibilityVersion","attr":{"newVersion":"5.0"}}
{"t":{"$date":"2021-07-16T15:28:46.926+00:00"},"s":"I",  "c":"NETWORK",  "id":4915702, "ctx":"initandlisten","msg":"Updated wire specification","attr":{"oldSpec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":13},"incomingInternalClient":{"minWireVersion":0,"maxWireVersion":13},"outgoing":{"minWireVersion":0,"maxWireVersion":13},"isInternalClient":true},"newSpec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":13},"incomingInternalClient":{"minWireVersion":13,"maxWireVersion":13},"outgoing":{"minWireVersion":13,"maxWireVersion":13},"isInternalClient":true}}}
{"t":{"$date":"2021-07-16T15:28:46.927+00:00"},"s":"I",  "c":"NETWORK",  "id":4915702, "ctx":"initandlisten","msg":"Updated wire specification","attr":{"oldSpec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":13},"incomingInternalClient":{"minWireVersion":13,"maxWireVersion":13},"outgoing":{"minWireVersion":13,"maxWireVersion":13},"isInternalClient":true},"newSpec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":13},"incomingInternalClient":{"minWireVersion":13,"maxWireVersion":13},"outgoing":{"minWireVersion":13,"maxWireVersion":13},"isInternalClient":true}}}
{"t":{"$date":"2021-07-16T15:28:46.927+00:00"},"s":"I",  "c":"STORAGE",  "id":5071100, "ctx":"initandlisten","msg":"Clearing temp directory"}
{"t":{"$date":"2021-07-16T15:28:46.927+00:00"},"s":"I",  "c":"CONTROL",  "id":20536,   "ctx":"initandlisten","msg":"Flow Control is enabled on this deployment"}
{"t":{"$date":"2021-07-16T15:28:46.929+00:00"},"s":"I",  "c":"FTDC",     "id":20625,   "ctx":"initandlisten","msg":"Initializing full-time diagnostic data capture","attr":{"dataDirectory":"/data/db/diagnostic.data"}}
{"t":{"$date":"2021-07-16T15:28:46.929+00:00"},"s":"I",  "c":"STORAGE",  "id":20320,   "ctx":"initandlisten","msg":"createCollection","attr":{"namespace":"local.startup_log","uuidDisposition":"generated","uuid":{"uuid":{"$uuid":"8f4a4648-e995-448f-bf46-93296146c08f"}},"options":{"capped":true,"size":10485760}}}
{"t":{"$date":"2021-07-16T15:28:46.935+00:00"},"s":"I",  "c":"INDEX",    "id":20345,   "ctx":"initandlisten","msg":"Index build: done building","attr":{"buildUUID":null,"namespace":"local.startup_log","index":"_id_","commitTimestamp":null}}
{"t":{"$date":"2021-07-16T15:28:46.938+00:00"},"s":"I",  "c":"STORAGE",  "id":20320,   "ctx":"LogicalSessionCacheRefresh","msg":"createCollection","attr":{"namespace":"config.system.sessions","uuidDisposition":"generated","uuid":{"uuid":{"$uuid":"ecf1ee3c-304a-42aa-b1b0-8ded4f98ddf5"}},"options":{}}}
{"t":{"$date":"2021-07-16T15:28:46.940+00:00"},"s":"I",  "c":"CONTROL",  "id":20712,   "ctx":"LogicalSessionCacheReap","msg":"Sessions collection is not set up; waiting until next sessions reap interval","attr":{"error":"NamespaceNotFound: config.system.sessions does not exist"}}
{"t":{"$date":"2021-07-16T15:28:46.940+00:00"},"s":"I",  "c":"NETWORK",  "id":23015,   "ctx":"listener","msg":"Listening on","attr":{"address":"/tmp/mongodb-27017.sock"}}
{"t":{"$date":"2021-07-16T15:28:46.940+00:00"},"s":"I",  "c":"NETWORK",  "id":23015,   "ctx":"listener","msg":"Listening on","attr":{"address":"<IP_ADDRESS>"}}
{"t":{"$date":"2021-07-16T15:28:46.941+00:00"},"s":"I",  "c":"NETWORK",  "id":23016,   "ctx":"listener","msg":"Waiting for connections","attr":{"port":27017,"ssl":"off"}}
{"t":{"$date":"2021-07-16T15:28:46.947+00:00"},"s":"I",  "c":"INDEX",    "id":20345,   "ctx":"LogicalSessionCacheRefresh","msg":"Index build: done building","attr":{"buildUUID":null,"namespace":"config.system.sessions","index":"_id_","commitTimestamp":null}}
{"t":{"$date":"2021-07-16T15:28:46.948+00:00"},"s":"I",  "c":"INDEX",    "id":20345,   "ctx":"LogicalSessionCacheRefresh","msg":"Index build: done building","attr":{"buildUUID":null,"namespace":"config.system.sessions","index":"lsidTTLIndex","commitTimestamp":null}}
{"t":{"$date":"2021-07-16T15:29:46.915+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"Checkpointer","msg":"WiredTiger message","attr":{"message":"[1626449386:914877][1:0x7fc18d5b2700], WT_SESSION.checkpoint: [WT_VERB_CHECKPOINT_PROGRESS] saving checkpoint snapshot min: 34, snapshot max: 34 snapshot count: 0, oldest timestamp: (0, 0) , meta checkpoint timestamp: (0, 0)"}}
{"t":{"$date":"2021-07-16T15:30:46.924+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"Checkpointer","msg":"WiredTiger message","attr":{"message":"[1626449446:924072][1:0x7fc18d5b2700], WT_SESSION.checkpoint: [WT_VERB_CHECKPOINT_PROGRESS] saving checkpoint snapshot min: 36, snapshot max: 36 snapshot count: 0, oldest timestamp: (0, 0) , meta checkpoint timestamp: (0, 0)"}}
{"t":{"$date":"2021-07-16T15:31:46.930+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"Checkpointer","msg":"WiredTiger message","attr":{"message":"[1626449506:929925][1:0x7fc18d5b2700], WT_SESSION.checkpoint: [WT_VERB_CHECKPOINT_PROGRESS] saving checkpoint snapshot min: 37, snapshot max: 37 snapshot count: 0, oldest timestamp: (0, 0) , meta checkpoint timestamp: (0, 0)"}}
{"t":{"$date":"2021-07-16T15:32:46.935+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"Checkpointer","msg":"WiredTiger message","attr":{"message":"[1626449566:935232][1:0x7fc18d5b2700], WT_SESSION.checkpoint: [WT_VERB_CHECKPOINT_PROGRESS] saving checkpoint snapshot min: 38, snapshot max: 38 snapshot count: 0, oldest timestamp: (0, 0) , meta checkpoint timestamp: (0, 0)"}}
{"t":{"$date":"2021-07-16T15:33:46.940+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"Checkpointer","msg":"WiredTiger message","attr":{"message":"[1626449626:940551][1:0x7fc18d5b2700], WT_SESSION.checkpoint: [WT_VERB_CHECKPOINT_PROGRESS] saving checkpoint snapshot min: 39, snapshot max: 39 snapshot count: 0, oldest timestamp: (0, 0) , meta checkpoint timestamp: (0, 0)"}}
{"t":{"$date":"2021-07-16T15:34:46.947+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"Checkpointer","msg":"WiredTiger message","attr":{"message":"[1626449686:946981][1:0x7fc18d5b2700], WT_SESSION.checkpoint: [WT_VERB_CHECKPOINT_PROGRESS] saving checkpoint snapshot min: 40, snapshot max: 40 snapshot count: 0, oldest timestamp: (0, 0) , meta checkpoint timestamp: (0, 0)"}}
{"t":{"$date":"2021-07-16T15:35:46.952+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"Checkpointer","msg":"WiredTiger message","attr":{"message":"[1626449746:951982][1:0x7fc18d5b2700], WT_SESSION.checkpoint: [WT_VERB_CHECKPOINT_PROGRESS] saving checkpoint snapshot min: 41, snapshot max: 41 snapshot count: 0, oldest timestamp: (0, 0) , meta checkpoint timestamp: (0, 0)"}}
{"t":{"$date":"2021-07-16T15:36:46.961+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"Checkpointer","msg":"WiredTiger message","attr":{"message":"[1626449806:961640][1:0x7fc18d5b2700], WT_SESSION.checkpoint: [WT_VERB_CHECKPOINT_PROGRESS] saving checkpoint snapshot min: 42, snapshot max: 42 snapshot count: 0, oldest timestamp: (0, 0) , meta checkpoint timestamp: (0, 0)"}}
{"t":{"$date":"2021-07-16T15:37:46.967+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"Checkpointer","msg":"WiredTiger message","attr":{"message":"[1626449866:967245][1:0x7fc18d5b2700], WT_SESSION.checkpoint: [WT_VERB_CHECKPOINT_PROGRESS] saving checkpoint snapshot min: 43, snapshot max: 43 snapshot count: 0, oldest timestamp: (0, 0) , meta checkpoint timestamp: (0, 0)"}}
{"t":{"$date":"2021-07-16T15:38:46.975+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"Checkpointer","msg":"WiredTiger message","attr":{"message":"[1626449926:975698][1:0x7fc18d5b2700], WT_SESSION.checkpoint: [WT_VERB_CHECKPOINT_PROGRESS] saving checkpoint snapshot min: 44, snapshot max: 44 snapshot count: 0, oldest timestamp: (0, 0) , meta checkpoint timestamp: (0, 0)"}}

One thing I didn't mention is that my Debian is running through Proxmox so maybe the fact that it's a virtual machine is messing things up? Weird thing is it works for 4.4.6 but not for 5.0. Maybe I should edit the main post and add this information
I would try and mount a Debian fresh install in my Proxmox server and see if this happens again. Will report later

It might be helpful to get the logs of the crashing container. Can you replicate the failure via a plain a docker run -it --rm?

I'd just like to point out that the environment variables PUID ang PGID have no effect on the mongo images.  If you are trying to run as a specific user, then you need to set user: (docker run --user).

It might be helpful to get the logs of the crashing container. Can you replicate the failure via a plain a docker run -it --rm?
I'd just like to point out that the environment variables PUID ang PGID have no effect on the mongo images. If you are trying to run as a specific user, then you need to set user: (docker run --user).

If I do docker run -it --rm mongo:4.4.6 it gives a full log.

But if I do docker run -it --rm mongo:latest it just disappear from existence without leaving any trace.

It seems to be related to running on a Debian Buster host but it works fine on Debian Bullseye.  I tried --security-opt seccomp=unconfined with no effect. There was no change when updating libseccomp2 on Buster to the backports version (from 2.3.3-4 to 2.4.4-1~bpo10+1).
mongo and mongod crash in the same way.
I am out of my depth to figure out where the issue lies. Maybe this debugging output will help someone dig deeper. Here is part of the strace:
...
mprotect(0x7f8e26431000, 4096, PROT_READ) = 0
munmap(0x7f8e26401000, 11584)           = 0
set_tid_address(0x7f8e24f76f50)         = 653
set_robust_list(0x7f8e24f76f60, 24)     = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f8e25f91bf0, sa_mask=[], sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f8e25f9f3c0}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f8e25f91c90, sa_mask=[], sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f8e25f9f3c0}, NULL, 8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024, rlim_max=RLIM64_INFINITY}) = 0
--- SIGILL {si_signo=SIGILL, si_code=ILL_ILLOPN, si_addr=0x563861eb30da} ---
+++ killed by SIGILL (core dumped) +++
Illegal instruction

The backtrace from the core dump:
root@e701f3df7942:/# gdb -c core mongo
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
...
Core was generated by `/usr/bin/mongo'.
Program terminated with signal SIGILL, Illegal instruction.
#0  0x00005646a7f8a0da in tcmalloc::SizeMap::Init() ()
(gdb) bt
#0  0x00005646a7f8a0da in tcmalloc::SizeMap::Init() ()
#1  0x00005646a7f929f7 in tcmalloc::Static::InitStaticVars() ()
#2  0x00005646a7f94447 in tcmalloc::ThreadCache::InitModule() ()
#3  0x00005646a7f945dd in tcmalloc::ThreadCache::CreateCacheIfNecessary() ()
#4  0x00005646a803cf35 in tcmalloc::allocate_full_malloc_oom(unsigned long) ()
#5  0x00007f618d7e211a in __newlocale (category_mask=<optimized out>,
    locale=<optimized out>, base=<optimized out>) at newlocale.c:200
#6  0x00007f618cf580dd in ?? () from /lib/x86_64-linux-gnu/libp11-kit.so.0
#7  0x00007f618df78b8a in ?? () from /lib64/ld-linux-x86-64.so.2
#8  0x00007f618df78c91 in ?? () from /lib64/ld-linux-x86-64.so.2
#9  0x00007f618df6813a in ?? () from /lib64/ld-linux-x86-64.so.2
#10 0x0000000000000001 in ?? ()
#11 0x00007fffd3f058d7 in ?? ()
#12 0x0000000000000000 in ?? ()

This mongo:5 image:
$ docker pull mongo:5
5: Pulling from library/mongo
Digest: sha256:f4ff7bb4291eb5d3f530a726fc524ba8e4318d652e64f2d58560ff87d083a84c
Status: Downloaded newer image for mongo:5
docker.io/library/mongo:5

$ docker run -it --rm mongo:5 bash
$ # try mongo or mongod

It seems to be related to running on a Debian Buster host but it works fine on Debian Bullseye.

as I mentioned before, it didn't work on a fresh install of Ubuntu server which is based on Bullseye (as far as I can tell by doing  cat /etc/debian_version)

Same here
The only log i found is
traps: mongod[2994] trap invalid opcode ip:56017a3a6cda sp:7ffda040e0c0 error:0 in mongod[560176496000+5022000]

I'm on pop_os which is debian based and 5.0.0 crashes on start as well. Had to revert to 4.4.6.

Running mongodb within docker on Ubuntu on an older CPU (Core2Duo P8600) crashes with mongod 5 (the container restarts with code 132) but is running fine with 4.4.6.
Whereas on newer CPUs (Core i5-4310m or AMD Ryzen Threadripper 1920X 12-Core) the 5 is starting and running fine.
What I have tried was using gdb:
root@5f09ddb07e92:/# gdb /usr/bin/mongod
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
[...]
Reading symbols from /usr/bin/mongod...
(No debugging symbols found in /usr/bin/mongod)
(gdb) run
Starting program: /usr/bin/mongod
warning: Error disabling address space randomization: Operation not permitted
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGILL, Illegal instruction.
0x0000564f3ca21cda in tcmalloc::SizeMap::Init() ()
(gdb)
Here I have found the information that restarting a container with code 132 is related to instructions not available on the CPU
https://stackoverflow.com/questions/60930359/docker-containers-exit-code-132
https://hub.mender.io/t/unable-to-start-on-premise-demo-server-per-getting-started-instructions/1414/23
In fact my Core2Duo is missing sse4_2 (and other flags in comparison to my other CPUs). But now I don't know how to proceed further, i.e. how to check the parameters used to compile mongod within the docker-image, ...
But maybe this is something an enlightet persons is able to check?

Hi,
I also encounter this error.
I notice it happens after Ubuntu upgrade : containerd.io:amd64 (1.4.6-1, 1.4.8-1).
I tried to downgrade to 1.4.6 without success.
Ubuuntu 20.04 (happens on  5.4.0-77-generic) :
Linux ns******.eu 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 22:49:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Packages updated :
Upgrade: containerd.io:amd64 (1.4.6-1, 1.4.8-1), beamium:amd64 (2.0.7-focal, 2.0.8-bionic), libsystemd0:amd64 (245.4-4ubuntu3.7, 245.4-4ubuntu3.10), udev:amd64 (245.4-4ubuntu3.7, 245.4-4ubuntu3.10), libudev1:amd64 (245.4-4ubuntu3.7, 245.4-4ubuntu3.10), systemd-timesyncd:amd64 (245.4-4ubuntu3.7, 245.4-4ubuntu3.10), python3-distupgrade:amd64 (1:20.04.33, 1:20.04.35), ubuntu-release-upgrader-core:amd64 (1:20.04.33, 1:20.04.35), qemu-user-static:amd64 (1:4.2-3ubuntu6.16, 1:4.2-3ubuntu6.17), systemd-sysv:amd64 (245.4-4ubuntu3.7, 245.4-4ubuntu3.10), libpam-systemd:amd64 (245.4-4ubuntu3.7, 245.4-4ubuntu3.10), systemd:amd64 (245.4-4ubuntu3.7, 245.4-4ubuntu3.10), libnss-systemd:amd64 (245.4-4ubuntu3.7, 245.4-4ubuntu3.10), apache2-utils:amd64 (2.4.41-4ubuntu3.3, 2.4.41-4ubuntu3.4)

I can run bash but cannot exec docker entrypoint :
docker run --rm -it mongo:5.0 bash
root@6041c8b2a4f6:/# docker-entrypoint.sh mongod
Illegal instruction

Can also attest that mongo:latest no longer works and had to downgrade to 4.4.6 for the image to work on Raspberry Pi 4 (running Ubuntu Server 21.04).

Same thing here, looks like my test instance server updated the MongoDB image to version 5 or whatever, and then none of the mongo containers would start anymore, empty log output and endless restarting. Rolled back to tag "4" and everything worked great again. Running up-to-date Ubuntu Server 20.04.2 LTS in a VM on an R620 running Proxmox 7, since it sounds like that's relevant.

I have the same problem. I'm using a virtual machine with Ubuntu and got this exit code 132. This SO thread and few others suggest that the CPU is a problem. So I changed virtual machine to the one with newer and better CPU, more RAM, but still Ubuntu. Fresh install of everything and ... same exit code 132.
I then downgrade do 4.4.7 and .... it works.

+1 here. Same as the others; using the :latest tag on my machine gives me exit code 132 as well now. I'm running Desktop + Ubuntu (WSL2).

seems avx cpu feature needed to run mongo5, can somebody can confirm this? cat /proc/cpuinfo | grep avx

@martadinata666 interesting find, on my Debian Buster machine (which can run mongo:5) it does have that avx flag
$ cat /proc/cpuinfo | grep -i avx
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology cpuid tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm cpuid_fault invpcid_single pti ssbd ibrs ibpb fsgsbase bmi1 hle avx2 smep bmi2 erms invpcid rtm avx512f avx512dq clwb avx512cd avx512bw avx512vl xsaveopt arat pku ospke

$ uname -mrv
4.19.0-14-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30) x86_64

$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

$ cat docker-compose.yml | grep image
  image : mongo:5

$ docker-compose up -d
Creating mongodb ... done

$ docker ps
CONTAINER ID   IMAGE     COMMAND                  CREATED              STATUS              PORTS                                           NAMES
36ec193f8fd6   mongo:5   "docker-entrypoint.s…"   About a minute ago   Up About a minute   <IP_ADDRESS>:27017->27017/tcp, :::27017->27017/tcp   mongodb

 docker logs mongo
$ docker logs mongodb
{"t":{"$date":"2021-08-02T16:19:45.152+00:00"},"s":"I",  "c":"NETWORK",  "id":4915701, "ctx":"-","msg":"Initialized wire specification","attr":{"spec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":13},"incomingInternalClient":{"minWireVersion":0,"maxWireVersion":13},"outgoing":{"minWireVersion":0,"maxWireVersion":13},"isInternalClient":true}}}
{"t":{"$date":"2021-08-02T16:19:45.164+00:00"},"s":"I",  "c":"CONTROL",  "id":23285,   "ctx":"main","msg":"Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'"}
{"t":{"$date":"2021-08-02T16:19:45.166+00:00"},"s":"W",  "c":"ASIO",     "id":22601,   "ctx":"main","msg":"No TransportLayer configured during NetworkInterface startup"}
{"t":{"$date":"2021-08-02T16:19:45.166+00:00"},"s":"I",  "c":"NETWORK",  "id":4648601, "ctx":"main","msg":"Implicit TCP FastOpen unavailable. If TCP FastOpen is required, set tcpFastOpenServer, tcpFastOpenClient, and tcpFastOpenQueueSize."}
{"t":{"$date":"2021-08-02T16:19:45.170+00:00"},"s":"W",  "c":"ASIO",     "id":22601,   "ctx":"main","msg":"No TransportLayer configured during NetworkInterface startup"}
{"t":{"$date":"2021-08-02T16:19:45.171+00:00"},"s":"I",  "c":"REPL",     "id":5123008, "ctx":"main","msg":"Successfully registered PrimaryOnlyService","attr":{"service":"TenantMigrationDonorService","ns":"config.tenantMigrationDonors"}}
{"t":{"$date":"2021-08-02T16:19:45.171+00:00"},"s":"I",  "c":"REPL",     "id":5123008, "ctx":"main","msg":"Successfully registered PrimaryOnlyService","attr":{"service":"TenantMigrationRecipientService","ns":"config.tenantMigrationRecipients"}}
{"t":{"$date":"2021-08-02T16:19:45.171+00:00"},"s":"I",  "c":"CONTROL",  "id":4615611, "ctx":"initandlisten","msg":"MongoDB starting","attr":{"pid":1,"port":27017,"dbPath":"/data/db","architecture":"64-bit","host":"36ec193f8fd6"}}
{"t":{"$date":"2021-08-02T16:19:45.171+00:00"},"s":"I",  "c":"CONTROL",  "id":23403,   "ctx":"initandlisten","msg":"Build Info","attr":{"buildInfo":{"version":"5.0.0","gitVersion":"1184f004a99660de6f5e745573419bda8a28c0e9","openSSLVersion":"OpenSSL 1.1.1f  31 Mar 2020","modules":[],"allocator":"tcmalloc","environment":{"distmod":"ubuntu2004","distarch":"x86_64","target_arch":"x86_64"}}}}
{"t":{"$date":"2021-08-02T16:19:45.172+00:00"},"s":"I",  "c":"CONTROL",  "id":51765,   "ctx":"initandlisten","msg":"Operating System","attr":{"os":{"name":"Ubuntu","version":"20.04"}}}
{"t":{"$date":"2021-08-02T16:19:45.172+00:00"},"s":"I",  "c":"CONTROL",  "id":21951,   "ctx":"initandlisten","msg":"Options set by command line","attr":{"options":{"net":{"bindIp":"*"}}}}
{"t":{"$date":"2021-08-02T16:19:45.175+00:00"},"s":"W",  "c":"STORAGE",  "id":22271,   "ctx":"initandlisten","msg":"Detected unclean shutdown - Lock file is not empty","attr":{"lockFile":"/data/db/mongod.lock"}}
{"t":{"$date":"2021-08-02T16:19:45.175+00:00"},"s":"I",  "c":"STORAGE",  "id":22270,   "ctx":"initandlisten","msg":"Storage engine to use detected by data files","attr":{"dbpath":"/data/db","storageEngine":"wiredTiger"}}
{"t":{"$date":"2021-08-02T16:19:45.175+00:00"},"s":"W",  "c":"STORAGE",  "id":22302,   "ctx":"initandlisten","msg":"Recovering data from the last clean checkpoint."}
{"t":{"$date":"2021-08-02T16:19:45.175+00:00"},"s":"I",  "c":"STORAGE",  "id":22297,   "ctx":"initandlisten","msg":"Using the XFS filesystem is strongly recommended with the WiredTiger storage engine. See http://dochub.mongodb.org/core/prodnotes-filesystem","tags":["startupWarnings"]}
{"t":{"$date":"2021-08-02T16:19:45.175+00:00"},"s":"I",  "c":"STORAGE",  "id":22315,   "ctx":"initandlisten","msg":"Opening WiredTiger","attr":{"config":"create,cache_size=485M,session_max=33000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),builtin_extension_config=(zstd=(compression_level=6)),file_manager=(close_idle_time=600,close_scan_interval=10,close_handle_minimum=250),statistics_log=(wait=0),verbose=[recovery_progress,checkpoint_progress,compact_progress],"}}
{"t":{"$date":"2021-08-02T16:19:45.714+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"[1627921185:714759][1:0x7f146768cc80], txn-recover: [WT_VERB_RECOVERY_PROGRESS] Recovering log 1 through 2"}}
{"t":{"$date":"2021-08-02T16:19:45.925+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"[1627921185:925803][1:0x7f146768cc80], txn-recover: [WT_VERB_RECOVERY_PROGRESS] Recovering log 2 through 2"}}
{"t":{"$date":"2021-08-02T16:19:46.158+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"[1627921186:158221][1:0x7f146768cc80], txn-recover: [WT_VERB_RECOVERY | WT_VERB_RECOVERY_PROGRESS] Main recovery loop: starting at 1/7260928 to 2/256"}}
{"t":{"$date":"2021-08-02T16:19:46.159+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"[1627921186:159567][1:0x7f146768cc80], txn-recover: [WT_VERB_RECOVERY_PROGRESS] Recovering log 1 through 2"}}
{"t":{"$date":"2021-08-02T16:19:46.231+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"[1627921186:231973][1:0x7f146768cc80], txn-recover: [WT_VERB_RECOVERY_PROGRESS] Recovering log 2 through 2"}}
{"t":{"$date":"2021-08-02T16:19:46.287+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"[1627921186:287648][1:0x7f146768cc80], txn-recover: [WT_VERB_RECOVERY | WT_VERB_RECOVERY_PROGRESS] Set global recovery timestamp: (0, 0)"}}
{"t":{"$date":"2021-08-02T16:19:46.287+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"[1627921186:287891][1:0x7f146768cc80], txn-recover: [WT_VERB_RECOVERY | WT_VERB_RECOVERY_PROGRESS] Set global oldest timestamp: (0, 0)"}}
{"t":{"$date":"2021-08-02T16:19:46.311+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"[1627921186:311087][1:0x7f146768cc80], WT_SESSION.checkpoint: [WT_VERB_CHECKPOINT_PROGRESS] saving checkpoint snapshot min: 4, snapshot max: 4 snapshot count: 0, oldest timestamp: (0, 0) , meta checkpoint timestamp: (0, 0)"}}
{"t":{"$date":"2021-08-02T16:19:46.315+00:00"},"s":"I",  "c":"STORAGE",  "id":4795906, "ctx":"initandlisten","msg":"WiredTiger opened","attr":{"durationMillis":1139}}
{"t":{"$date":"2021-08-02T16:19:46.315+00:00"},"s":"I",  "c":"RECOVERY", "id":23987,   "ctx":"initandlisten","msg":"WiredTiger recoveryTimestamp","attr":{"recoveryTimestamp":{"$timestamp":{"t":0,"i":0}}}}
{"t":{"$date":"2021-08-02T16:19:46.319+00:00"},"s":"I",  "c":"STORAGE",  "id":4366408, "ctx":"initandlisten","msg":"No table logging settings modifications are required for existing WiredTiger tables","attr":{"loggingEnabled":true}}
{"t":{"$date":"2021-08-02T16:19:46.325+00:00"},"s":"I",  "c":"STORAGE",  "id":22262,   "ctx":"initandlisten","msg":"Timestamp monitor starting"}
{"t":{"$date":"2021-08-02T16:19:46.326+00:00"},"s":"W",  "c":"CONTROL",  "id":22120,   "ctx":"initandlisten","msg":"Access control is not enabled for the database. Read and write access to data and configuration is unrestricted","tags":["startupWarnings"]}
{"t":{"$date":"2021-08-02T16:19:46.327+00:00"},"s":"W",  "c":"CONTROL",  "id":22178,   "ctx":"initandlisten","msg":"/sys/kernel/mm/transparent_hugepage/enabled is 'always'. We suggest setting it to 'never'","tags":["startupWarnings"]}
{"t":{"$date":"2021-08-02T16:19:46.339+00:00"},"s":"I",  "c":"NETWORK",  "id":4915702, "ctx":"initandlisten","msg":"Updated wire specification","attr":{"oldSpec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":13},"incomingInternalClient":{"minWireVersion":0,"maxWireVersion":13},"outgoing":{"minWireVersion":0,"maxWireVersion":13},"isInternalClient":true},"newSpec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":13},"incomingInternalClient":{"minWireVersion":13,"maxWireVersion":13},"outgoing":{"minWireVersion":13,"maxWireVersion":13},"isInternalClient":true}}}
{"t":{"$date":"2021-08-02T16:19:46.340+00:00"},"s":"I",  "c":"STORAGE",  "id":5071100, "ctx":"initandlisten","msg":"Clearing temp directory"}
{"t":{"$date":"2021-08-02T16:19:46.340+00:00"},"s":"I",  "c":"CONTROL",  "id":20536,   "ctx":"initandlisten","msg":"Flow Control is enabled on this deployment"}
{"t":{"$date":"2021-08-02T16:19:46.344+00:00"},"s":"I",  "c":"FTDC",     "id":20625,   "ctx":"initandlisten","msg":"Initializing full-time diagnostic data capture","attr":{"dataDirectory":"/data/db/diagnostic.data"}}
{"t":{"$date":"2021-08-02T16:19:46.344+00:00"},"s":"I",  "c":"STORAGE",  "id":20320,   "ctx":"initandlisten","msg":"createCollection","attr":{"namespace":"local.startup_log","uuidDisposition":"generated","uuid":{"uuid":{"$uuid":"10795fe8-3471-4360-823c-287d43eed4fe"}},"options":{"capped":true,"size":10485760}}}
{"t":{"$date":"2021-08-02T16:19:46.352+00:00"},"s":"I",  "c":"INDEX",    "id":20345,   "ctx":"initandlisten","msg":"Index build: done building","attr":{"buildUUID":null,"namespace":"local.startup_log","index":"_id_","commitTimestamp":null}}
{"t":{"$date":"2021-08-02T16:19:46.356+00:00"},"s":"I",  "c":"NETWORK",  "id":23015,   "ctx":"listener","msg":"Listening on","attr":{"address":"/tmp/mongodb-27017.sock"}}
{"t":{"$date":"2021-08-02T16:19:46.356+00:00"},"s":"I",  "c":"NETWORK",  "id":23015,   "ctx":"listener","msg":"Listening on","attr":{"address":"<IP_ADDRESS>"}}
{"t":{"$date":"2021-08-02T16:19:46.357+00:00"},"s":"I",  "c":"NETWORK",  "id":23016,   "ctx":"listener","msg":"Waiting for connections","attr":{"port":27017,"ssl":"off"}}
{"t":{"$date":"2021-08-02T16:19:47.024+00:00"},"s":"I",  "c":"FTDC",     "id":20631,   "ctx":"ftdc","msg":"Unclean full-time diagnostic data capture shutdown detected, found interim file, some metrics may have been lost","attr":{"error":{"code":0,"codeName":"OK"}}}
{"t":{"$date":"2021-08-02T16:20:46.330+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"Checkpointer","msg":"WiredTiger message","attr":{"message":"[1627921246:330058][1:0x7f145ee7a700], WT_SESSION.checkpoint: [WT_VERB_CHECKPOINT_PROGRESS] saving checkpoint snapshot min: 12, snapshot max: 12 snapshot count: 0, oldest timestamp: (0, 0) , meta checkpoint timestamp: (0, 0)"}}

mine is intel g5400 that doesn't have the avx instruction, mongodb will just show error 132 illegal instructions

@martadinata666 Thanks for this info - verified on my three boxes:
Ubuntu 20.04. on Intel P8600: no avx - mongo:5 is not able to run.
Windows 10 with Docker running in HyperV on Intel Core i5-4310M: checked from within a docker-container: avx2 available - mongo:5 is running
Debian 10 on AMD Ryzen Threadripper 1920X: avx2 available - mongo:5 is running
Here the complete list of flags supported by my CPUs:
status:  mongo:5 not working
model name      : Intel(R) Core(TM)2 Duo CPU     P8600  @ 2.40GHz
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts nopl cpuid aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm pti tpr_shadow vnmi flexpriority dtherm ida
status:  mongo:5 working
model name      : AMD Ryzen Threadripper 1920X 12-Core Processor
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl tsc_reliable nonstop_tsc cpuid extd_apicid pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ssbd ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xsaves clzero arat overflow_recov succor
status:  mongo:5 working
model name      : Intel(R) Core(TM) i5-4310M CPU @ 2.70GHz
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology cpuid pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm abm invpcid_single ssbd ibrs ibpb stibp fsgsbase bmi1 avx2 smep bmi2 erms invpcid xsaveopt flush_l1d arch_capabilities

seems confirmed, https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610

Thanks @martadinata666 for the link.
Summary:

For Intel x86_64, MongoDB requires Sandy Bridge or later.
For AMD x86_64, MongoDB requires Bulldozer or later.
Starting in MongoDB 5.0, mongod, mongos, and the legacy mongo shell no longer support x86_64 platforms which do not meet this minimum microarchitecture requirement.
-https://docs.mongodb.com/manual/administration/production-notes/#x86_64

the underling requirement for the MongoDB 5.0 binary server packages is CPUs with AVX instructions. These are broadly Sandy Bridge or newer Intel CPUs, but there is a caveat:

Not all CPUs from the listed families support AVX. Generally, CPUs with the commercial denomination Core i3/i5/i7/i9 support them, whereas Pentium and Celeron CPUs do not.

- https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2

What does this mean for the mongo image?  We currently consume the apt packages and windows downloads as provided by upstream and have no plans to compile them from source.

(I've proposed https://github.com/docker-library/mongo/pull/491 which introduces a warning during container startup for affected users.)

Added datapoint: this also affects the ARM64 builds.
https://docs.mongodb.com/manual/administration/production-notes/#arm64

MongoDB on arm64 requires the ARMv8.2-A or later microarchitecture.

is running through Proxmox

Set the cpu type to host in the hardware settings of the vm. That gives avx into the processor flags and mongodb will start.

For anyone else trying to get mongodb working on older CPUs, I went down this rabbit hole earlier today.
My approach was to build from source, as mentioned at https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2
I wasn't sure of creating a clean build environment, so I used the scripts and docker image from https://github.com/meteor/mongodb-builder with two small adjustments:

Add 'CCFLAGS=-march=nehalem' to build.sh
Adjust # CPUs in build.sh to match my machine (I used '-j 6') and adjust the --memory value in run-builder.sh similarly (I used '28g')
Specify a version of mongodb in run-builder.sh (I used '5.0.17' - values found from https://www.mongodb.com/try/download/community )

My test run took about 1h30 on my desktop machine, and I ended up with a .tgz file that looks promising:
drwxr-xr-x myuser/users         0 2023-04-26 22:52 mongodb-linux-x86_64-5.0.17/
drwxr-xr-x myuser/users         0 2023-04-26 22:58 mongodb-linux-x86_64-5.0.17/bin/
-rwxr-xr-x root/root     62211216 2023-04-26 22:52 mongodb-linux-x86_64-5.0.17/bin/mongos
-rwxr-xr-x root/root     86620528 2023-04-26 22:52 mongodb-linux-x86_64-5.0.17/bin/mongod

I haven't tested the binary itself yet, so will update this comment after I have done so tomorrow...

@jmhunter: did you finally get it to work?

@jmhunter: did you finally get it to work?

Hi @sputnick-dev - yes, my steps above worked perfectly for me; or at least mongodb is now running in its container with no issues (I'm still working on the application that uses it..)

What I've done to run on old cpu:
apt-get install -y mongodb-org=4.4.16 mongodb-org-server=4.4.16 mongodb-org-shell=4.4.16 mongodb-org-mongos=4.4.16 mongodb-org-tools=4.4.16

That looks like an installation of a specific (older) MongoDB version from APT sources. My approach was to use version 5 via docker, but replace the binary shipped in the docker container with a version I compiled myself with the correct flags for my CPU - hence my use of https://github.com/meteor/mongodb-builder .

Hi,
we compile binaries and build images without AVX requirement for our needs.
If those artifacts suit you, give it a try.
https://github.com/flakybitnet/mongodb-docker


📝💼 adding template files for magento

These changes are in prep for integrating Magento open source approval process into Adobe's internal one. Would like to have the template files that we want Magento projects to generally use handy in this repo as well.

contributing guidelines shamelessly copied from magento/magento2
OSL license
copying.txt from the magento2 repo
added example magento copyright header to license header doc.

Especially interested in @dmanners' take on this to make sure I have this right 😄

It looks good to in the sense that the files are the ones from our repo but it does remind me that I should update these files to match our new beginners guides from https://github.com/magento/magento2/wiki/Getting-Started

@dmanners OK, well, I can update the template files in here to reflect whatever changes end up landing. Let me know!

I have added a new PR with my initial thoughts and further questions to our devdocs writer and head of open source https://github.com/magento/magento2/pull/22951 will let you know when we get some update on this.


Add posibility to load script tag with src attribute

Hello @ramitos!, I've been seeing the extension and it's looks pretty good, but I have a problem.
I have a script tag with a src attribute that load a video player from an external JS file. It would be great if the extension could be load this.
Thanks so much!

I have this on my todo list as it's a feature we need in our product as well. It should be simple to implement; I anticipate having something ready in the next few days - will update soon.

Any updates?

Any updates?


Add new routing request parameter "maneuvers=true/false"

"maneuvers" parameter specifies whether maneuver element is included into step element or not.
Default value is false.
In json response, every maneuver element consists of the following elements:
location - The coordinate of the point where a maneuver takes place.
bearing_before - Specifies an azimuth angle (in degrees) of the direction right before the maneuver.
bearing_after - Specifies an azimuth angle (in degrees) of the direction right after the maneuver.

Done in 0f3331736962dc80106211cd567e5b1119b30359


CM-410: Add page scroll useEffect

Jira Ticket:
CM-410
Jira Ticket URL:
https://bcparksdigital.atlassian.net/browse/CM-410
Description:

Made the find-a-park page scroll to the top every time the pagination clicked

Please see the comment I added to the ticket.

Changed the scroll position

does not scroll to the top of the page (including the Headline, Header, and so on)
just to TextField with the ref

if we need to the Top Page
you could use this method, this takes position to the viewport
  const handlePageChange = (event, value) => {     setCurrentPage(value)     const dims = searchRef.current.getBoundingClientRect();     window.scrollTo({       behavior: 'smooth',       top: dims.top,     });   }

does not scroll to the top of the page (including the Headline, Header, and so on) just to TextField with the ref

if we need to the Top Page you could use this method, this takes position to the viewport
const handlePageChange = (event, value) => {
    setCurrentPage(value)
    const dims = searchRef.current.getBoundingClientRect();
    window.scrollTo({
      behavior: 'smooth',
      top: dims.top,
    });
  }

Oh, I changed the position based on the feedback from Jane and Mike 🙂 Details are in this ticket.

This isn't working reliably for Safari and Firefox.

This isn't working reliably for Safari and Firefox.

Good catch, thanks! Seems there are some differences in scrollIntoView between browsers.
Added polyfill and works fine on any browser.


Should report an error if we set wrong auth info to jira source.

Description
When we setting a jira source, we want to know if the endpoint as well as the auth info is correct.
Describe the solution you'd like
I suggest that lake should return specific error info when something is wrong. For example:

Tell if the endpoint is resolvable.
Tell if the endpoint is connectable.
Tell if the endpoint is a valid jira api server.
Tell if the auth info is right.

Has the Feature been Requested Before?
No

So we have something for this now in the routes called: TestConnection.
GET /github/test
func (plugin Github) ApiResources() map[string]map[string]core.ApiResourceHandler {
	return map[string]map[string]core.ApiResourceHandler{
		"test": {
			"GET": api.TestConnection,
		},

Here is the implementation
/*
GET /plugins/github/test
*/
func TestConnection(input *core.ApiResourceInput) (*core.ApiResourceOutput, error) {
	ValidationResult := core.ValidateParams(input, []string{"endpoint", "auth"})
	if !ValidationResult.Success {
		return &core.ApiResourceOutput{Body: ValidationResult}, nil
	}
	endpoint := input.Query.Get("endpoint")
	auth := input.Query.Get("auth")
	tokens := strings.Split(auth, ",")
	githubApiClient := tasks.CreateApiClient(endpoint, tokens)

	// PLEASE NOTE: This works because GitHub API Client rotates tokens on each request
	for i := 0; i < len(tokens); i++ {
		res, err := githubApiClient.Get("user/public_emails", nil, nil)
		if err != nil || res.StatusCode != 200 {
			logger.Error("Error: ", err)
			return &core.ApiResourceOutput{Body: core.TestResult{
				Success: false,
				Message: core.InvalidConnectionError + fmt.Sprintf("Check token: %v or endpoint %v", tokens[i], endpoint),
			}}, nil
		}
		githubApiResponse := &ApiUserPublicEmailResponse{}
		err = core.UnmarshalResponse(res, githubApiResponse)
		if err != nil {
			logger.Error("Error: ", err)
			return &core.ApiResourceOutput{Body: core.TestResult{Success: false, Message: core.UnmarshallingError}}, nil
		}
	}
	return &core.ApiResourceOutput{Body: core.TestResult{Success: true, Message: ""}}, nil
}

Actually, jira already has this too: plugins/jira/api/jira_connections.go

all plugins have test connection. I need to update docs.

Thank u for your replies.
Just a further question, will it be better to test connection when setting jira auth info automatically? I just don't know why we can set a wrong auth info to jira plugin(without auto check).

@narrowizard
Adding a new source is a plain simple operation which can be performed even without internet connection.
TestConnection on the other hand depends only internet connection.
Even if we combined these two operations, the token was verified and stored into database, they still can be expired afterward, so, what is the point of doing this?
Seperate these two operations provide more flexibility for clients IMO.

Now we check jira auth info using the test api. Close this issue now.
But the error info returned by jira test api is not concrete enough. I will try to create a PR for that.


Migrate to CircleCI 2

Update CircleCI config to 2
Update Node.js testing environment to current LTS (node 4 has been dropped)
Use yarn instead of npm and add yarn.lock
Install missing eslint-plugin-react peer dependency of @segment/eslint-config

Ref LIB-370

Codecov Report

Merging #7 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #7   +/-   ##
=======================================
  Coverage   88.88%   88.88%
=======================================
  Files           1        1
  Lines          27       27
  Branches       10       10
=======================================
  Hits           24       24
  Misses          3        3

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 83aac34...308f55f. Read the comment docs.


 It's unpredictable where they load comments from one page to another. I've tried several times. I'll take a look at this again, but it'll have to wait a bit until I've got more time.

I've tried quite a bit, and nothing ever sticks. I'd suggest looking for an extension that specifically addresses facebook, or a style to use with the "stylus" extension.


refactor(sdk): make filesync stats use Paths as keys rather than strs, for type-safety

Description
We don't have a consistent conceptual type for the keys of wandb.filesync.Stats.file_stats:

For run-files, the keys are "save names" ~= relative file-paths. (see here)
For artifact-files, the keys are local filesystem paths. (see here)

Currently, we never try to access nonexistent file_stats keys, but I think that's just good luck: it's easy to (not notice)-and-then-break this invariant; we don't have tests that catch when that happens. (see #4786)
I think a significant chunk of the problem here is that save_name and path both have type str, despite representing different things ("logical location of a file within a run ~= sequence of non-empty strings" vs "path to an actually-existing file on the user's filesystem"), and we don't carefully distinguish between the two flavors. I opine that:

When we're talking about a "path to an actually-existing file on the user's filesystem," we should use a Path, since that's... what Path is mean to represent.
Path is the appropriate key-type of Stats.file_stats. (We can't use SaveName, since two artifacts could contain unrelated files with the same SaveName, and then their stats would collide.)

Testing
The only functional changes in this PR are:

In StepChecksum and UploadJob, a path-str is converted to a Path.
In Stats, that Path is turned back into a str before being passed to some library functions that accept strs.
Also in StepChecksum and UploadJob, we use the job's path as a stats-key instead of its save_name.

Problems I would expect could manifest from this:

"Sometimes str(Path(x)) != x." I ran experiments including weird ASCII control characters and all sorts of punctuation; the only time I observed str(Path(x)) ~= x is that on Windows / gets normalized to \; which won't affect the consumers of the manipulated string (is_wandb_file and str.startswith("media")).
"Sometimes the same filesystem-path is uploaded to a run under multiple different save-names, so keying off the Path instead of the SaveName will cause collisions." I wouldn't expect this to happen often, and I think it would be okay for the stats to be slightly off when it does.

(I also added some unit tests for Stats, just in case.)

This isn't worth me doing: I keep making very plausible-looking PRs for this and then discovering ways they'll still cause bugs.


GEKPLS Extra Points?

What are extra points in the context of GEKPLS? The documentation simply says "Number of extra points per training point" What is an extra point and when should I enable them?
Thanks,
Kevin

You will find some answers in the paper (the link is broken in the SMT documentation).

extra_points is the number of additional nearby points that are sampled to make a first order Taylor approximation.


Provide a way to populate <platform>/env

The buildpack spec describes the way that environment variables get to buildpacks during build is by populating <platform>/env.  There is also a proposal to extend this to detect.
Currently there is no way to populate this part of the filesystem during pack build and there should be.

I assume you mean "during pack build"?

This is available using pack build --env-file as of<EMAIL_ADDRESS>


Dependency audit

Now that we've pulled the core logic into @miragejs/server we need to audit our dependencies. For example I don't think we need pretender as a dependency anymore.

https://github.com/miragejs/ember-cli-mirage/pull/1820 closes


absence of a export.js in a template folder -> Unable to load template at path .... Path should consist of [template folder name]/[template name]...

linkml.yaml runs to completion. Error appears when loading main.html or changing templates.

Sorry, I'm a dunce!  This is a warning about an "export.js" file that is expected to sit in each template folder - even if it has nothing in it, besides "var EXPORT_FORMATS = {}".

Ok to close this?

Closing as I believe this is resolved.


[stable/prometheus] Cannot configure alertmanagers if alertmanager is not enabled

Describe the bug
I'm a little bit unsure if this should be considered a bug or not but I decided that it was a bug. It is not possible to set "server.alertmanagers" if "alertmanager.enabled" is not true. I don't see how a local Alertmanager cluster should be a prerequisite for configuring alertmanagers in Prometheus Server.
Version of Helm and Kubernetes:
3.0.0, 1.14
Which chart:
stable/prometheus
What happened:
I cannot set alertmanagers for Prometheus Server unless the chart is configured to install Alertmanager.
What you expected to happen:
I expect that server.alertmanagers will set static alertmanager config.
How to reproduce it (as minimally and precisely as possible):
Set server.alertmanagers to something while disabling the installation of alertmanager.
Anything else we need to know:
The way this is implemented makes zero sense as you'd never want to use static alertmanager configuration (server.alertmanagers) if you have a local installment (which you always have with alertmanager.enabled). Then you'd always want to find Alertmanagers with the SD config options.

Can someone look into this? Otherwise I will create a PR myself probably.