Update OutputMetadata

Description
Update OutputMetadata to https://editor.swagger.io/?url=https://raw.githubusercontent.com/iotaledger/tips/tip48/tips/TIP-0048/openapi3-core.yaml
In bindings
Motivation
It's outdated

Closed by https://github.com/iotaledger/iota-sdk/pull/1685


fix group_commit is not support on table with property light_schema_change=false

When light_schema_change is false, there is no column id in schema, now relaying wal is relying on column id, so group commit is not support on this scenario.
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


Please provide watermark position

top, bottom,center,left,right

Hi there,
I'm not currently adding new features to the V2 platform as I am now working on a cross-platform version of ImageProcessor for corefx.
https://github.com/JimBobSquarePants/ImageProcessor/blob/1bae9d492217e4e619e411a4cec66ea0304d4b23/README.md
If you wish to add the functionality please submit a pull request and I will review it.
Cheers
James

:+1: +1


Make this work for jasmine too

It should more or less work, but it might need some tweaks to command order.

I'm inclined to wait until I someone tells me they actually need this.

Looked at this more, jasmine takes all of its config via a json file which we already support via the command line options. The only real change needed is to change the --grep option for running a search because jasmine calls it something else.

I'm using jest and got this working in about 1h using the following advice to replace mocha-generate-command. I think jest runs jasmine under the hood, so this should probably work. I still haven't figured out how to get line/column numbers from jest, so not sure if the regex pattern will have to change, though I doubt that.
(defcustom mocha-jest-command "node_modules/jest/bin/jest.js --colors"
  "The path to the jest command to run."
  :type 'string
  :group 'mocha)

(defun mocha-generate-command--jest-command (debug &optional filename testname)
  "Generate a command to run the test suite with jest.
If DEBUG is true, then make this a debug command.
If FILENAME is specified run just that file otherwise run
MOCHA-PROJECT-TEST-DIRECTORY.
IF TESTNAME is specified run jest with a pattern for just that test."
  (let ((target (if testname (concat " --testNamePattern \"" testname "\"") ""))
        (path (if (or filename mocha-project-test-directory)
                  (concat " --testPathPattern \"" (if filename filename mocha-project-test-directory) "\"")
                ""))
        (node-command (concat mocha-which-node (if debug (concat " --debug=" mocha-debug-port) ""))))
    (concat node-command " "
            mocha-jest-command
            target
            path)))

(advice-add 'mocha-generate-command :override 'mocha-generate-command--jest-command)

+1 I'd be interested in this. Requesting :)

@felipeochoa
Noticed jest outputs a few random escape sequences that aren't caught by the current filter.
Something like this clears them up for me.
  ;; Clear up stray ansi escape sequences.
  (defvar jj*--mocha-ansi-escape-sequences
    ;; https://emacs.stackexchange.com/questions/18457/stripping-stray-ansi-escape-sequences-from-eshell
    (rx (or
         "^[\\[[0-9]+[a-z]"
         ""
         "")))

  (defun jj*--mocha-compilation-filter ()
    "Filter function for compilation output."
    (ansi-color-apply-on-region compilation-filter-start (point-max))
    (save-excursion
      (goto-char compilation-filter-start)
      (while (re-search-forward jj*--mocha-ansi-escape-sequences nil t)
        (replace-match ""))))

  (advice-add 'mocha-compilation-filter :override 'jj*--mocha-compilation-filter)

@jojojames not working for me (using jest), is there any extra thing to do besides using that code?

You need to combine the two posts above together.
Here's a minimal use-package setup.
(use-package mocha
  :ensure t
  :commands (mocha-test-project
             mocha-debug-project
             mocha-test-file
             mocha-debug-file
             mocha-test-at-point
             mocha-debug-at-point)
  :config
  ;; Clear up stray ansi escape sequences.
  (defvar jj*--mocha-ansi-escape-sequences
    ;; https://emacs.stackexchange.com/questions/18457/stripping-stray-ansi-escape-sequences-from-eshell
    (rx (or
         "^[\\[[0-9]+[a-z]"
         ""
         "")))

  (defun jj*--mocha-compilation-filter ()
    "Filter function for compilation output."
    (ansi-color-apply-on-region compilation-filter-start (point-max))
    (save-excursion
      (goto-char compilation-filter-start)
      (while (re-search-forward jj*--mocha-ansi-escape-sequences nil t)
        (replace-match ""))))

  (advice-add 'mocha-compilation-filter :override 'jj*--mocha-compilation-filter)

  ;; https://github.com/scottaj/mocha.el/issues/3
  (defcustom mocha-jest-command "node_modules/jest/bin/jest.js --colors"
    "The path to the jest command to run."
    :type 'string
    :group 'mocha)

  (defun mocha-generate-command--jest-command (debug &optional filename testname)
    "Generate a command to run the test suite with jest.
If DEBUG is true, then make this a debug command.
If FILENAME is specified run just that file otherwise run
MOCHA-PROJECT-TEST-DIRECTORY.
IF TESTNAME is specified run jest with a pattern for just that test."
    (let ((target (if testname (concat " --testNamePattern \"" testname "\"") ""))
          (path (if (or filename mocha-project-test-directory)
                    (concat " --testPathPattern \""
                            (if filename filename mocha-project-test-directory)
                            "\"")
                  ""))
          (node-command
           (concat mocha-which-node
                   (if debug (concat " --debug=" mocha-debug-port) ""))))
      (concat node-command " "
              mocha-jest-command
              target
              path)))

  (advice-add 'mocha-generate-command
              :override 'mocha-generate-command--jest-command))

I don't know if the ansi escape sequences print properly on github. It's easy to run mocha and then copy the escape sequence yourself if you want to get rid of them.

@jojojames thank you very much, looks like a charm, it was characters not being displayed correctly on GH


Can't POST inside docker container

Expected behaviour
Using your library across multiple OS, and it works great. However today I encountered an issue with your library, as it was suddenly returning response code -1 all the time (Failed to query). This only happens for me after I've packed it in a Docker container, so not sure if it will have to do with your library. Though I would like to have an idea or solution why this isn't working properly.
Actual behavior
If I do a raw curl query from the command line (inside the docker container) I get a 200.
But if I run the C++ application it returns code -1
https://github.com/mrtazz/restclient-cpp/blob/master/source/connection.cc#L384
Environment and debugging details

compiler and version: Docker
libcurl version and compile flags: curl 7.35.0
restclient-cpp version: 0.4.4

Looks like this has something todo with SSL: https://stackoverflow.com/questions/44073504/curl-in-docker-container-fails-b-c-of-ssl

Update: 1 step closer, it looks when I try to GET google.com it works. Probably this has something to do with trusted certificates. Is there a way I can disable it with this API?

So far I've gone the way of requiring the OS to be set up with the proper certs to connect instead of allowing to disable cert checking and verification (e.g. here). If this turns out to be a huge problem, I'd be open to revisit that decision.

Well this issue was two sided (resolved now), I hadn't installed most recent curl-openssl package. Also I have forked your library as it wasn't possible to disable SSL verification. Thanks for your response @mrtazz


Happy Eyeballs

Implement Happy Eyeballs to fallback from IPv6 if it is not supported by the next party.
IETF promotes that IPv6 should be the preference when choosing among 2 addresses. But the next party (your ISP) might not support it. So:

on a IPv6 enabled machine you can receive AAAA dns entry for www.google.com but if you continue with IPv6 over SOCKS it might fail on a proxy server side if proxy's ISP is not supporting IPv6.
if you are connecting private machine it might have local IPv4 which is unreachable by proxy, while reachable by IPv6.
To facilitate this, there should be Happy Eyeballs or similar implementation: Happy Eyeballs attempts to establish connection with both algorithms simultaneously. If IPv6 succeeded, it proceeds with IPv6 otherwise falls back to IPv4.

For the PROXY server in the middle this have one more option: proceed with Domain Name instead. This one also should be considered for better connectivity

This is mostly for Socks5ClientStream
			var targetIsIp = IPAddress.TryParse(targetHost, out var ip);
			if (!targetIsIp) // if targetHost is IP - just use IP
			{
				var dns = Dns.GetHostAddresses(targetHost);
				var ipv4 = dns.FirstOrDefault(x => x.AddressFamily == AddressFamily.InterNetwork);
				var ipv6 = dns.FirstOrDefault(x => x.AddressFamily == AddressFamily.InterNetworkV6);

				ip = ipv4 ?? ipv6; // have to take ipv4 first because ipv6 is not working most of the times and HappyEyeballs is not possible via socks due to single connection
			}


Error executing vim.schedule lua callback in the latest version from nui.nvim

Since yesterday I'm getting the following error:

I guess there's some breaking changes from nui?

The most important part of that message is cutoff. Can you post the full message, particularly the top line?
I just updated this morning and I'm not getting that error, so I think it's something other than a breaking change in nui.

for some reason notify is showing a different error.. interesting.
I had to remove it and noice in order to show the real message..
[Neo-tree ERROR] debounce  filesystem_navigate  error:  ...zi/.local/share/nvim/lazy/nui.nvim/lua/nui/tree/init.lua:185: missin
g bufnr

Hi, I'm noticing this issue as well. It happens if I open nvim on a directory and if I run the 'Neotree' command with no arguments. I found that the commit fee76c06e2bfd7d3dbb39b197fc208f6d5c0410c introduced the error message for me though since that commit only adds minimal error checking I'm guessing the issue is somewhere else. Minimal config to reproduce is below.
packer.lua
local fn = vim.fn
local packer_install_path = fn.stdpath('data') ..'/site/pack/packer/start/packer.nvim'
local packer_compile_path = fn.stdpath('config') .. '/lua/packer_compiled.lua'

if fn.empty(fn.glob(packer_install_path)) > 0 then
  packer_bootstrap = fn.system({ 'rm', '-f', packer_compile_path })
  fn.system({'git', 'clone', '--depth', '1', 'https://github.com/wbthomason/packer.nvim', packer_install_path})
  print "Installing packer, close and reopen nvim"
  vim.cmd [[packadd packer.nvim]]
end

if fn.filereadable(packer_compile_path) == 1 then
  require('packer_compiled')
end

vim.cmd [[
  augroup packer_user_config
    autocmd!
    autocmd BufWritePost packer.lua source <afile> | PackerSync
  augroup end
]]

local ok_packer, packer = pcall(require, 'packer')
if not ok_packer then
  return
end
local ok_util, util = pcall(require, 'packer.util')
if not ok_util then
  return
end

packer.init({
  compile_path = packer_compile_path,
  profile = {
    enable = true
  },
  display = {
    open_fn = function()
      return util.float({
        border = 'single',
        height = math.ceil(vim.o.lines * 0.5),
      })
    end,
  },
})

packer.startup(function(use)
  use { 'wbthomason/packer.nvim' }

  use {
    'nvim-neo-tree/neo-tree.nvim',
    branch = 'v2.x',
    requires = {
      'nvim-lua/plenary.nvim',
      'kyazdani42/nvim-web-devicons',
      'MunifTanjim/nui.nvim'
    },
    config = require('benpl.neo-tree'),
  }

  if packer_bootstrap then
    require('packer').sync()
  end
end)

neo-tree.lua
return function()
  vim.cmd [[let g:neo_tree_remove_legacy_commands = 1]]

  vim.fn.sign_define("DiagnosticSignError",
    { text = " ", texthl = "DiagnosticSignError" })
  vim.fn.sign_define("DiagnosticSignWarn",
    { text = " ", texthl = "DiagnosticSignWarn" })
  vim.fn.sign_define("DiagnosticSignInfo",
    { text = " ", texthl = "DiagnosticSignInfo" })
  vim.fn.sign_define("DiagnosticSignHint",
    { text = "", texthl = "DiagnosticSignHint" })

  require('neo-tree').setup {
    log_level = "trace",
    log_to_file = true,
    enable_git_status = true,
    enable_diagnostics = true,
    sort_case_insensitive = false,
    windows = {
      position = "current"
    },
    filesystem = {
      netrw_hijack_behavior = 'open_current',
      use_libuv_file_watcher = true,
    }
  }

end

neo-tree logs of the issue are attached below.
neo-tree.nvim.log

Was able to track it down.. this happens when position = "current"

I don't have the same problem. I'd bet it's caused by an interaction with another plugin.
What happened in the commit that @benplante identified is that I started using the window id that was current at the moment that the Neotree command was issued, whereas before this I was using the window that was current after the asynchronous loading of files is complete, just as neo-tree is about to be rendered.
If you have a session manager or lots of pop ups with status updates then they could be getting in the way and causing conflicts.

Unfortunately, I'm still noticing the error when I started fresh with a new user in MacOS 13 and ran nvim with exactly the init.lua shown below. Opening nvim with a directory passed argument or running :Neotree or :Neotree [filesystem|git_status|buffers] when window.position = 'current' seems to cause the command to fail and print the error message as @lucax88x mentioned.
local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({
    "git",
    "clone",
    "--filter=blob:none",
    "https://github.com/folke/lazy.nvim.git",
    "--branch=stable", -- latest stable release
    lazypath,
  })
end
vim.opt.rtp:prepend(lazypath)

require("lazy").setup({
  "nvim-neo-tree/neo-tree.nvim",
  dependencies = {
    "nvim-lua/plenary.nvim",
    "nvim-tree/nvim-web-devicons",
    "MunifTanjim/nui.nvim",
  },
  config = function()
    require("neo-tree").setup({
      window = {
	position = "current"
      }
    })
  end
})

I spent some time digging through the neo-tree codebase and I think I understand why this is happening, though I have zero experience writing neovim plugins so in all likelihood I'm wrong about this.
In lua/neo-tree/command/init.lua line 75-80 manager.get_state() is only called with the current window id if the position=current argument is set in the command line thus state.id differs from the current window id when the :Neotree is executed without a position arg and config.window.position = 'current'.

What happens is that for any positions other than "current", the tree belongs to the tab and there is only one instance per tab, so the id is the current tabnr. For position=current however, there can be one tree per window so the id is the winid for the window that the tree was opened in.
When the window is eventually created, all other position types just create or reuse a window based on the window position specified, while position = current is for the specific winid of the window that the command was issued in. In the case where the window focus is changed after the command is issued, using the id of the state insures that the tree is opened in the correct window and not some popup window that opened automatically at the wrong time.


FPS Drop In Grid

Currently using version 0.7.16 in FTB Unstable.
I've been using forestry and playing with bees.  I've been storing bees in refined storage.  Now when I open a grid, I get a large FPS drop, from 40+ fps to barely 5.  I've noticed that if I search for something (like coal) the fps returns to the expected 40 fps.  If I search for drone the fps drops down to around 5.
I suspect this is because bees are expensive to render.  One solution could be to only render the current "screen" of items rather than the whole inventory.  Regardless of whether bees are expensive to render I feel a feature like this would greatly benefit refined storage as a whole.

One solution could be to only render the current "screen" of items rather than the whole inventory.

That is already what is happening, it only renders what is visible.
This is clearly a Forestry issue, their bees aren't rendered efficiently. You can reproduce this by searching for bees in JEI for example.

While I understand that it is forestry's fault for rendering bees poorly I still believe there is a bug in refined storage.
In my initial scenario, with all my bees in RS, when I open my grid, I have only one bee visible on screen (as I sort by quantity) and my fps would drop to 3-5.
Moving all the bees (except for my "top" bees as they exceed 1k and I have nowhere else to put them) out of RS results in my fps returning to normal.  This is why I assumed they were being rendered regardless of if they are visible.  If nothing else this behavior odd since it sounds like items that are not visible are not rendered.
I have since moved all my bees into other storage devices and am using an ender io inventory panel to access them without issue or any noticeable fps drop.

I guess you are playing on singleplayer and not on a server?
If this is correct this issue might be related to: https://github.com/raoulvdberge/refinedstorage/issues/145

I'm assuming this FPS drop is caused by sending all the bee NBT data over the network everytime the storage changes. So, not really related I guess.

This is on a server, not single player.

Fixed!


BK Pipeline Security

Right now Buildkite is configured with admin tokens and some service accounts because it has to publish packages and run automated tests. Is there a more secure way to run tests and builds without giving such open access to the infra systems?

The yaml configuration file lists all accounts that Buildkite has access to as ENV values.
I have added a comment next to each one note how it is used.
https://github.com/MinaProtocol/mina-deployments/blob/main/src/buildkite/buildkite-central1.yaml
There were a few conversations for how to best separate or protect the access that is granted. The favored idea currently was to use a system such as Hashicorp Vault to sit in between and issue temp tokens (zero knowledge access) on demand, but adding this needed additional resources/planning.

Current status: @mkaito: Started working on porting the vault-secrets stuff to GCP

While I do that, let me explain what I'm doing.
Synopsis
I'm working on updating a HashiCorp Vault deployment that I wrote for my previous employer for use at Mina on GCP. vault-secrets is not involved. While that is based on the same architecture, vault-secrets is a NixOS module to manage server-level secrets.
@yorickvP wrote a buildkite hook that pulled secrets from a known path in Vault, constructed from a combination of BK variables such as repo and pipeline name, and injected them into the runner environment. As hooks run at the pipeline level, this made secrets effectively pipeline-isolated.
In practice, this means that an operator can place a secret in a specific path in Vault and this will then automatically be available in matching pipelines. This can be done via the vault CLI or the web interface. I recommend the former as I have little experience with the web interface.
Initial Vault and Consul setup can be quite involved, but the system is quite nice to use at runtime.
About Vault
Vault is, in essence, a REST API for secrets. It doesn't store secrets, it just provides the REST API, along with various authentication mechanisms, and various system backends (you can plug things like SSH or PostgreSQL into Vault as an auth backend). Storage is handled by Consul, which also does much more than just storage.
While both Vault and Consul are very powerful tools, the usage that concerns us here is actually very simple, and requires little involvement.
As Vault does not store any data, Vault nodes can be considered ephemeral. Consul handles all the data, including encryption at rest. Traffic between Vault and Consul should only happen over private network or an encrypted channel.
The data fed to Consul is encrypted by Vault itself. Consul can not read this data, it only stores it.
Vault uses a mechanism called Shamir Secrets, which takes the encryption key and divides it into a number of keys. The number of keys required to carry out an operation can be smaller than the total number of parts. For example, you may have 5 operators, each with their own key, but you may decide to only require 3 of them to be present for privileged action.
Vault also supports "auto unseal", where a trusted cloud service is used instead of operators.
About Consul
Consul is a networking and configuration management swiss army knife. It does a lot of things. We only want it to provide a fault tolerant HA data backend for Vault.
The smallest possible Consul deployment involves 3 nodes. The nodes are spun up using a pre-shared secret that must be available on the server. This is the only secret in the system that can not be stored in Vault itself, since it must be available before Vault itself can start.
Backups are handled by taking hot snapshots from any Consul node. The data on them is identical and coherent at any given time. This data is still encrypted, and does not need additional security.
While Vault itself is quite stable, we're going to run 2 nodes in HA mode with automatic failover. The nodes talk to each other and decide which one is active. The inactive node will reject all connections and redirect to the other node, but we'll have external health checks to route traffic to the active node.
What is actually being done
My experience with this configuration is deploying it on AWS. I have little experience with GCP, but I'm hoping there are sufficient parallels between the two services to allow a similar, hopefully identical configuration. This is what I'm currently working on: porting the deployment to GCP.


Issue downloading file from drive

Hi there, I've uploaded a png file to a Deta Drive, I can download it fine using the HTTP API but not using the Python library.
def download_file(attachment_stored_filename):
   return drive.get(attachment_stored_filename)

@app.get("/workorders/attachment/{attachmentStoredFilename}")
async def get_work_order_attachment(attachmentStoredFilename: str):
    drive_streaming_body = deta_drive.download_file(attachmentStoredFilename)
    return StreamingResponse(
        drive_streaming_body.iter_chunks()
    )

These are the relevant methods, as you can see I'm simply passing the DriveStreamingBody from the first method into the second and then using iter_chunks as suggested in the tutorial.
The error in the logs is as follows, can anyone suggest where I'm going wrong?
[ERROR]	2021-07-22T13:29:21.529Z	8dc4c713-992c-474c-bf45-526a5cc71cbe	Exception in ASGI application Traceback (most recent call last):   File "/opt/python/detalib/adapters/asgi/protocols/http.py", line 47, in run     await app(self.scope, self.receive, self.send)   File "/opt/python/fastapi/applications.py", line 199, in __call__     await super().__call__(scope, receive, send)   File "/opt/python/starlette/applications.py", line 112, in __call__     await self.middleware_stack(scope, receive, send)   File "/opt/python/starlette/middleware/errors.py", line 181, in __call__     raise exc from None   File "/opt/python/starlette/middleware/errors.py", line 159, in __call__     await self.app(scope, receive, _send)   File "/opt/python/starlette/exceptions.py", line 82, in __call__     raise exc from None   File "/opt/python/starlette/exceptions.py", line 71, in __call__     await self.app(scope, receive, sender)   File "/opt/python/starlette/routing.py", line 580, in __call__     await route.handle(scope, receive, send)   File "/opt/python/starlette/routing.py", line 241, in handle     await self.app(scope, receive, send)   File "/opt/python/starlette/routing.py", line 55, in app     await response(scope, receive, send)   File "/opt/python/starlette/responses.py", line 226, in __call__     (self.listen_for_disconnect, {"receive": receive}),   File "/opt/python/starlette/concurrency.py", line 24, in run_until_first_complete     [task.result() for task in done]   File "/opt/python/starlette/concurrency.py", line 24, in <listcomp>     [task.result() for task in done]   File "/opt/python/starlette/responses.py", line 221, in stream_response     await send({"type": "http.response.body", "body": b"", "more_body": False})   File "/opt/python/starlette/exceptions.py", line 68, in sender     await send(message)   File "/opt/python/starlette/middleware/errors.py", line 156, in _send     await send(message)   File "/opt/python/detalib/adapters/asgi/protocols/http.py", line 113, in send     self.response["body"] = body.decode() UnicodeDecodeError: 'utf-8' codec can't decode byte 0x89 in position 0: invalid start byte No errors

This is the png I used for testing:
http://clipart-library.com/image_gallery/320477.png

@timbusfield
You need to pass the media type with the response:
@app.get("/workorders/attachment/{attachmentStoredFilename}")
async def get_work_order_attachment(attachmentStoredFilename: str):
    drive_streaming_body = deta_drive.download_file(attachmentStoredFilename)

    return StreamingResponse(drive_streaming_body.iter_chunks(), media_type="image/png")

Thanks very much, I'll make sure I capture the UploadFile.content_type when the file is uploaded so that I can pass it to the StreamingResponse as the media_type when it is downloaded later

@timbusfield you could easily get the media type on the fly from the file's extension. Look at this simple example: https://github.com/abdelhai/drive-starter-python/blob/master/main.py#L19

@abdelhai you have more faith in the users than I do :) I've seen a few instances of incorrect file extensions the past.
I'd probably use a module like this one to make the conversion, if I was going to take that approach:
https://docs.python.org/3/library/mimetypes.html
The tool I'm working on should accept any file type really so I'll need to test it on quite a few different file types. Thanks for your help.


Syntax Errors in Script

When running the bash command for Debian based distros, I receive the following errors and the script is aborted:
/dev/fd/63: line 29: syntax error near unexpected token 'do'
/dev/fd/63: line 29: '@@ -35,48 +32,66 @@ while [ "$CHOICE -ne 4" ]; do'
I'm currently running Linux Mint 20.2 on a Surface Pro 4 with all dependencies installed and root password set.

Hi there! I apologize about that. This is entirely a fault on my part, which I have fixed just now. If you bump into any issues again, please tell me as soon as you can.

Thanks very much.  It's getting further, but is now erroring out on a different line:
/dev/fd/63: line 51: d: command not found
Looks like there's a misplaced tab in the middle of the word "dialog"

Thank you once again, I apologize for the inconvenience. I will do some more troubleshooting later today. In the mean time, I have removed the misplaced tab.


Remove unsupported linker flag

This flag isn't supported by zig and now errors with zig 0.11.0.
The original comment said we needed this for builds with gcc, but that no longer seems to be the case. So lets try just removing it.
Fixes #11

So this did cause ci to fail with older go versions (1.17 and 1.18): https://github.com/psanford/sqlite3vfs/actions/runs/7064275972/job/19231973944?pr=12
But it passes with current stable and oldstable (1.21 and 1.20). This is acceptable since we're not going to support EOL go versions.


:wrench: Fix Fixed a bug in the session details screen.

Issue

Nothing.

Overview (Required)

Fixed a problem in which two-digit minutes were not displayed when one-digit minutes were used.

Links

Nothing.

Screenshot

Before
After

👀


add tty support

Changes proposed in this PR

enable tty in kubernetes containers

Why are we making these changes?
allocate a TTY to support tools that need to read from stdin

Will merge when green


Update main.tf

removed the ending zero to resolve "no suitable version is available" issue
@claydanford  please approve this.

v2.5.6 released with this change. Thank you for opening the PR!


Fix for mutating in-flight cache responses

I discovered a very strange issue where when requesting the transaction receipt after submitting a transaction I was receiving the wrong value for receipt.status. After much investigation I realized what was happening:

web3's send transaction method requests the receipt for its own PromiEvent monitoring
I also request web3.eth.getTransactionReceipt() in my own tracker, which the in-flight cache lumps into a single request
When the original response comes back it is parsed by web3 using the method's outputFormatters which has an unfortunately strict line:

if (typeof receipt.status !== 'undefined') {
  receipt.status = Boolean(parseInt(receipt.status));
}

Since it is modifying the object directly, that gets passed on to the next handler, causing this to happen:

// Initial run
parseInt('0x1') // 1
Boolean(1) // true

// Second run
parseInt(true) // NaN
Boolean(NaN) // false

The solution here is to make sure that we copy the result before submitting to each handler so that the changes are not propagated. This is just one case where it caused issues for me, but I'm sure there are others. FWIW, I am also opening a PR with web3.js for this particular issue.
I'm using Object.assign in this PR, but if ES2015 is too modern this can be achieved with JSON.parse(JSON.stringify(result)) since the result should always be primitive values here anyway.

Nice report
This is an improvement but a deep clone of the response would be more correct

@kumavis Fair enough. I switched this to use clone, as I noticed it is already being used by this package.


update

Nagging Reviewer : You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 26 days with no activity and the awaiting review label has been applied.

Nagging Reviewer : You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 45 days with no activity and the awaiting review label has been applied.

I don't think this is a useful PR, there are no actual changes to TensorFlow code and the commits are just merges of old PRs. Thus, closing.


(Issue #110) Add setup files to make viya4-ark pip installable via Git

The setup.py file has been added to the project root to allow for pip installation via the "git" protocol. I also added 2 access methods to the ViyaDeploymentReport class it make it easier to use in a pip installation scenario.

Can you also add something to README to instruct on how to install using pip?

I would also recommend changing any requirements.txt entries which pin a specific version to be either >= or ~ as appropriate, once you start installing this with pip and other modules the chances of some 3rd party having the same but conflicting version requirements is high. I see @kevinlinglesas has recently made a couple of them like that, probably best to do them all.

This would also be a good opportunity to make use of command line tooling that pip can setup, for example to make it so after pip installing the project it can be run like this:
viya-ark deployment-report --namespace sas
This can be done by setting up entry_points "console_scripts" in the setup.py:
https://stackoverflow.com/questions/774824/explain-python-entry-points


Update to haskell-lsp-0.8 and fix snippet not respecting client capabilities

Closes #822
The haskell-lsp-0.8 update mainly involves importing/removing Lens imports.

LGTM


perf(semantic): avoid repeated hashing resolving bindings

WIP. Just an experiment really at this stage.

#4238  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite

@Boshen This is my attempt at #4227. It stores hashes and so avoids rehashing on every insert, but the benchmark result is meh. I've tried tweaking it in a bunch of ways, but nothing seems to make much difference.
Do you think worth tidying it up and merging? Or leave it for now and see if storing hashes in Atom and using that everywhere has more of an effect?

Let's close. This'll make future changes harder.


Support dense segmentation and oriented-point annotations

This adds support for segmentation-mask and oriented-points annotations types.

Segmentation masks are supported by loading the corresponding OME-Zarrs in a similar way to the tomogram (i.e. according to resolution).
Oriented points are currently read and displayed as regular points. We can follow up with another PR to augment that with the orientation information (e.g. with a vectors layer).
As some datasets contain tomograms with lots of different annotations (e.g. 10000), performance can suffer both while waiting for data to arrive and when interacting with napari once it has.
This also fixes an alignment issue caused by the highest resolution tomogram volume having a non-unit volume. I originally separated that into #31, but there was some overlap with the changes here, so I brought it into this PR.
Closes #22 and #23

Thanks for the review!


accuracy of second

i use this library in android and ios. when change Tab navigation and back, value of seconds part changed. example : 2 => 2.000001020

Duplicate of #51


Compatibility with transformers.ResNetForImageClassification

Minimal, reproducible example:
https://colab.research.google.com/drive/1ucUpr-PJFS2JQJ-9T5ziCKXlxcz7A2E8?usp=sharing
I am getting the following error with transformers.ResNetForImageClassification. Seems like the error happens only for GradCAM and GuidedGradCam.
ERR GradCam
Traceback (most recent call last):
  File "<ipython-input-10-db9ca3d8f319>", line 10, in <cell line: 7>
    explanations[name] = explainer.attribute(inputs, labels)
  File "/content/pnpxai/pnpxai/explainers/grad_cam.py", line 29, in attribute
    layer = find_cam_target_layer(self.model)
  File "/content/pnpxai/pnpxai/explainers/utils/utils.py", line 15, in find_cam_target_layer
    traced_model = symbolic_trace(model)
  File "/content/pnpxai/pnpxai/core/detector/detector.py", line 42, in symbolic_trace
    graph = tracer.trace(model)
  File "/usr/local/lib/python3.10/dist-packages/torch/fx/_symbolic_trace.py", line 823, in trace
    (self.create_arg(fn(*args)),),
  File "<ipython-input-5-df7d3287eee8>", line 207, in forward
  File "/usr/local/lib/python3.10/dist-packages/torch/fx/proxy.py", line 456, in __iter__
    return self.tracer.iter(self)
  File "/usr/local/lib/python3.10/dist-packages/torch/fx/proxy.py", line 327, in iter
    raise TraceError('Proxy object cannot be iterated. This can be '
torch.fx.proxy.TraceError: Proxy object cannot be iterated. This can be attempted when the Proxy is used in a loop or as a *args or **kwargs function argument. See the torch.fx docs on pytorch.org for a more detailed explanation of what types of control flow can be traced, and check out the Proxy docstring for help troubleshooting Proxy iteration errors

ERR GuidedGradCam
Traceback (most recent call last):
  File "<ipython-input-10-db9ca3d8f319>", line 10, in <cell line: 7>
    explanations[name] = explainer.attribute(inputs, labels)
  File "/content/pnpxai/pnpxai/explainers/guided_grad_cam.py", line 30, in attribute
    layer = find_cam_target_layer(self.model)
  File "/content/pnpxai/pnpxai/explainers/utils/utils.py", line 15, in find_cam_target_layer
    traced_model = symbolic_trace(model)
  File "/content/pnpxai/pnpxai/core/detector/detector.py", line 42, in symbolic_trace
    graph = tracer.trace(model)
  File "/usr/local/lib/python3.10/dist-packages/torch/fx/_symbolic_trace.py", line 823, in trace
    (self.create_arg(fn(*args)),),
  File "<ipython-input-5-df7d3287eee8>", line 207, in forward
  File "/usr/local/lib/python3.10/dist-packages/torch/fx/proxy.py", line 456, in __iter__
    return self.tracer.iter(self)
  File "/usr/local/lib/python3.10/dist-packages/torch/fx/proxy.py", line 327, in iter
    raise TraceError('Proxy object cannot be iterated. This can be '
torch.fx.proxy.TraceError: Proxy object cannot be iterated. This can be attempted when the Proxy is used in a loop or as a *args or **kwargs function argument. See the torch.fx docs on pytorch.org for a more detailed explanation of what types of control flow can be traced, and check out the Proxy docstring for help troubleshooting Proxy iteration errors

Hello @wltjr1007, thank you for reporting the issues. Please let me briefly explain why your error happens and how the latest PR fix it.
Why the error happens
Your error happens because our CAM-based explainers try to automatically find cam target layer using torch.fx.symbolic_trace which requires explicit symbol, instead of *args or **kwargs, as arguments of forward method. For example,
class YourModel(YourModelBase):
#    def forward(self, *args, **kwargs):
#        return super().forward(*args, **kwargs)
    def forward(self, pixel_values):
        return super().forward(pixel_values)

By the way, this kind of correction may also not work because symbolic_trace requires more rigorous style to the model's forward method e.g. it does not allow dynamic control in the method such as if-else. Unfortunately, transformers.ResNetForImageClassification does not satisfy the condition.
How the latest PR fix it
I simply added set_target_layer method to the CAM-based explainers and validations for it. In your case, now, you can manually set the target layer as followings:
explainer = GradCam(model)
attrs = explainer.set_target_layer(model.resnet.encoder).attribute(inputs, labels)

Thank you once again for the reporting issues.


Snake Game using JavaScript, Html and CSS

I am Nandini Dasgupta a frontend developer. I would like to add this Javascript based game
Could you please assign this to me as a GSSOC'21 participant?

Sure go for it @nandini2110 :)


fix: carry gateguard in EphmeralFile

Ephemeral files cleanup on drop but did not delay shutdown, leading to problems with restarting the tenant. The solution is as proposed:

make ephemeral files carry the gate guard to delay Timeline::gate closing
flush in-memory layers and stable references to those on Timeline::shutdown

Fixes: #7830

I am overall worried how difficult are these enterings to debug. I was thinking of the list/collection/set in Gate but that would not really have told me much (inmemlayer was holding it). I would have needed a tool to show that this arc pointer is reachable through timeline -> timeline::write_lock -> TimelineWriterState::open_layer.

Created a take2 version of this PR, rationale: https://github.com/neondatabase/neon/pull/8332#issuecomment-2219882645
This PR still has good fixes like the anyhows, optimization for likely_resident_layers etc. but I will try to eventually commit them separately.

We had the call, I now understand the rationale for not failing LayerManager::layers() and callers after we've shut down the LayerManager.
I really like this impl, will do more review on it but I think this is the way to go because of the robustness-in-depth it provides.
In contrast, the alternative idea in https://github.com/neondatabase/neon/pull/8332 is to
use a separate gate for EphemeralFile so we can order the removal of the InMemoryLayer from layer manager strictly after the Timeline::gate has closed.
That's quite clever, but doesn't have the same robustness-in-depth.
To the annoyance of everyone involved, I would like to entertain a third option: instead of making the LayerManager have a shut-down state, we could also push that down into the InMemoryLayer: make it an enum { Open(...), Frozen(...), ShuttingDown }.
I can imagine it would result in slightly fewer error bubble ups required, because we only interact with InMemoryLayer on the data path, and data path already has PageReconstructError::Cancelled.
Sorry I didn't think about this earlier.

To the annoyance of everyone involved, I would like to entertain a third option: instead of making the LayerManager have a shut-down state, we could also push that down into the InMemoryLayer: make it an enum { Open(...), Frozen(...), ShuttingDown }.
I can imagine it would result in slightly fewer error bubble ups required, because we only interact with InMemoryLayer on the data path, and data path already has PageReconstructError::Cancelled.

The difference between the implemented solution alternatives and the above is that this version does not allow read operations to complete (detect cancellation or succeed with the read). The alternative with the additional gate lets them complete.
Humoring the proposed third option:

currently the frozen-ness is handled via an OnceCell (not enum)
in this solution all of the in-mem layers would be cleaned up with this state transition?

would require moving the cleanup from drop to state transition, no problem there

I'll cleanup the conflict soon-ish and ask a wider opinion.

I played with moving the enum{} wrapper up into Timeline, and it works, but the bulk of the code churn remains of course in changing all the infallible code paths to be fallible, so it's not much of a net benefit.
In future, what we really need is some ActiveTimeline guard that holds a gate and ensures the interior timeline is not shut down, so that it can do infallible access to the layer map.  An outer class that implements the "stuff that only makes sense if a timeline is active" stuff could be a step in the direction of breaking up Timeline a bit (in future))

In future, what we really need is some ActiveTimeline guard that holds a gate and ensures the interior timeline is not shut down, so that it can do infallible access to the layer map. An outer class that implements the "stuff that only makes sense if a timeline is active" stuff could be a step in the direction of breaking up Timeline a bit (in future))

CF the Handle added in https://github.com/neondatabase/neon/pull/8339/files#diff-903846e8f4524450320e7bd111f5fb36159867c47edab206b5b3ed8e62f85f48R81-R93

We also had a second session on the unified signal refactoring.


App Store upload problem - non-public API use

Hi,  do you experience the same problem as me? I am using Ably in my iOS app and I cannot upload it to App Store since I am getting this error:
ITMS-90338: Non-public API usage - The app references non-public selectors in Frameworks/Ably.framework/Ably: initWithURLRequest:, readyState, send:, setDelegateDispatchQueue:. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed.
is this known error? How should I proceed?
Thanks!

Hi @cibetik - we were not aware of this as nobody else has reported submission issues. That is really interesting and apologies for any inconvenience. We'll take a look.
Additional information that would help us is:

Which version of this SDK are you using?
How are you integrating the SDK into your project - either:

Are you using Carthage? If yes, specify the version (carthage version)
or, are you using Cocoapods? If yes, specify the version (pod --version)

Thanks.

@QuintinWillison thanks for reply!
I am using Carthage 0.37.0
versions:

github "ably-forks/SocketRocket" "0.5.2-ably-7"
github "ably/ably-cocoa" "1.2.3"
github "ably/delta-codec-cocoa" "1.2.0"

PJ

Hmm, very curious. This particular ITMS complaint seems to be reported by many but, in the quick read I've had of responses to questions out there, there is little concrete indication of a single solution or even a way to get local build tools to spot this ahead of app submission.
We'll take a closer look and get back to you. Thanks for the report.

Hi @cibetik, we believe this is related with a dependency we use called SocketRocket. Could you tell us what's the minimum deployment target of your app? Do you still support iOS 12 and older?

It's worth mentioning that we have https://github.com/ably/ably-cocoa/pull/1090 yet to land (compiles SocketRocket sources within our SDK, rather than via dependency), though that may not fix this either.
From our internal Slack conversation, we may need to refactor to use URLSessionWebSocketTask - however that class is only available from iOS 13.0 runtime and later.

Method names reported by Apple are pretty random, f.e. here - https://developer.apple.com/forums/thread/656894
I think we just have very misleading error message here and renaming will not help. Probably they detect private API call somewhere in the source code and just report topmost method name as a cause. The real question is why not all users report this? WDYT @lukasz-szyszkowski @ben-xD

That's interesting why it's not reproducible on the Apple side. Is it still happening or it was just a "one-shot"?

@cibetik Couldn't you please update us on this issue?

We've not been able to reproduce this and @cibetik has not got back to us with any indication that this is still causing an issue.


Make pages with custom permissions more discoverable

Describe the feature you'd like
If you share a page directly (through page custom permissions, but without any permissions on the book/chapter the page is in) with another user, the only way for that user to discover the page is:

through direct link to the page
through the "recently updated/viewed pages" dasbhoard
through clicking on the little arrow at the top of the page once you are in a shared page (which will let you see all pages for the book shared in this way)

I think it should be possible to discover pages with direct permissions through regular Books menu - the Books menu should show the entire path (Book->Chapter->Page) to the page, but only show books/chapters that have at least one page for which the user has at least View permissions.
Describe the benefits this feature would bring to BookStack users
Pages that have direct permissions set in this way are not discoverable by any user-friendly means. Accessing direct links by the user is not practical for any sort of knowledge base and "recently updated pages" dashboard may not contain the page user is looking for (plus, no user would look there for specific page).
Clicking the little arrow is not usable - most users will not even think to look there (as all the other content is accessed through the Books menu) and it will only offer pages from the same book (but the user has no way of knowing which page belongs to which book).

Thanks for the suggestion @pavlkx.

the Books menu should show the entire path (Book->Chapter->Page) to the page, but only show books/chapters that have at least one page for which the user has at least View permissions.

To be honest I don't want to go down that route. For that to occur, there'd be specific permissions applied to those pages and chapters to prevent viewing.  I think a solution along the lines of #182 may be more suitable.

All right, I understand if you do not want to do it this way. #182 would solve this problem as well and will benefit other use cases too.
Let's close this suggestion then, thank you for taking the time to consider it.

Thanks for your understanding.
Closing as suggested.


what is    effect about it ? I  don't have   this directory

That's the directory into which uv will install Python, if you use uv python install.

thanks ,  and I  want to know   that   how to  use uv  to  show current   python version  of using


Add domain for unitama.ac.id

@pasnur-unitama First stage of verification passed, official domain for Universitas Teknologi Akba Makassar is unitama.ac.id as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@pasnur-unitama Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


Prep for Rails 8: Define enums with positional arguments

Thanks for creating an issue! Please fill out this form so we can be sure to have all the information we need, and to minimize back and forth.

What are we trying to do?

What feature or behavior is this required for?

How could we solve this issue? (Not knowing is okay!)

Anything else?

From the tests:
DEPRECATION WARNING: Defining enums with keyword arguments is deprecated and will be removed
in Rails 8.0. Positional arguments should be used instead:

enum :role, {:cm=>0, :data_volunteer=>1, :admin=>2}
 (called from <class:User> at /home/runner/work/dcaf_case_management/dcaf_case_management/app/models/user.rb:30)
DEPRECATION WARNING: Defining enums with keyword arguments is deprecated and will be removed
in Rails 8.0. Positional arguments should be used instead:

enum :age_range, {:not_specified=>:not_specified, :under_18=>:under_18, :age18_24=>:age18_24, :age25_34=>:age25_34, :age35_44=>:age35_44, :age45_54=>:age45_54, :age55plus=>:age55plus, :bad_value=>:bad_value}
 (called from <class:ArchivedPatient> at /home/runner/work/dcaf_case_management/dcaf_case_management/app/models/archived_patient.rb:21)
DEPRECATION WARNING: Defining enums with keyword arguments is deprecated and will be removed
in Rails 8.0. Positional arguments should be used instead:

enum :status, {:reached_patient=>0, :left_voicemail=>1, :couldnt_reach_patient=>2}
 (called from <class:Call> at /home/runner/work/dcaf_case_management/dcaf_case_management/app/models/call.rb:10)
DEPRECATION WARNING: Defining enums with keyword arguments is deprecated and will be removed
in Rails 8.0. Positional arguments should be used instead:

enum :config_key, {:insurance=>0, :external_pledge_source=>1, :pledge_limit_help_text=>2, :language=>3, :resources_url=>4, :practical_support_guidance_url=>5, :fax_service=>6, :referred_by=>7, :practical_support=>8, :hide_practical_support=>9, :start_of_week=>10, :budget_bar_max=>11, :voicemail=>12, :days_to_keep_fulfilled_patients=>13, :days_to_keep_all_patients=>14, :shared_reset=>15, :hide_budget_bar=>16, :aggregate_statistics=>17, :hide_standard_dropdown_values=>18, :county=>19, :time_zone=>20, :procedure_type=>21, :show_patient_identifier=>22, :display_practical_support_attachment_url=>23, :display_practical_support_waiver=>24}
 (called from <class:Config> at /home/runner/work/dcaf_case_management/dcaf_case_management/app/models/config.rb:46)
DEPRECATION WARNING: Defining enums with keyword arguments is deprecated and will be removed
in Rails 8.0. Positional arguments should be used instead:

enum :event_type, {:reached_patient=>0, :couldnt_reach_patient=>1, :left_voicemail=>2, :pledged=>3, :unknown_action=>4}
 (called from <class:Event> at /home/runner/work/dcaf_case_management/dcaf_case_management/app/models/event.rb:12)
DEPRECATION WARNING: Defining enums with keyword arguments is deprecated and will be removed
in Rails 8.0. Positional arguments should be used instead:

enum :role, {:cm=>0, :data_volunteer=>1, :admin=>2}
 (called from <class:User> at /home/runner/work/dcaf_case_management/dcaf_case_management/app/models/user.rb:30)

on it


Bug 1769003: Implement Structural Schema for CRDs

oc explain recently broke when OLM was rebased on top of version 1.16 of Kubernetes. This is due to the introduction of [CRDs Structural Schemas]([1] https://kubernetes.io/blog/2019/06/20/crd-structural-schema/). This PR updates OLMs CustomResourceDefinitions to include a structural schema.

/bugzilla refresh

/retest

/hold
Unit and e2e tests must be updated.

The changes look good. I assume this is still in progress since all tests are not updated with the changes. I liked the checks to prevent unessasry copies.

/retest

Fixed #1155

/retest

/retest

/cherry-pick release-4.3

/retest

/retest

/retest

/retest

/test unit

/retest

/lgtm
test failures look unrelated

/retest

/retest

/retest
level=info msg="Destroying the bootstrap resources..."
level=info msg="Waiting up to 30m0s for the cluster at https://api.ci-op-m2v6p4rc-0af52.origin-ci-int-aws.dev.rhcloud.com:6443 to initialize..."
level=info msg="Cluster operator insights Disabled is False with : "
level=info msg="Cluster operator machine-config Available is False with : Cluster not available for 0.0.1-2019-12-10-125713"
level=info msg="Cluster operator machine-config Progressing is True with : Cluster is bootstrapping 0.0.1-2019-12-10-125713"
level=error msg="Cluster operator machine-config Degraded is True with RequiredPoolsFailed: Failed to resync 0.0.1-2019-12-10-125713 because: timed out waiting for the condition during syncRequiredMachineConfigPools: pool master has not progressed to latest configuration: configuration status for pool master is empty: pool is degraded because nodes fail with \"3 nodes are reporting degraded status on sync\": \"Node ip-10-0-128-174.ec2.internal is reporting: \\\"machineconfig.machineconfiguration.openshift.io \\\\\\\"rendered-master-c877ee86b24ddae29e2b2a56e9167162\\\\\\\" not found\\\", Node ip-10-0-130-226.ec2.internal is reporting: \\\"unexpected on-disk state validating against rendered-master-c877ee86b24ddae29e2b2a56e9167162\\\", Node ip-10-0-155-146.ec2.internal is reporting: \\\"unexpected on-disk state validating against rendered-master-c877ee86b24ddae29e2b2a56e9167162\\\"\", retrying"
level=info msg="Cluster operator support Disabled is True with NotAuthorized: Reporting was not allowed: your Red Hat account is not enabled for remote support or your token has expired"
level=fatal msg="failed to initialize the cluster: Cluster operator machine-config is reporting a failure: Failed to resync 0.0.1-2019-12-10-125713 because: timed out waiting for the condition during syncRequiredMachineConfigPools: pool master has not progressed to latest configuration: configuration status for pool master is empty: pool is degraded because nodes fail with \"3 nodes are reporting degraded status on sync\": \"Node ip-10-0-128-174.ec2.internal is reporting: \\\"machineconfig.machineconfiguration.openshift.io \\\\\\\"rendered-master-c877ee86b24ddae29e2b2a56e9167162\\\\\\\" not found\\\", Node ip-10-0-130-226.ec2.internal is reporting: \\\"unexpected on-disk state validating against rendered-master-c877ee86b24ddae29e2b2a56e9167162\\\", Node ip-10-0-155-146.ec2.internal is reporting: \\\"unexpected on-disk state validating against rendered-master-c877ee86b24ddae29e2b2a56e9167162\\\"\", retrying"
2019/12/10 13:53:30 Container setup in pod e2e-aws-olm failed, exit code 1, reason Error
Another process exited

/retest

Failures seem to be related to this bugzilla

/retest

/retest

/retest

/retest

/retest

CI policy issue
/Retest

/retest

/retest
template pod "e2e-gcp" failed: the pod ci-op-mhv3c6t5/e2e-gcp failed after 8m17s (failed containers: setup, test): ContainerFailed one or more containers exited

/test e2e-gcp

/test e2e-gcp

/retest

/retest
New error:
I1211 17:12:06.456907     275 gce.go:871] Using DefaultTokenSource &oauth2.reuseTokenSource{new:jwt.jwtSource{ctx:(*context.emptyCtx)(0xc000054278), conf:(*jwt.Config)(0xc00189de60)}, mu:sync.Mutex{state:0, sema:0x0}, t:(*oauth2.Token)(nil)}
W1211 17:12:06.521825     275 gce.go:468] No network name or URL specified.
I1211 17:12:06.776151     275 gce.go:509] managing multiple zones: [us-east1-b us-east1-c us-east1-d]
Dec 11 17:12:08.744: INFO: lookupDiskImageSources: gcloud error with [[]string{"instance-groups", "list-instances", "", "--format=get(instance)"}]; err:exit status 1
Dec 11 17:12:08.744: INFO:  > ERROR: (gcloud.compute.instance-groups.list-instances) could not parse resource []
Dec 11 17:12:08.744: INFO:  >
Dec 11 17:12:08.744: INFO: Cluster image sources lookup failed: exit status 1

/retest

/retest

/retest

/hold cancel

/retest

/bugzilla refresh


use PowerShell to get schema version

for...
https://docs.microsoft.com/en-us/troubleshoot/windows-server/identity/find-current-schema-version
...you can do this using PowerShell;
Get-ItemProperty  'AD:\CN=Schema,CN=Configuration,DC=corp,DC=contoso,DC=com' -Name objectVersion

@anwarmahmood1 Thank you for your feedback. I am working on this.

Hi, I have updated the article as suggested. Thank you for the feedback.


Test https://reviews.llvm.org/D139308

This is duplicate of https://github.com/iree-org/iree/pull/11454 :) .

ha, got it!


Time delag/lag when adding new tasks to work items

I have noticed that there is at least a 15-20 seconds delay till the tasks get generated after clicking the extension. Is anyone else facing this delay?

Yes, I am getting the same. started happening a week or 2 ago, you press the one click and seems like 20 seconds before it starts adding the tasks and then its taking about 2 seconds a task,

Also have this issue.

Yes, I am also facing the same problem

Also having this issue.

Has anyone found a solution to this?


Fix ImagePullTimeout to use "Initialized"

Fixes https://github.com/tektoncd/pipeline/issues/7881.
ImagePullBackOffTimeOut currently uses the "Scheduled" pod condition transition time, however a pod can be scheduled on a node far earlier than when image pulling begins which can (and does) result in Tasks failing when image pulls could be retried and succeed.
We should use the transition time for "PodReadyToStartContainers" (1.29+) / "Initialized" for checking the image pull timeout as these conditions more accurately capture when the image pull began.
Changes
This commit updates the imagePullBackOffTimeOut logic to use the "PodInitialized" or "PodReadyToStartContainers" Pod Condition in favour of "PodScheduled" and adds the covering tests.
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
[x] Has Tests included if any functionality added or changed
[x] pre-commit Passed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
[ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
Fix ImagePullTimeout to use "PodInitialized" or "PodReadyToStartContainers" PodCondition transition time

/kind bug

/approve

/lgtm
thank you @skaegi 👍


drivers: ssd16xx: Imlement better partial refresh

Overview
There is currently no way to specify different configuration overrides for different refresh types (full/partial). This pull request addresses that by introducing different refresh profiles in the device tree. There is also no way to use partial refresh on SSD168x devices that are able to select partial refresh LUTs from OTP. This pull request addresses these deficiencies.
It consists of three major changes:

drivers: ssd16xx: Use device-specific compatibles
drivers: ssd16xx: Update DT bindings for multiple profiles
drivers: ssd16xx: Add support for partial refresh profiles

Device-specific compatibles
The SSD16xx driver currently provides basic support for most chips in the Solomon Systech SSD16xx range of e-paper drivers. We currently use the SSD1608, SSD1673, SSD1675A, and SSD1681 in various boards
supported by Zephyr.
The main user-facing difference between the various SSD16xx chips is the resolution they support (sources & gates), but there are other differences as well. For example:

8 or 16 bits used to represent x coordinates
8 or 16 bits used to represent y coordinates
Differences in refresh configuration (SSD16XX_CMD_UPDATE_CTRL2)
Differences in LUT sizes

The driver currently assumes that the user specifies the number of bits used to describe coordinates. However, as we add support for more chips, more of the differences will become apparent and need workaround.
Comparing data sheets from different chips in the SSD16xx range suggests that there are (at least) two different generations present. These differ in the size of the LUTs they expect and the way they handle partial refresh. This impacts register layout where SSD16XX_CMD_UPDATE_CTRL2 uses bit 3 selects "mode 2" whereas older
devices uses this for a mode referred to as "initial".
In order to add support for partial refresh in newer devices, we need to be able to distinguish between the different generations of the chip. It might be possible to add a DT property to indicate the revision, but that seems like a bit of an anti-pattern and it would be hard for users to specify the correct chip generation.
This change introduces chip-specific compatible strings instead of the generic SSD16xx. There is unfortunately clear pattern that can be used to distinguish different generations, so the full chip name must be specified. A benefit of this is that we don't need to specify the width of the fields describing coordinates in device trees.
Add support for separate refresh profiles
Add support for separate partial and full refresh profiles. This makes it possible to use partial refresh on generation 2 devices which are able to store partial refresh LUTs in OTP.
Partial refresh is only enabled if a partial profile has been provided. The display will use the full refresh profile if in this case.
Devices that need custom LUTs and voltages can specify them separately for the full and partial profiles. The controller will be reset when changing profiles which means that profiles always override the default reset values. This means that it is, for example, possible to use default values and LUTs from OTP for a full refresh and a custom profile for partial refreshes.
For example, to use a GoodDisplay GDEY027T91 with partial refresh simply use the following device tree fragment:
display: ssd1680@0 {
	compatible = "solomon,ssd1680";

	spi-max-frequency = <4000000>;
	duplex = <SPI_HALF_DUPLEX>;
	reg = <0>;

	dc-gpios = <&arduino_header 15 GPIO_ACTIVE_LOW>;
	reset-gpios = <&arduino_header 14 GPIO_ACTIVE_LOW>;
	busy-gpios = <&arduino_header 13 GPIO_ACTIVE_HIGH>;

	/* Enable the built-in temperature sensor */
	tssv = <0x80>;

	width = <264>;
	height = <176>;

        /* Enable partial refresh using built-in LUT */
	partial {
	};
};

Updated device profiles
Since this change introduces different partial and full profiles, it also updates multiple in-tree boards. These boards have been updated with the configuration from the match GoodDisplay example code.
Testing
This has so far only been tested on a GDEY027T91. I don't own any boards using the older controllers, so I would really appreciate it if someone with access to boards using SSD1608/SSD1673/SSD1675A could test this change on their devices.

NB: This change depends on https://github.com/zephyrproject-rtos/zephyr/pull/47712. The commits that are a part of that PR should be reviewed there. I'm posting this PR before the other one has been merged primarily to get early feedback on the DT changes. I will rebase it once that change has been merged.

@galak Could you review the DT changes please? In particular, is using hard-coded node names the best way to specify different display profiles?

@galak Could you review the DT changes please? In particular, is using hard-coded node names the best way to specify different display profiles?

Will take a look, off the top of my head that seems ok.  Will see if I think of any better way to handle that.

@mbolivar-nordic I don't think we have a way to specify a node name as part of a binding, seems like that might be useful.

You're right, we don't have that.

Wonder if we have some other cases of specific node names being utilized.

Child nodes of the fixed-partitions compatible are all named partition.

@jfischer-no I have rebased this change onto the latest main after the opt overrides PR was merged. This is now ready for review.

@jfischer-no @galak ping

For GDEM029T94 used in waveshare 2.9inch display V2 there are needed additional patches.
They are here:
https://github.com/korneliuszo/zephyr/tree/ssd16xx-partial-v3

@andysan , I have cleared the 3.2 milestone and this is past the release freeze date. Kindly pick a milestone for a future release.

@galak Could you revisit this?

@andysan It would be nice if you picked it up again and rebase, thanks.

@andysan It would be nice if you picked it up again and rebase, thanks.

Happy to do so, but I'll need to wire up the dev board again to test it. As far as I can tell though, there has been no conclusion on the topic of device trees. @galak any thoughts on the best way of solving the DT design?

@andysan please rebase


Add oidc-react to documentation

Hello 👋
I have built an oidc-client-based React component to make it easier to implement authentication for React developers. I'd love to get more users to use it and subsequently more contributors!
The motivation behind oidc-react is that most other solutions out there are unfinished, outdated or too complicated. For most users, familiar API design is the most important thing, and nowadays we utilize React Hooks. oidc-react handles most authentication flows, that also is supported by oidc-client-js, but it does not introduce a multitude of features and complexity.
Main repository: https://github.com/bjerkio/oidc-react
Example implementation with React: https://github.com/cobraz/example-oidc-react
Example implementation with Next.js: https://github.com/cobraz/nextjs-oidc-react

@cobraz Is the Next.js example moved/deleted/private? I get a 404 when I try to check it out.

it was, sorry about that. It's available publicly now!

Added to the wiki


Update the GetCppWinRTMdMergeInputs target to not depend on the Midl target.

With #491, the Midl target is invoked twice in multi-pass builds used in razzle. This PR removes the target dependency that caused this as it is not necessary.
It also adds DependsOn properties so the build dependencies are more clear.

I'm not in favor of the DependsOn properties.  If they're meant as extensibility points, then they should append to their existing values.  If not, then they just move the dependencies far away from their points of reference, making things less clear, and the targets file larger.  I'd rather we be intentional about adding extensibility points.

@Scottj1s They were helpful to understand the dependencies and you can already inject targets anywhere using BeforeTargets/AfterTargets, but I can certainly remove them again.


Import a road noise layer. https://github.com/acteng/atip/issues/491

The preprocessing steps take a bit. road_noise.pmtiles should be 200MB. Please upload to both buckets. I can send the file if it's easier

Or copy from https://atip.uk/layers/v1/road_noise.pmtiles


Improve Assign statement to local variable

Added ASComepleteTests.GetExpression
[Haxe] Fixed generation of Assign statement to local variable for callback
@Neverbirth @elsassph please review this PR

Guys?

I was going to check it yesterday at night, but you kept pushing commits heh. I will try to take a look into it today night.

Okay, then I'm not going to push until

@Neverbirth  please look, I can not do anything further ((

;(

As discussed, there is part of this that I will probably change, so please, don't work extensively over it. I will do my best... sadly I'm overloaded.


Can't commit files in subfolders

Step 1: create a new project in Visual Studio.  Create a new project in, say, C#.  Let's stick with a Console Application because it's easy (it's the C# version of printf/scanf).
MAKE SURE THAT YOU CLICK ON 'Create directory for the solution', so that stuff shows up in subfolders:

Click ok to create it.  Quiz Visual Studio at this point, then move the folder containing all the VS stuff into a repo that Elegit knows about, like so:

At this point Elegit will notice that a bunch of new files have been added:

BUG: Clicking on the 'Add' button doesn't do anything.  I expected it to add the files, but it doesn't. The Commit button confirms that there's no staged files because it gives an error message when I try to commit.
Am I doing something wrong?  If I (and my students) are just using Elegit wrong I would be thrilled to know that there's a fix on my side :)
Also - is there a way to find the version number of Elegit?  I can't find an 'About' box menu item.

Easy thing to answer: Elegit doesn't have an "About" at the moment (#488), but you can find the version number by going to the directory where the executable is stored, then into the 'app' subdirectory. The jar inside that should be named with the version.

As far as adding files, you aren't doing anything wrong, this is a bug.
Notes to the team: a possible quick fix is making the select all option do something along the lines of git.add().addFilePattern(".");. This will add all files and make it possible to add these difficult files. That being said, it appears to be a jgit bug that it doesn't work to add a single file within a directory. A possible hacky fix is setting the workingtreeiterator subtree iterator to something that only adds the file(s) you want to add.

Any chance that it is spitting out any exceptions? You won't see them if you run it directly via double clicking in the icon, but if you can find the jar file it's firing up you can run "java -jar ..." from the command line and exceptions should hopefully get dumped out to the terminal window.
Version number: it's not in there yet, and it has also occurred to me that we need it. I'm adding that as a new issue (#489).

Thanks, Eric -- I got interrupted while composing the answer and you get in before me, well done. :) And we both opened the same issue. I'll combine 'em sometime.

Oh, and yuck that it's a jgit bug. Blech. @erictwalker18 , do you know if there's a jgit bug report for that>

I couldn't find any exceptions, even surrounding the jgit adder.call() with try/catch. I couldn't find any specific bugs on their page, but I might've missed one that covers this.

@MikeTheGreat: A workaround with the current release for files that have previously been added is to use 'commit -a' (by right clicking on the commit button), however the initial add will have to be done using a different tool. We have a naive workaround, but still figuring out the jgit bug.

Turned out to be a change in how jgit interprets filepaths in a recent version, so we just had to change the file separator to /


containerregistry: Fixing issue where list_tag_properties and list_manifest_properties raise TypeError: NoneType is not iterable if there are no images in the repository

Description
Calling list_tag_properties or list_manifest_properties on a repository with no images in it currently raises TypeError. This change fixes that problem.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

Hi @hrichardlee , thanks for your contribution!
Here I have some feedback: could you also update the sync one and add some tests?
Thanks

Hi @hrichardlee , I can't reproduce the error you met.
I tried with the tests below in test_container_registry_client.py and test_container_registry_client_async.py without your updates but didn't get any errors, all tests are passed.

Let me know if I missed anything.
Thanks

Close it as not hear updates from the PR author.
@hrichardlee Thanks for your contribution! Feel free to reopen/recreate a PR if the issue still exists in your end.


Allow adapters to be inherited and extended

Added AdapterFactory and IAdapterFactory interface
Updated all built in Adapters to contain virtual methods and protected members so they can be extended
Updated ObjectAdapter to accept an AdapterFactory as part of the constructor.  If not provided, the default AdapterFactory is used
Updated the ApplyTo methods in the JsonPatchDocument to use the default AdapterFactory when an ObjectAdapter is not provided
Added an ApplyTo method which allows a custom AdapterFactory and supports the logErrorAction method

@rynowak Changes made... fingers crossed...  Thanks again for your help on all of this.
As a side question, assuming this gets merged, are there preview NuGets available that we can use until 2.2 is released, or do we need to continue using our forks?  Thanks!

Looks awesome!
Our CI builds are available on https://dotnet.myget.org/gallery/dotnet-core

@rynowak.
It looks like https://dotnet.myget.org/gallery/dotnet-core is still focusing on 2.1 and not 2.2, is that right?  The latest version is 2.1.0-rtm-30765 and doesn't appear to have these changes.  Do I just need to wait until 2.1 is finalized, or is there another place I need to look for the build.
Thanks!

I'll check on this.

We have definitely had builds pass since then... 🤔
I think I gave you the wrong feed. Try this one... https://dotnet.myget.org/gallery/aspnetcore-dev


OpenatDirExt: add helper to update atime and mtime

This adds one helper method to update timestamps (atime and mtime)
to current time, taking care of retrying in case of interrupted
syscall.
This occurs in a couple of places in rpm-ostree, although in a
non-uniform way (missing retries or missing AT_SYMLINK_NOFOLLOW).

Rebased. Tests are now using syncfs and seem to work realiably on GH runners too.


Able to get member while having dunce hat if they agree in #join

Recently a member who had dunce hat left the server and later rejoined. The bot correctly gave dunce hat back to the member but allowed them to agree to the server rules which gave them back member. It seems that we need to have a specific way to get member such that if something would conflict with it its instead added to the saved roles.

This will require:

Checking for "guest" in !agree when it's unset.
Ensuring reapply always takes precedence.

On Sat, Feb 9, 2019, 10:54 AM Rageoholic<EMAIL_ADDRESS>wrote:

Recently a member who had dunce hat left the server and later rejoined.
The bot correctly gave dunce hat back to the member but allowed them to
agree to the server rules which gave them back member. It seems that we
need to have a specific way to get member such that if something would
conflict with it its instead added to the saved roles.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/strinking/futaba/issues/257, or mute the thread
https://github.com/notifications/unsubscribe-auth/AIcClkP5PcAwD_Vz8HnqiqKCicLDHfqMks5vLu84gaJpZM4aymXX
.

@Rageoholic provisionally closed, if this happens again reopen the issue.


Return 400 on failed training request

Description
PR changes validation logic to throw 400 error codes as opposed to 500 errors codes during training.
In RestTrainModelHandler, change parser.text to parser.textOrNull to allow a user to pass in a null string argument. Validation is then done later.
In training request execution, throw a validation exception if there is no training capacity. This results in a 400 error being returned
Check List

[X] Commits are signed as per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #168 (5b62017) into main (549b8ac) will decrease coverage by 0.09%.
The diff coverage is 33.33%.

@@             Coverage Diff              @@
##               main     #168      +/-   ##
============================================
- Coverage     82.66%   82.57%   -0.10%
  Complexity      803      803
============================================
  Files           117      117
  Lines          3582     3586       +4
  Branches        338      338
============================================
  Hits           2961     2961
- Misses          466      470       +4
  Partials        155      155

Impacted Files
Coverage Δ

...in/transport/TrainingJobRouterTransportAction.java
80.00% <0.00%> (-3.73%)
:arrow_down:

...org/opensearch/knn/training/TrainingJobRunner.java
54.54% <0.00%> (-1.71%)
:arrow_down:

...nsearch/knn/plugin/rest/RestTrainModelHandler.java
61.90% <100.00%> (ø)

Continue to review full report at Codecov.

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


Steam Heaters should cause damage to entities that collide

This will require changing the bounding box for the Steam Heater, but it should only require a tiny slice of it to be removed. It should deal fire damage, or a new DamageSource like "You got steamed" or something.

I think a better way to do this would be to create a new extended bounding box that only exists in the TE to check for colliding players.


Update en translation for Shinobigami sheet

Changes / Comments
Update English translation for the Shinobigami sheet. A lot of it seems literally translated, presumably from the original Chinese version.
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[X] Does the pull request title have the sheet name(s)? Include each sheet name.
[X] Is this a bug fix? No
[X] Does this add functional enhancements (new features or extending existing features)? No
[X] Does this add or change functional aesthetics (such as layout or color scheme)? No
[X] If changing or removing attributes, what steps have you taken, if any, to preserve player data? Shouldn't be applicable
[X] If this is a new sheet, did you follow Building Character Sheets standards? Not a new sheet

If you do not know English. Please leave a comment in your native language.

Anyone who reviews this... Is this the proper way to update the translations? I also see a translation.json file with English in it so I'm not certain which is the source of truth.

@ZhugeSong
translation.json is the master file that updates all the others when new keys are added. We use a website called Crowdin for translations though this method you have used will work.
If you send me an email at<EMAIL_ADDRESS>then I'll be happy to get you an invite to Crowdin if you are multilingual and interested in helping translate. :)


Remove  from project files to improve build time

PR Details

Description
This PR removes <RestorePackages>true</RestorePackages> from all project files. I believe it is the reason why the projects are rebuilt everytime - Stride.Core.Tasks among others did a force restore which touched its project.assets.json and forced all dependants to recompile as well.
The removed tag is from an older version of MSBuild that didn't do automatic NuGet restores (see link).
Please verify that my observations are reproduced.
Related Issue
N/A (we talked about it on Discord (msg))
Motivation and Context
Well, after the change I don't have to wait 3 minutes to start GameStudio (event without any changes), but more like 20 seconds.
Types of changes

[x] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Retested, seems there's no difference to previous behavior 😢
Doing 'Clean Solution' and then building twice - the second time is fast but after reloading the solution we're back with the slow builds.


blank pdf

Hello,
when i run the command, if has generated 21 pages of pdf but it is just empty and the file size is just 14kb.
am i missing something or plugin is still in experimental stage?

Since here are some internal changes of node api in VuePress, you would get stuck in some of the transitional versions, could you check<EMAIL_ADDRESS>and<EMAIL_ADDRESS>and tell me if I close this issue?

yay! it is generating so i am closing this issue.
but i found many issues

it has links to dev URL (localhost:800)

ordering of pages is not correct

some text is being convered up by header part

i understand that, root cause of all these is using puppeteer and making screenshots into pdf,
probably we should go with some other approach like gitbook does.

All the issues you mentioned can be addressed, contribution welcome!

Hi,
I am on vuepress 1.5 and the latest version of the plugin. However, I am still getting a blank pdf even though the tool runs properly to completion. Am I missing something?
Thanks


How to check if token is expired in ClientForce object?

If this is still an issue (see latest updates to code) please re-open with more specifics.

@wadewegner, I am not able to find the relevant changes. Could you please point me to the commit that addresses the token expiration? Thanks!


Configure default logger

Is there a reason why the configure method of the default logger is not exposed? I know that I can add/remove transports from it but I would like to set my transports to avoid issues with missing/duplicate transports when Mocha reboots my app.
Seems a simple fix would be to add 'configure', above this line. Happy to submit a PR but just checking whether the omission is deliberate first.

@tamlyn PR definitely welcome here. .configure is a relatively new feature so it just slipped through the cracks.

PR created #852


feat(client): Archon Client Builder

Description
There should be a PipelineBuilder that constructs the Archon pipeline.
In a very idiomatic syntax, the pipeline builder would take items that implement the Stage interface/trait and only accept stages that consume the previous stage's output channel.

Hi, I took this on and open a pr.


The preselected checkbox is not on the checklist until toggled off and on

See http://plnkr.co/edit/1Ef6d7udy5NXTRKtGUR7?p=preview

I have only problem here. What happens if there is an inconsistency between ngModel and checklistModel? Let's say that ngModel is true, but checklistModel doesn't contain the value? Or the other way around?

Just curios - why don't you use for initialization the checklist-model?

So, using the checklistModel instead of ngModel solved this. I guess it is fine to leave it like this and close this issue. What do you think?

Yep
Kamil Pękala
Dnia 7 gru 2015 o godz. 11:33 Adrian Ber<EMAIL_ADDRESS>napisał(a):

So, using the checklistModel instead of ngModel solved this. I guess it is fine to leave it like this and close this issue. What do you think?
—
Reply to this email directly or view it on GitHub.

Thanks! Anyway I added to the documentation comments about ngModel and a link to this issue. Many thanks for your involvement.


update to version 0.1.6 ,Android studio lose focus ,Can't click.

today i update to version 0.1.6,after the open terminal,Android studio lose focus ,Can't click. close terminal back to normal.
before update no this issue
Android Studio 3.1.3
Build #AI-173.4819257, built on June 5, 2018
JRE: 1.8.0_152-release-1024-b02 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
terminal : git-bash mintty 2.8.5

Hi @longforus ,
Can you provide your FAVORITE_TERMINAL env variable?

@sburlyaev  yes ,like this:
FAVORITE_TERMINAL : C:\Git\git-bash.exe

@longforus ,
I've fixed it and uploaded a new build to the repository - waiting JetBrains approval.
Thanks!

@longforus ,
Done! v0.1.7 is already there.

@sburlyaev nice! , it fixed ,i very like this plugin,very converient ,thank you for your sharing 😄.

Thanks! You are welcome 😊


@react-native-community/geolocation: NativeModule.RNCGeolocation is null

Ask your Question
  ERROR    Error: @react-native-community/geolocation: NativeModule.RNCGeolocation is null. To fix this issue try these steps:
• Run react-native link @react-native-community/geolocation in the project root.
• Rebuild and re-run the app.
• If you are using CocoaPods on iOS, run pod install in the ios directory and then rebuild and re-run the app. You may also need to re-open Xcode to get the new pods.
If none of these fix the issue, please open an issue on the Github repository: https://github.com/react-native-community/react-native-geolocation
[Fri Jan 01 2021 15:08:07.695]  ERROR    Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication)

@maulik-vekariya  Did you find a solution?

Hi, I had the same error.
Could you please give me solution?
thanks


get std.path to compile with -dip1000

Due to a lot of entanglement with other Phobos modules, a lot of changes were needed.

Some of these changes might be useful in the future.


Merge pull request #1 from lovell/master

update

my bad didn't mean to open these PR

Coverage remained the same at 99.021% when pulling ec9506681b37ae809fd68f04b2f2ee39b2a9a4d0 on hightide2020:master into ba3f9144457a46a23177b69caaaef572231ba2da on lovell:master.


Reevaluate Mobs spawn/despawn range

There's been complains that the spawn area is too small for farms to work properly

Good Morning,
While I absolutely understand the needs of a server like CivMC to have non-vanilla spawn rules, to avoid mob-generation abuse, and to ensure an even distribution of mob spawning, the spawn rates and radii are quite low/small respectively.
On one level, I'd like to see the spawn rates raised. It feels strange that even for time-intensive, well-built, and carefully planned mob farms, the rates are still low enough to make a project feel wasted, and the infrequency of mob spawning can make the project difficult to debug on live servers (sometimes needing to wait minutes or hours for mobs to spawn across the tested area)
More generally, as well, I believe returning to vanilla spawn radii would make sense. Of course, the rates, limits, and mechanics a should remain different from Vanilla to ensure server health, but the distances themselves seem like they have no need of being different from the vanilla ranges for spawn, motion, and despawn. Especially with the currently low spawn rates, I would be surprised if moving to vanilla radii negatively affected server performance.
Thanks for all you do!


Add config file path to readme

Accorgind to
https://github.com/KELiON/cerebro/blob/603cb555eaeb4d1db73adab9b1bbf95911c07c65/app/lib/config.js#L9
and
https://github.com/electron/electron/blob/v1.1.0/docs/api/app.md#appgetpathname

Thanks!


Unexpected re-render with old data

Hey,
TL;DR: I'm using Async.Resolved to load some async data and unfortunately have to perform some side-effects that will determine whether some action later will error or not.
Here's a test case: https://codesandbox.io/s/vvp32m6kr3
Initial render is fine. Then, click on set duration 5000ms and watch the console.
Currently, the whole subtree underneath Async re-renders when it receives new props, causing the child-function of Async.Resolved to be called again, even though data is the old value, and isLoading is false.
In my case this causes react-intl to complain about a mismatch between the (old) provided localeData and the newly set locale.
My full example:
export class I18nProvider extends React.PureComponent {
  render() {
    const { children } = this.props
    return (
      <Connect mapStateToProps={({ user: { locale } }) => locale}>
        {locale => (
          <Async promiseFn={loadLocale} watch={locale}>
            <Async.Resolved>
              {([localeData, messages]) => {
                console.log({ locale, localeData, messages })

                addLocaleData(localeData)

                return (
                  <IntlProvider locale={locale} messages={messages}>
                    {children}
                  </IntlProvider>
                )
              }}
            </Async.Resolved>
          </Async>
        )}
      </Connect>
    )
  }
}

Hey Philipp,
Sorry for the late reply and thanks for using react-async, I hope you like it.
In general you should not be triggering side-effects from within a React render function. It goes against the React principles. What you should probably be using is the onResolve callback.
I'm aware that the whole subtree will rerender when any part of Async's state changes. I'm considering adding a subscription prop similar to the one in react-final-form to allow more fine grained control over rerenders. What do you think?

Hey Gert,
Yeah, I'm aware about the side-effects. Unfortunately I'm forced to do this for now, because react-intl spews errors if the locale set via the locale prop and the localeData passed to addLocaleData doesn't match. Its really awkward to use.
onResolve sounded like exactly what I needed, but onResolve gets called after the children re-render. I'm not sure whether that's intentional.
Demonstrated here: https://codesandbox.io/s/4xv4xz6860?expanddevtools=1&view=editor
I'm not familiar with react-final-form's subscription. From a user perspective I'd expect (especially when using the watch prop) that by default the component does not re-render unless the actual promise value changes. I would not expect (but accept I guess) having to specify which updates I care about via some subscription prop :)

Hi Philipp,
Are you still in need of this feature? I prefer not to overcomplicate the package. I think you can do something like this to avoid calling you function on every render:
class Watch extends React.Component {
  componentDidMount() {
    this.props.onChange()
  }
  componentDidUpdate(prevProps) {
    if (prevProps.watch !== this.props.watch) this.props.onChange()
  }
  render() {
    return this.props.children || null
  }
}

Then wrap your side-effect in a <Watch onChange={doSideEffect}> instance inside <Async.Resolved> to get what you're looking for. You can pass a watch prop to Watch in order to have it invoke the onChange callback again, but probably you don't even need it.


Incorrect url returned from call to cloudinary from nuxt component.

Making a call to cloudinary for a video returns a 500 response, while image returns 200. but the URL doesn't match the documentation.
this.$cloudinary.image.url('01_nrwgrf') returns https://res.cloudinary.com/xxx-xxx/image/upload/f_auto,q_auto/01_nrwgrf.

@mattbtay just to confirm, do you mean this.$cloudinary.image.url or this.$cloudinary.video.url? Because if it is this.$cloudinary.image.url then the generated link in the example is correct.

@mattbtay I just checked, it seems to be fine to me if you use video.url(). Below is a quick CodeSandbox demo I created.
Code example
Can you please provide more details if it still happens to you?

Yes, the demo works just, fine. must be something on my end.


another way to ignore DNS servers pushed by DHCP and some questions

NetworkManager has two useful settings —— ipv4.ignore-auto-dns and ipv6.ignore-auto-dns, disabling systemd-resolved seems to be unnecessary.
slirp4netns "receives" the TAP FD opened in another namespace instead of moving an interface to another namespace ( https://github.com/rootless-containers/slirp4netns/blob/f9f45d571a4cb6117ba678782b5e7ed7267d537b/main.c#L122 ) , it seems easier to be used by unprivileged processes. What do you think of this method? Do you have any plan to support it?

The issue with systemd-resolved is that it provides hostname resolution over D-Bus (see man 5 org.freedesktop.resolve1 for details), which can cross network namespace boundaries. So the issue is only partly about the injection of a malicious DNS server --- it's also that DNS requests from inside the protected namespace will be ultimately be relayed over the physical interface (where systemd-resolved is running), which is a privacy issue.
I can look into the slirp4netns technique but I would be surprised if it is possible to accomplish all of the necessary tasks without root privileges. For example, we need to create the namespace if it doesn't exist already, and call ip link set and ip addr add.

I can look into the slirp4netns technique but I would be surprised if it is possible to accomplish all of the necessary tasks without root privileges.

Starting  in  Linux  3.8,  unprivileged processes can create user namespaces, and the other types of namespaces can be created with just  the CAP_SYS_ADMIN capability in the caller's user namespace ( see man 7 user_namespaces ).
Create a user namespace and a network namespace:
(host)$ unshare --user --map-root-user --net
(namespace)$ echo $$
3000

Enter the user namespace and the network namespace:
(host)$ nsenter --target 3000 --user --net --preserve-credentials


Show workflow name in GitHub Actions

First step of below issue, show workflow name
https://github.com/backstage/backstage/issues/4689

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)

Tugboat has finished building the preview for this pull request!
Link:

https://pr4864-t2meawkpqngtcnoe7asngjlaikpk7af9.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6045cd4365f81702c50543a9


Migrate tooling to TypeScript with ts-node

Really not high-priority, but it would be could to have everything as TypeScript, including tooling.

Gonna scrap this issue. It's a bit overkill in my opinion. When I update the entire codebase from react-slingshot, it'll come with babel-node which I think is good enough with it's ES6 goodness.


update ID after dragging

Hello,
is there a function to update the ID after dragging a element? I have some elements:
{
"id": 2,
"title": "blabla",
"editing": false,
"note_editing": false,
"note": null,
"nodes": []
},
{
"id": 1,
"title": "hallo",
"editing": false,
"note_editing": false,
"note": "hello",
"nodes": []
},
and I want to update the ID(in this example after dragging the element with the title "blabla" should have the ID "1" and the element with the title "hallo" should have the ID "2").
I hope anybody can help me :-)

Closing this issue due to inactivity. See #815 for more information.
Please create a new issue is this still occurs with the current version of the component.


Added lines

A similar PR may already be submitted!
Please search among the Pull request before creating one.
Thanks for submitting a pull request! Please provide enough information so that others can review your pull request:
Before opening a pull request, please make sure all the tests pass locally by running npm test.
Summary

This PR fixes/implements the following bugs/features

[ ] Bug 1
[ ] Bug 2
[ ] Feature 1
[ ] Feature 2
[X ] Breaking changes

Explain the motivation for making this change. What existing problem does the pull request solve?

Test plan (required)
Demonstrate how the issue/feature can be replicated. For most cases, simply adding an appropriate html/css template into the reftests should be sufficient. Please see other tests there for reference.
Code formatting
Please make sure that code adheres to the project code formatting. Running npm run format will automatically format your code correctly.
Closing issues

Fixes #

Please complete the remaining checks...


Improve tests

I have found this library: https://github.com/AngleSharp/AngleSharp.Diffing
It allows to implement HTML diffing. But we usually render a lot of extra things, therefore I made 2 changes:

Add a "plain" attribute to mjml to render everything just plain without the default html, head, body and so on.
Add a few methods to disable all helpers in the tests (for head components).

Once merged, I'll update tests in <mj-text> and <mj-button> branches!

What do you think about the plain attribute or would you just create a test component?

What do you think about the plain attribute or would you just create a test component?

I prefer the idea of test component. I think it fits in nicely with the rest of the project.

I forgot to hit submit. :( The <mjml-test> looks good. 👍


Gabor/cleanup

Motivation: #2640

This PR does not affect the produced WebAssembly code.

await-without-yield and commit-on-await (in run-drun/) already trigger the cleanup callbacks (when installed). No one-shot cleanup callback is ever seen to be triggered.

We have several problems currently.
a) non-self-send async methods may invoke a reply/reject continuation that traps. The index allocated in the ClojureTable and what it points to will never be deallocated.
b) Explicit self-sends allocate ClojureTable index (for the future) that is supposed to be removed on the other side of the call. If that traps, the sender-side becomes the owner of the future's slot. Then the reject callback gets invoked and can (additionally) pop it. The trouble starts when the reject callback also traps. Then the cleanup callback will be invoked and must clean up two slots. But the problem is that if the reply callback trapped it only needs to clean-up one slot. But the cleanup callback has no information whatsoever what happened.
For a) the solution is easy, pop the one slot.
For b) we have to consolidate the two slots to one (pointing to a 3-element array) in which the other side can peep to fetch the future.

To avoid serializing/deserialing the result of the future, if wonder if it would make sense to transfer it it in a fourth slot of that array?

To avoid serializing/deserialing the result of the future, if wonder if it would make sense to transfer it it in a fourth slot of that array?

Yep, I was thinking overwriting the third position of the array (i.e. the future) since that is not needed any more. But sending the payload back in heap changes the semantics a bit, so I'd only do that for single, small results.

Thanks for this! I had quite some trouble figuring out what’s happening based on the patch only, but the comment in https://github.com/dfinity/motoko/pull/2663#issuecomment-884974977 helped. Maybe worth expanding the code comments a bit, so that future readers (who don’t have the benefit of the PR discussion) can make sense of it? Probably one comprehensive GHC-style code node that explains how async self-calls works would be useful.


Ensure we generate events where required

This includes:

DRPC
VRG
DRPolicy

(from HackMD list)

Closed as part of #224 and #202