OIDC implicit/token profile

Evaluate the current OIDC support in CAS to determine whether implicit profile can be supported. It may already be, but we’ll need to make sure and document nuances. Discuss with @leleuj

It should work as the OAuth 2.0 support handles it, but I need to test it to be sure.

I do some tests and it's not yet supported :
I use cas-gradle-overlay-template with 5.0.3-SNAPSHOT CAS version because of #2333
I add :
compile "org.apereo.cas:cas-server-support-oidc:${project.'cas.version'}"
compile "org.apereo.cas:cas-server-support-json-service-registry:${project.'cas.version'}"
In OIDC doc about implicit flow (http://openid.net/specs/openid-connect-implicit-1_0.html#RequestParameters), the response_type request parameter is “REQUIRED. This value consists of id_token and token, as a space-delimited list.”
With a service :
servimplicit-1.json :
{
"@class" : "org.apereo.cas.services.OidcRegisteredService",
"clientId": "servimplicit",
"serviceId" : "^https://localhost:8443/test",
"signIdToken": true,
"name": "servimplicit",
"id": 1,
"evaluationOrder": 100
}
A GET on https://cas.cocktail.fr:8443/cas/oidc/authorize?response_type=id_token token&client_id=test&redirect_uri=https://localhost:8443/test&scope=openid profile&state=af0ifjsldkj&nonce=n-0S6_WzA2Mj
log "ERROR [org.apereo.cas.web.controllers.OidcAuthorizeEndpointController] - "

My use case : A angular front requesting a java/rest back-end. Front use a JWT to carry auth information to back-end. Today front obtain JWT in a non standard way. I want to use CAS as an OIDC server to obtain this JWT.
I am ok to test implicit flow as soon as implemented.
I will try to have a look on code but not sure I can make a pull request because of lack of time and competence but I will try...

Thank you @raymondBourges I adjusted the milestone to note that this will be covered in 5.1.

I saw some commits yesterday.
I test on master and it seems ok. Great job :)
I will test deeper asap.
Thanks

2 problems against specification:
With a service servimplicit-1.json:
{
"@class" : "org.apereo.cas.services.OidcRegisteredService",
"clientId": "servimplicit",
"serviceId" : "^https://localhost:8443/test",
"signIdToken": true,
"implicit": true,
"name": "servimplicit",
"id": 1,
"evaluationOrder": 100
}
A GET on https://cas.cocktail.fr:8443/cas/oidc/authorize?response_type=id_token token&client_id=servimplicit&redirect_uri=https://localhost:8443/test&scope=openid profile&state=af0ifjsldkj&nonce=n-0S6_WzA2Mj
I obtain this jwt PAYLOAD:
{
"jti": "2d6c294b-638f-4c67-8b6e-6c0de9e3dd08",
"iss": "http://cas.cocktail.fr:8443/cas/oidc",
"aud": "servimplicit",
"exp":<PHONE_NUMBER>,
"iat":<PHONE_NUMBER>,
"nbf":<PHONE_NUMBER>,
"sub": "casuser",
"amr": [
"AcceptUsersAuthenticationHandler"
],
"state": "af0ifjsldkj",
"nonce": "n-0S6_WzA2Mj",
"preferred_username": "casuser"
}
according http://openid.net/specs/openid-connect-implicit-1_0.html#IDToken

iss should begin with "https" and not "http"
at_hash is required

Thanks

Excellent. Thanks for the feedback. The issuer is controlled by you via settings I believe. But at_hash , yes that should be fixed.

You are right about issuer. It's a error in my settings. Excuse me.

No worries. at_hash should now also be functional. Continue testing please :)


Add a reference to the colorize gem.

First of all, this gem is exactly what I was looking for. Very very useful. Thanks a lot.
I didn't see any reference to the colorize gem in the readme, so I wanted to mention it in the issue.
https://github.com/fazibear/colorize
You can use the colorize gem option as follows.
config/initializers/colorize_logs.rb
colorize_logs_formatter = ColorizeLogs::Formatter.new

colorize_logs_formatter.configure do
  match(/Started/) do |msg|
    msg.colorize(color: :black, background: :yellow, mode: :bold)
  end

  match(/Processing by/) do |msg|
    msg.colorize(color: :white, background: :light_blue, mode: :bold)
  end

  match(/Rendering layout/) do |msg|
    msg.blue
  end

  match(/Rendering.*within layouts/) do |msg|
    msg.blue
  end
end

::Rails.logger.formatter = colorize_logs_formatter

The output will be as follows.

This is actually not an issue, so I will close it. Thanks !

Also, the list of supported colors and modes can be found here.

https://github.com/fazibear/colorize/blob/51c3f67fdd162aa604f653954c871992c6994052/lib/colorize/class_methods.rb

module Colorize
  module ClassMethods
...
    @@color_codes ||= {
      black:         30,
      red:           31,
      green:         32,
      yellow:        33,
      blue:          34,
      magenta:       35,
      cyan:          36,
      white:         37,
      default:       39,
      light_black:   90,
      light_red:     91,
      light_green:   92,
      light_yellow:  93,
      light_blue:    94,
      light_magenta: 95,
      light_cyan:    96,
      light_white:   97
    }

    @@mode_codes ||= {
      default:          0, # Turn off all attributes
      bold:             1,
      dim:              2,
      italic:           3,
      underline:        4,
      blink:            5,
      blink_slow:       5,
      blink_fast:       6,
      invert:           7,
      hide:             8,
      strike:           9,
      double_underline: 20,
      reveal:           28,
      overlined:        53
    }
...
  end
end

@kohheepeace  Hey, sorry for my late reply. Thanks that you found this gem useful. Also, thanks for sharing your suggestions about improving/highlighting lines using different approach.

👍


feat: add relayer command

Overview

Closes https://github.com/celestiaorg/orchestrator-relayer/issues/48
Depends on the other PRs.
Checklist

[ ] New and updated code has appropriate documentation
[ ] New and updated code has new and/or updated testing
[ ] Required CI checks are passing
[ ] Visual proof for any user facing features like CLI or documentation updates
[ ] Linked issues closed with keywords

Codecov Report

Merging #151 (a1c76fb) into main (dc40f9b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #151   +/-   ##
=======================================
  Coverage   48.74%   48.74%
=======================================
  Files          17       17
  Lines        1155     1155
=======================================
  Hits          563      563
  Misses        528      528
  Partials       64       64

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

@evan-forbes done. There is an issue with TempDir in the CI which happens from time to time... I'm looking into, can we merge this one even if it's not solved? I will create an issue specifically for it

aproov :shipit:


Can not typing Chinese

Can not typing Chinese

hi @senlinmuvs
What operating system are you using?

There is no further information.
For cleaning up old issues, I close this. You can reopen it anytime if it's needed.


Implement cli.js

Implement cli.js, which is the main controller of the cypress-parallel-rs app.

Done
https://github.com/hiroyone/cypress-parallel-rs/commit/0934cbb066b4ca0ba86af45e2d96e9c3ea7b3d79


Autobuild decision

when I activate the decision the options appear invalid
said "ec_open_autobuild_settings"
the "options "ARoAI_economy_events.6.1a" etc...
[17:45:12][pdx_persistent_reader.cpp:252]: Error: "Failed to read key reference: si_economic_system_automation: si_economic_system_automation, near line: 1

ops I missed this one, I have to create line codes

Some kind of conflict with Improved Automation. You seem to use an older version of it. I just tried the latest version and it's totally fine.


Feature/folder support

Here is my PR to address issue #108 I filed earlier.  I made an attempt to write tests but I couldn't figure out how to get the cloudbees plugin installed in the test instance of jenkins, so the test is included but ignored for now.  I also included a manual test you can run against an external instance of jenkins which demonstrates how the APIs work.
I've confirmed that all tests still pass, and I've confirmed that my project works as well, including the new folder features (which you can check out here if you are curious):
https://github.com/terabyte/stashbot/commit/ab99ca7aed05616a0b44d6ecc00796a9baf98575
My change also includes a "fix" for the "shade" change - apparently package names with dashes in them work when "shaded" internally but fail when an external dependency tries to mention them (for example, if you return a guava "Optional" object with dashes in its package name).  Pretty subtle.
If there is anything I can do to make this change better or assist with any cleanup, please let me know.

Many thanks for merging my change! =D


Update repository tool document

The repository tool documentation should be synced with the latest version of the codebase.  For example, instances of write() should be changed to writeall().  Also consider integrating the changes introduced in the Docker demo document, which includes a section on blocking malicious updates.

Addressed in PR https://github.com/theupdateframework/tuf/pull/381


Fix: publish latest seam os routes

Thought I needed routes, turned out I just needed to update the client? Closing in favor of #136.


[Task]: Support embeddings using ML models in MLTransform

What needs to happen?
doc - https://docs.google.com/document/d/1En4bfbTu4rvu7LWJIKV3G33jO-xJfTdbaSFSURmQw_s/edit#heading=h.wskna8eurvjv discusses on supporting generation of embeddings in MLTransform.
This would be an umbrella issue to track different features/tasks required for embeddings in MLTransform.
Issue Priority
Priority: 2 (default / most normal work should be filed as P2)
Issue Components

[X] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam YAML
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

Tasks needs to be done after PR https://github.com/apache/beam/pull/29564 is merged.

Add set_model_handler method
Support Dead letter queue for RunInference and asses its compatibility with tft transforms.


TransAttention performance

Thanks for the great work.
I have a question about how to reproduce TransAttention performance on CUB-200 (Table 5). I got much higher performance by changing https://github.com/vasgaowei/TS-CAM/blob/aeb823ee097ce0c5594b8cb10d14c0aa03652df3/lib/models/deit.py#L62 to
cams = cams.repeat((1, 200, 1, 1)):
Cls@1:0.803	Cls@5:0.948
Loc@1:0.690	Loc@5:0.816	Loc_gt:0.859
wrong_details:3998 1139 0 556 96 5
And, I got Loc@1:0.154	Loc@5:0.177	Loc_gt:0.183 for TransCAM, seems there's a mistake in the table. Personally, I feel it's unfair to compare with TransCAM without tuning CAM_THR to its optimal, I can get Loc@1:0.333 Loc@5:0.379	Loc_gt:0.387 by setting CAM_THR to around 0.8, I wonder your thoughts here.

Hi, thanks for your attention and your reviews.  The following are my answers.

You got a much higher performance by changing  cams = cams * feature_map to cams = cams.repeat((1,200,1,1)). I try to answer your question from two views.

Firstly, the localization accuracies are also still lower than the TS-CAM.
Secondly,  there are two version implementations for TransAttention. For the first one, we just fine-tune Deit-S on CUB-200-2011 dataset,  predict the image classification logits based on Class Token, then calculate the cross-entropy loss between the logits and ground-truth labels.   For the second implementation, we get the image classifications logits based on average pooling all the Patch Tokens but excluding Class Token. Our results in Table 5 in our paper are from the first implementation. And your result is from the second implementation.

