text:
Rage Attack Bonus isn't working

When applying rage, I'm not getting the appropriate damage bonus for strength based attacks.  Here is the configuration for the rage bonus.

Here is the resulting attack from a lvl 9 barbarian (I would expect to see +3, not +0)

If this is a simple attribute change or adjustment please let me know.  Thanks for all you do, this module is great!

Check you rage scale in the Barbarian class advancement.
There was an issue some time ago with DnD Beyond imports having a wrong identifier.

Got it.  Instead of @scale.barbarian.rage-damage it was supposed to be @scale.barbarian.rage
This is fixed, thank you

repo: DFreds/dfreds-convenient-effects


text:
背景与动机
如题，在带萌新补boss成就的时候经常会用到。
因为我只能记得boss的成就名，但不清楚其属于哪个专辑，所以搜索了boss的名称后（如无相火）弹出的结果不知道哪个属于天地万象（隐藏类成就），哪个属于挑战者的可见成就，还需要挨个专辑查找并排除……

想要实现或优化的功能
希望实现搜索成就反向查找其所在的专辑

仍未彻底实现
（下面视频用了x265编码压缩体积，github好像没法预览）
https://github.com/user-attachments/assets/72a09f20-64f9-4115-8515-64cd6155caca

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
背景与动机
目前的养成计划只提供了：

材料清单：计算角色从目前练度，养成到预计练度所需要的材料。
背包物品：提供背包物品的统计。

（似乎背包物品和材料清单没有任何功能上的关联？例如：我的背包里有某个养成计划中所需的材料，不会改变材料清单上的数字。不确定是不是我使用方法有问题）

如图所示，我已在背包里设置了这些材料，但没有反映在材料清单功能中。
作为一个用户，我希望养成计划功能能够提供一些具体的方案（如下所示）来养成角色。因为这样可降低用户的思考量或计算量，使养成过程更加便捷。
想要实现或优化的功能
“具体的方案”如下：

在材料清单中，显示“所需材料 (已有材料/总所需材料)”，如"10 (19/29)“。这样可使用户更直观地看到还需刷取多少材料。
在材料清单中，添加面向材料获取方式的面板，而不是面向材料本身的面板。例如，我仍需要 93 个 「巧思」的哲学，那么在该面板中，应显示仍需刷取 精通秘境：妙语 Ⅳ 46 次 (920 树脂)。（数字是随手填的）
在材料清单，面向材料获取方式的面板中，标识它们的开放时间。例如：假设今天是周一，那么应显示 （周二/周五/周日）精通秘境：妙语 Ⅳ 46 次 (920 树脂)，并用灰色字体或是 disabled 效果来标识今天无法获得此种材料。

有用的链接：BOSS及秘境掉落数据统计
如果作者比较忙的话，我可以抽空写一个养成计划的原型

@FlandiaYingman
需要不引入多余的第三方库：Google.OrTools

@Lightczx
从头实现线性规划稍显困难，我会试一下

@Lightczx
目前已经实现了无需第三方库的版本。然而，这么做会使运算时间上升到~20s左右。
目前，我的程序中包含了所有的合成配方（包括尘歌壶、食物等），经过测试，我认为是这些多余的配方拖慢了运算速度。
所以，你能提供一份胡桃启动器中，养成计划=>背包物品中所有养成材料的名称的列表吗？我会用它将多余的配方剔除。

换句话说，我需要这个界面中材料的名称。

自己实现的线性规划更慢？算法有问题吧？不然时间应该差不多

@Lightczx
嗯，线性代数相关的算法需要矩阵运算的基础库支持才能写的更有效些。只用数组的话，实现简单的单纯形算法已经是我能力的极限了。
不过，慢十几秒有点夸张了，我猜想是许多无效约束造成的。我会同时试着在应用层面和算法层面剔除掉这些无用约束。

https://learn.microsoft.com/en-us/dotnet/api/system.numerics

@Lightczx
你发的那些仅支持特定大小的matrix（3x2）（4x4)，没办法做大型线性方程组的运算。

那就自己实现吧

那就自己实现吧

能力有限，无法实现

能把具体的运算过程讲解一下么

@Lightczx
刚想讲解运算过程，在写的过程中发现了算法设计的问题。
你指出的“算法有问题”是对的😭。我为无上界的约束指定的上界是 double.PositiveInfinity，然而，直接在约束矩阵里去除上界更有效率些。
目前的运算速度：~ 1000 ms，相比于用第三方 native 库的 ~ 400 ms，我觉得时间上已经可以接受了。
纯 C# 实现已经推到 https://github.com/FlandiaYingman/Genshin.Planner.Demo 上了

目前没有办法获取秘境入口与秘境的对应关系
合成材料的元数据可以获取

@Lightczx
我 project 里的 QuickType.DomainJson 里有一个 domainentrance，对应着各秘境的秘境入口。
数据来源于这个 API：https://genshindb-ia.netlify.app/
query=names&matchCategories=true&verboseCategories=true&resultLanguage=ChineseSimplified

元数据必须从ExcelBin 中解析，不接受外界的数据，我们必须对数据源具有控制权

@Lightczx
抱歉，ExcelBin 是什么？
如果无法获取秘境入口与秘境的对应关系，那么我认为跳过秘境入口名，直接显示秘境名也可以。因为我想大部分玩家都没有看到秘境入口名就能反应该刷哪个秘境的能力，大家都是点开某个材料然后跳转到秘境去的。

看了眼他的解析方式
https://github.com/theBowja/GenshinData-scripts/blob/main/extract/extractDomain.js
我觉得还是不能做秘境对应

看了眼他的解析方式 https://github.com/theBowja/GenshinData-scripts/blob/main/extract/extractDomain.js 我觉得还是不能做秘境对应

只是没办法做秘境和秘境入口吗？有没有什么曲线救国的方式？
如果找不到方法的话就 close 吧

秘境的材料是可以做的，秘境入口不行

稍微描述一下算法吧

@Lightczx
求解线性规划用的是单纯形法，不赘述了。
关于怎么构造的线性规划
由于有合成功能的存在，简单地将需求材料数乘以秘境掉落期望数的算法是不完善的。因而，我们需要找到一个最优解，使得消耗总树脂最低，即最大程度地利用背包里的材料。
设 x1, x2, ..., xn 为线性规划的变量，我们用各变量代表一个独立的行为（刷秘境或合成）。所以，线性规划求解完毕后，各个变量的最优值即是我们想要的结果（某个秘境刷 n 次，某种材料合成 m 个，etc.）。特别地，有一个 stock 变量恒定为 1，它的作用是代表背包里的材料。
注意，由于个别材料（例如，突破宝石）有不止一个合成方式，我为每个合成方式都赋了一个独特的 ID（就是合成产物名字后面跟一个计数器而已）。不过我的算法还没实现 BOSS 和掉落产物的对应，所以赋 ID 这一步可以省略。
然后，设 c1, c2, ..., cm 为线性规划的约束，我们用各约束代表各材料。每个材料的表达式是对每个会产出该材料的行为乘以该行为产出材料的期望值求和。注意有些合成行为是消耗材料的，所以该行为产出负数个此材料。最后再加上背包的材料，它用 stock 变量（即 1）乘以背包材料的数量来表示。（实际上 stock 变量放到约束里就是一个常数项而已）
如果我们不需要这个材料，那么在这个约束中，我们使这个表达式大于等于 0，这样就不会有负数材料的出现；如果我们需要这个材料，那么在这个约束中，我们使这个表达式大于等于需要材料数。
最后，使最优化函数=各行为需要消耗的树脂的数量的和，我们要使最优化函数最小。然后求解，结果就出来了
例子
约束 c1 代表“高塔孤王的断片”
这个材料有三种获取方式：

变量 x1：炼武秘境：水光之城 Ⅲ
变量 x2：炼武秘境：水光之城 Ⅳ
变量 x3：合成“高塔孤王的断片”

以及一种消耗方式：

变量 x4：合成“高塔孤王的碎梦”

那么，构造一个表达式，使它表达我们“高塔孤王的断片”的数量：
“高塔孤王的断片” = 0.22*x1 + 0.64*x2 + 1*x3 - 3*x4 + 背包里已有“高塔孤王的断片”的数量

其中 0.22，0.64 是刷一次对应秘境掉落“高塔孤王的断片”的期望值，1*x3 的意思是合成一次“高塔孤王的断片”可以获得 1 个“高塔孤王的断片”，- 3*x4 的意思是合成一次“高塔孤王的碎梦”会消耗 3 个“高塔孤王的断片”。
由于线性规划中不允许常数项的出现，我们使 stock 变量恒为 1，然后把背包里已有“高塔孤王的断片”的数量变为背包里已有“高塔孤王的断片”的数量*stock。
所以，最后的约束
c1: 0.22*x1 + 0.64*x2 + 1*x3 - 3*x4 + 背包里已有“高塔孤王的断片”的数量*stock >= 需要的“高塔孤王的断片”的数量

一些 Trick

设高等级的秘境比低等级的秘境消耗的树脂要稍微少一些（0.01），这样规划程序不会在刷任意一个秘境都满足条件的情况下刷低等级的秘境。
设合成也会消耗少量树脂（0.01）这样规划程序不会瞎合成不需要的材料。

这些树脂仅在最优化函数中表达，等我们最后计算需要多少树脂的时候，对 x1, x2, ..., xn 乘以对应行为需消耗的真实树脂求和，重新计算一遍就可以了。

低等级的秘境应该无论如何材料掉的都比高等级的少吧

@Lightczx
对，我添加这个只是为某些可能尚未解锁高等级秘境的新手考虑。如果不考虑他们，低等级秘境可以删掉。

有个问题需要注意

BOSS与天赋/武器本的掉率是非官方的数据
不精确的数据是难以接受的

有个问题需要注意

BOSS与天赋/武器本的掉率是非官方的数据

不精确的数据是难以接受的

个人认为如：

圣遗物评分的算法
深渊统计

等系统的数据，跟此掉落数据一样是玩家上传的、非官方的、不精确的数据。因此只要标识清楚哪些数据是精确值，哪些数据是统计值，我认为是可以接受的。

主要是部分数据的样本量实在太小了

主要是部分数据的样本量实在太小了

样本较小的情况都出现在低冒险等级的时候。我觉得把这些低冒险等级的情况剔除掉就行了

@xTaiwanPingLord
我在一开始提出该方法时确实没有经过太多的实践，
经过这些天的实践，我赞同你对该方法过于复杂的看法，因为求出最优解的收益不大，不值得为此设计一个复杂的方法。

误差是不可避免的 但是我们还是缺少很多domian的Datas 我觉得 @FlandiaYingman  提供的算法example进过改良之后还是可以达到预期内的时间 我还需要一点时间来熟悉示例代码 我也需要寻找更多的能够维持正常更新的domain datas

误差是不可避免的 但是我们还是需要一些domian的Datas 我觉得 @FlandiaYingman 提供的算法example进过改良之后还是可以达到预期内的时间 我还需要一点时间来熟悉示例代码 我也需要寻找更多的能够维持正常更新的domain datas

@GashByte
https://github.com/DGP-Studio/Snap.Data.Mapper
https://github.com/UIGF-org/GenshinData
https://github.com/DGP-Studio/Snap.Metadata

@Lightczx
https://github.com/UIGF-org/GenshinData 已经 404 了

@Lightczx https://github.com/UIGF-org/GenshinData 已经 404 了

Internal Only

以当前胡桃的用户量，可以考虑通过胡桃收集副本挑战掉落材料，样本量充足且数据源可控。
具体实现，可以在胡桃中内置截图识别+上传，结合已有用户体系，可收集到的数据有：

挑战的副本及等级
掉落物及数量
挑战副本的时间（可进行时间相关性统计）
数据来源（方便洗去恶意数据）

