text:
Duplicate K8s API Logs

We have an issue where we are collecting api logs twice. This is because our K8s API servers are deployed a containers on the control plane. Therefore, fluentd collects the container logs from /var/log/containers and because of this source https://github.com/SumoLogic/fluentd-kubernetes-sumologic/blob/master/conf.d/file/source.kubernetes.conf#L74 fluentd collects the api server logs from a log file. This is a problem since it significantly increases our intake and we're hitting overage fees.
We can do the following but none are ideal:

We could add the path to the api server logs in our EXCLUDE_PATHS env var. However, I prefer those logs since they are enriched with Kubernetes metadata, which makes them much more useful for debugging
We could fork the repo and make the necessary changes ourselves. I think the solution would be beneficial to more than us.

Maybe there is something else I can do?

@salilgupta1 thank you for the issue.  I agree 1 is not ideal, we need a better way to solve this to prevent the duplication.  Let me see what I can do here.

@salilgupta1 ok wanted to give you an update on this issue.  In order to prevent this duplication, and ensure the logs we capture have all the enriched metadata, I am going to remove the duplicated sources from the appropriate configs.  However, this constitutes a breaking change as 1) some folks may be using those log lines and 2) our current Kubernetes app uses these log lines and not the container log lines.
So the plan to address this is the following:

I will work on fixing our application to use the container log lines instead of the current source.  There are some parsing changes that need to happen as the log format is slightly different.

When the app changes are done, I will fix the FluentD plugin to remove these duplicated sources and cut a major release for the plugin (v2.0.0).

@frankreno any updates on your end here? Could we release this fix and then you all can migrate your Kubernetes integrations onto the new version?

@salilgupta1 I apologize for the delay.  We will be pushing the changes out in the next couple of days.

This has been fixed in v2.0.0

repo: SumoLogic/fluentd-kubernetes-sumologic


text:
Add action limit explanation

Purpose of this pull request
This pull request (PR) adds a couple of new sections, and in the process sneaks in an explanation of action limit:
https://help.sumologic.com/docs/cse/automation-service/automation-service-app-central/
Issue number: None. Done at the request of @pkazmir-sumo.

Select the type of change:

[ ] Minor Changes - Typos, formatting, slight revisions
[x] Update Content - Revisions and updating sections
[ ] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, and new packages for the site, Gatsby, React, etc

Thanks, @JV0812!

source: gharchive/pull-request

repo: SumoLogic/sumologic-documentation

license: MIT

license_type: permissive

license_source: github-api


text:
Update faq.md

Add FAQ statement
Purpose of this pull request
This pull request...
Select the type of change

[ ] Minor Changes - Typos, formatting, slight revisions
[x] Update Content - Revisions, updating sections
[ ] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - .clabot, version updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

Ticket (if applicable)

@wjakelee, I suggest changing "Sumo UI" to "Sumo Logic UI". The "Voice and tone" section in our style guide says:

Our brand guideline is to always refer to “Sumo Logic”, rather than Sumo.


text:
In LostInfoBrowsing, mAdapter changes in backgroud thread error.

If click the item early(before lostInfoList finished), this error will come out.

To avoid the item to be clicked early, I added a ProgressDialog.

source: gharchive/issue

repo: SunGoodBoy/EasyEcard

license_source: bigquery


text:
Improve runtime and peak memory usage of PVEngine.run_full_mode

This PR does two things:

As discussed in #134, the majority of the runtime of PVEngine.run_full_mode is in the matrix inversion.  However, especially for large simulations, using a sparse linear solve function turns out to be significantly faster than explicitly inverting the full matrix. This replaces the linear algebra operations from numpy.linalg with sparse equivalents from scipy.sparse.linalg.
PVEngine.run_full_mode creates many large matrices, most of which are only needed in certain parts of the function.  This results in significant (GBs) memory usage for large simulations.  Especially for large simulations, including del statements when these large matrices are no longer needed reduces maximum memory usage significantly.

Here are some runtime and peak memory comparisons of a typical call to the pvlib wrapper function (pvlib.bifacial.pvfactors_timeseries in v0.9.0).  All values are the ratio of this PR to v1.5.2, so e.g. a value of 0.67 means this PR runs in 2/3 the time, or uses 2/3 the memory, relative to v1.5.2.
Runtime ratio:
n_timestamps  100    1000   5000   10000
n_pvrows
3              0.91   0.77   0.81   0.80
5              0.61   0.41   0.31   0.39
7              0.60   0.40   0.30   0.34

Peak RAM usage ratio:
n_timestamps  100    1000   5000   10000
n_pvrows
3              0.99   0.84   0.67   0.63
5              0.97   0.67   0.60   0.59
7              0.75   0.61   0.58   0.58

The above ratios, especially the peak memory values, are relatively stable on my machine.  Timing is rather less stable; reducing external CPU load as much as possible and setting the power mode to "best battery" (in an attempt to disable CPU turbo boost and such) seems to help.  I would be very interested to see if others can recreate the above results, especially on the timing side -- @spaneja kindly ran some for me earlier and the results were not wholly consistent with what I've shown above.
Miscellaneous to-do:

