outpoint discrepancy between two installs for updated claim

The Issue
Today I noticed I'm having trouble streaming lbry://one - the app didn't recognize it as a previously downloaded file, but I know I had it in the past and it shows up in my Downloads section. If I try to stream it, it also fails - just get's stuck on the loading icon after geting a completed notification and the daemon shows - lbrynet.daemon.Daemon:1571: Already have a file for one. If I click Download, it shows connecting and then goes back to showing the download button - the daemon shows the same message about having the file. This claim was recently updated by Oakie so I checked the file_list and noticed that the outpoint is incorrect on the broken install and shows correctly on working install (not sure how one updated but not the other).  I'm hoping the streaming issue is also related to an incorrect endpoint, but not sure.  Both installs had the file downloaded well before the outpoint was changed.
So as a more general question, can we check the functionality of file_list and when/how it is updated?
Update: Now I'm not even sure how the laptop received the updated endpoint. My current testing shows this will happen anytime a claim is updated and the filename remains the same. This causes a mess for anyone that downloaded the content but then the claim is updated - cannot download the new content without deleting the file manually (using file_delete, not sure about deleting the file in the downloads directory yet - haven't tested).
main PC (broken)
  {
    "claim_id": "008401a48cecef2a13cf5376b696169bb36b18c6",
    "completed": true,
    "download_directory": "D:\\LBRY Downloads Main PC",
    "download_path": "D:\\LBRY Downloads Main PC\\Happy Working Song - Enchanted - Holly Oakey-lZ5ZL0VSlC4.mp4",
    "file_name": "Happy Working Song - Enchanted - Holly Oakey-lZ5ZL0VSlC4.mp4",
    "has_signature": false,
    "key": "abf7fb30e4bb9d683ffa635617ee0974",
    "message": null,
    "metadata": {
      "claimType": "streamType",
      "stream": {
        "metadata": {
          "author": "",
          "description": "All proceeds go to holly for buying toys, i will post the video with those toys on Xmas day",
          "language": "en",
          "license": "All rights reserved.",
          "licenseUrl": "",
          "nsfw": false,
          "preview": "",
          "thumbnail": "http://www.thetoydiscounter.com/happy.jpg",
          "title": "Holly singing The Happy Working Song",
          "version": "_0_1_0"
        },
        "source": {
          "contentType": "video/mp4",
          "source": "92b8aae7a901c56901fd5602c1f1acc0e63fb5492ef2a3cd5b9c631d92cab2e060e2a908baa922c24dee6c5229a98136",
          "sourceType": "lbry_sd_hash",
          "version": "_0_0_1"
        },
        "version": "_0_0_1"
      },
      "version": "_0_0_1"
    },
    "mime_type": "video/mp4",
    "name": "one",
    "outpoint": "8e5d6945d238e8508520364d5eae7885b0db15d77d6d5cffee3f860dc13f0b45:0",
    "points_paid": 0.0,
    "sd_hash": "92b8aae7a901c56901fd5602c1f1acc0e63fb5492ef2a3cd5b9c631d92cab2e060e2a908baa922c24dee6c5229a98136",
    "stopped": true,
    "stream_hash": "bb4dc73b33652ca5a2bbaecdbd36831a2301791967801576049644fd79f26d6b57c605702d0f15da7118505679d21a08",
    "stream_name": "Happy Working Song - Enchanted - Holly Oakey-lZ5ZL0VSlC4.mp4",
    "suggested_file_name": "Happy Working Song - Enchanted - Holly Oakey-lZ5ZL0VSlC4.mp4",
    "total_bytes": null,
    "written_bytes": 9227338
  }

Laptop(correct)
 {
    "claim_id": "008401a48cecef2a13cf5376b696169bb36b18c6",
    "completed": true,
    "download_directory": "C:\\Users\\SoloDolo\\Downloads",
    "download_path": "C:\\Users\\SoloDolo\\Downloads\\Happy Working Song - Enchanted - Holly Oakey-lZ5ZL0VSlC4.mp4",
    "file_name": "Happy Working Song - Enchanted - Holly Oakey-lZ5ZL0VSlC4.mp4",
    "has_signature": false,
    "key": "abf7fb30e4bb9d683ffa635617ee0974",
    "message": null,
    "metadata": {
      "claimType": "streamType",
      "stream": {
        "metadata": {
          "author": "",
          "description": "All proceeds go to holly for buying toys, i will post the video with those toys on Xmas day",
          "language": "en",
          "license": "All rights reserved.",
          "licenseUrl": "",
          "nsfw": false,
          "preview": "",
          "thumbnail": "http://www.thetoydiscounter.com/happy.jpg",
          "title": "Holly singing The Happy Working Song",
          "version": "_0_1_0"
        },
        "source": {
          "contentType": "video/mp4",
          "source": "92b8aae7a901c56901fd5602c1f1acc0e63fb5492ef2a3cd5b9c631d92cab2e060e2a908baa922c24dee6c5229a98136",
          "sourceType": "lbry_sd_hash",
          "version": "_0_0_1"
        },
        "version": "_0_0_1"
      },
      "version": "_0_0_1"
    },
    "mime_type": "video/mp4",
    "name": "one",
    "outpoint": "0a173a57e6949a06af01638fa1e53f84120ff6fc05083f3a3c60b6df1446347f:0",
    "points_paid": 0.0,
    "sd_hash": "92b8aae7a901c56901fd5602c1f1acc0e63fb5492ef2a3cd5b9c631d92cab2e060e2a908baa922c24dee6c5229a98136",
    "stopped": true,
    "stream_hash": "bb4dc73b33652ca5a2bbaecdbd36831a2301791967801576049644fd79f26d6b57c605702d0f15da7118505679d21a08",
    "stream_name": "Happy Working Song - Enchanted - Holly Oakey-lZ5ZL0VSlC4.mp4",
    "suggested_file_name": "Happy Working Song - Enchanted - Holly Oakey-lZ5ZL0VSlC4.mp4",
    "total_bytes": null,
    "written_bytes": 9227338
  }

Steps to reproduce

Expected behaviour
Tell us what should happen
Actual behaviour
Tell us what happens instead
System Configuration

LBRY Daemon version:
LBRY App version:
LBRY Installation ID:
Operating system:

Anything Else

Screenshots

https://github.com/lbryio/lbry/blob/master/lbrynet/daemon/Daemon.py#L1564
Is checking if it already has the file by looking up the file by claim ID.
This is wrong, as updates preserve claim ID and could change the stream.

I'll rename this issue to be more generic related to the download / file list issues.