同时可以结合胡桃云激励时长，鼓励用户上传副本数据。收集到充足样本后，使用简单的期望估计即可解决问题。期望值可以根据背包中物品数量进行迭代而不断修正
当然也可以选择更精确的统计模型进行计算，只要样本充足，都可以实现（实际上，基于大量样本的简单期望估计一定比线性规划更准确，理由是在精确概率不可知的情况下，参数越少受误差影响越小）
此外，可以视样本的收集率，选择一定长度的滑动时间窗口进行概率估计。此举可保证即使官方暗改了概率，应用也可以自适应概率的变化。更进一步，还可以对时间进行水平划分，通过大量样本计算是否存在所谓的“玄学时间”

以当前胡桃的用户量，可以考虑通过胡桃收集副本挑战掉落材料，样本量充足且数据源可控。 具体实现，可以在胡桃中内置截图识别+上传，结合已有用户体系，可收集到的数据有：

挑战的副本及等级
掉落物及数量
挑战副本的时间（可进行时间相关性统计）
数据来源（方便洗去恶意数据）

同时可以结合胡桃云激励时长，鼓励用户上传副本数据。收集到充足样本后，使用简单的期望估计即可解决问题。期望值可以根据背包中物品数量进行迭代而不断修正
当然也可以选择更精确的统计模型进行计算，只要样本充足，都可以实现（实际上，基于大量样本的简单期望估计一定比线性规划更准确，理由是在精确概率不可知的情况下，参数越少受误差影响越小）
此外，可以视样本的收集率，选择一定长度的滑动时间窗口进行概率估计。此举可保证即使官方暗改了概率，应用也可以自适应概率的变化。更进一步，还可以对时间进行水平划分，通过大量样本计算是否存在所谓的“玄学时间”

掉落概率其实是固定的，现在是元数据没准备好

Tracked by #1394

authors: AZhrZho FlandiaYingman GashByte Lightczx


text:
Phone connection

As a user, I want to be able to open up the application on my mobile phone.
Acceptance criteria:

[ ] the software should be tested by being opened by an android phone

Are we referring to MQTT connection here?

authors: Druner arrestoteles


text:
Add new tile Security to homepage

Adding a new section to the website

[ ] Add a new tile named Security to the homepage.

[ ] Use this icon https://fontawesome.com/v4.7/icon/shield in the same style as the other ones.

[ ] Create a new  section like reports

[ ] Add two documents

https://www.divd.nl/uploads/OPENBAAR - Informatiebeveiligingsbeleid v1.0.pdf

https://www.divd.nl/uploads/OPENBAAR - Security Visie v1.0.pdf

Draft PR gemaakt voor 't raamwerk (incl. verplaatsing van de partners-tile naar de footer). Even afstemmen welke precieze tekst erin moet

authors: cookiemonster wschoot

repo: DIVD-NL/sites


text:
[question] Possible bug during hyper parameter tuning

https://github.com/DLR-RM/rl-baselines3-zoo/blob/0c89a31fff69183577c44a244f3c0e5de48f2831/utils/exp_manager.py#L640
Optuna tries to minimize the objective function, so if you want to maximize reward, then shouldn't this be negative? i.e
return -reward ?

I see that the study is created with direction="maximize", my bad. It's all good. Closing the issue.


text:
Investigate actions that make the browser flicker

When I Share Note and click Save, the browser flickers a few times (just something to note, not a fatal flaw)
When I advance to answering questions in a new section w/o saving and click through the modal that prompts me to Save previous answers, I observe the same browser flickering

@stephaniesimms is this still an issue with now that we have redesigned the page?

nope. not that i've noticed in the past few weeks of testing at least. if you don't see flickering either it's probably safe to close @briri

Haven't noticed any flickering either. Closing out

authors: briri sjDCC stephaniesimms

repo: DMPRoadmap/roadmap

license: mit

license_source: bigquery


text:
Simpler type casting and reserved loop, and other cosmetic changes.

Do you intend to not exit on err from getNsRecords()?
I switched out the fmt.Println with log.Fatalln there.

Aah very nice like this indeed, thank you!

source: gharchive/pull-request

authors: Gurpartap mattiasgeniar

repo: DNSSpy/zone-nameservers


text:
Reveal.js Slides

This pull request should have all the Reveal.js presentations from the summer, but some may need to be worked on/ rerecorded.

We are cancelling this one. We've moved all relevant things into "main"

Sounds good! Should I delete the malina-experimenting branch?
On Mon, Oct 7, 2024 at 4:06 PM Erik Spjut @.***> wrote:

We are cancelling this one. We've moved all relevant things into "main"
—
Reply to this email directly, view it on GitHub
https://github.com/DOFProGuru/CTP/pull/18#issuecomment-2398092101, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BCI5IQHT3J6FS3PCOFNEJZ3Z2MHVRAVCNFSM6AAAAABOW7YTMSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJYGA4TEMJQGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

I think I already did. Hopefully, everything is in your new branch.
Prof. R. Erik Spjut (spyoot rhymes with cute)(he/him/his)
Union Oil Company Design Fellowship Professor
Engineering Department, Harvey Mudd College, Claremont, CA 91711
Cell 909-367-9085 Office 909-607-3890 Fax 909-621-8967 Message 909-621-8019

On Oct 7, 2024, at 4:07 PM, Malina Andrews @.***> wrote:
Sounds good! Should I delete the malina-experimenting branch?
On Mon, Oct 7, 2024 at 4:06 PM Erik Spjut @.***> wrote:

We are cancelling this one. We've moved all relevant things into "main"
—
Reply to this email directly, view it on GitHub
https://github.com/DOFProGuru/CTP/pull/18#issuecomment-2398092101, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BCI5IQHT3J6FS3PCOFNEJZ3Z2MHVRAVCNFSM6AAAAABOW7YTMSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJYGA4TEMJQGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.Message ID: @.***>

authors: ErikSpjut malina-andrews

repo: DOFProGuru/CTP


text:
Bump to Confluent version 5.0.0

The Java adapter is currently on version 4.0.0
We should bump the version to 5.0.0 to have the latest bug fixes/enhancements, BUT this drops support for Java 7.
We can do this on a separate branch and merge after Trial 2.

Confluent is now at 5.0.1
Kafka is at 2.1.0

repo: DRIVER-EU/java-test-bed-adapter


text:
experimental: introduce img understand pipeline

This new feature creates a new ImgUnderstand pipeline which uses vision LLMs to describe the pictures contained in documents.
The pipeline allows to use

Local LLM, via vLLM
LLM as a service, e.g. on watsonx.ai or openai compatible apis

Checklist:

[x] Commit Message Formatting: Commit titles and messages follow guidelines in the
conventional commits.
[ ] Documentation has been updated, if necessary.
[ ] Examples have been added, if necessary.
[ ] Tests have been added, if necessary.

Offline LLM
vLLM
Pros:

efficiently run vision models offline, see the docs page.
supports different models without further specialization
already used by InstructLab and part of RHEL AI

Cons:

no support for mac (any architecture)
vLLM has an exact pinning of torch, which creates issues with poetry.

vllm==0.5.x depends on torch==2.3.0
vllm==0.6.x depends on torch==2.4.0.

HF transforms
Pros:

no strong pinning of torch

Cons:

more code needed
different models require different implementations, e.g. llava-next is different than phi-3-v.

@dolfim-ibm could we not use some standard HF models (eg florence and onechart)?

superseded by #259

authors: PeterStaar-IBM dolfim-ibm


text:
Dependency review

The SFR dependency rationale table looks like it may have gotten messed up during edits.
At a minimum FCS_CKM.2, FCS_CKM_EXT.3 are missing completely.

FCS_CKM.2 dependency for FTP_PRO.1 should be adjusted to FTP_ITP_EXT.1, FTP_ITE_EXT.1 or FTP_ITC_EXT.1.

Fixed messed up table, was a duplicate line that threw everything off.

repo: DSC-iTC/cPP


text:
🛑 Apps is down

