text:
Unable to Upgrade to Big Sur Beta

Describe the bug
Unable to boot into installer of Big Sur Beta when installed with OTA update, stuck with error message.

Expected behavior
It should boot into the installer with no issue
Configuration

HaC Mini version [e.g: 2.0]: 2.13
OSX version [e.g: 10.14.6]: 10.15.7
NUC model [e.g: NUC8i7HNK]: NUC8i7HVK
Boot SSD model and protocol [e.g: Samsung EVO 860 1TB, SATA]: Samsung 1TB, NVMe
Second SSD model and protocol (if installed) [e.g: HP EX920 1TB, NVMe]: N/A
First DIMM model [e.g: Patriot DDR4-2666 16GB]: Crucial DDR4-2400 16GB
Second DIMM model (if installed): N/A
Display port(s) used [e.g: USB-C, mini DP]: Mini DP + HDMI
Display resolution(s) [e.g: 4K, 5K]:
Any TB3 devices: N/A
Any USB devices: N/A
Any Wi-Fi/Bluetooth devices [e.g:DW1820A, BCM94360CS2, Intel 8265]: BCM94360CS2

When tried to boot through external USB installer, the HaC Mini Installer won't recognize the Installer USB as a installer, and when booting from it, it hangs at this error.

You can upgrade to the latest version of the Big sur system with either a freshå install or an online upgrade, and I tested the fresh install myself (following Mr. OSY86's tutorial exactly), and some other users tested the online upgrade with no problems.
However, there are some bugs, not sure whether they come from Hac-mini or Big sur, such as.
1, 4k 60hz display, the login interface resolution is too small, the content display is too large, this should be able to adjust the config file can be solved.
2. logging into the desktop stage, which will black screen and then reappear as content.
3, part of the shadow rendering of the dialog box is incorrect.
Nothing else yet, good experience, thanks Mr. OSY86!
Translated with www.DeepL.com/Translator (free version)

You can upgrade to the latest version of the Big sur system with either a freshå install or an online upgrade, and I tested the fresh install myself (following Mr. OSY86's tutorial exactly), and some other users tested the online upgrade with no problems.
However, there are some bugs, not sure whether they come from Hac-mini or Big sur, such as.
1, 4k 60hz display, the login interface resolution is too small, the content display is too large, this should be able to adjust the config file can be solved.
2. logging into the desktop stage, which will black screen and then reappear as content.
3, part of the shadow rendering of the dialog box is incorrect.
Nothing else yet, good experience, thanks Mr. OSY86!
Translated with www.DeepL.com/Translator (free version)

The installer won't boot with a OTA upgrade, as I said in the post.

You can upgrade to the latest version of the Big sur system with either a freshå install or an online upgrade, and I tested the fresh install myself (following Mr. OSY86's tutorial exactly), and some other users tested the online upgrade with no problems.
However, there are some bugs, not sure whether they come from Hac-mini or Big sur, such as.
1, 4k 60hz display, the login interface resolution is too small, the content display is too large, this should be able to adjust the config file can be solved.
2. logging into the desktop stage, which will black screen and then reappear as content.
3, part of the shadow rendering of the dialog box is incorrect.
Nothing else yet, good experience, thanks Mr. OSY86!
Translated with www.DeepL.com/Translator (free version)

The installer won't boot with a OTA upgrade, as I said in the post.

Please follow the hac-mini tutorial to install it without any problems. Clean up the nvram before installation, if you don't, the 4k display will be hua ping!

You can upgrade to the latest version of the Big sur system with either a freshå install or an online upgrade, and I tested the fresh install myself (following Mr. OSY86's tutorial exactly), and some other users tested the online upgrade with no problems.
However, there are some bugs, not sure whether they come from Hac-mini or Big sur, such as.
1, 4k 60hz display, the login interface resolution is too small, the content display is too large, this should be able to adjust the config file can be solved.
2. logging into the desktop stage, which will black screen and then reappear as content.
3, part of the shadow rendering of the dialog box is incorrect.
Nothing else yet, good experience, thanks Mr. OSY86!
Translated with www.DeepL.com/Translator (free version)

The installer won't boot with a OTA upgrade, as I said in the post.

Please follow the hac-mini tutorial to install it without any problems. Clean up the nvram before installation, if you don't, the 4k display will be hua ping!

I got the PCIe error when directly OTA upgrading.

I think I have the same issue with #342 , but I do not know how to fix it. I may have to wipe and reinstall macOS all over again.

I was able to upgrade to Big Sur by disabling SIP, creating a installer USB, install HaC Mini package onto that USB (the patch installer option grayed out), and boot into that USB, and finish the installation.


text:
Description for "Forgive minor mistakes"

Describe to the user when a mistake is considered to be minor (in a reasonable way). Problem here: This might change in the future.

DONE

source: gharchive/issue

license: mit

license_type: permissive

license_source: bigquery


text:
add text color for functions in advanced scripting window

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
Add text color to functions like Count(), Any(), Replace(), AddTable() - for any object type, Delete(), SetAnnotation(), GetAnnotation(), FormatDax(), EvaluateDax(), ExcecuteCommand(), ToString(), Where(), Append() etc.
Additional context
Think this would be helpful when reading & writing advanced scripts. Thanks!

I've tried to stick to the same syntax highlighting scheme as Visual Studio for C# code, where functions aren't color coded. Tabular Editor V3 will let you customise color schemes for both DAX and C# :-)

authors: m-kovalsky otykier

repo: otykier/TabularEditor

license: MIT

license_source: github-api


text:
Mail friends doesn't arrive

When you try to send a friend request, the mail never arrives.

@abom, can you investigate this issue plz? It happens when the third button in the screenshot is used.

I tested it more than once with latest android client (locally), and on Veurne app (production).
Both worked normally and the email arrives.
Can you please provide more info? time, which app...(and version).

authors: OSAMaureen abom bart-at-mobicage

repo: our-city-app/oca-backend


text:
无法打印“廖学峰python”在线文档

我尝试使用该工具打印“廖学峰python”在线文档（https://liaoxuefeng.com/books/python/introduction/index.html）
无论我怎样设置url，工具运行结果都是 “No Pages to Print”
工具在中文\英文的vue文档运行是正常的。

sorry，我没看懂文档需要插件来支持各类型网站的解析

repo: ourongxing/web-printer


text:
Require Python>=2.7.9/3.4.0 in setup.py

This pull request adds a check to the beginning is setup.py that exits when the current Python version is not >=2.7.9/3.4.0.
Closes #29.

Seems to work.
$ python setup.py install --user
ERROR: Python 2.7.9 or later required (you have 2.6.6)

source: gharchive/pull-request

authors: ikisusi jviide

repo: ouspg/trytls


text:
Support for TensorRT-LLM

Outlines currently support the vLLM inference engine, it would be great if it could also support the tensorRT-LLM inference engine.

Yes waiting for this as welll

TensorRT-LLM supports logits processors so it should be possible to integrate.
How are you hoping to use it? Are you seeking outlines.models.tensorrt, a serve endpoint, or both?

I'm looking at something similar to outlines.models.tensorrt right now as my usecase is mostly offline batched inference. Could you give me a starting point to how I can build this out, I'm eager to contribute and add such a feature.

@SupreethRao99 glad to hear you're interested in contributing.
I think a good starting point is looking into how TensorRT handles performs generation and handles LogitsProcessors
https://github.com/NVIDIA/TensorRT-LLM/blob/0ab9d17a59c284d2de36889832fe9fc7c8697604/tensorrt_llm/runtime/generation.py#L368-L386
https://github.com/NVIDIA/TensorRT-LLM/blob/0ab9d17a59c284d2de36889832fe9fc7c8697604/tensorrt_llm/runtime/model_runner_cpp.py#L266-L267
Then I'd review how llamacpp is being implemented, it shares similarities with how TensorRT would work https://github.com/outlines-dev/outlines/pull/556/ Specifically llamacpp.py https://github.com/dtiarks/outlines/blob/726ec242fb1695c5a67d489689be13ac84ef472c/outlines/models/llamacpp.py
Please let me know if you have any questions!

Thank you for the resources , I'll definitely get back to you with questions after going through these links.
Thanks!

Related to #655

This can likely be implemented with the Executor API:
https://github.com/NVIDIA/TensorRT-LLM/blob/31ac30e928a2db795799fdcab6be446bfa3a3998/examples/cpp/executor/README.md#L4

repo: outlines-dev/outlines


text:
微信分享悬浮框宽度不够，需要修改样式

修改后的内容
.social-share .icon-wechat .wechat-qrcode {
    width: 220px;
    left: -95px;
}
.wechat-qrcode .help p {
    padding-left: 8px;
}

我直接把width、left干掉就好了。 demo: https://youendless.com


text:
$message->MsgType使用时会提示该公众号服务出现故障

我用的环境
PHP 版本：7.3
overtrue/wechat 版本：4.0
是否使用了框架？框架名称：
laravel 5.7
问题及现象
描述你的问题现象，报错贴截图粘贴或者贴具体信息，提供必要的代码段
$wechat->server->push(function ($message) {
switch ($message->MsgType) {
case 'event':
return '收到事件消息';
break;
case 'text':
return '收到文字消息';
default:
return '收到其它消息';
});
return $wechat->server->serve();
可以运行官网文档提供的return "您好！欢迎使用 EasyWeChat";但是一判断消息类型就会出现该公众号提供的服务出现故障，请稍后再试

不好意思啊，把这个issues关了吧，我犯了个低级的错误

repo: overtrue/wechat


text:
强制项目不要自动获取AccessToken

我用的环境
PHP 版本：5.6
overtrue/wechat 版本：~3.1
问题及现象
因为AccessToken已经有一个脚本定时维护刷新，所以接入的overtrue/wechat的项目，不希望项目自动retry，除了，直接改你Core里面的抽象类，还有什么办法能比较好的解决这个问题？

不是有自定义 access token 的方法么？https://easywechat.org/zh-cn/docs/access_token.html#修改-app-的-Access-Token

设置AccessToken后，如果设置的AccessToken失效，就会Retry, 然后就悲剧了。其实最简单是修改你抽象累的retryMiddleware，但是，Vendor的文件本来就tracking。所以就很蛋疼了。

如果设置的AccessToken失效

所以你的那个自动脚本存在的意义并不大咯

@overtrue 主要是我多个环境需要用到同一个AccessToken。而且这个脚本跑了很久也没什么问题。就不想动这个脚本。anyway谢谢啦。

你的 token 来自脚本维护的对吧，那你的脚本保证了 “取到的 token 是可以正常非过期” 的
那既然 token 是没过期的，就肯定不会触发重试机制

@overtrue 这么说吧，token保存在生产环境的redis里，我在本地开发的时候，就需要从线上把token复制下来，然后再跑程序。但是，如果有人没有遵循这个规则，就有可能导致强token的情况，所以我希望把程序写死，token失效直接报错，而不是重新去获取。这么说明白吗？

@leocxy 看了一下 3.0 要做这个改动很不方便（设计上的原因决定了要可配置这里改动比较大，虽然可以实现但是破坏了统一性），所以这里暂时不做修改了，而且这里最多重试两次，其实也影响不大，我们将在 4.0 支持这个可配置特性。建议你现在 可以考虑解决 “如果有人没有遵循这个规则” 这个问题可能比较容易。 抱歉。

没有，只是我这边情况比较特殊，看看你有没有解决方案。谢谢拉。

authors: leocxy overtrue


text:
feat: Split payload and metadata from SSH plugin

As discussed /w @loopfz, it's better to split JSON payload object and execution metadata.
Signed-off-by: Valentin Pichard 7628998+w3st3ry@users.noreply.github.com

CDS Report test#172.0 ✘

Stage 1

Test ✘

CDS Report test#172.1 ✘

Stage 1

Test ✘

CDS Report test#172.2 ✘

Stage 1

Test ✘

CDS Report test#206.0 ✘

Stage 1

Test ✘

repo: ovh/utask


text:
tests failing from cosmos-sdk: t.TmpDir not defined

Not sure what is going on here.  They may be using a newer version of go, but I don't think that we updated the cosmos-sdk version lately?
vendor/github.com/cosmos/cosmos-sdk/testutil/network/network.go:172:34: t.TempDir undefined (type *testing.T has no field or method TempDir)

@boz please update your golang version. Required version 15.x

authors: anilCSE boz

repo: ovrclk/akash


text:
Fatal owtools Javadoc errors using Java 8

When I tried to build OWLTools using Maven, after about 6 minutes of doing stuff I get a whole bunch of errors and a build fail message. I have attached a text file with the list of errors, in case that matters.

Actually, I can't attach a file, so I will just paste the beginning of the list here:
100 errors
100 warnings
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] OWLTools-Parent .................................... SUCCESS [  1.103 s]
[INFO] OWLTools-Core ...................................... FAILURE [05:05 min]
[INFO] Lego ............................................... SKIPPED
[INFO] OWLTools-Annotation ................................ SKIPPED
[INFO] OWLTools-Oort ...................................... SKIPPED
[INFO] OWLTools-Sim ....................................... SKIPPED
[INFO] OWLTools-Web ....................................... SKIPPED
[INFO] OWLTools-Solr ...................................... SKIPPED
[INFO] OWLTools-Runner .................................... SKIPPED
[INFO] OWLTools-NCBI ...................................... SKIPPED
[INFO] Golr-Client ........................................ SKIPPED
[INFO] MolecularModelServer ............................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 05:06 min
[INFO] Finished at: 2015-04-04T15:11:06-07:00
[INFO] Final Memory: 35M/532M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar (attach-javadocs) on project OWLTools-Core: MavenReportException: Error while creating archive:
[ERROR] Exit code: 1 - /Users/rwalls-iplant/owltools/OWLTools-Core/src/main/java/owltools/cli/Opts.java:70: warning: no description for @param
[ERROR] * @param opt
[ERROR] ^
[ERROR] /Users/rwalls-iplant/owltools/OWLTools-Core/src/main/java/owltools/cli/Opts.java:169: warning: no description for @param
[ERROR] * @param params
[ERROR] ^
[ERROR] /Users/rwalls-iplant/owltools/OWLTools-Core/src/main/java/owltools/cli/Opts.java:170: warning: no description for @param
[ERROR] * @param desc
[ERROR] ^
[ERROR] /Users/rwalls-iplant/owltools/OWLTools-Core/src/main/java/owltools/diff/ReasonerDiff.java:27: warning: no description for @param
[ERROR] * @param newAxioms
[ERROR] ^
[ERROR] /Users/rwalls-iplant/owltools/OWLTools-Core/src/main/java/owltools/diff/ReasonerDiff.java:28: warning: no description for @param
[ERROR] * @param removedInferredAxioms
[ERROR] ^
...

Thanks for reporting the problem.
What java and maven version are you using?
These seem to be non-fatal Javadoc warnings. That should not cause the build to stop.
On a related note: we have a continuous integration test running for owltools. At the moment it compiles and passes all tests during the maven build. You can see the current status here:
http://build.berkeleybop.org/job/owltools/

I am using Maven 3.3.1 and Java 1.8.0_20. I had to set JAVA_HOME to point to the latest version before I could build.
It definitely failed to build! I can't use any of the tools.

I can reproduce the problem using Java8. There are two possible work-arounds until we fix the underlying issue:

Use the pre-built owltools/oort from Jenkins
Skip the javadoc during the owltools build: -Dmaven.javadoc.skip=true

The proper solution is to fix the Javadoc errors and also have an integration test using Java 8, in addition to the current Java 7 one in Jenkins.

Thanks! I will try to use the pre-built version. I have no desire to build it myself and just want to use a standard build. It might help to have a link to that on the home page here, if that will continue to be a viable option.
I do realize that this github site is still under construction.

The installation details are available in the OWLTools wiki. Unfortunately that is not very prominent on the landing page: Installing OWLTools

Ah...  You just made my life a lot easier!

Isn't it simply this issue? http://stackoverflow.com/questions/15886209/maven-is-not-working-in-java-8-when-javadoc-tags-are-incomplete
The fix is a one-liner in pom.xml.

Yes that seems to be the issue. It is necessary to use a Maven profile, otherwise the Java 7 built fails.
But we still should run the integration tests both on Java 7 and Java 8.

authors: fbastian hdietze rlwalls2008

repo: owlcollab/owltools


text:
Add a files-only mode

Currently, the file picker supports variations where only folders or both files and folders can be selected. What is missing is a mode where only files can be selected.

Would this be limited to any file? I am thinking if it would make sense to introduce an array of enabled mime types but that would probably be too overengineered?

My use case is just any files, but as long as the list of MIME types would allow wildcards, then that would work, too.
How would an array be passed to the web component?

How would an array be passed to the web component?

It could be a string * or png,jpeg, which we would then just split into an array inside of the component.

Works for me.
PS: Those are file extensions, not MIME types. That's mostly important for the documentation later, otherwise people will try using image/png or video/*.

authors: LukasHirt VP-

repo: owncloud/file-picker


text:
test client VFS with ocis

[x] client does not yet support oidc: https://github.com/owncloud/client/issues/7482

emulate oauth2 app?

[ ] test VFS

[x] client does not yet support oidc: owncloud/client#7482

2.7.0 daily builds fully support oCIS-OIDC :
https://download.owncloud.com/desktop/daily/?sort=time&order=desc

[ ]  test VFS

VFS should work independent from backend. No backend logic needed.

authors: butonic michaelstingl

repo: owncloud/ocis


text:
[QA] APi test apiSearch/dateSearch.feature:42 is failing

CI: https://drone.owncloud.com/owncloud/ocis/28263/25/7
Scenario Outline: search resources using different search patterns (KQL feature) in the personal space                                                                 # /drone/src/tests/acceptance/features/apiSearch/dateSearch.feature:21
    Given user "Alice" uploads a file "filesForUpload/textfile.txt" to "/today.txt" with mtime "today" via TUS inside of the space "Personal" using the WebDAV API       # SpacesTUSContext::userUploadsAFileToWithMtimeViaTusInsideOfTheSpaceUsingTheWebdavApi()
    And user "Alice" uploads a file "filesForUpload/textfile.txt" to "/yesterday.txt" with mtime "yesterday" via TUS inside of the space "Personal" using the WebDAV API # SpacesTUSContext::userUploadsAFileToWithMtimeViaTusInsideOfTheSpaceUsingTheWebdavApi()
    And user "Alice" uploads a file "filesForUpload/textfile.txt" to "/lastWeek.txt" with mtime "lastWeek" via TUS inside of the space "Personal" using the WebDAV API   # SpacesTUSContext::userUploadsAFileToWithMtimeViaTusInsideOfTheSpaceUsingTheWebdavApi()
    And user "Alice" uploads a file "filesForUpload/textfile.txt" to "/lastMonth.txt" with mtime "lastMonth" via TUS inside of the space "Personal" using the WebDAV API # SpacesTUSContext::userUploadsAFileToWithMtimeViaTusInsideOfTheSpaceUsingTheWebdavApi()
    And user "Alice" uploads a file "filesForUpload/textfile.txt" to "/lastYear.txt" with mtime "lastYear" via TUS inside of the space "Personal" using the WebDAV API   # SpacesTUSContext::userUploadsAFileToWithMtimeViaTusInsideOfTheSpaceUsingTheWebdavApi()
    And using spaces DAV path                                                                                # FeatureContext::usingOldOrNewDavPath()
    When user "Alice" searches for '<pattern>' using the WebDAV API                                                                                # SearchContext::userSearchesUsingWebDavAPI()
    Then the HTTP status code should be "207"                                                                                # FeatureContext::thenTheHTTPStatusCodeShouldBe()
    And the search result of user "Alice" should contain these entries:                                                                                # FeatureContext::thePropfindResultShouldContainEntries()
      | <search-result-1> |
      | <search-result-2> |
    But the search result of user "Alice" should not contain these entries:                                                                                # FeatureContext::thePropfindResultShouldContainEntries()
      | <search-result-3> |
      | <search-result-4> |

    Examples:
      | pattern            | search-result-1 | search-result-2 | search-result-3 | search-result-4 |
      | Mtime:today        | /today.txt      |                 | /yesterday.txt  | /lastWeek.txt   |
      | Mtime:yesterday    | /yesterday.txt  |                 | /today.txt      |                 |
      | Mtime:"this week"  | /today.txt      |                 | /lastWeek.txt   | /lastMont.txt   |
      | Mtime:"this month" | /today.txt      |                 | /lastMont.txt   |                 |
      | Mtime:"last month" | /lastMonth.txt  |                 | /today.txt      |                 |
        Failed step: But the search result of user "Alice" should not contain these entries:
        response does contain the entry '/today.txt' but should not
        Failed asserting that Array &0 (
            0 => SimpleXMLElement Object &000000004a7c430e000000001853932f (
                0 => 'today.txt'
            )
        ) is false.

==> REQUEST
REPORT /remote.php/dav/spaces/c72a6f6d-22f2-480b-8333-dd929b65cba8$6e857aa2-eaa7-4235-b999-934eac984ac5
X-Request-ID: apiSearch/dateSearch.feature:42-28
==> REQ BODY
<?xml version='1.0' encoding='utf-8' ?>
<oc:search-files xmlns:a='DAV:' xmlns:oc='http://owncloud.org/ns' >
  <oc:search>
    <oc:pattern>Mtime:"last month"</oc:pattern>
  </oc:search>
</oc:search-files>

RESPONSE
<== RESPONSE
207 Multi-Status
Transfer-Encoding: chunked
<== RES BODY
<d:multistatus
	xmlns:s="http://sabredav.org/ns"
	xmlns:d="DAV:"
	xmlns:oc="http://owncloud.org/ns">
  <d:response>
    <d:href>/remote.php/dav/spaces/c72a6f6d-22f2-480b-8333-dd929b65cba8$6e857aa2-eaa7-4235-b999-934eac984ac5/lastMonth.txt</d:href>
    <d:propstat>
      <d:prop>
        <oc:fileid>c72a6f6d-22f2-480b-8333-dd929b65cba8$6e857aa2-eaa7-4235-b999-934eac984ac5!28ea6a9e-2d63-4e6c-a3ff-db8d11c3b23f</oc:fileid>
        <oc:file-parent>c72a6f6d-22f2-480b-8333-dd929b65cba8$6e857aa2-eaa7-4235-b999-934eac984ac5!6e857aa2-eaa7-4235-b999-934eac984ac5</oc:file-parent>
        <oc:name>lastMonth.txt</oc:name>
        <d:getlastmodified>2023-10-01T00:00:00Z</d:getlastmodified>
        <d:getcontenttype>text/plain</d:getcontenttype>
        <oc:permissions>RDNVW</oc:permissions>
        <oc:highlights></oc:highlights>
        <oc:tags></oc:tags>
        <d:getetag></d:getetag>
        <d:resourcetype></d:resourcetype>
        <d:getcontentlength>28</d:getcontentlength>
        <oc:score>2.2801826000213623</oc:score>
      </d:prop>
      <d:status>HTTP/1.1 200 OK</d:status>
    </d:propstat>
  </d:response>
  <d:response>
    <d:href>/remote.php/dav/spaces/c72a6f6d-22f2-480b-8333-dd929b65cba8$6e857aa2-eaa7-4235-b999-934eac984ac5/today.txt</d:href>
    <d:propstat>
      <d:prop>
        <oc:fileid>c72a6f6d-22f2-480b-8333-dd929b65cba8$6e857aa2-eaa7-4235-b999-934eac984ac5!d87d4efe-68df-47bd-b691-a0dde234a906</oc:fileid>
        <oc:file-parent>c72a6f6d-22f2-480b-8333-dd929b65cba8$6e857aa2-eaa7-4235-b999-934eac984ac5!6e857aa2-eaa7-4235-b999-934eac984ac5</oc:file-parent>
        <oc:name>today.txt</oc:name>
        <d:getlastmodified>2023-10-31T00:00:00Z</d:getlastmodified>
        <d:getcontenttype>text/plain</d:getcontenttype>
        <oc:permissions>RDNVW</oc:permissions>
        <oc:highlights></oc:highlights>
        <oc:tags></oc:tags>
        <d:getetag></d:getetag>
        <d:resourcetype></d:resourcetype>
        <d:getcontentlength>28</d:getcontentlength>
        <oc:score>2.040480852127075</oc:score>
      </d:prop>
      <d:status>HTTP/1.1 200 OK</d:status>
    </d:propstat>
  </d:response>
  <d:response>
    <d:href>/remote.php/dav/spaces/c72a6f6d-22f2-480b-8333-dd929b65cba8$6e857aa2-eaa7-4235-b999-934eac984ac5/yesterday.txt</d:href>
    <d:propstat>
      <d:prop>
        <oc:fileid>c72a6f6d-22f2-480b-8333-dd929b65cba8$6e857aa2-eaa7-4235-b999-934eac984ac5!b3dfc698-4afe-497b-b2f3-be930198e392</oc:fileid>
        <oc:file-parent>c72a6f6d-22f2-480b-8333-dd929b65cba8$6e857aa2-eaa7-4235-b999-934eac984ac5!6e857aa2-eaa7-4235-b999-934eac984ac5</oc:file-parent>
        <oc:name>yesterday.txt</oc:name>
        <d:getlastmodified>2023-10-30T00:00:00Z</d:getlastmodified>
        <d:getcontenttype>text/plain</d:getcontenttype>
        <oc:permissions>RDNVW</oc:permissions>
        <oc:highlights></oc:highlights>
        <oc:tags></oc:tags>
        <d:getetag></d:getetag>
        <d:resourcetype></d:resourcetype>
        <d:getcontentlength>28</d:getcontentlength>
        <oc:score>2.040480852127075</oc:score>
      </d:prop>
      <d:status>HTTP/1.1 200 OK</d:status>
    </d:propstat>
  </d:response>
  <d:response>
    <d:href>/remote.php/dav/spaces/c72a6f6d-22f2-480b-8333-dd929b65cba8$6e857aa2-eaa7-4235-b999-934eac984ac5/lastWeek.txt</d:href>
    <d:propstat>
      <d:prop>
        <oc:fileid>c72a6f6d-22f2-480b-8333-dd929b65cba8$6e857aa2-eaa7-4235-b999-934eac984ac5!d510ba2c-4b3c-4e37-9196-324e182bfd2e</oc:fileid>
        <oc:file-parent>c72a6f6d-22f2-480b-8333-dd929b65cba8$6e857aa2-eaa7-4235-b999-934eac984ac5!6e857aa2-eaa7-4235-b999-934eac984ac5</oc:file-parent>
        <oc:name>lastWeek.txt</oc:name>
        <d:getlastmodified>2023-10-24T00:00:00Z</d:getlastmodified>
        <d:getcontenttype>text/plain</d:getcontenttype>
        <oc:permissions>RDNVW</oc:permissions>
        <oc:highlights></oc:highlights>
        <oc:tags></oc:tags>
        <d:getetag></d:getetag>
        <d:resourcetype></d:resourcetype>
        <d:getcontentlength>28</d:getcontentlength>
        <oc:score>2.040480852127075</oc:score>
      </d:prop>
      <d:status>HTTP/1.1 200 OK</d:status>
    </d:propstat>
  </d:response>
  <d:response>
    <d:href>/remote.php/dav/spaces/c72a6f6d-22f2-480b-8333-dd929b65cba8$6e857aa2-eaa7-4235-b999-934eac984ac5</d:href>
    <d:propstat>
      <d:prop>
        <oc:fileid>c72a6f6d-22f2-480b-8333-dd929b65cba8$6e857aa2-eaa7-4235-b999-934eac984ac5!6e857aa2-eaa7-4235-b999-934eac984ac5</oc:fileid>
        <oc:file-parent>c72a6f6d-22f2-480b-8333-dd929b65cba8$6e857aa2-eaa7-4235-b999-934eac984ac5</oc:file-parent>
        <oc:name>Alice Hansen</oc:name>
        <d:getlastmodified>2023-10-31T06:31:12Z</d:getlastmodified>
        <d:getcontenttype>httpd/unix-directory</d:getcontenttype>
        <oc:permissions>RDNVCK</oc:permissions>
        <oc:highlights></oc:highlights>
        <oc:tags></oc:tags>
        <d:getetag></d:getetag>
        <d:resourcetype>
          <d:collection/>
        </d:resourcetype>
        <oc:size>140</oc:size>
        <oc:score>1.9607993364334106</oc:score>
      </d:prop>
      <d:status>HTTP/1.1 200 OK</d:status>
    </d:propstat>
  </d:response>
</d:multistatus>

The log shows that the month for all files is 10 (Oct).

This could be due to the differences in timezone

search doesn't work properly with date 31?

When the date is 31: (same date range for both :question:)

Mtime: "this month"Start: 63831694500 # Wednesday, September 30, 3992 12:00:00 AM GMT+05:45
End: 63834372899 # Friday, October 30, 3992 11:59:59 PM GMT+05:45

Mtime: "last month"Start: 63831694500 # Wednesday, September 30, 3992 12:00:00 AM GMT+05:45
End: 63834372899 # Friday, October 30, 3992 11:59:59 PM GMT+05:45

When the date is NOT 31: (different date range for both :heavy_check_mark:)

Mtime: "this month"Start: 63831694500 # Wednesday, September 30, 3992 12:00:00 AM GMT+05:45
End: 63834372899 # Friday, October 30, 3992 11:59:59 PM GMT+05:45

Mtime: "last month"Start: 63829102500 # Monday, August 31, 3992 12:00:00 AM GMT+05:45
End: 63831694499 # Tuesday, September 29, 3992 11:59:59 PM GMT+05:45


text:
Inconsistent Audit Log

When I share a folder, the audit log shows this as file.
When I share a space, the audit log shows this as a space.
Please make the share of a folder transparent to the audit log.

Please add "create new version" to audit log

@dj4oC could you please adjust the bug description in the Is and Should style, i.e. (for me its not completely clear what you need)
Actual behavior
...
Expected behavior
...

@tbsbdr @micbar
I hope this helps. I cannot desc what my expected behavior is, but my questions might lead you to the answers.
Generally speaking: why are the fields and their order not consistent?
I will try to collect other events too, but as I mentioned already: edit space members is missing, "create new version" is shown as "create file" (similar misleading like renaming is shown as "move file")

The more I go through all this, the more I ask myself: would that actually help me? and in what case?
Use case 1: understanding user behavior: in that case I would love to have grafana counters instead of audit log files to be parsed.
use case 2: cyber security forensic: understanding a suspicious  behavior. in that case I would always need source IP and user agent filled.
use case 3: understanding what happened to a file / folder: in  that case I would always need some kind of clear text instead of file ids and folder ids next to the technical ids

Maybe related: https://github.com/owncloud/ocis/issues/7971

{
"action": "space_shared",
"app": "admin_audit",
"cli": false,
"granteegroupid": "",
"granteeuserid": "4a370541-5e6e-4532-9c3a-2069072f2746",
"level": 1,
"message": "user '2d589cfe-6cd0-4aec-9268-3cc63d4fa7bf' shared the space '557875ba-e440-45e0-9788-edcd761a97b6' with 'user:4a370541-5e6e-4532-9c3a-2069072f2746' (storage: 'f8e95455-ceb1-4355-8457-a9cb798e6ea6')",
"method": "",
"remoteaddr": "",
"spaceid": "f8e95455-ceb1-4355-8457-a9cb798e6ea6$557875ba-e440-45e0-9788-edcd761a97b6",
"time": "",
"url": "",
"user": "",
"useragent": ""
}
- Question: Why are $method, $remoteaddr, $url, $user, $useragent, $granteegroupid, $time empty?

{
"remoteaddr":"",
"user":"",
"url":"",
"method":"",
"useragent":"",
"time":"2024-08-05t06:21:58Z",
"app":"admin_audit",
"message":
"user '2d589cfe-6cd0-4aec-9268-3cc63d4fa7bf' updated space '557875ba-e440-45e0-9788-edcd761a97b6!557875ba-e440-45e0-9788-edcd761a97b6'.
name: '$name',
quota: '0',
opaque: 'map[etag:"2d79b76adadeccf6afe723e63d961a2c"
grants: grants_expirations:
groups: image:557875ba-e440-45e0-9788-edcd761a97b6!2721707f-1c95-4133-81d4-389ad1895719
quota.remaining:5492442791936
quota.total:0
quota.used:6055728
readme:557875ba-e440-45e0-9788-edcd761a97b6!6cf23641-3827-46ad-83ff-f13c3602139a
spacealias:$spacealias]'
(storage: 'f8e95455-ceb1-4355-8457-a9cb798e6ea6')",
"action":"space_updated",
"cli":false,
"level":1,
"spaceid":"f8e95455-ceb1-4355-8457-a9cb798e6ea6$557875ba-e440-45e0-9788-edcd761a97b6!557875ba-e440-45e0-9788-edcd761a97b6",
"name":"Lorem Ipsum",
"opaque":
{"etag":""2d79b76adadeccf6afe723e63d961a2c"",
"grants":"",
"grants_expirations":"",
"groups":"",
"image":"557875ba-e440-45e0-9788-edcd761a97b6!2721707f-1c95-4133-81d4-389ad1895719",
"quota.remaining":"5492442791936",
"quota.total":"0",
"quota.used":"6055728",
"readme":"557875ba-e440-45e0-9788-edcd761a97b6!6cf23641-3827-46ad-83ff-f13c3602139a",
"spacealias":"foo/baa"},
"quotamaxbytes":0
}
- JSON parser does not accept this input
- Question: Why are $method, $remoteaddr, $url, $user, $useragent, empty?

{
    "action": "space_unshared",
    "app": "admin_audit",
    "cli": false,
    "granteegroupid": "",
    "granteeuserid": "a596adc2-611b-4f5f-b0c8-90896c5fd855",
    "level": 1,
    "message": "user '24363869-4fb2-4f36-b106-d3ca05a9da14' unshared the space '49b4eb7b-967b-49d0-8dbb-be048c1800fe' with 'user:a596adc2-611b-4f5f-b0c8-90896c5fd855' (storage: 'c1e23045-8f04-408d-ab2b-3eb62a3b4a32')",
    "method": "",
    "remoteaddr": "",
    "spaceid": "c1e23045-8f04-408d-ab2b-3eb62a3b4a32$49b4eb7b-967b-49d0-8dbb-be048c1800fe",
    "time": "2024-08-05t07:18:54Z",
    "url": "",
    "user": "",
    "useragent": ""
}

Question: Why are $method, $remoteaddr, $url, $user, $useragent, $granteegroupid empty?

is space_unshared == revoke space membership and
space_shared == grant space membership ?

{
    "action": "",
    "app": "admin_audit",
    "cli": false,
    "fileid": "2026ca7b-ae8b-4eb0-bc6d-b3f9a81f67e0",
    "itemtype": "",
    "level": 1,
    "message": "",
    "method": "",
    "owner": "0d0d00d7-75f1-4383-bec3-176e864ee172",
    "path": "",
    "remoteaddr": "",
    "shareid": "8195b18e-a69c-5767-b4c5-c97078d5d3e1:0d0d00d7-75f1-4383-bec3-176e864ee172:512d69c1-5ddc-4756-aab4-e9047b744a25",
    "sharetype": "user",
    "sharewith": "f59379b3-d2fe-4380-ad6d-40316b05b639",
    "time": "2023-11-29t07:43:29Z",
    "url": "",
    "user": "f59379b3-d2fe-4380-ad6d-40316b05b639",
    "useragent": ""
}

Question: Why are $method, $remoteaddr, $url, $useragent, $action, $itemtype, $message, $path,   empty?
What kind of action is this?

@dj4oC i would not dig deep into the reasoning why things are like they are, nobody knows.
The audit service had the requirement that all message bodies should look exactly like ownCloud10 to make use of the Splunk app in the Splunk app store. This requirement is now completely gone.
Time for a refactoring.
@tbsbdr should be scheduled according to the prio.

@dj4oC i would not dig deep into the reasoning why things are like they are, nobody knows.
The audit service had the requirement that all message bodies should look exactly like ownCloud10 to make use of the Splunk app in the Splunk app store. This requirement is now completely gone.
Time for a refactoring.
@tbsbdr should be scheduled according to the prio.

The Splunk Plugin is archived and not compatible anymore: https://splunkbase.com/app/5502/
If you are going to refactor it, I would appreciate if we add a grafana counter to each action

{
    "remoteaddr":"",
    "user":"942b0905-fe39-4a84-b3aa-ab962fd4a99f",
    "url":"",
    "method":"",
    "useragent":"",
    "time":"2024-08-01t16:30:37Z",
    "app":"admin_audit",
    "message":"user '942b0905-fe39-4a84-b3aa-ab962fd4a99f' updated field 'TYPE_PASSWORD' of public link 'MUnlxxxJvozPlqj'",
    "action":"share_password_updated",
    "cli":false,
    "level":1,
    "fileid":"61f68f0a-f10b-4a31-9f53-5fd5b90af90e",
    "owner":"942b0905-fe39-4a84-b3aa-ab962fd4a99f",
    "path":"",
    "shareid":"MUnlxxxJvozPlqj",
    "itemtype":"",
    "expirationdate":"",
    "sharepass":true,
    "permissions":"get_path:true get_quota:true initiate_file_download:true initiate_file_upload:true list_container:true list_recycle:true restore_recycle_item:true stat:true ",
    "sharetype":"link",
    "sharewith":"",
    "shareowner":"942b0905-fe39-4a84-b3aa-ab962fd4a99f",
    "sharetoken":"vOrJItxxxCDJExY"
  }

Question: Why are $method, $remoteaddr, $url, $useragent, $action, $itemtype, $message, $path, $expirationdate, $sharewith  empty?

  {
    "remoteaddr":"",
    "user":"942b0905-fe39-4a84-b3aa-ab962fd4a99f",
    "url":"",
    "method":"",
    "useragent":"",
    "time":"2024-08-01t16:30:37Z",
    "app":"admin_audit",
    "message":"user '942b0905-fe39-4a84-b3aa-ab962fd4a99f' updated field 'TYPE_PERMISSIONS' of public link 'MUnlxxxvozPlqj'",
    "action":"share_permission_updated",
    "cli":false,
    "level":1,
    "fileid":"61f68f0a-f10b-4a31-9f53-5fd5b90af90e",
    "owner":"942b0905-fe39-4a84-b3aa-ab962fd4a99f",
    "path":"",
    "shareid":"MUnlxxxvozPlqj",
    "itemtype":"",
    "expirationdate":"",
    "sharepass":true,
    "permissions":"get_path:true get_quota:true initiate_file_download:true initiate_file_upload:true list_container:true list_recycle:true restore_recycle_item:true stat:true ",
    "sharetype":"link",
    "sharewith":"",
    "shareowner":"942b0905-fe39-4a84-b3aa-ab962fd4a99f",
    "sharetoken":"vOrJItYXfCDJExY"
}

{
    "remoteaddr":"",
    "user":"5da1d769-3e9f-43a9-899d-763ec77ba908",
    "url":"",
    "method":"",
    "useragent":"",
    "time":"2024-08-05t08:07:00Z",
    "app":"admin_audit",
    "message":"user '5da1d769-3e9f-43a9-899d-763ec77ba908' created a public link to file '2ff8e897-b56e-4a68-8b2d-1ea361497684' with id 'yEyEkJnxxxcCiN'",
    "action":"file_shared",
    "cli":false,
    "level":1,"fileid":"2ff8e897-b56e-4a68-8b2d-1ea361497684",
    "owner":"5da1d769-3e9f-43a9-899d-763ec77ba908",
    "path":"",
    "shareid":"",
    "itemtype":"",
    "expirationdate":"",
    "sharepass":true,
    "permissions":"permissions:\u003ccreate_container:true get_path:true get_quota:true initiate_file_download:true initiate_file_upload:true list_container:true list_recycle:true stat:true \u003e ",
    "sharetype":"link",
    "sharewith":"",
    "shareowner":"5da1d769-3e9f-43a9-899d-763ec77ba908",
    "sharetoken":"uBjgCagptZbXofZ"
}

sharetype can be  and

{
    "action": "space_deleted",
    "app": "admin_audit",
    "cli": false,
    "level": 1,
    "message": "user '24363869-4fb2-4f36-b106-d3ca05a9da14' deleted the space '13b24c4f-b834-445e-b6db-eb7592b150f7' (storage: 'c1e23045-8f04-408d-ab2b-3eb62a3b4a32')",
    "method": "",
    "remoteaddr": "",
    "spaceid": "c1e23045-8f04-408d-ab2b-3eb62a3b4a32$13b24c4f-b834-445e-b6db-eb7592b150f7",
    "time": "2024-08-05t08:05:03Z",
    "url": "",
    "user": "",
    "useragent": ""
}

{
    "action": "space_disabled",
    "app": "admin_audit",
    "cli": false,
    "level": 1,
    "message": "user '24363869-4fb2-4f36-b106-d3ca05a9da14' disabled the space '13b24c4f-b834-445e-b6db-eb7592b150f7' (storage: 'c1e23045-8f04-408d-ab2b-3eb62a3b4a32')",
    "method": "",
    "remoteaddr": "",
    "spaceid": "c1e23045-8f04-408d-ab2b-3eb62a3b4a32$13b24c4f-b834-445e-b6db-eb7592b150f7",
    "time": "2024-08-05t08:04:41Z",
    "url": "",
    "user": "",
    "useragent": ""
}

{
    "remoteaddr":"",
    "user":"",
    "url":"",
    "method":"",
    "useragent":"",
    "time":"2024-08-05t08:29:42Z",
    "app":"admin_audit",
    "message":"user '3635a66d-518c-44fc-befe-e1d44367640b' renamed space '3591363c-68bd-4a72-894b-082a99c4d10f!3591363c-68bd-4a72-894b-082a99c4d10f' to '9b Physik' (storage: '25ede41b-527b-4b52-9bde-0966d2056206')",
    "action":"space_renamed",
    "cli":false,
    "level":1,
    "spaceid":"25ede41b-527b-4b52-9bde-0966d2056206$3591363c-68bd-4a72-894b-082a99c4d10f!3591363c-68bd-4a72-894b-082a99c4d10f",
    "newname":"9b Physik"
  }

JSON formaer does not accept this input
what was the old name of the space?
Why are $remoteaddr, $user, $url, $method, $useragent empty?

{
    "action": "file_unshared",
    "app": "admin_audit",
    "cli": false,
    "fileid": "",
    "itemtype": "",
    "level": 1,
    "message": "share id:'8195b18e-a69c-5767-b4c5-c97078d5d3e1:2507ed59-d86c-4f2c-8f30-8eb2de3801f8:90547b66-92cc-4272-bf5c-3a62fb3ba5c8' uid:'' item-id:'' was removed",
    "method": "",
    "owner": "",
    "path": "",
    "remoteaddr": "",
    "shareid": "8195b18e-a69c-5767-b4c5-c97078d5d3e1:2507ed59-d86c-4f2c-8f30-8eb2de3801f8:90547b66-92cc-4272-bf5c-3a62fb3ba5c8",
    "sharetype": "",
    "sharewith": "",
    "time": "2024-08-05t08:54:00Z",
    "url": "",
    "user": "",
    "useragent": ""
  }

why is $fileid, $itemtype, $method, $owner, $path, $remoteaddr, $sharetype, $sharewith, $url, $user, $useragent empty?
why is uid:'' item-id:'' in the message tag empty?

{
  "remoteaddr": "",
  "user": "",
  "url": "",
  "method": "",
  "useragent": "",
  "time": "2024-08-05t12:05:32Z",
  "app": "admin_audit",
  "message": "user '69eea927-ae5f-41ba-8d0e-971830bcc7ab' (re-) enabled the space '48e447a5-982d-44c3-afcf-872f7273ef4c!48e447a5-982d-44c3-afcf-872f7273ef4c' (storage: '2061b89f-49c0-5d51-8d67-ed01c4c10527')",
  "action": "space_enabled",
  "cli": false,
  "level": 1,
  "spaceid": "2061b89f-49c0-5d51-8d67-ed01c4c10527$48e447a5-982d-44c3-afcf-872f7273ef4c!48e447a5-982d-44c3-afcf-872f7273ef4c"
}

I dont think we should keep oC10 compatibility moving forward. If  and which additions make sense needs to be investigated. @tbsbdr @micbar  should we take that to the roadmap backlog?

authors: dj4oC dragotin micbar tbsbdr wkloucek


text:
bring back identifier-registration.yaml, strip commented stuff, rebuild embed.go

Description
konnectd/assets/identifier-registration.yaml was removed in #1390 but should have been moved to idp/assets/identifier-registration.yaml
This PR brings back the file, removes commented stuff from that file. In order to build the embed.go file in CI, also the Makefile and CI was fixed.
Related Issue

Motivation and Context

How Has This Been Tested?

local test -> login possible

Screenshots (if appropriate):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[ ] Tests only (no source changes)

Checklist:

[ ] Code changes
[ ] Unit tests added
[ ] Acceptance tests added
[ ] Documentation ticket raised:

https://drone.owncloud.com/owncloud/ocis/3142/75/2
docker-arm: Error response from daemon: No such image: owncloudci/nodejs:12
It looks like https://hub.docker.com/r/owncloudci/nodejs/tags?page=1&ordering=last_updated is only amd64

https://drone.owncloud.com/owncloud/ocis/3142/75/2
docker-arm: Error response from daemon: No such image: owncloudci/nodejs:12
It looks like https://hub.docker.com/r/owncloudci/nodejs/tags?page=1&ordering=last_updated is only amd64

CI related part moved to #1580

authors: phil-davis wkloucek


text:
refactor(ast, transformer)!: remove BlockStatement::new methods

First of a series of PRs removing new and new_with_scope_id etc methods from AST types. Following #6760, all AST node creation can now go via the AST builder.
This lays groundwork for Node IDs (#5689), as we'll need NodeIds to be generated in AstBuilder, so that all nodes receive an ID.

#6788
#6787
#6786
#6785
#6784
#6783  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite

@Boshen I imagine something in this stack will break Rolldown. I assume they have access to AstBuilder, so it'll be an easy fix to migrate over to using AstBuilder methods to generate nodes?

repo: oxc-project/oxc


text:
[Ques] Font in the screenshot

https://github.com/oxfist/night-owl.nvim/blob/main/img%2Fcalculator.png

@niksingh710 it's MonoLisa!


text:
Release/v0.2.0

Completa refatoração do Logger para remover a dependência do Winston e melhorar sua performance.
Com isso alguns suportes foram removidos, por exemplo:

conexão com MongoDB
escrita de logs para arquivos

Em relação a utilização do Logger, não deve haver nenhuma incompatibilidade com as versões anteriores. É recomendado apenas utilizar da função createLogger para instanciar o logger, visto que o método .init() foi deprecado.
A principal mudança agora envolve a remoção completa da intercomunicação IPC para alteração da verbosidade do logger durante a execução das aplicações. Houve uma substituição por um servidor HTTP implementado a partir do módulo http do nodejs, favorecendo leveza e performance, dessa maneira é possível continuar alterando a verbosidade dos logs através de um request HTTP.
O módulo conta com as seguintes variáveis de ambiente para configurar o comportamento dos logs:

OZLOGGER_LEVEL=debug : nível padrão dos logs
OZLOGGER_OUTPUT=json : formato de saída dos logs
OZLOGGER_COLORS=false : atribui cor aos logs
OZLOGGER_SERVER=9898 : porta na qual o servidor HTTP irá ouvir (localhost)

Closes #5

repo: ozmap/ozlogger


text:
Homebridge-config-Uni-x.service

@oznu
after install hb-service the created Homebridge-config-ui-x.service contain default user “homebridge”
[Unit]
Description=Homebridge Config UI X
After=syslog.target network-online.target
[Service]
Type=simple
User=homebridge
EnvironmentFile=/etc/default/homebridge
ExecStart=/usr/bin/homebridge-config-ui-x $HOMEBRIDGE_OPTS
Restart=on-failure
RestartSec=3
KillMode=process
CapabilityBoundingSet=CAP_IPC_LOCK CAP_NET_ADMIN CAP_NET_BIND_SERVICE CAP_NET_RAW CAP_SETGID CAP_SETUID CAP_SYS_CHROOT CAP_CHOWN CAP_FOWNER CAP_DAC_OVERRIDE CAP_AUDIT_WRITE CAP_SYS_ADMIN
AmbientCapabilities=CAP_NET_RAW

[Install]
WantedBy=multi-user.target

for me it is not true, I do not use this user, how to change? If I change it manually after every reinstall the user changed.

Hi @grzegorz914,
If you've setup Homebridge using hb-service there is no need to use "standalone" mode which is what the homebridge-config-ui-x.service systemd service file is used for.
hb-service replaces the need for standalone mode and uses homebridge.service by default.
You can remove the homebridge-config-ui-x.service using these commands:
systemctl stop homebridge-config-ui-x
systemctl disable homebridge-config-ui-x
rm -rf /etc/systemd/system/homebridge-config-ui-x.service
systemctl daemon-reload

I hope this answers your question?
Standalone mode still works, but should not be used in conjunction with hb-service. I need to update the wiki page for standalone directing people to use hb-service instead.

Added a note to the top of the standalone mode wiki page: https://github.com/oznu/homebridge-config-ui-x/wiki/Standalone-Mode

repo: oznu/homebridge-config-ui-x


text:
Added a network widget

It displays sent & received megabytes per second as well as a graph of the overall throughput per second.

Need a small fix, I'm going to recreate the pull request.


text:
Update vue-virtual-scroll-list and vuedraggable version

Based on the vue-virtual-scroll-list, changed the props name and added extra-props for extra props to the items
also fixed the typo and example and added realOldIndex and realNewIndex in the start end event
Also published in npm
https://www.npmjs.com/package/vue-draggable-virtual-scroll-list

why not a devDependency? :)

We need to extends the sortablejs interface if we put it on devDependency it will miss the sortablejs typing
and for the indent will do
Thanks for the review


text:
uwsgi cannot be started

When I try to use this docker image, I had the following error:
pppp@docker1:~$ docker run -p 80:80 p0bailey/docker-flask
/usr/lib/python2.7/dist-packages/supervisor/options.py:295: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
'Supervisord is running as root and it is searching '
2016-07-26 03:11:39,632 CRIT Supervisor running as root (no user in config file)
2016-07-26 03:11:39,632 WARN Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
2016-07-26 03:11:39,651 INFO RPC interface 'supervisor' initialized
2016-07-26 03:11:39,652 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2016-07-26 03:11:39,652 INFO supervisord started with pid 1
2016-07-26 03:11:40,654 INFO spawned: 'nginx' with pid 7
2016-07-26 03:11:40,656 INFO spawned: 'uwsgi' with pid 8
2016-07-26 03:11:40,666 INFO exited: uwsgi (exit status 1; not expected)
2016-07-26 03:11:41,671 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-07-26 03:11:41,672 INFO spawned: 'uwsgi' with pid 13
2016-07-26 03:11:41,677 INFO exited: uwsgi (exit status 1; not expected)
2016-07-26 03:11:43,681 INFO spawned: 'uwsgi' with pid 14
2016-07-26 03:11:43,686 INFO exited: uwsgi (exit status 1; not expected)
2016-07-26 03:11:46,691 INFO spawned: 'uwsgi' with pid 15
2016-07-26 03:11:46,696 INFO exited: uwsgi (exit status 1; not expected)
2016-07-26 03:11:47,698 INFO gave up: uwsgi entered FATAL state, too many start retries too quickly
Seems to be related to supervisord and uwsgi, but not sure what's the cause of this.

Because of the directory /var/log/{nginx,uwsgi}
it must be departed.
like RUN mkdir -p /var/log/nginx /var/log/uwsgi

authors: kaya-mikio theonlypippo


text:
This script suck

This script is a real example of a poorly made program. They don't even load in a service like XAMPP or LAMPP to test...
It is very poorly documented installation and there are no error files.
On the Hostinger server it simply does not load the initial page and does not indicate the possible error and where to find it...
There is also no access to previous versions.
The one who makes a good installation script for Softacoulus or Fantastico is assured a prize...

I think you have some issues with your PHP environment. The server requirements can be found at https://ph7builder.com/doc/en/requirements
Thank you for sharing your frustrations, but it's a bit hard to help you here with only little information about the reason/error why it doesn't work for you.

I'm just getting going on PH7.  Did you find a way to load using XAMPP?

authors: MarceloRojasOlivos ediblepeachey pH-7


text:
Issue #1026

Issuing pull request to fix this issue

Looks good overall with a minor comment.

And thanks for your contribution.

Merging. I'll make the small change by myself.

Forget my comment. The property was used in another method.

authors: leleuj scoldwell


text:
list-job not working in 1.6.0rc5

@JoeyZwicker, myself, and a couple users have been seeing this.  Apparently all the expected jobs are running and producing output (as judging by the repos and files), but pachctl list-job won't list the jobs that are running.  We have seen this so far with minikube and in the cloud (GKE).
$ pachctl list-repo
NAME                CREATED             SIZE
montage             16 minutes ago      1.653MiB
edges               16 minutes ago      155.8KiB
images              17 minutes ago      238.3KiB
$ pachctl list-job
ID OUTPUT COMMIT STARTED DURATION RESTART PROGRESS DL UL STATE

User [12:42 PM]
hi @dwhitena the fix on pachctl list-job now working, but not for all
User [12:42 PM]
added this Plain Text snippet
ip-192-168-1-26:pachyderm-pipeline-poc ettieeyre$ pachctl list-job
ID OUTPUT COMMIT STARTED DURATION RESTART PROGRESS DL UL STATE
ip-192-168-1-26:pachyderm-pipeline-poc ettieeyre$ pachctl list-job -p edges
ID                  OUTPUT COMMIT             STARTED    DURATION RESTART PROGRESS DL    UL    STATE
b782ebe8-200f-4622-9936-18838fa8032c edges/1a4293c5ae31447fb1ae64a723db61d0 38 seconds ago 6 seconds 0    1 + 0 / 1 57.27KiB 22.22KiB success
Add Comment
User [12:42 PM]
only when you specify a pipeline

Yeah I was seeing this too.  I will look into it.

authors: derekchiang dwhitena

repo: pachyderm/pachyderm


text:
Don't run TestParallelismSpec in short mode

Since it needs the k8s client to run

authors: msteffen sjezewski


text:
Minimizes the pachd container image.

Pachd image is now 60MB total and it's probably not getting much smaller since that's nothing more than the go binary and some certificates.

authors: derekchiang jdoliner


text:
Empty namespace(groupId) for maven does not throw exception

While parsing pkg:maven//a@v?&type=e one would expect that an exception is thrown giving the namespace (groupId) is required for maven or that a namespace is expected, but instead the purl (string value) is parsed and it's generated with encoded characters pkg:maven/%2Fa@v?type=e

Thanks for reporting. Issue is resolved in v1.3.1

authors: mr-zepol stevespringett

repo: package-url/packageurl-java


text:
convert git remote get-url into HTTPS url and use it

this way, people won't need to specify upstream_project_url
Fixes #553

Build failed.
* [packit-pre-commit ](https://softwarefactory-project.io/zuul/t/local/build/b1a9c9d846ad4f7a9fe67c459bfa9c29) : SUCCESS in 1m 52s

* [packit-tests-rpm ](https://softwarefactory-project.io/zuul/t/local/build/35f48385f64a4040b53d146107457aa9) : SUCCESS in 3m 44s

* [packit-tests-pip-deps ](https://softwarefactory-project.io/zuul/t/local/build/2876d53aec5349e99cf24a59ff68820e) : SUCCESS in 4m 13s

Tests are now passing

Tests are now passing

Nice! This is why I wanted to wait for fixing the tests before merging this.

Not sure about dockerhub tests, but LGTM codewise.

https://github.com/packit-service/packit/issues/561

authors: TomasTomecek lachmanfrantisek

repo: packit-service/packit


text:
Move setting of SRPM URL to avoid temporary one

Since COPR sets just a temporary URL for SRPM when triggering the build,
move setting of the URL to check_copr_build where it will be set after
the build is finished.
Fixes #934
Signed-off-by: Matej Focko mfocko@redhat.com

What about processing that in the build-start/build-end handler (as well)?

I'm not really sure about that, both AbstractCoprBuildEvent and CoprBuildEndHandler are using precomputed values (not having COPR build object at all); maybe if we kept COPR build object in CoprBuildJobHelper? and for objects that were not created by running a build have it as a property?

What about processing that in the build-start/build-end handler (as well)?

I'm not really sure about that, both AbstractCoprBuildEvent and CoprBuildEndHandler are using precomputed values (not having COPR build object at all); maybe if we kept COPR build object in CoprBuildJobHelper? and for objects that were not created by running a build have it as a property?

I'm not really sure about that, both AbstractCoprBuildEvent and CoprBuildEndHandler are using precomputed values (not having COPR build object at all); maybe if we kept COPR build object in CoprBuildJobHelper? and for objects that were not created by running a build have it as a property (get the build object from COPR by ID)?

Sure, do it where you think it's the best place. I haven't thought about that so much.

I'm not really sure about that, both AbstractCoprBuildEvent and CoprBuildEndHandler are using precomputed values (not having COPR build object at all); maybe if we kept COPR build object in CoprBuildJobHelper? and for objects that were not created by running a build have it as a property (get the build object from COPR by ID)?

Sure, do it where you think it's the best place. I haven't thought about that so much.

@lachmanfrantisek added check to set the URL only if unset
regarding moving it to CoprBuildEndHandler, I need to think about it; proposing to fix it as a bug for now and refactor it later

@lachmanfrantisek added check to set the URL only if unset
regarding moving it to CoprBuildEndHandler, I need to think about it; proposing to fix it as a bug for now and refactor it later

authors: lachmanfrantisek mfocko

repo: packit/packit-service


text:
Support activerecord v6.0.0

Context
I fixed errors when using ar tasks (e.g. ar:migrate, ar:rollback) with activerecord v6.0.0
Example
Gemfile
gem "padrino", "0.14.0"
gem "activerecord", "6.0.0", require: "active_record"

Backtrace
$ bundle exec rake ar:migrate:reset --trace
** Invoke ar:migrate:reset (first_time)
** Invoke ar:drop (first_time)
** Invoke skeleton (first_time)
** Execute skeleton
** Execute ar:drop
rake aborted!
NotImplementedError: `ActiveRecord::Base.configurations` in Rails 6 now returns an object instead of a hash. The `with_indifferent_access` method is not supported. Please use `configs_for` or consult the documentation for supported methods.
/app/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.0/lib/active_record/database_configurations.rb:221:in `method_missing'
/app/vendor/bundle/ruby/2.6.0/gems/padrino-gen-0.14.4/lib/padrino-gen/padrino-tasks/activerecord.rb:108:in `block (2 levels) in <top (required)>'
/app/vendor/bundle/ruby/2.6.0/gems/rake-12.3.3/lib/rake/task.rb:273:in `block in execute'
/app/vendor/bundle/ruby/2.6.0/gems/rake-12.3.3/lib/rake/task.rb:273:in `each'
/app/vendor/bundle/ruby/2.6.0/gems/rake-12.3.3/lib/rake/task.rb:273:in `execute'
/app/vendor/bundle/ruby/2.6.0/gems/rake-12.3.3/lib/rake/task.rb:214:in `block in invoke_with_call_chain'
/Users/sue445/.rbenv/versions/2.6.3/lib/ruby/2.6.0/monitor.rb:230:in `mon_synchronize'
/app/vendor/bundle/ruby/2.6.0/gems/rake-12.3.3/lib/rake/task.rb:194:in `invoke_with_call_chain'
/app/vendor/bundle/ruby/2.6.0/gems/rake-12.3.3/lib/rake/task.rb:238:in `block in invoke_prerequisites'
/app/vendor/bundle/ruby/2.6.0/gems/rake-12.3.3/lib/rake/task.rb:236:in `each'
/app/vendor/bundle/ruby/2.6.0/gems/rake-12.3.3/lib/rake/task.rb:236:in `invoke_prerequisites'
/app/vendor/bundle/ruby/2.6.0/gems/rake-12.3.3/lib/rake/task.rb:213:in `block in invoke_with_call_chain'
/Users/sue445/.rbenv/versions/2.6.3/lib/ruby/2.6.0/monitor.rb:230:in `mon_synchronize'
/app/vendor/bundle/ruby/2.6.0/gems/rake-12.3.3/lib/rake/task.rb:194:in `invoke_with_call_chain'
/app/vendor/bundle/ruby/2.6.0/gems/rake-12.3.3/lib/rake/task.rb:183:in `invoke'
/app/vendor/bundle/ruby/2.6.0/gems/rake-12.3.3/lib/rake/application.rb:160:in `invoke_task'
/app/vendor/bundle/ruby/2.6.0/gems/rake-12.3.3/lib/rake/application.rb:116:in `block (2 levels) in top_level'
/app/vendor/bundle/ruby/2.6.0/gems/rake-12.3.3/lib/rake/application.rb:116:in `each'
/app/vendor/bundle/ruby/2.6.0/gems/rake-12.3.3/lib/rake/application.rb:116:in `block in top_level'
/app/vendor/bundle/ruby/2.6.0/gems/rake-12.3.3/lib/rake/application.rb:125:in `run_with_threads'
/app/vendor/bundle/ruby/2.6.0/gems/rake-12.3.3/lib/rake/application.rb:110:in `top_level'
/app/vendor/bundle/ruby/2.6.0/gems/rake-12.3.3/lib/rake/application.rb:83:in `block in run'
/app/vendor/bundle/ruby/2.6.0/gems/rake-12.3.3/lib/rake/application.rb:186:in `standard_exception_handling'
/app/vendor/bundle/ruby/2.6.0/gems/rake-12.3.3/lib/rake/application.rb:80:in `run'
/app/vendor/bundle/ruby/2.6.0/gems/rake-12.3.3/exe/rake:27:in `<top (required)>'
/app/vendor/bundle/ruby/2.6.0/bin/rake:23:in `load'
/app/vendor/bundle/ruby/2.6.0/bin/rake:23:in `<top (required)>'
/Users/sue445/.rbenv/versions/2.6.3/lib/ruby/2.6.0/bundler/cli/exec.rb:74:in `load'
/Users/sue445/.rbenv/versions/2.6.3/lib/ruby/2.6.0/bundler/cli/exec.rb:74:in `kernel_load'
/Users/sue445/.rbenv/versions/2.6.3/lib/ruby/2.6.0/bundler/cli/exec.rb:28:in `run'
/Users/sue445/.rbenv/versions/2.6.3/lib/ruby/2.6.0/bundler/cli.rb:463:in `exec'
/Users/sue445/.rbenv/versions/2.6.3/lib/ruby/2.6.0/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/Users/sue445/.rbenv/versions/2.6.3/lib/ruby/2.6.0/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
/Users/sue445/.rbenv/versions/2.6.3/lib/ruby/2.6.0/bundler/vendor/thor/lib/thor.rb:387:in `dispatch'
/Users/sue445/.rbenv/versions/2.6.3/lib/ruby/2.6.0/bundler/cli.rb:27:in `dispatch'
/Users/sue445/.rbenv/versions/2.6.3/lib/ruby/2.6.0/bundler/vendor/thor/lib/thor/base.rb:466:in `start'
/Users/sue445/.rbenv/versions/2.6.3/lib/ruby/2.6.0/bundler/cli.rb:18:in `start'
/Users/sue445/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/bundler-1.17.2/exe/bundle:30:in `block in <top (required)>'
/Users/sue445/.rbenv/versions/2.6.3/lib/ruby/2.6.0/bundler/friendly_errors.rb:124:in `with_friendly_errors'
/Users/sue445/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/bundler-1.17.2/exe/bundle:22:in `<top (required)>'
/Users/sue445/.rbenv/versions/2.6.3/bin/bundle:23:in `load'
/Users/sue445/.rbenv/versions/2.6.3/bin/bundle:23:in `<main>'
Tasks: TOP => ar:migrate:reset => ar:drop

@namusyaka @ujifgc can this be merged?

@namusyaka @ujifgc it could be merged?

ping

ping

Using in production. Works without any issue.

authors: basex daanielcarvalho schweigert sue445

repo: padrino/padrino-framework


text:
New cache module allowing to add cache providers and including the ones for memcached and redis

A new cache architecture (designed according to  https://github.com/pagekit/framework/pull/15)
No UI changes yet. And sorry for duplicate pull requests - I am Github newbie :(

We released the Pagekit Beta today. I close this pull request because the code base completely changed. Please create a new one

authors: karevn saschadube

repo: pagekit/pagekit


text:
Ability to lock users down to agency/s

** Feature request **
Ability to lock down certain user/s to one or more agency IE: If null then all messages blank but if set to "TEST" then only "TEST" agency messages displayed to that user.

I'm currently working on a feature that let's you create groups of aliases. Would it help you if you can choose groups your users can see?

repo: pagermon/pagermon

license: Unlicense


text:
Add support for non-standard port numbers for mysql databases

Is your feature request related to a problem? Please describe.
When attempting to deploy to docker hosts with more than on mysql database, unique port numbers are required.
Describe the solution you'd like
Addition of a new field in the settings page to support non-standard ports.
Describe alternatives you've considered
Not required, I believe.
Additional context
N/A

Fixed in #520

authors: DanrwAU MitchDrage


text:
Allow toggling the Java Agent on/off at runtime

Describe the Enhancement
Right now, when you do a build the Java agent is enabled through JAVA_TOOL_OPTIONS at build time. This is difficult to disable without rebuilding. We should allow the Java agent to be enabled/disabled at runtime.
Possible Solution
Add a helper. The helper can be in charge of setting the JAVA_TOOL_OPTIONS options. It would look at an env variable and use that to turn on/off the agent.
Motivation
Sometimes you want to run with the Agent disabled and don't want to do a full rebuild, which is inconvenient.

Resolved by #160

repo: paketo-buildpacks/datadog