Cache function not working - No ID to convert to TMDb ID

I have a problem when running the script. For every movie i get the error that there is no ID to convert to TMDb:
| Cache | ! | plex://movie/5d9f356d06d220001feb5561          | No ID to convert to TMDb ID for Nowhere Boy | | Cache | ! | plex://movie/5d776a62f617c9002016c73f          | No ID to convert to TMDb ID for The Nut Job | | Cache | ! | plex://movie/5d9f3d15d5fd3f001ee1fb53          | No ID to convert to TMDb ID for Oasis: Supersonic | | Cache | ! | plex://movie/5d7768b96f6af7001ee5bc7f          | No ID to convert to TMDb ID for Oblivion | | Cache | ! | plex://movie/5d9f3d02adeb7a0021cea10d          | No ID to convert to TMDb ID for Oceans Eight | | Cache | ! | plex://movie/5d9f3504e4fc29001eb65755          | No ID to convert to TMDb ID for October Sky | | Cache | ! | plex://movie/5d776c36ad5437001f7b7272          | No ID to convert to TMDb ID for Official Secrets | | Cache | ! | plex://movie/5d776c9dad5437001f7c3a8a          | No ID to convert to TMDb ID for Oklahoma City | | Cache | ! | plex://movie/5d7768373c3c2a001fbcea01          | No ID to convert to TMDb ID for Old School |
I'm quite sure that all those movies exist and that they are properly indexed in plex. As every movie can't be cached, it makes every run very slow. It takes hours for the initial scan to be done and when i run the script again it repeats this process as it does not make use of the cache.
My settings are as follows:
settings:                                       # Can be individually specified per library as well   cache: true   cache_expiration: 60   asset_directory: config/assets   asset_folders: true   assets_for_all: false   sync_mode: sync   show_unmanaged: true   show_filtered: false   show_missing: true   save_missing: true   run_again_delay: 2

you need to refresh the metadata on your items or update your server and then refresh. Plex originally didn't include external IDs (like TMDb or IMDb) with their output from your library so you either haven't refreshed since you've updated or haven't updated yet. without one of those external IDs PMM has no idea what you movie it

Ah thank you, I’ll try that first then.
I am using the new media agent but maybe it did not scan all of the older movies.

it should have scanned everything fine if they're showing up but they have incorrect metadata. start with a refresh all metadata and try again. If you're still getting errors let me know

It's even stranger. I updated all the metadata information and the first time that i ran it, it started to add the movies to a the cache with 2 Id's in the terminal.
When i ran it today, it's giving me the same output as last time. So the problem can't be in the metadata. It is also strange that it would scan everything again as it should already be in the cache.

can you try again with v1.9.0 and then send me the resulting meta.log file

im trying it again now with v1.9.1. The cache functions seems to be a lot faster when initializing. But i have a lot of movies so i hope that it will be done in 3 hours. Then i'll send the meta.log file and report if the cache function is fast the second time.

A lot of movies still don't match but the runtime is 18 minutes now, which is fine!
https://drive.google.com/file/d/16EDlR6bje2Vf5lRWpaj_lazT4vbOiL_E/view?usp=sharing

what version of PMS are you using?

so are you still having the No ID to convert to TMDb ID issue?

i'll try the newest version now. I still have the No ID to convert to TMDb ID in i think 5% of all movies in version 1.9.1 but this may also be an issue with the obscurity of the movies itself.

I have now run it with version 1.10 and it is amazingly faster. Almost all the movies that were not added to the cache have been added and even accounting for the fact that it had to add a lot of movies to the cache, it still finished faster.
Version 1.9.1 finished in 0:12:03
version 1.10 on the first run finished in 0:03:16
Version 1.10 on the second run finished in 0:01:32, with most of the time being spend waiting for the movie library to load - not sure what it does there or why it has to wait

awesome glad its all working again! Im going to close this for now If you have any further issue feel free to reopen or make a new issue.
it has always waited for the library to load i just didnt have the message before. the plex api only loads 100 items per call so what its doing there is loading your whole library into an array.


OS not supported - Windows

Hi,
When I try to run :Glow it won't run for me, it only says "OS not supported"
My config:

nvim version:

> nvim --version
NVIM v0.7.2
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Features: -acl +iconv +tui

Windows 10 Home 21H1 19043.2130
:lua print(vim.loop.os_uname().sysname) = "Windows_NT"
:lua vim.pretty_print(jit.os) = "Windows"
I use packer.nvim and this is my init.lua

use {"ellisonleao/glow.nvim"}

require("glow").setup({})

I also saw the other issue #82, but it still doesn't work

same issue

Chiming in to also echo, same issue!

The auto-install of the glow.exe doesn't work on windows yet (uses tar/curl commands) so for now you'll probably want to download glow somewhere and add it to your $PATH. With scoop, scoop install glow does that for you.


404 not found error occurs when adding documents to an API, and the page breaks when refreshing the document page

Description
Description:
404 error occurs when user trying to add document to an API and page breaks when refreshing document page.

Steps to Reproduce

Login to publisher portal
Create an API
Navigate to Documents tab -> Add New document\
Add document details and click on 'Add document' button (document is not saved)
Refresh the document page

Affected Component
APIM
Version
4.3.0
Environment Details (with versions)
No response
Relevant Log Output
Console logs

Add Document

react-dom.production.min.js:106 Uncaught TypeError: f.addDocument is not a function
at onClick (Create.jsx:118:47)
at Object.je (react-dom.production.min.js:54:317)
at He (react-dom.production.min.js:54:471)
at react-dom.production.min.js:55:35

Refresh Page

react-dom.production.min.js:189 TypeError: Cannot read properties of null (reading 'docVisibilityEnabled')

Related Issues
No response
Suggested Labels
No response

Closing as the fix is merged.


feat(carousel): improve server env checking and coverage

Coverage increased (+2.6%) to 78.0% when pulling 3243c8880ab5eeb5f12abac023e4162f884c72dc on feat/increase_code_coverage into 2ef7a8f71706e735735fea91d02fee7dff208886 on master.


Unexpected JSON end

Just updated to latest version and now I get this error:
SyntaxError: Unexpected end of JSON input
    at Object.parse (native)
    at ChildProcess.<anonymous> (/Users/jontedejong/.atom/packages/atom-autocomplete-php/lib/services/php-proxy.coffee:83:52)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:852:16)
    at Socket.<anonymous> (internal/child_process.js:323:11)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at Pipe._handle.close [as _onclose] (net.js:492:12)

I tried updating Atom too to 1.12.3 but no dice.

Same problem...

#303 Same problem...

Hello,
Should be fixed.


Make PlayerUseItemOnBlockEvent.getBlockFace() return a BlockFace

Currently PlayerUseItemOnBlockEvent.getBlockFace() returns a Direction instead of a BlockFace. Since there's a BlockFace.toDirection() method you can easily convert a BlockFace back to a Direction if you really need to, however there's no such easy way of getting a BlockFace from a Direction.

Oops


Should the tls option receive a boolean

I have seen examples online where the tls connection option can be a boolean.
Should this be added to the type of tls if that's the case?

I was running into this question as well. For context, it just needs to be a truthy value, so an empty object {} works, and is a valid type-match if you are using typescript.

I was running into this question as well. For context, it just needs to be a truthy value, so an empty object {} works, and is a valid type-match if you are using typescript.

Sorry for the late response! Although any truthy values work, strickly it should be an object of options used to create a secure context. So I'd suggest if the default options work for you and you just want to enable tls, {} should be used.


Move detection of hardware from onCreate to onResume

...otherwise we'll never know if bluetooth got enabled while paused.

@nomwerp would you like to become a contributor to this project?

sure, for now I'm just interested in doing small improvements to make this project more usable for myself. will discuss anything more drastic with yourself first.

You're given it more time than I do so.. :-) thanks a lot!


gallery

pics differentiated according to events

Apply a related image for every event on the main page of gallery, instead of using the same for all

Component vise distribution
|
+--Header
|
+--Gallery (Event wise gallery card)
|    |
|    +--Open source
|    |
|    +--Metamorphosis ....
|
+-- Footer

** Apply a related image for every event on the main page of gallery, instead of using the same for all .

Yes seperate page will be good for each event and only one image on main gallery page.

@Palak-shravagi Assign kela nahi ka?

abhi krti hu assign


Dipping preview spinner

I think the preview spinner rocks up and down by a pixel and / or has a sheared edge on a small section of the circumference. Here's a screen capture, which has been accidentally but conveniently slowed down in some part of the capture / gif conversion process:

See https://gfycat.com/RevolvingFondCommabutterfly for a full-speed capture.

There's a definite wobble. It's most clear if you have the stylesheet module installed at navigate to /admin/styleguide/#icons

I believe the cause of this is that the loading icon appears to be a character inside a text box, and due to the character not being perfectly centered within the text box it is wobbling as the text box rotates. A possible (hopefully not too difficult) fix could be to replace the text box with an actual image like this:

This way there will be no wobble as the image itself can be rotated.

No longer relevant, the admin preview has no preview spinner since #3383 was merged.


HassIO  install stops at “udevd[9]: starting eudev-3.2.7”

Home Assistant release with the issue:

Raspberry Pi 2 B Hassio image
Operating environment (HassOS/Generic):

HassOS
Supervisor logs:

NA
Description of problem:
I try install HassIO on my RPi2. I have downloaded the latest image file (hassos_rpi2-2.11.img.gz) for RPi2, I copied it to a 32Gb microSD card with Balena Etcher. After successful flashing I insert the card into my RPi, it starts up the boot process and then it stops at: “udevd[9]: starting eudev-3.2.7”
I am trying to install Hass.IO since yesterday, I have flashed the SD card several times, I tried adding “my-network” file with LAN or WIFI connections, but nothing helps.
I have LAN connection on my RPi.
I can see my RPi in my router's device list, but I cannot access http://hassio.local:8123 nor http://RPi_IP_ADD:8123
Does anyone have a solution for this?

Login into your device as "root" and on CLI enter login. After that use ip addr show to confirm the IP Address.

Can you detail your answer a little bit. I am a newbie in this. What do you mean by "Login into your device as "root" and on CLI enter login"? After the installation stops at eudev-3.2.7 I try to reach my RPi with Putty on the IP address which I see in my router for the Hassio, but when I try to connect to it I get an error message that: Network error. Connection refused. If I try to ping the IP address everything works fine.
What should I do now?

@pvizeli Could you be so kind to reply to my questions above?
Thank you for your support.

@KixMan28 you can connect a keyboard and monitor directly to your pi and login as described. You hit enter and then you use root with no password to get to the Hassio CLI. From there you enter "login" to continue to the host os. From there you can use ip addr show

@cogneato Thank you for your explanation. It works now.

@cogneato Thank you for your explanation. It works now.

How did you resolve the issue? I have the same problem; Hass.io hangs during install. Specifically after eudev 3.2.7