In 9f9551d, Apps (https://apps.unhas.ac.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Apps is back up in f51b92c after 14 minutes.


text:
🛑 Dikmawa is down

In 2cbf3dc, Dikmawa (https://dikmawa.unhas.ac.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Dikmawa is back up in 198c923.


text:
🛑 SSO Unhas is down

In 17123ba, SSO Unhas (https://sso.unhas.ac.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SSO Unhas is back up in 049502a after 17 minutes.


text:
🛑 Fakultas Hukum is down

In 4087f61, Fakultas Hukum (https://lawfaculty.unhas.ac.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Fakultas Hukum is back up in 86c4c6f after 4 minutes.


text:
🛑 Unhas Main is down

In 476f740, Unhas Main (https://unhas.ac.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Unhas Main is back up in 15bb675.


text:
🛑 Fakultas Ilmu Budaya is down

In 41e8174, Fakultas Ilmu Budaya (https://ilmubudaya.unhas.ac.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Fakultas Ilmu Budaya is back up in 1e39e2d after 42 minutes.


text:
🛑 Apps is down

In 579e4ea, Apps (https://apps.unhas.ac.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Apps is back up in 559ac7c.


text:
🛑 Fakultas Hukum is down

In 9d5a229, Fakultas Hukum (https://lawfaculty.unhas.ac.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Fakultas Hukum is back up in 9d40047 after 4 minutes.


text:
🛑 Fakultas IKP is down

In d239eee, Fakultas IKP (https://fikp.unhas.ac.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Fakultas IKP is back up in b5be3fb after 13 hours, 36 minutes.


text:
🛑 Unhas Main is down

In c24f9a8, Unhas Main (https://unhas.ac.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Unhas Main is back up in e02e8e3 after 6 minutes.


text:
🛑 Neosia is down

In dd650d9, Neosia (https://neosia.unhas.ac.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Neosia is back up in 844f37f after 13 minutes.


text:
Calibration of the average daily photosynthetic conversion efficiency RUE for CERES-Rice

We found that CERES-Rice model fails to react to solar radiation SRAD. Thus we are looking into the necessity
to calibrate the average daily photosynthetic conversion efficiency RUE (g/MJ), which is hardcoded in the daily biomass calculation module ( RI_Grosub.for; code snippet ⬇ ).
      PAR     = 0.5*SRAD     !PAR local variable

      PLSC    = AMIN1((0.5+0.001*PLANTS),1.0)
      TL      = EXP(-0.85*ROWSPC*PLSC)               ! .65
      Y1      = EXP(-0.625*LAI)                      ! .625
      Y2      = EXP(-TL*LAI)
      EPLANTS = PLANTS**0.975
      RUEA    = 5.85   !6.85      UPS UH 03/21/03
      RUEX    = 0.65

      PCARB   = RUEA*PAR**RUEX/EPLANTS*(1.0-AMIN1(Y1,Y2))

We are looking into the modification of RI_Grosub.for to read an external file of RUE data, and ultimately add RUEA and RUEX in the subroutine arguments, and reading the external file in an upper level subroutine.

I recommend that you explore the subroutine RI_IPCROP.for which is reading the parameters from the SPE file RICER048.SPE.

Per @GerritHoogenboom : We need to create an Ecotype file for CERES-Rice. It is the only model that does not have an Ecotype file.

Per @GerritHoogenboom : We need to create an Ecotype file for CERES-Rice. It is the only model that does not have an Ecotype file.

Thank you for your comment, @chporter . Is anyone working on this already? Also, is there a specific reason why CERES-Rice doesn't have an Ecotype file?

authors: NadaBenMhenni chporter lpmorenoc

repo: DSSAT/dssat-csm-os


text:
DS-3734 Fixed missing trigger of item last modified date when adding a bitstream

https://jira.duraspace.org/browse/DS-3734
When a bitstream is added to an item after it was archived the last modified date of the owning item is not triggered.
To reproduce the error:
Go to http://demo.dspace.org/xmlui/
Log in as administrator
Click on any item and hit "Edit this Item"
Click on "Item Bitestreams"
Click on "Upload a new Bitstream"
Upload the file
Click on Item Status
Expected behavior: Last Modified equals current date and time.
Observed behavior: Last Modified didn't change

Does this also update the last modified date when f.e. a thumbnail is created?

@AlexanderS I am not sure about this as we don't use thumbnails in our DSpace instance. But a far as I understand this, a thumbnail is a bitstream in the bundle THUMBNAIL. In this case adding a thumbnail to an item will change the date which is consistent with removing it. Because at org.dspace.content.BundleServiceImpl.removeBitstream(Context, Bundle, Bitstream) we already  trigger the update of the item last modified date.

authors: AlexanderS christian-scheible

repo: DSpace/DSpace


text:
DS-4551 Close FileInputStreams

References

Fixes DS-4551

Description
Closes FileInputStreams immediately after they are no longer in use, to avoid an excessive number of open files when processing a large upload. In the original code, only the last FileInputStream was closed, because is.close() was called outside of the loop that opens the streams instead of within the loop. I just moved the is.close() to the appropriate place.
To verify the problem and the result from outside you can profile open files for the process. Description of how to do so can be found in DS-4551.

merged as being tiny and obvious.


text:
Show notifications when failing to create/delete role Groups

References
Add references/links to any related issues or PRs. These may include:

Fixes #1557
Backend PR: https://github.com/DSpace/DSpace/pull/8286

Description
Show error notifications when Community/Collection role Group creation/deletion fails.
Instructions for Reviewers

Run a local DSpace instance at the backend PR's branch
Select (or create) a Collection with the admin account assigned to the first workflow role
Deposit a new submission, confirm that it appears in the admin account's pool on /mydspace
Edit the Collection: attempt to delete the first role' Group

A notification should pop up informing you that this can't be done

Checklist
This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome). If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

[x] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
[x] My PR passes TSLint validation using yarn run lint
[x] My PR doesn't introduce circular dependencies
[x] My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
[x] My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
[x] If my PR includes new, third-party dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.

@tdonohue

Groups with pending claimed tasks can still be deleted as of the backend PR. I only brought up that problem there and opened another issue for it, I think we still have to discuss how to approach it exactly.
https://github.com/DSpace/DSpace/issues/8272
The "422 OK" notification does look weird, I'll look into what's going wrong there

I can't seem to replicate this with the two PR branches, this is the notification I get

The one you got does look a lot like how it looks when running against current main

That message is just the default Angular message that comes up when the error response doesn't come with it's own message (no idea why yours would have "422 OK" though...)

@ybnd : Thanks for retesting. In that case, maybe I made a mistake in my tests & somehow was running this against main instead of against https://github.com/DSpace/DSpace/pull/8286.   I'll retest this -- sounds like the mistake may have been on my end.
I'll also ignore the issue described in https://github.com/DSpace/DSpace/issues/8272 since that will be fixed separately.

Thanks for the extra info!
The 422 response I get back does include that message we need while yours didn't, so this appears to be a backend issue.

authors: tdonohue ybnd

repo: DSpace/dspace-angular


text:
Use npm instead of Yarn

References

Fixes https://github.com/DSpace/dspace-angular/issues/1074

Description
Simplify the project by using npm (which ships with Node.js) instead of Yarn (an extra global dependency and prerequisite).
The original reasons for using Yarn (dependency install speed and robust lockfiles) are no longer as compelling. In the past few years npm has improved in both of these areas. Furthermore, we are using Yarn 1.x "classic", which has been deprecated for several years and migration to Yarn 2, which is not backwards compatible, will require us to do some work anyway.
Instructions for Reviewers
Please add a more detailed description of the changes made by your PR. At a minimum, providing a bulleted list of changes in your PR is helpful to reviewers.
List of changes in this PR:

Remove yarn.lock
Update package.json to use npm run for all scripts
Add package-lock.json

TODO:

Update README.md with new instructions for npm
Update CI and GitHub templates

Include guidance for how to test or review your PR.
Try installing dependencies and building the application in dev and production mode:
$ rm -rf node_modules && npm install --legacy-peer-deps
$ npm run build
$ npm start

Checklist
This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome).
However, reviewers may request that you complete any actions in this list if you have not done so. If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

[x] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
[x] My PR passes ESLint validation using yarn lint
[x] My PR doesn't introduce circular dependencies (verified via yarn check-circ-deps)
[x] My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
[x] My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
[x] My PR aligns with Accessibility guidelines if it makes changes to the user interface.
[x] My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
[x] My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
[x] If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
[x] If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
[x] If my PR fixes an issue ticket, I've linked them together.

Thanks for this work @alanorth !  I can see we'll need to do more work here to update other areas where yarn is used (namely the GitHub Actions, Docker scripts & README).  But, this looks like a good start!
I've linked this over to the 9.0 brainstorms we've started gathering for Steering to discuss.  I see this as a task which can help with the "Easier Installation" idea (by removing a prerequisite in yarn).
@artlowel and @atarix83 : I added you both as reviewers here as I'd appreciate your feedback on this idea.  I'd be willing to help @alanorth to get the GitHub Actions / Docker scripts updated, assuming we all agree with the goal of removing usage of yarn in favor of npm.  So, please let me know if you have immediate objections/concerns.

Thanks @artlowel!

This PR does seem to break our lint step (On github you see the yarn version, but I get the same issue running lint with npm). Since it won't compile, perhaps eslint resolves to a different version now?

Oh I'm not sure, that needs more investigation. Appreciate any advice.

You can get rid of the resolutions section in package.json, it's something unique to yarn, to force to use a certain version of a dependency when their are conflicts. Since the project builds fine, it looks like these particular resolutions are no longer necessary anyway.

Done, thanks.

I do think we should add the npm equivalent, which is called overrides, and solve any conflict we have with peerDependencies in there, rather than instructing people to run npm install with --legacy-peer-deps

Oh that is nice to know. I have worked through the conflicting dependencies and added overrides for each. Now we can install with npm install!

@alanorth I fixed the lint errors with an update to the unused-imports plugin (this was causing the problem, not the spec test itself) - "eslint-plugin-unused-imports": "^4.1.3", does it, though note that the documentation says 4.x.x is for eslint 9, eslint 8-5 (we are behind this right?), so I think to be sure we should review all the eslint versions and see what we can update?

Thanks @kshepherd! You're right, the eslint-plugin-unused-imports say this:

Version 4.1.x is for eslint 9 with @typescript-eslint/eslint-plugin v8 to v5
Version 3.x.x is for eslint 8 with @typescript-eslint/eslint-plugin 6 - 7
Version 2.x.x is for eslint 8 with @typescript-eslint/eslint-plugin 5

We are using 2.x.x currently, but according to this we should be using 3.x.x. It fixes the lint error, though I'm not sure why we don't hit that issue with yarn. :thinking:

Thanks for testing @artlowel and @kshepherd. This is at +2 now. As far as I can see the only thing remaining is to update the DSpace wiki, though the section for DSpace 9 doesn't exist yet.

authors: alanorth kshepherd tdonohue


text:
Ping search feature

I implemented the feature to ping search engine. In the current Implementation the search is notified when any new metadata is added to the FDP and when the repository metadata is updated. My current implementation has a service interface to interact with search and I implemented this interface based on unirest.

Coverage increased (+0.02%) to 75.646% when pulling 8717ab6205d3b26fafca02df12db12c72999dee3 on rajaram5:develop into 32d75194834285cf6ed653713b6d003d80e5047a on DTL-FAIRData:develop.

Coverage increased (+0.02%) to 75.646% when pulling b8138985a305c1d32f1f5be382ee122e883ed8ca on rajaram5:develop into 32d75194834285cf6ed653713b6d003d80e5047a on DTL-FAIRData:develop.

Coverage increased (+0.02%) to 75.646% when pulling 8fbf5c3edbfcd5f1d5d8699965426b2fabd15e10 on rajaram5:develop into 32d75194834285cf6ed653713b6d003d80e5047a on DTL-FAIRData:develop.

repo: DTL-FAIRData/FAIRDataPoint


text:
[Doc] BlockHeader size

done

repo: DTStack/dt-react-component


text:
AudioWebsocketError NPE

General Troubleshooting
Hey there! Before you report a bug or suggest a new feature,
please make sure to follow these steps first!

[X] I have checked for similar issues.
[X] I have updated to the latest JDA version.
[X] I have checked the branches or the maintainers' PRs for upcoming features/bug fixes.

This is not the place to learn Java. Please refer to StackOverflow
for your general programming questions.

Issue
Issue Type

[X] Bug Report
[ ] Feature Request

For questions join the official JDA discord server: https://discord.gg/0hMr4ce0tIl3SLv5

Description
For whatever reason, JDA is throwing a NPE when I attempt to connect to a voice channel. I've checked, and neither the Receiver nor the Sender are null. The weird thing is, line 1172 of that file (WebSocketClient.java) seems to just be related to logging - why would it be throwing a NPE?
2018-09-15 17:11 -04:00: [Debug] Receiver==NOT NULL and SENDER==NOT NULL
2018-09-15 17:11 -04:00:
2018-09-15 17:11 -04:00: [JDA AudioWS-WriteThread (guildId: REMOVED)] ERROR AudioWebSocket - There was some audio websocket error
java.lang.NullPointerException
   at net.dv8tion.jda.core.requests.WebSocketClient.lambda$queueAudioReconnect$6(WebSocketClient.java:1172)
   at net.dv8tion.jda.core.requests.WebSocketClient.locked(WebSocketClient.java:1138)
   at net.dv8tion.jda.core.requests.WebSocketClient.queueAudioReconnect(WebSocketClient.java:1170)
   at net.dv8tion.jda.core.audio.AudioWebSocket.lambda$close$0(AudioWebSocket.java:184)
   at net.dv8tion.jda.core.audio.AudioWebSocket.lambda$locked$1(AudioWebSocket.java:523)
   at net.dv8tion.jda.core.utils.MiscUtil.locked(MiscUtil.java:240)
   at net.dv8tion.jda.core.audio.AudioWebSocket.locked(AudioWebSocket.java:523)
   at net.dv8tion.jda.core.audio.AudioWebSocket.close(AudioWebSocket.java:138)
   at net.dv8tion.jda.core.audio.AudioWebSocket.onDisconnected(AudioWebSocket.java:287)
   at com.neovisionaries.ws.client.ListenerManager.callOnDisconnected(ListenerManager.java:223)
   at com.neovisionaries.ws.client.WebSocket.finish(WebSocket.java:3638)
   at com.neovisionaries.ws.client.WebSocket.onThreadsFinished(WebSocket.java:3608)
   at com.neovisionaries.ws.client.WebSocket.onWritingThreadFinished(WebSocket.java:3597)
   at com.neovisionaries.ws.client.WritingThread.notifyFinished(WritingThread.java:539)
   at com.neovisionaries.ws.client.WritingThread.runMain(WritingThread.java:78)
   at com.neovisionaries.ws.client.WebSocketThread.run(WebSocketThread.java:45)

The specific line of code is
        getGuild().getAudioManager().setReceivingHandler(getRecorder());
        getGuild().getAudioManager().setSendingHandler(customAudioPlayer);
log("Debug", "Receiver==" + (getRecorder() == null ? "NULL" : "NOT NULL") + " and SENDER==" + (customAudioPlayer == null ? "NULL" : "NOT NULL"));
        getGuild().getAudioManager().openAudioConnection(vc);

The bot DOES connect to the voice channel, but the receiver and sender never are able to properly function.

@kantenkugel As per my pom.xml file, 3.7.1_422.
        <dependency>             <groupId>net.dv8tion</groupId>             <artifactId>JDA</artifactId>             <version>3.7.1_422</version>         </dependency>

Is the voicechannel null? cuz either that or something very weird is happening... The code erroring

VoiceChannel 100% isn't null given that the bot correctly connects to the voice channel.

I want to point out that the error happens on a disconnect unrelated to this code segment of yours.

So, is it an "expected" error...? Or did I miss it in one of the existing issues (if so, I'm sorry!)
Just to make sure, I tested it, and definitely not null on my end.
2018-09-15 17:43 -04:00: [Debug] Receiver==NOT NULL and SENDER==NOT NULL [Debug] VoiceChannel==NOT NULL and GUILD==NOT NULL

Does this issue appear consistently across all channels/guilds?

While this seems to be a bug, it might be caused by the audio server rejecting the bot from connecting, As this happens when the Audio connection is closed by the server and JDA tries to reconnect.
Have you tried using other channels/guilds like Minn suggested? Maybe just switching the voice region might already fix it

Tested in both the guild the bot will run in, as well as a test guild. Tried changing region of both, from US-West to US-East to US-South - no effect on the issue.
When the bot starts up it gets this message:
2018-09-15 17:43 -04:00: [SessionControllerAdapter-Worker] ERROR WebSocketClient - Encountered IDENTIFY (OP 2) Rate Limit! Waiting 5 seconds before trying again!
Could that have something to do with it?

Could enable debug logs and show what they say?

Any update on this?

@MinnDevelopment Ended up fixing this. At one point in the process the JDA object was updated to be the wrong instance, and hence not match the JDA object from the VoiceChannel.
However, now, for some reason CombinedAudio is...empty?
Up until about 2 days ago, it's been routinely working fine. Records all user audio. Then, despite no changes from myself, it is only receiving empty audio.
I added logs to the handleCombinedAudio method, and it is firing, so it's receiving data, but it's nothing useful.
When I added a ConnectionListener, the onUserSpeaking method does correctly detect when people start and stop speaking. Just the AudioReceiveHandler seemingly isn't getting the data.
getGuild().getAudioManager().setConnectionListener(new ConnectionListener() {
            @Override
            public void onPing(long l) {

            }

            @Override
            public void onStatusChange(ConnectionStatus connectionStatus) {
                log("ConnectionStatus", connectionStatus.name());
            }

            @Override
            public void onUserSpeaking(User user, boolean b) {
                if (b) {
                    log("Spoke", user.getName() + "!");
                }
            }
        });
getGuild().getAudioManager().setReceivingHandler(getRecorder());
getGuild().getAudioManager().openAudioConnection(vc);

As stated above, the ConnectionStatus and Spoke logs are logged accurately.
VC is not null. getRecorder is not null, as the recorder variable is defined when the class is instantiated.
public Recorder(JDA jda, int id) {
        this.jda = jda;
        this.id = id;
        recorder = new AudioRecorder(jda, id);
        log("Recorder", "Finished setting up recorder #" + this.id);
    }

    public AudioRecorder getRecorder() {
        return recorder;
    }

The AudioReceiveHandler handles the audio as follows:
    @Override
    public void handleCombinedAudio(CombinedAudio combinedAudio) {
        log("CombinedAudio", "Received data!");
        try {
            if (getLinkedRecorder() != null) {
                Recorder rec = getLinkedRecorder();
                if (combinedAudio.getUsers().size() > 0) {
                    if (rec.getTranscriptFos() != null) {
                        try {
                            FileOutputStream fos = rec.getTranscriptFos();
                            StringBuilder names = new StringBuilder();
                            for (User user : combinedAudio.getUsers()) {
                                try {
                                    if (matches.containsKey(user.getId())) {
                                        if (!matches.get(user.getId()).equals(user.getName())) {
                                            matches.replace(user.getId(), (matches.get(user.getId()) + "," + user.getName()));
                                        }
                                    } else {
                                        matches.put(user.getId(), user.getName());
                                    }
                                } catch (Exception e) {
                                    e.printStackTrace();
                                }
                                names.append(user.getName()).append(",");
                            }
                            long diff = System.currentTimeMillis() - Long.parseLong(rec.getStartTime());
                            long minutes = TimeUnit.MILLISECONDS.toMinutes(diff);
                            diff -= TimeUnit.MINUTES.toMillis(minutes);
                            long seconds = TimeUnit.MILLISECONDS.toSeconds(diff);
                            diff -= TimeUnit.SECONDS.toMillis(seconds);
                            String time = minutes + ":" + seconds + "." + diff;
                            String toWrite = time + " > " + names.toString().substring(0, names.toString().length() - 1) + "\n";
                            fos.write(toWrite.getBytes());
                        } catch (IOException e) {
                            e.printStackTrace();
                        }
                    }
                }
                try {
                    FileOutputStream fos = rec.getOpusFos();
                    fos.write(combinedAudio.getAudioData(1.0));
                } catch (IOException e) {
                    e.printStackTrace();
                }
            } else {
                log("Debug", "No recorder linked. int=" + String.valueOf(recorder));
            }
        } catch (Exception e) {
            e.printStackTrace();
        }
    }

The "CombinedAudio" log at the start of the method is fired, rapidly, in ~20ms intervals, as would be expected.
canReceiveCombined does return true.
It 100% isn't that the ReceiveHandler isn't instantiated, as the files are being written to - it's just empty audio.
No idea why this randomly stopped working 2 days ago - I literally had made no changes to it.

@MinnDevelopment
Reposting as I deleted this previously to test something quickly to make sure it wasn't something I did to the best of my knowledge
Ended up fixing this. At one point in the process the JDA object was updated to be the wrong instance, and hence not match the JDA object from the VoiceChannel.
However, now, for some reason CombinedAudio is...empty?
Up until about 2 days ago, it's been routinely working fine. Records all user audio. Then, despite no changes from myself, it is only receiving empty audio.
I added logs to the handleCombinedAudio method, and it is firing, so it's receiving data, but it's nothing useful.
When I added a ConnectionListener, the onUserSpeaking method does correctly detect when people start and stop speaking. Just the AudioReceiveHandler seemingly isn't getting the data.
getGuild().getAudioManager().setConnectionListener(new ConnectionListener() {
            @Override
            public void onPing(long l) {

            }

            @Override
            public void onStatusChange(ConnectionStatus connectionStatus) {
                log("ConnectionStatus", connectionStatus.name());
            }

            @Override
            public void onUserSpeaking(User user, boolean b) {
                if (b) {
                    log("Spoke", user.getName() + "!");
                }
            }
        });
getGuild().getAudioManager().setReceivingHandler(getRecorder());
getGuild().getAudioManager().openAudioConnection(vc);

As stated above, the ConnectionStatus and Spoke logs are logged accurately.
VC is not null. getRecorder is not null, as the recorder variable is defined when the class is instantiated.
public Recorder(JDA jda, int id) {
        this.jda = jda;
        this.id = id;
        recorder = new AudioRecorder(jda, id);
        log("Recorder", "Finished setting up recorder #" + this.id);
    }

    public AudioRecorder getRecorder() {
        return recorder;
    }

The AudioReceiveHandler handles the audio as follows:
    @Override
    public void handleCombinedAudio(CombinedAudio combinedAudio) {
        log("CombinedAudio", "Received data!");
        try {
            if (getLinkedRecorder() != null) {
                Recorder rec = getLinkedRecorder();
                if (combinedAudio.getUsers().size() > 0) {
                    if (rec.getTranscriptFos() != null) {
                        try {
                            FileOutputStream fos = rec.getTranscriptFos();
                            StringBuilder names = new StringBuilder();
                            for (User user : combinedAudio.getUsers()) {
                                try {
                                    if (matches.containsKey(user.getId())) {
                                        if (!matches.get(user.getId()).equals(user.getName())) {
                                            matches.replace(user.getId(), (matches.get(user.getId()) + "," + user.getName()));
                                        }
                                    } else {
                                        matches.put(user.getId(), user.getName());
                                    }
                                } catch (Exception e) {
                                    e.printStackTrace();
                                }
                                names.append(user.getName()).append(",");
                            }
                            long diff = System.currentTimeMillis() - Long.parseLong(rec.getStartTime());
                            long minutes = TimeUnit.MILLISECONDS.toMinutes(diff);
                            diff -= TimeUnit.MINUTES.toMillis(minutes);
                            long seconds = TimeUnit.MILLISECONDS.toSeconds(diff);
                            diff -= TimeUnit.SECONDS.toMillis(seconds);
                            String time = minutes + ":" + seconds + "." + diff;
                            String toWrite = time + " > " + names.toString().substring(0, names.toString().length() - 1) + "\n";
                            fos.write(toWrite.getBytes());
                        } catch (IOException e) {
                            e.printStackTrace();
                        }
                    }
                }
                try {
                    FileOutputStream fos = rec.getOpusFos();
                    fos.write(combinedAudio.getAudioData(1.0));
                } catch (IOException e) {
                    e.printStackTrace();
                }
            } else {
                log("Debug", "No recorder linked. int=" + String.valueOf(recorder));
            }
        } catch (Exception e) {
            e.printStackTrace();
        }
    }

The "CombinedAudio" log at the start of the method is fired, rapidly, in ~20ms intervals, as would be expected.
canReceiveCombined does return true.
It 100% isn't that the ReceiveHandler isn't instantiated, as the files are being written to - it's just empty audio.
No idea why this randomly stopped working 2 days ago - I literally had made no changes to it.
And yeah, I know it'll be empty if noone talks. My issue is that there are users talking, and the bot isn't getting the audio data. the ConnectionListener is aware they are talking, but the AudioReceiveHandler isn't.

I know that audio will not be received if JDA-NAS is being used at the same time, apart from that I cannot tell what could cause your issue. Make sure you're capable of receiving datagram packets on your network/machine and that they are indeed received.

@ElectronicWizard I ran into this issue too and the fix is #653
I had removed the SilenceHandler because it was working without it but then it stopped working again. I'd say give it a shot. That's why @MinnDevelopment 's pastebin works, because it loops the received audio into the send handler.
Good Luck!

As per the final comment in #653, That error should be fixed now

@DV8FromTheWorld I get that, but I literally setup a dumb little loopback. For about 2 seconds after the bot joins VC, it does a basic echo of what it hears, and then stops. That fixes it. It now correctly gets the UDP packets.

@ElectronicWizard unfortunately, that's the way it is when Discord changes things and it affects everyone. I don't believe this is an issue with JDA itself. There's a small subset of us using the Voice features and JDA is pretty much the only library supporting this to a great extent.
That being said, instead of doing a loopback, just send 2 seconds of silence and you won't have that weird loopback.
Anyway, carry on and make good bots!

@ElectronicWizard @jvtrigueros Please follow #789.

authors: DV8FromTheWorld ElectronicWizard MinnDevelopment jvtrigueros kantenkugel


text:
Can you help connect the script to the PlayerJS player?

Hello, can you help please connect the script to PlayerJS
Here is the link to the player: https://playerjs.com/en/
Api: https://playerjs.com/docs/q=api

Try
function PlayerjsEvents(event, id, data){
    if(event==="init"){
        var video = document.querySelector("video");
        window.SubtitlesOctopusOnLoad = function () {
            var options = {
                video: video,
                subUrl: '/JavascriptSubtitlesOctopus/subtitles/test.ass',
                fonts: [
                    '/JavascriptSubtitlesOctopus/fonts/Arial.ttf',
                    '/JavascriptSubtitlesOctopus/fonts/TimesNewRoman.ttf'
                ],
                workerUrl: '/JavascriptSubtitlesOctopus/assets/js/subtitles-octopus-worker.js'
            };
            window.octopusInstance = new SubtitlesOctopus(options);
        };
        if (SubtitlesOctopus) {
            SubtitlesOctopusOnLoad();
        }
    }
}

function PlayerjsEvents(event, id, data){
if(event==="init"){
var video = document.querySelector("video");
window.SubtitlesOctopusOnLoad = function () {
var options = {
video: video,
subUrl: '/JavascriptSubtitlesOctopus/subtitles/test.ass',
fonts: [
'/JavascriptSubtitlesOctopus/fonts/Arial.ttf',
'/JavascriptSubtitlesOctopus/fonts/TimesNewRoman.ttf'
],
workerUrl: '/JavascriptSubtitlesOctopus/assets/js/subtitles-octopus-worker.js'
};
window.octopusInstance = new SubtitlesOctopus(options);
};
if (SubtitlesOctopus) {
SubtitlesOctopusOnLoad();
}
}
}

thanks a lot, everything worked

repo: Dador/JavascriptSubtitlesOctopus


text:
Game models are sometime darker than the environment suggests

Look at the reactor and the machinegun turret, they are too dark for the light we must expect at this place given the light on the lightmap:

This issue seems to be related to #324, game models always used lightgrid light direction. But in that case it also uses lightgrid color so there is not attempt to restore the color from lightmap and light direction (see #320).

For info, the map is terminus

Those models are lit with the lightgrid, I now consider this as an asset issue (the shipped lightgrid being too dark there).
At best this can be a bug in q3map2, but this map has no source, so no one can reproduce the bug on q3map2 side. One would open an issue on NetRadiant issue tracker if he reproduces it while compiling a map.

authors: bmorel illwieckz

repo: DaemonEngine/Daemon


text:
Fix the problem of map jitter when clicking cluster.

点击聚合点时，地图缩放后抖动的问题，是由于重复设置了click监听造成的。

其实这个 marker clusterer 是直接从官网扒的，我没考虑好是否应该直接在上面改 API

authors: Dafrok ipcjs


text:
I want change device name

How can i use tool do it？(If can do)
device name：amiibolink  -> other name

This has its own protocol, it isn’t compatible with amiibolink or others

This has its own protocol, it isn’t compatible with amiibolink or others

Is puck.js different from amiibolink? But can puck.js also input amiibo?


text:
Using sort() that is deprecated in Pandas.

I ran into the issue of a newer version of Pandas that uses sort_values or sort_index for sort (deprecated in 2017).  In PyALE_src\ALE_1D.py, sort is being called in line 96.  Can we switch to the newer function sort_values?  In other lines of the program, lines 61 and 221, sort_values and sort_index are being used.  I am getting an error, "AttributeError: 'Categorical' object has no attribute 'sort'".
Issue Code Line 95 and 96:
groups = X[feature].unique()
groups.sort()

Hi edwardmoradian,
groups is a numpy array (the output of unique) so the function sort in this location is not supposed to be pandas deprecated sort.
can you please provide a reproducible example of the error you got so I can take a deeper look into it?

Thanks for the clarification.  Looks like unique() is returning a Categorical dtype for me instead of the ndarray. I need to manipulate my data.

authors: DanaJomar edwardmoradian

repo: DanaJomar/PyALE


text:
[charts/redis-ha][BUG] Lost conectivity due to announce service

Description:
Lost connectivity first to master and then to slave.
Steps to reproduce the behavior:

Start minikube on debian VM.
Set hardAntiAffinity to false.
Setup redis-ha.
Wait until master<-> slave relationships are settled.
Check logs of sentinel.
Delete master with kubectl delete.
Wait until failover is complete and master<-> slave relationships are settled.
Check redis-cli role on each replica.

Actual behaviour
At step 5 there is a +sdown master mymaster 10.107.27.237 6379 in master sentinel logs.
At step 8:
Pod 0 result of redis-cli role

"slave"
"10.109.188.240"
(integer) 6379
"connected"
(integer) 103726

Pod 1 result of redis-cli role

"master"
(integer) 104010

"10.107.27.237"
"6379"
"103868"

Pod 2 result of redis-cli role

"slave"
"10.107.27.237"
(integer) 6379
"connected"
(integer) 104010

Expected behaviour
There should no sdown reported, and there should be one master that reports two connected slaves, and two slaves that report connection to the master.
Additional context
Kubernetes version: v1.15.4
Helm version: v2.15.1
Minikube version: v1.6.2
Redis HA version: v4.5.2
Debian version: 9.11 (VM running on Windows 10)
I have tested with version Redis HA version 3.0.3 and there the same problem does not occur, but it appears on 3.0.4, thus the claim in the title that it depends on the announce service.
I have also been able to test in another environment where this problems does not occur, but in minikube it occurs almost every time I run the test.
Furthermore, when running this test I have also seen that the result have been three slaves that do not do a proper failover, and also split-brain, i.e. two masters and one slave, but I haven't analysed these issues further.
Is this a known issue or a bug?

@StefanKarlsson321 Can you throw some logs at me? The redis-cli commands look valid?
Does Minikube come with hairpining enabled? I know I've seen something like this happen my cluster wasn't allowing hairpinning which messed with the comms between the nodes.

The redis-cli command only shows one slave connected on master which is wrong. Correct output with two connected slaves should be:
1) "master"
2) (integer) 30847
3) 1) 1) "10.101.85.243"
      2) "6379"
      3) "30847"
   2) 1) "10.110.234.71"
      2) "6379"
      3) "30847"

