text:
Advise about the quality / health of an Open Source project / dependency package

In addition to security vulnerabilities the advisor could also advise about the general quality of an Open Source project, e.g. using

CHAOSS Software (GrimoireLab, Cauldron)
Google's scorecard project. Also see the criticality score of Open Source projects: https://github.com/ossf/criticality_score.
Pub Points.
End-of-life (EOL)

by extending https://github.com/oss-review-toolkit/ort/blob/19c89ff9a0a7aa2a52d85c82fd477531da1ecf3d/model/src/main/kotlin/AdvisorCapability.kt#L31-L37 with HEALTH or so.

Somewhat related is the criticality score of Open Source projects: https://github.com/ossf/criticality_score

I this should be splitted in the different tools. We are interested in Google Scorecard.

I this should be splitted in the different tools. We are interested in Google Scorecard.

@dgutson, please indicate your interest by adding 👍🏻 to the top post, as that way we can rank the issues.

I would also suggest the OpenSSF Scorecard, see https://github.com/ossf/scorecard.

I would also suggest the OpenSSF Scorecard, see https://github.com/ossf/scorecard.

It's mentioned above as "Google's scorecard project".

authors: MacOS dgutson sschuberth

repo: oss-review-toolkit/ort


text:
reporter: Add test for the AntennaAttributionDocumentReporter

The AntennaAttributionDocumentReporterTest tests only the size of the
generated report and uses for this the scanners test result.

@bs-ondem detekt reports wrong spacing.

source: gharchive/pull-request

authors: bs-ondem sschuberth

license_type: permissive

license_source: github-api


text:
Onboarding - Field Notes and media page

Onboarding - Field Notes and media page
Goal: To educate users on good ethnographic note-taking and media capturing practices
Tasks:

Create a field notes and media onboarding page
Provide guidelines on what makes a good ethnographic note and how to capture media appropriately

Acceptance Criteria:
The field notes and media onboarding page should guide users on effective ethnographic note-taking and respectful media capturing practices.

This was moved to the "more" page and is now merged into deliverable-6 which is in a PR to main.

source: gharchive/issue

license: MIT


text:
worked on test cases and the workflow

Fixes #27
Unit Tests for Core Functionality of the Python Library
Overview
This PR introduces a comprehensive suite of unit tests for the core functionalities of the Python library, ensuring robustness, reliability, and high test coverage. The tests focus on verifying both standard operations and edge cases to guarantee that the library behaves as expected in a variety of scenarios.
Changes
Core Functionality Testing

TBE File Reading: Added tests to ensure proper reading of TBE files.
Header Stripping and Isolation: Verified that headers are correctly stripped and isolated from the data.
Directory Reading: Created tests to validate the reading of directories containing TBE files.

These tests ensure that the core functions of the library handle valid inputs and provide expected outputs.
Edge Case Testing
The following edge cases are now tested to ensure the library handles them gracefully:

Missing Metadata Fields: Ensures the library responds correctly to missing metadata.
Incomplete TBL Sections: Tests behavior when TBL sections are incomplete or corrupted.
Malformed ATT Attributes: Verifies that the library identifies and handles malformed attributes.
Invalid Datatypes / Unexpected Formats: Tests the system’s robustness against incorrect data formats and invalid datatypes.

These edge case scenarios help validate the reliability of the library under varying conditions.
Test Suite & Reporting

A total of at least 7 unit tests have been created to ensure comprehensive coverage of the core functions and edge cases.
Clear and detailed reporting is provided for each test, ensuring any issues are quickly identified.

Automated Testing Setup

An automated testing setup has been implemented to streamline the testing process, ensuring that tests can be executed efficiently in continuous integration (CI) pipelines.

Running the Tests
To run the tests, execute the following command in your terminal:
PYTHONPATH=$(pwd) pytest -v python/src/tests/test_tbe_file_operations.py

The provided unit tests are a good start, but they can be improved by adding tests for missing functionalities like outputting TBE and CSV files. Additionally, increasing test coverage and using a testing framework like pytest for better reporting will enhance the overall quality of the test suite. Thank you for your effort!

repo: oss-slu/tbe


text:
Enforce certain status checks in branch protections

Accept an optional yaml list of status check names for the branch protection policy to enforce repos have enabled an organization's expected checks. The yaml list should accept objects containing at least the fields name and required (to enforce whether a particular status check should be marked as required).
I'm happy to take on this pull request myself if the maintainers approve of the issue.

Maybe also, in the object: an optional msg field that overwrites the message given to developers if that status check is found missing. If not present a general "missing X status check" message will be outputted.

This sounds great. It would be good to propose the additional names and types of the members in the config.
Why would required be needed. Why would you list a name of expected check, but it not be required?
The GitHub data looks straight forward, just a list of strings.

Why would required be needed. Why would you list a name of expected check, but it not be required?

We have a bunch of status checks we supply through GitHub Apps in our org to give feedback to folks as they work on PRs, but they don't necessarily need to succeed before code is merged. e.g. providing teams early security feedback but the violations only have to be fixed later on, teams can still merge code with the failed status check.
I'm fine with putting this together without the required field but that's my use case.

Given the GitHub data it seems the status checks submitted must be considered required, which makes sense. So the new data going into the config would look like:
status_checks:
  - mycheck
  - theothercheck
  - other

With no other metadata needed. Just the names

Sounds great, lgtm

I had a need for this for our org's use case so I went ahead and took a stab at an implementation! https://github.com/ossf/allstar/pull/147

FYI #147 was just merged. Note that the final version changed the interface slightly to allow for specifying the GH app that should provide the context:
requireStatusChecks:
  - context: "Analyze (go)"
    appID: 15368
  - context: "lint"
  - context: "build"
    appID: 15368

Refer to https://github.com/ossf/allstar/pull/147#discussion_r832761480 for rationale

Closed with above

repo: ossf/allstar


text:
Failing e2e tests - scorecard-golang on ossf-tests/scorecard-action

Matrix: {
"results_format": "sarif",
"publish_results": true
}
Repo: https://github.com/ossf-tests/scorecard-action/tree/main
Run: https://github.com/ossf-tests/scorecard-action/actions/runs/2504994475
Workflow name: scorecard-golang
Workflow file: https://github.com/ossf-tests/scorecard-action/tree/main/.github/workflows/scorecards-golang.yml
Trigger: push
Branch: main

I think there are issues going on with Rekor server causing these failures. Closing these for now and will investigate further is any action is necessary.

repo: ossf/scorecard-action


text:
Release 4.4.0 does not offer tarballs for all platforms

Describe the bug
Release 4.4.0 does not offer tarballs for all platforms. Instead for amd64, a binary is attached. This change makes it difficult to process updates automatically
Reproduction steps
Steps to reproduce the behavior:

Check assets of release 4.4.0
COmpare to assets of previous releases, e.g. 4.3.1

Expected behavior
Release 4.4.0 offers tarballs for all supported platforms
Additional context
The project docker-setup relies on automated updates using RenovateBot. Since release 4.4.0, the installation of scorecard fails because the amd64 tarball is missing.

You're correct, it's because I disabled Goreleaser for the amd64 build

Thanks for the report @nicholasdille. @laurentsimon definitely need to fix before we rollout the SLSA workflow. Assigning to you.

Thanks for the report @nicholasdille. @laurentsimon definitely need to fix before we rollout the SLSA workflow. Assigning to you.

This should be a bug in SLSA Workflow.

The fix I propose is to rename the final binary to something different. When we decide to fully migrate to the SSLSA builders, we'll rename them.
@nicholasdille Can you confirm that using binaries instead of tarballs/zip works? I think your problem is that it was inconsistent, so you script expected to have tarballs, or binaries, but not both. (Not all projects use tarballs so I think this would work in your case)

Thanks for the update. Rolling out an SLSA workflow sound terrific :-) Verifying the SLSA provenance is already on my list. Unfortunately, very few projects have started to implement this.
@laurentsimon Binaries as well as tarballs are fine. I can even manage if they are mixed for different platforms. But consistency across releases would be awesome :-)

I will fix the current release by adding the tarball.
@azeemshaikh38 @naveensrinivasan is there a reasons we're using compressed assets in our release? Does GH have limitation on sizes. Otherwise a simple solution would be to change the GoReleaser config to output binaries instead of zipped tarballs. (tarballs are useful if we output multiple binaries per OS/Arch, but we don't need it)
@nicholasdille if you get some of the project you fetch binaries from to adopt some SLSA builders, check out sos.dev: it lets you be rewarded for improving supply-chain security.
Also, we're going to release https://github.com/slsa-framework/slsa-github-generator/tree/main/internal/builders/generic this month, and it should be easy for most projects to integrate.. maybe a path to get projects to adapt SLSA and use sos.dev :)

fyi, I've fixed the existing release by uploading a tarball.
I'll wait to see what @naveensrinivasan and @azeemshaikh38 think w.r.t using binaries in the GoReleaser config

is there a reasons we're using compressed assets in our release?

Don't think there is a strong reason. However, if we simply shift over to using binaries instead of tarballs I wonder how many other users we might break. Something to consider for your SLSA workflow - it might be important to provide users of the workflow the option to output binaries or tarballs.

yep that's something we'd like to support at some point for the Go builder, we have not prioritized it. I think we need to support multiple builds first. In the meantime, the generic generator will sidestep this problem by letting users add provenance to whatever they want.

On a side note, maybe it's a good thing we use tarballs? That way, every tarball can contain related metadata for the binary (SLSA provenance, signature etc.) along with the binary. Again, not a strong reason to use tarballs, just seems neat :)

Agreed. Actually I was wondering whether the provenance should be on the full zip / tarball file, or inside.. or both

fyi, I've fixed the existing release by uploading a tarball.

is the tarball correct? scorecard_4.4.0_linux_amd64.tar.gz is only
32.9 KB. I don't think the executable is included, just a scorecard-linux-amd64.intoto.jsonl file

Actually I was wondering whether the provenance should be on the full zip / tarball file, or inside.. or both

Good point, might be something to discuss with the SLSA folks. IIUC, if the compression step from zip can be part of the provenance, then just a single provenance outside the tarball should be enough.

We may generate binaries instead of zip in the future. If we do that it will break your setup. Since we're still experimenting with SLSA, I wanted to. give you a notice.

Thanks for the heads up. Scorecard is treated like a dependency. Any update is automatically tested. If it fails to install I can take a look. So any changes to the release assets will show up so I can fix the installation for a new version. So... No worries 😀

authors: azeemshaikh38 laurentsimon naveensrinivasan nicholasdille spencerschrock

repo: ossf/scorecard


text:
🐛 Fix e2e tests for branch protection

I broke the unit tests, see https://github.com/ossf/scorecard/issues/1834
It turns out that the ginkgo's Skip() function only works in the It() function.
Fix e2e tests for branch protection
no breaking changes
Fix e2e tests for branch protection

@naveensrinivasan I think this one may fix it. I tested locally and it worked. Fingers crossed.

tentatively merging.


text:
📖 Clarifications about the pinned dependencies check

The pinned dependencies check is confusing to authors of libraries, who shouldn't be pinning the dependencies of the library. But it is still valuable for flagging things which are used as part of the build and release process for a library.
Signed-off-by: Jeremy Katz jeremy@tidelift.com
What kind of change does this PR introduce?
Docs update

[X] PR title follows the guidelines defined in our pull request documentation

What is the current behavior?
Currently library maintainers are confused thinking that this check wants them to pin their dependencies but that is not the real intent. This tries to make the documentation a little clearer.
Which issue(s) this PR fixes
NONE
Special notes for your reviewer
Does this PR introduce a user-facing change?
NONE

Generate the checks.md file using make generate-docs