As for your second question,  you got higher performances for TransCAM, with higher CAM_THR. However, the localization accuracies are still much lower than TS-CAM, and also lags behind the CNN-CAM method. So, this doesn't affect the conclusion. Also, for a fair comparison,  we try to settle the CAM_THR the same.


'Clothing' of survival doesn't give +2 AC

My group noticed this a while back and I thought it might have been fixed by now but the description on the various clothings of survival indicates that it should give +2 AC but it does not.  It does give the increased save rolls.  We saw this on a barbarian clothing and monk clothing in the past.  My current playthrough has a wizard and monk with the clothing and the bug persists.

They indeed won't stack with any other source of natural armor. It won't get fixed as fix would require players to RESPEC. Don't use them.

Sounds good.  Thanks


Consider GraphQL over REST API

Simplicity of REST API is great until:

Responses are large enough that getting only subsets becomes important.
Round-trips start to matter and some batching strategy is necessary.

Both lead to custom & non-composable solutions. For these reasons I would like to propose to consider https://graphql.org/ based API because:

You can query exactly what application needs / expects.
All operations are composeable and can be bundled into single request as necessary.
There is great tooling available for it.

It is also worth considering how IPLD selectors fit or whether they could be a better solution than REST or / and GraphQL

E.g. #1 is perfect example of needing to batch which GraphQL supports out of the box.

Would be good to run this idea by (a) Pinning  Services (b) go-ipfs/js-ipfs
Quick take: In this specific domain (simple CRUD for managing pins) I don't believe there will be use case for mixing operations (any examples?), but I agree on  batch check  (#1). Also  pagination is missing from v0.0.1 of existing spec – filled https://github.com/ipfs/pinning-services-api-spec/issues/12 for tracking that separately.
The old thread includes some feedback from @bonedaddy  about representing this API over gRPC (Temporal looked into using go-swagger + grpc-gateway). I see people are successful with querying  graphQL API over gRPC, but it is hard for me to tell if it makes things easier or harder for non-HTTP representations – are there any case studies we could look at?

Would be good to run this idea by (a) Pinning Services (b) go-ipfs/js-ipfs

I think there are some relevant questions asked here https://github.com/ipfs/pinning-services-api-spec/issues/2#issuecomment-652597003

Quick take: In this specific domain (simple CRUD for managing pins) I don't believe there will be use case for mixing operations (any examples?), but I agree that batching status checks would be useful (#1). Also, pagination is missing from v0.0.1 of the spec – filled #12 for tracking that separately.

Once scheduler is introduced into the system batching of queued operations becomes relevant. For instance once node goes offline it may accumulate bunch of pin, delete, maybe even status requests and ability to fulfill them in a single request would be fairly convenient. However if each operation allowed batching of sorts win probably will be negligible, however nice thing about GraphQL is that it's all composable so you get batching for free with an ability to query specific fields.

The old thread includes some feedback from @bonedaddy about representing this API over gRPC (Temporal looked into using go-swagger + grpc-gateway). I see people were successful with querying graphQL API over gRPC

I'm not familiar with gRPC and from a glance I do not really see a reason for creating gRPC layer just to add GraphQL over it, that is unless system already had a gRPC layer and GraphQL introduced a querying mechanism.

but it is hard for me to tell if it makes things easier or harder for non-HTTP representations – are there any case studies we could look at?

There are some case studies here https://www.graphql.com/case-studies/
I also have good experience building both GraphQL server and client, would not have raised this otherwise.
Could you elaborate on what you mean by "easier or harder for harder for non-HTTP representations"
GraphQL services are typically served over HTTP, that is not strictly necessary but I suspect pool of libraries to use with other transports to be smaller.


Improve build

The TinyPICO board definition includes a ARDUINO_TINYPICO macro, so there's no need to use another #define.

Support customizing the  build using platformio_override.ini, which is an approach I've copied from WLED: https://github.com/Aircoookie/WLED/blob/master/platformio.ini

Some other minor refactors.

If this is OK, can you add the hacktoberfest-accepted label, please?


Option to disable 'getjson' function.

I see that #167 introduces the getjson function. While I can see the utility of the function, this opens up a huge security vulnerability if the provided jsonpath is not trusted. A user could use the getjson function to make nearly unlimited HTTP requests.
Could you add an option to the configuration to disable this feature? Thanks.

The option should be disabled by default and require configuration to enable
Option.ALLOW_HTTP_GET

@kallestenflo Considering the "not intended to be merged" in the commit message of https://github.com/mgreenwood1001/JsonPath/commit/b919644425613279e01f08273767d8d23c6b011c and the latest comments on #167 (https://github.com/jayway/JsonPath/pull/167#issuecomment-185968312), I wonder if we should simply revert https://github.com/mgreenwood1001/JsonPath/commit/b919644425613279e01f08273767d8d23c6b011c. Or do you definitely want to keep the function?

I agree that it can be dropped.

Okay, I'll put up a PR.


Fix for crash when height or width is nil

This PR fixes the issue of height/width being nil in line no 128 of RCTImagePickerManager.m .
   [self _dismissPicker:picker args:tempImageTag ? @[tempImageTag, height, width] : nil];
Fixes#20411
Test Plan
To verify the fix , please make the changes to make either height, width or both nil
in - (void)imagePickerController:(UIImagePickerController *)picker didFinishPickingMediaWithInfo:(NSDictionary<NSString *, id> *)info function of RCTImagePickerManager.m , run the code , you will see the error saying , one of the argument is nil from the array .

Now run the code with the fix , it will not crash .
Release Notes:
[IOS][BUGFIX][RCTImagePickerManager]Fix for crash when height or width or both are nil .
[IOS][BUGFIX][RCTImagePickerManager]Change in RCTImagePickerManager to handle crashes if height/width is nil .
Issue number - https://github.com/facebook/react-native/issues/20411

Warnings

:warning:

:clipboard: Release Notes - This PR may have incorrectly formatted Release Notes.

  Generated by :no_entry_sign: dangerJS


Error status code.

Is it possible to get error http status code?

I was looking for the same feature. Unfortunately the http status code gets removed from the error object in this function, except Salesforce did not return a error in the response body: https://github.com/jsforce/jsforce/blob/a3ce63633f92672edcb536bbc22b6afcf2f592b2/lib/http-api.js#L250

triaging old issues...
you can see the request status code by setting the log level to debug when creating the connection:
https://jsforce.github.io/jsforce/types/connection.ConnectionConfig.html
https://github.com/jsforce/jsforce/blob/af8a10e84557d95e20a62dae37e9dbf1e4d50fa8/src/http-api.ts#L120
some weird errors might include the status code, IIRC this was added to catch API returning HTML:
https://github.com/jsforce/jsforce/blob/af8a10e84557d95e20a62dae37e9dbf1e4d50fa8/src/http-api.ts#L312C1-L320C13


--add-override no longer works

Describe the bug
running /usr/local/outset/outset --add-override  doesn't add the override as expected
however
running /usr/local/outset/outset --add-overide  returns
DEBUG: Adding / to overide list
To Reproduce
/usr/local/outset/outset --add-override  returns nothing
Expected behavior
/usr/local/outset/outset --add-override  should return
DEBUG: Adding / to ove(r?)ride list

can you check out this release and let me know if there's any issues.
https://github.com/macadmins/outset/releases/tag/v<IP_ADDRESS>15

Yes, that has fixed it.
Thanks!

cool - I'll see if there are any other minor bugs and then do a release after the weekend.


IFRAME >_<

There's a lot of empty space that can be used to view banner links nicely instead of FILLING UP THE ENTIRE PAGE AS AN IFRAME.

Fixed in this commit


lighteval support after checkpoint, UX refactor

Info

Install lighteval from https://github.com/eliebak/lighteval/tree/current-nanotron otherwise it will not work
Follow up of the s3upload PR220
in the launcher.py there is some path to examples/smollm which doesn't exist yet (will add it in another PR very soon)

Changes

Automated Lighteval Job Execution

Triggers after each checkpoint save (locally or on S3)
Implemented via:

self.s3_mover.post_upload_callback (S3 enabled)
self.post_checkpoint_callback (local)

Results logged to Wandb

Enhanced Wandb

Store ID and project in general args
Lof tokens in the x axis instead of steps
Enables logging for both training and evaluation

New scripts for users: launcher.py and create_config.py

Fix model parameter counting

New function: model_config.get_llama_param_count()
Updated get_flops() method:

Added rms norm
Corrected block_compute_costs:

Included layer norm and GQA calculation for FLOPS

Customizable Slurm Folder

Separate modifications for training and evaluation jobs

Usage Instructions
create_config.py

Modify the Python file as needed
Run: python create_config.py --save_path <path_to_save>
Optional: Add --launch to execute immediately

launcher.py
Basic usage:
python launcher.py --logs_path <path_to_log> --run <name_of_the_run>

Creates timestamped folder in logs_path/run
Numbering: Starts at 001 for first run

Additional options:

Slurm: Add --slurm --nodes <number_of_node>
Override config arguments:
python nanotron/launcher.py [other_args] --override KEY1=VALUE1 KEY2=VALUE2 ...

Minor Changes

Changed 'G' to 'B' in human format function
Lighteval branch fixes:

Added evaluation to Wandb
Set trust_remote_code=True globally
Created repository for uploading details and results

Recommended Workflow

Create a new folder for each project
Copy and customize in the folder:

launcher.py
create_config.py
slurm folder (if using Slurm)

Fancy prints ✨

Command
python launcher.py --base-config "smollm-360M-4nodes" --run "smol-360M" --override "tokens.micro_batch_size=8" "optimizer.learning_rate_scheduler.learning_rate=1e-3" --slurm --nodes 4

Output

⇄ Applied overrides:
  tokens.micro_batch_size=8
  optimizer.learning_rate_scheduler.learning_rate=1e-3

🏋  Model Parameters:
┌───────────────────────┬────────────────────────┐
│ Total Parameters      │                   362M │
│ Layers                │                     32 │
│ Attention Heads       │                     15 │
│ Hidden Size           │                    960 │
│ Intermediate Size     │                   2560 │
│ Context Length        │                   2048 │
│ Tokenizer             │ HuggingFaceTB/cosmo2-t │
│ Vocab Size            │                  49152 │
└───────────────────────┴────────────────────────┘

🎛 Parallelism Configuration:
┌───────────────────────┬────────────────────────┐
│ Nodes                 │                      4 │
│ Total GPUs            │                     32 │
│ Data Parallel (DP)    │                     32 │
│ Pipeline Parallel (PP)│                      1 │
│ Tensor Parallel (TP)  │                      1 │
└───────────────────────┴────────────────────────┘