No minikube does not have hairpin enabled it seems. I have actually found out also that it is the reason. redis-sentinel cannot contact redis-server on the same pod due to using the announce ip service. I have confirmed this by checking whether redis can reach itself through the announced ip, when source and destination is the same pod. It cannot. When the destinations are not the same it works however.
I have been sparse with logs since there are plenty of them. But I see something that looks wrong when master starts up, i.e. the last message +sdown. This is probably due to that redis-sentinel cannot reach redis-server from the same pod then:
(Sentinel logs of master pod server-0)
1:X 03 Apr 2020 09:39:24.765 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:X 03 Apr 2020 09:39:24.765 # Redis version=5.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
1:X 03 Apr 2020 09:39:24.765 # Configuration loaded
1:X 03 Apr 2020 09:39:24.767 * Running mode=sentinel, port=26379.
1:X 03 Apr 2020 09:39:24.767 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:X 03 Apr 2020 09:39:24.767 # Sentinel ID is 50ac74ff20de0efb51e8d72400e2a6365c394553
1:X 03 Apr 2020 09:39:24.767 # +monitor master mymaster 10.96.182.167 6379 quorum 2
1:X 03 Apr 2020 09:39:34.773 # +sdown master mymaster 10.96.182.167 6379

Similarly the slaves also report themselves to be down:
(Sentinel logs of slave pod server-1)
1:X 03 Apr 2020 09:39:29.875 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:X 03 Apr 2020 09:39:29.875 # Redis version=5.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
1:X 03 Apr 2020 09:39:29.875 # Configuration loaded
1:X 03 Apr 2020 09:39:29.877 * Running mode=sentinel, port=26379.
1:X 03 Apr 2020 09:39:29.877 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:X 03 Apr 2020 09:39:29.877 # Sentinel ID is 12ac0bdf6462de03e2d9ed378dea0ac96434d9cf
1:X 03 Apr 2020 09:39:29.877 # +monitor master mymaster 10.96.182.167 6379 quorum 2
1:X 03 Apr 2020 09:39:29.878 * +slave slave 10.101.85.243:6379 10.101.85.243 6379 @ mymaster 10.96.182.167 6379
1:X 03 Apr 2020 09:39:39.924 # +sdown slave 10.101.85.243:6379 10.101.85.243 6379 @ mymaster 10.96.182.167 6379
1:X 03 Apr 2020 09:39:46.105 * +sentinel sentinel 7f3dd8c6941e6456bf071c702d42be93134af6c8 10.110.234.71 26379 @ mymaster 10.96.182.167 6379
1:X 03 Apr 2020 09:39:49.984 * +slave slave 10.110.234.71:6379 10.110.234.71 6379 @ mymaster 10.96.182.167 6379

