enrich Dsecure condition with FullSecure test

Current situation
Dsecure accepts 3 possible values Non-secure, Secure and TZ-disabled.
The problem
We generally use Non-secure and Secure conditions to provide Startup component files that serves co-existing secure and non-secure applications.
To enrich Startup with files serves only a secure application that uses the full memory space, we need to enrich the Dsecure with a value that checks for such condition.
Proposal
We propose to add Full-secure (or equivalent) to permit selecting a set of files to satisfy the use-case where all memory resources are reserved for a single secure application (no jump to non-secure)

Update: In Open-CMSIS-Pack meeting we discussed the potential usage of TZ-disabled.
We noted the following:

this is semantically incorrect since TZ is "really" enabled
memory mapping is different vs TZ-disabled.
STM32U5 as example:

Dsecure
TZ-disabled
Secure
Non-secure

FLASH addr
0x08000000
0x0C000000
0x08000000

For the Full-secure proposal, we need to use secure mapping (0x0C000000) which is different from TZ-disabled mapping (0x08000000)
Conclusion: using TZ-disabled do not satisfy this use-case

During the meeting we have also discussed whether there should be a separate attribute indicating that the Secure project will not be combined with one or more related Non-secure projects. Which means there is no need for resource partitioning and there must not be a cmse-lib.o created.
I think adding another attribute may make things more complicated than necessary.
I prefer the term:
Secure-only

I believe, the issue is wider then just the startup code. We have template projects that help users to get started.
For the STM32U5 these are here:
https://github.com/Open-CMSIS-Pack/STM32U5xx_DFP/blob/main/Keil.STM32U5xx_DFP.pdsc#L1924
Currently the STM32 based projects rely on the features of CubeMX for device configuration.
The reason why I believe this is better covered with template projects is:

It is required to setup certain project parameters (i.e. compiler or linker configuration).
It may require a specific startup code (currently this is generated by CubeMX)
It may require different linker scripts.

Maybe it makes sense to create an project example first to see all the aspects. How should we proceed?

In the processor: node of the CMSIS Solution project format the trustzone: node can be configured to one of:
secure | non-secure | off
an additional setting secure-only would not only enable the condition evaluation of Dsecure="Secure-only" to true but would also prevent the linker from the attempt to create a cmse library.


Get image ID with tag name

the /v1/ registry response /repositories/<repo>/tags used to list the image ID along with the tag handle. /v2/ only seems to give the handle. It would be useful to get the ID to compare to the ID found locally. The only place I can find the ID is in the v1Compat section of the manifest (which is overkill for the info I want)

@amancevice This property of the V1 API was very computationally expensive for the way images are stored on the backend. Only the tag names are enumerated to avoid a secondary lookup. In addition, the V2 API does not deal in Image IDs. Rather, it uses digests to identify layers, which can be calculated as property of the layer and are independently verifiable.

@stevvooe What is the proper way to compare two docker images?

@kevinsimper : please don't comment on closed issues.  If you have a question can you open a new issue and state your use case for comparing docker images?


A dependency license is copyleft (highline package)

New Issue Checklist

[v] Updated fastlane to the latest version
[v] I read the Contribution Guidelines
[v] I read docs.fastlane.tools
[v] I searched for existing GitHub issues

Issue Description
Projects with proprietary code may have issues with using fastlane since one of the dependency licenses is copyleft: https://github.com/JEG2/highline