[x] take a closer look at where memory is allocated and where it is used; the current del situation is probably still suboptimal
[x] what's new
[x] tests?
[x] make scipy an explicit dependency (right now it's implicit via pvlib)
[x] document _sparse_solve
[ ] ...and maybe put it somewhere that makes more sense?
[ ] consider making the sparse approach opt-in via a boolean kwarg or similar?

I suppose this is ready for review!  Open questions:

The private sparse solve function seems a bit out of place in engine.py; should it live somewhere else?
Should the new sparse approach be made opt-in somehow?
An alternative to using del is to break up run_full_mode into small functions where the intermediate arrays created in each sub function go out of scope when that function finishes.  I think sub functions is probably the more pythonic approach, but it would be a bigger change than just throwing in a few dels.  Any preference?
Most importantly: can other people replicate the runtime and memory improvements I'm seeing locally?

I suppose this is ready for review!  Open questions:

The private sparse solve function seems a bit out of place in engine.py; should it live somewhere else?
Should the new sparse approach be made opt-in somehow?
An alternative to using del is to break up run_full_mode into small functions where the intermediate arrays created in each sub function go out of scope when that function finishes.  I think sub functions is probably the more pythonic approach, but it would be a bigger change than just throwing in a few dels.  Any preference?
Most importantly: can other people replicate the runtime and memory improvements I'm seeing locally?

If you can permute the matrix so that the non-zero elements are close to the diagonal axis you can further improve the computation simplicity. Although I believe most sparse solvers will try to permute the matrix automatically.

scipy.sparse.linalg.spsolve seems to include automatic column permuting but I didn't think I was qualified to try to do better than the default :)  For reference, here's what a typical slice of a_mat looks like (color means nonzero):

Passing empty timeseries inputs currently works on master but didn't work here; 480b350 fixes that and adds a relevant test.  Not sure how valuable it is to support that use case, but might as well if it's easy...

Ping @campanelli-sunpower -- these changes would be nice to have in the main branch for a project @spaneja and I are doing, any chance this could get merged soonish?

Putting this back to draft -- after further experimentation I'm no longer confident that this PR is the best approach.  I will continue the discussion back in #134.

repo: SunPower/pvfactors


text:
이벤트의 진행방식

단발성 이벤트
아주 간단한 이벤트로 별도의 선택지가 존재하지 않습니다.
예시 1
당신은 길을 가던 중 돌부리에 발이 걸려 넘어졌습니다.
체력이 1 감소합니다
예시 2
당신은 길에 떨어져 있는 나이프를 주웠습니다.
나이프(아이템) 1개 인벤토리에 추가
선택지형 이벤트
1개 이상의 선택지가 있습니다.
또한 한 이벤트 내에서 선택지를 고르는 순간이 여러 번 있을 수 있습니다.
예시 1
당신은 탐사를 진행하던 중, 길거리를 배회하는 좀비 한 마리를 발견했습니다.
좀비를 사냥하고 탐사를 이어가거나, 길을 조금 돌아갈 수도 있겠죠.
선택지 1: 싸운다
선택지 2: 조용히 돌아간다
선택지 1 선택 시
확률적으로 전투 승패를 결정
전투 승리: 당신은 좀비와의 전투에서 승리했습니다.  (일정확률로 아이템 드랍, 해당 아이템 취득 여부 결정 가능)
전투 패배: 당신은 좀비에게 큰 공격을 당했고, 그대로 도망칩니다. 다행히도 좀비가 쫓아오지는 않는군요.
체력이 5 감소했습니다.
선택지 2 선택 시
당신은 조금 돌아가기로 합니다. 좀비는 당신을 알아채지 못했습니다.
아이템에 관한 초기 구상
아이템은 플레이어가 고를 수 있는 선택지를 확장시키는 요소입니다.
게임 내에서 플레이어가 아이템을 직접적으로 사용하는 경우는 없을 것입니다.(예: 구급상자를 사용하여 체력회복) 이는 특정 상황에서 아이템 남용을 막기 위한 장치입니다.
이 의도를 아래의 이벤트로 예를 들겠습니다.
아이템이 플레이어의 선택지를 확장시키는 경우
당신은 한 주택 앞에 멈춰섰습니다.
주택의 문은 잠겨있습니다.
1 (아이템: 빠루 소지 시) 문을 강제로 연다 (본 선택지는 아이템이 없으면 표시되지 않습니다)
2 돌아간다.
1을 선택한 경우
당신은 문을 여는 데 성공했고 주택을 탐사합니다.
게임 내에서 플레이어가 아이템을 직접적으로 사용하는 경우는 없는 이유
플레이어가 언제든 원할 때마다 아이템을 사용하는 것은 게임의 긴장감을 떨어뜨린다고 판단했습니다.
연속된 전투를 치른다면 상처를 돌볼 시간이 없을 것입니다. 그런데 언제든 아이템을 사용하는 것을 적절치 않다고 생각했습니다. 또한 탐사 도중 다쳤다 해도 그 자리에서 바로 상처를 처치할 수 없는 경우도 있겠죠. 즉, 상처에 대한 처치를 할 수 있는 상황이어야 한다는 겁니다. 따라서 '처치가 가능한 상황'을 이벤트로 구현하고자 하였습니다.
개발자는 플레이어에게 특정한 상황이 진행되도록 강요해야 합니다. 또한 플레이어는 진행되는 상황 속에서 자신이 고를 수 있는 최선의 선택을 할 뿐이죠. 게임을 일시 중지하고 아이템을 사용하는 상황은 있어선 안된다고 생각했습니다.
몇가지 예시를 들겠습니다.

현재 체력이 n 이하인 경우, 체력 회복 이벤트 발생.

체력 회복을 위한 이벤트
(단, 체력을 회복했음에도 체력이 n 이하인 경우, 그 다음 이벤트에 "체력 회복을 위한 이벤트"가 바로 발생하지 않음. 최소한의 발생 주기를 가짐.)
당신의 몸 상태가 좋지 않습니다.
여러 부상이 겹친 탓에 몸이 너덜너덜한 상태입니다.
1.(구급상자 소지) 구급상자를 사용한다(체력 10 회복, 상태: 출혈, 상태: 골절 제거)
2.(붕대 소지) 붕대를 감는다(체력 5 회복, 상태: 출혈 제거)
3. 아무 것도 할 수 없다.

특정 상태에 대한 이벤트

중독을 예시로 들겠습니다.
중독:[레벨] : 3개의 이벤트에 한 번 "중독에 대한 이벤트" 발생, 해당 이벤트에서 중독 제거 실패 시 [레벨]만큼 체력 감소.
중독에 대한 이벤트
당신은 중독된 탓에 몸이 말을 듣지 않습니다.
어떻게든 처치를 해야합니다.
1.(아이템:해독제 소지)해독제를 먹는다 .(상태: 중독 제거)
2. 방치한다. (체력이  중독의 [레벨]만큼 감소, 3개 이벤트 후 다시 중독에 대한 이벤트 발생)

아이템 사용에 제약을 두는 방식에 대해
언제든 아이템울 사용할 수 있으나, 특정 이벤트에서만 어이템 사용을 금지하는 방식 또한 구상한 구조 중 하나입니다.

게임 내에서 플레이어가 아이템을 직접적으로 사용하는 경우는 없는 이유 <-- 부분의 의견인데

포x몬 처럼 전투에 들어갈 시 턴제 형식으로 진행 될 경우 -> 플레이어는 공격, 방어, 소지품사용 등 선택지가 주어질거고 그에 따라 전투중에도 자신의 한 턴을 소지품 사용 내의 회복 아이템 사용, 헤독제 사용 등으로 해결 할 수 있다고 생각.

예시 1
당신은 탐사를 진행하던 중, 길거리를 배회하는 좀비 한 마리를 발견했습니다.
좀비를 사냥하고 탐사를 이어가거나, 길을 조금 돌아갈 수도 있겠죠.

선택지 1: 싸운다
선택지 2: 조용히 돌아간다  <-- 부분에서 돌아간다를 선택하게 되면 다음 선택지가 등장할 것 ( 턴제 형식이니 )
ex) 갈림길이 나타났다 어디로 행할까 1. 왼쪽, 2. 오른쪽, 이와같이 새로운 선택지가 등장할텐데 그 선택지를 고르는 과정에서도 전에 선택지를 한 번 더 주는 방식.
ex) (선택지)1.이동한다.  2.소지품을 사용한다. 3. 저장하기 -> 갈림길이 나타났다 어디로 행할까? 1. 왼쪽, 2. 오른쪽 (선택지) -> 1. 왼쪽으로 행했더니 이미 누군가 왔다간듯한 편의점이 있다 어떻게 할까? (선택지)
와 같이 플레이어의 행동을 직진방식, 무조건 진행만이 아닌 소지품을 사용하거나, 무언가 이벤트로 인해 위기가 발생할 것 같은 대목이 나온다면 저장을 할 수도 있는 방식으로 진행한다. 소지품에는 회복과 상태회복 뿐만이 아닌 라디오듣기와 같은 방식으로 힌트를 획득할수도 있는 방식으로. 단, 저장은 플레이어의 플레이 내에서 횟수 제한을 걸어두는 것.
저장 기능을 생각한건 전에 회의에서 나왔던 의견 중 턴제게임인데 계속 죽을 때마다 하드리셋은 너무 가혹할 수도 있기 때문
왜 이런 의견을 생각했냐하면 지금 1번의 방식이 아닌 2번 그냥 전투를 진행하면 바로 결과가 나오는 방식으로 기획한 거 같은데 만약 이러면 hp가 30 이하에서 체력 회복 이벤트가 발생한다는 가정에서 전투를 진행했는데 31의 데미지를 입어버리면 hp회복 이벤트를 못 거치고 바로 죽는 엔딩이 될 수 있기 때문,
그저 의견일 뿐이니 혹시 제 의견에 대한 의견 있으면 남겨주시면 감사하겠습니다~

게임 내에 전투 방식
게임의 전투 방식은 '플레이어가 때린다','스킬을 쓴다'와같은 항목이 있는 게 아니라
싸운다 -> 1의 체력이 닳았다. 가지고 있던 ' '을 얻었다.
이런 식으로 진행 될 것 같습니다. 전투 방식을 넣는 다면 더욱 좋겠지만 시간이 부족할 것 같습니다.
아이템 사용 방식
아이템을 바로바로 사용하는 게 긴장감을 떨어트린다는 의견이 있는 데 이건 아이템의 유형이나 게임의 진행방향에 따라 다를 것 같습니다. 예를 들어 회복 물품를 쓸 수 있는 이벤트가 몇 주기에 한번씩 일어난다고 하면 어떤 상황에서 전투를 할지,도망칠지 선택하는 과정으로 긴장감이나 선택지를 고민하게 하는 재미가 될 수 있습니다. 하지만 쉘터로 돌아 올 때 휴식을 취하면서 체력을 회복한다거나 가방에 자리가 부족하다던지라는 상황으로 방해가 되는 요소가 될 수 있고 이떤 특정한 이벤트가 생겨 갑자기 회복상자를 사용할 수 있다거나 붕대를 사용할 수 있는 상황이 생기는 게 부자연스럽습니다. 그래서 아이템의 사용 방식에 대해서는 2가지를 생각해 보는 것이 좋을 것 같습니다.
이벤트 종류
이벤트 종류를 나눠 제작하는 게 좋을 듯합니다.
단발성 이벤트(회복,불운,아이템,동료,전투 등등 하나의 이벤트로 끝나는 경우)
연발성 이벤트(전 이벤트를 기억해 특별한 이벤트가 진행되는 경우 예를 들어 전에 도와준 사람이 ' '을 가지고 왔다 등등)
엔딩성 이벤트(엔딩 관여하는 이벤트)
지금 생각하는 종류는 이정도이며 전부 제작할 필요도 없고 단발성 이벤트만 있어도 좋습니다.