When I delete master  it wakes up and becomes a slave with basically the same logs as above sentinel logs of slave pod:
(Contnued sentinel logs of  pod server-0)
1:X 03 Apr 2020 09:44:37.923 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:X 03 Apr 2020 09:44:37.923 # Redis version=5.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
1:X 03 Apr 2020 09:44:37.923 # Configuration loaded
1:X 03 Apr 2020 09:44:37.925 * Running mode=sentinel, port=26379.
1:X 03 Apr 2020 09:44:37.925 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:X 03 Apr 2020 09:44:37.925 # Sentinel ID is 50ac74ff20de0efb51e8d72400e2a6365c394553
1:X 03 Apr 2020 09:44:37.925 # +monitor master mymaster 10.101.85.243 6379 quorum 2
1:X 03 Apr 2020 09:44:37.926 * +slave slave 10.96.182.167:6379 10.96.182.167 6379 @ mymaster 10.101.85.243 6379
1:X 03 Apr 2020 09:44:38.590 * +sentinel sentinel 7f3dd8c6941e6456bf071c702d42be93134af6c8 10.110.234.71 26379 @ mymaster 10.101.85.243 6379
1:X 03 Apr 2020 09:44:38.598 # +new-epoch 1
1:X 03 Apr 2020 09:44:42.045 * +sentinel sentinel 12ac0bdf6462de03e2d9ed378dea0ac96434d9cf 10.101.85.243 26379 @ mymaster 10.101.85.243 6379
1:X 03 Apr 2020 09:44:47.980 # +sdown slave 10.96.182.167:6379 10.96.182.167 6379 @ mymaster 10.101.85.243 6379

Following the new master will report the additional logs:
(Continued logs of slave that becomes master server-1)
1:X 03 Apr 2020 09:44:27.536 # +new-epoch 1
1:X 03 Apr 2020 09:44:27.536 # +config-update-from sentinel 7f3dd8c6941e6456bf071c702d42be93134af6c8 10.110.234.71 26379 @ mymaster 10.96.182.167 6379
1:X 03 Apr 2020 09:44:27.536 # +switch-master mymaster 10.96.182.167 6379 10.101.85.243 6379
1:X 03 Apr 2020 09:44:27.537 * +slave slave 10.110.234.71:6379 10.110.234.71 6379 @ mymaster 10.101.85.243 6379
1:X 03 Apr 2020 09:44:27.537 * +slave slave 10.96.182.167:6379 10.96.182.167 6379 @ mymaster 10.101.85.243 6379
1:X 03 Apr 2020 09:44:37.564 # +sdown master mymaster 10.101.85.243 6379
1:X 03 Apr 2020 09:44:37.564 # +sdown slave 10.96.182.167:6379 10.96.182.167 6379 @ mymaster 10.101.85.243 6379
1:X 03 Apr 2020 09:44:38.034 # -sdown slave 10.96.182.167:6379 10.96.182.167 6379 @ mymaster 10.101.85.243 6379
1:X 03 Apr 2020 09:44:39.997 * +sentinel sentinel 50ac74ff20de0efb51e8d72400e2a6365c394553 10.96.182.167 26379 @ mymaster 10.101.85.243 6379

The slave that does not get promoted reports:
(Full logs of server-2)
1:X 03 Apr 2020 09:39:44.090 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:X 03 Apr 2020 09:39:44.090 # Redis version=5.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
1:X 03 Apr 2020 09:39:44.090 # Configuration loaded
1:X 03 Apr 2020 09:39:44.092 * Running mode=sentinel, port=26379.
1:X 03 Apr 2020 09:39:44.092 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:X 03 Apr 2020 09:39:44.092 # Sentinel ID is 7f3dd8c6941e6456bf071c702d42be93134af6c8
1:X 03 Apr 2020 09:39:44.092 # +monitor master mymaster 10.96.182.167 6379 quorum 2
1:X 03 Apr 2020 09:39:44.093 * +slave slave 10.101.85.243:6379 10.101.85.243 6379 @ mymaster 10.96.182.167 6379
1:X 03 Apr 2020 09:39:44.105 * +slave slave 10.110.234.71:6379 10.110.234.71 6379 @ mymaster 10.96.182.167 6379
1:X 03 Apr 2020 09:39:44.158 * +sentinel sentinel 12ac0bdf6462de03e2d9ed378dea0ac96434d9cf 10.101.85.243 26379 @ mymaster 10.96.182.167 6379
1:X 03 Apr 2020 09:39:54.138 # +sdown slave 10.110.234.71:6379 10.110.234.71 6379 @ mymaster 10.96.182.167 6379
1:X 03 Apr 2020 09:44:27.159 # Executing user requested FAILOVER of 'mymaster'
1:X 03 Apr 2020 09:44:27.159 # +new-epoch 1
1:X 03 Apr 2020 09:44:27.159 # +try-failover master mymaster 10.96.182.167 6379
1:X 03 Apr 2020 09:44:27.207 # +vote-for-leader 7f3dd8c6941e6456bf071c702d42be93134af6c8 1
1:X 03 Apr 2020 09:44:27.207 # +elected-leader master mymaster 10.96.182.167 6379
1:X 03 Apr 2020 09:44:27.207 # +failover-state-select-slave master mymaster 10.96.182.167 6379
1:X 03 Apr 2020 09:44:27.263 # +selected-slave slave 10.101.85.243:6379 10.101.85.243 6379 @ mymaster 10.96.182.167 6379
1:X 03 Apr 2020 09:44:27.263 * +failover-state-send-slaveof-noone slave 10.101.85.243:6379 10.101.85.243 6379 @ mymaster 10.96.182.167 6379
1:X 03 Apr 2020 09:44:27.335 * +failover-state-wait-promotion slave 10.101.85.243:6379 10.101.85.243 6379 @ mymaster 10.96.182.167 6379
1:X 03 Apr 2020 09:44:27.462 # +promoted-slave slave 10.101.85.243:6379 10.101.85.243 6379 @ mymaster 10.96.182.167 6379
1:X 03 Apr 2020 09:44:27.462 # +failover-state-reconf-slaves master mymaster 10.96.182.167 6379
1:X 03 Apr 2020 09:44:27.529 * +slave-reconf-sent slave 10.110.234.71:6379 10.110.234.71 6379 @ mymaster 10.96.182.167 6379
1:X 03 Apr 2020 09:44:27.529 # +failover-end master mymaster 10.96.182.167 6379
1:X 03 Apr 2020 09:44:27.529 # +switch-master mymaster 10.96.182.167 6379 10.101.85.243 6379
1:X 03 Apr 2020 09:44:27.529 * +slave slave 10.110.234.71:6379 10.110.234.71 6379 @ mymaster 10.101.85.243 6379
1:X 03 Apr 2020 09:44:27.529 * +slave slave 10.96.182.167:6379 10.96.182.167 6379 @ mymaster 10.101.85.243 6379
1:X 03 Apr 2020 09:44:37.553 # +sdown slave 10.96.182.167:6379 10.96.182.167 6379 @ mymaster 10.101.85.243 6379
1:X 03 Apr 2020 09:44:37.553 # +sdown slave 10.110.234.71:6379 10.110.234.71 6379 @ mymaster 10.101.85.243 6379
1:X 03 Apr 2020 09:44:38.040 # -sdown slave 10.96.182.167:6379 10.96.182.167 6379 @ mymaster 10.101.85.243 6379
1:X 03 Apr 2020 09:44:39.997 * +sentinel sentinel 50ac74ff20de0efb51e8d72400e2a6365c394553 10.96.182.167 26379 @ mymaster 10.101.85.243 6379