Hi @mach77777
After several restarts I have left my RPi running all night. In the morning I saw that I have a different message on the display. I connected a keyboard to my RPi and I tried to scroll back, but I saw only strange characters, then I pressed Enter and I typed what pvizeli recommended and it worked, so honestly I don't know what solved the issue.
I have re-imaged my MicroSD card several times. Last time I did it with Rufus.
Maybe the solution is to wait a little bit longer (maybe 20-30 minutes) after you have the eudev message. I have installed Hass.io in the past and that time after several lines of installation messages on the display at a certain moment in time it switched to a white screen with the blue HA logo. All YouTube videos showed this screen. It looks like the newer HA versions don't have this white screen, but only the texts on the display.
I haven't find anywhere information related to this and also no other information about what else I should do once i have the eudev message on my display.
I hope I could help you. Let me know how it works for you.

starting eudev-3.2.7 is the last thing the console SHOULD say.
You need to go to a browser on a PC or whatever and start there.
Warning the instruction to enter the url hassio.local:8123 did not work for me. I had to find its IP and use that eg... <IP_ADDRESS>:8123

@KixMan28 That screen shown in youtube videos is from the browser, not from the console you get when you attach a monitor to the HDMI.
HassOS is designed to run headless (without a monitor).


Blank screen after login

After logging in via xrdp i get a blank screen and nothing happens. Journalctl -xe gives the error "Listening socket is in wrong state, terminating listener".

You should at least mention about xrdp version, client what you use,  where your xrdp obtained from.

Im using xrdp 0.9.1-7build1 on ubuntu 17.04 and downloaded xrdp with apt.
xrdp.log
[20170728-13:33:36] [INFO ] A connection received from: ::ffff:<IP_ADDRESS> port 2091 [20170728-13:33:36] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:<IP_ADDRESS> port 3389) [20170728-13:33:36] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389) [20170728-13:33:37] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem [20170728-13:33:37] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem [20170728-13:33:37] [DEBUG] Security layer: requested 11, selected 0 [20170728-13:33:37] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:<IP_ADDRESS> port 3389) [20170728-13:33:37] [ERROR] Listening socket is in wrong state, terminating listener [20170728-13:33:37] [INFO ] A connection received from: ::ffff:<IP_ADDRESS> port 2092 [20170728-13:33:37] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:<IP_ADDRESS> port 3389) [20170728-13:33:37] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389) [20170728-13:33:37] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem [20170728-13:33:37] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem [20170728-13:33:37] [DEBUG] Security layer: requested 0, selected 0 [20170728-13:33:38] [DEBUG] xrdp_00000647_wm_login_mode_event_00000001 [20170728-13:33:38] [INFO ] Loading keymap file /etc/xrdp/km-00000407.ini [20170728-13:33:38] [WARN ] local keymap file for 0x00000407 found and doesn't match built in keymap, using local keymap file [20170728-13:33:38] [DEBUG] Closed socket 17 (AF_UNIX) [20170728-13:33:42] [DEBUG] Closed socket 17 (AF_UNIX) [20170728-13:33:44] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip <IP_ADDRESS> port 3350 [20170728-13:33:45] [INFO ] xrdp_wm_log_msg: sesman connect ok [20170728-13:33:45] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait... [20170728-13:33:45] [DEBUG] return value from xrdp_mm_connect 0 [20170728-13:33:45] [INFO ] xrdp_wm_log_msg: login successful for display 10 [20170728-13:33:45] [DEBUG] xrdp_wm_log_msg: started connecting [20170728-13:33:45] [DEBUG] Closed socket 17 (AF_UNIX) [20170728-13:33:49] [DEBUG] Closed socket 17 (AF_UNIX) [20170728-13:33:49] [DEBUG] Closed socket 17 (AF_UNIX) [20170728-13:33:52] [DEBUG] Closed socket 17 (AF_UNIX) [20170728-13:33:53] [DEBUG] Closed socket 17 (AF_UNIX) [20170728-13:33:56] [DEBUG] Closed socket 17 (AF_UNIX) [20170728-13:33:56] [DEBUG] Closed socket 17 (AF_UNIX) [20170728-13:33:59] [DEBUG] Closed socket 17 (AF_UNIX) [20170728-13:34:00] [DEBUG] Closed socket 17 (AF_UNIX) [20170728-13:34:03] [DEBUG] Closed socket 17 (AF_UNIX) [20170728-13:34:03] [DEBUG] Closed socket 17 (AF_UNIX) [20170728-13:34:06] [DEBUG] Closed socket 17 (AF_UNIX) [20170728-13:34:07] [DEBUG] Closed socket 17 (AF_UNIX) [20170728-13:34:10] [DEBUG] xrdp_wm_log_msg: connection problem, giving up [20170728-13:34:10] [DEBUG] Closed socket 17 (AF_UNIX) [20170728-13:34:10] [DEBUG] xrdp_wm_log_msg: some problem [20170728-13:34:10] [DEBUG] xrdp_mm_module_cleanup [20170728-13:34:10] [DEBUG] Closed socket 16 (AF_INET6 ::1 port 59238) [20170728-13:34:10] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:<IP_ADDRESS> port 3389) [20170728-13:34:10] [DEBUG] Closed socket 17 (AF_UNIX) [20170728-13:34:10] [DEBUG] xrdp_mm_module_cleanup [20170728-13:34:10] [ERROR] Listening socket is in wrong state, terminating listener [20170728-13:34:14] [DEBUG] Closed socket 17 (AF_UNIX) [20170728-13:34:17] [DEBUG] Closed socket 17 (AF_UNIX)
xrdp-sesman.log
[20170728-13:33:44] [INFO ] A connection received from ::1 port 59262 [20170728-13:33:45] [INFO ] ++ created session (access granted): username server, ip <IP_ADDRESS>:2092 - socket: 12 [20170728-13:33:45] [INFO ] starting Xorg session... [20170728-13:33:45] [DEBUG] Closed socket 9 (AF_INET6 :: port 5910) [20170728-13:33:45] [DEBUG] Closed socket 9 (AF_INET6 :: port 6010) [20170728-13:33:45] [DEBUG] Closed socket 9 (AF_INET6 :: port 6210) [20170728-13:33:45] [DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350) [20170728-13:33:45] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350) [20170728-13:33:45] [INFO ] Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp   [20170728-13:33:55] [ERROR] X server for display 10 startup timeout [20170728-13:33:55] [INFO ] starting xrdp-sessvc - xpid=1611 - wmpid=1610 [20170728-13:33:55] [ERROR] X server for display 10 startup timeout [20170728-13:33:55] [ERROR] another Xserver might already be active on display 10 - see log [20170728-13:33:55] [DEBUG] aborting connection... [20170728-13:33:55] [INFO ] ++ terminated session:  username server, display :10.0, session_pid 1609, ip <IP_ADDRESS>:2092 - socket: 12

Im using xrdp 0.9.1-7build1 on ubuntu 17.04 and downloaded xrdp with apt.
xrdp.log

[20170728-13:33:36] [INFO ] A connection received from: ::ffff:<IP_ADDRESS> port 2091
[20170728-13:33:36] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:<IP_ADDRESS> port 3389)
[20170728-13:33:36] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20170728-13:33:37] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20170728-13:33:37] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20170728-13:33:37] [DEBUG] Security layer: requested 11, selected 0
[20170728-13:33:37] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:<IP_ADDRESS> port 3389)
[20170728-13:33:37] [ERROR] Listening socket is in wrong state, terminating listener
[20170728-13:33:37] [INFO ] A connection received from: ::ffff:<IP_ADDRESS> port 2092
[20170728-13:33:37] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:<IP_ADDRESS> port 3389)
[20170728-13:33:37] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20170728-13:33:37] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20170728-13:33:37] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20170728-13:33:37] [DEBUG] Security layer: requested 0, selected 0
[20170728-13:33:38] [DEBUG] xrdp_00000647_wm_login_mode_event_00000001
[20170728-13:33:38] [INFO ] Loading keymap file /etc/xrdp/km-00000407.ini
[20170728-13:33:38] [WARN ] local keymap file for 0x00000407 found and doesn't match built in keymap, using local keymap file
[20170728-13:33:38] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:33:42] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:33:44] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip <IP_ADDRESS> port 3350
[20170728-13:33:45] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20170728-13:33:45] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait...
[20170728-13:33:45] [DEBUG] return value from xrdp_mm_connect 0
[20170728-13:33:45] [INFO ] xrdp_wm_log_msg: login successful for display 10
[20170728-13:33:45] [DEBUG] xrdp_wm_log_msg: started connecting
[20170728-13:33:45] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:33:49] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:33:49] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:33:52] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:33:53] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:33:56] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:33:56] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:33:59] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:34:00] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:34:03] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:34:03] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:34:06] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:34:07] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:34:10] [DEBUG] xrdp_wm_log_msg: connection problem, giving up
[20170728-13:34:10] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:34:10] [DEBUG] xrdp_wm_log_msg: some problem
[20170728-13:34:10] [DEBUG] xrdp_mm_module_cleanup
[20170728-13:34:10] [DEBUG] Closed socket 16 (AF_INET6 ::1 port 59238)
[20170728-13:34:10] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:<IP_ADDRESS> port 3389)
[20170728-13:34:10] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:34:10] [DEBUG] xrdp_mm_module_cleanup
[20170728-13:34:10] [ERROR] Listening socket is in wrong state, terminating listener
[20170728-13:34:14] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:34:17] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:34:21] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:34:24] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:34:28] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:34:31] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:34:35] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:34:38] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:34:42] [DEBUG] Closed socket 17 (AF_UNIX)
[20170728-13:36:14] [DEBUG] Closed socket 17 (AF_UNIX)

xrdp-sesman.log

[20170728-13:33:44] [INFO ] A connection received from ::1 port 59262
[20170728-13:33:45] [INFO ] ++ created session (access granted): username server, ip <IP_ADDRESS>:2092 - socket: 12
[20170728-13:33:45] [INFO ] starting Xorg session...
[20170728-13:33:45] [DEBUG] Closed socket 9 (AF_INET6 :: port 5910)
[20170728-13:33:45] [DEBUG] Closed socket 9 (AF_INET6 :: port 6010)
[20170728-13:33:45] [DEBUG] Closed socket 9 (AF_INET6 :: port 6210)
[20170728-13:33:45] [DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350)
[20170728-13:33:45] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)
[20170728-13:33:45] [INFO ] Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp
[20170728-13:33:55] [ERROR] X server for display 10 startup timeout
[20170728-13:33:55] [INFO ] starting xrdp-sessvc - xpid=1611 - wmpid=1610
[20170728-13:33:55] [ERROR] X server for display 10 startup timeout
[20170728-13:33:55] [ERROR] another Xserver might already be active on display 10 - see log
[20170728-13:33:55] [DEBUG] aborting connection...
[20170728-13:33:55] [INFO ] ++ terminated session:  username server, display :10.0, session_pid 1609, ip <IP_ADDRESS>:2092 - socket: 12

Did you read /usr/share/doc/xrdp/README.Debian? Follow instructions written in the file.