📙 Training Configuration:
┌───────────────────────┬────────────────────────┐
│ Total Tokens          │                   629B │
│ Global Batch Size     │              1,048,576 │
│ Batch Size (per GPU)  │                 32,768 │
└───────────────────────┴────────────────────────┘

📊 Learning Rate Schedule:
┌───────────────────────┬────────────────────────┐
│ Initial LR            │               1.00e-03 │
│ Warmup Style          │                 linear │
│ Warmup Steps          │                   5000 │
│ Decay Style           │                 1-sqrt │
│ Decay Start Step      │                 500000 │
│ Decay Steps           │                 100000 │
│ Final LR              │               0.00e+00 │
└───────────────────────┴────────────────────────┘

🔧 Optimization Configuration:
┌───────────────────────┬────────────────────────┐
│ Optimizer             │     AdamWOptimizerArgs │
│ Weight Decay          │               1.00e-02 │
│ Gradient Clipping     │                   1.00 │
│ Adam Epsilon          │               1.00e-08 │
│ Adam Beta1            │                   0.90 │
│ Adam Beta2            │                   0.95 │
│ ZeRO Stage            │                      0 │
│ FP32 Grad Accumulation│                   True │
└───────────────────────┴────────────────────────┘

🚀 Slurm job launched with id=8552705
    🤖 Slurm Configuration Details:
        qos: high
        gpus_per_node: 8
        cpus_per_task: 88

    📁 Log structure:
    logs/smol-360M/
    └── run001_2024-09-03_05-45-23/
        ├── config/
        ├── launch-script/
        ├── slurm-logs/
        └── evals/
            ├── launch-config/
            └── logs/

Hello, thanks for the PR, those are very useful features to have !
Some stuffs to solve before merging. As well, can you run pre-commit to comply with current coding style please ?
Plus, before merging this PR, we need to first merge #220 into main, and update this branch with the merge @zzhhjjj @xrsrke

What's the reason we have to "Install lighteval from https://github.com/eliebak/lighteval/tree/current-nanotron otherwise it will not work"

What's the reason we have to "Install lighteval from https://github.com/eliebak/lighteval/tree/current-nanotron otherwise it will not work"

I changed the installation to https://github.com/huggingface/lighteval/tree/nanotron-compatible in the .toml file. It's an older version of lighteval that work with the current code, at the time i made the change lighteval was changing a bit so used an older commit that was the one for the FW ablation. I (or other ppl) can update to the code to the current version after :)

Thanks for the review, made the changes! :) It launch a slurm job using run_slurm_one_job for the evaluation here if no s3 and here

in your config the checkpoint_path is set to null resume_checkpoint_path: null that's why you've got this error


Reconfiguring matplotlib

Addressed issue #54 . Now HGTector lets matplotlib use Agg as backend so that it can generate figures even when the computer does not have a graphical interface (e.g., ssh instead of ssh -X into a remote server).

