Update faqimporting-pst-files-to-office-365.yml

@markjjo - i have added a FAQ (know issue) since the fix is going to take time.

@Durga-SC I'm closing this PR and will make the changes in the private repo and then publish. I will also add same FAQ to network upload section.


Installation issue

Hi,
I'm trying for the first time soajs and cannot get very far as the installation doesn't seems to be working.
I hope this is the right project to open the issue.
I get bunch of error but the script continue and give me a message at the end that the container are started like everything looks fine?
My docker installation works fine, I'm able to do  a "docker run -it ubuntu bash" without problem.

Cannot connect to the Docker daemon. Is the docker daemon running on this host?
1- Cleaning previous docker containers ...
Cannot connect to the Docker daemon. Is the docker daemon running on this host?
docker: "stop" requires a minimum of 1 argument.
See 'docker stop --help'.
Usage:	docker stop [OPTIONS] CONTAINER [CONTAINER...]
Stop a running container.
Sending SIGTERM and then SIGKILL after a grace period
Cannot connect to the Docker daemon. Is the docker daemon running on this host?
docker: "rm" requires a minimum of 1 argument.
See 'docker rm --help'.
Usage:	docker rm [OPTIONS] CONTAINER [CONTAINER...]
Remove one or more containers

2- Starging Mongo Container "soajsData" ...
docker: Cannot connect to the Docker daemon. Is the docker daemon running on this host?.
See 'docker run --help'.

Cannot connect to the Docker daemon. Is the docker daemon running on this host?
Mongo ip is:
3- Starging Mongo Container "soajsDataDev" ...
docker: Cannot connect to the Docker daemon. Is the docker daemon running on this host?.
See 'docker run --help'.

Cannot connect to the Docker daemon. Is the docker daemon running on this host?
Mongo Dev ip is:
4- Importing core provisioned data ...
About to run: mongo --host DOCKER /Users/slegaul1/node_modules/soajs.utilities/lib/../data/provision/data-tmp.js
/Users/slegaul1/node_modules/soajs.utilities/data/provision /Users/slegaul1/node_modules/soajs.utilities/lib
MongoDB shell version: 3.2.4
connecting to: DOCKER:27017/test
2016-04-17T10:24:58.079-0400 I NETWORK  [thread1] getaddrinfo("DOCKER") failed: nodename nor servname provided, or not known
2016-04-17T10:24:58.081-0400 E QUERY    [thread1] Error: couldn't initialize connection to host DOCKER, address is invalid :
connect@src/mongo/shell/mongo.js:226:14
@(connect):1:6
exception: connect failed
Done importing data:  1
/Users/slegaul1/node_modules/soajs.utilities/lib
5- Importing URAC data...
About to run: mongo --host <IP_ADDRESS> /Users/slegaul1/node_modules/soajs.utilities/lib/../data/urac/data-tmp.js
/Users/slegaul1/node_modules/soajs.utilities/data/urac /Users/slegaul1/node_modules/soajs.utilities/lib
MongoDB shell version: 3.2.4
connecting to: <IP_ADDRESS>:27017/test
2016-04-17T10:24:58.238-0400 W NETWORK  [thread1] Failed to connect to <IP_ADDRESS>:27017, reason: errno:61 Connection refused
2016-04-17T10:24:58.238-0400 E QUERY    [thread1] Error: couldn't connect to server <IP_ADDRESS>:27017, connection attempt failed :
connect@src/mongo/shell/mongo.js:226:14
@(connect):1:6
exception: connect failed
Done importing data:  1
/Users/slegaul1/node_modules/soajs.utilities/lib

6- Starting SERVICES ...

Starting Controller Container soajs.urac ...
docker: Cannot connect to the Docker daemon. Is the docker daemon running on this host?.
See 'docker run --help'.
Starting Controller Container soajs.dashboard ...
docker: Cannot connect to the Docker daemon. Is the docker daemon running on this host?.
See 'docker run --help'.
Starting Controller Container soajs.prx ...
docker: Cannot connect to the Docker daemon. Is the docker daemon running on this host?.
See 'docker run --help'.
Starting Controller Container soajs.controller ...
docker: Cannot connect to the Docker daemon. Is the docker daemon running on this host?.
See 'docker run --help'.

Cannot connect to the Docker daemon. Is the docker daemon running on this host?
7- Starting NGINX Container "nginx" ...
docker: Cannot connect to the Docker daemon. Is the docker daemon running on this host?.
See 'docker run --help'.

8- Containers created and deployed:
Cannot connect to the Docker daemon. Is the docker daemon running on this host?

Cannot connect to the Docker daemon. Is the docker daemon running on this host?
Add the following to your /etc/hosts file:
dashboard-api.soajs.org
dashboard.soajs.org
Containers started, please login to the dashboard @ http://dashboard.soajs.org

Linux or Mac?  What OS version?
http://www.soajs.org/#/documentation/deployment/docker
What is your output of:  docker env

