text:
PSA: YTCenter seems to be dead. Use Youtube+

It's been months since an update and MANY things are broken. It would be nice if someone took over but I've heard that the code is complicated to work with so who knows..
There is another similar addon called Youtube+.
It isn't quite as feature rich as YTC but it's being kept up to date and works very well.
If you aren't able to use YTC anymore because it doesn't work, I suggest you check out YT+. It might not be for everyone but I've been using it for a while and love it.

The last commit was on August 16, 2015 by Yeppah on the Master Branch.
It's not been months and months.
But yes, support has dwindled.
Jeppe got a full time job and it has been eating up his time and he basically does the same thing at his job, code stuff, so by the time he gets home he doesn't want to do anything.
It seems he doesn't wish to work on Youtube Center anymore.
So, instead of letting it die, someone here needs to pick it up and continue it.
Code is always complicated to work with, don't let that stop anyone.
Just do it or else YTC will die.

PSA:
I tried your addon, it is:
a) broken
b) not playing well with other addons
c) laughably short on features. Making a video the size of the screen is not worth an addon.
There you go, a warm recommendation from me:
Stay well away from Youtube+.

@Eisys: Please close this issue. Promotion and/or denigration of other projects is an inappropriate subject for an issue tracker.

I did not really like the alternative, either.
It's too feature poor and the dev is already whining about how it's getting clogged down with "useless" features.
Yes because being able to see the Like/Dislike ratio or the render quality, is useless -_-  He also has no way to disable the watch button.
It is really not a replacement.

@Eisys The publicity is appreciated, but not here, I hope you understand.
@Corruptinglyneedful YT+ is not meant to be a replacement of YTC, it never was: https://github.com/ParticleCore/Particle/issues/95#issuecomment-144881029
Every feature request is welcomed and might be added at a later stage, but adding every single feature would result in a catastrophic mess and nightmare to maintain. For that reason the requests are open to the author's choice, wether he finds it useful or not being the most important criteria. Each person making a request obviously finds it useful, it doesn't mean it will be for others too.
No one is annoying anyone, if it seems that way it is not intentional and I don't know where the idea of "whining" and "clogged with useless features" came from but I assure you that this is not correct.

@IMNdi I have received your review reporting the problems you found and posted a reply. Thanks to your feedback and another user's I was finally able to fix the missing icons problem which was only happening with the AMO add-on version. The 0.7.7 version with the fix for this is already available in the archive section for download if you want to try it again.
Also YT+ is not compatible with similar add-ons, Magic Actions being one good example because it interferes with many core functionalities which YT+ also needs. It was never meant to work along with other similar add-ons and it is focused on being light, not featured packed like other alternatives.
It would really make me happy if you could try it again. If you decide to try, in the future please try to contact me about any issues before rating the add-on at one start because of something that could have been fixed beforehand, and because of something that was never the focus of the software or advertised as (to be compatible with similar add-ons, such as Magic Actions).

@ParticleCore Fixed.

@IMNdi Thank you, I am really glad that you decided to try it again. It is not surprising that YT+ does not work well with other add-ons for the reasons that I mentioned before, especially with YTC broken in many ways and especially because when all YTC settings are off it doesn't mean it isn't modifying the page, it still changes it regardless. YTC settings off does not mean the add-on is disabled which is why it still causes conflicts with YT+ with all settings off.
Your suggestions have been noted (especially the help link behavior improvement) and just wanted to address some of the other points you listed:

Missing a few details (In night mode, there are controls in settings that are black on black) but I'd call that "working".

It is not surprising, the buttons were made in such a way that users with night mode userstyles could just invert the black buttons with a simple css invert rule, but it wasn't made to work with any background other than YouTube's default. This includes the Magic Action night mode, of course. Although I am happy to know that it works better than expected with Magic Actions, despite it not being made to be compatible with it.

Glitches out if you click fullbrowser when video is popped to the side.

I never remembered to test that chain of events, will certainly try to fix this.

If I set quality to 1080 and the video has 720p only, the Quality buttons shows nothing.

It is a YouTube bug present in the new HTML5 player. I reported on the same day I found it, but they haven't fixed it since. Still will try to see if I can find a workaround on our end.
In the future, if you want to, make any request for features or improvements, or even bug reports in my issue tracker: https://github.com/ParticleCore/Particle/issues
it will make it easier to informed of recent feedback and for tracking the problems as well.
Once again, thank you for all your help!

@Yonezpt I edited my post to more accurately reflect what I meant and remove things that you confirmed as not true.
To put it simply, if people are advertising you as an alternative, you are expected to be equal to or greater than the original idea they are coming from.  You aren't and this is what upsets people and also what upset me because I wasted my time for something that was pitched as an alternative to Youtube Center, when it isn't.  It's not even close.
I absolutely LOVE Youtube Center, but if it's dead, than we need an alternative that IS AS GOOD as Youtube Center is right now.  You've pretty much declared you are not going to be that alternative, yet you listed Youtube Center as a inspiration for you starting your own project.  So you are sending mixed signals.  There are about TWO Youtube addons that I can think of that are worth their salt, with the features that are provided.  One being YTC and the other is a Youtube addon on Chrome, I can't think of the name right now, but I showed Yeppah it one time and he said it was very good and feature rich, but Chrome Only.
The long and short of it, is this;
People are ALWAYS going to ask for more, more and more features.  You can't keep denying them forever, eventually people will get fed up and leave.

You are assuming that YT+ was created to compete with something when it was already well established that it was not, it is nothing more than a lighter option for those that want that. If people want more then YT+ is not it.
To be inspired by something does not mean that the person aims to be like it or better than its inspiration, at best you can only be certain that the inspiration gave birth to the project. It can be anything completely unrelated to the inspiration too, it is not mutually exclusive.
If people want to leave because they wanted YT+ to be something that was not meant to be then that's the best decision they can make, there's no reason to keep using something that the user doesn't like anymore. It is always best to look for something better that meets their needs.
It is like I said, YT+ is not a replacement of anything, it is an option for people that want just what YT+ offers. If there's something else they would like to see implemented but is not a must for them then they can just request. It might be included, it might not be, it might be included at a later time.
If there's any idea being officially given that YT+ is a replacement for similar add-ons then it is being misunderstood and it is incorrect. Furthermore, it is often reminded that YT+ focuses on being light and compact, not feature rich or anything similar.
In short, YT+ is for people that find the current feature set enough and want somethig that is light. It is not trying to compete with anything, it is not trying to be anything but itself and it is not trying to sound like something that it is not, and will never be as far as I can tell.
And in your new edited text you have the following:

He also has no way to disable the watch button.

How so? It is clearly explained here that you can toggle it at will: https://github.com/ParticleCore/Particle/wiki/Features#info_bar
Or do you mean the watch later button? Because that is not any inability, it is simply something that isn't implemented. In fact if the user wants this he can just remove it with a simple userstyle rule. Can you show the reply confirming what you said?
And although you said you removed things that I confirmed as untrue then the following should not be present as well:

the dev is not happy about it getting clogged down with "useless" features and seems adverse with people coming from Youtube Center and suggesting features that Youtube Center has.

And:

Yes because being able to see the Like/Dislike ratio or the render quality, is useless

I clearly explained that saying that something isn't useful for that person does not mean that it is useless. If you can find any reply saying that the feature is useless I would really appreciate you showing me, otherwise what you said is not true.
I would also appreciate if you could provide examples of where the "seems adverse with people" is being conveyed because I can't find anything that could be constructed as being "adverse" towards anything or anyone, otherwise what you said about this is also not true.

You never actually said anything like that, sorry if it comes off that way.  It's more your attitude that speaks it for you. By this I mean;  I seen several replies to users asking for legitimate, to them, features from Youtube Center and you turned them down, citing that you did not want Y+ to become over saturated with features because than it would be hard to maintain and that if the user so wanted, they could just do this OTHER thing but you would take their suggestion into consideration.
You're telling them to sod off, you're just being nice about it.
That's basic PR speech for "Go away, I do not care, go do this other thing, and stop bothering me."
As more and more people begin to look at you as a replacement to Youtube Center, these things will only continue increasing and becoming more and more annoying.
Here's the thing about that though.  The majority doesn't  care why you started the project or what it was meant to be.  The majority, especially about now are looking at you for ONE thing, to be a replacement to Youtube Center.  Your little buddy there, the one that's been singing your praises, didn't help with that situation, either.  He literally is pitching you as an alternative to Youtube Center.  That brings certain expectations when people hear that.  To find out that those expectations aren't going to get met, well that's upsetting.
That is one of the reasons I am so upset.  I wasted my time because it was pitched as an alternative to YTC and so I went into it with certain expectations, those of which were not met and when I realized you have no intention to meet those expectations, well it's just bitter disappointment and a waste of time.
Just like this whole damn conversation.  So this is going to be the last thing I say and there will not be a reply, so don't ask for one, because you won't get one.
If you do not aim or aspire to be greater or equal to the bigger dogs that people want you to become or compete with, than they will eventually tire and leave, which makes your project dead.  You might still be maintaining it but if the majority of your user-base leaves, well you'll be forgotten about and moved on from.
This is currently what is happening to World of Warcraft.  I use them because they are the biggest and most successful example but I do realize that the projects aren't the same, only the sentiment but just go with me here.  For years WoW refused to adapt, change, or add new features that people wanted, because it did not want them or find them useful.  It was being a stick in the mud.  Fast forward a few and competitors FINALLY came up with something that was better and exceeded user expectations.  So now WoW is loosing subs daily and Blizzy doesn't want to talk about it anymore, they are ashamed.  WoW attempted to recover by conceding and finally adapting and changing but it was too late.  It will die.  Eventually, it will get down to the point where the userbase paying for it, becomes more and more of an expense and a drain on Blizzy and they will shut it down.
Mark my words.  I give it MAYBE 10 years and Blizzy will shut WoW down, unless there is some fantastic turn-around.
The problem with your particular situationhere, is that your competitors ALREADY exist and have a better product than you do.  So, if you continue on the whole "THIS IS MY PROJECT AND I'LL ONLY DO WHAT I WANT WITH IT." well you're going be obsolete pretty quickly then, which maybe that's fine with you.  Frankly, I just think it's a waste of potential and time.
Anyways, I'm not going to start in on a rant about creators working for their user-base rather than themselves, that's not my point here.  Just try and think about what I have said or you can just chalk this all up to a jaded user experience, I don't really care.
I wish you success with w/e becomes of your project and no, I won't be around to see it.
PS: I have no qualms with you, think of this as advice.
PPS: This took me 15 minutes or longer to think up and type, so it's not something that was just bashed out on the keyboard in under 5 minutes.

You're telling them to sod off, you're just being nice about it.

I am actually not, if i didn't want any more suggestions I would just close the issues and ignore them. I do always take them into consideration and I have already implemented at least 5 features, or more, which at first I didn't find them to be useful as well. I do go through all requests now and then to see if there's one I could add or not, if it is simple to do or not, worth it or not, etc.
Some times when I can tell the feature can be achieved from the user side easily (userstyles for example) I actually suggest them in case the user doesn't want to wait or really wants to have just that feature. Other times I even suggest other add-ons (userscripts) that do what they are looking for.

As more and more people begin to look at you as a replacement to Youtube Center, these things will only continue increasing and becoming more and more annoying.

That is unfortunate, but I can't do anything about it other than clear things up like I have been doing here. I could do as many other developers do and not interact with the userbase other than for bug tracking, but I prefer to interact because I think there's more to gain than to lose for both sides like this.

Your little buddy there, the one that's been singing your praises, didn't help with that situation, either.

Unfortunately it is something out of my control, he is also not the only one that considers YT+ to be a replacement for YTC, quite a few others do too and it is their opinion that this is true, not mine. If that's how they feel about it who am I to say that they are wrong? It is their opinion afterall and like I said, if they look at YT+ as something that is enough, even though it could have a bit more, then it fits what they were looking for.