According to https://github.com/JEG2/highline/blob/master/LICENSE the user decides of the license
Distributed under the user's choice of the {GPL Version 2}[http://www.gnu.org/licenses/old-licenses/gpl-2.0.html] (see COPYING for details) or the
{Ruby software license}[http://www.ruby-lang.org/en/LICENSE.txt] by
James Edward Gray II and Greg Brown.

According to https://github.com/JEG2/highline/blob/master/LICENSE the user decides of the license
Distributed under the user's choice of the {GPL Version 2}[http://www.gnu.org/licenses/old-licenses/gpl-2.0.html] (see COPYING for details) or the
{Ruby software license}[http://www.ruby-lang.org/en/LICENSE.txt] by
James Edward Gray II and Greg Brown.

Unfortunately, Ruby license is not present at that location anymore but from what I found https://www.tldrlegal.com/license/ruby-license-ruby it is also "copyleft" - requires users to disclose all their source code.

My understanding is that ruby is provided under the BSDL license as per this document.
Ruby is copyrighted free software by Yukihiro Matsumoto<EMAIL_ADDRESS>You can redistribute it and/or modify it under either the terms of the
2-clause BSDL (see the file BSDL), or the conditions below:
[...]

so by extension, highline should also be covered by the BSDL if we wish so. If that's the case, aren't we good?
IANAL.


Add Alpine Linux package and Repology badge to readme

Thanks for maintaining this :). Alpine is one of my favourite distros.


Compiler warning about changed sign for uint

I started testing with lzav and find this compiler warning, which makes me nervous considering uint LHS. Cheers
"lzav.h", line 653: warning: integer conversion resulted in a change of sign [integer_sign_change]
                uint32_t ov = (uint32_t) ( 255 << 24 | d << 6 | 2 << 4 );
                                           ^

"lzav.h", line 664: warning: integer conversion resulted in a change of sign [integer_sign_change]
        uint32_t ov = (uint32_t) ( 255 << 24 | d >> 2 );
                                   ^

Could you please try inserting (uint32_t) 255 in these cases? If that works, I'll update the code soon. Compilers I use do not show the warning.

I've changed the code, hopefully it fixes the warning.


AbortController & AbortSignal are missing

According to releases notes, they should be available globally.
I recommend you to use this polyfill:
https://github.com/aws/aws-sdk-js-v3/tree/main/packages/abort-controller
import { AbortController, AbortSignal } from '@aws-sdk/abort-controller'
export { AbortController, AbortSignal }

Tested over v2, abort polyfills are not there.
Related:
https://github.com/cloudflare/miniflare/blob/e7aee3574327fd3bac09af9453d0dc1252d546cf/src/modules/standards.ts#L99


[QUESTION] How to write a title text from (D3:F3) in Excel file

Prerequisites

[X] Have read and understood: https://github.com/Maatwebsite/Laravel-Excel/blob/3.1/.github/SUPPORT.md
[X] Checked if your Laravel Excel version is still supported: https://docs.laravel-excel.com/3.1/getting-started/support.html#supported-versions
[X] Checked that your question isn't already asked before.
[X] Filled in the entire issue template

Versions

PHP version: 7.2.19
Laravel version: 5.8.35
Package version:^3.1

Description

Additional Information
Any additional information, configuration or data that might be necessary to reproduce the issue.
I have search a lot but I can't find any good solution to write a title on my excel file from column D and row 3 up to the column F row 3 (D3:F3)
Addition Information
Importer
<?php

namespace App\Exports;

use App\Model\Vacancy;
use Maatwebsite\Excel\Concerns\FromCollection;
use Maatwebsite\Excel\Concerns\WithCustomStartCell;
use Maatwebsite\Excel\Concerns\ShouldAutoSize;
use Maatwebsite\Excel\Concerns\WithHeadings;
use Maatwebsite\Excel\Concerns\WithTitle;
use Maatwebsite\Excel\Events\BeforeExport;

class ApplicantLongListExport implements FromCollection, WithCustomStartCell, ShouldAutoSize, WithHeadings, WithTitle
{
    private $id;

    public function __construct(string $id)
    {
        $this->id = $id;
    }

    public function collection()
    {
        return Vacancy::where('id', $this->id)->get();
    }

    public function startCell(): string
    {
        return 'B2';
    }

    public function headings(): array
    {
        return [
            '#',
            'Name',
            'Email',
            'Created at',
            'Updated at'
        ];
    }

    public function registerEvents(): array
    {
        return [
            // Handle by a closure.
            BeforeExport::class => function(BeforeExport $event) {
                $event->writer->getProperties()->setTitle('Patrick');
            },
        ];
    }

    public function title(): string
    {
    	return 'Some Text';
    }
}

I have find the solution and is in below:
    /**
    * @return array
    */
   public function registerEvents(): array
   {
       return [
           AfterSheet::class => function(AfterSheet $event) use ($stylesArray, $vacancy) {
               $event->sheet->setCellValue('D3:F3', 'Value');
           },
       ];
   }


Why do the images I generated from different viewpoints look gray?

like this:

What code are you using?

What code are you using?

The code I ran is as follows：
`import torch
import requests
from PIL import Image
from diffusers import DiffusionPipeline, EulerAncestralDiscreteScheduler
Load the pipeline
pipeline = DiffusionPipeline.from_pretrained(
"sudo-ai/zero123plus-v1.1", custom_pipeline="sudo-ai/zero123plus-pipeline",
torch_dtype=torch.float16
)
Feel free to tune the scheduler!
timestep_spacing parameter is not supported in older versions of diffusers
so there may be performance degradations
We recommend using diffusers==0.20.2
pipeline.scheduler = EulerAncestralDiscreteScheduler.from_config(
pipeline.scheduler.config, timestep_spacing='trailing'
)
pipeline.to('cuda:0')
Download an example image.
cond = Image.open(requests.get("https://d.skis.ltd/nrp/sample-data/lysol.png", stream=True).raw)
Run the pipeline!
result = pipeline(cond, num_inference_steps=75).images[0]
for general real and synthetic images of general objects
usually it is enough to have around 28 inference steps
for images with delicate details like faces (real or anime)
you may need 75-100 steps for the details to construct
import rembg
result = rembg.remove(result)
result.show()
result.save("output.png")`

What code are you using?
The code I ran is as follows:
`import torch
import requests
from PIL import Image
from diffusers import DiffusionPipeline, EulerAncestralDiscreteScheduler
pipeline = DiffusionPipeline.from_pretrained(
"sudo-ai/zero123plus-v1.1", custom_pipeline="sudo-ai/zero123plus-pipeline",
torch_dtype=torch.float16
)

pipeline.scheduler = EulerAncestralDiscreteScheduler.from_config(
pipeline.scheduler.config, timestep_spacing='trailing'
)
pipeline.to('cuda:0')
cond = Image.open(requests.get("https://d.skis.ltd/nrp/sample-data/lysol.png", stream=True).raw)
result = pipeline(cond, num_inference_steps=75).images[0]
import rembg
result = rembg.remove(result)
result.show()
result.save("output.png")`

What code are you using?

The code I ran is as follows:

Can you provide the code as a formatted code block in the comment so i may try to reproduce the behavior on my side?

Can you provide the code as a formatted code block in the comment so i may try to reproduce the behavior on my side?

Thank you!Here is the code I used:
`import torch
import requests
from PIL import Image
from diffusers import DiffusionPipeline, EulerAncestralDiscreteScheduler
pipeline = DiffusionPipeline.from_pretrained(
"sudo-ai/zero123plus-v1.1", custom_pipeline="sudo-ai/zero123plus-pipeline",
torch_dtype=torch.float16
)
pipeline.scheduler = EulerAncestralDiscreteScheduler.from_config(
pipeline.scheduler.config, timestep_spacing='trailing'
)
pipeline.to('cuda:0')
cond = Image.open(requests.get("https://d.skis.ltd/nrp/sample-data/lysol.png", stream=True).raw)
result = pipeline(cond, num_inference_steps=75).images[0]
import rembg
result = rembg.remove(result)
result.show()
result.save("output.png")`

Can you provide the code as a formatted code block in the comment so i may try to reproduce the behavior on my side?

Thank you!Here is the code I used:
`import torch
import requests
from PIL import Image
from diffusers import DiffusionPipeline, EulerAncestralDiscreteScheduler
pipeline = DiffusionPipeline.from_pretrained(
"sudo-ai/zero123plus-v1.1", custom_pipeline="sudo-ai/zero123plus-pipeline",
torch_dtype=torch.float16
)
pipeline.scheduler = EulerAncestralDiscreteScheduler.from_config(
pipeline.scheduler.config, timestep_spacing='trailing'
)
pipeline.to('cuda:0')
cond = Image.open(requests.get("https://d.skis.ltd/nrp/sample-data/lysol.png", stream=True).raw)
result = pipeline(cond, num_inference_steps=75).images[0]
import rembg
result = rembg.remove(result)
result.show()
result.save("output.png")`

Thank you！Here is the code I used, actually, the only difference between this and img_to_mv.py is that the background is removed at the end.
import torch
import requests
from PIL import Image
from diffusers import DiffusionPipeline, EulerAncestralDiscreteScheduler
pipeline = DiffusionPipeline.from_pretrained(
"sudo-ai/zero123plus-v1.1", custom_pipeline="sudo-ai/zero123plus-pipeline",
torch_dtype=torch.float16
)
pipeline.scheduler = EulerAncestralDiscreteScheduler.from_config(
pipeline.scheduler.config, timestep_spacing='trailing'
)
pipeline.to('cuda:0')
cond = Image.open(requests.get("https://d.skis.ltd/nrp/sample-data/lysol.png", stream=True).raw)
result = pipeline(cond, num_inference_steps=75).images[0]
import rembg
result = rembg.remove(result)
result.show()
result.save("output.png")

Can you provide the code as a formatted code block in the comment so i may try to reproduce the behavior on my side?

Thank you！Here is the code I used, actually, the only difference between this and img_to_mv.py is that the background is removed at the end.
import torch
import requests
from PIL import Image
from diffusers import DiffusionPipeline, EulerAncestralDiscreteScheduler
pipeline = DiffusionPipeline.from_pretrained(
"sudo-ai/zero123plus-v1.1", custom_pipeline="sudo-ai/zero123plus-pipeline",
torch_dtype=torch.float16
)
pipeline.scheduler = EulerAncestralDiscreteScheduler.from_config(
pipeline.scheduler.config, timestep_spacing='trailing'
)
pipeline.to('cuda:0')
cond = Image.open(requests.get("https://d.skis.ltd/nrp/sample-data/lysol.png", stream=True).raw)
result = pipeline(cond, num_inference_steps=75).images[0]
import rembg
result = rembg.remove(result)
result.show()
result.save("output.png")

I am running your code changing nothing and here is my result. Maybe there is a problem with the diffusers version?

 I am running your code changing nothing and here is my result. Maybe there is a problem with the diffusers version?

Thank you! I reinstalled the environment and the problem is solved.


BUG:  Black/White background color on hover windows since neovim v0.10

Did you check docs and existing issues?

[X] I have read all the docs.
[X] I have searched the existing issues.
[X] I have searched the existing discussions.

Neovim Version (nvim -v)
0.10.0-2
Operating System / Version
ArchLinux 6.8.9-arch1-2
Describe the Bug
All hover windows (rename, move, etc) have a pure black/white background, based on the colorscheme's style(dark/light). This started to occur with the update to neovim 0.10. I also tested several color schemes, including neovim's default scheme and it appears on all of them.
I experience the same behavior for hover windows of lspsaga and lazy's hover window. skim hover windows however seem to work just fine.
Things I tried

Checked different terminals (xterm and alacritty) , but it appears on both terminals.
Unset all environment variables from my environment (except $HOME). Didn't do anything. As soon as settermguicolors is activated, the behavior appears.
Minimal reproducable setup, which can be seen below.
Switch back to v0.9, whichfixes the problem. The behavior only occurs on v0.10.

Workaround
Setting set :notermguicolors fixes the problem! It just looks bad.
Similar issues
I stumbled upon this neovim issue, but it seems to be a different problem, even though it sound suspiciously similar. Their minimal config works perfectly fine on my system and the transparent windows is displayed correctly.
Screenshots, Traceback

Trace log of the event:
[TRACE Mon 20 May 2024 03:15:34 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:97: Firing event:  vim_win_closed  with args:  {
  afile = "1006"
}
[DEBUG Mon 20 May 2024 03:15:34 AM CEST] ...hare/nvim/lazy/neo-tree.nvim/lua/neo-tree/setup/init.lua:731: VIM_WIN_CLOSED: disposing state for window 1006
[TRACE Mon 20 May 2024 03:15:34 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:81: Handler  {
  event = "vim_win_closed",
  handler = <function 1>
}  for vim_win_closed called successfully.
[TRACE Mon 20 May 2024 03:15:34 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:97: Firing event:  vim_tab_closed  with args:  {
  afile = "2"
}
[DEBUG Mon 20 May 2024 03:15:34 AM CEST] ...hare/nvim/lazy/neo-tree.nvim/lua/neo-tree/setup/init.lua:718: VIM_TAB_CLOSED: disposing state for tabnr 2
[TRACE Mon 20 May 2024 03:15:34 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:81: Handler  {
  event = "vim_tab_closed",
  handler = <function 1>
}  for vim_tab_closed called successfully.
[TRACE Mon 20 May 2024 03:15:34 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:97: Firing event:  vim_win_enter  with args:  {
  afile = "neo-tree filesystem [1]"
}
[TRACE Mon 20 May 2024 03:15:34 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:81: Handler  neo-tree-win-enter  for vim_win_enter called successfully.
[TRACE Mon 20 May 2024 03:15:34 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:97: Firing event:  vim_buffer_enter  with args:  {
  afile = "neo-tree filesystem [1]"
}
[TRACE Mon 20 May 2024 03:15:34 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:97: Firing event:  neo_tree_buffer_enter  with args:  nil
[TRACE Mon 20 May 2024 03:15:34 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:81: Handler  {
  event = "vim_buffer_enter",
  handler = <function 1>
}  for vim_buffer_enter called successfully.
[TRACE Mon 20 May 2024 03:15:34 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:81: Handler  buffers.vim_buffer_enter  for vim_buffer_enter called successfully.
[TRACE Mon 20 May 2024 03:15:34 AM CEST] ...nvim/lazy/neo-tree.nvim/lua/neo-tree/sources/manager.lua:402: buffers  disposing of tab:  3 buffers
[DEBUG Mon 20 May 2024 03:15:34 AM CEST] ...ree.nvim/lua/neo-tree/sources/filesystem/lib/fs_scan.lua:655: Not unwatching folders... use_libuv_file_watcher is  nil  and state.tree is  false
[DEBUG Mon 20 May 2024 03:15:34 AM CEST] ...are/nvim/lazy/neo-tree.nvim/lua/neo-tree/ui/renderer.lua:116: Closing window, but saving position first.
[TRACE Mon 20 May 2024 03:15:35 AM CEST] ....nvim/lua/neo-tree/sources/filesystem/lib/fs_actions.lua:174: Moving node:  /home/nuke/temp/bewerbung.md  to  nil , using root directory:  /home/nuke/temp
[TRACE Mon 20 May 2024 03:15:35 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:97: Firing event:  vim_buffer_enter  with args:  {
  afile = ""
}
[TRACE Mon 20 May 2024 03:15:35 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:97: Firing event:  neo_tree_popup_buffer_enter  with args:  nil
[TRACE Mon 20 May 2024 03:15:35 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:81: Handler  {
  event = "vim_buffer_enter",
  handler = <function 1>
}  for vim_buffer_enter called successfully.
[TRACE Mon 20 May 2024 03:15:35 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:81: Handler  buffers.vim_buffer_enter  for vim_buffer_enter called successfully.
[TRACE Mon 20 May 2024 03:15:35 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:97: Firing event:  vim_buffer_modified_set  with args:  {
  afile = ""
}
[TRACE Mon 20 May 2024 03:15:35 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:67: Seed for vim_buffer_modified_set returned: table: 0x788547a3cdf8
[TRACE Mon 20 May 2024 03:15:35 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:81: Handler  buffers.vim_buffer_modified_set  for vim_buffer_modified_set called successfully.
[TRACE Mon 20 May 2024 03:15:35 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:81: Handler  git_status.vim_buffer_modified_set  for vim_buffer_modified_set called successfully.
[TRACE Mon 20 May 2024 03:15:35 AM CEST] ...are/nvim/lazy/neo-tree.nvim/lua/neo-tree/ui/renderer.lua:692: Redrawing tree filesystem 1
[DEBUG Mon 20 May 2024 03:15:35 AM CEST] ...are/nvim/lazy/neo-tree.nvim/lua/neo-tree/ui/renderer.lua:1134: render_tree: Saving position
[DEBUG Mon 20 May 2024 03:15:35 AM CEST] ...are/nvim/lazy/neo-tree.nvim/lua/neo-tree/ui/renderer.lua:653: Saved cursor position with lnum: 6
[DEBUG Mon 20 May 2024 03:15:35 AM CEST] ...are/nvim/lazy/neo-tree.nvim/lua/neo-tree/ui/renderer.lua:654: Saved window position with topline: 1
[TRACE Mon 20 May 2024 03:15:35 AM CEST] .../neo-tree.nvim/lua/neo-tree/sources/common/container.lua:309: wanted width:  6  actual width:  37
[TRACE Mon 20 May 2024 03:15:35 AM CEST] .../neo-tree.nvim/lua/neo-tree/sources/common/container.lua:309: wanted width:  10  actual width:  35
[TRACE Mon 20 May 2024 03:15:35 AM CEST] .../neo-tree.nvim/lua/neo-tree/sources/common/container.lua:309: wanted width:  97  actual width:  35
[TRACE Mon 20 May 2024 03:15:35 AM CEST] .../neo-tree.nvim/lua/neo-tree/sources/common/container.lua:309: wanted width:  113  actual width:  35
[TRACE Mon 20 May 2024 03:15:35 AM CEST] .../neo-tree.nvim/lua/neo-tree/sources/common/container.lua:309: wanted width:  125  actual width:  35
[TRACE Mon 20 May 2024 03:15:35 AM CEST] .../neo-tree.nvim/lua/neo-tree/sources/common/container.lua:309: wanted width:  12  actual width:  35
[TRACE Mon 20 May 2024 03:15:35 AM CEST] .../neo-tree.nvim/lua/neo-tree/sources/common/container.lua:309: wanted width:  9  actual width:  35
[TRACE Mon 20 May 2024 03:15:35 AM CEST] .../neo-tree.nvim/lua/neo-tree/sources/common/container.lua:309: wanted width:  4  actual width:  35
[TRACE Mon 20 May 2024 03:15:35 AM CEST] .../neo-tree.nvim/lua/neo-tree/sources/common/container.lua:309: wanted width:  13  actual width:  35
[DEBUG Mon 20 May 2024 03:15:35 AM CEST] ...are/nvim/lazy/neo-tree.nvim/lua/neo-tree/ui/renderer.lua:1161: render_tree: Restoring position
[DEBUG Mon 20 May 2024 03:15:35 AM CEST] ...are/nvim/lazy/neo-tree.nvim/lua/neo-tree/ui/renderer.lua:674: Restoring window position to topline: 1
[DEBUG Mon 20 May 2024 03:15:35 AM CEST] ...are/nvim/lazy/neo-tree.nvim/lua/neo-tree/ui/renderer.lua:675: Restoring cursor position to lnum: 6
[DEBUG Mon 20 May 2024 03:15:35 AM CEST] ...are/nvim/lazy/neo-tree.nvim/lua/neo-tree/ui/renderer.lua:664: Forget about cursor position.
[TRACE Mon 20 May 2024 03:15:35 AM CEST] ...are/nvim/lazy/neo-tree.nvim/lua/neo-tree/ui/renderer.lua:698:   Redrawing tree done filesystem 1
[TRACE Mon 20 May 2024 03:15:35 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:81: Handler  filesystem.vim_buffer_modified_set  for vim_buffer_modified_set called successfully.
[TRACE Mon 20 May 2024 03:15:35 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:97: Firing event:  neo_tree_popup_input_ready  with args:  {
  bufnr = 8,
  winid = 1008
}
[TRACE Mon 20 May 2024 03:15:35 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:97: Firing event:  vim_win_closed  with args:  {
  afile = "1007"
}
[DEBUG Mon 20 May 2024 03:15:35 AM CEST] ...hare/nvim/lazy/neo-tree.nvim/lua/neo-tree/setup/init.lua:731: VIM_WIN_CLOSED: disposing state for window 1007
[TRACE Mon 20 May 2024 03:15:35 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:81: Handler  {
  event = "vim_win_closed",
  handler = <function 1>
}  for vim_win_closed called successfully.
[TRACE Mon 20 May 2024 03:15:35 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:97: Firing event:  vim_win_closed  with args:  {
  afile = "1008"
}
[DEBUG Mon 20 May 2024 03:15:35 AM CEST] ...hare/nvim/lazy/neo-tree.nvim/lua/neo-tree/setup/init.lua:731: VIM_WIN_CLOSED: disposing state for window 1008
[TRACE Mon 20 May 2024 03:15:35 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:81: Handler  {
  event = "vim_win_closed",
  handler = <function 1>
}  for vim_win_closed called successfully.
[TRACE Mon 20 May 2024 03:15:35 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:97: Firing event:  vim_win_enter  with args:  {
  afile = "neo-tree filesystem [1]"
}
[TRACE Mon 20 May 2024 03:15:35 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:81: Handler  neo-tree-win-enter  for vim_win_enter called successfully.
[TRACE Mon 20 May 2024 03:15:35 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:97: Firing event:  vim_buffer_enter  with args:  {
  afile = "neo-tree filesystem [1]"
}
[TRACE Mon 20 May 2024 03:15:35 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:97: Firing event:  neo_tree_buffer_enter  with args:  nil
[TRACE Mon 20 May 2024 03:15:35 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:81: Handler  {
  event = "vim_buffer_enter",
  handler = <function 1>
}  for vim_buffer_enter called successfully.
[TRACE Mon 20 May 2024 03:15:35 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:81: Handler  buffers.vim_buffer_enter  for vim_buffer_enter called successfully.
[TRACE Mon 20 May 2024 03:15:40 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:97: Firing event:  vim_win_enter  with args:  {
  afile = "neo-tree filesystem [1]"
}
[TRACE Mon 20 May 2024 03:15:40 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:81: Handler  neo-tree-win-enter  for vim_win_enter called successfully.
[TRACE Mon 20 May 2024 03:15:40 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:97: Firing event:  vim_buffer_enter  with args:  {
  afile = "/home/nuke/.local/share/nvim/neo-tree.nvim.log"
}
[TRACE Mon 20 May 2024 03:15:40 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:97: Firing event:  neo_tree_buffer_leave  with args:  nil
[TRACE Mon 20 May 2024 03:15:40 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:81: Handler  {
  event = "vim_buffer_enter",
  handler = <function 1>
}  for vim_buffer_enter called successfully.
[TRACE Mon 20 May 2024 03:15:40 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:81: Handler  buffers.vim_buffer_enter  for vim_buffer_enter called successfully.
[TRACE Mon 20 May 2024 03:15:40 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:97: Firing event:  vim_buffer_enter  with args:  {
  afile = "/home/nuke/.local/share/nvim/neo-tree.nvim.log"
}
[TRACE Mon 20 May 2024 03:15:40 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:81: Handler  {
  event = "vim_buffer_enter",
  handler = <function 1>
}  for vim_buffer_enter called successfully.
[TRACE Mon 20 May 2024 03:15:40 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:81: Handler  buffers.vim_buffer_enter  for vim_buffer_enter called successfully.
[TRACE Mon 20 May 2024 03:15:40 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:97: Firing event:  state_created  with args:  {
  bind_to_cwd = true,
  commands = {
    add = <function 1>,
    add_directory = <function 2>,
    buffer_delete = <function 3>,
    cancel = <function 4>,
    close_all_nodes = <function 5>,
    close_all_subnodes = <function 6>,
    close_node = <function 7>,
    close_window = <function 8>,
   ...
[TRACE Mon 20 May 2024 03:15:40 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:81: Handler  buffers.state_created  for state_created called successfully.
[TRACE Mon 20 May 2024 03:15:40 AM CEST] ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/events/queue.lua:81: Handler  git_status.state_created  for state_created called successfully.

Steps to Reproduce

Run neovim with nimimal reproducable config.
Press m on neo-tree to open move menu.

Expected Behavior
The background shouldn't switch to black/white.
Your Configuration
local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim"
if not (vim.uv or 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({
    ----- Libraries -----
    "MunifTanjim/nui.nvim",
    "nvim-lua/plenary.nvim",
    "nvim-neo-tree/neo-tree.nvim",
})

vim.cmd(":Neotree source=filesystem")

I played around a bit more and found out that the issue doesn't happen on the habamax colorscheme doesn't appear to have this issue. The original vim colorscheme also seems to look fine (even though the colors are extreme).
habamax:

vim:

What's confusing though is that the default neovim colorscheme has this problem as well as the other three colorschemes I tested. So I assume this is an issue introduced with the new colorscheme?
default:

I am also experiencing a similar issue. I observe the black background on the status lines of inactive windows and inside the Lazy UI. I'm not certain if it was the cause but I started noticing the behavior after installing lualine and setting cmdheight=0 but reverting these actions didn't fix it.

Same thing here. The Lazy UI is affected as well, including the top bar.
What's interesting is that the Lazy UI uses and set the habamax colorscheme by default every time it starts up. This seems to break something for the top line, which otherwise works perfectly fine for me.

Just popping in here to confirm that I can recreate your issue with the provided config.
What's interesting is if you add literally any valid value for popup_border_style, it corrects the issue
local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim"
if not (vim.uv or 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",
            "MunifTanjim/nui.nvim",
        },
        branch = "main",
        config = {
            popup_border_style = "single",
        }
    },
})

vim.cmd(":Neotree source=filesystem")

Valid values for popup_border_style can be found in :h api-win-config under the config.border section
border:       Style of (optional) window border. This can either
                    be a string or an array. The string values are
                    • "none": No border (default).
                    • "single": A single line box.
                    • "double": A double line box.
                    • "rounded": Like "single", but with rounded corners
                      ("╭" etc.).
                    • "solid": Adds padding by a single whitespace cell.
                    • "shadow": A drop shadow effect by blending with the
                      background.
                    • If it is an array, it should have a length of eight or
                      any divisor of eight. The array will specify the eight
                      chars building up the border in a clockwise fashion
                      starting with the top-left corner. As an example, the
                      double box style could be specified as:
                      [ "╔", "═" ,"╗", "║", "╝", "═", "╚", "║" ].

                      If the number of chars are less than eight, they will be
                      repeated. Thus an ASCII border could be specified as
                      [ "/", "-", \"\\\\\", "|" ],

                      or all chars the same as
                      [ "x" ].

                    An empty string can be used to turn off a specific border,
                    for instance,
                     [ "", "", "", ">", "", "", "", "<" ]

                    will only make vertical borders but not horizontal ones.
                    By default, `FloatBorder` highlight is used, which links
                    to `WinSeparator` when not defined. It could also be
                    specified by character:
                     [ ["+", "MyCorner"], ["x", "MyBorder"] ].

Not really sure what is going on but this workaround seems to work for me.
Without setting popup_border_style

With setting popup_border_style to something (single) in my case

IIRC Neo-tree uses nui for the popup handling, might be a nui regression?

Sorry, I realized my issue was unrelated (I don't use neo-tree). If it helps the behavior I observed was due to enabling transparent floating windows with my theme (kanagawa-dragon) but I accidentally copied over an override for the LazyNormal highlight group which caused the Lazy floating window to have a black background.

I'm at this point very sure that this has to do with old color schemes.
The ported lua variant of gruvbox works just fine, so I'll guess I'll close this for now.

@miversen33's comment with adding popup_border_style = "single", fixed this for me with using the dracula/vim theme.
Before:

After:

Without setting popup_border_style
With setting popup_border_style to something (single) in my case
IIRC Neo-tree uses nui for the popup handling, might be a nui regression?

Similarly with tokyonight colorscheme but regarding using the require("neo-tree").setup({}) lines at all:
not calling it:

calling with no explicit popup_border_style = "", key

NOTE : we get the same result with the explicit popup_border_style = "NC" key
calling with popup_border_style = "single",

Does look the best in v1 to me


Impossible to logout after login.

Would be nice add a button to login/logout in the web

I've try but I have some trouble with micronaut about this feature.
Will add it in a future release

There is still the issue from micronaut I think : https://github.com/micronaut-projects/micronaut-core/issues/1532
Wait for the response, but the logout button is available on dev image with docker pull tchiotludo/kafkahq:dev


Bot is not able to recognize gender.

Describe the bug
Bot only understands 2 genders Male/Female but if transgender is entered still it asks for "How subject is identified ?Male/Female".
If Transgender is given then bot take it as female by default.
To Reproduce
In bot Ask : Risk test for transgender.
Expected behavior
It should not ask again to identify gender. In Backend it may get managed.
Default gender female should removed.
Screenshots

Added a new entry in Gender Entity for transgender.


[FE-BUG] Amplify pagination table bug (fe only)

Environment information
-

Description
After i configure the new variable at the new amplify UI, i've got this bug:

i can't scroll to the bottom within the table's container.

it'll worked when i zoom out to 80% - 70%

Closing this as a duplicate of #1615 and I'll recommend subscribing to it to track updates on the fix. Thanks!


skip tokenization for tokenized corpora

Is it possible to skip the tokenization step in training? I have tokenized corpora but could not find the skip option in training parameters.

I am not sure if there is a way to do it through the command line, but if you have MMT built from source, I think you can comment this line
<processor>eu.modernmt.processing.tokenizer.Tokenizer</processor>
in
"modernmt/src/textprocessing/src/main/resources/eu/modernmt/processing/preprocessor-default.xml"
and rebuild MMT again, then run your training.
Good luck!

Hi @dominikacecylia
ModernMT pre-processing pipeline (including tokenization) is a mandatory step in the process. Unfortunately, the hint of @mzeidhassan won't work because the tokenizer is needed to identify words. If the tokenizer is not run, ModernMT will simply find a sentence without Words.
However, what you can do is follow the instructions of @mzeidhassan but, instead of removing the tokenizer, you can write your own "WhitespaceTokenizer" implementation, which only relies on whitespaces to identify tokens.
A simpler solution could be to just run a de-tokenizer on your training corpus. This might be the easiest fix if you have such a de-tokenizer script.

Thanks @davidecaroselli for your feedback and support.
I have one question that is related somehow:
Is the current instructions on how to disable cleaning still valid?

Remark: it seems wiki pages have a problem. I see HTML code in place of the rendered viewing. A github bug?
I'm always using the --skip-cleaning option, and it seems to be properly recognized.

@EtienneAb3d the --skip-cleaning option also works for me.
@davidecaroselli thanks for the tip, I detokenized my data as it seemed the easiest tip.
Also about tokenization, does it work for Czech or Slovak? As it failed when I tried my corpora, but maybe that was just the file issue not the tokenizer. I use cs or sk as the language abbreviations.

Thanks @EtienneAb3d. I appreciate it.
Yes, it seems there is something wrong with the click-through link, that's why I copied the main page link there.

Remark: it seems wiki pages have a problem. I see HTML code in place of the rendered viewing. A GitHub bug?

Yes, very strange Github issue; I solved it by doing a hard refresh of the page (command+shift+R on my Mac).

I'm always using the --skip-cleaning option, and it seems to be properly recognized.

Yes, that's the correct way!

Also about tokenization, does it work for Czech or Slovak?

Yes, our pipeline fully supports both languages and the language codes are correct: cs and sk.


Add tests for object releasing

Closes #353
This adds tests, in a new folder so it won't interfere with the unit tests. The idea is basically, doing for each kind of object:

Get how many objects we have of each kind.
Create a bunch of objects of a specific kind.
Make sure the counts are indeed up.
Delete the objects.
Check that the counts are down.

Todo:

[x] Generic logic that is the same for each unit test.
[x] Implement some meta-tests to make sure that the tests indeed fail when they should.
[x] Implement a test function for every object.
[x] Can we now remove that delayed_releaser? Yes!
[x] Can we now enable some release calls that previously panicked? Yes!
[x] ~Measure process memory consumption to detect leaks?~ --> #406
[x] Do we want our BindGroupLayout object to cache instances like wgpu-core does?
[ ] Does this close #275?
[x] Investigate fails:

[ ] Device (simply does not clean up in native).
[ ] Queue (related to the above)
No luck yet.
Following up in #405

Can you explain what polling the device does conceptually?

Can you explain what polling the device does conceptually?

From what I understand, wgpu has an an event-loop of sorts, so it can perform asynchronous tasks. Polling the device flushes the device's queue. We also use poll in the functions that are asyn in nature, like buffer mapping. Related to #391.

I think this is good to go. I'll have a look (probably after the weekend) what the state of #275 is. But in the mean time this is ready for review.

I created 2 new issues for follow-up work.


Barrier cluster

Import Barrier cluster

Deleting this PR. Will reopen. It has a lot of extra stuff that's in master


Math.random() generates same results

Because srand() is not used on initialization. Without it, the Math.random() function generates the same results every time (not every call, but every time the environment runs).
This works on other JS engines like V8 (nodejs). IMHO we should look to achieve same results to be consistent with JS platform

@tosyu I'm not sure about the reference to other JS engines, because initialising the libc random generator should be the responsibility of the application, not the library (the JS engine). That being said, however, it's true that srand is not called anywhere, not even in jerry-main. Will you be submitting a patch to fix that?

do we have srand in jerry libc?

Note: interestingly, tests/unit-core/test-common.h calls srand.
@zherczeg yes, we do.

@akosthekiss I did not find anything in the documentation about initializing random number generator with srand(), so for an application developer this would require to make assumptions about Math.random() implementation, which in my opinion is a "no-no". Either it should be fixed in the code or it should be written in the documentation that srand() needs to be called

@tosyu I see no way for fixing this issue in code (as code of the engine) because library should not (re-)initialise the RNG (might have already been done by the application, and so the lib could cause conflicts). It can and should be fixed in the code of the jerry-main application(s) though. I also agree that it could be documented that Math.random is based on libc's rand, which would imply the need for initialisation by srand (and that could also be written explicitly). (No idea though where to put that note, as we have no dedicated documentation for the JS objects/functions as we assume that everything is documented in the standard. Perhaps the documentation of jerry_init in the API docs could have some similar notes. I'm also open to suggestions.)

@akosthekiss IMHO docs/03.API-EXAMPLE.md would be sufficient to put the information about srand(); as an example

@tosyu That could work, too. Are you up for submitting a PR for this or shall we put that on our todo list?

@akosthekiss please put it on the todo list for now


use laravel Event Observers for clearing cache

This uses the Laravel Model Event Observer to handle the flushing of the cache for roles.
This should resolve issue #428

This does bring up the question - why is this flushing all cached roles instead of just the specific user's?
and why isn't it clearing the cache on detachRole / attachRole?

Looks good. I'll merge tomorrow

:+1: Implementation looks good.  I definitely like that this simplifies the code by overloading fewer methods.

So it looks like a different method to resolve this has been chosen which adds in extra code around all of this.  @andrewelkins Should I bother correcting the conflicts at this point?

@andrewelkins I've updated this to be against the latest codebase


Add keyboard bindings to colour interactives with sliders

Description
It would be useful to add bindings to all sliders in colour interactives to precisely select values. Right and up arrow keys should increment values by one, and left and down arrow keys should decrement values by one.
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the issue.

[x] I have linked any relevant existing issues/suggestions in the description above (include #??? in your description to reference an issue, where ??? is the issue number)
[x] I have applied relevant labels

This example will be helpful for implementing this feature: http://refreshless.com/nouislider/examples/#section-keyboard

Duplicate of #496, closing this one because the other is worked on


Add healthchecks

Add healthcheck api, and update docker image and documentation to use healthchecks.
for more info, see: https://medium.com/better-programming/docker-healthchecks-eb744bfe3f3b

Reopening as docker image is reporting unhealthy due to curl being absent in image.
With .Net 5, Docker container images no longer include curl. This is documented in #2379, and prevents us from using curl to invoke our health check. The official reason is to remove attack surfaces, but there's also some evidence to support that having a companion "health check" app is a best practice


:latest and Dockerfile do not match.

The Dockerfile found at https://github.com/Microsoft/mssql-docker/blob/master/windows/mssql-server-windows-express/dockerfile does not build to same container image as the container image that is received by running a container with "microsoft/mssql-server-windows-express".
The containers that use the Dockerfile container image start up and stop after a few seconds. The containers using a pull "microsoft/mssql-server-windows-express" container image stay alive.

Thanks @Ariwari!
We are currently looking into reproducing this behavior on our end so we can understand and resolve the issue.

Thanks for the quick response @perrysk-msft!
Something that I noticed is that the 2 containers I'm now running (from the 2 different container images) have a different Args when using docker iinspect
The "microsoft/mssql-server-windows-express" containerimage has the following
"Args": [
"/S"
"/C"
"powershell ./start -sa_password %sa_password% -ACCEPT_EULA %ACCEPT_EULA% -attach_dbs \"%attach_dbs%\" -Verbose"
]
The containerimage built with the linked Dockerfile has:
"Args": [
"-Command",
"$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';",
".\start -sa_password $env:sa_password -ACCEPT_EULA $env:ACCEPT_EULA -attach_dbs \"$env:attach_dbs\" -Verbose"
]'

:latest and Dockerfile now match.


Better error reporting when having technical issues

For example, when running out of space in that server, instead a 9999 we should give a more comprehensive text saying that there are technical issues right now, try again please. (something like that)

This is not as easy as it sounds... The operating system reports simply that it couldn't create "a lock file", nothing else.
This also can happen in multiple steps: When creating lock, when creating file, transforming...
This really is an internal technical issue and not a standard error, if you really think is worth spending time on it ok, but I really don't see why improving feedback in case of an internal severe error would add value to the user :/  (we have or should have alerts instead and that's all)
/cc @zenitraM @javisantana


Support AWS::RDS::DBInstance and AWS::RDS::DBCluster

Issue
Currently,  awsdac does not support AWS::RDS::DBInstance and AWS::RDS::DBCluster types.
$ awsdac template.yaml -v
...
WARN[0000] Unknown type: AWS::RDS::DBCluster
WARN[0000] Unknown type: AWS::RDS::DBInstance

Note/Workaround
You can use AWS::RDS in your template.
https://github.com/awslabs/diagram-as-code/blob/642d911bc7d3742b91426b9d101c6258f327ef1a/definitions/definition-for-aws-icons-light.yaml#L2914-L2923

Resources:
  Aurora:
    Type: AWS::RDS::DBCluster
  DB:
    Type: AWS::RDS::DBInstance


Fix mismatched height between ListView items

ListView items currently have mismatched heights when an ActionGroup is included:

This was due to the overflow: hidden added to the description styles when adding wrapping/truncation support.
Adding a fixed height to the description fixes this issue. This PR adds a fixed height that matches the listview item's line height (OK for default overflowMode: truncate), and reverts to height: auto for overflowMode: wrap.
✅ Pull Request Checklist:

[ ] Included link to corresponding React Spectrum GitHub Issue.
[ ] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[ ] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:
In ListView stories:

Check that item heights match between ActionButton, ActionGroup, and ActionMenu stories
Check that overflowMode behavior still works in those stories

Note: Test across browsers, original issue was only present in some.
🧢 Your Project:

LGTM, were you able to test this with spacious and compact or are those stories in Chromatic?

Looks like the large stories have changed row heights by 1px, is that expected? Seeing that in chromatic https://www.chromatic.com/test?appId=5f0dd5ad2b5fc10022a2e320&id=6282bac9c22bfd004a6fb025

My initial thought is that maybe there was previously some rounding going on without the fixed height? I'll take a closer look to try to find out what this could be


Initial commit for cleaning code to confirm to PEP-8 standards

No new logic introduced or functionality changes made. Cleaned code to confirm with python standards. Mostly the refactoring has been done with a python formatter rather than by hand

Remove unnecessary print statements
Clean white spaces to confirm to python standard
format json, method parameters.
Refactor exceptions and import statements

Overall base code looks much better now. Performed a test for successful run with new code to ensure it hasn't broken functionality.

All ok, but I think we are changing a whole bunch of code that will defo conflict with upstream files when you try to rebase.

All ok, but I think we are changing a whole bunch of code that will defo conflict with upstream files when you try to rebase.

Done. Just refactoring done to code we have touched.


Problem with shared static variable between dll

I installed the lib gtkmm and run asample program from the manual (base.cc). A run-time error occurred because the dll pangomm called the function wrap_register from glibmm which has a static variable wrap_func_table but because pangomm has its own copy not initialized a run-time error occurs when this variable is referenced in wrap_register.
How can I solve this problem ? I hoped vcpkg would solve these kind of linking issues automatically.

I think I have a fix already - going to prepare a PR

Ok, thanks.  I expect the same  problem not only for pangomm.dll but also for the atkmm.dll.
Were these dll statically compiled with glibmm, so that the functions were included in the dlls ?
Sent from Mail for Windows 10
From: Norbert Nemec
Sent: Saturday, 25 May 2019 18:40
To: microsoft/vcpkg
Cc: JacqKrol; Author
Subject: Re: [microsoft/vcpkg] Problem with shared static variable between dll(#6550)
I think I have a fix already - going to prepare a PR
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

The problem was that since #5937 glibmm could only be built as static library but atkmm, pangomm and gtkmm each can only be linked as dynamic libary, leading to up to three copies of the glibmm static data in one executable. My fix reverts that change so that glibmm is also built as dynamic libary.


Cannot figure out how to set callback for setColor()

Hello PitPik, I'm trying to use your nice color picker but I cannot figure out how to get the value of the color selected. From reading I have figured out that I need to change the function setColor that belongs to the Colors object that belongs to ColorPicker().  What is the simplest way to update the callback function setColor?

Hi @patrickcorrigan,
thanks for your interest in tinyColorPicker ;o)
I don't quite understand your question though...

setColor() is a method from Colors, a module that calculates all kinds of color values. You don't need to change this method (you actually shouldn't ;o)
if you want to use setColor() as you are about to manipulate the color by a different source (just like in the example with the RGB-sliders) then look at the example in ./demo/index.js on line 29 how it is done. that.color.setColor({r: 200}, 'rgb'); sets the red value of the current color to 200. Next time the rendering will take place (that.render();), it will update your colorPicker with this value.
Instead of {r: 200}; you can change more than one part of the color or all like {r: 200, g: 10, b: 33}

You're actually writing "I cannot figure out how to get the value of the color selected", so you want to "read" something and then you ask: "...to update the callback function setColor". Maybe I miss understood you and didn't answer quite the way you expected. If that's the case, please let me know.
Cheers

Hi @PitPik,
thank you for the quick and informative responses. Yes you are right what I actually want to say is that I can't figure out how to get the value of the color selected :P How do I do this. I feel ridiculous as I couldn't figure it out and had to ask you. Thank you in advance :)

Hi @patrickcorrigan again,
I still don't know what you need to do. When do you need to read the color value. Is it in the renderCallback? This is done by var colors = this.color.colors;, there you get all the values you need,... or is it after you closed it, then you just need to either also use renderCallback or just read the value from the input field.
I need a bit more information (or code) to figure out what your problem is.
I make another wild guess:
I assume you choose a color and just closed the color picker:
renderCallback: function($elm, toggled) {
    var colors = this.color.colors;

    if (toggled === true) { // this happens on open (first time or when switching to another one)
        if (this.$oldElement) { // previously closed while opening this one
            console.log(colors); // show color model of previously opened
        }
        this.$oldElement = $elm; // store for next switch...
    } else if (toggled === false) { // this happens on close (only)
        console.log(colors); // show color model of just closed
        this.$oldElement = null; // delete $oldElement as there is no other swich possible
    }
}

Does this help??

Hi @patrickcorrigan again,
I still don't know what you need to do. When do you need to read the color value. Is it in the renderCallback? This is done by var colors = this.color.colors;, there you get all the values you need,... or is it after you closed it, then you just need to either also use renderCallback or just read the value from the input field.
I need a bit more information (or code) to figure out what your problem is.
I make another wild guess:
I assume you choose a color and just closed the color picker or switched to another one, so you might want to save your choice right after closing or switching (console.log demonstrates some action):
renderCallback: function($elm, toggled) {
    var colors = this.color.colors,
        oldValue = '';

    if (toggled === true) { // this happens on open (first time or when switching to another one)
        if (this.$oldElement && this.$oldElement[0] !== $elm[0]) { // previously closed while opening this one
            oldValue = this.$oldElement.val(); // actual value of previous element
            oldValue = this.color.setColor(oldValue, this.$oldElement.data('colorMode')); // set color to that old value
            console.log(this.color.toString()); // show color of previously opened in rgba mode
        }
        this.$oldElement = $elm; // store for next switch...
    } else if (toggled === false) { // this happens on close (only)
        console.log(this.color.toString()); // show color model of just closed
        this.$oldElement = null; // delete $oldElement as there is no other swich possible
    }
}

Does this help??

Hi @patrickcorrigan again,
I still don't know what you need to do. When do you need to read the color value. Is it in the renderCallback? This is done by var colors = this.color.colors;, there you get all the values you need,... or is it after you closed it, then you just need to either also use renderCallback or just read the value from the input field.
I need a bit more information (or code) to figure out what your problem is.
I make another wild guess:
I assume you choose a color and just closed the color picker or switched to another one, so you might want to save your choice right after closing or switching (console.log demonstrates some action):
renderCallback: function($elm, toggled) {
    var colors = this.color.colors,
        oldValue = '',
        helperColor = this.helperColor = this.helperColor || new this.color.constructor(); // new instance for converting colors

    if (toggled === true) { // this happens on open (first time or when switching to another one)
        if (this.$oldElement && this.$oldElement[0] !== $elm[0]) { // previously closed while opening this one
            oldValue = this.$oldElement.val(); // actual value of previous element
            helperColor.setColor(oldValue); // set color to that old value
            console.log(helperColor.toString()); // show color of previously opened in rgba mode
        }
        this.$oldElement = $elm; // store for next switch...
    } else if (toggled === false) { // this happens on close (only)
        console.log(this.color.toString()); // show color model of just closed
        this.$oldElement = null; // delete $oldElement as there is no other swich possible
    }
}

Does this help??

Hi @patrickcorrigan,
Does the last example answer your questions and help you with your needs?
Please let me know if there is more you need to know.
See also ./demo/index.js (in new updated files) for a slightly different solution.
Cheers,
Peter

I'm terribly sorry for the late reply. Thank you so much for your response. Yes it solved my problem perfectly. Thank you so much. The only issue I have left is that after selecting a color there is a slight delay before the callback is executed. Is there any way to synchronously get the color. Thank you so much for your help.

Should I set the color in the mousedown event instead?


Bot no longer starts

I pulled the latest dev commit (https://github.com/PokemonGoF/PokemonGo-Bot/commit/d5622898c0817c7f4913e1cec6076a687e4acf16) and now the bot won't start up
[11:15:57]  PokemonGO Bot v1.0
[11:15:57]  Configuration initialized
[11:15:57]  Not logged in!
Traceback (most recent call last):
File "pokecli.py", line 442, in
main()
File "pokecli.py", line 85, in main
report_summary(bot)
File "pokecli.py", line 93, in report_summary
metrics.capture_stats()
File "/Users/yitao/Downloads/pokemongo/PokemonGo-Bot/pokemongo_bot/metrics.py", line 75, in capture_stats
response_dict = self.bot.api.call()
File "/Users/yitao/Downloads/pokemongo/PokemonGo-Bot/pokemongo_bot/api_wrapper.py", line 57, in call
if not self._can_call():
File "/Users/yitao/Downloads/pokemongo/PokemonGo-Bot/pokemongo_bot/api_wrapper.py", line 29, in _can_call
raise NotLoggedInException()
pgoapi.exceptions.NotLoggedInException
(PokemonGo-Bot)

Post your config, check your credentials. Be sure to use code tags

Same error and my credential and my location was valid.

I resolved it by removing "proxy_ip" configuration

I got this problem too, for me my password was to long for the bot.


Hand cursor on buttons

Would you consider this change?
button, input[type="button"], input[type="submit"] {
  cursor: pointer;
}

@nicolasparada, care to chime in on why not?

https://medium.com/simple-human/buttons-shouldnt-have-a-hand-cursor-b11e99ca374b

https://github.com/twbs/bootstrap/pull/21812

Conceptually, I like the "hand cursor is only for non-obvious elements" mantra. And it is consistent with what operating systems do, which makes it easier to use sanitize.css as-is in a desktop app (e.g. via Electron).
That said, look at GitHub, it is using the hand cursor for everything and I like it a lot in practice.
¯\_(ツ)_/¯

Going with @nicolasparada’s advice.


[SPARK-47523][SQL] Replace deprecated JsonParser#getCurrentName with JsonParser#currentName

What changes were proposed in this pull request?
This pr replaces the use of JsonParser#getCurrentName with JsonParser#currentName in Spark code, as JsonParser#getCurrentName has been deprecated since jackson 2.17.
https://github.com/FasterXML/jackson-core/blob/8fba680579885bf9cdae72e93f16de557056d6e3/src/main/java/com/fasterxml/jackson/core/JsonParser.java#L1521-L1551
    /**
     * Deprecated alias of {@link #currentName()}.
     *
     * @return Name of the current field in the parsing context
     *
     * @throws IOException for low-level read issues, or
     *   {@link JsonParseException} for decoding problems
     *
     * @deprecated Since 2.17 use {@link #currentName} instead.
     */
    @Deprecated
    public abstract String getCurrentName() throws IOException;

    /**
     * Method that can be called to get the name associated with
     * the current token: for {@link JsonToken#FIELD_NAME}s it will
     * be the same as what {@link #getText} returns;
     * for field values it will be preceding field name;
     * and for others (array values, root-level values) null.
     *
     * @return Name of the current field in the parsing context
     *
     * @throws IOException for low-level read issues, or
     *   {@link JsonParseException} for decoding problems
     *
     * @since 2.10
     */
    public String currentName() throws IOException {
        // !!! TODO: switch direction in 2.18 or later
        return getCurrentName();
    }

Why are the changes needed?
Clean up deprecated API usage.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass GitHub Actions
Was this patch authored or co-authored using generative AI tooling?
No

Merged to master for Apache Spark 4.0.0.
Thank you, @LuciferYang and @yaooqinn .


Feature request: support the ?stats=1 query parameter

Prometheus supports stats=1 as part of the /api/v1/query and api/v1/query_range endpoints. It returns an additional json field called "stats" with some execution timings. For /query:
{
  "status": "success",
  "data": {
    "resultType": "vector",
    "result": ["..."],
    "stats": {
      "timings": {
        "evalTotalTime": 0.0000875,
        "resultSortTime": 0,
        "queryPreparationTime": 0.000051542,
        "innerEvalTime": 0.000029166,
        "execQueueTime": 0.00004725,
        "execTotalTime": 0.000141459
      },
      "samples": {
        "totalQueryableSamples": 1,
        "peakSamples": 1
      }
    }
  }
}

Right now this parameter causes gmp-frontend to return an error:
{
  "error": {
    "code": 400,
    "message": "Invalid JSON payload received. Unknown name \"stats\": Cannot bind query parameter. Field 'stats' could not be found in request message.",
    "status": "INVALID_ARGUMENT",
    "details": [
      {
        "@type": "type.googleapis.com/google.rpc.BadRequest",
        "fieldViolations": [
          {
            "description": "Invalid JSON payload received. Unknown name \"stats\": Cannot bind query parameter. Field 'stats' could not be found in request message."
          }
        ]
      }
    ]
  }
}

This means we can't make use of some excellent Prometheus tooling out there like pint to lint for expensive queries, because it relies on the stats=1 parameter (and not just for that one check, but all that call Prometheus APIs). Is it possible to increase compatibility with Prometheus and start supporting this param?

Thanks! Great request. 💪🏽
The main issue is to map internal workings of Google Cloud Monitoring PromQL engine to those stats which assumes Prometheus' TSDB PromQL engine.
We could make it work, at the minimum level, so tools like [pint](https://cloudflare.github.io/pint/checks/query/cost.html could work OR we could contribute to pint to make sure it's more generic. Anyway, the acceptance criteria here:
Acceptance Criteria

Make GMP work with pint


cli: implemente delete command

requires https://github.com/inveniosoftware/invenio-vocabularies/pull/103
closes https://github.com/inveniosoftware/invenio-vocabularies/issues/87

Sample command:
invenio vocabularies delete -v names -i crxej-zf213

Need for discussion on how to implement --all (cc @slint), options:

implement bulk delete
implemente delete_all method at service level
use read_all + delete (hackish...)


Revert "images/cilium-test: New test suite image"

This reverts pull requests https://github.com/cilium/cilium/pull/12941 and https://github.com/cilium/cilium/pull/15605.
This code isn't used anywhere anymore.
cc @errordeveloper

/test

/test

/test

k8s-1.16-kernel-4.9 failed with known flake https://github.com/cilium/cilium/issues/22404. That flake is unrelated to the present changes. Reviews are in. Merging.

Marking this for backports to v1.13 as we keep getting dependency updates for that directory there.


Received memory warning when downloading large file (100mb)

I get like 3 warnings and than it crashes. Is there a way to get around this? Seems like it's downloading to memory first? I've seen some post about downloading directly to disk.
Any ideas?

I've used the library with files bigger than that. Would you please post the errors that you get? The stack trace? Where exactly the error occurs?


Define CPU and RAM limits/guarantees in K8s

The deployment descriptors should contain a reasonable limitations and guarantees for computing resources.
See https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/

This is an absolute necessity for #63, as the Payara image is using a JVM with container support and no other limits set to gain maximum momentum out of the containers resources.
Without limitation, the JVM will believe it is free to eat all of your RAM. Beware.


ManagementPortMiddleware log adjustment

Description
This change reduces the level of this log entry from Error to Warning and includes more information.
Before:
<timestamp> [APP/PROC/WEB/0] [OUT] fail: Steeltoe.Management.Endpoint.ManagementPort.ManagementPortMiddleware[0]
<timestamp> [APP/PROC/WEB/0] [OUT] ManagementMiddleWare Error: Access denied on 80 since Management Port is set to 9999

After:
<timestamp> [APP/PROC/WEB/0] [OUT] fail: Steeltoe.Management.Endpoint.ManagementPort.ManagementPortMiddleware[0]
<timestamp> [APP/PROC/WEB/0] [OUT] Access to /actuator/metrics on port 80 denied because 'Management:Endpoints:Port' is set to 9999.

Quality checklist

[ ] Your code complies with our Coding Style.
[ ] You've updated unit and/or integration tests for your change, where applicable.
[ ] You've updated documentation for your change, where applicable.
If your change affects other repositories, such as Documentation, Samples and/or MainSite, add linked PRs here.
[ ] There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.
[ ] You've added required license files and/or file headers (explaining where the code came from with proper attribution), where code is copied from StackOverflow, a blog, or OSS.

/azp run Steeltoe.All


Moving post analysis scripts to new folder

After much futzing, I think the best folder structure should be:
qfit-3.0/src/qfit/: base scripts
qfit-3.0/src/post_analysis_scripts: scripts based on qFit package but not needed to run qFit itself
qfit-3.0/scripts: pre/post refinement scripts, bulk solvent, ect. These scripts do not call qFit to run.
Open for feedback on this structure.

What are your thoughts on:

/src/qfit: qfit package
/scripts/pre: things to be run before
/scripts/post: things to be run after

I'm not convinced we need a distinction between things that require qFit and things that don't. Imo, the user shouldn't need to be made aware of such a distinction.
Also, I think it's reasonably safe to assume that if the user is accessing these scripts, they've already installed qFit.

I like that. Should we make the shell scripts CLI as well?

Yes. Things in the scripts folder should have 755 permissions. Especially if we're going to make them available through the setup.py.

This PR is deleting the following scripts:
check_qfit_run.sh
post_refine_phenix_restraints.csh
post_refine_phenix_single.csh
qfit_complete_parser.py
qfit_complete_wrapper.sh
run_protein.py

For find_largest_ligand, please keep moving_scripts version. I can't seem to resolve the conflict without merging.

Hey Stephanie, why are the scripts in src/scripts, and not just in scripts like was agreed to https://github.com/ExcitedStates/qfit-3.0/pull/84#issuecomment-658304726 ?
Your changes to setup.py (probably removing packages = find_packages('src') ?) seems to have broken the package structure of qfit. None of the CI tests complete, they can't run qfit_protein --help, and it's because they can't find qfit.Structure.
I should probably explain how these pre/post scripts fit into the setuptools model: these post/pre scripts are being distributed with the package, but they're not part of the qFit source itself (they shouldn't be accessible if someone types import qfit), especially not the .sh files.
As such, they shouldn't be in src/, nor should they be listed in the packages argument to setup.
Also, following from this, they don't fit in entry_points={'console_scripts':[...]}.
I strongly recommend using
setup(
   ...
   scripts=[
        'name_of_script.py',
        'qfit_final_refine_xray.sh',
        ...,
   ],
   ...
)

instead.

Also, you shouldn't merge dev back into your branch, for a PR that will be merged into dev.
This goes against the idea of separating independent lines of development.

this works on my local branch on my computer (qfit_protein, qfit_ligand). I was not able to get the structure of /scripts/___ to work in the setup script. If we do what you suggested then we need the package to start ABVOE src, which then gets in the way with the tests, ect. Which is why I stated earlier (see comment above) I was going to do /src/qfit and src/scripts. I would like the post analysis scripts


Cleanup/runtimehelper

This PR removes the old RuntimeHelper class and introduces the new ScriptEnvironment class that contains environmental information related to resolving dependencies, compiling and executing scripts.
This lays down the foundation for passing/injecting ScriptEnvironment  in the future.
Many of the changes here are just simply static methods that now are instance methods.
It kind of rippled through a large portion of the code base, but the overall design is now less static.

@filipw Are we good to merge this ? 😎

definitely!


Reorganize Hubble docs

To better support continued expansion of the Hubble documentation, we need somewhere to put documentation related to Hubble configuration somewhere besides the getting started section. We already have the hubble export documentation in the Observability section, so let's add a new "Network Observability with Hubble" section under the Observability section to the docs where we can add more structure to the documentation around Hubble.
The new section will focus primarily on network observability, ie: ways to access Hubble flows, either through the API or through file export, and how to configure these features. This means we're keeping Hubble metrics documentation in the Monitoring & Metrics section, instead of consolidating it under this new Hubble section. This gives the existing Hubble TLS documentation a better home (as it's not really a "getting started" topic), and provides us a place where we can link to using Hubble CLI instead of trying to embed the instructions into the relevant pages. This allows us to expand the current usage documentation for Hubble CLI, to better support future usage docs around using CEL, and other Hubble CLI filters.

Rebasing to pick up CI fixes

/test

/test


ADBDEV-3536 Fix extension creation when extension scripts drop anything

gptkh installation on gpdb5 fails with error:
adb=# create extension if not exists gptkh; ERROR: cannot drop function local_tables(text,text,text,integer,text,text) because extension gptkh requires it HINT: You can drop extension gptkh instead.

The error is caused by an attempt to delete local_tables function. In gptkh 0.8 there was no attempt to drop this function within the installation script, but in newer version we try to drop some newly created functions, which causes the error.
There’s a difference in extension dependency control between gpdb 5 and gpdb 6. While the 5th forbids dropping extension’s dependencies, the 6th allows to drop dependencies to the extension itself.
Backported test doesn't fully match the test that's on 6x because 5x treats some objects differently. For example, it allows extensions dropping existing views which is forbidden in 5x. However, extensions are not allowed to drop existing functions
The backported commits are as follows:

https://github.com/arenadata/gpdb/commit/b313cdf2e598fe05ce72a8882493d112f4c44c72 This commit resets extension related variables on segments

https://github.com/arenadata/gpdb/commit/313786a74155cf04e4539f4d613a6993aab199d8 If the other object is the extension currently being created/altered, ignore this dependency and continue with the deletion.  This allows dropping of an extension's objects within the extension's scripts, as well as corner cases such as dropping a transient object created within such a script.

https://github.com/arenadata/gpdb/commit/ad20725bf24ea6a85213e6e0379dbd1e665719a0 This patch fixes problem with incorrect handling of search_path GUC at QE: create/alter extension process sets up this GUC to the newer state, but GUC is not reset after this process finishes - as a result there will broken version of GUC inside transaction. The patch fixes this problem by saving the state of GUCNestlevel at QE variable to enable correct state machine work (of create/alter extension process) executed on QE.

https://github.com/arenadata/gpdb/commit/3769eac6d28cfd59b808ff59bfafe264b68649dd The implementation of UPDATE EXTENSION is very similar to CREATE EXTENSION.
First, on QD, we update the pg_extension row to the new version, and update extension's dependency entries according to the new requires introduced by the new version specified control file.
Second, we dispatch the UPDATE EXTENSION statement to QEs to update pg_extension row and extension's dependency entries on QEs, and the global status like creating_extension, CurrentExtensionObject of QEs will be set.
Finally, we execute the update script file on QD. because of the correct set of creating_extension, CurrentExtensionObject on QEs, the dependency between object and extension will be handled correctly, so the CREATE/DROP object statement will be executed successfully.

Seems the logic with cleanup global variables (ResetExtensionCreatingGlobalVarsOnQE) inside  transactions (in case of abort) should be ported from 6.x branch (there are two places as I see AbortTransaction + AbortOutOfAnyTransaction)

I'm on vacation until Apr 11, 2023.

There are failed tests the CI, so research (and fix) of problem which leads to this behavior is needed. And it's worth to add tests for current patch, I suppose src/test/modules/extension is a suitable place for this (like it's done at 6/7.x)

If we backport something, we should add a links to backported commits to PR and commit description. Can you add this, please?

Added links to commits and their descriptions

Done

To enable tests - seems that src/test/modules/Makefile should be filled like contrib/Makefile and upper-level GNUMakefile installcheck-world target should be extended with extension checks

I found some warnings during compilation. Can you please check?
extension.c: In function ‘CreateExtension’:
extension.c:1586:25: warning: passing argument 1 of ‘ApplyExtensionUpdates’ from incompatible pointer type [-Wincompatible-pointer-types]
 1586 |   ApplyExtensionUpdates(stmt, extensionOid, pcontrol,
      |                         ^~~~
      |                         |
      |                         CreateExtensionStmt * {aka struct CreateExtensionStmt *}
extension.c:106:55: note: expected ‘AlterExtensionStmt *’ {aka ‘struct AlterExtensionStmt *’} but argument is of type ‘CreateExtensionStmt *’ {aka ‘struct CreateExtensionStmt *’}
  106 | static void ApplyExtensionUpdates(AlterExtensionStmt *stmt, Oid extensionOid,
      |                                   ~~~~~~~~~~~~~~~~~~~~^~~~
extension.c: In function ‘ApplyExtensionUpdates’:
extension.c:3063:40: warning: implicit declaration of function ‘makeDefElem’ [-Wimplicit-function-declaration]
 3063 |    update_stmt->options = lappend(NIL, makeDefElem("new_version", (Node*)makeString(versionName)));
      |                                        ^~~~~~~~~~~
extension.c:3063:40: warning: passing argument 2 of ‘lappend’ makes pointer from integer without a cast [-Wint-conversion]
 3063 |    update_stmt->options = lappend(NIL, makeDefElem("new_version", (Node*)makeString(versionName)));
      |                                        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                                        |
      |                                        int
In file included from ../../../src/include/access/tupdesc.h:19,
                 from ../../../src/include/access/formatter.h:19,
                 from ../../../src/include/access/relscan.h:17,
                 from ../../../src/include/access/genam.h:17,
                 from extension.c:31:
../../../src/include/nodes/pg_list.h:207:14: note: expected ‘void *’ but argument is of type ‘int’
  207 | extern List *lappend(List *list, void *datum);
      |              ^~~~~~~
xact.c: In function ‘AbortTransaction’:
xact.c:3197:3: warning: implicit declaration of function ‘ResetExtensionCreatingGlobalVarsOnQE’ [-Wimplicit-function-declaration]
 3197 |   ResetExtensionCreatingGlobalVarsOnQE();
      |   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

@HustonMmmavr @InnerLife0 ready for review

Also there are a broken pipeline at regression tests with postgres

True, please check the tests.
Also, I see some differences between 6x and 5x versions of test_extensions.sql. Can you briefly describe the difference and why our tests changed?

@HustonMmmavr there's no need to remove drop function test_func1 statement, this behaviour is consistent with 6x

test_extension.sql from the patch differs from the 6x version in the following cases:

gpdb5 doesn't support if not exists expression, so the test is irrelevant
gp_inject_fault test was dropped because of different internal organization of this extension
btree_gin extension doesn't exist in gpdb5 and was replaced by test_ext_cau which causes little differences across the test


this.book.setStyle is not a function error

When I try to use the reader.adjustFontSize function, it throws an error because there is no this.book.setStyle in epub.js. Can you point me in the right direction for changing the font size? @fchasen

Thanks, updated.

Thanks, updated.

Maybe you haven't pushed it ;)


fixed custom-accelerator create command

Prior documentation stated command should be az spring application-accelerator customized-accelerator add to add a new customized app accelerator.
Per the latest spring extension (1.14.0) the correct command is az spring application-accelerator customized-accelerator create

Thanks, @ryandotclair! I'll make this fix internally.
#please-close


🐛 [firebase_messaging 8.0.0-dev.5] App crashes when opening notification with data message in iOS

Bug report
Describe the bug
I am sending a notification with this payload to the app.
payload = {
                        notification: {
                            title: `You have received a new message!`,
                            body: contentMessage,
                            badge: '1',
                            sound: 'default',
                            click_action: 'FLUTTER_NOTIFICATION_CLICK',
                            idFrom: idFrom,
                            idTo: idTo,
                        },
                        data: {
                                asking: 'true'
                                screen: 'active'
                                type: 'qna',
                                convoId: '123456',
                        },
                    }

The notification is received when app is in background.. When I tap on it, the app opens and then crashes with no error logs.
Simply Lost connection to device.
This is my onMessageOpenedApp function
onMessage = FirebaseMessaging.onMessageOpenedApp
        .listen((RemoteMessage message) async {
      var data = message.data ?? ((message as Map).cast<String, dynamic>());
      if (data['type'] == 'inbox') {
        await goToInbox();
      }
      if (data['type'] == 'qna') {
        await goToQna(data);
      }
    });

I have tried removing the '((message as Map).cast<String, dynamic>());' before, but it didn't fix it.
When I try to print message, I get flutter: Instance of 'RemoteMessage'
This suggests that my message is being received and the function works, just that I suspect data field is null
Steps to reproduce
Steps to reproduce the behavior:

Send a notification with data message to iOS device.
Tap on notification to open the app when app is killed or backgrounded.

Expected behavior

App should open and navigate to the correct route.

Additional context
The code in its old form works when using 7.0.3. I suspect iOS is not handling the data message correctly as previously it was not attached to the 'data' field; the data fields were simply appended to the message directly.. Now there seems to be no way to access those fields as RemoteMessage class hides those fields.

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
[✓] Flutter (Channel stable, 1.22.3, on Mac OS X 10.15.6 19G2021, locale en-SG)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 12.1)
[!] Android Studio (version 4.1)
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
[✓] VS Code (version 1.50.1)
[✓] Connected device (3 available)

When I try to print message, I get flutter: Instance of 'RemoteMessage'
This suggests that my message is being received and the function works, just that I suspect data field is null

If you print message.data does that also cause it to crash, or does that show it as null?

I'm trying that now, will update in a bit.. takes some time to reboot the app as have to do flutter run again everytime it crashes.

No rush, am about to log off for the night, it's late here, will pick up first thing in morning, but any logs you have will be helpful. Thanks

The code is
   onMessage = FirebaseMessaging.onMessageOpenedApp
        .listen((RemoteMessage message) async {
      print('msg opened app');
      print(message);
      print(message.data);
      if (message.data == null) print('data is null');
      print(message.data['type']);
    });

The logs:
flutter: locale.languageCode: en
flutter: locale.languageCode: en
flutter: msg opened app
flutter: Instance of 'RemoteMessage'
flutter: {screen: active, asking: true, convoId: 5fa1c460bde60900135b923f, type: qna}
flutter: qna
flutter: msg opened app
flutter: Instance of 'RemoteMessage'
flutter: {screen: active, asking: true, convoId: 5fa1c460bde60900135b923f, type: qna}
flutter: qna
flutter: msg opened app
flutter: Instance of 'RemoteMessage'
flutter: {screen: active, asking: true, convoId: 5fa1c460bde60900135b923f, type: qna}
flutter: qna
flutter: msg opened app
flutter: Instance of 'RemoteMessage'
flutter: {screen: active, asking: true, convoId: 5fa1c460bde60900135b923f, type: qna}
flutter: qna
flutter: msg opened app
flutter: Instance of 'RemoteMessage'
flutter: {screen: active, asking: true, convoId: 5fa1c460bde60900135b923f, type: qna}
flutter: qna
flutter: msg opened app
Lost connection to device.

App crashed.

Seems like data is read but app still crashes..

Interesting, looks like the background handler is getting to the end of the function fine, might be something else causing an asynchronous crash. On Xcode you can attach to a process by name to debug and then send a message - when it comes through and if it crashes you should see the cause of the crash on detox. There's also the Console.app on macOS that will show your devices logs

Specifically, open your ios/Runner.xcworkspace file in Xcode, then run the app as you normally do through flutter run, and attach using:

Name should be Runner by default but if you've changed your app name then it'll be that.

Instead of crashing, it gets stuck at the splash screen when I attach the process using Xcode.. Not sure what this means

At the bottom right there should  be a logs/debug panel which you can copy logs from. That looks like the Firebsse iOS SDK is throwing an error, just need to see what it is
Could you screenshot the left panel as well, it should show the threads and what looks like a stack trace.

There wasn't any errors. But it's stuck here.

I tried it again.. seems like it keeps printing the print messages over and over... Might be some kind of overflow?

getInitialMessage() seems to have the same crashing issue, although I cannot confirm as not able to get logs when opening the app from a terminated state.

@Salakar Any luck with the repro? Let me know if I can assist further.. really hope to upgrade to v8 soon so that the android notifications can work properly again!

Could you share your AppDelegate with me? Struggling to reproduce

import UIKit
import Flutter

@UIApplicationMain
@objc class AppDelegate: FlutterAppDelegate {
  override func application(
    _ application: UIApplication,
    didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?
  ) -> Bool {
    if #available(iOS 10.0, *) {
      UNUserNotificationCenter.current().delegate = self as? UNUserNotificationCenterDelegate
    }
    GeneratedPluginRegistrant.register(with: self)
    return super.application(application, didFinishLaunchingWithOptions: launchOptions)
  }
}

Can you remove;
    if #available(iOS 10.0, *) {
      UNUserNotificationCenter.current().delegate = self as? UNUserNotificationCenterDelegate
    }

It's not required, did you add this for messaging specifically?

Yes I think so..
Although I believe it was added to allow both local notifications and flutter notifications to work at the same time if I didn't recall incorrectly.

Messaging & local notifications should now both be compatible without any manual changes (we added stuff internally to support this).

I see, let me try it. Wondering if this https://github.com/FirebaseExtended/flutterfire/issues/4034 is related.

I see, let me try it. Wondering if this #4034 is related.

Have commented there as well, I think it is the same issue.

Found the bit in the old documentation about it;

If you can confirm this solves your problem and everything still appears to be working then I can add an additional step to the migration guide to remove these.

Ok, what happens now is that the problem with firebase seems resolved BUT my local notification stopped being able to execute onSelectNotification function. Hence when I tap on my local notification, it no longer navigates me to the correct page.

Seems like it's required in their documentation:

https://pub.dev/packages/flutter_local_notifications

Damn, not sure why though as you can just delegate internally - will have a think and see if I can handle that internally. Whats happening is we're setting a delegate but if there's one there already we keep a reference to it and forward any calls on our delegate to the original, but the above also does that and so we're getting an infinite loop until a stack overflow.

Can you re-add the code to your delegate, and then I'll see if I can send you over a patch to apply locally quickly to confirm it works

Sure thing, I already have a local copy of your repo. you can let me know which branch.

Think I have a fix, 1 minute, I'll push up to a branch

@joniaiuser could you try https://github.com/FirebaseExtended/flutterfire/pull/4043 - thanks

Unfortunately, the crash is back when I add
    if #available(iOS 10.0, *) {
      UNUserNotificationCenter.current().delegate = self as? UNUserNotificationCenterDelegate
    }

Also noticed the same happens for local notifications, will check if it happens when using .dev5

Let me do a thorough flutter clean and pods delete and give it another try.

I'm also trying to try on my test iPhone device as well and add in that AppDelegate change, but Xcode has decided it hates me today and can't see my device 😫

Yup, confirmed that the issue exists with the fix.

Got my device working and have reproduced, leave it with me, am debugging. will get back to you shortly.

Right I have a fix again, but am just on a call right now. Will push in 20mins or so.

Ok, just pushed to the same branch @joniaiuser - could you try it again? Thanks :)

Great, seems to be fixed!

iOS seems fine now.. will proceed to test Android. Thanks!

Great, will ship a dev release shortly, just fixing another issue. Please ping me on the discussion if you come across anymore issues :)

8.0.0-dev.6 is now up.

If all goes well, we will be planning to try this in production middle of next week.


How to update schema and flush data cache without restarting xmondrian server?

Hi Roland,
Thanks for xmondrian, which make me easy to use mondrian to build OLAP engine.
I have one question about xmondrian cache. Once I modify the schema, or update the data in dw, I have to restart xmondrian server. Otherwise, I will get the old one. Would you have any suggestion to flush xmondrian cache? Should I write some codes to flush cache during xmondrian server is running? How to do it?
Thanks in advance.

Hi @hustszh! SOrry for the late reply - I should've replied earlier.

I have one question about xmondrian cache. Once I modify the schema, or update the data in dw, I have to restart xmondrian server. Otherwise, I will get the old one. Would you have any suggestion to flush xmondrian cache?

Currently, I have nothing in xmondrian that does this for you. But you're very right - it should certainly be possible to do this in a graceful way.
To tell you the truth, I currently do not know how to do this. My hunch is there must be already something that allows you to do this, but I did not configure it in the web.xml.

Should I write some codes to flush cache during xmondrian server is running? How to do it?

What would help is if you could look at the Mondrian documentation and see if there is a servlet already that could be used for this. Or maybe take a look at how Pentaho does it. If you could report your findings back here, then we can think about how to put this into xmondrian.
Thanks!

Greetings,
This can be done in the Pentaho BI control panel, clicking tools->refresh->mondrian cache, imho... this equivalent to
#!bin/bash
user=XXX
pass=XXX
host=localhost
schema=Reporting%20schemas

wget --no-check-certificate http://${host}:2310/pentaho/content/analyzer/ajax/clearCache?catalog=${schema}\&userid=${user}\&password=${pass}

Documentation http://mondrian.pentaho.com/api/mondrian/rolap/CacheControlImpl.html
I think, it should be help http://wiki.bizcubed.com.au/xwiki/bin/view/Main/Search?text=Flush+Mondrian+Cache
Roland, it would be very good to have this functionality in xmondrian.

IMHO you will find an answer there
https://mondrian.pentaho.com/documentation/schema.php#Dynamic_datasource_xmla_servlet

Thanks all. I will gladly accept a pull request for this.


Support for Lumen Framework v10.0

(Please read the guidelines before creating PRs.)
Changes proposed in this pull request:

Support for Lumen Framework v10.0
PHP 8.2 for tests

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 90.698%

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
78

Relevant Lines:
86

💛  - Coveralls

OK, I got it!
Also, I just realized that middleware Illuminate\Http\Middleware\HandleCors is available for Lumen. So, there is no need to use the package.
Anyway, thank you for your work!


Remove Clippy linting badge

Remove Clippy service linting badge because the clippy-service currently
incorrectly returns a failing result, despite the lack of clippy issues.
Closes #45.

Coverage remained the same at 97.802% when pulling b63c9ae46e0fcc78891761d8a2e7f2cd1f580768 on chore-remove-clippy-linting-badge into<PHONE_NUMBER>70ec265f2e1d5bbd9da235050fa323 on master.


PP-5249 Change event schema

We have agreed that an event should only have event metadata
as top level attributes, and any payload should be under
event_details.
As part of this I have removed the 'payment_id' from
the event, as this is contained in the external_resource_id.

looks good, one minor non blocking comment .. we could address that if we need to in the future


Duplicate summary ("rspec running twice")

Getting duplicate summary output, like #1929.
Code has one config.formatter = :documentation and my ~/.rspec has --format d. Removing either one of them solves the problem of getting duplicate summary.
Could it be possible for rspec to be smart about this?

Using ruby 2.2.2p95 and rspec-core 3.2.3.

Your instructing us to add two formatters here, given we support multiple formatters this is the expected behaviour, you can check in your config that formatters are empty before adding the :documentation formatter via code.

Actually, this feels like #1144 resurfacing, which was supposedly solved by #1206.  @JonRowe does this not seem like a regression to you?

Thanks @JonRowe

Oh I see whats happening, we actually have specs for this but they're not correct


Platformer Update

...

wait how did you open PR for just the latest commit instead of whole branch???????? Did you run git cherry-pick command?


Format code to Google Java Style Guide standards.

Google-originated open source projects should follow the Google Style Guide. The Java style guide can be found here.

Looks good to me.

I added another commit to make single-line JavaDoc comments where possible (had to adjust an option on my IntelliJ formatter and make the changes manually). I also had to change the email address on my git commits to pass the CLA checks (hence the "outdated diff" comment).

Great, thanks!

Awesome!


Subscription resource id usage in request unclear

Relates to https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb/issues/1926
The documentation could be a bit clearer with regards to the subscription resource id usage in the update (PATCH) and delete (DELETE) requests.  It took me quite some time to eventually find out that the id must be enclosed in single quotes.
The documentation currently looks like this:
DELETE businesscentralPrefix/subscriptions({'id'})

The fact that the single quotes are within the curly braces (which as per convention only contain placeholder data) and no other resource that I encountered needed single quotes, did it ever occur to me that these were a vital part of the syntax.
It's probably better to put the single quotes outside the curly braces, indicating that these are not part of the placeholder. And seeing as this is an exceptional situation compared to other resource, it might be useful to add some extra clarification.

DELETE {businesscentralPrefix}/subscriptions('{id}')

⚠ Attention: the id MUST be enclosed in single quotes.

@wimski - please add the article that the issue is related to- thx

@SusanneWindfeldPedersen

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/api-reference/v2.0/api/dynamics_subscriptions_update
https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/api-reference/v2.0/api/dynamics_subscriptions_delete


Feature request: A rule to turn private variables and methods if unused outside the class

@Component({
  template: `
    <div *ngIf="aMethod()">
      {{ x }}
    </div>
  `
})
class AppComponent {
  aMethod() {
    this.bMethod();
  }

  bMethod() { // failure here indicating that you can turn this in a private variable
    // ...
  }
}

PS: This rule may not be trivial to implement, since people could be using this method outside the template, in another component, for example.

Can the linter try to change it to private in a dry run of type checking and then check if it broke something? That seems like the easiest way to know if the user is using it somewhere.