In this case, README.Debian doesn't solve the issue. Please forget it.

I have a similar problem after updating to Debian 9. Please help me.

Xorg is properly started but terminated immediately. startwm.sh needs to be adjusted.

No feedback from the reporter, closing. Maybe startwm.sh needs to be adjusted.
When you're back, please leave a comment. I'll reopen this.

Problem solved with latest beta / release candidate.


[Review] Feature/pwa

Looks cool but much left to be done (code climate, test coverage, etc)

Ok, maybe I've missed something, but what's this all about? Is there an earlier PR which contains much more documentation?

This PR creates a cloud service configuration that could be applied to a site or context under /conf.  Creating the configuration includes filling out details needed for creating the Service Worker(SW) and the manifest file along with the few other details like what paths/patterns of the url to cache and uncache.
The manifest configuration details helps making the site function like a native mobile app allowing to add the site as a shortcut to the device homescreen.
The SW acts a a proxy to every request and starts caching the response on the browser. So the next time a request is made for the same url, the response is served from the cache in the browser.
The manifest details are loaded as part of the header of the site through a manifest servlet and the pwa-clientlib loads at the footer.
The pwa-clientlibs makes a servlet call to know whether it should and under what location of the site it should create the SW. Whenerver there is a new content available at the server side, the cache version is checked from the cloud service configuration and the browser cache is updated. The cache busting is implemented using IndexedDb.

Closing for @avitripathy01 can re-open as his

some screenshots or video recording please....


Amend Product Search Catalog

Amend the Product--SearchCatalog-SubCatalog_and_Inventory per discussion between John, Nick and Jason.

@jtprince requested changes ... see how easy and reasonable we are 😄


Handle InvalidWheel for metadata backfill

Fixes https://python-software-foundation.sentry.io/issues/5002343865/.

For once this is done, it might be an interesting blog post to look at the unbackfillable as a "here's some weird stuff that we've accumulated over 20 years of existence"


Custom editor undo/redo not working on Linux

@mjbvz Hi! I'm working along with @tiagobento integrating the new Custom Webview Editor API in our editors.
I've been focused on integrating the Undo/Redo on our editor state control API. I managed to succesfully propagate each change that happens on our editor by generating an edit and firing the onDidChange event on our CustomEditorEditingCapability, however I found two issues when trying to execute the Undo/Redo from VSCode.
The first issue is that Undo/Redo menu actions under Edit menu are not working. Clicking them isn't notifying our CustomEditorEditingCapability to execute the undoEdits/applyEdits methods. However the key shortcuts (Ctrl+Z / Ctrl+Y) seem to work, and our capability is able to execute the undoEdits/applyEdits methods.
Second one only happens when running VSCode on Linux. Looks like if two or more changes happen on the editor and I execute the Undo/Redo key shortcut the undo's/redo's are executed twice. For example if we make two changes on the editor that generate two separate edits (edit1 and edit2). If later I try to undo last change (edit2), our capability undoEdits method is executed twice, first time for edit2 and then for edit1. As I said, the same error happens with Redo. We tried this on different computers (Fedora, Ubuntu, Mac & Windows) and it seems to be present only Linux ones. I attached some gifs showing the error on different systems.

Wrong behaviour (Fedora): undoing two edits at same time

Correct behaviour (Mac): undoing only a single edit each time

Correct behaviour (Windows): undoing only a single edit each time
Originally posted by @pefernan in https://github.com/microsoft/vscode/issues/77131#issuecomment-594493351

@mjbvz just some more info that may help you. Looks like same issue is also happening on the current extension api's (not the proposed).
I think that the issue is that while pressing Ctrl+Z on webviews it triggers the undo faster than on text editor, so not necessarily two times. In a normal "press" it executes twice the udno while on a text editor it executes only one time. If we keep the Ctrl+Z pressed to undo multiple changes happens exactly the same, on webviews it triggers the undo more times.

Thanks for testing this!
The edit-> undo menus not working is a known issue: #90110. We're looking into it but may not get around to in April
The duplicate undo/redo has the same root cause as #82670. Should be fixed in the next insiders build. Let me know if you still see the duplicate commands once the next VS Code insiders


Improve to_array

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (700bb72) to head (aa00817).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #261   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           91        91
  Lines         2225      2227    +2
  Branches       201       202    +1
=========================================
+ Hits          2225      2227    +2

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


End of the interpolated curves are giving a lot of very similar values.

I'm trying to do route transition using the TransitionMotion. One issue I am having is that the transition seems to end forever. By that I mean that there is a very long moment where the modal has moved up completely but stays blank because I wait until the animation is complete until rendering the content. This ensures that the modal doesn't frame.
The curves have a lot of points in their endings at very low velocity (see graph below). This takes like half of the "animation time". (Basically 500ms of animation and then 500 ms of being "almost static", but still rendering a lot...). I tried changing stiffness, damping, precision, but it seems to always give me about the same length of 950ms in my case.
See the values near the end. Basically a lot of points are between target and target - 1, which doesn't provide much difference.
const ANIMATE_STYLE = { offset: spring(0, { stiffness: 210, damping: 26, precision: 0.01 }) };

.