What I gather is that the extra +sdown messages are due to the hairpin problem, and can likely cause further issues. I see a workaround  at https://stackoverflow.com/questions/54911270/kubernetes-service-can-not-send-request-to-itself, but since I run the none vmdriver it is not possible for me.

@StefanKarlsson321 Sorry I didn't get back to you on this.
Are you suggestion that we find a workaround for this, or are you happy for this to be closed?

This can be closed. It is quite a small use case.

repo: DandyDeveloper/charts


text:
no autocomplete when typing ident right after -

foo := -no_autocomplete_here
foo := - this_is_fine

nvm this is a sublime issue, not ols: https://github.com/sublimehq/sublime_text/issues/456

repo: DanielGavin/ols


text:
add os

@ErikJiang @Rei1010  麻烦 review 下

See preview:
https://deploy-preview-4958--daocloud-docs.netlify.app/install/best-practices/replace-os

/lgtm

authors: Rei1010 jzhupup windsonsea

repo: DaoCloud/DaoCloud-docs


text:
printing primitive arrays in opts in one line

This fixes #22 and prints all arrays that contain only primitive values in one line like the key or cert buffer

@coolaj86 I would just print these long arrays in one line, what do you think?
Then the startup linecount isn't pushing the begin of itself out of the terminal line buffer anymore.

repo: Daplie/letsencrypt-express


text:
Fix 403 forbiden issue on prod

While local development works for all request types (GET, POST, PUT, DELETE, etc) prod is only allowing GET requests. I believe this is most likely a CSRF issue, but may be related to something else like CORs or a firewall issue.

closed by #205, #204, and #202

repo: DartExplore/dallas-by-metro-backend


text:
Xenos ? BlackBone Manual Mapping Error?

User Manual Mapping & Kernel Manual Mapping
Test OS:windows 7 x64 ultimate
32bit & 64bit dll File Manual Mapping No option Injection
But 10~20 Time -> ManualMapping dll Thread Dead
Extreme Injector ManualMapping dll Thread no dead
test.dll file cmd.exe <-- manual mapping injection!
test.zip

So what's the actual issue? It doesn't inject or what?

manual mapping dll injection The resulting thread dies within 10~20 seconds

Thread must die, injector leaves no traces after job is done.

no injector form dead video
https://youtu.be/6eTlFOq2BcE

It's a bug in your dll. You do not return from DllMain. Create new thread and start your from it.

repo: DarthTon/Blackbone


text:
NET test suite wrongly assumes every device has an "enp*" interface

Device
Optiplex 7010
RTE version

OSFV version
optiplex-resurrect-release-v0.1.0
Affected component(s) or functionality
NET test suite
Brief summary
The test assumes that the ethernet interface is called enp*, it is not on optiplex 7010
How reproducible
100%
How to reproduce
Run the tests or see manually using ip a that there is no enp* interface. The name enp* is set as an "altname" for interface eno0.
Expected behavior
The test should pass if interface eno0 is UP
Actual behavior
it does not, because it checks only the line in ip a that contains enp*, but the line only informs that this is an altname. It does not contain "UP" therefore the test fails
Link to screenshots or logs

Additional context
dasharo-stability_log.zip
Multiple tests failed here. Look for the NET test suite.
Solutions you've tried
Maybe just adding eno as an alternative to enp would be enough? Something like:
${network_status}=    Execute Command In Terminal    ip link | grep -E 'enp'
        Should Contain    ${network_status}    UP

replace to:
${network_status}=    Execute Command In Terminal    ip link | grep -E 'enp|eno'
        Should Contain    ${network_status}    UP

There are few more names that we could include to "future-proof" this test case. Depending on OS and board used this enumeration might vary.
    eno: Names containing the index numbers provided by firmware/BIOS for on-board devices, example: eno1 (eno = Onboard).
    ens: Names containing the PCI Express hotplug slot numbers provided by the firmware/BIOS, example: ens1 (ens = Slot).
    enp: Names containing the physical/geographical location of the hardware's port, example: enp2s0 (enp = Position).
    enx: Names containing the MAC address of the interface (example: enx78e7d1ea46da).
    eth: Classic unpredictable kernel-native ethX naming (example: eth0).

Taken from: https://www.thomas-krenn.com/en/wiki/Predictable_Network_Interface_Names

authors: SebastianCzapla philipandag

repo: Dasharo/open-source-firmware-validation


text:
[risk=no] Security patches for jackson

Addresses
Update to the latest dropwizard version which addresses the latest jackson issue.
Covers these SC issues:

https://broadinstitute-dsp.sourceclear.io/workspaces/jppForw/issues/vulnerabilities/7039263/18759598
https://broadinstitute-dsp.sourceclear.io/workspaces/jppForw/issues/vulnerabilities/7039263/18759597
https://broadinstitute-dsp.sourceclear.io/workspaces/jppForw/issues/vulnerabilities/7039263/6580955
https://broadinstitute-dsp.sourceclear.io/workspaces/jppForw/issues/vulnerabilities/7039263/6580954
https://broadinstitute-dsp.sourceclear.io/workspaces/jppForw/issues/vulnerabilities/7039263/6580953
https://broadinstitute-dsp.sourceclear.io/workspaces/jppForw/issues/vulnerabilities/7039263/6580952
https://broadinstitute-dsp.sourceclear.io/workspaces/jppForw/issues/vulnerabilities/7039263/6580950

Coverage remained the same at 62.254% when pulling f96bdf2568bf9ac988dfc84ed8bb014861c5d39c on security into b1955a72d6f81dd97b37f3434e158f91cae10eee on develop.

authors: coveralls rushtong

repo: DataBiosphere/consent


text:
Always decode objectPath

The generated openapi rest controller doesn't seem to be decoding path params.

can you give more context? e.g. a ticket, or the before and after

authors: rogerwangcs yuhuyoyo

repo: DataBiosphere/terra-axon-server


text:
[Mac] DMG install process failures

The upgrade process is never clean on brew cask upgrade which seems to just pull the DMG and install.
brew cask upgrade output
==> Downloading https://s3.amazonaws.com/dd-agent/datadogagent.dmg
######################################################################## 100.0%
==> Verifying checksum for Cask datadog-agent
==> Starting upgrade for Cask datadog-agent
==> Running uninstall process for datadog-agent; your password may be necessary
==> Uninstalling packages:
com.datadoghq.agent
==> rm: /opt/datadog-agent/embedded/share/terminfo/2/2621a: No such file or directory
==> rm: /opt/datadog-agent/embedded/share/terminfo/e/eterm: No such file or directory
==> rm: /opt/datadog-agent/embedded/share/terminfo/e/eterm-color: No such file or directory
==> rm: /opt/datadog-agent/embedded/share/terminfo/h/hp2621a: No such file or directory
==> rm: /opt/datadog-agent/embedded/share/terminfo/h/hp70092a: No such file or directory
==> rm: /opt/datadog-agent/embedded/share/terminfo/l/lft-pc850: No such file or directory
==> rm: /opt/datadog-agent/embedded/share/terminfo/n/ncr260vt300wpp: No such file or directory
==> rm: /opt/datadog-agent/embedded/share/terminfo/n/ncrvt100wpp: No such file or directory
==> rm: /opt/datadog-agent/embedded/share/terminfo/p/p12: No such file or directory
==> rm: /opt/datadog-agent/embedded/share/terminfo/p/p12-m: No such file or directory
==> rm: /opt/datadog-agent/embedded/share/terminfo/p/p12-m-w: No such file or directory
==> rm: /opt/datadog-agent/embedded/share/terminfo/p/p12-w: No such file or directory
==> rm: /opt/datadog-agent/embedded/share/terminfo/p/p14: No such file or directory
==> rm: /opt/datadog-agent/embedded/share/terminfo/p/p14-m: No such file or directory
==> rm: /opt/datadog-agent/embedded/share/terminfo/p/p14-m-w: No such file or directory
==> rm: /opt/datadog-agent/embedded/share/terminfo/p/p14-w: No such file or directory
==> rm: /opt/datadog-agent/embedded/share/terminfo/p/p4: No such file or directory
==> rm: /opt/datadog-agent/embedded/share/terminfo/p/p5: No such file or directory
==> rm: /opt/datadog-agent/embedded/share/terminfo/p/p7: No such file or directory
==> rm: /opt/datadog-agent/embedded/share/terminfo/p/p8: No such file or directory
==> rm: /opt/datadog-agent/embedded/share/terminfo/p/p8-w: No such file or directory
==> rm: /opt/datadog-agent/embedded/share/terminfo/p/p9: No such file or directory
==> rm: /opt/datadog-agent/embedded/share/terminfo/p/p9-8: No such file or directory
==> rm: /opt/datadog-agent/embedded/share/terminfo/p/p9-8-w: No such file or directory
==> rm: /opt/datadog-agent/embedded/share/terminfo/p/p9-w: No such file or directory
==> Purging files for version 6.0.3-1 of Cask datadog-agent
Error: Command failed to execute!

==> Failed command:
/usr/bin/sudo -E -- /usr/bin/xargs -0 -- /bin/rm --

==> Standard Output of failed command:

