Delete blueprint.xml

An alternative to #187 - see discussion there

@jrudolph is this PR ok as an alternative to #187 ?


Live Deployment

Hi, this looks like a pretty interesting project. I am the head of developer relations at the nervos network blockchain. I was wondering if you have any live deployment of openstore, perhaps running on a testnet I could see? Thank you! ~

Hi. Thank you for your interest in the project. We have currently deployed the project in Polygon Mumbai testnet. However doing this not only slowed down the creation process cascading to slow transactions and resulting in an error in creation (mainly due to network error)
The faucet providing test tokens also returns an error signifying the replacement transaction to be underpriced. Due to this, we were not able to get the tokens necessary to conduct transactions for creation as well as for purchase (We were able to get some tokens for deployment).
Once again, thanks for your interest and will get back to you once we get these sorted out

We had created a demo video for the same
https://www.youtube.com/watch?v=sHytyvUQB0Q


Update supported versions

We should still keep supporting non-LTS versions for 5 weeks

Duplicated with #216


kconfig: default to LEGACY_INCLUDE_PATH=n

Migrate the remaining code to the "zephyr/" prefixed #include and flip the default.
Dependencies:

[x] https://github.com/zephyrproject-rtos/mcuboot/pull/82

[x] https://github.com/mcu-tools/mcuboot/pull/1421
[x] https://github.com/zephyrproject-rtos/mcuboot/pull/83

[x] https://github.com/zephyrproject-rtos/chre/pull/3

[x] https://android-review.googlesource.com/c/2160657
[x] https://github.com/zephyrproject-rtos/chre/pull/4

[x] https://github.com/zephyrproject-rtos/sof/pull/17
[x] https://github.com/zephyrproject-rtos/segger/pull/12
[x] https://github.com/zephyrproject-rtos/hal_silabs/pull/18
[x] https://github.com/zephyrproject-rtos/hal_nordic/pull/119

@fabiobaltieri please rebase and update shas

Cool, let's see what else broke since the last run...

