The word 'FROM' in square bracket clause's causes error

If you have the word "FROM" surrounded by spaces in a square bracket clause the query will return an error.
Ex:
SELECT in()[name = ' FROM '] FROM Object;

The errors are random:
Missing closed string character: '''
Class 'xxxxx' was not found in the current database
I tried other keywords but it seems FROM is the only one that messes things up.
This happens on 1.7.10, 2.0-rc1, and the 20150108 2.0 SNAPSHOT.

Looks like this also happens with the 'LET' keyword.

@luigidellaquila is this already resolved?

no, AFAIK

Got the same problem with property named 'from'. Got it working changing to 'fromXXX'

@mathieubodin FROM is a reserved word, so you should not be able to use it as a property name (there is another issue about avoiding this when creating schema). Also new parser will complain about this.
Another story is inside strings, where it's supposed to work fine

fixed in 2.1 snapshot

by the way we could support 'select from from example' it should be quite easy in the new parser


Logout wreply url is missing from console ui when creating a passiveSTS application.

Describe the issue:
From the PR https://github.com/wso2-extensions/identity-inbound-auth-sts/pull/144, WReply Logout URL was added to passiveSTS and it is considered as a mandatory field in the edit window.

But when creating a new passiveSTS application, that field is not asked from the user.

Environment information

Product Version: 7.0.0-beta
OS: Mac
Database: H2
Userstore: JDBC

The WReply Logout URL validation was added to the backend and was marked as mandatory in the edit window with https://github.com/wso2/identity-apps/pull/4518 to enforce users to configure the wreply logut url.
Setting configurations for passive sts application in the create window was not available when this change was done. Since  we seem to be now allowing users to set the configuration in the create window, the WReply Logout URL should be added here as well and marked as mandatory.

Verified the fix in the latest build.
https://github.com/wso2/product-is/assets/41533942/1b855326-7a53-430c-ba12-bf4537ebf706


[FLINK-9359][docs] Update quickstart docs to only mention Java 8

This is a trivial but important fix to the quickstart setup page in the docs. This fix should be made to the 1.4, 1.5, and 1.6 docs so that folks aren't confused when Java 7, 9, and 10 all fail to work.

+1

merging.


NEW_PASSWORD_REQUIRED challenge not being raised for unconfirmed users

It looks like the initiate_auth is not returning the NEW_PASSWORD_REQUIRED challenge  for unconfirmed users, and is instead just logging them in. I checked the test suite and didn't find any checks on it. Also didn't find any other issues on the topic. I might be wrong in setting up the client though, here's the full code to check it.
moto version: 2.3.0
import boto3
from moto import mock_cognitoidp

@mock_cognitoidp
def main():
    cidp = boto3.client("cognito-idp")
    response = cidp.create_user_pool(
        PoolName='Test',
        Policies={
            'PasswordPolicy': {
                'MinimumLength': 6,
                'RequireUppercase': True,
                'RequireLowercase': True,
                'RequireNumbers': False,
                'RequireSymbols': True,
                'TemporaryPasswordValidityDays': 123
            }
        },
        UsernameAttributes=['email']
    )
    user_pool_id = response["UserPool"]["Id"]
    response = cidp.create_user_pool_client(
        UserPoolId=user_pool_id,
        ClientName="test",
        AllowedOAuthFlows=['implicit'],
        AllowedOAuthScopes=['email']
    )
    user_pool_client_id = response["UserPoolClient"]["ClientId"]

    email =<EMAIL_ADDRESS>    password = "SomePassword_1"
    cidp.admin_create_user(
        UserPoolId=user_pool_id,
        Username=email,
        UserAttributes=[{"Name": "email", "Value": email}],
        TemporaryPassword=password
    )

    response = cidp.initiate_auth(
        AuthFlow='USER_PASSWORD_AUTH',
        AuthParameters={
            'USERNAME': email,
            'PASSWORD': password},
        ClientId=user_pool_client_id)

    print(response)
    assert "ChallengeName" in response
    assert response["ChallengeName"] == "NEW_PASSWORD_REQUIRED"

if __name__ == "__main__":
    main()

Thanks for raising this @dominusmi. A PR would be very welcome!

Great job on the speed of the whole process, making me want to further collaborate!


fix: remove duplicate apollo-angular dep

Closes #393

@manekinekko Do you need to update the package-lock.json too?

No need to update the lock file. It was already deduplicating that dependency and using the lastest version.


No need for Steam login anymore

Just a heads up :)
https://developer.valvesoftware.com/wiki/Counter-Strike_2/Dedicated_Servers#Download_the_CS2_Dedicated_server

If this issue is still relevant, reopen it on joedwards32/CS2. This repository is now a mirror.


Add more unit test coverage and remove unused class AbstractView

Add some basic unit test coverage for MainActivity and PermissionsManager
Also removes an unused class AbstractView

@JSunde  PTAL?

/gcbrun

/gcbrun


feat: show name of ipfsid

test:
run ./bin/run wallet-service
Shows name of wallet service when running wallet-service commands.

:tada: This PR is included in version 2.23.1 :tada:
Your semantic-release bot :package::rocket:


Include Winbtrfs to File Explorer Add-ons

Winbtrfs a tool used to natively mount btrfs file system.
I hope you can also do for FAT32, like how Winbtrfs implemented. So there is less hassle exchanging files with a dual boot system. Although you can already do it with linux-subsystem.

Betting this is what you want, https://devblogs.microsoft.com/commandline/whats-new-in-the-windows-subsystem-for-linux-september-2020/#linux-fs
Correct?  if so, WSL2 / File explorer will have this starting with builds 20211 or newer

Was it already preinstalled in 20211, or have to install manually? If not, a single click from PowerToys will be great.

WSL isn't preinstalled on Windows machines. You'll need to first install WSL and then you'll need to (mount the disk that you want into WSL)[https://docs.microsoft.com/en-us/windows/wsl/wsl2-mount-disk] to access it from File Explorer.


BUG report: video freezes after one click on page.

Hi. I'm trying to build an app with this library but after click on play sound button picture freezes.
here's my code:
`import { launch, getStream } from 'puppeteer-stream';
import { createWriteStream } from 'fs';
const file = createWriteStream(__dirname + '/../recordings' + '/test.webm');
async function main() {
const browser = await launch({
executablePath: '/usr/bin/google-chrome',
headless: false,
defaultViewport: null,
devtools: false,
args: [
'--window-size=1920,1080',
'--window-position=1921,0',
'--autoplay-policy=no-user-gesture-required',
],
ignoreDefaultArgs: ['--mute-audio'],
});
const page = await browser.newPage();
page.setViewport({
width: 1920,
height: 1080,
deviceScaleFactor: 1,
isLandscape: true,
});
await page.goto('https://www.rainymood.com/', { timeout: 0 });
const stream = await getStream(page, {
audio: true,
video: true,
mimeType: 'video/webm;codecs=vp8,opus',
});
stream.pipe(file);
console.log('recording');
console.log('now clicking...');
const button = await page.waitForSelector('#pButton');
await button.click();
setTimeout(async () => {
await stream.destroy();
file.end();
file.close(() => {
process.exit(0);
});
console.log('finished');
}, 1000 * 40);
}
main();
`

oh this is because of my player bug. when i played it's output with chrome doesn't freeze. maybe this problem raised because of output file doesn't have correct duration. i must convert it to mp4 with ffmpeg.


Issue #306 Add pre-cluster start certs validity check

Fixes #306

@anjannath @gbraad shouldn't we take it from metadata since it have build time "buildTime": "2019-06-28T09:30:28+00:00", which we can compare and return this way we can tell user very early before even starting the VM?

buildtime is not conclusive and ONLY an indicator, as when certificates have rotated, the in VM certificates are newer.
You can, and that was the idea, have an inidication this this might NOT be the latest bundle, as it is older than 30 days.

@anjannath @gbraad shouldn't we take it from metadata since it have build time "buildTime": "2019-06-28T09:30:28+00:00", which we can compare and return this way we can tell user very early before even starting the VM?

buildTime is set as part of the snc script and after that we wait addtional 24hrs for the cert rotation, we can probably have a preflight check for the bundle (and warn) using the buildTime, but checking the certs from inside the VM (pre cluster-start) seemed more robust..

seemed more robust..

and the only way. The buildtime is informational, but it can never error out the start, merely warn.

@anjannath Can you add that info in commit message (like @gbraad said when cert rotation happen then buildtime is not conclusive) ? I am OK with that patch will merge after.

@praveenkumar Done!


Can I come up with a decent model of translucency?

I'm thinking two passes:

Dispatch the back-faces of all translucent objects and draw the fragment normal and distance into a texture
Dispatch the front-faces of everything as normal with the first pass texture as a uniform

In the normal shader, read the backface distance and normal from the first pass texture if this fragment is translucent. Use backface position (${viewpoint} + \vec{V} \cdot d_{backface}$) and normal to calculate how much of each light falling there is absorbed into the object. Use this light multiplied by a transmission colour (is that just the albedo colour?) and multiplied by the translucency raised to the power of the thickness (difference between front and backface distance) to determine an amount of transmitted light that can be added into the fragment colour.
This assumes that our new translucency material property is a fraction of light transmitted per unit distance.
There is an argument that this path should also be taken for transparent instances and that transparency should also take account of the material thickness. So then translucency is how much lights behind an object can be seen through an object and transparency is how much of the scene behind can be seen through an object.

First pass definitely doesn't need to be done with multi-sampling, probably could be done at a lower resolution – although I'm slightly nervous about whether mad interpolated values might be sampled from the texture near the outside edges of objects…

Commit notes:
The new translucency attribute on materials specifies a depth "half-life" (in the world coordinate system) that controls both how quickly backface light dissipates as it travels through the material and how much it scatters. Larger values mean less light travelling through the object and greater scattering, lower values mean more light and less scattering. The scattering of light is achieved by taking a selection of random samples of the backface light falling on the object, offset by how much scattering is happening. It is a very loose approximation and will tend to "fizz" a little.
As the amount of light you will see is dependent on scattering, very low values of translucency will actually result in a dark object not a bright one. As translucency becomes lower, the object also becomes more transparent. As with transparency, the background image isn't scattered and so partially transparent objects don't look realistic.

Of course, sadly those commit notes are wrong. For the record, the truth from the docs is:
translucency= TRANSLUCENCY
Specifies how translucent this material is as a distance (in the world coordinate system) over which half of the light falling on the backfaces of the object will pass through it. The default is 0, meaning no translucency. At low levels of translucency, light will be scattered and will glow through the edges/thin-parts of objects. At higher levels of translucency light will be scattered less and the object will become more transparent. Setting this to non-zero both affects the model render order and also forces an additional render pass to determine the thickness of the object and the light falling on the back faces.


Place the short argument in front of long argument in help document.

Here's what our argument help looks like:
Arguments
    --destination-blob -b      [Required]: Name of the destination blob. If the exists, it will be
                                           overwritten.
    --destination-container -c [Required]: The container name.

Note that the order of the arguments is long first and then short one follows. It is inconsistent with common linux manuals, in which short arguments are in the front and long arguments are aligned.
11:44 $ curl --help
Usage: curl [options...] <url>
Options: (H) means HTTP/HTTPS only, (F) means FTP only
     --anyauth       Pick "any" authentication method (H)
 -a, --append        Append to target file when uploading (F/SFTP)
     --basic         Use HTTP Basic Authentication (H)
     --cacert FILE   CA certificate to verify peer against (SSL)
     --capath DIR    CA directory to verify peer against (SSL)
 -E, --cert CERT[:PASSWD]  Client certificate file and password (SSL)
     --cert-status   Verify the status of the server certificate (SSL)
     --cert-type TYPE  Certificate file type (DER/PEM/ENG) (SSL)
     --ciphers LIST  SSL ciphers to use (SSL)
     --compressed    Request compressed response (using deflate or gzip)
 -K, --config FILE   Read config from FILE

The latter format is more readable since there short arguments easily stand out.

/cc @JasonRShaver

Cleaning u old issues, reopen if this is still active.


gateway-api: Bump version to v0.8.0-rc1

This is to regularly sync-up with upstream releases, which will make
things easy for v1.0.0 later.
Uptream release: https://github.com/kubernetes-sigs/gateway-api/releases/tag/v0.8.0-rc1

/test

/test

Closed in favour of https://github.com/cilium/cilium/pull/27592


Telnet: cant_connect but telnet is open

Hi All, Thanks for your job @AlexxIT !
I have open telnet in FW 1.4.xx, but still cant connect to XiaomiGateway3.
What i see now, when i update my FW to 1.5.4_090
Name: Brama
Model: lumi.gateway.mgl03
IP: 192.168.x.151
MAC: 54:EF:xx:22:xx:63
Token: 664c4550xxxxxx57
Telnet: cant_connect

when i connect manually telnet:
======================================================
FIRMWARE........: 1.5.4_0090 #20220509
IP..............: 192.168.x.151
MAC.............: 54:EF:xx:22:x:63
TOKEN...........: 664c4550xxxxxxxxxxxxx57
DID.............: 40856xx60
KEY.............: 5z3xxxxxxe26TgIx
======================================================

Why i cant add gateway to HomeAssistant via XiaomiGateway 3.3.3?
I reinstall all, i use key, i use without key, i check everything ten times. Still cant connect. All is update.
Best regards!
M

If you are sure about Telnet, you may have problems with your network.

Аналогичная ситуация


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-source-version-target/pull/73 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-source-version-target.git

Docs Build status updates of commit 3b953b1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

versioningArchiveSourceFolder/TOC.yml
:white_check_mark:Succeeded
View (sql-server-2014 || azuresqldb-current || azuresqldb-mi-current || azure-sqldw-latest || >= aps-pdw-2016 || >= sql-server-2016 || >= sql-server-linux-2017 || sql-server-previousversions || sqlallproducts-allversions)

versioningArchiveSourceFolder/docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Using iOS as main access?

We are using PowerBI and some reports are shared with me as email attachments.
It would be great to have guidance on How to use those if all you have is the mobile app?
I use a Mac Laptop and have not Found the Power BI sw for it.

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

ID: cf174abf-6474-14ae-3183-31e40fa9b1b6
Version Independent ID: ca82ad59-c057-fccd-b6e0-627df4326c62
Content: Explore reports in the Power BI mobile apps - Power BI
Content Source: powerbi-docs/mobile-reports-in-the-mobile-apps.md
Service: powerbi
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Thank you for your question. This issue has been assigned to the author for review.

Hi, @CarlMagnusC -- thanks for your question! If I understand correctly, you've received a Power BI report, a PBIX file, via email. Right? And you have the Power BI mobile app for iOS? Or you're trying to view it on the Mac?
Either way, you and the person who created it need Power BI Pro licenses, and the creator needs to publish it to the Power BI service on the web. Then you can view it in a browser on the Mac or in the Power BI mobile app for your iOS device.
Does that answer your question?
Thanks again!

However, my college that uses a PC can be Viewed with the trial licence... and We are evaluating it together.
Br, Carl-Magnus
Sent from my iPhone
On 20 Jul 2018, at 3.36, Maggie Sparkman <notifications<EMAIL_ADDRESS>wrote:
Closed #61https://github.com/MicrosoftDocs/powerbi-docs/issues/61.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/powerbi-docs/issues/61#event-1743795083, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Am_FjtVbSUwBFJ3muhJqL9z47AKj283Eks5uISYlgaJpZM4VE3NU.


"Aerial could find no supported backend" with *.tsx files

Describe the bug
"Aerial could find no supported backend" with *.tsx files
System information

OS: [mac]
Neovim version: 0.7.0
AerialInfo: [output of :AerialInfo]

Aerial Info
-----------
Filetype: NvimTree
Configured backends:
  treesitter (not supported) [No treesitter parser for NvimTree]
  lsp (not supported) [LSP client not attached]
  markdown (not supported) [Filetype is not markdown]
Show symbols: Class, Constructor, Enum, Function, Interface, Module, Method, Struct

Aerial config:

-- Call the setup function to change the default behavior
require("aerial").setup({
  -- Priority list of preferred backends for aerial.
  -- This can be a filetype map (see :help aerial-filetype-map)
  -- Enum: persist, close, auto, global
  --   persist - aerial window will stay open until closed
  --   close   - aerial window will close when original file is no longer visible
  --   auto    - aerial window will stay open as long as there is a visible
  --             buffer to attach to
  --   global  - same as 'persist', and will always show symbols for the current buffer
  close_behavior = "auto",

  -- Set to false to remove the default keybindings for the aerial buffer
  default_bindings = true,

  -- Enum: prefer_right, prefer_left, right, left, float
  -- Determines the default direction to open the aerial window. The 'prefer'
  -- options will open the window in the other direction *if* there is a
  -- different buffer in the way of the preferred direction
  default_direction = "prefer_right",

  -- Disable aerial on files with this many lines
  disable_max_lines = 10000,

  -- Disable aerial on files this size or larger (in bytes)
  disable_max_size = 10000000,

  -- A list of all symbols to display. Set to false to display all symbols.
  -- This can be a filetype map (see :help aerial-filetype-map)
  -- To see all available values, see :help SymbolKind
  filter_kind = {
    "Class",
    "Constructor",
    "Enum",
    "Function",
    "Interface",
    "Module",
    "Method",
    "Struct",
  },

  -- Enum: split_width, full_width, last, none
  -- Determines line highlighting mode when multiple splits are visible.
  -- split_width   Each open window will have its cursor location marked in the
  --               aerial buffer. Each line will only be partially highlighted
  --               to indicate which window is at that location.
  -- full_width    Each open window will have its cursor location marked as a
  --               full-width highlight in the aerial buffer.
  -- last          Only the most-recently focused window will have its location
  --               marked in the aerial buffer.
  -- none          Do not show the cursor locations in the aerial window.
  highlight_mode = "split_width",

  -- Highlight the closest symbol if the cursor is not exactly on one.
  highlight_closest = true,

  -- Highlight the symbol in the source buffer when cursor is in the aerial win
  highlight_on_hover = false,

  -- When jumping to a symbol, highlight the line for this many ms.
  -- Set to false to disable
  highlight_on_jump = 300,

  -- Define symbol icons. You can also specify "<Symbol>Collapsed" to change the
  -- icon when the tree is collapsed at that symbol, or "Collapsed" to specify a
  -- default collapsed icon. The default icon set is determined by the
  -- "nerd_font" option below.
  -- If you have lspkind-nvim installed, aerial will use it for icons.
  icons = {},

  -- Control which windows and buffers aerial should ignore.
  -- If close_behavior is "global", focusing an ignored window/buffer will
  -- not cause the aerial window to update.
  -- If open_automatic is true, focusing an ignored window/buffer will not
  -- cause an aerial window to open.
  -- If open_automatic is a function, ignore rules have no effect on aerial
  -- window opening behavior; it's entirely handled by the open_automatic
  -- function.
  ignore = {
    -- Ignore unlisted buffers. See :help buflisted
    unlisted_buffers = true,

    -- List of filetypes to ignore.
    filetypes = {},

    -- Ignored buftypes.
    -- Can be one of the following:
    -- false or nil - No buftypes are ignored.
    -- "special"    - All buffers other than normal buffers are ignored.
    -- table        - A list of buftypes to ignore. See :help buftype for the
    --                possible values.
    -- function     - A function that returns true if the buffer should be
    --                ignored or false if it should not be ignored.
    --                Takes two arguments, `bufnr` and `buftype`.
    buftypes = "special",

    -- Ignored wintypes.
    -- Can be one of the following:
    -- false or nil - No wintypes are ignored.
    -- "special"    - All windows other than normal windows are ignored.
    -- table        - A list of wintypes to ignore. See :help win_gettype() for the
    --                possible values.
    -- function     - A function that returns true if the window should be
    --                ignored or false if it should not be ignored.
    --                Takes two arguments, `winid` and `wintype`.
    wintypes = "special",
  },

  -- When you fold code with za, zo, or zc, update the aerial tree as well.
  -- Only works when manage_folds = true
  link_folds_to_tree = false,

  -- Fold code when you open/collapse symbols in the tree.
  -- Only works when manage_folds = true
  link_tree_to_folds = true,

  -- Use symbol tree for folding. Set to true or false to enable/disable
  -- 'auto' will manage folds if your previous foldmethod was 'manual'
  manage_folds = false,

  -- These control the width of the aerial window.
  -- They can be integers or a float between 0 and 1 (e.g. 0.4 for 40%)
  -- min_width and max_width can be a list of mixed types.
  -- max_width = {40, 0.2} means "the lesser of 40 columns or 20% of total"
  max_width = { 40, 0.3 },
  width = nil,
  min_width = 40,

  -- Set default symbol icons to use patched font icons (see https://www.nerdfonts.com/)
  -- "auto" will set it to true if nvim-web-devicons or lspkind-nvim is installed.
  nerd_font = "auto",

  -- Call this function when aerial attaches to a buffer.
  -- Useful for setting keymaps. Takes a single `bufnr` argument.
  on_attach = nil,

  -- Automatically open aerial when entering supported buffers.
  -- This can be a function (see :help aerial-open-automatic)
  open_automatic = false,

  -- Set to true to only open aerial at the far right/left of the editor
  -- Default behavior opens aerial relative to current window
  placement_editor_edge = false,

  -- Run this command after jumping to a symbol (false will disable)
  post_jump_cmd = "normal! zz",

  -- When true, aerial will automatically close after jumping to a symbol
  close_on_select = false,

  -- Show box drawing characters for the tree hierarchy
  show_guides = false,

  -- The autocmds that trigger symbols update (not used for LSP backend)
  update_events = "TextChanged,InsertLeave",

  -- Customize the characters used when show_guides = true
  guides = {
    -- When the child item has a sibling below it
    mid_item = "‚îú‚îÄ",
    -- When the child item is the last in the list
    last_item = "‚îî‚îÄ",
    -- When there are nested child guides to the right
    nested_top = "‚îÇ ",
    -- Raw indentation
    whitespace = "  ",
  },

  -- Options for opening aerial in a floating win
  float = {
    -- Controls border appearance. Passed to nvim_open_win
    border = "rounded",

    -- Enum: cursor, editor, win
    --   cursor - Opens float on top of the cursor
    --   editor - Opens float centered in the editor
    --   win    - Opens float centered in the window
    relative = "cursor",

    -- These control the height of the floating window.
    -- They can be integers or a float between 0 and 1 (e.g. 0.4 for 40%)
    -- min_height and max_height can be a list of mixed types.
    -- min_height = {8, 0.1} means "the greater of 8 rows or 10% of total"
    max_height = 0.9,
    height = nil,
    min_height = { 8, 0.1 },

    override = function(conf)
      -- This is the config that will be passed to nvim_open_win.
      -- Change values here to customize the layout
      return conf
    end,
  },

  lsp = {
    -- Fetch document symbols when LSP diagnostics update.
    -- If false, will update on buffer changes.
    diagnostics_trigger_update = true,

    -- Set to false to not update the symbols when there are LSP errors
    update_when_errors = true,

    -- How long to wait (in ms) after a buffer change before updating
    -- Only used when diagnostics_trigger_update = false
    update_delay = 300,
  },

  treesitter = {
    -- How long to wait (in ms) after a buffer change before updating
    update_delay = 300,
  },

  markdown = {
    -- How long to wait (in ms) after a buffer change before updating
    update_delay = 300,
  },
})

To Reproduce
Steps to reproduce the behavior:

open some tsx file
tap :AerialToggle
got error

If possible, provide a minimal file that will trigger the issue:
minimal code here

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Looks like you ran :AerialInfo from inside of nvim tree. Could you run it from a tsx buffer instead?


appbar always show in custom route?

i successfully create a page that doesn't need auth base on my question #367
but why my appbar always show in my page,
any idea to not render the appbar in my custom route like login page there is no appbar in that page

To create custom pages that are not included in admin-on-rest's layout, you'll need to create your own Redux app, and incorporate admin-on-rest inside it.


Update kubeadm-upgrade.md

apt-mark hold is still required when apt-get is used with --allow-change-held-packages.
--allow-change-held-packages unholds the package but it doesn't pin the new version.
After feedback in the PR it was decided to remove these examples completely.

/sig cluster-lifecycle

That sounds good to me, I'm okay with removing the >1.1 example with the flag considering both approaches need to hold the packages again anyway, the example without the flag is more clear and explicit indeed. I'll push a new commit with the updates.

@neolit123 I made the changes and removed >1.1 examples.

I love a PR that removes more than it adds!
/approve

/label tide/merge-method-squash


clipctl disable/enable is too slow with clipmenu 7

Nowadays, because xdotool type --delay 0 "$string" mangles non-ASCII characters, I do this:

clipctl disable
Putting $string in the clipboard.
Pasting the clipboard in the target window.
Restoring the content of the clipboard.  (By the way, shouldn’t clipctl enable restore itself the content of the clipboard to whatever is first in the list shown by clipmenu?  Now I’m doing it by finding the most recently modified directory in $XDG_RUNTIME_DIR/clipmenu.7.$UID and putting the content of its file 1 in the clipboard.)
clipctl enable

But since I updated to the unreleased (I think) clipmenu 7, to take advantage of the fact that it doesn’t overwrite clips with the same first line, Steps 1 and 5 take a bit more than 100 ms each, which leads to a sensible delay when ‘typing’ in this way.
By looking at the code, I see this is due to a sleep command:
https://github.com/cdown/clipmenu/blob/1113ca8df96615aba67aa4494c7c43fb56f3dfde/src/clipctl.c#L96
I understand it is needed to ensure clipmenu is really disabled/enabled before quitting, but isn’t 100 ms too much?  Are there circumstances where it takes that long to disable itself?
As a workaround, I tried just backgrounding it in step 1 above: clipctl disable &, but this doesn’t leave enough time for clipmenud to disable itself and the $string is recorded by clipmenud.
Now I’m using another workaround: when launching clipmenud in xinitrc, I cache its PID in $XDG_RUNTIME_DIR/clipmenu.7.$UID/pid and in step 1 above, I just do kill -USR1 "$(<"$XDG_RUNTIME_DIR/clipmenu.7.$UID/pid")" as the old Bash clipctl did (without the caching of the PID).  With that, I didn’t have a leak of $string in any of my tests.
So I’m wondering if it would not be possible to check every 1 ms or so rather than every 100 ms, or first every 1 ms and then every 100 ms for the exceptionally slow cases?

Huh, 100 msec is indeed pretty high, not sure what I was thinking when I wrote it that way :-) Since MAX_STATE_RETRIES is 20 that would make 2 seconds, which is crazy.
I need to get clipmenu 7 ready for final release and hopefully will have some work on that in the coming weeks. I'll make sure this is also tweaked down. Thanks for the report!

Please try out #237, hopefully it will make this better. Thanks for reporting!

As far as I can tell, everything works fine.  Disabling/enabling each take less than 10 ms on average.


dialog.open () doesn't work

Description of the Bug
The dialog does not work as in the usage example.
Code and Logs
    def stop(self, *args):
        print("Exiting...")

        dialog = MDDialog(
            title="Alert",
            text="bla bla bla?",
            size_hint=(.8, .3),
            text_button_ok='Yes',
            text_button_cancel='Cancel',
            events_callback=self.on_exit_handler
        )
        dialog.open()
        print("Dialog!!!")

Versions

OS: Ubuntu
Python: 3.x
Kivy: 1.11.1
KivyMD: 0.103.0

@aprilahijriyan Please describe what behavior do you expect and what is going wrong

@aprilahijriyan ```python
from kivy.uix.button import Button
from kivymd.app import MDApp
from kivymd.uix.dialog import MDDialog
class Test(MDApp):
def on_exit_handler(self, *args):
print(args)
def show(self, *args):
    print("Exiting...")

    dialog = MDDialog(
        title="Alert",
        text="bla bla bla?",
        size_hint=(.8, .3),
        text_button_ok='Yes',
        text_button_cancel='Cancel',
        events_callback=self.on_exit_handler
    )
    dialog.open()
    print("Dialog!!!")

def build(self):
    return Button(on_press=self.show)

Test().run()

@Mountaino I try to handle the event when the user wants to exit the application and display a dialog. but does not work.

@aprilahijriyan Does stop() call when user tries to exit?

@aprilahijriyan This question is not related to the KivyMD library. You are misleading users!

@aprilahijriyan I showed you that the dialog box opens perfectly. If you have questions about another topic, create a new question.

@Mountaino yes, the stop() method is called when the user tries to exit, you can try it!

@aprilahijriyan In Kivy if you want to prevent application closing, you need to bind to Window.on_request_close. So your app would be
from kivy.core.window import Window
from kivy.lang import Builder
from kivymd.app import MDApp
from kivymd.uix.dialog import MDDialog

root_kv = """
BoxLayout:
    orientation: "vertical"
    spacing: dp(5)

    MDToolbar:
        id: toolbar
        title: "Title"
        left_action_items: [["menu", lambda x: None]]
        elevation: 10
        md_bg_color: app.theme_cls.primary_color

    BoxLayout:
"""

class MainApp(MDApp):
    def __init__(self, **kwargs):
        super().__init__(**kwargs)
        Window.bind(on_request_close=self.on_request_close)

    def build(self):
        self.root = Builder.load_string(root_kv)

    def on_request_close(self, window, source):
        dialog = MDDialog(
            title="Closing",
            text="Do you want to close app?",
            size_hint=(.8, .3),
            text_button_ok='Yes',
            text_button_cancel='Cancel',
            events_callback=self.on_exit_handler
        )
        dialog.open()
        return True  # Do not stop application

    def on_exit_handler(self, answer, dialog):
        if answer == "Yes":
            self.stop()

if __name__ == "__main__":
    MainApp().run()

@Mountaino thank you! but in the on_request_close () method I change the parameter to * args) this works perfectly!


[RN68] Android compliance: test project

@d4vidi where can I find the detox source code which supports RN 0.68 on Android?


[pycga] use native namespace packaging for pycga

Update pyclaragenomics module naming to use native namespace packaging convention. This will multiple independent repositories to use the claragenomics namespace without needing to be installed from the same place.
https://packaging.python.org/guides/packaging-namespace-packages/#native-namespace-packages

rerun tests


2025-04-28-lost-in-prediction

OpenReview Submission Thread

Checklist before opening a PR

[x] I am opening a pull request against the main branch of the 2025 repo.
[x] The title of my PR is exactly the name of my markdown file

i.e. _posts/2025-04-28-[SUBMISSION NAME].md would require a PR name 2025-04-28-[SUBMISSION NAME]

[x] I have anonymized my post: my author's list is Anonymous, and there is no potential
content which can reveal my/my collaborators identities.
[x] My post matches the formatting requirements, including (but not limited to):

[x] I have ONLY MODIFIED files in the following locations (failure to do so will result in
your PR automatically being closed!):

a Markdown (or HTML) file in _posts/ with the format _posts/2025-04-28-[SUBMISSION NAME].md (or .html)
static image assets added to assets/img/2025-04-28-[SUBMISSION NAME]/
interactive HTML figures added  to assets/html/2025-04-28-[SUBMISSION NAME]/
citations in a bibtex file in assets/bibliography/2025-04-28-[SUBMISSION NAME].bib

[x] I have a short 2-3 sentence abstract in the description field of my front-matter
[x] I have a table of contents, formatted using the toc field of my front-matter
[x] My bibliography is correctly formatted, using a .bibtex file as per the sample post

Any other comments

Hi, thanks for your submission! I believe we fixed our pipeline - could you please sync your fork and hopefully that should auto trigger the build process.
Note: If this applies to you, please make sure your pull request title, post filename and all references/directories are all lowercase, e.g.:
2025-04-28-Sample-Test.md               -> 2025-04-28-sample-test.md
assets/img/2025-04-28-Sample-Test/ 	-> assets/img/2025-04-28-sample-test/

and in your post:
{% include figure.html path="assets/img/2025-04-28-Sample-Test/img.png" class="img-fluid" %}
-->
{% include figure.html path="assets/img/2025-04-28-sample-test/img.png" class="img-fluid" %}

Thanks a lot for your patience and please tag me if you need any more help!

Hi @busycalibrating , thanks for your comment. Do I still need to sync if I got the submission URL?
When hovering the sync button I get a warning that my commits will be removed.


Set points in both images in DisparityAnalyzerSTAN

Currently only points in the right image are output to results.

Duplicate of #27


Compatibility issue

Error shows that this module has been compiled using Node version 59 but MagicMirror requires Node Version 57

what do I do now? the music widget shows and the usb is also detected by the pi but music does not start playing.....

Greetings
Did you ever get MMM-MP3Player working? I was able to get it installed, run MagicMirror without issues (thank you to another post where we have to rebuild some stuff for newer node.js versions), and it shows the widget on the Mirror, but doesn’t do anything once a USB stick is plugged in.
Also tried rebooting with the stick inserted, but does not play. Watching the console after
npm run start
shows it started the socket and started the MMM-MP3Player module, but no info is displayed when inserting the USB stick.


Replace event cause system

This PR proposes changes to reduce the amount of obscurity as to the actual type of primary cause returned from an event by making Cause generic and expanding the Reason system while preserving the functionality of the recursive nature that Causes currently have.
Events which have had their reasons created for them:

EntityTeleportEvent -> TeleportReason
EntityChangeHealthEvent -> HealthChangeReason
EntityDeathEvent -> DamageReason
PlayerDeathEvent -> DamageReason
EntitySpawnEvent -> EntitySpawnReason
EntityAboutToConstructEvent -> EntitySpawnReason

Events which have had cause removed:

BlockEvent -> The cause has been removed from this base event in favor of selectively adding it where applicable to its sub events. (Break/Place events are the ones I'm looking at).
EntityExpireEvent -> The cause of an entities expiration is just that, expiration.
ProjectileLaunchEvent -> The cause of a projectile launch is inferred by the included projectile source.

A builder has also been added for the creation of more complex or custom damage reasons.
Some example reason chains for two of the currently defined reasons:
EntitySpawnReason (currently used in the EntitySpawnEvent and EntityAboutToConstructEvent)

BLOCK_SPAWNING -> BlockReason
DISPENSE -> BlockReason
DROPPED_ITEM -> BlockReason/EntityReason
EXPERIENCE -> BlockReason/EntityReason
FALLING_BLOCK -> BlockReason
MOB_SPAWNER -> BlockReason
PLACEMENT -> PlayerReason
PROJECTILE -> ProjectileSourceReason
SPAWN_EGG -> BlockReason/EntityReason
TNT_IGNITE -> BlockReason

HealthChangeReason (currently used in the EntityChangeHealthEvent and EntityDeathEvent)

FOOD -> ItemReason
IN_FIRE -> BlockReason
LAVA -> BlockReason
DROWN -> BlockReason
IN_WALL -> BlockReason
CACTUS -> BlockReason
ANVIL -> EntityReason
FALLING_BLOCK -> EntityReason

@sk89q I'll leave this to you as you wanted causes.

I've updated the intent of the PR, please see the updated main description.
@sk89q I believe that this is now closer to your original intention for the Cause system, let me know what you think. It should have all of the flexibility and power of your original system but with slightly less obscurity by making the Cause generic.

I haven't gotten around to looking at everything but the removal of cause from all events means you cannot throw an event such as "block at x1, y1, z2 placed block ay x2, y2, z2" without creating your own event that no one else will listen to.

I'm not sure I see the difference between adding an event no one will listen to or a cause no one will check. Adding arbitrary causes to events is all well and good, but it relies on the listeners of the event looking for these causes.
Preferable as I see it is having the first layer of causes defined with additional causes chained after it in an arbitrary and undefined fashion. So the BlockPlaceEvent would have a defined first cause one of which may be BLOCK_SPREAD or something, which could then have a parent cause referencing the second block to be referenced if required.

Plenty of gameplay, protection and logging plugins would listen to Cause.
WorldGuard already listens to a Cause in Bukkit, which it generates on its own.
The primary purpose of Cause is not to track parent causes. Cause exits because it's unfeasible to cause parent causes.
For example, a CraftBook gate triggered by Redstone may be ultimtaely caused by a player, but because it's not reasonable to trace it to the player, Cause allows an event to be fired with the cause being the block.
Saplings that grow into trees may ultimately have been placed by a player, but because that's not possible to trace, the Cause becomes the sapling itself.

Yes, I think we agree on what a cause is or isn't. Where I think we differ is the type of information available in a cause.
If we take example of a player taking some damage from a source (Our EntityChangeHealthEvent, bukkit's EntityDamageEvent, worldguard's DamageEntityEvent) there are two (that I'll present here anyway) options for what information to include in the cause.
Option A (the world guard way): the cause includes only the damager, either block or entity.
Option B (my current proposition): the cause includes first more general cause information followed then by additional information, such as a damager if one exists.
If we narrow our example to be an entity standing in a fire block. Option A gives us a cause which contains only the fire block and leaves the listener to infer the reason of the damage being caused by that block. Whereas with option B our cause would have the structure (IN_FIRE, BlockLoc) so the reason for the damage is explicit.
Option B provides overall more information and leaves some cases as being less ambigious. For example with Option A it is impossible to detect the difference between damage from falling or damage from starving.
If I have misinterpreted the usage and extent of causes in worldguard please correct me.

There is option C, which is the current Sponge way (although not well developed), which is an extension of option A with general cause information.
In your example of an entity of a fire block, under option C:

Cause would refer to the fire block
Cause.getReason() would refer to IN_FIRE

C, which is currently what is in Sponge, is a superset of both other options.

However, it seems to me that 'cause' and 'reason' are essentially the same thing. One issue I have with option C is that the cause is non-optional while the reason is optional. With the example of falling damage the reason would be FALLING and the cause would be...null?
So I think it is applicable to a wider range of uses to have cause and reason as the same thing and chained in the fashion of option B, and we still aren't losing any information with option B over C although I think I'll streamline the objects a bit more to make them more easily usable (so its not cause.getReason().getEntity() the reason can just be the entity or something like that, thoughts on this?).
(I'd argue that the optional on cause and reason could be reversed but in my opinion this still doesn't solve the issue of being applicable to the widest array of use cases)

The cause could be the world. Personally I feel that the number of cases that are caused by a block or entity vastly outnumber the cases that don't. Pretty much every event that we have involves a player, entity, or block.
The reason I am generally for cause first is because this is the easy information to provide for most mods and plugins that modify the world, which is important because we should expect the absolute worse from developers. Its basis is on objects that already exist in Minecraft (entity, block, etc.).
Reasons are a Sponge invention, and their proper use means that a custom Reason may have to be provided, so in most cases, we can assume (assuming the worst) that the developer would just pass UNKNOWN and would forget (or more likely, not know) to specify the causing block or entity.
But as I mentioned, my main issue is not "reason first" or "cause first" -- so everything above is unimportant in the grand scheme in my opinion. My issue is that the PR doesn't implement A, B, or C -- there is no reason or cause at all on the events. It implements Bukkit's way.
BlockChangeEvent is completely useless after these changes. There is no way at all to fire an event (without creating a new one that no one will listen to) to say that a block has changed another block.

@SpongePowered/developers Feedback please.
@Deamon5550 I think Cause needs to remain an integral part of Events. Find a way to happily marriage Cause and Reason.

Yeah, its not my intention to remove the concept of a cause. I've got a fair idea of where I want to run with this, but I'll need to rewrite it.
Closing this for now.


MSQ window functions: Fix query correctness issues when using multiple workers

Description
This PR fixes query correctness issues for MSQ window functions when using more than 1 worker (that is, maxNumTasks > 2).
Currently, we were keeping the shuffle spec of the previous stage when we didn't have any partition columns for window stage. This PR changes it to override the shuffle spec of the previous stage to MixShuffleSpec (if we have a window function with empty over clause) so that the window stage gets a single partition to work on.
A test has been added for a query which returned incorrect results prior to this change when using more than 1 workers.
Sample Query
select countryName, cityName, channel,
row_number() over (order by countryName, cityName, channel) as c1,
count(channel) over (partition by cityName order by countryName, cityName, channel) as c2
from "wikipedia"
where countryName in ('Austria', 'Republic of Korea')
group by countryName, cityName, channel
order by countryName, cityName, channel

Currently, the above query gives incorrect results with maxNumTasks=5 as can be seen in the following screenshot.

With this PR's changes, the above query gives correct results, as can be seen in the added test.

This PR has:

[x] been self-reviewed.
[ ] added documentation for new or modified features or behaviors.
[ ] a release note entry in the PR description.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[x] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[x] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[ ] been tested in a test Druid cluster.

@Akshat-Jain, could you make a follow up PR to handle this: https://github.com/apache/druid/pull/16804/files#r1700096766?
Essentially, perhaps we should have a separate org.apache.druid.msq.querykit.DataSourcePlan#forQuery, which passes a result shuffle spec factory which encapsulates the logic of choosing the shuffle spec. We could then change the overriding of shuffle spec to a validation exception instead.
cc: @cryptoe

@adarshsanjeev But how would the GroupBy/Scan query kits know the ClusterBy columns (needed for the 1st window stage) with which to use the resultShuffleSpecFactory with?

Do you mean something that is available in the windowQueryKit only? That information could be passed while creating the shuffleSpecFactory.

@adarshsanjeev How can we pass ClusterBy from WindowOperatorQueryKit to the other query kits via ShuffleSpecFactory? 🤔

@adarshsanjeev Also, the ShuffleSpecFactory we pass to other query kits (from WindowOperatorQueryKit) will keep getting propagated to further query kits. But that doesn't seem right? We only want it propagated and taken into consideration through 1 layer of query kits, not all of them?


GitHub issue flair addition: "Minimal reproduction project"

Flair would be added if there is a minimal reproduction project included in the issue, enabling better prioritization by maintainers. Thoughts?

While they are handy for issues to which they are applicable, for many issues a repro project would be irrelevant.

I don't think this would help that much. My question is: do you want that to be easier for you to find potential issues to fix? If it's not for you, then it's just speculation.
While sample project definitely help pinpoint the origin of issues, in the end contributors will search issues in the area they're more familiar with.

We don't currently plan to add a mrp label, but we now require all issues to include a minimal reproduction project if asked by a maintainer.


README: Link craco-purescript-loader

I created a plugin to add purs-loader with create-react-app.
It allows you to use PureScript code.
Plugin
https://github.com/andys8/craco-purescript-loader

Merged, thank you :)


CRC-32 verification of log records

For extra protection against log corruption put a CRC-32 record checksum at the end of the log record.
This should be checked during log validation on startup.

Implemented


added int3face blockchain to the chain-registry

Added Int3face mainnet chain and assets

Let's omit to sol and ton logos until we're ready to use them (sol and ton are not in the assetlist)


test: correctly mark the test as XFAIL

This was happening to pass previously due to an unrelated error matching. This corrects the XFAIL annotation to fix the test on rebranch.
Thanks to @bnbarham for pointing out the invalid XFAIL string!

Thanks to @bnbarham for pointing out the invalid XFAIL string!

FWIW I'm actually confused about this. If I'm reading the lit.py code correctly, XFAIL: windows should currently work. This is eventually checked by:
self.value = self.token in self.triple or any(regex.fullmatch(var) for var in self.variables)

Where triple is config.target_triple. And we set:
config.target_triple = "@LLVM_TARGET_TRIPLE@"

But if you're sure it fixed it... 🤷

Oh ... I was looking at the wrong branch. LLVM has (what I consider) fixed this to no longer do a contains on target_triple! There's now a target=<target_triple> feature. So that explains this.

Sounds like a ~fire~ merge at will 🚀


1 missed record in us-ca-alameda_county.csv

There is a record in us-ca-alameda_county.csv with empty street name, around row 525352.  It should be Bigge St. Thanks for your efforts!
https://www.google.com/maps/place/10700+Bigge+St,+94577
https://www.google.com/maps/place/37°43'36.7"N+122°11'15.4"W/@37.7268605,-122.1876111

Hi @xjlin0. Thanks for the information. Since openaddresses is pulling directly from the authoritative source, one would have to contact the county directly with any corrections.  Want to take the lead and contact them?
In the future I think the intent is that there will be mechanism built in to allow reporting of errors to municipalities.

Hi Brando:
In addition, there are about ~100 records missing zip codes, could you tell me where's the source you pull from?  I might be able to find the possibilities to contact them.
Meanwhile, if I fill the empty cells, should I send you back the curated data instead?
Thanks!

So if you navigate here you'll find the list of sources, with each in a separate JSON file.  If you click on us-ca-alameda_county.json you will find the source metadata.  The data: field is the path to the source data.  Sometimes you will find a website field that might take you to the city/county/etc website.  Though there's not one for this source.
It's likely the county assessor's office. http://acgov.org/assessor/resources/
If the county makes any changes to their data it will reflected in this repository during the next run.

Closing - @xjlin0 feel free to reopen open another ticket if you have any more questions.


fix: switched result.date to result.send_at in job email condition

Hey man, great library!
In the Job email at the condition, the attribute date was wrong, should be send_at in order to compare the date well, because in the queue.js the attribute is send_at.
 if (Date.now() < new Date(result.send_at).getTime()) {
        cabin.info('It it not time yet to send message', { result });
        return;
  }

Well that's just embarrassing!  THANK YOU FOR THE FIX!


Where is the video ?

I'm sorry, I haven't upload the video. In fact, I recorded a video but the audio was bad. I will record a new one and upload it as soon as possible.

can u guide me how to install this package ? i tried scidownl.

can u guide me how to install this package ? i tried scidownl.

I will upload the video in 12 hours. It is a little complicated because a commercial captcha identification system is need. And there is only Chinese website for this captcha identification system. That's why I introduce it using video.

Hi, habeeeb4u. I have upload tutorial.md. Now you can find the detailed instructions.

Thank You !


added crontab highlighting.

add basic crontab highlighting. #681

Seems to have a syntax error at line 21.

I just tested this and did not have an issue with a syntax error. @Noammac are you sure you cloned/copied the file correctly?

Tried it again. Did
https://raw.githubusercontent.com/tommyshem/micro/744e827dd3568f63ef82c20e05191bf888f2998c/runtime/syntax/crontab.yaml
> $GOPATH/src/github.com/zyedidia/micro/runtime/syntax/crontab.yaml```

Then I executed `make runtime` and `make install` but still got the same
error.

On Thu, 1 Jun 2017 at 23:18 Zachary Yedidia<EMAIL_ADDRESS>wrote:

> I just tested this and did not have an issue with a syntax error. @Noammac
> <https://github.com/noammac> are you sure you cloned/copied the file
> correctly?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/zyedidia/micro/pull/689#issuecomment-305608483>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/ASpZq8TPxLA9OkAFXrxoqgxw7Qvse6Cxks5r_xylgaJpZM4Nso68>
> .
>

Tried it again. Did
curl -sL https://raw.githubusercontent.com/tommyshem/micro/744e827dd3568f63ef82c20e05191bf888f2998c/runtime/syntax/crontab.yaml > $GOPATH/src/github.com/zyedidia/micro/runtime/syntax/crontab.yaml

Then I executed make runtime and make install but still got the same error.

Hmm I'm not having an error when I run this. Is it possible that you are using an out-of-date version?

I'm using the latest version checked out from github (cloned using the go
get command)
On Fri, 2 Jun 2017 05:01 Zachary Yedidia<EMAIL_ADDRESS>wrote:

Hmm I'm not having an error when I run this. Is it possible that you are
using an out-of-date version?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zyedidia/micro/pull/689#issuecomment-305668691, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ASpZq7TnOk89rW8AzHs1AIXiHX-UqBj2ks5r_2zjgaJpZM4Nso68
.

The comment section is copied from fish.yaml file.
I am on Linux Arch and it works on my machine.
What os are you running ?
Does the error come up straight away or when you load the file.
If on file load could I have a copy ?
I built my micro with
make build-all
./micro
Then load file.

I'm running Ubuntu 16.04
The error comes up straight away as I have compiled micro with it (using micro version 4644a2b)
Here's a copy of the file
I built micro using make runtime and then make install but make build-all outputs the same error

Ok thanks for info. I am working so no time at minute to check over. But when I get time, I will run docker with ubuntu and try and find fault.

I have run docker Ubuntu 16.04 and pulled the version of micro you used.
Copied the curl command and compiled the files with make build-all.
Tested opening micro and no errors.
Loaded my test crontab file and the syntax highlighted as it should.
I can not find any errors.
I have had to clear out GOPATH src when I get errors running micro with syntax ymal errors and start again. (Only happen to me once)
Sorry I have no more ideas to try.
Can some else try on Ubuntu 16.04 to test ??

I'll try rm -rfing my GOPATH and then reinstalling micro (and the yaml
file) and see what happens. But I'm going to sleep and can only access my
computer on the 5th.
Let's hope that'll fix it
On Sun, 4 Jun 2017 01:44 Tommy<EMAIL_ADDRESS>wrote:

I have run docker Ubuntu 16.04 and pulled the version of micro you used.
Copied the curl command and compiled the files with make build-all.
Tested opening micro and no errors.
Loaded my test crontab file and the syntax highlighted as it should.
I can not find any errors.
I have had to clear out GOPATH src when I get errors running micro with
syntax ymal errors and start again. (Only happen to me once)
Sorry I have no more ideas to try.
Can some else try on Ubuntu 16.04 to test ??
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zyedidia/micro/pull/689#issuecomment-306005860, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ASpZq0hvDGtxFAFpCybLSL9ccFzJitkIks5sAeHbgaJpZM4Nso68
.

Tried it again, once again got the same error.

Ok last idea. Edit the crontab.yaml file and delete from line 18 onwards which will remove the comments high lighting and save it.
i.e from - comment onwards.
Then try compiling again to see if error comes up.

@Noammac there's probably something wrong with the way you are building micro from source. Make sure to use the version that is on your GOPATH and make sure you are up-to-date (git pull).
You can also try using this with a prebuilt binary (place the yaml file in ~/.config/micro/syntax).

I just completely removed my GOPATH foler, mkdir'd it again, redid the go
get -d, curled the file, did a make build-all and I still get the same
error.
Here's an interesting thing, even after I removed lines 18 and forwards and
rebuilt micro, it still had an error on the 21st line. It could be that I
put another yaml file in ~/.config/micro but I'll have to check it out
tomorrow.
On 4 Jun 2017 23:25, "Zachary Yedidia"<EMAIL_ADDRESS>wrote:

@Noammac https://github.com/noammac there's probably something wrong
with the way you are building micro from source. Make sure to use the
version that is on your GOPATH and make sure you are up-to-date (git pull
).
You can also try using this with a prebuilt binary (place the yaml file in
~/.config/micro/syntax).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zyedidia/micro/pull/689#issuecomment-306064601, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ASpZq5X_jKjRVE9o9QFjSX47a4zdbS2lks5sAxKkgaJpZM4Nso68
.

Never mind, the problem was with the hand-copied file in ~/.config/micro/syntax. This version (curld) works.

Ok, glad you got it working. Give it a try on your crontab file and let me know if the high lighting needs any work, or any hight lighting which needs removing.

Do you know if it's possible to make individual columns different colours?

the regex is in groupings but I do not know if it is possible in micro to do different colours per gruop matching like in other editors. I will look into when I get more time.


”HUNEDOARA” is listed in the drop-down menu

Description:
"HUNEDOARA" is listed in the drop-down menu alongside its corresponding county and commune, according to the law.
Precondition:
The website is up an running.

Step 1
Type "HUNEDOARA" in the search bar.

Expected results
The location is listed in the drop-down menu as "Oraș HUNEDOARA, HUNEDOARA (HUNEDOARA)".


add error handler (like while_loading)

GraphQL has a loading and error handling mechanism.
Should extend while_loading or add when_error or some similar syntax.

Would a HyperComponent be able to return a promise that would be resolved once all DummyValues disappear?


TestMergeWithArchivedWorkflows fail because actual data and expected data is dismatch.

Pre-requisites

[X] I have double-checked my configuration
[X] I can confirm the issues exists when I tested with :latest
[X] I'd like to contribute the fix myself (see contributing guide)

What happened/what you expected to happen?
https://github.com/argoproj/argo-workflows/actions/runs/6166062084/job/16734921912
Version
latest
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
no need workflows data

Logs from the workflow controller
kubectl logs -n argo deploy/workflow-controller | grep ${workflow}

Logs from in your workflow's wait container
kubectl logs -n argo -c wait -l workflows.argoproj.io/workflow=${workflow},workflow.argoproj.io/phase!=Succeeded

@sunyeongchoi just for reference, if you're already making a PR for something (especially when it's small and a follow-up to another PR, especially your own PR (#11761 in this case)), you can totally skip making an issue and go straight to PR 🙂 .
Just may need to document the PR a bit more in the "Motivation" section.
Thanks for the fixes again!

@sunyeongchoi just for reference, if you're already making a PR for something (especially when it's small and a follow-up to another PR, especially your own PR (#11761 in this case)), you can totally skip making an issue and go straight to PR 🙂 .
Just may need to document the PR a bit more in the "Motivation" section.
Thanks for the fixes again!

Thank you for your explain!!😄


Suddenly homebridge not working, error...

Version 3.5.5
I suddenly see that homebridge does not work and trying to load shows me this error:
[Broadlink] Initializing BroadlinkRM platform...
/usr/lib/node_modules/homebridge-broadlink-rm/node_modules/node-persist/src/local-storage.js:666
throw Error('[PARSE-ERROR] ' + file + ' does not look like a valid storage file!');
^
Error: [PARSE-ERROR] /home/pi/.homebridge/plugin-persist/homebridge-broadlink-rm/74525101b52fbaa4f2f9631f0c2ed99d does not look like a valid storage file!

I deleted the file /home/pi/.homebridge/plugin-persist/homebridge-broadlink-rm/74525101b52fbaa4f2f9631f0c2ed99d and homebridge started working again!
Can you explain why did this happen?
Thanks!
Refael.S

I have the same issue, also deleting the file solved the problem, but it appeared 3-4 times yet.

i had this as well. deleting it was the fix. thanks for sharing here.

The file can become corrupted, I'm working on a fix.


custom ui path not recognised

Describe The Bug
Hi!
I'm working with the homebridge-eufy-security team and have recently redesigned the custom ui screen which utilises plugin-ui-utils.
As mentioned here it should be possible to set a custom path to the ui through config.schema.json but for me this setting is ignored. It always falls back to the default ./homebridge-ui/public/index.html
I looked briefly at the source and found that this setting is read in this repo rather then plugin-ui-utils, so I've opened an issue here.
An example branch can be found here
Let me know if the issue lies somewhere else.
Logs
[9.7.2022, 10:00:15] [Homebridge UI] [homebridge-eufy-security] ENOENT: no such file or directory, open '/usr/lib/node_modules/homebridge-eufy-security/homebridge-ui/public/index.html'

Config
{
  "pluginAlias": "EufySecurity",
  "pluginType": "platform",
  "singular": true,
  "customUi": true,
  "customUiPath": "./dist/homebridge-ui"
}

Homebridge UI Version
4.49.0
Homebridge Version
1.5.0
Node.js Version
16.13.0
Operating System
Ubuntu / Debian (or a variant)
Environment Info

[ ] Using Docker?
[ ] Using Hyper-V?
[X] Using hb-service?

Raspberry Pi Model
No response

It seems to be working when I build the plugin locally:

The UI may aggressively cache the customUiPath - please make sure you've tried to do a full restart of Homebridge UI (Drop down menu top right -> Homebridge Settings -> Force Service Restart).

I did initially get this error, but it's unrelated to the problem you were facing:
[09/07/2022, 18:28:54] [Homebridge UI] [homebridge-eufy-security] node:internal/modules/cjs/loader:936
  throw err;
  ^

Error: Cannot find module '../package.json'
Require stack:
- /Users/xxxxx/src/homebridge/Homebridge-eufy-plugin/dist/homebridge-ui/server.js

Thx for your fast feedback.

The UI may aggressively cache the customUiPath - please make sure you've tried to do a full restart of Homebridge UI (Drop down menu top right -> Homebridge Settings -> Force Service Restart).

Force restart did help. But didn't realise that there is a difference to normal restart before.
This way I don't think it's suitable for our plugin since most users would face this issue. (we used default path before, but the new path would suit our new workspace structure better).
Could the path caching be reset on normal restart?

The cache is per version of the plugin, and since you can't publish the same version twice, it will never be an issue in the real world.

Expecting users to also update the UI might be an issue, you can probably get away with creating a symlink from ./homebridge-ui to ./dist/homebridge-ui and publishing it as part of the package:
ln -s dist/homebridge-ui homebridge-ui

But wouldn't users running homebridge on windows have problems with symlinks?

Probably, but you're looking at less than 2% of total Homebridge users who run on Windows natively.
Fixed in 4.49.1-test.1

Wow. Thx for the fast fix!

I forgot to mention this yesterday. You should probably move the Angular and other UI dependencies to devDependencies, as once the bundle is created you don't need these at run time, and making your users install all these packages alongside your plugin will just slow things down.

I forgot to mention this yesterday. You should probably move the Angular and other UI dependencies to devDependencies, as once the bundle is created you don't need these at run time, and making your users install all these packages alongside your plugin will just slow things down.
https://github.com/thieren/Homebridge-eufy-plugin/blob/customUiPath/package.json#L37

Yeah you're likely right. I just used the default dependencies generated by ng new when creating a new angular app.
But will look into it and move the dependencies not needed. Thx!


Issue using via package manager since build is required

According to the documentation you used this library by adding require('react-native-mock/mock'); to tests.
But react-native-mock/mock require ./build/react-native-mock.js which is not into the package when getting it via npm.
So I add to run babel node_modules/react-native-mock/src --out-dir  node_modules/react-native-mock/build  before using this library.
Is that normal ?
nb: I used the rewrite branch

This is normal, and intended. Only versions distributed through npm have the built source. Rather than that babel command, which doesnt look that great, you can do:
cd node_modules/react-native-mock && npm run build && cd -

to reuse the internal build script.

Reading the code I tried to call the react-native-mock like that require('react-native-mock/src/react-native-mock'); which seems to work the built version is only for non es6 support ?

There are almost certainly other things the build does rather than just convert to ES5 (I forget off the top of my head). So whilst this isnt advised, it does work, yes. It's likely in future versions this will become less supported.
The highly recommended solution is to either run the version from npm, or run the build script.
(Saying that, testing for the rewrite branch is incredibly useful, so if you find any issues with it, be sure to let us know!)

@RealOrangeOne where can the rewrite version be found on npm? The version currently available on npm is pretty old.

@dannycochran Currently, it can't. The rewrite branch is still Work in Progress. Hopefully there will be a beta to test soon

The highly recommended solution is to either run the version from npm

I had to fork and update the dependencies to deal with #139 so can't run via npm (see @danReynolds solution). I think that's going to be happening to most people who are upgrading > 16


[Bug]: Sugar doesn't resolve Token decimal places

Issue description

Input 3,000,000 BONK for token payment guard config
Deploy Candy Machine
Mint cost is 30 BONK instead of 3M as expected

It seems like Sugar doesn't resolve decimal places for token payments the same way it does for SOL. Ideally the handling should be same.
Relevant log output
No response
Priority this issue should have
Low (slightly annoying)

This is actually a really annoying refactor as it requires passing a Program object from the main function processing guards through multiple levels of nesting to the TokenPayment to_guard_format implementation. Or we have to know in that function which cluster we're on so we can build a RPC client and a make a network call to find out the number of decimal places in the mint.
The SOL implementation works because we know SOL always has nine decimal places.


emitting many key blocks fails

/emit_kb?n= with high numbers fails with status 500, didn't see anything in logs

this has been fixed and is already released, thank you!


Scene NetworkedObjects InstanceId issues.

(reported on Discord)
Describe the bug
NetworkedObject in the scene can be matched between client and server as softsync objects. This is done by having the PostProcessScene.cs assign an InstanceId to them. The post process scene script has a sorting algorithm to ensure that all NetworkedObjects in the scene are assigned ids in the same order. This algorithm has a bug causing it to not work if there are any NetworkedObjects which aren't directly under the hierarchy root.
To Reproduce
Steps to reproduce the behavior:

Create a scene with NetworkedObjects at different levels in the hiearchy.
Make sure 'UsePrefabSync' is deactivated in the networking manager.
Copy or clone the project and open it in another Unity editor
Press play in both editors and compare the InstanceId field on all the behaviours at runtime

Expected behavior
InstanceIds should match for the same scene this is not always the case.
Screenshots

Going to await for confirmation on if it's still an open issue before moving to our backlog

This will go away with the new GlobalObjectIdHash pattern.


Example rate-limit issues

Kinesis rate limits GetRecords requests to 5 per second per shard.  The example's "getRecords" method will quickly hit that, and by not handling the rate limit error will fail as you proceed to attempt iterating over the records.  It's recommended to sleep after every request for 500-1000ms, and to check for errors after GetRecords
http://docs.aws.amazon.com/kinesis/latest/APIReference/API_GetRecords.html
If a call returns 10 MB of data, subsequent calls made within the next 5 seconds throw ProvisionedThroughputExceededException. If there is insufficient provisioned throughput on the shard, subsequent calls made within the next 1 second throw ProvisionedThroughputExceededException. Note that GetRecords won't return any data when it throws an exception. For this reason, we recommend that you wait one second between calls to GetRecords; however, it's possible that the application will get exceptions for longer than 1 second
Python library calling sleep:
https://github.com/awslabs/kinesis-poster-worker/blob/master/worker.py

Fixed by https://github.com/sendgridlabs/go-kinesis/pull/28


Ability to backup and restore custom cluster metadata

Use case:
In case of a cluster failure I would like to be able to restore custom cluster metadata from a backup.
This includes metadata such as:

VIEWS
USERS (sys.users)
PERMISSIONS (sys.privileges)
UDFs
ANALYZERS

Feature description:
A possible way would be to always include the metadata in snapshots, and be able to add a keyword in the RESTORE SNAPSHOT statement, e.g. RESTORE SNAPSHOT repository_name.snapshot_name METADATA WITH (...), additionally to TABLE and ALL. Alternatively every metadata kind has its own keyword, such as VIEWS, USERS, etc.

@chaudum We've implemented this by https://github.com/crate/crate/pull/11149 which will be part of the next 4.5 release.
Thank you for this great feature request and description.


Publishing .NET Core images to Microsoft Container Registry (MCR)

Publishing .NET Core images to Microsoft Container Registry (MCR)
Microsoft teams are now publishing container images to the Microsoft Container Registry. There are two primary reasons for this change:

Syndicate Microsoft-provided container images to multiple registries, like Docker Hub and Red Hat.
Use Microsoft Azure as a global CDN for delivering Microsoft-provided container images.

You will use and see MCR as a storage back-end for Microsoft images. The primary way you learn about Microsoft container images and tags will be through a registry, which for most users will continue to be Docker Hub. Most of the experience you've had browsing for .NET Core container images will continue unchanged with this new model. The Docker Hub URLs you've used for Microsoft repos will continue to work, and forward to updated locations on Docker Hub. Existing Docker Hub will images will be maintained as-is.
See .NET Core Container Images now Published to Microsoft Container Registry for the most updated information on our use of MCR.
Discussion
Please share your thoughts on this change and see what others are saying at:

dotnet-docker #935

Starting with .NET Core nightly repo
On the .NET team, we started our transition to MCR with the .NET Core "nightly" repo. dotnet-nightly is now hosted on MCR and syndicated to Docker Hub. We started with the nightly repo in order to discover and fix any challenges we found with this new model before we move our higher-traffic primary container repository.
We will start publishing dotnet to MCR a bit later, in either February or March. This issue will be updated when that happens.
Repo Split
The .NET Core repo currently includes 4 major categories of tags:

sdk
aspnetcore-runtime
runtime
runtime-deps

Providing all of the tags in one place has helped with discoverability but made for a repo with an enormous README that can be challenging to navigate and consume. It is large enough that we exceeded Docker Hub README limits and had to artificially make it smaller.
Going forward, we will provide a repo for each of the tag categories listed above. We'll also provide a "product repo" that will hierarchicaly group all of our repos together. This will satisfy discoverability needs so that it will be easy to find the tags you want.
You can already see this experience with microsoft-dotnet-core-nightly. There are now multiple repos for our nightly builds:

.NET Core Nightly product repo
.NET Core SDK Nightly repo
.NET Core ASP.NET Core Nightly repo
.NET Core Runtime Nightly repo
.NET Core Runtime-deps Nightly repo

The same split will exist for the non-nightly stable repo (currently hosted at  microsoft/dotnet) when we start publishing it to MCR and syndicating it back to DockerHub.
Changes to registry URL
The biggest change is that your Dockerfiles need to be updated to point to the MCR registry in order get access to new .NET Core container tags. The same change is required for scripts or human operations that pull images via docker pull.
The following example shows the registry path, repo and tag for the .NET Core 2.2 "Nightly" SDK on MCR:
mcr.microsoft.com/dotnet/core-nightly/sdk:2.2

As comparison, the following repo and tag have been used to date for the .NET Core 2.2 "Nightly" SDK on Docker Hub:
microsoft/dotnet-nightly:2.2-sdk

The new repo URL is provided at each of the news repos. For example, the new .NET Core SDK "nightly" repo provides a box on the right where you can copy and paste the correct MCR-based repo syntax that you can use for docker pull or in FROM statements in your Dockerfiles.

Servicing existing Docker Hub tags
We will continue to service existing non-version-specific or floating tags on Docker Hub while the associated .NET Core version is supported. For example the microsoft/dotnet:2.1-sdk tag is a floating tag that will continue to be serviced for the lifetime of .NET Core 2.1. You can continue using floating tags without issue.
If you use non-floating tags, like microsoft/dotnet:2.1.504-sdk-alpine, then you will need to update your Dockerfile to use a new non-floating tag. No new non-floating tags will be published to microsoft/dotnet and microsoft/dotnet-nightly after we fully transition to MCR.
.NET Core 3.0 Preview 3 and later will only be made available on MCR.
Microsoft is a Verified Publisher
Until now, Microsoft-provided container images were considered "community images". As part of this change, we are re-classifying Microsoft as a "verified publisher" on Docker Hub. This designation should make it clearer that .NET and other Microsoft-provided images are coming from a verified source. There clearly was that expectation previously, but Docker is now making that clearer in the Docker Hub pages they host for Microsoft.
We will provide official vulnerability scanning Microsoft-provided images as a second phase of this transition.

See .NET Core Container Images now Published to Microsoft Container Registry for the most updated information on our use of MCR.


Receive one only retained message after multiple subscribes

Hi. I'm going crazy with this problem:
in the onConnected callback I have multiple subscriptions (4 of them) with qos=2.
All of the 4 topics have retained messages.
The problem is that I only get a onMessage callback for the first topic.
If I send new messages to those topics I receive all of them. The problem is related only to the retained messages that should be received after subscribe; as I said i only receive the retained message related to the first subscribed topic.
Please take a look, it's really important. thanks!

@tuanpmt help :D

help!!!

I have the same problem, albeit I'm working off an older code base but I think the code hasn't changed that much.
The problem seems to be that a single TCP packet from my mosquito server contains 3 messages in the following order, PUBHLISH, SUBACK, PUBLISH. The first two get processed fine, but the third gets discarded. Looking at mqtt_tcpclient_recv(), it only loops back if the last message was a PUBLISH, so commenting out this check resolves the issue for me:
			// NOTE: this is done down here and not in the switch case above
			// because the PSOCK_READBUF_LEN() won't work inside a switch
			// statement due to the way protothreads resume.
			//*** COMMENT OUT THIS IF STATEMENT ***
//			if(msg_type == MQTT_MSG_TYPE_PUBLISH)
//			{
			  len = client->mqtt_state.message_length_read;

			  if(client->mqtt_state.message_length < client->mqtt_state.message_length_read)
			  {
				  //client->connState = MQTT_PUBLISH_RECV;
				  //Not Implement yet
				  len -= client->mqtt_state.message_length;
				  pdata += client->mqtt_state.message_length;

				  INFO("Get another published message\r\n");
				  goto READPACKET;
			  }

//			}

I have the same issue on multiple subscribes. I only receive the retained message on the first topic. Going to try the above mentioned solution soon

Already did the test, and it seems to work fine now. Both topics receive the retained messages now. I'm running the latest version of MQTT and SDK_2.0.0
@sconwayaus, you made my day, thanks a lot


null pointer calls are not handled

The following crashes within the operator= as it is dereferencing a null pointer:
DSString* pointers;
pointers[0] = "invalid pointer";

This happens with any member function as a nullptr can call any method. This error should be caught.

The error is the fault of the user of the class, not the class itself. As a proper program would not be trying to utilize an uninstantiated object. Also, std::string does not handle this error.


feat: change wildcard behaviour in Authz

Issue #, if available:
Description of changes:
Change behavior of wildcard evaluation inside Authorization. This was previously implemented where we evaluated both MQTT wildcards (+,#) and glob wildcard (*). https://github.com/aws-greengrass/aws-greengrass-nucleus/pull/1152
Changes:

MQTT wildcards will not be evaluated and will be treated as string literals.
Glob wildcard will not respect MQTT levels now and match across levels. (eg - ab/*/c will match ab/1/2/c and ab/12/c)

Why is this change necessary:
The change was made so that wildcards in different policies are consistent with each other and particularly match IoT Core policy's behavior.
How was this change tested:
Unit tests
Any additional information or context required to review the change:
Design change Discussion: https://quip-amazon.com/9tvKA4JH4Tag/Authorization-Edge-Workflow-CX-Review
Checklist:

[ ] Updated the README if applicable
[ ] Updated or added new unit tests
[ ] Updated or added new integration tests
[ ] Updated or added new end-to-end tests
[ ] If your code makes a remote network call, it was tested with a proxy
[ ] You confirm that the change is backwards compatible

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Should this pr be closed as replaced by #1173 ?

Yes, we don't need this


Do not send loop counters to device

The CI failure is a precision error. The ONNX is also failing on main. :)

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


Docs need to be updated for widgets.

I'm using hyprlock from my package manager on Arch, and when attempting to use the image widget, I get this error:
Config error in file /home/smol/.config/hypr/hyprlock.conf at line 71: config option <image:monitor> does not exist.
Config error in file /home/smol/.config/hypr/hyprlock.conf at line 72: config option <image:path> does not exist.
Config error in file /home/smol/.config/hypr/hyprlock.conf at line 73: config option <image:size> does not exist.
Config error in file /home/smol/.config/hypr/hyprlock.conf at line 74: config option <image:rounding> does not exist.
Config error in file /home/smol/.config/hypr/hyprlock.conf at line 75: config option <image:border_size> does not exist.
Config error in file /home/smol/.config/hypr/hyprlock.conf at line 76: config option <image:border_color> does not exist.
Config error in file /home/smol/.config/hypr/hyprlock.conf at line 77: config option <image:rotate> does not exist.
Config error in file /home/smol/.config/hypr/hyprlock.conf at line 78: config option <image:reload_time> does not exist.
Config error in file /home/smol/.config/hypr/hyprlock.conf at line 79: config option <image:reload_cmd> does not exist.
Config error in file /home/smol/.config/hypr/hyprlock.conf at line 81: config option <image:position> does not exist.
Config error in file /home/smol/.config/hypr/hyprlock.conf at line 82: config option <image:halign> does not exist.
Config error in file /home/smol/.config/hypr/hyprlock.conf at line 83: config option <image:valign> does not exist.

the erroneous section of my config file in question:
image {
    monitor = DP-2
    path = /home/smol/Pictures/arch/archlinux-logo-white.png
    size = 150 # lesser side if not 1:1 ratio
    rounding = -1 # negative values mean circle
    border_size = 4
    border_color = rgb(221, 221, 221)
    rotate = 0 # degrees, counter-clockwise
    reload_time = -1 # seconds between reloading, 0 to reload with SIGUSR2
    reload_cmd =  # command to get new path. if empty, old path will be used. don't run "follow" commands like tail -F

    position = 0, 200
    halign = center
    valign = center
}

The widget code is practically a carbon copy of what is provided by the wiki.

your issue is practically a carbon copy of what is provided by #243
no images in 0.2.0


video: update .mp4 file used in test

Fixes https://github.com/GoogleCloudPlatform/java-docs-samples/issues/2545

[ x] Tests pass
[ x] Appropriate changes to README are included in PR
[ x] API's need to be enabled to test (tell us)
[ x] Environment Variables need to be set (ask us to set them)

Hang on running the cloud-client tests now. Will need to push an update on some of those if they ever finish.


Pose estimation on cropped BB

Hi all,
Thank you for your excellent work and for sharing your code and models. I want to use your model as part of my system, here is the system's description:
Input ---> Person Object Detection ---> Pose estimation for each detected BB ---> further analysis ---> output
I want to extract pose estimation for each BB but I think I will encounter two problems:

As most DL models, since BB is much smaller than the image sizes you trained your model on it won't perform well. (This is a common generalization problem in DL)
BBs may differ in size with can cause a discrepancy for the model.

I thought of one solution where I can pad each BB to match the size you trained your model on, but I thought there must be a more elegant way to approach this.
Have you tried to tackle such problem? Do you have a suggestion for me?
Cheers.

Thanks Avivsham!
According to your description, in your system, the person box will be detected. So you need to check the top-down approach: https://github.com/leoxiaobin/deep-high-resolution-net.pytorch.
Thanks

@welleast Thank you for your response.

Can you please elaborate on the differences between top-down and bottom-up? (my guess is that bottom up refers to first do the pose estimation and then the detection)
It didn't answer my question on how to deal with different BB size / input size (compare to training)

The differences you guessed are correct.
Just normalize the BB to a fixed size same with the training size.

About your second point, as I said -  "I thought of one solution where I can pad each BB to match the size you trained your model on, but I thought there must be a more elegant way to approach this." I guess there is no more elegant way, is that your point?

Maybe there is a more elegant way. Will figure out it...


fix listings in preview

fix #144

@silasmahler they're working correctly. See here for reference.


Single equal symbol is parsed as a Markdown header inside a $$ ... $$ block.

Hi,
This is more of a question than an issue.
I had a problem with a math block when I migrated from Jekyll to Hugo. A minimal example:
	input := `$$
P
=
Q
$$
`

P and Q were large matrices so I put them on separate lines.
Goldmark runs the block parsers first and the = is recognised as a header, so it renders to

$$
P

Q
$$

I guess this is an inherent limitation because passthrough is an inline parser? So even changing its priority wouldn't help because the block parsers run before the inline parsers?
adding block parser: *parser.setextHeadingParser
adding block parser: *parser.thematicBreakPraser
adding block parser: *parser.listParser
adding block parser: *parser.listItemParser
adding block parser: *parser.codeBlockParser
adding block parser: *parser.atxHeadingParser
adding block parser: *parser.fencedCodeBlockParser
adding block parser: *parser.blockquoteParser
adding block parser: *parser.htmlBlockParser
adding block parser: *parser.paragraphParser
adding inline parser: *parser.codeSpanParser
adding inline parser: *parser.linkParser
adding inline parser: *passthrough.inlinePassthroughParser
adding inline parser: *parser.autoLinkParser
adding inline parser: *parser.rawHTMLParser
adding inline parser: *parser.emphasisParser

An easy workaround is to indent the == by 4 spaces.

Do this instead:
$$
P
\\=
Q
$$

@j2kun Comments?

@jmooring  thanks for the quick reply.

Do this instead:
$$
P
\\=
Q
$$

Unfortunately that introduces a newline in the equation:

I'm expecting:

@carlohamalainen With this:
$$
P
\\=
Q
$$

I get this when using the MathJax engine:

And I get this when using the KaTeX engine:

This is a known KaTeX issue:
https://github.com/KaTeX/KaTeX/issues/437

I'm at conferences through the weekend but will take a look after. My initial impression is that a good workaround is to use the aligned environment.


Enable or disable auto loading of projects on start

Add a checkbox to projects and categories which enables or disables that projects are loaded on start, so large configurations can still startup quickly.

Done for projects, need to add for categories as well.

Done


Create  components that visually streams like PHP

In practice it is better than PHP because sibling suspense boundaries can still execute.
I think there is an argument that Next should wrap layout/layout/page boundaries with a component like this. If we don't do that, we should still make a component library that provides reusable non-primitive streaming functionality.

Closing as it's not a pattern we currently want to show.


Packed format semantics

Vulkan splits the formats into packed/unpacked. The former group's bitwise representation depends on the platform endianness. The latter is independent.
Since other backends don't provide "packed" formats, we need to apply the endianness to reverse the order of components on those formats at some point:

in the backends: this would require "packed" semantics to be exposed in HAL
in the portability layer: this would require HAL to have both forward and backward version of packed formats, some clearly unused.

Interestingly, I suspect that #2032 can be solved by applying the endianness, given that the reverse formats do exist in D3D.

Fixed DX12 by #2037, doesn't appear to be needed on Metal.


Stats

added support plus basic testing for fetching table column statistics from HMS.

@criccomini there's still work to be done here, I need more tests and to add partition stats. But I thought it might be useful to have the basics there for you to play around. Partition stats are not going to be different in terms of returned stats, it's just the artifact that the stats refer to that changes.

Awesome! I'll have a look tomorrow AM and merge in. 😀


Loading updated version of works ontology

What is this PR trying to achieve?
Material relating to Identifiers has been updated: in this version, there are only two types.  These are:

identifier: covering unique system-generated identifiers, and identifiers within public metadata that are preferred for public citation purposes

alternativeIdentifier: covering identifiers that are not preferred for citation purposes, such as previous identifiers that may occur still in outdated finding aids

[ ] Reviewed by @jtweed

I'm completely confused by this pull request.
Because the file was removed, then fully replaced, rather than updated in place, it's really hard to see what's been changed.
And I'm not sure what's in the comment above is actually reflected in the ontology. Also one of the commits looked to have changed the dates, but they are still xsd:Date and not ww:Period.

I think I need to go back and do this one again - @kenoir and I were struggling with getting my local repository to synch this morning and it looks like this is the old version, not the new one.  I'll try to get the new version in tomorrow (and will make sure we have ww:Period).


How to read de trace file( xx.tr )?

After simulation ,we get the  trace file( xx.tr ).
In the directory: SimAI/ns-3-alibabacloud/analysis :
'./trace_reader <xx.tr file>', but read nothing.

Same as #29 ,I assume you wish to trace the flow dynamics within ns3, like switch throughput, NIC throughput, and switch queue information, which would be easily visible in the newer ns-3-alibabcloud version.


Rough stab at making the default template settings-driven

This is a quick stab at converting the templating to be dynamic. I was not able to get the project to build locally, so this is completely untested, but the changes appear to be quite simple. Along with other users in the issue thread at https://github.com/lynchjames/obsidian-day-planner/issues/56 , being able to customize my default Day Planner would be a fantastic QOL improvement.

Just wanted to say that I'm eagerly waiting for this feature to be merged. I can't comment on the code (I know nothing about JS) but in case a huge +1 was going to help getting this in sooner, then here it is :)
Thanks for the work!!!

I hugely appreciate this addition as I felt it was the only major thing missing from the plugin and wanted to give it a whirl so I fixed up the build (failing due to API changes) and was able to test and fix a couple things so I'll outline them all here.
Not directly related to this PR but to get it to build I did the following:
in tsconfig.json :
remove `"inlineSourceMap": true,"
in main.ts:
On line 46 change:
    this.registerEvent(this.app.on("codemirror", this.codeMirror));

to
    this.registerCodeMirror(this.codeMirror);

The API was changed in v0.10.0 in obsidianmd/obsidian-api@2e4ac7c#diff-0eaea5db2513fdc5fe65d534d3591db5b577fe376925187c8a624124632b7466
Also, I feel like it would be nice to specify a template file instead of having to jam markdown into the tiny little config text box. The core Daily notes plugin does this but not sure how specifically. However, I'm pretty happy with the setting for now :)

@Thracky the inlineSourceMap setting has now been removed from tsconfig.json.
I decided to replace the CodeMirror event with a file modified event as the Day Planner does not need to be updated on every single change in the CodeMirror editor, modifications to the file are enough to keep the gantt chart, status bar and timeline updated.

@davidfells could you rebase from lynchjames:main to get the latest updates and make the changes @Thracky has suggested?

hello, I want to load specific markdown template. it's great to know you done it. And I had downloaded those 4 changed files with updates. Question: How can i enable it ? need I update the main.js ? thanks in advanve.

Would love to see this merged as well as this would be a big benefit over hacking the JS code to change the daily template.

:+1: would also love this feature

I am going to take this up, i made the necessary changes here and have it working locally.  However I am going to add extra functionality around templater.  If templater is installed and you provide a path to the template file then it will parse the template through templater first.

Also following this feature closely. Seems like it would add some great benefits

Closing this as stale. If you think this is still valuable, please rewrite the implementation (the code in main has been rewritten) and open another PR.


Re-export extra types from react-query

Hello!
I'm wrapping the useQuery in custom hooks to reuse them accross the application, for example:
export const useFetchTodos = (options) => {
  return useQuery('todos', todosFetcher, options)
}

The problem I'm facing is that I'd need UseQueryOptions  to be able to type it, since otherise it's any. I was thinking about opening a PR adding that type to the index.ts :
export type {
  UseQueryOptions
} from "react-query/types";

What do you think?

Hi,
I would say that it would be beneficial to reexport all types instead of exporting them one by one.
Maybe in a similar fashion like in main package like vue-query/core-types or something similar to not pollute the main entry point and avoid name clashing.
What do you think? 🤔

Why not import type directly from react-query?

It seems reasonable to make the exports as similar as possible to react-query. This will provide great DX. So far, I really like the fact that I can use the documentation for react-query with vue-query and the examples work there.

Types should be available under vue-query/types in version https://github.com/DamianOsipiuk/vue-query/releases/tag/v1.8.0


⚠ Fortnite has degraded performance

In 0b80c03, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1257 ms

Resolved: Fortnite performance has improved in 6e83f80.


Fixed #32385 -- Remove unnecessary load tag in admin base template

i18n template tags are currently loaded twice in the admin base template.
https://code.djangoproject.com/ticket/32385

@tim-mccurrach Thanks :+1: See comment.

@tim-mccurrach Thanks :+1: See comment.

buildbot, test on selenium.

buildbot, test on selenium.


Create pylint.yml: Set up Pylint Github Actions Workflow

Set up Pylint Github Actions Workflow

Used black formatter whilst developing, will switch to pylint and try to fix the errors with autopep8 or pylint-fix while paying attention in detail so as not to introduce new issues,


cannot connect to logstash on port 5044

I am testing the master ES version 5.6.2. My remote filebeat cannot access logstash via port 5044. I recommend enable 5044 port forwarding by default by adding the following line in logstash section at docker-compose.yml.
"5044:5044"

Not sure if that would be relevant, we don't have anything listening on TCP port 5044 by default.
https://github.com/deviantony/docker-elk/blob/6cd82cf47abf4c08396f34df9a789d52d0be4c07/logstash/pipeline/logstash.conf#L1-L13

maybe occupied by other program: try netstat -anp | grep 5044

@lakerzhou-lenovo I would recommend following @MarStarck advice and track which program is listening on that port. If that's Logstash it would mean you configured a custom input, which makes that port only relevant within your setup.

Hi, if you are using logstash with docker, try to make your port available for the other applications which are not in your container.
You can use the flag -p 5044 when you are installing the docker.
For example:
docker run -d --name logstash
-p 5044:5044
--restart=always
-e "XPACK.MONITORING.ELASTICSEARCH.URL=http://ELASTIC_IP:9200"
docker.elastic.co/logstash/logstash:7.0.0


New section for Community Partners [Addition]:

Description
I have  a suggestion of adding a new section to the website. We're missing an important section " community partners". It would be an addition of new section to the website which is an important one,
Solution
It would be great if we can have this section
Anything else?
No response
Code of Conduct

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

Do you want to work on this @MadhuSaini22? I can as well take this

Hii toby, Can you please let me know do we need to create new page for this section or we need to add this section to already created pages?

Hey @MadhuSaini22! You can add another section before the footer on the homepage. You can use the "Partner communities" header.

Awesome, You can Assign this to me @tobySolutions

All yours @MadhuSaini22!!


turms-client-dart miss _requestMap

in file message_service.dart ,miss _requestMap

Thanks for reporting. Fixed.