When a claim is updated but the claim id does not change, this is the publisher indicating that it is the same content that was there previously. Therefore the data should be re-downloaded, but there should be no subsequent charge for the download.
An update without a claim id change should be the equivalent of a fixing a typo (or, if you stretch it, making Greedo shoot first).
Right now more substantial edits may be taking place without a claim id change (imagine a user publishing a much different piece of content over lbry://one). This probably requires some updates to the publish, to indicate a certain publish to the same name should involve a regeneration of claim id.

The main problem right now is that any edit to the claim changes the outpoint (since its a new tx), so we have these various downstream issues on the download and publishing side.  I agree that a new claim ID should be generated in certain instances -  sounds difficult to do automatically so will need to be a clearly explained user option.
Would the re-download functionality be an app side issue or daemon also?


Header title has been dissapear from v10 to v11

material-react-table version
11.0
react & react-dom versions
latest
Describe the bug and the steps to reproduce it
Hello,
We start migrating from v10 to v11 and we catch that the header title was removed on v11
https://github.com/KevinVandy/material-react-table/commit/9b085d570b0f63dfb028cc861b08300087d9fc2d#diff-14511697e8813fa2b40be42ddb17235d138cf21c768924f3826bf98b15f3aebcL270
Is there any reason?
Minimal, Reproducible Example - (Optional, but Recommended)
You cant view it in the basic table example on https://www.material-react-table.com/
Screenshots or Videos (Optional)
No response
Do you intend to try to help solve this bug with your own PR?
Maybe, I'll investigate and start debugging
Terms

[X] I understand that if my bug cannot be reliably reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

because I got so many complaints that it was there. You can easily add it back in muiTableHeadCellProps.title


Rename filename to CustomerProfiles/create-customer-profile-from-a-transa…

Rename filename to CustomerProfiles/create-customer-profile-from-a-transaction.php for match with API reference http://developer.authorize.net/api/reference/index.html#customer-profiles-create-a-customer-profile-from-a-transaction

Duplicate pull request. Closing it.


style: homepage

What does this PR do?
Improve homepage layout
Related Issue(s)
No previous issue
Changes

Applied a gradient color to the title.
Made minor revisions to the text content.
Implemented a hover effect for the button.
Updated the background color using gradient.
Eliminated inline styles and transitioned to Tailwind CSS classes.
Created a new folder to store images also added few images inside.

Screenshots or GIFs (if applicable)
Before:

After:

Checklist

[x] I have read and followed the contributing guidelines.
[x] My code follows the project's coding style and conventions.
[ ] I have added unit tests (if applicable) to ensure the code works as expected.
[ ] I have updated the project documentation (if necessary).

Additional Comments
Add any additional comments, context, or information about this PR.
By submitting this PR, I confirm that:

[x] I have reviewed my code and believe it is ready for merging.
[x] I understand that this PR may be subject to review and changes.
[x] I agree to abide by the code of conduct and contributing guidelines of this project.

I made some other optimizations, I'm going to open a new PR


Variable name conflict causing dupes to break after #439

Duping some things like wire teleporters now errors with addons/advdupe2/lua/advdupe2/sv_clipboard.lua:1273: bad argument #2 to '__add' (Vector expected, got table)

I swapped out the pcall to a ProtectedCall so the error prints the full stack:
[advdupe2] addons/advdupe2/lua/advdupe2/sv_clipboard.lua:1266: bad argument #2 to '__add' (Vector expected, got table)
  1. __add - [C]:-1
   2. unknown - addons/advdupe2/lua/advdupe2/sv_clipboard.lua:1266
    3. ProtectedCall - [C]:-1
     4. func - addons/advdupe2/lua/advdupe2/sv_clipboard.lua:1478
      5. unknown - addons/ulib/lua/includes/modules/hook.lua:260

This might be unrelated to the PR, but either way it's an deeper issue that's been revealed now.
https://github.com/wiremod/wire/blob/master/lua/entities/gmod_wire_teleporter.lua#L20
Teleporter defines a field LocalPos. AdvDupe2 stores dupe data directly on the entity, so it's likely it was trying to access this incorrect LocalPos field instead of the AdvDupe2 data.

Oh wow, yeah seems like that's the issue, maybe the advdupe2 values should be named better? Although i don't know how that'd work with backwards dupe compat etc

Should change the issue title and description to reference that instead, although if you can confirm that it doesn't happen on the previous commit, then that's even more mysterious.

Looking deeper into it, it seems this might be due to the implementation of backwards compatibility with AdvDupe1.

@wrefgtzweve
Nope. It does not seem to be my patch that is related only to bone manipulations. Wire teleporter is not a ragdoll :D

It's weirdly inconsistent which made me believe the pr broke it, my bad for that

The issue is still present, that pr didn't solve it for me
[AdvDupe2Notify]	Pasting...
[AdvDupe2Notify]	addons/advdupe2/lua/advdupe2/sv_clipboard.lua:1244: attempt to compare nil with number
[AdvDupe2Notify]	Finished Pasting!

I think the pr fixed it for the Queue'd case (multiplayer), but maybe the singleplayer case isn't fixed.

This is from accessing Queue.Revision which gets its value in function AdvDupe2.LoadDupe, in a dupe info struct whose field revision is set in function AdvDupe2.Decode, where that field is impossible to be nil, so this is likely some sort other issue.
SP and MP both use the Queue. I tested in SP.

Hm, maybe check that you're not using the workshop version, @wrefgtzweve ?

I'm on commit 7f061801bf7bbdfdb573ed23410591d48c1e93ae, restarted my game, i don't have it on workshop either.

Are you willing to share the dupe to help? Any other considerations?

Oh wait, looking at the error im getting / posted, it's a different error than before which adds up

[AdvDupe2Notify]	addons/advdupe2/lua/advdupe2/sv_clipboard.lua:1244: attempt to compare nil with number

Are you willing to share the dupe to help? Any other possible points of conflict?

I mentioned it here, https://github.com/wiremod/advdupe2/issues/441#issuecomment-1786025168 im just copying a newly spawned teleporter, its not a dupe file

Seems like copying any prop and trying to spawn it is currently broken, it all gives the sv_clipboard.lua:1244 error

Okay i see now, i think once you load a dupe file it works fine, but before that any copy paste (no dupe file) is broken

Do you have an addon that's mucking with the Advdupe2 Queue entries? I can't investigate right now, but later I can.

I shouldn't have anything like that, my dev env is minimal

I'll see if i can get a clip and compress it under githubs 10mb limit

Okay i see now, i think once you load a dupe file it works fine, but before that any copy paste (no dupe file) is broken

Okay, that is my fault, I should've accounted for that. Sorry for my incorrect assumption that was impossible.

No problem, thanks for sticking around and fixing it!


ERROR: Unable to download webpage: '' (caused by BadStatusLine("''",));

Checklist

[x] I'm reporting a broken site support issue
[x] I've verified that I'm running youtube-dl version 2021.12.17
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar bug reports including closed ones
[x] I've read bugs section in FAQ

Verbose log

PASTE VERBOSE LOG HERE

Description

WRITE DESCRIPTION HERE
I hope I'm reporting this correctly.
The error, which is not with every download, started about a day or two ago which is,
ERROR: Unable to download webpage: '' (caused by BadStatusLine("''",));
Sometimes I get the error 404 but it's really the above error. It affects only downloads from the ITV channel & it can be with a news programme from yesterday to Emmerdale from the 01st January to the 14th January to other ones since then but not all of them.
The latest youtube-dl file 17-12-2021 seemed to have more problems than the one I was using which was the 26-04-2021.
Until about 2 days ago I've never had or seen the above error before.
Firstly, the following is what came up when I first tried to download the programme.
C:\Users\User\Videos\youtube-dl Downloads>youtube-dl https://www.itv.com/hub/itv-evening-news/2a4545a1578
[ITV] 2a4545a1578: Downloading webpage
ERROR: Unable to download webpage: '' (caused by BadStatusLine("''",)); please report this issue on https://yt-dl.org/bug .
Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to
call youtube-dl with the --verbose flag and include its complete output.
Then the following is the verbose.
C:\Users\User\Videos\youtube-dl Downloads>youtube-dl https://www.itv.com/hub/itv-evening-news/2a4545a1578 --verbose
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['https://www.itv.com/hub/itv-evening-news/2a4545a1578', '--verbose']
[debug] Encodings: locale cp1252, fs mbcs, out cp850, pref cp1252
[debug] youtube-dl version 2021.12.17
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.19041
[debug] exe versions: ffmpeg 4.0.2, ffprobe 3.4.1
[debug] Proxy map: {}
[debug] Using fake IP <IP_ADDRESS> (GB) as X-Forwarded-For.
[ITV] 2a4545a1578: Downloading webpage
[ITV] 2a4545a1578: Downloading JSON metadata
ERROR: Unable to download JSON metadata: HTTP Error 404: Not Found (caused by HTTPError()); please report this issue on https://yt-dl.org/bug .
Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpupik7c6w\build\youtube_dl\extractor\common.py", line 634, in _request_webpage
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpupik7c6w\build\youtube_dl\YoutubeDL.py", line 2288, in urlopen
File "C:\Python\Python34\lib\urllib\request.py", line 470, in open
File "C:\Python\Python34\lib\urllib\request.py", line 580, in http_response
File "C:\Python\Python34\lib\urllib\request.py", line 508, in error
File "C:\Python\Python34\lib\urllib\request.py", line 442, in _call_chain
File "C:\Python\Python34\lib\urllib\request.py", line 588, in http_error_default
As well as the above programme the following are a small selection of other programmes with the same error trying to download.
youtube-dl https://www.itv.com/hub/good-morning-britain/2a3211a3218
youtube-dl https://www.itv.com/hub/coronation-street/1a0694a10537
youtube-dl https://www.itv.com/hub/loose-women/1a3173a3902
youtube-dl https://www.itv.com/hub/this-morning/2a6292a0758
youtube-dl https://www.itv.com/hub/itv-evening-news/2a4545a1579
I've just tried a different wi-fi network & it's the same.
I've noticed in the verbose it says I've got Python version 3.4.4 (CPython) but in Control Panel it says I've got Python 3.9.5 (64-bit). The reason why I was checking to see if I've got the latest version thinking that by getting the latest version might have an effect on the error.

There's a PR #30266 that is needed for ITV now (also use --user-agent "Mozilla/5.0" if the extractor hangs or times out  downloading the webpage), or use yt-dlp. If you were using either of the last two release versions, I'm surprised that it worked at all.
In either case https://www.itv.com/hub/itv-evening-news/2a4545a1579 works but https://www.itv.com/hub/itv-evening-news/2a4545a1578 gives 404, "No longer available" according to ITV.

Should probably not pay attention to any YT-DLP PR, as it doesnt work with YT-DLP either:
PS C:\> yt-dlp https://www.itv.com/hub/itv-evening-news/2a4545a1580
[ITV] 2a4545a1580: Downloading webpage
[ITV] 2a4545a1580: Downloading JSON metadata
ERROR: [ITV] 2a4545a1580: Unable to download JSON metadata: HTTP Error 403:
Forbidden (caused by <HTTPError 403: 'Forbidden'>); please report this issue on
https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version;
see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp
with the --verbose flag and include its complete output. (caused by <HTTPError
403: 'Forbidden'>); please report this issue on
https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version;
see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp
with the --verbose flag and include its complete output.

PS C:\> yt-dlp --version
2022.01.21

WFM in UK (yt-dlp 'https://www.itv.com/hub/itv-evening-news/2a4545a1580') without any specific UA.

Hi,
I've had 2 family birthdays this week including on Saturday so hence my delay in catching up with the latest.
I will first say thanks to dirkf for the help/contribution etc as well as anybody else who has done so as well.
I will say dirkf that I'm intelligent but lack knowledge & experience so when you mentioned above 'There's a PR #30266 that is needed for ITV now' I didn't know what it meant precisely. Same with some other things. Then when I saw someone had put yt-dlp before a programme I thought I would have to do that with the youtube-dl file that I've got which was the latest from 17-12-2021. Well that didn't work so I thought that there must be another application file called yt-dlp so obviously I searched for that on the site & downloaded it & popped it in front of another programme to download i.e. yt-dlp https://www.itv.com/hub/itv-news-weekend-teatime/2a4546a0629 & the download worked, fantastic. I didn't know of the existence of the file yt-dlp until now. Anyway the programme downloaded but it kept on stopping & starting. I thought it might be my internet connection but I didn't have any problems with speed etc when I used get_iplayer to do a download from the BBC. Anyway it did finish downloading eventually with one time out as can be seen in the screenshots I've uploaded. As I've only done the one download I don't know if the stopping & starting will be with all downloads from now on. At least I can download again thanks to you guys.

Just done some more downloads & they've taken a long time to complete because of the stopping & starting. I've submitted another screenshot so you can see how the 2nd download went.

yt-dlp is a forked version of yt-dl that only supports newer Python versions and has some further potential capabilities and dependencies.
As you're using yt-dlp, you should raise any problems in its tracker. Try to provide text logs (see, eg, https://www.laptopmag.com/articles/how-to-windows-10-command-prompt-copy) and use the --verbose/-v option. Having said that, yt-dlp's ITV extractor is essentially the same as the version in the yt-dl PR #30266.
Your timeout issues might be a problem with your internet connection, or with the ITV site, or possibly deliberate interference by the ITV site which might be alleviated by specifying a different user agent string, eg --user-agent "Mozilla/5.0" as suggested above.


symbol_in_winbar not work well

Description
symbol_in_winbar prints 'All servers of this buffer does not support textDocument/documentSymbol' when opening or switch between buffers whose server seems not support the LSP method.
Expected Behavior
Auto disable ``symbol_in_winbar` or the prints when server not support.
Actual Behavior

Details

require('lspsaga').init_lsp_saga({
  border_style = "rounded",
  saga_winblend = 5,
  move_in_saga = { prev = '<c-p>', next = '<c-n>' },
  diagnostic_header = { " ", " ", " ", "ﴞ " },
  show_diagnostic_source = true,
  code_action_icon = "💡",
  code_action_lightbulb = {
      enable = true,
      sign = true,
      sign_priority = 20,
      virtual_text = false,
  },
  max_preview_lines = 20,
  finder_action_keys = {
    open = "o",
    vsplit = "x",
    split = "s",
    tabe = "t",
    quit = "q",
    scroll_down = "<C-f>",
    scroll_up = "<C-b>", -- quit can be a table
  },
  code_action_keys = {
    quit = "q",
    exec = "<CR>",
  },
  rename_action_quit = "<C-c>",
  symbol_in_winbar = {
    in_custom = true,
  --   enable = false,
  --   separator = ' ',
  --   show_file = true,
  --   click_support = false,
  },
  -- show outline
  show_outline = {
    win_position = 'right',
    -- set the special filetype in there which in left like nvimtree neotree defx
    left_with = '',
    win_width = 30,
    auto_enter = true,
    auto_preview = true,
    virt_text = '┃',
    jump_key = 'o',
    -- auto refresh when change buffer
    auto_refresh = true,
  },
  server_filetype_map = { dartls = { "dart" } },
})

NVIM v0.8.0-dev-nightly-9-g1ef84547a
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: /Applications/Xcode_13.2.1.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNVIM_TS_HAS_SET_MATCH_LIMIT -DNVIM_TS_HAS_SET_ALLOCATOR -O2 -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Ws
hadow -Wconversion -Wdouble-promotion -Wmissing-noreturn -Wmissing-format-attribute -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=always -DINCLUDE_GENERATED_DECLARATIONS -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG
_LEVEL=3 -I/Users/runner/work/neovim/neovim/build/cmake.config -I/Users/runner/work/neovim/neovim/src -I/Users/runner/work/neovim/neovim/.deps/usr/include -I/Applications/Xcode_13.2.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.1.sdk/usr/include -I/Library/Framewo
rks/Mono.framework/Headers -I/Users/runner/work/neovim/neovim/build/src/nvim/auto -I/Users/runner/work/neovim/neovim/build/include
Compiled by<EMAIL_ADDRESS>

@changyiyao  I want to know  what's filetype in this buffer

@glepnir - I've been seeing this message frequently as well ("All servers ... text/documentSymbol") in various filetypes (most common lua and python). I decided to dig in on what was causing it and it turns to be null-ls. Basically, if I have a client attached to a null-lsprovided "server" [this message](https://github.com/glepnir/lspsaga.nvim/blob/7559a32a527c6d18b8e8ddaca64fd4ff960b001d/lua/lspsaga/symbolwinbar.lua#L163) is raised. I've managed to make it less disruptive by settingvim.notify = require("notify")(vianvim-notify`) but I'd love to understand what I'm doing wrong here.
Happy to open a new issue if that's preferred.