Thanks for the quick reply,
Mac OSX, El Capitan, 10.11.4
yes, eval "$(docker-machine env default)" fixed the issue.
But in the end there is still something wrong :(
➜  lib docker-machine ls
NAME                 ACTIVE   DRIVER       STATE     URL                         SWARM                         DOCKER    ERRORS
default              *        virtualbox   Running   tcp://<IP_ADDRESS>:2376                                 v1.11.0
soajs-dash           -        virtualbox   Error                                 soajs-swarm-master            Unknown   machine does not exist
soajs-dev            -        virtualbox   Error                                 soajs-swarm-master            Unknown   machine does not exist
soajs-swarm-master   -        virtualbox   Error                                 soajs-swarm-master (master)   Unknown   machine does not exist
soajs-v-keystore     -        virtualbox   Error                                                               Unknown   machine does not exist

Please send the result of this:
docker-machine ls
docker-machine env

If you do not need your virtualbox VMs:
docker-machine rm -f $(docker-machine ls -q)
or remove each soajs machine one by one:
docker-machine rm -f soajs-dash
After all machines soajs machines are removed run ./dockermachineDeploy.sh

Thanks working now.


Update cli.py

a simple solution to solve the issues #58 and #61.
perhaps the rest of options would be helpful to supply with type too...

@jezdez what's necessary to merge this PR? It seems to fix the problem with setting the poll interval value.


Images do not get dislayed when docs are built using yaydoc

Actual Behaviour
The images do not get displayed when building docs using yaydoc
Expected Behaviour
They should be displayed
Screenshots of the issue

Would you like to work on the issue?
Yes

@pri22296 please replace the current images with the ones here: http://imgur.com/a/QSIeo


Add tags to cirq.FrozenCircuit

Fixes https://github.com/quantumlib/Cirq/issues/6265
Things left to do as a follow up

Update circuit diagrams for cirq.FrozenCircuit to print the tags if they exist
Tags on FrozenCircuits are not automatically "imported" to the operation level when a frozen circuit get's wrapped in a circuit operation. I think we should leave this as it is for now and, if a need arises later, we can update the interop methods to propagate the tags.

This looks pretty awkward to use.  Since you usually get a FrozenCircuit from circuit.freeze(), should we add circuit.freeze(tags=tags) or a cirq.freeze_with_tags(tags)?


[SelectField] Overlapping text with floating label

Problem description
When using a floating label for the Select Field component the label does not float and overlaps with the first item in the dropdown on page load. I am seeing this on both my own app and your demo site, it does not exist on 0.15.2
Steps to reproduce

Go to http://www.material-ui.com/v0.15.3/#/components/select-field
Scroll down to Floating label example, notice overlapping text and lack of floating label
Selecting an item from any of the Select Field dropdowns causes all floating labels to behave correctly

Versions

Material-UI: 0.15.3
React: 15.3.0
Browser: Chrome 52.0.2743.82 (64-bit), Safari 9.1.2
OS: OS X 10.11.6

Is this not the same issue?
https://github.com/callemall/material-ui/issues/4891

Oh yes it, I didn't see that one when searching the issues.


Style: Harmonize header includes in platform ports

This applies our existing style guide, and adds a new rule to that style guide for modular components such as platform ports and modules:

Includes from the platform port or module should be included with relative paths (relative to the root folder of the modular component, e.g. platform/linuxbsd/), in their own section before Godot's "core" includes.

I'll add this to the style guide if/when we reach consensus.
This helps differentiate between "local" code and the rest of the engine which can be treated as a library. The order of includes therefore flows from the most local (header.h for header.cpp) to the most external (<string.h>, <windows.h>, etc.). It's not perfect for platform code as we also have code in drivers/ which has a similar kind of "locality" to headers in the platform folder, but rules can never be perfect ;)
This also helps (at least theoretically) with keeping module components modular. If we want to rename a platform or module folder, or more importantly, if people need to maintain a thirdparty platform or module, keeping the component's own files with relative includes help with the plug 'n play mechanism for platform/ and modules/.

Marked for cherry-picking (if approved) to keep the codebases in sync. Should be relatively easy to cherry-pick / solve merge conflicts by redoing the changes on affected files.


python3Packages.sentry-sdk: 1.4.3 -> 1.5.0

Motivation for this change
Update to latest upstream release 1.5.0
Change log: https://github.com/getsentry/sentry-python/releases/tag/1.5.0
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 146466 run on x86_64-linux 1

3 packages failed to build:

gns3-server
home-assistant
octoprint

10 packages built:

alerta-server
cura
gns3-gui
moodle-dl
moz-phab
python38Packages.django-rq
python38Packages.sentry-sdk
python39Packages.django-rq
python39Packages.sentry-sdk
tribler

I am seeing some test failures in test_rq.py, such as:
=================================== FAILURES ===================================
__________________________________ test_basic __________________________________
tests/integrations/rq/test_rq.py:50: in test_basic
    queue.enqueue(crashing_job, foo=42)
/nix/store/2dx7v83fi90jkw8xkfvwjn6p47mjdc9s-python3.8-rq-1.10.1/lib/python3.8/site-packages/rq/queue.py:508: in enqueue
    return self.enqueue_call(
/nix/store/2dx7v83fi90jkw8xkfvwjn6p47mjdc9s-python3.8-rq-1.10.1/lib/python3.8/site-packages/rq/queue.py:406: in enqueue_call
    return self.enqueue_job(job, pipeline=pipeline, at_front=at_front)
sentry_sdk/integrations/rq.py:107: in sentry_patched_enqueue_job
    return old_enqueue_job(self, job, **kwargs)
/nix/store/2dx7v83fi90jkw8xkfvwjn6p47mjdc9s-python3.8-rq-1.10.1/lib/python3.8/site-packages/rq/queue.py:566: in enqueue_job
    job.save(pipeline=pipe)
/nix/store/2dx7v83fi90jkw8xkfvwjn6p47mjdc9s-python3.8-rq-1.10.1/lib/python3.8/site-packages/rq/job.py:663: in save
    if self.get_redis_server_version() >= (4, 0, 0):
/nix/store/dgmp76d54xxb3bka1fph17yz7n8rfkai-python3-3.8.12/lib/python3.8/distutils/version.py:70: in __ge__
    c = self._cmp(other)
/nix/store/dgmp76d54xxb3bka1fph17yz7n8rfkai-python3-3.8.12/lib/python3.8/distutils/version.py:170: in _cmp
    if self.version != other.version:
E   AttributeError: 'tuple' object has no attribute 'version'

Reported upstream at https://github.com/getsentry/sentry-python/issues/1274

Let's disable the rq test for now: https://github.com/NixOS/nixpkgs/pull/150020


Delete what to expect on teacher training blog post

Trello card
https://trello.com/c/dEDUTjtR/2186-delete-and-redirect-blog-post-on-what-to-expect-on-your-teacher-training
Context
We want to delete this blog post https://getintoteaching.education.gov.uk/blog/what-to-expect-on-your-teacher-training.
We have an information page on what to expect in teacher training https://getintoteaching.education.gov.uk/train-to-be-a-teacher/initial-teacher-training so we can add any additional information that’s useful from the blog post to this page.
Changes proposed in this pull request

Add any relevant content to the information page
Delete blog post
Set up blog post redirect

Guidance to review

@gemmadallmandfe I'm not sure most of the info in the blog post works for the page as it's specific to PGCE so I don't know whether it may confuse people. I've added in a section about holidays but happy to take it out for the reason I just said if you think it may confuse people.

@MaxineCl There are further links to the blog post on the following pages, which is why you are getting build failures:

/train-to-be-a-teacher/what-is-a-pgce
/funding-and-support/salaried-teacher-training
/funding-and-support/scholarships-and-bursaries

@martyn-w Deleting this blog post is causing one of the spec tests to fail as we now only have 3 blogs under /blog/tag/advisers rather than 4
Could you update the spec test please? Thanks!

I've updated the blog spec test to reduce the count from 4 to 3.
@MaxineCl there are a couple of other failing tests which require fixing:

invalid path /blog/what-to-expect-on-your-teacher-training on page /funding-and-support/salaried-teacher-training
invalid redirect: bad URI(is not URI?): "http://www.example.com/ /train-to-be-a-teacher/initial-teacher-training?abc=def&ghi=jkl"


kubernetes_state check fails to initialize

Output of the info page
====================
Collector (v 5.27.0)
====================

  Status date: 2018-09-19 23:03:42 (12s ago)
  Pid: 26
  Platform: Linux-4.4.111+-x86_64-with-debian-9.5
  Python Version: 2.7.15, 64bit
  Logs: <stderr>, /var/log/datadog/collector.log

  Clocks
  ======

    NTP offset: -0.0003 s
    System UTC time: 2018-09-19 23:03:54.418839

  Paths
  =====

    conf.d: /etc/dd-agent/conf.d
    checks.d: Not found

  Hostnames
  =========

    socket-hostname: dd-agent-xkqrd
    hostname: gke-pre-prd-cluster-pre-prd-pool-1-8--1350f1d9-4n17.c.docrepository-160410.internal
    socket-fqdn: dd-agent-xkqrd

  Checks
  ======

    kubernetes_state (3.0.0)
    ------------------------
      - initialize check class [ERROR]: AttributeError("'KubernetesState' object has no attribute '_deprecations'",)

  Emitters
  ========

    - http_emitter [OK]

====================
Dogstatsd (v 5.27.0)
====================

  Status date: 2018-09-19 23:03:53 (2s ago)
  Pid: 23
  Platform: Linux-4.4.111+-x86_64-with-debian-9.5
  Python Version: 2.7.15, 64bit
  Logs: <stderr>, /var/log/datadog/dogstatsd.log

  Flush count: 506
  Packet Count: 3775
  Packets per second: 2.3
  Metric count: 23
  Event count: 0
  Service check count: 2

====================
Forwarder (v 5.27.0)
====================

  Status date: 2018-09-19 23:03:53 (4s ago)
  Pid: 22
  Platform: Linux-4.4.111+-x86_64-with-debian-9.5
  Python Version: 2.7.15, 64bit
  Logs: <stderr>, /var/log/datadog/forwarder.log

  Queue Size: 1791 bytes
  Queue Length: 1
  Flush Count: 1631
  Transactions received: 1530
  Transactions flushed: 1529
  Transactions rejected: 0
  API Key Status: API Key is valid

======================
Trace Agent (v 5.27.0)
======================

  Pid: 21
  Uptime: 5131 seconds
  Mem alloc: 1148472 bytes

  Hostname: gke-pre-prd-cluster-pre-prd-pool-1-8--1350f1d9-4n17.c.docrepository-160410.internal
  Receiver: <IP_ADDRESS>:8126
  API Endpoint: https://trace.agent.datadoghq.com

  --- Receiver stats (1 min) ---

  --- Writer stats (1 min) ---

  Traces: 0 payloads, 0 traces, 0 bytes
  Stats: 0 payloads, 0 stats buckets, 0 bytes
  Services: 0 payloads, 0 services, 0 bytes

Additional environment details (Operating System, Cloud provider, etc):
Linux / k8s (Google GKE) / COS
Steps to reproduce the issue:

Create a kubernetes_state check (with auto discovery)

Describe the results you received:
The check can not be initialized since it fails in the constructor (starting since version 3.0.0):
2018-09-19 22:55:29,015 | ERROR | dd.collector | config(config.py:1076) | Unable to initialize check kubernetes_state
Traceback (most recent call last):
  File "/opt/datadog-agent/agent/config.py", line 1060, in _initialize_check
    agentConfig=agentConfig, instances=instances)
  File "/opt/datadog-agent/embedded/lib/python2.7/site-packages/datadog_checks/kubernetes_state/kubernetes_state.py", line 47, in __init__
    "DEPRECATION NOTICE: pod phase service checks are deprecated. Please set "
AttributeError: 'KubernetesState' object has no attribute '_deprecations'

Describe the results you expected:
THe check not throwing an error
Additional information you deem important (e.g. issue happens only occasionally):

Is there a known workaround for this? I'm experiencing the same issue.

Fixed in 5.27.2, see https://github.com/DataDog/integrations-core/pull/2317


Bump httpoison to 0.9.0 to remove unsafe var compiler warnings

httpoison 0.8.0 has some unsafe var compiler warnings in Elixir 1.3, bumping it to 0.9.0 removes these warnings when using sendgrid_elixir.

Thanks!


Rectify typographical inaccuracies

This PR addresses several typographical errors across various files in the project. The changes improve readability and maintain the professional standard of the documentation and code comments.
Justification
Typographical errors, while minor, can detract from the overall quality of the project. Correcting these errors ensures clarity and professionalism, making the project more accessible and understandable for current and future contributors.
Hope it helps.

None of these are actually errors. Please do not open PRs for minor wording changes.


Fido-related bug when adding new meeting

When adding a third fido style network, the prenode hangs hard (cannot even be terminated in the OS) when I try to create a new meeting for that network.
A work-around is to create the new meeting with valid settings except which domain the meeting is part of. I simply choose another domain (i.e Fidonet) and then, when the meeting is created, change it to the correct domain.

Offline discussion has clarified the problem to that at least in NiKomCon it doesn't really hang. It just doesn't accept the correct input. GetNumber() was called with the wrong parameters. This is now fixed.
It seems to work in NiKomSer as well now. Why it was hanging hard is still unknown.


An adapter for Hydra

I've built a basic adapter for Hydra here:
https://github.com/pmackay/oat_hydra
Any feedback much appreciated. Also is it best to keep this as a separate gem and release it, or integrate into Oat?

Hey, apologies for not responding earlier.
I think it's awesome that you added Hydra support as a separate gem, thank you!
Are you still using it? I'll be happy to add a link to Oat's README.

I am using it for a prototype API. Would be great if could add a link in the README, others might find it useful. It needs more work before it could be considered fully functional.


botocore requires python-dateutil lower than 2.8.1

pip install flytekit
...
ERROR: botocore 1.13.41 has requirement python-dateutil<2.8.1,>=2.1; python_version >= "2.7", but you'll have python-dateutil 2.8.1 which is incompatible.
...

This usually has no issue but recently we started to get error like:
Traceback (most recent call last):
  File "/root/.venv/lib/python3.6/site-packages/pkg_resources/__init__.py", line 574, in _build_master
    ws.require(__requires__)
  File "/root/.venv/lib/python3.6/site-packages/pkg_resources/__init__.py", line 892, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/root/.venv/lib/python3.6/site-packages/pkg_resources/__init__.py", line 783, in resolve
    raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (python-dateutil 2.8.1 (/root/.venv/lib/python3.6/site-packages), Requirement.parse('python-dateutil<2.8.1,>=2.1; python_version >= "2.7"'), {'botocore'})

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/root/.venv/bin/flyte-cli", line 6, in <module>
    from pkg_resources import load_entry_point
  File "/root/.venv/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3088, in <module>
    @_call_aside
  File "/root/.venv/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3072, in _call_aside
    f(*args, **kwargs)
  File "/root/.venv/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3101, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/root/.venv/lib/python3.6/site-packages/pkg_resources/__init__.py", line 576, in _build_master
    return cls._build_from_requirements(__requires__)
  File "/root/.venv/lib/python3.6/site-packages/pkg_resources/__init__.py", line 589, in _build_from_requirements
    dists = ws.resolve(reqs, Environment())
  File "/root/.venv/lib/python3.6/site-packages/pkg_resources/__init__.py", line 783, in resolve
    raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (python-dateutil 2.8.1 (/root/.venv/lib/python3.6/site-packages), Requirement.parse('python-dateutil<2.8.1,>=2.1; python_version >= "2.7"'), {'botocore'})

Which part of the code uses boto?

This is the corresponding botocore issue - https://github.com/boto/botocore/issues/1872
I'm okay with this change for now, but while we're pinning I think we should just pin to 2.8.0 since it's meant to be a short-term patch anyways.  Once the underlying issue is fixed, we should remove it.
Thoughts @matthewphsmith ?

I'd worry about pinning since it might be over-specific and cause downstream contextual version conflicts.


[WIP] Proofreading of zh-CN part

[x] Have you followed the contributing guidelines?
[x] Have you explained what your changes do, and why they add value to the Guides?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

It just a simply check of most typing mistake, most syntax mistake and a bit translate mistake.
This PR will be the first, I will proofread more the once time.

Looks like tests are failing. Looks like master is also failing, but with different errors https://travis-ci.org/github/opensource.guide/builds/351805696

@WordlessEcho Thanks for the PR! These errors will need to be addressed:

_site/zh-cn/best-practices/index.html

linking to ../building-community/#share-ownership-of-your-project, but share-ownership-of-your-project does not exist (line 315)
一起管理项目
linking to internal hash #Take%20care%20of%20yourself%20first! that does not exist (line 138)
首先照顾好自己

_site/zh-cn/leadership-and-governance/index.html

linking to ../building-community/#share-ownership-of-your-project, but share-ownership-of-your-project does not exist (line 219)
共享所有权

_articles/zh-cn/best-practices.md

249:6-249:7  warning  Expected a straight apostrophe: ', not ’  apostrophe  retext-quotes

Another error I'm afraid:

_site/zh-cn/best-practices/index.html

linking to internal hash #Take%20care%20of%20yourself%20first! that does not exist (line 138)
首先照顾好自己

@WordlessEcho Still failing I'm afraid. You can test this locally by running ./script/test

@MikeMcQuaid I know where the problem is now, thanks for you keep following. : )

@WordlessEcho I'd recommend running the tests locally so you know if the issue is fixed before you push more commits. Also you can compare to the other translations or existing code.

OK, I will do it locally.


[BUG] - incorrect year in date picker in fa-IR

NextUI Version
2.4.6
Describe the bug
reported from

https://github.com/nextui-org/nextui/issues/2842#issuecomment-2266755078
https://github.com/nextui-org/nextui/issues/2842#issuecomment-2266755078

Your Example Website or App
No response
Steps to Reproduce the Bug or Issue

change to locale  fa-IR
the year range is not correct

Expected behavior
The year should be correct with the locale  fa-IR
Screenshots or Videos
No response
Operating System Version
macOS
Browser
Chrome

Hi again
After updating to newer version after @wingkwong merge request. I still have year problem in date picker.
May we can solve it together?
@wingkwong

@MhEsn We haven't released yet. It's likely done tmr.