==> Standard Error of failed command:
rm: /opt/datadog-agent/embedded/share/terminfo/2/2621a: No such file or directory
rm: /opt/datadog-agent/embedded/share/terminfo/e/eterm: No such file or directory
rm: /opt/datadog-agent/embedded/share/terminfo/e/eterm-color: No such file or directory
rm: /opt/datadog-agent/embedded/share/terminfo/h/hp2621a: No such file or directory
rm: /opt/datadog-agent/embedded/share/terminfo/h/hp70092a: No such file or directory
rm: /opt/datadog-agent/embedded/share/terminfo/l/lft-pc850: No such file or directory
rm: /opt/datadog-agent/embedded/share/terminfo/n/ncr260vt300wpp: No such file or directory
rm: /opt/datadog-agent/embedded/share/terminfo/n/ncrvt100wpp: No such file or directory
rm: /opt/datadog-agent/embedded/share/terminfo/p/p12: No such file or directory
rm: /opt/datadog-agent/embedded/share/terminfo/p/p12-m: No such file or directory
rm: /opt/datadog-agent/embedded/share/terminfo/p/p12-m-w: No such file or directory
rm: /opt/datadog-agent/embedded/share/terminfo/p/p12-w: No such file or directory
rm: /opt/datadog-agent/embedded/share/terminfo/p/p14: No such file or directory
rm: /opt/datadog-agent/embedded/share/terminfo/p/p14-m: No such file or directory
rm: /opt/datadog-agent/embedded/share/terminfo/p/p14-m-w: No such file or directory
rm: /opt/datadog-agent/embedded/share/terminfo/p/p14-w: No such file or directory
rm: /opt/datadog-agent/embedded/share/terminfo/p/p4: No such file or directory
rm: /opt/datadog-agent/embedded/share/terminfo/p/p5: No such file or directory
rm: /opt/datadog-agent/embedded/share/terminfo/p/p7: No such file or directory
rm: /opt/datadog-agent/embedded/share/terminfo/p/p8: No such file or directory
rm: /opt/datadog-agent/embedded/share/terminfo/p/p8-w: No such file or directory
rm: /opt/datadog-agent/embedded/share/terminfo/p/p9: No such file or directory
rm: /opt/datadog-agent/embedded/share/terminfo/p/p9-8: No such file or directory
rm: /opt/datadog-agent/embedded/share/terminfo/p/p9-8-w: No such file or directory
rm: /opt/datadog-agent/embedded/share/terminfo/p/p9-w: No such file or directory

==> Exit status of failed command:
#<Process::Status: pid 9930 exit 1>

Describe what happened:
cask upgrading datadog-agent fails and requires manual intervention.
Step 1: See above.
Step 2: Copy your config over, this is going to be "fun".
Step 3: Let's try uninstalling: Fail 2
brew cask uninstall datadog-agent
==> Uninstalling Cask datadog-agent
==> Running uninstall process for datadog-agent; your password may be necessary
==> Uninstalling packages:
com.datadoghq.agent
Password:

Error: No such file or directory @ rb_file_s_stat - /opt/datadog-agent/embedded/share/terminfo/X
Follow the instructions here:
  https://github.com/caskroom/homebrew-cask#reporting-bugs
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/pkg.rb:96:in `stat'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/pkg.rb:96:in `stat'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/pkg.rb:96:in `with_full_permissions'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/pkg.rb:30:in `block in uninstall'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/pkg.rb:29:in `each'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/pkg.rb:29:in `uninstall'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/artifact/abstract_uninstall.rb:214:in `block (2 levels) in uninstall_pkgutil'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/artifact/abstract_uninstall.rb:212:in `each'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/artifact/abstract_uninstall.rb:212:in `block in uninstall_pkgutil'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/artifact/abstract_uninstall.rb:211:in `each'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/artifact/abstract_uninstall.rb:211:in `uninstall_pkgutil'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/artifact/abstract_uninstall.rb:59:in `block in dispatch_uninstall_directives'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/artifact/abstract_uninstall.rb:56:in `each'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/artifact/abstract_uninstall.rb:56:in `dispatch_uninstall_directives'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/artifact/uninstall.rb:7:in `uninstall_phase'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/installer.rb:403:in `block in uninstall_artifacts'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/2.3.0/set.rb:674:in `each'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/2.3.0/set.rb:674:in `each'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/installer.rb:400:in `uninstall_artifacts'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/installer.rb:353:in `uninstall'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/uninstall.rb:22:in `block in run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/uninstall.rb:12:in `each'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/uninstall.rb:12:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/abstract_command.rb:35:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:98:in `run_command'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:168:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:132:in `run'
/usr/local/Homebrew/Library/Homebrew/cmd/cask.rb:8:in `cask'
/usr/local/Homebrew/Library/Homebrew/brew.rb:100:in `<main>'

Step 4: Is it still there? Yes, kinda:
ls -l /opt/datadog-agent
total 0
drwxr-xr-x 15 root    wheel 480 Mar 14 08:19 LICENSES
drwxr-xr-x  3 root    wheel  96 Mar 14 08:19 bin
drwxr-xr-x  9 root    wheel 288 Mar  7 05:46 embedded
drwxr-xr-x  6 **** admin 192 Mar 14 08:19 etc
drwxr-xr-x  2 **** admin  64 Mar  7 05:43 run
drwxr-xr-x  2 root    wheel  64 Mar  7 05:43 scripts
drwxr-xr-x  3 root    wheel  96 Mar  7 05:43 sources

Step 5: Kill it with fire: sudo rm -Rf /opt/datadog-agent
Step 6: Now you must make homebrew happy:
brew cask uninstall datadog-agent
==> Uninstalling Cask datadog-agent
==> Running uninstall process for datadog-agent; your password may be necessary
==> Uninstalling packages:
com.datadoghq.agent
==> Purging files for version 6.0.2-1 of Cask datadog-agent

Step 7: Now install again:
brew cask install datadog-agent
==> Caveats
You will need to update /opt/datadog-agent/etc/datadog.conf and replace APIKEY with your api key

If you ever want to start/stop the Agent, please use the Datadog Agent App or datadog-agent command.
It will start automatically at login, if you want to enable it at startup, run these commands:

sudo cp '/opt/datadog-agent/etc/com.datadoghq.agent.plist' /Library/LaunchDaemons
sudo launchctl load -w /Library/LaunchDaemons/com.datadoghq.agent.plist

==> Satisfying dependencies
==> Downloading https://s3.amazonaws.com/dd-agent/datadogagent.dmg
Already downloaded: /Users/*****/Library/Caches/Homebrew/Cask/datadog-agent--6.0.3-1.dmg
==> Verifying checksum for Cask datadog-agent
==> Installing Cask datadog-agent
==> Running installer for datadog-agent; your password may be necessary.
==> Package installers may write to any location; options such as --appdir are ignored.
==> installer: Package name is Agent
==> installer: Installing at base path /
==> installer: The install was successful.
🍺  datadog-agent was successfully installed!

Step 8: Now copy back over your config & restart the agent. And we're left with:
ls -l /opt/datadog-agent
total 48
-rw-r--r--   1 root    wheel 31633 Mar 12 08:31 LICENSE
drwxr-xr-x 121 root    wheel  3872 Mar 14 08:29 LICENSES
-rw-r--r--   1 root    wheel    30 Mar 12 08:27 agent_requirements.txt
drwxr-xr-x   4 root    wheel   128 Mar 12 08:27 bin
drwxr-xr-x   9 root    wheel   288 Mar 12 08:29 embedded
drwxr-xr-x   7 ***** admin   224 Mar 14 08:29 etc
drwxr-xr-x   2 ***** admin    64 Mar 12 08:27 run
drwxr-xr-x   2 root    wheel    64 Mar 12 08:27 scripts
drwxr-xr-x   3 root    wheel    96 Mar 12 08:19 sources
-rw-r--r--   1 root    wheel  7906 Mar 12 08:31 version-manifest.json
-rw-r--r--   1 root    wheel  2843 Mar 12 08:31 version-manifest.txt

Describe what you expected:
Clean upgrade process that is tolerant of directories missing and minor errors.
Steps to reproduce the issue:
just upgrade 🍭 See above.
Additional environment details (Operating System, Cloud provider, etc):
OS: High Sierra 10.13.3
Model: MBP 2017

Hi @platinummonkey! Thanks for the detailed report.
The datadog-agent cask isn't officially supported and we haven't tested the upgrade path from Agent v5 to 6 on the cask.
I'm not very familiar with how casks work, and which commands are run exactly when upgrading a pkg, but upgrades from v5 to v6 work without errors when done using the official install script or when executing the DMG directly.
Would you happen to know which tools/command cask uses internally to install/upgrade a pkg?

hey! I didn't try from v5 to v6, only v6.<some revision> -> v6.<some newer revision>. In a nutshell it's just downloading the DMG extracting the pkg and installing that.

same things happens this latest release datadog-agent (6.0.3-1) --> 6.1.0-1

authors: olivielpeau platinummonkey

repo: DataDog/datadog-agent


text:
[CWS] fix hardlink for exec in overlayfs

What does this PR do?
This PR fixes the Nlink value of files for exec events in overlayfs. This value is used during the path resolution in order to determine if the cache has to be used or not. Before this PR exec events in busybox container, using hardlink, were having path resolution issue. The first entry in the cache for a busybox binary was used for all the subsequent resolutions whatever the command used.

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

@safchain do we still need this ? Can I help rebasing it ?

authors: paulcacheux safchain


text:
[USMON-711] USM: Ignore TLS traffic from decoding in socket-filter

What does this PR do?
If a connection was classified as TLS, then we're not processing it in our socket-filter callbacks.

Motivation
In the context of a socket filter we're not able to decode encrypted traffic.
Thus, we should abort early.
The only exception for this new rule is TCP termination, meaning, if we're identifying
a TCP termination, we should still process it in our probes. This is a fallback for missing
TLS termination and ensure we're cleaning resources.

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided. Except if the qa/skip-qa label, with required either qa/done or qa/no-code-change labels, are applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

/merge


text:
Change testing of configprovider

What does this PR do?
Currently, the config returned by the custom config provider Get is tested against a manually built otelcol.Config struct. This will become unmaintainable as we add more test cases.
This PR changes this so we test the output of our custom config provider Get against the output of Get using the "upstream" configprovider. Currently, we are not modifying the config, so both Gets will point to the same URI in the test. Once we add support for enhanced config, we will start pointing the "upstream" Get we are validating against to a "result.yaml" files.
Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


text:
[E2E] Do not log executed commands in case it contains secrets

What does this PR do?

Do not log commands executed to avoid leaking secrets.
Motivation

Avoid leaking secrets.
Additional Notes

It would nice to print something to identify the command / scrub it, but for now just don't.
Introduced by https://github.com/DataDog/datadog-agent/pull/27595.
Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge -p incident


text:
Handle unregistered teams in the chase_release_managers task and fix a link

What does this PR do?

Handle unregistered team in the chase_release_managers task
Fix a link
Add some logs

Motivation

The link is not properly rendered
Missing teams in the map make the script explode. Fixing it writing a message to let the users know

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


text:
Add support BP_DATADOGTRACE_ENABLED

Updated dependencies:

golang 1.16
pack 0.20.0
jam 0.14.3
buildpack.toml api 0.6

In addition to service binding will the buildpack participate if BP_DATADOGTRACE_ENABLED is set.

still WIP

I've successfully tested the pull request with a spring sample application and do see the datadog trace agent:
Picked up JAVA_TOOL_OPTIONS: -Djava.security.properties=/layers/paketo-buildpacks_bellsoft-liberica/java-security-properties/java-security.properties -agentpath:/layers/paketo-buildpacks_bellsoft-liberica/jvmkill/jvmkill-1.16.0-RELEASE.so=printHeapHistogram=1 -javaagent:/layers/paketo-buildpacks_datadog-trace/datadog-trace-java/dd-java-agent.jar -XX:ActiveProcessorCount=6 -XX:MaxDirectMemorySize=10M -Xmx2490385K -XX:MaxMetaspaceSize=88998K -XX:ReservedCodeCacheSize=240M -Xss1M -Dorg.springframework.cloud.bindings.boot.enable=true
[dd.trace 2021-08-20 10:28:57:263 +0000] [dd-task-scheduler] INFO datadog.trace.agent.core.StatusLogger - DATADOG TRACER CONFIGURATION {"version":"0.85.0~2626c788b3","os_name":"Linux","os_version":"5.10.25-linuxkit","architecture":"amd64","lang":"jvm","lang_version":"11.0.12","jvm_vendor":"BellSoft","jvm_version":"11.0.12+7-LTS","java_class_version":"55.0","http_nonProxyHosts":"null","http_proxyHost":"null","enabled":true,"service":"org.springframework.boot.loader.JarLauncher","agent_url":"http://localhost:8126","agent_error":true,"debug":false,"analytics_enabled":false,"sampling_rules":[{},{}],"priority_sampling_enabled":true,"logs_correlation_enabled":true,"profiling_enabled":false,"appsec_enabled":false,"dd_version":"0.85.0~2626c788b3","health_checks_enabled":true,"configuration_file":"no config file present","runtime_id":"b376de41-fea9-4a47-b829-9ed5dd049fed","logging_settings":{"levelInBrackets":false,"dateTimeFormat":"'[dd.trace 'yyyy-MM-dd HH:mm:ss:SSS Z']'","logFile":"System.err","configurationFile":"simplelogger.properties","showShortLogName":false,"showDateTime":true,"showLogName":true,"showThreadName":true,"defaultLogLevel":"INFO","warnLevelString":"WARN","embedException":false}}