Is there a way I can get the current target & current val (I seem to get only currentVal in getStyles and only current Target in willLeave)? This way I could tell the current style to "stop" interpolating (eg: if target is 0 and we're at < 0.3, I could pass a flat 0 instead of a spring). Same for exit if I get the target & the value, then if the value is close enough I could pass a flat value instead of a spring to have it exit earlier.
By enabling early exit, I could then use the getStyle to provide a flat value since the number of elements in "oldStyles" when from 2 to 1 for example. Allowing for quicker "entry" also.
const leavingStyle = willLeave(oldMergedPropsStyle, oldCurrentStyles[oldIndex]);

Or maybe is there an issue with velocity? Should it be stopping earlier? The end of the graph delta seems to be under precision of 0.01. Should I be using a much lower precision?

Alright, after trying some way higher precision values (than what I thought) for eg: 0.5, it seems to be a lot better when interpolating big values like this. 0.01 seems good for something like 0 to 1, but seems to be a bit off for 0 to 100.  Should we reflect in the doc that bigger interpolations can afford to have way "lower" (eg 0.5) precision values.

Related: #235 #274


Documented embedded navigators in the Navigator class file (#15040).

#15040

nit: move the bug number it fixes into the PR body instead of the title (so github makes it clickable) :)

@xster I added a description of real world nested navigators with the tabbed example we discussed.

LGTM


rootston: add per-seat views

This also allows to prevent some seats from sending input events to some views.
Test plan: with two seats, check that focus semantics and keybindings operate per-seat. This includes: open three views, focus different ones with the seats, focus the same one with both, close the focused view. Expected: the two previous views get focus.
Fixes #424

It's a very good start, but I think we can improve the data structures a bit.
I don't like it how the seat is now a first-class container of views when all we want to do is maintain a focus stack. I think this is an excellent use case for wlr_list. I'm also not thrilled about wrapping the view in roots_seat_view only for the purpose of storing it in a list because it's a conceptually heavy abstraction for that purpose alone.
Here's what I'll suggest:
Keep a wlr_list of views on the seat. When you focus a view for a seat, add it to the front of the list. When the view is destroyed, remove it from the list. The view at the head of the list is the focused view. When the focus of the seat is cleared, set a has_focus bit on the seat to false.
Now abstract getting the focus for a seat into a getter. It returns NULL if the list is empty or has_focus is false or otherwise the head of the list.
What do you think about that?

One drawback is that we loose the destroy listener, making it necessary for the desktop to remove views from all seats when these are destroyed.
But I agree that an array of pointers is better than a wl_list in this case. I've made the change in the last commit.

One drawback is that we loose the destroy listener

Each seat should listen to the destroy signal of the view itself and remove it from the list when that happens.

Where do we store the wl_listener then?

Ready for review!

@acrisci's comments have been addressed.

Focusing a new window for all the seats is going to have some serious usability problems. I wish there was some way to map a new window to a seat.

Would be a bit cumbersome but we might be able to map a window to a seat by looking at its pid/ppid and see if these are related to anything we recognize, and if we find such a view look for seats that has it focused as of the new window spawning?
That'd require keeping tracks of what pid owns every surface though, not sure we want to bother with that -- or actually of how easy that would be. X11 has _NET_WM_PID property, is there something equivalent for wl/xdg shells that'd let us know?

is there something equivalent for wl/xdg shells that'd let us know?

If you can propose any way to get this working with xdg-shell without a new protocol we should consider it, but I think it's going to need a new protocol.

If you can propose any way to get this working with xdg-shell without a new protocol we should consider it, but I think it's going to need a new protocol.
I was looking along for how an xkill replacement would work, but there actually is something standard, found in weston, give or take null checks:

pid_t weston_desktop_surface_get_pid(...) {
  pid_t pid;
...
  struct wl_client *wl_client = ...;
  wl_client_get_credentials(wl_client, &pid, NULL, NULL);
...
  return pid;
}

So, if we want to, we could track the PID of every surface (through this for native wayland and X11 props for xwayland) -- I'm still dubious if it's a good idea to try to associate focus based on PID or PPID though, it was an idea but it'll definitely need some consideration...

👍 looks good


Questions regarding retrying HTTP requests

Based on @ryanjbaxter blog post Retrying HTTP Requests In Spring Cloud Netflix, and my own quest to understand how this works, I've the following questions:

There are load balancing clients in Ribbon general, org.springframework.cloud.netflix.feign.ribbon.LoadBalancerFeignClient, for example, and third-party specific, org.springframework.cloud.netflix.ribbon.okhttp.OkHttpLoadBalancingClient, without any apparent link between them. I'd think that a load balancing Feign client would delegate to one of the third-party specific Ribbon client, like OkHttp, but that doesn't seem to be the case. Can you help me understand the design here?

For retryable load balancing clients, since you're always instantiating the RetryTemplate, the user doesn't have a chance to use all the features of it, like exponential back off, for example. If you looked up one first from the context, users could supply their own RetryTemplate.

It appears that with Hystrix enabled, I can't use Feign Retryer. Hystrix intercepts and throws an exception before the retryer gets it's chance. Is that correct or am I missing something?

What's the Hystrix group key used by a Spring Cloud Feign client, since the @FeignClient annotation doesn't have an attribute to specify it?
Debugging shows the group key is the same as the Feign client name.

What's the Hystrix thread pool name used by a Spring Cloud Feign client, since the @FeignClient annotation doesn't have an attribute to specify it?
Debugging shows the thread pool key is the same as the Feign client name.

There are currently 3 ways HTTP requests can be made in Spring Cloud Netflix.  Feign, Zuul (via a proxy) and LoadBalanced RestTemplates.  I understand your confusion since all 3 use Ribbon so it would seem logical that there would be a common "client" that is used by all.  Unfortunately that is not the case as the moment so there different retryable versions of each as well.  I am not sure of the history as to why there isn't a single client implementation that is used but it might be something to look into in the future.

Yes I agree, this is covered in #1872.

This depends on why Hystrix is intercepting the request.  Might be worth opening a separate issue for this and providing more details (stack trace).

Thanks @ryanjbaxter.
Regarding #1, opened https://github.com/spring-cloud/spring-cloud-netflix/issues/1999
Regarding #3, opened https://github.com/spring-cloud/spring-cloud-netflix/issues/1998


delegate method call in last

Hello,
in your calendar class which delegate method call in last?

Hi @mohsinalimat  I'm not sure what u mean by 'call in last'.

i mean when calendar appear in last?

which FSCalendar delegate mathod call when calendar reload?

I suppose what u mean is
- (void)calendarCurrentPageDidChange:(FSCalendar *)calendar;

when run my project june month show perfect result below tableview but change next month then go to forward to june then in table view show only 3 records

Sorry I still don't know what's your issue is.

I have all records of event in this dictionary self.borderDefaultColors and i want to set up particular month list(mean filter in list) show in tableview but records as per lunar date events

solve my issue with perform selector


Error: Request failed with status 400

Issue scenario:
Am using the below code to trap a release and then send a slack notification and am getting error "Error: Request failed with status 400". The notification works for every other event like deployment created, succeeded etc, except for release published. This used to work, and has broken in the 2 months or so. I strongly believe that this is a GITHUB issue as this error doesnt occur if I create a release manually from github portal. When I create a release from github code shown below, the error from slack .
I will open a case with Git and see how it goes and update here.
  - name: Release Published
    if: github.event_name == 'release' && github.event.action == 'released'
    uses: tokorom/action-slack-incoming-webhook@master
    env:
      INCOMING_WEBHOOK_URL: ${{env.SLACK_CHANNEL_WEBHOOK}}
      TITLE: ":loudspeaker: *<${{github.event.release.html_url}}|${{github.event.repository.name}} ${{github.event.release.tag_name}}>* is ready for verification testing."
      BODY: "*${{github.event.release.name}} Release Notes*\n${{github.event.release.body}}"
      BUTTON: "Open ${{github.event.release.tag_name}}"
      URL: ${{github.event.release.html_url}}
      FOOTER: ":information_source: *<${{ github.event.repository.html_url }}|${{github.event.repository.name}} repository>*"
    with:
      text: "CHAdminTable Production Released"

Code to create the release. This release creation event triggers the above code to send slack notification and fails. If the release is created manually from GIT, the slack notification comes through just fine.
  - shell: pwsh
    name: Get the app version from chart.yml
    run: |
            $RELEASE_NUMBER = (get-content .\charts\Metricon.ClickHome.AdminTables.Web\Chart.yaml| ConvertFrom-Yaml | Select version).version
            Write-Output "::set-env name=RELEASE_NUMBER::$RELEASE_NUMBER"
            $env:ReleaseNotes | out-file releasenotes.txt
  - name: Create Release
    id: create_release
    uses: actions/create-release@v1
    env:
      GITHUB_CONTEXT: ${{ toJson(github) }}
      GITHUB_TOKEN: ${{ env.Password }}
    with:
      tag_name: ${{ env.RELEASE_NUMBER }}
      release_name: ${{ env.RELEASE_NUMBER }}
      body_path: releasenotes.txt
      draft: true
      prerelease: false

#echo "RELEASE_NUMBER=$RELEASE_NUMBER" >> $GITHUB_ENV - this isnt working.
#https://docs.github.com/en/actions/reference/workflow-commands-for-github-actions

@g0pinath
In order to isolate the problem, could you please try to run just one simple job like the one below in your environment and see if sending a message to Slack works?
Replace INCOMING_WEBHOOK_URL with your variables.
When I tried this job in my environment, I received the message CHAdminTable Production Released to Slack.
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
    - name: post a message to slack
      uses: tokorom/action-slack-incoming-webhook@main
      env:
        INCOMING_WEBHOOK_URL: ${{ secrets.INCOMING_WEBHOOK_URL }}
      with:
        text: "CHAdminTable Production Released"

Yup, this action works beautifully, across all repos for other events like
deployment created, failed, PR etc. Even for release, if the release is
created from GITHUB portal, the slack notification comes through.
Somehow the create release action by GIT is causing this action to fail. I
am already working with an engineer from GITHUB and will keep you posted.
On Thu, May 6, 2021 at 7:02 PM tokorom @.***> wrote:

@g0pinath https://github.com/g0pinath
In order to isolate the problem, could you please try to run just one
simple job like the one below in your environment and see if sending a
message to Slack works?
Replace INCOMING_WEBHOOK_URL with your variables.
When I tried this job in my environment, I received the message CHAdminTable
Production Released to Slack.
jobs:
test:
runs-on: ubuntu-latest
steps:
- name: post a message to slack
uses: @.***
env:
INCOMING_WEBHOOK_URL: ${{ secrets.INCOMING_WEBHOOK_URL }}
with:
text: "CHAdminTable Production Released"
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tokorom/action-slack-incoming-webhook/issues/14#issuecomment-833360906,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJTKCPWUH3FZORL4YCYPATLTMJLJRANCNFSM44DU7HNA
.

Thanks for the reply. I understand the situation.
I'm relieved to hear that the action-slack-incoming-webhook itself is working fine!

@g0pinath did you finally solve this issue?
I have the same issue 400 I create the release with Lerna in a Github action then trigger the slack notification, but I always get 400


Upgrade golangci-lint to 1.19.1

Fix whitespace and stylecheck error.
Disable godox.
preparing https://github.com/pion/.goassets/pull/4

Codecov Report

Merging #172 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #172   +/-   ##
=======================================
  Coverage   72.48%   72.48%
=======================================
  Files          60       60
  Lines        3431     3431
=======================================
  Hits         2487     2487
  Misses        652      652
  Partials      292      292

Impacted Files
Coverage Δ

internal/udp/conn.go
82.35% <ø> (ø)
:arrow_up:

conn.go
77.04% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


fix infinite reading  from CLOSE_WAIT socket

CPU usage 100%  issue  was seen on CentOS-7.
"perf top "  output of lighttpd process:
   2.67%  libssl.so.1.0.2k     [.] ssl3_read_bytes
   2.40%  lighttpd             [.] gw_handle_subrequest
   2.33%  [kernel]             [k] sysret_check
   2.31%  [kernel]             [k] tcp_recvmsg
   2.10%  [kernel]             [k] __fget_light
   2.00%  [kernel]             [k] ep_send_events_proc
   1.97%  mod_openssl.so       [.] connection_read_cq_ssl
   1.92%  [kernel]             [k] tcp_poll
   1.85%  lighttpd             [.] connection_set_fdevent_interest
   1.73%  libcrypto.so.1.0.2k  [.] ERR_clear_error
   1.70%  lighttpd             [.] connection_handle_read_post_state
   1.64%  lighttpd             [.] server_main_loop
   1.61%  [kernel]             [k] _raw_spin_lock_irqsave
   1.60%  libcrypto.so.1.0.2k  [.] CRYPTO_lock
   1.49%  libc-2.17.so         [.] __GI___libc_read
   1.47%  [kernel]             [k] select_estimate_accuracy
   1.47%  libssl.so.1.0.2k     [.] ssl3_read_n
   1.38%  [kernel]             [k] _raw_spin_unlock_irqrestore
   1.35%  [kernel]             [k] do_sync_read
   1.31%  [kernel]             [k] selinux_file_permission
   1.30%  [kernel]             [k] ktime_get_ts64
   1.27%  [kernel]             [k] ep_scan_ready_list.isra.7
   1.17%  [kernel]             [k] sys_epoll_wait
   1.12%  lighttpd             [.] server_run_con_queue
   1.10%  lighttpd             [.] fdevent_linux_sysepoll_poll
   1.10%  [kernel]             [k] system_call_after_swapgs
   1.06%  [kernel]             [k] __local_bh_enable_ip
   1.05%  [kernel]             [k] fsnotify
   1.01%  [kernel]             [k] sock_aio_read.part.9
   0.96%  [kernel]             [k] security_file_permission
   0.94%  [kernel]             [k] sys_read
   0.93%  [kernel]             [k] ep_poll
   0.90%  libcrypto.so.1.0.2k  [.] ERR_get_state

only one CLOSE-WAIT  connection was seen at that time:
/ # ss -natp | grep lighttpd
LISTEN     0      512          *:80                       *:*                   users:(("lighttpd",pid=917,fd=6))
LISTEN     0      512    <IP_ADDRESS>:443                  *:*                   users:(("lighttpd",pid=917,fd=5))
LISTEN     0      512    <IP_ADDRESS>:443                  *:*                   users:(("lighttpd",pid=917,fd=4))
CLOSE-WAIT 0      0      <IP_ADDRESS>:443                <IP_ADDRESS>:41200      users:(("lighttpd",pid=917,fd=20))

According to the perf ouptut,   it seems that lighttpd ran into an infinite loop because of CLOSE-WAIT  ssl3 socket.
gw_handle_subrequest
  reqbody_read
    connection_handle_read_post_state
      network_read
        connection_read_cq_ssl
          ssl3_read_bytes

Apologies in advance.  I do not have time to analyze this at the moment, but will the second weekend of Sep.
What version of lighttpd are you using in your tests?
Does this issue occur with lighttpd 1.4.66 using a modern version of openssl? which has not been end-of-lifed?
Your bug report might be an issue in lighttpd.  Independent of that, I am unable to take seriously CentOS 7 using outdated, end-of-lifed openssl 1.0.2 software, which is no longer receiving security patches from openssl.org.  openssl 1.0.2 was end-of-lifed Dec 31, 2019, which is over 2 1/2 years ago.

Are you able to reproduce this on your CentOS-7 system?  Can you describe how?  What kind of HTTP requests and behavior?

Are you able to reproduce this on your CeitntOS-7 system? Can you describe how? What kind of HTTP requests and behavior? I cann't reproduce it, but the issue occured serveal time, every time i need to restart lighttpd to fix it.

What version of lighttpd are you using in your tests?
Does this issue occur with lighttpd 1.4.66 using a modern version of openssl?
(openssl 1.0.2 was end-of-lifed Dec 31, 2019, which is over 2 1/2 years ago.)

Look in the lighttpd error log.  Any useful trace?  If not, try add debug.log-ssl-noise = "enable" to lighttpd.conf, restart lighttpd, and check the error log the next time the issue occurs.
Do you have ssl.read-ahead set in your lighttpd.conf?  Try ssl.read-ahead = "disable" (which is the default)
https://wiki.lighttpd.net/Docs_SSL
Other options: lighttpd supports other TLS modules.  Try mod_gnutls instead of mod_openssl.  https://wiki.lighttpd.net/Docs_SSL

Also, if the situation occurs again, please lighttpd: strace -o strace.log -p <pid> for a second to on what system calls lighttpd is spinning on, and the results of the system calls

Look in the lighttpd error log. Any useful trace? If not, try add debug.log-ssl-noise = "enable" to lighttpd.conf, restart lighttpd, and check the error log the next time the issue occurs.
Do you have ssl.read-ahead set in your lighttpd.conf? Try ssl.read-ahead = "disable" (which is the default) https://wiki.lighttpd.net/Docs_SSL
Other options: lighttpd supports other TLS modules. Try mod_gnutls instead of mod_openssl. https://wiki.lighttpd.net/Docs_SSL

No error was found in logs, and "read-ahead" option is not set.

tcp_recvmsg

I will try "strace" next time. I think the above "perf top -p" ouput  already contains the syscalls . It is clear that  lighttpd is reading the ssl3 socket repeatedly ,  even though the socket is half-closed and there is no data  from remote peer.

@gstrauss ,     I collected more info this time.
perf top -g
===========
- 5.21% server_main_loop
      - 4.06% fdevent_poll
         - 2.49% 0x7faf083ae0e3
            - 2.10% system_call_fastpath
               - 3.78% sys_epoll_wait
                  - 6.69% ep_poll
                     - 5.28% ep_scan_ready_list.isra.7
                        - 2.71% ep_send_events_proc
                           + 2.13% sock_poll
                     + 1.51% select_estimate_accuracy
                       0.99% ktime_get_ts64
           1.30% fdevent_linux_sysepoll_poll
      - 2.00% server_run_con_queue
         - 1.94% connection_state_machine
            - 3.53% connection_state_machine_h1
               - 2.25% connection_state_machine_loop
                  - 3.64% http_response_handler
                     - 4.69% gw_handle_subrequest
                        - 7.96% connection_handle_read_post_state
                           - 3.11% connection_read_cq_ssl
                              + 1.18% chunkqueue_get_memory
                              + 1.08% chunkqueue_use_memory
                 1.43% connection_set_fdevent_interest
         + 1.00% 0x7faf083ae0e3
        1.17% __clock_gettime

perf top
========
   2.56%  libssl.so.1.0.2k     [.] ssl3_read_bytes
   2.07%  lighttpd             [.] gw_handle_subrequest
   2.03%  [kernel]             [k] tcp_recvmsg
   2.01%  [kernel]             [k] sysret_check
   1.90%  [kernel]             [k] tcp_poll
   1.89%  mod_openssl.so       [.] connection_read_cq_ssl
   1.88%  [kernel]             [k] ep_send_events_proc
   1.72%  lighttpd             [.] connection_set_fdevent_interest
   1.61%  lighttpd             [.] connection_handle_read_post_state
   1.59%  [kernel]             [k] __fget_light
   1.58%  libcrypto.so.1.0.2k  [.] ERR_clear_error
   1.47%  libcrypto.so.1.0.2k  [.] CRYPTO_lock
   1.44%  lighttpd             [.] server_main_loop
   1.41%  libssl.so.1.0.2k     [.] ssl3_read_n
   1.39%  [kernel]             [k] _raw_spin_lock_irqsave
   1.38%  [kernel]             [k] _raw_spin_unlock_irqrestore
   1.31%  [kernel]             [k] ktime_get_ts64
   1.23%  [kernel]             [k] system_call_after_swapgs
   1.21%  [kernel]             [k] select_estimate_accuracy
   1.20%  [kernel]             [k] do_sync_read
   1.16%  [kernel]             [k] ep_scan_ready_list.isra.7
   1.15%  libc-2.17.so         [.] __GI___libc_read
   1.13%  [kernel]             [k] __local_bh_enable_ip
   1.02%  [kernel]             [k] inet_recvmsg
   1.02%  [kernel]             [k] selinux_file_permission
   1.01%  [kernel]             [k] sys_epoll_wait
   0.97%  [kernel]             [k] sys_read
   0.97%  [kernel]             [k] sock_aio_read.part.9

logs
====
Aug 21 00:00:01 daemon.err lighttpd[30817]: (mod_openssl.c.3091) SSL: 1 -1 error:1409E0E5:SSL routines:ssl3_write_bytes:ssl handshake failure
Aug 21 00:00:28 daemon.err lighttpd[30817]: (response.c.359) request-size too long: 4194524 -> 413
Aug 21 00:00:37 daemon.err lighttpd[30817]: (response.c.359) request-size too long: 4194524 -> 413
Aug 21 00:00:39 daemon.err lighttpd[30817]: (response.c.359) request-size too long: 4194524 -> 413
Aug 21 01:41:58 daemon.err lighttpd[30817]: (mod_openssl.c.3216) SSL: -1 5 32: Broken pipe
Aug 21 04:09:59 daemon.err lighttpd[30817]: (mod_openssl.c.3091) SSL: 1 -1 error:1409E0E5:SSL routines:ssl3_write_bytes:ssl handshake failure
Aug 21 04:10:04 daemon.err lighttpd[30817]: (mod_openssl.c.3091) SSL: 1 -1 error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown
Aug 21 04:10:04 daemon.err lighttpd[30817]: (mod_openssl.c.3091) SSL: 1 -1 error:1409E0E5:SSL routines:ssl3_write_bytes:ssl handshake failure
Aug 21 06:12:23 daemon.err lighttpd[30817]: (mod_openssl.c.3091) SSL: 1 -1 error:1409E0E5:SSL routines:ssl3_write_bytes:ssl handshake failure
Aug 21 06:52:41 daemon.err lighttpd[30817]: (mod_openssl.c.3091) SSL: 1 -1 error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown
Aug 21 06:52:41 daemon.err lighttpd[30817]: (mod_openssl.c.3091) SSL: 1 -1 error:1409E0E5:SSL routines:ssl3_write_bytes:ssl handshake failure
Aug 21 06:53:40 daemon.err lighttpd[30817]: (mod_openssl.c.3091) SSL: 1 -1 error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown
Aug 21 06:53:40 daemon.err lighttpd[30817]: (mod_openssl.c.3091) SSL: 1 -1 error:1409E0E5:SSL routines:ssl3_write_bytes:ssl handshake failure
Aug 21 07:51:38 daemon.err lighttpd[30817]: (gw_backend.c.530) connect /tmp/php-fastcgi.sock-3: Connection refused
Aug 21 07:52:46 daemon.err lighttpd[30817]: (connections.c.694) oversized request-header -> sending Status 431
Aug 21 09:09:07 daemon.err lighttpd[30817]: (mod_openssl.c.3216) SSL: -1 5 32: Broken pipe
Aug 21 13:05:33 daemon.err lighttpd[30817]: (mod_openssl.c.3091) SSL: 1 -1 error:1409E0E5:SSL routines:ssl3_write_bytes:ssl handshake failure
Aug 21 16:52:00 daemon.err lighttpd[30817]: (mod_openssl.c.3216) SSL: -1 5 32: Broken pipe
Aug 21 17:46:03 daemon.err lighttpd[30817]: (mod_openssl.c.3216) SSL: -1 5 32: Broken pipe
Aug 21 17:46:03 daemon.err lighttpd[30817]: (mod_openssl.c.3216) SSL: -1 5 32: Broken pipe
Aug 21 18:40:25 daemon.err lighttpd[30817]: (connections.c.694) oversized request-header -> sending Status 431
Aug 21 18:40:31 daemon.err lighttpd[30817]: (connections.c.694) oversized request-header -> sending Status 431

* These logs may be useless, because the problem happened at "Aug 21 19:42" *

strace -p 30817
==============

read(29, "", 5)                         = 0
epoll_wait(13, [{EPOLLIN, {u32=28542736, u64=28542736}}], 4097, 1000) = 1
read(29, "", 5)                         = 0
epoll_wait(13, [{EPOLLIN, {u32=28542736, u64=28542736}}], 4097, 1000) = 1
read(29, "", 5)                         = 0
epoll_wait(13, [{EPOLLIN, {u32=28542736, u64=28542736}}], 4097, 1000) = 1
read(29, "", 5)                         = 0
epoll_wait(13, [{EPOLLIN, {u32=28542736, u64=28542736}}], 4097, 1000) = 1
read(29, "", 5)                         = 0
epoll_wait(13, [{EPOLLIN, {u32=28542736, u64=28542736}}], 4097, 1000) = 1
read(29, "", 5)                         = 0
epoll_wait(13, [{EPOLLIN, {u32=28542736, u64=28542736}}], 4097, 1000) = 1
read(29, "", 5)                         = 0
epoll_wait(13, [{EPOLLIN, {u32=28542736, u64=28542736}}], 4097, 1000) = 1
read(29, "", 5)                         = 0
epoll_wait(13, [{EPOLLIN, {u32=28542736, u64=28542736}}], 4097, 1000) = 1
read(29, "", 5)                         = 0
epoll_wait(13, [{EPOLLIN, {u32=28542736, u64=28542736}}], 4097, 1000) = 1
read(29, "", 5)                         = 0
epoll_wait(13, [{EPOLLIN, {u32=28542736, u64=28542736}}], 4097, 1000) = 1
read(29, "", 5)                         = 0
epoll_wait(13, [{EPOLLIN, {u32=28542736, u64=28542736}}], 4097, 1000) = 1
read(29, "", 5)                         = 0
epoll_wait(13, [{EPOLLIN, {u32=28542736, u64=28542736}}], 4097, 1000) = 1
read(29, "", 5)                         = 0
epoll_wait(13, [{EPOLLIN, {u32=28542736, u64=28542736}}], 4097, 1000) = 1
read(29, "", 5)                         = 0
epoll_wait(13, [{EPOLLIN, {u32=28542736, u64=28542736}}], 4097, 1000) = 1
read(29, "", 5)                         = 0
epoll_wait(13, [{EPOLLIN, {u32=28542736, u64=28542736}}], 4097, 1000) = 1
read(29, "", 5)                         = 0
epoll_wait(13, [{EPOLLIN, {u32=28542736, u64=28542736}}], 4097, 1000) = 1
read(29, "", 5)                         = 0
epoll_wait(13, [{EPOLLIN, {u32=28542736, u64=28542736}}], 4097, 1000) = 1
read(29, "", 5)                         = 0
epoll_wait(13, [{EPOLLIN, {u32=28542736, u64=28542736}}], 4097, 1000) = 1
read(29, "", 5)                         = 0
epoll_wait(13, [{EPOLLIN, {u32=28542736, u64=28542736}}], 4097, 1000) = 1
read(29, "", 5)                         = 0
epoll_wait(13, [{EPOLLIN, {u32=28542736, u64=28542736}}], 4097, 1000) = 1
read(29, "", 5)                         = 0
epoll_wait(13, [{EPOLLIN, {u32=28542736, u64=28542736}}], 4097, 1000) = 1
read(29, "", 5)                         = 0
epoll_wait(13, [{EPOLLIN, {u32=28542736, u64=28542736}}], 4097, 1000) = 1
read(29, "", 5)                         = 0
epoll_wait(13, [{EPOLLIN, {u32=28542736, u64=28542736}}], 4097, 1000) = 1
read(29, "", 5)                         = 0
epoll_wait(13, [{EPOLLIN, {u32=28542736, u64=28542736}}], 4097, 1000) = 1

 # ss -natp | grep lighttpd
======================
LISTEN     0      512          *:80                       *:*                   users:(("lighttpd",pid=30817,fd=11))
LISTEN     0      512    <IP_ADDRESS>:443                 *:*                   users:(("lighttpd",pid=30817,fd=8))
CLOSE-WAIT 0      0      <IP_ADDRESS>:443         <IP_ADDRESS>:48724               users:(("lighttpd",pid=30817,fd=28))
CLOSE-WAIT 0      0      <IP_ADDRESS>:443         <IP_ADDRESS>:47026               users:(("lighttpd",pid=30817,fd=29))
CLOSE-WAIT 0      0      <IP_ADDRESS>:443         <IP_ADDRESS>:47000               users:(("lighttpd",pid=30817,fd=21))
CLOSE-WAIT 0      0      <IP_ADDRESS>:443         <IP_ADDRESS>:48730               users:(("lighttpd",pid=30817,fd=30))
CLOSE-WAIT 0      0      <IP_ADDRESS>:443         <IP_ADDRESS>:48716               users:(("lighttpd",pid=30817,fd=27))
CLOSE-WAIT 0      0      <IP_ADDRESS>:443         <IP_ADDRESS>:37966               users:(("lighttpd",pid=30817,fd=23))

The strace shows that lighttpd is not spinning internally, but rather is in a tight loop of testing the file descriptor for readability with epoll(), and then calling read().  Your ancient, outdated, unsupported, end-of-lifed openssl 1.0.2 is the likely culprit for your issue.  You can search through openssl git history for 'close_notify' to find openssl 'close_notify' changes since openssl 1.0.2.
You might try building lighttpd against a manually-built (but not necessarily installed) openssl 1.1.1 or openssl 3.0.0, and then run that with LD_LIBRARY_PATH set so that lighttpd can find the manually-built openssl libs.

Other options: lighttpd supports other TLS modules. Try mod_gnutls instead of mod_openssl. https://wiki.lighttpd.net/Docs_SSL

The strace shows that lighttpd is not spinning internally, but rather is in a tight loop of testing the file descriptor for readability with epoll(), and then calling read(). Your ancient, outdated, unsupported, end-of-lifed openssl 1.0.2 is the likely culprit for your issue. You can search through openssl git history for 'close_notify' to find openssl 'close_notify' changes since openssl 1.0.2.
You might try building lighttpd against a manually-built (but not necessarily installed) openssl 1.1.1 or openssl 3.0.0, and then run that with LD_LIBRARY_PATH set so that lighttpd can find the manually-built openssl libs.

Other options: lighttpd supports other TLS modules. Try mod_gnutls instead of mod_openssl. https://wiki.lighttpd.net/Docs_SSL

Thanks， I have upgrade openssl to 1.1.1 and disable ssl3.  This may solve the problem.  But I still think the upper callers should stop testing or reading the file descriptor after the "connection_read_cq_ssl" function returns -2,   it seems that FDEVENT_RDHUP and close_notify doesn't work as expected.

No code change is needed.

But I still think the upper callers should stop testing or reading the file descriptor after the "connection_read_cq_ssl" function returns -2, it seems that FDEVENT_RDHUP and close_notify doesn't work as expected.

When the lighttpd function connection_read_cq_ssl() returns -2, lighttpd works as expected.  Your issue was that your ancient, outdated, unsupported, end-of-lifed openssl 1.0.2 was not behaving properly.  Please stop wasting my time troubleshooting your poorly maintained systems running end-of-lifed openssl software.


renderAjax doesn't reload js files

I'm using registerJsFile inside renderAjax file. This is my ajax view file:
$themeUrl = $this->theme->baseUrl;
<EMAIL_ADDRESS>['depends' => JqueryAsset::className()], uniqid());
$this->registerJs('console.log("Inline js script")');