@wingkwong Thanks then.

Hi again,
I'm still waiting for the release. When do you think it will releases?
thanks
@wingkwong

it's out already. please upgrade to 2.4.8.


[FEATURE] ZTE ZXHN F680 / RT-GM-5

Hello, I would like the RT-GM-5 (possibly the same as ZTE ZXHN F680) router to be supported.
Tried using serial number both with --serial and --key. Getting the following errors:

without using key or serial: Malformed decrypted payload, likely you use the wrong key!
using serial as a key: Hint: Payload type is 4, might need a serial number instead of a key.
using serial with --serial: Malformed decrypted payload, likely you use the wrong key!

If it helps, I can send a config.bin file and serial number for test to one of dev e-mails (to not share possible private info here).

Good time of day.
I join the request above. I have RT-GM-5 and am ready to provide all possible assistance
Thanks.

Hello,  I would also like to see support for this device (zte RT-GM-5   he is  ZTE ZXHN F680).
I can also share  config.bin    with  password user admin.
<EMAIL_ADDRESS>

Hello my friends I need your support to decrypt the backup  of ZTE ZXHN F680
I can also share config.bin
<EMAIL_ADDRESS>

Here's RT-GM-5
Software Version  F680_V6.0.10P3T4_UPGRADE_BOOTLDR.zip
CspDBInitPdtInterface looks like this
`CspDBInitPdtInterface(undefined4 *param_1,undefined4 param_2,undefined4 param_3,undefined4 param_4)
{
dbAddCfgItem(0xffff,0,"/userconfig/cfg/db_user_cfg.xml",param_4,param_4);
dbAddCfgItem(0xffff,1,"/userconfig/cfg/db_default_cfg.xml");
dbAddCfgItem(0xffff,2,"/userconfig/cfg/db_backup_cfg.xml");
param_1[2] = 1;
*param_1 = 0;
param_1[3] = CspDBSetBackupItem;
param_1[7] = dbPdtTransferCfg;
pdtGetAesUserEncry.isra.0((int)param_1 + 0x159);
strncpy((char *)((int)param_1 + 0x17a),"f680",0x20);
return 0;
}
`


Plugin silently gives wrong advices when different versions of a dependency are used in different source sets of the same project

Build scan link

https://scans.gradle.com/s/lyx5rjpyqfnhu/console-log
Plugin version

1.21.0
Gradle version

7.6.1
reason output for bugs relating to incorrect advice

https://scans.gradle.com/s/lyx5rjpyqfnhu/console-log?page=1#L304
Describe the bug

If there are different versions of a dependencies for different source sets (in the example junit-jupiter-api:5.9.0 vs  junit-jupiter-api:5.9.1) only one of the Jars is analyzed. In the example 5.9.0 is used. Then this does not match in cases where 5.9.1 is in the dependency graph and the plugin assumes "an empty Jar" (for 5.9.1). As result, the plugin gives the wrong advice to remove the dependencies to junit-jupiter-api in such cases. In the example, it advices to remove testImplementation although src/test/java is using it.
https://scans.gradle.com/s/lyx5rjpyqfnhu/dependencies?dependencies=junit-jupiter-api&expandAll&projectFilter=WyI6YXBwIl0
To Reproduce
I am not yet sure if this happens every time in such a situation or if there are some special circumstances causing this. I'll provide a reproducer later.
Expected behavior
I don't think this necessarily needs to be supported in all cases. Having consistent versioning in one build is what is desired in most cases. It's just easily missed. IMO, it would also be fine to fail in some form if the plugin can detect such a case it cannot handle.
Just the wrong advice you get right now is confusing.

I suspect this might be fixed in 1.24.0. I found a bug relating to version skew with external dependencies, in a different context than this, and fixed it. Can you test?

I can confirm that the problem is gone with 1.24.0 in the project setup where I faced this

Sorry I was mistaken. Problem still exists. New scan with 1.24.0:
https://scans.gradle.com/s/dvnrv3xf5xehy/console-log?page=1#L303

@jjohannes here's a reproducer, I think: https://github.com/autonomousapps/dependency-analysis-gradle-plugin/pull/1191

Thank's for fixing this!


About neg_metrics -> p_neg_weight

Hi @strongwolf,
I have one more question about the code. Looks like in this line you use non one-to-one correspondence between gt_labels and num_classes. So in case if ambiguous anchor some values in neg_metrics will be simply ignored. And what is more strange the ignored value depends on the order of labels in gt_labels. Like here the value 2 is ignored in the resulting tensor:
>>> t = torch.tensor([[1]])
>>> t[[0, 0], [0, 0]] = torch.tensor([2, 3])
>>> t
tensor([[3]])

Do I understand it correctly?

Yes, your understanding is correct.  This phenomenon only occurs when an anchor is inside two gt boxes that have the same category label. I have tried to use min() or max() to deal with this situation and found there is no much difference from the original implementation. The reason I guess is that the number of such ambiguous anchors is very small compared with the total number of anchors.

I see, thank you.


Unable to run on up-to-date Mac

On up-to-date OSX it doesn't seem possible to run pymagicc--- is this correct?
The problem is that 32-bit applications (including wine) are no longer supported (see: https://superuser.com/questions/1513877/bad-cpu-type-in-executable-wine-macos-catalina).
If this is the case, could you update the README to make this apparent up front? Otherwise, are there any workarounds?

Does it work with the MAGICC7 binary available here? https://magicc.org/download/magicc7
See further down in the README on how to use a different binary.

That does seem to be the correct workaround. We weren't able to get it to work, though for seemingly unrelated reasons (libgfortran wasn't linked properly and we gave up). I would request updating the README for Macs since using the provided binary will be necessary for all Macs going forward.

Having the same issue, both libgfortran is not linked and struggling with setting the environment variable to use 'magicc-darwin-arm64' in MAGICC7. An updated readme would be really helpful, thank you!

@Aq0amancer and @grahamas, not sure if you're still experiencing the issue with libgfortran, but there's the steps I recently took to get it to work on macOS Sequoia:
# ensure gcc is installed as that provides libgfortran
brew install gcc

# find path to libgfortran.5.dylib
find /opt/homebrew -name "libgfortran*.dylib"

# use environment variable to specify the path to libgfortran
# in my case, my path looked like the following
export DYLD_LIBRARY_PATH=/opt/homebrew/Cellar/gcc/14.2.0_1/lib/gcc/current:$DYLD_LIBRARY_PATH

# now you should be able to use the magicc7 executable
./magicc-darwin-arm64

For using pymagicc, you'll also need the MAGICC_EXECUTABLE_7 env var as mentioned at the bottom of the README. I have the following cell in my python notebook before using pymagicc:
%env DYLD_LIBRARY_PATH=/opt/homebrew/Cellar/gcc/14.2.0_1/lib/gcc/current:$DYLD_LIBRARY_PATH
%env MAGICC_EXECUTABLE_7=/path/to/magicc/magicc-v7.5.3/bin/magicc-darwin-arm64


Logged more info when running local project.

Changes
Logged more info when running local project.

Testing
all Tests have been passed.

Docs
No Docs need to update.

Would you mind Closing this PR, and re-opening another PR based off the main branch? I can take another look when that‘s ready. Sorry for the confusion.

Sure.


refactor: Move to pub(crate) fn in order to detect and remove unused functions

4d550ec5616dade518a131e9f856ab533cd775e6 moves from pub fn to pub(crate) fn where possible
c46aa7d4e8f1a03e0bd6fdc855a888cca46d05ad removes unused functions

Heh. A couple of these I was using in magic downstream. I add pixi as a crate dep and call into some of these pub functions that are not pub(crate). Think most I can work around. A few I’ll need to be pub again in our downstream patches (like clap execute commands). Hoping to open source that project soon so it’s easy to see how embed pixi

@zbowling let us know when we can make things easier for you. And yes, open-sourcing magic would help here

Yeah I'm hoping to get through final approvals to open source in the next month. Some of our changes to Pixi are in a public fork, though, right now. I'd like to get those upstreamed where it makes sense. It's some small stuff mostly (in a few cases making a few APIs pub. It's funny because I'm using Pixi as a library, but it's building toward being a binary, so it doesn't have a well-defined API surface like it does a CLI surface. There was no contract there, so I took on that burden knownly. :-P
Magic also uses clap as a CLI driver, but to make things easy, I just reference clap structs in pixi and call execute like it does, too. That way I can bring about 80% of the high-level packaging CLI commands into magic and then add in all our bespoke stuff around mojo build system integration, our vscode extension hooks (so we can sniff the current project and get access ot the right mojo LSP), support our cloud packaging/deploying system (wrapping things up in docker), and local serving commands (just invoking tools when the max package is added to the current project in the max package). We also change the default implicit channels to include our 3rd party conda repo. And to avoid breaking people, we also change the pixi.lock to magic.lock and the venv directory from .pixi to .magic so if you are using magic and pixi side by side and we are lagging a version or two behind it doesn't break anything.
That's why we end up dipping into some of the project and high-level CLI APIs in Pixi a bit.
Goal is also to make magic optional so you can use pixi, conda, or mamba if you want, but magic just drives specific tools in the MAX package in a more convenient way at a high level when the project includes a MAX deps. It also gives us some telemetry of what our users are using the most, like which other frameworks they are using with MAX and mojo (like pytorch, onnx, tesnorflow, cuda, etc)


Rewrite input group component

I've rewritten the input group HTML (slightly) and CSS (mostly). This was primarily motivated by a need to support our HTML5 form validation and an urge to improve the readability of this component's CSS. Prior to this PR, adding form validation feedback and styles wasn't possible without visually breaking the component.
This is a breaking change from Beta 2.
Changes

Input group addons are now specific to their placement relative to an input. We've dropped .input-group-addon and .input-group-btn for two new classes, .input-group-prepend and .input-group-append. You must explicitly use an append or a prepend now, simplifying much of our CSS.

Multiple inputs are now supported, though I'm unsure on the accessibility angle here (/cc @patrickhlauke). I'm also unsure how this affects form validation. Fixes #23454.

Added support for form validation feedback in input groups. .input-group now has flex-wrap: wrap; on by default, allowing you to place validation feedback within the .input-group and style it based on the input's overall state. This isn't applicable to file inputs though.

Buttons now must all be of the same element type for :last-of-type to work. We use :last-of-type to avoid border-radius issues from HTML5 form validation and dropdowns being the true :last-child elements.

We no longer allow .form-control-sm or .form-control-lg on the input group elements. Instead, use .input-group-sm and .input-group-lg on the parent .input-group. Currently I'm unclear how to handle custom file and select sizing.

There are a few more direct children selectors. While we strive to avoid direct children selectors in Bootstrap 4 (e.g., .parent > .child), input groups require them to avoid cascading styles into additional components. For example, we have to target only the children buttons in a prepend or append otherwise we could affect dropdown menu content.

More consistently handles double borders, fixes #25005.

We've dropped ~50 lines of source Sass in the process.

I'll update this list as I work through todos listed below.
Todos

[x] Double check files and selects
[ ] Form validation example added to form docs (verifying multiple inputs? file inputs?)
[x] Update input groups everywhere else in docs and examples
[ ] Migration docs added w/ breaking changes detailed
[ ] Explore a custom input group button, styled to match the input with a white background and same color border
[ ] Do we try to do file input and custom select sizes?

Screenshots of the new component in action...
Custom file:

Custom select:

Segemented dropdowns:

Multiple inputs:

Validation styles:

What if I want two inputs and a text label between? E.g. timespan input group. Another case, I'm using multiple inputs in a wrapper div as a main element of input-group, surrounded by input-group-addons, will that work?