So this is going to be the last thing I say and there will not be a reply, so don't ask for one, because you won't get one.

I understand, I just want things to be clear so that something like this doesn't keep happening, at least not with you.

If you do not aim or aspire to be greater or equal to the bigger dogs that people want you to become or compete with, than they will eventually tire and leave, which makes your project dead. You might still be maintaining it but if the majority of your user-base leaves, well you'll be forgotten about and moved on from.

If that is the case then it will sadden me, but it will not change what YT+ is because if I were to change then I would certainly get tired of it due to the intense maintenance and abandon the project.
I think I explained it better when I wrote this:

It's not due to lack of interest but because I don't want to add more features unless I find them to be useful. The software has already reached a point where it has too many features for me to be comfortable with maintaining, especially with YouTube changing so often. If I were to add every feature that is requested I would very likely be having trouble now trying to maintain the software and keeping it light, eventually getting tired of it and abandoning the project.

I would love to make a full feature packed software with all possible features requested by the users, but the frequent changes on YouTube do not permit it, at least not with just one person possessing limited time and programing knowledge.

I hope you understand.

https://greasyfork.org/en/forum/discussion/comment/17892/#Comment_17892
I do appreciate that you took the time to explain more of your thoughts, this will be a very useful conversation for other people that think of YT+ like you thought.

@Corruptinglyneedful  @Yonezpt
I am sorry for all this.
I never meant that YT+ is an absolute replacement for YTC.
I just really like YT+ and wanted others to try it out if YTC wasn't working out for them anymore.

authors: Corruptinglyneedful Eisys IMNdi ParticleCore Yonezpt Zarggg

repo: YePpHa/YouTubeCenter


text:
数据集，训练模型问题，

您好，我这边运行默认训练的时候，提示：No such file or directory: 'dataset//NUDT-SIRST/images/000282.png'  这个数据集 是不是自动下载的吗？怎么处理啊，可否发我一份到邮箱啊 15527803769@163.com

你好，请关注repo内的相关数据集链接

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
update[BUG]

Office Tool Plus Version, e.g. 8.1.0.0:

The 72nd file keeps showing updates being downloaded

Operating System, e.g. Windows 10 20H2 or Windows 7 SP1:

Windows11

Error description (required):

No error message, two hours after the update is still displayed in the update

Reproduction steps (suggested):
Screenshot (suggested):

Additional information (optional):

如果用的是中国移动宽带，那这个问题我也无解。由于 Office Tool Plus 的服务器是入门级别的，因此没法提供全面的服务。可以忽略这个更新，或者在这里下载最新打包的程序。

Fixed, the new version will be released this month.

authors: YerongAI yycyyx

repo: YerongAI/Office-Tool


text:
fix: dialog height

目前來看其他沒有被影響到

看起来是 #148 引入的，可以把这个 pr 的 line-break 去掉看看。如果单纯去掉 margin-bottom，可能会让多段落排版出问题。

line-break 去掉後可以解決這個問題

新版本导致 PWA 应用无法正常使用键盘 iOS Safari

去掉之后ReactMarkdown中将不展示换行

source: gharchive/pull-request

authors: HimiCos RugerMcCarthy Yidadaa hugoyue

repo: Yidadaa/ChatGPT-Next-Web


text:
pyodide

I see that you are using Pyodide. have you triend with the nodejs flavour? https://www.npmjs.com/package/pyodide

I haven't.

thank you. I was curious about your choice, I'm using it (pyodide nodejs) and I'm having some problems.

I have a compatibility layer for WebWorker API on top of VS Code's Node worker and it lets me use normal Pyodide. (I'm not sure how much of the compatibility is actually required--I think it uses window.location at least...)
That might not be very efficient though because it loads a bunch of stuff from the web and relies on Electron to cache it instead of maintaining its own cache. I'm not sure whether that's a problem or not in practice. The main use case for the extension is vscode.dev and the local use case is secondary.

got it! I will try your approach.
In my case it works fine in debug mode, but not when I pack the extension: https://github.com/pyodide/pyodide/issues/4267

It's probably because of the way you are using the packer (webpack?). My solution, while having  some other downsides, sidesteps this nicely
This isn't an issue with the YoWASP VS Code extension so I'm going to close this one.

I don't use any packer.
Sure, I'm sorry for the offtopic.

authors: qarlosalberto whitequark

repo: YoWASP/vscode

license: ISC


text:
cannot import name 'set_seed' from 'scvi'

import scanpy as sc
import matplotlib.pyplot as plt
import numpy as np
import pandas as pd
import torch
import anndata
import os

from scvi.dataset import Dataset10X
from scvi.models import TOTALVI
from scvi.inference import TotalPosterior, TotalTrainer
from scvi import set_seed

# Control UMAP numba warnings
import warnings; warnings.simplefilter('ignore')

if IN_COLAB:
    %matplotlib inline

# Sets the random seed for torch and numpy
set_seed(0)

---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
<ipython-input-2-2fb278341b08> in <module>
     10 from scvi.models import TOTALVI
     11 from scvi.inference import TotalPosterior, TotalTrainer
---> 12 from scvi import set_seed
     13
     14 # Control UMAP numba warnings

ImportError: cannot import name 'set_seed' from 'scvi'

Sorry this is confusing because the notebooks are designed to work with the code in the master branch. Please see #568. For now you can just install scvi from the tip of master.

authors: adamgayoso naity

repo: YosefLab/scVI


text:
Victory?

Google decided not to implement WEI in browsers. But they're doing basically the same thing for WebViews.
Source: https://9to5google.com/2023/11/02/google-chrome-web-integrity-api/