create a new issue for this.btw i don't use null lsp. so I need some useful informations


Support a Netty4 engine for HTTP routers

Finagle-6.36 introduces a usable netty4 backend for HTTP. linkerd users should
be able to opt-in to this new backend so that it may be introduced in a
controlled manner (until it's proven to be a suitable default).
Client and Server sections of the HTTP router configuration admit an engine
block that controls which HTTP implementation is used.

:star: 🚒  pending moving the changelog entry

⭐  Thanks for updating, looks good.


Bug: Warning: Attempted to read state from uninitialized service MACHINE_NAME. Make sure the service is started first.

Description
Hi,
Still I get this warning, I'm using xstate with react, I know the reason, probably in useInterpret the service starts in useEffect or somewhere before first render. because when I use interpret(machine).start() directly in constructor or in a function not after first mount, it works without any warning.
but don't you want to fix this?
Expected result
.
Actual result
.
Reproduction
.
Additional context
No response

Please always try to share a repro case in a runnable form - either by providing a git repository to clone or a codesandbox.

I'll try to reproduce it in a sandbox and share it here.

But this is what I'm talking about.
https://github.com/statelyai/xstate/blob/679a84eee468a9c4b359b68eff3e82d60aab6fe0/packages/xstate-react/src/useInterpret.ts#L138

No actual repro case has been provided here so it's hard for me to investigate this specific problem. If you manage to create a repro case, let me know - I can always reopen this issue.


[Cloud-Masthead]: Implement lazy load and DOM pruning from masthead v2 on cloud masthead

Related Ticket(s)
Resolves #10056
Description
Adds the performance enhancements that were implemented for Masthead v2 to the Cloud Masthead, specifically:

https://github.com/carbon-design-system/carbon-for-ibm-dotcom/pull/9595
https://github.com/carbon-design-system/carbon-for-ibm-dotcom/pull/9602

The first change (quoting @andy-blum here): Initializes the masthead-container with either the left-nav or the top-nav depending on the width of the viewport. Additionally swaps one for the other when the viewport crosses the 960px boundary. This should effectively cut the number of masthead nodes in half with very little other changes.
The second change (again quoting @andy-blum here): Currently the Masthead loads both the SideNav and Megamenu components at the same time, even if they haven't been opened yet. This causes the amount of nodes to increase considerably right away. In order to mitigate this, a fast solution is to dynamically load the required components only when the user has interacted with the menus.
This means that the mobile version wouldn't be loading the Megamenu, and the desktop wouldn't load SideNav until/if required.
Another optimization that was done ensures that the Megamenu component wouldn't get loaded into the DOM unless a user has clicked on the menu beforehand. Then and only then, the megamenu would be loaded in. Once the menu is closed, the component gets removed from the DOM to ensure the total node count doesn't shoot up.
Note that, due to the structure of the Masthead and Cloud Masthead, these changes are not entirely isolated to the Cloud Masthead alone. Specifically, the Masthead is responsible for mega menu rendering, thus the Masthead implements lazy loading of the megamenu which then is inherited by the Cloud Masthead.
Testing
Testing should cover regression tests on both the Masthead and Cloud Masthead components.
Changelog
New

Adds support for dynamic imports
Utliizes dynamic imports to lazy load left nav and megamenu scripts that are only necessary when the user expands the menu.
Only renders left nav custom elements when we're at the mobile break
Only renders megamenu custom elements when user expands the menu

I think this PR needs to be targeted to feat/masthead-v2. Currently the dds-masthead component doesn't implement any of the lazy loading/dom-pruning

I think this PR needs to be targeted to feat/masthead-v2. Currently the dds-masthead component doesn't implement any of the lazy loading/dom-pruning

My understanding was that the Cloud team is not using v2 yet, so they needed this implementation on main, to be released with the regular C4IBM release.

@m4olivei is correct. The current /cloud web segment on production is currently adopting v1 of the masthead code coming from the main branch and we're not looking to switch to v2 at the moment (pending approval from Cloud Stakeholders regarding v2 design updates). This PR will improve the performance of the existing Global and Cloud Masthead v1.
We might see some merge conflicts, once we update our feat/masthead-v2 with main.

@kennylam @annawen1 Can help take a look at this PR?


Wallet not syncing [macOS]

Hi,
I'm coming here after looking at this reddit post : https://www.reddit.com/r/nanocurrency/comments/8j3j26/nano_classic_wallet_v13_for_windows_not/ .
I'm running on macOS High Sierra 10.13.1, 2.3 GhZ i5 with 8 GB RAM.
My wallet worked fine from December to March this year.
I got v13 yesterday and got it syncing for 24h+ hours but it wouldn't sync at all.
I attached the logs, hope it helps.
log_2018-05-13_19-21-16.76.log
log_2018-05-13_20-00-17.77.log
log_2018-05-13_20-39-19.78.log
log_2018-05-13_21-14-53.79.log
log_2018-05-14_08-52-17.80.log

@pscott what's your block counts?

That's what I thought, but is has literally been more than 24hours haha

Hello,
I'm the one who made the reddit thread mentioned above. I have the same issue as pscott but on Windows and from the thread you can see that there are also other people with it and all at about the same level of synching.
My block count was 7744627 (1456515) when I gave up and pulled a snapshot.
So it seems like there is really something wrong at that block count.

Same from here: https://github.com/nanocurrency/raiblocks/issues/823

Interesting, also at 7.7 million blocks... I really wonder what happened at this point...

I feel like it has something to do with the release of the canary block. 7.7 million blocks were reached on April 11. Exactly when the canary block was released.

I was waiting for two days for v13.0 to synchronize (on Ubuntu), then gave up and ran v12.1 in parallel on another Ubuntu machine - it synchronized from scratch in just 1 hour and 10 minutes.
v13.0 is still stuck at "7746122 (1518204)".

Same problem with v13.0 node.
Sync stuck at 7,746,299, log full of "Block ... was republished to peers" and "Broadcasting confirm req for block ... to 8 representatives" with same blocks, for example 6872CBA6C17A89AA0C88D1B208A80A8F3D1108F4469EC1BF4AC0D4B9CBAB8BCD.
Also log contains lines like:
[2018-05-15 18:23:24.577331]: 338 blocks have been unconfirmed averaging 1049 announcements

And 9k log lines later
[2018-05-15 18:29:17.635485]: 338 blocks have been unconfirmed averaging 1071 announcements

It seems that node trying to re-confirm same blocks again and again.
Using a snapshot is a wrong way IMHO - blocklattice must be verifiable and sync'able from the ground up. I'll try v12.1...

@justdmitry Is that Hash correct? I can't find that block in any block explorer...

@Nanoraii Here is part of my log, between "338 blocks have been unconfirmed averaging...". I think you will find all 338 blocks here.
log_2018-05-15_18-23-08.22-3.log

By the way, I backup'ed data-files, installed v12.1 node and started it with v13 database. After 3-5 minutes later it moved to 7,778,986, after 20min - to 7,841,421.
It seems that v13 have some "infinite confirm loop" that v12.1 does not.
Here is log from v12.1: log_2018-05-15_19-06-20.25-2.log. I can't find here any block from v13 stuck-log...

curl -d '{"action":"unchecked_get", "hash":"6872CBA6C17A89AA0C88D1B208A80A8F3D1108F4469EC1BF4AC0D4B9CBAB8BCD"}' localhost:7076

{ "contents": "{\n    "type": "receive",\n    "previous": "12F1F4C94C61A632E7B48548C3E6740E9808CF7EEBC50F4361011D1B99616384",\n    "source": "A5466412D80BB689B90864C559E46EC1D69438EC301D99F9590331EB81D17CBD",\n    "work": "119258f02ed5568c",\n    "signature": "4F8BE5E92E4254FB45BD41961A7D15A0E7B188069E132961B204D5A6739E0E1E20668D739AE0663528FF16EBBECC137B6D58D9D6BA416914481B4C6DAD8B8C0D"\n}\n" }

https://www.nanode.co/block/A5466412D80BB689B90864C559E46EC1D69438EC301D99F9590331EB81D17CBD

curl -d '{"action":"unchecked_get", "hash":"12F1F4C94C61A632E7B48548C3E6740E9808CF7EEBC50F4361011D1B99616384"}' localhost:7076

{ "error": "Unchecked block not found" }

curl -d '{"action":"block", "hash":"A5466412D80BB689B90864C559E46EC1D69438EC301D99F9590331EB81D17CBD"}' localhost:7076

{  "contents": "{\n    "type": "send",\n    "previous": "9E4776C402CAA1C6986B36BFFA25C0B66D1EBF552CD25AEFA739F42D218646EF",\n    "destination": "xrb_1tig1rio7iskejqgy6ap75rima35f9mexjazdqqquthmyu48118jiewny7zo",\n    "balance": "00000000000000000000000000000000",\n    "work": "e6240bcc83cc666f",\n    "signature": "F515D40CCC45C34B9DAC9B0628D7B9AE9DDB0D3B4FA979EF5903D19A9295F4749AE630B59E6023D04D7C2A1A7969A35CA56546302B8B2C18C44AE13703C18B0A"\n}\n" }

https://www.nanode.co/account/xrb_1tig1rio7iskejqgy6ap75rima35f9mexjazdqqquthmyu48118jiewny7zo - OKex Rep

I guess there were some forks in the past, and blocks are still "alive".

Not sure if this would help, but I appeared to get this or a similar issue on the beta nano network. My node was stuck at about 9.9k blocks and wouldn't sync up. I was also trying to create and process a new state 'open' block from this same node and for some reason my blocks were disappearing.
I took a copy of the data.ldb, a relevant log file, and have a copy of the rai_node exec for the version that I was running that was having issues (note: it was a git master compile probably around June30). I would have no issue sending this to the team if it would help?
BTW I "fixed" it by deleting the data.ldb, recompiled rai_node from latest git master, and it sync'd up quick and fine, so it didn't re-occur again. Also, after doing and it syncing, I re-ran the same RPC command that was making my state 'open' block vanish previously, and it now works fine.

We made many improvements in V17.0 related to bootstrapping, such as lazy bootstrapping and better handling of forks during bootstrapping.  Please re-try with V17.0 and re-open this ticket if it remains an issue.  Thanks !


node clusterrole does have permissions to read secrets.

Expected Behavior
When configuring a BGPPeer with has a password, I would expect calico-node to be able to read the secretref.

Current Behavior

Calico-node does not have permission to list or get secrets, and as such it logs spew the following lines:
W0610 00:16:46.957663      69 reflector.go:324] pkg/mod/k8s.io/client-go@v0.23.3/tools/cache/reflector.go:167: failed to list *v1.Secret: secrets "bgp-password" is forbidden: User "system:serviceaccount:calico-system:calico-node" cannot list resource "secrets" in API group "" in the namespace "calico-system"
E0610 00:16:46.957705      69 reflector.go:138] pkg/mod/k8s.io/client-go@v0.23.3/tools/cache/reflector.go:167: Failed to watch *v1.Secret: failed to list *v1.Secret: secrets "bgp-password" is forbidden: User "system:serviceaccount:calico-system:calico-node" cannot list resource "secrets" in API group "" in the namespace "calico-system"