The component can't and shouldn't solve everything, @alecpl. I'd suggest something of a hybrid for that, mixing this and/or our utils for something custom.

How about add .btn-static class as a modifier for a button instead of .input-group-text? The SCSS will be more concise and modulable.

    @

  <input type="text" class="form-control" placeholder="Username" aria-label="Username" aria-describedby="basic-addon1">

SCSS: (This is an example, there are many code where similar things can be done.)
.btn + .btn,
.btn + .input-group-text,
.input-group-text + .input-group-text,
.input-group-text + .btn {
  margin-left: -$input-border-width;
}

to
.btn + .btn {
  margin-left: -$input-border-width;
}

How about add .btn-static class as a modifier for a button instead of .input-group-text? The SCSS will be more concise and modulable.

Doesn't feel right to extend the button class into something that isn't actually a button.

How do you add invalid feedback to the custom files?


Fix ENet max clients highest value.

Was 4096, while actually it's 4095. Fixed now in both docs and create_server check.
Fixes #34636

Thanks!


Desktop screen cannot be synchronized

The remote end has been confirmed to be able to connect normally, but when the two computers are connected, the screen is out of sync.

This is not an RDP Wrapper issue. Please, read about session shadow mode: https://woshub.com/rds-shadow-how-to-connect-to-a-user-session-in-windows-server-2012-r2/
If you need sync screen, please use Any-desk, Team-viewer, etc...


tcpSlaveAgentListener not found

Issues and Contributing
Docker commands that you execute
copy the command from README and run it on my laptop
docker run -d -v jenkins_home:/var/jenkins_home -p 8080:8080 -p 50000:50000 jenkins/jenkins:lts

Actual result
it runs fine, I can login, and also confirm I have enabled the jnlp port
So I can make sure the port 50000 is actived
$ curl localhost:50000
Jenkins-Agent-Protocols: JNLP4-connect, Ping
Jenkins-Version: 2.150.1
Jenkins-Session: a693c836
Client: <IP_ADDRESS>
Server: <IP_ADDRESS>
Remoting-Minimum-Version: 3.4

but when connect with  jnlp slave (container is jenkins/jnlp-slave), I got exact same error described in https://issues.jenkins-ci.org/browse/JENKINS-28499
tcpSlaveAgentListener not found

the test:
$ curl localhost:50000/tcpSlaveAgentListener/
Not Found

Expected outcome
register slaves to jenkins master
Have you tried a non-dockerized Jenkins and get the expected outcome?
Seems there are some issues reported with https://issues.jenkins-ci.org/browse/JENKINS-28499 for same issue
Output of docker version
$ docker version
Client: Docker Engine - Community
 Version:           18.09.0
 API version:       1.39
 Go version:        go1.10.4
 Git commit:        4d60db4
 Built:             Wed Nov  7 00:47:43 2018
 OS/Arch:           darwin/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.0
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.4
  Git commit:       4d60db4
  Built:            Wed Nov  7 00:55:00 2018
  OS/Arch:          linux/amd64
  Experimental:     true

Other relevant information

@ozbillwang https://stackoverflow.com/questions/58719522/tcpslaveagentlistener-is-invalid-404-not-found/59616476#59616476 check out my comment here

Anyone looking for the real explanation for this... You must configure a different port for jnlp i.e. 50000. The catch is that you need to provide the JENKINS_URL=http://jenkins:8080 and JENKINS_TUNNEL=jenkins:50000. If you try to hit 50000 on both the URL and TUNNEL you will get the error of 50000/tcpSlaveAgentListener invalid 404 not found. If you try to hit 8080 on both URL AND TUNNEL you will get an error like "Incorrect acknowledgement sequence, expected 0x000341434b got 0x485454502f". I hope this saves someone time

{             "name": "JENKINS_URL",             "value": "http://<jenkins>:8080"           },           {             "name": "JENKINS_TUNNEL",             "value": "<jenkins>:50000"           },

For us, restarting the pod fixed the issue in Jenkins which was running on an AWS EKS Kubernetes cluster using Helm. It was running as a stateful set, so we deleted the pod so that it can get created/deployed again and it worked after that.


Create CRUD/Admin API views

[x] Create Create view
[x] Create Update view
[x] Create Delete view
[x] Create Detail View
[x] Create List View
[ ] Write unit tests

@Zuiluj Please create unit tests for this issue.

Up for review:
https://github.com/capless/pfunk/blob/feature/api_tests/pfunk/tests/test_web_crud.py


Laravel 5.5

Nice project, I was wondering if you plan to support Laravel 5.5. Thanks.

I  think it's not being maintained any longer.


CI: Configure stale bot for PRs

We want to remind both contributors and maintainers that PRs should be up-to-date, reviewed and merged. Stale bot does a pretty good job of notifying the right people :^)

I believe it's possible to exempt draft PRs with exempt-draft-pr: true if we wanted to do that.
https://github.com/actions/stale?tab=readme-ov-file#exempt-draft-pr

I believe it's possible to exempt draft PRs with exempt-draft-pr: true if we wanted to do that.

Why would we add an exception for drafts?

Drafts to me indicate that there may be external blockers (e.g. spec updates or research) so having to worry about stalebot might be a bit annoying. But, some drafts don't fit that category either and just sit for no reason.
Not really an issue either way, but thought I'd point it out in-case maintainers found it useful.

Drafts to me indicate that there may be external blockers (e.g. spec updates or research)

Right, that happens sometimes, but we also have a lot of blocked drafts that never get any followup. Stalebot is useful in that sense to keep drafts alive and relevant, imo.

Having PRs be auto-closed after 30 days seems somewhat bad, especially if the PR is "done", and only waiting for review / merge by a maintainer

Having PRs be auto-closed after 30 days seems somewhat bad, especially if the PR is "done", and only waiting for review / merge by a maintainer

That's the goal of stalebot: if it just needs a review or merge, we should be reminded with a somewhat looming deadline.

That's the goal of stalebot: if it just needs a review or merge, we should be reminded with a somewhat looming deadline. Not everyone uses #code-review and not all maintainers peruse the PR list continuously.

Yes, but from experience with it in Serenity, it got to the point a good few times 😅

The alternative to Stalebot is what we have now: pages of PRs that are months old and forgotten about.
It's not perfect and we're open to better solutions, but the current setup really isn't working, and Stalebot would be a big improvement.

That's the goal of stalebot: if it just needs a review or merge, we should be reminded with a somewhat looming deadline. Not everyone uses #code-review and not all maintainers peruse the PR list continuously.

Yes, but from experience with it in Serenity, it got to the point a good few times 😅

Then you can Bump your own PR (which removes the stale label and resets the 30 day counter) and post it in code-review as a reminder

Let's merge this and let the reaping begin!

Instead of auto-closing, can it just post another message to remind everyone? I see zero benefit of auto-closing and to me it is incredibly annoying.

