🐛  fix(bal-navigation): Active State remains for closed first level navigation

Current Behavior
The active state for closed menu items in the first level main navigation remains even if the menu is closed
Expected Behavior
When the menu is closed, no item should be marked as active
Steps to Reproduce
regular usage
Version
15.0.2
Browsers
Firefox, Chrome, Safari, Microsoft Edge
Device
Desktop
Code Reproduction URL
No response
Additional Information
On page load:

Opened and closed:

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@clastzoo is the behaviour correct like that

close due to inactivity


Add .bmp file in the Main Window

Hi, everyone, how can I add an existing .bmp file in the main window for Druid?
Thanks in advance.
Sardina Simone

What does 'add' mean in this context. Do you want to drag the file into the window?

@xarvic Thanks for replying me. Sorry i didn't make myself clear. I meant how to show an image in the main window, for example a logo at the top of it, using an existing .bmp file in the source.
Thanks in regards,
Sardina Simone


Hide custom toolbar if fullscreen mode?

Wonderful library.
I am making a custom toolbar and it's working good. However, when user selects full screen mode, I want to hide the custom toolbar. How can I programmatically know when the viewer is in full screen mode?
This is a snippet of how I am instantiating the viewer (Vue3):
viewer.value = OpenSeadragon({
    element: osdContainer.value,
    tileSources: {
      type: 'image',
      url: 'https://ik.imagekit.io/XXX/users%2F5cnu6iDlTsa5mujH2sKPsBJ8OKH2%2Fposts%2Fview-from-an-observation-post-in-france-during-ww1_K_V0?alt=media&token=c521a542-909d-4666-9506-8416eafcbb9e&tr=pr-true,dpr-auto'
    },
    defaultZoomLevel: 1,
    toolbar: props.toolBarDiv,
    zoomInButton: props.zoomInBtn,
    zoomOutButton: props.zoomOutBtn,
    homeButton: props.resetBtn,
    fullPageButton: props.fullPageBtn
  })

Check out the Viewer event full-screen: https://openseadragon.github.io/docs/OpenSeadragon.Viewer.html#.event:full-screen

Check out the Viewer event full-screen: https://openseadragon.github.io/docs/OpenSeadragon.Viewer.html#.event:full-screen

Yes, thank you that works!


Falabracman Activity intro popup Header text & cross button UI issue solved

hey @llaske
I have correct the Falabracman activity intro popup header issue.
Refer to issue: https://github.com/llaske/sugarizer/issues/1246
Before:

After:

Good work @VedantSharma11 .
I suggest you to mention this tip on the https://github.com/llaske/sugarizer/issues/1090 page so it could be applied for other activities.

@llaske sure i'll mention it there


[BUG] storage suddenly full because of old snapshots

Describe the bug
Today I looked into the longhorn stats and found out that the storage is almost full:

Unfortunatly the guy does not show me which volume waste so much disk space.
I have only a bunch of volumes, which used to only need about 50% of the storage:

I could image that longhorn did not cleanup volumes. I have open all volumes but could not find any specific volume which has more than 3 replicas.
Cubi1 is the only node which hasn't been rebooted for weeks. I suspect that during the rebuilding operations caused by reboots of Cubi2-3 some files were not cleaned up.
I also suspect of longhorn beeing responsible for zombie processes:
Welcome to Ubuntu 20.04 LTS (GNU/Linux 5.4.0-37-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage

  System information as of Wed 17 Jun 2020 08:34:49 PM UTC

  System load:  1.33              Processes:               351
  Usage of /:   43.0% of 9.78GB   Users logged in:         0
  Memory usage: 47%               IPv4 address for cni0:   <IP_ADDRESS>
  Swap usage:   0%                IPv4 address for enp6s0: <IP_ADDRESS>
  Temperature:  52.0 C

  => /var/longhorn is using 92.0% of 98.30GB
  => There are 16 zombie processes.

 * MicroK8s gets a native Windows installer and command-line integration.

     https://ubuntu.com/blog/microk8s-installers-windows-and-macos

2 updates can be installed immediately.
0 of these updates are security updates.
To see these additional updates run: apt list --upgradable

The prometheus volume looks ok in the webgui:

But in the filesystem there are additional files of snapshots which are not shown in the gui. Funny enough I haven't used snapshots for this specific volume...
root@cubi003:/var/longhorn/replicas/pvc-07ac78d6-e7c0-4f5b-a91c-27214846faf1-19c98e47# ls -la
total 35151564
drwx------  2 root root        4096 Jun 15 15:47 .
drwxr-xr-x 26 root root        4096 Jun 15 15:20 ..
-rw-------  1 root root        4096 Jun 17 20:36 revision.counter
-rw-r--r--  1 root root<PHONE_NUMBER>0 Jun 17 20:36 volume-head-001.img
-rw-r--r--  1 root root         178 Jun 15 15:20 volume-head-001.img.meta
-rw-r--r--  1 root root         184 Jun 15 15:47 volume.meta
-rw-r--r--  1 root root<PHONE_NUMBER>0 Jun 15 15:47 volume-snap-0575529f-7b3a-4262-b36c-875dfc08a5a4.img
-rw-r--r--  1 root root         178 Jun 15 15:47 volume-snap-0575529f-7b3a-4262-b36c-875dfc08a5a4.img.meta
-rw-r--r--  1 root root<PHONE_NUMBER>0 Jun 15 15:47 volume-snap-33673919-030e-40de-989a-0285d47a3b25.img
-rw-r--r--  1 root root         178 Jun 15 15:47 volume-snap-33673919-030e-40de-989a-0285d47a3b25.img.meta
-rw-r--r--  1 root root<PHONE_NUMBER>0 Jun 15 15:29 volume-snap-38283387-fefc-4b9b-b997-eab0e6aebd73.img
-rw-r--r--  1 root root         178 Jun 15 15:29 volume-snap-38283387-fefc-4b9b-b997-eab0e6aebd73.img.meta
-rw-r--r--  1 root root<PHONE_NUMBER>0 Jun 15 15:47 volume-snap-54bb0542-7768-409d-aac2-1946906f40c5.img
-rw-r--r--  1 root root         178 Jun 15 15:47 volume-snap-54bb0542-7768-409d-aac2-1946906f40c5.img.meta
-rw-r--r--  1 root root<PHONE_NUMBER>0 Jun 15 15:47 volume-snap-7d8417a3-0b5b-463d-8b0c-736d793911e3.img
-rw-r--r--  1 root root         178 Jun 15 15:47 volume-snap-7d8417a3-0b5b-463d-8b0c-736d793911e3.img.meta
-rw-r--r--  1 root root<PHONE_NUMBER>0 Jun 15 15:47 volume-snap-866eda87-848f-49eb-bd76-c5eea9d90159.img
-rw-r--r--  1 root root         178 Jun 15 15:47 volume-snap-866eda87-848f-49eb-bd76-c5eea9d90159.img.meta
-rw-r--r--  1 root root<PHONE_NUMBER>0 Jun 15 15:20 volume-snap-ad7b6d2a-604e-4b15-9802-850bb48e807c.img
-rw-r--r--  1 root root         178 Jun 15 15:20 volume-snap-ad7b6d2a-604e-4b15-9802-850bb48e807c.img.meta
-rw-r--r--  1 root root<PHONE_NUMBER>0 Jun 15 15:39 volume-snap-d1985dbd-492b-4a4a-88bc-22aec130d387.img
-rw-r--r--  1 root root         126 Jun 15 15:39 volume-snap-d1985dbd-492b-4a4a-88bc-22aec130d387.img.meta
-rw-r--r--  1 root root<PHONE_NUMBER>0 Jun 15 15:29 volume-snap-d55808ea-cdbc-40af-8e16-382ecfb18cf8.img
-rw-r--r--  1 root root         178 Jun 15 15:29 volume-snap-d55808ea-cdbc-40af-8e16-382ecfb18cf8.img.meta
-rw-r--r--  1 root root<PHONE_NUMBER>0 Jun 15 15:47 volume-snap-dbcbed02-3d60-469a-9e4e-fd986859c8a4.img
-rw-r--r--  1 root root         178 Jun 15 15:47 volume-snap-dbcbed02-3d60-469a-9e4e-fd986859c8a4.img.meta

Environment:

Longhorn version: 1.0
Kubernetes version: k3s
Node OS type and version: ubuntu 20.04

Additional context
Add any other context about the problem here.

Btw. this problem affects other volumes too. I just tried to manually delete the files but the storage is still used... I guess some process might still be using the file.
The problem is I cannot reboot the node because this would lead to another big rebuild operation with no storage left...

If the volume is created from backup or gets expanded, there will be a snapshot hidden by the system. (You can check it by enabling the switch Show System Hidden).
Since you mentioned nodes except for cubi001 are rebooted, the snapshots in the directory are caused by the rebuild.
But if there is only one hidden snapshot in the volume and the replica directory mentioned above belongs to an active replica, the case will be weird: If the replica is errored due to rebuilding failure or node reboot, a new replica with a different directory will be created for the next rebuilding, and Longhorn won't reuse the directory of a failed replica. How can there be so many snapshots in that directory?

Can you provide the support bundle to us? we will see if we can find more cues/the cause for this issue.

I can see them using the "show system hidden" feature... deleting them in the webui is very time consuming... (with 10+ volumes and 5-10 snapshots each it would take hours to click and wait)
yes I think it is caused by the reboots... but ad edge a three node cluster is quite normal... longorn should be able to handle single node reboots just fine
I have no idea... today the filesystem is at 100% at cubi002

I have sent you the support bundle via mail. Furthermore please check out my latest file listings:
https://gist.github.com/runningman84/f21953222e2886491a91ff01dc52c81b

Can you please add a cleanup operation (delete old system snapshots) before trying to rebuild degraded volumes? Otherwise the fs is full before even reaching a Healthy state.

Do you mean there are multiple hidden snapshots in the volume and the replica directory you show above is the active one? If YES, then nothing is wrong with the rebuild itself. (Probably except for the zombie process issue.)
Right now what you are worried about is that there may be too many hidden snapshots in the volume and it won't be cleaned up on time. I think there is no doubt that rebuilding needs to copy all snapshots from the existing replica to the new replica.

What I am saying is that I see about 10 hidden snapshots for each volume. I do not get why I need 10 I could imagine to need one last snapshot to sync the volume. Before replicating and rebuilding stuff I would expect a cleanup of old snapshots.
I understand that you have to replicate all normal snapshots which are created using the backup feature.
In my case I have a bunch of bigger volumes which contain log and monitoring data. I don't want any backup of this data anyway. But especially these volumes suffer from this issue.
Maybe we also need a few additional buttons:
Pause rebuilding
Resume rebuilding
Cleanup old system snapshots

Once a replica is rebuilt, there will be a new hidden snapshot in the volume. It seems that your cluster nodes may be rebooted 10 times hence there are 10 rebuilds for each volume.
By deleting an arbitrary snapshot, all hidden snapshots will be cleaned up automatically.
Hence, there are 2 ways to clean up the hidden snapshots:

Manually delete one snapshot.
Create a recurring snapshot/backup job. Then the volume will automatically do snapshot creation and deletion.

The feature rebuilding pause is tracked by issue #307

Ok I manually deleted the snapshots... deleting a single snapshot in each volume also deleted other system snapshots.
For the volumes like elasticsearch and so on I do not want any snapshot or backup. This should also be a valid use case and should not require manual steps. Maybe after rebuilding a volume the final step should be purging old system snapshots...

Btw. the cleanup still does not look complete:

All nodes should have a similar storage usage... because they all have the same replicas. But my two rebooted nodes use additional 16 GB file system space...

When the node is rebooted, the replicas on the nodes will become failed. Then Longhorn will do the cleanup when it decides to remove the failed replica. But the node may be still unavailable during the cleanup. In this case, Longhorn has no way to remove the replica directory on the node. And once the failed replica is gone, the replica directory will be a leftover and Longhorn won't touch it anymore. That's why you see the cleanup not work right now.
The reason why Longhorn doesn't apply an aggressive cleanup is that users can use the left replica directory to recover the data when there is something wrong with Longhorn or the volume. Maybe we can provide an option for the aggressive cleanup later.

The current problem is that I don't know which files are obsolete. The gui does not provide this information.
I understand that a cleanup might be aggressive but once all volumes are green again I don't see any use for these old files...

OK. The replica directory in host is /var/lib/longhorn/replicas/<volume name>-<8 random characters> and you can find the accurate path in the volume detail page. You can follow the below instructions to do manual cleanup:

Log into one node and run cd /var/lib/longhorn/replicas.
List all replica directories on the node ls.
For each directory, check if the corresponding volume still exists and if there is a replica using it. If NO, then you can directly remove the directory.

@runningman84 another part of the story is currently we don't have the awareness of what's leftover on the disk. Once we implemented #1304 , we should be able to enhance this part.
The issue was in fact reported before with #685 .

Ok I manged to cleanup old files... this was very time consuming. I hope to get some automatic solution in the future. Otherwise this would be a nogo for any production system.

@runningman84 Surely we will fix it. #685 targets for v1.1.0 release now.

remove stale due to the incorrect exempt label

Is this still an issue?


Release/0.0.0

Fixes

Merged @dkorrel's fix for #11 mentioned in #12
Removed unused and empty files

Other

Tidied up code using PHPCS, following PSR-1/PSR-2 standards
Added a VERSION.md
Added .gitignore
Added more quality assurance tools, and fixed the ones that were already there
Added rules for new QA tools

If anyone wants to use this before it's potentially merged (obviously it might not be), update your composer.json like this:
"repositories": [
  {
    "type": "git",
    "url": "https://github.com/Gisleburt/soap-client.git"
  }
],
"require": {
    ...
    "phpforce/soap-client": "^0.0.0",
    ...
}

If phpforce/soap-client get's a release number above 0.0.0, it'll automatically override my repository.

Nice cleanup! But could you please remove the QA configs (we have Scrutinizer for that) and squash commits? Thanks!

Scrutinizer isn't a tool I've used before, is this something third parties can use before submitting pull requests or end users can use to check against their implementations?
Using those packages in require-dev allows anyone to run them at any time. Other CI tools I've used  (Travis, Jenkins and PHPCI, which I wouldn't actually recommend unless you really hate Java) are all based around using them.
Sorry if it sounds like I'm being stubborn, it's merely a lack of understanding on my part. :)

