text:
simple-view-behavior/app/src/main/res/layout/activity_profile.xml

in this file,if i change the textview "HI!" by findViewIyId,   it's will have a bug.
the image will do not move to the top
java code
      TextView detial_name = (TextView) bottomsheet1.findViewById(R.id.name_detial
https://github.com/zoonooz/simple-view-behavior/issues/ne
![Uploading Screenshot_2016-05-20-18-13-44.png…]()
![Uploading Screenshot_2016-05-20-18-13-47.png…]()

w);
//        Picasso.with(getApplicationContext())
//                .load("http://192.168.1.106/enterprise/Public/" + detialInfo.getData().getTutor_profile())
//                .into(circleImageView);
        detial_name.setText("2323");

res code

 <de.hdodenhof.circleimageview.CircleImageView
        android:layout_width="120dp"
        android:layout_height="120dp"
        android:layout_gravity="center|top"
        android:layout_marginTop="50dp"
        android:elevation="10dp"
        android:src="@drawable/bigmercu"
        app:civ_border_color="#ffffff"
        app:civ_border_width="2dp"
        app:dependTargetY="-176dp"
        app:dependType="y"
        app:dependsOn="@+id/app_barA"
        app:layout_behavior="com.zoonref.SimpleViewBehavior"
        app:targetHeight="40dp"
        app:targetWidth="40dp"
        app:targetX="16dp"
        app:targetY="8dp"
        android:id="@+id/detialTouxiang" />

    <TextView
        android:layout_width="wrap_content"
        android:layout_height="?attr/actionBarSize"
        android:layout_marginLeft="72dp"
        android:layout_marginTop="-100dp"
        android:alpha="0"
        android:elevation="10dp"
        android:gravity="center_vertical"
        android:id="@+id/name_detial"
        android:text="吴老师"
        android:textColor="@android:color/white"
        android:textSize="18dp"
        app:dependTargetY="-206dp"
        app:dependType="y"
        app:dependsOn="@+id/app_barA"
        app:layout_behavior="com.zoonref.SimpleViewBehavior"
        app:targetAlpha="1"
        app:targetY="0dp" />

@Bigmercu I tested on demo project and it's working. maybe you can send me sample project so I can take a look.

I add the snap tag to the CollapsingToolbarLayout,maybe it's have some effect. I have changed some code to solve the problem,I will send it to your Email.

authors: Bigmercu zoonooz

repo: zoonooz/simple-view-behavior


text:
hex color breaks the plugin in "display name" section

The title says everything

Fixed! Thank you!

source: gharchive/issue

authors: rakzoser zorbeytorunoglu

repo: zorbeytorunoglu/thebestranks

license: MIT

license_type: permissive

license_source: github-api


text:
Support for New Bootstrap Icons (official Bootstrap icon library) v1.0.0-alpha3

Will there be support for Bootstrap Icons, Bootstrap's first-ever icon library?

I am not the maintainer of this repo, but from module-architecture perspective I think the bootstrap icons should be a separate project.

Here are some docs about icons: https://django-bootstrap4.readthedocs.io/en/latest/migrate.html#icons

Yes (thanks @guettli), this would be for https://github.com/zostera/django-icons.

authors: dyve f0rest8 guettli

license_source: bigquery


text:
Fix: stylesheet-html must have 'href' attribute

When using {% bootstrap_css %} if  settings.py has 'theme_url', the link tag for theme_url is generated wrong.
Because sanitize_url_dict() always generate dict(src=url) from URL string.
But in  tag, URL resource path must be in href attribute.
Except:
<link ref="stylesheet" href="/static/css/theme.css" >

Actually:
<link ref="stylesheet" src="/static/css/theme.css">

This PR fixes it.

Coverage increased (+0.1%) to 91.182% when pulling c2c67d20c746bc73bb5b330767c57761f48c8e64 on attakei:fix-link-attrs into c444ceab651dc0b7841229ea503bee3df5099d4c on zostera:develop.

thanks!

source: gharchive/pull-request

authors: attakei coveralls jieter


text:
Release fat Jar using sbt-s3 plugin

As a user, I want to be able to release this repo as a fat jar to AWS S3.

Fixed with a script in #6

repo: zouzias/spark-lucenerdd-aws


text:
Bug: menu dropdown is not hiding properly

Tested with Chrome desktop and mobile version.
To reproduce:

Visit https://zowe.github.io/
Click on menu icon on top-right corner
Click on "What is Zowe?"
The page seems try to move to https://zowe.github.io/#what-is-zowe name tag, but the content is covered with menu list layer, which is not hidden.

Hi @jackjia-ibm , good work on the site. @JamesBauman and I noticed that on Desktop there is a hamburger menu icon, rather than horizonal nav buttons. To me this is the mobile design, but should be responsive on desktop too. Should I open an issue, or is the current design intended?

@alexcontini Can you look into this?

Zowe icon and text is not visible in header with Firefox Quantum on Linux Mint, with Chromium it's ok.
Pull down menu items cover content when pulled down and menu remains down after select. To go back to menu one has to go all the way back up or use the browser "go backwards one page", would be nice to have the menu button remain on top when scrolling down or have a goto top button remain at bottom.

@jackjia-ibm @jmertic
sorry for the delay with this!
I think it's finally fully fixed: https://alexcontini.github.io/zowe.github.io/
Let me know when you have a chance and I will create a PR to make live

Thanks @alexcontini! It looks perfect to me.

@jackjia-ibm great!! PR is here - https://github.com/zowe/zowe.github.io/pull/52

authors: BrandonJenkins14 alexcontini fbeyl jackjia-ibm jmertic


text:
Support for matchstyle in app segments

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Support multimatch setting in app segments
https://help.zscaler.com/zpa/using-app-segment-multimatch

Support it in the app segment reosurce

zpa_application_segment
References
https://help.zscaler.com/zpa/configuring-application-segments-using-api
matchStyle:
INCLUSIVE (default)
EXCLUSIVE

@D4rkiiee This feature is now available as of provider version 3.2.0.
Regards

repo: zscaler/terraform-provider-zpa


text:
signature menu: preselect last selected category

currently all icons are shown each time when the menu opens

discussed with @thornch & @LazuLitee and feature not implemented
A preselected filter can be confusing to the user. E.g. user not finding symbol because symbol selection is pre-filtered and user may not realize that filter must be turned off.  If filter is removed each time the window is closed, this will not happen. Additionally, the feature for copying symbols and the feature for recently-used symbols may make this workflow improvement negligible.

authors: thornch timogi

repo: zskarte/zskarte


text:
The PS capacity is not reduced correctly, when attach Data Volume to NFS Primary Storage.

Create 1 VM
Create a Volume
Attach the Volume to VM. The volume size is 10485760. But in PS capacity, the capacity is only reduced 10475200. And check the file in system, it's real size is 10813440.

[root@centos61 Packages]# ls -l /opt/zstack/nfsprimarystorage/prim-917c95b2e39943d0b7d31469bc23db05/dataVolumes/acct-36c27e8ff05c4780bf6d2fa65700f22e/vol-1a080f619eed42b083a92bbc44d884e9/1a080f619eed42b083a92bbc44d884e9.qcow2
-rw-rw-rw-. 1 root qemu 10813440 Jul 10 13:10 /opt/zstack/nfsprimarystorage/prim-917c95b2e39943d0b7d31469bc23db05/dataVolumes/acct-36c27e8ff05c4780bf6d2fa65700f22e/vol-1a080f619eed42b083a92bbc44d884e9/1a080f619eed42b083a92bbc44d884e9.qcow2
"inventory": {
    "createDate": "Jul 10, 2015 1:05:15 PM",
    "deviceId": 1,
    "diskOfferingUuid": "c83c641770c44af386dcf7ce93e15e7c",
    "format": "raw",
    "installPath": "/opt/zstack/nfsprimarystorage/prim-917c95b2e39943d0b7d31469bc23db05/dataVolumes/acct-36c27e8ff05c4780bf6d2fa65700f22e/vol-1a080f619eed42b083a92bbc44d884e9/1a080f619eed42b083a92bbc44d884e9.qcow2",
    "lastOpDate": "Jul 10, 2015 1:05:15 PM",
    "name": "test",
    "primaryStorageUuid": "917c95b2e39943d0b7d31469bc23db05",
    "size": 10485760,
    "state": "Enabled",
    "status": "Ready",
    "type": "Data",
    "uuid": "1a080f619eed42b083a92bbc44d884e9",
    "vmInstanceUuid": "ab73cae16c9642d29e05a0673fc99bca"
},

    {
        "attachedClusterUuids": [
            "3d7d0c992e0b4d638d3b5b9977dcc76b"
        ],
        "availableCapacity": 50959220735,
        "availablePhysicalCapacity": 50969695935,
        "createDate": "Jul 10, 2015 12:53:27 PM",
        "description": "Test",
        "lastOpDate": "Jul 10, 2015 12:53:27 PM",
        "mountPath": "/opt/zstack/nfsprimarystorage/prim-917c95b2e39943d0b7d31469bc23db05",
        "name": "nfs",
        "state": "Enabled",
        "status": "Connected",
        "totalCapacity": 50969706496,
        "totalPhysicalCapacity": 50969706496,
        "type": "NFS",
        "url": "zstack:/home/nfs",
        "uuid": "917c95b2e39943d0b7d31469bc23db05",
        "zoneUuid": "5336c32ab7a34fc2afe3c05766c8ac6f"
    }

The PS primary storage totalCapacity and

you may do a wrong math. totalCapacity(50969706496) - availableCapacity(50959220735) = 10485761 which is 1 byte bigger than the volume size(10485760), not 10475200. The extra 1 byte is wried. I tried to repdouce but cannot.
To check the volume size on disk, you should use qemu-img like:
qemu-img info /opt/zstack/nfsprimarystorage/prim-406dd2cde78a4ddfbc4b201a1fc70bc0/dataVolumes/acct-36c27e8ff05c4780bf6d2fa65700f22e/vol-1a6fa3a5e70d412880fbbc1679fb8305/1a6fa3a5e70d412880fbbc1679fb8305.qcow2
image: /opt/zstack/nfsprimarystorage/prim-406dd2cde78a4ddfbc4b201a1fc70bc0/dataVolumes/acct-36c27e8ff05c4780bf6d2fa65700f22e/vol-1a6fa3a5e70d412880fbbc1679fb8305/1a6fa3a5e70d412880fbbc1679fb8305.qcow2
file format: qcow2
virtual size: 1.0G (1073741824 bytes)
disk size: 272K
cluster_size: 65536
Because of the thin-provisioning, the size checked by command 'll' is not different that the users asked

authors: youyk zxwing

repo: zstackorg/zstack


text:
Malformed byte-stream input to CharsetDecoder

Not really sure this issue should go here as it's a combination of bytestreams and aleph and possibly just me doing something wrong.
The following gives IllegalArgumentException Malformed byte-stream input to CharsetDecoder  byte-streams.char-sequence/parse-result (char_sequence.clj:17)
(-> @(http/get "http://www.google.ch/?gfe_rd=cr&ei=zhvOVNSyH6eH8QfbhoHoBg")
    :body
    bs/to-string)

Am I using bs/to-string incorrectly?  Looking at the response headers I can see the charset specified and I tried:
(-> @(http/get "http://www.google.ch/?gfe_rd=cr&ei=zhvOVNSyH6eH8QfbhoHoBg")
    :body
    (bs/to-string {:charset "ISO-8859-1"}))