Possible Solution
Add the ability to clusterrole calcio-node to be able to list and read secrets.
https://github.com/tigera/operator/blob/fc4f3d8f2c6c44ccf6b6b93623972dd2b45db91e/pkg/render/node.go#L282
Steps to Reproduce (for bugs)

Create a BGP Peer like the following:

---
apiVersion: projectcalico.org/v3
kind: BGPPeer
metadata:
  name: my-global-peer4
spec:
  peerIP: <IP_ADDRESS>
  asNumber: 64515
  sourceAddress: UseNodeIP
  password:
    secretKeyRef:
      key: password
      name: vultr-bgp-password

Watch the logs show it fail to be able to read the secret.

Context

Your Environment

Operating System and version:
Link to your project (optional):

Hi @georgyo , we faced with same issue. I've added appropriate PR to fix it. please vote - https://github.com/tigera/operator/pull/2107


Update to tree-sitter 0.23

Tree-sitter released version 0.23 recently. This contains a breaking, but ultimately very good change to how parser bindings work (https://github.com/tree-sitter/tree-sitter/pull/3069). The TLDR of that change is that parsers do not depend on tree-sitter anymore, but instead on a shard (and supposedly very stable) tree-sitter-language crate. As a result, clients are free to chose their tree-sitter version as the parser ABI is supported. Library and parser versions are less tighly coupled, and it should no longer be necessary to move all the parsers to the next tree-sitter version in lock-step to be able to upgrade the library.
Most of the changes in this PR are from running tree-sitter generate. I'll add comments on other changes I did to explain why I thought they are necessary, or where I'm not sure I did it correctly.

Thanks for doing this! Happy to hear about the changes in how versioning is handled.
Please add a new commend once this follows an approach that doesn't check in generated files so that I know it's ready to review further.

Thanks! I think a bump to 0.6.0 is correct here because of the change in underlying tree-sitter version — I think of that as an exported dependency (although maybe not anymore!). You’re doing it the right way with manual changes to those files.

I'm currently verifying the bindings by running their tests. I'll let you know when I'm done with that--need to install all GBs of XCode first...

Binding tests work okay for me!

Thank you for approving and merging this one @alex-pinkus. Do you think it would be possible to do a new release soon as well?

The release to crates.io and npm happened automatically when I pushed this change. Do you also need a new release tag? I’m traveling right now so I won’t be able to get that immediately.

The release to crates.io and npm happened automatically when I pushed this change. Do you also need a new release tag? I’m traveling right now so I won’t be able to get that immediately.

Oh, great! No, I need the crate actually, but only looked at the repo for the latest release. Thanks for dealing with all of this so quickly 🙇🏻


Short solution needed: "How to indent line" (vim)

Please help us write most modern and shortest code solution for this issue:
How to indent line (technology: vim)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments to make solution explained.
Link to this issue in comments of pull request.

How to indent line forward


cloudskiff/driftctl:latest hub docker image doesn't include the latest stable

Description
Context: A user reported a crash on Docker latest image.
Our latest released version is v0.1.1 and it's working great (cloudskiff/driftctl:v0.1.1)
But our "latest" tagged docker hub includes an older dev release:
$ ./bin/driftctl_linux_amd64 version
v0.1.0-6-gbb52629-dev

Environment

OS: current docker hub latest
driftctl version: n/a

How to reproduce
use the docker hub cloudskiff/driftctl:latest release
Possible Solution
Update the release pipeline for latest to match the real latest
Additional context
Originally a user reported an issue like this one:
docker: Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: exec: "scan": executable file not found in $PATH: unknown.
ERRO[0001] error waiting for container: context canceled

Multiple issues here.

docker hub auto build was still listening to the master branch (master was renamed main 10+ days ago)
mapping latest to our unstable unreleased build may not be the best strategy for our users stability

Actions taken for now:

removed auto build for latest tag
pushed v0.1.1 as latest


Errors in Safari Private Browsing.

Hello,
I'm having trouble in using Firebase Auth functions when I'm working on Safari Private Browsing. This is the error that is thrown:
[Error] EXCEPTION: Error: This operation is not supported in the environment this application is running on. "location.protocol" must be http or https and web storage must be enabled.
    logError (main.bundle.js:62184)
    logGroup (main.bundle.js:62194)
    call (main.bundle.js:55552)
    next (main.bundle.js:38677)
    (anonymous function) (main.bundle.js:40713)
    __tryOrUnsub (main.bundle.js:1383)
    next (main.bundle.js:1332)
    _next (main.bundle.js:1282)
    next (main.bundle.js:1246)
    _finalNext (main.bundle.js:4960)
    _next (main.bundle.js:4952)
    next (main.bundle.js:4909)
    emit (main.bundle.js:40701)
    onError (main.bundle.js:41440)
    onHandleError (main.bundle.js:60279)
    handleError (main.bundle.js:118538)
    runTask (main.bundle.js:118470)
    invoke (main.bundle.js:118634)
[Error] Error: This operation is not supported in the environment this application is running on. "location.protocol" must be http or https and web storage must be enabled.
    __tryOrUnsub (main.bundle.js:1387)
    next (main.bundle.js:1332)
    _next (main.bundle.js:1282)
    next (main.bundle.js:1246)
    _finalNext (main.bundle.js:4960)
    _next (main.bundle.js:4952)
    next (main.bundle.js:4909)
    emit (main.bundle.js:40701)
    onError (main.bundle.js:41440)
    onHandleError (main.bundle.js:60279)
    handleError (main.bundle.js:118538)
    runTask (main.bundle.js:118470)
    invoke (main.bundle.js:118634)

After a bit of searching on this issue, I found, these:
https://github.com/firebase/firebaseui-web/issues/51
https://groups.google.com/forum/#!topic/firebase-talk/_uRh7jkHfZ0
https://github.com/angular/angularfire2/issues/279
Looking at #279, that is for Ionic where file protocol is used. But my project is a web app.
Is there any workaround on this?

@dowsanjack Give me some time to reproduce, thanks for reporting it :)

@davideast ,  do you have any updates on this ?
I am facing the same issue and could not find any solutions.

AngularFire2 no longer provides these auth methods. If this problem still persists open a question on Stackoverflow for Firebase Authentication.


fix: get-code-button malfunction

🛠 Closes #73

👨💻 Changes proposed

Fixed copy to clipboard not working correctly

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers
The get code button was not working, i.e. not copying the first time it was clicked because of an event
listener was being added in the first click, and it made the copy to clipboard code unreachable
the first time. Removing it fixed the bug.

📷 Screenshots

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


Unable to apply average to data when using footprint_data_merge

At the moment there is no way to apply an explicit average to the obs data timeseries when merging with the footprints. This can be done when creating the separate data object using the get_obs_surface() function but this is not called when using footprint_data_merge() as present.
This may link to Issue #42, as this may be something we incorporate into a new workflow rather than apply separately to the current code.

For the moment we could just add averaging until the work discussed in #42  is done?

Closing this due to the work being covered by #42 .


Unexpected CFBundleExcutable key

After delete the CFBundleExcutable key, I can upload my ipa successfully.

Deleted, thanks!


the program cannot find the path of the model