Had to pull back the segger module by one patch, HEAD there needs one more patch (#48513). Fixed few more includes and squashed them in the two initial commits.

Here goes nothing... will need a rebase if https://github.com/zephyrproject-rtos/zephyr/pull/48513 goes in first.

Dropped "default n" from the config option definition (it's the default).

@fabiobaltieri #48513 went in first. this now needs a rebase.

@fabiobaltieri #48513 went in first. this now needs a rebase.

Cool, rebased, does not touch the segger module anymore since that's already done!

Thanks folks! Let's do this! :-)


Data Augmentation on graphs

❓ Questions & Help
Hey,
at the moment I'm thinking about applying data augmentation to graph data .I have two scenarios in my mind and I want to ask you whether they are easily implementable (or better there is already an existing one) and reasonable. The main idea is to rearrange the indices of each node but keep the edges and features and train the model with different arrangements in each iteration (equal to the data augmentation example for images in Pytorch). The concrete implementations of my idea would be:

Via a tranformation operation which randomly rearranges the indices of each graph (including the rearrangement of the node and edge features)
Via a dataset which is filled with rearrangements of each graph in advance and the dataloader selects one random arrangement of each graph per epoch. This can be either implemented by an additional identifier in the Data-object which is equal for all arrangements of one graph or by drawing the samples randomly out of multiple bins (each bin only has one arrangement of a graph) each iteration.

I hope that I proposed my idea in an understandable way.^^
Best regards!

I think you can use transforms for this use-case:
class Rearange(object):
    def __call__(self, data):
        perm = torch.randperm(data.num_nodes)
        data.x = data.x[perm]
        data.edge_index = perm[data.edge_index]

What about the edge attributes?

No need to change them since the order of esges stays the same.


fix(tauri): export WindowBuilder struct instead of trait, closes #3827

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Docs
[ ] New Binding issue #___
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change?

[ ] Yes, and the changes were approved in issue #___
[ ] No

Checklist

[x] When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
[x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
[ ] I have added a convincing reason for adding this feature, if necessary

Other information
The trait won't be needed on the next release, we will drop the create_new_window APIs.

Tests will be fixed on #3834


[TODO] Implement allow-skips

This has been suggested by @pradyunsg.
Use-case: workflows that run jobs conditionally, depending on the files changed in associated PRs, for example — https://github.com/pypa/pip/blob/bbc7021/.github/workflows/ci.yml#L29-L49, using a change detection action like dorny/paths-filter.

@pradyunsg mind checking out the change?
https://github.com/re-actors/alls-green/commit/3a2de129f0713010a71314c74e33c0e3ef90e696
https://github.com/webknjaz/check-gha-test/runs/4515033319?check_suite_focus=true#step:3:59
It is currently testable via the unstable branch:
- uses: re-actors/alls-green@unstable/v1
  id: check
  with:
    allowed-failures: failing-job0
    allowed-skips: failing-job1, skipped-job
    jobs: ${{ toJSON(needs) }}

Due to my impatience, I've published this under a stable release v1.1.0.

The behaviour looks good to me!

Perfect! @pradyunsg should I make a PR in pip?

Yes!


Add video links in zerops guide

Description (required)

Added video links of one click deploy for both ssr and ssg

Related issues & labels (optional)

Closes #
Suggested label:

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

en
guides/deploy/zerops.mdx
Source changed, localizations will be marked as outdated.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


GEODE-4728: api docs - fix SystemProperties docs

Simple corrections identified [paired with @mmartell] back in May that weren't included in the May check-in.

Changes look great!


vNEXT Proposal: Add profile to System constructors

Overview
Since each profile is required by most systems (The exception being the teleport system, but they may change in the future). Systems should setup their initial values using the profiles provided in the constructor.
This better implements the Dependency injection patterns we've been utilizing and adding robustness to the systems. All initial variable values will be set in the constructor.
Requirements

BaseSystem class with the profile constructor parameter.
Update to the MixedRealityToolkit to register a system with the profile constructor arg.
Updates to all the systems to set up their initial conditions based off of the provided profile.

Acceptance Criteria

[x] I can register a system with its profile
[ ] All systems have been updated to initialize their initial values using the provided profile.

complete


when error occurs,it do not report error span

https://github.com/opentracing-contrib/java-redis-client/blob/784e55d5f7a422af77bba326464ba2fdac24aced/opentracing-redis-spring/src/main/java/io/opentracing/contrib/redis/spring/connection/RedisTracingUtils.java#L40-L46

thanks for fixed this problem.But,today i found jdbc instrument has the same problem.I suppose that it is o good idea to check other instrument  like hytrix and so on


Decreasing swagger file in multimodule project FIXED tests #539

@who can you take a look at the proposed fix ?

@kongchen can you please take a look ?


[Feature]: Unable to edit or delete plans in subscriptions

🚀 Feature Proposal
To create any subscription, a base plan is required. However, there is no way to edit or delete these plans.
Suggested Solution
Add edit & delete Plans API
Alternatives
No response
Additional Information
https://razorpay.com/docs/api/payments/subscriptions/#plans

@harshmsomani You can create a new plan and update that plan-id in your subscription. Also, If the plan is edited, it will result in some serious problems for the customers.

I am closing this issue as the issue has been resolved. If you need any help, please let us know.


Interactive window has odd behavior on internal exception

In the pop-out console, when running a command that causes an internal exception to be generated, the "internal error" NetLogo window comes up.  After dismissing it, the console window also disappears.  Clicking the menu item to re-add it does nothing the first time, but the second time it's clicked it does come back and works as normal.  I think it would be more desirable for the window to not vanish on an error, but if it has to, it should come back just by clicking the menu item once.
I discovered this running the py:runresult "os.environ['HOME']" command, an example from the Python Basic Example models library model.  I have no idea why it's giving an exception on my system, seems like a security/permissions issue somehow.

Hmmm, I was not able to reproduce this.
Steps attempted:

open the python demo file, ran setup (which does py:setup py:python and imports some libs)
open the interactive console, ran import os; ran os.environ['HOME']
I got no error

I also tried to get a similar internal error to hopefully reproduce the behavior if not the cause

open the interactive console, ran f = open("/<path to a file that my user doesn't have permissions to open").
I got the netlogo internal error pop up but when I dismissed it, the interactive console window stayed open.

Now that said, I think that having errors in the interactive console show up as  netlogo internal errors is a pretty bad user experience. It could make people think they did something horrible to break netlogo when really they just mistyped something or something like that. We should try our best to imitate the experience of using a standard python REPL.

The root cause of the issue and the difference in behavior I got might be platform dependent as I was using Windows 11 to test with (and NetLogo 6.2.2 for what it's worth).  I do agree the "scary" error pop-up is likely not what we want in most cases.

Used the latest Python extension version to re-test this and confirmed it is resolved for me with the changes.  Thanks for the fix!


CommonMark 0.6.0 breaks compatibility

Hi, it seems CommonMark (which was uploaded yesterday to pypi) breaks compatibility with this package. The error:
>>> from recommonmark.parser import CommonMarkParser
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/manuelmiranda/.virtualenvs/docs/lib/python2.7/site-packages/recommonmark/parser.py", line 9, in <module>
    from CommonMark import DocParser, HTMLRenderer
ImportError: cannot import name DocParser

Forcing the installation of 0.5.4 works again. Tested with both 0.2.0 and 0.1.1 versions.

  File "conf.py", line 308, in <module>
    from recommonmark.parser import CommonMarkParser
  File "/www/readthedocs.org/user_builds/tbiodocs/envs/latest/lib/python2.7/site-packages/recommonmark/parser.py", line 5, in <module>
    from CommonMark import DocParser, HTMLRenderer
ImportError: cannot import name DocParser

I tried forcing 0.5.4 by changing the requirements/pip.txt for rtfd/readthedocs.org to include CommonMark==0.5.4, uninstalling 0.6.0 using pip, and installing 0.5.4 directly, but I still get this issue. Do you have a workaround?

Mmm? Have you tried that manually using the python terminal? By forcing the installation of the 0.5.4 package worked for me both in my local environment and in a RTD page (I had to write a requirements.txt file and tell my project to install the packages from that file).
Have you checked the build process? Maybe it is forcing the installation of 0.5.4 before it installs recommonmark which may be again installing a higher version.

I did try manually, but, I ended up just using a symlink so it would stop overwriting with 0.6.0, which was successful.

Is there a way to override this during the build process?  A single update would be a quick fix for now, until there's a proper resolution.

Updating tasks.py to include 'CommonMark==0.5.4' has worked for me.

Pardon my ignorance, but it does not seem to work for me. I updated tasks.py earlier and lately updated it to use capital letters in case that mattered, but it persists in believing that >=0.5.4 is good and as 0.6.1 came out and made my 0.6.0 symlink meaningless, I have resumed having issues.
    # Install requirements
    requirements = [
        'sphinx==1.3.1',
        'Pygments==2.0.2',
        'virtualenv==13.1.0',
        'setuptools==18.0.1',
        'docutils==0.11',
        'mkdocs==0.14.0',
        'mock==1.0.1',
        'pillow==2.6.1',
        'readthedocs-sphinx-ext==0.5.4',
        'sphinx-rtd-theme==0.1.9',
        'alabaster>=0.7,<0.8,!=0.7.5',
        'recommonmark==0.1.1',
        'CommonMark==0.5.4'
    ]

Do I need to place it earlier in the list or something?

@tomck Is there a reason that you have recommonmark pinned to 0.1.1?
I am getting clean imports with the changes that were pushed today by @ericholscher (Thanks Eric!).
recommonmark==0.4.0
CommonMark==0.5.4

cc/@lu-zero FYI. Will test a bit more tommorrow.

No, ReadTheDocs has it pinned to 0.1.1 and I'm not having much luck with
altering what versions it likes.
On Tuesday, January 5, 2016, Carol Willing<EMAIL_ADDRESS>wrote:

@tomck https://github.com/tomck Is there a reason that you have
recommonmark pinned to 0.1.1?
I am getting clean imports with the changes that were pushed today by
@ericholscher https://github.com/ericholscher (Thanks Eric!).
recommonmark==0.4.0
CommonMark==0.5.4
cc/@lu-zero https://github.com/lu-zero FYI. Will test a bit more
tommorrow.
—
Reply to this email directly or view it on GitHub
https://github.com/rtfd/recommonmark/issues/24#issuecomment-169172629.

@tomck Are you using the rtfd/ReadTheDocs.org repo for your build?
This is the requirements.txt file that ultimately is loaded for it
https://github.com/rtfd/readthedocs.org/blob/master/requirements/pip.txt
If you share a bit more about how you are set up, I may be able to help you workaround.

I am using a docker install actually, for reasons. The initial reason was, the docker install Just Works (tm).  https://hub.docker.com/r/vassilvk/readthedocs/

@tomck I would try editing this Dockerfile for your deployment if you are able. https://hub.docker.com/r/vassilvk/readthedocs/~/dockerfile/
You could insert lines in the Dockerfile:
# Install the required Python packages
RUN pip install -r requirements.txt

# Install a higher version of requests to fix an SSL issue
RUN pip install requests==2.6.0

# Install a different version of recommonmark
RUN pip install recommonmark==0.4.0

@tomck I also am using docker, although building rtd through the dockerfile.  I added CommonMark above recommonmark in the list.  I added it to tasks.py in a running container to test.  My dockerfile copies the custom task.py during build, to ensure I always have the same settings.
Dockerfile
COPY docker/fixes/tasks.py $RTD_DIR/readthedocs/projects/tasks.py
tasks.py
# Install requirements
requirements = [
'sphinx==1.3.1',
'Pygments==2.0.2',
'virtualenv==13.1.0',
'setuptools==18.0.1',
'docutils==0.11',
'mkdocs==0.14.0',
'mock==1.0.1',
'pillow==2.9.0',
'readthedocs-sphinx-ext==0.5.4',
'sphinx-rtd-theme==0.1.9',
'alabaster>=0.7,<0.8,!=0.7.5',
'CommonMark==0.5.4',
'recommonmark==0.1.1',
]

@willingc I did exactly this, rebuilt and re-deployed, and it is still trying to use 0.1.1.
python /www/readthedocs.org/user_builds/read-the-docs/envs/stable/bin/pip install --use-wheel -U --cache-dir /www/readthedocs.org/user_builds/read-the-docs/.cache/pip sphinx==1.3.1 Pygments==2.0.2 virtualenv==13.1.0 setuptools==18.0.1 docutils==0.11 mkdocs==0.14.0 mock==1.0.1 pillow==2.6.1 readthedocs-sphinx-ext==0.5.4 sphinx-rtd-theme==0.1.9 alabaster>=0.7,<0.8,!=0.7.5 recommonmark==0.1.1
...
Requirement already up-to-date: commonmark>=0.5.4 in ./user_builds/read-the-docs/envs/stable/lib/python2.7/site-packages (from recommonmark==0.1.1)

@tomck Bah to the first part. It looks like the installation of recommonmark 0.1.1 does not pin its dependency to commonmark==0.5.4 but instead any release greater than 0.5.4 which would explain why 0.6.1 is being installed.
Glad the second part is working for you. :smiley:

I've got RTD deployed to a server and have changed the files requirements/pip.txt and readthedocs/projects/tasks.py to 'recommonmark==0.4.0', and removed the file readthedocs/projects/tasks.pyc but I when building it seems to ignore this and still fails.  Any thoughts?

@alasdairdc Awesome :sunny:

On my computer, I've found that using CommonMark-py v0.5.5 (that last release before v0.6.0) works as well.
In regards to the 0.6.0 changes, it seems that it has brought a significant reworking of the AST (see this comment for some details). I don't understand enough of what is going on to fix it myself, but hopefully someone else will find this helpful.


Unable to add CLA Managers via CLA Corporate Console

Summary
Adding a CLA Manager is failing in the CLA Corporate Console
Background
Previous report on https://github.com/communitybridge/easycla/issues/4373 the CLA Managers and other issues with users service was reported. While the issue was resolved, we found our that adding a CLA Manager is failing:
{
    "data": {
        "addNewClaManager": {
            "code": 400,
            "message": "User <redacted for PII> has no LF Login account. User can be added as CLA Manager after LF Login is created",
            "success": false,
            "newManager": null,
            "__typename": "AddClaManagerResult"
        }
    }
}

Payload:
{"operationName":"addNewClaManager","variables":{"input":{"projectId":"a0941000002wBz4AAE","companyId":"644b311e-a7d9-4060-b6df-a264a2479332","firstName":"<REDACTED>","lastName":"<REDACTED>","userEmail":"<REDACRED>"}},"query":"mutation addNewClaManager($input: AddClaManagerInput!) {\n  addNewClaManager(input: $input) {\n    code\n    message\n    success\n    newManager {\n      existingUser\n      approvedOn\n      lfUsername\n      name\n      email\n      claGroupName\n      organizationName\n      organizationSfid\n      projectId\n      projectName\n      projectSfid\n      userSfid\n      __typename\n    }\n    __typename\n  }\n}\n"}

Frontend: https://linuxfoundation.atlassian.net/browse/CD-2587
Expected behavior
CLA Manager should be added
Environment
Please complete the following information:

Environment:

[ ] ALL
[ ] DEV
[ ] STAGING
[x] PROD

Browser:

[x] Chrome/Brave

Tested on the dev site and found that it is working fine
Refer screenshot for more details

Tested on production and found that it is working fine, So updating this issue status

This is in PROD now. Closing.


Add Doc on how to use External Secrets.

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screenshot.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65e9e6d1d0e09f29901879ad--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65e9f6f48cb0963fce79e3e4--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65ea06440d726d4bc856ee0d--harness-developer.netlify.app


Support multiple files converter in ThorVG Viewer

What if user wants convert many svg files at once? ThorVG could allow loading multiple svg files from the file dialog box and export them altogether?

@mmaciola have any idea?

I think that using wasm Thorvg Viewer to convert multiple files is not the best idea. It is a viewer - great for previewing, validation and basic editing, but it is not a converter software.
For a few files (2-3 files), user can convert them one by one using Thorvg Viewer, but for multiple, the native software should definitely be used. Web applications has limitations there (memory usage, problem downloading multiple files from browser, need for zipping).
Now we have two tools: svg2tvg and svg2png. Maybe we should create some more general converter that would cover [tvg/svg/...]2[png/tvg] (tvg2tvg can update standard version and change compression).
What do you think about such approach and a tool?

Thorvg Viewer now supports multiple files upload and switching between files. Working on bulk export and other functions

@mmaciola great thanks!


[ENHANCEMENT] Harvester CI retry on failure when deleting VM

Is your enhancement related to a problem? Please describe.

Observed in PR https://github.com/harvester/harvester/pull/4626.
CI fails randomly due to below error.
File: https://github.com/harvester/harvester/blob/6da66dc6f7bdebf43bd4932eb5128642ec397e51/tests/integration/api/vm_apis_test.go#L245
The test case deleting a vm and its volume may fail due to VMI is updated silently and such error
failed to delete action, response with 500, {"type":"error","links":{},"code":"ServerError","message":"Failed to set removedPersistentVolumeClaims to virtualMachine default/test-7h4z9, Operation cannot be fulfilled on virtualmachines.kubevirt.io \"test-7h4z9\": the object has been modified; please apply your changes to the latest version and try again","status":500,"type":"error"}
Describe the solution you'd like

CI add retry on such case.
Describe alternatives you've considered

Retry in backend code:
https://github.com/harvester/harvester/blob/6da66dc6f7bdebf43bd4932eb5128642ec397e51/pkg/api/vm/store.go#L48
Additional context

When deleting a VM with it's disk, there is also such log in harvester POD:

time="2023-10-24T09:58:53Z" level=error msg="error syncing 'default/vm1': handler VMController.ManageOwnerOfPVCs: Operation cannot be fulfilled on virtualmachines.kubevirt.io "vm1": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachines/default/vm1, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 0528d3c1-dd91-42b4-8126-a57c2164e2b8, UID in object meta: , requeuing"

Request URL:

https://<IP_ADDRESS>/v1/harvester/kubevirt.io.virtualmachines/default/vm1?removedDisks=disk-0&propagationPolicy=Foreground

auto-generated VM actions
    "id": "default/vm1",
    "type": "kubevirt.io.virtualmachine",
    "links": {
        "remove": "https://<IP_ADDRESS>/v1/harvester/kubevirt.io.virtualmachines/default/vm1",
        "self": "https://<IP_ADDRESS>/v1/harvester/kubevirt.io.virtualmachines/default/vm1",
        "update": "https://<IP_ADDRESS>/v1/harvester/kubevirt.io.virtualmachines/default/vm1",
        "view": "https://<IP_ADDRESS>/apis/kubevirt.io/v1/namespaces/default/virtualmachines/vm1"
    },
    "actions": {
        "addVolume": "https://<IP_ADDRESS>/v1/harvester/kubevirt.io.virtualmachines/default/vm1?action=addVolume",
        "clone": "https://<IP_ADDRESS>/v1/harvester/kubevirt.io.virtualmachines/default/vm1?action=clone",
        "createTemplate": "https://<IP_ADDRESS>/v1/harvester/kubevirt.io.virtualmachines/default/vm1?action=createTemplate",
        "findMigratableNodes": "https://<IP_ADDRESS>/v1/harvester/kubevirt.io.virtualmachines/default/vm1?action=findMigratableNodes",
        "migrate": "https://<IP_ADDRESS>/v1/harvester/kubevirt.io.virtualmachines/default/vm1?action=migrate",
        "pause": "https://<IP_ADDRESS>/v1/harvester/kubevirt.io.virtualmachines/default/vm1?action=pause",
        "removeVolume": "https://<IP_ADDRESS>/v1/harvester/kubevirt.io.virtualmachines/default/vm1?action=removeVolume",
        "restart": "https://<IP_ADDRESS>/v1/harvester/kubevirt.io.virtualmachines/default/vm1?action=restart",
        "softreboot": "https://<IP_ADDRESS>/v1/harvester/kubevirt.io.virtualmachines/default/vm1?action=softreboot",
        "stop": "https://<IP_ADDRESS>/v1/harvester/kubevirt.io.virtualmachines/default/vm1?action=stop"
    },
    "apiVersion": "kubevirt.io/v1",
    "kind": "VirtualMachine",

New PR https://github.com/harvester/harvester/pull/6445 will solve this issue as well.
Anohter related issue: https://github.com/harvester/harvester/issues/5968

Accomplished as PR https://github.com/harvester/harvester/pull/6445 is merged.


in_tail: unexpected rotation detection behaviour

Describe the bug
Fluentd cannot detect rotated log file unless I pass the parameter "open_on_every_update=true" in the config files.
To Reproduce
Set the parameter "open_on_every_update" as false:
When a new log file are created by logger (log rotation), fluentd didn't recognize them and only logs from the first app.log are shown on docker logs.
Set the parameter "open_on_every_update" as true:
Rotation detection works as expected.
Expected behavior
As described in docs: "Open and close the file on every update instead of leaving it open until it gets rotated."
As a sanity check, I also check tail -F on app.log in both situations. Both cases give "normal" result.
Your Environment

Fluentd or td-agent version: Fluentd offical docker image
Operating system: macOS Catalina Version 10.15.4
Logging library: Python 3.6.9 built-in logging library, with TimedRotatingFileHandler

Your Configuration
fluentd.conf
# /tmp/fluentd.conf
<source>
  @type tail
  path /logs/*/app.log
  pos_file /var/log/td-agent/tmp/optimizer.log.pos
  tag XXX.*
  refresh_interval 5
  read_from_head true
  open_on_every_update true
  <parse>
    @type json
  </parse>
</source>
<match **>
  @type stdout
</match>

Your Error Log
open_on_every_update = false
(end of docker logs)

open_on_every_update = true
(fluentd handled the log rotation situation rapidly.)

Additional context
I am not sure if this issue is related to #2200

@repeatedly  Sorry for not following the issue format. I have made the corresponding changes. Can you help reopen the issue?

is this issue still open ?

I'm not sure... I tested in_tail with python's TimedRotatingFileHandler and it seems to work.

conf

<source>
  @type tail
  path ./py_test.log
  pos_file ./pos_py_test.pos
  refresh_interval 5
  read_from_head true
  tag test.log
  <parse>
    @type none
  </parse>
</source>

<match test.**>
  @type stdout
</match>

log

2021-02-03 02:43:00 +0900 [info]: #0 following tail of ./py_test.log
2021-02-03 02:43:00.899691000 +0900 test.log: {"message":"2021-02-03 02:43:00,657 test"}
2021-02-03 02:43:02.909053000 +0900 test.log: {"message":"2021-02-03 02:43:02,663 test"}
2021-02-03 02:43:04.908030000 +0900 test.log: {"message":"2021-02-03 02:43:04,664 test"}
2021-02-03 02:43:06.907831000 +0900 test.log: {"message":"2021-02-03 02:43:06,668 test"}
2021-02-03 02:43:08.908537000 +0900 test.log: {"message":"2021-02-03 02:43:08,669 test"}
2021-02-03 02:43:10 +0900 [info]: #0 detected rotation of ./py_test.log; waiting 5 seconds
2021-02-03 02:43:10 +0900 [info]: #0 following tail of ./py_test.log
2021-02-03 02:43:10.911339000 +0900 test.log: {"message":"2021-02-03 02:43:10,671 test"}
2021-02-03 02:43:12.912024000 +0900 test.log: {"message":"2021-02-03 02:43:12,678 test"}
2021-02-03 02:43:14.912167000 +0900 test.log: {"message":"2021-02-03 02:43:14,683 test"}
2021-02-03 02:43:16.914236000 +0900 test.log: {"message":"2021-02-03 02:43:16,683 test"}
2021-02-03 02:43:18.914319000 +0900 test.log: {"message":"2021-02-03 02:43:18,688 test"}
2021-02-03 02:43:20 +0900 [info]: #0 detected rotation of ./py_test.log; waiting 5 seconds
2021-02-03 02:43:20 +0900 [info]: #0 following tail of ./py_test.log
2021-02-03 02:43:20.915548000 +0900 test.log: {"message":"2021-02-03 02:43:20,700 test"}
2021-02-03 02:43:22.916332000 +0900 test.log: {"message":"2021-02-03 02:43:22,706 test"}
2021-02-03 02:43:24.916393000 +0900 test.log: {"message":"2021-02-03 02:43:24,711 test"}
2021-02-03 02:43:26.918701000 +0900 test.log: {"message":"2021-02-03 02:43:26,712 test"}
2021-02-03 02:43:28.916554000 +0900 test.log: {"message":"2021-02-03 02:43:28,713 test"}
2021-02-03 02:43:30 +0900 [info]: #0 detected rotation of ./py_test.log; waiting 5 seconds
2021-02-03 02:43:30 +0900 [info]: #0 following tail of ./py_test.log
2021-02-03 02:43:30.921425000 +0900 test.log: {"message":"2021-02-03 02:43:30,714 test"}
2021-02-03 02:43:32.922104000 +0900 test.log: {"message":"2021-02-03 02:43:32,719 test"}
2021-02-03 02:43:34.923376000 +0900 test.log: {"message":"2021-02-03 02:43:34,723 test"}
2021-02-03 02:43:36.923727000 +0900 test.log: {"message":"2021-02-03 02:43:36,727 test"}
2021-02-03 02:43:38.923215000 +0900 test.log: {"message":"2021-02-03 02:43:38,729 test"}

python logger

import logging
import logging.handlers
import time

def main():
    log = logging.getLogger(__name__)
    trfh = logging.handlers.TimedRotatingFileHandler('./py_test.log',
        encoding='utf-8', when='S', interval=10, backupCount=10)
    trfh.setFormatter(logging.Formatter('%(asctime)s %(message)s'))
    log.addHandler(trfh)

    while True:
        time.sleep(2)
        log.warning('test')

    return

main()

This is very simple code, so I can't judge my setup is correct or not for reproducing the issue.

Thanks for input here. if path is set to /var/lib/docker/container//.log
will it be able to track each and every rotation ? We are findings issues there while running a simple logging-load-driver program which can generate log-lines at different rates. We can check this happening at different maxsize of logfiles setting.

Which all cases  the below condition if true can miss the rotations ? Please let me know.
Will StatWatcher can track realtime every single file rotation ? Please help me understand it better.
  if @enable_stat_watcher
   tt = StatWatcher.new(path, log) { tw.on_notify }
  tw.register_watcher(tt)
  end.


: fix the problem there has no response when account manager crash

name: Default template
about: Default template for pull request
title: '(scope): subject'
标题
不超过80个字符，英文
格式：
<type>(scope): subject

示例：
<feat>(interchain): support inter-chain call from contract

type
type用于说明PR的类别，只允许使用下面的标识

feat: 新功能

fix: 修复bug

perf: 优化相关，比如提升性能、体验

test: 增加测试

style: 格式（不影响代码运行的变动）

refactor: 重构（即不是新增功能，也不是修改bug的代码变动）

docs: 文档

chore: 构建过程或辅助工具的变动

revert: 回滚到上一个版本

merge: 代码合并

sync: 同步主线或分支的Bug

project: 项目配置如readme、changelog（不影响代码）

scope
scope用于说明PR影响的范围，比如交易、事务、资源、网络等等
subject
subject是PR目的的简短描述

Codecov Report

Merging #474 (b5601d9) into release-1.1.0 (b41fa31) will decrease coverage by 0.07%.
The diff coverage is 0.00%.

@@                 Coverage Diff                 @@
##             release-1.1.0     #474      +/-   ##
===================================================
- Coverage            14.94%   14.87%   -0.08%
  Complexity             401      401
===================================================
  Files                  181      181
  Lines                 8281     8325      +44
  Branches               694      696       +2
===================================================
  Hits                  1238     1238
- Misses                6949     6993      +44
  Partials                94       94

Impacted Files
Coverage Δ
Complexity Δ

...oss/network/client/NettyAsyncHttpClientEngine.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

...s/network/rpc/authentication/RemoteAuthFilter.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

Codecov Report

Merging #474 (b5601d9) into release-1.1.0 (b41fa31) will decrease coverage by 0.07%.
The diff coverage is 0.00%.


Pt 354 clinical statements

Introduction
The following pull request adds a new module which allows the authoring and review of clinical statements.
The plugin supports the listing of clinical statements, however there is currently no rest api which supports the creation of these. With mocked data, this looks like:

A creation panel has been created which allows searching of existing clinical statements (using an external api)

The search is not currently part of the main api, therefore I had to manually wire this in to the main application by adding the following to the proxy section in the webpack-config.js
  '/api-clinicalContent/*': {
    target: 'http://<IP_ADDRESS_HERE>:8080',
    rewrite: function (req){
      req.url = req.url.replace(/^\/api-clinicalContent(.+)$/, '/api/clinicalContent$1');
    }

The creation panel supports validation (at least one statement and author must be defined).
There are three types of statement which can be inputted using the component:

Template with variables in
Free text entry
Static template from rest api

Each of these are shown respectively below.

Final Comments
I have implemented a detail view. However I have not implemented the Edit as the redundancy between Create and Detail pages can be addressed separately.
Currently *Root Solutions are looking in to a more free formed presentation for the statements. This will likely build upon this pull request

I thought it might be worth adding the diff to wire this plugin up:
diff --git a/src/app/actions/index.js b/src/app/actions/index.js
index 85c88ac..4e2a936 100644
--- a/src/app/actions/index.js
+++ b/src/app/actions/index.js
@@ -33,6 +33,7 @@ import appointmentsActions from '../rippleui/pages/appointments/appointments-act
 import imageActions from '../rippleui/pages/dicom/image-actions';
 import eolcareplansActions from '../rippleui/pages/care-plans/eolcareplans-actions';
 import personalnotesActions from '../rippleui/pages/clinical-notes/clinicalnotes-actions';
+import clinicalstatementsActions from '../rippleui/pages/clinical-statements/clinicalstatements-actions';
 import heightAndWeightActions from '../rippleui/pages/height-and-weight/heightAndWeight-actions';
 import genericmdtActions from '../rippleui/pages/generic-mdt/generic-mdt-actions';
 import transferOfCareActions from '../rippleui/pages/transfer-of-care/transfer-of-care-actions';
@@ -57,6 +58,7 @@ export default angular
     .factory('imageActions', imageActions)
     .factory('eolcareplansActions', eolcareplansActions)
     .factory('personalnotesActions', personalnotesActions)
+    .factory('clinicalstatementsActions', clinicalstatementsActions)
     .factory('heightAndWeightActions', heightAndWeightActions)
     .factory('genericmdtActions', genericmdtActions)
     .factory('transferOfCareActions', transferOfCareActions)
diff --git a/src/app/constants/ActionTypes.js b/src/app/constants/ActionTypes.js
index a5073c8..17d3198 100644
--- a/src/app/constants/ActionTypes.js
+++ b/src/app/constants/ActionTypes.js
@@ -257,6 +257,26 @@ export const CLINICALNOTES_UPDATE = 'CLINICALNOTES_UPDATE';
 export const CLINICALNOTES_UPDATE_SUCCESS = 'CLINICALNOTES_UPDATE_SUCCESS';
 export const CLINICALNOTES_UPDATE_ERROR = 'CLINICALNOTES_UPDATE_ERROR';

+export const CLINICALSTATEMENTS = 'CLINICALSTATEMENTS';
+export const CLINICALSTATEMENTS_SUCCESS = 'CLINICALSTATEMENTS_SUCCESS';
+export const CLINICALSTATEMENTS_ERROR = 'CLINICALSTATEMENTS_ERROR';
+
+export const CLINICALSTATEMENTS_GET = 'CLINICALSTATEMENTS_GET';
+export const CLINICALSTATEMENTS_GET_SUCCESS = 'CLINICALSTATEMENTS_GET_SUCCESS';
+export const CLINICALSTATEMENTS_GET_ERROR = 'CLINICALSTATEMENTS_GET_ERROR';
+
+export const CLINICALSTATEMENTS_CREATE = 'CLINICALSTATEMENTS_CREATE';
+export const CLINICALSTATEMENTS_CREATE_SUCCESS = 'CLINICALSTATEMENTS_CREATE_SUCCESS';
+export const CLINICALSTATEMENTS_CREATE_ERROR = 'CLINICALSTATEMENTS_CREATE_ERROR';
+
+export const CLINICALSTATEMENTS_UPDATE = 'CLINICALSTATEMENTS_UPDATE';
+export const CLINICALSTATEMENTS_UPDATE_SUCCESS = 'CLINICALSTATEMENTS_UPDATE_SUCCESS';
+export const CLINICALSTATEMENTS_UPDATE_ERROR = 'CLINICALSTATEMENTS_UPDATE_ERROR';
+
+export const CLINICALSTATEMENTS_QUERY = 'CLINICALSTATEMENTS_QUERY';
+export const CLINICALSTATEMENTS_QUERY_SUCCESS = 'CLINICALSTATEMENTS_QUERY_SUCCESS';
+export const CLINICALSTATEMENTS_QUERY_ERROR = 'CLINICALSTATEMENTS_QUERY_ERROR';
+
 export const TRANSFEROFCARE = 'TRANSFEROFCARE';
 export const TRANSFEROFCARE_SUCCESS = 'TRANSFEROFCARE_SUCCESS';
 export const TRANSFEROFCARE_ERROR = 'TRANSFEROFCARE_ERROR';
diff --git a/src/app/index.js b/src/app/index.js
index 01f5ff6..e0d57dd 100644
--- a/src/app/index.js
+++ b/src/app/index.js
@@ -107,6 +107,10 @@ import ClinicalnotesListComponent from './rippleui/pages/clinical-notes/clinical
 import ClinicalnotesCreateComponent from './rippleui/pages/clinical-notes/clinicalnotes-create.component';
 import ClinicalnotesDetailComponent from './rippleui/pages/clinical-notes/clinicalnotes-detail.component';

+import ClinicalstatementsListComponent from './rippleui/pages/clinical-statements/clinicalstatements-list.component';
+import ClinicalstatementsCreateComponent from './rippleui/pages/clinical-statements/clinicalstatements-create.component';
+import ClinicalstatementsDetailComponent from './rippleui/pages/clinical-statements/clinicalstatements-detail.component';
+
 import HeightAndWeightListComponent from './rippleui/pages/height-and-weight/heightAndWeight-list.component';
 import HeightAndWeightDetailComponent from './rippleui/pages/height-and-weight/heightAndWeight-detail.component';

@@ -206,6 +210,10 @@ const app = angular
     .component('clinicalnotesCreateComponent', ClinicalnotesCreateComponent)
     .component('clinicalnotesDetailComponent', ClinicalnotesDetailComponent)

+    .component('clinicalstatementsListComponent', ClinicalstatementsListComponent)
+    .component('clinicalstatementsCreateComponent', ClinicalstatementsCreateComponent)
+    .component('clinicalstatementsDetailComponent', ClinicalstatementsDetailComponent)
+
     .component('heightAndWeightListComponent', HeightAndWeightListComponent)
     .component('heightAndWeightDetailComponent', HeightAndWeightDetailComponent)

diff --git a/src/app/index.route.js b/src/app/index.route.js
index 3d7f977..a62f8af 100644
--- a/src/app/index.route.js
+++ b/src/app/index.route.js
@@ -825,6 +825,64 @@ function routeConfig($stateProvider, $urlRouterProvider) {
         }]
       })

+      .state('clinicalStatements', {
+        url: '/patients/{patientId:int}/clinicalStatements?reportType&searchString&queryType',
+        views: {
+          banner: {template: '<patients-banner-component></patients-banner-component>'},
+          actions: {template: '<patients-sidebar-component></patients-sidebar-component>'},
+          main: {template: '<clinicalstatements-list-component></clinicalstatements-list-component>'}
+        },
+        breadcrumbs: [{
+          title: 'Patient Listings',
+          state: 'patients-list'
+        }, {
+          title: 'Patient Summary',
+          state: 'patients-summary'
+        }, {
+          title: 'Clinical Statements',
+          state: 'clinicalStatements'
+        }]
+      })
+      .state('clinicalStatements-create', {
+        url: '/patients/{patientId:int}/clinicalStatements/create?reportType&searchString&queryType',
+        views: {
+          banner: {template: '<patients-banner-component></patients-banner-component>'},
+          actions: {template: '<patients-sidebar-component></patients-sidebar-component>'},
+          main: {template: '<clinicalstatements-list-component></clinicalstatements-list-component>'},
+          detail: {template: '<clinicalstatements-create-component></clinicalstatements-create-component>'}
+        },
+        breadcrumbs: [{
+          title: 'Patient Listings',
+          state: 'patients-list'
+        }, {
+          title: 'Patient Summary',
+          state: 'patients-summary'
+        }, {
+          title: 'Clinical Statements',
+          state: 'clinicalStatements'
+        }]
+      })
+      .state('clinicalStatements-detail', {
+        url: '/patients/{patientId:int}/clinicalStatements/{clinicalStatementIndex}?filter&page&reportType&searchString&queryType&source',
+        views: {
+          banner: {template: '<patients-banner-component></patients-banner-component>'},
+          actions: {template: '<patients-sidebar-component></patients-sidebar-component>'},
+          main: {template: '<clinicalstatements-list-component></clinicalstatements-list-component>'},
+          detail: {template: '<clinicalstatements-detail-component></clinicalstatements-detail-component>'}
+        },
+        params: { source: '{}' },
+        breadcrumbs: [{
+          title: 'Patient Listings',
+          state: 'patients-list'
+        }, {
+          title: 'Patient Summary',
+          state: 'patients-summary'
+        }, {
+          title: 'Clinical Statements',
+          state: 'clinicalStatements'
+        }]
+      })
+
       .state('heightAndWeights', {
         url: '/patients/{patientId:int}/heightAndWeights?reportType&searchString&queryType',
         views: {
diff --git a/src/app/redux/reducer.js b/src/app/redux/reducer.js
index 4c0d5e3..63ad413 100644
--- a/src/app/redux/reducer.js
+++ b/src/app/redux/reducer.js
@@ -40,6 +40,7 @@ import instanceIdGet from '../rippleui/pages/dicom/instance-id-reducer-get';
 import eolcareplans from '../rippleui/pages/care-plans/eolcareplans-reducer-all';
 import heightAndWeight from '../rippleui/pages/height-and-weight/heightAndWeight-reducer-all';
 import personalnotes from '../rippleui/pages/clinical-notes/clinicalnotes-reducer-all';
+import clinicalStatements from '../rippleui/pages/clinical-statements/clinicalstatements-reducer-all';
 import genericmdt from '../rippleui/pages/generic-mdt/generic-mdt-reducer-all';
 import transferOfCare from '../rippleui/pages/transfer-of-care/transfer-of-care-reducer-all';

@@ -69,6 +70,7 @@ export default combineReducers({
   eolcareplans,
   heightAndWeight,
   personalnotes,
+  clinicalStatements,
   genericmdt,
   transferOfCare
 });
\ No newline at end of file
diff --git a/webpack.config.js b/webpack.config.js
index 60f0c00..4968685 100644
--- a/webpack.config.js
+++ b/webpack.config.js
@@ -158,6 +158,12 @@ if (ENV_DEVELOPMENT) {
     proxy: {
       '/api/*': {
         target: API_URL
+      },
+      '/api-clinicalContent/*': {
+        target: 'http://<IP_ADDRESS>:8080',
+        rewrite: function (req){
+          req.url = req.url.replace(/^\/api-clinicalContent(.+)$/, '/api/clinicalContent$1');
+        }
       }
     },
     historyApiFallback: true

Details about the expected api structure
Following a discussion with [~rob.tweed], he has demonstrated the structure which I can expect to receive from the querying side of this. Given an optional tag and a query, an expected response would be
[{
    "phraseId": 9,
    "phrase": "Some phrase from the backend"
  },
  ...
]

The structure of the phrases will contain delimiters which the UI will process to return specified values back to the api. The following delimiters should be expected ~SUBJECT~ |VALUE| {UNIT}
A selected phrase which contains any of these delimiters can be submitted back to the rest api with values. E.g
[{
  "phraseId": 9,
  "subject": "My special subject",
  "value": "5000",
  "unit": "elephants"
}]

In the case of a fresh phrase (one which is not provided by the api). It is expected that a structure similar to the following will be sent:
[{
  "phraseId":null,
  "subject": "Full fresh subject statement"
}]

Code was included & refactored in order to fit the needs of the application;
PR can be closed


TexturePacker for Sprite WITH ERRORS

DO NOT MERGE CONTAINS ERRORS
I need some help. Currently I am testing that the changes are backward compatible and am having a problem displaying the correct cell.
When you load this page (sprit cellIndex set to 0) https://tender-murdock-275855.netlify.com/sprites/test1.html you will see sprite cellIndex 44 upside down in the center as a sprite, after a moment the data for cellIndex 0 is used as a texture for the plane on the right.
The data for the plane texture can be seen on lines 68, 69 and 75, 76 of https://github.com/BabylonJSGuide/oddsNEdnds/blob/master/sprites/Test1.html, the console values seem also confirm the correct values.
 As far as I can see what I have done for vUV.x and vUV.y in the sprite,vertex.fx file matches what I did on line 68, 69, 75, 76 in the test1.html file.
Any help in spotting my error (whatever it is) would be gratefully received as I have been looking at it for a couple of days now  and can not see what I have done wrong. (Own mistakes often remain invisible). Thank you.

Nearly there still have a minor issue to solve. When I am happy I will close this PR and open a new one.
A point of clarification if you do not mind:
I am using assetsManager to load the json file as in my PR spriteManager.ts lines 233 to 264.
Is this a good a way as any or would there be a better way?

I would recommend not loading it with the assetManager and more with a direct XHR call as users may not want to drag the AssetsManager dependency if they only use the Sprites sub system

Opening a new PR for this


fix: refine tars query

log look like:
{"event-GUID":"e70a40f6-7a56-11eb-9920-5b7df3cfafa3","event-type":"push","level":"info","msg":"Search for query "archived:false is:pr is:open sort:created-asc org:"ti-community-infra" repo:"test-dev" base:"/master"" cost 3 point(s). 4975 remaining.","plugin":"ti-community-tars","time":"2021-03-01T06:25:23Z"}
{"event-GUID":"e70a40f6-7a56-11eb-9920-5b7df3cfafa3","event-type":"push","level":"info","msg":"Considering 0 PRs.","plugin":"ti-community-tars","time":"2021-03-01T06:25:23Z"}
{"event-GUID":"e76c35b8-7a56-11eb-95cd-da45d7f2c8d6","event-type":"push","level":"info","msg":"Checking ti-community-infra/test-dev#/testaddeee PRs.","plugin":"ti-community-tars","time":"2021-03-01T06:25:23Z"}
{"event-GUID":"e76c35b8-7a56-11eb-95cd-da45d7f2c8d6","event-type":"push","level":"info","msg":"Search for query "archived:false is:pr is:open sort:created-asc org:"ti-community-infra" repo:"test-dev" base:"/testaddeee"" cost 3 point(s). 4972 remaining.","plugin":"ti-community-tars","time":"2021-03-01T06:25:23Z"}

/hold

/assign @Mini256
PTAL~ Thanks!
/unhold

/merge


Option to save search terms in a list

I like some particular artists more than others, but there is no way to quickly access those artists. The collections and bookmarks would have to be maintained with each new work.
So could you add a button that allows us to save and access specific searches? That way you wouldn't have to type in specific search terms each time and can quickly search your favorite genres.
There doesn't seem to be an OR function built into the search unfortunately, right? On the ehentai page a "~" character is interpreted as OR, so you can display multiple artists at once with one search query.

Do you prefer to save the search history or add a list of options manually

Thank you for your quick reply!
I would prefer a list that you can add manually.
But maybe it would be easier to integrate it into the user interface if you can only save the search term.
For example with a star icon to "save" the search term and then a star icon to call the saved keyword list.
Here's just an idea of how it might look, in the end I'm happy to see an integration no matter what it looks like.
https://imgur.com/a/bgd3Fxb

Added customOptions in version 1.4.10.


Add named pipe support for windows

This PR adds named pipe support for windows machines. Named pipes are similar to unix domain sockets. This PR supports submitting metrics to Datadog in Azure App Services (https://github.com/DataDog/datadog-aas-extension).
The main changes are:

Abstracting DatagramChannel into the ClientChannel interface
Adding a ClientChannel implementation for named pipes
Adding configuration support in the builder
Subclassing DummyStatsD server for testing of the 3 transport types

Unfortunately, only existing named pipes can be written to in pure Java. In order to create named pipes for testing, JNA is used.

@vickenty Did you want to rereview or should I just merge this PR with the fixes?

@randomanderson Sorry for the delay, I will take another look. Meanwhile, we would like to make sure configuration options are the same between libraries for different languages. Windows pipes are not universally supported by all libraries we support, but where it is available, we'd like the configuration to be the same (same env vars / methods). Can you please check if we're aligned with https://github.com/DataDog/datadog-go for example?

@vickenty Windows pipes are only implemented in .NET and the dogstatsd server. They both use DD_DOGSTATSD_PIPE_NAME which is what I used here

There are some warnings in the CI, would you mind taking a look and fixing if any are new?
Do you think it might be useful to throw an error if named pipe is requested on a non-windows OS?

@vickenty I made that small change. I left the 2-arg constructor because UnixDatagramClientChannel uses it.


OrbTk apps crashes when left on its own

Describe the bug
When I'm AFK for a minute, after coming back I see that a previously launched OrbTk app is disappeared and Visual Studio's terminal is full of stack traces.
I'm experiencing this the third time.
To Reproduce
Steps to reproduce the behavior:

Compile and run any example of orbtk or your own app using orbtk from Visual Studio's terminal with cargo run
Leave it alone for a few minutes (at least 10-15), go drink a coffee, or eat your lunch, etc,
Come back to the PC
See an error in Visual Studio's terminal and that app is closed.

Expected behavior
The apps should not crash, even if it's running for months, or year(s).
Desktop (please complete the following information):

OS: Windows 10 build 1903
Version: 0.3.1-alpha1

Additional context
Backtrace logs attached.
backtrace_1.txt
backtrace_2.txt
backtrace_3.txt

@kivimango thank you for the report, this also for the latest version.

Could you check it again. I used the doit app the complete work day and it didn't crashed.

I did not experience crashes for now. It was related to RenderingTasks, maybe the changes to the rendering backend fixed it somehow.


Infeasible Problem Detected - CasLL1 alpha sweep with custom Cl, Cd and Cm functions

Hey Peter,
I'm trying to use casll1 as a solver instead of optimizing and I'm performing an alpha sweep analysis on a conventional configuration using my own functions for the sectional Cl, Cd and Cm. These functions are just polynomial fits to data obtained from CFD analyses on the airfoil for the Reynolds and Mach number of interest.
I'm defining the aircraft and running the alpha sweep the same way presented in the examples with the addition of the custom airfoil functions. However, depending on the operating point, the solver raises an error, which can be read using the cas.Opti().debug method:
sol
Opti(Opti {
  instance #0
  #variables: 2 (nx = 144)
  #parameters: 1 (np = 1)
  #constraints: 2 (ng = 144)
  CasADi solver allocated.
  CasADi solver was called: Infeasible_Problem_Detected
})

I played around with the solver settings and various paneling combinations, however, the issue persisted. Is this an issue with the casll1 solver or does it have to do with CasADI? Is there a way to use the casll1 solver without setting up an optimization environment?
I am also attaching the code I'm using along with a json file containing all the data required for the aircraft and operating point definition.
aircraft_casll1.zip
Sorry for the long question. I really think what you are building here is great!

Thanks for writing in, and especially thanks for providing the steps to reproduce this - taking a look at this now!
One quick observation - you can comment out line 441 of aero_solver.py:
    # prob.setup(run_symmetric_if_possible=True)

This setup happens as part of the Casll1 constructor (you have this in line 425), so this will save you a hair of computational time :)
Looking over the rest now!

Cool - I think I've found the issue!
Why it's failing: Local alphas are too high
If I'm interpreting your setup correctly, this is what the 2D lift curve for your wing airfoil looks like:

While one of CasLL1's biggest strengths is that it can solve with nonlinear 2D data, this lift curve slope is exceptionally nonlinear (significant decambering by 6 degrees; CL_max at 8.5 degrees). It's possible that the solver is getting stuck due to this strong nonlinearity. At the alpha = 10 case, this is what the local angles of attack look like at each section:

Noting that some sections are reporting local angles of attack as high as 13.8 degrees, it's possible that these are nonlinear enough to cause solution failure above this point.
Why local alphas are too high
So, this is puzzling, because you don't typically see local angles of attack that ever significantly exceed the local angle of attack - if anything, they're usually significantly lower than the freestream angle of attack due to downwash.
So what's happening? Why are the local alphas peaking so high (13.8 degrees, -14.8 degrees)? There's something in the solution that's causing a massive unhandled circulation jump - let's see if we can find it. Here's what the local angles of attack look like:

At first, this looks normal - but if we zoom in on the wing, we find this:

It looks like flaps are being implemented here, but their circulation jump is just too sharp to be resolved correctly by our discretization.
You might try spreading out the flap transition length (in the spanwise direction) or reducing the nonlinearity of the lift curves to see if that makes a difference.
One hot fix
One thing that you can instantly due to (partially) alleviate some of these issue is to adjust how the analysis initializes itself. By supplying a better initial guess, you'll deal with nonlinearities better. It turns out that a great initial guess is just the last solution, so you can just pop these into your code as an instant upgrade: (near line 475 of aero_solver.py)
        # Solve
        sol = opti.solve()
        opti.set_initial(sol.value_variables()) # NEW LINE: Initialize primals from last solution
        opti.set_initial(opti.lam_g, sol.value(opti.lam_g)) # NEW LINE: Initialize duals from last solution
        # Create solved object
        prob_sol = copy.deepcopy(prob)
        prob_sol.substitute_solution(sol)

By adding these two lines, I was able to keep this converging to alpha = 12 or so! That  but beyond that, I think it's just too nonlinear with the existing lift curves! That gives this happy lil airplane (drawn with prob_sol.draw()):

Beyond 12 degrees, my hunch is that this is just too nonlinear with the existing lift curves - but the steps listed above may help!

Thanks a lot for your prompt and very detailed response! I suppose I have to accept the limitations of the lifting line theory when it comes to very non-linear cases. Below I am attaching the lift curve of my double-slotted flapped airfoil. I guess these excessively non-linear cases cannot be handled by lifting line theory. It would not even converge at 0 degrees.

On the other hand, removing the intermediate spanwise wing sections and applying a finer paneling (25 spanwise panels) allowed me to extend the solution up to 15 degrees, even using the lift curve you showed above. My issue might have something to do with the transition between the flapped and unflapped regions. Increasing the panel density near these regions didn't really make a difference, even if I spread out the flap transition length. Since I was able to get converged solutions with the unflapped wing, I will just implement the flap effects using empirical methods provided by DATCOM. I will also try and simplify the polar fits to something like an exponential and see if that makes a difference.
One more question regarding the definition of the airfoil functions. Is the lambda method the only way to define those functions? And if so, I was trying to use if statements to define different fits depending on the angle of attack, however "alpha" is not compatible with boolean operations, as it's type is "MX", created using the CasADI package. Is there a way to bypass that?
Traceback (most recent call last):
  File ".\aero_solver.py", line 535, in <module>
    data = aero_solver('aero_generate.json', 'cruise')
  File ".\aero_solver.py", line 459, in aero_solver
    opti=opti
  File "C:\Python37\lib\site-packages\aerosandbox\aerodynamics\casll1.py", line 23, in __init__
    self.setup()
  File "C:\Python37\lib\site-packages\aerosandbox\aerodynamics\casll1.py", line 66, in setup
    self.calculate_vortex_strengths()
  File "C:\Python37\lib\site-packages\aerosandbox\aerodynamics\casll1.py", line 414, in calculate_vortex_strengths
    ) for i in range(self.n_panels)
  File "C:\Python37\lib\site-packages\aerosandbox\aerodynamics\casll1.py", line 414, in <listcomp>
    ) for i in range(self.n_panels)
  File "C:\Python37\lib\site-packages\aerosandbox\aerodynamics\casll1.py", line 151, in <lambda>
    deflection=inner_xsec.control_surface_deflection
  File ".\aero_solver.py", line 197, in <lambda>
    airfoil_pC(pClw, alpha)
  File ".\aero_solver.py", line 9, in airfoil_pC
    if aoa <= 10:
  File "C:\Python37\lib\site-packages\casadi\casadi.py", line 9651, in __bool__
    return _casadi.MX___bool__(self, *args)
RuntimeError: .../casadi/core/mx_node.cpp:181: Can only determine truth value of a numeric MX.

Hi @alexandroslessis !
Will respond in more detail later, but to do a conditional statement, use:
cas.if_else(conditional, value_if_true, value_if_false)

like:
cas.if_else(alpha > 5, value_if_true, value_if_false)


Utilize Object.observe for automatic dirty checks

It would be quite nice if Loki supported automatic dirty checks via Object.observe (if available), which would make it unnecessary to call update() manually.
Ideally an implementation of this feature could also check whether an indexed property was changed and unlike update() only mark the affected indexes as dirty.
This would make code easier and possibly even faster (since no unnecessary index rebuilds will be triggered).

I suppose feature detection is just checking if that method exists?  Quick search leads me to think maybe this is supported as of node.js version 12.0 (regular -and- harmony)? I suppose all objects could register the same callback and we could dig out the $loki id when it fires.  Would probably need throttling too.
Not sure what @techfort's thoughts on this are, so we'll see what he thinks.  Is this something you would be interested in contributing or just curious?

Sure. I'd like to help with this feature. I would have already started sketching it out if I were more familiar with the codebase. Would you simply add the observers in loadJSON and insert or are there other ways for an object to get into Loki?
Regarding Object.observe support: Yes. As far as I know Object.observe is enabled without runtime flags in Node 0.12+, Chrome 36+ and Opera 30+.

@Cortys the idea is nice, however in the future i'd like object clones to be returned from insert/update/read operations, which means you'd be monitoring the wrong object with observe(). Or do I misunderstand what you're saying?

@techfort You are right. When working with clones this feature would not be useful.
Now that you mention it, how would clones and the object inflation feature play together?

@Cortys the current default inflation pattern is already a clone of sorts, because inflating objects from serialized json effectively creates a new object from a constructor function then copies properties from the source object to the new destination object. So this would not change. If anything, leveraging ES2015 will make it easier to inflate json into a prototype by doing Object.assign( (new MyObject()), srcObject)
How does it sound?

@techfort Right, that's when creating the objects. When reading however, do I get a newly inflated instance for each query or do I always get the same inflated object?

@Cortys I suppose this would really be optional. If the user needs a full prototype copy at each read he/she should be able to specify so. Probably by specifying a clone function? I mean it's all very much optional so it can go to any level of complexity.

@techfort I see. So getting the actual objects instead of clones will still be possible, right?
Regarding the Object.observe idea: I think it would be useful with or without the clone feature. When clones are used, those could be observed as well and changes can then be reproduced at the corresponding DB internal object.

@Cortys absolutely! If you want to draft that up i'd be curious. And yes, getting the actual objects will be possible.

@techfort Great! I'll take a look at it this weekend.
One question: Would you simply attach the observers in loadJSON/loadDatabase and insert or are there other ways for an object to get into Loki?

Those are the only ways. And of course insert()
On Fri 2 Oct 2015 20:13 Clemens Damke<EMAIL_ADDRESS>wrote:

@techfort https://github.com/techfort Great! I'll take a look at it
this weekend.
One question: Would you simply attach the observers in loadJSON/
loadDatabase and insert or are there other ways for an object to get into
Loki?
—
Reply to this email directly or view it on GitHub
https://github.com/techfort/LokiJS/issues/231#issuecomment-145129182.

Implementation for this merged in #233.

Just for my own understanding...
What is the explanation behind "dirty" term in lokijs?
Thanks for your help
You can let this ticket closed :)

dirty is usually a flag to indicate that an object's state has changed and its cache representation is stale @thomaschampagne

@techfort Thanks for the clarification 👍


Add basic NLP models like text-classification or sequence-to-sequence.

🚀 Feature
Incorporate basic NLP models like text classification or sequence-to-sequence models.
Do I need to clarify further?

mind have look at #128 #34

Yes, it would be great to extend support to NLP. We can probably add torchtext support as well.
torchtext is currently under revamp, the old data modules are getting deprecated and in October release we will have stable and good torchtext on which we can build pipelines.
Have a look here.

I've been working on this. I think we want options for using both torchtext and HuggingFace transformers. So much research has gone towards transformers in NLP, so I want to support that...but we should also support torchtext stuff too.
I'm thinkin for torchtext, we use their data sources, for HuggingFace, we use their datasets library. That way we can install either version independently so the dependencies don't start stacking up.
What do you think?


Fix ExportDataAsCode not considering some characters for variable name

With a fileName argument like my-image.png.h, the output inside my-image.png.h looks like this:
#define MY-IMAGE.PNG_DATA_SIZE     119076

static unsigned char MY-IMAGE.PNG_DATA[MY-IMAGE.PNG_DATA_SIZE] = ...

This commit checks if characters such as -, ., ? and ! are present in varFileName and replaces them with _, so my-image.png.h would be
#define MY_IMAGE_PNG_DATA_SIZE     119076

static unsigned char MY_IMAGE_PNG_DATA[MY_IMAGE_PNG_DATA_SIZE] = ...

I think you have not considered enough. Filenames beginning with '+' are also not okay, as an example.
There are also multiple ExportXAsCode functions where this needs to be considered.
See #3814 as well.

Right, I checked Ray's decision on this topic and will close the pr. Thanks!

@lauchimoon I finally decided to implement this change, I merged a similar PR (#3832) but I think yours is better, please, could you resent it?

Hi @raysan5, sure thing! If there's any other functions I should modify please lmk :)

Will open a new commit because I've made a mess with the conflicts...


region-fg in doom-nord breaks other themes (but not doom-nova)

After 36962d9a13c310ea0bbb23d18b59581ba458710c , if doom-nord is applied, and another doom theme is applied afterwards, the new theme won't load; I did this using counsel, but manually evaluating load-theme on one of the affected themes returns the error (void-variable region-fg) if the debugger loads, and the usual Symbol's value as variable is void: region-fg in the minibuffer. In my tesitng, the only theme that is not affected is doom-nova.

e54e7a0f may have addressed this, by deferring evaluation to post-expansion of the macro. I have been unable to reproduce this issue, so this is a shot in the dark. Give it a try and let me know!

I am closing this, because it is a duplicate of #166.


use unpacking

https://github.com/openforis/gfc_wrapper_python/blob/09e4e287026af6178036ea6db30d2f64ee0fc645/component/scripts/compute_areas.py#L178
I can do the same in 1 single line

read better next time


UKI: branding and menu configuration for active, passive and recovery

Is your feature request related to a problem? Please describe.
Currently in GRUB mode we can have custom menu entries and we can customize the installed entries for active, passive and recovery. We can also add new entries that uses the same files with different boot args
Describe the solution you'd like
Branding to work as compatible with what GRUB supports, however we can also document the required steps (as creating the entries manually) or make it part of the shim.
We need also to document how to create multiple entries for the same file (with different boot cmdargs)
Describe alternatives you've considered
Document the manual steps
Additional context
This should be part of the shim:

We currently support GRUB
systemd-boot have to be supported as well

Few links.
For branding, very simple is just text files:

https://wiki.archlinux.org/title/systemd-boot#Configuration
https://uapi-group.org/specifications/specs/boot_loader_specification/ (type 2, which is UKI)

For cmdline override and different configs:

https://www.freedesktop.org/software/systemd/man/latest/systemd-stub.html#Companion Files

Basically systemd-boot supports having *.addon.efi files (signed) which provide only the .cmdline and .dbt sections and can be used to "override" whats on the main UKI EFI file

one idea would be:

during build, we allow building those extra PE files with different cmdlines (as example, one normal one with rd.immucore.debug)
those PE have an extra section called .branding
That branding is what systemd-boot would show, so what we have to store in the conf file
During install/upgrade a hook checks for those PE files and extracts the .branding section (its plain text) and creates the conf files to have different entries

Another ide would be to actually build those cmdlines and CHECK what systemd-boot does with them, becuase we currently have no idea. If you got your kairos.efi file and then a normal.efi and a debug.efi files in there, what does systemd-boot does? Does it show 2 different entries? Becuase maybe it does it out of the box and we only need the branding to show up and the cmdline appears by itself somehow
Alos, we may need to check with upstream directly to ask for this use-case as thye may have it covered already. systemd has a nice matrix chat where the full dev team is in there, so it may be the fastest way to check this.

bad news, we have to duplicate each uki file for each cmdline that we want: https://github.com/systemd/systemd/issues/24539


Feat: Display Confirmation Message After Form Submission

Describe the feature
Implement a feature that displays a confirmation message to users after they successfully submit a newsletter form. This message should confirm that their submission has been received.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@anuragverma108 @huamanraj  @RishabhDhawad Sir please assign this issue to me

Assigned!
Make sure to attach before & after screenshots in your PR and include the issue number.
Also, please star the repo before working on it. Happy open-source contributing!


fix tests issue #178

new PR for #178

@sobolevn fix it

Thanks! Let's wait for @lk-geimfari to merge it!

@sobolevn You can merge any PR by yourself, if everything is in okay. You are collaborator.


HADOOP-18880. Add some rpc related metrics to Metrics.md

Description of PR
https://issues.apache.org/jira/browse/HADOOP-18880
Add some rpc related metrics to Metrics.md
such as
DeferredRpcProcessingTime
RpcResponseTime
RpcRequeueCalls

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 30s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
markdownlint
0m  0s

markdownlint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
34m 40s

trunk passed

+1 :green_heart:
compile
11m 26s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
9m 37s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
0m 51s

trunk passed

+1 :green_heart:
mvnsite
1m 10s

trunk passed

+1 :green_heart:
javadoc
0m 59s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 42s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
1m 43s

trunk passed

+1 :green_heart:
shadedclient
22m 23s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 39s

the patch passed

+1 :green_heart:
compile
9m 44s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
9m 44s

the patch passed

+1 :green_heart:
compile
9m 36s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
9m 36s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 47s

the patch passed

+1 :green_heart:
mvnsite
1m 10s

the patch passed

+1 :green_heart:
javadoc
0m 53s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 42s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
1m 44s

the patch passed

+1 :green_heart:
shadedclient
22m 16s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
16m 23s

hadoop-common in the patch passed.

+1 :green_heart:
asflicense
0m 49s

The patch does not generate ASF License warnings.

151m 47s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6015/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6015

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets markdownlint

uname
Linux 6dad2523537d 4.15.0-212-generic #223-Ubuntu SMP Tue May 23 13:09:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 7f4cdb34a292908cd9d74b819e9ab6ae724d9839

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6015/1/testReport/

Max. process+thread count
1276 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6015/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

Thanks @slfan1989 @goiri help me review and merge it.


Add option to manually pick a color for a contact

Hello GermainZ and thank you for this great application !
Would it be possible to add an option to manually set background color of a contact picture?
The automatic generation is very good but I would like to to define myself the color of some special contacts :)

could tie into #8 if there was the option to limit color pallet temporalily and regenerate.


cmd/compile: weird diagnostic, missing method instead of duplicate

What version of Go are you using (go version)?

$ go version
go version go1.19.4 linux/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
playground
What did you do?
package main

type A interface {
	a()
}

type AB interface {
	A
	b()
}

type Foo struct {
	A
	AB
}

func main() {
	var _ AB = Foo{}
}

https://go.dev/play/p/_SQyOJ_n2qv
What did you expect to see?
Either no error or an error saying that Foo has 2 a methods.
What did you see instead?
./prog.go:18:13: cannot use Foo{} (value of type Foo) as type AB in variable declaration:
	Foo does not implement AB (missing a method)

I didn't find this case in spec, but the message seems wrong.

@griesemer

Foo doesn't have two a methods; it is missing method a because a is not promoted due to being present in two embedded fields at the same depth. The rule comes from https://go.dev/ref/spec#Selectors:

For a value x of type T or *T where T is not a pointer or interface type, x.f denotes the field or method at the shallowest depth in T where there is such an f. If there is not exactly one f with shallowest depth, the selector expression is illegal.

And per https://go.dev/ref/spec#Struct_types, a field or method f of a type embedded in a struct x is only promoted when x.f is a legal selector.

It seems reasonable in principle for the error message hint to be "ambiguous selector" instead of "missing method".
/cc @findleyr

Agreed. This should be fairly straight-forward. I'll have a look.


how to call a function with arguments

Hello there,
can you please share a way we can call a function and pass it a parameter?
i tried the lambda but i'm getting error..
Ticker smyFunc([](char i)                            { funcToCall(i); },                            1, 1);
thank you,
Jay

There is an example which using lambdas. Using functional was an PR not from me.

yes i just saw that, thank you :)


Add kustomization for crds

Closes https://github.com/aws/aws-controllers-k8s/issues/468
Description of changes:
Now when you run kustomize build services/${SERVICE}/config/default crds are generated.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Hi @jaypipes thanks. I will follow up with changes to the ack-generate controller.

@jaypipes closing this in favor of https://github.com/aws/aws-controllers-k8s/pull/508


Automatically extend vitest with wrapito matchers

:tophat: What?

Automatically add wrapito-vitest matchers to vitest.
:thinking: Why?

Pure convenience, the older way still works.
:test_tube: How has this been tested? / :boom: How will I know if this breaks?

I test this locally using secco and our Vite boilerplate.
🗣 Comments
Now when you install wrapito-vitest in your setupTest.ts you can do:
import 'wrapito-vitest/integration'
import { configure } from 'wrapito-vitest'

configure({}) // Normal configuration

And matchers will be added to vitest.

Closes #48


Fix NPE while decoding private key with invalid alias [1.1.x]

Purpose
This PR fixes NPE while decoding private key with invalid alias.
Fixes #20896
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #21190 into ballerina-1.1.x will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff                @@
##           ballerina-1.1.x   #21190   +/-   ##
================================================
  Coverage            15.21%   15.21%
================================================
  Files                   50       50
  Lines                 1341     1341
  Branches               208      208
================================================
  Hits                   204      204
  Misses                1121     1121
  Partials                16       16

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 41d6018...e6c8b02. Read the comment docs.


Homepage: Quote content

Quote should be a testimonial about a group that benefits from BSSw rather than inspirational

This is old and long done.


Stuck on pinging, then crash with "ticking screen"

I'm not even sure CMM is the cause of this, it just seemed like the only possible thing that could be causing it, and it's the ONLY mod in my pack that is GUI related that has updated since the issue started to occur.
Basically on the Multiplayer screen where it would normally say "pinging" for a second or two and then show the server info, it will say "Pinging" for several seconds and then crash with this ticking screen error: https://paste.dimdev.org/fuzutoqepu.mccrash

Found out this is VanillaFix...https://github.com/DimensionalDevelopment/VanillaFix/issues/128
Closing :)


TypeError: run_algorithm() got an unexpected keyword argument 'data'

Dear Zipline Maintainers,
I used Dockerfile to run zipline as a container,
when i send pandas data panel as data parameter to run_algorithm function, it returns the following error:
TypeError: run_algorithm() got an unexpected keyword argument 'data'
It's worth mentioning that the same exact code works perfectly in ubuntu but when running in the docker container it produces the error.
Below you can see the code:
def run_strategy(strategy_name):
mod = ScalpBollingerBand()
data_panel, start, end = prepareCSV('csv')
print(data_panel, type(start))
return run_algorithm(
   trading_calendar=CryptoCalendar(),
    initialize=getattr(mod, 'initialize', None),
    handle_data=getattr(mod, 'handle_data', None),
    before_trading_start=getattr(mod, 'before_trading_start', None),
    analyze=getattr(mod, 'analyze', None),
    data=data_panel,
    environ=environ,
    data_frequency='minute',
    **merge({
        'capital_base': 5000,
        'start': start,
        'end': end,
   }, mod._test_args())
)

I have the same issue. No fix more than 1 year after?

I have the same problem with a using a python venv.
zipline.__version__
'1.4.1'

The docstring for run_algorithm indeed does not have this kwarg.

I have the same problem with a using a python venv.
zipline.__version__
'1.4.1'

The docstring for run_algorithm indeed does not have this kwarg.

The argument 'data' has been deprecated. I guess we have to input the data file to a bundle in Zipline and run a backtest with the custom Bundle. See docs here: https://www.zipline.io/bundles.html


<EMAIL_ADDRESS>invalid version: unknown revision due to connect: connection timed out (but the repo server isn't down)

Package ecosystem

Go
Package manager version

go.mod 1.16
Language version

Go 1.16
Manifest location and content prior to update

https://github.com/containerd/nerdctl/blob/785fc7346a1bb34979b0ee4fa519ed08b43754d4/go.mod
dependabot.yml content

https://github.com/containerd/nerdctl/blob/785fc7346a1bb34979b0ee4fa519ed08b43754d4/.github/dependabot.yml
Updated dependency

N/A
What you expected to see, versus what you actually saw

Dependabot fails with the following error:
go<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>invalid version: unknown revision

Logs:
  proxy | 2021/12/15 05:41:39 [253] GET https://git.apache.org:443/thrift.git/info/refs?service=git-upload-pack
  proxy | 2021/12/15 05:42:11 [253] WARN: Cannot read TLS response from mitm'd server dial tcp <IP_ADDRESS>:443: connect: connection timed out
  proxy | 2021/12/15 05:42:11 [255] GET https://git.apache.org:443/thrift.git/HEAD
  proxy | 2021/12/15 05:42:43 [255] WARN: Cannot read TLS response from mitm'd server dial tcp <IP_ADDRESS>:443: connect: connection timed out
  proxy | 2021/12/15 05:42:43 [002] GET https://git.apache.org:443/thrift.git/info/refs?service=git-upload-pack
  proxy | 2021/12/15 05:43:14 [002] WARN: Cannot read TLS response from mitm'd server dial tcp <IP_ADDRESS>:443: connect: connection timed out
  proxy | 2021/12/15 05:43:14 [004] GET https://git.apache.org:443/thrift.git/HEAD
  proxy | 2021/12/15 05:43:46 [004] WARN: Cannot read TLS response from mitm'd server dial tcp <IP_ADDRESS>:443: connect: connection timed out
  proxy | 2021/12/15 05:43:46 [007] GET https://github.com:443/francoispqt/gojay/info/refs?service=git-upload-pack
  proxy | 2021/12/15 05:43:46 [007] * authenticating git server request (host: github.com)
  proxy | 2021/12/15 05:43:46 [007] 200 https://github.com:443/francoispqt/gojay/info/refs?service=git-upload-pack
updater | INFO <job_244779636> Handled error whilst updating github.com/tidwall/gjson: dependency_file_not_resolvable {:message=>"go<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>invalid version: unknown revision"}

Dependabot seems failing to connect to https://git.apache.org:443/thrift.git, but I can clone this repo locally.
Native package manager behavior

N/A
Images of the diff or a link to the PR, issue or logs

https://github.com/containerd/nerdctl/issues/529
🕹 Bonus points: Smallest manifest that reproduces the issue

N/A

Thanks for this report! From what I can tell Dependabot is being rate limited or blocked by the git.apache.org server. I tried the update in an environment with a different ip range and it was able to complete successfully.
There is a change in the works which would allow Dependabot to fetch dependencies from proxy.golang.org instead. That should eliminate the need to connect to git.apache.org in most cases.

Possibly related: https://github.com/mozilla/sops/issues/443

Thank you, it seems working now

https://github.com/containerd/nerdctl/pull/674
https://github.com/containerd/nerdctl/pull/675


00-running env var section should mention MoarVM's env vars.

Including a reference to 'moar --help' is fine, as they are all doc'd there. Should include some language about how this is (obviously) rakudo/MoarVM specific.

added to https://github.com/rakudo/rakudo/wiki/dev-env-vars, which is linked to from doc/Programs/00-running.pod6


Handle disconnects from AMQP broker

We should deal with loosing connection to Amqp broker within AmqpVerticle.

Implemented.


Snow effect in Christmas theme causes lag

Description
I am aware that the Christmas theme is a temporary feature. That being said, I think it's also fair to report that the snow feature in the latest version causes lag on my system. When I start the working day, I start a number of programs, not necessarily using them immediately. After a while, my computer becomes laggy. Turns out the Xorg process uses over 150% CPU, bringing the load of my system to between 4 and 5. This ends when I open a tab or when I close DBeaver.
I wouldn't mind if this gets closed immediately. Just wanted to put this out there to make a record of it.
DBeaver Version
Community Edition 23.3.0
Operating System
Manjaro Linux 23.1.1
Database and driver
No response
Steps to reproduce

Open DBeaver
Close all tabs to start the snow effect
Run top on the command line to list processes
Examine the CPU usage of the Xorg command

Additional context
No response

@yard-mschwartz you can turn the snow off here

@yard-mschwartz Hi, I have looked there is a significant increase in CPU consumption. Just to be sure can you give us additional info about your system: your CPU model and what graphic environment is used?

Hi @Destrolaric, is all the information you need in here?
$ inxi -v7azy
System:
  Kernel: 6.1.69-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1-x86_64
    root=UUID=a432be9b-15bd-475f-b169-cd9516f7a995 rw quiet apparmor=1
    security=apparmor udev.log_priority=3
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm
    v: 4.18.0 vt: 7 dm: LightDM v: 1.32.0 Distro: Manjaro Linux base: Arch Linux
[...]
Memory:
  System RAM: total: 32 GiB note: est. available: 31.04 GiB
    used: 11.58 GiB (37.3%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges required.
 This will be enough.


Android and delay option

Problem:
I am testing the library with both iOS and Android.
On iOS seems perfect; however on Android, when using the library with the "delay" option, it's very difficult to use.
There are two specific situations:

Try just to touch to start the sortable; with delay set I neraly always fail to start the sortable; without the delay options is perfect (could it be related to https://github.com/SortableJS/Sortable/issues/981 ?)
If you use an high delay (for example 500) after some simple repeated scrolls, you need to wait 2x delay to see the sortable work (it's like if when scrolling the delay launched from the touchstart triggered by the scroll is not cancelled)

Chrome: 72.0.3626.121
Android 8.1.0
JSBin/JSFiddle demonstrating the problem:
https://jsbin.com/nolazet

Delay option in Android is not working again!!
I want to need help, too.

@kimemin Was there a version in which it did work?

@owen-m1 I found well-working version, but old one.
use https://github.com/SortableJS/Sortable/tree/584f5e52d0ca13fc03b9a4325521352c304c4647.
this version works on both Android and iOS.

"Try just to touch to start the sortable; with delay set I neraly always fail to start the sortable; without the delay options is perfect (could it be related to #981 ?)" Exactly got the same problem in 1.8.4 with this options :
const sortableOptions = {
    forceFallback: true,
    fallbackOnBody: true,
    animation: 150,
    delay: 100,
    filter: '.static',
    ghostClass: 'ghost',
    fallbackClass: 'chosen',
    chosenClass: 'chosen',
    scrollSpeed: 20,
  };

@KingRial @kimemin @clemishow Please try master branch, and let me know if it solved the problem on your end.

Working for me, thank you very much for your reactivity 👏

Working for me, thank you very much for your reactivity 👏

@owen-m1 I found well-working version, but old one.
I used https://github.com/SortableJS/Sortable/tree/584f5e52d0ca13fc03b9a4325521352c304c4647.
this version works on both Android and iOS.

very good!!!

I was able to fix this issue by setting the draggable option. draggable: ".item"


[Bug Report] i use v-for in el-table-column，when columnsArray changed, the table can't render right

Element UI version
2.15.6
OS/Browsers version
mac
Vue version
2.6.14
Reproduction Link
https://codepen.io/a602120/pen/mdMmKNo?editors=1010
Steps to reproduce
when i changed my columns in settimeout, table not render
What is Expected?
table render wright when columns change
What is actually happening?
table not work when when i changed my columns in settimeout


add label planned for ci to check issue inactive

Codecov Report
Base: 79.60% // Head: 79.63% // Increases project coverage by +0.02% :tada:

Coverage data is based on head (4bbf107) compared to base (28b8efe).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2408      +/-   ##
==========================================
+ Coverage   79.60%   79.63%   +0.02%
==========================================
  Files         598      595       -3
  Lines       49682    49343     -339
==========================================
- Hits        39551    39294     -257
+ Misses       8132     8066      -66
+ Partials     1999     1983      -16

Flag
Coverage Δ

go-1.15-386
?

go-1.15-amd64
?

go-1.16-386
?

go-1.16-amd64
79.63% <ø> (-0.04%)
:arrow_down:

go-1.17-386
?

go-1.17-amd64
?

go-1.18-386
?

go-1.18-amd64
?

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

Impacted Files
Coverage Δ

os/gcron/gcron_schedule_fix.go
81.81% <0.00%> (-9.10%)
:arrow_down:

net/gtcp/gtcp_pool.go
68.88% <0.00%> (-6.67%)
:arrow_down:

os/gfsnotify/gfsnotify_watcher_loop.go
78.15% <0.00%> (-5.05%)
:arrow_down:

frame/gins/gins_database.go
53.78% <0.00%> (-3.37%)
:arrow_down:

os/glog/glog_logger_rotate.go
61.99% <0.00%> (-1.36%)
:arrow_down:

container/gmap/gmap_hash_str_any_map.go
97.00% <0.00%> (-1.00%)
:arrow_down:

contrib/config/kubecm/kubecm.go

contrib/config/kubecm/kubecm_kube.go

contrib/drivers/oracle/oracle.go

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.


[Service Bus] Browser support requires mocks/stubs configured

Running the Service Bus Client on the browser with @azure/service-bus (v1.1.0) requires that mocks and stubs are configured in the webpack config like this:
node: {
  dns: 'mock',
  fs: 'empty',
  net: 'empty',
  tls: 'empty',
},

Otherwise you'll get errors like these:
<EMAIL_ADDRESS>Module not found: Can't resolve 'dns' in '<snip>\node_modules\@azure\amqp-common\dist-esm\src'

This is set up by default on the create-react-app template, but may not be default on other templates (as in our case).
Is it possible to remove these dependencies from the SDK when running in a browser context? Since these will never be used by our code (and aren't used by any of our other dependencies), it would be good not to have to needlessly pollute the namespace. It also potentially produces some uncertainty about the behavior of the SDK, as it becomes unclear what is properly handled/supported in a browser context.

Thanks for bringing this up @trylle! I spent some time investigating and here is what I found:
tl;dr The problem seems to be that ServiceBus and rhea ES Modules are not "Browser friendly" (opposite to our UMD bundle generated by Rollup).
Details:
There seem to be 2 main problems:

Amqp-common.retry depends on dns which is not supported in Browsers. While this is handled by Rollup when generating UMD bundle by shimming and leveraging dead code elimination, this browser incompatibility is not handled in the compiled ES Modules (dist_esm/*).

Similar to (1), rhea depends on fs, tls and net without providing and alternative for Browsers. This is also handled when bundling ServiceBus UMD in Rollup by shimming the dependencies, but compiled ES Modules are not browser friendly.

Possible Workarounds:
a) The work around proposed by @trylle  to shim, the unsupported dependencies
b) If we remove the "module": "dist-esm/src/index.js" field from sdk/servicebus/service-bus/package.json (or setup an override in "browser" field), Webpack and other bundlers will pickup the UMD bundle generated by Rollup which has been "normalized" for browser compatibility, so no error would be thrown.
Long Term Fix
To fix (1) we can create 2 separate versions of retry (retry.node.ts and retry.browser.ts) exporting each retry in index.node.ts and index.browser.ts respectively. There is already a "Browser Field" override in package.json for index.browser.ts
To fix (2) we'll need to provide a Browser alternative for the dependencies taken on rhea/rhea-promise (in sdk/servicebus/service-bus). Or work in rhea itself to make it Browser compatible.
I think workaround a) would be preferable to b) since we'll keep using ES Modules and bundlers would be still bale to Treeshake. Option b) may cause larger bundle size by bringing in unneeded stuff. We should update the README for Webpack users
We should eventually go with the longer term fixes to make sure the SDK is fully compatible with Browser and no extra work is needed from consumers to work with it.
@ramya-rao-a, @bterlson - Do you have any thoughts?

I think retry.node.ts and retry.browser.ts is reasonable. Another approach, if it's just dns, is to create our own shim module where e.g. dns.node.ts exports dns, and dns.browser.ts exports a shim. That may save some code duplication.
Unfortunately rhea itself isn't super well suited for browser - it depends on browserify, and doesn't expose the necessary metadata other bundlers need to do a good job. Would love to contribute some fixes upstream for that, it might be as simple as adding a package.json browser field for them.

We've made updates to rhea to better support bundling, and updated core-amqp to work with bundling by using the filename.ts and filename.browser.ts pattern to avoid importing node built-ins in unified code.
We should be able to backport what we did in core-amqp to amqp-common to fix this issue in service-bus v1. Alternatively we could add a "dns": "empty" key/value in the package.json browser field for amqp-common.

Hi @trylle  I was wondering if you'd be willing to share with us your experience working with this library so far. We're committed to improving our SDK, GitHub support process, and documentation. Your feedback is extremely helpful to us, so please let us know if we can hop on a quick call to discuss it. Thanks!

Hi,
Our team has a Teams meeting with Elena Raikhman at 09-10:00 UTC today.
It looks like you're included in that meeting, so I guess we'll see you
then.
Regards,
Frits Talbot.
On 17.03.2020 23:52, lilyjma wrote:

Hi @trylle https://github.com/trylle I was wondering if you'd be
willing to share with us your experience working with this library so
far. We're committed to improving our SDK, GitHub support process, and
documentation. Your feedback is extremely helpful to us, so please let
us know if we can hop on a quick call to discuss it. Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-sdk-for-js/issues/5364#issuecomment-600338839,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAOTXKMYVAHGD7JP6LRA4C3RH75KLANCNFSM4I5ALFXA.

Sorry, that's 09:00-10:00 (UTC-08:00) Pacific Time (US & Canada).
Regards,
Frits Talbot.
On 19.03.2020 08:40, Frits Talbot wrote:

Hi,
Our team has a Teams meeting with Elena Raikhman at 09-10:00 UTC
today. It looks like you're included in that meeting, so I guess we'll
see you then.
Regards,
Frits Talbot.
On 17.03.2020 23:52, lilyjma wrote:

Hi @trylle https://github.com/trylle I was wondering if you'd be
willing to share with us your experience working with this library so
far. We're committed to improving our SDK, GitHub support process,
and documentation. Your feedback is extremely helpful to us, so
please let us know if we can hop on a quick call to discuss it. Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-sdk-for-js/issues/5364#issuecomment-600338839,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAOTXKMYVAHGD7JP6LRA4C3RH75KLANCNFSM4I5ALFXA.

#7323 fixes the issue in amqp-common.
This issue is not present in<EMAIL_ADDRESS>Follow the instructions at bundling-azure-sdk-libraries to use the library in the browsers. In case you're using webpack with the instructions provided in the link, no additional config is required.


Trigger refactored

improve logging for existing trigger management logic
remove unnecessary and unused code in existing trigger management logic
move flow SLA trigger from web server to executor so that SLA checking is performed on executor side but keep schedule trigger as it is in web server

splitting this change into multiple PRs. closing this one.


option to remove effects off blade of olympus

option to remove effects off blade of olympus

Effects removed & these are now on the Shawesome blade instead


Error when loading image record with Chinese names

I always came across encoding error when loading image record with Chinese names.
But I solved this by changing line 91 in base.py
from
return ctypes.c_char_p(string.encode('utf-8'))

to
return ctypes.c_char_p(string)

Usually you don't want any non ascii character in your path specially if you are using windows. Dealing with this across platforms and python version is a nightmare so I don't think we are going to support it.