An image with these changes is available here: ghcr.io/vchrisb/datadog-trace-paketo-buildpack/datadog-trace-paketo-buildpack:1.0.3
Due to the lack of a datadog environment, I was not able to test it end-to-end.
Looking at the Datadog Java Agent docs, any configuration files are optional, hence the introduction of BP_DATADOGTRACE_ENABLED to make enablement easier.
I also set the datadog agent version explicitly to have a deterministic version in the buildpack.
@kevinfwl could you have a look at the proposed changes and test it with a Datadog environment? 💯

repo: DataDog/datadog-trace-paketo-buildpack


text:
RUMM-2770: Improve mapping upload flow handling

What does this PR do?
This change improves mapping upload flow handling by doing the following:

Additional check for the API key validity is done (using API key validation API) if server returns code 400, this is basically aligns logic with datadog-ci.
Removed a statement saying that server may already have mapping uploaded - server will never return error if there is already mapping uploaded.
Added an additional check for quotes\apostrophes in API key, this may be useful for the error investigation on the client side (this check is quite limited to only quotes and apostrophes, because there is no public contract for the API key format).
Added a site name to the upload info message (and to some other messages as well).

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #131 (8268d10) into develop (5d67abb) will decrease coverage by 1.20%.
The diff coverage is 75.61%.

@@              Coverage Diff              @@
##             develop     #131      +/-   ##
=============================================
- Coverage      87.45%   86.25%   -1.20%
- Complexity       169      174       +5
=============================================
  Files             21       21
  Lines            526      560      +34
  Branches          65       72       +7
=============================================
+ Hits             460      483      +23
- Misses            42       49       +7
- Partials          24       28       +4

Impacted Files
Coverage Δ

...in/kotlin/com/datadog/gradle/plugin/DatadogSite.kt
84.62% <0.00%> (-15.38%)
:arrow_down:

...m/datadog/gradle/plugin/DdMappingFileUploadTask.kt
88.49% <75.00%> (-0.48%)
:arrow_down:

...m/datadog/gradle/plugin/internal/OkHttpUploader.kt
82.52% <77.78%> (-3.78%)
:arrow_down:

repo: DataDog/dd-sdk-android-gradle-plugin


text:
fix: Standardize architectures

What does this PR do?
The symbolication service currently understands arm, arm64, x86 and x64 as valid symbol file architectures. Instead of adding the Android ABIs, we map them to those architectures instead.
Review checklist (to be filled by reviewers)

[x] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #249 (bb01f6f) into develop (81aace0) will increase coverage by 0.43%.
The diff coverage is 90.91%.

Additional details and impacted files
@@              Coverage Diff              @@
##             develop     #249      +/-   ##
=============================================
+ Coverage      81.30%   81.73%   +0.43%
- Complexity       203      205       +2
=============================================
  Files             26       26
  Lines            802      810       +8
  Branches         104      104
=============================================
+ Hits             652      662      +10
  Misses           112      112
+ Partials          38       36       -2

Files
Coverage Δ

...datadog/gradle/plugin/DdNdkSymbolFileUploadTask.kt
77.63% <90.91%> (+2.63%)
:arrow_up:

... and 2 files with indirect coverage changes

authors: codecov-commenter fuzzybinary


text:
Pass consumer offsets into highwater offsets

What does this PR do?

Motivation

Additional Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached
[ ] If the PR doesn't need to be tested during QA, please add a qa/skip-qa label.

Current dependencies on/for this PR:

master

PR #13918

PR #14076

PR #14077   👈

PR #14078

PR #14079

This comment was auto-generated by Graphite.

repo: DataDog/integrations-core


text:
Update README.md to add GRANT for schema_size_metric

SDBM-1144
What does this PR do?

Adds a note concerning the schema_size_metrics option
Motivation

SDBM-1144
Additional Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[x] Changelog entries must be created for modifications to shipped code
[x] Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
[ ] If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

Thanks!
/merge


text:
Increase timeout of the tcp_check since it fail pretty often on travis

What does this PR do?
TCP tests are very flaky on the CI right now. Let experience with the timeout to see if travis speed might be one of the problems.

Not working


text:
[WIP] I also want to test benchmarks

What does this PR do?
A brief description of the change being made with this pull request.
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
How to test the change?
Describe here in detail how the change can be validated.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 73.02%. Comparing base (89f48d4) to head (63ccb02).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #637      +/-   ##
==========================================
- Coverage   73.05%   73.02%   -0.03%
==========================================
  Files         252      252
  Lines       36093    36076      -17
==========================================
- Hits        26366    26345      -21
- Misses       9727     9731       +4

Components
Coverage Δ

crashtracker
20.53% <ø> (ø)

datadog-alloc
98.73% <ø> (ø)

data-pipeline
90.12% <ø> (ø)

data-pipeline-ffi
0.00% <ø> (ø)

ddcommon
83.08% <ø> (ø)

ddcommon-ffi
69.52% <ø> (ø)

ddtelemetry
59.10% <ø> (ø)

ipc
83.63% <ø> (ø)

profiling
84.26% <ø> (ø)

profiling-ffi
77.42% <ø> (ø)

serverless
0.00% <ø> (ø)

sidecar
40.12% <ø> (ø)

sidecar-ffi
0.00% <ø> (ø)

spawn-worker
50.36% <ø> (ø)

tinybytes
91.66% <ø> (ø)

trace-mini-agent
72.49% <ø> (ø)

trace-normalization
98.25% <ø> (ø)

trace-obfuscation
95.73% <ø> (ø)

trace-protobuf
77.67% <ø> (ø)

trace-utils
93.30% <ø> (+0.41%)
:arrow_up:

authors: VianneyRuhlmann codecov-commenter

repo: DataDog/libdatadog


text:
Fails to find plasma-workspace .so files

yabi fails to find certain .so files of the installed package plasma-workspace
 🗸  Done
 ✗  Failed to find libraries:
 ✗     libkdeinit5_kcminit.so
 ✗     libkdeinit5_klipper.so
 ✗     libkfontinstui.so.5

https://dev.getsol.us/source/plasma-workspace/browse/master/pspec_x86_64.xml$62
we do have a special pattern for it inside the package.yml
https://dev.getsol.us/source/plasma-workspace/browse/master/package.yml$16

After a sec run only Klipper is left oO

It looks like libkdeinit5_kcminit.so and libkdeinit5_klipper.so are plugins, so it's only natural that they wouldn't have any matches for symbols. If libkfontinstui.so.5 is matching now, I don't think there's anything to broken here.

authors: DataDrake Girtablulu

repo: DataDrake/abi-wizard


text:
🛑 Gitlab is down

In fe6c6d3, Gitlab (https://gitlab.data-ensta.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Gitlab is back up in 2c65064 after 4 minutes.

repo: DataEnsta/upptime


text:
🛑 DaTA is down

In a7cbf35, DaTA (https://data-ensta.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: DaTA is back up in b71e12e after 10 minutes.


text:
Upgrade or replace the operating systems running the K8s controller VMs

docker-ucsb-4 and docker-dev-ucsb-1 are running on Ubuntu 18.04 and should be upgraded to a newer operating system.
The VMs may be deleted and replaced by a newer OS as part of the HA conversion (#1) and/or rename process (#38).

I upgraded both VMs to Ubuntu 22.04


text:
add possibility to specify width of collection menu + remove fixed width

Hi! Is there reason why the width of the collection menu is fixed to 150px? As long as you have column names smaller than 10 characters or so this is ok.
In case there IS any reason for 150px, I left it as a default value. But the user should be able to declare a width or just set it "auto".
Best regards,
Jakob

It is set to 150 just because it needed some value and that seemed a sensible default.
I've not added an option for it in Javascript because it can easily be done in CSS: ul.ColVis_collection { width: ...; }.

I understand. In my case it didn't work in the first try because I had loaded your CSS after my own. So I thought that the width is overwritten by your JS.
Still I think defaulting to "auto" would be just fine. Anyway nice library!

authors: DataTables haffla

repo: DataTables/ColVis


text:
footerCallback first argument is undefined

template:

JS:
build dt with data

The first argument of headerCallback() is the
 element inside the
. However, the first argument of footerCallback() is undefined.
If you add an empty

 into the

 then you get the
 element as the footerCallback() first argument.
The headerCallback provides the row element because it is built by DT and the columns dataset. However, in both cases this is incorrect.
Shouldn't both callbacks return the parent element
 and
 and not the
 element it contains as the docs mention?
https://datatables.net/reference/option/headerCallback
https://datatables.net/reference/option/footerCallback

I fear that's going to be a double bug. Yes I agree, it should return the containing element, but given that its probably always been that way for the 1.x series that's not something that I can really change now lest it break loads of code that relies upon that.
The correct thing to do is probably to change the documentation to reflect the current behaviour and then for v2 introduce new events which do give the containing elements.
Thanks for flagging this up.

👍 sounds good :)

authors: DataTables smasala

repo: DataTables/DataTables


text:
Update quick_inference_script to reflect minimal example in CAM

Update quick_inference_script to reflect minimal working example in CAM.
That is, we want the following structure:
single set of inputs (i.e., one time step) -> run inference -> gather output into format required for CAM

@TomMelt so do I need to update the MWE code on my end now? and (say) change it to a callable function which takes the dynamical variables as input and pops out the predicted fluxes?

Ack, sorry, ignore my previous comment. I get now that the answer to my question is Yes.


text:
mysql 0.4.1 throws exception

With the database_cleaner 1.5.1 and mysql 0.4.1 I get the following exception:
 Specified 'mysql2' for database adapter, but the gem is not loaded. Add `gem 'mysql2'` to your Gemfile (and ensure its version is at the minimum required by ActiveRecord). (Gem::LoadError)

I think this issue may not caused by database_cleaner, it's caused by the mysql2 version you're using.
See: https://github.com/rails/rails/issues/21544

You are right. Thank you.

:smile:


text:
Add Serial Ports explorer view and context menus

For better look and feel integration with MPRemote and more pleasing user interaction.

Closed with https://github.com/DavesCodeMusings/esptool-vscode/commit/830f3a67eb6d112562641e30556c59d5e962c2e0

repo: DavesCodeMusings/esptool-vscode


text:
Garbage in release files.

There are unnecessary files and folders in the downloaded version of the module:
..git*
._MACOSX*
..DS_Store

I know.  is it causing problems?    It's easiest for me to just zip the
directory I use to actually test or else then I'll need to test twice.
On Thu, Jul 15, 2021 at 5:46 PM kimitsu @.***> wrote:

There are unnecessary files and folders in the downloaded version of the
module:
..git*
._MACOSX*
..DS_Store
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/David-Zvekic/TokensVisible/issues/22, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH3YQQWQBYSPS7WF2ICMLTLTX5JL7ANCNFSM5AOMCCEA
.

.git is problematic in particular since it may conflict with other repositories. For exxample I keep my whole modules folder as a local repository to keep track of local changes.

I'll figure out something out for future versions. I just needed to know
someone is actually benefiting from this.
On Mon, Jul 19, 2021 at 5:25 AM kimitsu @.***> wrote:

.git is problematic in particular since it may conflict with other
repositories. For exxample I keep my whole modules folder as a local
repository to keep track of local changes.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/David-Zvekic/TokensVisible/issues/22#issuecomment-882395656,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH3YQQUIYSAES6RGW3IKYI3TYPVRFANCNFSM5AOMCCEA
.

2.5.4 and beyond should no longer have the extra files in them

authors: David-Zvekic kimitsu

repo: David-Zvekic/TokensVisible