but the result is the same.

Just as a heads up, that endpoint seems to get a redirect, but if I follow the redirect I get the same error.  The fact that this doesn't get any such error:
(-> @(http/get "http://www.google.ch/?gfe_rd=cr&ei=zhvOVNSyH6eH8QfbhoHoBg")
    :body
    bs/to-byte-array
    bs/to-string)

Suggests the error is in https://github.com/ztellman/byte-streams/blob/master/src/byte_streams/char_sequence.clj, which is slightly surprising (that code's been around for a while), but I'll take a look and see what I can find.

Ha, okay, this took me way too long to figure out.  The problem is that you need to pass in {:encoding "ISO-8859-1"}, not {:charset "ISO-8859-1"}.  The secondary problem is that (String. byte[]) is more forgiving of encoding issues than the alternate path.  Near term fix is to pass in the charset the proper way, longer term fix is for me to make the encoding errors less stringent, but configurable.
Marking this as closed.

The latest byte-streams 0.2.0-SNAPSHOT will fix this so that the encoding doesn't need to be specified (though this may cause some characters to be replaced with placeholders).

Ah great.  One thing I don't understand then, if I use (-> x bs/to-byte-array bs/to-string) is this going to possibly replace some characters with placeholders as well?  Or is it using UTF8 and will be decoded incorrectly?

I'm not sure I understand the "or"; when it can't decode a particular
character it will replace it with a placeholder, which I'd consider
"incorrect" decoding.  However, it won't throw an error, and I've made it
so that both conversions with and without the bs/to-byte-array behave
consistently, by replacing unknown characters.  You can get the old
behavior by specifying {:on-encoding-error :report} in the options if you
like.
Does that make sense?
On Sun, Feb 1, 2015 at 10:49 AM, David Smith notifications@github.com
wrote:

Ah great. One thing I don't understand then, if I use (-> x
bs/to-byte-array bs/to-string) is this going to possibly replace some
characters with placeholders as well? Or is it using UTF8 and will be
decoded incorrectly?
—
Reply to this email directly or view it on GitHub
https://github.com/ztellman/aleph/issues/138#issuecomment-72377772.

Yes, I think I understand now.  Thanks for the quick work and great communication again :)

repo: ztellman/aleph


text:
[Feature Request] Support for gpt-4-1106-preview and gpt-4-vision-preview?

Would be cool to add support for new models and image recognition.
I added this functionality locally in a cloned repo with dedicated button and clipboard support, but it's far from perfect and doesn't have image preview in messages, so maybe officially support it.

Also it's now possible to  add image gen support #462

Btw we can't store base64 images in localStorage as we do now for chats because it will exceed storage quota fast.

Btw we can't store base64 images in localStorage

Then switch to alternatives?
IndexedDB for example, but idk how hard it will be to implement though 🤔

https://github.com/animalnots/BetterChatGPT-VISION/releases

https://github.com/animalnots/BetterChatGPT-VISION/releases

好！

authors: AriesAlex Happiness777 RimoChan animalnots

repo: ztjhz/BetterChatGPT


text:
添加阿里的ali-oss插件后编译失败

Failed to compile.
index.js from UglifyJs
Unexpected token: name (Mime) [index.js:62173,8]
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! qianquduo-admin@2.0.1 build: roadhog build
npm ERR! Exit status 1
npm ERR!

分两步：

无视错误编译出来，build 后面加个--watch，build success最后会卡住，ctrl +c就好了。原理就是毕竟是UglifyJs的锅

分析这个问题，找到报错的地方，我贴出来吧，该不该找下ali-oss
`class Mime {
constructor() {
this._types = Object.create(null);
this._extensions = Object.create(null);
for (var i = 0; i < arguments.length; i++) {
this.define(arguments[i]);
}
}`

建议采用CDN的方式引入

目前解决是采用CDN方式引入没问题。
@superlbr，对，就是这个地方报错,个人认为是不是该采用babel-loader

云谦是打包大师，跟他提了一下，此issue不再跟踪，Close
@cybibo 可以贴下CDN怎么引入的，方便后来人

authors: cybibo superlbr yzzting

repo: zuiidea/antd-admin

license: mit


text:
新建pages，路由生成之后一直指向404页面

pages新建test路由
.umi/router.js中也自动生成test路由
但页面访问却显示404

是的，因为没有考虑权限
mock/menu.js了解下

刚刚搞定  多谢大牛   之前只看了mock的menu


text:
Star message with a long press

This a feature request: it would be awesome if I could star a message on the android client with a long press. Thank you all for the awesome work!

Hi! I can take this up if you tell me what exactly needs to be done. Is it something like adding a star right next to the msg ?

@reached-ankita Well the star can be implemented at the bottom or in the left of timestamp, on pressing the star button it would star/unstar the message, store the boolean if the message is starred in a separate column of the messages model just like read/unread boolean in the message model.
This would be the first step and send a PR for this!
Another step in another PR would be syncing from the server!

Alright I will perform the first step and send a PR to begin with.

@kunall17 Hey! I am having a doubt regarding the implementation of star button. Where should I put the code for starring and unstarring in the codebase? I am not understanding where exactly message_tile.xml is inflated and updated.

Where should I put the code for starring and unstarring in the codebase?

Add the click listener here https://github.com/zulip/zulip-android/blob/5301d960d65f05589fc49749d52fd62a8f672487/app/src/main/java/com/zulip/android/activities/RecyclerMessageAdapter.java#L118

I am not understanding where exactly message_tile.xml is inflated and updated.

message_tile.xml is the layout used for items in the recylcerView.
You could search the usages in for this file in studio, and you could easily find where it was being used!
Inflated here - https://github.com/zulip/zulip-android/blob/5301d960d65f05589fc49749d52fd62a8f672487/app/src/main/java/com/zulip/android/activities/RecyclerMessageAdapter.java#L316

@kunall17 I would like to work on this issue. Shall I proceed?

@yadav-rahul go for it!

@kunall17 I am done with this part

Well the star can be implemented at the bottom or in the left of timestamp, on pressing the star button it would star/unstar the message, store the boolean if the message is starred in a separate column of the messages model just like read/unread boolean in the message model.
This would be the first step and send a PR for this!

Now I am on

Another step in another PR would be syncing from the server!

@yadav-rahul send a pr for the first step till the reviewing process you can work with syncing!

OK. I am sending PR for first step.

Nice! @yadav-rahul can you please claim this task using zulipbot? That way it'd be easy for other contributors to search through unassigned issues :)

@zulipbot claim

authors: Sam1301 kunall17 munyari reached-ankita timabbott yadav-rahul

repo: zulip/zulip-android


text:
Only active status is shown in UserStatusIndicator.

Currently only active status is shown (green). But for users who are idle nothing is shown.
If someone status changes , app still shows previous status unless it is reopened.

@zulipbot claim

Is it a minor bug or something more complicated?
I was thinking of splitting the users and the presences (I think we are somewhat split right now) and rely on selectors.

Yeah we have done with splitting users and presence, and use selectors to get status.
But the problem is status for all users present in state.presence is active because currently only there is one way to add/edit/update state.presence which is through EVENT_PRESENCE (sent from the server). And server only sends events when someone becomes active. There are no events when someone becomes idle or inactive. (If server will send this event too then this is automatically fixed). Another problem is currently PRESENCE_RESPONSE action is never fired. We need to pass result of focusPing (sendFocusPing), so that we store status of all users in presence (and get through selector). And for updation we can ping focus (or call /users/me/presence) in fixed time interval to get latest status. (like in web and native Java Android app)

repo: zulip/zulip-mobile


text:
Upgrade suggested Vagrant version?

The docs currently suggest developers use Vagrant 1.8.1 (December 2015). The current version is 1.8.4. According to the Vagrant changelog, there are breaking changes between 1.8.1 and 1.8.3.

Vagrant 1.8.1 is the version I tested with across all platforms. Before we update the recommended version, we should probably make sure 1.8.4 works as expected.

Vagrant 1.8.4 works as expected on OS X, Windows 10, and Ubuntu 16.04. I'd like to update the first-time contributor instructions for Ubuntu 14.04 and 16.04 to explicitly use this new vagrant version, particularly because it fixes the rubygems issue that previously required a manual patch.

Sounds good to me!

authors: brainwane christi3k timabbott

repo: zulip/zulip


text:
Muted topics with unread messages appear in condensed stream topic list