If you do not want it to close you can leave a comment. It will remove the stale label and reset the timeout (at least that's how it worked back in the SerenityOS days). It will also do so if you rebase the branch onto master, which will fix the merge conflicts that may develop over the course of 37 days, allowing the PR to be actually reviewed. If the author has no interest about the PR after 37 days, allowing it to go to a likely unmergeable state, only then it will be closed.

If you do not want it to close you can leave a comment.

Or if i wanted to close i would just close.
If the author has no interest about the PR they wouldn't have opened it in the first place.
“A computer can never be held accountable, therefore a computer must never make a management decision.”

They can lose interest after opening it. As has happened for many PRs here

The point of stalebot is to give both maintainers and contributors more opportunities (and distinct gates) to get emails/notifications about the PR. It forces action to either say "oh yeah, I didn't care about this change" or to say "hey, this needs review!" and get a maintainer to look at it with a message/ping in #code-review. Because we do feel bad when a PR with good changes drops off the radar. It also acts as an opportunity for contributors to say "oh, I don't have time to work on this change", which allows other contributors or the maintainers to commandeer the PR to get a new revision of the patch up for review.


feat: optimizing SVG graphics

Hi everyone
This PR adds a step that optimizes SVGs downloaded from Figma by using the SVGO API.
That ends up benefiting the final users as it helps on reducing bundle sizes and also makes it easier for animations by optimizing the number of paths.
The benefit can already be seen on simple SVGs, but the more complex SVG, the bigger the benefits. The difference is also huge when importing illustrations from Figma.
Example of an SVG downloaded from Figma:
SVG xml:
<svg width="50" height="50" viewBox="0 0 50 50" fill="none" xmlns="http://www.w3.org/2000/svg">
<path d="M29.2656 21.6875L25.2344 14.7083L21.2031 21.6875L12.974 16.9323L18.8073 6.82812C19.186 6.17855 19.7279 5.63927 20.3793 5.26377C21.0307 4.88828 21.769 4.68962 22.5208 4.6875H27.9479C28.6998 4.68962 29.4381 4.88828 30.0895 5.26377C30.7409 5.63927 31.2828 6.17855 31.6615 6.82812L37.5 16.9323L29.2656 21.6875ZM25.2344 12.6302L29.6458 20.2604L36.0677 16.5521L30.7552 7.34896C30.4699 6.85693 30.0605 6.44839 29.5679 6.16415C29.0753 5.8799 28.5167 5.72992 27.9479 5.72917H22.5208C21.9513 5.72953 21.3919 5.87931 20.8983 6.16354C20.4048 6.44778 19.9945 6.85652 19.7083 7.34896L14.4011 16.5521L20.8333 20.2604L25.2344 12.6302Z" fill="black"/>
<path d="M25.2344 14.1875H25.1823C25.1138 14.181 25.0472 14.161 24.9865 14.1286C24.9257 14.0962 24.872 14.0521 24.8284 13.9988C24.7848 13.9455 24.7522 13.8841 24.7325 13.8182C24.7128 13.7522 24.7064 13.683 24.7135 13.6146C24.7135 13.4115 25.3021 8.5625 31.0365 6.59896C31.1018 6.57377 31.1715 6.56202 31.2415 6.56439C31.3114 6.56676 31.3802 6.58321 31.4437 6.61277C31.5071 6.64232 31.564 6.68436 31.6109 6.73638C31.6577 6.7884 31.6936 6.84933 31.7163 6.91554C31.7391 6.98174 31.7483 7.05185 31.7434 7.12168C31.7384 7.19152 31.7195 7.25964 31.6876 7.32197C31.6557 7.38431 31.6116 7.43958 31.5579 7.48449C31.5042 7.5294 31.442 7.56301 31.375 7.58333C26.2604 9.33854 25.7552 13.6771 25.75 13.724C25.7359 13.851 25.6756 13.9685 25.5805 14.054C25.4854 14.1395 25.3622 14.187 25.2344 14.1875Z" fill="black"/>
<path d="M36.2761 23.4375L26.7396 21.7188L29.224 20.5052L36.5156 16.2969L39.1198 14.5469L36.2761 23.4375ZM30.0261 21.2708L35.5625 22.2552L37.2188 17.099L37.0417 17.2188L30.0261 21.2708Z" fill="black"/>
<path d="M40.6823 44.7135L29.0104 44.6823V35.1771H37.0677L33.0573 28.1875L41.3021 23.4635L47.1302 33.599C47.5049 34.2511 47.7021 34.9901 47.7021 35.7422C47.7021 36.4943 47.5049 37.2333 47.1302 37.8854L44.4062 42.5729C44.0279 43.2251 43.4846 43.7662 42.8309 44.1419C42.1773 44.5177 41.4362 44.7148 40.6823 44.7135ZM30.0521 43.6406L40.6771 43.6719C41.2452 43.6711 41.8033 43.5217 42.2958 43.2385C42.7882 42.9552 43.198 42.548 43.4844 42.0573L46.2083 37.3698C46.4921 36.8771 46.6415 36.3186 46.6415 35.75C46.6415 35.1814 46.4921 34.6229 46.2083 34.1302L40.9375 24.9062L34.5 28.5938L38.8854 36.2448H30.0677L30.0521 43.6406Z" fill="black"/>
<path d="M40.6719 44.7135H40.5729C40.5054 44.7005 40.4412 44.6742 40.3839 44.6361C40.3266 44.5981 40.2774 44.5491 40.2392 44.492C40.2009 44.4348 40.1744 44.3707 40.161 44.3032C40.1477 44.2358 40.1478 44.1663 40.1615 44.099C41.2031 38.7969 37.7136 36.1771 37.6823 36.151C37.6195 36.1143 37.5652 36.0648 37.5227 36.0058C37.4802 35.9468 37.4505 35.8795 37.4356 35.8083C37.4207 35.7371 37.4209 35.6636 37.4361 35.5925C37.4513 35.5213 37.4813 35.4542 37.5241 35.3954C37.5668 35.3365 37.6214 35.2873 37.6844 35.2508C37.7473 35.2144 37.8172 35.1915 37.8895 35.1837C37.9618 35.1759 38.035 35.1833 38.1042 35.2055C38.1735 35.2277 38.2374 35.2641 38.2917 35.3125C38.4583 35.4323 42.3646 38.3542 41.1823 44.3021C41.1572 44.4188 41.0929 44.5233 41 44.5982C40.907 44.6731 40.7912 44.7138 40.6719 44.7135Z" fill="black"/>
<path d="M30.25 47.2917L24 40.375L30.25 32.9792L30.0469 35.7396V44.1458L30.25 47.2917ZM25.3958 40.3542L29.0417 44.375V44.1615V36.0625L25.3958 40.3542Z" fill="black"/>
<path d="M20.9271 44.8281L9.26563 44.7917C8.51316 44.7872 7.77507 44.5852 7.12519 44.2058C6.47532 43.8265 5.93645 43.2832 5.5625 42.6302L2.86979 37.9427C2.49505 37.2915 2.29782 36.5534 2.29782 35.8021C2.29782 35.0508 2.49505 34.3126 2.86979 33.6615L8.76042 23.5469L16.974 28.3281L12.9167 35.2917L20.974 35.3281L20.9271 44.8281ZM9.13542 25L3.78646 34.151C3.50264 34.6437 3.35324 35.2023 3.35324 35.7708C3.35324 36.3394 3.50264 36.898 3.78646 37.3906L6.48438 42.0781C6.76127 42.5768 7.16454 42.9938 7.65365 43.2873C8.14277 43.5808 8.70051 43.7404 9.27083 43.75L19.8906 43.7917L19.9271 36.375L11.1094 36.3333L15.5469 28.7135L9.13542 25Z" fill="black"/>
<path d="M9.3021 36.8125C6.95687 36.7834 4.70723 35.8787 2.99481 34.276C2.89132 34.1848 2.82827 34.0562 2.81948 33.9185C2.81069 33.7809 2.85689 33.6453 2.94793 33.5417C3.03917 33.4382 3.16774 33.3751 3.30542 33.3663C3.44311 33.3576 3.57865 33.4037 3.68231 33.4948C7.71876 37.0469 11.6406 35.401 11.8021 35.3281C11.9292 35.2722 12.0733 35.269 12.2027 35.3193C12.3321 35.3696 12.4363 35.4693 12.4922 35.5964C12.5481 35.7234 12.5513 35.8675 12.501 35.997C12.4507 36.1264 12.3511 36.2305 12.224 36.2865C11.292 36.6447 10.3005 36.8232 9.3021 36.8125Z" fill="black"/>
<path d="M18.2552 30.5052L15.9688 28.9427L8.70313 24.7188L5.88022 23.3125L14.9948 21.3854L18.2552 30.5052ZM9.02084 23.7344L9.21355 23.8281L16.2083 27.9063L14.3177 22.5938L9.02084 23.7344Z" fill="black"/>
</svg>

SVG Image:

Example of the same SVG after the optimization:
SVG xml
<svg width="50" height="50" fill="none" xmlns="http://www.w3.org/2000/svg">
  <path d="m29.266 21.688-4.032-6.98-4.03 6.98-8.23-4.756 5.833-10.104a4.313 4.313 0 0 1 3.714-2.14h5.427a4.313 4.313 0 0 1 3.713 2.14L37.5 16.932l-8.234 4.756Zm-4.032-9.058 4.412 7.63 6.422-3.708-5.313-9.203a3.25 3.25 0 0 0-2.807-1.62H22.52a3.255 3.255 0 0 0-2.813 1.62L14.4 16.552l6.432 3.708 4.401-7.63Z" fill="#000"/>
  <path d="M25.234 14.188h-.052a.52.52 0 0 1-.468-.573c0-.204.588-5.053 6.323-7.016a.52.52 0 1 1 .338.984c-5.115 1.756-5.62 6.094-5.625 6.141a.521.521 0 0 1-.516.463Zm11.042 9.25-9.536-1.72 2.484-1.213 7.292-4.208 2.604-1.75-2.844 8.89Zm-6.25-2.167 5.537.984 1.656-5.156-.177.12-7.016 4.052Zm10.656 23.443-11.672-.032v-9.505h8.058l-4.01-6.99 8.244-4.724L47.13 33.6a4.302 4.302 0 0 1 0 4.286l-2.724 4.688a4.296 4.296 0 0 1-3.724 2.14Zm-10.63-1.073 10.625.03a3.257 3.257 0 0 0 2.807-1.614l2.724-4.687a3.245 3.245 0 0 0 0-3.24l-5.27-9.224-6.438 3.688 4.385 7.65h-8.817l-.016 7.397Z" fill="#000"/>
  <path d="M40.672 44.714h-.1a.518.518 0 0 1-.41-.615c1.041-5.302-2.448-7.922-2.48-7.948a.52.52 0 1 1 .61-.839c.166.12 4.073 3.042 2.89 8.99a.52.52 0 0 1-.51.412ZM30.25 47.292 24 40.375l6.25-7.396-.203 2.76v8.407l.203 3.146Zm-4.854-6.938 3.646 4.021v-8.313l-3.646 4.292Zm-4.469 4.474-11.661-.036a4.296 4.296 0 0 1-3.704-2.162L2.87 37.943a4.292 4.292 0 0 1 0-4.282l5.89-10.114 8.214 4.781-4.057 6.964 8.057.036-.047 9.5ZM9.135 25l-5.349 9.151a3.245 3.245 0 0 0 0 3.24l2.698 4.687a3.25 3.25 0 0 0 2.787 1.672l<IP_ADDRESS>-7.417-8.818-.042 4.438-7.62L9.135 25Z" fill="#000"/>
  <path d="M9.302 36.813a9.4 9.4 0 0 1-6.307-2.537.52.52 0 0 1 .687-.781c4.037 3.552 7.959 1.906 8.12 1.833a.524.524 0 0 1 .422.958 7.909 7.909 0 0 1-2.922.526Zm8.953-6.308-2.286-1.562-7.266-4.224-2.823-1.407 9.115-1.927 3.26 9.12Zm-9.234-<IP_ADDRESS> 6.994 4.078-1.89-5.312-5.297 1.14Z" fill="#000"/>
</svg>

SVG Image:

Final result:
The SVG image remains the same, but the markup is optimized and more readable.
Added the optimization as default but added the --noOptimizeSVG CLI option for users to disable the optimization if needed (It can also be disabled by setting optimizeSVG: false on the figmarc file)
Description of the changes made

added svgo and @types/svgo library on package.json
added optimizeSVG option enabled by default
added optimizeSVGGraphics function
updated the createGraphics function to call optimizeSVGGraphics (only when output is outputFormatGraphics is svg)
updated docs with optimizeSVG and noOptimizeSVG option
added test cases for optimizeSVGGraphics and update test case for createGraphics

Checklist

[x]  I have read the Figmagic Contribution Guideline
[x]  The PR title summarizes the change

This is a smart idea, but I am concerned about bundling even more dependencies; by the way this uses svgo as a dev dependency which wouldn't work?
On that note, is svgo "bundleable" with Webpack?
This is one more thing that could be provided possibly as a guide rather than a feature.

On that note, is svgo "bundleable" with Webpack?

Hey, yes it should be on 'dependencies' instead of devDependencies to be "bundable" by webpack, I just updated the PR

This is a smart idea, but I am concerned about bundling even more dependencies; by the way this uses svgo as a dev dependency which wouldn't work?

It's "bundleable", and it significantly increases the package size: from 218 kb to 1.49 MB,
Current:

With SVGO:

On my note, I wasn't so worried about bundle size because Figmagic is a dev dependency and won't get bundled for end users, and on the other side, the SVGs are bundled, and having them optimized by default could make the trade-off worthwhile.

This is one more thing that could be provided possibly as a guide rather than a feature.

That might be a good idea 💡

OK, @opauloh. While I love your work, I feel like this one isn't in line with design goals like keeping this light and dependency-less. It's a bit of a dud that Figmagic uses Webpack at all, but it comes down to bundling all of the files of the project rather than, as is normal, also any third party dependencies. This design goal may not have been clear, but I feel it's the right call—svgo optimization I am happy to support with a dedicated guide that we can link to in the regular README.
Once again, it's never "fun" saying no, but in this case we retain the clarity of the project while easing production-grade use for our users.

Thanks for your kindly anwer @mikaelvesavuori , I agree with you, and realized I had precipitated myself in opened the PR (we could had discussed that on an issue first).
I'll be happy to add an guide on how to optimize svgs later, thanks


Upgrade to Gradle 6.2.1, and simplify the build

Should we change to gradle kts build scripts?
Fixes #2

Thanks @timyates.
I suppose the answer to your question feeds in to the discussion around #6.  This looks good as is anyway, so let's get it merged and see what comes of #6.


Sometimes objects don't cast shadows

This seems to happen in weird circumstances (such as z>300.0f and y is slightly larger than the wooden cylinder).
This is unexpected because the shadowmap's projection matrix dynamically expands to pack the entire scene. Very odd.

This was fixed a while ago, the scene boundary was incorrect, so thats why the projection expansion didn't yield the correct visuals. I don't have a commit hash for it, sorry. It was a few weeks ago.


fix github actions workflows

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


NAS-124262 / 24.04 / Remove haproxy from ixdiagnose

Context
HAProxy was removed in DragonFish so there is no reason to capture it's contents in debug.
This PR removes the HAProxy related info gathering in VM plugin.

Jira URL: https://ixsystems.atlassian.net/browse/NAS-124262

@bmeagherix thank you for pointing out - fixed the label


Long names and many measurements in a surface

Dear Michael,
I have really long names for measurements containing all the specifications of the simulation on the "analyze-page" the names are cut and I can not properly select the single measurements.
Additionally, it might be useful to scroll through the measurements. Thus one can see what changes in the plot if one selects or deselects a single measurement. If the list is too long and one clicks on a measurement at the end one can not see the plot anymore because the whole screen is filled with the list.
Also for many measurements, it might be useful if the selected measurements in one plot can be automatically selected in all other plots. Otherwise I have to select in e.g. PSD and VBM and other plots always the same measurements by hand.
I have shared the surface 956 with you such that you can see my problems

Dear Richard,
Thanks for your message and for sharing the surface. There are three things you are mention here:
Analyze page
I'm not fully sure what list of names you are referring to on the "Analyze" page. There are several places possible.
You mean the selection dialogue under each plot, right?
If it is about the first column in the Roughness Parameter table, see #560. This will be fixed in the next version.
Scroll through the measurements
I understand .. if we would have some fixed area in which scrolling is possible, the plot could stay at a fixed place
without scrolling away.
One selection for multiple plots
Would it be better to have one selection dialogue for all plots?
I'm not sure how to implement this, because currently the plots are individual and also individually loaded
and it's probably not straightforward to address several plots at once from Javascript..
I need to discuss this with the others.

Dear Michael,
sorry for being imprecise in describing my problems. A picture like in #560 describes a problem much easier and better, I should stick to such a descriptions.
Analyze page
Yes, I meant the selection dialogue under each plot

Scroll through the measurements
Yes, I was thinking of something like this
One selection for multiple plots
For me a single selection dialogue would be fine, but I am not sure if this is true for all users....

Dear Richard,
Thanks for the screenshot! I've discussed this yesterday with Lars.
Actually, there is already sth which is similar to what you suggested.
The page "Find & select" allows to scroll (and search) for individual measurements. You see the full name
with a description:

Here you can select individual measurements and press the green Analyze button in the top area, where all selected items are listed:

This will narrow all plots to the selection. Did you try that?
You can also open a new tab with a right click on "Analyze" and have different tabs with different selections.
Like this you have both, scrolling and one selection for all plots. And your analysis downloads are also narrowed to the selected measurements.
Doing this all on the "Analyze" page is a bit difficult with the current implementation and probably not all users want one common selection for all plots.
Does this help?

What you can also do here is to assign tags to individual groups of measurements and select the tags to compare the corresponding analyses.

Hi Michael,
thanks for the explenation, this perfectly solves my problems!


[BUG] Incompatibility with Levels

Module appears to be incompatible with the Levels module

is there anything we can do to bump this up.  from what i learned from the dev of levels, they have instructions for calling an exposed api to determine if Levels is hiding and how to override.

This has been a low priority issue since I personally don't use Levels, and I haven't had a lot of complaints about the incompatibility. I am a bit afraid that both Levels and making Shared Vision compatible with it is quite complex, but when I have the time I'll have a look.

I take it you haven't had the time to investigate this further? It's a real shame that they are incompatible with each other as they are both very useful for various purposes. Especially when it comes to utilising multiple scenes and multiple levels. Makes it a nightmare otherwise.

I would also very much like having this work, as i personally use levels alot in maps that i make for my games

I'd love to fix this incompatibility, but I'm not sure what's wrong. This issue is almost 2 years old and I don't remember why I created it. It might even be the case that the original incompatibility no longer exists. I don't use Levels and never have, so I don't know.
If anyone has specific things that I can test for it would greatly help, thanks.

@OmegaRogue has done some testing to figure out the issues with Shared Vision and Levels. The issue we found was that if 2 tokens are on levels on top of each other, it is not possible to share vision between those tokens. The reason is that the vision of both tokens would overlap, so you'd see a mixture of both levels.
I don't think there's a solution, besides projecting the second level onto a different part of the screen, which would be too much work to implement. You could look into using Multilevel Tokens instead of Levels.
I will leave this issue open for a few weeks in case someone can think of a solution.


Update cross_agent_tests

Changes were made October 5. The changes are all spelling corrections.

Whoops, this reverted improvements previously introduced


Verify code over Polygon and Linea testnets

Use --verify over deployed code to have explorer assess the verification for Polygon and Linea.
(Error appeared for unknown reason using polygon Api key, to be checked)

gotta generate separate API key, and maybe use blockscoot for linea

Even using a linea API KEY, the deployment script fails only for this chain.

Closing as SCL is superseding FCL.


Add mail-wrapper.sh to allow email notifications from within

I added mail-wrapper.sh which is a wrapper shell script to allow the container's apcupsd to send email notifications using busybox's sendmail.
I created it so that I can get email notifications, so I've only tested this with my email service provider with my particular configuration (using STARTTLS).  It might be nice to allow for non-STARTTLS connections but I'm not interested in that right now.
I've included some documentation as comments in the script itself.

Hi @lenkawamoto . Thank you for your contribution. This looks very mature and clean. Can you help me understand some design decisions you made?
If I understand correctly, apcupsd calls mail to send mails, which is not installed in that image. Instead, you write a wrapper, that can be used like mail but internally uses sendmail which indeed is installed in the image.

Why don't we install mail in the Dockerfile?
You recommend to bind-mount the file into the container. Why not ADD it in the Dockerfile?

I want to object to your contribution in NO way. I'm just really interested in your thoughts. Thanks again and Cheers!

My thought was to minimize impacting the docker image as much as possible, and with this solution there was no need to build a new docker image.
Since sendmail is already available, I didn't think there's a need to add an extra binary (which might add more configuration/overhead/other dependencies) to accomplish what I needed in enabling email notifications from within the container.
You could install the script into the container, but then you would need a mechanism to get the user defined configuration values for $mailTo, $mailFrom, $mailServer, $mailPort, $mailUsername, $mailPassword.  Also, as it stands, NOT having this shell script makes the container behave as is -- not send any email notifications.  Adding this shell script will change how this container behaves, and unless the sendmail related configurations are correct, will cause errors.  Leaving it outside the container makes it an optional functionality.
You're totally welcome to merge this pull request or disregard it and install the /usr/bin/mail binary into the image.  Either way, I will not be offended at all.  Installing mail might be better in that it is a well used/mature binary, whereas my shell script is new.  However, I think this script is pretty trivial on what it does and (of course) it works for me as is.

Thank you for your explanation and your great contribution! I added an Add-Ons part to the README that mentions your wrapper.


fix(chat): fix items aligment and edit attachment functionality (Issues #1263, #1264)

Description:
Fix items aligment and edit attachment functionality
Issues:

#1263
#1264

Checklist:

[x] the pull request name complies with Conventional Commits
[x] the pull request name starts with fix(<scope>):, feat(<scope>):, feature(<scope>):, chore(<scope>):, hotfix(<scope>): or e2e(<scope>):. If contains breaking changes then the pull request name must start with fix(<scope>)!:, feat(<scope>)!:, feature(<scope>)!:, chore(<scope>)!:, hotfix(<scope>)!: or e2e(<scope>)!: where <scope> is name of affected project: chat, chat-e2e, overlay, shared, sandbox-overlay, etc.
[x] the pull request name ends with (Issue #<TICKET_ID>) (comma-separated list of issues)
[x] I confirm that do not share any confidential information like API keys or any other secrets and private URLs

/deploy-review

/deploy-review


[Feature request] disable analytics by default

Please consider disabling any kind of data analytics/collect by default.

There is a question at first launch which asks you what if you accept to enable google analytics.
You have a global settings to disable later.
It is enough to manage analytics


LAPACKE_sgesdd_work on armv7 android float-abi=hard never returns for some cases

Hi!
I'm using openblas on an android device. So far everything works fine, but now I'm facing a strange error. In my function, I'm calling LAPACKE_sgesdd_work directly using preallocated memory.
For special cases: It never returns.
I compiled LAPACKE_sgesdd_work with debug flags and jumped into the disassembly: It runs until it gets into the fortran call sgesdd_. It never returns from there.
This code should give you the same behavior on an armv7 device:
float A[ 9 ] = {  1.f,  0.f, -1.f,
                 -2.f,  1.f,  4.f,
                 -3.f,  4.f,  5.f };

float U[ 9 ]; float S[ 3 ]; float V_t[ 9 ];

/* number of rows of A */
const int m = 3;
/* number of cols of A */
const int n = 3;
/* leading dimension of A */
const int ld_a = n;
/* leading dimension of U */
const int ld_u = m;
/* leading dimension of V_t */
const int ld_v_t = n;
/* SVD workspace array */
int iwork[ 8 * 4 ];
/* SVD workspace array length */
int lwork = 180;
/* SVD workspace array */
float work[ 180 * 2 ];

int result = 1;

result = LAPACKE_sgesdd_work(LAPACK_ROW_MAJOR, 'A', m, n, A, ld_a, S, U, ld_u,
                                                     V_t, ld_v_t, work, lwork, iwork);

Crucial: If I compile exactly the same code for x86, it works.
I do allocate more memory than needed just to be sure that there is no access vialoation inside.
On the other hand the following does work:
float A[ 4 ] = {  1.f,  0.f,
                 -2.f,  1.f };

float U[ 4 ]; float S[ 2 ]; float V_t[ 4 ];

/* number of rows of A */
const int m = 2;
/* number of cols of A */
const int n = 2;
/* leading dimension of A */
const int ld_a = n;
/* leading dimension of U */
const int ld_u = m;
/* leading dimension of V_t */
const int ld_v_t = n;
/* SVD workspace array */
int iwork[ 8 * 3 ];
/* SVD workspace array length */
int lwork = LAPACK_GESDD_LWORK( 3, 3 );
/* SVD workspace array */
float work[ LAPACK_GESDD_LWORK( 3, 3 ) ];

int result = 1;

result = LAPACKE_sgesdd_work(LAPACK_ROW_MAJOR, 'A', m, n, A, ld_a, S, U, ld_u,
                                                     V_t, ld_v_t, work, lwork, iwork);

I can now even confirm, it is the same behavior when calling sgesdd_ directly:
 float A[ 9 ] = {  1.f,  0.f, -1.f,
                  -2.f,  1.f,  4.f,
                  -3.f,  4.f,  5.f };

float U[ 9 ]; float S[ 3 ]; float V_t[ 9 ];

/* number of rows of A */
int m = 3;
/* number of cols of A */
int n = 3;
/* leading dimension of A */
int ld_a = n;
/* leading dimension of U */
int ld_u = m;
/* leading dimension of V_t */
int ld_v_t = n;
/* SVD workspace array */
int iwork[ 8 * 4 ];
/* SVD workspace array length */
int lwork = 180;
/* SVD workspace array */
float work[ 180 * 2 ];

char jobz = 'A';
int info = 1;

sgesdd_(&jobz, &m, &n, A, &ld_a, S, U, &ld_u, V_t,
        &ld_v_t, work, &lwork, iwork, &info );

I also tested the latter example with lapack-3.6.0 using reference BLAS from netlib and there it works.

Are you sure workspace estimation (*work=-1) returns same workspace size on x86 and arm?
Please dump threads and share the log from frozen process:
gdb 2>&1 | tee gdb.log
gdb> atta
gdb> t a a bt
gdb> deta
gdb> q

No I'm not sure, whether the workspace estimation returns the same size on arm or x86, but neither am I running any test on x86 nor am I using the workspace estimation. I read the documentation and preallocated the workspace bigger than necessary.
I'm not sure how to run these commands on my phone using a remote debugger. I'm working with QtCreator to compile and install a test app with this code. If i try to pause the application with the QtCreator, after a while, it tells me whether I want to to stop gdb since it does not respond or give it more time.

Hi,
every lapack function, that needs a local workspace,
calls ilaenv to get a block size. If you need another
local work size, you have to modify ilaenv.f in lapack-netlib/SRC.
Look at source of sgesdd.f to find the calls to ilaenv
Best regards
Werner
On 05/30/2016 11:05 AM, Mikaso wrote:

No I'm not sure, whether the workspace estimation returns the same
size on arm or x86, but neither am I running any test on x86 nor am I
using the workspace estimation. I read the documentation and
preallocated the workspace bigger than necessary.
I'm not sure how to run these commands on my phone using a remote
debugger. I'm working with QtCreator to compile and install a test app
with this code. If i try to pause the application with the QtCreator,
after a while, it tells me whether I want to to stop gdb since it does
not respond or give it more time.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/xianyi/OpenBLAS/issues/894#issuecomment-222447676, or
mute the thread
https://github.com/notifications/unsubscribe/AC1e6Gtf_sMU086lPBeIHezNpJPIhFEmks5qGqhVgaJpZM4ImdUT.

Ok, thanks for the information, but what am I supposed to do about it and how should I know whether it's right? Shouldn't both calls of sgesdd use the same amount of memory?

If you had machine with dozen of terabytes of RAM you would rewrite ilaenv.
Can you dump the threads?

I found how to run the gdb commands in QtCreator. I cannot run it the moment it freezes, but here is the dump right after the call of sgesdd_:

>&"t a a bt\n"
>~"\nThread 22 (Thread 30114.30179):\n"
>~"#0  0xb6d3440c in __ioctl () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#1  0xb6d3c4d4 in ioctl () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#2  0xb6f46d88 in ?? ()\n"
>~"Backtrace stopped: previous frame identical to this frame (corrupt stack?)\n"
>~"\nThread 21 (Thread 30114.30154):\n"
>~"#0  0xb6d02610 in syscall () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#1  0xb6d32b24 in __pthread_cond_timedwait_relative(pthread_cond_internal_t*, pthread_mutex_t*, timespec const*) () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#2  0xa87fb00e in ?? ()\n"
>~"Backtrace stopped: previous frame identical to this frame (corrupt stack?)\n"
>~"\nThread 20 (Thread 30114.30153):\n"
>~"#0  0xb6d02610 in syscall () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#1  0xb6d32b24 in __pthread_cond_timedwait_relative(pthread_cond_internal_t*, pthread_mutex_t*, timespec const*) () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#2  0x9f0ad252 in ?? ()\n"
>~"Backtrace stopped: previous frame identical to this frame (corrupt stack?)\n"
>~"\nThread 19 (Thread 30114.30152):\n"
>~"#0  0xb6d02610 in syscall () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#1  0xb6d32b24 in __pthread_cond_timedwait_relative(pthread_cond_internal_t*, pthread_mutex_t*, timespec const*) () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#2  0xa099660e in QWaitConditionPrivate::wait(unsigned long) () from C:\\Qt\\Qt5.6.0\\5.6\\android_armv7\\lib\\libQt5Core.so\n"
>~"#3  0xa0996be2 in QWaitCondition::wait(QMutex*, unsigned long) () from C:\\Qt\\Qt5.6.0\\5.6\\android_armv7\\lib\\libQt5Core.so\n"
>~"#4  0xaeca7378 in QSGRenderThreadEventQueue::takeEvent(bool) () from C:\\Qt\\Qt5.6.0\\5.6\\android_armv7\\lib\\libQt5Quick.so\n"
>~"#5  0xaeca74d2 in QSGRenderThread::processEventsAndWaitForMore() () from C:\\Qt\\Qt5.6.0\\5.6\\android_armv7\\lib\\libQt5Quick.so\n"
>~"#6  0xaeca76d0 in QSGRenderThread::run() () from C:\\Qt\\Qt5.6.0\\5.6\\android_armv7\\lib\\libQt5Quick.so\n"
>~"#7  0xa0995d16 in QThreadPrivate::start(void*) () from C:\\Qt\\Qt5.6.0\\5.6\\android_armv7\\lib\\libQt5Core.so\n"
>~"#8  0xb6d32ea6 in __pthread_start(void*) () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#9  0xb6d04c36 in __start_thread () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#10 0x00000000 in ?? ()\n"
>~"\nThread 18 (Thread 30114.30150):\n"
>~"#0  0xb6d344e0 in __pselect6 () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#1  0xb6d07398 in select () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#2  0xa0adc388 in qt_safe_select(int, __kernel_fd_set*, __kernel_fd_set*, __kernel_fd_set*, timespec const*) () from C:\\Qt\\Qt5.6.0\\5.6\\android_armv7\\lib\\libQt5Core.so\n"
>~"#3  0xa0add230 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () from C:\\Qt\\Qt5.6.0\\5.6\\android_armv7\\lib\\libQt5Core.so\n"
>~"#4  0xa0add4f8 in QEventDispatcherUNIX::processEvents(QFlags) () from C:\\Qt\\Qt5.6.0\\5.6\\android_armv7\\lib\\libQt5Core.so\n"
>~"#5  0xa0aa6dc4 in QEventLoop::processEvents(QFlags) () from C:\\Qt\\Qt5.6.0\\5.6\\android_armv7\\lib\\libQt5Core.so\n"
>~"#6  0xa0aa73de in QEventLoop::exec(QFlags) () from C:\\Qt\\Qt5.6.0\\5.6\\android_armv7\\lib\\libQt5Core.so\n"
>~"#7  0xa0993758 in QThread::exec() () from C:\\Qt\\Qt5.6.0\\5.6\\android_armv7\\lib\\libQt5Core.so\n"
>~"#8  0x9d43b88a in ?? ()\n"
>~"Backtrace stopped: previous frame identical to this frame (corrupt stack?)\n"
>~"\nThread 17 (Thread 30114.30149):\n"
>~"#0  0xb6d344e0 in __pselect6 () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#1  0xb6d07398 in select () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#2  0xa0adc388 in qt_safe_select(int, __kernel_fd_set*, __kernel_fd_set*, __kernel_fd_set*, timespec const*) () from C:\\Qt\\Qt5.6.0\\5.6\\android_armv7\\lib\\libQt5Core.so\n"
>~"#3  0xa0add230 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () from C:\\Qt\\Qt5.6.0\\5.6\\android_armv7\\lib\\libQt5Core.so\n"
>~"#4  0xa0add4f8 in QEventDispatcherUNIX::processEvents(QFlags) () from C:\\Qt\\Qt5.6.0\\5.6\\android_armv7\\lib\\libQt5Core.so\n"
>~"#5  0xa0aa6dc4 in QEventLoop::processEvents(QFlags) () from C:\\Qt\\Qt5.6.0\\5.6\\android_armv7\\lib\\libQt5Core.so\n"
>~"#6  0xa0aa73de in QEventLoop::exec(QFlags) () from C:\\Qt\\Qt5.6.0\\5.6\\android_armv7\\lib\\libQt5Core.so\n"
>~"#7  0xa0993758 in QThread::exec() () from C:\\Qt\\Qt5.6.0\\5.6\\android_armv7\\lib\\libQt5Core.so\n"
>~"#8  0xaefa18e0 in QQmlThreadPrivate::run() () from C:\\Qt\\Qt5.6.0\\5.6\\android_armv7\\lib\\libQt5Qml.so\n"
>~"#9  0xa0995d16 in QThreadPrivate::start(void*) () from C:\\Qt\\Qt5.6.0\\5.6\\android_armv7\\lib\\libQt5Core.so\n"
>~"#10 0xb6d32ea6 in __pthread_start(void*) () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#11 0xb6d04c36 in __start_thread () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#12 0x00000000 in ?? ()\n"
>~"\nThread 15 (Thread 30114.30144):\n"
>~"#0  0xb6d02610 in syscall () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#1  0xb6d32b24 in __pthread_cond_timedwait_relative(pthread_cond_internal_t*, pthread_mutex_t*, timespec const*) () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#2  0x9f0ad252 in ?? ()\n"
>~"Backtrace stopped: previous frame identical to this frame (corrupt stack?)\n"
>~"\nThread 14 (Thread 30114.30142):\n"
>~"#0  0xb6d342cc in __epoll_pwait () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#1  0xb6d04fbc in epoll_pwait () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#2  0xb6d04fd6 in epoll_wait () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#3  0xb6f7c356 in ?? ()\n"
>~"Backtrace stopped: previous frame identical to this frame (corrupt stack?)\n"
>~"\nThread 13 (Thread 30114.30143):\n"
>~"#0  sgesdd (jobz=..., m=3, n=3, a=..., lda=3, s=..., u=..., ldu=3, vt=..., ldvt=3, work=..., lwork=180, iwork=..., info=0, _jobz=0) at sgesdd.f:216\n"
>~"#1  0xa033a268 in LAPACKE_sgesdd_work (matrix_layout=, jobz=0 '\\000', m=0, n=-1629229824, a=0x9ee3ee04, lda=3, s=0x9ee3edf8, u=0x9ee3ee28, ldu=3, vt=0x9ee3ee4c, ldvt=1065353216, work=0x9ee3eef0, lwork=180, iwork=0x9ee3ee70) at lapacke_sgesdd_work.c:84\n"
>~"#2  0xa0332f00 in LAPACKE_sgesdd_work_wrapper (layout=102, jobz=65 'A', m=3, n=3, A=0x9ee3ee04, lda=3, S=0x9ee3edf8, U=0x9ee3ee28, ldu=3, vt=0x9ee3ee4c, ldvt=3, work=0x9ee3eef0, lwork=180, iwork=0x9ee3ee70) at ..\\openblas_wrapper/lapacke_wrapper.h:270\n"
>~"#3  0xa0333200 in cblas_issue_894 () at ..\\openblas_wrapper\\main.cpp:107\n"
>~"#4  0xa0333000 in main (argc=1, argv=0x9ee3f4f8) at ..\\openblas_wrapper\\main.cpp:53\n"
>~"#5  0xb36cc5e0 in startMainMethod(void*) () from C:\\Qt\\Qt5.6.0\\5.6\\android_armv7\\plugins\\platforms\\android\\libqtforandroid.so\n"
>~"#6  0xb6d32ea6 in __pthread_start(void*) () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#7  0xb6d04c36 in __start_thread () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#8  0x00000000 in ?? ()\n"
>~"\nThread 11 (Thread 30114.30131):\n"
>~"#0  0xb6d3440c in __ioctl () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#1  0xb6d3c4d4 in ioctl () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#2  0xb6f46d88 in ?? ()\n"
>~"Backtrace stopped: previous frame identical to this frame (corrupt stack?)\n"
>~"\nThread 10 (Thread 30114.30129):\n"
>~"#0  0xb6d35da8 in wait4 () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#1  0xb066a686 in ?? ()\n"
>~"Backtrace stopped: previous frame identical to this frame (corrupt stack?)\n"
>~"\nThread 9 (Thread 30114.30126):\n"
>~"#0  0xb6d3440c in __ioctl () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#1  0xb6d3c4d4 in ioctl () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#2  0xb6f46d88 in ?? ()\n"
>~"Backtrace stopped: previous frame identical to this frame (corrupt stack?)\n"
>~"\nThread 8 (Thread 30114.30125):\n"
>~"#0  0xb6d3440c in __ioctl () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#1  0xb6d3c4d4 in ioctl () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#2  0xb6f46d88 in ?? ()\n"
>~"Backtrace stopped: previous frame identical to this frame (corrupt stack?)\n"
>~"\nThread 7 (Thread 30114.30124):\n"
>~"#0  0xb6d02610 in syscall () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#1  0xb494fa0c in ?? ()\n"
>~"Backtrace stopped: previous frame identical to this frame (corrupt stack?)\n"
>~"\nThread 6 (Thread 30114.30123):\n"
>~"#0  0xb6d02610 in syscall () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#1  0xb494fa0c in ?? ()\n"
>~"Backtrace stopped: previous frame identical to this frame (corrupt stack?)\n"
>~"\nThread 5 (Thread 30114.30122):\n"
>~"#0  0xb6d02610 in syscall () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#1  0xb494fa0c in ?? ()\n"
>~"Backtrace stopped: previous frame identical to this frame (corrupt stack?)\n"
>~"\nThread 4 (Thread 30114.30121):\n"
>~"#0  0xb6d02610 in syscall () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#1  0xb494fa0c in ?? ()\n"
>~"Backtrace stopped: previous frame identical to this frame (corrupt stack?)\n"
>~"\nThread 3 (Thread 30114.30120):\n"
>~"#0  0xb6d354f4 in recvmsg () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#1  0xb4c5a022 in ?? ()\n"
>~"Backtrace stopped: previous frame identical to this frame (corrupt stack?)\n"
>~"\nThread 2 (Thread 30114.30119):\n"
>~"#0  0xb6d345e0 in __rt_sigtimedwait () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#1  0xb6d0844a in sigwait () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#2  0xb4b935e8 in ?? ()\n"
>~"Backtrace stopped: previous frame identical to this frame (corrupt stack?)\n"
>~"\nThread 1 (Thread 30114.30114):\n"
>~"#0  0xb6d342cc in __epoll_pwait () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#1  0xb6d04fbc in epoll_pwait () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#2  0xb6d04fd6 in epoll_wait () from D:\\MobileApp\\build-openblas_wrapper-Android_f_r_armeabi_v7a_GCC_4_9_Qt_5_6_0-Debug\\libc.so\n"
>~"#3  0xb6f7c356 in ?? ()\n"
>~"Backtrace stopped: previous frame identical to this frame (corrupt stack?)\n"
>2879^done

Does C kernel work? (ARMv5)? Looks like wrong calling convention or something.

~"#1  0xa033a268 in LAPACKE_sgesdd_work (matrix_layout=, jobz=0 '\000', m=0, n=-1629229824, a=0x9ee3ee04, lda=3, s=0x9ee3edf8, u=0x9ee3ee28, ldu=3, vt=0x9ee3ee4c, ldvt=1065353216, work=0x9ee3eef0, lwork=180, iwork=0x9ee3ee70) at
lapacke_sgesdd_work.c:84\n"
LWORK-IWORK=128(DEC)<<180

The calling convention might be the right point to look at. Since I'm using QtCreator to build an executable for my phone and it's prebuilt binaries are built with soft float abi I decided to try out erlv's approach to wrapp the openblas function calls, see #853 , because currently, for ARMV7, only hard float abi is supported, as far as I know. In my specific case, for this method it is:
// LAPACKE_sgesdd_work ------
int LAPACKE_sgesdd_work_wrapper( int layout, char jobz, int m, int n,
        float* A, int lda, float* S, float* U, int ldu, float* vt, int ldvt,
        float* work, int lwork, int* iwork) {
#ifdef __ARM_PCS_VFP
  // if compiled by -mfloat-abi=hard, directly call LAPACKE_sgesdd_work
  return LAPACKE_sgesdd_work(layout, jobz, m, n, A, lda, S, U, ldu, vt, ldvt, work, lwork, iwork);
#else
#ifdef __SOFTFP
#error "ERROR:please build use softfp or hard ABI\n"
#else
  // if compiled by -mfloat-abi=softfp, run the assembly to prepare for the hardfp ABI call.
  register int val asm("r0") = 1;
  __asm__ __volatile__("sub sp, sp, #72 \n\t"
                       "mov r0, %0 \n\t"            // layout
                       "mov r1, %1 \n\t"            // jobz
                       "mov r2, %2 \n\t"            // m
                       "mov r3, %3 \n\t"            // n
                       "str %4, [sp] \n\t"          // A
                       "str %5, [sp, #4] \n\t"      // lda
                       "str %6, [sp, #8] \n\t"      // S
                       "str %7, [sp, #12] \n\t"     // U

                       "ldr r12, %8 \n\t"           // ldu
                       "str r12, [sp, #16] \n\t"

                       "ldr r12, %9 \n\t"           // vt
                       "str r12, [sp, #20] \n\t"

                       "ldr r12, %10 \n\t"          // ldvt
                       "str r12, [sp, #24] \n\t"

                       "ldr r12, %11 \n\t"          // work
                       "str r12, [sp, #28] \n\t"

                       "ldr r12, %12 \n\t"          // lwork
                       "str r12, [sp, #32] \n\t"

                       "ldr r12, %13 \n\t"          // iwork
                       "str r12, [sp, #36] \n\t"

                       "bl " LAPACKE_sgesdd_work "(PLT)\n\t"
                       "add sp, sp, #72 \n\t"
                       :
                       : "r"(layout), "r"(jobz), "r"(m), "r"(n),
                         "r"(A), "r"(lda), "r"(S), "r"(U), "g"(ldu),
                         "g"(vt), "g"(ldvt),
                         "g"(work), "g"(lwork), "g"(iwork)
                       : "cc", "memory", "r0", "r1", "r2", "r3", "sp", "r12");
  return val;
#endif
#endif
}
// LAPACKE_sgesdd_work ------

When my wrappers are running, I want to share them to the community.
Besides of problems while developing - are there any downsides of such wrappers?

Actually it is about IDFEF-changing function prologues like e.g. this one:
https://github.com/xianyi/OpenBLAS/blob/develop/kernel/arm/dgemm_kernel_4x4_vfpv3.S
And performance considerations here:
https://wiki.debian.org/ArmHardFloatPort/VfpComparison#A.22softfp.22
(count dgemm parameters and multiply by 20 - for small matrices like DSP code inline C will be faster)


PySide can not be used on 2.3

If PyQt4 is not installed, sip is also unavailable, so import fails earlier that a try/except block that sets PySide as a fallback.

This bug has been present for a long time. The exact same code is in master and nobody has noticed it before :-)
I guess very few people is using Spyder with PySide then.

I guess very few people is using Spyder with PySide then.
In Linux at least, lots of packages depends on python-pyqt4, si it tends to be installed along pyside. And in Anaconda PySide is not supported anymore (but still installable if I recall correctly).
So even people using pyside have pyqt and sip installed.

@ccordoba12 majority of people who are trying Spyder, don't know how to report bugs for it. And nobody would care to go through Github registration to report bug in a product they couldn't even start. These are all Windows users, who are not in open source at all.
I am reporting it only because I obscured this behavior in a class of students who are still using IDLE to learn Python.


About Moviechat-vicuna

I notice that you provided a new Moviechat-vicuna LLM decoder in your hugging face. However, you mention in your article that no fine-tuning was performed on the model. Is there a difference between Moviechat-Vicuna and the original LLAMA-Vicuna model?

No difference. Just for convenience.it is an applied delta version

Thank you.


chore: Rewrite tests to AVA

Fixes #832

TODO:

[ ] Main (assigned: @curtisjohnson1)

[ ] Split into multiple files

[x] External encoding
[x] Headers
[x] Request
[x] Response

Information
The original tests are in the test directory, while the new ones are in the test-new directory. We will rename it to test when done.
Please use XO code style.

@xxczaki https://github.com/avajs/ava/blob/master/docs/recipes/es-modules.md

@tinovyatkin Thanks, to support Node.js 10 & 12 I used the esm package.

@tinovyatkin Thanks, to support Node.js 10 & 12 I used the esm package.

Hmm. Remember that c8 doesn't work well with esm. I don't really understand why to introduce a dependency and test transpired code on 10 and 12 where we currently are testing original sources?

The ESM package is used only for AVA. I can add the experimental modules flag instead, but I'm not sure if that works on Node.js 10.

The ESM package is used only for AVA. I can add the experimental modules flag instead, but I'm not sure if that works on Node.js 10.

Flag works, see our current tests

Ok, I will replace it with a flag later today ;)

Update: all the "basic" test files are now rewritten. The only 1 left is the massive main.js.
@curtisjohnson1 Let me know if you need any help ;)