It's good to see that this project reached its goal.
I don't think there's much we can do about this Android Webview only Integrity, the Android ecosystem has always been controlled by Google, and the Play Integrity API / Widevine DRM confrontation has always been a cat-and-mouse game, and I don't have any ability to even formally confront it. I don't have any ability to fight against it even formally. Therefore, this project has come to an end.
I will update the README, remove all the code from the js file and replace it with a line reminding to remove the console.log of this js file. This project will not be Archive, but there will not be any updates either.
There is a saying in China, `Chinese temperament is always like to reconcile and compromise. For example, if you say that this room is too dark and you need to open a window here, people will definitely not allow it. But if you advocate removing the roof, they will come to an accommodation and be willing to open a window." In a similar vein, I don't think this new proposal is going to set off massive opposition, and therefore as stated above, have no incentive to engage in any confrontation.

Translated by DeepL
很欣慰看到这个项目达到了它的目标。关于这个Android Webview only Integrity，我并不认为我们能做什么。Android生态系统一直是受谷歌控制的，对于Play Integrity API / Widevine DRM的对抗也一直是处于猫鼠游戏的状态，我没有任何能力哪怕是仅仅从形式上去对抗它。因此，这个项目算是走到尽头了
我将更新README、将js文件中的代码全部删除并替换为一行提醒移除此js文件的console.log。此项目不会Archive，但也不会有任何更新。
中国有句话，“中国人的性情是总喜欢调和，折中的。譬如你说，这屋子太暗，须在这里开一个窗，大家一定不允许的。但如果你主张拆掉屋顶，他们就会来调和，愿意开窗了。”与之相似的，我也不认为这个新的proposal会掀起大规模的反对，也因此就像上面所述，并无动机进行任何对抗。

Yeah, I agree. I believe I should nevertheless thank everyone for their time and effort.

repo: Young-Lord/fight-for-the-open-web

license: Unlicense


text:
🛑 UPC is down

In 565b669, UPC (https://www.upc.edu.cn/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: UPC is back up in fccb293 after 20 minutes.

repo: Yourrrrlove/upptime


text:
🛑 UPC is down

In 587f4c4, UPC (https://www.upc.edu.cn/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: UPC is back up in bd411eb after 12 minutes.


text:
🛑 UPCME is down

In 363c1ad, UPCME (http://medwww.upc.edu.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: UPCME is back up in 893c58c after 9 minutes.


text:
JIT和非JIT对比

实际跑下来（用真正的业务层复杂函数），且确保所调用的所有函数都被jit的情况下，最后结果和非JIT还是差不多，有其他没考虑到的可能性吗？

我粗看了这个jit实现,说的不对,欢迎作者批评.
这个JIT可以说说纯粹翻译成C调用Lua API,本质上去掉了VM的指令派发,其他应该跟原生的无任何差别.
这个工作15年前有人做过lua2c,结论是不会有太大的提升.
我不知道作者的最大7倍提升的benchmark是什么.
因为编译器根本不理解动态语言.
建议你直接换luajit.
不过作者做的NOGC还是很好的优化点,尤其是在大量使用不变lua配置的环境下

我粗看了这个jit实现,说的不对,欢迎作者批评.
这个JIT可以说说纯粹翻译成C调用Lua API,本质上去掉了VM的指令派发,其他应该跟原生的无任何差别.
这个工作15年前有人做过lua2c,结论是不会有太大的提升.
我不知道作者的最大7倍提升的benchmark是什么.
因为编译器根本不理解动态语言.
建议你直接换luajit.
不过作者做的NOGC还是很好的优化点,尤其是在大量使用不变lua配置的环境下

使用了 mir 作为后端去优化

c2mir_compile不就是将C语言JIT吗?
这个工作流程我看了一下,就是直接翻译字节码到LUA C API,最后拼装了一份C的代码,扔进MIR编译一下.
本质上不就是去掉了VM的字节码派发吗,难道还有其他优化么,麻烦指出来.我可能遗漏了.
这种方式其实就跟V8的Sparkplug引擎差不多,直接翻译字节码,压根不追踪代码运行状态,不做任何条件假设.
不过好歹V8的堆栈是用的机器码,不是跟lua一样用堆模拟的.

看看mir吧。至于你说的其他类似inline cache优化确实是没有的。

c2mir_compile不就是将C语言JIT吗?
这个工作流程我看了一下,就是直接翻译字节码到LUA C API,最后拼装了一份C的代码,扔进MIR编译一下.
本质上不就是去掉了VM的字节码派发吗,难道还有其他优化么,麻烦指出来.我可能遗漏了.
这种方式其实就跟V8的Sparkplug引擎差不多,直接翻译字节码,压根不追踪代码运行状态,不做任何条件假设.
不过好歹V8的堆栈是用的机器码,不是跟lua一样用堆模拟的.

看看mir吧。至于你说的其他类似inline cache优化确实是没有的。

你的意思是mir内部会根据热点路径来做类型具化减少类型判断等优化？ @fesily 说的我之前也是感觉到疑惑，所以认为jit常见的部分侦测mir会搞定。但实际跑起来确实没啥区别

你可以看看ravi,也是用的mir.
作者的博客今年2月code-specialization-mir-lightweight-jit-compiler动态去优化计划中,所以这个功能估计现在没有.

你可以看看ravi,也是用的mir.
作者的博客今年2月code-specialization-mir-lightweight-jit-compiler动态去优化计划中,所以这个功能估计现在没有.

因为我自己一些想法的转变，这个项目已经不再继续维护了。

authors: Yu2erer fesily linxiaolong


text:
Failed to resolve: com.github

@YuganshT79 Hello yugansh, nice custom library there!
But the first time I tried to implement this in dependencies, it shows Failed to resolve: com.github

Can you share the LogCat here, show the problem is more clear 👍


text:
[FEATURE] Create Card Component

Description
Create a card component using storybook. Do research on typical horizontal card styling (height, width, padding,..) by checking out common frameworks like MUI or Bootstrap.

Additional links
Official docs from storybook https://storybook.js.org/
### Tasks
- [ ] Creade card component
- [ ] Use dummy image and text

Hi @YuriDevAT ! I'm still quite new to open-source but familiar with working with NextJs & would love to work on this issue ☺

Happy to have you on the team, @TaylorDJones11 😄

@YuriDevAT looking over the code, should my set up be similar to the "stories" directory or "components"

Thanks for your question @TaylorDJones11. As far as I understand how storybook works is to create a component as a "story" as they call it. These are stored in the stories folder

There are already a few premade components in it. As you can see in the folder structure, a button component consists of three files: Button.js, Button.stories.js and button.css.
To see the storybook of AccessibilityMentor locally, you have to run npm run storybook, then it will be opened in localhost:6006.

Thanks for your question @TaylorDJones11. As far as I understand how storybook works is to create a component as a "story" as they call it. These are stored in the stories folder  There are already a few premade components in it. As you can see in the folder structure, a button component consists of three files: Button.js, Button.stories.js and button.css.
To see the storybook of AccessibilityMentor locally, you have to run npm run storybook, then it will be opened in localhost:6006.

Great, thanks!

repo: YurisCodingClub/accessibility-mentor


text:
npm package provenance

概要

https://zenn.dev/bicstone/articles/npm-provenance
https://docs.npmjs.com/generating-provenance-statements

その他

無事にpublishできたことを確認
https://github.com/YuukiToriyama/japanese-address-parser/actions/runs/11764265132/job/32769235756

repo: YuukiToriyama/japanese-address-parser


text:
is there any way to extract encrypted database if yes tell me a way

is there any way to extract the encrypted database, if yes, tell me a way with some program option

I don't understand, if you're asking about getting you un-encrypted database then yes, that is the sole purpose of this tool.

I'm asking which option to use to return me the encrypted database for me to decrypt it

Encrypted database is in phone storage, you can simply copy that from phone "WhatsApp/Databases" folder. You don't require any tool for that.

The problem is when I get the key extracted by this program, I get the encrypted database trying to decrypt and it returns error in whats app viewer

Share screenshot showing the contents this tool pulled.

here are the files

This db is not encrypted.

Don't use decrypt function in viewer, simply open this file

Please avoid open unnecessary issues.

when i try to read the conversations decrypted by the program i get this error

Use sqlite-browser or any other db reader.

This is not an issue of this repo.


text:
Request to Add Program "Check if a Given Linked List is Palindrome" in C

Description:
I would like to request adding a new program in C that checks whether a given linked list is a palindrome or not.
Problem Description:
A palindrome is a sequence that reads the same backward as forward. For a linked list, the task is to check if the elements of the linked list form a palindrome.
Please assign me this task @Reynaldev

You can start doing it if you can, because I'm not a maintainer of this repo. Or if you're asking me to write that program for you, then I would.

@twinkle485  maintainer alert 😅.   @YuweAEC  I'm the maintainer and you can proceed

@YuweAEC, I tried to mention you, but the tag feature was not available for you.

No problem if the tag was not there you just post the issue

I have made a PR, pls check it

authors: Reynaldev YuweAEC twinkle485

repo: YuweAEC/hacktoberfest-playground


text:
Support for Middle Earth - Shadow of War

Middle Earth - Shadow of War:
Game package name: WarnerBros.Interactive.WB-Kraken_ktmk1xygcecda
I have found reddit post noting that it is possible to move saves (however link in the comment is dead ;) ): https://www.reddit.com/r/shadow_of_war/comments/k6hfy6/transfer_save_game_from_microsoft_store_to_steam/
Steam save to download from external source: https://gtrainers.com/load/categories/savegames/middle_earth_shadow_of_war_save_game_100_2_dlc/30-1-0-6348
wgs.zip

Hi! Any news on this?

It seems that the save files contain some player IDs, which need to be changed during runtime for the transferred saves to work. See https://www.pcgamingwiki.com/wiki/Middle-earth:_Shadow_of_War#Inability_to_transfer_Steam_saves_to_the_GOG_version.
Here's your save file if you'd like to try. I just set the name to that by hand, as the wgs data doesn't contain any filename information.
save.zip
I'd like to avoid adding support for this game as long as the save files aren't easily editable by the script to work with different versions.

authors: Aramil-S Luilem Z1ni


text:
Odoo Support

Could you consider Odoo chart support? I have tried a custom image with arm support but some path doesn't match with the official bitnami chart values.
Thanks for amazing job btw.

@joepa37 I looked at odoo, but found that it wasn't infrastructure related software. I don't think it's the software I'm using or interested in in the near future. It's hard to use the time for this. It is also mentioned in the README, but supporting all bitnami's charts is not currently the goal of this repository. Also, even if I write those images, few people will use them.
I recommend making a chart that uses the official image or modifying bitnami's chart to use the official image.

repo: ZCube/bitnami-compat


text:
Add patterns to text_patterns.py

for asking about

fav things
feelings
help

@Jonah-gr pull request ready to be merged


text:
🛑 Official Website is down

In 825d1af, Official Website (https://www.zeenkey.com) was down:

HTTP code: 500
Response time: 173 ms

Resolved: Official Website is back up in 2e7a35c.

repo: ZEENKEY/statuspage


text:
🛑 Server 1 is down

In b586fe5, Server 1 (https://www.zeenkey.com) was down:

HTTP code: 500
Response time: 188 ms

Resolved: Server 1 is back up in 6275b1d.


text:
🛑 ZEENKEY CDN is down

In 52d7022, ZEENKEY CDN (https://zeenkeycdn.ga) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ZEENKEY CDN is back up in 55dffb9.


text:
Make use of path filters for GitHub actions

Is your feature request related to a problem? Please describe.
The following pipelines are currently triggered/running regardless whether there is a change justifying a run:
https://github.com/ZEISS/czicompress/actions/workflows/czicompress_cmake.yml
https://github.com/ZEISS/czicompress/actions/workflows/czishrink_dotnet.yml
https://github.com/ZEISS/czicompress/actions/workflows/czicompress_codeql.yml
https://github.com/ZEISS/czicompress/actions/workflows/czishrink_codeql.yml
Describe the solution you'd like
Make use of https://github.com/dorny/paths-filter to only run the pipelines listed above in case of changes in:
https://github.com/ZEISS/czicompress/actions/workflows/czicompress_cmake.yml
https://github.com/ZEISS/czicompress/actions/workflows/czicompress_codeql.yml
-> Change in czicompress or ./ excluding czishrink
https://github.com/ZEISS/czicompress/actions/workflows/czishrink_dotnet.yml
https://github.com/ZEISS/czicompress/actions/workflows/czishrink_codeql.yml
-> Change in czishrink or ./ excluding czicompress
Additional context
Add any other context or screenshots about the feature request here.
https://stackoverflow.com/questions/70708306/github-actions-run-step-job-in-a-workflow-if-changes-happen-in-specific-folde
https://github.com/orgs/community/discussions/25669
https://how.wtf/run-workflow-step-or-job-based-on-file-changes-github-actions.html
In particular, status checks will still work/apply: https://docs.github.com/en/actions/managing-workflow-runs/skipping-workflow-runs

We had path filters initially in PR #6, but we removed them because the respective github workflows were required PR checks (via branch protection rules). E. g. when you make changes to czishrink, a successful czicompress_cmake build is still required to be able to complete a PR targeting main.

We had path filters initially in PR #6, but we removed them because the respective github workflows were required PR checks (via branch protection rules). E. g. when you make changes to czishrink, a successful czicompress_cmake build is still required to be able to complete a PR targeting main. So it would be required to 'path-filter' also the branch protection rules.

Thanks for your remark. Please refer to "Additional context" above. The workflow will not be skipped - the job will be skipped based on the outcome of https://github.com/dorny/paths-filter, i.e. it works on job/step level. Thus, individual jobs will be marked as skipped, which however makes the check pass/succeed.

I've abandoned the PRs #36 and #37. Nobody seems to work on this any more and there is no real urgency => closing the issue.

repo: ZEISS/czicompress


text:
Chore/update dependencies

Types of Changes
Prerequisites
Please make sure you can check the following two boxes:

[x] I have read the CONTRIBUTING document
[x] My code follows the code style of this project

Contribution Type
What types of changes does your code introduce? Put an x in all the boxes that apply:

[x] Bug fix (non-breaking change which fixes an issue, please reference the issue id)
[ ] New feature (non-breaking change which adds functionality, make sure to open an associated issue first)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Styled-components updated from v4 to v5
React-datepicker updated from v2 to v4
Lots of minor changes everywhere can cause unexpected issues, thorough integration testing is needed.

[ ] My change requires a change to the documentation
[ ] I have updated the documentation accordingly
[x] I have added tests to cover my changes
[x] All new and existing tests passed

Description
This is another attempt to upgrade Precise UI dependencies. Lots of our dependencies including such major ones as Typescript, Webpack, Styleguidist, or React are one or many major versions behind. There were 3 unfinished attempts to update some or all of them during the last year:

https://github.com/ZEISS/precise-ui/tree/feature/update-deps
https://github.com/ZEISS/precise-ui/tree/chore/UpdateTypeScriptDependecy
https://github.com/ZEISS/precise-ui/pull/321

This attempt is not based on any of them directly, but I used them for reference. My primary goal was to update Typescript to version 4. Most of the other updates are cascading changes needed to fix issues with the main upgrade. There are still many dependencies that have to be updated, but the PR is already huge. Here are some points I want to highlight:
Text snapshot changes
During the upgrade, I had to update some snapshots.  There are 3 main reasons for the changes:

Some components now have meaningful names instead of just  (example)
Some CSS selectors are sorted differently (example)
Components are missing additional  wrapper with metadata (example)

Some of these changes may potentially cause problems. I ran the visual tests before committing them, and they were OK, so I hope I have not broken anything. I am not an expert in frontend and not closely familiar with Precise UI, so please check the changes thoroughly.
Visual snapshot changes
I have updated Puppeteer and Chromium. There was a bunch of broken snapshots but the difference mostly was not noticeable visually. I guess it was caused by the rendering engine changes in Chromium.
I have attached the visual diff files for your convenience. Please take a look, as some of the changes were more significant, like the ones in StackPanel_3-diff.png, TagBuilder_15-diff.png, and Flyout_11-diff.png
Bundle size
The bundle size has increased from 650 to 726 Kb. I did not try to do anything with it as I am not an expert in this field and optimizing the bundle was not my primary goal. Maybe there is a way to decrease it, but I am not capable of doing it myself.
There is still lots of work to do, including updates of Jest, Webpack, some other packages, but I believe we should move forward with smaller steps, so I have stopped here.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Illia Simenko seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant simenko

repo: ZEISS/precise-ui


text:
menu

I want to add a playlist in my blog's menu.
But how can I add the image

like this for it ,it just like this.

Could you tell me how can I add this thing?

Thanks a lot
从 Windows 版邮件https://go.microsoft.com/fwlink/?LinkId=550986发送
发件人: @.>
发送时间: 2021年10月8日 21:42
收件人: @.>
抄送: @.>; @.>
主题: Re: [ZJDoc/Hexo-NexT] menu (#1)
I want to add a playlist in my blog's menu. But how can I add the image [image] https://user-images.githubusercontent.com/78669276/136377158-694ea68e-a5ef-4231-9ffe-c684e951cbf3.png like this for it ,it just like this. [image] https://user-images.githubusercontent.com/78669276/136377261-76e6a871-7190-4404-a165-138d09f29b31.png Could you tell me how can I add this thing?
see 菜单栏https://hexo-next.readthedocs.io/zh_CN/latest/next/base/菜单栏/
#commonweal: /404/ || fa fa-heartbeat
fa fa-heartbeat means icons, you can choose one from fontawesomehttps://fontawesome.com/
―
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/ZJDoc/Hexo-NexT/issues/1#issuecomment-938653548, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASYGLXAREUM5KOCAHGXSHQ3UF3YMFANCNFSM5FRCQJEQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

repo: ZJDoc/Hexo-NexT


text:
GSoC2023: Updated build.sh File

Added sed "s=<organization>=<config><organization>=g;s=</organization>=</organization></config>=g" -i docker/ets-ogcapi-processes/src1/ets-ogcapi-processes10/src/main/config/teamengine/config.xml in build.sh file.

Please provide a PR including only the modification to the build.sh file and we will merge it.

repo: ZOO-Project/ZOO-Project


text:
Update dev-line after upstreaming

Updates the dev line builds after upstreaming less patches: https://github.com/gwsw/less/pull/464

You upstreamed the changes?  Very nice!

authors: AnthonyGiorgio IgorTodorovskiIBM

repo: ZOSOpenTools/lessport


text:
where is the papaer?

Hi  great works! but Where can I get a download link for this paper?

Thank you for your question.  A camera-ready version of the manuscript has been submitted to the CVPR official; the exact visible time needs to be subject to the CVPR official. In addition, we have no plans to release a preprint. If you would like to see the manuscript in advance, please contact me at ziyangchen2000 AT gmail DOT com

Thank you for your interest. Preprint paper is available here.

repo: ZYangChen/MoCha-Stereo


text:
error: Rate Limit Exceeded #2

After more testing with the fix in place for the previous issue (#1), I hit the rate limit exceeded error again. Debugged like before and found that filtron has a rss/csv/json limit. Since this app uses json, it got caught by the limit which in my case (default filtron settings) was a dismal 2 requests every 121 seconds. I just disabled the json part of that rule for now but if using other searx instances with that rule in place, this same problem will occur.
Fix would be to not use the format flag at all and render the html page instead of json

Seems like the solution is to rewrite this app using webviews

See new app (currently works fine but still WIP) here: https://github.com/Zackptg5/Searx-Android


text:
Web UI

Создать каркас веб-интерфейса на основе технологии Blazor.
Настроить навигацию между страницами.

[ ] Создать карточку для просмотра личного профиля пользователя


text:
Damage Calculator

OK, I'm new to all this cool stuff so I know some of this won't be correct but I do know it works! So feedback would be appreciated! (I know I should probably be using Tools.getMove etc but the command fucks up when I do so if you know how to fix that go ahead and comment).

Holy shit that's a lot errors.

I'll do what it says and fix it.

Are we interested in a calc plugin? O.o
The plan was to embed honko's in the battle gui this whole time...

Also note, the comments I made were just general to help you in general; I personally don't have a preference if this actually should or shouldn't be added to the project.

This seems like a hassle and also doesn't take into account past generations. This also gets rid of a lot of cool things honko's Calc has (all vs one, etc). Imo this is completely un-needed and adds more work that is already done somewhere else.

@AustinXII considering I'm doing all the work I don't see how it does cause a hassle. @Slayer95 This isn't permanent it's just till we get Honko's calculator implemented and. @panpawn Thanks will do.

@czn-PS you still are forgetting about the special features that the damage calc currently has... I know quite a few people would be upset losing one vs all, etc

what do you mean by "losing" this is just an add on you can still get the normal calc by typing /calc url. :/

Honestly, as long as it links to Honkalculator by typing /calc by itself, it's fine, but the main problem here is still low-quality code. I'm going to wait this to at least pass npm test before I offer more detailed feedback on code quality.

@Zarel thanks.

Command name idea: if we're keeping /calc as the link to Honkalculator, then maybe make this new command just /damagecalc

They can share the same name. It's not a big deal.

Sooooooo I read you're guys stuff and the code looks really nice now I'm not using globals anymore which is awesome! Which has taught me how most of the Tools work and there really convenient! So yeah looking good! :D

This isn't the final code this is just to display what I have updated and npm test doesn't work on my Cloud 9 so Travis is gonna help me out. :)

OK so now I all I got to do is do what Travis says and it's done!!!

I'm not using globals anymore

You still are :|

Are you going to be updating this? If there are no changes in another 7 days, I'm going to close this. You can open a new pull request when your code gets to the point where it passes npm test.

@Zarel yes I will sorry I have had exams at school so was concentrating on that more but I will be updating sorry again!

embedding Honko's calc to the server will be noice

This code isn't originally yours.  It comes from sparkyboTTT (I wrote the code about 1 to 1.5 years ago, hence the low quality)... You remind me of (gitbanned) user psnsVGC who tried to PR the exact same code i gave him in a hastebin to ChuChuBoTTT repository in Jan 2016.
(the globals for Pokedex, Movedex, etc were taken from battle/battle.js where i made them global for the battling AI, as well as use in kunc, damage calc etc...)

authors: AustinXII Lord-Haji Slayer95 Zarel czn-PS panpawn sparkychildcharlie

repo: Zarel/Pokemon-Showdown

license: mit

license_source: bigquery


text:
LightwalletD w\ Zebra backend fails to connect

Description

[short summary of the bug]
Steps to Reproduce
I tried this:
[behavior or code sample that causes the bug]
Running LightwalletD with the zcash.conf file empty as described in the first bullet point of 'Syncing LightwalletD' in the zebra book here
https://github.com/ZcashFoundation/zebra/blob/main/book/src/user/lightwalletd.md#sync-lightwalletd
Fails with the output
john@john-Latitude-5490:~/go/bin$ ./lightwalletd --no-tls-very-insecure --zcash-conf-path ~/.config/zcash.conf --data-dir . --log-file /dev/stdout
{"app":"lightwalletd","buildDate":"","buildUser":"","gitCommit":"","level":"info","msg":"Starting gRPC server version v0.0.0.0-dev on 127.0.0.1:9067","time":"2022-12-01T11:24:08-07:00"}
{"app":"lightwalletd","level":"warning","msg":"Starting insecure no-TLS (plaintext) server","time":"2022-12-01T11:24:08-07:00"}
Starting insecure server
{"app":"lightwalletd","error":"stat : no such file or directory","level":"warning","msg":"error with getblockchaininfo rpc, retrying...","retry":1,"time":"2022-12-01T11:24:08-07:00"}

Adding the required lines the zcash.conf file as described in the LightwalletD build instructions here
https://github.com/zcash/lightwalletd#zcashd
txindex=1
insightexplorer=1
experimentalfeatures=1
rpcuser=xxxxx
rpcpassword=xxxxx

Fails with the output
john@john-Latitude-5490:~/go/bin$ ./lightwalletd --no-tls-very-insecure --zcash-conf-path ~/.config/zcash.conf --data-dir . --log-file /dev/stdout
{"app":"lightwalletd","buildDate":"","buildUser":"","gitCommit":"","level":"info","msg":"Starting gRPC server version v0.0.0.0-dev on 127.0.0.1:9067","time":"2022-12-01T11:45:39-07:00"}
{"app":"lightwalletd","level":"warning","msg":"Starting insecure no-TLS (plaintext) server","time":"2022-12-01T11:45:39-07:00"}
Starting insecure server
{"app":"lightwalletd","level":"info","msg":"Got sapling height 419200 block height 1898069 chain main branchID c2d6d0b4","time":"2022-12-01T11:45:39-07:00"}
{"app":"lightwalletd","level":"info","msg":"Found 0 blocks in cache","time":"2022-12-01T11:45:39-07:00"}
{"app":"lightwalletd","level":"info","msg":"getblock 419200 failed, will retry: error requesting block: 0: parse error: Height(u32) integer parse error","time":"2022-12-01T11:45:39-07:00"}

Expected Behaviour
I expected to see this happen: Lightwalletd starts and begins successfully querying for block info
Actual Behaviour
Instead, this happened: getblock fails
Zebra Logs
Details: From going, stopped and restarted for info purposes

2022-12-01T18:35:48.646326Z  INFO {zebrad="79419b6" net="Main"}:{peer=Out("18.217.102.40:8233")}:msg_as_req{msg="inv"}:inbound:download_and_verify{hash=000000000131943c276a2a95213478d8b190a938ed90b3f8f070fefa839903e3}: zebrad::components::inbound::downloads: downloaded and verified gossiped block height=Height(1898065)
2022-12-01T18:35:49.176259Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::sync::progress: finished initial sync to chain tip, using gossiped blocks sync_percent=100.000% current_height=Height(1898065) network_upgrade=Nu5 remaining_sync_blocks=0 time_since_last_state_block=0s
2022-12-01T18:36:08.355410Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::mempool::gossip: sending mempool transaction broadcast request=AdvertiseTransactionIds({Witnessed(WtxId { id: transaction::Hash("d90c71d78766563a07c172874f509071ce5e2a493daefc64050b80ba030ed825"), auth_digest: AuthDigest("77e2ffad83f06c9e822d0c0af7104b88dd4ae58d2481a7e27c62656f2bdf9fe9") })})
2022-12-01T18:36:36.189620Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::mempool::gossip: sending mempool transaction broadcast request=AdvertiseTransactionIds({Legacy(transaction::Hash("afb801ef36cd562e4109b82c50dd0cace28f1af397f7bec5df05dffbf9703897"))})
2022-12-01T18:36:43.781903Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::mempool::gossip: sending mempool transaction broadcast request=AdvertiseTransactionIds({Legacy(transaction::Hash("fc8d08d77c6f906c177fd9b17a9f41cf04b4aef3d3a248d680318ca866cfa7a4"))})
2022-12-01T18:36:45.402568Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::mempool::gossip: sending mempool transaction broadcast request=AdvertiseTransactionIds({Legacy(transaction::Hash("59397c7696b1fcf36d72eae52f57c089d6edc2b460f5b333b4a8e32cd4489236"))})
2022-12-01T18:36:49.177950Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::sync::progress: finished initial sync to chain tip, using gossiped blocks sync_percent=100.000% current_height=Height(1898065) network_upgrade=Nu5 remaining_sync_blocks=1 time_since_last_state_block=1m
2022-12-01T18:36:53.320040Z  INFO {zebrad="79419b6" net="Main"}:sync:try_to_sync: zebrad::components::sync: starting sync, obtaining new tips state_tip=Some(Height(1898065))
2022-12-01T18:36:54.318313Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::mempool::gossip: sending mempool transaction broadcast request=AdvertiseTransactionIds({Witnessed(WtxId { id: transaction::Hash("338287daaccefd248c313a2808fea2e30d3b13c1b6c625044a47c00436c9138f"), auth_digest: AuthDigest("8c3b37123b819bf0daea8fad08766f61e868c6e43ab58a10dc4271d521da7179") })})
2022-12-01T18:36:59.321668Z  INFO {zebrad="79419b6" net="Main"}:sync:try_to_sync: zebrad::components::sync: exhausted prospective tip set
2022-12-01T18:36:59.321688Z  INFO {zebrad="79419b6" net="Main"}:sync: zebrad::components::sync: waiting to restart sync timeout=67s state_tip=Some(Height(1898065))
2022-12-01T18:36:59.321776Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::mempool::gossip: sending mempool transaction broadcast request=AdvertiseTransactionIds({Witnessed(WtxId { id: transaction::Hash("619c479c683a99bf21120321d4e67e67e11f7c4f6af8ec56fca51aed4724eac5"), auth_digest: AuthDigest("35e7f5302ab6cc6045f16c1b38dd99fe4a939af91cb700736d6ca085b715c7a2") })})
2022-12-01T18:37:19.424846Z  INFO {zebrad="79419b6" net="Main"}:crawl_and_dial{new_peer_interval=61s}: zebra_network::peer_set::candidate_set: timeout waiting for peer service readiness or peer responses
2022-12-01T18:37:49.179017Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::sync::progress: finished initial sync to chain tip, using gossiped blocks sync_percent=100.000% current_height=Height(1898065) network_upgrade=Nu5 remaining_sync_blocks=1 time_since_last_state_block=2m
2022-12-01T18:38:06.318562Z  INFO {zebrad="79419b6" net="Main"}:{peer=Out("54.145.30.137:8233")}:msg_as_req{msg="inv"}:inbound:download_and_verify{hash=000000000124a266ab9ba9f167951917d8d0820b813d61d0bf2982a32422ac1d}: zebrad::components::inbound::downloads: downloaded and verified gossiped block height=Height(1898066)
2022-12-01T18:38:06.323066Z  INFO {zebrad="79419b6" net="Main"}:sync:try_to_sync: zebrad::components::sync: starting sync, obtaining new tips state_tip=Some(Height(1898066))
2022-12-01T18:38:12.324595Z  INFO {zebrad="79419b6" net="Main"}:sync:try_to_sync: zebrad::components::sync: exhausted prospective tip set
2022-12-01T18:38:12.324610Z  INFO {zebrad="79419b6" net="Main"}:sync: zebrad::components::sync: waiting to restart sync timeout=67s state_tip=Some(Height(1898066))
2022-12-01T18:38:20.720343Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::mempool::gossip: sending mempool transaction broadcast request=AdvertiseTransactionIds({Legacy(transaction::Hash("50f783f70c8e5021875a3bbe6bdeccd97e936cce71a885148a73699405c6e159"))})
2022-12-01T18:38:40.851730Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::mempool::gossip: sending mempool transaction broadcast request=AdvertiseTransactionIds({Legacy(transaction::Hash("dc72e145567c9f8af4212a2e2a64c9053844faeddf9c141d5202f786f67d4615"))})
2022-12-01T18:38:49.180422Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::sync::progress: finished initial sync to chain tip, using gossiped blocks sync_percent=100.000% current_height=Height(1898066) network_upgrade=Nu5 remaining_sync_blocks=0 time_since_last_state_block=0s
2022-12-01T18:38:51.698494Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::mempool::gossip: sending mempool transaction broadcast request=AdvertiseTransactionIds({Witnessed(WtxId { id: transaction::Hash("cd3fda32462c026f3375df3a21642fca7f8f26938ff27457026f7d71b351aafc"), auth_digest: AuthDigest("69a4ee98d51145f64b21c4e0e6220ff6af3f5caed0d394ef14ff6ad015974b5d") })})
2022-12-01T18:39:01.128618Z  INFO {zebrad="79419b6" net="Main"}:{peer=Out("18.217.102.40:8233")}:msg_as_req{msg="inv"}:inbound:download_and_verify{hash=0000000000ec43edc08b074906598611737785c682f31f5becf69b121e34a7f6}: zebrad::components::inbound::downloads: downloaded and verified gossiped block height=Height(1898067)
2022-12-01T18:39:01.527074Z  INFO write_blocks_from_channels{finalized_state=FinalizedState { network: Mainnet, debug_stop_at_height: None, db: ZebraDb { db: DiskDb { ephemeral: false, db: RocksDB { path: "/home/john/.cache/zebra/state/v25/mainnet" } } } } non_finalized_state=NonFinalizedState { chain_set: {}, network: Mainnet }}: zebra_state::service::non_finalized_state::chain: starting to rebuild note commitment trees after a non-finalized chain fork rebuilt_block_count=98 fork_height=Height(1898066) fork_tip=block::Hash("000000000124a266ab9ba9f167951917d8d0820b813d61d0bf2982a32422ac1d")
2022-12-01T18:39:01.626902Z  INFO write_blocks_from_channels{finalized_state=FinalizedState { network: Mainnet, debug_stop_at_height: None, db: ZebraDb { db: DiskDb { ephemeral: false, db: RocksDB { path: "/home/john/.cache/zebra/state/v25/mainnet" } } } } non_finalized_state=NonFinalizedState { chain_set: {}, network: Mainnet }}: zebra_state::service::non_finalized_state::chain: finished rebuilding note commitment trees after a non-finalized chain fork rebuild_time="99ms" rebuild_time_per_block="1ms" rebuilt_block_count=98 fork_height=Height(1898066) fork_tip=block::Hash("000000000124a266ab9ba9f167951917d8d0820b813d61d0bf2982a32422ac1d")
2022-12-01T18:39:01.667838Z  INFO {zebrad="79419b6" net="Main"}:{peer=Out("8.209.80.185:8233")}:msg_as_req{msg="inv"}:inbound:download_and_verify{hash=00000000004bdc2ad244dcfdbb9405d279bc751f6868dd54ab9523b3e7a4f59b}: zebrad::components::inbound::downloads: downloaded and verified gossiped block height=Height(1898067)
2022-12-01T18:39:19.326261Z  INFO {zebrad="79419b6" net="Main"}:sync:try_to_sync: zebrad::components::sync: starting sync, obtaining new tips state_tip=Some(Height(1898067))
2022-12-01T18:39:19.467658Z  INFO {zebrad="79419b6" net="Main"}:sync:try_to_sync: zebrad::components::sync: exhausted prospective tip set
2022-12-01T18:39:19.467677Z  INFO {zebrad="79419b6" net="Main"}:sync: zebrad::components::sync: waiting to restart sync timeout=67s state_tip=Some(Height(1898067))
2022-12-01T18:39:22.678809Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::mempool::gossip: sending mempool transaction broadcast request=AdvertiseTransactionIds({Legacy(transaction::Hash("5f849bb194e24ff5db8e39475aae5fb7a525ee9440c0345dd08047ecff740a5d"))})
2022-12-01T18:39:42.254570Z  INFO {zebrad="79419b6" net="Main"}:{peer=Out("120.24.79.67:8233")}:msg_as_req{msg="inv"}:inbound:download_and_verify{hash=000000000044f7b23410de825f0fb0219cef9daa51eacc1fee1e29c4b369eb13}: zebrad::components::inbound::downloads: downloaded and verified gossiped block height=Height(1898068)
2022-12-01T18:39:43.421312Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::mempool: resetting mempool: switched best chain, skipped blocks, or activated network upgrade tip_height=Height(1898068)
2022-12-01T18:39:43.421338Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::mempool: activating mempool: Zebra is close to the tip tip_height=Some(Height(1898068))
2022-12-01T18:39:48.422931Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::mempool::gossip: sending mempool transaction broadcast request=AdvertiseTransactionIds({Legacy(transaction::Hash("5f849bb194e24ff5db8e39475aae5fb7a525ee9440c0345dd08047ecff740a5d"))})
2022-12-01T18:39:49.181712Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::sync::progress: finished initial sync to chain tip, using gossiped blocks sync_percent=100.000% current_height=Height(1898068) network_upgrade=Nu5 remaining_sync_blocks=0 time_since_last_state_block=0s
2022-12-01T18:39:54.232080Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::mempool::gossip: sending mempool transaction broadcast request=AdvertiseTransactionIds({Legacy(transaction::Hash("2388b5cd87710a931f67f1c75ee7bfd42f00bee2ffc8d78ded64305730593a72"))})
2022-12-01T18:40:06.042703Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::mempool::gossip: sending mempool transaction broadcast request=AdvertiseTransactionIds({Legacy(transaction::Hash("c43eef30531be160d3af6ebbcb14a07bd076cfc0c917b41eb86edcff1ec01991"))})
2022-12-01T18:40:24.184824Z  INFO {zebrad="79419b6" net="Main"}:{peer=Out("162.19.139.182:8233")}:msg_as_req{msg="inv"}:inbound:download_and_verify{hash=00000000000ad1e2fd14f8640d4b6a269fcb1749d3566e34ce79d2b3f6744f09}: zebrad::components::inbound::downloads: downloaded and verified gossiped block height=Height(1898069)
2022-12-01T18:40:26.468720Z  INFO {zebrad="79419b6" net="Main"}:sync:try_to_sync: zebrad::components::sync: starting sync, obtaining new tips state_tip=Some(Height(1898069))
2022-12-01T18:40:30.396543Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::mempool::gossip: sending mempool transaction broadcast request=AdvertiseTransactionIds({Legacy(transaction::Hash("da911b0e9669055f3c701b9d72fdb7c0137ac1b8fd1893322cb781360d5368d5"))})
2022-12-01T18:40:31.409399Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::mempool::gossip: sending mempool transaction broadcast request=AdvertiseTransactionIds({Legacy(transaction::Hash("9ece0d755f6ac78a80d74d5dda6c35764d34d9963ca2f4b2b5f34612c5979931"))})
2022-12-01T18:40:32.469724Z  INFO {zebrad="79419b6" net="Main"}:sync:try_to_sync: zebrad::components::sync: exhausted prospective tip set
2022-12-01T18:40:32.469744Z  INFO {zebrad="79419b6" net="Main"}:sync: zebrad::components::sync: waiting to restart sync timeout=67s state_tip=Some(Height(1898069))
2022-12-01T18:40:45.578094Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::mempool::gossip: sending mempool transaction broadcast request=AdvertiseTransactionIds({Legacy(transaction::Hash("cc7b211de4e9117e90b5f2e04eaecfb5b94563316da1e88b132d0f3f27900ece"))})
2022-12-01T18:40:49.182709Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::sync::progress: finished initial sync to chain tip, using gossiped blocks sync_percent=100.000% current_height=Height(1898069) network_upgrade=Nu5 remaining_sync_blocks=0 time_since_last_state_block=0s
2022-12-01T18:40:53.475509Z  INFO {zebrad="79419b6" net="Main"}:{peer=Out("18.217.102.40:8233")}:msg_as_req{msg="inv"}:inbound:download_and_verify{hash=00000000015593c9aa6987207a4da6f1cd1f220ccc276b1f6b065abeec761dbe}: zebrad::components::inbound::downloads: downloaded and verified gossiped block height=Height(1898070)
^C2022-12-01T18:41:04.697536Z  INFO {zebrad="79419b6" net="Main"}:sig{kind=SignalKind(2) name="SIGINT"}: zebrad::signal: received SIGINT, starting shutdown
2022-12-01T18:41:04.697579Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::tokio: waiting for async tokio tasks to shut down TOKIO_SHUTDOWN_TIMEOUT=20s
2022-12-01T18:41:04.697975Z  INFO write_blocks_from_channels{finalized_state=FinalizedState { network: Mainnet, debug_stop_at_height: None, db: ZebraDb { db: DiskDb { ephemeral: false, db: RocksDB { path: "/home/john/.cache/zebra/state/v25/mainnet" } } } } non_finalized_state=NonFinalizedState { chain_set: {}, network: Mainnet }}: zebra_state::service::finalized_state::disk_db: forcing shutdown of a state database with multiple active instances path="/home/john/.cache/zebra/state/v25/mainnet"
2022-12-01T18:41:04.698010Z  INFO write_blocks_from_channels{finalized_state=FinalizedState { network: Mainnet, debug_stop_at_height: None, db: ZebraDb { db: DiskDb { ephemeral: false, db: RocksDB { path: "/home/john/.cache/zebra/state/v25/mainnet" } } } } non_finalized_state=NonFinalizedState { chain_set: {}, network: Mainnet }}: zebra_state::service::finalized_state::disk_db: flushing database to disk path="/home/john/.cache/zebra/state/v25/mainnet"
2022-12-01T18:41:04.698442Z  INFO {zebrad="79419b6" net="Main"}: zebra_network::address_book_updater: stopping address book updater error=Err(AllAddressBookUpdaterSendersClosed)
2022-12-01T18:41:24.698198Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::tokio: shutting down Zebra
2022-12-01T18:41:24.698221Z  INFO {zebrad="79419b6" net="Main"}: zebrad::commands::start: stopping zebrad

john@john-Latitude-5490:~$ zebrad start
2022-12-01T18:41:27.422601Z  INFO zebrad::components::tracing::component: started tracing component filter="info" TRACING_STATIC_MAX_LEVEL=LevelFilter::INFO LOG_STATIC_MAX_LEVEL=Info
2022-12-01T18:41:27.422620Z  INFO zebrad::application: Diagnostic Metadata:
version: 1.0.0-rc.1
Zcash network: Mainnet
state version: 25
branch: master
git commit: 79419b6
commit timestamp: 2022-11-01T22:35:21Z
target triple: x86_64-unknown-linux-gnu
build profile: release
2022-12-01T18:41:27.422644Z  INFO {zebrad="79419b6" net="Main"}: zebrad::application: initialized rayon thread pool for CPU-bound tasks num_threads=8
2022-12-01T18:41:27.423118Z  INFO {zebrad="79419b6" net="Main"}: zebrad::commands::start: Starting zebrad
2022-12-01T18:41:27.423200Z  INFO {zebrad="79419b6" net="Main"}: zebrad::commands::start: config=ZebradConfig { consensus: Config { checkpoint_sync: true, debug_skip_parameter_preload: false }, metrics: Config { endpoint_addr: None }, network: Config { listen_addr: 0.0.0.0:8233, network: Mainnet, initial_mainnet_peers: {"dnsseed.z.cash:8233", "dnsseed.str4d.xyz:8233", "mainnet.seeder.zfnd.org:8233", "mainnet.is.yolo.money:8233"}, initial_testnet_peers: {"dnsseed.testnet.z.cash:18233", "testnet.seeder.zfnd.org:18233", "testnet.is.yolo.money:18233"}, peerset_initial_target_size: 25, crawl_new_peer_interval: 61s }, state: Config { cache_dir: "/home/john/.cache/zebra", ephemeral: false, debug_stop_at_height: None, delete_old_database: true }, tracing: Config { use_color: true, force_use_color: false, filter: None, buffer_limit: 128000, endpoint_addr: None, flamegraph: None, use_journald: false }, sync: Config { download_concurrency_limit: 50, checkpoint_verify_concurrency_limit: 800, full_verify_concurrency_limit: 20, parallel_cpu_threads: 0 }, mempool: Config { tx_cost_limit: 80000000, eviction_memory_time: 3600s, debug_enable_at_height: None }, rpc: Config { listen_addr: Some(127.0.0.1:8232), parallel_cpu_threads: 0, debug_force_finished_sync: false } }
2022-12-01T18:41:27.423262Z  INFO {zebrad="79419b6" net="Main"}: zebrad::commands::start: initializing node state
2022-12-01T18:41:27.426651Z  INFO {zebrad="79419b6" net="Main"}: zebrad::commands::start: opening database, this may take a few minutes
2022-12-01T18:41:27.426802Z  INFO zebra_state::service::finalized_state::disk_db: the open file limit is high enough for Zebra current_limit=1024 min_limit=512 ideal_limit=1024
2022-12-01T18:41:34.537712Z  INFO zebra_state::service::finalized_state::disk_db: Opened Zebra state cache at /home/john/.cache/zebra/state/v25/mainnet
2022-12-01T18:41:34.539126Z  INFO zebra_state::service::finalized_state: loaded Zebra state cache tip=Some((Height(1897971), block::Hash("00000000011fe66d4109bd3879c7ad19414c7f945e68a6f58db8c7e77adddd8c")))
2022-12-01T18:41:34.539282Z  INFO zebra_state::service: created new read-only state service
2022-12-01T18:41:34.539303Z  INFO zebra_state::service: starting legacy chain check
2022-12-01T18:41:34.539862Z  INFO zebra_state::service: cached state consensus branch is valid: no legacy chain found
2022-12-01T18:41:34.539937Z  INFO {zebrad="79419b6" net="Main"}: zebrad::commands::start: initializing network
2022-12-01T18:41:34.539957Z  INFO {zebrad="79419b6" net="Main"}:open_listener{addr=0.0.0.0:8233}: zebra_network::peer_set::initialize: Trying to open Zcash protocol endpoint at 0.0.0.0:8233...
2022-12-01T18:41:34.539990Z  INFO {zebrad="79419b6" net="Main"}:open_listener{addr=0.0.0.0:8233}: zebra_network::peer_set::initialize: Opened Zcash protocol endpoint at 0.0.0.0:8233
2022-12-01T18:41:34.540019Z  INFO {zebrad="79419b6" net="Main"}: zebra_network::address_book_updater: starting the address book updater
2022-12-01T18:41:34.688832Z  INFO {zebrad="79419b6" net="Main"}:add_initial_peers: zebra_network::config: resolved seed peer IP addresses seed="dnsseed.str4d.xyz:8233" remote_ip_count=34
2022-12-01T18:41:34.694568Z  INFO {zebrad="79419b6" net="Main"}:add_initial_peers: zebra_network::config: resolved seed peer IP addresses seed="dnsseed.z.cash:8233" remote_ip_count=25
2022-12-01T18:41:34.724313Z  INFO {zebrad="79419b6" net="Main"}:add_initial_peers: zebra_network::config: resolved seed peer IP addresses seed="mainnet.is.yolo.money:8233" remote_ip_count=3
2022-12-01T18:41:39.541518Z  INFO {zebrad="79419b6" net="Main"}:add_initial_peers: zebra_network::config: DNS timeout resolving peer IP addresses host="mainnet.seeder.zfnd.org:8233" e=Elapsed(())
2022-12-01T18:41:39.541549Z  INFO {zebrad="79419b6" net="Main"}:add_initial_peers: zebra_network::config: Retrying peer DNS resolution host="mainnet.seeder.zfnd.org:8233" retry_count=1
2022-12-01T18:41:44.542370Z  INFO {zebrad="79419b6" net="Main"}:add_initial_peers: zebra_network::peer_set::initialize: limiting the initial peers list from 59 to 25
2022-12-01T18:41:44.542462Z  INFO {zebrad="79419b6" net="Main"}:add_initial_peers: zebra_network::peer_set::initialize: connecting to initial peer set initial_peer_count=25 initial_peers={104.233.147.162:8233, 3.16.30.39:8233, 5.9.74.158:8233, 51.77.64.61:8233, 8.218.11.43:8233, 18.117.148.170:8233, [2a11:3b80::225:90ff:fef3:f72]:8233, 8.209.65.101:8233, [2a01:4f9:4b:42cb::2]:8233, [2a01:4f9:4a:1e15::2]:8233, 18.189.228.115:8233, 135.181.79.230:8233, [2a02:7b40:c287:513d::1]:8233, 109.190.117.131:8233, [2620:a6:2000:1:1:0:3:d555]:8233, 46.4.65.10:8233, [2a01:4f9:c010:31a6::1]:8233, 46.4.192.189:8233, 194.135.81.61:8233, 47.254.69.198:8233, 54.84.155.205:8233, [2a01:4f8:140:2393::2]:8233, 65.21.40.28:8233, 35.233.224.178:8233, 23.129.64.30:8233}
2022-12-01T18:41:44.693292Z  INFO {zebrad="79419b6" net="Main"}:add_initial_peers: zebra_network::peer_set::initialize: an initial peer connection failed successes=2 errors=1 addr=[2a11:3b80::225:90ff:fef3:f72]:8233 e=Network is unreachable (os error 101)
2022-12-01T18:41:44.743598Z  INFO {zebrad="79419b6" net="Main"}:add_initial_peers: zebra_network::peer_set::initialize: an initial peer connection failed successes=2 errors=2 addr=[2a01:4f9:4b:42cb::2]:8233 e=Network is unreachable (os error 101)
2022-12-01T18:41:44.768740Z  INFO {zebrad="79419b6" net="Main"}:add_initial_peers: zebra_network::peer_set::initialize: an initial peer connection failed successes=2 errors=3 addr=[2a01:4f9:4a:1e15::2]:8233 e=Network is unreachable (os error 101)
2022-12-01T18:41:44.843579Z  INFO {zebrad="79419b6" net="Main"}:add_initial_peers: zebra_network::peer_set::initialize: an initial peer connection failed successes=3 errors=4 addr=[2a02:7b40:c287:513d::1]:8233 e=Network is unreachable (os error 101)
2022-12-01T18:41:44.893193Z  INFO {zebrad="79419b6" net="Main"}:add_initial_peers: zebra_network::peer_set::initialize: an initial peer connection failed successes=4 errors=5 addr=[2620:a6:2000:1:1:0:3:d555]:8233 e=Network is unreachable (os error 101)
2022-12-01T18:41:44.943930Z  INFO {zebrad="79419b6" net="Main"}:add_initial_peers: zebra_network::peer_set::initialize: an initial peer connection failed successes=6 errors=6 addr=[2a01:4f9:c010:31a6::1]:8233 e=Network is unreachable (os error 101)
2022-12-01T18:41:45.068197Z  INFO {zebrad="79419b6" net="Main"}:add_initial_peers: zebra_network::peer_set::initialize: an initial peer connection failed successes=8 errors=7 addr=[2a01:4f8:140:2393::2]:8233 e=Network is unreachable (os error 101)
2022-12-01T18:41:45.215737Z  INFO {zebrad="79419b6" net="Main"}:add_initial_peers: zebra_network::peer_set::initialize: an initial peer connection failed successes=12 errors=8 addr=46.4.65.10:8233 e=Peer offered obsolete version: Version(170002)
2022-12-01T18:41:48.045597Z  INFO {zebrad="79419b6" net="Main"}:add_initial_peers: zebra_network::peer_set::initialize: an initial peer connection failed successes=16 errors=9 addr=54.84.155.205:8233 e=request timed out
2022-12-01T18:41:48.045633Z  INFO {zebrad="79419b6" net="Main"}:add_initial_peers: zebra_network::peer_set::initialize: finished connecting to initial seed peers handshake_success_total=16 handshake_error_total=9 outbound_connections=17
2022-12-01T18:41:48.045715Z  INFO {zebrad="79419b6" net="Main"}: zebra_network::peer_set::initialize: sending initial request for peers active_initial_peer_count=17
2022-12-01T18:41:48.046114Z  INFO {zebrad="79419b6" net="Main"}: zebrad::commands::start: initializing verifiers
2022-12-01T18:41:48.046170Z  INFO {zebrad="79419b6" net="Main"}:crawl_and_dial{new_peer_interval=61s}: zebra_network::peer_set::initialize: starting the peer address crawler crawl_new_peer_interval=61s outbound_connections=17
2022-12-01T18:41:48.049172Z  INFO {zebrad="79419b6" net="Main"}:init{config=Config { checkpoint_sync: true, debug_skip_parameter_preload: false } network=Mainnet debug_skip_parameter_preload=false}: zebra_consensus::chain: initializing chain verifier tip=Some((Height(1897971), block::Hash("00000000011fe66d4109bd3879c7ad19414c7f945e68a6f58db8c7e77adddd8c"))) max_checkpoint_height=Height(1862281)
2022-12-01T18:41:48.049193Z  INFO {zebrad="79419b6" net="Main"}: zebrad::commands::start: initializing syncer
2022-12-01T18:41:48.049199Z  INFO {zebrad="79419b6" net="Main"}: zebrad::commands::start: initializing mempool
2022-12-01T18:41:48.049207Z  INFO {zebrad="79419b6" net="Main"}: zebra_rpc::server: Trying to open RPC endpoint at 127.0.0.1:8232...
2022-12-01T18:41:48.049296Z  INFO {zebrad="79419b6" net="Main"}: zebrad::commands::start: spawned initial Zebra tasks
2022-12-01T18:41:48.049308Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::sync::gossip: initializing block gossip task
2022-12-01T18:41:48.049319Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::mempool::crawler: initializing mempool crawler task
2022-12-01T18:41:48.049327Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::mempool::queue_checker: initializing mempool queue checker task
2022-12-01T18:41:48.049330Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::mempool::gossip: initializing transaction gossip task
2022-12-01T18:41:48.049415Z  INFO {zebrad="79419b6" net="Main"}: zebra_state::config: checking for old database versions
2022-12-01T18:41:48.050115Z  INFO {zebrad="79419b6" net="Main"}:sync:try_to_sync: zebrad::components::sync: starting sync, obtaining new tips state_tip=Some(Height(1897971))
2022-12-01T18:41:48.050461Z  INFO {zebrad="79419b6" net="Main"}: zebra_rpc::server: Opened RPC endpoint at 127.0.0.1:8232
2022-12-01T18:41:48.052553Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::sync::progress: estimated progress to chain tip sync_percent=99.995% current_height=Height(1897971) network_upgrade=Nu5 remaining_sync_blocks=96 time_since_last_state_block=0s
2022-12-01T18:41:48.059515Z  INFO {zebrad="79419b6" net="Main"}:init{config=Config { checkpoint_sync: true, debug_skip_parameter_preload: false } network=Mainnet debug_skip_parameter_preload=false}: zebra_consensus::primitives::groth16::params: checking and loading Zcash Sapling and Sprout parameters
2022-12-01T18:41:48.071660Z  INFO {zebrad="79419b6" net="Main"}: zebra_state::config: finished old database version cleanup task
2022-12-01T18:41:59.235663Z  INFO {zebrad="79419b6" net="Main"}:init{config=Config { checkpoint_sync: true, debug_skip_parameter_preload: false } network=Mainnet debug_skip_parameter_preload=false}: zebra_consensus::chain: Groth16 pre-download and check task finished
2022-12-01T18:42:06.745050Z  INFO {zebrad="79419b6" net="Main"}:sync:try_to_sync: zebrad::components::sync: extending tips tips.len=1 in_flight=19 extra_hashes=0 lookahead_limit=20 state_tip=Some(Height(1898050))
2022-12-01T18:42:06.877946Z  INFO {zebrad="79419b6" net="Main"}:sync:try_to_sync: zebrad::components::sync: exhausted prospective tip set
2022-12-01T18:42:06.877965Z  INFO {zebrad="79419b6" net="Main"}:sync: zebrad::components::sync: waiting to restart sync timeout=67s state_tip=Some(Height(1898053))
2022-12-01T18:42:48.053600Z  INFO {zebrad="79419b6" net="Main"}: zebrad::components::sync::progress: estimated progress to chain tip sync_percent=100.000% current_height=Height(1898069) network_upgrade=Nu5 remaining_sync_blocks=2 time_since_last_state_block=0s

Version Info

john@john-Latitude-5490:~$ neofetch
            .-/+oossssoo+/-.               john@john-Latitude-5490
        `:+ssssssssssssssssss+:`           -----------------------
      -+ssssssssssssssssssyyssss+-         OS: Ubuntu 20.04.5 LTS x86_64
    .ossssssssssssssssssdMMMNysssso.       Host: Latitude 5490
   /ssssssssssshdmmNNmmyNMMMMhssssss/      Kernel: 5.4.0-132-lowlatency
  +ssssssssshmydMMMMMMMNddddyssssssss+     Uptime: 14 days, 2 hours, 43 mins
 /sssssssshNMMMyhhyyyyhmNMMMNhssssssss/    Packages: 3196 (dpkg), 19 (snap)
.ssssssssdMMMNhsssssssssshNMMMdssssssss.   Shell: bash 5.0.17
+sssshhhyNMMNyssssssssssssyNMMMysssssss+   Resolution: 1920x1080
ossyNMMMNyMMhsssssssssssssshmmmhssssssso   DE: GNOME
ossyNMMMNyMMhsssssssssssssshmmmhssssssso   WM: Mutter
+sssshhhyNMMNyssssssssssssyNMMMysssssss+   WM Theme: Adwaita
.ssssssssdMMMNhsssssssssshNMMMdssssssss.   Theme: Yaru [GTK2/3]
 /sssssssshNMMMyhhyyyyhdNMMMNhssssssss/    Icons: Yaru [GTK2/3]
  +sssssssssdmydMMMMMMMMddddyssssssss+     Terminal: gnome-terminal
   /ssssssssssshdmNNNNmyNMMMMhssssss/      CPU: Intel i5-8350U (8) @ 3.600GHz
    .ossssssssssssssssssdMMMNysssso.       GPU: Intel UHD Graphics 620
      -+sssssssssssssssssyyyssss+-         Memory: 2704MiB / 7811MiB
        `:+ssssssssssssssssss+:`
            .-/+oossssoo+/-.

john@john-Latitude-5490:~$ rustc --version
rustc 1.65.0 (897e37553 2022-11-02)
john@john-Latitude-5490:~$ go version
go version go1.18.8 linux/amd64
john@john-Latitude-5490:~$ zebrad version
zebrad 1.0.0-rc.1

Downloaded 83 crates (13.4 MB) in 3.93s (largest was `plotters` at 8.6 MB)
tower-batch v0.2.32 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/tower-batch)
├── ed25519-zebra v3.1.0
├── tower-fallback v0.2.32 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/tower-fallback)
│   └── zebra-test v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-test)
├── zebra-consensus v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-consensus)
│   ├── tower-batch v0.2.32 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/tower-batch) (*)
│   ├── tower-fallback v0.2.32 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/tower-fallback) (*)
│   ├── zebra-chain v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-chain)
│   │   ├── ed25519-zebra v3.1.0 (*)
│   │   └── zebra-test v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-test) (*)
│   │   └── zebra-test v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-test) (*)
│   ├── zebra-script v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-script)
│   │   └── zebra-chain v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-chain) (*)
│   │   └── zebra-test v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-test) (*)
│   └── zebra-state v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-state)
│       ├── zebra-chain v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-chain) (*)
│       └── zebra-test v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-test) (*)
│       ├── zebra-chain v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-chain) (*)
│       └── zebra-test v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-test) (*)
│   ├── zebra-chain v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-chain) (*)
│   ├── zebra-state v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-state) (*)
│   └── zebra-test v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-test) (*)
└── zebra-test v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-test) (*)
tower-fallback v0.2.32 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/tower-fallback) (*)
zebra-chain v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-chain) (*)
zebra-client v1.0.0-beta.0 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-client)
zebra-consensus v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-consensus) (*)
zebra-network v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-network)
└── zebra-chain v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-chain) (*)
├── zebra-chain v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-chain) (*)
└── zebra-test v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-test) (*)
zebra-node-services v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-node-services)
└── zebra-chain v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-chain) (*)
zebra-rpc v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-rpc)
├── zebra-chain v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-chain) (*)
├── zebra-network v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-network) (*)
├── zebra-node-services v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-node-services) (*)
└── zebra-state v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-state) (*)
├── zebra-chain v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-chain) (*)
├── zebra-state v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-state) (*)
└── zebra-test v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-test) (*)
zebra-script v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-script) (*)
zebra-state v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-state) (*)
zebra-test v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-test) (*)
zebra-utils v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-utils)
├── zebra-chain v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-chain) (*)
├── zebra-consensus v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-consensus) (*)
└── zebra-state v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-state) (*)
zebrad v1.0.0-rc.1 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebrad)
├── zebra-chain v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-chain) (*)
├── zebra-consensus v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-consensus) (*)
├── zebra-network v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-network) (*)
├── zebra-node-services v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-node-services) (*)
├── zebra-rpc v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-rpc) (*)
└── zebra-state v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-state) (*)
├── zebra-chain v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-chain) (*)
├── zebra-consensus v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-consensus) (*)
├── zebra-network v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-network) (*)
├── zebra-state v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-state) (*)
└── zebra-test v1.0.0-beta.17 (/home/john/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6/zebra-test) (*)
john@john-Latitude-5490:~/.cargo/git/checkouts/zebra-d0d93d7ded255019/79419b6$

Thanks, what fork and commit of lightwalletd are you using?

@mpguerra this looks like an argument parsing error in lightwalletd RPCs. And a mistake in some of our lightwalletd documentation.
Can we schedule it for our next sprint?
It's not urgent, so anyone on the team could do these fixes.

v0.0.0.0-dev It was built with git clone https://github.com/zcash/lightwalletd.git so I assume the current branch but it doesn't list that with the lightwalletd version flag

It was built with git clone https://github.com/zcash/lightwalletd.git

Thanks! It will be using the latest commit on the master branch.
We actually test Zebra with another fork, https://github.com/adityapk00/lightwalletd :
https://github.com/ZcashFoundation/zebra/blob/afdb3a7013bcadca87d38da443645297f2ca60db/.github/workflows/zcash-lightwalletd.yml#L60
which seems to work fine:

{"app":"lightwalletd","level":"info","msg":"Waiting for block: 1896841","time":"2022-12-01T03:56:07Z"}
https://github.com/ZcashFoundation/zebra/actions/runs/3592200664/jobs/6048302550#step:8:211

Zebra should work with both forks, but we might want to switch to the one we're testing in the instructions.

That makes sense, I'll try adityas as well to see if it isn't resolved on my end by that

That fixed it. The zecwallet lite one seems a little more behind currently but yeah :+1:, close when yall are satisified it's squared away

That fixed it. The zecwallet lite one seems a little more behind currently but yeah 👍, close when yall are satisified it's squared away

I think we should fix the docs, and maybe fix the error message from the RPC.
(I'm not sure if anyone ever tested those docs, or if it's a new breaking change in zcash/lightwalletd.)

The native lightwalletd instructions for using with zcashd work. All of the instructions for zebra lightwalletd (like using empty conf) work if you use adityas version it seems, that's the only thing different I believe. Why they diverge idk

Hey team! Please add your planning poker estimate with Zenhub @arya2 @conradoplg @dconnolly @oxarbitrage @teor2345 @upbqdn

authors: autotunafish mpguerra teor2345

repo: ZcashFoundation/zebra


text:
Validate spends of transparent coinbase outputs

Motivation
Zebra needs to check the consensus rules that restrict how transparent outputs of coinbase transactions can be spent.
Specifications
See #2329 and #2330.
Designs
These designs are more complex than we actually need:
https://github.com/ZcashFoundation/zebra/blob/main/book/src/dev/rfcs/0004-asynchronous-script-verification.md , particularly the changes in PR #1970
https://github.com/ZcashFoundation/zebra/blob/main/book/src/dev/rfcs/0005-state-updates.md#requestawaitspendableutxo--outpoint-outpoint-spend_height-height-spend_restriction-spendrestriction-
Solution
Implementation:

Add a CoinbaseSpendRestriction enum and Transaction method
Check UTXO spendability during contextual validation, using known valid UTXOs

Test fixes:

Skip created UTXOs in the genesis block in arbitrary block chains
Refactor out a new_transaction_ordered_outputs function
Add Transaction::outputs_mut for tests
Only spend valid UTXOs in arbitrary block chains

Closes #2329
Closes #2330
Closes #2410
WIP Tests
Skip

[x] non-coinbase UTXOs

existing unit tests, acceptance tests, and cached state tests

Success

[x] coinbase UTXO spent to shielded outputs after 100 or more blocks

existing unit tests, acceptance tests, and cached state tests

[x] coinbase UTXO spent to shielded outputs after exactly 100 blocks

modified existing state request test

Failure

[ ] coinbase UTXO spent to non-shielded outputs after 100 or more blocks
[x] coinbase UTXO spent to shielded outputs after less than 100 blocks

Test coverage

[x] make the proptest chain lengths slightly longer (ideally using a single constant)
[x] make sure that restriction-checked and unchecked proptest chains contain UTXO prevout spends

We could also do tests for finalized/non-finalized state, and both non-shielded and immature. But these tests are the essential ones.
I'm also running a full sync test locally on mainnet and testnet.
Review
I'd like an initial review from @jvff while I'm working on the rest of the tests.
Reviewer Checklist

[ ] Code implements Specs and Designs
[ ] Tests for Expected Behaviour
[ ] Tests for Errors

Follow Up Work
Move the design changes in PR #1970 to an "alternatives" section, and explain how the simpler design works.
(Or just revert most of PR #1970.)

This change is

I just worked out that this PR is blocking the next PR after #2486.
There's a chain of about 5 PRs we need to do there.
So I might just admin-merge this PR after CI passes.
After the last approval, I added one requested test and some comments.

Admin-merged, because the PR was approved before minor changes, and it's blocking other work


text:
Add mempool metrics

Motivation

Specifications

Designs

Solution

Review
Just a draft to show the current work, and a question: is it worthwhile to track transactions_serialized_size in this slightly error-prone way to avoid iterating the entire list to compute the total size every time?

Reviewer Checklist

[ ] Code implements Specs and Designs
[ ] Tests for Expected Behaviour
[ ] Tests for Errors

Follow Up Work

@dconnolly I just noticed that this calculation is very similar to the eviction weight from ZIP-401 in #2780.
(But it's not the same, because small transactions are given the minimum weight.)
So we might want to merge this PR pretty quickly to avoid conflicts.

@dconnolly I just noticed that this calculation is very similar to the eviction weight from ZIP-401 in #2780. (But it's not the same, because small transactions are given the minimum weight.)
So we might want to merge this PR pretty quickly to avoid conflicts.

I've moved this out of draft and will keep working on the remaining metrics in a separate PR to make this easier.

I've also just learned that increment_gauge (and decrement) exists  in more recent metrics so we can use that in this PR and not keep track of the total size, but that will have to be done in #2780 anyway. But we'd need to update metrics. Let me know what's better.


text:
fix(build): put gRPC tests behind an optional feature flag

TODO (teor)
Split this PR into different sets of changes, after checking it all works.
Motivation
This fixes a production build failure introduced by the gRPC tests in #3512.
Closes #4367.
Specifications
https://doc.rust-lang.org/cargo/reference/features.html
https://doc.rust-lang.org/cargo/reference/build-scripts.html
Designs
Put the gRPC tests and dependencies behind an optional lightwalletd-grpc-tests feature, so they don't get compiled in production builds.
Solution
TODO: add details here after split
Testing
The "Install zebrad from lockfile without cache" CI job runs without these dependencies, and the gRPC tests run with them. So this change is already covered by existing tests.
Review
This PR needs to be split before review.
Reviewer Checklist

[ ] Code implements Specs and Designs
[ ] Tests for Expected Behaviour
[ ] Tests for Errors

Oops, but at least this is an easy fix:

exec cargo test --locked --release --features enable-sentry,lightwalletd-grpc-tests --package zebra-state --lib -- --nocapture --include-ignored with_fake_activation_heights
error: none of the selected packages contains these features: enable-sentry, lightwalletd-grpc-tests

https://github.com/ZcashFoundation/zebra/runs/6368707158?check_suite_focus=true#step:3:137


text:
Add "Remaining balance" to Confirm Transaction window

When a user presses the Send button, a Confirm Transaction window pops up. I would like to see the remaining balance in the sending address after the transaction is sent. For example if I start with 1 ZEC, and send 0.5 with a 0.0001 fee then it should show a remaining balance of 0.4999 in this window.

I'm in two minds about this.
On one hand, I want the confirm window to be very very simple, showing exactly the information that will be passed to zcashd. This is a critical window, since it confirms the exact data that will be sent to zcashd, and I want to minimize the surface to keep bugs away. Showing an additional field that is not being sent might cause cognitive overhead (eg., confuse the remaining balance with amount sent).
Maybe we should show this field elsewhere? Like maybe on the send tab, at the bottom or somewhere?
What do you think?

I can understand the desire to keep the confirmation window simple. Putting the remaining balance on the send screen would be a fair compromise to me.

Maybe we can have a "Change from Tx" row, which shows how much balance will remain. Although it might not be technically accurate, since all UTXOs might not be included by zcashd in the Tx, and the "change" from the Tx might be lower than the total remaining balance.

Although it might not be technically accurate, since all UTXOs might not be included by zcashd in the Tx, and the "change" from the Tx might be lower than the total remaining balance.

That is my thought as well, what I'm looking for is the total remaining balance not just the change amount (which as you point out can be different than the remaining balance).
I can also accept if you aren't able to accommodate this feature request. I appreciate your consideration and responsiveness to these issues I opened!

In v0.5.5

repo: ZcashFoundation/zec-qt-wallet


text:
Multiple columns in the tree view.

[Name | Rev | Description | Model Name]
These values exist on the tree items.
treeItem.getParameter('Rev').getValue()
treeItem.getParameter('Description').getValue()

Note: we can populate the columns with data later. For now it would be nice to just have the layout working.

const populateRev = ()=> {
   const revParam = item.getParameter('Rev')
   if (revParam) revValue = revParam.getValue()
}

['Rev', 'Description', 'Model Name']

resizable columns

https://www.brainbell.com/javascript/making-resizable-table-js.html

repo: ZeaInc/zea-svelte-template


text:
🛑 Game Server Proxy (prod) is down

In 83461b0, Game Server Proxy (prod) (https://proxy.zebr-a.com/api/Version) was down:

HTTP code: 502
Response time: 323 ms

Resolved: Game Server Proxy (prod) is back up in cc9b40b.

repo: Zebrainy/upptime


text:
add p256 curve support

lots of clone() had to be added to cryptographic_primites/* because SecretKey does not implement the Copy trait (because it zeroizes by default)

@ra-- see comment above - if it works (I think it does) - you can remove significant amount of the clones

question : if you use Scalar instead of SecretKey in:
pub type SK = SecretKey;
does it solves the clone issue ? (Scalar can be copied)

question : if you use Scalar instead of SecretKey in:
pub type SK = SecretKey;
does it solves the clone issue ? (Scalar can be copied)

It does solve the clone issue. See https://github.com/ZenGo-X/curv/pull/87/commits/e910270f0facac3e6e23c793dd9038512d130822

authors: omershlo ra--

repo: ZenGo-X/curv


text:
Sodium not conficting with cheatutils

PLS HELP

What?

authors: SSShadowPheonix Zergatul

repo: Zergatul/cheatutils


text:
fix: Verify modified files weren't just created

Due to https://docs.rs/notify/7.0.0/notify/#editor-behaviour, we cannot guarantee that a "Modified" event isn't an "Added" event. Since our FsIndex already tracks the files we know about, we'll check if it is aware of the file that was "modified", inserting it if not.

Ok, thanks! Seems to work better. 😄

authors: Zheoni kaylee-kiako

repo: Zheoni/cooklang-chef


text:
can not download the KITTI test dataset from the provided Google Drive website

Thank you for excellent works ! But I can not download the KITTI test dataset from the provided Google Drive website, could you please privide the BaiduNetdisk Download that I will appreciate.

Thank you for your attention. The Baidu Netdisk for downloading the KITTI test dataset is now available. You can find it in readme file.

Thank you very much!


text:
editor preview errors

for example ImageView fails to load SVG (which is pretty obvious as SVG loading is not available in edit mode)

fixed

repo: ZieIony/Carbon


text:
Create use case

Create a use case to visualize the functional analysis of the project.

@axd1967 Can you suggest software to design this use case? Or shall I write it down in plain text ( we obviously have the assignment document already, so I guess no?)?

(I liked StarUML http://sourceforge.net/projects/staruml/ but that is Windows, and now paying)
a flat text file Project/doc/usecases.md or something (advantage over the wiki: it will evolve together with the repo code)
list all the use cases
see https://en.wikipedia.org/wiki/Use_case#Examples, limit to

Title (include an ID )
Brief, short description

tip: when creating branches such as Analysis, usually this goes together with some task, or issue.
So, make sure to have an issue that goes with a branch. also, make a habit to name your branches like this:
issue/<issuenumer>_sometext, e.g.
issue/234_analysis
you will discover in you .git/refs/ (look under heads  and remotes) that all your branches are grouped in a subdirectory "issues/". some IDE also allow to take profit from this (e.g. SourceTree).

[ ] make sure that each use case refers to a GitHub issue where the use case is implemented

See 9863b61 for use cases, this okay? Seems good enough for this project.

there are file extensions missing?

Apologies: fa3a362

a user has many ratings
a message has many ratings
a system user is not a superuser
a superuser is a user (otherwise a superuser cannot behave like a normal user)

System is not  a user. It is meant to illustrate that superusers can be appointed either manually by an administrator, or automatically by an automated script  ( #8 ).

Could you please indicate what part of the analysis you're referring to?

I would not say that "system IS A SuperUser", because System will never create threads
but a Superuser should also be a user, otherwise he can't participate as normal user.

indeed , system will appoint a Superuser, but that is a use case; don't use inheritance (-->)  from Systemuser to Superuser for that.

That makes sense :).
Patched cd327791dac130997a21838e02b0372e11b89f78 . Okay to merge with master?

yup

(btw, you removed the System user and the (promoe) case? )

careful: there are also changes in the other diagram:
(see remote 64fafe53cfa443986e2c2cb085655713794040c2)

Added relation between user and rating (93aab3ca9b2075274292a91bd89165fdc4602f9f). Did not implement area since all areas are static and hard scripted.

Assuming closed and merging if no reply follows.

Merged.

(fetch -> I've added a few more ideas)

about Area: you probably need to add two fields to User class
fetch!

Thanks! :) I cannot seem to find your commit though, are you referring to 76e01ee ?

I'm still having doubts regarding the area class. The properties you mention are irrelevant since they are hardcoded directly into the html. I'm not dynamically loading any area content (except for the messages). The only good reason I can think of for creating a separate area class, is if we had any plans to increase the amount of available domains. But since we're definitely not doing that, I fail to see any purpose for the extra class.

you will have to refer to specific areas from user records (area1, area2). now you are using strings for that, but you will have to store the area information "somehow", probably in a directory, or in a table.
when I write "class", I don't mean that you have to end up with a class in your code (C#, C++, Java, db table...). A class in analysis is simply a concept, an object that has properties. In the implementation there might be no physical class, but somewhere you will be able to say: "here is an (instance of an) area" and be able to refer to it (eg by using its name, as you intend to do). therefore, that is an object, that has properties, and thus it is an instance of a class, and that is how you can document it in the Class analysis diagram.

Thank you for the clarification! :+1:

(idem here, add a link to the Use case diagram in the top comment. not necessary)

repo: ZiggyMaes/NMCT-Server-Side-Applications


text:
今天用返回的的信息请求接口提示重新登陆

{
    "datas": {
        "WEC-REDIRECTURL": "/portal/login",
        "WEC-HASLOGIN": false
    },
    "code": 0,
    "message": "successs"
}

安徽师范大学的疫情签到接口
https://ahnu.campusphere.net/wec-counselor-collector-apps/stu/collector/queryCollectorProcessingList

如果我没记错的话，你们学校是走的这个学校安徽商贸职业技术学院的认证

所以 有参考吗？

你把学校配置改成那个不就好了吗

你好我好像没有看到安徽商贸职业技术学院的认证，请问可以说的详细点吗

只需要把auto-submit项目里面的config.yml里面的school改了就可以了，可能会遇到一些小问题，比如今日校园更新了api，加群看看公告，或者你看看pr和issues，就能搞定，这个模拟登陆的项目有空你可以慢慢研究，希望你能从中学到一些东西吧，goot luck

authors: ZimoLoveShuang zerodayZHOUXUTIAN

repo: ZimoLoveShuang/wisedu-unified-login-api


text:
🛑 blog.zinglix.xyz is down

In b82239c, blog.zinglix.xyz (https://blog.zinglix.xyz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: blog.zinglix.xyz is back up in b7c2d7e.

repo: ZingLix/blog-mirror-uptime