and this is the save-load.js file
console.log('js file');

As you can see the "Inline js script" shows every time I make a request, but the 'js file' only show for the first time. The same thing happen for my jquery code, it only work for the first request, then the next request it doesn't work anymore. Example:
var $pjaxGrids = $(
        'div#pjax-load-bill-grid, div#pjax-save-bill-grid,'+
        'div#pjax-save-system-grid, div#pjax-load-system-grid, '+
        'div#pjax-save-toutimes-grid, div#pjax-load-toutimes-grid, '+
        'div#pjax-save-proposal-grid, div#pjax-load-proposal-grid, '+
        'div#pjax-save-consumption-grid, div#pjax-load-consumption-grid'
    );
$pjaxGrids.on('click', 'tr', selectRow);

This code only work for the first time, but if I move it to the registerJs instead of registerJsFile then it works in every request as I expect

This is by design, A JavaScript file would typically only need loading once so all subsequent requests filter out already included files.
If you wan't to load it with every request you can add it's path to yii.reloadableScripts yii.js

Hi,
Would you please explain how to add it's path to yii.reloadableScripts.
Thanks.


[Draft][Demo] auto tp training

This is an experimental demo on autoTP training, not for review. Apologies for its somewhat rudimentary draft version, I hope to elucidate this process.
Currently, I tested pure TP (DP=1 cases), directly using the HF transformers Trainer. I trained llama7B (finetune from pretrained weights) on 4GPUs and 8GPUs with pure TP and achieved a loss curve of 1.6~0.3(expected).
Main modifications are as follows:

On the train script side:

Explicit use of an API (currently directly using the inference API, invoking autoTP to do module replacement).
Manual modification of a dataloader to synchronize data for all TP ranks (this is a temporary solution).
Setting ds_config.json where zero_config zero_stage=0, autotp_size=num_gpus(DP=1).

On the DS side change, in this demo:
1 Decoupling MPU and Megatron, I've directly taken Megatron's code and put it in the parallel_states.py file
2 Adding backward code for the main replace modules, linelinear & linearallreduce.
3 Adding the 'tensor_model_parallel' attribute for linelinear & linearallreduce, ensuring they are correctly handled in grad norm or other calculations.
5 Setting requires_grad=True for the weights and bias of linelinear & linearallreduce, ensuring they are captured in model_params by  transformer prepare_deepspeed logic and fed to the DS optimizer in related.
6 _broadcast_model: Due to some inconsistencies in group settings, the dp group used by _broadcast_model is not correct, so I directly bypass the logic here(DP=1).
7 gradient_allreduce:  directly disable it because of the similar reason as 6.  5&6 can be resolved by a unified group init function.
8 Adding the autotp_size config.

Currently, in this basic version,  I did two simple tests. Under the same gbs and gas conditions, it has 70% performance compared to zero3, but there are some gbs threshold limits lower than zero3 (at this time, zero3 performs better, TP oom, may be either the dataloader or lacking some optimizations from Megatron? I didn't further analyze)
The benefit of doing this is to decouple TP and Megatron bindings, enable user directly using transformers+ds training with tp+something, which can also be applied to other simple models (through module replacement). Additionally, because There are autoTP inference code and the inheritance between zero backend and transformers, No need for particularly much additional logic

For the most basic usage, there are some issues to handle:

Transformer seems to have no logic about real TP(Only single-device simulation), which causes some minor problems with dataset counting. For example, if two ranks each load 4 identical data, it will consider this as 8 data. This affects the display of counters and some parameters of the optimizer schedule (equivalent to increasing the lr decay). Need to correct the counting of trained num_samples.
Load and save checkpoint: If the code for autoTP_training is just for autoTP inference, I think this should be much easier. Otherwise, some reverse shard operations may be needed.

For better use:
The most basic is to consider compatibility with zero dp, and it may also be compatible with more features(reuse the relevant logic of ds for Megatron's TP), Some performance and memory optimizations.

This PR should be addressing this discussion.  Link.
https://github.com/microsoft/DeepSpeed/discussions/4930

@inkcherry and @delock, please let us know any way we can help. Thanks!

It would be super helpful if one can make autoTP training with domino #6733.

@delock and @inkcherry, is this still active work?

Hi @skyshine102 @delock @inkcherry ,
I am leading domino project, would like to collaborate if possible with this effort of autoTP training & decouple TP and Megatron bindings.

Hi @GuanhuaWang is Domino referring to this paper?  https://arxiv.org/html/2409.15241v1   Thanks!

@delock Yes, @GuanhuaWang is the first author.
I would suggest a refactoring on parallel_states.py first. Deepspeed team may need to discuss on

maintain deepspeed's parallel_states version (megatron deepspeed) or whether to make it more consistent with NV's megatron-core API

It would be great to reserve TP/PP/EP process group API, even it's not used by ZeRO algorithm.

support torch DeviceMesh API

as this will be the main entrypoint for most torch & huggingface transformers users
currently DeviceMesh API for sequence parallel is supported, but not PP/TP/EP e.t.c. A well-designed process group management  API can alleviate future contributor's development cost in prototyping stage.

@GuanhuaWang, sure, I can help with rebasing the code recently. I think this PR still needs three things to be done:

As mentioned by @skyshine102 , the comm group API is needed, at least for TP and DP.
Dataloader API.
Checkpoint API.

@GuanhuaWang, sure, I can help with rebasing the code recently. I think this PR still needs three things to be done:

As mentioned by @skyshine102 , the comm group API is needed, at least for TP and DP.
Dataloader API.
Checkpoint API.

@inkcherry , I just noticed that you copied parallel_state from megatron-core to your draft but deepspeed engine already has one (here). You may modify this file instead of copying. Currently deepspeed engine support DP/PP/EP/SP and now TP. I suppose all of these process groups will be needed.

Dataloader API: Not sure if deepspeed team wants to maintain it...  "it's already implemented in megatron-deepspeed repo." Maybe just a quick demo snipplet in example.py will be enough.

Hi @inkcherry need to make sure this PR does not impact autotp inference performance and compatibility.  When your PR is stable, check with Guobing and @rogerxfeng8 for internal test.


Linter/formatter should enforce coding style rules that will gate merging PRs

See this issue https://github.com/ipfs/js-ipfs-http-client/issues/1225
Thanks!

This is exactly what our eslint config does, closing this issue.
Feel free to re-open if you think you have more to add.

I think we should reopen it. I’m pretty sure I ran the linter and it didn’t catch the issue linked to above. I can try to reproduce it to confirm.

@hugomrdias Indeed, making a change such as this:
if (options.enableShardingExperiment != null) searchParams.set('enable-sharding-experiment', options.enableShardingExperiment)

->
if (options.enableShardingExperiment != null) {
  searchParams.set('enable-sharding-experiment', options.enableShardingExperiment)
}

doesn't create any new warnings or errors. So I think this issue should be reopened. Here are the other issues like this I noticed:
https://github.com/ipfs/js-ipfs-http-client/pull/1224#discussion_r369415389
https://github.com/ipfs/js-ipfs-http-client/pull/1224#discussion_r369415673
https://github.com/ipfs/js-ipfs-http-client/pull/1224/files#r369679391

that happens when you have extra formatters in your editor or manual change formatting. we use eslint-standard and while it doesn't have every single style rule defined to avoid these issues it is enough for our needs.
we might adopt prettier in future but for now it is what it is.
In general when contributing one should try not to add changes to the formatting to make PRs easier to review, we haven’t had any major problems with this so priority is pretty low.

Yep, I know. I thought this might increase the odds of helpful PRs making it in going forward, but that's a very reasonable prioritization choice. Thanks!


cargo-deny: 0.9.0 -> 0.9.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/EmbarkStudios/cargo-deny/releases.
meta.description for cargo-deny is: "Cargo plugin to generate list of all licenses for a crate"
meta.homepage for cargo-deny is: "https://github.com/EmbarkStudios/cargo-deny"
meta.changelog for cargo-deny is: ""
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/1kblc0pdqrqvk49zx5x29l1c86q7s2xn-cargo-deny-0.9.1/bin/cargo-deny passed the binary check.

1 of 1 passed binary check by having a zero exit code.

1 of 1 passed binary check by having the new version present in output.

found 0.9.1 with grep in /nix/store/1kblc0pdqrqvk49zx5x29l1c86q7s2xn-cargo-deny-0.9.1

found 0.9.1 in filename of file in /nix/store/1kblc0pdqrqvk49zx5x29l1c86q7s2xn-cargo-deny-0.9.1

directory tree listing: https://gist.github.com/30c743bd18e0ab976e5c683edf114e95

du listing: https://gist.github.com/7aeada5bd5db32abd4f9dbc84e281c44

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

4 total rebuild path(s)

1 package rebuild(s)

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

First fifty rebuilds by attrpath
cargo-deny

Instructions to test this update (click to expand)

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

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1kblc0pdqrqvk49zx5x29l1c86q7s2xn-cargo-deny-0.9.1
ls -la /nix/store/1kblc0pdqrqvk49zx5x29l1c86q7s2xn-cargo-deny-0.9.1/bin

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

1 package built:

cargo-deny

Maintainer pings
cc @matthiasbeyer for testing.

@ofborg eval


Update DG

Acknowledgement:

[x] code, ideas, libraries adapted

Design:

[ ] Architecture
[ ] UI
[ ] Model
[ ] Storage
[ ] Common

implementation: check your own parts if its still relevant + try to standardise

[ ] import
[ ] addstudent
[ ] addgroup (can please change the header How the AddGroupCommand works: so it dosent look weird in table of contents) (i changed the title alr)
[x] addalloc
[x] addscore
[x] search
[x] show

Appendix:requirements:

[x] Product scope
[x] user story
[ ] use case
[x] non functional req (please help check)
[x] glossary

Appendix:testing

[ ] Saving Data (im not sure for the last case)

I made some changes to the Table of Contents. What do yall think? Currently it looks like this

If yall are okay with this then I can bold the titles of the UG too to make the DG and UG kinda consistent

looks good! Can you add the subpoints under Design section too?

looks good! Can you add the subpoints under Design section too?

Ah okay!


Bug: Latest version doesn't always add # before data-link-tags

This may be confusing or break previous configurations.

Same issue. A lot of my tags follow this format on frontmatter, which doesn't work anymore:
tags:
  - tag
  - tag

@lkadre Until we fix this, you can change your CSS to [data-link-tags *='tag-name'] instead of [data-link-tags *='#tag-name']


[camera] Removed obsolete example folder from camera root

This is a maintenance pull request cleaning up the example directory from the ./packages/camera folder. This is a left over folder from the converting the plugin to the federated architecture.
Merging this PR doesn't require a release of the camera plugin.
Pre-launch Checklist

[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide and the C++, Objective-C, Java style guides.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test exempt.
[ ] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[ ] I updated CHANGELOG.md to add a description of the change.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I signed the CLA.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

You'll need to merge in master to pick up the fix for the script issue that caused the publishable failure, then should be good to land.

You'll need to merge in master to pick up the fix for the script issue that caused the publishable failure, then should be good to land.

Thanks @stuartmorgan, should have thought about that myself. Really appreciate the headsup.


Python3-pip

Not completely sure about this one
https://packages.ubuntu.com/xenial/python3-pip
https://apps.fedoraproject.org/packages/python3-pip
https://packages.debian.org/stretch/python3-pip

What are you not sure about?

What are you not sure about?

Whether Is it ok to install python3 in rosdep


Add theme: Ayu

Add theme: Ayu
This PR adds a new theme to the theme library.
Theme Details

Name: Ayu
Description: Ayu Colorscheme for Zen Browser
Homepage: https://github.com/arindamukawlas/ayu-zen-browser
Author: @arindamukawlas

Please ignore this PR bro as I submitted the wrong code in it.
I submitted another PR with the correct code a few minutes later #571


Add self-contained artifact upload script for apache nexus (#11329)

I initially wanted to use Python but without additional libraries it overwhelmed me and I wanted to keep it simple and self-contained. There is some extra verbosity (XML processing in Java is hell) but it does work and I staged artifacts for Lucene 10.0.0 successfully (and dropped the repository afterwards).
Now... I'm not so sure how to test the wizard bit. I based the changes on @HoustonPutman 's work on Solr side. The script can accept user name and password in environment variables, on command line or will prompt for password if not provided... but I haven't tested this as I'm not sure how to test it in isolation (@janhoy - is there any way to do it?).

For stand-alone use, it's simple enough too:
java dev-tools\scripts\StageArtifacts.java -u dweiss /release/candidate/maven-artifacts

will prompt for password for nexus access.

Thanks @dweiss I'll give it a try!

@jpountz What did you point the script at, exactly? I'll look into it - drop the staging repo, please.

I think I know what the problem is, but would like a confirmation from you first - let me know what you pointed the script at (which directory).

The script should be pointed at the maven folder, including parent subfolders, as in:
https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.0-RC2-rev-0384b4fcad7856ddc574c8b994c814a568ce6d0a/lucene/maven/
I'm surprised nexus even closed the staging repository since artifact group IDs shouldn't allow you to do that...

This is the folder I ran it against. I used the same folder that the release wizard recommended using with the Ant build.

Give me a sec. you're getting a different output than I do then.

Hi @jpountz . Sorry about this - I'm not sure what happened there but the relative upload path of those artifacts was indeed wrong (and I'm also not sure why nexus isn't complaining about it!...). I fixed the script on 9x and main and added an extra check to make sure the groupId matches every uploaded artifact's path.
You can also add {{--description "Lucene 9x"}} to the command line - it shows as the staging repository's description in the UI.

No worries at all @dweiss, thanks a lot for modernizing Maven staging upload, it's a relief we no longer have a dependency on a 8.x build!

I wonder if this should be reported to infra though. The fact you can close an upload repository with top-level artifacts is strange... I wonder what would happen if you clicked release on that, would it actually promote those JARs to here? It seems crazy!
https://repo1.maven.org/maven2/

@dweiss So I did release the staged repository with top-level artifacts, and Nexus did not give me any errors either. :( After browsing the content, I saw all the artifacts that I had expected, it's only after clicking and realizing that publication to Central wasn't working that I thought that the lack of hierarchy was weird.
Good news is that I have released with the correct directory layout earlier today and now I can see the artifacts on Maven Central.

I filed this question to infra: https://issues.apache.org/jira/browse/INFRA-23931

Thanks Dawid!

Just FYI - Sonatype's nexus wouldn't let you release that staging repository, I've tried:

I'll follow up with Gavin on the Infra ticket. Seems like the rules at Apache are not as strict. And sorry for this.

Again, no worries at all, not your fault.


helm upgrade command fails

helm version output:
version.BuildInfo{Version:"v3.4.2", GitCommit:"23dd3af5e19a02d4f4baa5b2f242645a1a3af629", GitTreeState:"dirty", GoVersion:"go1.15.5"}

Upgrading from chart version 0.2.2 to 0.2.3
Ran the following command:
helm upgrade -i pinot pinot/pinot -n pinot --reuse-values -f helm.yaml

Got output:
Error: UPGRADE FAILED: template: pinot/templates/minion/statefulset.yml:23:11: executing "pinot/templates/minion/statefulset.yml" at <include "pinot.minion.fullname" .>: error calling include: template: no template "pinot.minion.fullname" associated with template "gotpl"

Looks like this has to do with the latest upgrade to the chart: addition of the minion https://github.com/apache/incubator-pinot/pull/6430

Thanks for reporting this! The issue is that _helpers.tpl is not packaged correctly.
Updated the package in PR #6459.

Thanks for reporting this! The issue is that _helpers.tpl is not packaged correctly.
Updated the package in PR #6459.


Add pagination to GET /persons and GET /encounters

Description

Allow option to retrieve subset of data in pages
Acceptance Criteria

[ ] Add optional limit and page query params to both endpoints
[ ] Correctly returns limit number of entries at page=x

Implementation details

Both query params must be present for pagination
Testing notes

LGTM 😎

This is done for GET /persons and GET /encounters now!


Fusion Table Connector error - Community Connector Error

There was an error caused by the community connector. Please report the issue to the provider of this community connector if this issue persists.
Connector details
There was an error caused by this connector.

Since we removed the fusion table connector from this repo, this issue is no longer needed.


Version number needs bumping

Tried to get 0.0.9 today using bower and it said that it required version 1.0.8 of angular. It isn't pulling in the change to 1.*.

So many reasons this is no longer needed.


(cluster-providers): tagging ec2 instances

Describe the feature
Propagate tags to EC2 instances.
Use Case

Having the Name tag propagated to EC2 instances helps us to visually identify node in the EC2 dashboard faster
While analyzing costs it's very useful to separate by service, team, customer, whatever tags are configured
Sometimes instance tags are also used by iam policies and considered best practice in some docs
...

Proposed Solution
Always create a NodeGroup with a LaunchTemplate and pass tags
Other Information
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-launchtemplate-launchtemplatetagspecification.html instance
Acknowledgements

[X] I may be able to implement this feature request

CDK version used
2.37.1
EKS Blueprints Version
1.2.0
Node.js Version
18.7.0
Environment details (OS name and version, etc.)
MacOS

Is there a workaround for this right now, is it possible to add tags to the cluster provider?

Is there a workaround for this right now, is it possible to add tags to the cluster provider?

You can check the approach taken in the PR that I linked here #624. It is achievable now by creating a subclass of the GenericClusterProvider and applying changes similar to those in the PR. Or you can wait just a bit, once the PR is merged, we will release 1.6.1 with this support.

@shapirov103 thanks for the quick response, that's exactly what I need the customTags I'll wait for that PR thanks.

@praveenperera Are you good to close this Issue. The issue is fixed.


As per the docs:

In a 3-node cluster, the output should look like this:
NAME               NODE   STATUS   CAPACITY      USED   AVAILABLE
microk8s-m2-pool   m2     Online<PHONE_NUMBER>6   0<PHONE_NUMBER>6
microk8s-m1-pool   m1     Online<PHONE_NUMBER>6   0<PHONE_NUMBER>6
microk8s-m3-pool   m3     Online<PHONE_NUMBER>6   0<PHONE_NUMBER>6

Reproduction Steps
Follow the instructions at https://microk8s.io/docs/addon-mayastor
Introspection Report

inspection-report-20230807_145905.tar.gz
Can you suggest a fix?

If only I had a suggestion :disappointed:
Are you interested in contributing with a fix?

Sure, if I knew what to do!

Update
This looks like it's a hugepages issue. Only one of the three nodes has retained its vm.nr_hugepages setting. Looking into it...

Looks like I must have done something wrong on one of the nodes - I rebuilt it from scratch and all is fine. For the other, it's a 2GB pi and that's not enough to handle 1024 Huge Pages!


Authenicate users for release workflow

What is the purpose of this change?
Make sure only memebers of ema-release-team can trigger the release workflow
How was this change implemented?

Added an environment called prod https://github.com/SolaceLabs/event-management-agent/settings/environments/1084306188/edit

where only ema-release-team can proceed with the release

changed release workflow's environment to prod

Awesome find. Can you demo this to the team later? Want to see the approval process Thanks.

sure, will demo it tomorrow!


custom checkboxes inside input groups

You think of allowing custom checkboxes inside input groups, this example is bugged when using form-control-sm
https://codepen.io/claudioalmeiida/pen/XQmRYE

you could play with utilities helper as a fallback : https://codepen.io/lausselloic/pen/PgPKOd

We've just suggested using margin utility classes to handle the small input group:
https://bootstrap-vue.js.org/docs/components/input-group#custom-radio-checkbox-and-switch-addons


update GeMS_ValidateDatabase.py sorts problematic map units in ValidationErrors.html alphabetically

Prepended the text '2.5' to 'Duplicated MapUnit values in DescriptionOfMapUnits' to match the other rule violations when displayed in ValidationErrors.html.

Added sort_mapunit_errors function and called it for Rules 2.4, 2.5, 3.8, and 3.9, which should satisfy this enhancement request: https://github.com/DOI-USGS/gems-tools-pro/issues/99#issue-2180305267

This is great, Darby! Thank you for doing it.

No problem!


Strange looking virtual user count in average response time graph

We've been using this plugin for quite some time and I must say it has a comprehensive set of charts that are really helpful in explaining performance indicators.
Recently, we tried running the JMeter test with multiple workers (2 workers), and below is the output we observed in the average response time graph:

The virtual user count line went beyond the test duration (which is 10 minutes).
We attempted to reproduce this with org.apache.jmeter.visualizers.backend.influxdb.InfluxdbBackendListener (official JMeter implementation) and we observed the following:

Hence we're wondering what could cause the virtual user count to extend beyond test duration in the first graph?
Here's the query for 2nd graph just in case:
from(bucket: "${bucket}")
  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
  |> filter(fn: (r) => r["_measurement"] == "jmeter")
  |> filter(fn: (r) => r["_field"] == "avg")
  |> filter(fn: (r) => r["statut"] == "ok")
  |> aggregateWindow(every: ${aggregation}s, fn: mean, createEmpty: false)
  |> yield(name: "mean")

from(bucket: "${bucket}")
  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
  |> filter(fn: (r) => r["_measurement"] == "jmeter")
  |> filter(fn: (r) => r["_field"] == "meanAT")
  |> aggregateWindow(every: ${aggregation}s, fn: mean, createEmpty: false)
  |> keep(columns: ["_time", "_value", "_field"])

We would really appreciate it if you could shed some light on this. Thanks in advance!

Hi @pooventhan, on the first chart you can see the such users chart maybe due to in the plugin we have async await (asynchronously) in the implementation of the data sending to flux. Jmeter do not waits when data is placed. It means threads will die with some prolongation when data sending is finished. It seems like that.
BR,
Mike

Hi @mderevyankoaqa , it turns out that the official plugin org.apache.jmeter.visualizers.backend.influxdb.InfluxdbBackendListener accumulates data collection for a short period before pushing over to Influx. Besides, the payload isn't comprehensive compared to yours i.e: properties such HTTP status code, response body have been omitted. Hence, it sends data to the server faster and gets processed fast.


Docs: Clarify the documentation on the sandbox network.

Fix some confusing phrasings in the README and make it clearer.

!ci-build-me


No notification at all

Helllo guys,
i am moving from the old push notification plugin to this one, but i can't success in showing the actual notification.
I am using the example provided in this repo but without results.
The registration works, but not the notification event (i got a sucess answer from the gcm endpoint, so i guess that the notification arrived to my device but for some reason it wont show).
Is this working for you?
I am testing on a Samsung tablet with Android 5.1.1 and i tested the latest version of the plugin and the 1.3.0
Thanks!

hi @riccardoSocialcities
the latest for now is 1.4.2

@riccardoSocialcities getting a success answer from the gcm endpoint only means that gcm has successfully gotten the message, not the device.
What payload are you sending to the device? Can you run adb logcat | grep PushPlugin from the command line to see if the plugin is receiving the message. Is your app open or minimized when you send the push? An open app should get the on('notification') event handler called, a minimized one should get a notification in the shade if a title or message are provided.

@riccardoSocialcities re-open if still a problem.


chore use NotFallbackInPasrser to label stmt impl in Nereids

add a interface named NotFallbackInPasrser.
If we already impl same stmt in Nereids, we let the stmt in legacy planner implement it.
When stmt implement NotFallbackInPasrser, it could not fall back to legacy planner when parse failed in Nereids.

run buildall


Remove deprecated cfg_attr from README

tool_attributes are stable since 1.30: Playground The old cfg_attr(rustfmt, rustfmt_skip) attributes aren't necessary anymore and everyone should switch to #[rustfmt::skip] sooner or later.
There is also a Clippy lint in the making for this: rust-lang-nursery/rust-clippy#3123

Thanks!


Error in comments

A very common mistake that happens to me is when there are several comments and they are misaligned, as shown in the image.

I select the lines, and press Option+A, the lines move towards the end of the file, this is very strange.

Could you please provide full text? Seems for me, it works. I mean:
//Only some comments
  //Only some comments
    // Only some comments
      // Only some comments
        //Only some comments

will formated to :
  //Only some comments
  //Only some comments
  // Only some comments
  // Only some comments
  //Only some comments

@chouzz I see three issues related to comments indentation.
1
In VSCode:
Open a blank file and paste this:
if (x > 5) dummy = 1;
//----------------------------------
// Format NULL
//----------------------------------
else if (v === null)
    v = '<i class=muted>n/a</i>';

Select it and press Option+A.
Each time you press the keys, the comments will advance two spaces.
2
But if I'm editing in Windsurf, with all plugins disabled except BetterAlign, when pressing the keys even only once, the comments will start advancing like crazy, several times per second, even without me pressing any key. The only way to stop it is to press a key that clears the selection (ex: Esc).
The only way to prevent this from happening is to set "betterAlign.surroundSpace.comment" to -1
I also made sure there is no other conflicting key binding.
3
It is also very annoying the even with comment=0, when invoking BetterAlign, the comments will still be indented 2 spaces. I am unable to align them to the other lines, they always end up indented in relation to the rest of the surrounding code.


[Rest API] Login example with JSON

curl http://localhost:3000/api/v1/login \
     -d "user=myusername&password=mypassword"

curl -H "Content-type:application/json" \
      http://localhost:3000/api/v1/login \
      -d '{ "username": "myusername", "password": "mypassword" }'

I think the JSON call has typo. username should be user.

It can actually be either one, this was to demonstrate that.
On Wed, Jan 11, 2017, 9:59 AM Ashis Rai<EMAIL_ADDRESS>wrote:

curl http://localhost:3000/api/v1/login
-d "user=myusername&password=mypassword"
curl -H "Content-type:application/json"
http://localhost:3000/api/v1/login
-d '{ "username": "myusername", "password": "mypassword" }'
I think the JSON call has typo. username should be user.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/RocketChat/Rocket.Chat.Docs/issues/173, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAz51yb_sdhXOnxrb_xImjK7Kf8rGT5Uks5rRMQ7gaJpZM4LggBi
.

@graywolf336 below is what i am seeing while using username.

That's interesting as it has always worked for me, what version of
rocket.chat?
On Wed, Jan 11, 2017, 10:03 AM Ashis Rai<EMAIL_ADDRESS>wrote:

@graywolf336 https://github.com/graywolf336 below is what i am seeing
while using username.
[image: screen shot 2017-01-11 at 5 45 55 pm]
https://cloud.githubusercontent.com/assets/330362/21847821/0dc705e4-d826-11e6-8831-c888123cc32f.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/RocketChat/Rocket.Chat.Docs/issues/173#issuecomment-271851840,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAz513ZWmoe5wyPmxndxlWnoWzhzsE1zks5rRMUngaJpZM4LggBi
.

It is 0.48.2. Now it is working on my local machine but not on a staging. user works though in staging. Strange!

@graywolf336
Since browser authentication supports both username and email, I expected same support to API as well.
BTW, below is another way to log in.
curl -H "Content-type:application/json"  \
      http://localhost:3000/api/v1/login \
      -d '{"user":"ashis@cloudfactory.com","password":"nepal"}'

Response
{
  "status": "success",
  "data": {
    "authToken": "-HYTyASph0kU6iz_ikKMEeMf3_eOXjaxmFqQeY2Nijz",
    "userId": "tTAibfAzxAhM4PnJ5"
  }
}


Make the smallest path to reference image

Thanks for a great plugin! I have one improvement I would like to see. I use Obsidian to write blog posts. I have two folders:
Pages  - these are my published blog posts
WIP - "work in progress" blog posts
I start a post in the WIP folder, say for example the post with filename new_post. If I paste an image, I get the following Markdown link:
![image-20242172518665.png](WIP/new_post/image-20242172518665.png)

When my post is done, I move both the new_post.md file and the new_post folder to my `Pages folder, but at that moment all links are broken. The image link also works if it was pasted as:
![image-20242172518665.png](new_post/image-20242172518665.png)

Would be great if that was the default behavior. I could not fix it with the other settings.

Thank you for your suggestion. It may be a little troublesome to implement this function. I will try my best to do it in a few days.


Instructions for nuget for the Mac are incorrect.

I believe the examples of things to execute for the Mac are WRONG!
E.g. nuget on the mac is simply nuget not nuget.exe
And getting nuget for windows doesn't make sense.
Also when updating nuget on the mac you have to use sudo:
sudo nuget update -self
Somebody should double check all the Mac specific instructions to make sure they really work on the Mac.  I see several copy and paste errors.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3460a9b2-3b49-1cda-add2-14d26e217716
Version Independent ID: 95b91106-faff-c7f6-3699-94d643b5cf73
Content: Installing NuGet client tools
Content Source: docs/install-nuget-client-tools.md
Product: nuget
GitHub Login: @karann-msft
Microsoft Alias: karann

Thanks for the issue!
When you alias the nuget.exe on Mac, you can use just nuget because that is your alias name. If you do not alias it, you would have to call mono nuget.exe to use nuget.exe on Mac.
I'll add a note to include sudo usage on MacOS for update -self.
What about getting NuGet for Windows doesn't make sense? Also what examples are wrong? At first glance they seem okay to me.