text:
BIG: Breaking everything into smaller repos

What are we doing?
Currently, the Rover Team's repository is really... scary. Frankly, I'm not too sure how everyone got so much work done with this level of organization. Anyways, the plan is to fix the problems by organizing all of the different subdirectories that are sitting in this one repo. As needed, they will all become separate GitHub repos on the Sooner Rover Team org.
How are we splitting everything up?
I'm deciding a rough draft below. You can use the command tree to easily look at the file structures. Use tree -d to see only directories (folders). When I see patterns of grouped utilities that are developed together, they'll stay as a group. Otherwise, they're getting stored or archived.
How will it look?
Each of the listed items below will become their own split-off repo and project. The (/foo) represents its current location in the giant repo. There don't need to be any active maintainers, since our "human resources" are limited. That said, if something needs to be archived, let me know.  Also, this link on moving files between repos while preserving commit history will be very useful!
Anyways, I plan to have it look something like this:
Arduino
(/Arduino/)
This was a pretty easy split. This folder contains various Arduino files, all of which are related. Here's a folder listing:
Arduino/
├── arm_controller
├── arm_test
├── capstone_arm
│   ├── control_arm
│   ├── rover_arm
│   ├── rover_arm_pid_test
│   └── rover_arm_test
├── drill_controller
├── drill_test
├── servo_test
└── wheel_controller

YOLO/darknet
(/Autonomous/YOLO/darknet/)
This is a sizeable library whose source is just sitting in the middle of everything. It really needs its own repo. Here's a folder listing:
Autonomous/
├── YOLO
│   └── darknet
│       ├── 3rdparty
│       │   ├── pthreads
│       │   │   └── include
│       │   └── stb
│       │       └── include
│       ├── cfg
│       ├── cmake
│       │   └── Modules
│       ├── data
│       │   └── soro
│       ├── include
│       ├── scripts
│       │   ├── log_parser
│       │   └── windows
│       └── src
│           └── csharp
├── artags
│   └── old
│       └── PrintARTags
├── examples
├── gps
└── libs

MBED
(/MBED/)
MBED is a mixed bag for me. It includes many small projects that have connected goals. For this reason, I'm not sure if I want to put each project in its own repo, do that but with submodules, or just keep everything together. For now, I'll just say it belongs together. Here's a listing (it's so small that you can put files too):
MBED
├── EBoxMBED
│   └── main.cpp
├── README.md
├── SPItoCANRead
│   └── main.cpp
├── SPItoCANSend
│   └── main.cpp
├── UDPSocket
│   └── main.cpp
└── WheelMBED
    └── main.cpp

RoverMap
(/Mission Control/RoverMap/)
To be honest, even after studying the README, I'm not sure if these are two separate projects (frontend and backend) or if they both require each other. For now, let's keep them together. Here's a directory listing:
RoverMap/
├── RoverMapTileGenerator
├── example
└── frontend
    └── leaflet
        └── images