Indeed, Scrutinizer will use those tools, but it has them already available, so they don’t need to be installed. All I’d have to do is create a scrutinizer.ym and let Scrutinizer take care of the rest.

Sorry, I mean how do other people use this to check things over?

So this is entirely my opinion but, if you use standard tools that are included in require-dev, with the rules included in the repository, then:

The rules can be used in most CI tools; Travis, Jenkins, Scrutinizer (I assume), PHPCI (...sort of..,)
The rules can be used by contributors to check their work conforms to the defined rules.
Tests can be used by anyone to check integration
Having the QA tools in require-dev means the shouldn't get installed into production

+1 @Gisleburt @ddeboer

:birthday: :smile:


replace V8 Object.Set with ForceSet

Don't know why this part of my changes were left out but node-sodium won't build in io.js without this.

i merged these changes, plus the newer version of libsodium into the develop branch. can you try it and see if it works and compiles fine

No need to test. I made these changes to master branch because develop branch failed to build to some gyp related issues.

Don
try to run make configure before make sodium to generate the right files
for gyp to work.
I added the logic to grab the libsodium defines automatically from the
makefiles
Should be working, but please try it out.
Pedro
On 2/18/15 8:18 PM, Don Park wrote:

No need to test. I made these changes to |master| branch because
|develop| branch failed to build to some gyp related issues.
—
Reply to this email directly or view it on GitHub
https://github.com/paixaop/node-sodium/pull/35#issuecomment-74983442.

Will do later. My pants is on fire for the next few weeks.


[SVE] Change the dtype of Ramp and Broadcast lanes to PrimExpr

This change will allow us to express scalable vectors through Ramp and Broadcast nodes, e.g.
vec = tvm.tir.expr.Ramp(0, 1, 4 * tvm.tir.vscale())

We will use negative values for runtime::DataType the encode the scalable lane values, e.g. the above example would result in lanes = -4. That's because the lanes in runtime::DataType are tied to DLPack standard which uses uint16_t for the lanes. The conversion happens in the node definitions and runtime::DataType, so the int and uint16_t values should never be exposed to the API user, especially after the string support has been added.
Also include the TVMScript support for scalable Ramp and Broadcasts.
Note that this patch doesn't include lowering to the appropriate LLVM vectors, support for data type string representation or LoopVectorizer support. All of these will be part of future patches.

cc @neildhickey @lhutton1 @tqchen @cbalint13 @Lunderberg @Anndrey24

@tvm-bot rerun

Thanks @ekalda @tqchen @Lunderberg


Add command to list words that have exceptions

The results can either be sent in the channel or in DM

@diogoscf Are you up for a challenge?

I planned to make a discord version next, but sure

sure, I'll take it then
BTW I'll create an issue for Discord and assign you.
We'll be pro


Meaning of ClusterID and ServerID

I read some of the other issues to do with getting Kapacitor to play nice with InfluxDB when using Docker.
One of the recommendations was to pre-create Kapacitor subscriptions in InfluxDB using a deterministic cluster ID in order to be able to control the UDP ports which are used for subscription notifications.
I am curious about the actual intended purpose of these two variables. I see them written on first startup to the file system, and they look to contain generated identifiers.
ServerID - this should presumably be unique per Kapacitor host.
ClusterID - does this imply that it is possible to run multiple Kapacitor instances concurrently for a distributed HA setup?
I didn't find any docs on this, but please point me at them if I missed them!
Thanks

@mrwilby You are correct in your understanding of the IDs. While ClusterID is intended to be unique per cluster currently a cluster can only contain a single server. Its simply exists for future needs.

@nathanielc Thanks Nathaniel, appreciate the quick clarification!


Compare different face images

Hi,
I am trying to separate many face images into different classes. e.g., identify all faces of a person, named "Sarah", and put all identified face images into one folder.
Firstly, I download this model (20170511-185253) from this repository.
Secondly, I forward all my face images into this model and save the embedding of faces.
Thirdly,  I calculate the L2 distances with the embedding, between unknown faces and my reference face "Sarah".
Finally, I got this result shown in below figure. The first image is my reference image, "Sarah", the numbers are the distances, the images with red border are identified "Sarah".

But, the problem is that, the distances,
d1 = "reference Sarah" - "real Sarah",
d2 = "reference Sarah" - "not Sarah"
are quite the same.
Does anyone known how can I improve it?

+1
That's the same problem I'm facing to...

Hi,
What input pipeline did you use, i.e. image standardization, alignment, etc?

@davidsandberg hello, the pipeline looks like this:
some image => face detection => crop face => pre whiten =>  neural network => face representations => euclidean distance
I did't use face alignment. Should I use it?
Thanks

@davidsandberg +1,That's the same problem I'm facing to...

@davidsandberg
At me too such problem.
how can you solve this problem? Who knows?

+1 Any innovative ideas yet?


net/http: deadlock after leaked transport detected in TestConsumingBodyOnNextConn

2020-12-01T21:42:10-7fca39a/linux-386-longtest
This is the only failure in the logs matching the regexp (?ms)Test appears to have leaked a Transport.*test timed out. It may be a secondary failure mode associated with #42942, or a different regression from CL 213277, or a latent bug that just happened to turn up now.
CC @neild @fraenkel @bradfitz @nhooyr

Marking as release-blocker for 1.16 at least until we understand whether this is a regression. (CC @golang/release)

I believe this issue is unrelated to the recent change I submitted. My change only modifies how http.Server behaves when keep alives are disabled but they are enabled in the problematic test.

As far as I can tell, the affected test also doesn't use http.Transport anywhere. It's a leak from a different test.

Ah I see, the test I submitted isn't closing rwc. Pushing a fix.

Actually nvm, the body is being closed above before being asserted into a rwc.

As far as I can tell, the affected test also doesn't use http.Transport anywhere. It's a leak from a different test.

So in order for the afterTest leak test to run, t.Short() must be false which also means the tests aren't running in parallel, so I guess I'm wrong, the test must be using http.Transport somewhere. Or there's a test that doesn't have the preceding setParallel call.

Most likely related to #42942 given the goroutine stuck on line 2605.

/cc @neild

Labeling as okay-after-beta1, but still considering this a release blocking issue. Please comment if you disagree.

