Nebula Support

Will need @d6e 's help with a sample file so I can write the parser for this.

Nebula? Like https://nebula.org? We already support them with vcf files

Oh sorry, I got confused with the tag. I meant to tag 2d4d, a.k.a. @r0ze-at-github  😅
I added this task because it's one of the first things that 2d4d asked me to help out with. Since we already have support via VCF, I'll close this comment.


[WIP] Better error for min_success_ratio<1

Tracking issue

Why are the changes needed?

What changes were proposed in this pull request?

How was this patch tested?

Setup process
pyflyte run flyte-example/map_optional_list.py wf

import os
import tempfile
from typing import List

from flytekit import map_task, workflow, task
from flytekit.types.directory import FlyteDirectory

@task
def generate_directory(word: str) -> FlyteDirectory:
    temp_dir1 = tempfile.TemporaryDirectory()
    with open(os.path.join(temp_dir1.name, "file.txt"), "w") as tmp:
        tmp.write(f"Hello world {word}!\n")
    return FlyteDirectory(path=temp_dir1.name)

@task
def consume_directories(dirs: List[FlyteDirectory]):
    for d in dirs:
        print(f"Directory: {d.path} {d._remote_source}")
        for path_info, other_info in d.crawl():
            print(path_info)

mt = map_task(generate_directory, min_success_ratio=0.1)