(frontend is a whole web interface. but it's a lil guy)
python_drive
(/Mission Control/python_drive/)
This project is completely distinct from the rest of everything. It controls the vehicle! Here's a short file listing:
python_drive/
├── README.md
├── config.ini
├── controllertester.py
├── manual_operate.py
└── util.py

video_streamer
(/Mission Control/video_streamer/)
The video_streamer project has a lot of documentation! I think it would be well off in its own repo, along with a detailed INSTALLATION.md and reduced README.md. Here's a file listing:
video_streamer/
├── README.md
├── client.py
├── config.ini
├── static
│   └── logo.png
├── templates
│   └── index.html
├── utils.py
└── videostream.py

TO ARCHIVE

udp_mc_drill and udp_mc_drive (/Mission Control/udp_mc_dr***)

According to the Mission Control README, both of these are useless and have been replaced with a modern Python script.
It's sad to get rid of the only Rust projects, but necessary :(

And..?
With that, we're done! All of the files in the Sooner Rover Team's modern repo have been accounted for! I think it would be also wise to make a Junkyard repo that acts as a place to store archived projects that are pretty old/small. If you have any suggestions or changes I should make, please let me know!
Complete

[ ] Arduino
[ ] darknet
[ ] MBED
[ ] RoverMap
[ ] python_drive
[ ] video_streamer
[ ] Graveyard

[ ] udp_mc_drill
[ ] udp_mc_drive
[x] my rusty dreams :(

I like the breakdown for the most part. A few things can be moved around even more such as capstone_arm which hasn't been used in years and can go into the graveyard. Also we'll still need a repo for the autonomous code itself (stuff in gps, libs, and examples).

The arm capstone is current though… Christine WealeSenior, El.Eng. Junior, OUVP of Service, Alpha Phi OmegaUG Research Asst. | RIL From: Benton SmithSent: Friday, January 27, 2023 12:47To: Sooner-Rover-Team/SoonerRoverTeamVCc: SubscribedSubject: Re: [Sooner-Rover-Team/SoonerRoverTeamV] BIG: Breaking everything into smaller repos (Issue #32) I like the breakdown for the most part. A few things can be moved around even more such as capstone_arm which hasn't been used in years and can go into the graveyard. Also we'll still need a repo for the autonomous code itself (stuff in gps, libs, and examples).—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

As far as I can tell, all of the code in that folder is from the OLD arm capstone from 4-5 years ago. I'm not sure if any of it applies since that one worked very differently to the arm that we currently use on the rover.

Is graveyarding this the consensus? I'm happy to start working on moving everything, and of course, we can always revert and move the capstone_arm project somewhere else if it's deemed necessary.

Yeah, I like the idea of just throwing everything obsolete in a repo by itself so it's not in the way of the useful stuff but we have access to it if we need it.

For the Autonomous Folder, I would say that you could move the YOLO folder into a sub-repo. Other than that, I give it a green light.

dont touch til march 4th :)

Note: MBED was dissolved into Microcontrollers with fd11b43. Arduino was also moved.
In the future, please explicitly commit for moves like this - it's hard to keep track! Squash merges are a little scary ;)

Also moved:

[x] Discord Bot
[x] PCB

This seems to be a CAD backup repo. GitHub doesn't like that, and git isn't designed for it. It's best to remove this repo ASAP!

I now need to apply the MIT license to each of the moved repos. Let's keep track:

[ ] pcb
[ ] discord_bot
[ ] Autonomous
[ ] gps
[ ] rovercam-python
[ ] python_drive
[ ] RoverMap
[ ] YOLO (wish we'd have kept it WTFPL ;) )
[ ] Microcontrollers
[ ] soro-documentation

repo: Sooner-Rover-Team/SoonerRoverTeamV


text:
时间轴加载异常，设置按钮不再可见

您好！首先感谢您的付出！
发现时间: 2024/11/21 21:00
问题描述:时间轴无法正常加载，设置按钮不可见
排查过程:
21:00，我与朋友们（大约4人）都发现时间轴界面无法正常加载，在【刷新悬浮窗】后1人恢复可以看到时间轴但无法看到设置按钮，其余3人未恢复，我显示【已加载0条时间轴】
我尝试将URL从
https://souma.diemoe.net/#/timeline
改为
https://souma.diemoe.net/ff14-overlay-vue/#/timeline
再次尝试刷新悬浮窗后，显示【已加载22条时间轴】，显示恢复正常，但仍然看不到设置按钮

上图为解锁悬浮窗后，可以看到紫色的可移动界面，但无法在此看到设置用的紫色齿轮
我于11月20日晚11点使用确认此组件正常运作

我尝试过开关翻墙VPN，对此问题无改善

你好，我决定删除此按钮，改用只用浏览器进行交互。
请使用浏览器访问此地址：https://souma.diemoe.net/ff14-overlay-vue/#/timelineSettings?OVERLAY_WS=ws://127.0.0.1:10501/ws

个人通过浏览器交互的情况反馈~
分别使用呆萌和咖啡，在同一网络下开梯子和不开梯子的情况下测试，呆萌均可顺利访问网址并进行交互，但咖啡均未成功，停留在获取ACT数据阶段。

收到！

个人通过浏览器交互的情况反馈~ 分别使用呆萌和咖啡，在同一网络下开梯子和不开梯子的情况下测试，呆萌均可顺利访问网址并进行交互，但咖啡均未成功，停留在获取ACT数据阶段。

咖啡是否启用了ACT WS SERVER呢，并且如果你2个ACT一起开，端口是会冲突的。

抱歉我可能还需要请求一些帮助，我在启动ACT WS SERVER后，我的时间轴数量变为0了……
我眼下没有最近的备份文件，您有什么好的建议吗，感谢

我有备份过一个完整的ACT客户端，那个客户端里还保存着我以前的所有内容，但现在没有设置按钮……我不知道如何导出我以前的数据了

抱歉我可能还需要请求一些帮助，我在启动ACT WS SERVER后，我的时间轴数量变为0了…… 我眼下没有最近的备份文件，您有什么好的建议吗，感谢

嗯？？我在代码上已经尽量规避了用户设置被清空的惨剧，应该不会发生才对。。。

我也希望这不会发生……但很遗憾……

我也希望这不会发生……但很遗憾……

是设置页面显示0，并且时间轴里面也显示是0了吗！？

是的……如果是导入的轴倒是无所谓，但我有一些手工制作的轴……

我有备份过一个完整的ACT客户端，那个客户端里还保存着我以前的所有内容，但现在没有设置按钮……我不知道如何导出我以前的数据了

你先别急，可以恢复
用你以前的ACT：

非常抱歉出现这种情况，我会重新审视代码的实现

您无需道歉，毕竟能用到这东西已经非常棒了，我按照图中想想办法！

非常奇怪，我确信我在今晚曾经用其它url刷出过22条数据，我会再尝试几次

你关掉设置页面了吗？

是的，因为在关掉前我看到时间轴栏位显示了绿色的，类似保存成功语义的字样，但抱歉我没太记住具体写的什么

哦，已更新数据

首先使得你在悬浮窗中可以看到有22条时间轴。
然后在点击devTool时，你需要切换到时间轴那个标签，在他里面点开才有，因为数据是分域名保存的。

从现在开始设置页面必须手动点击按钮，才会进行数据传递了。
同时悬浮窗本体在接受数据时也会进行检查，当有删除操作时，必须手动确认才可以接受数据。
由于cdn的存在，改动会在大约30分钟后生效。

理解了，我要尝试寻找那22条时间轴……但我估计有些困难了，毕竟现在已经归0，我会尝试重试几次，实在不行就再弄一遍嘛没啥大事，以后能确保安全就好，辛苦您啦！

斯米马赛，感谢你

啊抱歉还得打扰下，我有了一个新的进展：我找到旧的ACT里的字符串了！非常棒！
可惜我将它复制出来后，在新版本中导入失败，报错为
TypeError: Spread syntax requires ...iterable[Symbol.iterator] to be a function
您是否需要我提供整体字符串文件给您呢

哦太棒了！非常感谢您，我自己搞定了
我看到有些部分似乎是描述时间轴风格的，所以我把jsonArray取了出来，它生效了！
我现在没有任何问题了，非常感谢您的协助！

啊抱歉还得打扰下，我有了一个新的进展：我找到旧的ACT里的字符串了！非常棒！
可惜我将它复制出来后，在新版本中导入失败，报错为
TypeError: Spread syntax requires ...iterable[Symbol.iterator] to be a function
您是否需要我提供整体字符串文件给您呢

我知道你解决了哦。
这里贴一下怎么替换，以便以后有人看到这个问题不知道该怎么办：拿到的字符串不可以直接在UI里导入，也应该跟拿到的时候一样，通过DEVTOOLS的存储-本地存储，找到key为timelines的值，把新的字符串手动粘进去。

是的，非常感谢您的协助，不过我不得不在最后提出一个小问题……
经过我3次重启电脑、act、浏览器之后，我确信【导出全部】按钮并没有生效，我认为这可能是因为我有相当多很长的（绝本）时间轴，因为在点击几次按钮后，页面显示了内存不足
恕我直言，我觉得导出到剪贴板里可能不完全是个好主意……

我不是大佬……咱们都是开发者嘛，而且实话说……我并不擅长前端开发，非常遗憾
如果是在后端开发中，重一点的我会使用缓存框架来尝试解决问题，轻一点的方式下……也许直接写文件会不会好一些？
因为在写文件的过程中，可以将多个json分步写到文件里，类似于seek那种实现。或者干脆写多个文件让玩家自行每个单独导入。这样的好处是一次只加载一条时间轴就可以了
毕竟作为用户来说，其实时间轴的风格这是几分钟就可以弄好的事情，只要轴本身没丢，一切就都好办

就好比我刚才传输的文件……它有203kb（其实这也不大啊……），日后成长到它的3-5倍大是肯定的

顺便提个小建议……我不知道js正则是不是有什么不同，但标准正则在跳转表达式中经常失效……

诚然这是我自己的问题……也许该找机会学学前端了……

加入了一些压缩导出体积的办法，（在cdn缓存更新之后）你可以尝试一下是否还会卡死

个人通过浏览器交互的情况反馈~ 分别使用呆萌和咖啡，在同一网络下开梯子和不开梯子的情况下测试，呆萌均可顺利访问网址并进行交互，但咖啡均未成功，停留在获取ACT数据阶段。

咖啡是否启用了ACT WS SERVER呢，并且如果你2个ACT一起开，端口是会冲突的。 并且ACT的悬浮窗里，要有timeline的本体并且启用了，才能通信成功。

俺又重新试了下！都启用了ACT WS SERVER打开timeline，然后咖啡和呆萌分别开和不开梯子测试4次，每次都重启电脑，还是呆萌OK但是咖啡不可以，一直是“正在请求数据，请确保ACT与时间轴悬浮窗已开启...，若 3 秒内仍未获取到数据，请检查ACT状态，且确认 timeline 悬浮窗已开启”的状态，在NGA看到帖子好像也有相同情况的好兄弟

俺又重新试了下！都启用了ACT WS SERVER打开timeline，然后咖啡和呆萌分别开和不开梯子测试4次，每次都重启电脑，还是呆萌OK但是咖啡不可以，一直是“正在请求数据，请确保ACT与时间轴悬浮窗已开启...，若 3 秒内仍未获取到数据，请检查ACT状态，且确认 timeline 悬浮窗已开启”的状态，在NGA看到帖子好像也有相同情况的好兄弟

我这里暂时无法复现你的问题，使用咖啡ACT、呆萌ACT都可以正常连接
另外测试时，不需要重启电脑。

俺又重新试了下！都启用了ACT WS SERVER打开timeline，然后咖啡和呆萌分别开和不开梯子测试4次，每次都重启电脑，还是呆萌OK但是咖啡不可以，一直是“正在请求数据，请确保ACT与时间轴悬浮窗已开启...，若 3 秒内仍未获取到数据，请检查ACT状态，且确认 timeline 悬浮窗已开启”的状态，在NGA看到帖子好像也有相同情况的好兄弟

我这里暂时无法复现你的问题，使用咖啡ACT、呆萌ACT都可以正常连接 另外测试时，不需要重启电脑。

嘿嘿问题不大！先用呆萌，感谢大佬！

导出测试可用，现在不存在任何问题了，我准备关闭此issues，感谢您的支持！

source: gharchive/issue

authors: Lynchlily SitaNya Souma-Sumire

license: MIT

license_type: permissive

license_source: github-api


text:
🛑 Marcel Web is down

In 3bd9f81, Marcel Web ($MARCEL_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Marcel Web is back up in 3de9bc7 after 1 hour, 13 minutes.

repo: Source-Graphics-GmbH/upptime


text:
Refactor Build Network tool to incorporate error finding, multiple tabs

The Build Network tool needs to be refactored so that there are multiple tabs, instead of individual tools/icons, etc.
Tab 1 : Find Subnetworks
Tab 2: Find Network Errors
Tab 3: Generate Network Attributes

I've decided to have separate tools instead of one tool with multiple tabs. So instead of a Build Network tool with three tabs, there will be two separate tools:

Find Subnetworks
Generate Network Attributes

repo: SouthForkResearch/pyGNAT


text:
Write slot as atomic batch

Description
This commit updates the ledger DB so that all components of a slot are written as batch. This should both improve efficiency and eliminate some potential concurrency bugs.
Linked Issues

Related to #417

Testing
Existing unit tests pass. cc @theochap @citizen-stig - let's see if we can reproduce the issue from #417 after this change or not

@preston-evans98 Do we have a test in main or this branch which has failing case? Otherwise we are blind.
Maybe this PR should be opened against #403, and merged there first?

source: gharchive/pull-request

repo: Sovereign-Labs/sovereign-sdk


text:
Can't dismiss the notificaton saying "Join A Meter Group"

The notification to use command to join a meter group doesn't want to disappear no matter what I do when trying to join group named with my nick, if I already was in that group. It even stays floating on other screens.

I'm using it on 1.18.2 for now on version 1.11.0 of the mod.
@EDIT
When trying to join existing meter group (named after my nick) the tutorial step didn't activate. Only when I joined new meter group the step completed.

I suppose there's two different bugs here.

The tutorial step only checks if you successfully joined a meter group, rather than if you used the appropriate command.
The toast isn't hidden when you open the menu.

Issue 1. is fixed, issue 2. appears to be an issue with all toasts, not just RSMM's toasts, so I won't consider it an RSMM bug. I'll release v1.11.1 with the fix shortly!


text:
Add spell checking toggle

WebCord uses the default chromium/electron spell checker which can be disabled in normal discord and in chromium by just right clicking on the message box. WebCord currently does not have the ability to disable the spell checker

Another related question is how to enable spell checking for other languages, not English only.

My temporary solution is put this line of code on line 371
mainWindow.webContents.session.setSpellCheckerEnabled(false);

Another workaround is edit /home/pablo/.config/WebCord/Preferences
with something like
{"electron":{"media":{"device_id_salt":"A267D7E33C450DD743629AF815A81DFB"}},"spellcheck":{"dictionaries":["es-ES"],"dictionary":""}}
(for Spanish (es-ES) in this case)

Another workaround is edit /home/pablo/.config/WebCord/Preferences with something like {"electron":{"media":{"device_id_salt":"A267D7E33C450DD743629AF815A81DFB"}},"spellcheck":{"dictionaries":["es-ES"],"dictionary":""}} (for Spanish (es-ES) in this case)

You can also set "spellcheck":false to disable spellchecking entirely.
I still prefer a toggle, but this is the best workaround.

I'd love to see a way to enable/disable spellchecking for multiple languages get implemented. Many users such as myself are bilingual and Electron only seems to enable spell checking of system language by default.

authors: 99linesofcode AlexeyShaferov FelixFourcolor K4zoku Potajito dolwup


text:
fix(ffe-buttons-react): fix InlineExpandButton types

Det er ikke mulig å sette type="button" på InlineExpandButton, så den ender opp med å få default type="submit". Når den brukes i et form vil dermed Enter-tasten på tastaturet fyre av denne knappen. For å unngå det trenger man å kunne sette type selv :ok_hand:

Jeg synes InlineExpandButton burde aldri ha type=submit og isteden burde denne knapp ha type=button per default.

Godt poeng, jeg kan si meg enig i den. Jeg la til 629b66f174023e73e8bc0580ab14e6497de82418 som fikser det. Det kan gjøres i samme commit, men det er strengt tatt to forskjellige ting. Så lenge commitsene her ikke squashes ved merge funker det vel å ha det i samme PR?

Å ha det i én PR er kosher så lenge det er to commits. Men trenger vi den endring i types-definisjonen?

Vi trenger det ikke for å sette type="button" by default, men for at brukeren av komponenten kan sette klassiske html-attributter som uansett spreades ned til html-elementet (slik som feks hvis vi vil override type) må vi endre typinga. Jeg mener det er riktig å også endre types-definisjonen siden det jo tross alt er/skal være mulig å sette hvilke som helst standard html-attributter på elementet.

Om man rebaser denne PR så burde travis bli grønt.

Coverage remained the same at 84.797% when pulling 0a02a575790fed4fa178a5f3379d31c5ed7dcddc on fix-inline-expand-button-types into 5f8e3ef3d6072508ebcfd101e0eaa322b2a3fd9b on develop.

authors: coveralls kwltrs torkjels


text:
🛑 Yiffed Main is down

In ccfe145, Yiffed Main (https://yiffed.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Yiffed Main is back up in 84204b5 after 24 minutes.

repo: SparksTheFolf/STF-Uptime-Status


text:
Go Linting Errors

Changelog

Fixes the Go Linting Errors found in the report

Codecov Report

Merging #38 into main will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #38   +/-   ##
=======================================
  Coverage   81.81%   81.81%
=======================================
  Files           9        9
  Lines         308      308
=======================================
  Hits          252      252
  Misses         41       41
  Partials       15       15

Flag
Coverage Δ

#unittests
81.81% <ø> (ø)

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

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update aa043e4...6720a97. Read the comment docs.


text:
Key hub updates and updates to updated_by/at handling for keys

There are two issues resolved here:

3884, show updated-by and -at for the whole key, not just the root node
The last two TODOs from @mjy on the keys hub: move Is Public to the last column and display number of otus in the key. Given work done for the updated_ issues I was able to add the otus count on load instead of only after actually loading/displaying all of the otus (which is why the two issues are being submitted together).

It took me some time to figure out some technical issues concerning the new query for root leads - see the commit message on the next to last commit (feel free to skip if it's all old news).
In short, the issue is that the query is a .joins. A simplified example is q = T.joins('JOIN U on T.id = U.id).select('U.*'). This is a contrived example, but two of the issues with this query are that, even though you selected the U side:

If you do q.order(:text) where both T and U have a text column, you get ordered by T.text, not U.text
If you do q.pluck(:text) you get texts from the T side of the relation, not the U side.
There are ways to call both order and pluck to get what you want, but it requires knowledge of how the query was created and (in my case) the alias used for the second table U. if you return this query from a function, users will have no idea of the issue. That's the current state of these commits. I'm not sure if this is a common kind of issue, or if there's a standard way to fix it, or if it's just the way it is. Thanks for taking a look!

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

Project coverage is 58.24%. Comparing base (0a0f093) to head (34ec776).
Report is 2 commits behind head on development.

:exclamation: Current head 34ec776 differs from pull request most recent head fbd1aa1. Consider uploading reports for the commit fbd1aa1 to get more accurate results

Files
Patch %
Lines

app/controllers/leads_controller.rb
0.00%
12 Missing :warning:

app/models/lead.rb
25.00%
3 Missing :warning:

app/helpers/leads_helper.rb
50.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@               Coverage Diff                @@
##           development    #3899       +/-   ##
================================================
- Coverage        84.35%   58.24%   -26.11%
================================================
  Files             2130     1645      -485
  Lines            79480    52027    -27453
================================================
- Hits             67046    30305    -36741
- Misses           12434    21722     +9288

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

authors: codecov-commenter kleintom

repo: SpeciesFileGroup/taxonworks


text:
New Mounts

// NEW
mount_0x5e6 i_mt_coconut_crab_mount
mount_0x5f6 i_mt_war_boar_mount
mount_0x5f7 i_mt_capybara_mount
mount_0x60a i_mt_newfoundland_mount
mount_0x60b i_mt_malamut_mount
mount_0x60c i_mt_bane_mount
mount_0x60d i_mt_bernard_mount
mount_0x60f i_mt_terier_mount
mount_0x610 i_mt_rottweiler_mount

[ITEMDEF i_mt_coconut_crab_mount]
ID=03ed1
TYPE=t_eq_horse
LAYER=layer_horse
TDATA3=c_coconut_crab_mount
WEIGHT=0
[ITEMDEF i_mt_war_boar_mount]
ID=03ed2
TYPE=t_eq_horse
LAYER=layer_horse
TDATA3=c_war_boar_mount
WEIGHT=0
[ITEMDEF i_mt_capybara_mount]
ID=03ed3
TYPE=t_eq_horse
LAYER=layer_horse
TDATA3=c_capybara_mount
WEIGHT=0
[ITEMDEF i_mt_newfoundland_mount]
ID=03ed4
TYPE=t_eq_horse
LAYER=layer_horse
TDATA3=c_dog_newfoundland
WEIGHT=0
[ITEMDEF i_mt_malamut_mount]
ID=03ed5
TYPE=t_eq_horse
LAYER=layer_horse
TDATA3=c_dog_malamut
WEIGHT=0
[ITEMDEF i_mt_bane_mount]
ID=03ed6
TYPE=t_eq_horse
LAYER=layer_horse
TDATA3=c_dog_dane
WEIGHT=0
[ITEMDEF i_mt_bernard_mount]
ID=03ed7 // to make it work need to edit tiledata anim and define item in scps
TYPE=t_eq_horse
LAYER=layer_horse
TDATA3=c_dog_bernard
WEIGHT=0
[ITEMDEF i_mt_terier_mount]
ID=03ed8
TYPE=t_eq_horse
LAYER=layer_horse
TDATA3=c_dog_terier
WEIGHT=0
[ITEMDEF i_mt_rottweiler_mount]
ID=03ed9
TYPE=t_eq_horse
LAYER=layer_horse
TDATA3=c_dog_rottweiler
WEIGHT=0

Here are the scripts, also with some new monsters that were there too.
NOTE: THE SCRIPTS ARE NOT EDITED YET SO ITS ONLY TO SHOW THE ID ETC...
https://pastebin.com/WZSqxjCY

And item: https://pastebin.com/bfxT0KbC

repo: Sphereserver/Scripts-X


text:
Added PATCH support

Adds PATCH support for IIS - relates to #1107

This is very interesting - for my own edification - where is the PATCH method used?

From RFC5789
"The existing HTTP PUT method only allows a complete replacement of a document.This proposal adds a new HTTP method, PATCH, to modify an existing HTTP resource."

This is interesting - i've seen the RFC - does anything use this? Just so we can test it :-P

We have tested this with part of our payments solution but the PATCH methods are not publicly accessible for 3rd party testing.
I guess you could test against any resource on an IIS server - without the fix if you have "detection mode = on" it will record "Guid_0.00" errors if it does not work.

Relevant documentation:

HTTP_REQUEST - https://msdn.microsoft.com/en-us/library/windows/desktop/aa364545(v=vs.85).aspx
HTTP_REQUEST_V1 - https://technet.microsoft.com/pt-br/aa364612(v=vs.71)
HTTP_REQUEST_V2 - https://msdn.microsoft.com/en-us/library/windows/desktop/aa364613(v=vs.85).aspx

@csanders-git The standard methods (GET, POST, PUT, PATCH, DELETE) are widely used in REST API interfaces, so having support to inspect those would be really helpful.

@Almamu - any idea of some examples that might be around?

@csanders-git I don't have any publicly accesible example as I've always worked on REST API for private systems, but searching about API REST in google gives a handful of results of how it should be implemented and documentation that specifies how the standar HTTP verbs are used in it and what they mean, although there is no RFC for REST API (as long as I recall).

So it looks like there's still not that many apps using PATCH these days. I could only find a few APIs to test (which were easy to deploy on Apache/Nginx, but a pain to get it working under IIS). Maybe someone could give us a hand in that direction... :)
That said, by doing some trickery with IIS WebDAV module I could run a few tests with CRS and some custom rules. As PATCH is not explicitly added to the main code base of ModSecurity looks like you can't use REQUEST_METHOD or REQUEST_LINE variables straightforward to match with PATCH requests. But It looks like you can still match stuff with ARGS, REQUEST_LINE or FULL_REQUEST variables.
On all my testes I couldn't spot any error related to "Guid_0.00" as mentioned but I'm really not familiar with this error message. It looks like that this issue could be related with PCRE limits parsing large bodies and / or XML but this is only a guess at this point.
@culyerr @Almamu maybe if you could share the rules you have loaded, some debug logs and ideally a HTTP PATCH request which triggers this issue would be great.
What I'm trying to understand is if this pull request is actually to fix a bug specific for ModSecurity on IIS or to add a functionality (PATCH verb support) =)

Closing this pull request, I will merge it once I find myself the manners to test it.

authors: Almamu csanders-git culyerr victorhora zimmerle

repo: SpiderLabs/ModSecurity

license_source: bigquery


text:
Add correct C function prototypes for msc_init and msc_create_rule_set

C function prototypes require a void parameter otherwise the error: function declaration isn't a prototype will be thrown in some compilers with -Werror=strict-prototype set.

Merged at https://github.com/SpiderLabs/ModSecurity/commit/004047ef6cee4ee5eca05648d55ca500d9ebe23a.

authors: steven-j-wojcik victorhora


text:
Update : 23/03/2021

Modifications de la decklist Grenzo:
Cuts:

Snuff Out
Unclaimed territory
Graven Cairns
Ins:
Chain Lightning
Mountain x2

The lists in the Codex are not meant to be up-to-date and may need revision from time to time.
I do not think it would be wise to log every update but maybe check the lists once per banlist?
All in all, I will wait for the next banlist and the possible new changes you'll do before accepting this PR

Ok!

authors: NotEjell Spigushe

repo: Spigushe/barrins-codex


text:
numbersetting not working

instead of using number setting use slidersetting

Have not implemented the number settings into the GUI yet, I am trying to decide whether I should make it with a slider or by typing in a value since I am anyway going to have to implement that logic in for the keybind setting so I can be done with the GUI (for now at least)

instead of using number setting use slidersetting

I see you made a fork trying to implement a slider, you can make a pull request if you want so I can add your changes.

Fixed number setting


text:
Implement DataSerializable for ServerLocation

SpongeAPI | Sponge

8bf35817def81dabb85f0c6c078795d54d820221

authors: ItsDoot dualspiral

repo: SpongePowered/Sponge


text:
🛑 [A] IP Ending with .116 is down

In f945bab, [A] IP Ending with .116 ($IP_GRP_A.116:$MONITORING_PORT) was down:

HTTP code: 0
Response time: 0 ms

Resolved: [A] IP Ending with .116 is back up in 78a45fc after 22 minutes.


text:
CSS Animated Button Hover_Effect

This is a(n):

[ ] Update to an existing Animated Button
[ ] Any Error
[x] Proposal to the Repository
[ ] Documentation / README.md changes

Details:
"Hi, I am a contributor in GSSOC'23, and I would like to add a new CSS animated button with a hover effect to this project. I will create an animated button that features a star sparkle effect when clicked, along with a gradient background. The button will also undergo transformations in scale and color when hovered over.
This button will create the illusion of a sparkling space when clicked, and it will perform a star animation upon hover to reveal the content on the other side. This type of button can significantly enhance the interactivity and visual appeal of your project.
I kindly request to assign me this task under label gssoc'23.

Please check #1346

Sorry for the inconvinience, but we are closing all the issues! Please open a new issue if you want to contribute anything. Also now you can create a new button from the website itself! You will get points for those too! I will add the instructions on how to create a new button soon and create an empty pr for the same to get points!


text:
Change the generated code to back and make it copyable or add a copy and paste button

add a copy and paste generated code button and change the generated code colour to white

i added copy button :)

repo: SquareScreamYT/sandboxels-mod-maker


text:
Lost data when restarting?

Hi
I've been using this docker compose file:
version: '2.1'
services:
  squidex_mongo:
    image: mongo:latest
    ports:
      - "27017:27017"
    volumes:
      - /etc/squidex/mongo/db:/data/db
    networks:
      - internal
    restart: unless-stopped

  squidex_squidex:
    image: "squidex/squidex:v1.3.1"
    ports:
      - "80:80"
    environment:
      - URLS__BASEURL=${SQUIDEX_PROTOCOL}://${SQUIDEX_DOMAIN}/
      - URLS__ENFORCEHTTPS=${SQUIDEX_FORCE_HTTPS}
      - EVENTSTORE__CONSUME=true
      - EVENTSTORE__MONGODB__CONFIGURATION=mongodb://squidex_mongo
      - STORE__MONGODB__CONFIGURATION=mongodb://squidex_mongo
      - IDENTITY__ADMINEMAIL=${SQUIDEX_ADMINEMAIL}
      - IDENTITY__ADMINPASSWORD=${SQUIDEX_ADMINPASSWORD}
      - IDENTITY__GITHUBCLIENT=${SQUIDEX_GITHUBCLIENT}
      - IDENTITY__GITHUBSECRET=${SQUIDEX_GITHUBSECRET}
      - IDENTITY__GOOGLECLIENT=${SQUIDEX_GOOGLECLIENT}
      - IDENTITY__GOOGLESECRET=${SQUIDEX_GOOGLESECRET}
      - IDENTITY__MICROSOFTCLIENT=${SQUIDEX_MICROSOFTCLIENT}
      - IDENTITY__MICROSOFTSECRET=${SQUIDEX_MICROSOFTSECRET}
      - LETSENCRYPT_HOST=${SQUIDEX_DOMAIN}
      - LETSENCRYPT_EMAIL=${SQUIDEX_ADMINEMAIL}
    depends_on:
      - squidex_mongo
    volumes:
      - /etc/squidex/assets:/app/Assets
    networks:
      - internal
    restart: unless-stopped

networks:
  internal:
    driver: bridge

However, I've recently restarted my server and lost all database records. It's as if it just recreated everything. Is there a way I can recover this?

No, sorry. To be on the safe side I would map the MongoDB storage folder to the host system.

Look at the docker-compose file. I am mapping it to the host system. That’s what is so weird.

Only the assets.

Is it the correct path?

Yes it is. When I navigate to the folder it’s full of mongodb files. Now they all have todays timestamp as they have been recreated.

strange

Seems like it didn't happen during restart. Something is corrupting the database. From one day to the other I couldn't login anymore. I restarted the squidex/squidex:v1.3.1 container and could login again, all data is gone tho, again... Not sure wether this is a squidex, squidex-docker or mongo issue though.

It has never happened to me. You can check the logs with docker logs container_id or install portainer. Have you checked the data with a mongo UI, e.g. studio 3t,?

Issue was due to port being exposed in the docker-compose files and my firewall not blocking it so my test database was compromised. I made a pull request with a fix to not expose the port any longer.

Have you had a collection there with a document: "Pay to get your data back"?

Yes I did. Why? Not gonna pay them, had backups.

Was just curious. Happened to me as well some years ago, but it was a test environment.

authors: LodeKennes SebastianStehle

repo: Squidex/squidex-docker


text:
Improve UI for dark mode

I want to improve the UI of all calculator pages in dark mode

@ArpitaSaga Go for it.

authors: ArpitaSaga Srijita-Mandal

repo: Srijita-Mandal/fix-your-nums


text:
🛑 Star Citizen Wiki API is down

In 42e440a, Star Citizen Wiki API (https://api.star-citizen.wiki) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Star Citizen Wiki API is back up in 677a00b after 2 minutes.

repo: StarCitizenWiki/status


text:
[Feature] Implement HiveMetastoreOperations

What type of PR is this：

[ ] BugFix
[x] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
https://github.com/StarRocks/starrocks/issues/11349
Problem Summary(Required) ：

HiveMetastoreOperations is the query-level instance.
It include query-level's CachingHiveMetastore instance and use it to get hive metastore metadata.
It will only get present partition statistics in cache to prevent the timeout of cbo.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

run starrocks_fe_unittest

run starrocks_fe_unittest

[FE PR Coverage Check]
:heart_eyes: pass : 39 / 40 (97.50%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/external/hive/CachingHiveMetastore.java
1
2
50.00%
[249]

:large_blue_circle:
com/starrocks/external/hive/HiveMetastoreOperations.java
32
32
100.00%
[]

:large_blue_circle:
com/starrocks/external/Utils.java
6
6
100.00%
[]

authors: stephen-shelby wanpengfei-git

repo: StarRocks/starrocks


text:
[Doc] Fix MV note

What type of PR is this：

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[x] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] I have checked the version labels which the pr will be auto backported to target branch

run starrocks_admit_test

@Mergifyio backport branch-2.5

authors: EsoragotoSpirit wanpengfei-git


text:
[Enhancement] Support temporary list partition prune

Signed-off-by: Astralidea astralidea@163.com
What type of PR is this：

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #17547
Problem Summary(Required) ：

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 2.5
[ ] 2.4
[ ] 2.3
[ ] 2.2

[FE PR Coverage Check]
:heart_eyes: pass : 57 / 62 (91.94%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/optimizer/rule/transformation/PartitionPruneRule.java
29
32
90.62%
[176, 177, 186]

:large_blue_circle:
com/starrocks/catalog/ListPartitionInfo.java
27
29
93.10%
[251, 252]

:large_blue_circle:
com/starrocks/persist/gson/GsonUtils.java
1
1
100.00%
[]

run starrocks_admit_test

authors: Astralidea wanpengfei-git


text:
[Feature] Support reading paimon table (#24626)

backport #24626

[FE PR Coverage Check]
:disappointed: fail : 249 / 599 (41.57%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/catalog/HudiTable.java
0
1
00.00%
[221]

:large_blue_circle:
com/starrocks/planner/PaimonScanNode.java
0
125
00.00%
[62, 63, 65, 66, 67, 70, 71, 72, 73, 76, 80, 84, 85, 86, 88, 89, 90, 91, 93, 97, 98, 99, 100, 105, 109, 110, 111, 112, 113, 114, 115, 117, 118, 119, 120, 123, 124, 125, 126, 127, 128, 129, 131, 132, 133, 136, 138, 139, 140, 141, 142, 143, 145, 146, 147, 149, 150, 152, 153, 156, 161, 163, 165, 166, 168, 169, 170, 172, 173, 174, 176, 177, 178, 180, 181, 182, 185, 186, 188, 189, 190, 191, 194, 195, 196, 199, 200, 202, 203, 205, 206, 207, 208, 209, 211, 214, 219, 224, 225, 226, 227, 229, 230, 232, 233, 234, 235, 236, 237, 238, 239, 242, 243, 246, 247, 248, 249, 251, 255, 258, 259, 263, 264, 265, 266]

:large_blue_circle:
com/starrocks/sql/plan/PlanFragmentBuilder.java
0
31
00.00%
[952, 954, 955, 956, 957, 960, 962, 963, 964, 967, 968, 969, 970, 971, 972, 973, 974, 975, 976, 977, 978, 979, 980, 981, 983, 985, 986, 988, 989, 990, 991]

:large_blue_circle:
com/starrocks/connector/hive/HiveMetaStoreThriftClient.java
0
8
00.00%
[723, 724, 732, 733, 734, 740, 741, 742]

:large_blue_circle:
com/starrocks/sql/optimizer/statistics/StatisticsCalculator.java
0
9
00.00%
[321, 326, 331, 332, 333, 334, 335, 336, 339]

:large_blue_circle:
com/starrocks/sql/optimizer/operator/logical/LogicalPaimonScanOperator.java
0
20
00.00%
[30, 36, 38, 39, 42, 46, 47, 48, 50, 51, 55, 60, 65, 66, 68, 71, 75, 80, 81, 82]

:large_blue_circle:
com/starrocks/sql/analyzer/QueryAnalyzer.java
0
2
00.00%
[255, 264]

:large_blue_circle:
com/starrocks/sql/optimizer/operator/physical/PhysicalPaimonScanOperator.java
0
14
00.00%
[41, 42, 43, 47, 52, 53, 57, 62, 67, 68, 69, 70, 71, 72]

:large_blue_circle:
com/starrocks/sql/optimizer/operator/OperatorVisitor.java
0
2
00.00%
[115, 266]

:large_blue_circle:
com/starrocks/connector/hudi/HudiRemoteFileIO.java
0
1
00.00%
[82]

:large_blue_circle:
com/starrocks/sql/optimizer/OptExpressionVisitor.java
0
1
00.00%
[133]

:large_blue_circle:
com/starrocks/qe/HDFSBackendSelector.java
0
4
00.00%
[101, 102, 103, 104]

:large_blue_circle:
com/starrocks/qe/ShowExecutor.java
0
4
00.00%
[782, 784, 785, 786]

:large_blue_circle:
com/starrocks/sql/optimizer/rule/implementation/PaimonScanImplementationRule.java
3
14
21.43%
[38, 39, 40, 41, 42, 43, 44, 45, 46, 48, 50]

:large_blue_circle:
com/starrocks/connector/paimon/PaimonFilter.java
7
20
35.00%
[37, 38, 41, 42, 45, 46, 47, 48, 49, 50, 53, 54, 56]

:large_blue_circle:
com/starrocks/catalog/Table.java
2
5
40.00%
[232, 278, 279]

:large_blue_circle:
com/starrocks/sql/optimizer/transformer/RelationTransformer.java
1
2
50.00%
[480]

:large_blue_circle:
com/starrocks/sql/optimizer/operator/OperatorBuilderFactory.java
1
2
50.00%
[56]

:large_blue_circle:
com/starrocks/connector/paimon/PaimonMetadata.java
64
107
59.81%
[79, 85, 86, 87, 97, 98, 105, 126, 127, 129, 130, 131, 132, 134, 135, 143, 148, 149, 150, 183, 184, 185, 197, 198, 199, 200, 202, 203, 205, 206, 207, 208, 209, 210, 211, 212, 213, 215, 218, 227, 228, 229, 231]

:large_blue_circle:
com/starrocks/connector/paimon/PaimonPredicateConverter.java
63
101
62.38%
[70, 77, 78, 80, 82, 83, 85, 93, 100, 114, 119, 135, 143, 151, 157, 167, 179, 184, 190, 192, 194, 198, 200, 202, 207, 208, 209, 210, 216, 217, 218, 220, 221, 223, 229, 234, 243, 251]

:large_blue_circle:
com/starrocks/catalog/PaimonTable.java
21
32
65.62%
[95, 100, 105, 106, 107, 108, 109, 110, 111, 112, 113]

:large_blue_circle:
com/starrocks/connector/paimon/PaimonConnectorFactory.java
2
3
66.67%
[13]

:large_blue_circle:
com/starrocks/connector/paimon/PaimonSplitsInfo.java
5
6
83.33%
[35]

:large_blue_circle:
com/starrocks/connector/paimon/PaimonConnector.java
21
25
84.00%
[78, 79, 81, 90]

:large_blue_circle:
com/starrocks/connector/ColumnTypeConverter.java
23
24
95.83%
[450]

:large_blue_circle:
com/starrocks/sql/optimizer/rule/transformation/ExternalScanPartitionPruneRule.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/connector/RemoteScanRangeLocations.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/catalog/HiveTable.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/server/MetadataMgr.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/sql/optimizer/rule/transformation/PruneHDFSScanColumnRule.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/connector/RemoteFileDesc.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/connector/paimon/RowDataConverter.java
15
15
100.00%
[]

:large_blue_circle:
com/starrocks/connector/hive/HiveRemoteFileIO.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/sql/optimizer/rule/transformation/MergeLimitDirectRule.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/sql/optimizer/rule/RuleType.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/sql/optimizer/rule/transformation/PushDownPredicateScanRule.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/connector/RemoteFileInfo.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/sql/optimizer/operator/OperatorType.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/connector/ConnectorMgr.java
1
1
100.00%
[]

authors: miomiocat wanpengfei-git


text:
[Enhancement] refresh row count info immediately after load

Why I'm doing:
cannot obatin  a correct row count immediately after load which may lead a bad plan.
What I'm doing:
use loaded rows from load task to help us estimate a more accurate row count .
Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.2
[x] 3.1
[ ] 3.0
[ ] 2.5

@mergify backport branch-3.2 branch-3.1


text:
Support olap table serialization with StarOSTablet

What type of PR is this：

[ ] bug
[x] feature
[ ] enhancement
[ ] others

Problem Summary(Required) ：

If storage medium is S3, use StarOSTablet in MaterializedIndex,
otherwise use LocalTablet.

[FE PR Coverage check]
:heart_eyes: pass : 34 / 37 (91.89%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/catalog/CatalogUtils.java
2
3
66.67%

:large_blue_circle:
com/starrocks/catalog/Partition.java
7
9
77.78%

:large_blue_circle:
com/starrocks/catalog/PartitionInfo.java
4
4
100.00%

:large_blue_circle:
com/starrocks/catalog/OlapTable.java
1
1
100.00%

:large_blue_circle:
com/starrocks/catalog/MaterializedIndex.java
10
10
100.00%

:large_blue_circle:
com/starrocks/catalog/Catalog.java
10
10
100.00%

authors: wanpengfei-git wyb


text:
fix null check in functions

What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] others

Which issues of this PR fixes ：
#4094 , #4092
Problem Summary(Required) ：
Some functions does not check null parameter correctly, cause BE crash.
The correct way to check the const value is FunctionContext::is_notnull_constant_column.

[FE PR Coverage check]
:heart_eyes: pass : 0 / 0 (0%)

[FE PR Coverage check]
:heart_eyes: pass : 0 / 0 (0%)

authors: mofeiatwork wanpengfei-git


text:
[Feature] support config starlet memory size bytes

Why I'm doing:
What I'm doing:
Fixes #issue
What type of PR is this:

[x] BugFix
[X] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.2
[x] 3.1
[ ] 3.0
[ ] 2.5

@mergify backport branch-3.2

@mergify backport branch-3.1


text:
[BugFix] Fix some problems of skew join

Why I'm doing:
CREATE TABLE t1 (
    c_key      INT NOT NULL,
    c_tinyint  TINYINT,
    c_smallint SMALLINT,
    c_int      INT,
    c_bigint   BIGINT,
    c_largeint LARGEINT,
    c_float    FLOAT,
    c_double   DOUBLE,
    c_decimal  DECIMAL(26,2),
    c_date     DATE,
    c_datetime DATETIME,
    c_string   STRING
)
DUPLICATE KEY(c_key)
DISTRIBUTED BY HASH(c_key) BUCKETS 1
PROPERTIES (
    "replication_num"="1"
);

CREATE TABLE t2 (
    c_key      INT NOT NULL,
    c_tinyint  TINYINT,
    c_smallint SMALLINT,
    c_int      INT,
    c_bigint   BIGINT,
    c_largeint LARGEINT,
    c_float    FLOAT,
    c_double   DOUBLE,
    c_decimal  DECIMAL(26,2),
    c_date     DATE,
    c_datetime DATETIME,
    c_string   STRING
)
DUPLICATE KEY(c_key)
DISTRIBUTED BY HASH(c_key) BUCKETS 1
PROPERTIES (
    "replication_num"="1"
);

Bug 1: Type int is not supported.
truncate table t1;
truncate table t2;
insert into t1(c_key, c_bigint) values (1, 1), (2, 1), (3, 1), (4, 12345678912), (5, 12345678912), (6, 3);
insert into t2(c_key, c_bigint) values (1, 1), (2, 12345678912), (3, 3);

mysql> select t1.c_key, t2.c_key from t1 join [skew|t1.c_bigint(1,12345678912,4444)] t2 on t1.c_bigint=t2.c_bigint order by t1.c_key, t2.c_key;
ERROR 1064 (HY000): VectorizedInPredicate type not same backend [id=10003] [host=172.26.92.227]

Bug 2: implicit type conversion is not supported.
truncate table t1;
truncate table t2;
insert into t1(c_key, c_int) values (1, 1), (2, 1), (3, 1), (4, 1234567), (5, 1234567), (6, 3);
insert into t2(c_key, c_bigint) values (1, 1), (2, 1234567), (3, 3);

mysql> select t1.c_key, t2.c_key from t1 join [skew|t1.c_int(1,2,99999)] t2 on t1.c_int=t2.c_bigint order by t1.c_key, t2.c_key;
ERROR 1064 (HY000): Can't find skew column

Bug3: Unknown error if skew column is not set
This pr will not fix the bug;
mysql> select t1.c_key, t2.c_key from t1 join [skew] t2 on t1.c_int=t2.c_bigint order by t1.c_key, t2.c_key;
ERROR 1064 (HY000): Unknown error

Bug4: Type of skew values maybe invalid convension.
truncate table t1;
truncate table t2;
insert into t1(c_key, c_tinyint) values (1, 1), (2, 1), (3, 1), (4, 2), (5, 2), (6, 3);
insert into t2(c_key, c_tinyint) values (1, 1), (2, 2), (3, 3);

select t1.c_key, t2.c_key from t1 join [skew|t1.c_tinyint(1,2,88888)] t2 on t1.c_tinyint=t2.c_tinyint order by t1.c_key, t2.c_key;
ERROR 1064 (HY000): VectorizedInPredicate type not same backend [id=10003] [host=172.26.92.227]

What I'm doing:

Skew values should cast to the type of column.
The result type of round() is BigInt, so generate_series also need to use bigint.
Support implicit cast.

What type of PR is this:

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.2
[x] 3.1
[ ] 3.0
[ ] 2.5

@Mergifyio rebase

https://github.com/Mergifyio backport branch-3.1


text:
optimize uuid() implements

What type of PR is this：

[ ] bug
[ ] feature
[x] enhancement
[ ] others

Problem Summary(Required) ：
uuid format: fixed 33 bytes

@Mergifyio rebase

@Mergifyio backport branch-2.2


text:
[Feature] Support full statistics collect with partition and histogram statistics

What type of PR is this：

[ ] bug
[ ] feature
[x] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Background:
Statistics currently default to sampling statistics. The purpose is to achieve the collection of full basic statistical information by default in a relatively low-cost way.
Added user interface

View analyze history: show analyze status
View the analysis status of the table, record the type and time of the last successful analysis: show stats meta
View the list of automatically collected tasks: show analyze job, the meaning is the same as the original show analyze

Statistics collection refinement

The collection granularity is changed from the original table level to the partition level (specific test result: HLL aggregation efficiency test), and then aggregated to the table level during query. The advantage of doing this is

The collection granularity is controllable, and the granularity and time of statistical information collection can be controlled according to the update information recorded in the meta. For partitions with no data update, statistics can no longer be updated.
When querying, aggregate the statistics of multiple partitions of a table into table statistics. Cardinality statistics are changed from the original table-level storage cardinality to the partition-level storage of HLL type columns. This ensures that although the storage granularity is changed to the partition level, the size of the statistical information stored in the memory of the FE will not expand significantly due to the partition granularity.
Configure the trigger time for statistics collection. If the trigger time is configured, statistics collection can only be performed at a specific time to minimize the impact of statistics collection on online cluster queries.
FE obtains the relevant line number information affected by Load and Delete through the information stored in Meta. Adjust the strategy for automatically collecting statistics by configuring the strategy. Trigger automatic updates when the threshold of row count changes is reached

Get information about data changes
Added AnalyzeMeta, which is used to record relevant raw data collected by table-level statistics. In all the positions of the load operation, the number of rows affected by this load is recorded in AnalyzeMeta, which keeps increasing. When statistics are successfully collected, update the status in AnalyzeMeta. Every time an Analyze is completed for each table, the counter of the corresponding table is cleared and counted again.
Process that triggers Analyze

As a background thread, StatisticAutoCollector continuously polls according to the statistic_collect_interval_sec attribute
Determine whether the table is within the set time period for statistical information collection
Collect the load data of each table. If change_row / row_number > auto_analyze_ratio , it is judged that the threshold for re-collecting statistics is met.
Get all partitions of the table. If the update time of the records in the partition is later than the last statistics collection time of the table, the update condition is satisfied. For unsatisfied partitions, statistics are not updated.

Problem Summary(Required) ：

[FE PR Coverage check]
:disappointed: fail : 373 / 944 (39.51%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/http/rest/QueryDumpAction.java
0
1
00.00%

:large_blue_circle:
com/starrocks/sql/optimizer/statistics/Bucket.java
0
10
00.00%

:large_blue_circle:
com/starrocks/service/FrontendServiceImpl.java
0
5
00.00%

:large_blue_circle:
com/starrocks/load/loadv2/SparkLoadJob.java
0
3
00.00%

:large_blue_circle:
com/starrocks/statistic/SampleStatisticsCollectJob.java
0
65
00.00%

:large_blue_circle:
com/starrocks/sql/ast/CreateAnalyzeJobStmt.java
0
1
00.00%

:large_blue_circle:
com/starrocks/sql/common/MetaUtils.java
0
4
00.00%

:large_blue_circle:
com/starrocks/sql/optimizer/statistics/Histogram.java
0
4
00.00%

:large_blue_circle:
com/starrocks/sql/optimizer/statistics/ColumnStatistic.java
0
3
00.00%

:large_blue_circle:
com/starrocks/statistic/StatisticUtils.java
0
2
00.00%

:large_blue_circle:
com/starrocks/load/loadv2/BrokerLoadJob.java
0
3
00.00%

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
0
21
00.00%

:large_blue_circle:
com/starrocks/persist/EditLog.java
0
15
00.00%

:large_blue_circle:
com/starrocks/sql/optimizer/statistics/CachedStatisticStorage.java
0
2
00.00%

:large_blue_circle:
com/starrocks/statistic/HistogramStatsMeta.java
0
20
00.00%

:large_blue_circle:
com/starrocks/sql/ast/ShowHistogramStatsMetaStmt.java
0
28
00.00%

:large_blue_circle:
com/starrocks/journal/JournalEntity.java
0
9
00.00%

:large_blue_circle:
com/starrocks/statistic/HistogramStatisticsCollectJob.java
0
28
00.00%

:large_blue_circle:
com/starrocks/qe/ShowExecutor.java
4
40
10.00%

:large_blue_circle:
com/starrocks/statistic/TableCollectJob.java
4
32
12.50%

:large_blue_circle:
com/starrocks/statistic/AnalyzeManager.java
8
49
16.33%

:large_blue_circle:
com/starrocks/statistic/StatisticsMetaManager.java
16
86
18.60%

:large_blue_circle:
com/starrocks/statistic/StatisticAutoCollector.java
16
66
24.24%

:large_blue_circle:
com/starrocks/statistic/BaseCollectJob.java
21
48
43.75%

:large_blue_circle:
com/starrocks/statistic/StatisticExecutor.java
38
75
50.67%

:large_blue_circle:
com/starrocks/statistic/BasicStatsMeta.java
18
30
60.00%

:large_blue_circle:
com/starrocks/statistic/FullStatisticsCollectJob.java
24
37
64.86%

:large_blue_circle:
com/starrocks/statistic/AnalyzeJob.java
10
14
71.43%

:large_blue_circle:
com/starrocks/sql/ast/ShowAnalyzeJobStmt.java
36
47
76.60%

:large_blue_circle:
com/starrocks/sql/ast/ShowAnalyzeStatusStmt.java
37
44
84.09%

:large_blue_circle:
com/starrocks/statistic/AnalyzeStatus.java
27
32
84.38%

:large_blue_circle:
com/starrocks/sql/ast/ShowBasicStatsMetaStmt.java
24
28
85.71%

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
7
8
87.50%

:large_blue_circle:
com/starrocks/statistic/StatisticSQLBuilder.java
29
30
96.67%

:large_blue_circle:
com/starrocks/catalog/FunctionSet.java
26
26
100.00%

:large_blue_circle:
com/starrocks/sql/ast/AnalyzeHistogramDesc.java
1
1
100.00%

:large_blue_circle:
com/starrocks/common/Config.java
4
4
100.00%

:large_blue_circle:
com/starrocks/statistic/Constants.java
2
2
100.00%

:large_blue_circle:
com/starrocks/sql/parser/SqlParser.java
1
1
100.00%

:large_blue_circle:
com/starrocks/sql/parser/ErrorHandler.java
3
3
100.00%

:large_blue_circle:
com/starrocks/catalog/Type.java
1
1
100.00%

:large_blue_circle:
com/starrocks/sql/analyzer/AnalyzeStmtAnalyzer.java
16
16
100.00%

[FE PR Coverage check]
:disappointed: fail : 382 / 957 (39.92%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/http/rest/QueryDumpAction.java
0
1
00.00%

:large_blue_circle:
com/starrocks/sql/optimizer/statistics/Bucket.java
0
10
00.00%

:large_blue_circle:
com/starrocks/service/FrontendServiceImpl.java
0
5
00.00%

:large_blue_circle:
com/starrocks/load/loadv2/SparkLoadJob.java
0
3
00.00%

:large_blue_circle:
com/starrocks/statistic/SampleStatisticsCollectJob.java
0
65
00.00%

:large_blue_circle:
com/starrocks/sql/ast/CreateAnalyzeJobStmt.java
0
1
00.00%

:large_blue_circle:
com/starrocks/sql/common/MetaUtils.java
0
4
00.00%

:large_blue_circle:
com/starrocks/sql/optimizer/statistics/Histogram.java
0
4
00.00%

:large_blue_circle:
com/starrocks/sql/optimizer/statistics/ColumnStatistic.java
0
3
00.00%

:large_blue_circle:
com/starrocks/statistic/StatisticUtils.java
0
2
00.00%

:large_blue_circle:
com/starrocks/load/loadv2/BrokerLoadJob.java
0
3
00.00%

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
0
21
00.00%

:large_blue_circle:
com/starrocks/persist/EditLog.java
0
15
00.00%

:large_blue_circle:
com/starrocks/sql/optimizer/statistics/CachedStatisticStorage.java
0
2
00.00%

:large_blue_circle:
com/starrocks/statistic/HistogramStatsMeta.java
0
20
00.00%

:large_blue_circle:
com/starrocks/sql/ast/ShowHistogramStatsMetaStmt.java
0
28
00.00%

:large_blue_circle:
com/starrocks/journal/JournalEntity.java
0
9
00.00%

:large_blue_circle:
com/starrocks/statistic/HistogramStatisticsCollectJob.java
0
30
00.00%

:large_blue_circle:
com/starrocks/qe/ShowExecutor.java
4
40
10.00%

:large_blue_circle:
com/starrocks/statistic/TableCollectJob.java
4
32
12.50%

:large_blue_circle:
com/starrocks/statistic/AnalyzeManager.java
8
49
16.33%

:large_blue_circle:
com/starrocks/statistic/StatisticsMetaManager.java
16
86
18.60%

:large_blue_circle:
com/starrocks/statistic/StatisticAutoCollector.java
16
66
24.24%

:large_blue_circle:
com/starrocks/statistic/BaseCollectJob.java
21
48
43.75%

:large_blue_circle:
com/starrocks/statistic/StatisticExecutor.java
38
75
50.67%

:large_blue_circle:
com/starrocks/statistic/BasicStatsMeta.java
18
30
60.00%

:large_blue_circle:
com/starrocks/statistic/FullStatisticsCollectJob.java
24
37
64.86%

:large_blue_circle:
com/starrocks/statistic/AnalyzeJob.java
10
14
71.43%

:large_blue_circle:
com/starrocks/sql/ast/ShowAnalyzeJobStmt.java
36
47
76.60%

:large_blue_circle:
com/starrocks/sql/ast/ShowAnalyzeStatusStmt.java
37
44
84.09%

:large_blue_circle:
com/starrocks/statistic/AnalyzeStatus.java
27
32
84.38%

:large_blue_circle:
com/starrocks/sql/ast/ShowBasicStatsMetaStmt.java
24
28
85.71%

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
7
8
87.50%

:large_blue_circle:
com/starrocks/sql/analyzer/AnalyzeStmtAnalyzer.java
24
26
92.31%

:large_blue_circle:
com/starrocks/statistic/StatisticSQLBuilder.java
29
30
96.67%

:large_blue_circle:
com/starrocks/catalog/FunctionSet.java
26
26
100.00%

:large_blue_circle:
com/starrocks/sql/ast/AnalyzeHistogramDesc.java
1
1
100.00%

:large_blue_circle:
com/starrocks/common/Config.java
5
5
100.00%

:large_blue_circle:
com/starrocks/statistic/Constants.java
2
2
100.00%

:large_blue_circle:
com/starrocks/sql/parser/SqlParser.java
1
1
100.00%

:large_blue_circle:
com/starrocks/sql/parser/ErrorHandler.java
3
3
100.00%

:large_blue_circle:
com/starrocks/catalog/Type.java
1
1
100.00%

authors: HangyuanLiu wanpengfei-git


text:
Seam carving

Let's admit that Images app is cool, but not as cool as it could be.
If the only purpose of this application is to store & present images, it should offer the world's top features available in image presenting.
Seam carving is such a feature. Adding this would let us explain more clearly why would someone compose their suite from great small apps.
JS implementations of seam carving: https://github.com/search?l=JavaScript&q=seam+carving&type=Repositories&utf8=✓
Correct way to do it is to create <img is="juicy-seam-carving"> Custom Element that uses one of the available JS libs, then use that Custom Element in Images app.

This is a very long term goal. The purpose of Starcounter prefabs is to prove that a "best-of-breed" Images app can provide an out of the box functionality that is better that what you would do within few days.
I just reported this issue as an example of such feature.

repo: StarcounterPrefabs/Images

license: mit


text:
Charybdis III Ghost Grazer Fauna Fix

Charybdis III Ghost Grazer Fauna not appearing correctly until a save & reload

Details
Mod fix located here:
https://www.nexusmods.com/starfield/mods/8214
Mod description:
This mod provides a fix for Ghost Grazer fauna on Charybdis III, where the bird will not appear correctly until the player either on purpose or accidentally lands on the correct biome and cannot find the last fauna. Normally a save and reload is needed for this fauna as it appears to be at the engine level. This bird is the only cloaking animal of flight in the game and apparently the engine has a hard time instantiating both flight and cloaking at the same time as of engine 1.8.88.0. This bird is non-hostile, so I removed the cloaking armor and replaced it with the Glowing Grazer variant as a stop-gap until Bethesda fixes their issue. The bird will immediately show up upon cell load of the correct biome without any other special commands.
Game Version
1.8.88.0
Language
English (EN)
New Game
Yes
Reproduction Steps
Read description for fix which you can add to the next CP.

This one appears to have been fixed officially.