Build verification : Storybook  Version 1.1.5 received on 8th July 2024

Sr.No
Task ID
Bug Title
Status
Remark

1
400
Storybook   > Check scrollbar position in storybook It is not right aligned properly ·   Raaghu Design System Storybook - React (github.com)
Closed

2
438
Storybook   > Components >Organization Tree> Default > Three dots button   isn't clickable. · Raaghu Design System Storybook - React (github.com)
Closed

3
449
Storybook   > Components >Alert Popup > Default > When click on Alert Popup   button and go to next component is not working. · Raaghu Design System   Storybook - React (github.com)
Closed

4
452
Storybook   > Components >Dynamic Entity Properties > Default >Placeholder   select entity select parameter is required · Raaghu Design System Storybook -   React (github.com)
Closed

5
460
Storybook   > Components >Premium Support > Default >Unable to see images. ·   Raaghu Design System Storybook - React (github.com)
Closed

6
463
Storybook   > Elements >Color Picker> Default >Selecting small, large mobile   view Border issue. · Raaghu Design System Storybook - React (github.com)
Closed

7
464
Storybook   > Elements>Navbar > Default >Selecting dark theme navbar content   is not display · Raaghu Design System Storybook - React (github.com)
Closed

8
466
Components   > File Uploader > After submitting uploaded file is not clear. · Raaghu   Design System Storybook - React (github.com)
Closed

9
403
Components   > Api resource basic > Ui label name and action data name are different   · Raaghu Design System Storybook - React (github.com)
Closed

10
307
Bug   : Component > Profile edit > Image is missing · Raaghu Design System   Storybook - React (github.com)
Closed

11
419
Storybook   > Component >Order Confirmation> Default > Video is not display ·   Raaghu Design System Storybook - React (github.com)
Closed

12
436
Storybook   > Components >Integration > Default > Selecting the dark theme   Notion and GitHub logos are not displayed. · Raaghu Design System Storybook -   React
Closed

13
437
Storybook   > Components >Features New > Default >Restore to Default and Save   buttons are not working. · Raaghu Design System Storybook - React   (github.com)
Closed

14
465
Storybook   > Elements>Button Group> Default >Selecting color Variant light   text is not display. · Raaghu Design System Storybook - React (github.com)
Closed

15
469
DS   > Implement Changes to Urls through application for Updated Urls · Raaghu   Design System Storybook - React (github.com)
Reopen

16
429
Storybook   > Components >Download Collection> Default > After click on   download icon no data display in action · Raaghu Design System Storybook -   React (github.com)
Reopen

17
448
Storybook   > Components >Visual Setting > Default >Alignment issue   Subheader, Menu, Footer, click on dropdown chevron is not upward and downward   · Raaghu Design System Storybook - React (github.com)
Reopen