Update: all the "basic" test files are now rewritten. The only 1 left is the massive main.js.
@curtisjohnson1 Let me know if you need any help ;)

Hey @xxczaki - sorry for the delay. I'm looking to get this finished over the weekend 👍

@curtisjohnson1 Great, no need to hurry :smile:

hi @xxczaki - sorry for the delay in this. I've been working on porting the test over for the past 2 days in my spare time and I've got 25% through the main.js file so far. My tests are currently here https://github.com/curtisjohnson1/node-fetch/blob/ava/test-new/main.js. Do you want me to either point my branch to this, otherwise, I can use this branch to push commits to?

@curtisjohnson1 Thanks for letting me know about the progress! Doesn't matter, you can use your branch or this one - just make sure to point it when you finish.


[Improvement][Log] Use RollingFileAppender to set the task instance log max size

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

do you want to fix it by yourself or want to volunteer?

do you want to fix it by yourself or want to volunteer?

This can be a good first issue.

I want to have a try, plz assign it to me.

Should we use the SizeAndTimeBasedRollingPolicy to set the maximum log file size? If so, what is the recommended name pattern and expected max file size? And when querying the log of a task instance, should we only query on the latest log file? @ruanwenjun

Should we use the SizeAndTimeBasedRollingPolicy to set the maximum log file size? If so, what is the recommended name pattern and expected max file size? And when querying the log of a task instance, should we only query on the latest log file? @ruanwenjun