@workflow
def wf():
    dirs = mt(word=["one", "two", "three"])
    consume_directories(dirs=dirs

Screenshots
Check all the applicable boxes

[ ] I updated the documentation accordingly.
[ ] All new and existing tests passed.
[ ] All commits are signed-off.

Related PRs

Docs link

i think it's good to have this...  i don't want flytekit to fall into the trap of duplicating the compiler, but this is a common  and tricky enough case that I think it's okay to explicitly catch this.


Refactor token list logic (currently in L2ERC721Table) for Ark endpoints

Including the token card display, activity page and collection summary

Can I be assigned to this issues please


fix(web): fixed base64 encoding of *.js and *.css files

Intent
Fix base64 encoding of *.js and *.css files when streaming to SAS 9.
Implementation
Updated 'getWebServiceContent' function and 'sasjsout' file.
Checks

[x] Code is formatted correctly (npm run lint:fix).
[ ] Any new functionality has been unit tested.
[x] All unit tests are passing (npm test).

[x] All CI checks are green.
[ ] JSDoc comments have been added or updated.

:tada: This PR is included in version 1.13.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Investigate how to support different versions of electron/OpenFin/browser

From the GoogleDoc:

Perhaps use peer dependencies for electron (allowing version flexibility)
See if we can fix it, or raise an issue

Determine how we support different versions of OpenFin, electron, and the browser, especially in the cases of breaking APIs etc.

electron-download looks like something possibly worth looking into. Seems like it has similar functionality to the openfin-launcher package, in that we can specify a version to download. I think this would mean we could always include the @types/electron packages, but not 100% sure.

In relation to this, there's also a question of what version of node we need to be loading for the CI builds. Travis runs against node 4, 6, and 7, and Appveyor installs the latest (I think).
Do we need to be testing against different versions, or are we only using it for running tasks etc. so we can use a single version.


Added logic to properly set arguments value

Problem
We need to properly set the arguments value when creating the query. Currently following code:
Graphlient::Query.new do
  invoices(id: 'test') do
    name
  end
end

results is
{
  invoices(id: test) {
    name
  }
}

Instead of id: "test"
Solution
Before setting the argument check the argument class and properly set it as argument value.

Also needs changelog.

Addressed those comments, going to merge 🙌

I cut 0.0.5 with this since it's a major fix.


Fix for IOS Expandable resize bug

Fix for IOS Expandable resize bug
Changes

Added some code to the expandable to check the contentHeight before resizing.

Testing

Visit the blog on the IOS simulator (http:<IP_ADDRESS>:8000/about-us/blog) and click/scroll on the expandable. It shouldn't close. Rotate the simulator 360 degrees; it should close.

Review

@anselmbradford
@jimmynotjim
@KimberlyMunoz

Todos

Throttle the window.resize method.

Checklist
Notes

Calling offsetHeight will cause a reflow so we need to address that at some point.

[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the front end playbook
[ ] Passes all existing automated tests
[ ] New functions include new tests
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)

When I scroll underneath the expandable it still randomly closes.

I was on the wrong branch. It works!! :tada: :+1:

Oops accidentally merged this while reviewing! Sorry! Looked good.


Allow to dynamically depend on plugins based on current app flavor

Use case
Many Flutter applications rely on native dependencies. Often, these native dependencies use the Google Play Services, Huawei App Services or Amazon Fire APIs on Android, make use of Vendor specific APIs or rely on special APIs (such as root features). Unfortunately, it is not possible to publish an application relying on certain APIs in all different marketplaces.
We are hence looking for a way to dynamically in- and exclude certain dependencies for certain build flavors.
E.g. myapp depends on the fictional package accesses_restricted_api whereas accesses_restricted_api makes use of a native API being only available on app marketplace 1 and being disallowed on app marketplace 2 and app marketplace 3 as well as unwanted in regard of the marketplace's philosophy in app marketplace 4.
We are hence looking for a way to blacklist/remove the package (or, to be clear a certain class name) in one of our build flavors.
To be clear for those people usually only publishing in the major app marketplaces: it's currently not possible to use Flutter's own capabilities to publish an app making use of one of the various native Google Service Framework-dependent plugins in Google Play Store, Huawei AppGallery, Amazon Appstore and F-Droid.
Workarounds tried
We tried to fork the fictional acces_restricted_api and create package-specific android build flavors too. Unfortunately, Flutter requires the native class to be present in android/src/**main** even if we would like to have different implementations for the different build flavors (e.g. in android/src/**libre**, android/src/**marketplace1** and android/src/**marketplace2**).
As this does not work, we now work around this by maintaining different branches for each app marketplace we target. This is a tremendous amount of work as every change needs to be integrated into four different code bases.
Proposal
We can imagine two different implementations:

ether allow flavor-specific implementations for native code on Android
or provide a way to remove / blacklist a dependency at compile time in case a certain flavor is used

Do you own these plugins?  If yes, a Flutter Android plugin is a Gradle subproject, so you could do something like this: https://stackoverflow.com/a/18213259, by referring to the plugin's subproject: project('acces_restricted_api').

Hello, In my case most of the time these plugins are third party, like GoogleMap and MapBox sdks.
I also think that this is not only an android problem, but also iOS, web etc.
A way to have "flavors" directly integrated in Flutter's pubspec.yaml, making each flavour to have a list of specific dependencies, added to the more general ones, would be the perfect solution for me. Surely we would also need different entry points (main.dart) that only uses these different dependencies, more or less like plugins already do for dart:io and dart:js, but without having to use multiple flutter projects

have you thought about creating your own CLI tool to achieve this behavior? We will be more than happy to review a proposed design.

Yes I thought it before, but from my understanding a CLI tool is not feasible at this time because at best it would require to use a cli command every time we want to switch from one flavor to another. This means that the pubspec.yaml can't be stored in version control, you would need to have several pubspec.yaml, one for each flavor, which means shared dependencies would be separated from specific flavor ones.
Also having it in flutter directly would allow this process to be automated as we already need to specify the --flavor option when we build (either on debug or on release).
We could make a tool if flutter would allow us to use custom procedures in the build process, like gradle on android do

I think this issue was unintentionally closed. The information requested by the bot does not apply here. I would be happy in case someone could re-open this issue.

Do you own these plugins?

Some yes, some no.
At the moment, the workaround is a hacky combination of patch files and branches we apply and rebase in CI in order to use different native plugins.

Seems like a duplicate of #46979


How to evaluate mesh chamfer distance?

Hi, thanks for your great work!
I want to evaluate the chamfer distance in Table 2 in the paper. It seems that the input data is normalized, so there is a rigid transformation between the extracted mesh and the ground truth mesh in the original DiLiGenT-MV dataset.
Could you please publish the code to calculate chamfer distance, or provide the rigid transformations so we can properly "unnormalize" the extracted mesh? Thank you!

For anyone who is interested, here is how I obtain the transformation matrix:
https://gist.github.com/gerwang/d4d03eeea4a496ae5494ad075ac009d7
I use the 20 camera positions as a point cloud to estimate the transformation. Seems that the estimation is accurate.


Reorganize and improve metainfo

Updates the metainfo to make the app integrate better with Linux app store frontends, and bring it more in line with Flathub's metainfo quality guidelines.
I've pulled in some text from the website for the description, populated the URL section with relevant links, and added info about screen size / input requirements.
I think the only thing missing for the app to be eligible for promotion on Flathub after this, is screenshots with shadows taken on Linux.
Let me know if anything with this should be changed.

Thanks!


How to use AzureOpenAI instead of OpenAI

Hello, I loved the project and its workflow
I wanted to use AzureOpenAI instead of OpenAi. Can you please explain the process and template code for the same.

I think it goes like this:
python```
client = AzureOpenAI(
api_key="",
azure_endpoint="",
api_version= "2023-09-01-preview",
)

simply replace client = OpenAI in the chatEngine.py file.

Sorry for late reply, you need to modify repo_agent/chat_engine.py to

Replace from openai import APIConnectionError, OpenAI with from openai import APIConnectionError, AzureOpenAI

line 72-76, replace

        client = OpenAI(
            api_key=setting.chat_completion.openai_api_key.get_secret_value(),
            base_url=str(setting.chat_completion.base_url),
            timeout=setting.chat_completion.request_timeout,
        )

with
        client = AzureOpenAI(
            api_key=setting.chat_completion.openai_api_key.get_secret_value(),
            api_version="place-your-api-version-here",
            azure_endpoint=str(setting.chat_completion.base_url),
            timeout=setting.chat_completion.request_timeout,

        )

In this way, you can still use repoagent configure to set api_key and azure_endpoint, but hardcode api_version .
3.
pip uninstall repoagent
pdm install

Use repoagnt run as the same.

I believe this is the easiest way to use AzureOpenai` right now. We want to introduce a robust solution of multiple llms support which is not priority but we are welcome to collaboration.
Note: I have deleted a wrong comment in this issue.


ValueError: Expected more than 1 value per channel when training, got input size torch.Size([1, 32, 1, 1])

How does it solve？

Hi, What's the size of the input image?

Hi, What's the size of the input image?
4806403，Does segmentation have relation with the size of input image？

4806403

Segmentation task don't have relation with the size of input image, but the spatial resolution of feature map will be 1/8. Can the size be written as weight * width?

Please ensure batch_size > 1

Segmentation task don't have relation with the size of input image, but the spatial resolution of feature map will be 1/8. Can the size be written as weight * width?

When I use the cityspace dataset, it occurs to this error.and batch_size =32

Hi, is there a more detailed error log?

Hi, is there a more detailed error log?

Nothing，i delete BatchNorm and it is ok.

BatchNorm is important , maybe this will affect performance.

-_-!  Does BatchNorm have connection with Batchsize?it doesn't work if not delete BN

When classifiying,is the background a class?

Namespace(aux=False, aux_weight=0.4, base_size=520, batch_size=1, crop_size=224, dataset='citys', device=device(type='cpu'), epochs=160, eval=False, lr=0.01, model='fast_scnn', momentum=0.9, no_val=True, resume=None, save_folder='./weights', start_epoch=0, train_split='train', weight_decay=0.0001)
Found 2975 images in the folder ./datasets/citys/leftImg8bit/train
Found 500 images in the folder ./datasets/citys/leftImg8bit/val
w/ class balance
Starting Epoch: 0, Total Epochs: 160
Traceback (most recent call last):
  File "/home/Fast-SCNN-pytorch/train.py", line 200, in <module>
    trainer.train()
  File "/home/Fast-SCNN-pytorch/train.py", line 135, in train
    outputs = self.model(images)
  File "/home/.pyenv/versions/anaconda3-4.4.0/lib/python3.6/site-packages/torch/nn/modules/module.py", line 493, in __call__
    result = self.forward(*input, **kwargs)
  File "/home/Fast-SCNN-pytorch/models/fast_scnn.py", line 36, in forward
    x = self.global_feature_extractor(higher_res_features)
  File "/home/.pyenv/versions/anaconda3-4.4.0/lib/python3.6/site-packages/torch/nn/modules/module.py", line 493, in __call__
    result = self.forward(*input, **kwargs)
  File "/home/Fast-SCNN-pytorch/models/fast_scnn.py", line 186, in forward
    x = self.ppm(x)
  File "/home/.pyenv/versions/anaconda3-4.4.0/lib/python3.6/site-packages/torch/nn/modules/module.py", line 493, in __call__
    result = self.forward(*input, **kwargs)
  File "/home/Fast-SCNN-pytorch/models/fast_scnn.py", line 139, in forward
    feat1 = self.upsample(self.conv1(self.pool(x, 1)), size)
  File "/home/.pyenv/versions/anaconda3-4.4.0/lib/python3.6/site-packages/torch/nn/modules/module.py", line 493, in __call__
    result = self.forward(*input, **kwargs)
  File "/home/Fast-SCNN-pytorch/models/fast_scnn.py", line 61, in forward
    return self.conv(x)
  File "/home/.pyenv/versions/anaconda3-4.4.0/lib/python3.6/site-packages/torch/nn/modules/module.py", line 493, in __call__
    result = self.forward(*input, **kwargs)
  File "/home/.pyenv/versions/anaconda3-4.4.0/lib/python3.6/site-packages/torch/nn/modules/container.py", line 92, in forward
    input = module(input)
  File "/home/.pyenv/versions/anaconda3-4.4.0/lib/python3.6/site-packages/torch/nn/modules/module.py", line 493, in __call__
    result = self.forward(*input, **kwargs)
  File "/home/.pyenv/versions/anaconda3-4.4.0/lib/python3.6/site-packages/torch/nn/modules/batchnorm.py", line 83, in forward
    exponential_average_factor, self.eps)
  File "/home/.pyenv/versions/anaconda3-4.4.0/lib/python3.6/site-packages/torch/nn/functional.py", line 1693, in batch_norm
    raise ValueError('Expected more than 1 value per channel when training, got input size {}'.format(size))
ValueError: Expected more than 1 value per channel when training, got input size torch.Size([1, 32, 1, 1])

background is a class.
BatchNorm has connection with batch size.
If I set batch_size=1, it will appear bug above, if batch_size = 4 or others (8, 16,...), there is no bug.

However I set batch_size = 4, it is amazing!

I will fix bug when batch_size=32.

OK，Thank you very much!


Remove kube-state-metrics - addonResizer

Kube-state-metrics has removed the addon resizer
https://github.com/kubernetes/kube-state-metrics/pull/750
https://github.com/kubernetes/kube-state-metrics/issues/672
This is to fix the issue where addonResizer makes kube-state-metrics constantly trigger scale events for the kube-state-metrics pod
56m         Normal    SuccessfulDelete    replicaset/kube-state-metrics-649755f886   Deleted pod: kube-state-metrics-649755f886-6qwd5
55m         Normal    SuccessfulCreate    replicaset/kube-state-metrics-649755f886   Created pod: kube-state-metrics-649755f886-96qnv
48m         Normal    SuccessfulDelete    replicaset/kube-state-metrics-649755f886   Deleted pod: kube-state-metrics-649755f886-96qnv
48m         Normal    SuccessfulCreate    replicaset/kube-state-metrics-649755f886   Created pod: kube-state-metrics-649755f886-65r5w
23m         Normal    SuccessfulDelete    replicaset/kube-state-metrics-649755f886   Deleted pod: kube-state-metrics-649755f886-65r5w
23m         Normal    SuccessfulCreate    replicaset/kube-state-metrics-649755f886   Created pod: kube-state-metrics-649755f886-td8sm
5m37s       Normal    ScalingReplicaSet   deployment/kube-state-metrics              Scaled up replica set kube-state-metrics-5bfc7db74d to 1
11m         Normal    ScalingReplicaSet   deployment/kube-state-metrics              Scaled down replica set kube-state-metrics-5bfc7db74d to 0
56m         Normal    ScalingReplicaSet   deployment/kube-state-metrics              Scaled down replica set kube-state-metrics-649755f886 to 0

jsonnet changes lgtm, if we don't need that sidecar anymore - haven't really followed the discussion.
Can you please run make genreate once and then commit the changes? Thanks!

The conflicts are with the jsonnetfile.lock.json file, and I am not sure what the correct hash should be in order for the automated tests. I was asked to update update it and committed and thats what I have done.
Can an admin of this project resolve

@latchmihay You just need to regenerate it after a rebase. https://github.com/coreos/kube-prometheus#contributing
If you can't manage to do it, I will regenerate for you and push to the branch. Let me know.

I took a crack at it. Trying to rebase with master and re-generating but no success. I must not be doing something right.
Can you please take care of it and let me know how you did since I have a few more pending PR's that will need the same procedure

This has been fixed independently in #235, so this one can be closed now.


Redirect user to /admin after login

Before, the user was getting redirected to the root url, which was annoying / unexpected. This redirects to the /admin route, which is more expected.

@bryangaledxw Yeah, I thought we should sort it before we start user testing!


Fix up unset

This is a follow up on #382, addressing #370, #377, and #383 for unset, which now does not stage modifications in order to roll them back, but only writes to disc if actually needed. Like set before via #382, it uses difflib instead of git-diff in order to show to-be-applied changes.

LGTM, thanks!


Remove doduo from team

Can you somehow auto-remove duduo from the team? Tested it on several accounts, and Duduo always takes the longest to train, making the bot train for a way longer timer than neccessary.

Just add Doduo to the file blacklist.lua.

The blacklist has been disabled. I am working on a more advanced team selection system.
Expect terrible teams until then. :D


Fix the markdown and refine syntax

This PR fixes broken links in the Python page and refine markdown syntax on several pages by inserting newlines.
Broken links
https://cylondata.org/docs/python

@shuuji3 Thank you for the PR.


Issue with suffix functions

I'm incorporating this library into a project where I want to let users create formulas that check against certain fields. This is mostly working, but I've hit a small roadblock when trying to create a x exists suffix operator that basically checks x != nil. This generally works, but fails in certain nesting conditions.
It might have to do something with operator precedence, as changing the order fixes one case but then causes another test case to fail. I'd appreciate some feedback on how to fix this or how to debug this.
The strange thing is that it works fine perfectly if it's a prefix operator (didset X in my example), though I'd prefer the suffix variant.
The full code sample is here, which is a minor modification of the code from the template example in this repo:  https://gist.github.com/nighthawk/060475d0ded20788e9269054e152d76d
Any help would be much appreciated!

Hi @nighthawk,
Thanks for reporting this issue, very useful finding!
I took some time reviewing the related code paths, looks like it's related to an issue with embedding expressions in parentheses. It is not a trivial fix, might take some more time, so I'm letting you know I'm working on a fix.
In the meantime, you are free to use prefix expressions with equivalent functionality - it's just the syntax that differs - which works as expected.

Status update: I managed to identify the issue. The expression "(toggle == true) and (url exists)" fails because the nested parentheses caused an issue, and the expression matcher only processes the string until the "(toggle == true) and (url" part, and not prioritizing the "url exists" expression.
Note: it works without the parentheses, if the suffix function "exists" has a higher priority than "and"


Files are left in the VHD

The directory/files %systemdrive%\Bits\PSWindowsUpdate and Convert-WindowsImageInfo.txt are left on the VHD and should be removed.

Good point

I have a fix almost ready and will be able to create a pull request tomorrow.


Showing difference between two json objects

I cannot figure out how I would go about doing this.
I looked into the patch function and thought about applying it to a default state of the object but suppose a key is set to boolean true while the default is false but the two objects don't differ in this key then applying the patch to the default and looking at the default would indicate this value has changed to false.
Essentially I just want a diff with minimal extra tooling.

Have you tried the diff function?

Ah good call, this was towards the end of the work day as I was despairing :+1:
So the the diff function returns me a patch object with json pointers, I assume I can then look at the pointers to see which specific keys have changed.
I will try and paste the solution here.

::diff was what I needed, thank you. I ended up just writing parts of the object that the diff had an op for to file, I had to parse the json path
{     "op": "replace",     "path": "/XX/YY/0/centerFrequencyInHz",     "value":<PHONE_NUMBER>.0   },
To create the nested structure with {"XX" : {"YY": [{"centerFrequencyInHz" :<PHONE_NUMBER>.0 }
but this is fine, I assume there isn't much need for the library to provide something like substract(left, right, patch) which would output that directly.


Bad Alloc Testing

This patch provides some small updates to enable catching and
handling when memory runs out (std::bad_alloc). Specifically,
when this happens, we can no longer use std::cout which
does many allocations in the process. Instead we exit
gracefully with an error code.
Signed-off-by: “Rian<EMAIL_ADDRESS>

Coverage remained the same at 100.0% when pulling b17d6a9d07e9e5d1275182aaaf49ca511c920130 on rianquinn:bad_alloc into acd0aaceb9a2dbbeb6fad294ec8f189140bf86ec on Bareflank:master.

Coverage remained the same at 100.0% when pulling 5b01e8ce80821816a8283c90f262ab0a3cb94de0 on rianquinn:bad_alloc into acd0aaceb9a2dbbeb6fad294ec8f189140bf86ec on Bareflank:master.


:sparkles: feature Remove dependency on KCP SyncTarget and Location resources

Create Kubestellar SyncTarget and Location resources and remove references to KCP's SyncTarget and Location resources

Summary
Related issue(s)
Issue 559
Issue 560
Fixes #

/lgtm

@fileppb : as you noted earlier, moving the relevant SyncTarget and Location exports from the root workspace to the root:espw workspace adds an ordering constraint in the usage.  https://github.com/fileppb/edge-mc/blob/0e6e3f90c12020bcba9cc409c2278f8a4e8c6108/docs/content/Coding Milestones/PoC2023q1/example1-subs/example1-post-kcp.md?plain=1#L8 is now out of order because it depends on the later line https://github.com/fileppb/edge-mc/blob/0e6e3f90c12020bcba9cc409c2278f8a4e8c6108/docs/content/Coding Milestones/PoC2023q1/example1-subs/example1-post-kcp.md?plain=1#L110 .  And there are other mis-orderings too.

I do not understand how https://github.com/kubestellar/kubestellar/actions/runs/5626329356 succeeded.  When I test the same commit (0e6e3f90c12020bcba9cc409c2278f8a4e8c6108) myself, it fails due to that mis-ordering.  Here is what I see after the attempt to use the not-yet-existing APIExport fails:
(venv) %n@%m %1~ %# kubectl ws root
Current workspace is "root".
(venv) %n@%m %1~ %# kubectl ws tree
.
└── root
    ├── compute
    └── imw-1

If I manually issue the kubestellar init command and then switch back to the IMW, then the ensure location succeeds.

@MikeSpreitzer Hi Mike, is there something that I need to revise in this code?

@fileppb : what needs revisions is the documents that tell users to kubectl kubestellar ensure location before kubestellar init.

Silly documents. How could you not do init before start and everything else, especially since that's in the quick start? But ok this is a new issue: bugfix 817, so needs new branch etc. Can this wait a day?

Before your move of the definitions of SyncTarget and Location, some of the commands did not rely on the ESPW because the relevant APIExport was put in the root workspace by kcp start.
Also: #817 is not about any bugs in what you did, it is about how the testing did not reveal the problems.


HTTPS issue to local registry:2

I've setup a docker-compose stack with docker registry:v2 and craneoperator. It worked fine with http-only. I've added mkcert local https authority.
I can reach my registry using https://registry-api.php-stack.docker:5000/ (desktop chrome says fine to https-cert).
But craneoperator web-ui tells me:
Error loading data from Registry
status code: 500

This is my stack simplyfied:
version: "3.7"

networks:
  default:
    name: php-stack.local
    external: true

volumes:
  cert-storage:
    name: php-stack-cert-storage
    driver: local
    driver_opts:
      type: none
      device: "$HOME/.local/share/mkcert"
      o: bind

  docker-registry-storage:
    name:  php-stack-docker-registry-storage
  docker-registry-config:
    name:  php-stack-docker-registry-config
  docker-registry-ui-auth:
    name:  php-stack-docker-registry-ui-auth
  docker-registry-ui-certs:
    name:  php-stack-docker-registry-ui-certs
  composer-cache:
    name: php-stack-composer-cache

services:
  cert-backend:
    image: vishnunair/docker-mkcert
    restart: "no"
    environment:
      domain: "*.php-stack.docker,<IP_ADDRESS>:5000"
    volumes:
      - "cert-storage:/root/.local/share/mkcert"

  docker-registry:
    image: registry:2
    restart: on-failure
    hostname: registry-api.php-stack.docker
    ports:
      - "<IP_ADDRESS>:5000:5000/tcp"
    networks:
      - default
    environment:
      #REGISTRY_HTTP_ADDR: "<IP_ADDRESS>:5000"
      REGISTRY_HTTP_TLS_CERTIFICATE: "/certs/_wildcard.php-stack.docker.pem"
      REGISTRY_HTTP_TLS_KEY: "/certs/_wildcard.php-stack.docker-key.pem"
    volumes:
      - "cert-storage:/certs"
      - "docker-registry-storage:/var/lib/registry"
      - "docker-registry-config:/etc/docker/registry"

  docker-registry-ui:
    image: parabuzzle/craneoperator:latest
    restart: on-failure
    depends_on:
      - docker-registry
    hostname: registry.php-stack.docker
    networks:
      - default
    environment:
      REGISTRY_HOST: registry-api.php-stack.docker
      REGISTRY_PORT: 5000
      REGISTRY_PROTOCOL: https
      REGISTRY_SSL_VERIFY: false
      REGISTRY_ALLOW_DELETE: true
    volumes:
      # tried to make craneoperator trust the mkcert's too -- but no luck
      - "cert-storage:/usr/local/share/ca-certificates/"

Just to avoid the question - yes there are certs created by dockerized mkcert on my local-machine:
ls -lah $HOME/.local/share/mkcert
rootCA-key.pem
rootCA.pem
_wildcard.php-stack.docker-key.pem
_wildcard.php-stack.docker.pem

Any suggest? I currently have no live deployment for craneoperator to check ssl works fine there. But I think this should work somehow to if the SSL cert works at all for local development?
I would like to run the registry in https because docker and some other local gitlab-ci begin to suck about non-ssl requests to registry. Hacking my local docker daemon.json to trust insecure-registry is already done, but gitlab-ci runners on my local machine using docker:dind won't have this and that makes everything too confusing.

Wow... that's funny. I think I've partly resolved my own ticket.
I've tested around and opened a shell in craneoperator docker-container. After running update-ca-certificates immediately the error in web-ui is gone and obviously everything works, at least until the container restarts.
I think it would make sense to run that command in docker-entrypoint or at least give an option to do so if required (or if there are files in '/usr/local/share/ca-certificates/').
update-ca-certificates

I've patched locally like this:
docker/craneoperator/Dockerfile
FROM parabuzzle/craneoperator:latest

ADD --chmod=+x ./docker-entrypoint.sh /docker-entrypoint.sh

ENTRYPOINT ["sh", "/docker-entrypoint.sh"]
CMD ["bundle", "exec", "foreman", "start"]

docker/craneoperator/docker-entrypoint.sh
#!/bin/sh
set -e

if [ $(ls -1 /usr/local/share/ca-certificates/ | wc -l) -ne 0 ];
then
  update-ca-certificates
fi

if [ $# -gt 1 ] && [ x"$1" = x"/bin/sh" ] && [ x"$2" = x"-c" ]; then
  shift 2
  eval "set -- $1"
fi

exec "$@"


respect hash and ensure it gets scrolled to

Published PR with canary version: 1.10.8-canary.115.1651


About offline upgrade

I'm looking at the upgrade instructions for 0.8.1 to 1.0.0, and as a pre-req it looks to require detaching all longhorn volumes in use prior to the upgrade.  This is very disruptive imo, but since this is moving from a beta version to GA maybe this is a one time requirement.  Just to be sure though, are there plans in future upgrades post 1.0 to allow for upgrading without the need to detach or affect any longhorn volumes in use?

Hi @mshack70
Our goal is the future upgrade shouldn't involve offline upgrade. We're still stabilizing the live upgrade framework, so it might change during the major releases (e.g. v1.0.0 to v1.1.0), but it should be good for patch version upgrade (e.g. v1.0.0 to v1.0.1). We will definitely try not to disrupt the live upgrade path even for the major releases.

Ok thanks, yeah I think it would be hard to use this for production if we have to detach PV's from applications for upgrades.  Hopefully this should be a high priority goal for future releases.  Thanks for the response.

In fact it's already a top priority item. The design guarantees that no function changes should be made to the live upgrade framework, it's hard to predict if there will be anymore bugs.


CoffeeScript problem

Hi,
Your plugin do not support CoffeeScript but still format it when saving (On save enabled).
it screws my doc block:
###
@ngdoc directive
@name wordpress-hybrid-client:wphcLoader
@restrict E
@description
A simple loader
@example
<pre>
</pre>
###

to this:
###
@ngdoc directive
@name wordpress - hybrid - client: wphcLoader
@restrict E
@description
A simple loader
@example
       < pre >
</pre >
###

When your plugin is disabled it is fine.
Thanks

Actually it seems that you support CoffeeScript but I do not see any specific options for it in the settings.

A really good feature would be to be able to activate/desactivate a specific file format. For instance this plugins https://github.com/atom/language-coffee-script seems to handle coffeescript better.
Cheers

CoffeeScript beautification support comes from https://github.com/derekchiang/Coffee-Formatter which is unfortunately not actively maintained. I am open to any alternatives.

For instance this plugins https://github.com/atom/language-coffee-script seems to handle coffeescript better.

That supports CoffeeScript beautification?

@Glavin001, @shprink I've been working on an npm module for coffee script reformatting, (like changing tabs to  arbitrary # of spaces or vice versa).  It's built on top of coffee-scripts own tokenizer (which is still pretty ambiguous).  Still very much beta, but it does at least transform the above docblock correctly.
Maybe you guys could check it out see how it performs.
https://www.npmjs.com/package/coffee-fmt

Great @sterpe ! I would love to support this and switch from Coffee-Formatter to your Coffee-fmt. Let me know once you think it's at an acceptable state for switching over and what the Node API is that I can use (see https://github.com/Glavin001/atom-beautify/blob/master/lib/langs/coffeescript-beautify.coffee ). Thanks!

Hey @sterpe, what is the status of coffee-fmt? If you are confident that it can replace Coffee-Formatter than I can support that. Let me know what you think :smiley:.

Published to v0.26.0
coffee-fmt is now the default CoffeeScript beautifier, deprecating Coffee-Formatter. Thanks for the awesome work so far, @sterpe !


Potential backwards-incompatible [for rocket-chip] changes to be made in Chisel3

[ ] package Chisel => package chisel
[ ] chiselMain => Driver.elaborate (with no wrapping of top level module)
[ ] trait FileSystemUtilities => object FileUtils
[ ] remove Module and Bundle factory methods that apply new params as partial functions => paramsScope

@hcook does this need to be open still?

Rocket-chip will stay on the compatibility layer.
We are no longer planning to rename chisel3 -> chisel, and Chisel will remain as the compatibility package.


Carousel no-wrap doesn't do anything

I have used angular-ui on three projects so far and have yet to get the no-wrap to do anything.  I assume I am doing something wrong but I've tried a bunch of things and it should really be in the documentation.  How do I stop carousel from wrapping?  I have used <carousel no-wrap="true">, <carousel no-wrap="false">, and <carousel no-wrap="noWrap"> and none work.

It should work if that noWrap variable is a bool (check the demo).
Still, I am checking the implementation and I am going to change it internally.

Closing due to lack of actionable information.
It should be noted that we have unit tests that cover this, so I highly suspect this is not a bug in the library.


Using the API Key shows an error in the browser console

Describe the bug
When rendering the map with an API key I get this error on my console:
Loading the Google Maps JavaScript API without a callback is not supported: https://developers.google.com/maps/documentation/javascript/url-params#required_parameters

To Reproduce
Steps to reproduce the behavior:

Render a map with an API key
See error on the browser console

Suggested solution(s)
Adding the callback  query string here should fix:
https://github.com/giorgiabosello/google-maps-react-markers/blob/76767785ea89ddfaf1997254b32cc5a9a3671675/src/hooks/useGoogleMaps.js#L9
We could store a user provided function into a safe global name and pass it as callback

An empty noop callback might do the trick?

Added a default noop function to window.googleMapsCallback. You can override it by passing scriptCallback to the GoogleMap component.


v3 dynamic pageTransition

Describe the feature
in a Nuxt v2 page you could pass a function to transition and have a from and a to ready - this allows you to dynamically decide page transitions, in v3 I don't see how this is possible:
I tried something basic like :
const router = useRouter()
const route = useRoute()
const step =  Array.isArray(route.params.step) ? 0 : parseInt(route.params.step)
const prev = router.options.history.state.back
const prevStep = prev && typeof prev === "string" ? parseInt(prev.replace('/step/', '')) : 0
const transition = prevStep < step ? 'page-left-to-right' : 'page-right-to-left'

definePageMeta({
  pageTransition: {
    name: transition,
  },
})

this results in
[nuxt] [request error] [unhandled] [500] transition is not defined

Is this at all possible? and if so how?
Additional information

[X] Would you be willing to help implement this feature?
[ ] Could this feature be implemented as a module?

Final checks

[X] Read the contribution guide.
[X] Check existing discussions and issues.

Happy to close this issue then @acidjazz ?

sure @Atinux ! funny i keep coming back to this for other projects as the example - simpler version might be useful on the docs


"These linked pull requests are closed" should only be commented if any are counted

"These linked pull requests are closed" should only be commented if any are counted. I've seen in Draeieg's quality assurance examples it posting a comment like that without closing any.
https://github.com/ubiquity/ubiquibot/blob/48e006da17c46cc172263fe9a3924cd90a0f3bcb/src/handlers/assign/action.ts#L78-L83

/assign

/wallet 0xCee33C98410DEbe67A319Cb94F39e403435Df319

@pavlovcik , its already fixed. Seems this issue is not needed.
Could you take a look at this?
``
Mentioned Draeieg 's QA example was the old one.

Oh I see. So then I should never refer to the QA repository for proactively filing issues. Instead I should wait until it's in production.
If you are sure that this solves the issue, we can credit the bounty hunter for their work and not merge.
Can you please review their pull request and leave your feedback? Maybe they improved the implementation?


RTL languages

When init the material app with RTL language, the close button will switch sides and will be located wrongly.
In addition, you can see that small part of the text is begin occluded by the widget decorations. (this happens in both rlt and ltr languages)
screenshot:

Thanks for responding!
I'm using hebrew (use Locale("he") when constructing your MeterialApp) and you can copy paste this text: "כתובת דואל אינה קיימת. יש לבצע רישום למערכת"
I believe you can also reproduce it by wrapping everything with:
Directionality(
    textDirection: TextDirection.ltr,
    child: AwesomeSnackbarContent(...),
)

This will force the direction of everything to be left-to-right regardless of the app's direction.

Fixed, updating new version in a while

much appreciated! thanks for really awesome snack bar design :)


Nats

Related to #318
Needs to be merge after #319
This pull request replaces Kakfa and Zookepper messaging by NATS
Verification
$ ./swarm stop
$ ./swarm pull
$ ./swarm start
$ make test

This is fantastic! Thanks @bertrand-quenin 👍


Small typo fix

Just a small typo fix...
It should be "This certificate authenticates the Linux or ..".
Not "This certificate authenticates the Linus or .." :-)
thanks,
br

@itreptil good catch! I wonder how long that's been like that....


sys/linux: fix make extract on latest linux-next

VIRTIO_F_IOMMU_PLATFORM was renamed to VIRTIO_F_ACCESS_PLATFORM to match the latest virtio spec.
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/include/uapi/linux/virtio_config.h?id=321bd212619a7269308696e4ddc446930ea73fad

Thanks. Please also add the .const file changes to the commit.

There are no .const file changes.

@googlebot I fixed it.

@googlebot I fixed it.

There are no .const file changes. The constant is used to derive a value for VIRTIO_IOMMU_PLATFORM so the renamed constant never appears in the .const files

Right! It's only used in our define, so the end result is not changed.


61-fixing-bugs-header-members-pages

Changing header logo
Fixing members page banner title
fixing my project link in burger menu


use dtParameters.sColumnNames when searching

I noticed that even if I'm using ArrayOutputType.ArrayOfObjects when returning data to datatable, when searching the code ignores the "object-like" behaviour and uses the old-style index based logics.
To obtain the same behaviour of ArrayOutputType.ArrayOfObjects also in searching feature, I think that accessing columns by looking at the PropertyInfoNames is more consistent and doesn't push you to maintain a specific column order, exactly like you expect when you want to manage data in ArrayOutputType.ArrayOfObjects mode.
Hope this could help

Sadly, it's been so long since I've worked on this, and I've got so little
time, it's hard to do a full review, especially with regards to maintaining
backward compatibility.
So,
q1 is this backward compatible? Or will this break existing people of I
merge and they upgrade?
Q2 Do all the example projects work properly?
On Sat, 18 Jul 2020, 15:16 lafadot<EMAIL_ADDRESS>wrote:

I noticed that even if I'm using ArrayOutputType.ArrayOfObjects when
returning data to datatable, when searching the code ignores the
"object-like" behaviour and uses the old-style index based logics.
To obtain the same behaviour of ArrayOutputType.ArrayOfObjects also in
searching feature, I think that accessing columns by looking at the
PropertyInfoNames is more consistent and doesn't push you to maintain a
specific column order, exactly like you expect when you want to manage data
in ArrayOutputType.ArrayOfObjects mode.
Hope this could help
You can view, comment on, or merge this pull request online at:
https://github.com/mcintyre321/mvc.jquery.datatables/pull/182
Commit Summary

use dtParameters.sColumnNames when names are filled, to obtain the
same behaviour of ArrayOutputType.ArrayOfObjects also in searching feature.

File Changes

M Mvc.JQuery.DataTables.Common/DataTablesFiltering.cs
https://github.com/mcintyre321/mvc.jquery.datatables/pull/182/files#diff-be3149dc2b42707d50cf7a47b9286e4f
(14)

Patch Links:

https://github.com/mcintyre321/mvc.jquery.datatables/pull/182.patch
https://github.com/mcintyre321/mvc.jquery.datatables/pull/182.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mcintyre321/mvc.jquery.datatables/pull/182, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACDJ6T3WVANGBHS6364MSDR4GVDFANCNFSM4O76Y7WQ
.

As I can see, DataTablesParam.sColumnNames is initialized only in BinV10Model.
Also, it is used in filtering code only if dtParameters.sColumnNames.Count> 0 and anyway there's a check if sColumnsName[i] is matching any propertyinfo name, so I think that it could be backward compatible.
I ran the example project, and it seems that search is working, anyway I can't be 100% sure because folder it seems Content/jquery-datatables-column-filter folder is included in project but not on github (maybe I dont know how to restore it in project once cloned repository?)

jquery-datatables-column-filter gets included via embdedde resources, as i recall?
Did both example projects work?
Well I'll merge and we'll see if anything explodes!


[Request] Remove the Preview Window

The Preview Window is just a duplicate of the canvas. With zoom on the Canvas functional there is no additional purpose (and it has hooks into the rendering that should not be present).

Working on this now.

Resolved with this change.


Add fixed-resizable-hybrid to plugin hub

Plugin that reskins the "Resizable - Classic Layout" by styling it to match the aesthetics of Fixed Mode. It provides a faithful representation of the fixed mode interface, while preserving the benefits of resizable mode, such as a larger game viewport and minimizable chat.

cool plugin!


Allow testing for type enum

As far as I know, all enums have the same properties / methods. In other words, they all act the same. I see no reason why we shouldn't be able to test if a value is an enum and then perform enum-y tasks on it.
For example, I have a BehaviorSubject that persists values on add to shared_preferences in Flutter. I support numbers, strings, and lists of strings. I'd like to also support enums but I can't because I cannot test if an incoming value is an enum.

This would also enable extension methods on enums.

We can already do extension methods on enums. Use them all the time.

@eernstg did I see you write on another issue that this is implemented in Dart 2.14?

Yes, class Enum is a supertype of every enum type, and it was added in 43cff263654c0511c058d9a19ece1c87a906ea6d, Jun 25 2021. It wasn't associated with a language version, but it is present in dart-pad as of today (SDK 2.14.0).


Add D♭♭

Adding a language

[x] The code displays "Hello World"
[x] I have updated the readme to include the new language

What are the differences between this language and C?
https://github.com/leachim6/hello-world/blob/4222cdd7e87933295e5e8f38d5c08a1975579afd/c/C.c#L1-L6

IDK I found it on esoteric langs

Maybe it’s like a R and python situation


Fix promise reject cannot be catched

Fix #1310

Codecov Report
Base: 36.55% // Head: 37.79% // Increases project coverage by +1.23% :tada:

Coverage data is based on head (60c1217) compared to base (ab3c82c).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1312      +/-   ##
==========================================
+ Coverage   36.55%   37.79%   +1.23%
==========================================
  Files         349      349
  Lines       16721    16721
  Branches     2618     2618
==========================================
+ Hits         6113     6319     +206
+ Misses      10052     9807     -245
- Partials      556      595      +39

Impacted Files
Coverage Δ

packages/core/src/asset/ResourceManager.ts
21.93% <0.00%> (ø)

packages/core/src/Scene.ts
68.26% <0.00%> (+1.19%)
:arrow_up:

packages/core/src/shadow/ShadowUtils.ts
3.22% <0.00%> (+1.29%)
:arrow_up:

packages/core/src/Transform.ts
49.30% <0.00%> (+1.73%)
:arrow_up:

packages/math/src/Vector2.ts
78.43% <0.00%> (+1.96%)
:arrow_up:

packages/math/src/Color.ts
62.37% <0.00%> (+1.98%)
:arrow_up:

packages/core/src/Component.ts
78.37% <0.00%> (+2.70%)
:arrow_up:

packages/core/src/Engine.ts
83.41% <0.00%> (+2.84%)
:arrow_up:

packages/core/src/RenderPipeline/Basic2DBatcher.ts
42.45% <0.00%> (+3.77%)
:arrow_up:

packages/core/src/ComponentsManager.ts
66.66% <0.00%> (+3.80%)
:arrow_up:

... and 10 more

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Certain logs in ECS/container don't get to Splunk

Check CONTRIBUTING guideline first and here is the list to help us investigate the problem.

fluentd or td-agent version (and other plugin information)

2019-03-29 07:09:54 +0000 [info]: starting fluentd-1.3.3 pid=27 ruby="2.4.5"
2019-03-29 07:09:54 +0000 [info]: spawn command to main:  cmdline=["/opt/td-agent/embedded/bin/ruby", "-Eascii-8bit:ascii-8bit", "/usr/sbin/td-agent", "--daemon", "/var/run/td-agent/td-agent.pid", "--log", "/var/log/td-agent/td-agent.log", "--under-supervisor"]
2019-03-29 07:09:56 +0000 [info]: gem 'fluent-plugin-elasticsearch' version '3.0.1'
2019-03-29 07:09:56 +0000 [info]: gem 'fluent-plugin-kafka' version '0.8.3'
2019-03-29 07:09:56 +0000 [info]: gem 'fluent-plugin-record-modifier' version '1.1.0'
2019-03-29 07:09:56 +0000 [info]: gem 'fluent-plugin-rewrite-tag-filter' version '2.1.1'
2019-03-29 07:09:56 +0000 [info]: gem 'fluent-plugin-s3' version '1.1.7'
2019-03-29 07:09:56 +0000 [info]: gem 'fluent-plugin-splunk-http-eventcollector' version '0.3.0'
2019-03-29 07:09:56 +0000 [info]: gem 'fluent-plugin-td' version '1.0.0'
2019-03-29 07:09:56 +0000 [info]: gem 'fluent-plugin-td-monitoring' version '0.2.4'
2019-03-29 07:09:56 +0000 [info]: gem 'fluent-plugin-webhdfs' version '1.2.3'
2019-03-29 07:09:56 +0000 [info]: gem 'fluentd' version '1.3.3'
2019-03-29 07:09:56 +0000 [info]: gem 'fluentd' version '0.12.43'
2019-03-29 07:09:56 +0000 [info]: adding filter pattern="dashboard**.**" type="record_modifier"
2019-03-29 07:09:56 +0000 [info]: adding match pattern="dashboard**.**" type="splunk-http-eventcollector"
2019-03-29 07:09:56 +0000 [info]: adding match pattern="nginx_access.log" type="splunk-http-eventcollector"

Environment information:

Operating system: cat /etc/os-release

NAME="Ubuntu"
VERSION="14.04.6 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.6 LTS"
VERSION_ID="14.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"

- Kernel version: `uname -r`

4.15.0-1034-aws

- Docker version:

# docker version
Client:
 Version:           18.09.4
 API version:       1.39
 Go version:        go1.10.8
 Git commit:        d14af54266
 Built:             Wed Mar 27 18:35:44 2019
 OS/Arch:           linux/amd64
 Experimental:      false

- ECS Agent version:  1.26.1

Your configuration

2019-03-29 07:09:54 +0000 [info]: using configuration file: <ROOT>
  <source>
    @type tail
    path "/data/log/production_ls_json.log"
    pos_file "/tmp/production_json.pos"
    tag "dashboard_production_json.log"
    path_key "logfile"
    format json
    <parse>
      @type json
    </parse>
  </source>
  <source>
    @type tail
    path "/data/log/dashboard_logger_production.log"
    pos_file "/tmp/dashboard_log.pos"
    tag "dashboard_logger.log"
    path_key "logfile"
    format multiline
    format_firstline /^[DFEWI],/
    format1 /^(?<loglevel>[DFEWI]), \[(?<hosttime>[^ ]*) (?<pid>[^\]]*)\] (?<severity>[DEBUG|FATAL|ERROR| WARN| INFO]*) -- : (?<message>.*)/
    <parse>
      format_firstline /^[DFEWI],/
      @type multiline
      format1 /^(?<loglevel>[DFEWI]), \[(?<hosttime>[^ ]*) (?<pid>[^\]]*)\] (?<severity>[DEBUG|FATAL|ERROR| WARN| INFO]*) -- : (?<message>.*)/
    </parse>
  </source>
  <filter dashboard**.**>
    @type record_modifier
    remove_keys "@timestamp,@version,host,cluster,class_name,tags,_dummy_,_dummy1_"
    <record>
      client_name client9
      _dummy_ ${if record.has_key?('class_name'); record['logger'] = record['class_name'].to_s; end}
      _dummy1_ ${if record.has_key?('severity'); record['severity'].strip!; end}
    </record>
  </filter>
  <source>
    @type tail
    path "/data/var/log/nginx/*.access.log"
    pos_file "/tmp/nginx_log.pos"
    tag "nginx_access.log"
    path_key "logfile"
    format /^(?<remote>[^ ]*) - - \[(?<isotime>[^\]]*)\] \[(?<utime>[^ ]*)\] -> \[(?<host>[^ ]*)\] (?<code>[^ ]*) "(?<method>\S+)(?: +(?<path>[^ ]*) +\S*)?" \[(?<mime_type>[^\]]*)\] \[(?<size>[^ ]*)\] \[(?<http_accept>[^\]]*)\] \[(?<bytes_sent>[^ ]*)\] "(?<referrer>[^\"]*)" "(?<agent>[^\"]*)" "(?<forwarded_for>[^\"]*)" \[(?<request_time>[^ ]*)\] \[(?<request_length>[^ ]*)\] \[(?<pipe>[^ ]*)\] \[(?<connection>[^ ]*)\] \[(?<connection_requests>[^ ]*)\] \[(?<session>[^ ]*)\]/
    <parse>
      @type regexp
      expression ^(?<remote>[^ ]*) - - \[(?<isotime>[^\]]*)\] \[(?<utime>[^ ]*)\] -> \[(?<host>[^ ]*)\] (?<code>[^ ]*) "(?<method>\S+)(?: +(?<path>[^ ]*) +\S*)?" \[(?<mime_type>[^\]]*)\] \[(?<size>[^ ]*)\] \[(?<http_accept>[^\]]*)\] \[(?<bytes_sent>[^ ]*)\] "(?<referrer>[^\"]*)" "(?<agent>[^\"]*)" "(?<forwarded_for>[^\"]*)" \[(?<request_time>[^ ]*)\] \[(?<request_length>[^ ]*)\] \[(?<pipe>[^ ]*)\] \[(?<connection>[^ ]*)\] \[(?<connection_requests>[^ ]*)\] \[(?<session>[^ ]*)\]
    </parse>
  </source>
  <match dashboard**.**>
    @type splunk-http-eventcollector
    server "http-inputs-test.splunkcloud.com"
    protocol "https"
    token "XXXXXX"
    host "ip-yyyy"
    index "dev_apps_logging"
    source "dashboard"
    sourcetype "ruby_apps"
    all_items true
    buffer_type "memory"
    buffer_chunk_limit 700k
    batch_size_limit 1000000
    flush_interval 2s
    <buffer>
      flush_mode interval
      retry_type exponential_backoff
      @type memory
      flush_interval 2s
      chunk_limit_size 700k
    </buffer>
  </match>
  <match nginx_access.log>
    @type splunk-http-eventcollector
    server "http-inputs-test.splunkcloud.com"
    protocol "https"
    token "XXXXXX"
    host "ip-yyyy"
    source "access_logs"
    sourcetype "ruby_apps"
    all_items true
    source "access_logs"
    sourcetype "ruby_apps"
    all_items true
    buffer_type "memory"
    buffer_chunk_limit 700k
    batch_size_limit 1000000
    flush_interval 2s
    <buffer>
      flush_mode interval
      retry_type exponential_backoff
      @type memory
      flush_interval 2s
      chunk_limit_size 700k
    </buffer>
  </match>
</ROOT>

Your problem explanation. If you have an error logs, write it together.

These two logs get pushed to Splunk when I use Fluentd in a container on my Mac.
When in an ECS container, the first log makes it, the second one doesn't. I'm using ECS agent version 1.26.1 and docker
Logs
I, [2019-03-29T16:34:40.667475 #178]  INFO -- : ---db_monitor dbmonitor finished in 0.01
E, [2019-03-29T16:34:44.912765 #178] ERROR -- : list_patients gets called, but failed[#Rescued Error => undefined method `user_level' for nil:NilClass :: /data/apps/current/app/utils/site_staff.rb:364:in `list_patients'

Something like this also does not make it to Splunk. This works locally in a container, but does not get pushed to Splunk in ECS/container.
{"service":"dashboard_ror","cluster":"ip-246","message":"create gets called, but failed[#Rescued Error =\u003E undefined method `iso8601' for \"2019-03-28T19:59:50.029Z\":String :: /usr/local/rvm/gems/ruby-1.9.3-p392/gems/logstash-event-1.2.02/lib/logstash/event.rb:107:in `to_s'\n/data/apps/current/app/workers/modules/sso/sso.rb:31:in `inspect'\n/data/apps/current/app/workers/modules/sso/sso.rb:31:in `inspect'\n/data/apps/current/app/workers/modules/sso/sso.rb:31:in `inspect'\n/data/apps/current/app/workers/modules/sso/sso.rb:31:in `inspect'\n/data/apps/current/app/workers/modules/sso/sso.rb:31:in `inspect'\n/data/apps/current/app/workers/modules/sso/sso.rb:31:in `inspect'\n/data/apps/current/app/workers/modules/sso/sso.rb:31:in `inspect'\n/data/apps/current/app/workers/modules/sso/sso.rb:31:in `verified?'\n/data/apps/current/app/controllers/sessions_controller.rb:74:in `create'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/implicit_render.rb:4:in `send_action'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/base.rb:167:in `process_action'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rendering.rb:10:in `process_action'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/callbacks.rb:18:in `block in process_action'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:459:in `block in _run__1167298983658507982__process_action__2792552851109248203__callbacks'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:215:in `block in _conditional_callback_around_2750'\n/data/apps/current/app/controllers/benchmark_filter.rb:5:in `filter'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:321:in `around'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:310:in `_callback_around_425'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:214:in `_conditional_callback_around_2750'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:447:in `_run__1167298983658507982__process_action__2792552851109248203__callbacks'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:405:in `__run_callback'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:385:in `_run_process_action_callbacks'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:81:in `run_callbacks'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/callbacks.rb:17:in `process_action'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rescue.rb:29:in `process_action'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:30:in `block in process_action'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:123:in `block in instrument'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/instrumenter.rb:20:in `instrument'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:123:in `instrument'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:29:in `process_action'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/params_wrapper.rb:207:in `process_action'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activerecord-<IP_ADDRESS>/lib/active_record/railties/controller_runtime.rb:18:in `process_action'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/base.rb:121:in `process'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/rendering.rb:45:in `process'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal.rb:203:in `dispatch'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rack_delegation.rb:14:in `dispatch'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal.rb:246:in `block in action'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:73:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:73:in `dispatch'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:36:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/journey-1.0.4/lib/journey/router.rb:68:in `block in call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/journey-1.0.4/lib/journey/router.rb:56:in `each'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/journey-1.0.4/lib/journey/router.rb:56:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:608:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/recurring_select-1.3.1/app/middleware/recurring_select_middleware.rb:24:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/best_standards_support.rb:17:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-1.4.7/lib/rack/etag.rb:23:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-1.4.7/lib/rack/conditionalget.rb:35:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/head.rb:14:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/params_parser.rb:21:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/flash.rb:242:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-1.4.7/lib/rack/session/abstract/id.rb:210:in `context'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-1.4.7/lib/rack/session/abstract/id.rb:205:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/cookies.rb:341:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activerecord-<IP_ADDRESS>/lib/active_record/query_cache.rb:64:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/connection_pool.rb:479:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/callbacks.rb:28:in `block in call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:405:in `_run__316997000888980778__call__1646723128461599002__callbacks'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:405:in `__run_callback'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:385:in `_run_call_callbacks'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:81:in `run_callbacks'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/callbacks.rb:27:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/remote_ip.rb:31:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/debug_exceptions.rb:16:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/show_exceptions.rb:56:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-<IP_ADDRESS>/lib/rails/rack/logger.rb:32:in `call_app'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-<IP_ADDRESS>/lib/rails/rack/logger.rb:16:in `block in call'\n/data/apps/current/app/workers/modules/ai_logging.rb:591:in `tagged'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-<IP_ADDRESS>/lib/rails/rack/logger.rb:16:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/request_id.rb:22:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-1.4.7/lib/rack/methodoverride.rb:21:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-1.4.7/lib/rack/runtime.rb:17:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/cache/strategy/local_cache.rb:72:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-1.4.7/lib/rack/lock.rb:15:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-cache-1.6.1/lib/rack/cache/context.rb:140:in `forward'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-cache-1.6.1/lib/rack/cache/context.rb:147:in `pass'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-cache-1.6.1/lib/rack/cache/context.rb:159:in `invalidate'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-cache-1.6.1/lib/rack/cache/context.rb:74:in `call!'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-cache-1.6.1/lib/rack/cache/context.rb:51:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-cors-1.0.3/lib/rack/cors.rb:95:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-<IP_ADDRESS>/lib/rails/engine.rb:484:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-<IP_ADDRESS>/lib/rails/application.rb:231:in `call'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-<IP_ADDRESS>/lib/rails/railtie/configurable.rb:30:in `method_missing'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:580:in `process_client'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:674:in `worker_loop'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:529:in `spawn_missing_workers'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:140:in `start'\n/usr/local/rvm/gems/ruby-1.9.3-p392/gems/unicorn-4.9.0/bin/unicorn_rails:209:in `\u003Ctop (required)\u003E'\n/usr/local/rvm/gems/ruby-1.9.3-p392/bin/unicorn_rails:23:in `load'\n/usr/local/rvm/gems/ruby-1.9.3-p392/bin/unicorn_rails:23:in `\u003Cmain\u003E'\n/usr/local/rvm/gems/ruby-1.9.3-p392/bin/ruby_executable_hooks:24:in `eval'\n/usr/local/rvm/gems/ruby-1.9.3-p392/bin/ruby_executable_hooks:24:in `\u003Cmain\u003E'] Process.ppid = 162 Process.pid = 181 Thread.current.object_id=14927980","method":"/app/controllers/sessions_controller.rb:161:in `rescue in create'","class_name":"SessionsController","@timestamp":"2019-03-28T19:59:50.039Z","@version":"1","severity":"ERROR","host":"ip-172-30-6-246","tags":["req","req_uuid:1ed853693bee94f0","req_class:Session","req_action:create","req_ajax:non-ajax","req_method:POST","req_remote:<IP_ADDRESS>","req_url:http://client9dev.aicure.com/login","req_time:1553803190029","req_sess_id:BAh7BzoQX2NzcmZf","req_sess_uid:","req_sess_tkn:NONE"]}

It seems that Fluentd is not related.
Fluentd does not output the logs you described.
The first log said:

undefined method user_level' for nil:NilClass :: /data/apps/current/app/utils/site_staff.rb:364:in list_patients'

What is /data/apps/current/app/utils/site_staff.rb?
The second log said:
create gets called, but failed[#Rescued Error =\u003E undefined method `iso8601' for \"2019-03-28T19:59:50.029Z\":String :: /usr/local/rvm/gems/ruby-1.9.3-p392/gems/logstash-event-1.2.02/lib/logstash/event.rb:107:in `to_s'
/data/apps/current/app/workers/modules/sso/sso.rb:31:in `inspect'
/data/apps/current/app/workers/modules/sso/sso.rb:31:in `inspect'
/data/apps/current/app/workers/modules/sso/sso.rb:31:in `inspect'
/data/apps/current/app/workers/modules/sso/sso.rb:31:in `inspect'
/data/apps/current/app/workers/modules/sso/sso.rb:31:in `inspect'
/data/apps/current/app/workers/modules/sso/sso.rb:31:in `inspect'
/data/apps/current/app/workers/modules/sso/sso.rb:31:in `inspect'
/data/apps/current/app/workers/modules/sso/sso.rb:31:in `verified?'
/data/apps/current/app/controllers/sessions_controller.rb:74:in `create'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/base.rb:167:in `process_action'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rendering.rb:10:in `process_action'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/callbacks.rb:18:in `block in process_action'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:459:in `block in _run__1167298983658507982__process_action__2792552851109248203__callbacks'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:215:in `block in _conditional_callback_around_2750'
/data/apps/current/app/controllers/benchmark_filter.rb:5:in `filter'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:321:in `around'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:310:in `_callback_around_425'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:214:in `_conditional_callback_around_2750'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:447:in `_run__1167298983658507982__process_action__2792552851109248203__callbacks'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:405:in `__run_callback'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:385:in `_run_process_action_callbacks'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:81:in `run_callbacks'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/callbacks.rb:17:in `process_action'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rescue.rb:29:in `process_action'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:30:in `block in process_action'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:123:in `block in instrument'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:123:in `instrument'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:29:in `process_action'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/params_wrapper.rb:207:in `process_action'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activerecord-<IP_ADDRESS>/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/base.rb:121:in `process'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/rendering.rb:45:in `process'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal.rb:203:in `dispatch'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rack_delegation.rb:14:in `dispatch'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal.rb:246:in `block in action'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:73:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:73:in `dispatch'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:36:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/journey-1.0.4/lib/journey/router.rb:68:in `block in call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/journey-1.0.4/lib/journey/router.rb:56:in `each'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/journey-1.0.4/lib/journey/router.rb:56:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:608:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/recurring_select-1.3.1/app/middleware/recurring_select_middleware.rb:24:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/best_standards_support.rb:17:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-1.4.7/lib/rack/etag.rb:23:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-1.4.7/lib/rack/conditionalget.rb:35:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/head.rb:14:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/params_parser.rb:21:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/flash.rb:242:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-1.4.7/lib/rack/session/abstract/id.rb:210:in `context'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-1.4.7/lib/rack/session/abstract/id.rb:205:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/cookies.rb:341:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activerecord-<IP_ADDRESS>/lib/active_record/query_cache.rb:64:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/connection_pool.rb:479:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/callbacks.rb:28:in `block in call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:405:in `_run__316997000888980778__call__1646723128461599002__callbacks'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:405:in `__run_callback'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:385:in `_run_call_callbacks'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:81:in `run_callbacks'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/remote_ip.rb:31:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/debug_exceptions.rb:16:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/show_exceptions.rb:56:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-<IP_ADDRESS>/lib/rails/rack/logger.rb:32:in `call_app'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-<IP_ADDRESS>/lib/rails/rack/logger.rb:16:in `block in call'
/data/apps/current/app/workers/modules/ai_logging.rb:591:in `tagged'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-<IP_ADDRESS>/lib/rails/rack/logger.rb:16:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/request_id.rb:22:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-1.4.7/lib/rack/methodoverride.rb:21:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-1.4.7/lib/rack/runtime.rb:17:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-<IP_ADDRESS>/lib/active_support/cache/strategy/local_cache.rb:72:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-1.4.7/lib/rack/lock.rb:15:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-cache-1.6.1/lib/rack/cache/context.rb:140:in `forward'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-cache-1.6.1/lib/rack/cache/context.rb:147:in `pass'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-cache-1.6.1/lib/rack/cache/context.rb:159:in `invalidate'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-cache-1.6.1/lib/rack/cache/context.rb:74:in `call!'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-cache-1.6.1/lib/rack/cache/context.rb:51:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-cors-1.0.3/lib/rack/cors.rb:95:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-<IP_ADDRESS>/lib/rails/engine.rb:484:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-<IP_ADDRESS>/lib/rails/application.rb:231:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-<IP_ADDRESS>/lib/rails/railtie/configurable.rb:30:in `method_missing'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:580:in `process_client'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:674:in `worker_loop'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:529:in `spawn_missing_workers'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:140:in `start'
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/unicorn-4.9.0/bin/unicorn_rails:209:in `\u003Ctop (required)\u003E'
/usr/local/rvm/gems/ruby-1.9.3-p392/bin/unicorn_rails:23:in `load'
/usr/local/rvm/gems/ruby-1.9.3-p392/bin/unicorn_rails:23:in `\u003Cmain\u003E'
/usr/local/rvm/gems/ruby-1.9.3-p392/bin/ruby_executable_hooks:24:in `eval'
/usr/local/rvm/gems/ruby-1.9.3-p392/bin/ruby_executable_hooks:24:in `\u003Cmain\u003E'

Do you use Ruby1.9.3-p392? Please check your application.

Fluentd clearly does not output the logs. It's my application that is creating these logs that then are not sent to Splunk via fluentd, when fluentd is running in the container.
Yes, my application uses ruby1.9.3-p392 and it's the application that's generating the logs that are not being sent to Splunk via fluentd when in a container.


Test packaging

There are couple of improvements which can be done for test files.

Currently both the source .bal and test.bal should be in the same package. Can we support having a test package separately and write test cases to required bal files
Cannot write tests to the .bal files in the root level. This is because of the same above issue and there is no package name for .bal files in root directory.

It's being discussed to change the test structuring model. Will update the with the progress

This was addressed in the testerina rewrite.


How to set "x-ms-version" in a service client, e.g. a blob client

using it like this
let blob_client = ClientBuilder::new(account, storage_credentials)
        .cloud_location(cloud_location)
        .blob_client(container, blob_name);
    let data = data.as_bytes().to_vec();
    blob_client.put_block_blob(data).await?;

I don't see how to set the api version when using the azure sdk.

I think it's hard coded here:
https://github.com/Azure/azure-sdk-for-rust/blob/aac41053c04585335d2764dc2d341750bc43fb38/sdk/storage/src/clients.rs#L27
...
Is there some way to modify this after the client is created, but before it is used?

It is possible to override the header value using a pipeline Policy:
https://github.com/Azure/azure-sdk-for-rust/issues/1290

Closed.  Thanks for providing the answer @johnbatty


Where() on compount indexes does not work

I have tried several times to query on a compound index without success.
{
  keyPath: ['foo', 'bar']
}

.where(store, ['foo', 'bar'], ...) // Using compound index
.where(store, 'foo, bar', ...)  // Expected name by YDN?
.where(store, 'foo,bar', ...)  // Expected name by YDN?
.where(store, 'foo_bar', ...) // Custom name

With, or without name, lead to no success. Sometimes it appeared that it was working but in fact the where was not filtering anything. I might have done something wrong, but I couldn't debug because the source code was minified and I do not have time to start building the app.
Cheers,
Fred

Forgot to mention that my workaround was to create an index with a generator using both values. And then doing a search on that index. Not sure if that's a good workaround long term, but that appeared to be working.

Your talking don't not make sense and creating rubbish issues annoying.
Proof your claims in jsbin and read before you do.

I am sorry if you're considering that my issues are rubish. I have spent hours yesterday trying to get this to work, I have tried to debug the minified JS, I have read everything I could and googled extensively. I will try to provide a code sample, but any help would be appreciated.

From the above documentation,

compound key can be created either by compound index using array keyPath or key itself

So the name of the index does not matter.

Hmm, thanks Fred. Interesting point, however I have to agree - your talking don't not make sense and creating rubbish issues annoying.


Prevent losing rifle when loading death loadout on respawn

There's a bug with ace and ARMA that a player's primary is not maintained when loading their loadout saved through onPlayerKilled.sqf (if I had to guess it's because the rifle is dropped to the ground a frame before the player is dead?).
This causes the player to respawn without their primary and getting pretty mad about it too like you did it on purpose to them.
A code workaround is possible, such as having a separate variable for the player's primary that is saved every X seconds as a fallback, or checking a small radius around the player's corpse for a primary.

Is it always the primary weapon or the one they're currently holding?

getCorpseWeaponholders should make this a lot easier to implement


fix: support multiple conditions per field (AUTO-176)

Changes
Support multiple conditions in a single field, as in { "Date": {  "$gte": "2020-02-24", "$lt": "2020-02-25" } }.
Testing

Added unit tests
Tested with this PR (see this comment).

Notes
I checked this is not resolved in the parent repo (jsforce/jsforce).

Upstream PR: https://github.com/jsforce/jsforce/pull/992


Short solution needed: "Using switch...case" (lua)

Please help us write most modern and shortest code solution for this issue:
Using switch...case (technology: lua)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments to make solution explained.
Link to this issue in comments of pull request.

Using switch...case


[integrated_dev] Restrict RTL changes for Darjeeling and its HW IP blocks

At the same time remove restrictions on changes for Earlgrey (on the integrated_dev branch).

CHANGE AUTHORIZED: BLOCKFILE

CHANGE AUTHORIZED: BLOCKFILE

Let's announce this in the WG tomorrow and then merge.

RTL blocker announced by email -- merging.


DTrackClient class instances + fix for issue 21

This PR combines #31, #34 and #32 to consistently take advantage of both developments (and further enhance DTrackClient class methods with the optional parent arguments from PR #21/#32) in one clean merge.
Closes: #20

Merged remaining differences after merge of other PRs. Resulting text practically matches what I run locally for the past couple of months.

thanks a lot.


proposal: add a new "http" metadata protocol

Glad to see https://github.com/kvcache-ai/Mooncake/pull/21 start to support multiple metadata servers.
Now, only etcd and redis are supported. I'm here to proposal a new "http" metadata type, benifits:

http metadata server are easy to deploy and scale.
the http metadata server could expose more APIs for system operator know/manage the system better.

Design:
The http server provide three restful APIs:

GET $metadata_uri?key=$key
PUT $$metadata_uri?key=$key, with json body
DELETE $metadata_uri?key=$key

If this does make sense, I'd like to have a try, thanks.

Good idea! I think inheriting TransferMetadataImpl in mooncake-transfer-engine/src/transfer_metadata.cpp is enough :)


Does RunCommand work on Mac OS Big Sur?

Setup info

Workflow name: RunCommand
Workflow version: v20.2
Alfred version: 4.3.2
macOS version: macOS 11.2.1

Description of issue
It doesn't seem to work on my machine running macOS Big Sur. It does work on another machine running macOS Catalina (10.15.7).
I extracted the runcommand script and it works on both machines.
Debugger output
[12:10:49.916] RunCommand[Keyword] Processing complete
[12:10:49.917] RunCommand[Keyword] Passing output 'qrscan' to Run Script
[12:10:49.920] ERROR: RunCommand[Run Script] /bin/bash: ./runcommand: Permission denied
[12:10:49.921] RunCommand[Run Script] Processing complete
[12:10:49.921] RunCommand[Run Script] Passing output '' to Large Type

Hitting simply ENTER (without pressing CMD) results in
[12:30:12.006] RunCommand[Keyword] Processing complete
[12:30:12.007] RunCommand[Keyword] Passing output 'qrscan' to Run Script
[12:30:12.076] ERROR: RunCommand[Run Script] /bin/bash: ./runcommand: Permission denied
/bin/bash: line 13: ./Notificator.app/Contents/Resources/Scripts/notificator: Permission denied
[12:30:12.081] RunCommand[Run Script] Processing complete
[12:30:12.081] RunCommand[Run Script] Passing output '' to Run Script

I honestly don't know, why permissions are denied. The workflows (and other Alfred settings) are synced via nextcloud (Alfred.alfredpreferences) so both machines use the same workflow files.
Maybe i missed to enable some macOS security related stuff. I reinstalled Alfred without any luck.

Yes, it runs on Big Sur. If you go into the Workflow’s directory and ls -a, what do you get?

Jap. You're right. Just checked the workflow files and needed to chmod +x runcommand. Everything works now. Thanks for pointing me in the right direction 👍

Great workflow btw. :)


训练开启Flash Attention运行报错

Reminder

[X] I have read the README and searched the existing issues.

Reproduction
使用chinese-alpaca-2-7b模型在两块H800进行SFT训练，开启Flash Attention加速，训练报错，请帮忙看一下，谢谢。
信息如下：
[INFO|trainer.py:1812] 2024-03-14 12:07:36,974 >> ***** Running training ***** [INFO|trainer.py:1813] 2024-03-14 12:07:36,974 >>   Num examples = 48,818 [INFO|trainer.py:1814] 2024-03-14 12:07:36,974 >>   Num Epochs = 1 [INFO|trainer.py:1815] 2024-03-14 12:07:36,974 >>   Instantaneous batch size per device = 4 [INFO|trainer.py:1818] 2024-03-14 12:07:36,974 >>   Total train batch size (w. parallel, distributed & accumulation) = 32 [INFO|trainer.py:1819] 2024-03-14 12:07:36,974 >>   Gradient Accumulation steps = 4 [INFO|trainer.py:1820] 2024-03-14 12:07:36,974 >>   Total optimization steps = 5 [INFO|trainer.py:1821] 2024-03-14 12:07:36,975 >>   Number of trainable parameters = 6,929,256,448   0%|                                                                                | 0/5 [00:00<?, ?it/s]Traceback (most recent call last):   File "/root/llm/train.py", line 91, in <module>     main()   File "/root/llm/train.py", line 50, in main     run_exp()   File "/root/llm/src/llmtuner/train/tuner.py", line 32, in run_exp     run_sft(model_args, data_args, training_args, finetuning_args, generating_args, callbacks)   File "/root/llm/src/llmtuner/train/sft/workflow.py", line 73, in run_sft     train_result = trainer.train(resume_from_checkpoint=training_args.resume_from_checkpoint)   File "/usr/local/lib/python3.10/dist-packages/transformers/trainer.py", line 1624, in train     return inner_training_loop(   File "/usr/local/lib/python3.10/dist-packages/transformers/trainer.py", line 1961, in _inner_training_loop     tr_loss_step = self.training_step(model, inputs)   File "/usr/local/lib/python3.10/dist-packages/transformers/trainer.py", line 2902, in training_step     loss = self.compute_loss(model, inputs)   File "/usr/local/lib/python3.10/dist-packages/transformers/trainer.py", line 2925, in compute_loss     outputs = model(**inputs)   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl     return self._call_impl(*args, **kwargs)   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1527, in _call_impl     return forward_call(*args, **kwargs)   File "/usr/local/lib/python3.10/dist-packages/deepspeed/utils/nvtx.py", line 15, in wrapped_fn     ret_val = func(*args, **kwargs)   File "/usr/local/lib/python3.10/dist-packages/deepspeed/runtime/engine.py", line 1852, in forward     loss = self.module(*inputs, **kwargs)   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl     return self._call_impl(*args, **kwargs)   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1527, in _call_impl     return forward_call(*args, **kwargs)   File "/usr/local/lib/python3.10/dist-packages/transformers/models/llama/modeling_llama.py", line 1176, in forward     outputs = self.model(   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl     return self._call_impl(*args, **kwargs)   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1527, in _call_impl     return forward_call(*args, **kwargs)   File "/usr/local/lib/python3.10/dist-packages/transformers/models/llama/modeling_llama.py", line 1008, in forward     layer_outputs = self._gradient_checkpointing_func(   File "/usr/local/lib/python3.10/dist-packages/torch/_compile.py", line 24, in inner     return torch._dynamo.disable(fn, recursive)(*args, **kwargs)   File "/usr/local/lib/python3.10/dist-packages/torch/_dynamo/eval_frame.py", line 328, in _fn     return fn(*args, **kwargs)   File "/usr/local/lib/python3.10/dist-packages/torch/_dynamo/external_utils.py", line 17, in inner     return fn(*args, **kwargs)   File "/usr/local/lib/python3.10/dist-packages/torch/utils/checkpoint.py", line 451, in checkpoint     return CheckpointFunction.apply(function, preserve, *args)   File "/usr/local/lib/python3.10/dist-packages/torch/autograd/function.py", line 539, in apply     return super().apply(*args, **kwargs)  # type: ignore[misc]   File "/usr/local/lib/python3.10/dist-packages/torch/utils/checkpoint.py", line 230, in forward     outputs = run_function(*args)   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl     return self._call_impl(*args, **kwargs)   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1527, in _call_impl     return forward_call(*args, **kwargs)   File "/usr/local/lib/python3.10/dist-packages/transformers/models/llama/modeling_llama.py", line 740, in forward     hidden_states, self_attn_weights, present_key_value = self.self_attn(   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl     return self._call_impl(*args, **kwargs)   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1527, in _call_impl     return forward_call(*args, **kwargs)   File "/root/llm/src/llmtuner/extras/patches/llama_patch.py", line 127, in llama_flash_attn_forward     cos, sin = self.rotary_emb(value_states, seq_len=kv_seq_len)   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl     return self._call_impl(*args, **kwargs)   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1527, in _call_impl     return forward_call(*args, **kwargs)   File "/usr/local/lib/python3.10/dist-packages/torch/utils/_contextlib.py", line 115, in decorate_context     return func(*args, **kwargs) TypeError: LlamaRotaryEmbedding.forward() missing 1 required positional argument: 'position_ids'   0%|                                                                                | 0/5 [00:00<?, ?it/s] [2024-03-14 12:07:39,691] [INFO] [launch.py:316:sigkill_handler] Killing subprocess 16822 [2024-03-14 12:07:42,010] [INFO] [launch.py:316:sigkill_handler] Killing subprocess 16823
Expected behavior
No response
System Info
python 3.10
transformers 4.38.2
torch 2.1.2
Others
No response

未复现问题，请升级到最新版本，并给出训练脚本看一下。
另外看错误描述，感觉模型文件本身或者版本就不太对，也请做一些检查，一般不会出现如下这种错误。
TypeError: LlamaRotaryEmbedding.forward() missing 1 required positional argument: 'position_ids'

又测试了两遍7b 13b没有再复现，先关闭问题。


Add incident sli

Adds incident threshold as an SLI codebundle
adds new Papi keywords for metrics and tasksets
fixes edge case bug in rest keyword

Should we be support less than or equal to, and greater than or equal to?


add support for gecko driver, add headless for chrome

@estuold what should I do to run tests in a headless chrome?


Option to turn off faster re-recording behavior

There is this feature:

About recording sessions
Faster re-recording explained
Whispering keeps the media stream open after you start recording, enabling quick re-recording with reduced latency.
This means your computer will show this tab is still using the microphone.
When finished, click the 🔴 button to close the stream and end microphone access.

I appreciate the motivation behind this, and this might be very useful for lots of people, I however have not noticed a large latency to begin with, and having a recording tab in the background has given me pause a few times when I noticed it later. So I'd like an option to turn this off.
Some alternative ideas in case the above sounds sub optimal for some reason:

Quick timeout for the recording tab, maybe settable in seconds, after a recording ends.
Option to work similarly as Whisler for ChatGPT, i.e. do the recording on the same tab as the icon was clicked. This has some trade-offs too.

Love this feature idea and also was independently was thinking of incorporating it in the next release! Knowing that community members will make it a higher priority. Thank you for letting me know and hope to merge soon!

@braden-w Glad to hear! Out of curiosity, you are referring to the main idea, i.e. option to turn off re-recording, right? Or one of the alternative ideas?

I to add something as brainstorming idea: Another option would be to having a pleasant sound after a time. For example avery 20
seconds. That I'm capable to make longer dictations and also if I started accidentally, I get a reminder to turn it off. Instead to decide to limit my dictation time,  Up front..


Lightweight images

Experimental image build update to reduce weight of base images.
Result from running make build/php-8.0-fpm on this branch:
$ docker image ls lagoon/php-8.0-fpm
REPOSITORY           TAG       IMAGE ID       CREATED              SIZE
lagoon/php-8.0-fpm   latest    fbdce423c96c   About a minute ago   268MB

Versus current released image:
$ docker image ls uselagoon/php-8.0-fpm
REPOSITORY              TAG       IMAGE ID       CREATED       SIZE
uselagoon/php-8.0-fpm   latest    7f83e8db81b4   4 weeks ago   625MB

oooh - I like this - I separated the three stages whilst we were in dev - but putting them together has the obvious benefits.
I'll do a bit more testing (and probably extend this logic to PHP7.4 too), but it looks good!

Nice!
Looks like a 60% reduction in size!
$ docker image ls | grep fpm
...
uselagoon/php-7.4-fpm                      22.2.0                     a4f82306c90b   4 weeks ago     622MB
testlagoon/php-7.4-fpm                     pr-426                     1efbe7cd333f   2 hours ago     266MB
...
uselagoon/php-8.0-fpm                      22.2.0                     7f83e8db81b4   4 weeks ago     625MB
testlagoon/php-8.0-fpm                     pr-426                     d767d2189428   2 hours ago     269MB
...
uselagoon/php-8.1-fpm                      22.2.0                     912c93d86c02   4 weeks ago     596MB
testlagoon/php-8.1-fpm                     pr-426                     a73872088560   2 hours ago     237MB


[Question]  /META-INF/script/custom_rate_limiter.lua can’t find error

Question
I did RateLimiterAlgorithm interface class implement also lua script. But I added under /META-INF/script, I got an error that ‘custom_rate_limiter.lua’ file not open because not exists…
Do you happen to know how can I fix it? I think that can use custom lua script for new implement RateLimiterAlgorithm class!!
Please some tips….

getScriptName  return  custom_rate_limiter
public interface RateLimiterAlgorithm {
/**
 * Gets script name.
 *
 * @return the script name
 */
String getScriptName();

I got that error like that [org.apache.shenyu.plugin.ratelimiter.handler.ShenyuReactiveScriptExecutor - Redis execute exception: Error reading script text; nested exception is java.io.FileNotFoundException: class path resource [META-INF/scripts/costum_rate_limiter.lua] cannot be opened because it does not exist]
Because of initialize through constructor, script name value was set..
Can you check my code and lua script file location?
`
@Join
public class CustomRateLimiterAlgorithm extends AbstractRateLimiterAlgorithm {
private static final String KEY_NAME = "custom_rate_limiter";
private static final String SCRIPT_NAME = KEY_NAME + ".lua";

public GameServerGWRateLimiterAlgorithm() {
	super(SCRIPT_NAME);
}

@Override
protected String getKeyName() {
	return KEY_NAME;
}

}
`

resources
-- META-INF
--- script
---- custom_rate_limiter.lua

@yu199195
I solved this issue through setting on sub-class constructor like that
`
public GameServerGWRateLimiterAlgorithm() throws IOException {
super(SCRIPT_NAME); // not working...
	// need to setting that was set on super class
	DefaultRedisScript redisScript = new DefaultRedisScript();
	redisScript.setScriptSource(new ResourceScriptSource(new ClassPathResource("/META-INF/script/" + SCRIPT_NAME)));
	redisScript.setResultType(List.class);
	this.script = redisScript;

}
`


reconcile eris-db rpc port with tendermint rpc port

this is blocking until we move to tmsp (post 0.12.0). until we formally move to tmsp this work isn't very important. after that switch, we will need to control "more" from the erisdb-rpc port. Indeed, erisdb-rpc port should be the single gateway to eris chains and then be able to proxy to tmint's rpc if needed (or the application manager, etc.)

what is currently in erisdb is likely to become the base for our messenger component of eris chains ...

right. so this is a big one. we need to strategize a bit about what httpserver/rpc framework we want to use here. I like tendermint/go-rpc because it exposes the same endpoints as GET requests (so we can see in browser), as jsonrpc POST, and as websocket messages. of course the js libs use the erisdb "rest" api but I believe there have been some issues there and dave has even started using the 46657 api.  granted there's no rush on this but maybe we should put @NodeGuy in charge of this interface since he's responsible for the js tools which will be talking to it, and we can make the mint-client tools conform to whatever he thinks is best for the API here.

It's bigger than the js tooling. We will discuss this at the chains team summit next week.

overly broad. closing