왜 이런 의견을 생각했냐하면 지금 1번의 방식이 아닌 2번 그냥 전투를 진행하면 바로 결과가 나오는 방식으로 기획한 거 같은데 만약 이러면 hp가 30 이하에서 체력 회복 이벤트가 발생한다는 가정에서 전투를 진행했는데 31의 데미지를 입어버리면 hp회복 이벤트를 못 거치고 바로 죽는 엔딩이 될 수 있기 때문,

확실히 가혹할 수는 있으나 그 리스크를 감수하는 것도 재미라고 생각합니다. 하드리셋으로 하되 해당 죽음을 모면할 수 있는 부활용 아이템을 추가하는 것은 어떤가요?


text:
create: schoolNotice & edit: notice to intranetNotice and more

notice를 intranetNotice로 수정
schoolNotice 추가
notice, intranetNotice test 추가

Mistake;;


text:
Healthy refactor [Bug fixes, extensions, submission status]

THIS IS A SECOND PR FROM THIS BRANCH
CHECK THE FIRST ONE: https://github.com/SunriseCommunity/Sunrise/pull/25
Description
This PR is a merge of refactoring of smelly code (mostly talking about Database.cs), fix for some weird bugs and updated score system. Detailed information about each change below.
Fixes

Multiplayer can't be started if in progress, while nobody is playing
If user rejoins server without sending leave packet, make soft remove of previous session, to clear multi rooms, etc.
Update max combo on loved beatmaps
Don't show scores from same player on same beatmap twice in /top;
Get top scores (were used by API for user's profile) by TotalScore, not PP
Show "NC" as short mod for Nightcore
Make cache for AllUsers much safer by resetting it on any user update
Don't include restricted users in total users for API

FEATURES

Don't save duplicated beatmapsets for different pointers, make pointers point to set_id;
Add extensions as alternative to Helpers
Rewrite ScoreService.cs in Database for better readability
Init SubmissionStatus field for score model, and use it to decide if it's user's PB

MY CONCERNS
This PR is should have been JUST about refactoring, but Submission Status was forced to be introduced in this PR, so for anyone (including future me) - please recheck this PR a couple of times before merging. While I do love all changes, they could introduce critical bugs (this that you get when you don't have automated tests).
Ignoring Submission Status, everything else should be GTG, but again, careful review is needed.

Going to check this tomorrow on a light head. All comments are welcome.

LGTM 🙏

These changes were also reviewed by @ohaui, so big thumbs up to him.

repo: SunriseCommunity/Sunrise


text:
STYLE: Simplified BlueprintImpl comparison own vs other parameter values

Simplified BlueprintImpl comparison between "own" and "other" ParameterValueType objects, by using the Standard C++ Library implementation of operator!= for std::vector<std::string>.

@kaspermarstal, @FBerendsen This pull request removes a lot of code duplication and reduces "selxBlueprintImpl.cxx" by 62 lines of code, simply by using the ability to compare std::vector<string> objects by != (instead of having for loops over all vector elements).
Please have a look! I would like to merge this tomorrow.

OK, I'll just merge. It's green at Travis CI. Hope you can still have a look afterwards.

repo: SuperElastix/SuperElastix


text:
Added coins is not appearing on the coin list after login once close the application.

Steps To Reproduce:

Open the application.
Click on 'Activate Coin' button.
Select a coin [KMD] and click on 'Activate Coin' button.
Enter the 'wallet seed', and click on 'Sign in' button.
Now, click on 'Activate Coin' button on top of the right.
Select another coin and click on 'Activate coin' button.
Logout from the app and then again login with the same seed.
Verify added coins is appearing on the coin list.
Repeat the steps 5, 6 and 7 and verify added wallets is appearing on the coin list.
Now, close the application and again login with the same seed.
Verify the result.

Expected Result:
Added coins should be appeared on the coin list.
Actual Result:
Added coins is not appearing on the coin list after login once close the application.
Please consider the screencast url:
http://www.screencast.com/t/cFgnfza4yV2Q

10.Now, close the application and again login with the same seed.

Totally expected behaviour. Not a bug.

authors: gitmegha satindergrewal

repo: SuperNETorg/Agama


text:
Help - Admin - Template variables - Missing Quote ID (quid)

https://help.superoffice.com/Documentation/Help/EN/CRM/WebHelpAdmin/index.htm#t=Template_variables.htm
In the header for: Variables for Quote info
We need to add the variable for Quote ID = quid

@kirstiaa Quote ID added to the Template variables reference page https://docs.superoffice.com/document/templates/variables/for-quote-info.html. Should I keep this Issue open so it is also added to the Help - Admin - Template variables reference?

Yes, @pavlas77 Martin, please keep it open since there are multiple assignees here :)
I'll add a little more data in the description

Updated in RoboHelp (User/Admin) and GitHub

authors: kirstiaa pavlas77 thaugholt

repo: SuperOfficeDocs/superoffice-docs


text:
🛑 Matrix Federation Tester is down

In 1a884e6, Matrix Federation Tester (https://federationtester.matrix.org/api/report?server_name=supersandro.de) was down:

HTTP code: 200
Response time: 11003 ms

Resolved: Matrix Federation Tester is back up in ff2dfe3 after 12 minutes.


text:
🛑 Matrix Federation Tester is down

In b6582b4, Matrix Federation Tester (https://federationtester.matrix.org/api/report?server_name=supersandro.de) was down:

HTTP code: 200
Response time: 3038 ms

Resolved: Matrix Federation Tester is back up in 13cf460 after 2 hours, 35 minutes.


text:
[Doc] 01. 목표 구체화

[x] a. 우리가 만들고자 하는 것
[x] b. 이 서비스가 도우려고 하는 것
[x] c. 이 서비스가 도움이 되려면

https://github.com/Supply-Chain-Management-PFC/SCM_BE/wiki/[Doc]-01.-목표-구체화-%2301


text:
Is tmux necessary? Does surreal support Windows?

Surreal framework does leave me a deep impression.
Is tmux a necessary requirement?
Does surreal support Windows?
Looking forward to see surreal growing.
Thank you.

Tmux is not strictly required as you can go straight to setup on a kubernetes cluster. However it is recommended since being able to run code locally helps faster iteration.
We only support Mac and Linux.

authors: forhonourlx jirenz

repo: SurrealAI/surreal


text:
fix: return typename by default

issue: https://github.com/SurveyMonkey/graphql-ergonomock/issues/104
Problem: ergonomock() only includes __typename if the query does
For the fix, I borrowed the addTypenameToDocument helper function from @apollo/client. As the result, every query will have __typename auto-appended if applicable.
That being said, I don't like that we introduced vendor specific dependency in the mock function. However, I also don't want to re-invent the wheel...
Please let me know if you know a better way to solve this.
cc @joual

Yeah I think using addTypenameToDocument from Apollo makes a lot of sense in this case. As per the inline comment I would suggest moving it up one level to the MockLink to stay in line with Apollo's implementation.

@joual alright, sounds good! Just one question tho, do you foresee a case where we might want to add addTypename option directly on the ergonomock function?
I'm thinking about the users that using ergonomock   instead of the MockedProvider

Actually I did more digging on this one, I don't think a fix is required, since we are already passing through addTypename to InMemoryCache which is calling the addTypenameToDocument for us.
Here are the code traces:
Passing through addTypename to InMemoryCache
https://github.com/SurveyMonkey/graphql-ergonomock/blob/master/src/apollo/ErgonoMockedProvider.tsx#L41
QueryManger calling

Apologies, I have not noticed this PR!

I think @jfulse wants to have the addTypename option added directly to the ergonomock function.
From the issue description, seems like he is using the MockedProvider from apollo rather than ErgonoMockedProvider.

That is correct, that was my original request, and I was indeed using apollo's MockedProvider, not realising that my issue with ErgonoMockedProvider was that I had custom scalars. Thanks to your great work it seems that might soon no longer be an issue though!

I'm merging this PR since it's only containing the test cases for addTypename. I believe this is useful for us to prevent regressions in the future.
The fix for the actual issue (custom scalar type) is tracked under a seperate PR https://github.com/SurveyMonkey/graphql-ergonomock/pull/113

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: jfulse joual victor-guoyu

repo: SurveyMonkey/graphql-ergonomock


text:
black or transparent background

Can you, please, pinpoint what to set in the style sheet to have transparent (or black) background for the embedded graph? I prefer changing this linear-gradient to black.

Unfortunately, Boom Theme changes the look of the Dashboard only, the embedded graph's background remains gradient.
I know it's out of your module's focus, but after 5 hours of digging the code I'm pretty much lost.

any hints?

repo: SvenSommer/MMM-GrafanaChart


text:
Update index.js with typo fix

Found a typo

Are you sure about that, @NullableInt ? :)

Fixed by #361

authors: NullableInt VikingTristan pthoang


text:
Tweet button on mobile

There is no tweet button on the speakers sites, only a link with the text "Tweet" which is positioned weirdly.

Which platform is this on? Looks good on Chrome/Safari on iOS at least.

Firefox on Android

tweet button removed on the new speaker site that are about to be publiched

authors: SiggeSax andlju ceciliasharp

repo: Swetugg/swetugg-web

license: mit


text:
Operation and OperationQueue Tutorial in Swift

推荐收录 / 意见反馈
请将您认为的有价值的信息、资讯、文章、工具、代码、音视频资料等以链接的形式提交给我们，我们会尽快处理。记得写上推荐的理由哦。如果有任何意见或建议也可以提交给我们，按下方对应提示填写即可，♥
链接
https://www.raywenderlich.com/190008/operation-and-operationqueue-tutorial-in-swift
理由
详细介绍swift中的operation和operationqueue的用法
意见反馈（可选）
[此处填写您对我们周报的意见或建议]

一个使用 Operation 和 OperationQueue 的教程，Operation & OperationQueue 相比 GCD 而言，可以在 Operation 之间添加依赖关系决定它们的执行顺序，并且可以取消暂停和恢复.作者利用这些特性，来改善一个图片列表页的体验。将图片的下载及加工添加到 OperationQueue 中。在列表页开始滑动时，暂停所有的 OperationQueue，停止滚动时，恢复 OperationQueue，并取消掉屏幕外 cell 的 Operation,启动屏幕内 cell 的 Operation，提升了列表页滑动的流畅度。

repo: SwiftOldDriver/iOS-Weekly


text:
Options not visible with cornerRedius

Hi,
When I set corner radius of cell then options not visible for me, could you please check the same?
Thanks

very helpful post , you are the best of mine.

We were experiencing the same issue

authors: JerilynHebert joshgare sureshpatel-cnpl

repo: SwipeCellKit/SwipeCellKit


text:
resource control adegano

feat: resource access control rfc
grammar pass
add notes
[wip] refactoring
fill last 3 sections and remove input YAML as it is confusing and will not be used

If you do not like the yaml representation of the postgres data then here is a bullet point list that we can use instead.
quota:

cpu
memory
gpu
storage

resource pool:

name
users (list of keycloak user IDs that have access to the specific resource pool)
classes (list of references to a resource class or a list of resource classes)
quota (reference to a quota or the content of quota)

resource class:

name
cpu
memory
gpu
storage

resource pool:
* name

* users (list of keycloak user IDs that have access to the specific resource pool)

* classes (list of references to a resource class or a list of resource classes)

* quota (reference to a quota or the content of quota)

I think users <> resource-pool is a many-to-many relation and as such needs a separate mapping table

authors: Panaetius aledegano olevski


text:
v0.10.3 DDay event bugs

DDay event siren is too louder.
DDay was triggered in Vow and March only, after it, event and siren's sound kept triggering in other moons and even with the ship in orbit.
Host and users' mod console thrown errors indicating that DDay event's explosion sound couldn't be played and loops in that error, making fps drops.

Maybe these clips can help:
https://youtu.be/cf6z6m894mU
https://youtu.be/pfQKOw0j7o0

If possible can you give the full log file

Should be fixed in next release, if this still persists reopen this issue.

authors: ByakkoSamma Sylkadi

repo: Sylkadi/BrutalCompanyMinus


text:
If there someone could tell me how to install fasm in windows?

`
running build
running build_py
running egg_info
writing fasm.egg-info\PKG-INFO
writing dependency_links to fasm.egg-info\dependency_links.txt
writing entry points to fasm.egg-info\entry_points.txt
writing requirements to fasm.egg-info\requires.txt
writing top-level names to fasm.egg-info\top_level.txt
reading manifest file 'fasm.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
no previously-included directories found matching 'docs_*'
no previously-included directories found matching 'docs\env'
warning: no previously-included files matching '.git' found anywhere in distribution
warning: no previously-included files found matching '.gitmodules'
warning: no previously-included files found matching 'update_version.py'
no previously-included directories found matching 'third_party'
no previously-included directories found matching '.github'
no previously-included directories found matching 'pycache'
writing manifest file 'fasm.egg-info\SOURCES.txt'
running build_ext
-- The C compiler identification is GNU 10.2.0
-- The CXX compiler identification is GNU 10.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - failed
-- Check for working C compiler: /mingw64/bin/cc.exe
-- Check for working C compiler: /mingw64/bin/cc.exe - works
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - failed
-- Check for working CXX compiler: /mingw64/bin/c++.exe
-- Check for working CXX compiler: /mingw64/bin/c++.exe - works
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at CMakeLists.txt:34 (find_library):
Could not find ANTLR4_RUNTIME using the following names: antlr4-runtime
-- Configuring incomplete, errors occurred!
See also "/c/userdata/code/EDA/symbiflow/env/fasm/build/temp.win-amd64-3.8/Release/CMakeFiles/CMakeOutput.log".
See also "/c/userdata/code/EDA/symbiflow/env/fasm/build/temp.win-amd64-3.8/Release/CMakeFiles/CMakeError.log".
Failed to build ANTLR parser, falling back on slower textX parser. Error:
Command '['cmake', 'C:\userdata\code\EDA\symbiflow\env\fasm\src', '-DCMAKE_INSTALL_PREFIX=C:\userdata\code\EDA\symbiflow\env\fasm\build\lib.win-amd64-3.8\fasm/parser', '-DCMAKE_LIBRARY_OUTPUT_DIRECTORY=C:\userdata\code\EDA\symbiflow\env\fasm\build\lib.win-amd64-3.8\fasm/parser', '-DPYTHON_EXECUTABLE=C:\software\miniconda3\python.exe', '-DANTLR_RUNTIME_TYPE=shared', '-DCMAKE_BUILD_TYPE=Release']' returned non-zero exit status 1.
Traceback (most recent call last):
File "setup.py", line 103, in run
super().run()
File "C:\software\miniconda3\lib\site-packages\setuptools\command\build_ext.py", line 79, in run
_build_ext.run(self)
File "C:\software\miniconda3\lib\distutils\command\build_ext.py", line 340, in run
self.build_extensions()
File "C:\software\miniconda3\lib\distutils\command\build_ext.py", line 449, in build_extensions
self._build_extensions_serial()
File "C:\software\miniconda3\lib\distutils\command\build_ext.py", line 474, in _build_extensions_serial
self.build_extension(ext)
File "setup.py", line 185, in build_extension
subprocess.check_call(
File "C:\software\miniconda3\lib\subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['cmake', 'C:\userdata\code\EDA\symbiflow\env\fasm\src', '-DCMAKE_INSTALL_PREFIX=C:\userdata\code\EDA\symbiflow\env\fasm\build\lib.win-amd64-3.8\fasm/parser', '-DCMAKE_LIBRARY_OUTPUT_DIRECTORY=C:\userdata\code\EDA\symbiflow\env\fasm\build\lib.win-amd64-3.8\fasm/parser', '-DPYTHON_EXECUTABLE=C:\software\miniconda3\python.exe', '-DANTLR_RUNTIME_TYPE=shared', '-DCMAKE_BUILD_TYPE=Release']' returned non-zero exit status 1.
`

After install java,and the error just like https://github.com/SymbiFlow/fasm/issues/65
I found that it use the env of mysys,and I change the env to vs,error happened just like here:
Failed to build ANTLR parser, falling back on slower textX parser. Error:  Command '['cmake', '--build', '.', '--config', 'Release']' returned non-zero exit status 1. Traceback (most recent call last):   File "setup.py", line 103, in run     super().run()   File "C:\software\miniconda3\lib\site-packages\setuptools\command\build_ext.py", line 79, in run     _build_ext.run(self)   File "C:\software\miniconda3\lib\distutils\command\build_ext.py", line 340, in run     self.build_extensions()   File "C:\software\miniconda3\lib\distutils\command\build_ext.py", line 449, in build_extensions     self._build_extensions_serial()   File "C:\software\miniconda3\lib\distutils\command\build_ext.py", line 474, in _build_extensions_serial     self.build_extension(ext)   File "setup.py", line 189, in build_extension     subprocess.check_call(   File "C:\software\miniconda3\lib\subprocess.py", line 364, in check_call     raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['cmake', '--build', '.', '--config', 'Release']' returned non-zero exit status 1

repo: SymbiFlow/fasm

license: isc


text:
feat(error): Use the icon from .tk-validation__errors

Description

Use the generated icon from .tk-validation__errors

Demo

Will merge the change in the other PR : https://github.com/SymphonyPlatformSolutions/symphony-ui-toolkit/pull/402


text:
[CS] Add test case for #855

See #855 .
Hope I got it right :). Both wrong and fixed are the same files, because the expected behavior is the file will be left untouched by the Sniff.

Perfect, thanks. I'm on it

authors: OndraM TomasVotruba

repo: Symplify/Symplify


text:
testsettings.json files should be automatically copied to output directory

Currently, users must manually adjust the csproj file of the test project to copy the testsettings.json and testsettings.Development.json file to the output directory. We should include a corresponding target in the NuGet package.

@andreas-koenig Perhaps you can do this task, too?
https://docs.microsoft.com/en-us/nuget/concepts/msbuild-props-and-targets


text:
Debug log: Connect to self before connecting to other controller

Tyler Longwell: could we add a check to the ftl-controller startup that makes sure it can talk to itself over its dns name before it tries to talk to its peer?

This should make sure that istio is up and running before we try connecting to the peer.
We will log a debug log on success, error log on failure

Closing, will try a istio option first


text:
Add timeline events for async calls

Include cron, fsm, pubsub
From @wesbillman: add specific types for cron, fsm, pubsub instead of a single async_call type.
Relates to #1260

We're already recording the call event when a call is executed, including via the async mechanisms. Some async specific events that might make sense:

cron_scheduled when a cron job is added to async_calls
fsm_start on fsm start state
fsm_transition on fsm state transitions
topic_publish on publish to a pubsub topic


text:
Add Ability to have Encryption for ORM and ODM at the same time

I use it for both entities and documents, but have not tested the update command.

Just now also fixed a bug when the entity is persisted multiple times

@wodka, Sorry for the LONG delayed response, and thanks for making these changes.  I am reviewing the PR, and I noticed a few things.

You added listeners on a bunch of Doctrine events.  This seems repetitive.  Why?
I am concerned that using both services simultaneously will cause conflicts with the default ObjectManager functionality.  I admit I have not tested this theory yet.  Thoughts?

Hi @westinpigott

I added those to decrypt the model after saving - without that you will not have access to the data after the persist
I'm using it for entities and documents at the same time - till now no problems appeared.

OK.  I merged it.  I am in the process of changing the way the listeners are fired for Issue #16, so those parts will change.

authors: westinpigott wodka

repo: TDMobility/DoctrineEncryptBundle


text:
it seems not work for windows

i install it in windows but after i run flask shell i can't input any thing, i tried with powershell and cmd,both have of them has the same problem

Hi.
Thank you for raising the issue.
Do you happen to have any screenshots of the issue, or a way to reproduce it?
Do you have the virtual environment enabled?

i tried this in windows10, and it worked. I'd definitely like to help you solve the problem. :)

pip list
Package                Version
---------------------- ---------
alembic                1.12.0
apispec                6.3.0
appdirs                1.4.4
arrow                  1.2.3
asttokens              2.4.0
backcall               0.2.0
blinker                1.6.2
certifi                2023.7.22
cffi                   1.15.1
charset-normalizer     3.2.0
click                  8.1.7
colorama               0.4.6
decorator              5.1.1
exceptiongroup         1.1.3
executing              1.2.0
Flask                  2.3.3
flask-apispec          0.11.4
Flask-Migrate          4.0.4
flask-moreshell        0.0.2
Flask-SQLAlchemy       3.0.5
gevent                 23.7.0
greenlet               2.0.2
gunicorn               21.2.0
idna                   3.4
ipython                8.15.0
itsdangerous           2.1.2
jedi                   0.19.0
Jinja2                 3.1.2
Mako                   1.2.4
Markdown               3.4.4
MarkupSafe             2.1.3
marshmallow            3.20.1
marshmallow-sqlalchemy 0.29.0
PyJWT                  2.8.0
python-dateutil        2.8.2
PyYAML                 6.0.1
requests               2.31.0
setuptools             65.5.1
shellescape            3.8.1
six                    1.16.0
SQLAlchemy             2.0.20
stack-data             0.6.2
traitlets              5.9.0
typing_extensions      4.7.1
urllib3                2.0.4
wcwidth                0.2.6
webargs                8.3.0
Werkzeug               2.3.7
wheel                  0.38.4
zope.event             5.0
zope.interface         6.0

It seems to be working fine, but does that mean that when you type something on the keyboard in the last screenshot, nothing gets entered?

It seems to be working fine, but does that mean that when you type something on the keyboard in the last screenshot, nothing gets entered?
yes

I've installed all the packages, but I still can't reproduce the problem. If you can tell me how I can reproduce the problem, I think it will help me solve this.
Lastly, let me know if this is causing any problems.

make app.py

from flask import Flask

app = Flask(__name__)

and open terminal with venv, and try  this. load ipython, and call load_ipython with app context.
(venv) PS C:\Users\ingst\Desktop\test> ipython
Python 3.10.4 (tags/v3.10.4:9d38120, Mar 23 2022, 23:13:41) [MSC v.1929 64 bit (AMD64)]
Type 'copyright', 'credits' or 'license' for more information
IPython 8.15.0 -- An enhanced Interactive Python. Type '?' for help.

In [1]: from app import app

In [2]: from flask_moreshell import load_ipython

In [3]: with app.app_context():
   ...:     load_ipython()

this should activate ipython shell, with your flask app.

I've installed all the packages, but I still can't reproduce the problem. If you can tell me how I can reproduce the problem, I think it will help me solve this.
Lastly, let me know if this is causing any problems.

make app.py

from flask import Flask

app = Flask(__name__)

and open terminal with venv, and try this. load ipython, and call load_ipython with app context.
(venv) PS C:\Users\ingst\Desktop\test> ipython
Python 3.10.4 (tags/v3.10.4:9d38120, Mar 23 2022, 23:13:41) [MSC v.1929 64 bit (AMD64)]
Type 'copyright', 'credits' or 'license' for more information
IPython 8.15.0 -- An enhanced Interactive Python. Type '?' for help.

In [1]: from app import app

In [2]: from flask_moreshell import load_ipython

In [3]: with app.app_context():
   ...:     load_ipython()

this should activate ipython shell, with your flask app.

it works by manual load, thank you。
i use windows 11, maybe it's the reason of this.i tried powershell and cmd,it has the same problem.

It's not perfect, but I'm glad it's loading. It wasn't reproduced in the Windows 10 version, and it's sad that my current hardware doesn't support Windows 11 so I can't upgrade.
If I do update my OS, this will be at the top of my list.
Thanks for bringing this up.

It's not perfect, but I'm glad it's loading. It wasn't reproduced in the Windows 10 version, and it's sad that my current hardware doesn't support Windows 11 so I can't upgrade. If I do update my OS, this will be at the top of my list. Thanks for bringing this up.

i got the reason, i run monkey.patch_all()  before app create in wsgi.py file, i comment out the monkey.patch_all() and it works.

authors: ElfenSterben TGoddessana

repo: TGoddessana/flask-moreshell


text:
微调时提示模型路径为None

System Info / 系統信息
(myenv) root@ecs-e2fa:~/ChatGLM3/finetune_demo/chatglm3-6b# python --version
Python 3.11.7
(myenv) root@ecs-e2fa:~/ChatGLM3/finetune_demo/chatglm3-6b# nvidia-smi | grep -i cuda
| NVIDIA-SMI 535.154.05             Driver Version: 535.154.05   CUDA Version: 12.2     |
(myenv) root@ecs-e2fa:~/ChatGLM3/finetune_demo/chatglm3-6b# pip list | grep transformers
sentence-transformers     2.6.1
transformers              4.39.2
(myenv) root@ecs-e2fa:~/ChatGLM3/finetune_demo/chatglm3-6b# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.3 LTS
Release:        22.04
Codename:       jammy
Who can help? / 谁可以帮助到您？
No response
Information / 问题信息

[ ] The official example scripts / 官方的示例脚本
[ ] My own modified scripts / 我自己修改的脚本和任务

Reproduction / 复现过程
!CUDA_VISIBLE_DEVICES=1 python finetune_hf.py  data/AdvertiseGen_fix  chatglm3-6b  configs/lora.yaml
我用print检查过modelDir 传的是chatglm3-6b不是None，不知道为啥到底层代码就变None了
chatglm内部代码报错：
/root/.pyenv/versions/3.11.7/lib/python3.11/site-packages/bitsandbytes/cextension.py:34: UserWarning: The installed version of bitsandbytes was compiled without GPU support. 8-bit optimizers, 8-bit multiplication, and GPU quantization are unavailable.
warn("The installed version of bitsandbytes was compiled without GPU support. "
/root/.pyenv/versions/3.11.7/lib/python3.11/site-packages/bitsandbytes/libbitsandbytes_cpu.so: undefined symbol: cadam32bit_grad_fp32
╭───────────────────── Traceback (most recent call last) ──────────────────────╮
│ /root/ChatGLM3/finetune_demo/finetune_hf.py:461 in main                      │
│                                                                              │
│   458                                                                        │
│   459 ):                                                                     │
│   460 │   ft_config = FinetuningConfig.from_file(config_file)                │
│ ❱ 461 │   tokenizer, model = load_tokenizer_and_model(model_dir, peft_config │
│   462 │   data_manager = DataManager(data_dir, ft_config.data_config)        │
│   463 │                                                                      │
│   464 │   train_dataset = data_manager.get_dataset(                          │
│                                                                              │
│ /root/ChatGLM3/finetune_demo/finetune_hf.py:390 in load_tokenizer_and_model  │
│                                                                              │
│   387 │   │   model_dir: str,                                                │
│   388 │   │   peft_config: Optional[PeftConfig] = None,                      │
│   389 ) -> tuple[PreTrainedTokenizer, nn.Module]:                            │
│ ❱ 390 │   tokenizer = AutoTokenizer.from_pretrained(model_dir, trust_remote_ │
│   391 │   if peft_config is not None:                                        │
│   392 │   │   if peft_config.peft_type.name == "PREFIX_TUNING":              │
│   393 │   │   │   config = AutoConfig.from_pretrained(model_dir, trust_remot │
│                                                                              │
│ /root/.pyenv/versions/3.11.7/lib/python3.11/site-packages/transformers/model │
│ s/auto/tokenization_auto.py:822 in from_pretrained                           │
│                                                                              │
│   819 │   │   │   _ = kwargs.pop("code_revision", None)                      │
│   820 │   │   │   if os.path.isdir(pretrained_model_name_or_path):           │
│   821 │   │   │   │   tokenizer_class.register_for_auto_class()              │
│ ❱ 822 │   │   │   return tokenizer_class.from_pretrained(                    │
│   823 │   │   │   │   pretrained_model_name_or_path, *inputs, trust_remote_c │
│   824 │   │   │   )                                                          │
│   825 │   │   elif config_tokenizer_class is not None:                       │
│                                                                              │
│ /root/.pyenv/versions/3.11.7/lib/python3.11/site-packages/transformers/token │
│ ization_utils_base.py:2086 in from_pretrained                                │
│                                                                              │
│   2083 │   │   │   else:                                                     │
│   2084 │   │   │   │   logger.info(f"loading file {file_path} from cache at  │
│   2085 │   │                                                                 │
│ ❱ 2086 │   │   return cls._from_pretrained(                                  │
│   2087 │   │   │   resolved_vocab_files,                                     │
│   2088 │   │   │   pretrained_model_name_or_path,                            │
│   2089 │   │   │   init_configuration,                                       │
│                                                                              │
│ /root/.pyenv/versions/3.11.7/lib/python3.11/site-packages/transformers/token │
│ ization_utils_base.py:2325 in _from_pretrained                               │
│                                                                              │
│   2322 │   │                                                                 │
│   2323 │   │   # Instantiate the tokenizer.                                  │
│   2324 │   │   try:                                                          │
│ ❱ 2325 │   │   │   tokenizer = cls(*init_inputs, **init_kwargs)              │
│   2326 │   │   except OSError:                                               │
│   2327 │   │   │   raise OSError(                                            │
│   2328 │   │   │   │   "Unable to load vocabulary from file. "               │
│                                                                              │
│ /root/.cache/huggingface/modules/transformers_modules/chatglm3-6b/tokenizati │
│ on_chatglm.py:109 in init                                                │
│                                                                              │
│   106 │   ):                                                                 │
│   107 │   │   self.name = "GLMTokenizer"                                     │
│   108 │   │   self.vocab_file = vocab_file                                   │
│ ❱ 109 │   │   self.tokenizer = SPTokenizer(vocab_file)                       │
│   110 │   │   self.special_tokens = {                                        │
│   111 │   │   │   "": self.tokenizer.bos_id,                            │
│   112 │   │   │   "": self.tokenizer.eos_id,                            │
│                                                                              │
│ /root/.cache/huggingface/modules/transformers_modules/chatglm3-6b/tokenizati │
│ on_chatglm.py:17 in init                                                 │
│                                                                              │
│    14 class SPTokenizer:                                                     │
│    15 │   def init(self, model_path: str):                               │
│    16 │   │   # reload tokenizer                                             │
│ ❱  17 │   │   assert os.path.isfile(model_path), model_path                  │
│    18 │   │   self.sp_model = SentencePieceProcessor(model_file=model_path)  │
│    19 │   │                                                                  │
│    20 │   │   # BOS / EOS token IDs                                          │
│ in isfile:30                                                                 │
╰──────────────────────────────────────────────────────────────────────────────╯
TypeError: stat: path should be string, bytes, os.PathLike or integer, not
NoneType
Expected behavior / 期待表现
微调成功

使用绝对地址

authors: pencui zRzRzRzRzRzRzR


text:
Using CogVLM as an API

Feature request  / 功能建议
Hello guys,
Thank you so much for you hard work.
I was wondering if there's any way I could use CogVLM as an api so I can send some requests from my Python app just to test it. I don't have the required hardware to run a local version of it so that's why I was wondering if such feature exists or not.
Thank you

so may be you can use a server and use openai demo in this repos.  We do not provide api  of cogvlm.
you can use https://open.bigmodel.cn/ to use our commercial model api.

authors: moncefarajdal zRzRzRzRzRzRzR

repo: THUDM/CogVLM


text:
Debian base image issue

Debian package manager apt connects to http://deb.debian.org while apt-get update is run.
Azure firewall Security policy does not allow outbound http request and hence spotfire-base image is not getting created via azure DevOps pipeline.
Is there any workaround to overcome this issue?
If you suggest any other base image, please mention that as well.
Thanks,
Debasish Das

It is not common for apt-get to use HTTPS. There's a lot of threads about this online, one being https://askubuntu.com/questions/146108/how-to-use-https-with-apt-get
We use the official Debian "stable-slim" image as the base image, and this image is configured by Debian to use the HTTP repos.
Since our images are based on the Debian base images, I cannot recommend another image for you. You are however welcome to modify the docker files yourself, and experiment with other images. We have not tested other images than the Debian stable-slim image.
I would suggest looking into allowing the repo URL's through the Azure firewall. I think this will be the easiest path forward.

authors: ddasml mblixter


text:
🛑 CHECKS LATAM is down

In 59645e2, CHECKS LATAM (https://latam.tkschecks.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CHECKS LATAM is back up in b4fc5ed.

repo: TKS-IT/status-page


text:
新需求：复读机功能

像QQ一样, 在最新的消息后面增加一个+1的按钮..点了可以进行复读.
简单实现的话, 可以考虑在所有消息后面追加链接[复读], 这样就不用在UI上添加额外的元素了
然后链接处理函数里, 特殊处理一下[复读]的这个链接即可

+1

authors: Eronana kaidiren

repo: TKkk-iOSer/WeChatPlugin-MacOS


text:
Fixed behaviour on Linux

Implemented some fixes to make the tool work on Linux as well.
I slightly changed the default paths for Linux to properly utilize/encode environment variables and refined the handling for the ilspycmd installation process a bit to work on unix-based systems.
[I also added a yes/no prompt to the ilspycmd installation process and ensured that the prompt (and the installation) is only executed on the first startup of the tool]
Tested on GNU/Linux Gentoo (Kernel 5.10.27-gentoo)

Thanks! 👍

repo: TML-Patcher/TMLPatcher


text:
Dependency Graph Extractor stops on its own analysis

When running
PS C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd> .\bin\dependency_graph_extractor.exe -o dependency_graph_extractor.graphml -p C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd .\dependency_graph_extractor.gpr

One gets
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\.git
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\.github
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\.gitignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\.gitattributes
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\.github
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\.gitignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\.gitreview
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_gmp_22.0.0_f3732e5d\.gitattributes
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_gmp_22.0.0_f3732e5d\.gitignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_gmp_22.0.0_f3732e5d\.gitreview
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_iconv_22.0.0_f3732e5d\.gitattributes
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_iconv_22.0.0_f3732e5d\.gitignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_iconv_22.0.0_f3732e5d\.gitreview
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\libadalang_22.0.0_5f365aa4\ocaml\.ocamlformat
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\libgpr_22.0.0_30e39dcc\.gitattributes
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\libgpr_22.0.0_30e39dcc\.gitignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\libgpr_22.0.0_30e39dcc\.gitreview
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\libgpr_22.0.0_30e39dcc\examples\extended_projects\new_obj_util\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\libgpr_22.0.0_30e39dcc\examples\subsystems\obj\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\libgpr_22.0.0_30e39dcc\examples\subsystems\obj1\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\libgpr_22.0.0_30e39dcc\examples\subsystems\obj_util\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\.gitattributes
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\.gitignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\.gitreview
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\dom\lib\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\dom\lib\relocatable\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\dom\lib\static\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\dom\obj\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\dom\obj\relocatable\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\dom\obj\static\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\input_sources\lib\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\input_sources\lib\relocatable\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\input_sources\lib\static\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\input_sources\obj\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\input_sources\obj\relocatable\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\input_sources\obj\static\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\schema\lib\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\schema\lib\relocatable\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\schema\lib\static\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\schema\obj\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\tests\results\.gitignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\unicode\lib\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\unicode\lib\relocatable\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\unicode\lib\static\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\unicode\obj\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\unicode\obj\relocatable\.cvsignore
Skipping C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\unicode\obj\static\.cvsignore
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support.gpr --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_iconv_22.0.0_f3732e5d\iconv\gnatcoll_iconv.gpr --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_gmp_22.0.0_f3732e5d\gmp\gnatcoll_gmp.gpr --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\schema\xmlada_schema.gpr --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\dom\xmlada_dom.gpr --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\input_sources\xmlada_input.gpr --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\sax\xmlada_sax.gpr --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\xmlada_shared.gpr --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\unicode\xmlada_unicode.gpr --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\xmlada_22.0.0_b322ae27\distrib\xmlada.gpr --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\libgpr_22.0.0_30e39dcc\gpr\gpr.gpr --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\gnatcoll.gpr --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\libadalang_22.0.0_5f365aa4\libadalang.gpr --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\config\dependency_graph_extractor_config.gpr --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\dependency_graph_extractor.gpr --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-any_types.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-any_types.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-arg_lists.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-arg_lists.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-asserts.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-asserts.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-atomic.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-atomic.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-boyer_moore.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-boyer_moore.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-coders-base64.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-coders-base64.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-coders-streams.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-coders-streams.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-coders.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-coders.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-config.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-config.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-damerau_levenshtein_distance.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-damerau_levenshtein_generic.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-damerau_levenshtein_generic.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-email-mailboxes.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-email-mailboxes.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-email-parser.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-email-parser.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-email-utils.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-email-utils.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-email.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-email.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-format_columns_vertical.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-formatters.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-formatters.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-geometry.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-geometry.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-io-native-codec__win32.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-io-native.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-io-native.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-io-remote-unix.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-io-remote-unix.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-io-remote-windows.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-io-remote-windows.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-io-remote.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-io-remote.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-io.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-io.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-json-utility.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-json-utility.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-json.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-json.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-locks.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-locks.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-memory.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-memory.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-mmap-system__win32.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-mmap-system__win32.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-mmap.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-mmap.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-opt_parse.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-opt_parse.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-path.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-path.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-plugins.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-plugins__windows.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-pools.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-pools.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-projects-aux.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-projects-aux.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-projects-krunch.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-projects-krunch.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-projects-normalize.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-projects-normalize.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-projects.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-projects.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-promises.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-promises.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-refcount-weakref.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-refcount-weakref.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-refcount.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-refcount.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-remote-db.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-remote-db.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-remote.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-scripts-files.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-scripts-files.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-scripts-impl.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-scripts-impl.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-scripts-projects.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-scripts-projects.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-scripts-shell.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-scripts-shell.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-scripts-utils.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-scripts-utils.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-scripts.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-scripts.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-storage_pools-alignment.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-storage_pools-alignment.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-storage_pools-headers.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-storage_pools-headers.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-storage_pools.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-string_builders.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-string_builders.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-string_list_builders.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-string_list_builders.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-strings.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-strings_impl.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-strings_impl.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-symbols.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-symbols.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-templates.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-templates.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-terminal.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-terminal.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-traces.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-traces.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-tribooleans.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-tribooleans.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-utils.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-utils.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-vfs.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-vfs.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-vfs_types.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-vfs_utils.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-vfs_utils.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-wstring_builders.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-wstring_builders.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-wstring_list_builders.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll-wstring_list_builders.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\gnatcoll.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\gnatcoll-os-constants__windows.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\gnatcoll-os-dir-close__win32.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\gnatcoll-os-dir-open__win32.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\gnatcoll-os-dir-read__win32.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\gnatcoll-os-dir.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\gnatcoll-os-dir.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\gnatcoll-os-dir_types__win32.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\gnatcoll-os-fs-is_console__win32.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\gnatcoll-os-fs-open__win32.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\gnatcoll-os-fs-open_pipe__win32.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\gnatcoll-os-fs-set_close_on_exec__win32.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\gnatcoll-os-fs.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\gnatcoll-os-fs.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\gnatcoll-os-process-internal_spawn__win32.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\gnatcoll-os-process-state__win32.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\gnatcoll-os-process-wait__win32.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\gnatcoll-os-process-wait_for_processes__win32.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\gnatcoll-os-process.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\gnatcoll-os-process.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\gnatcoll-os-process_types__win32.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\gnatcoll-os-process_types__win32.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\gnatcoll-os-stat-stat__win32.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\gnatcoll-os-stat.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\gnatcoll-os-stat.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\gnatcoll-os.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\win32\gnatcoll-os-win32-files.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\win32\gnatcoll-os-win32-files.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\win32\gnatcoll-os-win32-process.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\win32\gnatcoll-os-win32-strings.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\win32\gnatcoll-os-win32-strings.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\win32\gnatcoll-os-win32.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\os\win32\gnatcoll-os-win32.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\paragraph_filling\gnatcoll-paragraph_filling-badnesses.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\paragraph_filling\gnatcoll-paragraph_filling-badnesses.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\paragraph_filling\gnatcoll-paragraph_filling-words.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\paragraph_filling\gnatcoll-paragraph_filling-words.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\paragraph_filling\gnatcoll-paragraph_filling.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_22.0.0_620c2f23\src\paragraph_filling\gnatcoll-paragraph_filling.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_gmp_22.0.0_f3732e5d\gmp\gnatcoll-gmp-integers-io.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_gmp_22.0.0_f3732e5d\gmp\gnatcoll-gmp-integers-io.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_gmp_22.0.0_f3732e5d\gmp\gnatcoll-gmp-integers-misc.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_gmp_22.0.0_f3732e5d\gmp\gnatcoll-gmp-integers-misc.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_gmp_22.0.0_f3732e5d\gmp\gnatcoll-gmp-integers-number_theoretic.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_gmp_22.0.0_f3732e5d\gmp\gnatcoll-gmp-integers-number_theoretic.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_gmp_22.0.0_f3732e5d\gmp\gnatcoll-gmp-integers-random.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_gmp_22.0.0_f3732e5d\gmp\gnatcoll-gmp-integers-random.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_gmp_22.0.0_f3732e5d\gmp\gnatcoll-gmp-integers-root_extraction.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_gmp_22.0.0_f3732e5d\gmp\gnatcoll-gmp-integers-root_extraction.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_gmp_22.0.0_f3732e5d\gmp\gnatcoll-gmp-integers.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_gmp_22.0.0_f3732e5d\gmp\gnatcoll-gmp-integers.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_gmp_22.0.0_f3732e5d\gmp\gnatcoll-gmp-lib.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_gmp_22.0.0_f3732e5d\gmp\gnatcoll-gmp-random_state.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_gmp_22.0.0_f3732e5d\gmp\gnatcoll-gmp-random_state.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_gmp_22.0.0_f3732e5d\gmp\gnatcoll-gmp.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_iconv_22.0.0_f3732e5d\iconv\gnatcoll-iconv.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\gnatcoll_iconv_22.0.0_f3732e5d\iconv\gnatcoll-iconv.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-abstract_relation.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-abstract_relation.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-debug.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-debug.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-eq_same.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-eq_same.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-logic_ref.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-logic_ref.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-logic_var.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-main_support.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-main_support.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-operations.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-operations.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-predicates.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-predicates.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-pure_relations.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-pure_relations.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-refcounted_eq_same.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-refcounted_logic_ref.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-refcounted_logic_ref.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-relations.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-relations.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-unify.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-unify.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-unify_lr.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-unify_lr.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-unify_one_side.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog-unify_one_side.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-adalog.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-array_utils.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-array_utils.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-boxes.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-boxes.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-bump_ptr-vectors.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-bump_ptr-vectors.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-bump_ptr.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-bump_ptr.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-cheap_sets.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-cheap_sets.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-diagnostics-output.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-diagnostics-output.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-diagnostics.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-diagnostics.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-errors.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-file_readers.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-file_readers.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-generic_api-analysis.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-generic_api-analysis.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-generic_api.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-generic_api.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-hashes.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-hashes.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-images.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-images.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-internal.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-iterators.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-iterators.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-lexical_envs.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-lexical_envs_impl.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-lexical_envs_impl.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-packrat.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-packrat.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-relative_get.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-relative_get.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-slocs.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-slocs.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-symbols-precomputed.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-symbols-precomputed.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-symbols.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-symbols.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-text.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-text.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-token_data_handlers.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-token_data_handlers.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-tree_traversal_iterator.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-tree_traversal_iterator.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-types.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-vectors.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support-vectors.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\langkit_support_22.0.0_d43df3a9\langkit_support.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\libadalang_22.0.0_5f365aa4\src\libadalang-analysis.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\libadalang_22.0.0_5f365aa4\src\libadalang-analysis.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\libadalang_22.0.0_5f365aa4\src\libadalang-auto_provider.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\libadalang_22.0.0_5f365aa4\src\libadalang-auto_provider.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\libadalang_22.0.0_5f365aa4\src\libadalang-c.adb --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\libadalang_22.0.0_5f365aa4\src\libadalang-c.ads --
-- C:\path\to\dependency_graph_extractor_0.1.0_71bc61cd\alire\cache\dependencies\libadalang_22.0.0_5f365aa4\src\libadalang-common.adb --

We don't the the second pass, and we don't see the final time being reported!

Issue localized to libadalang function.
Submitted issue
Could not reproduce on every windows PC we tried!

Same issue occurs when analyzing rejuvenation.gpr


text:
schema: add support for additional camera models in camera intrinsics

This updates the camera intrinsics proto to include the changes made by PD: https://github.com/parallel-domain/dgp/blob/master/dgp/proto/geometry.proto#L30
But also adds support for other camera distortion models such as the double sphere model.
Additional PRs will be needed for the dataloaders to use this information.

This change is

Is there any movement on this? Would be good for our use cases, too! @kuanleetri

authors: chrisochoatri wadimkehl

repo: TRI-ML/dgp


text:
Can't seem to run scenarios in headless mode

Hi,
I'm trying to run some scenarios without calling the gui. The reason for this is that in my scenarios I create around 2000-3000 aircraft and that seems to be very slow, meaning that simulation speed is down to x0.1. The way I do this is by first creating a headless server:
python BlueSky.py --headless
and then by creating a simulation node to which I also give the scenario file as an argument:
python BlueSky.py --sim --scenfile scenario1.scn
The problem seems to be that the commands in the scenario don't seem to be executed. If I create the server with the guy and then enter the scenario file as a command in the gui, everything works as expected.
Do you have any idea what might be causing this? Also do you think this is the right way to go about speeding the simulations? Thanks in advance.
Cheers,
Ralvi

Hi Ralvi,
I tried this out myself, and noticed that it indeed doesn't correctly process the scenfile argument. I've committed a fix in 15b55a5.
Note, though, that a) the gui doesn't take much CPU power (it mostly runs on the GPU), and b) if you really don't want the gui to be available all the time, you can always start headless, and connect with bluesky in client mode:
process 1: python BlueSky.py --headless
process 2: python BlueSky.py --client

authors: jooste risufaj

repo: TUDelft-CNS-ATM/bluesky


text:
Fix #3 by adding a newline to every injected content

@TabDigital/ping-api should fix the annoying bug where
cat README.md | markdown-toc - | inject-md -t toc

would generate
- last table of contents item -->

So you had to force a newline with
cat README.md | markdown-toc - | awk 1 | inject-md -t toc

Can anyone think of a case where adding the extra newline before --> will cause an issue?

👍

authors: nguyenchr rprieto

repo: TabDigital/node-injectmd


text:
Cyclic wisps spam the log

This message is constantly sent in the log file when a cyclic wisp is active:
[00:05:40] [Server thread/INFO]: scheduling casting sound, level is ServerLevel[New World]
[00:05:40] [Render thread/INFO]: playing casting sound, level is ClientLevel

Reckon it's better to change the debug level to debug/trace, or just get rid of them? For now I'm commenting them out since I'm not sure whether the log file would include them even at lower debug levels, but I might add them back at debug level if that would also fix the issue.

pretty sure I've fixed this, make a new issue if it's still a problem.


text:
inMap和百度地图怎么结合

怎么在inMap中使用百度地图的方法

inMap是基于百度地图开发的地图组件，所以百度地图的资源可以完全拿来用。
示例：
var inmap = new inMap.Map({
    id: "allmap",
    skin: "Blueness",
    center: ["114.215408", "22.654411"],
    zoom: {
    value: 11,
    show: true,
    max: 22
    }
});
var bmap = inmap.getMap();//返回百度地图实例

拿到百度地图实例后，可以做任何事情，下面是百度地图官方demo：
返回北京市“景点”关键字的检索结果，并展示在地图上。
var local = new BMap.LocalSearch(bmap, {
		renderOptions:{map: bmap}
	});
local.search("景点");

repo: TalkingData/inmap


text:
Suggestion: Entities getting pulled by wind

How about if there is a high wind event then all entities get (slightly) pulled by the wind similar to particles?
It could also push the player around as a toggleable config option and It would also be really nice to hear sound effects for wind accordingly.
Very nice mod, looking forward to seeing where it goes.

Oooooooo I really like that idea!

authors: Spaagz TalonFloof

repo: TalonFloof/EnhancedWeather