it give me a error that there was nothing or the path is non existent, i tried diffent path to like /user/lollo/stereopis-anithing/model/dephanything... and this work if i use cd in terminal but the program return me this error "Exception in thread Thread-2:
Traceback (most recent call last):
File "/Users/lollo/.pyenv/versions/3.8.20/lib/python3.8/threading.py", line 932, in _bootstrap_inner
self.run()
File "run.py", line 305, in run
model = ct.models.MLModel(model_path, compute_units=u)
File "/Users/lollo/.pyenv/versions/3.8.20/lib/python3.8/site-packages/coremltools/models/model.py", line 403, in init
self.proxy, self._spec, self._framework_error = self._get_proxy_and_spec(
File "/Users/lollo/.pyenv/versions/3.8.20/lib/python3.8/site-packages/coremltools/models/model.py", line 465, in _get_proxy_and_spec
specification = _load_spec(filename)
File "/Users/lollo/.pyenv/versions/3.8.20/lib/python3.8/site-packages/coremltools/models/utils.py", line 255, in load_spec
with open(specfile, "rb") as f:
FileNotFoundError: [Errno 2] No such file or directory: '/model/model/depth_anything_v2_vits2.mlpackage'
"

you didn't need specific the model path, just run command in "stereopis-anithing" floder.
python3 run.py

In case you want to use your own model, you can download the new code and use the new model with
python3 run.py -m  "/user/lollo/stereopis-anithing/model/depth_anything_v2_vits2.mlpackage"

you didn't need specify a model path, just run command in "stereopis-anithing" folder.
python3 run.py

In case you want to use your own model, you can download the new code and use the new model with
python3 run.py -m  "/user/lollo/stereopis-anithing/model/depth_anything_v2_vits2.mlpackage"

I tried run the the program from the folder, maybe is because i am using venv? Or because i used a tool to downgrade python to 3.8 because using the latest version of python with pip tell me that all version of torch and torchvision are not compatible?

@lollo1252 It look like it only couldn't find the AI model. Could you try the latest run.py with or without "-m".


runCmd: / bypassNpmRun: true

It should be a boolean rather than a string (perhaps a special-case command string is ok), and also consider renaming to bypassNpmRun so that the api is more like that of gulp-npm-run.

Name it withoutNpmRun - reads better / makes more sense.


Align repo to template repo

Align this repo with the template repo

remove old LICENSE.txt?

remove old LICENSE.txt?

sure. done. now it looks like LICENSE.txt was renamed but that's close enough


Running a queue task async when called from a Meteor Method

I am trying to use power-queue to run one async task at the end of my Meteor Method. It is running, but the meteor Method is treating it like a synchronous function. Any idea how I can format these queue calls so that Meteor doesn't wait for them to complete before returning the Meteor method call?
http://stackoverflow.com/questions/28436137/how-can-i-run-a-task-inside-a-meteor-method-without-waiting-for-it-to-complete

theres a flag for making Meteor methods non blocking - but PQ is used for http uploads and allow can allow multiple chunks files at a time - this is throttled (I'm not sure about the default config - it might be allow only one chunk at a time - but really, this is very flexible)

Ok, I know I can use the this.unblock() before calling the Meteor method, but that just makes the whole Meteor method call non-blocking. I'm really trying to find something that I can just run one task and not wait for it to finish before returning from my meteor method. Can Power-queue do that?

@c316 I know this is an old issue, but this may help someone else.
Considering the method doesn't need to wait for the result of the task, I'd be unlinking the actions. The method could publishing an event that a controller receives and adds the a task to the queue. The method should return without needing to be unblocked


Fix dockerfile build

As discussed offline cc @BenjaminBossan @muellerzr

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

I can confirm this leads to successfully building the docker image: https://github.com/huggingface/peft/actions/runs/6970869476/job/18969759804


How to Configure LGSVL Versions Prior to 2021.1 for Seamless SORA-SVL Communication

Hi Yuqi,
Thank you for your great work. I need some guidance on configuring versions of LGSVL prior to 2021.1. I'm currently using version 2020.1. However, when I click on 'open browser', it redirects to 'https://www.lgsvlsimulator.com/', suggesting that it's unable to establish communication with SORA-SVL. Can you advise on this?
here is my config.yml
hostname: "localhost"
port: 8080
headless: false
read_only: false
api_hostname: "localhost"
api_port: 8181
Thank you in advance.

Hi @zhang-junqi
Unfortunately I have no experience at all with versions prior to 2021.03
I’m currently traveling and cannot help you much. You may need to take a look at SVL’s source code to figure this out.


add a patch to fix the python issue29097

it bug will happen when using python 3.6 to python 3.7 just on windows.

For more detailed information about  python issue29097, please refer to the following link: https://bugs.python.org/issue29097

Codecov Report

Merging #206 (995daa2) into main (4ab57be) will decrease coverage by 0.06%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##             main     #206      +/-   ##
==========================================
- Coverage   81.54%   81.49%   -0.06%
==========================================
  Files          20       20
  Lines        2585     2588       +3
==========================================
+ Hits         2108     2109       +1
- Misses        477      479       +2

Files Changed
Coverage Δ

taos/field.py
80.12% <50.00%> (-0.89%)
:arrow_down:

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


test: HTTP weirdness

First reported in https://github.com/ipfs/js-ipfs-api/pull/648
4) 'deal with HTTP weirdness' tests does not crash if no content-type header is provided:
     Uncaught AssertionError: expected [Error: read ECONNRESET] to not exist
      at ipfsAPI.config.replace (test\request-api.spec.js:28:28)

This is just a work around and does not fix the underlying problem.  I've changed the test to use id instead of config.replace and the test passes.
@diasdavid I'm think the ECONNRESET could be coming from push stream not being read by the server.  But perhaps it something else.  More eyeballs might help.  I think it's more of a timing/race issue than a specific windows issue

Fixed it by consuming the entire request, before responding.

Interesting, this looks like a Node.js issue and not a js-ipfs-api. Thanks @richardschneider


Make SSKR generation flow less confusing

Describe the bug
When opening the app, I'm presented with two choices:

Check BIP39 recovery phrase
Check SSKR recovery phrase

My intent is to generate SSKR shards to backup my secret key.
I needed to read the README.md to understand that after entering my BIP39 key, I will be able to generate SSKR shards.
Expected behavior
I would like to see a menu item called "Generate SSKR recovery shards".
I would like to not have to type my BIP39 seed (after all, it's supposed to already be inside the device)

Hi again @clouedoc

I would like to not have to type my BIP39 seed (after all, it's supposed to already be inside the device)

Unfortunately this is how the app has to work.
Even though a seed is stored on a device, due to the security of the Ledger devices apps have no way of accessing the seed. This is actually a good thing.
To work around this security feature the app gets a user to prove that they know the seed. It uses a little trick to make sure that the user supplied seed can derive the same address as the onboarded seed. If they match then the supplied seed is correct. Ledger's own "Recovery Check" app uses the exact same technique.
The flow diagram here attempts to explain that a user must first supply the correct BIP39 phrase before they will be offered the option of generating the SSKR shares:
https://github.com/aido/app-seed-tool?tab=readme-ov-file#ledger-nano-application-menus

Also, when app-seed-tool is released for installation via Ledger Live there will be a blog post written explaining the origins and purpose of the app.
This Ledger blog post has been written but not published yet and it will contain some details on how to use the app too.


Objcopy executable path not found?

I've been trying to use objcopy from the existing toolchains generated through this system. I'm a bit surprised to see that the path for objcopy is just empty... Am I doing something wrong? I want to create a simple rule to make a binary from the generated elf... Would love alternate suggestions:
def _impl(ctx):
    toolchain = find_cc_toolchain(ctx)
    print(toolchain.cc.objdump_executable)
    print(toolchain.cc.objcopy_executable)

gen_binary = rule(
    implementation = _impl,
    toolchains = [
    ·   "@rules_cc//cc:toolchain_type",
    ],
    attrs = {
    ·   "_cc_toolchain": attr.label(
    ·   ·   default = Label(
    ·   ·   ·   "@rules_cc//cc:current_cc_toolchain",
    ·   ·   ),
    ·   ),
    ·   "src": attr.label(allow_single_file = True),
    },
    outputs = {
    ·   "elf": "%{name}.elf",
    ·   "bin": "%{name}.bin",
    },
)

With the command:
bazel build //bootloader --platforms=@bazel_embedded//platforms:cortex_m4_fpu

and I get the following:
DEBUG: /.../project/toolchains/platforms.bzl:29:10: external/bazel_embedded/toolchains/gcc_arm_none_eabi/gcc_wrappers/nix/objdump
DEBUG: /.../project/toolchains/platforms.bzl:30:10:  <--- This is the objcopy print statement

Hmm, I mustn't have defined the path for objcopy. So this is definitely a bug. However, I'd recommend using this workaround for now.
Here is how I use bazel-embedded to generate separate elfs/binaries.
The way that I do things is just to use the elf, or if I need the raw binary I just use the stripped target e.g. If I have the following build definition;
cc_binary(
    name = "main",
    srcs = ["main.cc"],
)

To get the elf file I run something like this (it won't have the .elf extension unless you name the cc_binary 'main.elf');
bazel build //:main --platforms=@bazel_embedded//platforms:cortex_m4_fpu
However, if I want the binary file I use the stripped sub-target which is configured to strip all ELF sections leaving the binary e.g.
bazel build //:main.stripped --platforms=@bazel_embedded//platforms:cortex_m4_fpu
You can use strip or objcopy to achieve the same result in this case.

I think the main concern is keeping the build and debug symbols in the same step. If the binary is generated in a separate build step than the elf, there may be issues when going to debug via gdb. I'd rather have this copy step. I think fixing the definition here is probably the right way to do it. I'll see if I can submit a fix.

Yeah technically they are preserved e.g. it already looks like elf->stripped. So if you go elf(with embedded debug dwarf section)->stripped it'll still produce the same binary minus the elf headers and dwarf sections. But in any case that PR looks fine, and is fixing what I would consider a bug.


ceph: 14.2.4 -> 14.2.5

Motivation for this change
Fixes a critical integrity bug n 14.2.3 and 14.2.4. Adds newly required deps on libnl and libcap_ng.
This needs backporting to 19.09, but I think we should also backport the various fixes to rocksdb etc. before doing so. I can author that.
WIP while my poor laptop chugs away at building it...
Things done

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

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

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

Notify maintainers
cc @

Ready for review. I'll hopefully be able to deploy this to a test cluster soonish, but I think it's good from testing in VMs.
There's a critical bug in the current 14.2.4 version which may cause OSD corruption when bluestore WALs are on separate devices.
There are other, smaller changes to deps and behaviour (specifically more health checks) that required tests to be tuned slightly.
Note that the multi node test currently fails because of a regression in the python test suite which causes files to no longer be shared among VMs in /tmp/shared. Reverting ef5bc381f969205493897b121ce36ecd7bdc1974 causes the ceph test to succeed, so I think we're good from this side.

Oh, and I'll probably set up a full backport of floklis fixes to ceph/rocksdb and this, if this passes review, since we really need to get this version in stable as well, and the changes should be safe. :)

cc @7c6f434c w.r.t /tmp/shared.

Hm, maybe we should split the shared reference into internal_shared and external_shared then?


Use memory mapping when filling data by default

TODO: Write some memory tracking tests!!!

@e-koch it's worth having another look at this one; using memmap for every slice resulted in a huge slowdown, so I think that's a bad idea, but the memory testing is a real thing.
I'm considering having use_memmap set to False by default for _get_filled_data, rather than trying to "cleverly" select based on cube size, since the latter is long-term a recipe for disaster.

I'm finally looking at this again... and the failures appear to be that there are some version combinations where memory isn't allocated.

Maybe you're right that the memory tracker is looking in the wrong place


Trim job suffix to extract out cron job name for workload metadata

Please provide a description for what this PR is for.
Fixes https://github.com/istio/istio/issues/24058
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

/test all

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
d5c02efd3173e4bfc52206da3b4e8d6060af0f2d
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
767b2f373c3f8ddbedb8d01edb4a3406cb9bd3a8
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
d93daa311d31b35d337078fee52c94051e5e6dff
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
d93daa311d31b35d337078fee52c94051e5e6dff
link
/test release-notes_istio

integ-security-k8s-tests_istio
d93daa311d31b35d337078fee52c94051e5e6dff
link
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

Yeah, I've confirmed the fix in a real set up. I need to check the manual injection logic a bit, but is it using a completely different code path to handle metadata env var?

Looks like manual injection needs better handling on newer cronjob api version, other than that it looks like the logic handles it pretty well: https://github.com/istio/istio/blob/10d12b824f13ef53217749d1e19c553e6586bc04/pkg/kube/inject/inject.go#L714

Has this been backported to 1.6 ?


A number of QOL improvements in preparation for real and WRF tasks

This PR introduces a number of QOL improvements in error checking, runtime control, and test.yaml defaults

Updates to test.yaml

Change default values to be more reasonable for AWS cluster testing
Add new option "exists" that can specify different options for dealing with existing working directories for each task

"die" (default): previous behavior, script will die with an exception
"skip": skip the task for which there is an existing working directory
"remove": remove the working directory and create a fresh one

Allow local_data to be fully removed rather than needing to specify it as an empty string to pull remote data

Automatically create top-level workdir (this was previous behavior, got changed accidentally)
Save full config dictionary to runinfo; this is useful for debugging
Remove some bad lines and fix misleading messages
Populate and use stub "symlink" function that has behavior of os.symlink, except returns an exception if target does not exist
Raise exception in ungrib if no input files are found

Expected Differences

[ ] Do these changes modify the system output in any way? No

Pull Request Testing

[ ] Describe testing already performed for these changes:

[ ] Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:

Instructions for testing on Cheyenne will be provided in comment

[ ] Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [No]

[ ] Do these changes include sufficient testing updates? [No]

[ ] Will this PR result in changes to the test suite? [No]

[ ] Please complete this pull request review by [2022-09-22].

Pull Request Checklist

[ ] Review the source issue metadata (labels, project, and milestone).
[ ] Complete the PR definition above.
[ ] Ensure the PR title matches the feature or bugfix branch name.
[ ] Define the PR metadata, as permissions allow.
Select: Reviewer(s)
Select: Project
Select: Milestone as the version that will include these changes
Select: Development to link to the original development issue.
[ ] After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
[ ] Close the linked issue and delete your feature or bugfix branch from GitHub.

Testing details:
Setup
Clone and set up code on Cheyenne
git clone git@github.com:NCAR/wrfcloud -b feature/QOL_improvements
module load conda
conda activate /glade/p/ral/jntp/CCproject/wrfcloud/conda/wrfcloud
export PYTHONPATH=`pwd`/wrfcloud/python/src
cd wrfcloud/python/src/wrfcloud/runtime/
cp /glade/p/ral/jntp/CCproject/wrfcloud/wpsprd/geo_em.d01.nc configurations/test/

Modify test.yml for Cheyenne values
    wpscodedir: /glade/p/ral/jntp/CCproject/wrfcloud/WPSV4.4_intel_serial_large-file/
    wrfcodedir: /glade/p/ral/jntp/CCproject/wrfcloud/WRFV4.4_intel_dmpar/
...
    workdir: /glade/scratch/your_name_here
...
    local_data: /glade/p/ral/jntp/CCproject/wrfcloud/input_data/gfs/2022060100/gfs.t00z.pgrb2.0p25.f*

Run the test case, should be successful through metgrid
./run.py
{"time": "2022-09-16 15:45:23.000 +0000", "message": "Initializing production environment", "appName": "no_name", "className": "NoClass", "level": "INFO "}
{"time": "2022-09-16 15:45:23.000 +0000", "message": "Starting new run \"test\"", "appName": "wrfcloud-production", "className": "NoClass", "level": "INFO "}
...
...
2022-09-16 15:49:10.000 +0000 - INFO  - wrfcloud-test - Wrf - Setting up WRF for "test"
2022-09-16 15:49:10.000 +0000 - WARN  - wrfcloud-test - Wrf - wrfcloud.runtime.wrf is not fully implemented yet!
2022-09-16 15:49:10.000 +0000 - INFO  - wrfcloud-test - PostProc - Setting up post-processing for "test"
2022-09-16 15:49:10.000 +0000 - WARN  - wrfcloud-test - PostProc - wrfcloud.runtime.postproc isn't fully implemented yet!

Test 1
Run the test case again, should fail due to existing workdir
./run.py
{"time": "2022-09-16 15:50:48.000 +0000", "message": "Initializing production environment", "appName": "no_name", "className": "NoClass", "level": "INFO "}
{"time": "2022-09-16 15:50:48.000 +0000", "message": "Starting new run \"test\"", "appName": "wrfcloud-production", "className": "NoClass", "level": "INFO "}
{"time": "2022-09-16 15:50:48.000 +0000", "message": "Could not read config file run.yml, trying test.yml", "appName": "wrfcloud-production", "className": "RunInfo", "level": "WARN "}
{"time": "2022-09-16 15:50:48.000 +0000", "message": "Setting up working directory /glade/scratch/kavulich/wrfcloud_PR_67_test", "appName": "wrfcloud-production", "className": "NoClass", "level": "INFO "}
{"time": "2022-09-16 15:50:48.000 +0000", "message": "Initializing test environment", "appName": "wrfcloud-production", "className": "NoClass", "level": "INFO "}
2022-09-16 15:50:48.000 +0000 - INFO  - wrfcloud-test - Ungrib - Setting up ungrib for "test"
2022-09-16 15:50:48.000 +0000 - FATAL - wrfcloud-test - NoClass - Directory already exists:
                 /glade/scratch/kavulich/wrfcloud_PR_67_test/ungrib
                 Move or remove this directory before continuing.
Traceback (most recent call last):
  File "/glade/scratch/kavulich/wrfcloud/PR_67/wrfcloud/python/src/wrfcloud/runtime/./run.py", line 73, in <module>
    main()
  File "/glade/scratch/kavulich/wrfcloud/PR_67/wrfcloud/python/src/wrfcloud/runtime/./run.py", line 48, in main
    ungrib.start()
  File "/glade/scratch/kavulich/wrfcloud/PR_67/wrfcloud/python/src/wrfcloud/runtime/__init__.py", line 89, in start
    self.success = self.run()
  File "/glade/scratch/kavulich/wrfcloud/PR_67/wrfcloud/python/src/wrfcloud/runtime/ungrib.py", line 87, in run
    action = check_wd_exist(self.runinfo.exists,self.runinfo.ungribdir)
  File "/glade/scratch/kavulich/wrfcloud/PR_67/wrfcloud/python/src/wrfcloud/runtime/tools/check_wd_exist.py", line 33, in check_wd_exist
    raise FileExistsError(msg1 + msg2)
FileExistsError: Directory already exists:
                 /glade/scratch/kavulich/wrfcloud_PR_67_test/ungrib
                 Move or remove this directory before continuing.

Test 2
Modify test.yml to set exists: remove and re-run ./run.py. You should now observe that the existing working directories are automatically removed and the tasks re-run.
vi test.yml
./run.py
...
...
2022-09-16 15:54:36.000 +0000 - INFO  - wrfcloud-test - Ungrib - Setting up ungrib for "test"
2022-09-16 15:54:36.000 +0000 - WARN  - wrfcloud-test - NoClass - Directory already exists:
                 /glade/scratch/kavulich/wrfcloud_PR_67_test/ungrib
                 Config option set to remove existing directory.
2022-09-16 15:54:36.000 +0000 - DEBUG - wrfcloud-test - Ungrib - Creating WPS namelist
...
...
2022-09-16 15:56:35.000 +0000 - INFO  - wrfcloud-test - MetGrid - Setting up metgrid for "test"
2022-09-16 15:56:35.000 +0000 - WARN  - wrfcloud-test - NoClass - Directory already exists:
                 /glade/scratch/kavulich/wrfcloud_PR_67_test/metgrid
                 Config option set to remove existing directory.
2022-09-16 15:56:35.000 +0000 - DEBUG - wrfcloud-test - MetGrid - Creating WPS namelist
...

Test 3
Edit test.yml to set exists: skip, manually remove metgrid directory, and re-run ./run.py. You should observe that the ungrib task is skipped and the old workdir used for the next step (metgrid).
vi test.yml
rm -rf /glade/scratch/your_name_here/metgrid
./run.py
...
...
2022-09-16 16:01:06.000 +0000 - INFO  - wrfcloud-test - Ungrib - Setting up ungrib for "test"
2022-09-16 16:01:06.000 +0000 - WARN  - wrfcloud-test - NoClass - Directory already exists:
                 /glade/scratch/kavulich/wrfcloud_PR_67_test/ungrib
                 Config option set to skip task, returning to main program.
2022-09-16 16:01:06.000 +0000 - INFO  - wrfcloud-test - MetGrid - Setting up metgrid for "test"
...
...

Test 4
Now edit test.yml to set exists: remove and modify the value of local_data to some junk value that does not correspond to input files (like removing the wildcard *), and re-run ./run.py. You should observe that the run fails gracefully with the message that no input data was found, whereas the current version of develop would run through all the tasks with no error message.
vi test.yml
./run.py
...
...
2022-09-16 16:10:30.000 +0000 - ERROR - wrfcloud-test - Ungrib - List of input files is empty; check configuration
Traceback (most recent call last):
  File "/glade/scratch/kavulich/wrfcloud/PR_67/wrfcloud/python/src/wrfcloud/runtime/./run.py", line 73, in <module>
    main()
  File "/glade/scratch/kavulich/wrfcloud/PR_67/wrfcloud/python/src/wrfcloud/runtime/./run.py", line 48, in main
    ungrib.start()
  File "/glade/scratch/kavulich/wrfcloud/PR_67/wrfcloud/python/src/wrfcloud/runtime/__init__.py", line 89, in start
    self.success = self.run()
  File "/glade/scratch/kavulich/wrfcloud/PR_67/wrfcloud/python/src/wrfcloud/runtime/ungrib.py", line 98, in run
    self.get_files()
  File "/glade/scratch/kavulich/wrfcloud/PR_67/wrfcloud/python/src/wrfcloud/runtime/ungrib.py", line 56, in get_files
    raise FileNotFoundError('No input files found')
FileNotFoundError: No input files found

Test 5
Now edit test.yml to delete or comment the local_data line, and re-run ./run.py. You should observe a successful run that retrieves remote data, whereas the current version of develop would fail to read the local_data variable.
vi test.yml
./run.py
...
...
2022-09-16 16:11:21.000 +0000 - DEBUG - wrfcloud-test - Ungrib - Getting ungrib input files
2022-09-16 16:11:21.000 +0000 - DEBUG - wrfcloud-test - Ungrib - "local_data" not set; getting GRIB file(s) from remote source
2022-09-16 16:11:21.000 +0000 - DEBUG - wrfcloud-test - NoClass - Getting GRIB file(s) from external source (NOMADS or AWS S3)
2022-09-16 16:11:22.000 +0000 - DEBUG - wrfcloud-test - NoClass - NOMADS URL does not exist for forecast hour 0, trying AWS S3.
2022-09-16 16:11:30.000 +0000 - DEBUG - wrfcloud-test - NoClass - Pulled forecast hour 0 from AWS S3.
...

I was also able to run all the tests successfully (setup, Test 1, Test 2, Test 3, Test 4, Test 5). I double checked the symlink mods are working for staged data and pulling data - success.
Side note #1: These are handy enhancements!
Side note #2: I had some issues with setting a new case (i.e., not test), but I think that was user error. I will follow-up on Slack to make sure I know the current protocol.

Changing priority to "blocker" as this PR must be merged before #69.

@mkavulich - Did you need anything further on this PR before merging? I will approve, and would be ok with leaving issue #55 for further discussion and enhancement separate from this PR.


Prevent infinite confirmation in shader editor

Fixes #66074
This is how script editor handles it.

Thanks!


Forward any refs passed down to withToastManager

Be sure to pass down any refs to the underlying component.
I tried doing some checking with Flow types but I haven't used flow in awhile so I was not able to validate the flow types.  There is no version of flow specified in the dev dependencies so I tried the latest version and received a bunch of errors.  Anyway...
This PR might need work to be compatible with Flow types.
If someone needs this functionality and this PR is not merged use this:
export const withToastManager2 = Comp =>
  React.forwardRef((props, ref) => (
    <ToastConsumer>
      {context => <Comp toastManager={context} {...props} ref={ref} />}
    </ToastConsumer>
  ));

And as a footnote and point of comparison, this is how withTheme for styled-components does it.
They use hoistStatics but also update the displayName:
https://github.com/styled-components/styled-components/blob/master/packages/styled-components/src/hoc/withTheme.js#L8


drivers: dai: sai: use TDR/RDR for fifo base address computation

Using the address of RDR/TDR for fifo base address computation has the same effect as using the FSL_FEATURE_SAI_{TX/RX}_FIFO_BASEn macro from NXP HAL. The only difference between the two is that the macro is not defined for all SoCs so whenever we introduce a new SoC that uses the SAI module we have to also introduce the macro for said SoC. Using TDR/RDR has the advantage that it doesn't require any additional changes to the NXP HAL.
Since we only support one data line per direction, it's fine to just use RDR[0] and TDR[0] for the address computation.

@kv2019i  this looks good! Can you help merge it?


No IntelliSense/AutoComplete when insert snippet

 in tsx/jsx.

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.56.2
OS Version: Windows_NT x64 10.0.19042

Steps to Reproduce:

create a user key binding:

{
		"key": "alt+w",
		"command": "editor.action.insertSnippet",
		"when": "editorTextFocus && editorLangId==typescriptreact || editorTextFocus && editorLangId==javascriptreact",
		"args": {
			"snippet": "<${1:div}${0}>$TM_SELECTED_TEXT</${1:div}>"
		}
}

When press alt+w, it will insert

 and select both div.

create a tsx file, and input let x =  , press alt+w

Try to input span, there no any autocomplete list showing.

But if you manualy input

,
place the cursor at the first div,
then use alt+click to select the two div,
the autocomplete will show.
And if the cursor is not firstly placed at the first div, for example at the second div, the autocomplet will not show.

When a snippet is active, IntelliSense as you type (aka quick suggestions) is disabled. That is because there is a conflict between the Tab-key which moves to the next placeholder but also accepts a completion. You wouldn't be able to type in a placeholder and then move to the next placeholder as you would accept a suggestion then. You have the following options

change the default via the editor.suggest.snippetsPreventQuickSuggestions-setting
in snippets trigger suggestions manually (via Ctrl+Space, Alt+ESC (macOS), or ctrl/cmd+i)


doc: missing link and confused by the guide

Is Pubsub#getSubscriptions supposed to link to something on this page?
What's the distinction here? Why would Topic#createSubscription retrieve a subscription? It sounds like it would create a subscription.

Subscriptions are sometimes retrieved when using various methods:

Pubsub#getSubscriptions
Topic#getSubscriptions
Topic#createSubscription

Subscription objects may be created directly with:

Topic#subscription

@anguillanneuf looks like a mistake to me, we should just remove it from that list entirely.

Topic#subscription also creates a subscription if autoCreate is set to true.
Does the PR add the missing link? @callmehiphop

@anguillanneuf actually subscription.get({autoCreate: true}) creates it, Topic#subscription is a factory for creating Subscription objects but it doesn't create it on the backend or make any requests.

@callmehiphop Last I looked, Pubsub#getSubscriptions and Pubsub#createSubscription still seem to be missing hyperlinks. Might worth double-checking.


[feat] File drop event enum

Describe the problem
I noticed file drop events:

tauri://file-drop
tauri://file-drop-hover
tauri://file-drop-cancelled

are only exposed to rust via the string ids.
Describe the solution you'd like
In the same spirit of other events we should expose these to Rust in a structured format (enum).
Alternatives considered
No response
Additional context
No response

#3686

oops, my bad! Thanks for the reminder!


compare the triplets java

Solved issue #(your issue number)  #418
In Language- (your used language) Java

[x] Updated README Link
[x] Added code with comments

Thanks for contributing!

Kindly add one more | at the end in Readme otherwise conflict may come

Algorithms/Warmup


fixing init.py

fixing improper importing of gdal.
from osgeo import gdal

fixing init.py.
from osgeo import gdal instead of import gdal directly.


Adding a Layer image not working on Mac OS 10.12.3

Opening the jar
Selecting the screen
Click Layer/Image/Paint/Loading
Click open file
Not allowing me to select any images including the PNG view3.png in the repository.

Are you currently using version 2.0.2? https://github.com/McAJBen/DungeonBoard/blob/master/Versions/Dungeon Board v2.0.2.jar
If you click the folder icon you are selecting a folder with image in it
Initially when you open the Jar it will create a folder next to it called "DungeonBoard" and its sub-folders. Try placing images inside of that and see it it works.

That version is working for me, thank you!


vulkaninfo: Fix typo in VK_EXT_surface_maintance1

Was VK_EXT_surface_maintance_1 which is wrong.
Fixes #908

CI Vulkan-Tools build queued with queue ID 73350.

CI Vulkan-Tools build # 1263 running.

CI Vulkan-Tools build # 1263 passed.


Affine Cipher Icon

ref: https://github.com/exercism/ruby/pull/817#issuecomment-406717099
No exercise icon exists yet.

There's a repository to create an issue in if you want/need an icon created.
I don't remember which one though :(

This is solved in https://github.com/exercism/website-icons/pull/17 :tada:


 Now we skip everything except actually applying ProtoData. If the users don't need ProtoData for any other generation purposes, they may disable ProtoData tasks manually.

Covered by a series of recent PRs already.


Contributed command to easily turn on/off/tail the db query log

Is there an existing issue for this?

[X] I have searched the existing issues

Is your feature request related to a problem?
When using ddev with a framework with a database abstraction layer, it can be finicky to set up being able to see the actual database queries generated by the application.
Describe your solution
A custom ddev command that allows a user to very very easily turn on or off query logging and optionally to tail that log.
Due to the noisy nature of the db log output, it would be best to exclude it from the general ddev logs output.
Describe alternatives
I considered adding configuration to the db container that would send all queries to the ddev logs. But I realized that would create a lot of noise, would slow down the application, and would make it difficult to toggle on and off. Looking at the db logs is generally something only necessary to do occasionally.
Additional context
I have written a command as described above and am using it successfully. I am posting this issue to see whether it would be considered generally worthwhile enough for it to be contributed to the ddev project as an included command.

@apotek Thanks for the suggestion.
Might be worth posting the command here, or sharing a gist to it so people can have a play and give feedback.
If it's something you think you might use a lot, consider creating an addon. That makes it easier to install for anyone. 😄

@apotek Thanks for the suggestion.
Might be worth posting the command here, or sharing a gist to it so people can have a play and give feedback. If it's something you think you might use a lot, consider creating an addon. That makes it easier to install for anyone. 😄

Hi @tyler36 and thank you for your reply. I just posted a merge request which should demonstrate the approach. I am curious about "creating an addon." I'll look into that.
I can in the meantime attempt to expand this script to include pgsql support as well (or just write another for that). But this should provide a starting point.

You can find the template here: https://github.com/ddev/ddev-addon-template
EG. https://github.com/tyler36/ddev-vscode-devcontainer is a simple addon that adds a "code" command.

I think that is a great idea and it helps me often when debugging.
I've made this command some years ago: https://gist.github.com/jonaseberle/28a675d034dfa1dbaf8e586184fd1d77 but I've not come around to upstream it as a DDEV add-on. Please feel free to take from it what you find useful. I am happy to install the add-on from you then! :)

Hi @tyler36 and @jonaseberle ! Thank you for your suggestions. I have created a rough draft for this as an add-on. Once I get it to pass its initial tests, I'll post a link to it here.
@jonaseberle I like a lot of the ideas in your script and may want to incorporate some of them while keeping the command light weight.
@tyler36 I agree also with you that it would be nice to make the command db-engine agnostic.

@tyler36 I have put up test-passing beta at https://github.com/ChromaticHQ/ddev-dblog and posted a feature request for postgres support here: https://github.com/ChromaticHQ/ddev-dblog/issues/1
@jonaseberle I have added a feature request to maybe implement some of your gist-ideas into the UX as the add-on matures. Thank you again for your suggestions: https://github.com/ChromaticHQ/ddev-dblog/issues/2

Thanks, that works well.
I think we can close here and use ddev get chromatichq/ddev-dblog and ddev dblog tail :)

Yay, thanks!


Arm unit tests should be created and hooked up to CI

This isn't trivial as there isn't an ARM SDK image therefore the current utest pattern doesn't work - use the platform SDK image to build an app that is tested with the platform runtime images.

In-lieu of having an ARM SDK, I think it would be reasonable to write a CI test that utilizes a multi-stage build running on a Windows 10 machine.  The first stage would utilize an AMD64 SDK image to build an app that would get copied to the ARM Runtime image in a second stage (e.g. just like what is done in the dotnetapp-prod sample)
@ravimeda - Can you ensure the version of Docker on the CI machines supports multi-stage builds?  I do not know what version of docker is on these machines.  It would be valuable to emit this as part of the CI runs.  If this is done for CI, the same should be done for official builds as well.

Thanks Michael. To get the version information of Docker where a test is running, I'm thinking of adding
$(docker version) | % { Write-Host "$_" }

at https://github.com/dotnet/dotnet-docker-nightly/blob/master/test/run-test.ps1#L45
Or the corresponding location in xUnit format of the tests. Thoughts?

17.05 or newer is required for multi-stage builds, per https://docs.docker.com/engine/userguide/eng-image/multistage-build/

I was thinking of adding it to the image-builder tool.  Because of https://github.com/dotnet/dotnet-docker-nightly/issues/401, it would also need to be added to https://github.com/dotnet/dotnet-docker-nightly/blob/master/build-and-test.ps1 as this is currently the entrypoint for CI.

One more prereq that we need is a win 10 docker enabled machine in the CI pool.  I am not sure if such a machine exists today.

@MichaelSimons please could you clarify the approach for ARM64 unit test.
In the first stage, create, build and publish a dotnet app on amd64 image. In the second stage, use a ARM32 image, copy the bits from first stage, and create an entry point to run the app. Based on that I have the Dockerfile shown below.
FROM microsoft/dotnet:2.0-sdk AS build-env

WORKDIR /app

RUN dotnet new console
RUN dotnet restore
RUN dotnet publish -c Release -o out
RUN ls -lR /app

# build runtime image
FROM microsoft/dotnet:2.0.0-runtime-stretch-arm32v7
WORKDIR appRuntime
COPY --from=build-env /app/out /appRuntime
RUN ls -lR /appRuntime
ENTRYPOINT ["dotnet", "app.dll"]

Build using the command below works fine, meaning no errors and a image named test is created.
docker build -t test .
But running it throws an error as shown below -
docker run --rm --name app test
Did you mean to run dotnet SDK commands? Please install dotnet SDK from:
  http://go.microsoft.com/fwlink/?LinkID=798306&clcid=0x409

Why is SDK needed? To run the app, only runtime, which is already available on the image, is the only thing that is needed, right? Please clarify...

Interactively running it seems to work -
docker run --rm -it test
root@30386ccad8b7:/appRuntime# dotnet app.dll
qemu: Unsupported syscall: 389
Hello World!
root@30386ccad8b7:/appRuntime#

Per a discussion w/@ravimeda, the posted Dockerfile produces a working image.  Not sure what caused the failure reported earlier.


Load projects only when they enter the view on projects page

It's an issue related to that branch: https://github.com/datsfilipe/datsfilipe.dev/tree/feat/rewrite-projects-page
Basically loading all images at once on projects page is impossible.

Done at c774fa65ef9556c1056a8ee74c0dcb663ac740a0


scrolling until visible doesn't wait after scroll anymore

Description

I was on version 17.14.9 of detox and this was working, I am not trying to upgrade to 19.4.2 and I am having a problem.
 In the last version of detox I think it first checks whether the expected element is visible (it's not because the modal is just coming into view) and then tries to scroll (it can't because now there is the modal) and it doesn't check again for the expected element and fails.
I am not sure what kind of a logic change happened between the two versions regarding this, but is there a way around this? I tried to make it wait a bit after every scroll but I couldn't find a way to do that either without manually writing the scroll. I am using the code below like in the documentation:
  waitFor(expectedElement)
    .toBeVisible()
    .whileElement(by.id(scrollElementId))
    .scroll(scrollOffset, direction, startPositionX, startPositionY);

Environment

Detox: 19.4.2
React Native: 0.66.3
Node: 14
Device: Simulator
OS: iOS
Test-runner: jest-circus

For now I found the below code to be the solution, but I am not sure if it's a good idea to use it like this:
  waitFor(expectedElement)
    .toBeVisible()
    .whileElement(by.id(scrollElementId))
    .scroll(scrollOffset, direction, startPositionX, startPositionY)
    .catch(async (_) => {
      await waitFor(expectedElement).toBeVisible().withTimeout(timeout);
    });

Is it not possible to add a wait for this?

@dbilgin thanks for the report!
I'm not really sure what happened here. Did it tried to continue the scrolling after the modal was already presented?

@asafkorem thanks for your reply. It goes like this:

it scrolls
waits for the element (I assume)
the element is not available right away
the modal slides in
tries to scroll again (I could see it)
cannot scroll and gives error saying it could neither scroll nor see the element

Have you considered the scrollTo(edge) API (here)?
await element(by.id(scrollElementId)).scrollTo('bottom');
await waitFor(expectedElement).toBeVisible().withTimeout(timeout);

Also, please provide the necessary logs as the issue template requires, it will help me to understand the problem better..

I did consider this, but it's an endless paginated flatlist and the modal appears at a certain point on the second page.
The workaround I came up with is working fine right now:
.catch(async (_) => {
      await waitFor(expectedElement).toBeVisible().withTimeout(timeout);
    });

But I was thinking it's probably not a nice way of doing it.
Let me get the logs for you, sorry about that

the element is not available right away

OK I can see the problem here, if fails to scroll after he thinks that the element is not visible yet (because it wasn't last time it was tested)..
Well, in that case, your workaround makes some sense (given the existing API).

So these are the logs from when the modal starts appearing (all the logs were immensely huge so I cut this part):

detox[10090] INFO:  [APP_STATUS] The app is busy with the following tasks:
• 1 enqueued native timers:
  - Timer #1:
    + Fire date: 2022-01-24 13:14:57 +0100.
    + Time until fire: 0.100.
    + Repeat interval: 0.
    + Is recurring: NO.
• The event "Network Request" is taking place with object: "URL: “https://--”".
• The event "Network Request" is taking place with object: "URL: “https://--”".
• There are 9 work items pending on the dispatch queue: "Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)".
• Run loop "Main Run Loop" is awake.
• The event "Network Request" is taking place with object: "URL: “https://--”".
• There are 1 pending delayed selectors to be performed.
• The event "Network Request" is taking place with object: "URL: “https://--”".
• UI elements are busy:
  - Layers needs display: 4.
  - Layers needs layout: 3.
  - View needs layout: 2.
detox[10090] TRACE: [WSS_GET_FROM, #app] {"messageId":7,"params":{"details":"Unable to scroll down in “<RCTCustomScrollView: 0x7fe61d02f600>” and no elements found for “MATCHER(text == “Test!”)”","NSLocalizedDescription":"Unable to scroll down in “<RCTCustomScrollView: 0x7fe61d02f600>” and no elements found for “MATCHER(text == “Test!”)”","viewHierarchy":"<UIWindowScene: 0x7fe61f10b620; scene = <FBSScene: 0x600003ca8380; identifier: sceneID:com.example-default>; persistentIdentifier = CBD22D2C-2017-4BB2-9F96-5F98FF97D16B; activationState = UISceneActivationStateForegroundActive>\n   + <UIWindow: 0x7fe61c61d570; frame = (0 0; 414 896); layer = <UIWindowLayer: 0x600001460f00>>\n   |    | <UITransitionView: 0x7fe61c6211f0;

In the earlier version of detox it was actually waiting for this long enough, thanks for confirming my method of working around this, but I was wondering if it would be logical to add a timeout functionality to this

I understand.. ATM Detox doesn't support the combination of wait-for expectations with both action and timeout, however, the API you suggest sounds reasonable indeed, we are talking about something like:
waitFor(expectedElement)
    .toBeVisible()
    .withTimeout(timeout)
    .whileElement(by.id(scrollElementId))
    .scroll(scrollOffset, direction, startPositionX, startPositionY);

yes! exactly something like this

Note that your current workaround will run faster than the suggested API (it will wait for timeout only on the last check), so I'm not convinced if waiting with timeout on each iteration will be the best practice on such cases.
Anyway, thanks, that's really an interesting scenario, I will think about it..

From the view hierarchy it seems like the scroll view is covered with a transition view, but the view that you're waiting for to be visible is not yet visible, so you may also consider something like:
await waitFor(scrollElementId)
  .not.toBeVisible()
  .whileElement(by.id(scrollElementId))
  .scroll(scrollOffset, direction, startPositionX, startPositionY);
await waitFor(expectedElement).toBeVisible().withTimeout(timeout);

hmm, I never thought of doing it that way, I thought it would work honestly, but got a similar error again.
As far as I understand, it initially checks if the element is there and because the modal is not yet visible, it is there, then by the time it tries to scroll again, the modal is already there and it cannot scroll, so it fails at the scroll


barDir is not working

Hi,
slide.addChart( pptx.charts.BAR, dataChartBar,{barDir:'h'} );
Im using the above code. But its not working.
can you please help.
thanks,
shiva

Is there any way to remove Gridlines in bar chart?

Need Horizontal bar chart
slide.addChart( pptx.charts.BAR, dataChartBar,{barDir:'h'} );
Its not working.

Hi @Shankar000536 ,
Thanks for letting me know about the barDir issue.
I'd written the README incorrectly, and have fixed it now.  The options should be bar (horiz) or col (vertical).

Other Questions:

Using path to add remote images (images from a different server) is not currently supported.
More Chart gridline and axis options are forthcoming


Which folder  to put downloaded ZoeDepth model?

I  tested the workflow,   and res101 is working good,
all those midas model does a bad work,
and I doult if ZoeDepth can do better job,
but it's errored  cause I don't have any folder with Zoe Models,
I downloaded ZoeModels  here,   all 3 of them, bu Idon''t know  where to put them.
https://github.com/isl-org/ZoeDepth/releases/tag/v1.0
Which folder  to put downloaded ZoeDepth model?

Just took at mine and they ended up here:
stable-diffusion-webui/extensions/stable-diffusion-webui-depthmap-script/scripts/checkpoints/
Although, I thought I remembered that model just downloaded itself when first going to use it, but it has been a while, not sure. As for the quality of ZoeDepth vs res101, I personally find the Zoe ones way better, but specifically the "indoor" one is even better to me than the more generic NK default one of theirs if actually working with indoor scenes.

This has been answered before, all models are download by the extension directly into /models/ except for the zoedepth models which are downloaded through torch hub.
They can be found here : ~/.cache/torch/hub/checkpoints/

THanks,   my internet use proxy,  I download each model by hand copy links from CMD window, and restart.

Just took at mine and they ended up here:
stable-diffusion-webui/extensions/stable-diffusion-webui-depthmap-script/scripts/checkpoints/

Thanks , I copied those 3 brothers there, hope they workss.


Dullsville! Options and Utils cleanup

I started this branch last night thinking it would be a 15-minute task, but ran into some fun with globs that took me all morning to get through.
Cleaned out some cruft, refactored some options, made a few things more modular.
Deep review not needed :).

I had a few ignorable comments. :+1:


XSS in innerHTML

The problem described in xss_in_login_form.md is not App related.
It is related to this line.


Update Advanced Topics conditions with operator-framework/operator-lib

Hello,
This PR Closes #3647
Description of the change:
It changes the documentation to point to the new status location that is now operator-framework/operator-lib
Motivation for the change:
see #3647. I've faced the same issue and it does not work with v1+ of operator-sdk.
Checklist
If the pull request includes user-facing changes, extra documentation is required:

[ ] Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
[x] Add or update relevant sections of the docs website in website/content/en/docs

/cherry-pick v1.0.x


GH-23221: [C++] webassembly / pyodide / emscripten build support

This PR adds a cmake build preset for emscripten / pyodide, and updates the setup for pyarrow so that it is possible to build a webassembly version of libarrow, and a version of pyarrow which works on pyodide.
Things that changed:

Cmake preset ninja-release-emscripten-python
Platform/toolchain override for cmake on emscripten, to set various build parameters
Some fixes to cmake files - e.g. pyarrow can build with static libarrow now, and third party dependencies pass the toolchain file through.
pyarrow knows about ARROW_ENABLE_THREADING and doesn't use threads if they are not enabled in libarrow.
pyarrow sets defaults for inclusion of submodules based on their inclusion in the arrow build. e.g. pyarrow.parquet is built only if ARROW_PARQUET is set. This makes it possible to build in situations where you don't have access to set the build environment variables (e.g. in cross compiling situations like pyodide). It also seems to me to make sense - I can't see why you'd want to build pyarrow without parquet if you've built arrow with it, and the inverse is obviously not possible.

Closes: #23221

Also fixes #34996 once this is in the pyodide package tree.

@kou I'm not sure who is the right person to review this - it's a smidgen of python / python packaging changes and cmake changes.

Can we split this pull request to the C++ part and then the Python part for easy to review?

@kou - I've split out the cmake changes into #37821. Once they're in, I can update this one to be just the pyodide build side of things - I think the python build depends on them, so it isn't worth reviewing the python changes until 37821 is in?

Closing this as all changes are in the other PRs


Documenting Node version requirement

Hey @izolate  Thanks for the great tool. ☺
I was struggling with getting html2pug working. Then discovered it relied on a new version of node due to the await function stuff. So I added that to the README.md.
I also added a bit about installing for development purposes. Hope that's ok.
Keep up the good work.

To be fair, I think that await there is superfluous, considering that await isn't used anywhere inside the body of the function. Probably should setup eslint in order to prevent this from happening

@popkinj Sorry for the struggle. Async functions are used in cli.js, and a note on minimum Node version has been added to the README on release of version 2.0.

No worries @izolate. Thanks for the update ☺.


Is there a plan here ?

The roadmap has been a while since there was an update. What is the current progress and future plan?

Currently I'm working on compiling SFC. compiler-core and compiler-dom has been mostly implemented.


Explore build container alternatives

https://github.com/redhat-developer/openshift-actions/issues/53

@lstocchi commented:
A bit of context: the goal here is to find the best way to build a container for our java app (first use-case) so that the resulting image can be pushed to a registry. The app could have a docker file or be dockerless.
Alternatives we are evaluating:

S2I
Buildah

is this complete?

Yes, i think we're done with this. @Divyansh42 feel free to reopen it if you want to add something else


junit5

I don't succeed to use Junit 5 with your lib. Any tips ?
PS : awsome work ! GJ !

Unfortunately, it is not something I've had time to try. If you can share a project that recreates the issues and explain the issues you are facing, I can try to help.