We discussed this in a release meeting and @neild is planning to look. The goal (from https://github.com/golang/go/issues/42943#issuecomment-737293754) is to understand whether this is a regression. Please update this issue as needed.

We discussed this in a release meeting and @neild is planning to look. The goal (from https://github.com/golang/go/issues/42943#issuecomment-737293754) is to understand whether this is a regression. Please update this issue as needed.

This isn't a regression per say but introduced by a fix, https://github.com/golang/go/issues/41600.

This isn't a regression per say but introduced by a fix, https://github.com/golang/go/issues/41600.

I am unable to reproduce this, and believe it has been fixed by https://golang.org/cl/274973 (the fix for #42942).

I am unable to reproduce this, and believe it has been fixed by https://golang.org/cl/274973 (the fix for #42942).

I understand this issue resolved (i.e., the unusual failure was investigated, and the investigation did not uncover any new reproducible problems to fix), closing.

I understand this issue resolved (i.e., the unusual failure was investigated, and the investigation did not uncover any new reproducible problems to fix), closing.


Unable to dl from hamster

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2018.11.18. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[ x] I've verified and I assure that I'm running youtube-dl 2018.11.18

Before submitting an issue make sure you have:

[ x] At least skimmed through the README, most notably the FAQ and BUGS sections
[ x] Searched the bugtracker for similar issues including closed ones
[ x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[ x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the -v flag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
Mac:Porn Downloads pornacct$ youtube-dl --verbose https://xhamster.com/videos/getting-a-stranger-pregnant-using-natural-insemination-10505612
[XHamster] 10505612: Downloading webpage
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'--verbose', u'https://xhamster.com/videos/getting-a-stranger-pregnant-using-natural-insemination-10505612']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2018.11.18
[debug] Python version 2.7.10 (CPython) - Darwin-17.7.0-x86_64-i386-64bit
[debug] exe versions: ffmpeg 3.3.1, ffprobe 3.3.1
[debug] Proxy map: {}
ERROR: Unable to download webpage: HTTP Error 410: Gone (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 605, in _request_webpage
return self._downloader.urlopen(url_or_request)
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 2211, in urlopen
return self._opener.open(req, timeout=self._socket_timeout)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 437, in open
response = meth(req, response)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 550, in http_response
'http', request, response, code, msg, hdrs)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 475, in error
return self._call_chain(*args)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 409, in _call_chain
result = func(*args)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 558, in http_error_default
raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)

---
### Description of your *issue*, suggested solution and other information

Explanation of your *issue* in arbitrary form goes here. Please make sure the [description is worded well enough to be understood](https://github.com/rg3/youtube-dl#is-the-description-of-the-issue-itself-sufficient). Provide as much context and examples as possible.
If work on your *issue* requires account credentials please provide them or explain how one can obtain them.

I've been using youtube-dl without issue for months, but suddenly it fails to download from xHamster about half the time. I haven't been able to identify any particular trend regarding which videos download and which don't, but I'm experiencing the same issue on both my Mac (see above) and my Windows 10 PC. I've verified that the videos in question play without issue on the site.

No such video.

My apologies! That's bizarre. I played the video without issue 2 hours ago, then was unable to download it. Reloaded the page just now and got the same deleted message you did.

Nope. Still happening with different videos. Got error message, then verified that it plays properly in browser. Windows and Mac.
pornacct$ youtube-dl --verbose https://xhamster.com/videos/teen-snapchat-compilation-10492935
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'--verbose', u'https://xhamster.com/videos/teen-snapchat-compilation-10492935']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2018.11.18
[debug] Python version 2.7.10 (CPython) - Darwin-17.7.0-x86_64-i386-64bit
[debug] exe versions: ffmpeg 3.3.1, ffprobe 3.3.1
[debug] Proxy map: {}
[XHamster] 10492935: Downloading webpage
[debug] Default format spec: bestvideo+bestaudio/best
[debug] Invoking downloader on u'https://19-12.b.cdn13.com/010/492/935/720p.h264.mp4?cdn_creation_time=1542682800&cdn_ttl=14400&cdn_bw=192k&cdn_bw_fs=784k&cdn_cv_data=<IP_ADDRESS>-dvp&cdn_hash=38bb168a5cbd9cd617616a37bfea669f'
ERROR: unable to download video data: <urlopen error [Errno 8] nodename nor servname provided, or not known>
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1908, in process_info
success = dl(filename, info_dict)
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1847, in dl
return fd.download(name, info)
File "/usr/local/bin/youtube-dl/youtube_dl/downloader/common.py", line 364, in download
return self.real_download(filename, info_dict)
File "/usr/local/bin/youtube-dl/youtube_dl/downloader/http.py", line 341, in real_download
establish_connection()
File "/usr/local/bin/youtube-dl/youtube_dl/downloader/http.py", line 109, in establish_connection
ctx.data = self.ydl.urlopen(request)
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 2211, in urlopen
return self._opener.open(req, timeout=self._socket_timeout)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 431, in open
response = self._open(req, data)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 449, in _open
'_open', req)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 409, in _call_chain
result = func(*args)
File "/usr/local/bin/youtube-dl/youtube_dl/utils.py", line 1139, in https_open
req, **kwargs)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 1197, in do_open
raise URLError(err)
URLError: <urlopen error [Errno 8] nodename nor servname provided, or not known>

pornacct$ youtube-dl --verbose https://xhamster.com/videos/good-god-10465624
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'--verbose', u'https://xhamster.com/videos/good-god-10465624']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2018.11.18
[debug] Python version 2.7.10 (CPython) - Darwin-17.7.0-x86_64-i386-64bit
[debug] exe versions: ffmpeg 3.3.1, ffprobe 3.3.1
[debug] Proxy map: {}
[XHamster] 10465624: Downloading webpage
[debug] Default format spec: bestvideo+bestaudio/best
[debug] Invoking downloader on u'https://19-10.b.cdn13.com/010/465/624/240p.h264.mp4?cdn_creation_time=1542682800&cdn_ttl=14400&cdn_bw=72k&cdn_bw_fs=166k&cdn_cv_data=<IP_ADDRESS>-dvp&cdn_hash=967a823dd691e2efca1368de0fcb5968'
ERROR: unable to download video data: <urlopen error [Errno 8] nodename nor servname provided, or not known>
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1908, in process_info
success = dl(filename, info_dict)
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1847, in dl
return fd.download(name, info)
File "/usr/local/bin/youtube-dl/youtube_dl/downloader/common.py", line 364, in download
return self.real_download(filename, info_dict)
File "/usr/local/bin/youtube-dl/youtube_dl/downloader/http.py", line 341, in real_download
establish_connection()
File "/usr/local/bin/youtube-dl/youtube_dl/downloader/http.py", line 109, in establish_connection
ctx.data = self.ydl.urlopen(request)
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 2211, in urlopen
return self._opener.open(req, timeout=self._socket_timeout)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 431, in open
response = self._open(req, data)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 449, in _open
'_open', req)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 409, in _call_chain
result = func(*args)
File "/usr/local/bin/youtube-dl/youtube_dl/utils.py", line 1139, in https_open
req, **kwargs)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 1197, in do_open
raise URLError(err)
URLError: <urlopen error [Errno 8] nodename nor servname provided, or not known>


landscape mode status bar display incorrect

just use lockToLandscape function  status bar display height   but the battery doesn't show  like follow pic

@testxin is this still happening? What RN Version are you using?

I'm seeing this as well, but only on some devices.  Specifically iPhone 6s, 10.2

The fix I found was to put
[application setStatusBarHidden:YES withAnimation:UIStatusBarAnimationNone];
[application setStatusBarHidden:NO withAnimation:UIStatusBarAnimationNone];
in AppDelegate.m in didFinishLaunchingWithOptions

This shouldn't happen with new version v2.0.0. If it persists please open a new issue. Also a workaround was provided above.


fix: Make probe more loose

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

/cherry-pick release-efix
Yes, let's merge it to efix channel


ocamlPackages.mirage{,-runtime}: 3.9.0 -> 3.10.0

Motivation for this change
IPv6
https://github.com/mirage/mirage/releases/tag/v3.10.0
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

cc @vbgl

@GrahamcOfBorg build ocamlPackages.mirage ocamlPackages.mirage-unix ocamlPackages.mirage-crypto-rng-mirage


[melodic|Fedora 31] Rviz segfault under wayland but work under X

Hi!

It's impossible to start rviz under Wayland but it starts fine under X. Under Wayland, rviz segfaults after complaining that Ogre as the wrong screen/server:
[ WARN] [1573737603.322616552]: OGRE EXCEPTION(3:RenderingAPIException): Invalid parentWindowHandle (wrong server or screen) in GLXWindow::create at /builddir/build/BUILD/ogre-1.9.0/RenderSystems/GL/src/GLX/OgreGLXWindow.cpp (line 240)
rviz::RenderSystem: error creating render window: OGRE EXCEPTION(3:RenderingAPIException): Invalid parentWindowHandle (wrong server or screen) in GLXWindow::create at /builddir/build/BUILD/ogre-1.9.0/RenderSystems/GL/src/GLX/OgreGLXWindow.cpp (line 240)

I have tried export LIBGL_ALWAYS_SOFTWARE=1 but the result is the same.
Your environment

OS Version: Fedora 31
ROS Distro: Melodic
RViz, Qt, OGRE, OpenGl version as printed by rviz:[ INFO] [1573737603.105062109]: rviz version 1.13.5
[ INFO] [1573737603.105137221]: compiled against Qt version 5.12.5
[ INFO] [1573737603.105158824]: compiled against OGRE version 1.9.0 (Ghadamon)
[ INFO] [1573737603.114214707]: Forcing OpenGl version 0.
[ INFO] [1573737603.314984160]: Stereo is NOT SUPPORTED
[ INFO] [1573737603.315102243]: OpenGl version: 3 (GLSL 1.3).

If source build, which git commit?

I have used the source install method of the wiki. So I'm at whichever commit this links to.

This seems to be a Wayland issue, not providing full X compatibility. Did you file an issue there?

Ok I've found a temporary solution by forcing the use of X11 on Wayland using QT_QPA_PLATFORM=xcb ./rviz.
I'm not sure whether Wayland is supposed to provide full X compatibility (some program notoriously won't work on Wayland but work on X) or if Rviz needs to be updated for wayland. If the consesnsus is that it's a Wayland problem, I'll go report the error there.

As indicated by the error, the culprit is OGRE, which doesn't support Wayland yet:
https://forums.ogre3d.org/viewtopic.php?t=93084#p537787

I'm not sure whether Wayland is supposed to provide full X compatibility

As far as I know, wayland allows to run an X11 server and thus provide the platform to run any X11 client program - exactly what you did with QT_QPA_PLATFORM=xcb.
However, to natively support wayland, besides relying on corresponding OGRE support, rviz will also require to replace some native X11 calls. See here for some hints:
https://blog.martin-graesslin.com/blog/2015/07/porting-qt-applications-to-wayland/
https://wayland.freedesktop.org/qt5.html

Hello,
This is happened when compiling with colcon using rolling branch.
RViz version 13.3.1 (ROS2 rolling)
Qt version 5.15.10
OGRE version 1.12.10 (Rhagorthua)


⚠ Samsung has degraded performance

In 136a8e9, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 1981 ms

Resolved: Samsung performance has improved in 1f19ac3.


Make Sub-Resource Unique, modify undesirable Node

Godot version:
3.1 calinou 3f01f40
OS/device including version:
Windows 10  Intel HD 4600
Steps to reproduce:

I expected, that Label2 will change size but Label changed size even it wasn't selected.

Does it still happen if you reselect the label after "Make resources unique"?

This only happens, when I change settings in Inspector immediately after select opition "Make Sub-Resource Unique".
When I change Node and return to it, everything seems to work.


memptyWhen / memptyUnless

Provide a specialised version for Option, something like:
declare const memptyWhen: (x: boolean) => <A>(y: Option<A>) => Option<A>

Prior art includes memptyIfFalse and memptyIfTrue.
I can't think of a compelling reason for either of the arguments to be lazy on the basis that this is essentially a conditional constructor which can rely upon the surrounding scope's laziness.

https://github.com/samhh/fp-ts-std/commit/c4ec0e0501714febefb26bae11854100506b16b0 & https://github.com/samhh/fp-ts-std/commit/9244e043b921838cb0451bdd769e8500b11d4a99


CoreFoundation: use local uuid library

@swift-ci please test

Because the target wont be created until after that CMakeList is processed.  Furthermore, there is no reason to assume that it has access to uuid - consider the OpenDarwin folks who use the CoreFoundation standalone build to target the non-Swift runtime.


Ability to use xread and pipeline/tx in parallel

This seems to only be a restriction/issue? with pipeline/tx, simple commands seem to work. Currently ends up in multiple errors: Invalid state, -ERR Protocol error: invalid multibulk length, raw.split is not a function or its return value is not iterable and similar.
const client = await newClient(opts);

// async
client.xread([{ key: "test", xid: 0 }], { block: 5000 });