Done (note I had to explicitly remove the file and then run the command... it didn't notice the change; makefile rule looks right to me though 🤷♂ )


text:
srs2.0边缘不去拉源站的流

1.srs源站配置
listen              1935;
max_connections     1000;
srs_log_tank        file;
srs_log_file        ./objs/srs.log;
http_server {
enabled             on;
listen              8080;
dir                 ./objs/nginx/html;
}
stats {
network         0;
disk            sda sdb xvda xvdb;
}
http_api {
enabled         on;
listen          1985;
crossdomain     on;
}
vhost defaultVhost {
dvr {
enabled         on;
dvr_plan        session;
time_jitter     full;
dvr_path        ./objs/nginx/html/[app]/[stream]/[2006]/[01]/[02]/[15].[04].[05].[999].flv;
}
transcode {
enabled         on;
ffmpeg          /usr/local/ffmpeg-3.4.6/ffmpeg;
engine  ff{
enabled on;
vfilter {
}
vcodec          libx264;
vprofile        baseline;
vpreset         superfast;
acodec          libfdk_aac;
abitrate        45;
asample_rate    44100;
achannels       2;
aparams {
}
output          rtmp://127.0.0.1:[port]/[app]?vhost=[vhost]/[stream]_[engine];
}
}

http_hooks {
enabled         on;
on_connect      http://192.168.3.198:8180/vaildToken;
on_publish      http://192.168.3.198:8180/publish;
on_dvr          http://192.168.3.198:8180/dvrs;
}
2.边缘srs配置
listen              1935;
max_connections     1000;
srs_log_tank        file;
srs_log_file        ./objs/srs.log;
http_server {
enabled         on;
listen          8080;
dir             ./objs/nginx/html;
}
vhost defaultVhost {
hls {
enabled         on;
hls_fragment    10;
hls_window      60;
hls_path        ./objs/nginx/html;
hls_m3u8_file   [app]/[stream].m3u8;
hls_ts_file     [app]/[stream]-[seq].ts;
}
mode                remote;
origin              192.168.3.198:1935;
token_traverse      on;

}
3. SRS版本(Version): 2.0.268

边缘SRS的日志如下(Log):
[2020-01-02 11:18:26.937][trace][101737][112] HTTP client ip=192.168.3.142
[2020-01-02 11:18:26.937][trace][101737][112] HTTP GET http://192.168.3.164:8080/live/myStream_ff.m3u8, content-length=-1
[2020-01-02 11:18:26.937][warn][101737][112][2] http miss file=./objs/nginx/html/live/myStream_ff.m3u8, pattern=/, upath=/live/myStream_ff.m3u8
[2020-01-02 11:18:26.939][warn][101737][112][104] client disconnect peer. ret=1004

期望行为(Expect)
边缘去源站进行拉流
是有什么功能在源站开启后就不能拉流了吗？

hls 应该放到源站
边缘 hls 播放不会主动触发回源啦流，rtmp 、http-flv 才会。如果一定要通过 hls 播放出发拉流，可以自己在外部做。

hls 应该放到源站
边缘 hls 播放不会主动触发回源拉流，rtmp 、http-flv 才会。如果一定要通过 hls 播放触发拉流，可以自己在外部做。

把hls在源站用另一个vhost进行切片解决了该问题，谢谢麻烦你了。

@RocFang 👍 正解。

@PhoenixGx 不太明白，在源站切片后，用户从边缘 hls播放，就能触发边缘主动回源吗？

authors: PhoenixGx RocFang f476717929 winlinvip

repo: ossrs/srs


text:
Add IBM Cybersecurity Analyst Professional Certificate to the Final Project section

I see that there is a thread containing discussion on the inclusion of cybersecurity resources #639. That repository has remained quiet for some time, but the field is continuing to grow in importance at a seemingly exceptional rate. I therefore think it should be an option to engage in a security related specialisation at the end of the OSSU.
See the specialisation home page here: https://www.coursera.org/professional-certificates/ibm-cybersecurity-analyst
Overview

The specialisation is comprised of 8 courses, with a capstone and assessment at the end, much like the other specialisations listed in the 'Final Project' section.
High quality teachers and recognised cybersecurity giant backing.
Wide range of of areas covered including an introduction, operational security, sysadmin, networking, threat assessment, database security and incident response.
Highly rated curriculum (4.5 stars minimum course rating - capstone project rated at 4.8 stars). Ratings are a representation of over 60,000 students enrolled on the course (with approximately 5700 ratings).
Course material is up to date.
The recommended completion time is in keeping with the other courses in this section.
English, Arabic, French, Portuguese (European), Italian, Vietnamese, German, Russian, Spanish subtitles.
The course is available to enrol for free.
The course is appropriately challenging and in keeping with the other courses in this section. The course starts out with a 'beginner' rated introduction and progresses to 'intermediate' difficulty by the end.

Considerations

There are some complaints about the audio quality on the videos. I would say that, although it is not perfect quality, it is perfectly audible and not at all difficult to understand or grating to listen to. In any case, the content of the video lectures is thorough and I personally feel that the course is taught in a clear, concise and easy to understand way.
Adding a cybersecurity related course to the Final Projects section may not be appropriate since the other cybersecurity sections of the readme note that their inclusion is provisional pending further consideration. Notwithstanding, it is clear that more and more traditional brick and mortar universities are putting a greater and greater emphasis on cybersecurity in their curriculum's and it would be prudent to mirror that behaviour.
Since the courses are taught by IBM, there is naturally discussion of some of the tools IBM offers, though this does not detract from the quality delivery of the subject matter and how best to approach various cybersecurity challanges. Traditional open source cybersecurity tools are heavily utilised.

Sundaries

If accepted, the course will need adding to the Trello board.

The OSSU is a fantastic resource and I am very grateful to have been able to take advantage of it. I believe it can only get better by embracing cybersecurity resources and adding them as a path for future students to take.  For many people the OSSU is their only option for getting a high quality, structured education in computer science and I think they should be given the option to engage deeper with cybersecurity.
^ The above said, I am no cybersecurity vetran and would certainly welcome the thoughts of those who are on IBM's offering. I have considered the contribution guidelines and this repository and hope that I have not missed anything obvious as to why this cannot be included.

Hello @lambdajack welcome to OSSU!
Thanks for the fantastic contribution and the well thought explanations.
Your explanations here in Pull Requests would not be very visible, and it's not the best place to discuss it. Please open an RFC under Issues so this can be discussed.
Include all your comments from here. The RFC template is a bit different but you can reorganize your comments and fit them into the RFC format no problem.
Keep this PR open (do not close it), so that upon successful conclusion of the issue, it can be merged. You can reference the PR in the issue.

For anyone stumbling upon this pull request - please find further discussion at the RFC open here: #1027

repo: ossu/computer-science

license: mit

license_source: bigquery


text:
Popover type issue with overlayProps

DOMProps is coming from React Aria's useOverlayTrigger hook.

Was fixed in this latest release

repo: osuresearch/ui


text:
The display is broken after upgrade os from 10.15.6 to 11 beta

Describe the bug
When right click application in dock, the right edge of menu displays masks :

When switch task(Command+Tab), the icon displays masks:

Expected behavior
It should display the image correctly.
Configuration

HaC Mini version [e.g: 2.0]: 2.12
OSX version [e.g: 10.14.6]: 11.0 Beta (20A5374g)
NUC model [e.g: NUC8i7HNK]: NUC8i7HNK
Boot SSD model and protocol [e.g: Samsung EVO 860 1TB, SATA]: WDC PC SN720 SDAPNTW-512G,NVMe
Second SSD model and protocol (if installed) [e.g: HP EX920 1TB, NVMe]: KXG50PNV2T04 TOSHIBA,NVMe
First DIMM model [e.g: Patriot DDR4-2666 16GB]: Micron DDR4-3200 16GB  (set 3067Mhz in BIOS)
Second DIMM model (if installed): Micron DDR4-3200 16GB (set 3067Mhz in BIOS)
Display port(s) used [e.g: USB-C, mini DP]: MiniDP
Display resolution(s) [e.g: 4K, 5K]: 4K
Any TB3 devices: No.
Any USB devices: No.
Any Wi-Fi/Bluetooth devices [e.g:DW1820A, BCM94360CS2, Intel 8265]: No.

Can you reinstall v2.12?

Can you reinstall v2.12?

I reinstalled it just now. After reboot, this issue still exists.

可以重新安装 v2.12 吗？

我刚刚重新安装了它。重新启动后，此问题仍然存在。

me tooooooooooo。有点后悔升级了

可以重新安装 v2.12 吗？

我刚刚重新安装了它。重新启动后，此问题仍然存在。

me tooooooooooo。有点后悔升级了

Do you have HNK or HVK?
If you are using HNK and have this issue, I'd assume that the current same patch won't work for HNK and HVK at the same time？

可以重新安装 v2.12 吗？

我刚刚重新安装了它。重新启动后，此问题仍然存在。

me tooooooooooo。有点后悔升级了

Do you have HNK or HVK?
If you are using HNK and have this issue, I'd assume that the current same patch won't work for HNK and HVK at the same time？

I have both NUC8i7HNK and NUC8i7HVK. There are the same issue on these two computers.

可以重新安装 v2.12 吗？

我刚刚重新安装了它。重新启动后，此问题仍然存在。

me tooooooooooo。有点后悔升级了

Do you have HNK or HVK?
If you are using HNK and have this issue, I'd assume that the current same patch won't work for HNK and HVK at the same time？

I have both NUC8i7HNK and NUC8i7HVK. There is the same issue on these two computers.

我的屏是4K 的。难道 4K才会有这种问题？bate 6 是没有问题 ，升级bate7  才出现的。 苹果今天又有新版本推送了。我再升级试试看吧

可以重新安装 v2.12 吗？

我刚刚重新安装了它。重新启动后，此问题仍然存在。

me tooooooooooo。有点后悔升级了

Do you have HNK or HVK?
If you are using HNK and have this issue, I'd assume that the current same patch won't work for HNK and HVK at the same time？

I have both NUC8i7HNK and NUC8i7HVK. There is the same issue on these two computers.

我的屏是4K 的。难道 4K才会有这种问题？bate 6 是没有问题 ，升级bate7 才出现的。 苹果今天又有新版本推送了。我再升级试试看吧

I have a display which resolution is 2560*1440. It still happened on it.

@havvk @fupoaiwo
Do you have this issue with beta7/8, but didn't have the issue with beta6?
Can you upload the file /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver to somewhere, so that we can see if anything changed in beta7 that makes the hot-patch not working.

@havvk @fupoaiwo
Do you have this issue with beta7/8, but didn't have the issue with beta6?
Can you upload the file /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver to somewhere, so that we can see if anything changed in beta7 that makes the hot-patch not working.

I didn't have this issue with beta6

Can we fix it by replacing AMDMTLBronzeDriver.bundle with the one from beta6?

That is quite unexpected. We need more work to do.
Not sure whether AAPL relocate the metal driver to another path, or it's just a bug in beta7/8.
You can just try putting the beta6 binary into that folder to see if works again, however the possibility is low.
AMDMTLBronzeDriver.zip

I think the offset changed. I’ll look into it this weekend.

That is quite unexpected. We need more work to do.
Not sure whether AAPL relocate the metal driver to another path, or it's just a bug in beta7/8.
You can just try putting the beta6 binary into that folder to see if works again, however the possibility is low.
AMDMTLBronzeDriver.zip

Unfortunately it doesn't work.
Maybe we should replace AMDMTLBronzeDriver.bundle instead of AMDMTLBronzeDriver ?

That is quite unexpected. We need more work to do.
Not sure whether AAPL relocate the metal driver to another path, or it's just a bug in beta7/8.
You can just try putting the beta6 binary into that folder to see if works again, however the possibility is low.
AMDMTLBronzeDriver.zip

IT WORKS!!!!!!
After put your file into /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/, this issue disappeared.
But we can not copy file into  /System easily.
We should mount / writable first.
We can mount / RW by following this video:
https://www.youtube.com/watch?v=oe2ySAadBf4&t=45s
Or this steps
1.Mount EFI partition

2.Modify config.plist
at NVRAM section，set csr-active-config to FF0F0000 ；
at MISC secion，turn Boot Protection to None。

3.reboot into recovery mode，open Terminal and input：
mount -uw /Volumes/SYS     (Replace all the string “SYS” in this guide with your disk volume name）
/System/Library/Filesystems/apfs.fs/Contents/Resources/apfs_systemsnapshot -v /Volumes/SYS -r ""
diskutil apfs listsnapshots /Volumes/SYS
diskutil apfs deletesnapshot /Volumes/SYS -uuid <here is the uuid list in the result of last command>
diskutil apfs listsnapshots /Volumes/SYS   ##check snapshot list again, until all of the snapshots were deleted.

4.reboot into normal mode.
Mount / writable using hackintool.
Or execute the following command in Terminal:

spctl --master-disable
mount -uw /

That's all.

@havvk Did your method also solve #316 ? I can see you are using a DisplayPort over HDMI 🤔

@havvk Did your method also solve #316 ? I can see you are using a miniDisplayPort rather than HDMI 🤔

No, after put AMDMTLBronzeDriver into /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/, the issue #316 happened.
But if I have this masks problem, the system menu borders will render correctly.
I'd rather have issue #316 instead of this.

Seems like in beta 7, Apple moved the binary to the shared cache in /System/Library/dyld/dyld_shared_cache_x86_64h. I'll have to re-enable the shared cache patching.

authors: fupoaiwo goodbest havvk mr-vito osy86


text:
Installer won't patch macOS Big Sur Beta 7 and results in error

Describe the bug
I have created a new clean USB installer stick with macOS Big Sur Beta 7, and applied my HacMini 2.13 on it via the already installer macOS Big Sur Beta 2 version. HacMini Installer shows USB stick is not an Installer, although it is.
So, I just copied EFI folder from SSD EFI to USB EFI folder.
Whenever I boot, it gets stuck at pci config.
Dortania mentions an issue with Intel HEDT motherboards.
See: https://dortania.github.io/OpenCore-Install-Guide/extras/big-sur/#stuck-at-pci-configuration-begins-for-intel-s-hedt-boards
Expected behavior
HacMini 2.13 should allow me to select my USB Installer automatically to patch and should also allow me to boot into the Installer as this is now supported with the new version of OpenCore for a clean install?
Also, checked source code of patch_installer.sh in HacMini and Big Sur InstallInfo.plist is missing?
Environment:

Running OSX version: macOS 11.0 Beta 2
Target drive OSX version:  macOS 11.0 Beta 7
HaC Mini installer version: 2.13

Additional context
Using Crucial MX500 SATA SSD as target disk
Logs
Cannot boot, hence no log

If you have already applied 2.13 to your USB, then you don't have to copy SSD EFI into your USB EFI (as this operation will overwrite your 2.13 EFI in your USB.
BTW, you can just ignore the installer patch option. You can just re-run the 2.13 installer manually after you set up your system.

If you have already applied 2.13 to your USB, then you don't have to copy SSD EFI into your USB EFI (as this operation will overwrite your 2.13 EFI in your USB.
BTW, you can just ignore the installer patch option. You can just re-run the 2.13 installer manually after you set up your system.

Thanks @goodbest !
So the problem is that I had to copy the EFI folder from my actual SSD rather than patching it from HacMini. Mine was just a workaround basically...
However, the Intel HEDT issue remains and I cannot boot into the Installer...

I’m confused at what you did. Copy the EFI? That’s not part of the guide. Can you follow the guide again from the start? Including checking your BIOS settings.

today i try to create a usb installer stick with macOS 11.0.1,
the hack mini installer v2.14, patch osx installer option is grey out, i proceed without that option anyway
then i try to boot from usb for macOS 11.0.1 installer, then i encounter this

it seems like it stuck on the boot loop
here's my option

I was attempting a clean install today of Big Sur 11.0.1 using v2.14. Also saw that the Patch OS X option is disabled. I will hold off on continuing this guide until a version is released that supports Big Sur.

Closing since the original issue seems to be resolved.

authors: fahdriyami goodbest keatliang2005 mr-vito osy osy86


text:
install.lock这个文件在哪儿

安装完之后它说已经安装过了,要删除这个文件,但我找不到这个文件在哪儿

你安装的tale目录下有个resources文件夹，打开里面就能看到了。

嗯看见了,页面上写着根目录,我去根目录下找了半天.....

authors: OuGaoJun molq

repo: otale/tale


text:
Add close friend state into social link state

This PR is for API for making a friend a close friend

heads up. You will need to also update the package number to publish it

repo: ottery-app/ottery-dto


text:
Knowledge - Restrict syncing files larger than certain size to prevent 100% cpu consumption on ingestion of these files.

When trying to ingest knowledge files ( from onedrive location in my casew) which have audio and video files > 100 MB large, it results in 100% cpu consumption making the server unresponsive.
Expected Behavior:
We should be able to restrict syncing files larger than certain size to prevent 100% cpu consumption on ingestion of these files.

I put a fix where files that are bigger than 50 mb won't be synced

Tested with latest build.
We sync only files that are less than 50 mb now.


text:
Kubernetes volumes

Выполнено ДЗ №

[x] Основное ДЗ
[x] Задание со *

В процессе сделано:

Пункт 1
Пункт 2

Как запустить проект:

Например, запустить команду X в директории Y

Как проверить работоспособность:

Например, перейти по ссылке http://localhost:8080

PR checklist:

[x] Выставлен label с темой домашнего задания

Добрый день! Дз принято


text:
Export all M queries as Text files

as now, Tabular Editor knows how to parse M queries which is fantastic by itself,  it will be really useful to have the  capability to export those Queries as a text file.
the rational is most of the time in PowerBI desktop we reuse a lot of M queries, having them as a text file, will make it easier for development.

You can do this easily by going to the Advanced Scripting tab and enter the following code:
{
    System.IO.File.WriteAllText("c:\\Output\\" + ds.Name + ".m", ds.MQuery);
}`

This assumes you already have a folder on your C: drive called "Output".

it did works but when i try to save i get this

Ah - that's another bug. Could you please try to create an empty CustomActions.json file in the specified location, before saving the action?

Just updated this release with a fix for that bug. It appears if the TabularEditor folder does not exist below AppData\Local when saving a Custom Action.

authors: djouallah otykier

repo: otykier/TabularEditor


text:
Not responding when selecting field after Refresh Table Metadata

Hi I’m running into the following issue:

Open model from Server
Right Click on <Table> -> Refresh Table Metadata…
a.	Tabular Editor: ‘Unable to validate source query’
<Table> -> Partitions -> All <Table>
Edit SQL Statement - > Click tick mark: √
Right Click on <Table> -> Refresh Table Metadata…
Apply Tabular Edit suggestions (including removing some fields)
Choosing a field which is not included in the SQL statement anymore
Tabular Editor crash

Unfortunately I’m not able to get the ‘Exception stack trace’ before the program is not responding and I have to shut it down.

Hi @andboy.
I'm not able to reproduce this issue. Can you provide the following details please:

Build version number of Tabular Editor used (File > Preferences)
Type of data source provider (SqlClient, OLEDB, ODBC, or...?)
Number of partitions on the table
Partition SQL query in step 2, before making the change
Partition SQL query in step 5, after making the change

Build version: 2.8.7004.27392
Data source provider: System.Data.SqlClient
Number of partitions: 1
Step 2 SQL:
SELECT [Selskab]
      ,[Løbenr]
      ,[Dokumentnr]
      ,[DokumentTypeNr]
      ,[DokumentType]
      ,[Posteringsdato]
      ,[BeløbDKK]
      ,[DimSagBKey]
      ,[DimFinanskontoplanBKey]
      ,[DimFirmaBKey]
      ,[DimLukkepostBKey]
      ,[DimOrganisationBKey]
      ,[DimProduktbogføringsgruppeBKey]
      ,[DimSegmentBKey]
      ,[DimVirksomhedsbogføringsgruppeBKey]
      ,[DimPosteringsdatoDKey]
  FROM [dbo].[FactFinans]

Step 5 SQL:
SELECT
      [BeløbDKK]
      ,[DimSagBKey]
      ,[DimFinanskontoplanBKey]
      ,[DimFirmaBKey]
      ,[DimLukkepostBKey]
      ,[DimOrganisationBKey]
      ,[DimProduktbogføringsgruppeBKey]
      ,[DimSegmentBKey]
      ,[DimVirksomhedsbogføringsgruppeBKey]
      ,[DimBogføringsdatoDKey]
      ,[DimBilagBKey]
  FROM [dbo].[FactFinans]

Hi Daniel,
After installing the newest build version: 2.8.7012.42370 i issue above is resolved :)

Good to know - thanks!

authors: andboy otykier


text:
建议加大command字段长度到512

json:"command" xorm:"varchar(256) notnull"
建议改为512
有时候shell命令过长超过256后会出现报错：
“表单验证失败，请检测输入”

这个不会改哈，命令过长写入脚本中。

authors: ouqiang yifenglingyun

repo: ouqiang/gocron


text:
Update mod panel modal logic

Problem
The modal currently opens when a user tries to navigate away from the moderation submission edit page using the back button in the browser. Logically we should only do this if there is unsaved information written in the form that may be lost.
Success
The modal only appears when a user has entered information in the form and tries to leave the page without saving it.
Requirements

[x] Refactor the modal to only appear when input is not saved.

Implementation notes
Only the logic for the second if block condition needs changing the rest of the statement should not need refactoring.

Closed as shown as the merge from #800

authors: NabbeunNabi ShizuokaTerrier

repo: ourjapanlife/findadoc-web


text:
本地部署一直警告 warnings：

warnings
Some items were passed to additionalManifestEntries without revisioning info. This is generally NOT safe. Learn more at https://bit.ly/wb-precache.

/404

One of the glob patterns doesn't match any files. Please remove or fix the following: {
"globDirectory": "/Users/xuwei/Downloads/agpt/chatgpt-vercel/dev-dist",
"globPattern": "/*.{css,js,html,svg,png,ico,txt}",
"globIgnores": [
"/node_modules/**/",
"sw.js",
"workbox-.js"
]
}

正常

authors: ourongxing souce-xu

repo: ourongxing/chatgpt-vercel


text:
[WIP] Add support for providing context for VERIFY FAILURE etc.

This pull request adds support for stubs to provide context on why their verdict was VERIFY SUCCESS, VERIFY FAILURE or UNSUPPORTED. The approach is outlined in issue #86.
The stubs are now required to print the verdict (such as VERIFY SUCCESS) as their last output line. All lines before that are taken as context and printed:
$ trytls https -- python stubs/python-urllib2/run.py
platform: OS X 10.11.5
runner: trytls 0.0.8 (CPython 2.7.12, OpenSSL 0.9.8zh)
stub: python 'stubs/python-urllib2/run.py'
 PASS expired certificate [reject expired.badssl.com:443]
 PASS wrong hostname in certificate [reject wrong.host.badssl.com:443]
      output: hostname 'wrong.host.badssl.com' doesn't match either of '*.badssl.com', 'badssl.com'

Closes #86.

Ping @oherrala, @ikisusi, @nkapu.

The other discussed but not implemented discussed way to do this was to allow giving a line of context inline in the verdict. For example the above result could then be achieved by printing VERIFY FAILURE hostname 'wrong.host.badssl.com' doesn't match either of '*.badssl.com', 'badssl.com'.
Also both ways could be supported, the inline option becoming a "reason" and the preceding lines becoming "context".

Quite beautiful.
$ trytls https -- stack exec test-wreq
platform: OS X 10.11.5
runner: trytls 0.0.8 (CPython 2.7.12, OpenSSL 0.9.8zh)
stub: stack exec 'test-wreq'
 PASS expired certificate [reject expired.badssl.com:443]
      output: HandshakeFailed (Error_Protocol ("certificate has expired",True,CertificateExpired))
 FAIL wrong hostname in certificate [reject wrong.host.badssl.com:443]
 PASS self-signed certificate [reject self-signed.badssl.com:443]
      output: HandshakeFailed (Error_Protocol ("certificate rejected: [SelfSigned]",True,CertificateUnknown))
 PASS SHA-256 signature [accept sha256.badssl.com:443]
 PASS 1000 subjectAltNames [accept 1000-sans.badssl.com:443]
 PASS incomplete chain of trust [reject incomplete-chain.badssl.com:443]
      output: HandshakeFailed (Error_Protocol ("certificate has unknown CA",True,UnknownCa))
 PASS Superfish CA [reject superfish.badssl.com:443]
      output: HandshakeFailed (Error_Protocol ("certificate has unknown CA",True,UnknownCa))
 PASS eDellRoot CA [reject edellroot.badssl.com:443]
      output: HandshakeFailed (Error_Protocol ("certificate has unknown CA",True,UnknownCa))
 PASS DSDTestProvider CA [reject dsdtestprovider.badssl.com:443]
      output: HandshakeFailed (Error_Protocol ("certificate has unknown CA",True,UnknownCa))
 PASS protect against an OS X vulnerability [reject www.ssllabs.com:10443]
      output: HandshakeFailed (Error_Protocol ("bad SignatureRSA for ecdhparams",True,HandshakeFailure))
 PASS protect against the FREAK attack [reject www.ssllabs.com:10444]
      output: HandshakeFailed (Error_Packet_Parsing "handshake[HandshakeType_ServerKeyXchg]: parsing error: remaining bytes")
 FAIL protect against the Logjam attack [reject www.ssllabs.com:10445]
 SKIP valid localhost certificate [accept localhost:53964]
 SKIP invalid localhost certificate [reject localhost:53965]
 SKIP use only the given CA bundle, not system's [reject sha256.badssl.com:443]

I guess this PR has gotten some traction, so I'll remove the [WIP] marker.

I suggest this to be merged ASAP to get maximum testing (and stub support) before 0.2.0 release.

authors: jviide oherrala

repo: ouspg/trytls


text:
add log tab to show all new recorded requests

show all recorded requests,
for each request add ability to add as new state or add to existing state
add ability to edit request

recorded(log) tab is implemented, it allow the user to capture all his network calls and customize them

repo: outbrain/Leonardo


text:
syntax errors that prevent proper parsing and downstream processing with JSON Generation  while using the google/gemma-1.1-2b-it&solidrust/Hermes-2-Pro-Llama-3-8B-AWQ Models

Describe the issue as clearly as possible:
When using the outlines library to generate JSON structures with the google/gemma-1.1-2b-it and solidrust/Hermes-2-Pro-Llama-3-8B-AWQ models, the JSON output is often invalid, leading to failures in downstream processes. This issue is frequently associated with InvalidSyntax errors during regex pattern parsing.
Steps/code to reproduce the bug:

Initialize the Sampling Parameters and Load the Model:
from vllm.sampling_params import SamplingParams
from outlines.transformers.vllm import VLLM
from huggingface_hub import snapshot_download
from vllm import LLM
from tempfile import TemporaryDirectory

# Set the sampling parameters for the model
samplimg_params = SamplingParams(max_tokens=2048)

# Define token and model path
token = "your_hf_token"

# Load google/gemma-1.1-2b-it model
model_name = "google/gemma-1.1-2b-it"
with TemporaryDirectory() as tmp_dir:
    snapshot_download(repo_id=model_name, local_dir=tmp_dir, token=token)
    model_gemma = LLM(model=tmp_dir, tokenizer=tmp_dir, trust_remote_code=True)

# Load solidrust/Hermes-2-Pro-Llama-3-8B-AWQ model
model_name = "solidrust/Hermes-2-Pro-Llama-3-8B-AWQ"
with TemporaryDirectory() as tmp_dir:
    snapshot_download(repo_id=model_name, local_dir=tmp_dir, token=token)
    model_solidrust = LLM(model=tmp_dir, tokenizer=tmp_dir, trust_remote_code=True, dtype="auto", quantization="awq")

# Wrap the models with VLLM
vllm_model_gemma = VLLM(model_gemma)
vllm_model_solidrust = VLLM(model_solidrust)

Note: This code downloads the model to a local temporary directory and loads it. This simulates uploading to S3 and then downloading it, as the end result is the same.

Prepare the Prompts:
prompts = [extract_job_description_summary(job['title'], job['description']) for job in df[['title', 'description']].to_dict(orient='records')]

Generate JSON:
generator = generate.json(vllm_model_gemma, JobDescriptionSummary, whitespace_pattern="[ \n\t]?")
results = generator(prompts, sampling_params=samplimg_params)

Expected result:
The model should generate valid JSON objects conforming to the schema defined by JobDescriptionSummary.
Error message:
The output JSON is often invalid, containing syntax errors that prevent proper parsing and downstream processing.
Error Details
For the google/gemma-1.1-2b-it model:
NoMatch: Can not match at index 4072. Got ')?([ ', expected any of ['*', '+', '?', '{', '(', '[', '\\', '.', '$', '^', "<Any 1 except ('\\\\', '$', '|', '?', '+', '.', '^', ')', '[', '(', '*')>", '|'].
Context(data[-10:+10]): ']?\\]|null))?([ \n\t]?,'

For the solidrust/Hermes-2-Pro-Llama-3-8B-AWQ model:
NoMatch: Can not match at index 4072. Got ')?([ ', expected any of ['*', '+', '?', '{', '(', '[', '\\', '.', '$', '^', "<Any 1 except ('\\\\', '$', '|', '?', '+', '.', '^', ')', '[', '(', '*')>", '|'].
Context(data[-10:+10]): ']?\\]|null))?([ \n\t]?,'

Outlines/Python version information:
Version information

* python: 3.10.4
* outlines: 0.0.41

Context for the issue:

Gemma model on Hugging Face: google/gemma-1.1-2b-it
Hermes model on Hugging Face: solidrust/Hermes-2-Pro-Llama-3-8B-AWQ

I've encountered an interesting and perplexing behavior while working with the solidrust/Hermes-2-Pro-Llama-3-8B-AWQ model using the outlines library. When loading the model directly from the Hugging Face Hub, I encountered a CUDA out-of-memory (OOM) error, whereas loading the same model from disk previously resulted in a syntax error. Below are the details of the observations and the code used.
Observation
When loading the solidrust/Hermes-2-Pro-Llama-3-8B-AWQ model directly from Hugging Face Hub:

OOM Error:
OutOfMemoryError: CUDA out of memory. Tried to allocate 28.00 MiB. GPU 0 has a total capacity of 21.99 GiB of which 21.00 MiB is free. Process 25933 has 21.95 GiB memory in use. Of the allocated memory 20.13 GiB is allocated by PyTorch, and 373.51 MiB is reserved by PyTorch but unallocated. If reserved but unallocated memory is large try setting max_split_size_mb to avoid fragmentation. See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF

Syntax Error when loading from disk:
NoMatch: Can not match at index 4072. Got ')?([ ', expected any of ['*', '+', '?', '{', '(', '[', '\\', '.', '$', '^', "<Any 1 except ('\\\\', '$', '|', '?', '+', '.', '^', ')', '[', '(', '*')>", '|'].
Context(data[-10:+10]): ']?\\]|null))?([ \n\t]?,'

Steps/code to reproduce the OOM error:
from vllm import LLM
from vllm.sampling_params import SamplingParams
from outlines.transformers.vllm import VLLM
import pandas as pd

# Initialize the model
model_name = "solidrust/Hermes-2-Pro-Llama-3-8B-AWQ"

llm = LLM(
    model=model_name,
    tokenizer=model_name,
    trust_remote_code=True,
    dtype="auto",
    quantization="awq"
)

# Set the sampling parameters for the model
samplimg_params = SamplingParams(max_tokens=2048)

# Wrap the model with VLLM
model = VLLM(llm)

# Prepare the prompts
prompts = [extract_job_description_summary(job['title'], job['description']) for job in df[['title', 'description']].to_dict(orient='records')]

# Generate JSON
generator = generate.json(model, JobDescriptionSummary, whitespace_pattern="[ \n\t]?")
results = generator(prompts, sampling_params=samplimg_params)

# Extract the results into a DataFrame
data = [model.dict() for model in results]
extracted_texts_df = pd.DataFrame(data)

result:
The OOM error occurs during the model loading phase when loading directly from the Hugging Face Hub, whereas a syntax error occurs when loading the model from disk.

okay, after a lot of testing the issue boils down to the Tuple contraint in the Basemodel.
from datetime import datetime
import json
from enum import Enum
from typing import List,Optional
from typing_extensions import List

from pydantic import BaseModel, constr
import interegular

import outlines.models as models
from outlines.fsm.json_schema import build_regex_from_schema
from outlines.integrations.utils import adapt_tokenizer, convert_json_schema_to_str

import pandas as pd
from pydantic import BaseModel, Field, conlist, constr
from outlines import models, prompt, generate
from typing import Annotated, Tuple, List, Optional

from pydantic import BaseModel, StringConstraints

class JobDescriptionSummary(BaseModel):
    salary_range: Optional[Tuple[int]] = Field(
        default=None,
        description="Salary range for the job, represented as a tuple of (min_salary, max_salary) in integers."

regex_str = build_regex_from_schema(json.dumps(JobDescriptionSummary.model_json_schema()))
regex_pattern = interegular.parse_pattern(regex_str)

returns:
NoMatch: Can not match at index 4072. Got ')?([\\', expected any of ['*', '+', '?', '{', '(', '[', '\\', '.', '$',
'^', "<Any 1 except ('(', '\\\\', '*', '^', '+', ')', '$', '[', '.', '|', '?')>", '|'].
Context(data[-10:+10]): ']*\\]|null))?([\\n ]*,'

Pinging @lapp0

Thanks for the great reproduction scripts and isolation of the problem @hugocool!
You can verify the fix with
pip install "git+https://github.com/lapp0/outlines@fix-905"
Issue details
The issue is that tuples, defined with prefixItems, is not handled.
https://docs.pydantic.dev/latest/api/json_schema/#pydantic.json_schema.GenerateJsonSchema.tuple_schema
tuple json schema:
{'properties': {'salary_range': {'anyOf': [{'maxItems': 1, 'minItems': 1, 'prefixItems': [{'type': 'integer'}], 'type': 'array'}, {'type': 'null'}], 'default': None, 'description': 'Salary range for the job, represented as a tuple of (min_salary, max_salary) in integers.', 'title': 'Salary Range'}}, 'title': 'JobDescriptionSummary', 'type': 'object'}

authors: hugocool lapp0 rlouf

repo: outlines-dev/outlines


text:
KafkaConsumer#stream "should handle rebalance" test failure

I hit this while running tests for (hopefully unrelated) changes locally. The full failure message was:
should handle rebalance *** FAILED *** (5 minutes, 11 seconds)
[info]   200 equaled 200, but Map("key-198" -> 1, "key-78" -> 3, "key-89" -> 2, "key-105" -> 1, "key-123" -> 1, "key-93" -> 2, "key-112" -> 2, "key-8" -> 2, "key-44" -> 2, "key-74" -> 2, "key-0" -> 2, "key-116" -> 2, "key-85" -> 3, "key-169" -> 1, "key-187" -> 1, "key-152" -> 1, "key-119" -> 1, "key-108" -> 1, "key-27" -> 3, "key-22" -> 2, "key-176" -> 1, "key-11" -> 2, "key-59" -> 2, "key-49" -> 3, "key-163" -> 1, "key-43" -> 2, "key-166" -> 2, "key-38" -> 3, "key-100" -> 1, "key-71" -> 3, "key-170" -> 1, "key-127" -> 1, "key-138" -> 1, "key-155" -> 1, "key-96" -> 2, "key-82" -> 2, "key-181" -> 1, "key-32" -> 2, "key-16" -> 2, "key-193" -> 1, "key-192" -> 2, "key-159" -> 2, "key-134" -> 2, "key-148" -> 2, "key-144" -> 1, "key-62" -> 2, "key-5" -> 3, "key-67" -> 3, "key-51" -> 2, "key-111" -> 1, "key-188" -> 2, "key-177" -> 2, "key-196" -> 1, "key-115" -> 1, "key-79" -> 3, "key-42" -> 2, "key-104" -> 1, "key-31" -> 2, "key-122" -> 1, "key-56" -> 2, "key-28" -> 2, "key-58" -> 3, "key-10" -> 3, "key-75" -> 2, "key-109" -> 1, "key-69" -> 2, "key-97" -> 2, "key-185" -> 1, "key-21" -> 2, "key-17" -> 2, "key-174" -> 1, "key-92" -> 3, "key-199" -> 2, "key-86" -> 2, "key-110" -> 1, "key-81" -> 2, "key-70" -> 3, "key-158" -> 1, "key-143" -> 1, "key-126" -> 1, "key-39" -> 3, "key-9" -> 2, "key-180" -> 1, "key-147" -> 1, "key-63" -> 3, "key-137" -> 1, "key-121" -> 2, "key-68" -> 2, "key-133" -> 2, "key-165" -> 1, "key-191" -> 1, "key-46" -> 3, "key-57" -> 2, "key-35" -> 2, "key-2" -> 3, "key-154" -> 1, "key-52" -> 2, "key-4" -> 2, "key-146" -> 1, "key-106" -> 1, "key-157" -> 1, "key-94" -> 2, "key-25" -> 3, "key-178" -> 2, "key-24" -> 3, "key-140" -> 2, "key-30" -> 3, "key-14" -> 2, "key-195" -> 1, "key-72" -> 2, "key-87" -> 2, "key-161" -> 1, "key-168" -> 1, "key-189" -> 2, "key-150" -> 2, "key-41" -> 3, "key-117" -> 1, "key-153" -> 1, "key-91" -> 2, "key-13" -> 2, "key-173" -> 1, "key-76" -> 3, "key-114" -> 1, "key-131" -> 1, "key-164" -> 1, "key-184" -> 2, "key-103" -> 1, "key-120" -> 1, "key-64" -> 2, "key-125" -> 2, "key-65" -> 2, "key-54" -> 2, "key-80" -> 2, "key-47" -> 2, "key-53" -> 2, "key-190" -> 2, "key-160" -> 1, "key-132" -> 1, "key-139" -> 1, "key-142" -> 2, "key-136" -> 1, "key-1" -> 2, "key-3" -> 3, "key-29" -> 2, "key-98" -> 3, "key-18" -> 3, "key-34" -> 3, "key-20" -> 2, "key-36" -> 2, "key-83" -> 2, "key-45" -> 2, "key-128" -> 2, "key-95" -> 3, "key-40" -> 2, "key-183" -> 1, "key-7" -> 2, "key-15" -> 2, "key-130" -> 1, "key-88" -> 2, "key-26" -> 2, "key-118" -> 2, "key-141" -> 2, "key-77" -> 3, "key-107" -> 1, "key-102" -> 1, "key-182" -> 2, "key-23" -> 3, "key-162" -> 2, "key-90" -> 2, "key-60" -> 2, "key-151" -> 1, "key-12" -> 3, "key-171" -> 1, "key-113" -> 2, "key-194" -> 1, "key-33" -> 3, "key-55" -> 2, "key-48" -> 3, "key-135" -> 1, "key-156" -> 1, "key-197" -> 1, "key-66" -> 3, "key-101" -> 2, "key-175" -> 2, "key-37" -> 2, "key-124" -> 1, "key-167" -> 1, "key-99" -> 2, "key-50" -> 3, "key-129" -> 2, "key-172" -> 1, "key-149" -> 1, "key-19" -> 2, "key-61" -> 2, "key-6" -> 3, "key-84" -> 2, "key-186" -> 2, "key-179" -> 1, "key-145" -> 1, "key-73" -> 3) did not equal Map("key-198" -> 1, "key-78" -> 2, "key-89" -> 2, "key-105" -> 1, "key-123" -> 1, "key-93" -> 2, "key-112" -> 1, "key-8" -> 2, "key-44" -> 2, "key-74" -> 2, "key-0" -> 2, "key-116" -> 1, "key-85" -> 2, "key-169" -> 1, "key-187" -> 1, "key-152" -> 1, "key-119" -> 1, "key-108" -> 1, "key-27" -> 2, "key-22" -> 2, "key-176" -> 1, "key-11" -> 2, "key-59" -> 2, "key-49" -> 2, "key-163" -> 1, "key-43" -> 2, "key-166" -> 1, "key-38" -> 2, "key-100" -> 1, "key-71" -> 2, "key-170" -> 1, "key-127" -> 1, "key-138" -> 1, "key-155" -> 1, "key-96" -> 2, "key-82" -> 2, "key-181" -> 1, "key-32" -> 2, "key-16" -> 2, "key-193" -> 1, "key-192" -> 1, "key-159" -> 1, "key-134" -> 1, "key-148" -> 1, "key-144" -> 1, "key-62" -> 2, "key-5" -> 2, "key-67" -> 2, "key-51" -> 2, "key-111" -> 1, "key-188" -> 1, "key-177" -> 1, "key-196" -> 1, "key-115" -> 1, "key-79" -> 2, "key-42" -> 2, "key-104" -> 1, "key-31" -> 2, "key-122" -> 1, "key-56" -> 2, "key-28" -> 2, "key-58" -> 2, "key-10" -> 2, "key-75" -> 2, "key-109" -> 1, "key-69" -> 2, "key-97" -> 2, "key-185" -> 1, "key-21" -> 2, "key-17" -> 2, "key-174" -> 1, "key-92" -> 2, "key-199" -> 1, "key-86" -> 2, "key-110" -> 1, "key-81" -> 2, "key-70" -> 2, "key-158" -> 1, "key-143" -> 1, "key-126" -> 1, "key-39" -> 2, "key-9" -> 2, "key-180" -> 1, "key-147" -> 1, "key-63" -> 2, "key-137" -> 1, "key-121" -> 1, "key-68" -> 2, "key-133" -> 1, "key-165" -> 1, "key-191" -> 1, "key-46" -> 2, "key-57" -> 2, "key-35" -> 2, "key-2" -> 2, "key-154" -> 1, "key-52" -> 2, "key-4" -> 2, "key-146" -> 1, "key-106" -> 1, "key-157" -> 1, "key-94" -> 2, "key-25" -> 2, "key-178" -> 1, "key-24" -> 2, "key-140" -> 1, "key-30" -> 2, "key-14" -> 2, "key-195" -> 1, "key-72" -> 2, "key-87" -> 2, "key-161" -> 1, "key-168" -> 1, "key-189" -> 1, "key-150" -> 1, "key-41" -> 2, "key-117" -> 1, "key-153" -> 1, "key-91" -> 2, "key-13" -> 2, "key-173" -> 1, "key-76" -> 2, "key-114" -> 1, "key-131" -> 1, "key-164" -> 1, "key-184" -> 1, "key-103" -> 1, "key-120" -> 1, "key-64" -> 2, "key-125" -> 1, "key-65" -> 2, "key-54" -> 2, "key-80" -> 2, "key-47" -> 2, "key-53" -> 2, "key-190" -> 1, "key-160" -> 1, "key-132" -> 1, "key-139" -> 1, "key-142" -> 1, "key-136" -> 1, "key-1" -> 2, "key-3" -> 2, "key-29" -> 2, "key-98" -> 2, "key-18" -> 2, "key-34" -> 2, "key-20" -> 2, "key-36" -> 2, "key-83" -> 2, "key-45" -> 2, "key-128" -> 1, "key-95" -> 2, "key-40" -> 2, "key-183" -> 1, "key-7" -> 2, "key-15" -> 2, "key-130" -> 1, "key-88" -> 2, "key-26" -> 2, "key-118" -> 1, "key-141" -> 1, "key-77" -> 2, "key-107" -> 1, "key-102" -> 1, "key-182" -> 1, "key-23" -> 2, "key-162" -> 1, "key-90" -> 2, "key-60" -> 2, "key-151" -> 1, "key-12" -> 2, "key-171" -> 1, "key-113" -> 1, "key-194" -> 1, "key-33" -> 2, "key-55" -> 2, "key-48" -> 2, "key-135" -> 1, "key-156" -> 1, "key-197" -> 1, "key-66" -> 2, "key-101" -> 1, "key-175" -> 1, "key-37" -> 2, "key-124" -> 1, "key-167" -> 1, "key-99" -> 2, "key-50" -> 2, "key-129" -> 1, "key-172" -> 1, "key-149" -> 1, "key-19" -> 2, "key-61" -> 2, "key-6" -> 2, "key-84" -> 2, "key-186" -> 1, "key-179" -> 1, "key-145" -> 1, "key-73" -> 2) (KafkaConsumerSpec.scala:81)

Luckily the keys were ordered, so a diff was useful:
3c3
<   "key-78" -> 3,
---
>   "key-78" -> 2,
8c8
<   "key-112" -> 2,
---
>   "key-112" -> 1,
13,14c13,14
<   "key-116" -> 2,
<   "key-85" -> 3,
---
>   "key-116" -> 1,
>   "key-85" -> 2,
20c20
<   "key-27" -> 3,
---
>   "key-27" -> 2,
25c25
<   "key-49" -> 3,
---
>   "key-49" -> 2,
28,29c28,29
<   "key-166" -> 2,
<   "key-38" -> 3,
---
>   "key-166" -> 1,
>   "key-38" -> 2,
31c31
<   "key-71" -> 3,
---
>   "key-71" -> 2,
42,45c42,45
<   "key-192" -> 2,
<   "key-159" -> 2,
<   "key-134" -> 2,
<   "key-148" -> 2,
---
>   "key-192" -> 1,
>   "key-159" -> 1,
>   "key-134" -> 1,
>   "key-148" -> 1,
48,49c48,49
<   "key-5" -> 3,
<   "key-67" -> 3,
---
>   "key-5" -> 2,
>   "key-67" -> 2,
52,53c52,53
<   "key-188" -> 2,
<   "key-177" -> 2,
---
>   "key-188" -> 1,
>   "key-177" -> 1,
56c56
<   "key-79" -> 3,
---
>   "key-79" -> 2,
63,64c63,64
<   "key-58" -> 3,
<   "key-10" -> 3,
---
>   "key-58" -> 2,
>   "key-10" -> 2,
73,74c73,74
<   "key-92" -> 3,
<   "key-199" -> 2,
---
>   "key-92" -> 2,
>   "key-199" -> 1,
78c78
<   "key-70" -> 3,
---
>   "key-70" -> 2,
82c82
<   "key-39" -> 3,
---
>   "key-39" -> 2,
86c86
<   "key-63" -> 3,
---
>   "key-63" -> 2,
88c88
<   "key-121" -> 2,
---
>   "key-121" -> 1,
90c90
<   "key-133" -> 2,
---
>   "key-133" -> 1,
93c93
<   "key-46" -> 3,
---
>   "key-46" -> 2,
96c96
<   "key-2" -> 3,
---
>   "key-2" -> 2,
104,108c104,108
<   "key-25" -> 3,
<   "key-178" -> 2,
<   "key-24" -> 3,
<   "key-140" -> 2,
<   "key-30" -> 3,
---
>   "key-25" -> 2,
>   "key-178" -> 1,
>   "key-24" -> 2,
>   "key-140" -> 1,
>   "key-30" -> 2,
115,117c115,117
<   "key-189" -> 2,
<   "key-150" -> 2,
<   "key-41" -> 3,
---
>   "key-189" -> 1,
>   "key-150" -> 1,
>   "key-41" -> 2,
123c123
<   "key-76" -> 3,
---
>   "key-76" -> 2,
127c127
<   "key-184" -> 2,
---
>   "key-184" -> 1,
131c131
<   "key-125" -> 2,
---
>   "key-125" -> 1,
137c137
<   "key-190" -> 2,
---
>   "key-190" -> 1,
141c141
<   "key-142" -> 2,
---
>   "key-142" -> 1,
144c144
<   "key-3" -> 3,
---
>   "key-3" -> 2,
146,148c146,148
<   "key-98" -> 3,
<   "key-18" -> 3,
<   "key-34" -> 3,
---
>   "key-98" -> 2,
>   "key-18" -> 2,
>   "key-34" -> 2,
153,154c153,154
<   "key-128" -> 2,
<   "key-95" -> 3,
---
>   "key-128" -> 1,
>   "key-95" -> 2,
162,164c162,164
<   "key-118" -> 2,
<   "key-141" -> 2,
<   "key-77" -> 3,
---
>   "key-118" -> 1,
>   "key-141" -> 1,
>   "key-77" -> 2,
167,169c167,169
<   "key-182" -> 2,
<   "key-23" -> 3,
<   "key-162" -> 2,
---
>   "key-182" -> 1,
>   "key-23" -> 2,
>   "key-162" -> 1,
173c173
<   "key-12" -> 3,
---
>   "key-12" -> 2,
175c175
<   "key-113" -> 2,
---
>   "key-113" -> 1,
177c177
<   "key-33" -> 3,
---
>   "key-33" -> 2,
179c179
<   "key-48" -> 3,
---
>   "key-48" -> 2,
183,185c183,185
<   "key-66" -> 3,
<   "key-101" -> 2,
<   "key-175" -> 2,
---
>   "key-66" -> 2,
>   "key-101" -> 1,
>   "key-175" -> 1,
190,191c190,191
<   "key-50" -> 3,
<   "key-129" -> 2,
---
>   "key-50" -> 2,
>   "key-129" -> 1,
196c196
<   "key-6" -> 3,
---
>   "key-6" -> 2,
198c198
<   "key-186" -> 2,
---
>   "key-186" -> 1,
201c201
<   "key-73" -> 3
---
>   "key-73" -> 2

It's not consistently reproducible, so there must be a race condition somewhere?

It looks like every record is being consumed one extra time. I've not seen this before. Would be good, albeit difficult, to rule out your local changes, and see if this happens on master.

authors: danxmoran vlovgr


text:
the deployment got closed due to an unknown reason along with the strange address

I am trying to figure where this address akash14pphss726thpwws3yc458hggufynm9x77l4l2u is coming from.
I remember seeing it few times already throughout long period of time.
I found it in this TX 3AD714F1AFE7487BF4108FCA9A98F6485F9FF1A77C7C21482385A2A80A591814 while investigating the reason why the user (owner) akash15jd3ye3sf47yqtf6xvfar9jffmc5czprhrz252 had his deployment 6907521/1/1 lease-create tx on this provider akash18ga02jzaq8cw52anyhzkwta5wygufgu6zsz6xc closed for an unknown reason. He used Akashlytics to deploy his app.
Similar report where akash14pphss726thpwws3yc458hggufynm9x77l4l2u appeared as well from April 2021 (a year+ ago) is here + analysis where a user was trying to figure who closed the deployment (dseq 1114883).
TX 0E759586D0C161B0CB2A4196CBDAACD969137BCCAE51F422F842D567C7907FD6
I also found akash14pphss726thpwws3yc458hggufynm9x77l4l2u address here and here

Is that address some internal address we use for something? Like community funds?

Is that address some internal address we use for something? Like community funds?

Not sure.. it's got 0 txs there https://www.mintscan.io/akash/account/akash14pphss726thpwws3yc458hggufynm9x77l4l2u  (if mintscan reports well)

The same occurred again, and again akash14pphss726thpwws3yc458hggufynm9x77l4l2u is spotted.
dseq 6922309 (oseq, gseq both 1), owner akash1lye33kdywf6dd2ddfsat8pvs9t3e46e6amjlez.
txhash FCE209EC3F3F3037DB56A233774BF68B16186A6D9EE846DDAAD9CBB63762AF5F
$ akash query tx FCE209EC3F3F3037DB56A233774BF68B16186A6D9EE846DDAAD9CBB63762AF5F | jq
{
  "height": "6954018",
  "txhash": "FCE209EC3F3F3037DB56A233774BF68B16186A6D9EE846DDAAD9CBB63762AF5F",
  "codespace": "",
  "code": 0,
  "data": "0A230A212F616B6173682E6D61726B65742E763162657461322E4D7367436C6F7365426964",
...
          "type": "akash.v1",
          "attributes": [
            {
              "key": "module",
              "value": "deployment"
            },
            {
              "key": "action",
              "value": "group-paused"
            },
            {
              "key": "owner",
              "value": "akash1lye33kdywf6dd2ddfsat8pvs9t3e46e6amjlez"
            },
            {
              "key": "dseq",
              "value": "6922309"
            },
...
        {
          "type": "message",
          "attributes": [
            {
              "key": "action",
              "value": "/akash.market.v1beta2.MsgCloseBid"
            },
            {
              "key": "sender",
              "value": "akash14pphss726thpwws3yc458hggufynm9x77l4l2u"
            },
            {
              "key": "sender",
              "value": "akash14pphss726thpwws3yc458hggufynm9x77l4l2u"
            }
          ]
        },
...
  "tx": {
    "@type": "/cosmos.tx.v1beta1.Tx",
    "body": {
      "messages": [
        {
          "@type": "/akash.market.v1beta2.MsgCloseBid",
          "bid_id": {
            "owner": "akash1lye33kdywf6dd2ddfsat8pvs9t3e46e6amjlez",
            "dseq": "6922309",
            "gseq": 1,
            "oseq": 1,
            "provider": "akash18ga02jzaq8cw52anyhzkwta5wygufgu6zsz6xc"
          }
        }
      ],
...

The same issue occurred again.

dseq 6940849, owner akash12hs7vay7pheanr4ze5lwnt7xg9krrtew34empl, provider akash19yhu3jgw8h0320av98h8n5qczje3pj3u9u2amp.

https://www.mintscan.io/akash/txs/56D783E12FDB646C93C841D5005E37770292E614B91F83E183764D0B5C13E44B
reported here https://discord.com/channels/747885925232672829/771909909335506955/1006165965391798302

FWIW: users are using a standard wordpress template available in Akashlytics

Which must be this https://github.com/ovrclk/awesome-akash/tree/b749184b/wordpress

I found this address, while browsing through my logs, .. makes me wonder now if that is somehow related to the depositor address

(**Click to expand**) akash-testnet-3@stealth:~$ akash tx deployment create --depositor-account
akash-testnet-3@stealth:~$ akash tx deployment create --depositor-account akash1qvr9vwsae25rn8pk9m77s9fkwrxdc65r2s3tt7 --from second deploy.yaml
Enter keyring passphrase:
{"body":{"messages":[{"@type":"/akash.deployment.v1beta2.MsgCreateDeployment","id":{"owner":"akash1fedhgmq6mjv94p2lu06x2hq3el9l2x4pqvg0dh","dseq":"131748"},"groups":[{"name":"westcoast","requirements":{"signed_by":{"all_of":[],"any_of":[]},"attributes":[{"key":"host","value":"akash"}]},"resources":[{"resources":{"cpu":{"units":{"val":"100"},"attributes":[]},"memory":{"quantity":{"val":"536870912"},"attributes":[]},"storage":[{"name":"default","quantity":{"val":"536870912"},"attributes":[]}],"endpoints":[{"kind":"SHARED_HTTP","sequence_number":0}]},"count":1,"price":{"denom":"uakt","amount":"1000.000000000000000000"}}]}],"version":"o8/63tCm60x0kMKl5gFR7tetyaEhtEx+h7L+p4RxJBg=","deposit":{"denom":"uakt","amount":"5000000"},"depositor":"akash1qvr9vwsae25rn8pk9m77s9fkwrxdc65r2s3tt7"}],"memo":"","timeout_height":"0","extension_options":[],"non_critical_extension_options":[]},"auth_info":{"signer_infos":[],"fee":{"amount":[],"gas_limit":"200000","payer":"","granter":""}},"signatures":[]}
confirm transaction before signing and broadcasting [y/N]: y
{"height":"131750","txhash":"8E34F8001B239DDDF9B7D3F8A1FF90AD68AD4F1438780A98A9131CC48817B21C","codespace":"","code":0,"data":"0A2F0A2D2F616B6173682E6465706C6F796D656E742E763162657461322E4D73674372656174654465706C6F796D656E74","raw_log":"[{"events":[{"type":"akash.v1","attributes":[{"key":"module","value":"deployment"},{"key":"action","value":"deployment-created"},{"key":"version","value":"a3cffaded0a6eb4c7490c2a5e60151eed7adc9a121b44c7e87b2fea784712418"},{"key":"owner","value":"akash1fedhgmq6mjv94p2lu06x2hq3el9l2x4pqvg0dh"},{"key":"dseq","value":"131748"},{"key":"module","value":"market"},{"key":"action","value":"order-created"},{"key":"owner","value":"akash1fedhgmq6mjv94p2lu06x2hq3el9l2x4pqvg0dh"},{"key":"dseq","value":"131748"},{"key":"gseq","value":"1"},{"key":"oseq","value":"1"}]},{"type":"coin_received","attributes":[{"key":"receiver","value":"akash14pphss726thpwws3yc458hggufynm9x77l4l2u"},{"key":"amount","value":"5000000uakt"}]},{"type":"coin_spent","attributes":[{"key":"spender","value":"akash1qvr9vwsae25rn8pk9m77s9fkwrxdc65r2s3tt7"},{"key":"amount","value":"5000000uakt"}]},{"type":"cosmos.authz.v1beta1.EventRevoke","attributes":[{"key":"msg_type_url","value":"\"/akash.deployment.v1beta2.MsgDepositDeployment\""},{"key":"granter","value":"\"akash1qvr9vwsae25rn8pk9m77s9fkwrxdc65r2s3tt7\""},{"key":"grantee","value":"\"akash1fedhgmq6mjv94p2lu06x2hq3el9l2x4pqvg0dh\""}]},{"type":"message","attributes":[{"key":"action","value":"/akash.deployment.v1beta2.MsgCreateDeployment"},{"key":"sender","value":"akash1qvr9vwsae25rn8pk9m77s9fkwrxdc65r2s3tt7"}]},{"type":"transfer","attributes":[{"key":"recipient","value":"akash14pphss726thpwws3yc458hggufynm9x77l4l2u"},{"key":"sender","value":"akash1qvr9vwsae25rn8pk9m77s9fkwrxdc65r2s3tt7"},{"key":"amount","value":"5000000uakt"}]}]}]","logs":[{"msg_index":0,"log":"","events":[{"type":"akash.v1","attributes":[{"key":"module","value":"deployment"},{"key":"action","value":"deployment-created"},{"key":"version","value":"a3cffaded0a6eb4c7490c2a5e60151eed7adc9a121b44c7e87b2fea784712418"},{"key":"owner","value":"akash1fedhgmq6mjv94p2lu06x2hq3el9l2x4pqvg0dh"},{"key":"dseq","value":"131748"},{"key":"module","value":"market"},{"key":"action","value":"order-created"},{"key":"owner","value":"akash1fedhgmq6mjv94p2lu06x2hq3el9l2x4pqvg0dh"},{"key":"dseq","value":"131748"},{"key":"gseq","value":"1"},{"key":"oseq","value":"1"}]},{"type":"coin_received","attributes":[{"key":"receiver","value":"akash14pphss726thpwws3yc458hggufynm9x77l4l2u"},{"key":"amount","value":"5000000uakt"}]},{"type":"coin_spent","attributes":[{"key":"spender","value":"akash1qvr9vwsae25rn8pk9m77s9fkwrxdc65r2s3tt7"},{"key":"amount","value":"5000000uakt"}]},{"type":"cosmos.authz.v1beta1.EventRevoke","attributes":[{"key":"msg_type_url","value":""/akash.deployment.v1beta2.MsgDepositDeployment""},{"key":"granter","value":""akash1qvr9vwsae25rn8pk9m77s9fkwrxdc65r2s3tt7""},{"key":"grantee","value":""akash1fedhgmq6mjv94p2lu06x2hq3el9l2x4pqvg0dh""}]},{"type":"message","attributes":[{"key":"action","value":"/akash.deployment.v1beta2.MsgCreateDeployment"},{"key":"sender","value":"akash1qvr9vwsae25rn8pk9m77s9fkwrxdc65r2s3tt7"}]},{"type":"transfer","attributes":[{"key":"recipient","value":"akash14pphss726thpwws3yc458hggufynm9x77l4l2u"},{"key":"sender","value":"akash1qvr9vwsae25rn8pk9m77s9fkwrxdc65r2s3tt7"},{"key":"amount","value":"5000000uakt"}]}]}],"info":"","gas_wanted":"200000","gas_used":"88242","tx":null,"timestamp":"","events":[{"type":"tx","attributes":[{"key":"ZmVl","value":"","index":true}]},{"type":"tx","attributes":[{"key":"YWNjX3NlcQ==","value":"YWthc2gxZmVkaGdtcTZtanY5NHAybHUwNngyaHEzZWw5bDJ4NHBxdmcwZGgvNA==","index":true}]},{"type":"tx","attributes":[{"key":"c2lnbmF0dXJl","value":"RWNJNVoxSVYxd2s5ZnIwdUt5MDl2V2dXTGZEQ1R3cTRQOHZkYUwzeFRFVVFXcXVsY3FvdGw5R01ubW51aTZacTFJT3hKZ0FKcHZqMm5Rb1BSbTNHTnc9PQ==","index":true}]},{"type":"message","attributes":[{"key":"YWN0aW9u","value":"L2FrYXNoLmRlcGxveW1lbnQudjFiZXRhMi5Nc2dDcmVhdGVEZXBsb3ltZW50","index":true}]},{"type":"cosmos.authz.v1beta1.EventRevoke","attributes":[{"key":"bXNnX3R5cGVfdXJs","value":"Ii9ha2FzaC5kZXBsb3ltZW50LnYxYmV0YTIuTXNnRGVwb3NpdERlcGxveW1lbnQi","index":true},{"key":"Z3JhbnRlcg==","value":"ImFrYXNoMXF2cjl2d3NhZTI1cm44cGs5bTc3czlma3dyeGRjNjVyMnMzdHQ3Ig==","index":true},{"key":"Z3JhbnRlZQ==","value":"ImFrYXNoMWZlZGhnbXE2bWp2OTRwMmx1MDZ4MmhxM2VsOWwyeDRwcXZnMGRoIg==","index":true}]},{"type":"akash.v1","attributes":[{"key":"bW9kdWxl","value":"ZGVwbG95bWVudA==","index":true},{"key":"YWN0aW9u","value":"ZGVwbG95bWVudC1jcmVhdGVk","index":true},{"key":"dmVyc2lvbg==","value":"YTNjZmZhZGVkMGE2ZWI0Yzc0OTBjMmE1ZTYwMTUxZWVkN2FkYzlhMTIxYjQ0YzdlODdiMmZlYTc4NDcxMjQxOA==","index":true},{"key":"b3duZXI=","value":"YWthc2gxZmVkaGdtcTZtanY5NHAybHUwNngyaHEzZWw5bDJ4NHBxdmcwZGg=","index":true},{"key":"ZHNlcQ==","value":"MTMxNzQ4","index":true}]},{"type":"akash.v1","attributes":[{"key":"bW9kdWxl","value":"bWFya2V0","index":true},{"key":"YWN0aW9u","value":"b3JkZXItY3JlYXRlZA==","index":true},{"key":"b3duZXI=","value":"YWthc2gxZmVkaGdtcTZtanY5NHAybHUwNngyaHEzZWw5bDJ4NHBxdmcwZGg=","index":true},{"key":"ZHNlcQ==","value":"MTMxNzQ4","index":true},{"key":"Z3NlcQ==","value":"MQ==","index":true},{"key":"b3NlcQ==","value":"MQ==","index":true}]},{"type":"coin_spent","attributes":[{"key":"c3BlbmRlcg==","value":"YWthc2gxcXZyOXZ3c2FlMjVybjhwazltNzdzOWZrd3J4ZGM2NXIyczN0dDc=","index":true},{"key":"YW1vdW50","value":"NTAwMDAwMHVha3Q=","index":true}]},{"type":"coin_received","attributes":[{"key":"cmVjZWl2ZXI=","value":"YWthc2gxNHBwaHNzNzI2dGhwd3dzM3ljNDU4aGdndWZ5bm05eDc3bDRsMnU=","index":true},{"key":"YW1vdW50","value":"NTAwMDAwMHVha3Q=","index":true}]},{"type":"transfer","attributes":[{"key":"cmVjaXBpZW50","value":"YWthc2gxNHBwaHNzNzI2dGhwd3dzM3ljNDU4aGdndWZ5bm05eDc3bDRsMnU=","index":true},{"key":"c2VuZGVy","value":"YWthc2gxcXZyOXZ3c2FlMjVybjhwazltNzdzOWZrd3J4ZGM2NXIyczN0dDc=","index":true},{"key":"YW1vdW50","value":"NTAwMDAwMHVha3Q=","index":true}]},{"type":"message","attributes":[{"key":"c2VuZGVy","value":"YWthc2gxcXZyOXZ3c2FlMjVybjhwazltNzdzOWZrd3J4ZGM2NXIyczN0dDc=","index":true}]}]}

the quick reproducer for akash14pphss726thpwws3yc458hggufynm9x77l4l2u address
Looks like that address has something to do with how escrow is working.

deploy a multi-service SDL and make sure one of the services would never get ready / constantly cause K8s restarting it;
wait for about 7-8 minutes;
the lease will get automatically closed with MsgCloseBid TX containing the akash14pphss726thpwws3yc458hggufynm9x77l4l2u address (coin_spent message about 5 AKT deposit and few uakt being spent with that address as a spender, and MsgCloseBid message with that address as a sender)  (example TX);
the deployment will switch into a paused state;

Deployment SDL: 1676-repro.yml
---
version: "2.0"

services:
  app:
    image: ubuntu:22.04
    command:
      - "sh"
      - "-c"
    args:
      - sleep infinity
  app2:
    image: ubuntu:22.04
    expose:
      - port: 80
        as: 80
        to:
          - global: true

profiles:
  compute:
    app:
      resources:
        cpu:
          units: 1
        memory:
          size: 512Mi
        storage:
          size: 512Mi
    app2:
      resources:
        cpu:
          units: 1
        memory:
          size: 512Mi
        storage:
          size: 512Mi
  placement:
    akash:
      attributes:
        host: akash
      signedBy:
        anyOf:
          - "akash1365yvmc4s7awdyj3n2sav7xfx76adc6dnmlx63"
      pricing:
        app:
          denom: uakt
          amount: 100000
        app2:
          denom: uakt
          amount: 100000

deployment:
  app:
    akash:
      profile: app
      count: 1
  app2:
    akash:
      profile: app2
      count: 1

Needs retesting after provider services upgrade @andy108369

Could be related to the situation when provider doesn't have enough resources and closes the deployment when reaching monitorMaxRetries => see https://github.com/akash-network/provider/issues/64 for details.

As of akash14pphss726thpwws3yc458hggufynm9x77l4l2u address, that's the escrow address:
$ akash query account akash14pphss726thpwws3yc458hggufynm9x77l4l2u
'@type': /cosmos.auth.v1beta1.ModuleAccount
base_account:
  account_number: "6732"
  address: akash14pphss726thpwws3yc458hggufynm9x77l4l2u
  pub_key: null
  sequence: "0"
name: escrow       <<<<<<<<<<<<<<<<
permissions: []

authors: andy108369 chandadharap tidrolpolelsef

repo: ovrclk/akash


text:
Failed to launch game

Failed to launch game, all mods disabled.

Doesn't work with "forcing Exe launch" either.

Console Log:
Error while starting game: System.ComponentModel.Win32Exception (0x80004005): Cannot find the specified file
  at System.Diagnostics.Process.StartWithShellExecuteEx (System.Diagnostics.ProcessStartInfo startInfo) [0x00129] in <a85c1a570f9a4f9f9c3d2cfa5504e34f>:0
  at System.Diagnostics.Process.Start () [0x00038] in <a85c1a570f9a4f9f9c3d2cfa5504e34f>:0
  at (wrapper remoting-invoke-with-check) System.Diagnostics.Process.Start()
  at System.Diagnostics.Process.Start (System.Diagnostics.ProcessStartInfo startInfo) [0x0001e] in <a85c1a570f9a4f9f9c3d2cfa5504e34f>:0
  at System.Diagnostics.Process.Start (System.String fileName) [0x00006] in <a85c1a570f9a4f9f9c3d2cfa5504e34f>:0
  at OWML.Abstractions.ProcessHelper.Start (System.String path, System.String[] args) [0x0000a] in <b0ef52ce82674911ae32968a3558c523>:0
  at OWML.Launcher.App.StartGame () [0x00171] in <2e01ec5b77c2492a91e414fbcb87dd0f>:0

File Log:
[01:46:38][WARN] Potentially failed to start game (exit code): Unknown
[01:46:38][WARN] Potentially Failed to Start Game (stdout):
[01:46:38][WARN] Potentially Failed to Start Game (stderr): run-detectors: unable to find an interpreter for /home/user/.steam/steam/steamapps/common/Outer Wilds/OuterWilds.exe

System: Debian trixie Linux 6.5.0-5-amd64
sigh just another reason why C# is total garbage.

apparently someone else just fixed it by reinstalling everything https://discord.com/channels/929708786027999262/929721596548104192/1221629699697148024

authors: JohnCorby anthonywww

repo: ow-mods/owml


text:
refactor(explorers): remove mention of deprecated explorer channel

Remove mention of deprecated explorer channel in catalog.
Is there any other change to be made with this regard?

Is there any other change to be made with this regard?

Not from ETL perspective.

authors: Marigold pabloarosado

repo: owid/owid-catalog-py


text:
clarify service vs. extension

When going over the dev docs @mmattel noticed that I was referring to ocdav as a service, whereas most places use the term extension. Even the folder containing all ocis extensions / services is called extensions. But what are we extending? The ocis platform? Currently, the ocis extensions provide the core functionality of ocis. There is a difference between these core extensions and actual extensions like a calender or contacts extension.
@C0rby pointed out that all extensions we currently have are actually not really extensions, but services that make up the ocis platform.
While we could keep calling all ocis services extensions it would be clearer to call them ocis services. That would allow distinguishing them from ocis extensions which extend the ocis platform that in turn consists of at least the set of ocis services.
Would that mean we rename the extensions folder to services?
@micbar @dragotin @dragonchaser @C0rby @kobergj @owncloud/pm thoughts?

Any clearance we make now, will avoid confusion and creative/challenging "explanations" later on.

Renaming extensions => services makes sense to me, in the future we could add a new extensions directory where we pin third-party extensions we want to bundle using git sub-modules.

So far, AFAIK we only have services that are bundled by default and make the functionality of oCIS. Extensions are optional for me, and could be maintained elsewhere as @dragonchaser says.
So I support the rename as well.

I agree with the arguments in the OP and support the rename as well.

authors: butonic dragonchaser dragotin mmattel pmaier1

repo: owncloud/ocis


text:
ocdav service still using machine auth

The ocdav service (living in reva) is still using machine auth in some cases. We want to use service accounts instead
Acceptance criteria:

[ ] pass service account config to ocdav
[ ] find occurences of machine auth (search for MachineAuthAPIKey) and replace them with service accounts
[ ] remove MachineAuthAPIKey config var in ocdav (reva)

Two occurrences of this in revas ocdav service:
https://github.com/cs3org/reva/blob/edge/internal/http/services/owncloud/ocdav/ocdav.go#L343
https://github.com/cs3org/reva/blob/edge/internal/http/services/owncloud/ocdav/ocdav.go#L370


text:
moving a file (with versions) into a shared folder as the sharee and as the sharer

Describe the bug
if someone is invited to a share with following permissions, 'create', 'delete', 'read', 'update', the invited user should NOT see the resource version anymore. the change happened in https://github.com/cs3org/reva/pull/3641.
What to do
rewrite the tests to use a project instead of a personal space, the NewSpaceEditorRole roleSet contains the ListFileVersions permission.
added to expected failures in https://github.com/owncloud/ocis/pull/7727

API tests added in https://github.com/owncloud/ocis/pull/8013 and extended in https://github.com/owncloud/ocis/pull/8183
So, I am closing this here

authors: fschade saw-jan


text:
500 when public uploads file to project space

Version | 5.1.0-prealpha+03bd7d83f

9.0.0-alpha.2

Steps:

admin creates project space and create public link for space (edit permission)
public opens link and upload file

Actual:

ocis_log:
2024-03-20 09:28:46 2024-03-20T08:28:46Z ERR rpc error: code = PermissionDenied desc = auth: core access token is invalid code=PermissionDenied end="20/Mar/2024:08:28:46 +0000" from=tcp://127.0.0.1:39022 pkg=rgrpc service=sharing start="20/Mar/2024:08:28:46 +0000" time_ns=106459 traceid=a2eea47ee507f6d36506413dba14592f uri=/cs3.sharing.collaboration.v1beta1.CollaborationAPI/ListReceivedShares user-agent=grpc-go/1.62.1
2024-03-20 09:28:46 2024-03-20T08:28:46Z ERR sharesstorageprovider: error calling ListReceivedSharesRequest: sharesstorageprovider: error calling ListReceivedSharesRequest: rpc error: code = PermissionDenied desc = auth: core access token is invalid code=PermissionDenied end="20/Mar/2024:08:28:46 +0000" from=tcp://127.0.0.1:58918 pkg=rgrpc service=storage-shares start="20/Mar/2024:08:28:46 +0000" time_ns=947958 traceid=a2eea47ee507f6d36506413dba14592f uri=/cs3.storage.provider.v1beta1.ProviderAPI/ListStorageSpaces user-agent=grpc-go/1.62.1
2024-03-20 09:28:46 2024-03-20T08:28:46Z ERR rpc error: code = PermissionDenied desc = auth: core access token is invalid code=PermissionDenied end="20/Mar/2024:08:28:46 +0000" from=tcp://127.0.0.1:59508 pkg=rgrpc service=ocm start="20/Mar/2024:08:28:46 +0000" time_ns=47042 traceid=a2eea47ee507f6d36506413dba14592f uri=/cs3.sharing.ocm.v1beta1.OcmAPI/ListReceivedOCMShares user-agent=grpc-go/1.62.1
2024-03-20 09:28:46 2024-03-20T08:28:46Z ERR gateway: error calling ListReceivedShares: rpc error: code = PermissionDenied desc = auth: core access token is invalid code=PermissionDenied end="20/Mar/2024:08:28:46 +0000" from=tcp://192.168.0.12:52110 pkg=rgrpc service=gateway start="20/Mar/2024:08:28:46 +0000" time_ns=575500 traceid=a2eea47ee507f6d36506413dba14592f uri=/cs3.gateway.v1beta1.GatewayAPI/ListReceivedOCMShares user-agent=grpc-go/1.62.1
2024-03-20 09:28:46 2024-03-20T08:28:46Z ERR failed to list storage spaces error="rpc error: code = PermissionDenied desc = gateway: error calling ListReceivedShares: rpc error: code = PermissionDenied desc = auth: core access token is invalid" filters=[{"Term":{"Path":"/public/MSdlKXQZLikAmoB/Screenshot 2024-03-19 at 13.54.06.png"},"type":5},{"Term":{"SpaceType":"+mountpoint"},"type":4}] pkg=rgrpc service=ocm status={"code":15,"message":"error listing spaces","trace":"a2eea47ee507f6d36506413dba14592f"} traceid=a2eea47ee507f6d36506413dba14592f
2024-03-20 09:28:46 2024-03-20T08:28:46Z ERR rpc error: code = PermissionDenied desc = auth: core access token is invalid code=PermissionDenied end="20/Mar/2024:08:28:46 +0000" from=tcp://127.0.0.1:59508 pkg=rgrpc service=ocm start="20/Mar/2024:08:28:46 +0000" time_ns=41875 traceid=a2eea47ee507f6d36506413dba14592f uri=/cs3.sharing.ocm.v1beta1.OcmAPI/ListReceivedOCMShares user-agent=grpc-go/1.62.1
2024-03-20 09:28:46 2024-03-20T08:28:46Z ERR gateway: error calling ListReceivedShares: rpc error: code = PermissionDenied desc = auth: core access token is invalid code=PermissionDenied end="20/Mar/2024:08:28:46 +0000" from=tcp://192.168.0.12:52110 pkg=rgrpc service=gateway start="20/Mar/2024:08:28:46 +0000" time_ns=456917 traceid=a2eea47ee507f6d36506413dba14592f uri=/cs3.gateway.v1beta1.GatewayAPI/ListReceivedOCMShares user-agent=grpc-go/1.62.1
2024-03-20 09:28:46 2024-03-20T08:28:46Z ERR failed to list storage spaces error="rpc error: code = PermissionDenied desc = gateway: error calling ListReceivedShares: rpc error: code = PermissionDenied desc = auth: core access token is invalid" filters=[{"Term":{"Path":"/public/MSdlKXQZLikAmoB/Screenshot 2024-03-19 at 13.54.06.png"},"type":5},{"Term":{"SpaceType":"+mountpoint"},"type":4}] pkg=rgrpc service=ocm status={"code":15,"message":"error listing spaces","trace":"a2eea47ee507f6d36506413dba14592f"} traceid=a2eea47ee507f6d36506413dba14592f
2024-03-20 09:28:46 2024-03-20T08:28:46Z ERR rpc error: code = PermissionDenied desc = auth: core access token is invalid code=PermissionDenied end="20/Mar/2024:08:28:46 +0000" from=tcp://127.0.0.1:39022 pkg=rgrpc service=sharing start="20/Mar/2024:08:28:46 +0000" time_ns=46333 traceid=a2eea47ee507f6d36506413dba14592f uri=/cs3.sharing.collaboration.v1beta1.CollaborationAPI/ListReceivedShares user-agent=grpc-go/1.62.1
2024-03-20 09:28:46 2024-03-20T08:28:46Z ERR sharesstorageprovider: error calling ListReceivedSharesRequest: sharesstorageprovider: error calling ListReceivedSharesRequest: rpc error: code = PermissionDenied desc = auth: core access token is invalid code=PermissionDenied end="20/Mar/2024:08:28:46 +0000" from=tcp://127.0.0.1:58918 pkg=rgrpc service=storage-shares start="20/Mar/2024:08:28:46 +0000" time_ns=385084 traceid=a2eea47ee507f6d36506413dba14592f uri=/cs3.storage.provider.v1beta1.ProviderAPI/ListStorageSpaces user-agent=grpc-go/1.62.1
2024-03-20 09:28:46 2024-03-20T08:28:46Z ERR error when calling Createhome error="gateway: grpc failed with code CODE_PERMISSION_DENIED" service=proxy
2024-03-20 09:28:46 2024-03-20T08:28:46Z ERR error resolving reference resource_id:<storage_id:"13b5b543-0239-4abf-b2fc-5b84758d183b" opaque_id:"2c35a76e-a0fc-4d35-9bd6-06a8d563880c" space_id:"8dfc1eb7-d9a0-4753-93cc-0d1a43b555ad" >  under scope publicshare:wHFaHdMgEUkdXIv error="error: permission denied: access forbidden via public link" pkg=rgrpc service=gateway traceid=a2eea47ee507f6d36506413dba14592f
2024-03-20 09:28:46 2024-03-20T08:28:46Z ERR error resolving reference resource_id:<storage_id:"13b5b543-0239-4abf-b2fc-5b84758d183b" opaque_id:"2c35a76e-a0fc-4d35-9bd6-06a8d563880c" space_id:"8dfc1eb7-d9a0-4753-93cc-0d1a43b555ad" >  under scope publicshare:wHFaHdMgEUkdXIv error="error: permission denied: access forbidden via public link" pkg=rgrpc service=gateway traceid=a2eea47ee507f6d36506413dba14592f
2024-03-20 09:28:46 2024-03-20T08:28:46Z ERR rpc error: code = PermissionDenied desc = auth: core access token is invalid code=PermissionDenied end="20/Mar/2024:08:28:46 +0000" from=tcp://192.168.0.12:53750 pkg=rgrpc service=gateway start="20/Mar/2024:08:28:46 +0000" time_ns=5148917 traceid=a2eea47ee507f6d36506413dba14592f uri=/cs3.storage.registry.v1beta1.RegistryAPI/ListStorageProviders user-agent=grpc-go/1.62.1
2024-03-20 09:28:46 2024-03-20T08:28:46Z ERR No info found for uploaded file name=com.owncloud.web.ocdav path="/public/MSdlKXQZLikAmoB/Screenshot 2024-03-19 at 13.54.06.png" request-id=52cedd47-3cac-456b-8add-8c41ac37e25a service=ocdav traceid=a2eea47ee507f6d36506413dba14592f

but after refresh page - the file exists
cc @2403905

Here is a fix for this issue https://github.com/cs3org/reva/pull/4589
@micbar We also have two similar tickets for v4.0.6 Should I make the backport?
#8629
#8658


text:
update faq

owncloud.org/faq/

A Table of Contents would be nice for FAQ - maybe custom fields or custom post types for the single questions, so we can autogenerate it.

authors: Kawohl lefherz


text:
Faq - there is no artificial limitation in ownCloud

Note that ownCloud Server is not artificially limited in number of users, files etc.

@karlitschek you wanted this, here it is ;-)

:+1: Great clarification.

@tomneedham a quick look should suffice...

authors: jospoortvliet karlitschek


text:
osu! Stats checker is not functioning + Improvements

Proposed changes after bugfix

[x]  parse avatar from http://a.ppy.sh
[x]  use a better formatting (util can be used) for text display

Fixed in #21

repo: owo-dev-team/owo-whats-this


text:
bug(semantic): AstNode has incorrect ScopeId

playground link
function foo(cb) { cb = function() { function something(a) { cb(1 + a); } register(something); }(); } foo();
//                                                           ^^^^^^^^^

To reproduce:

get The first read reference for cb (it has a node whose Id is for the above CallExpression)
Get the ScopeId pointed to by that Reference
Get the node associated with that ScopeId
Notice that it's the anonymous function wrapping something, when it should be the something function

Excellent bug-hunting!
I suspect this may have been caused by #4347 (but that's just a guess).

Get the ScopeId pointed to by that Reference

The reference doesn't store ScopeId. If you mean the ScopeId of the symbol pointed to by this reference, then the node looks correct.
The following scope snapshot was generated by your provided playground's code
---
source: crates/oxc_semantic/tests/main.rs
assertion_line: 112
input_file: crates/oxc_semantic/tests/fixtures/oxc/index.ts
---
[
  {
    "children": [
      {
        "children": [
          {
            "children": [
              {
                "children": [],
                "flag": "ScopeFlags(StrictMode | Function)",
                "id": 3,
                "node": "Function(something)",
                "symbols": [
                  {
                    "flag": "SymbolFlags(FunctionScopedVariable)",
                    "id": 3,
                    "name": "a",
                    "node": "FormalParameter",
                    "references": [
                      {
                        "flag": "ReferenceFlag(Read)",
                        "id": 0,
                        "name": "a",
                        "node_id": 27
                      }
                    ]
                  }
                ]
              }
            ],
            "flag": "ScopeFlags(StrictMode | Function)",
            "id": 2,
            "node": "Function(<anonymous>)",
            "symbols": [
              {
                "flag": "SymbolFlags(FunctionScopedVariable)",
                "id": 2,
                "name": "something",
                "node": "Function(something)",
                "references": [
                  {
                    "flag": "ReferenceFlag(Read)",
                    "id": 0,
                    "name": "something",
                    "node_id": 32
                  }
                ]
              }
            ]
          }
        ],
        "flag": "ScopeFlags(StrictMode | Function)",
        "id": 1,
        "node": "Function(foo)",
        "symbols": [
          {
            "flag": "SymbolFlags(FunctionScopedVariable)",
            "id": 1,
            "name": "cb",
            "node": "FormalParameter",
            "references": [
              {
                "flag": "ReferenceFlag(Write)",
                "id": 0,
                "name": "cb",
                "node_id": 11
              },
              {
                "flag": "ReferenceFlag(Read)",
                "id": 1,
                "name": "cb",
                "node_id": 28
              }
            ]
          }
        ]
      }
    ],
    "flag": "ScopeFlags(StrictMode | Top)",
    "id": 0,
    "node": "Program",
    "symbols": [
      {
        "flag": "SymbolFlags(BlockScopedVariable | Function)",
        "id": 0,
        "name": "foo",
        "node": "Function(foo)",
        "references": [
          {
            "flag": "ReferenceFlag(Read)",
            "id": 0,
            "name": "foo",
            "node_id": 36
          }
        ]
      }
    ]
  }
]

authors: DonIsaac Dunqing overlookmotel

repo: oxc-project/oxc


text:
Component system

With a component system, I should be able to implement: Boulders, Bombs (#69), Fire, Corpses etc
I don't think Zemeroth needs a full-featured ECS solution (like specs) as the game is turn-based. A bunch of HashMap<ObjId, ComponentType> will do the work fine.
See:

https://gridbugs.org/programming-languages-make-terrible-game-engines
https://gridbugs.org/modifying-entity-component-system-for-turn-based-games
See https://github.com/rsaarelm/calx-ecs

What about froggy?)

Nope, I think that froggy is an overkill for this task too.

Draft: https://play.rust-lang.org/?gist=ec459f6ec32ddc899f788a1565e44edf

Working in the WIP_i105_components branch.

Rancor seems to work fine, but I see two issues:

Too many braces in RON file with prototypes
Duplication of data between initial values of strength and base_strength fields (same for base_moves, base_attacks, base_jokers)

({
    "swordsman": [
        Strength((
            base_strength: (4),
            strength: (4),
        )),
        Agent((
            moves: (1),
            attacks: (1),
            jokers: (1),
            reactive_attacks: (1),
            attack_distance: (1),
            move_points: (3),
            base_moves: (1),
            base_attacks: (1),
            base_jokers: (1),
        )),
    ],
})

But I'll create separate issues for this problems.

authors: ozkriff vitvakatu

repo: ozkriff/zemeroth


text:
Exporter Prometheus

Bonjour :)
Je regarde LiveboxMonitor depuis longtemps, et je me demande s'il serait un jour possible de bénéficier d'un sorte de mode "headless" en lecture seule permettant de faire tourner l'application comme un exporter de métriques pour Prometheus
J'ai conscience que l'appli est de base une GUI de management (entre autre), mais la richesse des informations affichées me fait penser qu'un exporter Prometheus pourrait être sympa pour monitorer et avoir des graphs d'utilisation sur des outils comme Grafana.
J'ai un petit peu regardé le code mais n'étant pas nécessairement très à l'aise avec Python, je préfère en parler ici tout d'abord pour voir si cela pourrait avoir un quelconque intérêt, et si oui, pourquoi pas essayer d'ajouter cette feature de mon côté (même si ça risque de prendre un peu de temps 😄)

Bonjour @Unyxos,
À priori c'est tout à fait possible, un exporter pour Python étant disponible.
Au niveau des metrics vous voyiez autre chose que les données statistiques de trafic par appareil et par interface ?
Je me demande aussi si c'est vraiment une autre application dérivée sans UI qui conviendrait ou si ajouter cette fonctionnalité (qui nécessitera de toute façon du réglage) ne serait pas suffisant.
Personnellement je n'en aurai pas l'usage (le tab "Graphe" me suffit amplement), mais si vous ou d'autres y voyez un intérêt, pourquoi pas ! Je peux regarder moi même (ça n'a pas l'air bien sorcier) ou vous guider dans le code si vous vous sentez de le faire vous même.

Bonjour :)
Super! Au niveau des metrics je pense que tout ce qui est déjà remonté est déjà très complet (stats / appareil et / interface)
Pour la seconde question, j'avoue que j'avais surtout en tête un cas d'usage ou cela serait lancé en mode "exporter" dans un container Docker ou quelque chose du genre sur un raspberry pi/mini serveur maison sans interface graphique, d'ou l'idée de pouvoir lancer ça directement via un flag en CLI
Je peux essayer de regarder pour le code plus tard ce mois ci :)

Bonjour @Unyxos, dans ce cas j'ai l'impression qu'il vaudrait mieux repartir d'un fork du projet, voire de zéro en simplement copiant le code nécessaire (session, gestion des événements et des threads qui chopent les stats), et en rajoutant l'exporter Prometheus. Et d'autres metrics pourraient être rajoutés facilement, comme l'évolution de la RAM disponible (qu'il faut poller régulièrement).

Hello, je me permets de faire ma pub 😄 Si vous pensez que c'est inapproprié dites le moi, je supprimerai mon message.
Je n'ai pas pu m'empêcher, cela fait pas mal de temps que je bosse sur ce sujet en particulier: https://github.com/Tomy2e/livebox-exporter
L'exporter ne fournit pas autant de données que LiveboxMonitor, j'ai voulu aller à l'essentiel.
Avant de commencer un nouveau projet, n'hésitez pas à tester ça. Je suis preneur de vos retours également !

Bonjour @Tomy2e et merci beaucoup pour partager votre travail ! Cela me semble tout à fait répondre au besoin exprimé ici.
@Unyxos pourriez vous jeter un oeil et confirmer que l'on peut fermer ce ticket avec livebox-exporter en solution ?
Petite amélioration possible @Tomy2e : pour le nombre de total de reboots il vaudrait mieux s'appuyer sur l'API NMC.Reboot:get (champ BootCounter) qui comptabilise le nombre total sur toute la vie de la Livebox. Avec DeviceInfo:get le champ NumberOfReboots donne en fait le nombre de reboots depuis la dernière mise à jour du firmware (le compteur repasse à zéro à chaque mise à jour).

En toute transparence, il existe également d'autres exporters pour Livebox, à voir en fonction de ce qui vous convient le mieux:

https://github.com/tchapacan/livebox-exporter-rs
https://github.com/jeanfabrice/livebox-exporter
https://github.com/eric-b/livebox-exporter

Merci pour la suggestion concernant le nombre total de reboots, je ne connaissais pas cette façon de récupérer l'info. Je vais l'implémenter car elle est plus fiable en effet !

authors: Tomy2e Unyxos p-dor

repo: p-dor/LiveboxMonitor


text:
Deleting an item should just be triggered with the ⌫ key

Problem
In Maccy's settings, there's an option to setup a custom shortcut to delete an item:

It's not very clear whether this shortcut is system-wide, but I think it's sort of pointless anyway.
Solution
There's a dedicated key on computer keyboards to remove stuff: the backspace key. How about we just use it? 😉
When an element is selected in Maccy's pop-up, I think simply pressing ⌫ should delete it.

How would it work if you had typed something into search? Should the last character in the search field or the highlighted item be removed?

I would say the search field takes precedence : if the search field is not empty, then pressing backspace removes the last character from the field. Otherwise it deletes the selected item.
To be accurate, there is very slight UI inconsistency in the current search UI of Maccy. Indeed, it's not very clear which element is focused:

Is the text-field focused? That would make sense since this is the element that receives (most) keyboard input. Plus it is what the blue vertical cursor would suggest.
Is the best matched item focused? This would make sense too since this is the element that is validated when pressing return. This is also what the blue selection hints at.

Let's compare it to another search field, for example in Settings.app:

In that scenario, it's clear which element is focused.
So that's for the underlying UI issue. That being said, I don't think it has to be changed, because the current behavior is indeed more efficient.
As an alternative, we could also have the following behavior:

Search field takes precedence
A (non-customizable) shortcut, maybe ⌘-⌫ specifically targets the selected item and deletes it right away, even if the search field is not empty.

if the search field is not empty, then pressing backspace removes the last character from the field. Otherwise it deletes the selected item.

That's going to be a huge issue, you type something to search, then hold the Delete key to clear it and suddenly your history starts removing.

Indeed, it's not very clear which element is focused:
...
So that's for the underlying UI issue.

In Maccy, the focus is always given both to the search field and the selected item. The first one is necessary for the search-as-you-type feature - you don't have to focus on the search field first. The second one is necessary for you to copy/paste right away by using arrow keys and Enter.
The overall UX is optimized for quick usage with as few keypresses as possible.


text:
Small Suggestion???

Stop negative values.

Not right yet as that allows value 0.00. Will update soon.

Not right yet as that allows value 0.00. Will update soon.

I really appreciate your help @Undefined-Variables That's really awesome what you do for the software!

@pH-7 How is $is_admin_auth passed to the view? Say i wanted to use it in another modules view? I can't see why its not working for me, tried everything I can think of?

This works but is it okay like this?
$this->view->is_admin_auth = AdminCore::auth();

@Undefined-Variables You set variables in the Model. So this part of the code shall reside in the "Model".
https://en.wikipedia.org/wiki/Model–view–controller

@polynamaude Thanks and that is what I thought! Solved my issue near enough as you said.

This works but is it okay like this?
$this->view->is_admin_auth = AdminCore::auth();

Sorry for my late reply @Undefined-Variables
Since this condition is used quite often in the view, that template variable is always available in the view. Meaning that you don't need to assign it to the view before, just use it like {if $is_admin_auth} (directly in .tpl files).
https://github.com/pH7Software/pH7-Social-Dating-CMS/blob/3e67488dc976d5f865572a2c811e0c41948d7308/_protected/framework/Mvc/Controller/Controller.class.php#L185
Good luck!

authors: Undefined-Variables pH-7 polynamaude


text:
training loss setting

Thanks for your great work!
In some HPE works, they gave some many loss to improve the result mpjpe, but in your training data, just 3D loss get great result. So there is a question that: do you try other loss composition such as 2d loss or smooth loss?
looking forward to your reply!

@paTRICK-swk


text:
Security and uniformity overhaul

Refactor of the different controllers and services. The goal is to remove all try/catch blocks by leveraging NestJS filters. The DTOs have been protected according to the Prisma schema. Route parameters have been protected using NestJS pipes.
Uniformity of responses throughout the API is intended, and done through the use of response interceptors.
Checklist:

[x] protect DTOs
[x] protect routes
[x] add prisma filter for exceptions
[ ] ensure uniformity of responses
[ ] remove all try/catch blocks
[ ] refactor regexes into validators

Not forget to run an eslint fix

authors: BioTheWolff lapsus-ord

repo: paastech-cloud/api