Sr.No	Task ID	Bug Title	Status	Remark
1	400	[Storybook > Check scrollbar position in storybook It is not right aligned properly · Raaghu Design System Storybook - React (github.com)](https://github.com/orgs/Wai-Technologies/projects/16/views/1?filterQuery=status%3AResolved&pane=issue&itemId=67295472)	Closed
2	438	[Storybook > Components >Organization Tree> Default > Three dots button isn't clickable. · Raaghu Design System Storybook - React (github.com)](https://github.com/orgs/Wai-Technologies/projects/16/views/1?filterQuery=status%3AResolved&pane=issue&itemId=68529103)	Closed
3	449	[Storybook > Components >Alert Popup > Default > When click on Alert Popup button and go to next component is not working. · Raaghu Design System Storybook - React (github.com)](https://github.com/orgs/Wai-Technologies/projects/16/views/1?filterQuery=status%3AResolved&pane=issue&itemId=68980735)	Closed
4	452	[Storybook > Components >Dynamic Entity Properties > Default >Placeholder select entity select parameter is required · Raaghu Design System Storybook - React (github.com)](https://github.com/orgs/Wai-Technologies/projects/16/views/1?filterQuery=status%3AResolved&pane=issue&itemId=69120689)	Closed
5	460	[Storybook > Components >Premium Support > Default >Unable to see images. · Raaghu Design System Storybook - React (github.com)](https://github.com/orgs/Wai-Technologies/projects/16/views/1?filterQuery=status%3AResolved&pane=issue&itemId=69476757)	Closed
6	463	[Storybook > Elements >Color Picker> Default >Selecting small, large mobile view Border issue. · Raaghu Design System Storybook - React (github.com)](https://github.com/orgs/Wai-Technologies/projects/16/views/1?filterQuery=status%3AResolved&pane=issue&itemId=69811472)	Closed
7	464	[Storybook > Elements>Navbar > Default >Selecting dark theme navbar content is not display · Raaghu Design System Storybook - React (github.com)](https://github.com/orgs/Wai-Technologies/projects/16/views/1?filterQuery=status%3AResolved&pane=issue&itemId=69812756)	Closed
8	466	[Components > File Uploader > After submitting uploaded file is not clear. · Raaghu Design System Storybook - React (github.com)](https://github.com/orgs/Wai-Technologies/projects/16/views/1?filterQuery=status%3AResolved&pane=issue&itemId=69899325)	Closed
9	403	[Components > Api resource basic > Ui label name and action data name are different · Raaghu Design System Storybook - React (github.com)](https://github.com/orgs/Wai-Technologies/projects/16/views/1?filterQuery=status%3AResolved&pane=issue&itemId=67442805)	Closed
10	307	[Bug : Component > Profile edit > Image is missing · Raaghu Design System Storybook - React (github.com)](https://github.com/orgs/Wai-Technologies/projects/16/views/1?filterQuery=status%3AResolved&pane=issue&itemId=61636158)	Closed
11	419	[Storybook > Component >Order Confirmation> Default > Video is not display · Raaghu Design System Storybook - React (github.com)](https://github.com/orgs/Wai-Technologies/projects/16/views/1?filterQuery=status%3AResolved&pane=issue&itemId=67672097)	Closed
12	436	[Storybook > Components >Integration > Default > Selecting the dark theme Notion and GitHub logos are not displayed. · Raaghu Design System Storybook - React](https://github.com/orgs/Wai-Technologies/projects/16/views/1?filterQuery=status%3AResolved&pane=issue&itemId=68522627)	Closed
13	437	[Storybook > Components >Features New > Default >Restore to Default and Save buttons are not working. · Raaghu Design System Storybook - React (github.com)](https://github.com/orgs/Wai-Technologies/projects/16/views/1?filterQuery=status%3AResolved&pane=issue&itemId=68524533)	Closed
14	465	[Storybook > Elements>Button Group> Default >Selecting color Variant light text is not display. · Raaghu Design System Storybook - React (github.com)](https://github.com/orgs/Wai-Technologies/projects/16/views/1?filterQuery=status%3AResolved&pane=issue&itemId=69825134)	Closed
15	469	[DS > Implement Changes to Urls through application for Updated Urls · Raaghu Design System Storybook - React (github.com)](https://github.com/orgs/Wai-Technologies/projects/16/views/1?filterQuery=status%3AResolved&pane=issue&itemId=69909244)	Reopen
16	429	[Storybook > Components >Download Collection> Default > After click on download icon no data display in action · Raaghu Design System Storybook - React (github.com)](https://github.com/orgs/Wai-Technologies/projects/16/views/1?filterQuery=status%3AResolved&pane=issue&itemId=68125728)	Reopen
17	448	[Storybook > Components >Visual Setting > Default >Alignment issue Subheader, Menu, Footer, click on dropdown chevron is not upward and downward · Raaghu Design System Storybook - React (github.com)](https://github.com/orgs/Wai-Technologies/projects/16/views/1?filterQuery=status%3AResolved&pane=issue&itemId=68978118)	Reopen

Total Bugs Tested :17
Closed Bug: 15
Reopened Bug: 2


Correct StreamField block alignment & hierarchy highlighting

Alignment

[ ] Position of three-dots controls
[ ] Position of "Add block" trigger

Parked
Waiting on larger redesign:

[ ] Extra space on the RHS of fields
[ ] Avoid highlighting sibling blocks as well as currently-focused blocks
[ ] Correctly show StreamField "Add" button based on intended design rules
[ ] Spacing around icons
[ ] Follow-up to #8983. I believe there are some inconsistencies in the implementation compared to the designs, which require a review and likely a few changes to the styles.
[ ] Also see https://www.figma.com/file/h67EsVXdWsfu38WGGxWfpi/Wagtail-Design-System?node-id=9534%3A45339&t=2riUNZB8RwYt0uDO-4

See https://github.com/wagtail/wagtail/issues/9945 for larger redesign.


Fix: mongoid_slug:set rake task for Mongoid 5. [DON'T MERGE]

Need to make sure the mongoid HEAD build passes, right now there're some issues with mongoid/observers, see https://github.com/chamnap/mongoid-observers/pull/2.

https://travis-ci.org/Sharevari-Inc/mongoid/builds/136339223

Tests against mri 2.3.1, rails 5.0.0.rc1

[ ] mongoid tests passed
[ ] mongoid-observers tests passed
[ ] mongoid_paranoia tests passed
[ ] mongoid-slug head tests passed

@dblock want we target master branch on Mongoid HEAD?
https://github.com/Sharevari-Inc/mongoid-slug/commit/ab93caaa680c705a97706e3c11f105e9dff4d85f

Yes @Fudoshiki, but generally I am not too excited about trying to keep up with mongoid until there's some RC or something. Of course I'd take pull requests if someone is motivated to use the edge version(s).

@dblock Can You accept PR and merger with master

@dblock I will create PR with simmilar tasks https://github.com/simi/mongoid_paranoia/pull/44

@dblock
I targeted on Mongoid master branch, can we drop Mongoid 4/5 and ruby < 2.2.2 support in master branch?
https://github.com/simi/mongoid_paranoia/pull/44

@Fudoshiki I'd like not to, unless we must because we just can't make it work.

ok

We can close this

Closing in favor of #219 .


Fix integer overflow bug

Codecov Report

Merging #305 (5696d56) into master (ecbfb40) will decrease coverage by 0.05%.
The diff coverage is 76.92%.

@@             Coverage Diff              @@
##             master     #305      +/-   ##
============================================
- Coverage     71.20%   71.15%   -0.06%
- Complexity     1088     1091       +3
============================================
  Files           164      164
  Lines          3289     3304      +15
  Branches        459      462       +3
============================================
+ Hits           2342     2351       +9
- Misses          815      818       +3
- Partials        132      135       +3

Impacted Files
Coverage Δ

...main/java/seedu/address/commons/core/Messages.java
0.00% <ø> (ø)

...eedu/address/logic/commands/DeleteExamCommand.java
87.50% <50.00%> (-12.50%)
:arrow_down:

...u/address/logic/commands/ListExamTasksCommand.java
88.88% <50.00%> (-11.12%)
:arrow_down:

...eedu/address/logic/commands/UnlinkExamCommand.java
88.88% <60.00%> (-11.12%)
:arrow_down:

.../address/logic/parser/DeleteExamCommandParser.java
100.00% <100.00%> (ø)

...dress/logic/parser/ListExamTasksCommandParser.java
100.00% <100.00%> (ø)

.../address/logic/parser/UnlinkExamCommandParser.java
100.00% <100.00%> (ø)

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


⚠ ClamAV has degraded performance

In 10e2187, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 75 ms

Resolved: ClamAV performance has improved in 644f128.


Babel preset absoluteRuntime docs

Documented babel-preset-react-app absoluteRuntime option

Thanks for this @iddan. Out of interest, what was the motivation for this PR? Was it an issue you faced yourself? And if so, why did you need to modify this setting?
Thanks!

If I remember correctly I stumbled upon it while trying to integrate Storybook

I think this should be merged! It turns out that this plugin was causing the contenthash for my JS bundles to change when building the exact same code between two different directories. And I didn't know about it because minification was stripping out the absolute paths from the final bundle. I'm not sure why absoluteRuntime needs to be true anyways, perhaps it should default to false instead?
See: https://github.com/webpack/webpack/issues/1155 and https://github.com/webpack/webpack/issues/7179

Why was this not merged?

Sorry this got missed. Thanks @iddan.


Try to register a handle for .pr0 files

Check this:
https://docs.microsoft.com/en-us/microsoft-edge/progressive-web-apps-chromium/how-to/handle-files
https://developer.chrome.com/docs/apps/manifest/file_handlers/
The idea is to be able to open payment request files (.pr0) directly from links or the device's file system.

wrong repo


Improving head detector

Description
Some improvements and refactoring to head_detector. Most notably, I changed the error metrics to one harder to Goodhart (based on conversation on the mechinterp Slack). Also, added many more tests and support for passing multiple sequences to detect_head.
Type of change
Please delete options that are not relevant.

[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)

I changed the error metric in head_detector (as suggested by Jay), so I needed

Checklist:

[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works

Also, refactored the tests quite extensively

[x] New and existing unit tests pass locally with my changes
[ ] I have not rewritten tests relating to key interfaces which would affect backward compatibility

Since I changed the error metric, I had to rewrite expected outputs in tests (test_head_detector.py)

Hey sounds good. A few comments:

[ ] 1. Can you explain how the metrics are now harder to goodhart?
[ ] 2. As annoying as it sounds, can you please write tests for the two functions added to utils? Moving forward I'm trying to be strict about this on principle.
[ ] 3. What was the configuration of your pylintrc file? I'd be open to a PR with suggestions for one... :D

Things I liked about this PR:

Many separate commits are good practice!

Can you explain how the metrics are now harder to goodhart?

Until now, the score saying how well the detection pattern matches each attention head is calculated as the fraction of the attention pattern kept. So you can goodhart it by keeping all attention, i.e., by passing a detection pattern of all ones (or at least along the main diagonal and below it). The new metric is 1 - mean absolute difference between the attention pattern and the detection pattern. It ranges from -1 to 1, where 1 is perfect match and -1 total mismatch.

As annoying as it sounds, can you please write tests for the two functions added to utils? Moving forward I'm trying to be strict about this on principle.

No problem, I'm very sympathetic to that approach. Done.

What was the configuration of your pylintrc file? I'd be open to a PR with suggestions for one... :D

It's mostly basic settings + disabling some warnings (like missing-module-docstring) that are not relevant for the project and making valid names for arguments, variables, and attributes more generic because pylint's default snake_case doesn't include names like x or t1.

Until now, the score saying how well the detection pattern matches each
attention head is calculated as the fraction of the attention pattern kept.
So you can goodhart it by keeping all attention, i.e., by passing a
detection pattern of all ones (or at least along the main diagonal and
below it). The new metric is 1 - mean absolute difference between the
attention pattern and the detection pattern. It ranges from -1 to 1, where
1 is perfect match and -1 total mismatch.

Hmm, I think I disagree with this. If you have a head which eg attends to
the subject of a sentence, but that sentence is sometimes a single token
and sometimes two tokens, I want to be able to give a mask which has 1s on
all tokens of the subject, but which does not give a different score for
two vs one token words. And I believe the boolean mask swtup allows this
but your's doesn't?
More generally I don't care about this kind of Good Harting. If people set
a dumb metric that's their problem
On Sat, 29 Apr 2023, 10:09 am MatthewBaggins, @.***>
wrote:

Reopened #255 https://github.com/neelnanda-io/TransformerLens/pull/255.
—
Reply to this email directly, view it on GitHub
https://github.com/neelnanda-io/TransformerLens/pull/255#event-9130282718,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASRPNKOWI4FRSLO3WDK6CO3XDTLFDANCNFSM6AAAAAAXIRSM6I
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>

@JayBaileyCS do you think there are cases, where somebody who is not trying to goodhart the detector would rather use the new metric instead of the old one?
(for context: changing the metric was Jay's idea)
(also, the commit as is allows you to use the old metric, you just need to specify it when calling detect_head)

For context, I have used the "total attention paid to any token in this
word" trick when eg looking for translation heads. Having the option
available seems good to me though
On Sun, 30 Apr 2023 at 07:44, MatthewBaggins @.***>
wrote:

@JayBaileyCS https://github.com/JayBaileyCS do you think there are
cases, where somebody who is not trying to goodhart the detector would
rather use the new metric instead of the old one?
(for context: changing the metric was Jay's idea)
(also, the commit as is allows you to use the old metric, you just need to
specify it when calling detect_head)
—
Reply to this email directly, view it on GitHub
https://github.com/neelnanda-io/TransformerLens/pull/255#issuecomment-1528952535,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASRPNKJNVBAXKBX4VKTZTJTXDYC4VANCNFSM6AAAAAAXIRSM6I
.
You are receiving this because you commented.Message ID:
@.***>

So how about we make the old method the default and keep the option to use the new one?

Sounds good to me!
On Mon, 1 May 2023, 6:19 pm MatthewBaggins, @.***>
wrote:

So how about we make the old method the default and keep the option to use
the new one?
—
Reply to this email directly, view it on GitHub
https://github.com/neelnanda-io/TransformerLens/pull/255#issuecomment-1529914233,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASRPNKIW2YTTPFVL6Y3WDELXD7O7XANCNFSM6AAAAAAXIRSM6I
.
You are receiving this because you commented.Message ID:
@.***>

So, the Goodharting was what caused me to notice there was a problem, not being the problem in and of itself.
The advantage of switching to absolute prediction error is that you can make more precise predictions, and have that measured in the score. You can predict, for instance, 0.2 attention to X, and 0.8 attention to Y, and your score will be better if your prediction is closer - the original "mul" metric does not allow this, you'll get the same score if attention is 0.2, 0.8 or 0.5, 0.5 or 0.8, 0.2.
However, your example from above makes a lot of sense Neel. What you could do with absolute error would be:

Write code to identify the subject in the sentence.
Determine how many tokens that subject has.
Create your prediction based on that (i.e, 1 on subject if one token, 0.5, 0.5 if two tokens)

And this would work with absolute error. However, this is also more complicated and time-intensive than "Okay, I want to see how much attention is paid to this word in particular, and I don't care exactly how much attention is paid to which token yet" in which case the original metric is better.
So, I think that for quick or exploratory investigations, the original metric may be superior. For precise examinations where you're trying to reproduce as much functionality as possible or really test your understanding of the attention head, absolute error is best.
As a result, I agree with Neel that the original metric makes sense as the default option, with absolute prediction error existing for people who want to do more precise investigations. Whichever metric is best to start with, that should be the default option. Absolute error is there for people who want to dive in more.
It'd be nice to adjust the demo to make this clear, but I am happy to do that myself after this PR goes through, since I have the most context about it.

Closing this as it seems done. Good work!
A note for future work: I think PR's and conversations are best motivated in relation to existing research. The space of features is much larger than the space of features that are directly useful to research. That's not to say this conversation/PR wasn't valuable, but I want to try to make sure we have mental space/room to find work motivated by progress in MI possibly more closely.
By analogy, companies with software products must be very careful about which features they accept, even going so far as saying things like "if 100 people asked for a feature, don't' building it, wait for 1000" (insert numbers relevant to the scale of the operation.  This is especially important for software because of the capacity / maintenance cost which is often underestimated.
In the future, I'm going to try to establish the value of things like this more strongly so that people can grade invested effort accordingly. I also think this is a hard thing to do so I'll approach the topic with humility and a collaborative mindset.


Paket adds a BOM to xxproj files

Description
It would seem that Paket v4.4.0 adds a BOM to my xml files, widely considered a bad thing.

Repro steps
Please provide the steps required to reproduce the problem

paket install

cat myproj.fsproj

If someone wants to address this then it would be appreciated.

Hi - @haf do you think this is since 4.4 or do we need to pin down the regression version?

It's pretty new, but I'm not sure which version it's from, I'm afraid.

I assume we'd never want to have a change regarding the BOM, right? Apparently .fsproj files created in Visual Studio have one, those created by Ionide/Forge don't.
My impression is that writing a BOM or not comes down to https://github.com/fsprojects/Paket/blob/master/src/Paket.Core/PaketConfigFiles/ProjectFile.fs#L1187 (or rather the configuration of the FileStream/StreamWriter used), but any fixed decision there would be wrong for "half" of the user's project files - unless we go back to the existing file, ask for its BOM and adjust the encoding accordingly before writing the XML document.

Yes we don't want to write that. PRs welcome
Am 31.07.2017 05:46 schrieb "TeaDrivenDev"<EMAIL_ADDRESS>
I assume we'd never want to have a change regarding the BOM, right?
Apparently .fsproj files created in Visual Studio have one, those
created by Ionide/Forge don't.
My impression is that writing a BOM or not comes down to
https://github.com/fsprojects/Paket/blob/master/src/Paket.
Core/PaketConfigFiles/ProjectFile.fs#L1187 (or rather the configuration
of the FileStream/StreamWriter used), but any fixed decision there would be
wrong for "half" of the user's project files - unless we go back to the
existing file, ask for its BOM and adjust the encoding accordingly before
writing the XML document.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/fsprojects/Paket/issues/2271#issuecomment-318960381,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNHJaUuCA3w8s1VCWhRmq0s64VEdiks5sTU4NgaJpZM4NFBWo
.

@forki Isn't this issue fixed by #2575

Yes, thanks


Add DetailSections, DetailSection, DetailRow, and AccordionRow components

Adds several components in the context of thermostat details—wanting to get this in so that active engs can pull from the same set of components instead of duplicating efforts.

DetailSections • Used to group several DetailSection components together
DetailSection • A group of DetailRow or AccordionRow components
DetailRow • A basic detail row (like "Fan mode") that does not expand
AccordionRow • A DetailRow that expands when clicked.

I might have went a bit overkill with the amount of stories—if so, let me know and I can consolidate.

In Figma, these are called "control cells" (and derivatives). I think "section" and "row" is a bit more specific, but I can rename them if anybody has any strong opinions here.

Are all of these meant to be used individually, or are there only one or two that will be used?

Are all of these meant to be used individually, or are there only one or two that will be used?

@razor-x Not sure I fully understand your question. They will all be used to construct the various detail layouts—all in different contexts. I'm not sure if there's a good way to combine them because each context is a bit different (and it'd be a little strange to, for instance, proxy the rendering through a wrapping component (like DetailSection having a details prop))

Diff not found!

Ok, more specifically, would the Row components ever be used outside this folder?

Ok, more specifically, would the Row components ever be used outside this folder?

@razor-x Yeah, they will be used by the ThermostatDeviceDetails component under seam/components/DeviceDetails as well as within @Andrewjeska's components, but I'm not sure where those are located

the design is slightly different
We could move this up a level to individual folders in lib/ui/ and consider them generic ui building blocks. Components that don't use these yet can then be upgraded to use them. This will move things in a more uniform direction where any slight differences appear clearly as overrides on these components vs buried in lots of duplicated but not quite the same code / styles. Otherwise down the road, it won't be clear if slight differences are intentional or just a mistake where something copy/pasted looks like it didn't get updated.

We could move this up a level to individual folders in lib/ui/ and consider them generic ui building blocks. Components that don't use these yet can then be eventually upgraded to use them. [...]

@razor-x are you thinking just the lib/ui/layout folder? Or did you want a special folder just for these?

We could move this up a level to individual folders in lib/ui/ and consider them generic ui building blocks. Components that don't use these yet can then be eventually upgraded to use them. [...]

@razor-x are you thinking just the lib/ui/layout folder? Or did you want a special folder just for these?

That could work. As the ui folder gets bigger we may decide to re-group things a bit once better categories emerge. I am ok with flat or folder per-component. Main thing is getting this out of the thermostat namespace so they can be used elsewhere.


Syntastic + nerdtree-git-plugin: IOError: [Errno 2] No such file or directory: 'NERD_tree_1'

I get this error when using nerdtree-git-plugin + syntastic:
NERDTree: Refreshing the root node. This could take a while... DONE
syntastic: error: checker output:
Traceback (most recent call last):
  File "/home/jerome/.vim/bundle/syntastic/syntax_checkers/python/compile.py", line 11, in <module>
    compile(open(argv[1]).read(), argv[1], 'exec', 0, 1)
IOError: [Errno 2] No such file or directory: 'NERD_tree_1'
syntastic: error: checker python/python returned abnormal status 1

If I remove nerdtree-git-plugin, it works fine.
Using latest versions of nerdtree and syntastic, git bisect tells me that the first bad commit in nerdtree-git-plugin is 6564bb5 but this is because when I select an earlier commit I get other errors masking this one.
Using latest versions of nerdtree and nerdtree-git-plugin, git bisect tells me that the first bad commit in syntastic is adf899f.
I'm not sure which pluging is guilty, here. I emptied my .vimrc to rule it out.

I asked on Vi and Vim and was told by Syntastic developer that this is known issue. He proposed a fix here.

This pull request provides a solution.


Calculate the pmtu instead of hardcoding it

Currently the mtu is hardcoded to 1450. While this works for most cases, its not valid when the assumed underlay is an overlay itself. Use tracepath to reach the master from the node and subtract 50 from it?

Performance team decided to shy away from PTMU in the network-throughput tuned profile, collectively felt that changing the MTU on an interface would really surprise sysadmins.  Our implementation idea was PMTU to the default gateway...where else would you measure to?
OpenStack does have something interesting though:  they auto-set the Neutron interface to DHCP-MTU-minus 50.
So, we might need 2 solutions; one for OSE and we might get it for free when running on OpenStack.  Or perhaps adopt OpenStack technique for OSE.  This could be an interesting topic for the f2f.

We have decided not to change the MTU, default value will be 1450 but there will be config option for the admin to fine tune the value based on their need (like 9000 for jumbo frames).

Cool, yeah.   If a user needs the throughput improvement from jumbo frames, they probably want to get that data off of the overlay network.  If they're CPU bottlenecked in a packets-per-second type of workload, that's a separate issue.

Fix merged.


MNT: rerender

Hi! This is the friendly automated conda-forge-webservice.
I've started rerendering the recipe as instructed in #3.
If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!
Here's a checklist to do before merging.

[ ] Bump the build number if needed

Fixes #3

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe/meta.yaml:

ℹ No valid build backend found for Python recipe for package orange3-textable using pip. Python recipes using pip need to explicitly specify a build backend in the host section. If your recipe has built with only pip in the host section in the past, you likely should add setuptools to the host section of your recipe.
ℹ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.

For the host section of the recipe, you should usually use python {{ python_min }} for the python entry.
For the run section of the recipe, you should usually use python >={{ python_min }} for the python entry.
For the test.requires section of the recipe, you should usually use python {{ python_min }} for the python entry.
If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

ℹ PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12122509108. Examine the logs at this URL for more detail.

Looking at entry points https://github.com/conda-forge/orange3-singlecell-feedstock/blob/main/recipe/meta.yaml

setuptools 60.9.3 + pip 22.0.3

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12168335287. Examine the logs at this URL for more detail.


Fix clock on first boot

Configure the hardware clock
Run NTP?

https://wiki.odroid.com/odroid-n2/application_note/rtc_wakeup_time manually?

Let's do it manually when configuring petitboot for now.


[FEATURE REQUEST] Hide effects on EMI overlay

As stated in the discord, would you be able to include an option for the effects to be hidden in the EMI overlay. Since I use InventoryHUD+, I have these effects in another location on screen. Thank you so much.

Implemented in 1.1.15, thanks for the suggestion


start slowly

wsl starts slowly with Windows terminal

/logs

Same problem
Slow startup(cold), and even slow login(hot)


updated String class doc with 'allow_empty' optional argument info

(Update to the class reference - String)
Added an explanation for what the 'allow_empty' optional argument does in several String methods.

Thanks! And congrats for your first merged Godot contribution :tada:

Cherry-picked for 3.6.

Cherry-picked for 3.5.1.


Add missing tests for optimisation algorithms

As mentioned in #67 we are still missing unit tests for functions already merged into the master branch, one of these implementations are optimisation algorithms.
Tests for sampling-based algorithms are already implemented within the master branch, but not yet activated, this could be fixed asap.
Tests for trajectory-based algorithms are already in progress by Daniel (see fdeac7ecc8495ca828378917be6acccab644684c)

Done by 3751b33a9572c94112341b3f21f60a88f035de98


Add optional columns to public stats page

I haven't checked yet but we also need to make sure it's mobile friendly

Looks as okay as before I would say. Without any optional columns (I already scrolled a bit to the right on both screenshots):

After:

Until you start searching for a player

Until you start searching for a player

Good point. What about that:

And when searching:

It's basically just flex-wrap set to wrap 🤷


Add flutter pub.dev search extension

Description
This extension lets you search and copy the command to install a Flutter package from pub.dev.
Type of change

New extension

Screencast
https://user-images.githubusercontent.com/11705392/146821815-a4bb6dd8-39db-4fd9-b0d1-9a1af3ed123b.mov
Checklist

[x ] I read the extension guidelines
[x ] I read the documentation about publishing

I have also tested and fixed the URL formation for "Open in Browser" action

Please review this PR. I have applied all suggested changes

Hi @prasadsunny1 👋
I have a few more corrections, and I'm sure we're pretty sure to merge it 🔥
Request a new review when you are ready, feel free to contact me here or at Slack if you have any questions.

Accepted and Tested, Thanks

Hi @prasadsunny1 👋
Could you make sure that the code is formatted with Prettier? Request a new review when you are ready, feel free to contact me here or at Slack if you have any questions.

Hi @pernielsentikaer, It's done. Formatted the code using prettier extension in VScode

Great, Thanks


Separate type for get() with notSetValue provided.

As suggested in https://github.com/facebook/immutable-js/pull/1035#discussion_r105333309

Maybe this patch can be added to the flow typings as well?


Feedback for “Download and Installation”

Hello
How long is the licence valid for use?
is it a yearly plan?
Kind regards
Simon

Hello! Apologies for the delayed response. I’m currently working on updating the manual and the GitHub Issues section.
Plasticity licenses are perpetual for standalone use and include 12 months of updates and maintenance from the date of purchase. For more information, visit the official website: Plasticity Pricing.


fix: update to eye v10.16.8

fix: update to eye v10.16.8

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

npm package (@latest dist-tag)
GitHub release
v16.15.7

Your semantic-release bot :package::rocket:


how to select the --model parameter for the meta format checkpoints

I directly download the model from the meta website with the following file:
./Meta-Llama-3-8B/
|- original/
    |- consolidated.00.pth
    |- tokenizer.model
|- config.json
|- generation_config.json
|- model.safetensors.index.json
|- special_tokens_map.json
|- tokenizer_config.json
|- tokenizer.json
|- USE_POLICY.md
|- README.md
|- .gitattributes
|- LICENSE

I want to run the following command, but it failed with the output:ValueError: not enough values to unpack (expected 2, got 1)
I don't know why , It might be I use the wrong --model parameter? cause the model is not hugging face format. But what is the correct parameter?
lm_eval --model hf \
    --model_args  Meta-Llama-3-8B/meta_model_0.pt\
    --tasks gsm8k_cot \
    --device cuda:0 \
    --batch_size 8

--model_args  pretrained=Meta-Llama-3-8B/meta_model_0.pt \ . The --model_args accepts key, value pairs :)

--model_args  pretrained=Meta-Llama-3-8B/meta_model_0.pt \ ? The --model_args only accepts key, value pairs :)
I am sorry, I mean the --model parameter. I am trying to evaluate the meta formate model, I do not know how to select the parameter.

You'll probably have to use the HuggingFace-converted Llama checkpoints, or if you need to use the Meta-formatted ones for a specific reason, then that'll require edits to the code: we don't support this checkpoint format / codebase out of the box unfortunately.


Unable to load BSP - Funny staticprop length

Trying to load ahop_orange throws the error InvalidDataException: Funny staticprop length (14440 != 13680)

Three more files that break: https://filebin.net/wf75sz124bnxnthp
There's an int division in @tsa96 's fix for this that fails to trigger in some cases that needs to be fixed:
Change
            if (remainingLength / StaticProps.StructureSize != entries)

To:
            if (MathF.Ceiling(remainingLength / (float) StaticProps.StructureSize) != entries)

Why's the ceil needed, don't we want to fail if the structure size is not a factor of remaining length? Might be misremembering the details of this

Actually, yeah - the ceil is a bad way to do this. Something like this is better:
            if (remainingLength / StaticProps.StructureSize != entries || remainingLength % StaticProps.StructureSize != 0)

Isn't remainingLength % StaticProps.StructureSize != 0 always true if remainingLength / StaticProps.StructureSize != entries is true, given that entries is an integer? Second guessing myself now, but if A / B is a integer, then A % B == 0, right?
I haven't had a chance to test the maps you posted yet, could you explain why current check fails? Can probably figure it out from the values of remainingLength, StaticProps.StructureSize and entries. When I was working on this, I found debugging and setting a breakpoint after the check failed very helpful.

When loading jump_above:
remainingLength = 144
StaticProps.StructureSize = 68
entries = 2

144/68 = ~2.12 so it rounds to 2 which doesn't pass remainingLength / StaticProps.StructureSize != entries and so it never gets set to V7s.

So if StaticProps.StructureSize is 68, it's trying to fit a V8, and according to remaining length it's a V9 (144/2 = 72 which corresponds to V9).
I don't know the how the stupid prop versioning works, or why the current code only tries to fit V10s into V7s specifically, perhaps we should be doing that between other versions? @BIRD311 might be able to clarify

It enters into the function as a V7 (also 68 bytes) but it's actually a V7s.
public override int StructureSize => ActualVersion switch {
        StaticPropVersion.V4 => 56,
        StaticPropVersion.V5 => 60,
        StaticPropVersion.V6 => 64,
        StaticPropVersion.V7 => 68,
        StaticPropVersion.V7s => 72,
        StaticPropVersion.V8 => 68,
        StaticPropVersion.V9 => 72,
        StaticPropVersion.V10 => 76,
        StaticPropVersion.V11 => 80,
        StaticPropVersion.V12 => 80,
        StaticPropVersion.V13 => 88,
        _ => 1
    };

Oh woops, thought structuresize was unique to each version and didn't notice the other ones!
Just tried this out, you're right about it being an integer division, it's just that we want to still the comparison using floats. Just pushed a fix, seems to work for the maps you provided.


Update usage to the new yml syntax

This Pull Request has the same purpose as https://github.com/actions/npm/pull/42.

@andymckay Updated!

You’re welcome.

@andymckay I sent similar PR to other repositories. Old documents confuse many people, so we should update them as soon as possible.

Oh, most other repositories seem to have been deleted or archived.

Thank you for doing that work, but we've found most of the other repositories are just not relevant any more and we agree confuse people - so trying to clean those up too.

It makes sense!


Submodule handling?

To fix #206 I made space-wizards/ss14.shared.bsdiff to replace bsdifflib in C#. Problem is as follows: It's a separate repo (and I'd like to keep it this way to separate the Rust code from the main repo but keep the Rust code by its FFI buddy C#)
The problem with submodules is that they don't auto-update. Yay!
To fix this, we need post checkout and pull hooks. To make all of this easier I would also VERY much like to suggest that we make Python 3.5+ a hard dependency used in the build process because for the love of god there's no way to maintain this otherwise.
My original plan was to use msbuild, but this didn't work because msbuild doesn't build missing projects if they get created mid build. Problem!
We can probably use git hooks in some way, I guess?
I need suggestions seriously this is blocking #206.

P y t h o n.

The Python script in #275 fixes this. Take it from there when we set up the content repo.


Fluxcd Addon

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Looks better, added a few comments, mostly tactical. Once addressed I will run e2e and include in 1.6.2 ASAP.
@shapirov103 All Issues are fixed. Please review and run e2e.

/do-e2e-tests


Pivot: Fix array_agg + distinct scaling issue on gpdb

JIRA: MADLIB-1361
With large datasets, pivot fails because of the array_agg(distinct)
query. This is because array_agg collects the values first and filters
the distinct values later. This causes the array_agg to go out of
memory.
This commit fixes the issue by separating distinct from array_agg.
We use a subquery to get the distinct values. Then we aggregate these
values using array_agg.
Closes #413
Co-authored-by: Ekta Khanna<EMAIL_ADDRESS>

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/madlib-pr-build/979/


Most efficient way to read large number of file

Hi ! I have about 2.7 million images I'd like to efficiently read EXIF data from in Julia. ExifViewer seems much faster than ImageMagick for that task. Do you have any advice on how to complete this task most efficiently with ExifViewer?

I think the optimization for speed will come from by using keyword_arguments, so if you know which tags you specifically want to read and which IFD they are in, then we use
julia> read_tags(data; ifds =  specificidnum, read_all = false, tags= [ "EXIF....", "EXIF....."])

Okay, thanks! I'll test that.

I think we are likely to gain a exponential speed factor gain after use SnoopPrecompile, so reopening it till then.

With #19, experience for extracting exif will improve by alot, see the PR message to get more info. I'll go over the package again with JET.jl and other tools to find more spaces of improvements and get those fixed soon.


Feature: Run old tests against new version to detect breaking changes

This idea is actually from Stephan Bönnemann's talk and it was one of the clever ideas that motivated writing semv in the first place. So we should have this soon.
As an initial implementation, we could create a tmpdir, shallow clone the last tag into it and run tox --install-pkg <old-version>. Maybe with a configurable environment only (e.g. unit or cram).

Closing after #16 was merged.


Linux: Allow unbundling brotli to use system library

Added the core/SCsub change which I had forgotten to commit.


test / Add simulated instrument + test for R&S HMC804

Ideally, we should have such tests for all instruments. Well, here's one.
@QCoDeS/core

Looks good to me as well


Python3 support in GDB

GDB included in toolchain package is compiled with Python 2 support. It would be nice to enable support for Python 3 as support for 2.7 is ending next year.
I don't know if I should raise this issue here or in arm-none-eabi-gcc-build repository. If in the -build one, let me know I will create issue there.
Moved from https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc/issues/5

I'll try to add support for Python 3 in the next release, as a new binary, like *-gdb-py3.

Great, thanks!

I did some changes in the build scripts to improve python support.
unfortunatelly my experience with gdb-py is close to none, and I'm not sure the chages are ok.
for example, the new scripts will copy the python shared libraries in the same folder where gdb-py is located, such that gdb will always start, and not complain that python is not installed.
however I have no idea if python support is really functional in this configuration. I also have no idea what happens if the installed python has a different version (assuming a different 2.x) than the version included in gdb (2.7.13).
I would appreciate some help to test the new gdb support, or at least some feedback.
in the next few days I'll try to make a pre-release with the new configuration, and possibly add gdb-py3 to the set of binaries.

Sure thing. Once binaries are released I will check how they works with py2/3 support (at least on Windows, maybe on Linux)

I tryed to create a gdb-py3, but I got:
checking whether to use python... /Users/ilg/opt/homebrew/xbb/bin/python3
checking for python3.7... no
configure: error: no usable python found at /Users/ilg/opt/homebrew/xbb/bin/python3

my python3 config is:
ilg-mbp:~ ilg$ which python3
/Users/ilg/opt/homebrew/xbb/bin/python3
ilg-mbp:~ ilg$ python3 --version
Python 3.7.2

the script uses exactly the same configuration, I only replaced python2 with python3.
I'm not sure, but the gdb configure might not be ready for python3.
do you know of any distribution providing a python3 enabled gdb?

Both native gdb and arm-none-eabi-gdb on Arch Linux works with Python3.7. Crosstool-ng also seems confirm that gdb supports Python3 https://github.com/crosstool-ng/crosstool-ng/blob/master/config/debug/gdb.in.cross#L53

ok, then it should work for us too; probaby I have to do something different.

Arch Linux has easily available scripts they are using to built packages. Here is one for GDB: https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/arm-none-eabi-gdb

python3 also requires libintl, from the gettext package. I added it and the configure+make were successful.
later today I'll try to create some pre-release binaries and allow you to test them.

unfortunately building the windows gdb-py3 is more complicated than anticipated.
for the linux/mac versions, configure calls the python binary with various options to discover configuration strings, like include paths, lib paths and cflags.
for the windows version using python2, it is necessary to download the .msi file, unpack it with 7-zip, and use a script that pretends to be python, and return the paths to the folder containing the unpacked .msi and other settings.
in principle the same can be done for python3, but in the standard python distribution there is no .msi any more, now they provide .exe files, and I don't know how to extract the content from them.
I also checked the .zip files advertised for embedded use, but they do not include the headers.
the only place I found the headers is the source archive, but the headers cannot be used as is, they need to be processed by configure, to transform pyconfig.h.in -> pyconfig.h.
the conclusion is that, as usual, building for windows is hell.
if you know a method to extract the content from the https://www.python.org/ftp/python/3.7.2/python-3.7.2-amd64.exe file, please let me know, otherwise I'm afraid for now I cannot add gdb-py3 for windows.

Ok, I found something that may work: on https://www.python.org/ftp/python/3.7.2/amd64/ there are a lot of MSI files for different parts of python install. dev.msi contains includes and libraries.

thank you, I'll take a look. did you manage to extract the content with 7za? was pyconfig.h there?

Here's list of files extracted from that archive: https://gist.github.com/Novakov/90e6c33a37187c90df81a426c9ac64c7 Sadly directories are transformed into subdirectory/filename -> subdirectory_filename when using 7za

if 7za fails, can you suggst other tool that I can compile on linux to extract the content of msi files?

7z (not 7za) is far from failing ;) I put together some script to unpack archive and normalize files - see linked gist (files unpack.sh and unpacked.txt)

do you have a link where I can find the sources for this miraculous 7z? (personally I'm not comfortable with these non-unix solutions).

It seems to be packaged with 7z in p7zip-full package.

not very helpful. my production build machines are CentOS 6 and macOS 10.10, but on top of them I build all modern tools from sources.
even finding the 7za sources was an adventure in itself. I'll try that program on the new msi files, but I'm not very optimistic on the outcome.

Ok, now I see the issue (I'm not familiar with details of your build process/infrastructure). I took the p7zip sources (https://sourceforge.net/projects/p7zip/files/p7zip/16.02/), built 7z target (make 7z, by default only 7za is built) and executed bin/7z l dev.msi which listed files in the archive confirming that it works.

ah, ok, I know that awful project. :-(
I'll try to build the full 7z, but I rememebr last time I had some problems and gave up with only 7za.

It took me quite a while to put the tools together and now I have a new build environment which also includes 7z.
however I'm not able to extract the files from https://www.python.org/ftp/python/3.7.2/python-3.7.2-amd64.exe, all I get is
$ ls -l tmp/x
total 872
-rw-r--r-- 1 ilg ilg  86039 Dec 23 22:14 0
-rw-r--r-- 1 ilg ilg 617472 Dec 23 21:25 u0
-rw-r--r-- 1 ilg ilg  12028 Dec 23 21:16 u1
-rw-r--r-- 1 ilg ilg  10469 Dec 23 21:16 u2
-rw-r--r-- 1 ilg ilg  57891 Dec 23 21:16 u3
-rw-r--r-- 1 ilg ilg  97806 Dec 23 22:14 u4

I tried the Ubuntu 7z and 7za and none worked. the 7z that I compiled behaves the same.
the problem is that we need both the headers and the precompiled Windows dll. I can find the headers in https://www.python.org/ftp/python/3.7.2/python-3.7.2.post1-embed-amd64.zip, but the dll is not there.
as a workaround for tests I'll try to install the exe on windows and steal the dll from there, but we need a proper solution.

oops! my bad :-(
python-3.7.2.post1-embed-amd64.zip includes the DLLs, and I also found the header files in the main source archive.
now I need to convince configure to accept them in separate locations...

I finally found a workaround for both the DLLs and headers, and solved most of the small configurations problems, but in the end I could not make it build for windows, GDB does not support the new Python3 API when building with mingw-w64:
https://sourceware.org/bugzilla/show_bug.cgi?id=24469
the macOS and Linux builds seem ok.
I'm not very comfortable to make a release with partial support, I'll probably mark it experimental.

Experimental support added in 8.2.1-1.6.
We'll leave this ticket open until fully functional.


Select: See if we can use ellipsis for truncation

From @joshblack at #1978:

Should this have truncation styles? e.g. the ellipsis for text overflow
Note (@asudoh) - Dev's feedback is text-overflow: ellipsis does not seem to work there. Creating this issue just to continue the discussion.

adding what I wrote in the original discussion:
I don't believe truncation styles can be implemented without hacky JavaScript. This is a native  under the hood (as opposed to our custom dropdown #1994), so we are already quite limited in what we can do to style the element, on top of the custom styles and behaviors imposed by browser vendors and operating system defaults
it's worth nothing that for example, native <select> on mobile platforms are more like a modal than a dropdown and that can affect how we override styling. one suggestion that was briefly discussed with @asudoh was the possibility of applying a blur effect or some kind of filter as a replacement for an ellipsis


Your Hamper Page, padding at bottom of button

@rug1 I couldn't replicate this? Which view/screen size was it on?


Make HSV persistent during no texts and hud

a tiny fix for HSV not showing when tresholds dont reach 0

i made this toggleable and also used harmony's code matcher to find the if statement in the installer.
thank you for the idea, @Arimodu
#33


DataGrid is always empty

Describe the bug
<DataGrid /> never has any content - it just appears to stay as an empty component.
To Reproduce

Create a DataGrid in XAML
Either bind Items to a viewmodel, or add items via code-behind
The given items will not show at all

Expected behavior
The data bound to Items is used to create a table of information.
Screenshots

Desktop (please complete the following information):

OS: Arch Linux
Version 0.10.6

Additional context
Have tested with and without MVVM, have tested with and without custom columns, have tested with both fields and properties for the member in objects given.
Basically what I wrote on top of the MVVM template:
Class:
public class Song
{
	public string Name;
	public string Artist;
	public string Album;

	public Song(string name, string artist, string album)
	{
		Name   = name;
		Artist = artist;
		Album  = album;
	}
}

In ViewModel:
public class MainWindowViewModel : ViewModelBase
{
	private SourceList<Song> _songs = new();

	public SourceList<Song> Songs
	{
		get => _songs;
		set => this.RaiseAndSetIfChanged(ref _songs, value);
	}
}

In constructor:
public MainWindow()
{
	DataContext = new MainWindowViewModel();

	InitializeComponent();
#if DEBUG
	this.AttachDevTools();
#endif

	((MainWindowViewModel) DataContext!).Songs.Add(new("Start Again", "ONE OK ROCK", "Ambitions"));

In XAML
<DataGrid Items="{Binding Songs.Items}" AutoGenerateColumns="False">

	<DataGrid.Columns>
		<DataGridTextColumn Header="Song" Binding="{Binding Name}" />
		<DataGridTextColumn Header="Artist" Binding="{Binding Artist}" />
		<DataGridTextColumn Header="Album" Binding="{Binding Album}" />
	</DataGrid.Columns>

</DataGrid>

Did you add styles in your App.axaml ?
<Application.Styles>
    <StyleInclude Source="avares://Avalonia.Controls.DataGrid/Themes/Default.xaml"/>
</Application.Styles>

or
<Application.Styles>
    <StyleInclude Source="avares://Avalonia.Controls.DataGrid/Themes/Fluent.xaml" />
</Application.Styles>

https://docs.avaloniaui.net/docs/controls/datagrid#add-required-styles-to-app-axaml

Thank you!

Though the columns etc show, the datagrid still fails to show anything

hmm no it appears that this component is really really specific about how you use it? very weird...

It's not really really specific. Can you share any project how are you trying to do it?
Code pieces from above are fine and probably not enough to see the problem.
Although I don't know about SourceList and what type SourceList.Items is.

Yeah i'm kinda trying to experiment around with it. SourceList is part of DynamicData / ReactiveUI

ok ill put my code in a repo - working in a minimal test project right now

https://github.com/yellowsink/dgtest

the change notifications page suggests that dynamicdata works but i couldnt find any working examples

well i kinda can make it work but its janky

Your project works for me fine. What exactly is your problem?

Checked your previous code on the branch. I don't see any problems with Avalonia.
But it seems you are using SourceList wrong.
You bind to SourceList.Items, which IS NOT bindable property in ReactiveUI (or DynamicData). Neither SourceList implements INotifyPropertyChanged.
Check its documentation https://www.reactiveui.net/docs/handbook/collections/#how-to-use-it
In DataGrid you should use ObservableCollection for that task or anything else that implements INotifyCollectionChanged.

Ohhhhhh I didnt realise how dynamicdata worked. Thank you so much, and sorry if I wasted your time.


Kill recaptcha

Why does it sometimes have 3 second animations to show the next images?
Is it a bot that set the images in the first place? Because I always select all the correct images and it still gives me multiple other sets saying "try again"
Sometimes I spend 2 minutes selecting so many damn pictures
It didn't use to be this annoying, but now-a-days when I go to kijiji every single message asks for recaptcha and in the past week I've spent 2hours filling recaptchas
Recaptcha needs to die

Why doesn't recaptcha have some cache saying I just filed the recaptcha 30 times today successfully...

You want to know why? It's by design, in order to FORCE you into selling your soul to Google. Do any of the following apply to you?

You use a VPN, Tor, or for some reason have a non-residential ip address
You don't use Chrome
You are not signed into Google
You use AdBlock, or a similar program
You use Privacy Badger, or a similar tracker blocker
You use DDG, or an alternative search engine

If so, Google is purposefully wasting hours of your time, to turn you into another Google slave. These practices are blatantly illegal, immoral, and anti-competitive. This is censorship.
Stay strong, Chaython.

Ya, pretty much, need to let them pound my anus with tracking cookies.
Recaptcha needs to be smacked with some anti-trust; perhaps a GDPR fine for forcing this strict tracking?
It still goes through, but if you block some of their trackers it will give you more and more sets. If you white list all google and affiliated domains, then you can complete recaptcha in 1 set. The image fade in/out is also instant if you whitelist all, I do not understand why they make the fade in like a 5 second animation if you have certain domains blocked....

This "service" should be banned in EU. Period.

Unrelated to client.


Added README POLISH translation

Hi, I added a translation for README to polish. Could you please add hacktoberfest-label if this PR good? thanks :)

Hi, we're not likely to add any languages other than english and indonesian (our other community-preferred language) anytime soon.


feat: arbitrum bridge swapper

Description
This PR brings in Arbitrum Bridge as a swapper.
It:

handles ERC20 deposits, with granular status detection (i.e L1 pending, L2 pending, L2 confirmed)
handles ETH deposits, with granular status detection (i.e L1 pending, L2 pending, L2 confirmed)
handles ERC20 withdraws, without granular status detection (L1 Tx takes a week to be ready, not the best UX to leave the app open and poll for a week) - goes straight to confirm on L2 confirmed
handles ETH withdraws, without granular status detection (L1 Tx takes a week to be ready, not the best UX to leave the app open and poll for a week) - goes straight to confirm on L2 confirmed
additionally, escapes hatches out of the Arbitrum SDK for ERC20 deposits and uses Arbitrum's own hardcoded gasLimit from their repo, see comments. This allows us to still get a quote whether or not an approval is required. Actual execution data will be correct and use the Arbitrum SDK.

It does not:

add some UX for warning users about the 7 days delay, except for the actual quote 7d ETA
handle CCTP transfers. This is not Arbitrum bridge per se, and should be implemented as a separate swapper/PR.

TODO to make this an actual PR:

- [x] Remove fluff
- [x] More tests
- [x]  Support both ETH *and* ERC20s as well as deposits (L1 -> L2) and withdraws (L2 -> L1)
  - [x] Deposits
    - [x] ETH
    - [x] Tokens
  - [x] Withdraw
    - [x]  ETH
    - [x] Tokens
- [ ]  Should warn users of the 7 days withdraw thingie
  <img width="765" alt="image" src="https://github.com/shapeshift/web/assets/17035424/8dc388e3-8f5a-495d-bf4f-c57fa72a191f">
- [x] Have proper ETAs, see https://github.com/OffchainLabs/arbitrum-token-bridge/blob/382aaaf2294a4693abf184299c4dd821f33b0e61/packages/arb-token-bridge-ui/src/components/TransactionHistory/TransactionsTableRowAction.tsx#L37 for how they do that in the bridge UI
- [x] Handle non-yet-approved tokens, Arb SDK isn't happy with getting requests out of non-approved tokens, so we will probably need to get parts manually (gateway addys basically) and build the Tx ourselves. See https://github.com/OffchainLabs/arbitrum-token-bridge/blob/d17c88ef3eef3f4ffc61a04d34d50406039f045d/packages/arb-token-bridge-ui/src/hooks/TransferPanel/useGasEstimates.ts#L24-L35 which is probably what we want
- [x] Bring in some fancy pants icon for the bridge
- [x] Supported assetIds narrowing

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[x] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes https://github.com/shapeshift/web/issues/6968
contributes to https://github.com/shapeshift/web/issues/6978, but doesn't yet implement it for the RFOX feature specifically, only in swapper

Risk

High Risk PRs Require 2 approvals

Medium - mostly related to CCTP - ensure it is impossible to trade native USDC to native USDC (both directions). That is, native USDC <-> native USDC should not be an available route, but USDC on Ethereum -> USDC.e on Arbitrum should be, and the other way around too.

What protocols, transaction types or contract interactions might be affected by this PR?

Arbitrum bridge contracts
Testing

Note 1: Always have bridge.arbitrum.io handy when testing this, which you can use to verify the status of your bridge
Note 2: Arbitrum -> Ethereum direction does not mean your funds arrive. As mentioned in the description above, this does not yet implement the UX bits for telling users about the 7 days period and the need for a separate claim Tx yet. Use bridge.arbitrum.io to confirm the withdraw went through and has an ETA of 7 days before claim is available.

Ensure that Arbitrum Bridge isn't displayed as an option for pairs others than Ethereum <-> Arbitrum related assets
It is possible to do an Ethereum -> Arbitrum ETH deposit

Deposit should take ~10-15mn and show granular status, with completion when the L2 Tx is succesful
There should be no approval needed since we're talking ETH
Both L1 and L2 Txids should be displayed
Gas estimation is sane

It is possible to do an Ethereum -> Arbitrum ERC20 deposit

Deposit should take ~10-15mn and show granular status, with completion when the L2 Tx is succesful
There may be an approval step if you didn't grant allowance
Both L1 and L2 Txids should be displayed
Gas estimation is sane, though overestimated
Test with a few tokens

It is possible to do an Arbitrum -> Ethereum ERC20 withdraw

Withdraw should show as complete pretty much instantly, as Arbitrum is turbo fast
There is never an approval required for Arb tokens - bridge has some magic which makes this handled at protocol-level
Only the L2 Tx is displayed - L1 Tx would take a week to arrive
Gas estimation is sane
Test with a few tokens on Arbitrum, not only FOX
Ensure native USDC <-> native USDC is unavailable as a route to trade on Arbitrum bridge, but mainnet native USDC <-> Arbitrum USDC.e is

It is possible to do an Arbitrum -> Ethereum ETH withdraw

Withdraw should show as complete pretty much instantly, as Arbitrum is turbo fast
There is never an approval required for ETH on Arb - as it is the native token
Only the L2 Tx is displayed - L1 Tx would take a week to arrive
Gas estimation is sane

Engineering

☝🏽

Operations

☝🏽

Screenshots (if applicable)
USDC assets are unavailable to bridge

Native USDC

USDC.e

ERC20 Deposit

Inbound

https://jam.dev/c/916becf7-3f62-4a8f-84b1-2b2ffa33f4ce

Outbound

https://jam.dev/c/2b292395-4ea4-4c21-b362-6e676a53dcd8
ETH Deposit

Inbound

https://jam.dev/c/d2c8c6f7-6e8c-41dc-a442-6ab2e8fad54e

Outbound

https://jam.dev/c/0fea0a85-9e61-41d1-8f14-3d32f009b272
ERC20 Withdraw
https://jam.dev/c/9fc8cbf2-0c77-47ea-b1d0-2c11984501f7

ETH Withdraw
https://jam.dev/c/bf9c4a5d-6947-4808-91a2-65ad954003d6

Withdraw is going to require some extra UI to actually claim. We may want to disable L2 -> L1 and add as a follow up feature for this first implementation until we can discuss with product what that will actually look like and how we will need to detect such claims, etc.

Moving to draft until the remaining comments are tackled

ETH Deposit:
https://etherscan.io/tx/0x2f8cd59b09bd72dfe2de91d8281aa4bee8500c4e3c550fc8835a1f9ef5cf7ff1
https://arbiscan.io/tx/0x5040ea92642b93411b42f7dc8afcf89c6836694a6fa740d03dc499f86189ad61

Token Deposit:
https://etherscan.io/tx/0x4386796ab2ba3245adb6b9627c3af9fdd57e641c1fdd3b641cd1e0ca476615b7
https://etherscan.io/tx/0xb5589a29866139818395822d252d3587a8d0f26c412dc38fc283360a9ed967f8
https://arbiscan.io/tx/0xb2ee85982c04ecb2aa30163346234ea0239a8709ef3b60946a9952562c70db57

ETH Withdraw:
https://arbiscan.io/tx/0x1c5a9c479fd64efd49ffa6bc80ba3aabec530e71727f1889efbdb15b13f17f19

Token Withdraw:
https://arbiscan.io/tx/0xac1bb4570e61b2e70f2cad3af0cd7f7e59accd1f41359985e0a275b521fd73f8

Agreed with @kaladinlight to fast-follow with a one-liner to enable cross-account trading and dedicated testing next release


getUserIp looks at HTTP_X_FORWARDED_FOR then overwrites it anyway

https://github.com/rollbar/rollbar-php/blob/master/src/DataBuilder.php#L827
Just encountered this bug. This library appears to do something clever with HTTP_X_FORWARDED_FOR and with HTTP_X_REAL_IP, but line 827 overwrites it with REMOTE_ADDR no matter what. I'm not 100% sure what the intended behaviour is - the code linked above looks like a regression or a bad merge.
For now I am working around this by writing hacks in my code to overwrite REMOTE_ADDR with HTTP_X_FORWARDED_FOR to trick Rollbar into behaving nicely :)

Thanks for bringing this to our attention!

Thanks @zephod We will get this addressed soon.

This is now fixed in master and will be included in v1.5.4


Standard namespaces/classes/types are not found anymore

Issue Description
After an upgrade of the .NET Core SDK package on Ubuntu, VS Code shows many errors for standard namespaces and classes, like System, System.Object, etc.
Exactly the same happens on my Ubuntu 18.04 machine (where the logs below come from), and another Ubuntu 16.04 machine I have.
Steps to Reproduce
dotnet new console --name Test
code Test/

Expected Behavior
VS Code opens the C# project without any errors.
Actual Behavior
VS Code shows many errors, like:
The type or namespace name 'System' could not be found (are you missing a using directive or an assembly reference?) [Test]
Predefined type 'System.Object' is not defined or imported [Test]
'object' does not contain a constructor that takes 0 arguments [Test]
...

See screenshot:

Note: dotnet run on the command line works fine.
Logs
OmniSharp log
Starting OmniSharp server at 8/19/2020, 3:00:02 PM
    Target: /home/bkragl/Code/Test

OmniSharp server started with Mono 6.10.0.
    Path: /home/bkragl/.vscode/extensions/ms-dotnettools.csharp-1.23.0/.omnisharp/1.36.1/omnisharp/OmniSharp.exe
    PID: 31238

[info]: OmniSharp.Stdio.Host
        Starting OmniSharp on ubuntu 18.4 (x64)
[info]: OmniSharp.Services.DotNetCliService
        DotNetPath set to dotnet
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Located 2 MSBuild instance(s)
            1: Mono 16.8.0 - "/usr/lib/mono/msbuild/Current/bin"
            2: StandAlone 16.8.0 - "/home/bkragl/.vscode/extensions/ms-dotnettools.csharp-1.23.0/.omnisharp/1.36.1/omnisharp/.msbuild/Current/Bin"
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Registered MSBuild instance: Mono 16.8.0 - "/usr/lib/mono/msbuild/Current/bin"
            CscToolExe = csc.exe
            CscToolPath = /home/bkragl/.vscode/extensions/ms-dotnettools.csharp-1.23.0/.omnisharp/1.36.1/omnisharp/.msbuild/Current/Bin/Roslyn
[info]: OmniSharp.Cake.CakeProjectSystem
        Detecting Cake files in '/home/bkragl/Code/Test'.
[info]: OmniSharp.Cake.CakeProjectSystem
        Could not find any Cake files
[info]: OmniSharp.MSBuild.ProjectSystem
        No solution files found in '/home/bkragl/Code/Test'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/home/bkragl/Code/Test/Test.csproj'
[info]: OmniSharp.Script.ScriptProjectSystem
        Detecting CSX files in '/home/bkragl/Code/Test'.
[info]: OmniSharp.Script.ScriptProjectSystem
        Could not find any CSX files
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpFormattingWorkspaceOptionsProvider, Order: 0
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.RenameWorkspaceOptionsProvider, Order: 100
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.ImplementTypeWorkspaceOptionsProvider, Order: 110
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.BlockStructureWorkspaceOptionsProvider, Order: 140
[info]: OmniSharp.WorkspaceInitializer
        Configuration finished.
[info]: OmniSharp.Stdio.Host
        Omnisharp server running using Stdio at location '/home/bkragl/Code/Test' on host 31126.
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /home/bkragl/Code/Test/Test.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file '/home/bkragl/Code/Test/Test.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Adding project '/home/bkragl/Code/Test/Test.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: Test
[warn]: OmniSharp.MSBuild.PackageDependencyChecker
        Test: Did not find 'Microsoft.NETCore.App' in lock file.

C# log
Empty
Environment information
VSCode version: 1.48.0
C# Extension: 1.23.0
Mono Information
        OmniSharp using global mono :6.10.0
Dotnet Information
.NET Core SDK (reflecting any global.json):
 Version:   3.1.401
 Commit:    39d17847db
Runtime Environment:
OS Name:     ubuntu
OS Version:  18.04
OS Platform: Linux
RID:         ubuntu.18.04-x64
Base Path:   /usr/share/dotnet/sdk/3.1.401/
Host (useful for support):
Version: 3.1.7
Commit:  fcfdef8d6b
.NET Core SDKs installed:
2.2.402 [/usr/share/dotnet/sdk]
3.1.401 [/usr/share/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.2.8 [/usr/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.2.8 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.7 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.2.8 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.7 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download

Visual Studio Code Extensions

Extension
Author
Version

cpptools
ms-vscode
0.29.0

csharp
ms-dotnettools
1.23.0

latex-workshop
James-Yu
8.11.1

python
ms-python
2020.8.101144

selectline-statusbar
tomoki1207
0.0.2

I'm experiencing this as well with the exact same logs/results.

Please check on 1.23.1 which was released yesterday. I believe it should be resolved there

Please check on 1.23.1 which was released yesterday. I believe it should be resolved there

Yes, the problem seems to be resolved. Thanks!


Issue with "Easier copy-pasting from diffs by making +/- signs unselectable"

It doesn't seem to be working all the time with all the pages. Sometimes I see both the "unselectable +" and the "selectable +". I haven't found a pattern to reproduce the issue but, I can link you to a page in which I was facing the same issue. Here's a link to it, and a screenshot as well. If you need anything else, let me know.
Issue
Screenshot

Seems to be an issue with lazy loaded diffs since all of them are broken after a certain point

@jgierer12 Any way to prevent it from happening?

Not right now 🙁
It also happens when you switch between raw and rendered Markdown:


[SUPPORT] Data deduplication caused by drawback in the delete invalid files before commit

Dear community,
Our user complained that after their daily run job which written to a Hudi cow table finished, the downstream reading jobs find many duplicate records today. The daily run job has been already online for a long time, and this is the first time of such wrong result.
He gives a detailed deduplicated record as example to help debug. The record appeared in 3 base files which belongs to different file groups.

I find the today's writer job, the spark application finished successfully.
In the driver log, I find those two files marked as invalid files which to delete, only one file is valid files.

And in the clean stage task log, those two files are also marked to be deleted and there is no exception in the task either.

Those two files already existed on the hdfs before the clean stage began, but they still existed after the clean stage.
Finally, found the root cause is some corner case happened in hdfs. And fs.delete does not throw any exception, only return false if the hdfs does not delete the file successfully.

And I check the fs.delete api, the definition is reasonable.

I think we should check the return value offs.delete in HoodieTable#deleteInvalidFilesByPartitions to avoid wrong results. Besides, it's necessary to check all places which called  fs.delete.
Any suggestion?

you are right, we already got a fix recently: https://github.com/apache/hudi/pull/11343

@danny0405 Thanks for your attention.
I checked #11343, it could not cover the current issues. The issue should be fixed in HoodieTable#deleteInvalidFilesByPartitions to avoid fail to delete the invalid files, while #11343 aims to fix clean service.

hmm, would you mind  to fire a fix for it?

cc @yihua @nsivabalan @codope @xushiyan

thanks @beyond1920 . please put out a patch. I would like to review as well.

thanks @nsivabalan. I fire a pull request just now.
I think the underlying file system should ensure that fs.delete should throw exception instead of return false if it fail to delete the file.
But it might need a long time to discuss and push all the file system types updated.
Should we introduce new delete API in hoodie  HoodieStorage ensure this rules or changed existed delete API?

Should we introduce new delete API in hoodie HoodieStorage ensure this rules or changed existed HoodieStorage#deleteDirectory and HoodieStorage#deleteFile API to avoid all unexpected behavior when call fs.delete.

+1 for this way.

is the main reason, diff file system schemes treat file not found differently during fs.delete()? and you are proposing HoodieStorage#deleteFile to unify that?


[stable/postgesql] fix wrong values in statefulset-slaves, slavePod.xxx -> slave.podxxx

What this PR does / why we need it:
version 3.11.3 is not working
related PR: https://github.com/helm/charts/pull/11313
fix bug in statefulset-slaves
change .Values.slavePod.annotations -> .Values.slave.podAnnotations
change .Values.slavePod.labels -> .Values.slave.podLabels
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/assign @prydonius

Thanks!
/assign
/ok-to-test

/lgtm

/test all

/retest

We had an issue related to the test system, it should be fixed at this moment. I launched the tests again.
In the same way, this PR fixes this issue #11558 and I found another PR #11486 with the same changes, but at it is in a wrong state I will suggest closing the other in favor of this one.


Release rc4 parallel

Codecov Report

Merging #87 into release-rc4 will increase coverage by 1.65%.
The diff coverage is 11.53%.

@@                Coverage Diff                @@
##             release-rc4      #87      +/-   ##
=================================================
+ Coverage          37.61%   39.27%   +1.65%
+ Complexity           369      363       -6
=================================================
  Files                 49       48       -1
  Lines               3831     3659     -172
  Branches             336      333       -3
=================================================
- Hits                1441     1437       -4
+ Misses              2290     2119     -171
- Partials             100      103       +3

Impacted Files
Coverage Δ
Complexity Δ

.../com/webank/wecross/stub/bcos/AsyncCnsService.java
8.82% <0.00%> (+3.79%)
2.00 <0.00> (ø)

...a/com/webank/wecross/stub/bcos/BCOSConnection.java
66.01% <ø> (ø)
25.00 <0.00> (ø)

...om/webank/wecross/stub/bcos/BCOSGMStubFactory.java
0.00% <ø> (ø)
0.00 <0.00> (ø)

.../com/webank/wecross/stub/bcos/BCOSStubFactory.java
21.73% <ø> (ø)
4.00 <0.00> (ø)

...ank/wecross/stub/bcos/abi/ABICodecJsonWrapper.java
45.24% <0.00%> (ø)
34.00 <0.00> (ø)

...om/webank/wecross/stub/bcos/abi/ABIDefinition.java
52.32% <0.00%> (-6.16%)
16.00 <0.00> (-9.00)

...nk/wecross/stub/bcos/abi/ABIDefinitionFactory.java
57.89% <0.00%> (-14.33%)
6.00 <0.00> (ø)

...va/com/webank/wecross/stub/bcos/abi/ABIObject.java
78.38% <0.00%> (-0.46%)
93.00 <0.00> (ø)

...webank/wecross/stub/bcos/abi/ABIObjectFactory.java
83.87% <ø> (-0.26%)
22.00 <0.00> (ø)

...k/wecross/stub/bcos/abi/ContractABIDefinition.java
59.45% <0.00%> (-11.97%)
8.00 <0.00> (ø)

... and 10 more

Continue to review full report at Codecov.

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


Lazy load default kaffy field value

This introduces a minor performance boost (removes unnecessary JSON encoding in most of the cases).
However most importantly this is a quick fix to allow writing custom index queries like this:
  def custom_index_query(_conn, _schema, query) do
    from(r in query, join: c in Company, select: %{r | company: c})
  end

or
  def custom_index_query(_conn, _schema, query) do
    from(r in query, preload: :company)
  end

(right now it fails because the default value tries to be calculated and Jason cannot by default encode regular Ecto schemas).
One might ask why do we need these queries. In the index function you might want to do something like this:
  def index(_) do
    [
      id: nil,
      company: %{
        name: "Company",
        value: fn request ->
          request = Api.Repo.preload(request, :company)
          request.company.name
        end
      },
      inserted_at: nil
    ]
  end

However this introduces N+1 problem. Not a big deal I guess, but why not just not introduce it.
At this moment there is a solution, we can write the custom index query like this (but it's less optimal imo as it doesn't set a proper schema but just a pure map on a field that is expected to be a map):
  def custom_index_query(_conn, _schema, query) do
    from(r in query, join: c in Company, select: %{r | company: %{name: c.name}})
  end

Thanks! Very kind of you. Looks like we need to get the CI sorted first. Apologies.

hah yeah it's a bit out of date. Let me know when it's sorted (or if you need any help)

CI sorted. Re-running.

Could you re-submit this for me?

done

Thanks!


ctx.request_repaint_after makes app repaint constantly and not after set duration

[dependencies]
eframe = "0.23.0"
egui = "0.23.0"
rfd = "0.12.1"

Describe the bug
ctx.request_repaint_after makes app repaint constantly and not after set duration
To Reproduce
Steps to reproduce the behavior:

Take https://pastebin.com/raw/6kMba2X5
Run, see button getting wider, despite there is no mouse or keyboard input and large (but valid) request_repaint_after duration
Comment ctx.request_repaint_after(dur); and run again
Button gets wider only on input

Expected behavior
request_repaint_after should request repaint after set duration, not act as instant repaint request
Desktop (please complete the following information):

OS: Windows 11
Rust: rustc 1.73.0 (cc66ad468 2023-10-03)

Same as #3109. It only affects Windows, due to a workaround for winit introduced in egui 0.22, as discussed there.

Closing because dupe of https://github.com/emilk/egui/issues/3109


Architecture Link in Readme 404s

Describe the bug
The Detailed Space Cloud architecture link in the How it works section of the Readme 404s.

Oops. Need to get that fixed

Describe the bug
The Detailed Space Cloud architecture link in the How it works section of the Readme 404s.

This pull request fixes it. #1565


Community contributions 2022-10-27

Fix variable name type: https://github.com/input-output-hk/cardano-node/pull/3724
Update Update simple-scripts.md: https://github.com/input-output-hk/cardano-node/pull/3648
Also install libnuma-dev and llvm packages: https://github.com/input-output-hk/cardano-node/pull/2961

bors r+

bors r+


⚠ Bofrost.be has degraded performance

In 07ece01, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1412 ms

Resolved: Bofrost.be performance has improved in 9ff74f9.


libreddit: 0.15.3 -> 0.16.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/spikecodes/libreddit/releases.
meta.description for libreddit is: "Private front-end for Reddit"
meta.homepage for libreddit is: "https://github.com/spikecodes/libreddit"
meta.changelog for libreddit is: ""
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
/nix/store/ic77y68vk14k0wyj70jc1jsjiry66vs0-libreddit-0.16.0/bin/libreddit passed the binary check.
1 of 1 passed binary check by having a zero exit code.
1 of 1 passed binary check by having the new version present in output.
found 0.16.0 with grep in /nix/store/ic77y68vk14k0wyj70jc1jsjiry66vs0-libreddit-0.16.0
found 0.16.0 in filename of file in /nix/store/ic77y68vk14k0wyj70jc1jsjiry66vs0-libreddit-0.16.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
0 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
0 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
libreddit

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ic77y68vk14k0wyj70jc1jsjiry66vs0-libreddit-0.16.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libreddit https://github.com/r-ryantm/nixpkgs/archive/296549944f962318f69e81c7e8eb2866f1513df6.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ic77y68vk14k0wyj70jc1jsjiry66vs0-libreddit-0.16.0
ls -la /nix/store/ic77y68vk14k0wyj70jc1jsjiry66vs0-libreddit-0.16.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

libreddit

Maintainer pings
cc @fabaff for testing.

Result of nixpkgs-review pr 144415 run on x86_64-linux 1

1 package built:

libreddit


added lgess15 support

Added new template for the lg-ess-home-15 type
Adapted meters/lgess and lgpcs to be able to differ between lg-ess-home-8-10 and lg-ess-home-15 because lg-ess-home-15 provides different content in the json data.

this enhancement has not yet been tested live on an ESS HOME 15

Thank you for the PR (and creative use of generics)! I think we could still make this a little more elegant- if your want?

adapted to feedback :-)


Add Trisquel 7 (Belenos) support to install.sh

Install as Ubuntu Trusty.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "master" git@github.com:boite/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

we added the check_forked function for this, does it not work for your distro

@boite could you help out and provide the information for your system (as described in https://github.com/docker/docker/pull/15001#issuecomment-125721830);
Run the following commands and post their respective outputs here:
$ lsb_release -a
$ lsb_release -a -u
$ ls /etc/upstream-release/
$ cat /etc/upstream-release/*

/cc @fmoliveira

I've created a VM with Belenos Trisquel Sugar 7.0 and I've found out the -u option isn't supported by the lsb_release command.
Before we consider hard coding distro names, I've opened a discussion/proposal here, please check that @boite @jfrazelle @thaJeztah .

Or should we ask for Trisquel developers to add support for the -u option?
Here's how JoliOS have done that, and according to this topic, it's exactly how elementary OS guys have done it too.

I realise @fmoliveira has already determined that lsb_release -u isn't available on Trisquel, but here's the info requested from me anyway:-
$ lsb_release -a
No LSB modules are available.
Distributor ID: Trisquel
Description:    Trisquel GNU/Linux 7.0, Belenos
Release:        7.0
Codename:       belenos

$ lsb_release -a -u
Usage: lsb_release [options]

lsb_release: error: no such option: -u

$ ls /etc/upstream-release/
ls: cannot access /etc/upstream-release/: No such file or directory

I am going to close this for the time being re the discussion going on in #15765, thanks!


fix(sbb-train-formation): fix direction reading for screen readers

Closes #1771

Codecov Report

Merging #1787 (c5f0e97) into master (ab917b0) will increase coverage by 0.55%.
The diff coverage is 57.16%.

: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             @@
##           master    #1787      +/-   ##
==========================================
+ Coverage   54.85%   55.40%   +0.55%
==========================================
  Files          49      162     +113
  Lines        1659     6422    +4763
  Branches      406     1760    +1354
==========================================
+ Hits          910     3558    +2648
- Misses        671     2637    +1966
- Partials       78      227     +149

Impacted Files
Coverage Δ

...ts/sbb-accordion-item/sbb-accordion-item.events.ts
100.00% <ø> (ø)

...mponents/sbb-accordion-item/sbb-accordion-item.tsx
0.00% <0.00%> (-37.21%)
:arrow_down:

...onents/sbb-autocomplete/sbb-autocomplete.events.ts
100.00% <ø> (ø)

src/components/sbb-calendar/sbb-calendar.events.ts
0.00% <0.00%> (ø)

src/components/sbb-checkbox/sbb-checkbox.events.ts
0.00% <0.00%> (ø)

...components/sbb-datepicker/sbb-datepicker.events.ts
0.00% <0.00%> (ø)

src/components/sbb-datepicker/sbb-datepicker.tsx
49.18% <ø> (ø)

src/components/sbb-dialog/sbb-dialog.events.ts
100.00% <ø> (ø)

src/components/sbb-dialog/sbb-dialog.tsx
45.45% <ø> (ø)

src/components/sbb-divider/sbb-divider.tsx
100.00% <ø> (ø)

... and 30 more

... and 133 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Whitelist gateways

Currently a poorly-run gateway can join a federation and cause a lot of payment failures because the client isn't smart about ignoring such a gateway. For this reason, we should have an optional mechanism to whitelist gateways enabling guardians to prevent such unknown gateways from registering.
Simplest way to do this is a FM_GATEWAY_WHITELIST parameter that you can set to a list of gateway_ids. But this might be something that should be under consensus and configurable via guardian dashboard in the future.

I wouldn't restrict who can register gateways, but rather:

Add the necessary API to the LN client to select gateways manually
Define a meta field that specifies a set of vetted gateways. Clients can then choose to prefer these.

I'm thinking the gateway meta filed should be a JSON list of hex encoded gateway ids.  Would we need to add a meta field to LightningClientConfig, similar to GlobalClientConfig meta?

I worry a little bit that, in practice, adding a concept of vetted gateways essentially enables selection of the gateways by the federation.
Could we add smarter logic on the client-side for gateway selection? We've talked in the past about adding gateway selection policies but today everything is still manual.

I worry a little bit that, in practice, adding a concept of vetted gateways essentially enables selection of the gateways by the federation.

Yeah feels like vetting adds an element of censorship by the federation. Not sure if we should implement it anyways.
Regards to smarter selection logic, what parameters would a client consider when selecting a gateway, and how can we encode these in the gateway registration info? I'm imagining some kind of a reliability counter that updates with every failed send/receive payment

I'm imagining some kind of a reliability counter that updates with every failed send/receive payment

The hard part is not creating a system that can be easily gamed. If we just included the payment reliability, I could sabotage you're gateway by asking it to pay a bunch of invoices that don't correspond to any real lightning node.

The hard part is not creating a system that can be easily gamed. If we just included the payment reliability, I could sabotage you're gateway by asking it to pay a bunch of invoices that don't correspond to any real lightning node.

Right. My initial thought is to "discover" gateway reliability but do it per client (kind of like probing in the lightning network).
One issue with this though is that it takes time (and failures) to discover these things, so new users might have a poor experience while discovering which gateways are reliable.

I think having a vetted_gateways concept isn't in conflict with more intelligent GW selection logic, but can rather be seen as a starting point: other gateways can still be tried once we implement more client side logic and if vetted gateways don't perform they will be ignored.
But till we get better client side logic this is an adequate solution imo.

Progress

[x] propose meta field structure for vetted gateways: #3434
[ ] reflect gateway vetting meta on registered/announced gateways
[ ] add api for clients to manually select gateways based on vetting state
[ ] add api for guardians to vet newly registered gateways
[ ] add ux for guardians to vet registered gateways

@elsirion, What would be expected client behavior if it's config changed? I'm looking to add a generic consensus api for the guardians to vet a gateway and now I wonder what the implications are for modifying client config meta fields at runtime. ref

Currently the meta fields are static, eventually we want to make them dynamic, see #2791. Currently we hack around this limitation using meta_override_url. Now I'm wondering if it should be integrated for this particular purpose :grimacing: Then we'd need a caching strategy.

Now I'm wondering if it should be integrated for this particular purpose 😬 Then we'd need a caching strategy.

I'm testing an integration of meta_override_url as a source for whitelisted gateways, no client caching of meta

Works out pretty well. See #3533
What cache strategies do you have in mind, @elsirion

#3533 looks really good! Let's open an issue for caching, should be easy to patch in by storing the override meta json in the DB with a timestamp of when it was last fetched.


Use defaultConfigurationName for every target in a project

Currently defaultConfigurationName of a target is empty even if we set defaultConfigurationName in project settings. This is the same behavior as when we change a default configuration in Xcode.
As is
Project A -  defaultConfigurationName: "Release"
Target 1 -  defaultConfigurationName: ""
Target 2 -  defaultConfigurationName: ""

To be
Project A -  defaultConfigurationName: "Release"
Target 1 -  defaultConfigurationName: "Release"
Target 2 -  defaultConfigurationName: "Release"

Note: This defaultConfigurationName is used when building targets from xcodebuild without specific config.

Does this need to be on every target, or could it just be set once in the project build settings?

Does this need to be on every target, or could it just be set once in the project build settings?

In Xcode, a config name defined in Use [CONFIG_NAME] for command-line builds is used for every target in the project. I followed this behavior. Should I fix this change? 🙏

Yep, all good 👍


Remove validation logic from the core of contour.

Split contour to a validation implementation and the core contour which is independent from a fluentvalidation package.

this issue has been resolve in vnext branch.


Lazy attributes?

What do y'all think about adding support for "lazy" attributes using functions?
I've got an implementation ready to go.  This commit explains everything and includes some examples that should justify why I think this is useful:
https://github.com/moklett/ex_machina/commit/2bc2fe7e983985a31aa424d753d965682f42dbdc
Here's a little example:
def hero_factory do
  %{
    creature: "Bat",
    nickname: &"#{&1.creature}man",
    vehicle: &"#{&1.creature}mobile"
  }
end

build(:hero)
# => %{creature: "Bat", nickname: "Batman", vehicle: "Batmobile"}

build(:hero, creature: "Spider", vehicle: "webs")
# => %{creature: "Spider", nickname: "Spiderman", vehicle: "webs"}

Should I open a pull request?
Thanks!

This looks awesome @moklett! I'd love to see a PR for this.

@jsteiner here you go! https://github.com/thoughtbot/ex_machina/pull/131

As discussed in this comment we're going to hold off. The feature seems like a good idea, but Josh and I are not quite ready to support it. We think it'd be great to have as an external lib and we would be happy to link to it in the README if @moklett or someone else wants to tackle it


fix: cleanup some dead code

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Automatic refresh of calendar

Hi @itchyny . I was wondering if you could add the possiblity of automatically refreshing the calendar each time the app starts? I currently use the following (that seems to work):
function! s:RefreshCal()
    let timestamp_dir = g:calendar_cache_directory . '/timestamp'
    let file_list = globpath(timestamp_dir,'*', 0, 1)
    if empty(timestamp_dir)
        return
    endif
    " Delete Google calendar cache if not empty
    for item in file_list
        if exists(':VimProcBang') && s:is_win
            call vimproc#delete_trash(item)
        else
            execute delete(item)
        endif
    endfor
endfunction
nnoremap <silent> <Leader>ca :call <SID>RefreshCal()<CR>:Calendar -task
            \ -split=horizontal -position=below<CR>:wincmd J<bar>50 wincmd _<CR>

If you don't want to add something similar to this, just close the issue. Thank you in advance!

If the app refreshes the calendars on its every startup, it will download the calendars again and again; I felt too annoyed by the processes causing slowness on Vim. Sometimes I want to check the events quickly and the calendars are not updated that frequently. The app does automatically refresh the calendars if the last update is before 3 hours ago. The files under the timestamp directory are used for this feature (you may understand, I guess). I assume that users would not use both website interface and this app at the same time; if they liked this app, they would not update the event in the website, and that they would not switch that frequently between this app and their mobile devices.

Fair enough. Thanks for a great app!


The Istio deployment process and tools are understood

Everyone has gone through the process of deploying Istio to Kubernetes, and the deployment process / tools used are documented in a shared document. In the shared document, key steps in the process, tools used, and best practices are highlighted, with notes on how they may apply to this project.

Document is available here: https://cyberark365-my.sharepoint.com/:w:/r/personal/geri_jennings_cyberark_com/_layouts/15/Doc.aspx?sourcedoc={0A6DE3C5-9FCD-451E-9491-0CDCE9AF3E5C}&file=Istio notes from working through tutorials on 8-15-2018.docx&action=default&mobileredirect=true
This spike resulted in #343