We're still on an older 2.x version of Zulip, so this issue might have been fixed since then.
When a user mutes a topic, and other people talk in it, those messages still count as unread for that topic (See #11843 for more on this). For us, this is desirable but it leads to:
The muted topics, because they have unreads, now always show up in 'most recent topics/condensed topic' list when narrowed to that stream. If you click on 'more topics' it expands, and actual more recent topics (without unreads) show up before the muted topic with unreads.
Desired behavior:
Muted topics should not show up on the most recent topics/condensed topic list if they would normally be filtered out of that list by timestamp. So it's ok for them to show up in the condensed list if they normally would, but not ok for them to be special included just because they have unreads.
Pictures:

Here we see a narrowed stream view. The 5 most recent topics appear, 1 of them is muted. Below the top 5, a muted topic with unreads (final fantasy) is shown, along with the link to view "more topics". Clicking more topics leads to the full topic list:

Ignore the disappearance of the lunch topic, as these pictures were taken out of order. We see the full list now- that "final fantasy" is shoved down the list by more recent topics, "comics" and "top gun", which have been inserted into the list appropriately by datetime.

@swallitsch sorry for the slow reply -- this issue was missed in triage.  Can you check if you're still seeing this with zulip 3.x?  We definitely changed the logic for the sidebar system in that release, but I'm not sure if that specifically resolved this.

This is fixed in 3!

authors: swallitsch timabbott


text:
travis: Split out frontend/backend/static-analysis more clearly

We want to accomplish a few things that may be somewhat interrelated or raise interesting tradeoffs:

[x] Add tools/test-tools to travis.
[ ] Split out lint-all so it can do backend-only or frontend-only (and maybe overlap as needed for tools that blur the line and are fast...but we should probably just split those tools as well--check-templates comes to mind)
[x] [Decided to skip] Possibly make sure various travis scripts bootstrap themselves by running tools/test-tools and other lint-like things on the tools themselves, so that devs don't get confusing errors from broken tools.

I think it'd definitely be worth making the linter run separately against the backend vs. frontend code.  I think I might do it as lint --frontend runs against everything in package.json, static/, and templates/, and the other one runs against everything else in the repo.
We'd just use these options in Travis, to end the confusion we get sometimes with developers ignored "backend" failures in their "frontend only" changes, that are actually caused by lint errors in their frontend changes.
The third bullet I think isn't a priority, so I checked it and marked it as not going to happen.

Fixed via #6170.

authors: showell timabbott


text:
Add user documentation on stream/topic best practices

Per #675:

having advice on when you should split a stream into multiple streams, when you should use a new topic vs. replying to an existing one when sending a message, etc., would probably be useful.

This is also the sort of thing that would work well as a tip sent to new users about a month after they join Zulip.

When I first encountered this aspect of Zulip, I was expecting an option in the attached image to give me the option of splitting a topic off into a new one...

Editing the topic of a message is fine but adding it to the message/topic options might be an idea to increase usability... That might also then reduce the need to send out a new tip after a months time.

@timabbott Doesn't this already exist in https://chat.zulip.org/help/about-streams-and-topics? If not, how can the current documentation on that page be improved?

do you still need this?

I think https://zulip.com/help/getting-your-organization-started-with-zulip#create-streams covers this pretty well, so closing.

authors: 3ruce brainwane carpecodeum synicalsyntax timabbott


text:
Improve how we import Slack threads into Zulip

There's no coherent way to import the Slack "threads" feature into Zulip, but I think we could do better as follows:

When importing a message that's in a Slack thread replying to message X, we should add a line at the top of the import messages of the form "Slack thread reply to Tim Abbott's message"

This requires some pain to implement (since we need the message ID for tim's message, so we'll need to do an attachment-style rewriting thing to map the message ID).  But it's make the history a lot more readable.

The documentation needs to be added to say that this is not yet implemented.

@zulipbot claim

I am quite new to Zulip so I'm not sure what is the best idea to import Slack threads, but they should be somehow imported in a way which makes it easy to find old conversations and easy to follow things in those conversations.
I wonder if Slack threads could be implemented as Zulip topics? Is this good idea? I still don't understand how to use Zulip topics, so I don't know if this idea is good.
Also: I think this issue should be prioritized as more and more Slack users want to switch to Zulip. It is pain if import tool doesn't import everything well enough.

There is an open PR that does this: #19832.

authors: karolzlot rheaparekh rht timabbott


text:
overlays: Fix stream edit click-through bug.

Fixes ##12369.
Testing Plan:
GIFs or Screenshots:

side note: This was a terrible experience, it ate a lot of time. (but that is my fault for trying to find a good commit for a bisect before checking simple stuff first). That said, do our dev docs say anything about e.stopPropagation(); and if not should we consider something?

Nice, merged, thanks @YashRE42!
This is a common category of click handler bug.  As a general style rule, we try to use stopPropagation and preventDefault in essentially all of our focused click handlers (where you're clicking a specific button or area), but inevitable we end up merging some that don't have it, and the bugs it produces are almost always super annoying to track down just like this one.
It is probably worth doing an audit for similar issues in our click handlers, though we do need to be really careful to not just blindly find/replace, because some click handlers have cases where they want the default browser behavior to run.  Possibly we should add comments for all of those with that property.
Interested in working on that?

Would you have a strategy in mind for trying to get all the handlers?

There's this:
(zulip-py3-venv) tabbott@coset:~/zulip$ git grep '[.]on[(]' static/js/ | wc
    428    2455   40753

to find which files to look through.  It's a lot of call points, but I think it should be a pretty fast scan, since most of them will just have a .stopPropagation clearly there.

I'm wondering if we can write some regex to at least eliminate all the handlers which already have .stopPropagation (which would catch those that already have comments) from that count. I'll create an issue and track the progress there.

as further thought, if it's possible I think it'd be brilliant to add a rule in our linter to auto-catch this kind of thing. Essentially, for every .on handler, either the next brace pair should contain .stopPropagation or should have a comment that explicitly states why it's not there (and use the exact string .stopPropagation and hence also be excluded). I'll look into it, because we could put the linter in place first and then just look at all the handlers it points out.


text:
Convert non-total TypedDict declarations to Python 3.6 style too

Followup to #15093.

Great, merged, thanks @andersk!

authors: andersk timabbott


text:
integrations: Make clubhouse integration handle multiple actions

Fix #18022
Testing plan:
It has been tested with existing tests in addition to more tests on handling requests with multiple stories.
Instead of ignoring one of the stories, the integration will now send messages to all of them

When the webhook is directed to a single topic with three PRs this time

When updating multiple stories at the same time

When updating multiple stories at the same time, but only one change is made for each story

Merged, thanks for all the work on this @PIG208!


text:
Migrate edit_history from TextField to JSONField

What is PR for
The PR aims to migrate the edit_history field of AbstractMessage model from TextField to JSONField.
This was done as part of the audit which was mentioned in this issue: https://github.com/zulip/zulip/issues/17205
The changes done are:

Migrate the edit_history field from TextField to JSONField
Backfill migration to copy the elements in the field to their new type
Make changes across the codebase to use edit_history as an JSONField
Ensure the existing tests pass
Added tests for migration

Testing plan:
The changes have been tested by ensuring all the backend tests pass and were checked in development environment.
The behaviour is as expected.
Conversation : https://chat.zulip.org/#narrow/stream/2-general/topic/Migrate.20edit_history.20from.20TextField.20to.20ArrayField/near/1163454
@mateuszmandera it would be super helpful if you could give this a review.

This definitely reads cleaner, which probably suggests the migration is worth doing.  I posted a batch of comments on the details.

@edith007 can you renumber these migrations?

Also, do you understand what SQL is generated for an ArrayField?  We've not used them before so I'm not sure what to expect in terms of what tables it generates.

Also https://stackoverflow.com/questions/41134260/django-jsonfield-inside-arrayfield suggests to me that we might want just a JSONField rather than an ArrayField containing a JSONField; how did you think about that design decision?

Thanks for pointing these @timabbott!
I went through them and it is suggested not to use ArrayField and instead to use JSONField.
I went with the "ArrayField containing JSONField" implementation as it seemed to me that we were not searching for anything in the edit_history field, we just inserted the elements to the front of list and since the edit window is also of an hour so the array wont get that big...
Another reason was that the way we stored edit_history made me think that it is an Array containing JSON.. and I didn't even think of this alternative...
But after going through the above links, it does makes sense to use JSONField instead.

This looks essentially correct.  The main thing that needs reworking is that we need to process messages in batches in order to have an acceptable transaction size.  zerver/migrations/0313_finish_is_user_active_migration.py is a migration one could crib from.

Closing in favor of the current https://github.com/zulip/zulip/pull/26496.


text:
integrations: Enhance Grafana integration with alert state

Having the alert state in the message body is useful when alert topics are not defined by alert description but encoded in url.
E.g. in large environments having a topic for each alert [alerting] and [ok] would make it harder to properly track if an alert has been resolved.
When each alert is in a single topic, so far, the alert state has been missing.
This change will add the current alert state and a fitting icon in front of the alert name. (Similar to the prometheus alertmanager integration)

Feature enhancement, no issue existing.
Testing plan:
Tested with development instance on current master,
also tested on a prod env running 3.4
Linted with ./tools/lint
Gitlab Actions are also all green.
GIFs or screenshots:

This is an improvement/duplicate of #18372 now with added tests.

@adambirds I have removed that line, and it still passes all the tests

Merged, thanks @AdamVB and @adambirds!

(Also added this to the 4.x branch, so you can get this with upgrade-zulip-from-git 4.x if you're self-hosting; and then it'll be in the 4.3 release).

authors: AdamVB timabbott


text:
templates: fixed sender prefix in dialog.

The prefix was incorrect in the help dialog, changed the prefix from email to sender

Closing as I'm pretty sure we fixed the issue this was for (which unfortunately wasn't linked in the PR description).

authors: Biki-das timabbott


text:
narrow: Add backend support for new direct message filters.

Adds backend support for fetching messages with the new direct message narrows:

"is:dm" (deprecates "is:private")
"dm" (deprecates "pm-with")
"dm-including" (deprecates "group-pm-with")

UPDATED: Fixes #24806.
See relevant CZO conversations in api design and design streams.

git-grep of "pm-with" in /zerver after changes
$ git grep pm-with zerver/
zerver/lib/narrow.py:            # Both "pm-with" and "group-pm-with" are deprecated operators.
zerver/lib/narrow.py:            "pm-with": self.by_dm,
zerver/lib/narrow.py:            "group-pm-with": self.by_group_pm_with,
zerver/lib/narrow.py:            operators_supporting_id = ["sender", "group-pm-with", "stream", "dm-including"]
zerver/lib/narrow.py:            operators_supporting_ids = ["pm-with", "dm"]
zerver/lib/url_encoding.py:    base_url = f"{realm.uri}/#narrow/pm-with/"
zerver/lib/url_encoding.py:    base_url = f"{realm.uri}/#narrow/pm-with/"
zerver/lib/url_encoding.py:        "pm-with",
zerver/tests/test_email_notifications.py:            f"view it in Zulip Dev Zulip: http://zulip.testserver/#narrow/pm-with/{cordelia.id}-{encoded_name}"
zerver/tests/test_message_fetch.py:    # Test that deprecated "pm-with" works.
zerver/tests/test_message_fetch.py:        term = dict(operator="pm-with", operand=self.hamlet_email)
zerver/tests/test_message_fetch.py:    # Test that the underscore version of deprecated "pm-with" works.
zerver/tests/test_message_fetch.py:    # Test that deprecated "group-pm-with" works.
zerver/tests/test_message_fetch.py:        term = dict(operator="group-pm-with", operand=self.othello_email)
zerver/tests/test_message_fetch.py:        term = dict(operator="group-pm-with", operand=self.othello_email, negated=True)
zerver/tests/test_message_fetch.py:        term = dict(operator="group-pm-with", operand="non-existing@zulip.com")
zerver/tests/test_message_fetch.py:    # Test that the underscore version of deprecated "group-pm-with" works.
zerver/tests/test_message_fetch.py:            is_spectator_compatible([{"operator": "pm-with", "operand": "hamlet@zulip.com"}])
zerver/tests/test_message_fetch.py:            is_spectator_compatible([{"operator": "group-pm-with", "operand": "hamlet@zulip.com"}])
zerver/tests/test_message_fetch.py:        A request for old messages with a narrow by deprecated "group-pm-with"
zerver/tests/test_message_fetch.py:            narrow = [dict(operator="group-pm-with", operand=operand)]
zerver/tests/test_message_fetch.py:        narrow = [dict(operator="group-pm-with", operand=cordelia.email)]
zerver/tests/test_message_fetch.py:        # and deprecated "group-pm-with" operators
zerver/tests/test_message_fetch.py:        for operand in ["sender", "group-pm-with", "stream", "dm-including"]:
zerver/tests/test_message_fetch.py:        self.assertEqual(url, "http://zulip.testserver/#narrow/pm-with/77,80-pm/near/555")

Notes:

From the git-grep above, the only instances of "pm-with" that haven't been updated by these changes are those that directly reference pm-with URLs.
Have done some manual testing fetching messages via curl and via dev tools in the web app, but next steps will be to implement support for these in the frontend/web app.
For the dm:self_user case, in add_term where we build the query for sqlachemy, I used the same query that we use for is:dm since we basically want to return all of the logged in user's direct messages (group and 1:1) and added a comment to document why we do this.
There's a prep commit before the "dm-including" implementation to share some code between it and "group-pm-with" where we get the recipient IDs for group direct messages. This commit could be moved to be anywhere before the "dm-including" commit in the series.
Because the API documentation for the specific narrows we support is also part of the help center documentation, we will need to be careful with when we make those changes, which is why they are not included yet in these changes.

One thought I had was doing the API changelog feature level update and version.py bump with these changes.
And then updating the help center search for messages and the API docs construct narrow articles when the users can actually use these narrows in the web app (and other clients).

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Updates:

Added two commits for frontend implementation of new narrows.

First implemented is:dm to deprecate is:private.

When a user types is:p ... is:private, they will still get a search suggestion for is:dm. But the suggestions with user pills for dm: searches will not be filled in. But for the new is:dm, this works as expected.

Then implemented dm: to deprecate pm-with:.

I used the "from" alias for "sender" as a guide for my changes.
When a user types pm-with:, they will get search suggestions as if for dm:

Existing links in messages (like quote and reply near links) or that exist in general should still work with these changes. The backend still returns messages for those inputs, but the web app updates the operator/operand when creating the new Filter.

The URL bar in the browser does not update with these changes for these preexisting links.

Some example links to use in basic testing
I've gone through more thorough manual testing, but these are some examples. I'd also suggest prepping some near links via quote and reply to direct message conversations in the dev environment to make testing faster.
http://localhost:9991/#narrow/is/private
http://localhost:9991/#narrow/is/private/-pm-with/10-King-Hamlet
http://localhost:9991/#narrow/is/starred/is/private
http://localhost:9991/#narrow/pm-with/8-Cordelia,-Lear's-daughter
http://localhost:9991/#narrow/pm-with/11-Iago/has/image
http://localhost:9991/#narrow/pm-with/9-Desdemona/near/10

Still to-do:

Implement dm-including on the frontend.
Update backend webhook pm-with near URLs.
Add documentation and API feature level update, planned as final commit.

I played around with the PR, and the UX feels good to me!

Updates:

Added two new commits from previous update note:

A backend commit that updates the url-encoding, which is used for email notifications and outgoing webhooks, to use dm instead of pm-with.
A frontend commit that implements dm-including. This mirrors most of the implementation for group-pm-with.

Still to-do:

Update group-pm-with for deprecated behavior. I feel like it will be cleaner to do this in a separate commit from the dm-including implementation. Also, it would be good to clarify on CZO what we expect the web app to do for group-pm-with moving forward.
The final documentation commit with the API changelog / feature level bump as well as API, help center and ? menu documentation updates.

Screenshots for dm-including:

Empty narrow banners - no direct messages

Negated dm-including with current user - returns all stream messages

dm-including with current user - returns all private messages
Note: Like group-pm-with this view does not mark messages as read

dm-including returns both group and 1-on-1 direct messages

Negated `dm-including` with another user combined with `is:dm` returns all direct messages without that user

I commented on the changes so far; generally seems pretty clean.

Updates:

Addressed initial review feedback on first 7 commits (see individual comments above). Also, did a general pass to no longer use "DM" in any comments / code.
Added a commit removing "group-pm-with" support from the web app and making it a legacy alias for "dm-including".
Added the final commit with the API, help center and ? menu documentation updates.

Relevant CZO conversations:

#api design > direct messages search operators
#api documentation > direct messages search operators
#design > "Private" vs "Direct"

Documentation screenshots:

Search for messages
Current documentation

Web app ? menu

Before
After

API changelog update

Construct narrow
Current documentation

Get messages
Current documentation

Register queue - narrow parameter
Current documentation

Check messages match narrow
Current documentation

Update personal message flags for narrow
Current documentation

The help center and ? menu documentation looks good to me.

I had one thing to add, the screenshots otherwise lgtm.

@gnprice and @timabbott - Thanks for the feedback on the API documentation commit. I've updated for all the above comments. See screenshots below.
Notes:

In the API changelog note, I still used "operator" when specifically referring to the two operator changes (dm and dm-including). But in the general case or with the is:dm / is:private case I used "filter".
The construct a narrow Changes note has been expanded to cover the difference between dm-including and group-pm-with. I also added a specific note that the other two filters pairs (new/deprecated) return the same results.
The Changes note for the four endpoint parameters is the same, so I have only one example screenshot below. I did add "filter" to a few of the narrow parameter descriptions so that the Changes note would read more clearly.

Updated screenshots:

Revised API changelog note

Construct a narrow - expanded Changes note

Updated Changes note in endpoint parameter

Failing test is likely a puppeteer flake in copy-and-paste.test.ts.

Updates:

See above comment about changes to API documentation per review feedback.
The final commit notes that this PR will close #24806. The new direct message filters (is:dm, dm and dm-including) have the updated URLs. I feel like updating the URLs for existing/legacy links/searches should be a separate follow-up issue. I've updated the original comment to note that on this PR as well.
I had one note/question (see above about Filter.update_email, but I believe that could also be a small clean-up done after these changes.

Tagging as a release goal since we're certainly including this in 7.0 at this point; please re-add integration review when Greg's comments are addressed.

Updates:

Addressed @gnprice's feedback above.

The endpoint parameter Changes notes contextualize the use of "filter".
Fixed the missing space in construct_narrow.md and removed the line wrapping edits/clean up (with a note to myself to revisit as a separate refactor/clean up PR).

Updated screenshots:

Construct narrow changes note

Example of endpoint `narrow` parameter changes note

This is great, merged, thanks for executing this complex API transition @laurynmm!

authors: alya laurynmm timabbott


text:
Dark mode

Feature - Adding Dark mode to the website.

heyy, can i work on this feature?

repo: zuramai/voler


text:
Fix smoothScroll reference in foundation.js

This is a fix for the issue I posted in #235. Magellan seems to reference smoothScroll, which causes issues in development on rails 5.1.2, since it's being included after magellan.js in the foundation.js manifest.

Plase merge.

authors: MicahBrown taylorwilliams

repo: zurb/foundation-rails


text:
Reinitialize Plugin after PJAX load

I have a reveal modal that contains a menu. When I click on a menu item it loads a new page using BarbaJS . The problem is the page loads, but the reveal stays open. When I close it, it won't reopen. I tried to trigger a close on a new page load but I get an error message. I've used the following:
Barba.Dispatcher.on('newPageReady', function() {
  $('[data-reveal]').foundation('close');
});

I also tried
Barba.Dispatcher.on('transitionCompleted', function() {
  $('[data-reveal]').foundation('close');
});

Both times I get the following error:
foundation.core.js:281 Uncaught (in promise) ReferenceError: We're sorry, 'close' is not an available method for this element.

When I try to reinitialize with
Foundation.reInit('reveal');

I get this error
TypeError: Cannot read property '_init' of undefined

Any ideas on how to fix this? I tried the same thing for a sticky header and got the same result.

I got the reveal to close by reinitializing foundation:
Barba.Dispatcher.on('transitionCompleted', function(currentStatus) {
  $(document).foundation();
});

of course now that it is re-initializing foundation I get a message like this:
``
Tried to initialize accordion-menu on an element that already has a Foundation plugin.
for all the plugins I have on a page. This is expected. Is there a way to get around this?

see https://github.com/zurb/foundation-sites/issues/9047

Thanks. I've decided not to move forward with Barba for now so ill close this.

@cgts may I ask why? Because I wanted to try it out, since it is vanillajs without dependencies. And the Ajax issue with foundation has nothing to do with barba or smoothstate.

@phifa There was nothing wrong with Barba. I know very little javascript and had a limited amount of time to push this project out. I found that I was running into issues like modal windows being re-added (without being removed) whenever they were used. I'm sure these issues could have easily been overcome by anybody who know JS, I just didn't have the time to come up to speed.
I would definitely recommend it if you know JS.

@cgts without having a repro case it's hard to say for certain, but my guess is that since you were targeting globally [data-reveal], you were also getting some reveal elements from the NEW page that had not yet been initialized, and that is why you were seeing the error.

This example here the project owner supplies is useful:
https://plnkr.co/edit/wfgMT7kbvX3mhoGDggli?p=preview
This example ZF6 appears to be working with barba.js - though haven't tested extensively yet.
document.addEventListener("DOMContentLoaded", function() {
	pageInit(document);
	//BARBA	INIT
	Barba.Pjax.start();
	Barba.Prefetch.init();

	//AFTER PAGE INIT
	Barba.Dispatcher.on('newPageReady', function(currentStatus, oldStatus, container, newPageRawHTML) {
		pageInit(container);
	});

	function pageInit(scope) {
		// Init Foundation Plugins
		$(scope).foundation();
	}
	//END DOMContentLoaded
});

authors: CGTS iamrobert kball phifa

repo: zurb/foundation-sites


text:
Abimbola Ashonibare

My name is Abimbola Ashonibare and I am a product designer.
I worked along side other product designers, as well as developers on the QR code generation website for team 55.
I worked on developing the style guide that was used in this project along side some other designers.
I was charged with the responsibility of creating the colour styles which was of utmost important to this project.
It was important that we used the right set of colours for the website.
I created the grid style that was used for this project as well.
Also, I created all the button styles for both the desktop view and the mobile view. I made sure to create all
the various button states as well as shapes.
Here is a link to the colour style I created.
https://www.figma.com/file/h4z1WucYksn2jffHUW4VDE/Zuri-proj_team_55-team-library?node-id=460%3A249
Here is a link to the button styles I created (desktop).
https://www.figma.com/file/h4z1WucYksn2jffHUW4VDE/Zuri-proj_team_55-team-library?node-id=415%3A370
Here is a link to the button styles I created (mobile).
https://www.figma.com/file/h4z1WucYksn2jffHUW4VDE/Zuri-proj_team_55-team-library?node-id=457%3A255
Here is a link to the grid style I created.
https://www.figma.com/file/h4z1WucYksn2jffHUW4VDE/Zuri-proj_team_55-team-library?node-id=460%3A309

For the design of the website itself, I worked on the landing page.
I ensured the proper alignment of every single item on the website was in line with our 4 point system.
I also ensured the illustrations used were of the right size for the website. Also, I ensured the font size for
the landing page was just perfect.
I created the landing design for the mobile view as well.
Also, I ensured the overall aesthetics of the landing page was beautiful.
Here is a link to the landing page's wireframe.
https://www.figma.com/file/h4z1WucYksn2jffHUW4VDE/Zuri-proj_team_55-team-library?node-id=1641%3A8640
Here is a link to the landing page's low fidelity.
https://www.figma.com/file/h4z1WucYksn2jffHUW4VDE/Zuri-proj_team_55-team-library?node-id=1641%3A4550
Here is a link to the landing page's high fidelity (desktop view).
https://www.figma.com/file/h4z1WucYksn2jffHUW4VDE/Zuri-proj_team_55-team-library?node-id=1629%3A3617
Here is a link to the landing page's high fidelity (mobile view).
https://www.figma.com/file/h4z1WucYksn2jffHUW4VDE/Zuri-proj_team_55-team-library?node-id=1629%3A6134
thank you


text:
generator_bce input parameter

Anomaly Toolbox version: Latest
Python version: 3.8
Operating System: Linux

Description
Isn't the generator loss supposed to be computed based on the discriminator output of the regenerated image? Therefore shouldn't it be d_gex instead of g_ex as the input to bce_g_loss? Below is from trainers ganomaly.py
Discriminator on the reconstructed real data g_ex
d_gex, _ = self.discriminator(inputs=g_ex, training=True)
Encode the reconstructed real data g_ex
e_gex = self.encoder(g_ex, training=True)
Discriminator Loss
d_loss = self._minmax(d_x_features, d_gex_features)
d_loss = self._minmax(d_x, d_gex)
Generator Loss
adversarial_loss = losses.adversarial_loss_fm(d_f_x, d_f_x_hat)
bce_g_loss = generator_bce(g_ex, from_logits=True)
What I Did
Paste the command(s) you ran and the output.
If there was a crash, please include the traceback here.

Hello @fer927,
thank you for your detailed observation and for bringing this to our attention.
Issue Summary
You pointed out that in the current implementation of ganomaly.py, the generator's Binary Cross-Entropy (BCE) loss is computed as follows:
bce_g_loss = generator_bce(g_ex, from_logits=True)

You suggested that it should instead be:
bce_g_loss = generator_bce(d_gex, from_logits=True)

Evaluation of the Issue
After reviewing the code and the original GANomaly implementation, we can confirm that your observation seems indeed correct. The generator loss should incorporate the discriminator's feedback to ensure the generator improves its ability to produce realistic images.
Details
In GAN training, the generator's adversarial loss typically uses the discriminator's output on the generated data. This helps guide the generator to create data that can fool the discriminator.
In the original GANomaly implementation (model.py), the adversarial loss for the generator is computed based on the discriminator’s feedback, as shown below:
self.err_g_adv = self.l_adv(self.netd(self.input)[1], self.netd(self.fake)[1])

This indicates that the generator loss (err_g_adv) is computed using the discriminator's features (self.netd(self.fake)[1]).
Considerations
During the development of the anomaly toolbox, we encountered various challenges that might have led to the current implementation. Typically, when we deviate from standard practices, we leave comments explaining our rationale. However, in this case, there is no such comment, which suggests that your proposed change is likely correct.
Proposed Change
To align with the standard GAN training practices and the original GANomaly model, the BCE loss for the generator in ganomaly.py should be computed using d_gex, the discriminator's output on the reconstructed data:
bce_g_loss = generator_bce(d_gex, from_logits=True)

For further reference, please see the original GANomaly paper here.
Conclusion
Your suggestion appears to be correct, and we appreciate your attention to detail. We will update the code to reflect this correction. Thank you for helping us improve the quality of our project!

repo: zurutech/anomaly-toolbox


text:
Docs: Create initial docs directory and content

Created initial docs directory and added basic documentation. I tried to group together similar categories such as getting started, guides and middleware support. I would be happy to revise the content or make any further adjustments as needed.

@dai-shi thank you! I agree, it would be better to add an index number in the file names to sort them. I added a new commit to address it.

repo: zustandjs/zustand-slices


text:
⚠ Avatar API Endpoint has degraded performance

In d9f11f4, Avatar API Endpoint (https://avatar.roblox.com/v1/avatar-rules) experienced degraded performance:

HTTP code: 200
Response time: 4733 ms

Resolved: Avatar API Endpoint performance has improved in 4d691b1 after 13 minutes.


text:
Missing device configuration: Aibase A19 LED BULB RGBW, ZWA ID 2889

Checklist

[X] It is not in the configuration DB

[X] It was not merged recently or has a pending PR

Which device is missing?
Aibase A19 LED BULB RGBW, ZWA ID 2889
Manufacturer ID
0x0384
Product Type
0x0003
Product ID
0x0003
Firmware Version
2.20
Is the device listed on the Z-Wave Alliance website?
No response
Do you have a manual?
Reported by Telemetry:

capability
value

associationGroups
["Lifeline"]

supportsAGI
true

supportsConfigCCV3
false

supportsZWavePlus
true

zWavePlusVersion
1

If anyone plans on helping out with this file, please read https://zwave-js.github.io/node-zwave-js/#/config-files/using-telemetry-data first.

@zwave-js-bot import config 2889 from zwa

repo: zwave-js/node-zwave-js


text:
[bug] zwave-js fatal error on replace failed node

Version
Build/Run method

[X] Docker
[ ] PKG
[ ] Manually built (git clone - npm install - npm run build )

zwavejs2mqtt version: 2.1.0
zwavejs version: 6.6.0
Describe the bug
2021-03-03 18:12:45.564 INFO ZWAVE: Calling api replaceFailedNode with args: [ 6, false, [length]: 2 ]
2021-03-03 18:12:50.116 INFO ZWAVE: Controller status: Non-secure inclusion started
2021-03-03 18:12:50.120 INFO ZWAVE: Success zwave api call replaceFailedNode { success: true, message: 'Success zwave api call
', result: true }
2021-03-03 18:12:59.943 INFO ZWAVE: Controller status: Inclusion stopped
2021-03-03 18:12:59.966 INFO ZWAVE: Node 6: removed
2021-03-03 18:12:59.966 INFO ZWAVE: Node removed 6
2021-03-03 18:13:28.476 INFO ZWAVE: Node 6: added
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which wa
s not handled with .catch(). The promise rejected with the reason:
TypeError: Cannot read property 'basic' of undefined
at Object.dumpDeviceClass (/usr/src/app/node_modules/@zwave-js/server/dist/lib/state.js:85:26)
at Object.dumpNode (/usr/src/app/node_modules/@zwave-js/server/dist/lib/state.js:42:67)
at /usr/src/app/node_modules/@zwave-js/server/dist/lib/forward.js:23:31
at Array.forEach ()
at ZWaveController. (/usr/src/app/node_modules/@zwave-js/server/dist/lib/forward.js:20:34)
at ZWaveController.emit (node:events:390:22)
at ZWaveController.EventEmitter.emit (node:domain:470:12)
at ZWaveController.handleReplaceNodeRequest (/usr/src/app/node_modules/zwave-js/src/lib/controller/Controller.ts:1203:11)
at Driver.handleRequest (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:1936:22)
at Driver.handleUnsolicitedMessage (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:1670:5)
To Reproduce
Steps to reproduce the behavior:
Attempt to replace a dead node.

@AlCalzone do you know what's going on?

Seems like you try to dump the device class of the node before it is known.
https://github.com/zwave-js/zwave-js-server/blob/7580ba0d46d303e581117f846522282fdc81177e/src/lib/state.ts#L159
"node added" is emitted before the interview. In case of replacing a node, we don't know the device class yet, because we don't get the same info as during an inclusion.

I think you are calling the dumpNode when node is added but that property is undefined on that point

@AlCalzone Always some seconds before me :laughing:

Not sure how TypeScript let you do that though without testing for property existance:
https://github.com/zwave-js/node-zwave-js/blob/fc5492fbe517901ea0fd30a81b6be6eb2020be4c/packages/zwave-js/src/lib/node/Node.ts#L439-L442

Ah, rookie mistake... Using TypeScript without strict mode. 😅

authors: AlCalzone MartinHjelmare bs42 robertsLando

repo: zwave-js/zwave-js-server


text:
feature: Update Data Model

Overview
We'll need to revise the wireframes and add properties to the current collections.

Add playerPhoto to players collection
Create playerMatches collection following RIOT API
Add other collections or properties as needed

Acceptance Criteria
The models, is functions and the routes should use the updated data types.
NOTES: We'll need to discuss the playerMatches collection as the API returns more information than we need

Data Model

LeagueV4: Players

AccountV4: puuid

MatchesV4: Matches

MatchesV4: Match details

Get Challenger Players:
/lol/league/v4/challengerleagues/by-queue/{queue}
Get puuid -> playerId / profileIconId -> playerImage:
/lol/summoner/v4/summoners/{encryptedSummonerId}
Get Match Ids:
/lol/match/v5/matches/by-puuid/{puuid}/ids
Get Match Details:
/lol/match/v5/matches/{matchId}
Maximum Players: 2400
20 requests every 1 seconds100 requests every 2 minutes
Data needed
MatchesV4 -> teamPosition, kills, deaths, assists, championName, championId, win
Champion Image http://ddragon.leagueoflegends.com/cdn/12.19.1/img/champion/Aatrox.png
Summoner Icon
https://ddragon.leagueoflegends.com/cdn/12.20.1/img/profileicon/27.png

Data
Source
Property
Type

Rank

Role
MatchesV4
teamPosition
string

Champion
MatchesV4
championName, championId
string, number

Win/Loss
MatchesV4
win
boolean

Kills
MatchesV4
kills
number

Deaths
MatchesV4
deaths
number

Assists
MatchesV4
assists
number

Data Model

LeagueV4: Players

AccountV4: puuid

MatchesV4: Matches

MatchesV4: Match details

Get Challenger Players:
[/lol/league/v4/challengerleagues/by-queue/{queue}](https://developer.riotgames.com/apis#league-v4/GET_getChallengerLeague)
Get puuid -> playerId / profileIconId -> playerImage:
[/lol/summoner/v4/summoners/{encryptedSummonerId}](https://developer.riotgames.com/apis#summoner-v4/GET_getBySummonerId)
Get Match Ids:
[/lol/match/v5/matches/by-puuid/{puuid}/ids](https://developer.riotgames.com/apis#match-v5/GET_getMatchIdsByPUUID)
Get Match Details:
[/lol/match/v5/matches/{matchId}](https://developer.riotgames.com/apis#match-v5/GET_getMatch)
Maximum Players: 2400
20 requests every 1 seconds
100 requests every 2 minutes
Data needed
MatchesV4 -> teamPosition, kills, deaths, assists, championName, championId, win
Champion Image http://ddragon.leagueoflegends.com/cdn/12.19.1/img/champion/Aatrox.png
Summoner Icon
https://ddragon.leagueoflegends.com/cdn/12.20.1/img/profileicon/27.png

Data
Source
Property
Type

Rank

Role
MatchesV4
teamPosition
string

Champion
MatchesV4
championName, championId
string, number

Win/Loss
MatchesV4
win
boolean

Kills
MatchesV4
kills
number

Deaths
MatchesV4
deaths
number

Assists
MatchesV4
assists
number

repo: zyzmoz/global-player


text:
add Math.min to cap percent at 100%

This fixes #35 😊
If the percentage is over 100%, the stroke offset will always be full.

Thanks for this @karltaylor ! I added a small comment, let me know if you need any help

@zzarcon this GTM? :)

@karltaylor thanks a lot for the fix! And sorry for the delay :)

authors: karltaylor zzarcon

repo: zzarcon/react-circle


text:
style lost when using quill.clipboard.convert

I've encountered an issue when dealing with clipboard.convert method.
The injected html (as string) does not produce the correct list of Op (from Delta). As a result, i lost all my formatting (bold, italic, images, ...)
Here's the testing code:
import {AfterViewInit, Component} from '@angular/core';
import {RouterOutlet} from '@angular/router';
import Quill from 'quill';
import {
  defaultCustomSelect,
  TableAlign,
  TableMenuContextmenu,
  TableResizeLine,
  TableResizeScale,
  TableSelection,
  TableUp,
  TableVirtualScrollbar
} from 'quill-table-up';

Quill.register('modules/table-up', TableUp, true);

@Component({
  selector: 'app-root',
  imports: [RouterOutlet],
  template: '

',
  standalone: true,
  styleUrl: './app.component.css'
})
export class AppComponent implements AfterViewInit {
  title = 'QuillTable';

  ngAfterViewInit() {
    const config = {
      theme: 'snow',
      modules: {
        table: false,
        toolbar: [
          ['bold', 'italic', 'underline', 'strike'],

          [{[TableUp.toolName]: []}]
        ],
        [TableUp.moduleName]: {
          full: true,
          align: TableAlign,
          resize: TableResizeLine,
          resizeScale: TableResizeScale,
          scrollbar: TableVirtualScrollbar,
          customSelect: defaultCustomSelect,
          selection: TableSelection,
          selectionOptions: {
            tableMenu: TableMenuContextmenu
          }
        }
      }
    };

    const editor1 = new Quill('#editor', config);
    const editor2 = new Quill('#editor2', config);

    function change(html: string) {
      console.log(html);
      let contents = editor2.clipboard.convert({html: html});
      console.log(JSON.stringify(contents));
      editor2.setContents(contents);
    }

    editor1.on('text-change', ((delta: any, oldDelta: any, source: any) => {

      if (source == 'user') {
        change(editor1.root.innerHTML);
      }
    }).bind(this));

  }
}

Output code:

<colgroup data-table-id="z3fd2rq1bx" data-full="true" contenteditable="false"><col width="50%" data-full="true" data-table-id="z3fd2rq1bx" data-col-id="lkp85q7n9uq"><col width="50%" data-full="true" data-table-id="z3fd2rq1bx" data-col-id="2zlr6hlxeq6"></colgroup>

b

{"ops":[{"insert":"\n\n"},{"insert":{"table-up-col":{"tableId":"lsr531ftaa","colId":"ghy8tn0vs7","full":true,"width":50}}},{"insert":{"table-up-col":{"tableId":"lsr531ftaa","colId":"cvb5rwzr98","full":true,"width":50}}},{"attributes":{"table-up-cell-inner":{"tableId":"lsr531ftaa","rowId":"syegc3vsxll","colId":"ghy8tn0vs7","rowspan":1,"colspan":1}},"insert":"b\n"},{"attributes":{"table-up-cell-inner":{"tableId":"lsr531ftaa","rowId":"syegc3vsxll","colId":"cvb5rwzr98","rowspan":1,"colspan":1}},"insert":"\n"},{"insert":"\n"}]}

Versions used:
quill: 2.0.3
quill-table-up: 2.0.0
angular: 18.2.12

due to github issues, this issue has been duplicated

repo: zzxming/quill-table-up


text:
Add badge for android-gems.com

增加了 android-gems badge 方便用户直接运行demo http://www.android-gems.com/lib/zzz40500/AndroidSweetSheet?lib_id=300

已经加进去了.,不过是加在README.markdown ,不是README.md


text:
直播功能

请问一下实现直播功能了吗

直播功能，暂时没有实现，后面可以尝试做一做

authors: EternalStudying zzzlyly

repo: zzzlyly/tiktok


text:
chore: husky OS compatibility

This fails on Windows, the syntax is invalid and uname isn't a command

This should now work on Windows as well as Windows with WSL installed. There are two separate issues when using Github Desktop and this should also address issues with GitKraken and other GUI tools on Windows.

.husky/pre-commit: line 5: return: can only `return' from a function or sourced script
husky - pre-commit script failed (code 2)

Testing on a fresh Windows install with pretty much only VS Code, husky spits out this error.
exit should work here, just replace both replaces

authors: Pazaz o-k-a-y


text:
make pseudo cli an EventEmitter and have cdk logs delivered via events instead of writing into user's browser console

will not do for now.


text:
ログ出力機能を実装する

PythonバージョンのIssueなのでクローズします。


text:
Donation dApp Tutorial - Define Smart Contract Functions

https://aelfblockchain.sg.larksuite.com/wiki/Gdrnw8VAyigsIRk3cbPlWbYMgYe?from=from_copylink

repo: AElfProject/aelf-dapp-factory


text:
[Site] Change favicon link

Codecov Report

Merging #370 (d4b547d) into master (a89c038) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #370   +/-   ##
=========================================
  Coverage     68.38%   68.38%
  Complexity     1129     1129
=========================================
  Files           135      135
  Lines          3865     3865
  Branches        521      521
=========================================
  Hits           2643     2643
  Misses          996      996
  Partials        226      226

Continue to review full report at Codecov.

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

authors: Xiaoyunnn codecov-commenter


text:
Add test cases to AddCommandTest and DeleteCommandTest

Codecov Report

Merging #122 (ac77117) into master (e6409d1) will increase coverage by 1.09%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #122      +/-   ##
============================================
+ Coverage     71.32%   72.41%   +1.09%
- Complexity      503      507       +4
============================================
  Files            81       81
  Lines          1559     1559
  Branches        194      194
============================================
+ Hits           1112     1129      +17
+ Misses          396      380      -16
+ Partials         51       50       -1

Impacted Files
Coverage Δ

.../java/seedu/address/logic/commands/AddCommand.java
62.68% <0.00%> (+25.37%)
:arrow_up:

Continue to review full report at Codecov.

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


text:
Populate sample data

Codecov Report

Merging #76 (d3882f1) into master (cd50265) will decrease coverage by 0.33%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master      #76      +/-   ##
============================================
- Coverage     48.46%   48.12%   -0.34%
  Complexity      402      402
============================================
  Files           105      105
  Lines          1851     1864      +13
  Branches        197      200       +3
============================================
  Hits            897      897
- Misses          922      935      +13
  Partials         32       32

Impacted Files
Coverage Δ

src/main/java/seedu/address/MainApp.java
0.00% <0.00%> (ø)

...rc/main/java/seedu/address/logic/LogicManager.java
0.00% <0.00%> (ø)

...a/seedu/address/model/classgroup/ClassGroupId.java
30.00% <ø> (ø)

.../java/seedu/address/model/util/SampleDataUtil.java
12.00% <0.00%> (-8.00%)
:arrow_down:

Continue to review full report at Codecov.

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

authors: codecov-commenter lkldev


text:
Edit UI layout

Codecov Report

Merging #137 (cf20ae9) into master (9605c54) will increase coverage by 0.18%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master     #137      +/-   ##
============================================
+ Coverage     70.14%   70.32%   +0.18%
- Complexity      547      552       +5
============================================
  Files            88       89       +1
  Lines          1782     1793      +11
  Branches        223      226       +3
============================================
+ Hits           1250     1261      +11
  Misses          446      446
  Partials         86       86

Impacted Files
Coverage Δ

src/main/java/seedu/address/ui/ModCard.java
0.00% <0.00%> (ø)

...n/java/seedu/address/model/util/ModComparator.java
100.00% <0.00%> (ø)

...c/main/java/seedu/address/model/person/Person.java
94.31% <0.00%> (+0.06%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

authors: codecov-commenter sltsheryl


text:
Create calc.cpp and  2’s complement.cpp

#include
using namespace std;
int main()
{
int choice;
long num1, num2, x;
//displaying different options
cout << "Please choose your option:"
"\n1 = Addition"
"\n2 = Subtraction"
"\n3 = Multiplication"
"\n4 = Division"
"\n5 = Squares"
"\n6 = exit"
"\n\nChoice: ";
cin >> choice;
//while loop check whether the choice is in the given range
while(choice < 1 || choice > 6)
{
cout << "\nPlease choose the above mentioned option."
"\nChoice: ";
cin >> choice;
}
switch (choice)
{
//Addition
case 1:
cout << "Enter two numbers: \n";
cin >> num1 >> num2;
x = num1 + num2;
cout << "Sum = " << x;
break;
  //Subtraction
  case 2:
     cout << "Enter two numbers: \n";
     cin >> num1 >> num2;
     x = num1 - num2;
     cout << "Subtraction = " << x;
     break;

  //Multiplication
  case 3:
     cout << "Enter two numbers: \n";
     cin >> num1 >> num2;
     x = num1 * num2;
     cout << "Product = " << x;
     break;

  //Division
  case 4:
     cout << "Enter Dividend: ";
     cin >> num1;
     cout << "Enter Divisor: ";
     cin >> num2;

     //while loop checks for divisor whether it is zero or not
     while(num2 == 0)
     {
        cout << "\nDivisor cannot be zero."
                "\nEnter divisor once again: ";
        cin >> num2;
     }
     x = num1 / num2;
     cout << "\nQuotient = " << x;
     break;

  //Square
  case 5:
     cout << "Enter any number: \n";
     cin >> num1;
     x = num1 * num1;
     cout << "Square = " << x;
     break;

  case 6:
     return 0;

  default: cout << "\nError";

}
}

authors: debrajrout iamthecloverly


text:
[WIP] replaced deal token by erc721

Codecov Report

Merging #109 (126657f) into dev (31aceea) will decrease coverage by 19.65%.
The diff coverage is 0.88%.

@@             Coverage Diff             @@
##              dev     #109       +/-   ##
===========================================
- Coverage   50.19%   30.53%   -19.66%
===========================================
  Files          15       20        +5
  Lines         520      858      +338
  Branches      120      207       +87
===========================================
+ Hits          261      262        +1
- Misses        259      596      +337

Impacted Files
Coverage Δ

contracts/AelinERC721.sol
0.00% <0.00%> (ø)

contracts/AelinUpFrontDeal.sol
0.00% <0.00%> (ø)

contracts/AelinUpFrontDealFactory.sol
0.00% <0.00%> (ø)

contracts/libraries/AelinAllowList.sol
0.00% <0.00%> (ø)

contracts/libraries/AelinNftGating.sol
0.00% <0.00%> (ø)

contracts/AelinPool.sol
44.35% <50.00%> (-0.14%)
:arrow_down:

contracts/AelinFeeEscrow.sol
34.61% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

repo: AelinXYZ/aelin


text:
Adds android 11 specific installation instructions

@AnupKumarPanwar have you had time to look at this?

LGTM

repo: AnupKumarPanwar/Linkable


text:
Add "AM" and "portable-linux-apps.github.io" and update AppMan

@probonopd

repo: AppImageCommunity/awesome-appimage


text:
fix(docs): Reword welcome page to be more friendly

@jatinriverlane @safeamiiir Is this ok with either of you?

repo: AqueductHub/aqueductcore


text:
Finished assign and fixed how some of the errors are handled

superseded by #32

repo: AriGlockner/PLC-Group-Projects


text:
Data: Add New Information And Set Image

Closes #8

repo: AslanbekHasanov/Kino


text:
Refactor Nova => Hub

@Jabyl can we get a confirmation from the team this is something I can submit soon? We have #86 pending.

Resolved by #110.

repo: Aut-Labs/contracts


text:
Feat/tab legacy

It looks to be missing focus-visible styling.

authors: LauRoxx gregmartDOTin

repo: Availity/element


text:
chance icon of dreadlord elite to regular dreadlord

@richardik Could you clarify why? Is there overlap or something?

should be adressed with HD icons

authors: YakaryBovine richardik

repo: AzerothWarsLR/WarcraftLegacies


text:
chore(ci): dont look for tags if pure spot

Benchmark results
Metrics with a significant change:

circuit_witness_generation_time_in_ms (merge-rollup): 276 (+123%)
circuit_proving_time_in_ms (merge-rollup): 3,813 (+57%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
64 txs

l1_rollup_calldata_size_in_bytes
740
740
740

l1_rollup_calldata_gas
6,680
6,668
6,692

l1_rollup_execution_gas
586,865
586,853
586,877

l2_block_processing_time_in_ms
1,358
5,072
10,066 (-1%)

l2_block_building_time_in_ms
22,803
89,863
179,471

l2_block_rollup_simulation_time_in_ms
22,663
89,375
178,521

l2_block_public_tx_process_time_in_ms
8,970
35,109
70,342

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
15,602 (+1%)
28,621

node_database_size_in_bytes
22,892,624
39,460,944

pxe_database_size_in_bytes
29,868
59,425

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes
circuit_witness_generation_time_in_ms
circuit_proving_time_in_ms
circuit_proof_size_in_bytes

private-kernel-init
112
16,772
33,766
N/A
N/A
N/A

private-kernel-inner
312 (-1%)
57,607
33,766
N/A
N/A
N/A

private-kernel-reset
559 (-1%)
200,856
33,766
N/A
N/A
N/A

private-kernel-ordering
322
53,688
48,421
N/A
N/A
N/A

base-parity
7.48
128
64.0
287 (+2%)
13,452 (+1%)
2,208

root-parity
48.5
27,064
64.0
184 (-28%)
184,409 (+2%)
2,720

base-rollup
657
111,094
925
7,733
162,236 (+2%)
3,104

root-rollup
63.8
11,454
789
179 (-4%)
16,570
3,424

public-kernel-app-logic
122 (-1%)
61,017
51,751
296 (+9%)
434 (+5%)
65,344

public-kernel-tail
443
166,458
7,691
482 (+3%)
412 (+2%)
10,112

public-kernel-setup
101 (+2%)
61,017
51,751
311 (-1%)
399 (+4%)
65,344

public-kernel-teardown
103 (+2%)
61,017
51,751
270 (-1%)
342 (-2%)
65,344

merge-rollup
6.54 (+3%)
2,696
925
:warning: 276 (+123%)
:warning: 3,813 (+57%)
3,104

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
512 leaves
1024 leaves
2048 leaves
4096 leaves
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
11.0 (-1%)
17.9
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.7
31.8
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.639
0.548
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
51.8
80.7
260 (-1%)
508 (+1%)
986 (-1%)
1,947 (-1%)
N/A

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
543
1,055
2,079
4,127
N/A

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.529
0.498
0.474 (-1%)
0.474 (+1%)
0.467 (-1%)
0.465 (-1%)
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
61.2
121 (+1%)
375 (-1%)
746
1,463 (-1%)
2,918 (-1%)
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
106
208
692
1,363
2,707
5,395
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.534
0.540
0.510 (-1%)
0.512
0.507 (-1%)
0.507 (-1%)
N/A

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
67.2

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
108

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.588

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
51,016
1,046,607

Transaction size based on fee payment method
| Metric |  |
| - |  |
Transaction processing duration by data writes.

Metric
0 new note hashes
1 new note hashes
2 new note hashes

tx_pxe_processing_time_ms
2,366
2,123 (-1%)
5,288 (+2%)

Metric
0 public data writes
1 public data writes
2 public data writes
4 public data writes
8 public data writes

tx_sequencer_processing_time_ms
657
899 (-1%)
970 (+2%)
1,757 (+2%)
1,147 (+2%)

authors: AztecBot ludamad

repo: AztecProtocol/aztec-packages


text:
Remove generator dependency on TypeFormatters

duplicate of https://github.com/Azure/autorest.csharp/issues/4372


text:
Linux work needs to be done to enable "linuxfxversion" for .NET

We believe all of the work to support this has been done. Closing as resolved. (Thanks, @ankitkumarr !)

Anytime! ;)

authors: ankitkumarr brettsam fabiocav

repo: Azure/azure-functions-dotnet-worker


text:
Update CODEOWNERS

/azp run

authors: kasobol-msft zhenglaizhang

repo: Azure/azure-rest-api-specs


text:
Adding required service version to ListBlobs test

/azp run java - storage - tests

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-storage-blob

/azp run java - storage - tests

/azp run java - storage - tests

/azp run java - storage - tests

/azp run java - storage - tests

authors: azure-sdk ibrahimrabab

repo: Azure/azure-sdk-for-java


text:
[WIP] Schema Registry

API change check
API changes are not detected in this pull request.

Tracking issue: https://github.com/Azure/azure-sdk-tools/issues/6442

authors: azure-sdk samvaity


text:
fix: update governance types for relevant TimeLock events

:tada: This PR is included in version 1.21.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.21.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: NamelsKing axejintao

repo: Badger-Finance/badger-sdk


text:
求安装教程

我已经安装了beancount，为啥还是检测未安装啊

你可以在电脑命令行执行 bean-query --version，如果可以正常输出版本信息，就会检测通过。
否则，可以检查 beancount 是否配置到了 path 路径。
https://www.yuque.com/chuyi-ble7p/beancount-gs/eq81d8

authors: BaoXuebin GaoKaiNing

repo: BaoXuebin/beancount-gs


text:
Rename Detect Time Gap to Measure Elapsed & remove duplicate code.

Related to: #127

repo: BlueDotBrigade/weevil


text:
fix huffman table static declaration

Codecov Report

Merging #16 (685c3ef) into main (99a25a0) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##             main      #16   +/-   ##
=======================================
  Coverage   93.19%   93.19%
=======================================
  Files           4        4
  Lines         382      382
  Branches       59       59
=======================================
  Hits          356      356
  Misses         18       18
  Partials        8        8

Flag
Coverage Δ

unittests
93.19% <ø> (ø)

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

authors: BrianPugh codecov-commenter

repo: BrianPugh/tamp


text:
[gridtools] Adds conflicts with pgi.

launch jenkins gridtools

:green_circle: balfrin/integration_test/spack_info_gridtools.log
:green_circle: balfrin/integration_test/spack_spec_gridtools.log
:green_circle: balfrin/integration_test/spack_spec_gridtools_+cuda.log
:green_circle: balfrin/integration_test/spack_spec_gridtools_~cuda.log
:green_circle: balfrin/system_test/gridtools_@1.1.3_gcc.log
:green_circle: balfrin/system_test/gridtools_@1.1.3_nvhpc.log
:green_circle: balfrin/unit_test/summary.log

:green_circle: daint/integration_test/spack_info_gridtools.log
:green_circle: daint/integration_test/spack_spec_gridtools.log
:green_circle: daint/integration_test/spack_spec_gridtools_+cuda.log
:green_circle: daint/integration_test/spack_spec_gridtools_~cuda.log
:red_circle: daint/system_test/gridtools_@1.1.3_gcc.log
:green_circle: daint/system_test/gridtools_@1.1.3_nvhpc.log
:green_circle: daint/unit_test/summary.log

launch jenkins gridtools

:green_circle: tsa/integration_test/spack_info_gridtools.log
:green_circle: tsa/integration_test/spack_spec_gridtools.log
:green_circle: tsa/integration_test/spack_spec_gridtools_+cuda.log
:green_circle: tsa/integration_test/spack_spec_gridtools_~cuda.log
:green_circle: tsa/system_test/gridtools_@1.1.3_gcc.log
:green_circle: tsa/unit_test/summary.log

:green_circle: balfrin/integration_test/spack_info_gridtools.log
:green_circle: balfrin/integration_test/spack_spec_gridtools.log
:green_circle: balfrin/integration_test/spack_spec_gridtools_+cuda.log
:green_circle: balfrin/integration_test/spack_spec_gridtools_~cuda.log
:green_circle: balfrin/system_test/gridtools_@1.1.3_gcc.log
:green_circle: balfrin/system_test/gridtools_@1.1.3_nvhpc.log
:green_circle: balfrin/unit_test/summary.log

Jenkins failed to get the submodule spack in spack-c2sm on Daint 🤷

launch jenkins gridtools daint

:green_circle: tsa/unit_test/summary.log

:green_circle: balfrin/unit_test/summary.log

:green_circle: daint/integration_test/spack_info_gridtools.log
:green_circle: daint/integration_test/spack_spec_gridtools.log
:green_circle: daint/integration_test/spack_spec_gridtools_+cuda.log
:green_circle: daint/integration_test/spack_spec_gridtools_~cuda.log
:green_circle: daint/system_test/gridtools_@1.1.3_gcc.log
:green_circle: daint/system_test/gridtools_@1.1.3_nvhpc.log
:green_circle: daint/unit_test/summary.log

authors: PanicSheep jenkins-apn


text:
Delete lazy-lock.json

deleted lazy-lock.json

deleted lazy-lock.json


text:
Passing secrets from release workflow

#1108  👈
main

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

Join @CatChen and the rest of your teammates on  Graphite

repo: CatChen/eslint-suggestion-action


text:
Polish: try to enable end_of_line = lf in .editorconfig

Detect UTF-8 with BOM:
grep -IorHbm1 "^`echo -ne '\xef\xbb\xbf'`" . | sed '/:0:/!d;s/:0:.*//'

Filter git tracked files with BOM across history:
git filter-repo --refs "<test_branch!>" --replace-text <(echo 'regex:^\xEF\xBB\xBF==>')

license: Unlicense


text:
自建代理，突然提示failed, reason: connect ECONNREFUSED

@gygy  我使用的是该项目：linweiyuan / go-chatgpt-api ，可以成功自建反向代理 。 如果有x86的国外VPS可以试试。

@gygy  我使用的是该项目：linweiyuan / go-chatgpt-api ，可以成功自建反向代理 。 如果有x86的国外VPS可以试试。

我也是用这个。不过，经常有问题。

弄个定时重启就好了，我理解是有什么卡柱了

弄个定时重启就好了，我理解是有什么卡柱了

定时重启时怎么搞的

你用的是什么安装的呢？ Docker？

@1205129045x
用linux还不简单。 使用Cron即可。 可见： Linux基础 实用Linux命令一览表 - Bensz 的“crontab执行定期任务”小节。 你不是能用chatGPT，搜索一下，看能不能把握住。 加油！

docker 指向旁路由，直接翻墙，已经稳定一天多了。不再出现该问题了

试试我的 http://yl.iisai.cn 稳定快速

repo: Chanzhaoyu/chatgpt-web


text:
Briefs

I made a bit of confusion with the branches: this one includes both the teaching material post and the briefings post...

repo: ClimateCompatibleGrowth/guidelines


text:
[native/sqlite] improve

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

Opened unintentionally - closing.

authors: CLAassistant xsanm


text:
Testing Information : CCD SCAN : Total Circulating Supply

(CCDscan will probably be deployed on mainnet on 06-12)

@SRConcordium Can you check that on mainnet now pls?

repo: Concordium/concordium-scan


text:
feat(aptos): CW-11057 support aptos mainnet

Task linked: CW-11057 Support Aptos mainnet

repo: CoolBitX-Technology/coolwallet-sdk


text:
my second commit

this pull request contains Cpop's code for BillAPI class


text:
CASMSMF-7626: add sma-cli-utils to list of packages installed by cloud-init

/backport release/1.6

repo: Cray-HPE/csm


text:
Add goreportcard badge to README

yessir

authors: isimluk redhatrises

repo: CrowdStrike/falcon-operator


text:
[DICE-UNC/jargon#449] Bump version to 4.3.4.0-RELEASE (master)

Merging.

repo: DICE-UNC/jargon-pom


text:
chore(deps): upgrade node v22 lts

Des conflits sur package-lock, j'ai reinstall les dépendances et pousser le code mais ça a downgrade pas mal de dépendances dans le lock. Je pense que renovate va repasser pour mettre à jour le tout


text:
Log System

https://www.renpy.org/doc/html/developer_tools.html#renpy.log


text:
Release 3.1.0

Complete!

repo: DataBiosphere/findable-ui


text:
extra changes

Codecov Report

Merging #32 (bb6e429) into master (0e89125) will decrease coverage by 0.78%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #32      +/-   ##
==========================================
- Coverage   96.73%   95.95%   -0.79%
==========================================
  Files           7        7
  Lines         306      321      +15
==========================================
+ Hits          296      308      +12
- Misses         10       13       +3

Impacted Files
Coverage Δ

service/routes.py
100.00% <100.00%> (ø)

service/utils/error_handlers.py
89.47% <0.00%> (-7.90%)
:arrow_down:

Continue to review full report at Codecov.

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

authors: XinpingHuangE codecov-commenter

repo: DevopsShopcarts/shopcarts


text:
Collect dose from metadata files

This is done although only approximate values are available

repo: DiamondLightSource/python-murfey


text:
Include link in dev install tutorial to epics-containers devcontainer page

The URL that this change refers to is now live. Merging.

authors: callumforrester gilesknap


text:
Bug - Fixed build error in bytearray.go

Thanks @piyushhhxyz for this fix.

authors: piyushhhxyz psrvere

repo: DiceDB/dice


text:
Change position of Data in the hierarchy

depends on #136

Instead of #136 we do #252. All relevant tests pass, so we are done now.

authors: MxmUrw ooovi

repo: DiffMu/DiffPrivacyInferenceHs


text:
Robbe commentate

@Kaceba Robbè domani puoi dare tu un occhiata che chiede la command line?

Sì, dovrebbe solo essere un problema di duplici, me ne occupo io

authors: Djarrah Kaceba raffaellacioffi

repo: Djarrah/genuni-project


text:
next preview function added

carousel is a separate issue than the video. You need to put it in a different PR.

@hamxa152 your PR has video changes as well. Please do not mix changes from two different tickets into one PR. Each PR must only address one ticket.
Also as I have requested a dozen times - please put the link to the ticket in the comments of your commit. I don't see any links in your commit and don't know which PR they match to

repo: EnsembleUI/ensemble


text:
show methods as popover

done

repo: Entkenntnis/PurpleJ


text:
feat: [SEMANTICS-4590] fix showSuggestionsOnEmptyQuery props

Информационное сообщение: чтобы удобно запрашивать межкомандный ревью c github.com, заполните CODEOWNERS.

authors: Poline eg-deploy

repo: EruditorGroup/profi-design-system

license: ISC


text:
US #1: add horse names in database

/tina - can you have a look at this?

/tina - done

repo: EvelynChinarro/pet-clinic


text:
fix: Mobile-friendly Create/Edit Insight

:tada: This PR is included in version 3.5.7 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

repo: ExpediaGroup/insights-explorer


text:
Feature add pheno tab to pqtl table

This is no longer needed - this feature is coming as part of the other PR.

repo: FINNGEN/pheweb


text:
tôi muốn làm 1 bản dựng giá rẻ và tôi sử dụng esp 32U, Màn hình TFT 2.4 inch driver LIL 9341 và tôi không có mã nguồn và sơ đồ dây cụ thể liệu tôi dùng mã nguồn này của bạn thì nó có hoạt động được không hãy cho tôi lời khuyên cảm ơn người anh em :))

https://github.com/b00mekk/ESP32Marauder_ESP32-2432S024R_CYD
Is this what you need?

anh bạn tôi sử dụng màn hình ngoài thì nối dây như thế nào bạn có sơ đồ không

cảm ứng không hoạt động tôi phải làm sao


text:
Faq: php8 only typen

redaxo verwendet jetzt php 8.1 per default daher hat sich das erledigt erstmal

repo: FriendsOfREDAXO/rexstan


text:
Don't show progress donut to locked exercise links inside

Done!


text:
Fix properties bindings at ApplicationProperties

It was an IDE error. I need to install the Lombok plugin fo r eclipse to fix it.

repo: GLinBoy/linkshorter


text:
chore: upgrade graphql and enable typing for GT.Field

I have done a rebase @samerbuna

authors: nicolasburtey samerbuna

repo: GaloyMoney/galoy


text:
merged login.html into login.handlebars

LGTM


text:
Fix/fixed no id in cmv tests

:tada: This PR is included in version 5.0.3-rc.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

authors: BotellaA MelchiorSchuh

repo: Geode-solutions/OpenGeode-Inspector


text:
Replacing desktop with cpp for more platforms support

Oops

My bad with the title

Thanks!

repo: Geokureli/Newgrounds


text:
Paikkatietoasiantuntijana haluan antaa kaavamääräyksille teksti- ja numeerista tietoa, koska haluan tuottaa kaavalle kaavakartalle nimiöintejä, kaavakartalle selitteen sekä kaavaselosteen, jotta kaavasta tulee ymmärrettävä.

Kaavamääräystaulussa on kentät text_value ja numeric_value.

authors: msorvoja rlindb

repo: GispoCoding/hame-ryhti


text:
Improve Alertmanager discovery

Yes, this primarily makes it easier to use custom Endpoints objects as it no longer requires a matching Service

repo: GoogleCloudPlatform/prometheus-engine


text:
fix: dropdown width not being propery set

:tada: This PR is included in version 4.0.0-alpha.16 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.74 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.14 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0-alpha.6 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 4.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: chrisolsen tzuge

repo: GovAlta/ui-components


text:
Add georec, mxv, radrec, spkezr, vcrss, vdot, xpose

Dear @s-rah
First of all, thank you for your pull request!!
You're the first one that I receive and I'm learning from it.
I've been off the development of rust-spice for a bit as I got from it everything that I needed. But like you can see, many functions are still missing. Thank you for your changes, bringing more functions and more excitement to me to continue this project.
Before talking about the PR, I got couple of questions:

how did you find the project structure?
does the project structure make sense?
what would you change in the project structure?

More questions concerning the PR:

did you run the tests of the project before submitting PR?
if you ran the tests, went they well?

Status of your PR:
I think I should not accept the PR in this state. You requested it to be on the "main" branch, which is 8 commits behind the "dev" branch. These commits are fixing a bug on "main" that I found lately about FFI with C strings.
I should have written a contribution document with my expectations, I'm sorry for that I'll do it immediately.
Is it possible that you re-publish your pull-request on the "dev" branch? You will notice some changes about how to defines input and output strings.
After you PR, we can merge the "dev" branch into "main".
Let me know if this plan fits with you. I'm open to any remark and advice.

Hi!
Thank you for this project.

how did you find the project structure?
does the project structure make sense?

The project structure is great, it was very quick to get going.

what would you change in the project structure?

Currently the packaged metakernel (rsc/krn/hera_study_PO_EMA_2024.tm), which most of the tests use, references  "/home/greg/rob/hera/kernels" which means they fail out-of-the-box (I ended up overriding the file locally) - it is probably worth considering packaging a standalone test kernel for the tests with the relevant files so they run nicely on their own.
Some of the -derive annotations like (return_output) required some experiment to work out what they did and when they should be included.

did you run the tests of the project before submitting PR?

Yes

if you ran the tests, went they well?

Yes (with the caveat above about locally overriding the kernel)

Is it possible that you re-publish your pull-request on the "dev" branch?

Makes sense. Will do.

authors: GregoireHENRY s-rah

repo: GregoireHENRY/rust-spice


text:
test

Codecov Report
Patch coverage has no change and project coverage change: -3.69 :warning:

Comparison is base (dad9050) 74.19% compared to head (25ec3cb) 70.50%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main       #8      +/-   ##
==========================================
- Coverage   74.19%   70.50%   -3.69%
==========================================
  Files         176      176
  Lines       17209    17209
  Branches      286      201      -85
==========================================
- Hits        12768    12134     -634
- Misses       4441     5075     +634

Flag
Coverage Δ

bot
40.64% <ø> (ø)

bot-unit
40.64% <ø> (ø)

discordeno
100.00% <ø> (ø)

discordeno-unit
100.00% <ø> (ø)

gateway
29.98% <ø> (-44.22%)
:arrow_down:

gateway-integration
?

gateway-unit
29.98% <ø> (ø)

rest
71.97% <ø> (ø)

rest-unit
71.97% <ø> (ø)

types
100.00% <ø> (ø)

types-unit
100.00% <ø> (ø)

utils
95.24% <ø> (ø)

utils-unit
95.24% <ø> (ø)

see 2 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


text:
Revert failed publish

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant mattmurp

repo: HCL-TECH-SOFTWARE/appscan-sdk


text:
WIP Do not merge : Update from internal to external public repo

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant gyanenduprakash


text:
feat: 🎸 add simple SFC file ast snapshot testing

I don't think standalone SFC file is good for snapshot testing. The compiler core integration test still lacks a lot option tuning, which makes the compilation output different from real Vue compiler.
We  can have a E2E test in elsewhere but not in compiler crate for now.

authors: HerringtonDarkholme IWANABETHATGUY


text:
Minor typo fix

Typo was fixed in latest release.

authors: HomeSpan stockhuman

repo: HomeSpan/HomeSpan


text:
introduce arabic to normalized sacrebleu

@pklpriv Can you add support for Korean also?

@yoavkatz could you please take a look and merge ?. Thx.

authors: LukaszCmielowski piotrhelm pklpriv

repo: IBM/unitxt


text:
Creating EvaluatorBase

@ferag EvaluatorBase has oai_base as input argument. Since we have plugins that don't use OAI-PMH, it would make sense to change the name of this variable.

@ferag EvaluatorBase has oai_base as input argument. Since we have plugins that don't use OAI-PMH, it would make sense to change the name of this variable.

Do you think is it OK to use a general "api_endpoint" variable?

sure. Last commit address this, but not tested all the plugins

authors: ferag orviz


text:
Bug: Reward log query crashes when associated content was deleted

@LG1401 I added this issue, 1 SP should be enough


text:
#328 fix

please check my pr


text:
Tech Stack and Team Allocation

Team Member
Track
Responsibilities

Evgeny Bobkunov
Project Management
Team management, GitHub repository support, Issues creation and task tracking

Matvey Korinenko
Team Lead, Fullstack
Creating a Telegram bot as a frontend interface for users, Development of the project architecture, Working with MongoDB database

Artur Mukhutdinov
Backend, Deputy Team Lead
Development of API and architecture, Working with PostgreSQL database

Daniil Prostiruk
Frontend
Development of Telegram WebApp for the administration panel

Rufina Gafiiatullina
ML, DS
Exploring the feasibility of applying LLM to the project, Development of a fault detection algorithm


text:
Generate a manifest file for wolvic by jinja2 template

Related PR in igalia/wolvic : https://github.com/Igalia/wolvic/pull/521

repo: Igalia/wolvic-chromium


text:
Very good work, looking forward to the day it is completed

Super Boulot !!! J'attends aussi avec impatience le produit finis.
Bon courage

authors: DRWELLBABA LuckyFishGeek


text:
Daniwk #21 minor changes docs

Close #21
Thank you!! 🚀

authors: JonasKs daniwk

repo: Intility/fastapi-azure-auth


text:
Fix null type check for array in plugin

Can you make the merge, because we have the same problem ?

@thdgeorge I'm not able to merge this PR unfortunately.

Thanks a lot for the fix @RickvanB

authors: JaJuMa RickvanB thdgeorge

repo: JaJuMa-GmbH/hyva-faq-widget


text:
How to contact you through email?

My email is janaldo@mail.dlut.edu.cn

repo: JanaldoChen/Anim-NeRF


text:
Expand IEnvelopeRule to also enrich Otel Activity in outgoing messages

I don't think this has much applicability. Basically just saying that any sending endpoint could enrich the Otel information on outgoing messages. Nobody has asked for this.

repo: JasperFx/wolverine


text:
Automatically build and deploy front end code

Closed by a718b246d7871471fab36cbc720a4a470a0e928d

repo: JayNewstrom/InboundEmail