Issue resolved (#54 ).


Getting started - uninstalling extension during walkthrough

Testing #119543
Uninstalling the extension while doing the walkthrough should probably:

Remove the entry from the "Getting Started" section.
Close the "Getting Started" editor.

Fixed since a bit ago


issue on Angular 6

Hi Expert,
I installed the latest version of ngx-gallery on Angular 6 project. I follow the basic instruction here and got following error: Can you please advise if it supports Angular 6?
ERROR TypeError: Cannot read property 'map' of undefined
at NgxGalleryComponent.push../node_modules/ngx-gallery/bundles/ngx-gallery.umd.js.NgxGalleryComponent.ngOnInit (ngx-gallery.umd.js:1361)
at checkAndUpdateDirectiveInline (core.js:10097)
at checkAndUpdateNodeInline (core.js:11363)
at checkAndUpdateNode (core.js:11325)
at debugCheckAndUpdateNode (core.js:11962)
at debugCheckDirectivesFn (core.js:11922)
at Object.eval [as updateDirectives] (ProductViewComponent.html:1)
at Object.debugUpdateDirectives [as updateDirectives] (core.js:11914)
at checkAndUpdateView (core.js:11307)
at callViewAction (core.js:11548)

That's a rxjs problem with version 6.x. Install "rxjs-compat", then it should works.
They have changed the imports.

thx @JohnnyDevNull

I did install it but still i am getting the same error

Even after installing npm i rxjs-compat in angular 6, error still exists

Is there any fix to this?


Demo-App discrepency between Kong Konnect Mesh and Kong Mesh documentation

Where is the problem?
https://docs.konghq.com/konnect/mesh-manager/service-mesh/#install-a-demo-service
What happened?
The demo-app provided in the Konnect documentation [0] is not the same application as the demo-app provided in the mesh documentation that is linked [1]. This is likely to cause confusion among users how to actually test your application
[0] https://docs.konghq.com/konnect/mesh-manager/service-mesh/#install-a-demo-service
[1] https://docs.konghq.com/mesh/latest/quickstart/kubernetes/
What did you expect to happen?
The sample application should be the same if the Konnect docs are pointing to the Kong Mesh docs as an example of how to set up an application within the mesh.
Code of Conduct and Community Expectations

[X] I agree to follow this project's Code of Conduct
[X] I agree to abide by the Community Expectations

Hi @eshih ! Thanks for submitting this feedback! I've created a PR (#8008 ) that fixes this issue. Thanks again!


Revisit Page to configure User Attribute Change Verification settings

Describe the issue:
Required to revisit page to configure User Attribute Change Verification settings

Page title should be improve
Descriptions are too long
Add grouping
Sub cases are enable even though the main cases are disable. ( ex: include upper case character, include numbers in OTP)

How to reproduce:

Login to console
Go to user attributes and stored -> Select attibutes
Select "User Attribute Change Verification"

Expected behavior:

Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: wso2is-7.0.0-rc1-SNAPSHOT- buildno: 4957
OS: [e.g., Windows, Linux, Mac]
Database: postgres
Userstore: [e.g., LDAP, JDBC]

Optional Fields
Related issues:

Suggested labels:

This feature is not available on Build #4961

This feature is not available on Build #4961  @brionmario @jeradrutnam is this expected?

Will check this and verify. There was a config rename and seems like the build #4961 doesn't have the latest framework verion.

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


QualityOnDemand r1.1 release review

Release PR or issue to review
https://github.com/camaraproject/QualityOnDemand/pull/336
Review actions
Assign this issue to yourself and follow the below list.
For any review action, review the file(s) in the issue/PR listed above.
Put comments in the above issue or PR if they concern non-changed files/text.
Put a short summary of the main review result here into the review issue.

[x] API definition files (YAML) (check version in info & servers objects)
[x] test file(s) availability
[x] changelog updated
[x] readme updated (enforce correct release number / API version naming)
[x] API readiness checklist(s)

Release actions
Assign this issue to yourself or another RM team member and follow the below list.
When done, tick the box in this issue.

[ ] API release tracker available on wiki
[ ] Review comments addressed (by Sub Project)
[ ] Release PR approved (on behalf of Release Management)
[ ] PR merged (by Sub Project codeowner)
[ ] Release created within GitHub (by Sub Project codeowner)
[ ] Release Tracker updated (with creation date of the release and the release tag link)

Additional comments

Test definitions and user stories indicate expected update for the final release

@rartych Thanks for review - I have created the release (r1.1) and updated the three release tracker pages. So you can tick of the points and close the issue.

Issues for the tbd points until r1.2:

https://github.com/camaraproject/QualityOnDemand/issues/245
https://github.com/camaraproject/QualityOnDemand/issues/341
https://github.com/camaraproject/QualityOnDemand/issues/342


Survey from URL failed to load schema on thank you page

Expected behaviour
When loading a survey from a URL, on completing the survey you should be presented with the thank you page
Actual behaviour
The thank you page fails to load as it attempts to load the survey json from file.
Steps to reproduce the behaviour
Preview from author and submit the survey
Traceback (most recent call last):
  File "/usr/local/lib/python3.4/site-packages/flask/app.py", line 1612, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/local/lib/python3.4/site-packages/flask/app.py", line 1598, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/usr/src/app/app/views/questionnaire.py", line 175, in get_thank_you
    schema = load_schema_from_params(eq_id, form_type)
  File "/usr/local/lib/python3.4/site-packages/flask_caching/__init__.py", line 674, in decorated_function
    rv = f(*args, **kwargs)
  File "/usr/src/app/app/utilities/schema.py", line 24, in load_schema_from_params
    return load_schema_file('{}_{}.json'.format(eq_id, form_type), language_code)
  File "/usr/src/app/app/utilities/schema.py", line 49, in load_schema_file
    raise e
  File "/usr/src/app/app/utilities/schema.py", line 44, in load_schema_file
    with open(schema_path, encoding='utf8') as json_data:
FileNotFoundError: [Errno 2] No such file or directory: 'data/en/2_2.json'

@jonnyshaw89 I believe this is the same as Issue #1442. If so can it now be closed as that has been fixed?

Good shout.


Push Noticications not sent to all users

Hi, We tried using the feature to send push notifications to users of the Mobile app. That feature uses the Azure AD connector to get members of the group setup in the admin app.
The Azure AD connector  is only getting  the first 100 users in the group., so not everyone is getting notified. Any way around this?

Is this in regard to some Microsoft docs article? Please provide its URL. Is this a developer,admin, or end-user question? Thanks

Thanks for contacting us. As we haven’t heard back from you, I am closing this issue. If you need further help, please reopen the issue or open a new issue.


migration cannot proceed on: debian 10

when running vendor/bin/phinx migrate:
Migration cannot proceed, use the source: /var/www/your_domain/html/db/migrations/20200219075508_drop_secret.php

https://github.com/OPSnet/Gazelle/blob/5f9da3a6d0ba6e9fc346783f3d2e40c61dc9701f/db/migrations/20200219075508_drop_secret.php#L16

As stated by @haig233, a number of our migrations check for the existence of the LOCK_MY_DATABASE environment variable. This is due to the fact that running this migrations on a production database can take a long while and tie up the database if run while the database is under load.
You can bypass this error by doing LOCK_MY_DATABASE=1 vendor/bin/phinx migrate for one-offs or using export LOCK_MY_DATABASE=1 in some more permanent fashion if you're confident you'll always check all migrations before running it (or only running migrations on an offline site).

LOCK_MY_DATABASE=1 vendor/bin/phinx migrate

I got passed that error by using that command but then i got stuck on Migration cannot proceed, use the source: db/migrations/20200427085116_index_refactor.php


[Core] Add convenience access to front/back element of List

This also catches some cases of apparently unsafe use, hence the more complex changes in modules/mono/editor/bindings_generator.cpp
See https://github.com/godotengine/godot/pull/90705#discussion_r1589985336

There's no other method that directly returns a T

Except get, which can also be said for Vector, so I don't think that really matters, and again the crash check is relevant, it prevents weird segfaults as mentioned in the OP, this change found unsafe code

In my comment I was wondering about returning a pointer or null, thus instead of
if (!blah.is_empty())
{
// can crash if you forget the `is_empty()` check
foo = blah.front().get();
}

It becomes
T * front = blah.get_front();
if (front)
{
// do something with it
}

This is a slightly different paradigm for use (and not suggested to replace all cases, because the if check may be unnecessary in bottlenecks, and there's no need to change existing complex code).
This paradigm is by definition completely safe, whereas the current method it is easy to call front()->get() and cause a crash.
I have some memory that the original paradigm is used partly because the latter is not so easy in bound languages like gdscript (as it relies on pointers).

Now uses a DEV_ASSERT to catch unsafe use

Note that many of these cases already had a CRASH_COND in the flow before, this was originally inspired by the sheer number of cases introduced by the List cleanup, they originally used foo[0] which does a check, so this shouldn't introduce bottlenecks in most of the relevant cases, I can reduce it to cases that originally had operator[] to limit that risk if desired

Now uses a DEV_ASSERT to catch unsafe use

Agree this is sensible if going with original approach, as it provides some extra protection to pick up bugs during development, as well as slightly simplifying the syntax.
CRASH_COND() could be overkill and it might be better to swap to the other paradigm in those conditions.

I'll see about splitting the use cases into cases introduced by #90705 and look at other approaches where the size is checked separately, thank you for ideas and feedback!

I'll see about splitting the use cases into cases introduced by https://github.com/godotengine/godot/pull/90705 and look at other approaches where the size is checked separately, thank you for ideas and feedback!

Yes, just to be clear, I think the PR "as is" is an improvement, having a pointer version as an alternative is something that could be considered in another PR for specific cases.

Todo:

[ ] Change the check to check just against _data, as it is supposed to always be non-null if there's at least one element
[ ] Split the cases into two for easier decision (and removal to limit it)
[ ] Replace the cases in the mono module with List<...>::Element * and remove the size check, safer and equivalent for iteration part

Hopefully later today or tomorrow, for anyone else reviewing

It might be nice to summarize the benefits of this PR. I am seeing a lot of git noise to trade front()->get() for get_front() which is defined as:
DEV_ASSERT(_data);
return _data->first->get();

The difference seems to be twofold:

Instead of crashing with a nullptr reference (because front() can return a nullptr) when _data is null, we crash with a dev assert
We can skip the condition in front() and use first directly

Is that a fair summary of the benefits of this change?
I don't like making everyone have to rebase their PRs without good reason. So it would be nice to discuss the problem this is solving instead of just the technical aspects of the solution.

That's a good summary, the referencing the pointer is potentially dangerous in some cases when the value might be elided if it's not actually referenced, that seems to be why the case in mono worked even though it shouldn't have, ensuring the check is safer, and while it doesn't get much shorter I feel that doing a full access to a specific value without a check is odd and clunky going through a level of indirection

As we don't have a clear consensus yet, and we should now focus on bugfixing for 4.3, I'm putting this on the 4.4 milestone.


Sound cuts out very often on Mac

Hello.  We've been trying to run Soundbounce 0.9 Beta for our office on a Mac Mini (Late 2012).  Our problem is the sound cuts out a lot.  Like, nearly every track for almost a full minute.  I recognize there's a known issue with this symptom related to the initial sync of the seed playlist, and that it's expected the symptom to disappear after a few minutes after the sync is done.  Well, for us, it persists for days.
When we create the room, the playlist we seed it with is pretty big.  It's 781 tracks (over 51hours).  Do we think this might be related?

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/16191779-sound-cuts-out-very-often-on-mac?utm_campaign=plugin&utm_content=tracker%2F9578624&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F9578624&utm_medium=issues&utm_source=github).

Sound cuts out for us too.  Several songs can play successfully, then they will start cutting out randomly.

Yes this is frustrating for some users and a known issue with node-spotify, an alpha library that we use on OSX and linux.  It's nothing to do with playlist size.  The fix is to move to the proper CocoaLibSpotify API, but this is a huge rework and we're hoping an OSX dev takes it on (we'll accept pull requests for efforts in this area!)

Sorry, but this is basically a wontfix until spotify release a new SDK for windows and osx, expected later in 2015


Node shutdown after seed removal (continued)

An issue related to the same was closed in November; however, this issue is not resolved.  https://github.com/colinmollenhour/mariadb-galera-swarm/issues/51
I'm using 18.06.1-ce
Below is the log from the node which went from a status of primary to non-primary after the seed was removed and then shutdown.  NOTE:  There are crossed out lines but that appears only because of the application's html formatting from which I pulled the log.
The appropriate sequence of events from the remaining nodes are different (it does not change its status from primary to non-primary) after a node is removed per: https://severalnines.com/blog/galera-cluster-recovery-101-deep-dive-network-partitioning
Thoughts on a resolution?  At this point, I do not see how this code works with swarm once the seed is removed.
...------======------... MariaDB Galera Start Script ...------======------...,
Got NODE_ADDRESS=<IP_ADDRESS>,
Starting node, connecting to gcomm://<IP_ADDRESS>,
Tailing /tmp/mysql-console/fifo...,
===|mysqld.sh|===: Recovered position from grastate.dat: a122b452-175e-11e9-8164-e62c82786503:2914,
===|mysqld.sh|===: Safe to bootstrap: 0,
Galera Cluster Node status: synced,
===|mysqld.sh|===: Node at <IP_ADDRESS> is healthy!,
===|mysqld.sh|===: Found a healthy node! Attempting to join...,
===|mysqld.sh|===: ---------------------------------------------------------------,
===|mysqld.sh|===: Starting with options: --console --wsrep_sst_auth=xtrabackup:litmusblue --wsrep-on=ON --wsrep-sst-method=xtrabackup-v2 --wsrep_cluster_name=cluster --wsrep_cluster_address=gcomm://<IP_ADDRESS> --wsrep_node_address=<IP_ADDRESS>:4567 --default-time-zone=+00:00 --wsrep_start_position=a122b452-175e-11e9-8164-e62c82786503:2914,
2019-01-13 20:15:52<PHONE_NUMBER>87424 [Note] mysqld (mysqld 10.2.18-MariaDB-1:10.2.18+maria~bionic) starting as process 46 ...,
2019-01-13 20:15:52<PHONE_NUMBER>87424 [Note] WSREP: Read nil XID from storage engines, skipping position init,
2019-01-13 20:15:52<PHONE_NUMBER>87424 [Note] WSREP: wsrep_load(): loading provider library '/usr/lib/galera/libgalera_smm.so',
2019-01-13 20:15:52<PHONE_NUMBER>87424 [Note] WSREP: wsrep_load(): Galera 25.3.24(r3825) by Codership Oy<EMAIL_ADDRESS>loaded successfully.,
2019-01-13 20:15:52<PHONE_NUMBER>87424 [Note] WSREP: CRC-32C: using hardware acceleration.,
2019-01-13 20:15:52<PHONE_NUMBER>87424 [Note] WSREP: Found saved state: a122b452-175e-11e9-8164-e62c82786503:2914, safe_to_bootstrap: 0,
2019-01-13 20:15:52<PHONE_NUMBER>87424 [Note] WSREP: Recovering GCache ring buffer: version: 2, UUID: a122b452-175e-11e9-8164-e62c82786503, offset: -1,
2019-01-13 20:15:52<PHONE_NUMBER>87424 [Note] WSREP: GCache::RingBuffer initial scan...  0.0% (         0/2147483688 bytes) complete.,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: GCache::RingBuffer initial scan...100.0%<PHONE_NUMBER>/2147483688 bytes) complete.,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: Recovering GCache ring buffer: found gapless sequence 2914-2914,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: GCache::RingBuffer unused buffers scan...  0.0% (   0/2824 bytes) complete.,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: GCache::RingBuffer unused buffers scan...100.0% (2824/2824 bytes) complete.,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: GCache DEBUG: RingBuffer::recover(): found 0/1 locked buffers,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: GCache DEBUG: RingBuffer::recover(): used space: 2824/2147483648,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: Passing config to GCS: base_dir = /var/lib/mysql/; base_host = <IP_ADDRESS>; base_port = 4567; cert.log_conflicts = no; debug = no; evs.auto_evict = 0; evs.delay_margin = PT1S; evs.delayed_keep_period = PT30S; evs.inactive_check_period = PT0.5S; evs.inactive_timeout = PT15S; evs.join_retrans_period = PT1S; evs.max_install_timeouts = 3; evs.send_window = 4; evs.stats_report_period = PT1M; evs.suspect_timeout = PT5S; evs.user_send_window = 2; evs.view_forget_timeout = PT24H; gcache.dir = /var/lib/mysql/; gcache.keep_pages_size = 1024M; gcache.mem_size = 0; gcache.name = /var/lib/mysql//galera.cache; gcache.page_size = 128M; gcache.recover = yes; gcache.size = 2048M; gcomm.thread_prio = ; gcs.fc_debug = 0; gcs.fc_factor = 1.0; gcs.fc_limit = 16; gcs.fc_master_slave = no; gcs.max_packet_size = 64500; gcs.max_throttle = 0.25; gcs.recv_q_hard_limit =<PHONE_NUMBER>854775807; gcs.recv_q_soft_limit = 0.25; gcs.sync_donor = no; gmcast.segment = 0; gmcast.version = 0; pc.announce_timeout = PT3S; pc.checksum = false; ,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: Assign initial position for certification: 2914, protocol version: -1,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: wsrep_sst_grab(),
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: Start replication,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: Setting initial position to a122b452-175e-11e9-8164-e62c82786503:2914,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: protonet asio version 0,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: Using CRC-32C for message checksums.,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: backend: asio,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: gcomm thread scheduling priority set to other:0 ,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Warning] WSREP: access file(/var/lib/mysql//gvwstate.dat) failed(No such file or directory),
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: restore pc from disk failed,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: GMCast version 0,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') listening at tcp://<IP_ADDRESS>:4567,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') multicast: , ttl: 1,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: EVS version 0,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: gcomm: connecting to group 'cluster', peer '<IP_ADDRESS>:',
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') connection established to 6a1450ce tcp://<IP_ADDRESS>:4567,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') turning message relay requesting on, nonlive peers: tcp://<IP_ADDRESS>:4567 ,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: declaring 6a1450ce at tcp://<IP_ADDRESS>:4567 stable,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: declaring 91bf1a62 at tcp://<IP_ADDRESS>:4567 stable,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: Node 6a1450ce state prim,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: view(view_id(PRIM,08a8d172,6) memb {,
08a8d172,0,
6a1450ce,0,
91bf1a62,0,
} joined {,
} left {,
} partitioned {,
}),
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: save pc into disk,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: gcomm: connected,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: Changing maximum packet size to 64500, resulting msg size: 32636,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: Shifting CLOSED -> OPEN (TO: 0),
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: Opened channel 'cluster',
2019-01-13 20:15:56<PHONE_NUMBER>75520 [Note] WSREP: New COMPONENT: primary = yes, bootstrap = no, my_idx = 0, memb_num = 3,
2019-01-13 20:15:56<PHONE_NUMBER>75520 [Note] WSREP: STATE_EXCHANGE: sent state UUID: 08f5da22-1770-11e9-9885-7f4939202bda,
2019-01-13 20:15:56<PHONE_NUMBER>87424 [Note] WSREP: Waiting for SST to complete.,
2019-01-13 20:15:56<PHONE_NUMBER>75520 [Note] WSREP: STATE EXCHANGE: sent state msg: 08f5da22-1770-11e9-9885-7f4939202bda,
2019-01-13 20:15:56<PHONE_NUMBER>75520 [Note] WSREP: STATE EXCHANGE: got state msg: 08f5da22-1770-11e9-9885-7f4939202bda from 0 (f4fe8c340a39),
2019-01-13 20:15:56<PHONE_NUMBER>75520 [Note] WSREP: STATE EXCHANGE: got state msg: 08f5da22-1770-11e9-9885-7f4939202bda from 1 (43116c1e29c2),
2019-01-13 20:15:56<PHONE_NUMBER>75520 [Note] WSREP: STATE EXCHANGE: got state msg: 08f5da22-1770-11e9-9885-7f4939202bda from 2 (9a89a2dd6d2b),
2019-01-13 20:15:56<PHONE_NUMBER>75520 [Note] WSREP: Quorum results:,
version    = 4,,
component  = PRIMARY,,
conf_id    = 4,,
members    = 2/3 (joined/total),,
act_id     = 3885,,
last_appl. = -1,,
protocols  = 0/9/3 (gcs/repl/appl),,
group UUID = a122b452-175e-11e9-8164-e62c82786503,
2019-01-13 20:15:56<PHONE_NUMBER>75520 [Note] WSREP: Flow-control interval: [28, 28],
2019-01-13 20:15:56<PHONE_NUMBER>75520 [Note] WSREP: Trying to continue unpaused monitor,
2019-01-13 20:15:56<PHONE_NUMBER>75520 [Note] WSREP: Shifting OPEN -> PRIMARY (TO: 3885),
2019-01-13 20:15:56<PHONE_NUMBER>88096 [Note] WSREP: State transfer required: ,
Group state: a122b452-175e-11e9-8164-e62c82786503:3885,
Local state: a122b452-175e-11e9-8164-e62c82786503:2914,
2019-01-13 20:15:56<PHONE_NUMBER>88096 [Note] WSREP: New cluster view: global state: a122b452-175e-11e9-8164-e62c82786503:3885, view# 5: Primary, number of nodes: 3, my index: 0, protocol version 3,
2019-01-13 20:15:56<PHONE_NUMBER>88096 [Warning] WSREP: Gap in state sequence. Need state transfer.,
2019-01-13 20:15:56<PHONE_NUMBER>82816 [Note] WSREP: Running: 'wsrep_sst_xtrabackup-v2 --role 'joiner' --address '<IP_ADDRESS>' --datadir '/var/lib/mysql/'   --parent '46'  ''  ''',
WSREP_SST: [INFO] Streaming with xbstream (20190113 20:15:56.845),
WSREP_SST: [INFO] Using socat as streamer (20190113 20:15:56.848),
WSREP_SST: [INFO] Evaluating timeout -k 110 100 socat -u TCP-LISTEN:4444,reuseaddr stdio | pv -f  -i 10 -N joiner -F '%N => Rate:%r Avg:%a Elapsed:%t %e Bytes: %b %p'  2>>/tmp/mysql-console/fifo | xbstream -x; RC=( ${PIPESTATUS[@]} ) (20190113 20:15:56.903),
/usr/local/bin/start.sh: line 413: run-upgrades.sh: command not found,
2019-01-13 20:15:57<PHONE_NUMBER>88096 [Note] WSREP: Prepared SST request: xtrabackup-v2|<IP_ADDRESS>:4444/xtrabackup_sst//1,
2019-01-13 20:15:57<PHONE_NUMBER>88096 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.,
2019-01-13 20:15:57<PHONE_NUMBER>88096 [Note] WSREP: REPL Protocols: 9 (4, 2),
2019-01-13 20:15:57<PHONE_NUMBER>88096 [Note] WSREP: Assign initial position for certification: 3885, protocol version: 4,
2019-01-13 20:15:57<PHONE_NUMBER>01184 [Note] WSREP: Service thread queue flushed.,
2019-01-13 20:15:57<PHONE_NUMBER>88096 [Note] WSREP: IST receiver addr using tcp://<IP_ADDRESS>:4568,
2019-01-13 20:15:57<PHONE_NUMBER>88096 [Note] WSREP: Prepared IST receiver, listening at: tcp://<IP_ADDRESS>:4568,
2019-01-13 20:15:57<PHONE_NUMBER>75520 [Note] WSREP: Member 0.0 (f4fe8c340a39) requested state transfer from 'any'. Selected 1.0 (43116c1e29c2)(SYNCED) as donor.,
2019-01-13 20:15:57<PHONE_NUMBER>75520 [Note] WSREP: Shifting PRIMARY -> JOINER (TO: 3885),
2019-01-13 20:15:57<PHONE_NUMBER>88096 [Note] WSREP: Requesting state transfer: success, donor: 1,
2019-01-13 20:15:57<PHONE_NUMBER>88096 [Note] WSREP: GCache history reset: a122b452-175e-11e9-8164-e62c82786503:2914 -> a122b452-175e-11e9-8164-e62c82786503:3885,
2019-01-13 20:15:57<PHONE_NUMBER>88096 [Note] WSREP: GCache DEBUG: RingBuffer::seqno_reset(): full reset,
2019-01-13 20:15:58<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 0,
joiner: => Rate:[ 158 B/s] Avg:[ 158 B/s] Elapsed:0:00:01  Bytes:  214 B
,
2019-01-13 20:15:58<PHONE_NUMBER>75520 [Note] WSREP: 1.0 (43116c1e29c2): State transfer to 0.0 (f4fe8c340a39) complete.,
2019-01-13 20:15:58<PHONE_NUMBER>75520 [Note] WSREP: Member 1.0 (43116c1e29c2) synced with group.,
WSREP_SST: [INFO] xtrabackup_ist received from donor: Running IST (20190113 20:15:58.264),
WSREP_SST: [INFO] Galera co-ords from recovery: a122b452-175e-11e9-8164-e62c82786503:2914 0 (20190113 20:15:58.270),
WSREP_SST: [INFO] Total time on joiner: 0 seconds (20190113 20:15:58.275),
WSREP_SST: [INFO] Removing the sst_in_progress file (20190113 20:15:58.279),
WSREP_SST: [INFO] Cleaning up fifo file /tmp/mysql-console/fifo (20190113 20:15:58.284),
rm: cannot remove '/tmp/mysql-console/fifo': Permission denied,
2019-01-13 20:15:58<PHONE_NUMBER>82816 [ERROR] WSREP: Process completed with error: wsrep_sst_xtrabackup-v2 --role 'joiner' --address '<IP_ADDRESS>' --datadir '/var/lib/mysql/'   --parent '46'  ''  '': 1 (Operation not permitted),
2019-01-13 20:15:58<PHONE_NUMBER>87424 [Note] WSREP: SST complete, seqno: 2914,
2019-01-13 20:15:58<PHONE_NUMBER>87424 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins,
2019-01-13 20:15:58<PHONE_NUMBER>87424 [Note] InnoDB: Uses event mutexes,
2019-01-13 20:15:58<PHONE_NUMBER>87424 [Note] InnoDB: Compressed tables use zlib 1.2.11,
2019-01-13 20:15:58<PHONE_NUMBER>87424 [Note] InnoDB: Using Linux native AIO,
2019-01-13 20:15:58<PHONE_NUMBER>87424 [Note] InnoDB: Number of pools: 1,
2019-01-13 20:15:58<PHONE_NUMBER>87424 [Note] InnoDB: Using SSE2 crc32 instructions,
2019-01-13 20:15:58<PHONE_NUMBER>87424 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M,
2019-01-13 20:15:58<PHONE_NUMBER>87424 [Note] InnoDB: Completed initialization of buffer pool,
2019-01-13 20:15:58<PHONE_NUMBER>34048 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().,
2019-01-13 20:15:58<PHONE_NUMBER>87424 [Note] InnoDB: Highest supported file format is Barracuda.,
2019-01-13 20:15:58<PHONE_NUMBER>87424 [Note] InnoDB: Starting crash recovery from checkpoint LSN=14063401,
2019-01-13 20:15:59<PHONE_NUMBER>87424 [Note] InnoDB: 128 out of 128 rollback segments are active.,
2019-01-13 20:15:59<PHONE_NUMBER>87424 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1",
2019-01-13 20:15:59<PHONE_NUMBER>87424 [Note] InnoDB: Creating shared tablespace for temporary tables,
2019-01-13 20:15:59<PHONE_NUMBER>87424 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...,
2019-01-13 20:15:59<PHONE_NUMBER>87424 [Note] InnoDB: File './ibtmp1' size is now 12 MB.,
2019-01-13 20:15:59<PHONE_NUMBER>87424 [Note] InnoDB: Waiting for purge to start,
2019-01-13 20:15:59<PHONE_NUMBER>87424 [Note] InnoDB: 5.7.23 started; log sequence number 14063410,
2019-01-13 20:15:59<PHONE_NUMBER>58112 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool,
2019-01-13 20:15:59<PHONE_NUMBER>58112 [Note] InnoDB: Buffer pool(s) load completed at 190113 20:15:59,
2019-01-13 20:15:59<PHONE_NUMBER>87424 [Note] Plugin 'FEEDBACK' is disabled.,
2019-01-13 20:15:59<PHONE_NUMBER>87424 [Note] Recovering after a crash using tc.log,
2019-01-13 20:15:59<PHONE_NUMBER>87424 [Note] Starting crash recovery...,
2019-01-13 20:15:59<PHONE_NUMBER>87424 [Note] Crash recovery finished.,
2019-01-13 20:15:59<PHONE_NUMBER>87424 [Note] Server socket created on IP: '<IP_ADDRESS>'.,
2019-01-13 20:15:59<PHONE_NUMBER>87424 [Warning] 'user' entry 'root@b9f2d8463958' ignored in --skip-name-resolve mode.,
2019-01-13 20:15:59<PHONE_NUMBER>87424 [Warning] 'proxies_priv' entry '@% root@b9f2d8463958' ignored in --skip-name-resolve mode.,
2019-01-13 20:16:00<PHONE_NUMBER>87424 [Note] WSREP: Signalling provider to continue.,
2019-01-13 20:16:00<PHONE_NUMBER>87424 [Note] WSREP: SST received: a122b452-175e-11e9-8164-e62c82786503:2914,
2019-01-13 20:16:00<PHONE_NUMBER>88096 [Note] WSREP: Receiving IST: 971 writesets, seqnos 2914-3885,
2019-01-13 20:16:00<PHONE_NUMBER>90112 [Note] WSREP: Receiving IST...  0.0% (  0/971 events) complete.,
2019-01-13 20:16:00<PHONE_NUMBER>87424 [Note] Reading of all Master_info entries succeded,
2019-01-13 20:16:00<PHONE_NUMBER>87424 [Note] Added new Master_info '' to hash table,
2019-01-13 20:16:00<PHONE_NUMBER>87424 [Note] mysqld: ready for connections.,
Version: '10.2.18-MariaDB-1:10.2.18+maria~bionic'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution,
2019-01-13 20:16:06<PHONE_NUMBER>90112 [Note] WSREP: Receiving IST...100.0% (971/971 events) complete.,
2019-01-13 20:16:06<PHONE_NUMBER>88096 [Note] WSREP: IST received: a122b452-175e-11e9-8164-e62c82786503:3885,
2019-01-13 20:16:06<PHONE_NUMBER>75520 [Note] WSREP: 0.0 (f4fe8c340a39): State transfer from 1.0 (43116c1e29c2) complete.,
2019-01-13 20:16:06<PHONE_NUMBER>75520 [Note] WSREP: Shifting JOINER -> JOINED (TO: 3885),
2019-01-13 20:16:06<PHONE_NUMBER>75520 [Note] WSREP: Member 0.0 (f4fe8c340a39) synced with group.,
2019-01-13 20:16:06<PHONE_NUMBER>75520 [Note] WSREP: Shifting JOINED -> SYNCED (TO: 3885),
2019-01-13 20:16:06<PHONE_NUMBER>88096 [Note] WSREP: Synchronized with group, ready for connections,
2019-01-13 20:16:06<PHONE_NUMBER>88096 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.,
2019-01-13 20:16:42<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 30,
2019-01-13 20:17:26<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 60,
2019-01-13 20:18:11<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 90,
2019-01-13 20:18:55<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 120,
2019-01-13 20:19:40<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 150,
2019-01-13 20:20:24<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 180,
2019-01-13 20:21:09<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 210,
2019-01-13 20:21:54<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 240,
2019-01-13 20:22:38<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 270,
2019-01-13 20:23:23<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 300,
2019-01-13 20:24:08<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 330,
2019-01-13 20:24:53<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 360,
2019-01-13 20:25:38<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 390,
2019-01-13 20:25:58<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 6a1450ce (tcp://<IP_ADDRESS>:4567), attempt 0,
2019-01-13 20:26:01<PHONE_NUMBER>30368 [Note] WSREP: evs::proto(08a8d172, GATHER, view_id(REG,08a8d172,6)) suspecting node: 6a1450ce,
2019-01-13 20:26:01<PHONE_NUMBER>30368 [Note] WSREP: evs::proto(08a8d172, GATHER, view_id(REG,08a8d172,6)) suspecting node: 6a1450ce,
2019-01-13 20:26:01<PHONE_NUMBER>30368 [Note] WSREP: evs::proto(08a8d172, GATHER, view_id(REG,08a8d172,6)) suspecting node: 91bf1a62,
2019-01-13 20:26:02<PHONE_NUMBER>30368 [Note] WSREP: evs::proto(08a8d172, GATHER, view_id(REG,08a8d172,6)) suspecting node: 6a1450ce,
2019-01-13 20:26:02<PHONE_NUMBER>30368 [Note] WSREP: evs::proto(08a8d172, GATHER, view_id(REG,08a8d172,6)) suspecting node: 91bf1a62,
2019-01-13 20:26:02<PHONE_NUMBER>30368 [Note] WSREP: evs::proto(08a8d172, GATHER, view_id(REG,08a8d172,6)) suspecting node: 6a1450ce,
2019-01-13 20:26:02<PHONE_NUMBER>30368 [Note] WSREP: evs::proto(08a8d172, GATHER, view_id(REG,08a8d172,6)) suspecting node: 91bf1a62,
2019-01-13 20:26:03<PHONE_NUMBER>30368 [Note] WSREP: evs::proto(08a8d172, GATHER, view_id(REG,08a8d172,6)) suspecting node: 6a1450ce,
2019-01-13 20:26:03<PHONE_NUMBER>30368 [Note] WSREP: evs::proto(08a8d172, GATHER, view_id(REG,08a8d172,6)) suspecting node: 91bf1a62,
2019-01-13 20:26:03<PHONE_NUMBER>30368 [Note] WSREP: evs::proto(08a8d172, GATHER, view_id(REG,08a8d172,6)) suspecting node: 6a1450ce,
2019-01-13 20:26:03<PHONE_NUMBER>30368 [Note] WSREP: evs::proto(08a8d172, GATHER, view_id(REG,08a8d172,6)) suspecting node: 91bf1a62,
2019-01-13 20:26:04<PHONE_NUMBER>30368 [Warning] WSREP: evs::proto(08a8d172, GATHER, view_id(REG,08a8d172,6)) install timer expired,
evs::proto(evs::proto(08a8d172, GATHER, view_id(REG,08a8d172,6)), GATHER) {,
current_view=view(view_id(REG,08a8d172,6) memb {,
08a8d172,0,
6a1450ce,0,
91bf1a62,0,
} joined {,
} left {,
} partitioned {,
}),,
input_map=evs::input_map: {aru_seq=1740,safe_seq=1740,node_index=node: {idx=0,range=[1741,1740],safe_seq=1740} node: {idx=1,range=[1741,1740],safe_seq=1740} node: {idx=2,range=[1741,1740],safe_seq=1740} },,
fifo_seq=3501,,
last_sent=1740,,
known:,
08a8d172 at
{o=1,s=0,i=0,fs=-1,jm=,
{v=0,t=4,ut=255,o=1,s=1740,sr=-1,as=1740,f=0,src=08a8d172,srcvid=view_id(REG,08a8d172,6),insvid=view_id(UNKNOWN,00000000,0),ru=00000000,r=[-1,-1],fs=3492,nl=(
},
08a8d172, {o=1,s=0,e=0,ls=-1,vid=view_id(REG,08a8d172,6),ss=1740,ir=[1741,1740],},
6a1450ce, {o=0,s=0,e=0,ls=1740,vid=view_id(REG,08a8d172,6),ss=1740,ir=[1741,1740],},
91bf1a62, {o=1,s=0,e=0,ls=-1,vid=view_id(REG,08a8d172,6),ss=1740,ir=[1741,1740],},
),
},,
6a1450ce at tcp://<IP_ADDRESS>:4567,
{o=0,s=1,i=0,fs=5143,lm=,
{v=0,t=6,ut=255,o=1,s=1740,sr=-1,as=1740,f=4,src=6a1450ce,srcvid=view_id(REG,08a8d172,6),insvid=view_id(UNKNOWN,00000000,0),ru=00000000,r=[-1,-1],fs=5143,nl=(,
91bf1a62 at tcp://<IP_ADDRESS>:4567,
{o=1,s=1,i=0,fs=3840,jm=,
{v=0,t=4,ut=255,o=1,s=1740,sr=-1,as=1740,f=4,src=91bf1a62,srcvid=view_id(REG,08a8d172,6),insvid=view_id(UNKNOWN,00000000,0),ru=00000000,r=[-1,-1],fs=3840,nl=(,
install msg={v=0,t=5,ut=255,o=1,s=1740,sr=-1,as=1740,f=6,src=08a8d172,srcvid=view_id(REG,08a8d172,6),insvid=view_id(REG,08a8d172,7),ru=00000000,r=[-1,-1],fs=3493,nl=(
},
2019-01-13 20:26:04<PHONE_NUMBER>30368 [Note] WSREP: evs::proto(08a8d172, GATHER, view_id(REG,08a8d172,6)) node 6a1450ce failed to commit for install message, declaring inactive,
2019-01-13 20:26:04<PHONE_NUMBER>30368 [Note] WSREP: evs::proto(08a8d172, GATHER, view_id(REG,08a8d172,6)) node 91bf1a62 failed to commit for install message, declaring inactive,
2019-01-13 20:26:04<PHONE_NUMBER>30368 [Note] WSREP: view(view_id(NON_PRIM,08a8d172,6) memb {,
08a8d172,0,
} joined {,
} left {,
} partitioned {,
6a1450ce,0,
91bf1a62,0,
}),
2019-01-13 20:26:04<PHONE_NUMBER>75520 [Note] WSREP: New COMPONENT: primary = no, bootstrap = no, my_idx = 0, memb_num = 1,
2019-01-13 20:26:04<PHONE_NUMBER>75520 [Note] WSREP: Flow-control interval: [16, 16],
2019-01-13 20:26:04<PHONE_NUMBER>75520 [Note] WSREP: Trying to continue unpaused monitor,
2019-01-13 20:26:04<PHONE_NUMBER>75520 [Note] WSREP: Received NON-PRIMARY.,
2019-01-13 20:26:04<PHONE_NUMBER>75520 [Note] WSREP: Shifting SYNCED -> OPEN (TO: 3885),
2019-01-13 20:26:04<PHONE_NUMBER>30368 [Note] WSREP: forgetting 6a1450ce (tcp://<IP_ADDRESS>:4567),
2019-01-13 20:26:04<PHONE_NUMBER>30368 [Note] WSREP: deleting entry tcp://<IP_ADDRESS>:4567,
2019-01-13 20:26:04<PHONE_NUMBER>30368 [Note] WSREP: view(view_id(NON_PRIM,08a8d172,8) memb {,
2019-01-13 20:26:04<PHONE_NUMBER>88096 [Note] WSREP: New cluster view: global state: a122b452-175e-11e9-8164-e62c82786503:3885, view# -1: non-Primary, number of nodes: 1, my index: 0, protocol version 3,
2019-01-13 20:26:04<PHONE_NUMBER>88096 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
2019-01-13 20:26:09<PHONE_NUMBER>30368 [Note] WSREP:  cleaning up 6a1450ce (tcp://<IP_ADDRESS>:4567),
2019-01-13 20:26:23<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 420,
2019-01-13 20:27:07<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 450,
2019-01-13 20:27:52<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 480,
2019-01-13 20:28:37<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 510,
2019-01-13 20:29:22<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 540,
2019-01-13 20:30:06<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 570,
2019-01-13 20:30:51<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 600,
2019-01-13 20:31:36<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 630,
2019-01-13 20:32:21<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 660,
2019-01-13 20:33:06<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 690,
2019-01-13 20:33:51<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 720,
2019-01-13 20:34:36<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 750,
2019-01-13 20:35:21<PHONE_NUMBER>30368 [Note] WSREP: (08a8d172, 'tcp://<IP_ADDRESS>:4567') reconnecting to 91bf1a62 (tcp://<IP_ADDRESS>:4567), attempt 780,
Received TERM|INT signal.,
Shutting down...,
2019-01-13 20:35:55<PHONE_NUMBER>52992 [Note] mysqld (initiated by: system[system] @  [<IP_ADDRESS>]): Normal shutdown,
2019-01-13 20:35:55<PHONE_NUMBER>52992 [Note] WSREP: Stop replication,
2019-01-13 20:35:55<PHONE_NUMBER>52992 [Note] WSREP: Closing send monitor...,
2019-01-13 20:35:55<PHONE_NUMBER>52992 [Note] WSREP: Closed send monitor.,
2019-01-13 20:35:55<PHONE_NUMBER>52992 [Note] WSREP: gcomm: terminating thread,
2019-01-13 20:35:55<PHONE_NUMBER>52992 [Note] WSREP: gcomm: joining thread,
2019-01-13 20:35:55<PHONE_NUMBER>52992 [Note] WSREP: gcomm: closing backend,
MariaDB exited with return code (0),
2019-01-13 20:35:55<PHONE_NUMBER>52992 [Note] WSREP: view((empty)),
2019-01-13 20:35:55<PHONE_NUMBER>52992 [Note] WSREP: gcomm: closed,
2019-01-13 20:35:55<PHONE_NUMBER>75520 [Note] WSREP: Received self-leave message.,
2019-01-13 20:35:55<PHONE_NUMBER>75520 [Note] WSREP: Flow-control interval: [0, 0],
2019-01-13 20:35:55<PHONE_NUMBER>75520 [Note] WSREP: Trying to continue unpaused monitor,
2019-01-13 20:35:55<PHONE_NUMBER>75520 [Note] WSREP: Received SELF-LEAVE. Closing connection.,
2019-01-13 20:35:55<PHONE_NUMBER>75520 [Note] WSREP: Shifting OPEN -> CLOSED (TO: 3885),
2019-01-13 20:35:55<PHONE_NUMBER>75520 [Note] WSREP: RECV thread exiting 0: Success,
2019-01-13 20:35:55<PHONE_NUMBER>88096 [Note] WSREP: New cluster view: global state: a122b452-175e-11e9-8164-e62c82786503:3885, view# -1: non-Primary, number of nodes: 0, my index: -1, protocol version 3,
2019-01-13 20:35:55<PHONE_NUMBER>88096 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.,
2019-01-13 20:35:55<PHONE_NUMBER>52992 [Note] WSREP: Closing replication queue.,
2019-01-13 20:35:55<PHONE_NUMBER>52992 [Note] WSREP: recv_thread() joined.,
2019-01-13 20:35:55<PHONE_NUMBER>52992 [Note] WSREP: Closing slave action queue.,
GALERA saved state
version 2.1
uuid:    a122b452-175e-11e9-8164-e62c82786503
seqno:   3885
safe_to_bootstrap: 0,
2019-01-13 20:35:55<PHONE_NUMBER>88096 [Note] WSREP: applier thread exiting (code:0),
Goodbye

Is there any update on this issue and has this been tested on docker swarm?  The suggested compose file does not appear to work at all and results in the cluster's failing with the above error.
The root cause of the issue appears to be that the nodes (not the seed) are assigned to different IPs than what the cluster has registered, For example, a node with <IP_ADDRESS> in the above example does not actually exist and the node IP is a different but on the subnet, e.g. <IP_ADDRESS>.  Seed IPs do not appear to be an issue probably because the endpoint_mode is 'vip' (the default) vs 'dsnrr' (per the compose file for nodes).  If the endpoint_mode is the default for the nodes, the cluster obviously doesn't work.

So it seems like there are two pretty simple possible solutions:

Use dnsrr instead of vip.
Uses "tasks.node" instead of "node" as the DNS lookup for the service.

I think 2 is the best solution but I don't have a test environment setup.. Can you give this a try?

I'm using dnsrr for the node service.  I do not understand your #2 as the nodes fail with "sleep|no-galera|bash|seed|node ,..."  That is it appears that there is no command for task.node.  Shouldn't the command for the node service be: "node seed,node" per the suggested compose file?

The first token is the command, in the case of "node" the second token is the list of DNS names to resolve, so: "node seed,tasks.node" or "node "tasks.seed,tasks.node" to be more consistent.

Your suggestion #2 resolved the issue.  Can you please update the suggested compose file as I spent a significant amount of time seeking a resolution?  I appreciate your help in resolving the issue.

Thanks for reporting and testing!


Disable "duplicate including translation" button

Pressing this button sends out newsletters when used for news.
We can disable the button.

LGTM!


[Bug] Callable functions request does not include Auth context in editor

Description
Calling a callable function from Editor either targeting deployed function or functions emulator does not include Verifications-> Auth (missing) context.
Works fine on Android build.
Using anonymous authentication.
Reproducing the issue
In Unity Editor, authenticate with anonymous auth.
Once authentication is completed invoke a callable function, tried calls on various timings to make sure that it is not an issue relative to authentication completion.
Request object received by function doesn't contain auth context.
Functions used is AddMessage example in callable functions doc.
Using either deployed function or functions emulator result is the same.
Firebase Unity SDK Version
12.1.0
Unity editor version
2022.3.30f1
Installation Method
Unity Package Manager
Problematic Firebase Component(s)
Authentication, Functions
Other Firebase Component(s) in use
Database, Firestore, Storage
Additional SDKs you are using
No response
Targeted Platform(s)
Android
Unity editor platform
Windows
Scripting Runtime
IL2CPP
Release Distribution Type
Pre-built SDK from https://firebase.google.com/download/unity
Relevant Log Output
{
  "insertId": "xxx",
  "jsonPayload": {
    "message": "Callable request verification passed",
    "verifications": {
      "app": "MISSING",
      "auth": "MISSING"
    }
  },
  "resource": {
    "type": "cloud_run_revision",
    "labels": {
      "revision_name": "addmessage-xxx",
      "service_name": "addmessage",
      "location": "us-central1",
      "project_id": "xxx",
      "configuration_name": "addmessage"
    }
  },
  "timestamp": "2024-09-17T17:29:09.258142Z",
  "severity": "DEBUG",
  "labels": {
    "goog-managed-by": "cloudfunctions",
    "firebase-log-type": "callable-request-verification",
    "execution_id": "xxx",
    "instanceId": "xxx"
  },
  "logName": "xxx",
  "trace": "xxx",
  "receiveTimestamp": "2024-09-17T17:29:09.264748765Z",
  "spanId": "xxx"
}

If using CocoaPods for Apple platforms, the project's Podfile.lock

Expand Podfile.lock snippet

👀 Replace this line with the contents of your Podfile.lock!

Thanks for reaching out, @PizzaPie144. I tried using our Unity quickstarts for Firebase Functions, and tested out the functions of 1st and 2nd gen. It seems to be working correctly, and the auth context doesn't appear to be empty.
Here's my NodeJS functions.
1st gen:
exports.addNumbersV1 = functions.https.onCall((data, context) => {
    ...
    const uid = context.auth.uid;
    functions.logger.info("auth: " + uid);
    ...
}

2nd gen:

exports.addNumbersV2 = onCall((request) => {
    ...
    const uid = request.auth.uid;
    logger.info("uid: " + uid);
    ...
}

That said, I did notice that you're using an older version of the Unity Editor and Firebase SDK. Could you try updating to the latest version 2022.3.47f1 and 12.2.1. We normally recommend this to avoid issues that might have been fixed in the most recent versions. Let me know if it works!
If it doesn't, could you share a MCVE so we can investigate this further? Thanks!


MySQL install fails on amazon platform

Hi,
I'm using cookbooks database (2.3.0) and mysql (5.6.1) to do a basic installation of MySQL 5.6 on an Amazon EC2 instance (AMI 2014.03). I can see in the logs that MySQL 5.5 is installed first (by mysql-chef_gem), which subsequently creates conflicts with the packages of MySQL 5.6. Apart from the obvious inefficiency, this means that support for amazon is not really there.
Am I missing something? Are these cookbooks not supposed to be used together?
Thanks
ps: I'm using Chef 11.16.4

This is fixed in the current version. The database cookbook now depends on the mysql2_chef_gem, which was explicitly tested on Amazon.


case add regress cases for nested type nested type with csv format

Proposed changes
Issue Number: close #xxx
this pr

fix use podarray push_back() with back() will make heap_use_after_free when podarray is reach capacity which would may make heap free
add cases for csv format for nested types. and csv file has two define which are without quote or just like json text

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

run buildall

run p0

run buildall


Is this iPad compatible?

Unfortunately it is not. You can see the explanation in this thread: https://github.com/quackduck/uniclip/issues/17#issuecomment-1500386742


Product Search e2e test is failing (smoke test)

The product search smoke test is failing. Since it is a smoke test it prevents merging to develop.
These are the errors from Jenkins. It seems to be that the Stores facets are missing in the product search page. Going to the product search in de-17 the Stores facet is not visible

Pulled the latest sample addon to grab this fix: https://github.tools.sap/cx-commerce/spartacussampledataaddon/pull/17
and re-initialized the instance.


NO Event trigger ?

I was totally surprised to see that this awesome component does not trigger toggle updates. or am I missing something ?

Sounds like an inevitable requirement, I don't know how it got missed


:seedling: Fix integration test runs

Please check if the PR fulfills these requirements

[ ] Tests for the changes have been added (for bug fixes / features)
[x] PR title follows the guidelines defined in  https://github.com/ossf/scorecard/blob/main/CONTRIBUTING.md#pr-process

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Other information:

Is this PR good to submit after #1291?

Is this PR good to submit after #1291?

I think so.

Is this PR good to submit after #1291?

I think so.

Ok, lets submit this then. We've had 3 different PRs break different e2e tests in a single day. We really need this asap.
Thanks Naveen!


Updated First-Look-At-DP notebook

This material was adapted from a notebook for the Sydney Privacy Workshop

Closing. See comments in #1270


More didactic first notebook:

Split out data to simplify the notebook
Use a nearest-neighbor classifier, which was discussed in the video,
is actually better than the LogisticRegression (not explained yet),
and has no warning
Demonstrate overfit

LGTM
I guess some other notebooks will need to be adapted. A few things I can think of:

add the explanation about train-test split when introducing it in the next notebook
change the exercises + correction to use the numeric only dataset
should we use this numeric only dataset in all of the numeric-only data notebooks or only in this first notebook?
we probably want to adapt the notebook that talks about scaling numerical features because we were saying something like "we got a warning previously let's see what we can do about it".
the first notebook on data exploration uses the full dataset, so it is a bit weird to switch back and forth between full dataset, numeric-only dataset (but trust me this is the same as the previous dataset we were looking at I am not lying), and now back to the full dataset but we only select categorical features with pandas. I would argue that using slightly different versions of the same dataset can be confusing, possibly as confusing as using many different datasets.

My personal preference (I do get @GaelVaroquaux point about trying really hard to reduce cognitive load) would be to keep the boiler-plate pandas code to select the columns, maybe removing the make_column_selector that we had and doing it by column names instead.

should we use this numeric only dataset in all of the numeric-only data notebooks or only in this first notebook?

Actually, most of the in-depth notebook is only using numeric-only datasets

we probably want to adapt the notebook that talks about scaling numerical features because we were saying something like "we got a warning previously let's see what we can do about it".

I am discussing this issue slightly in the linear model notebook regarding the interaction with the regularization strength as well.
Since we might have a course at the Inria Academy that will use only the 4 first notebook, I think that we need to tackle this issue within this introductory notebook. I am always concerned that we get some course where the following is happening: https://github.com/scikit-learn/scikit-learn/issues/18824
For sure, the viable solution is to be implemented in scikit-learn avoiding these issues. But in the meanwhile, I would be in favour to have it somewhere in this first part.

we probably want to adapt the notebook that talks about scaling numerical
features because we were saying something like "we got a warning previously
let's see what we can do about it".

I am discussing this issue slightly in the linear model notebook regarding the
interaction with the regularization strength as well.

OK, I'll let you adapt.

For sure, the viable solution is to be implemented in scikit-learn avoiding these issues. But in the meanwhile, I would be in favour to have it somewhere in this first part.

Right, but later. Not in the first notebook that runs machine learning.

should we use this numeric only dataset in all of the numeric-only data notebooks or only in this first notebook?

Actually, most of the in-depth notebook is only using numeric-only datasets

Sorry I was not explicit enough, I was talking here about adult-census-numeric-all.csv (numeric-only dataset) vs adult-census.csv (full dataset). And by numeric-only notebooks I was talking about the 02_numerical_pipeline_* notebooks.

And to be honest, thinking a bit more about it, I am now wondering whether rather than changing the existing Predictive Modeling Pipeline notebooks that have some internal consistency, it would not be easier to add a separate simple notebook maybe just after the ML concepts slides.
An an exercise, I am thinking we could do the n_neighbors=1 100% training accuracy thing that is mentioned quickly in the slides.

And to be honest, thinking a bit more about it, I am now wondering whether rather than changing the existing Predictive Modeling Pipeline notebooks that have some internal consistency, it would not be easier to add a separate simple notebook maybe just after the ML concepts slides.

I decided that we needed to move forward. We can always come back later.
These notebook need rework anyhow, because they need much more text (in a MOOC, we are not there to make comments, all the comments must be written).
But also, I found that it was easier to adapt these notebooks

An an exercise, I am thinking we could do the n_neighbors=1 100% training accuracy thing that is mentioned quickly in the slides.

+1 for such an exercise!


fix: untranslatable relative path

this bug prevented the migration to webpack 5, because this line was
translated to a relative path, which could not be converted to an
absolute path. this is bad, because webpack 5 introduced a check about
relative paths and removed those and printed an error.

The change in question led to a different error for me, so I did a bit of digging.
Webpack 5
Indeed, Webpack 5 will check if the file dependencies found by the configured loaders are absolute paths.
A closer look (with some console.logs at some spots like here and configuration experimentation) did show that there was only one offending entry in fileDependencies, from the less-loader.
Directory structure
Note that the relevant part of the directory structure in the virtualenv should look like the following:
/path/to/venv/var/instance/assets
├── node_modules
│   └── semantic-ui-less
│       └── themes
└── less
    └── site
        └── globals
            └── site.variables

Configuration
The relevant variables defined in theme.config have the following values:

@themesFolder : '~semantic-ui-less/themes';
@siteFolder  : '../../less/site';

This means that the line @import '<EMAIL_ADDRESS>would result in ~semantic-ui-less/themes/../../less/site/globals/site.variables.
However, two directories up will only land in node_modules rather than assets, which requires another step up.
Results
Changing the value to @siteFolder  : '../../../less/site'; in the cookiecutter theme.config made the Webpack build without issues for me.
Especially, there's no more errors regarding any non-absolute paths pop up anymore, which hints at Webpack being able to handle relative paths as long as they can be resolved.
However, I'm not 100% sure if that's the correct change, and if other values should be changed as well.

The @imagesFolder : '../../images'; might have a similar issue, but there was no images directory to be found anywhere in my /var/instance/assets at all, so I can't say for sure.
Similar for the @fontPath : "../../../themes/@{theme}/assets/fonts"; – the value looks a lot like aliases to me, but from a quick glance I can't see an alias (in build/config.json) that would match this pattern.
Alternatively, the approach from this PR could be taken to change the variables' usage rather than their definition.

Further findings
The value for @site is set to rdm in the default cookiecutter, causing the change in this PR (@import '@{themesFolder}/@{site}/globals/site.variables';) to result in @import '~semantic-ui-less/themes/rdm/globals/site.variables';, which doesn't exist (at least for me, with a fresh my-site).
Instead, the rdm theme is located in the directory less/invenio_app_rdm/theme, which is accessible via the themes/rdm alias.


Linux export with embedded PCK fails with ERR_FILE_CORRUPT

Godot version:
3.2 master (bf1c81af), test build: https://downloads.tuxfamily.org/godotengine/3.2/dev.bf1c81adf/
OS/device including version:
Mageia 7 x86_64
Issue description:
When exporting https://github.com/KOBUGE-Games/jetpaca for Linux with the embedded PCK option enabled, the export fails with ERR_FILE_CORRUPT (so fixup_embedded_pck() is not satisfied).
This is with export templates built on the official buildsystem. Notable build options that could influence this are debug_symbols=no use_static_cpp=yes use_lto=yes. Building with GCC 8.
Even though the export fails and editor raises an error, the binary is still properly exported, and the PCK seems included, as it runs the game fine.
Note: contrarily to #32310, the Linux binaries are not signed. They are also not strip-ed beyond debug_symbols=no.
Steps to reproduce:

Download https://downloads.tuxfamily.org/godotengine/3.2/dev.bf1c81adf
Export a project to Linux with embedded PCK (tested both 32-bit and 64-bit, release and debug)

The issue doesn't seem to happen with signed Windows templates.

I'll have a look ASAP.

BTW, I had a hunch that it could be that it uses the wrong gcc-ar and gcc-ranlib as we use Ubuntu 14.04 and gcc-8 is an extra package that we install, not the default GCC 4.8 version Ubuntu shipped with.
And while the logs mention calling gcc-ranlib and gcc-ar, they seem to be properly set as symlinks to their versions from the GCC 8 distribution:
ls /usr/bin/gcc* -l
lrwxrwxrwx. 1 root root     14 Aug 31 18:32 /usr/bin/gcc -> /usr/bin/gcc-8
-rwxr-xr-x. 1 root root 775888 Apr 25  2018 /usr/bin/gcc-4.8
lrwxrwxrwx. 1 root root     22 Jul  5 14:10 /usr/bin/gcc-8 -> x86_64-linux-gnu-gcc-8
lrwxrwxrwx. 1 root root     17 Aug 31 18:32 /usr/bin/gcc-ar -> /usr/bin/gcc-ar-8
-rwxr-xr-x. 1 root root  26968 Apr 25  2018 /usr/bin/gcc-ar-4.8
lrwxrwxrwx. 1 root root     25 Jul  5 14:10 /usr/bin/gcc-ar-8 -> x86_64-linux-gnu-gcc-ar-8
lrwxrwxrwx. 1 root root     10 Apr  7  2014 /usr/bin/gcc-nm -> gcc-nm-4.8
-rwxr-xr-x. 1 root root  26968 Apr 25  2018 /usr/bin/gcc-nm-4.8
lrwxrwxrwx. 1 root root     25 Jul  5 14:10 /usr/bin/gcc-nm-8 -> x86_64-linux-gnu-gcc-nm-8
lrwxrwxrwx. 1 root root     21 Aug 31 18:32 /usr/bin/gcc-ranlib -> /usr/bin/gcc-ranlib-8
-rwxr-xr-x. 1 root root  26968 Apr 25  2018 /usr/bin/gcc-ranlib-4.8
lrwxrwxrwx. 1 root root     29 Jul  5 14:10 /usr/bin/gcc-ranlib-8 -> x86_64-linux-gnu-gcc-ranlib-8

So that shouldn't be the culprit.
It's worth nothing that they're from Ubuntu 14.04's old binutils though:
gcc-ranlib-8 --version
GNU ranlib (GNU Binutils for Ubuntu) 2.24
Copyright 2013 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) any later version.
This program has absolutely no warranty.

Hi @RandomShaper , any chance to have this fix for 3.2 Final? We are about to get the full 3.2 release and this is still not working.

The problem is due to the pck section missing from the template binaries.
When I developed this, I added a comment about maybe adding an CI check to check its presence (https://github.com/godotengine/godot/pull/24086#issuecomment-446373891).
Now, regarding why it's absent, I think it's up to the linker. Which version of ld is being used?

Now, regarding why it's absent, I think it's up to the linker. Which version of ld is being used?

GNU binutils 2.24, same as in https://github.com/godotengine/godot/issues/32513#issuecomment-537868093
We also build with use_lto=yes use_static_cpp=yes.

Works for me with 2.30 (with and without LTO). I've not been able to find a proper changelog to try to explain what's the relevant difference.

You can build the container we use for the official buildsystem with https://github.com/godotengine/build-containers/blob/master/Dockerfile.ubuntu-64
(see build.sh for usage instructions).
Then the in-container build script amounts to:
export BUILD_NAME=official
export SCONS="scons -j${NUM_CORES} verbose=yes warnings=no progress=no"
export OPTIONS="debug_symbols=no use_static_cpp=yes use_lto=yes"
export CC="gcc-8"
export CXX="g++-8"

$SCONS platform=x11 CC=$CC CXX=$CXX $OPTIONS tools=yes target=release_debug
mkdir -p /root/out/tools
cp -rvp bin/* /root/out/tools
rm -rf bin

$SCONS platform=x11 CC=$CC CXX=$CXX $OPTIONS tools=no target=release_debug
$SCONS platform=x11 CC=$CC CXX=$CXX $OPTIONS tools=no target=release
mkdir -p /root/out/templates
cp -rvp bin/* /root/out/templates
rm -rf bin

With /root/out being mounted to copy the binaries outsides of the container.


decidability, ecoles

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 5
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[d,e]

/trunk merge


First release to production

First release to production, set metadata (assignees, labels, milestones, projects

First release to production, add index.html from the develop branch to the main


[Question]: Why are files of doc, ppt, xls and other types not supported?

Describe your problem
When I parsed files of doc, ppt, xls and other types, an error parsing failure occurred.

There must be other errors.
RAGFlow supports all these type of files.

When I uploaded ppt type files on the test website（https://demo.ragflow.io/knowledge）, the following error was reported.

Possibly caused by PPT version.
What about using 'save as ...' to restore it, then upload it?