Yes, we can use SizeAndTimeBasedRollingPolicy  and set the maxFileSize

So, that means we need to change the log full path pattern from {log.base}/{taskSubmitTime}/{workflowDefinitionCode}/{workflowDefinitionVersion}/{workflowInstance}/{taskInstance}.log to {log.base}/{taskSubmitTime}/{workflowDefinitionCode}/{workflowDefinitionVersion}/{workflowInstance}/{taskInstance}/，and under this path we have latest.log and other history log files named after time and sequence, right?

Am I understanding correctly? @ruanwenjun

So, that means we need to change the log full path pattern from {log.base}/{taskSubmitTime}/{workflowDefinitionCode}/{workflowDefinitionVersion}/{workflowInstance}/{taskInstance}.log to {log.base}/{taskSubmitTime}/{workflowDefinitionCode}/{workflowDefinitionVersion}/{workflowInstance}/{taskInstance}/，and under this path we have latest.log and other history log files named after time and sequence, right? @ruanwenjun

This seems more complicated than I thought, I hope we have a way to keep the log in one file, by the file has max size.
Maybe we need to write our own appender?

This seems more complicated than I thought, I hope we have a way to keep the log in one file, by the file has max size. Maybe we need to write our own appender?

What is supposed to do when the file reach the max size? Just let the file rewritten by new content? @ruanwenjun