const tx = client.pipeline();
tx.xadd("test", "*", {a: "a"}, { approx: true, elements: 10000 });
const resp = await tx.flush();

client.close();

Note that simple commands will be delayed and cannot happen in parallel of xread "blocks". The workaround is to use two connections and might be worth clarifying in the documentation.


Improve lifetime management of ledger objects (SLEs) to prevent runaway memory usage. AKA "Is it caching? It's always caching."

High Level Overview of Change
This PR, if merged, changes CachedView to only cache the key needed to find each ledger object (SLE) in the global CachedSLEs, instead of a strong reference to the SLE itself. Further, it releases a hard reference to the last Ledger used for path finding work as soon as there is no more work to be done. Additionally, a bunch of logging is added to monitor cache sizes before and after sweeping for expired objects. The logging is not strictly necessary for the solution, but it doesn't appear to hurt, and can be useful if there are similar issues in the future. Finally, several more objects, and some statistics for the CachedSLEs, are tracked for the get_counts admin command.
Resolves #4224
Context of Change
Currently, the CachedView object holds and keeps strong references (std::shared_ptr) to objects being loaded from the ledger. This prevents those objects from being completely released from the global cache (CachedSLEs, which is a TaggedCache) and releasing their memory until the owning Ledger is released.
This is not a significant problem during typical server operations, but can lead to memory exhaustion in some circumstances, including path finding. This looks like a memory leak, but isn't really, because the memory would be recovered eventually if rippled was able to continue.
It needs to be noted that this is not a guaranteed complete solution for all path finding memory issues. It's still possible that sufficiently large path_search configuration values, or a sufficiently large set of steps, accounts, and trust lines could still consume enough memory to cause problems.
Problems with memory usage during path finding has been an ongoing issue. See also:

417cfc2 (#4061)
#4080
#4099
#4111
#4409

I hope that this is the last word on this issue, but real world performance remains to be seen.
Type of Change

[X ] Bug fix (non-breaking change which fixes an issue)
[X ] Refactor (non-breaking change that only restructures code)

API Impact

[X ] Public API: New feature (new methods and/or new fields)

Potentially adds several new key-value pairs to the output of get_counts.

Before / After
Before
Certain combinations of path finding requests could cause rippled to exhaust available memory and crash, or be killed by the operating system.
After
The same scenarios will not cause rippled to crash, or at worst will allow rippled to service many more requests and run a lot longer before crashing.
Test Plan
This is an optimization that shouldn't affect anything other than this particular edge case. Thus existing test cases should cover it.
Beta testers are encouraged to build this branch, put it on public facing servers with path finding configured, and report back on their results.

Requires additional testing since this makes changes that aren't necessarily specific to pathfinding.
There's a smaller / more targeted change that could be made, which cleans out the pointers: just the changes in src/ripple/app/ledger/impl/LedgerMaster.cpp.
Would like node operators (supporting pathfinding) to run this change to confirm that it resolves the problem.

Trying to get this built on my node box and seem to keep getting stuck here
[57/661] Building CXX object CMakeFiles/xrpl_core.dir/src/ripple/protocol/impl/STIssue.cpp.o
FAILED: CMakeFiles/xrpl_core.dir/src/ripple/protocol/impl/STIssue.cpp.o
/usr/bin/g++ -DBOOST_ASIO_DISABLE_HANDLER_TYPE_REQUIREMENTS -DBOOST_ASIO_USE_TS_EXECUTOR_AS_DEFAULT -DBOOST_BEAST_ALLOW_DEPRECATED -DBOOST_CONTAINER_FWD_BAD_DEQUE -DBOOST_COROUTINES_NO_DEPRECATION_WARNING -DBOOST_FILESYSTEM_DEPRECATED -DCARES_STATICLIB -DDATE_HEADER_ONLY -DDEBUG -DGIT_COMMIT_HASH=\"7bfdc8f2bb514b43d7483f4301b453d1b4e4e1dc\" -DHAS_UNCAUGHT_EXCEPTIONS=1 -DOPENSSL_NO_SSL2 -D_DEBUG -I/home/xrpl/rippled/src -I/home/xrpl/rippled/src/secp256k1/include -I/home/xrpl/rippled/src/ed25519-donna -isystem /home/xrpl/rippled/build/proto_gen -isystem /home/xrpl/rippled/build/proto_gen/src -isystem /home/xrpl/rippled/build/proto_gen_grpc -isystem /home/xrpl/rippled/build/proto_gen_grpc/ripple/proto -isystem /root/.conan/data/openssl/1.1.1u/_/_/package/23b828d52c0630e6b0b96d2945419feb7843c4f8/include -isystem /root/.conan/data/boost/1.82.0/_/_/package/3a52104b31a9c302344831090b42e066cefe22fe/include -isystem /root/.conan/data/date/3.0.1/_/_/package/5ab84d6acfe1f23c4fae0ab88f26e3a396351ac9/include -isystem /root/.conan/data/protobuf/3.21.9/_/_/package/e7b3aae6b77ab32a1300f43e340d3856a5c70e32/include -isystem /root/.conan/data/zlib/1.2.13/_/_/package/23b828d52c0630e6b0b96d2945419feb7843c4f8/include -isystem /root/.conan/data/grpc/1.50.1/_/_/package/e4b22279357772621ebd0f91c7be7bc55142e551/include -isystem /root/.conan/data/abseil/20230125.3/_/_/package/a0d04ca949f5f2ad68af2af705b4e0f9a95967a0/include -isystem /root/.conan/data/c-ares/1.19.1/_/_/package/5a258fabd5aeaa11cbc1951f7243b664f46595f6/include -isystem /root/.conan/data/re2/20230301/_/_/package/a0d04ca949f5f2ad68af2af705b4e0f9a95967a0/include -DBOOST_ASIO_HAS_STD_INVOKE_RESULT -Wall -Wdeprecated -Wextra -Wno-unused-parameter -g -fPIC -Wno-maybe-uninitialized -Wno-deprecated-declarations -frtti -Wnon-virtual-dtor -Wno-sign-compare -Wno-char-subscripts -Wno-format -Wno-unused-local-typedefs -fstack-protector -Wno-unused-but-set-variable -Wno-deprecated -O0 -pthread -Wsuggest-override -std=c++2a -MD -MT CMakeFiles/xrpl_core.dir/src/ripple/protocol/impl/STIssue.cpp.o -MF CMakeFiles/xrpl_core.dir/src/ripple/protocol/impl/STIssue.cpp.o.d -o CMakeFiles/xrpl_core.dir/src/ripple/protocol/impl/STIssue.cpp.o -c /home/xrpl/rippled/src/ripple/protocol/impl/STIssue.cpp
In file included from /home/xrpl/rippled/src/ripple/basics/base_uint.h:28,
                 from /home/xrpl/rippled/src/ripple/protocol/UintTypes.h:24,
                 from /home/xrpl/rippled/src/ripple/protocol/Issue.h:24,
                 from /home/xrpl/rippled/src/ripple/protocol/STIssue.h:24,
                 from /home/xrpl/rippled/src/ripple/protocol/impl/STIssue.cpp:20:
/home/xrpl/rippled/src/ripple/basics/Expected.h:139:5: error: ‘requires’ does not name a type
  139 |     requires std::convertible_to<U, T> constexpr Expected(U && r)
      |     ^~~~~~~~
/home/xrpl/rippled/src/ripple/basics/Expected.h:145:9: error: ‘requires’ does not name a type
  145 |         requires std::convertible_to<U, E> &&
      |         ^~~~~~~~
/home/xrpl/rippled/src/ripple/basics/Expected.h:221:9: error: ‘requires’ does not name a type
  221 |         requires std::convertible_to<U, E> &&
      |         ^~~~~~~~
In file included from /home/xrpl/rippled/src/ripple/protocol/UintTypes.h:24,
                 from /home/xrpl/rippled/src/ripple/protocol/Issue.h:24,
                 from /home/xrpl/rippled/src/ripple/protocol/STIssue.h:24,
                 from /home/xrpl/rippled/src/ripple/protocol/impl/STIssue.cpp:20:
/home/xrpl/rippled/src/ripple/basics/base_uint.h:553:37: error: ‘strong_ordering’ in namespace ‘std’ does not name a type
  553 | [[nodiscard]] inline constexpr std::strong_ordering
      |                                     ^~~~~~~~~~~~~~~
/home/xrpl/rippled/src/ripple/basics/base_uint.h: In function ‘constexpr bool ripple::operator==(const ripple::base_uint<Bits, Tag>&, const ripple::base_uint<Bits, Tag>&)’:
/home/xrpl/rippled/src/ripple/basics/base_uint.h:578:19: error: expected primary-expression before ‘>’ token
  578 |     return (lhs <=> rhs) == 0;
      |                   ^
In file included from /home/xrpl/rippled/src/ripple/protocol/STIssue.h:24,
                 from /home/xrpl/rippled/src/ripple/protocol/impl/STIssue.cpp:20:
/home/xrpl/rippled/src/ripple/protocol/Issue.h: At global scope:
/home/xrpl/rippled/src/ripple/protocol/Issue.h:88:37: error: ‘weak_ordering’ in namespace ‘std’ does not name a type
   88 | [[nodiscard]] inline constexpr std::weak_ordering
      |                                     ^~~~~~~~~~~~~
In file included from /home/xrpl/rippled/src/ripple/protocol/STIssue.h:26,
                 from /home/xrpl/rippled/src/ripple/protocol/impl/STIssue.cpp:20:
/home/xrpl/rippled/src/ripple/protocol/STBase.h:64:67: error: ‘constexpr bool ripple::operator==(ripple::JsonOptions, ripple::JsonOptions)’ cannot be defaulted
   64 |     operator==(JsonOptions lh, JsonOptions rh) noexcept -> bool = default;
      |                                                                   ^~~~~~~
/home/xrpl/rippled/src/ripple/protocol/STBase.h:66:67: error: ‘constexpr bool ripple::operator!=(ripple::JsonOptions, ripple::JsonOptions)’ cannot be defaulted
   66 |     operator!=(JsonOptions lh, JsonOptions rh) noexcept -> bool = default;
      |                                                                   ^~~~~~~
In file included from /home/xrpl/rippled/src/ripple/protocol/impl/STIssue.cpp:20:
/home/xrpl/rippled/src/ripple/protocol/STIssue.h: In function ‘bool ripple::operator<(const ripple::STIssue&, const ripple::STIssue&)’:
/home/xrpl/rippled/src/ripple/protocol/STIssue.h:125:24: error: no match for ‘operator<’ (operand types are ‘const ripple::Issue’ and ‘const ripple::Issue’)
  125 |     return lhs.issue() < rhs.issue();
      |            ~~~~~~~~~~~ ^ ~~~~~~~~~~~
      |                     |             |
      |                     |             const ripple::Issue
      |                     const ripple::Issue
In file included from /home/xrpl/rippled/src/ripple/basics/base_uint.h:29,
                 from /home/xrpl/rippled/src/ripple/protocol/UintTypes.h:24,
                 from /home/xrpl/rippled/src/ripple/protocol/Issue.h:24,
                 from /home/xrpl/rippled/src/ripple/protocol/STIssue.h:24,
                 from /home/xrpl/rippled/src/ripple/protocol/impl/STIssue.cpp:20:
/home/xrpl/rippled/src/ripple/basics/Slice.h:220:1: note: candidate: ‘bool ripple::operator<(const ripple::Slice&, const ripple::Slice&)’
  220 | operator<(Slice const& lhs, Slice const& rhs) noexcept
      | ^~~~~~~~
/home/xrpl/rippled/src/ripple/basics/Slice.h:220:24: note:   no known conversion for argument 1 from ‘const ripple::Issue’ to ‘const ripple::Slice&’
  220 | operator<(Slice const& lhs, Slice const& rhs) noexcept
      |           ~~~~~~~~~~~~~^~~
In file included from /home/xrpl/rippled/src/ripple/protocol/impl/STIssue.cpp:20:
/home/xrpl/rippled/src/ripple/protocol/STIssue.h:123:1: note: candidate: ‘bool ripple::operator<(const ripple::STIssue&, const ripple::STIssue&)’
  123 | operator<(STIssue const& lhs, STIssue const& rhs)
      | ^~~~~~~~
/home/xrpl/rippled/src/ripple/protocol/STIssue.h:123:26: note:   no known conversion for argument 1 from ‘const ripple::Issue’ to ‘const ripple::STIssue&’
  123 | operator<(STIssue const& lhs, STIssue const& rhs)
      |           ~~~~~~~~~~~~~~~^~~
/home/xrpl/rippled/src/ripple/protocol/STIssue.h: In function ‘bool ripple::operator<(const ripple::STIssue&, const ripple::Issue&)’:
/home/xrpl/rippled/src/ripple/protocol/STIssue.h:137:24: error: no match for ‘operator<’ (operand types are ‘const ripple::Issue’ and ‘const ripple::Issue’)
  137 |     return lhs.issue() < rhs;
      |            ~~~~~~~~~~~ ^ ~~~
      |                     |    |
      |                     |    const ripple::Issue
      |                     const ripple::Issue
In file included from /home/xrpl/rippled/src/ripple/basics/base_uint.h:29,
                 from /home/xrpl/rippled/src/ripple/protocol/UintTypes.h:24,
                 from /home/xrpl/rippled/src/ripple/protocol/Issue.h:24,
                 from /home/xrpl/rippled/src/ripple/protocol/STIssue.h:24,
                 from /home/xrpl/rippled/src/ripple/protocol/impl/STIssue.cpp:20:
/home/xrpl/rippled/src/ripple/basics/Slice.h:220:1: note: candidate: ‘bool ripple::operator<(const ripple::Slice&, const ripple::Slice&)’
  220 | operator<(Slice const& lhs, Slice const& rhs) noexcept
      | ^~~~~~~~
/home/xrpl/rippled/src/ripple/basics/Slice.h:220:24: note:   no known conversion for argument 1 from ‘const ripple::Issue’ to ‘const ripple::Slice&’
  220 | operator<(Slice const& lhs, Slice const& rhs) noexcept
      |           ~~~~~~~~~~~~~^~~
In file included from /home/xrpl/rippled/src/ripple/protocol/impl/STIssue.cpp:20:
/home/xrpl/rippled/src/ripple/protocol/STIssue.h:123:1: note: candidate: ‘bool ripple::operator<(const ripple::STIssue&, const ripple::STIssue&)’
  123 | operator<(STIssue const& lhs, STIssue const& rhs)
      | ^~~~~~~~
/home/xrpl/rippled/src/ripple/protocol/STIssue.h:123:26: note:   no known conversion for argument 1 from ‘const ripple::Issue’ to ‘const ripple::STIssue&’
  123 | operator<(STIssue const& lhs, STIssue const& rhs)
      |           ~~~~~~~~~~~~~~~^~~
/home/xrpl/rippled/src/ripple/protocol/STIssue.h:135:1: note: candidate: ‘bool ripple::operator<(const ripple::STIssue&, const ripple::Issue&)’
  135 | operator<(STIssue const& lhs, Issue const& rhs)
      | ^~~~~~~~
/home/xrpl/rippled/src/ripple/protocol/STIssue.h:135:26: note:   no known conversion for argument 1 from ‘const ripple::Issue’ to ‘const ripple::STIssue&’
  135 | operator<(STIssue const& lhs, Issue const& rhs)
      |           ~~~~~~~~~~~~~~~^~~
ninja: build stopped: subcommand failed.

Feed back so far.

follow up responses to the initial path_find request seem slower than what we have today.. the production build seems to return results much more frequently.
memory seems to behave for the 2-3 hrs I let node run on "normal" requests and some light pathing requests.

asked few a few people to hit a front end that adds a bunch of load on the box and managed to bring it down. Here is error log...

2023-Dec-04 21:38:43.756954454 UTC NetworkOPs:WRN Missing offer
2023-Dec-04 21:38:43.757092579 UTC NetworkOPs:WRN Missing offer
2023-Dec-04 21:38:43.758713948 UTC NetworkOPs:WRN Missing offer
2023-Dec-04 21:38:43.759163464 UTC NetworkOPs:WRN Missing offer
2023-Dec-04 21:38:43.829825677 UTC Resource:WRN Consumer entry <IP_ADDRESS> dropped with balance 15010 at or above drop threshold 15000
2023-Dec-04 21:38:43.830112890 UTC Resource:WRN Consumer entry <IP_ADDRESS> dropped with balance 15104 at or above drop threshold 15000
rippled: /root/.conan/data/boost/1.82.0/_/_/package/3a52104b31a9c302344831090b42e066cefe22fe/include/boost/beast/websocket/detail/soft_mutex.hpp:89: bool boost::beast::websocket::detail::soft_mutex::try_lock(const T*) [with T = boost::beast::websocket::stream<boost::beast::basic_stream<boost::asio::ip::tcp, boost::asio::executor, boost::beast::unlimited_rate_policy> >::close_op<boost::asio::executor_binder<ripple::BaseWSPeer<ripple::ServerHandler, ripple::PlainWSPeer<ripple::ServerHandler> >::close(const boost::beast::websocket::close_reason&)::<lambda(const error_code&)>, boost::asio::strand<boost::asio::executor> > >]: Assertion `id_ != T::id' failed.
 Here is error log...

That looks like a problem at the websocket layer, which path finding shouldn't affect. Can you tell if the same issue occurs under heavy load without this change?

Can you tell if the same issue occurs under heavy load without this change?

yeah it was fine with just me hitting the box for 2-3 hours, it did not fall over with that error.

right did some more testing off the develop branch this morning @ximinez

can validate that the issue is present outside of this change as well.

I run that interface off the 1.12.0 prod build and it does not fail with this error under decent load.

When you say "prod build", do you mean the published packages? Those have asserts disabled, so even if the issue exists there, you wouldn't see it. Could you build https://github.com/XRPLF/rippled/tree/1.12.0 the same way you built develop, and see if the issue exists there, too?

right did some more testing off the develop branch this morning @ximinez
can validate that the issue is present outside of this change as well.

Given the issue appears on develop (without #4822 - and therefore doesn't seem to be related to this PR), can you open a new issue so we can track/discuss your findings there? @lathanbritz

@Bronek @thejohnfreeman I pushed a commit to change the "miss" label to be lower-case. I don't think it requires re-review, but I wanted to give you a heads up.

@sophiax851 this may require perf signoff

Internal tracker: RPFC-79

Perf SignedOff: Examined the tagged cache sweeping during the test during lab testing and using a Mainnet node, didn’t observe abnormal behavior. No performance regression observed either.
Released in 2.0.1.

It's worth mentioning that this "Perf SignedOff" testing was conducted to ensure that there is no performance regression in the normal transaction processing with the changes made in this PR which was intended to address the root cause of the issue that I identified for #4224 . There was separate testing conducted in verifying the #4224.


Update free-programming-cheatsheets.md

What does this PR do?
Add resource(s)
For resources
Description
Add R color cheat sheet
Why is this valuable (or not)?
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

please resolve conflicts.

@eshellman Could you please review my work?

please resolve conflicts.

@eshellman I have resolved the conflicts.


First iteration of the manage translations form

Description

Adds route endpoints for managing program translations in routes
Adds AdminProgramTranslationsController to handle editing and updating localizations
Adds a form for updating program text translations (includes ProgramTranslationForm for binding, and ProgramTranslationView for displaying)

An admin can manage translations for a given program by:

Create a new draft program
Click "Manage Translations" on the program index view
Select the language they want to update
Add display name and description for that language
Submit

Checklist

[ ] Created tests which fail without the change (if possible)
[ ] Extended the README / documentation, if necessary

Issue(s)
#777

The translation view looks really nice. One non-blocking question: do we now have two ways to update the default locale: one in program edit page and one in the translation page?

Great question! Yes we do have two ways, that's a great point. I made issue #875 to capture this side effect


CB-5588 Enable Knox HA proxy for Schema Registry

Enabled HA proxying for Schema Registry in the Knox topology template.
Tested manually (installed a cluster with 2 Schema Registry instances, checked UI and API with either of the instances down)
Closes CB-5588

retest this please

retest this please


feat: add message modal when service worker is activated

This PR adds a message modal when users activate the service worker in order to notify them that their browser is an IPFS gateway after the activation.
It closes #30.

The close button in desktop is pretty weird, I think it's cut off:

We should add a scroll to the message when opening the "modal", in a tablet is pretty easy to miss it:

Just to leave some feedback, @diasdavid, the message should be a real modal that stood on top of the svg after it's done animating; that way people would possibly read it and then dismiss it.
The way it's done now seems odd, I bet many people won't read it and moreover, the containers have to jump around because of it... I really don't think it's ideal.


Henry Kuiper TSO/ISPF Git

Invite Henry Kuiper with his ZIGI project.
https://github.com/wizardofzos/zigi

Thank you for the suggestion and invitation.


WebtoonXYZ

assuming https://www.webtoon.xyz/

Where i can check the documentation to create the source for this page?? im interested in this source and im able to help with the source

The contributing guide should help, as well as the pins in #source-dev on the Discord server.


Update verify release set

Currently, verify release set works at follows:
Given the service directory and a list of libraries to be released verify that the list of libraries has full transitive closure. This means that we have to look at each library's pom file's current dependencies and ensure that each dependency is contained within the
list to be released.
The update I'm making here is:
If the current dependency isn't on the list of libraries to be released, instead of failing, check Maven to see if it was already released and, if so, allow the release to proceed. The scenario here would be releasing a library for a patch that's using the released versions of libraries within the same service directory. In other words, the current dependency on another library in the same service directory has already been released. This would also help if someone accidentally unchecked a checkbox for an was able to release everything else in the service directory and had to start another run to release the single library.
It's worth noting that the IsMavenPackageVersionPublished has been being used for several years to check whether or not something exists before creating the release/tag and it's tried and true, I'm just using it.

/azp run - java - template - ci

There's nothing in any CI pipeline that'll test this. I've run a template release against this refs/pull to verify.


Workspace count with multi-monitor

Even when you have monitor specific enabled, hyprpanel shows all workspaces that aren't linked to a specific monitor.
Feature request: for it to only show a workspace depending on the monitor that it's on.
Issue example
workspace 1 is linked to monitor 1
workspaces 2 and 3 are linked to monitor 2
Workspaces 4 and 5 are on monitor 2.
Hyprpanel on monitor 1 shows workspaces 4 and 5 that are on monitor 2.

made a "fix" in occupied.ts for workspaces
.filter((i) => {
const workspace = hyprland.workspaces.find((ws) => ws.id === i);
return workspace && (!monitorSpecific || (curMonitor && workspace.monitorID === curMonitor.id));
})

you can create a PR if you like

not sure if i want to because idk how reliable it is with other settings

rep. That fix solved it for me also.


add api version to mqtt.client for new version 2.0.0 compatibility

https://github.com/MiczFlor/RPi-Jukebox-RFID/discussions/2263

Seems like a new Version (2.0.0) of the plugin was released last week, that included breaking changes.
https://github.com/eclipse/paho.mqtt.python/blob/v2.0.0/docs/migrations.rst

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 76.82%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
633

Relevant Lines:
824

💛  - Coveralls

User reported the fix works: https://github.com/MiczFlor/RPi-Jukebox-RFID/discussions/2263#discussioncomment-8499675
So we could merge.


Drawing "red box" error

Description
It looks like the model for segmenting out the individual seeds and drawing red boxes around them has an issue when the red boxes would overlap, due to the shape, proximity, or orientation of the seeds.
Expected behavior
A red box would be drawn around each seed, overlapping slightly due to the angled orientation of the seeds
Actual Behavior
Only a single box is visible, surrounding the first (leftmost, higher) seed. Both IDs appear to be attached to that box. When I rotate the seeds so that the red boxes can be drawn without them overlapping, they appear as expected.
Supporting Images
To better understand the issue, please add screenshots:

Results: Include a screenshot of the interface showing the classification error or the issue as it appears in your environment.

Source Image: Attach the actual picture or image used when you encountered the issue.

Microscope Settings:  the microscope settings when the picture was taken.

@MaxenceGui can you provide an explanation as to why this is a backend issue rather than a model or frontend issue?

I want to investigate this in the backend before assuming it's a frontend issue because in the process_inference_request line 93 there a double for loop that decide if a box need to be hide if it's overlapping another one. If my assumption is wrong, I will transfer this issue to the frontend.


500: Play high and get the joker out

For God sakes, in 500, when the bot bids and has top cards but not the joker, make it stop throwing low 4 or 5 on first trick. Play high and get the joker out. That is the correct move. Or play low one time and if that doesn't work don't play it again. If bot plays low and I play low it means I don't have a high trump card, so don't play low a second time and essentially guarantee a set because the opponents can take the first two tricks with low trump cards and then still have the joker.

This is the most frustrating part of the 3 games I play. In 500 the bot calls 8 trumps and leads a 4 the opposition take it with a 7 for example. The game continues and we're set with the bot having left right Ace. Honestly it needs to be changed so that the bot leads an ace minimum.if going 7 or more.

When a bot wins the bid but does not have the joker, it is understandable to have it play the lowest trump, but after the partner does not have the joker, the bot with the bid should play either the highest or next highest trump in their hand. They give up too many tricks if they keep playing the lowest trump.


Consolidate YAML files [part-6]

This PR relocates the YAML files used by the stateful application
examples.

/assign @steveperry-53

Preview links:

https://deploy-preview-9261--kubernetes-io-master-staging.netlify.com/docs/tutorials/stateful-application/basic-stateful-set/
https://deploy-preview-9261--kubernetes-io-master-staging.netlify.com/docs/tutorials/stateful-application/cassandra/
https://deploy-preview-9261--kubernetes-io-master-staging.netlify.com/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume/
https://deploy-preview-9261--kubernetes-io-master-staging.netlify.com/docs/tutorials/stateful-application/zookeeper/

/approve
/lgtm


The week cannot be displayed normally

Environment

Windows 10 2004

Chinese language

Neovim v0.4.4

My vimrc
Screenshot

Let language to en_US can solve this problem. It seems that clander does not support Chinese encoding.
:lan en_US or insert language en_US in vimrc


Set File Extensions GUI

Example: https://github.com/cxasm/notepad--/issues/280#issuecomment-1865387982
Everything is integrated into the code editor. I don't want to have to open another text editor only to edit config file: https://github.com/SpartanJ/ecode/discussions/194

Agree. This needs design.

Agree. This needs design.

What do you think about Geany's approach? Tools -> Configuration Files will list the config files. Clicking on any of them will open the corresponding configuration file. This way, one can edit the configuration files without having to leave the editor. For example, Tools -> Configuration Files -> filetype_extensions.conf will open filetype_extensions.conf inside Geany. It seems to be hard with ecode as you said ecode will overwrite the configuration files when exit.


History

System was showing in history when admin approved order
Maybe because the react change I made or might be projection needs the user.

The history record has an acted by, so it is either my projection or react code changes

For the order projection, I filter the history, but unless I include the hostory.actedBy, it returns null and System is displayed.
Can either do an Include before the projection, or maybe have a separate call that populates the history table.


Expose addFiles method

I exposed a new public method addFiles. It works same as addFile but you can pass multiple files at once.
const resumable = new Resumable();
const files = [new File([], 'test.tmp'), new File([], 'foo.bar')];

resumable.addFiles(files);

This is needed in the case that you want to receive consistent events for bulk file adding.
Let me know if I need to update any other file.
Thanks!

@steffentchr @cpnielsen any chance to have a look into this? :crossed_fingers:

Simple, straightforward, looks good 👍  Thanks @zzarcon!

@cpnielsen awesome! thanks 🙌

@cpnielsen when will this be released? which version for resumable.js will it go into?

@cpnielsen could you please give us an update on this? really looking forward to the next release! 😄

@majames We are looking to make a general resumable.js release this week (hopefully), likely bumping the version number to 1.1.0, but I cannot say exactly when this will happen.


SQlite strategy needs to await creating tables

In the sqlite strategy we create the necessary table in the constructor, but we don't await on the promise..
This is potentially a problem since the action might not be done until significantly after the constructor finishes if the file system is slow for some reason.

This was solved in #27


"Create" and "Delete" are not valid Azure Powershell verbs

Quote: "The verb describes the action (examples include Create, Get, Set, Delete)"
"Create" and "Delete" are not valid Azure Powershell verbs.  The applicable example verbs are likely to be "New" and "Remove"... although "New" isn't a verb in the English language, making it a slightly confusing example choice. The list of valid verbs is linked in the article.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: afd3c996-55c2-59cc-7be0-cedc187774cd
Version Independent ID: cc8aa9be-2707-4ef6-e4d9-35498b837289
Content: Get started with Azure PowerShell
Content Source: docs-conceptual/azps-2.3.2/get-started-azureps.md
GitHub Login: @sptramer
Microsoft Alias: sttramer

The AzureRM module (and now Az module) do use some non-standard verbs. This is by design, to make the intent of the operation clearer regarding resource allocation/deletion. If you'd like to see aliases using the standard verbs made available, please file an engineering ticket.

It sounds like there's a misunderstanding.  I was confused why the quote mentioned Create and Delete.

Because these are verbs used frequently in the Azure PowerShell cmdlet set, and so being aware of them is useful for the purposes of searching for cmdlets.

Sorry, after I took some time to review this, information in the quote is actually a typo: They should read New and Remove. This should be fixed within the next couple of days.


Add example for deploy script after upgrade

[ ] Bug fix #…?
[ ] New feature?
[ ] BC breaks?
[ ] Deprecations?
[ ] Tests added?
[ ] Changelog updated?

Just a UPGRADE.md update.

Fixed the missing doc!


Use only Polaris release version is spack env name

This means that we update the release version for new spack envs and we update the alpha, beta, etc. for dependency changes.
The docs for spack deployment have been updated accordingly.
Port of https://github.com/MPAS-Dev/compass/pull/743 from Compass.

Checklist

[x] Developer's Guide has been updated
[x] Documentation has been built locally and changes look as expected
[ ] Testing comment in the PR documents testing used to verify the changes

Testing
I reran the ./configure_polaris_envs.py script on Perlmutter and verified that the spack environment for v0.2.0 still works (because there is currently no alpha version).
Then, I successfully ran the pr suite.


FIX the redirection after login in the admin panel

Fix #2206
By adding the Global variable YOURLS_SITE to the redirection

Ah, indeed, you're onto something.
Anyway this won't work when YOURLS is installed in a subdir. Also, this needs to comply to the current SSL situation (ie if URL requested is https, return https)

I think this should work in all cases:
yourls_match_current_protocol(yourls_sanitize_url(sprintf("%s%s", $_SERVER['SERVER_NAME'], $_SERVER['REQUEST_URI'])))
(albeit not the best readable thingie)


Can't install babel-core

mac 10.11.3
npm i babel-core
npm ERR! node v4.3.2
npm ERR! npm  v2.14.12
npm ERR! notarget No compatible version found<EMAIL_ADDRESS><7.0.0'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["6.5.0-1","6.2.4","6.6.0","6.3.13","6.5.0","6.0.2","6.2.0","6.0.12","6.3.0","6.1.18","6.0.14","6.0.15","6.0.16","6.1.17"]
npm ERR! notarget

Are you using a a proxy/mirror for npm?
npm view babylon dist-tags
{ latest: '6.6.4', old: '5.8.35', stable: '6.6.0' }

Also, this is the babel website repo - check phabricator for issues with babel (https://phabricator.babeljs.io/T7181)

I am using an internal registry. But the issue just started happening today. It wasn't working even installing when installing via the package.json and the version of babel-core hasn't been change in months.

Well its definetely updated on the public registry so not sure what we can do there for that specific case. We're talking about on just pinning dependencies if we can modify all the packages dependencies
 '6.5.0': '2016-02-07T00:06:46.070Z',
 '6.5.1': '2016-02-08T02:18:16.980Z',
 '6.5.2': '2016-02-12T16:30:05.366Z',
 '6.6.0': '2016-02-29T21:12:20.206Z',
 '6.6.4': '2016-03-02T21:29:24.740Z'


Configuration of pre-exec terminal title

Added ZSH_THEME_TERM_TAB_TITLE_EXEC and ZSH_THEME_TERM_TITLE_EXEC configuration variables to allow pre-exec title configuration
Right now, only idle titles are customizable. Defaulted to their current values.

That is too complicated to make it into the project. A better option is to redefine the whole function, or make a separate preexec function and add it to precmd_functions.
Thank you for your contribution though


"ImportError: cannot import name 'observe'"

Hi, using python 3.6.1, venv, Jupyter v 5.0.0, I just tried the bubblesort demo in a fresh venv and got "ImportError: cannot import name 'observe'". Stack trace + $ pip freee.

Hi, First of all thank you for leaving the issue. In my case, there was no problem in the same environment. I'll try a little more, but it seems to be a problem with traitlets. Can you try development installation and tell me the results?
$ git clone https://github.com/sn0wle0pard/ipytracer.git
$ cd ipytracer
$ pip install -e .
$ jupyter nbextension install --py --symlink --sys-prefix ipytracer
$ jupyter nbextension enable --py --sys-prefix ipytracer

Hi @sn0wle0pard. I don't think this is your problem. I think it's related to the Jupyter weirdness I've mentioned in the Jupyter Client issue.

Hey, I'm not sure if my system is particularly messed up right now, or jupyter notebook is kind of unstable ATM, but you might be amused to know that I had to work through two addition pretty confusing bugs before I finally got the bubblesort demo working in a fresh venv. : D


talk to NPC & fall for trap view implemented

There is a problem in the talk to npc view so please don't merge it - this is just an update. I'll make another pull request once the problem is resolved.

I fixed all the errors and updated views for fall for trap and talk to NPC so please review it and merge it. Thanks.


[FLINK-21133][connector/checkpoint] Fix the stop-with-savepoint case …

…in FLIP-27 source by stopping the mailbox loop in SourceOperatorStreamTask#finishTask().
What is the purpose of the change
This patch fixes the stop-with-savepoint case with FLIP-27 source. The issue was that stop-with-savepoint logic expects the tasks to exit by themselves after the synchronous savepoint is taken. The FLIP-27 source did not implement StreamTask#finishTask() so the tasks won't exit. This patch fixes the issue by stopping the mailbox loop in the SourceOperatorStreamTask#finishTask() method.
The unit test was copied from @kezhuw 's branch.
Brief change log

stop the mailbox loop in  SourceOperatorStreamTask#finishTask() method.

Verifying this change
The following unit test has been added to verify the change.
SavepointITCase#testStopSavepointWithFlip27Source.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

@pnowojski @StephanEwen @kezhuw Will you have time to take a look? Thanks.

@flinkbot run azure

PR Merged.
master a9cf18b4d25f130e0bd24d51b128bbcf71892b45
release-1.13: e129817f290442c6fd7e891a6d28d848ec090050


golang conform

Automatically importing packages, and then deleting the packages in the import when saving, I think there may be a bug

The packages imported during writing are normal, but when I execute : w , all the imported packages are gone

Yeah i see what you mean. It initially is fine but if you then delete it and then try to put it back in again it start deleting it. I have no idea why but i know where it's coming from.
if you remove or comment out this it should fix it. But unneeded imports will not be automatically removed anymore.
        ["goimports-reviser"] = {
            prepend_args = { "-rm-unused" },
        },

you are right, close  -rm-ununsed can solve this question , maybe version cause

Problem still exists and makes the entire setup not usable.
This is my ~/.config/lua/configs/conform.lua
local options = {
    formatters_by_ft = {
        lua = { "stylua" },
        go = { "gofumpt", "goimports-reviser", "golines" },
    },

    formatters = {
        ["goimports-reviser"] = {
            prepend_args = { "-rm-unused" },
        },
        golines = {
            prepend_args = { "--max-len=80" },
        },
    },

    format_on_save = {
        -- These options will be passed to conform.format()
        timeout_ms = 500,
        lsp_fallback = true,
    },
}

require("conform").setup(options)

return options

Once a project is initialized any new import gets automatically deleted, even if it's used in the go project. In this case my added html engine and fmt get deleted instantly when using :w.
import (
        "fmt"
	"github.com/gofiber/fiber/v2"
        "github.com/gofiber/template/html/v2"
)


GitHub login 500s if a user is connecting with a different host than expected.

(not sure if this is the right forum!)
Clicking 'login with GitHub' on chat.zulip.org takes me to a 500 page, with
500: Internal server error.

Well oops. This one's probably our fault. Sorry about that! Updates on service availability are posted to @ZulipStatus on Twitter.

If you'd like, you can drop us a line to let us know what happened.

Thanks for the bug report @yuvipanda!  This is in part a configuration thing -- chat.zulip.org is in the process of being renamed from zulip.tabbott.net, and the way GitHub oauth works, it doesn't support more than one URL to post back to at a time.  I believe we've moved all the links to zulip.tabbott.net and can finish the transition over the chat.zulip.org, so I just switched the GitHub oauth default to point to chat.zulip.org (which means GitHub auth now 500s if you use the zulip.tabbott.net URL).
Still a bug that it 500s rather than giving a clear error.
The traceback is this:
2016-11-03 19:09:35,782 ERROR    Internal Server Error: /complete/github/
Traceback (most recent call last):
  File "/home/zulip/deployments/2016-10-28-14-47-19/zulip-venv/lib/python2.7/site-packages/django/core/handlers/base.py", line 132, in get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/home/zulip/deployments/2016-10-28-14-47-19/zulip-venv/lib/python2.7/site-packages/django/views/decorators/cache.py", line 57, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
  File "/home/zulip/deployments/2016-10-28-14-47-19/zulip-venv/lib/python2.7/site-packages/django/views/decorators/csrf.py", line 58, in wrapped_view
    return view_func(*args, **kwargs)
  File "/home/zulip/deployments/2016-10-28-14-47-19/zulip-venv/lib/python2.7/site-packages/social/apps/django_app/utils.py", line 51, in wrapper
    return func(request, backend, *args, **kwargs)
  File "/home/zulip/deployments/2016-10-28-14-47-19/zulip-venv/lib/python2.7/site-packages/social/apps/django_app/views.py", line 28, in complete
    redirect_name=REDIRECT_FIELD_NAME, *args, **kwargs)
  File "/home/zulip/deployments/2016-10-28-14-47-19/zulip-venv/lib/python2.7/site-packages/social/actions.py", line 44, in do_complete
    user = backend.complete(user=user, *args, **kwargs)
  File "/home/zulip/deployments/2016-10-28-14-47-19/zulip-venv/lib/python2.7/site-packages/social/backends/base.py", line 41, in complete
    return self.auth_complete(*args, **kwargs)
  File "/home/zulip/deployments/2016-10-28-14-47-19/zulip-venv/lib/python2.7/site-packages/social/utils.py", line 246, in wrapper
    return func(*args, **kwargs)
  File "/home/zulip/deployments/2016-10-28-14-47-19/zulip-venv/lib/python2.7/site-packages/social/backends/oauth.py", line 385, in auth_complete
    state = self.validate_state()
  File "/home/zulip/deployments/2016-10-28-14-47-19/zulip-venv/lib/python2.7/site-packages/social/backends/oauth.py", line 88, in validate_state
    raise AuthStateMissing(self, 'state')
AuthStateMissing: Session value state missing.

It seems like this might be a bug in python-social-auth since I don't see any of our code in the traceback; @umairwaheed can you investigate?  It's reproducible if you just have the GitHub OAuth2 configuration inconsistent with the actual server about what hostname that still resolves to the right server is being used.

Sure.

Actually, it seems likely that we want to solve this the same way that we solved it for Google auth, namely having our GitHub auth button go to a canonical URL.

Yes, this is what I had on mind.

Starting this.

This was fixed in https://github.com/zulip/zulip/pull/2501/. I accidentally tagged #2501 which was the id of the PR.

Oh yeah, closing.


Add TX indication on GPIO

TXANT_EN indication added to GPIO[0].
To enable it, set FPGA register 0x00C0[0]  bit to '0';
To control TXANT_EN rising and falling edge delays use FPGA registers:
0x0010 - TXANT_PRE
0x0011 - TXANT_POST
By default TXANT_PRE and TXANT_POST registers are set to 0x0001. This means rising and falling edges are delayed by time equal to one period of sample rate.

I have observed that the feature almost works as described with the difference, that the

minimum delay TXANT_PRE = 0 switches on almost 10usec before TX begins and
TXANT_POST = 0 switches of approx 10 usec before of TX.

If I now try to use TXANT_PRE = 33, which is trunc(10e-6*samp_rate) in my case I can see a small variation between startups, i.e. the delay appears to be later or earlier by about 200nsec.
For the intended use case, PA switching, I believe this behaviour will pose no problems. However, I just wanted to report my findings.


Add support for Python 3.11.8 and 3.12.2

Release notes:
https://www.python.org/downloads/release/python-3118/
https://www.python.org/downloads/release/python-3122/
Binary builds:
https://github.com/heroku/heroku-buildpack-python/actions/runs/7812574422
https://github.com/heroku/heroku-buildpack-python/actions/runs/7812572989
GUS-W-14846638.
GUS-W-14846690.

Updated versions on:
https://devcenter.heroku.com/articles/python-support#specifying-a-python-version
https://devcenter.heroku.com/articles/python-runtimes#selecting-a-runtime
Published changelog entry:
https://devcenter.heroku.com/changelog-items/2799


"Sticky" vertex in Merge operation

I am trying to merge two adjacent vertices, and it seems that the second selection isn't recognizing the clicked vertex.
I'm working in the SW United States, selecting one vertex:

and trying to merge with its neighbor to the north:

but when I click the neighboring vertex, the merge is done with a far-away vertex:

There seems to be something special about this second vertex, as it is the one that is selected regardless of where I try to complete the merge.

Should be resolved in the latest version


Adding Payment lookup to Allocation object

Critical Changes
Changes

Adding Payment lookup field to Allocation object, which attributes allocations to a Payment and updates to GAU rollup field descriptions.

Issues Closed
New Metadata
Deleted Metadata

@force2b @juliesnow @pedrodalcol Hi all, the requested changes have been made:

Updates to Payment lookup descriptions
Approved updates to GAU Custom rollup descriptions
Updating the corresponding rollup field descriptions on the GAU object

Just let me know if anything else needs changing!

@force2b Thanks for taking the time to work through these changes with us! I just reverted all rollup changes except the descriptions in CRLP_DefaultConfigBuilder.cls
Also, the description for the new Payment lookup field has been approved by @juliesnow

Oh, don't forget to update the changes section in this PR @lparrott  @force2b  and @juliesnow to accurately portray any updates.

This one is ready to merge once the feature tests are done running.

@lparrott @force2b ~ Hey guys, I was just wondering if we had decided who would merge this (one of the tests had failed with CPU limit exceeded, but I'm re-running it). I just want to make sure we don't hit the NPSP merge freeze before getting it in...

Thank you, @force2b!

Hey @juliesnow @force2b @lparrott, sorry I'm late seeing these comments about the release notes. Will this field will be visible to/discoverable by customers? If so, we should mention it in the release notes. We need to be transparent about changes that customers may see to their orgs, even if they're for future features. I recommend we say something like "You may notice a new Payment Lookup field on the Allocations object. This field will be used by a future feature, and can safely be ignored for the time being."  FYI @coriobriensfdo @sam-knox


XInitThreads

The ImageJ Launcher calls XInitThreads on Linux when not in headless mode, so that 3D graphics libraries like Vulkan work as needed:
#ifdef __linux__
  void (*xinit_threads_reference)();
  ...
  // This call is neccessary on Linux to avoid X11 errors when using
  // various 3D graphics APIs like Vulkan or OpenGL.
  if (!headless) {
    void *libX11Handle = dlopen("libX11.so", RTLD_LAZY);
    if(libX11Handle != NULL) {
      debug("Running XInitThreads\n");
      xinit_threads_reference = dlsym(libX11Handle, "XInitThreads");

      if(xinit_threads_reference != NULL) {
        xinit_threads_reference();
      } else {
        error("Could not find XInitThreads in X11 library: %s\n", dlerror());
      }
    } else {
      error("Could not find X11 library, not running XInitThreads.\n");
    }
  }
#endif

Should Jaunch also do this? Maybe an optional directive? It would be a directive that does not switch the result from LAUNCH to CANCEL.

@kephale Not that I know of. But I know next to nothing about XInitThreads. Why is this even necessary in the first place? What impact does it have to run or not run it? I have no idea.

Yeah, all I know is that you get race conditions if you don't run it. sciview is still being haunted by whatever race conditions are happening on Linux, which can't be just XInitThreads...

#44 brings this one step closer 👍


Make resolveName ignore export specifiers without calling getSymbol

Fixes #3514 in release-1.5.
Export specifiers never put a symbol in scope in a module. Right now, resolveName calls getSymbol on the exports of the module, and if it finds an export specifier, dismisses it and keeps going. The problem is that getSymbol may try to resolveAlias on the export specifier, which would indirectly detect a circular reference if the target of the export specifier is outside the module.
The fix in this PR is to detect if the symbol in resolveName is an export specifier without calling getSymbol. Other than that, this PR is intended to keep the behavior pretty much the same.
This highlights an interesting difference between export modifiers and export specifiers when it comes to declaration merging of ambient external modules. I will open an issue to track this behavior discussion.
Another potential fix is to create two different symbol tables for the exports of external modules, one for loose exports that are put into scope, and one for strict exports that do not. That is a much deeper and invasive change though, and is likely not appropriate for release-1.5.

Opened #3535 to track more general issue of whether export specifiers should contribute to scope.

:+1:


Data After End of Packet is Considered Another Packet

We have been getting random 405 Method Not Allowed errors from an endpoint only when we use a Spring Cloud Gateway based proxy. After very lengthy investigation I could capture the some sample packets and reproduce the behavior. The packets, for a reason beyond my understanding, have additional data after the last \r\n. In Spring Cloud Zuul, the proxy would simply ignore these additional data. Spring Cloud Gateway would send this data in a separate packet. The receiving endpoint would receive this packet and not process it because it doesn't have CRLF at the end. Then, it woul receive the next packet and concatenate it with the previous packet. This would yield something like this "garbagePUT HTTP/1.1...", and this causes the 405 error. Not that the requests do not have a "Content-Length" header.
This also constitutes a security risk and sending corrupted packets can effectively corrupt packets sent by other clients!
Expected Behavior
Either reject or truncate the packet after the last CRLF.
Actual Behavior
The packet is split into two packets.
Steps to Reproduce
Send a packet with data after the last CRLF to Spring Cloud Gateway.
Your Environment
Windows 10 and Ubuntu 18.04
Spring Cloud Gateway 2.1.2
OpenJDK 11.0.3

To be clear, the corrupted data comes from outside gateway correct?
My guess is that this is a consequence of the underlying system being used by gateway and zuul. Zuul didn't do anything specific to combat this and neither does gateway. I'm not sure there's anything I can do to even detect this. A 405 error seems like the proper thing to do in this case.
There might be something in webflux or Reactor Netty that could be done, but I'm not sure.

Let me explain with more details then:
The data comes from one of our clients, it passes through some proxy before reaching our API Gateway. The corrupted data is either coming from the client or from our proxy, we are still testing that. However, we still have this very bad security vulnerability where a packet from Client A that has additional data after the last CRLF in the packet would be added to the packet from Client B. Can you imagine how serious this vulnerability is?
Now regarding Zuul: I didn't make thorough tests yet, but our Zuul based proxy has been online for more than a year getting all kinds of packets and we never had this problem before. I can assume that it is simply truncating the packets since we get any complaint from our client.
As for the 405: it is a random error generated by the endpoint due to appending the remaining split packet to the next one. Let me give you a more detailed example:
Suppose that you have an incoming packet that looks like this:
PUT /service/endpoint HTTP/1.1\r\n
\r\n
garbage
Now obviously, everything after the second \r\n is unwanted. Suppose that after that we receive a valid packet from the same or another client that looks like this
PUT /service/endpoint  HTTP/1.1\r\n
\r\n
The result of this is that Spring Cloud Gateay would generate 3 packets:
1:
PUT /service/endpoint HTTP/1.1\r\n
\r\n
2:
garbage
3:
PUT /service/endpoint  HTTP/1.1\r\n
\r\n
Now the endpoint will receive and process packet 1, then receive the second packet and NOT process it because it does not end with \r\n. When it receives the third packet it would concatenate it with the second packet resulting in a packet that looks like this:
garbagePUT /service/endpoint  HTTP/1.1\r\n
\r\n
Then it would parse the headers of that packet. This would, obviously, produce a 405 error because garbagePUT is not a known HTTP method. However, malicious packets can be crafted to alter the packets of other users in a way that might produce a data leak, DoS, ...etc

Right, like I said before, gateway is a library built on top of webflux and Reactor Netty. These are the things dealing with packets. I'll ask them about it tomorrow. If something is to be done, it will be there.

Having chatted with the reactor team, they agree gateway isn't where anything would change. They may reach out to you via the email on your github profile. If you'd like to be contacted somewhere else, send me an email (on my profile) or a dm on gitter.


Yandex.Maps and many other libraries does not work in version 3!

Version
3.0.0
Reproduction link
https://codesandbox.io/s/patient-dust-2q9bj?file=/src/components/Maps.vue
Steps to reproduce

We connect the library https://yandex.ru/dev/maps/jsapi/doc/2.1/quick-start/index.html/?from=techmapsmain
Add a point to the map
This library (https://vue-yandex-maps.github.io/guide/) and a number of others also stopped working. The release of version 3 messed up a lot.
https://github.com/PNKBizz/vue-yandex-map/issues/275

What is expected?
Point added
What is actually happening?
Numerous errors in the console: https://imgur.com/a/VElaZ4G

Sandbox link 2 version: https://codesandbox.io/s/charming-haibt-06w4x?file=/src/components/Maps.vue:0-1186
Sandbox link version 3: https://codesandbox.io/s/patient-dust-2q9bj?file=/src/components/Maps.vue
We use vue 3 versions for ionic, but due to compatibility problems we cannot finish our projects.

Open the issue on their repository not here

The library has been working for 5 years on all platforms, in all frameworks. View version 3 was updated and half of the libraries broke.

Vue 3 is a major version release. Major versions, by definition, come with breaking changes.
Libraries using Vue need to update to work with the new major version.
You can continue to use Vue 2 until you find that the libraries you need have done that.

Nobody will update their libraries in pure JS because you broke something there. You are losing a very large number of users. We need version 3 of the Vue because of ionic.
If it was a framework-specific library, then it would be a different matter. But this is a regular JS script.

But this is a regular JS script.

I missed that part as you mentioned a vue lib right after.
Took another look. this fixes it:
initializeYandexMap() {
      ymaps.ready(() => {
        const map = new ymaps.Map("yandex-map", {
          center: [55.76, 37.64],
          zoom: 10,
        });
        this. map = markRaw(map)
        this.setMarkers();
      });
    },

Thank you so much! It works!


Polyfill service loads wrong polyfills in IE compatibility view

IE10 in compatibility view behaves as an IE7, but the polyfill service doesn't handle it and serves polyfills for IE10.

Thanks for raising this.  I'd been vaguely aware that it was likely to be a problem.  My only suggested solution at the moment is to do something like:

If that works, let me know and I'll add it to the docs

Thanks Andrew.
The code was not syntactically correct, here is the corrected version:
<!--[if IE ]>
      <script>
        document.write('<'+'script src="//cdn.polyfill.io/v1/polyfill.min.js?ua=ie/'+document.documentMode+'"></'+'script>');
      </script>
    <![endif]-->
    <!--[if !IE]>-->
      <script src="//cdn.polyfill.io/v1/polyfill.min.js"></script>
    <!--<![endif]-->

This is better, in IE9 or IE10 browser mode and IE8 document mode this is working fine.
However, it seems that the polyfills for IE7 are not the best, polyfill itself throws an error:
SCRIPT16385: Not implemented
7, line 3 character 11588
Then the code that uses it:
SCRIPT438: Object doesn't support property or method 'addEventListener'
But that could be considered another issue regarding polyfills for IE7.

If there's a bug in a polyfill, please do raise that as a separate issue.
If the conditional comments are version specific, do they act on the document mode, or the real browser version?  If they act on the document mode, you can make a slightly better solution that doesn't use document.write by doing something like this (note that when I say 'something like' I am not guaranteeing syntactically correct code):
<!--[if IE 7 ]><script src="//cdn.polyfill.io/v1/polyfill.min.js?ua=ie/7"></script><![endif]-->
<!--[if IE 8 ]><script src="//cdn.polyfill.io/v1/polyfill.min.js?ua=ie/8"></script><![endif]-->
<!--[if IE 9 ]><script src="//cdn.polyfill.io/v1/polyfill.min.js?ua=ie/9"></script><![endif]-->
<!--[if IE 10 ]><script src="//cdn.polyfill.io/v1/polyfill.min.js?ua=ie/10"></script><![endif]-->
<!--[if IE 11 ]><script src="//cdn.polyfill.io/v1/polyfill.min.js?ua=ie/11"></script><![endif]-->
<!--[if !IE]>--><script src="//cdn.polyfill.io/v1/polyfill.min.js"></script><!--<![endif]-->

The current solution works fine, maybe I give it a try to the last one as well.
I corrected the syntax just because you said you would add it to the documentation, and I just wanted to help not to add an incorrect code by mistake :)

I've done some research here and found that in compatibility mode IE actually modifies it's user agent string.  I can't find any scenario in which the solutions above are necessary.  @roland-vachter can you provide a test case?

Yes, that's try, IE modifies the user agent to IE7. Still, I think polyfill service does not handle it as an IE7. I will double check again, but that's what I observed.

It seems it recognizes IE7 and the polyfill is served for IE7, probably it's not working due to the other issue that IE7 polyfill is not the best so far .. So I think this can be closed.


Adding development doesn't carry over port

// server.js
app.use(sslRedirect(['development', 'production'], 301))
`

I'm getting redirected from `localhost:3000` to `https://localhost/`, instead of `https://localhost:3000`

This module work on heroku dynos.
Please not use con localhost.


Parsing individual title

Take a GEDCOM with this individual:
0 @I1@ INDI
1 NAME Victoria /Hanover/
1 TITL Queen of England

ModelParser.handleTitl(Object) puts the TITL record within names adding the user-defined _type key:
{
  "id": "I1",
  "names": [
    {
      "value": "Victoria /Hanover/"
    },
    {
      "_type": "TITL",
      "value": "Queen of England"
    }
  ]
}

This is strange, because in GEDCOM 5.5 specifications TITL is a standard attribute of INDI (like for example OCCU or PROP):
INDIVIDUAL:=
n  <<NAME_STRUCTURE>>		{1:M}
n  TITL <INDI_TITLE>		{0:M}
n  ...

And also in GEDCOM 5.5.1 TITL is located among other standard attributes:
INDIVIDUAL_ATTRIBUTE_STRUCTURE:=
  [
  n ...
  |
  n TITL <NOBILITY_TYPE_TITLE>		{1:1}
    +1 <<INDIVIDUAL_EVENT_DETAIL>>	{0:1}
  ]

Wouldn't be more correct to parse the TITL record as a simple EventFact? Like this:
{
  "id": "I1",
  "names": [
    {
      "value": "Victoria /Hanover/"
    }
  ]
  "eventsFacts": [
    {
      "tag": "TITL",
      "value": "Queen of England"
    }
  ]
}

Fair enough. I'm happy to merge a pull request.