This seems more complicated than I thought, I hope we have a way to keep the log in one file, by the file has max size. Maybe we need to write our own appender?

What is supposed to do when the file reach the max size? Just let the file rewritten by new content? @ruanwenjun

We can stop writing when reach the max size.


Fix traces receiver for Grafana Agent

After some testing with the agent, a few things were not working, this PR fixes:

Generation of Span and Trace IDs
Set Resource Attributes
Added more tests to verify that those steps are not missing.

Codecov Report
Attention: Patch coverage is 9.67742% with 28 lines in your changes are missing coverage. Please review.

Project coverage is 67.47%. Comparing base (28cb938) to head (a6e23d2).
Report is 6 commits behind head on main.

Files
Patch %
Lines

pkg/internal/export/grafana_agent/traces.go
0.00%
28 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #690      +/-   ##
==========================================
- Coverage   76.92%   67.47%   -9.45%
==========================================
  Files          96       94       -2
  Lines        8016     7995      -21
==========================================
- Hits         6166     5395     -771
- Misses       1510     2193     +683
- Partials      340      407      +67

Flag
Coverage Δ

integration-test
67.47% <9.67%> (-0.44%)
:arrow_down:

unittests
?

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Anonymous access

Hi! Is it possible to send email through server that does not require authentication? I am getting
{ [Error: Invalid login]
  code: 'EAUTH',
  response: '504 5.7.4 Unrecognized authentication type ',
  responseCode: 504 }

every time I try to send email

If auth option is not set, then authentication is not used.