Not accessible under automatic1111 API

Is there any way to access this via the automatic1111 API? I've noticed other extensions on my list are accessible.

I've managed to use this extension with the api.
in javascript the request looked like
depth_args ={
    'compute_device':0,
    'model_type':1,
    'net_width':512,
    'net_height':512,
    'match_size':true,
    'invert_depth':true,
    'boost':false,
    'save_depth':true,
    'show_depth':true,
    'show_heat':false,
    'combine_output':false,
    'combine_output_axis':0,
    'gen_stereo':false,
    'gen_anaglyph':false,
    'stereo_divergence':2.5,
    'stereo_fill':0,
    'stereo_balance':0,
    'clipdepth':false,
    'clipthreshold_far':1,
    'clipthreshold_near':0.0,
    'inpaint':false,
    'inpaint_vids':false,
    'background_removal_model':'u2net',
    'background_removal':true,
    'pre_depth_background_removal':false,
    'save_background_removal_masks':false,
     'gen_normal':false,
}

for the depth arguments and then
dic = {
        "init_images": [OrigImage],
        // 'mask': lastMask,
        'prompt': params.prompt,
        'negative_prompt': params.negative_prompt,
        'steps': params.steps,
        // 'inpainting_mask_invert':0,
        // 'inpainting_fill':1,
        'sampler_name': params.sampler_name,
        'cfg_scale': params.cfg_scale,
        'seed': seed,
        'width': width,
        'height': height,
        'denoising_strength': denoising_strength,
        'script_name': scriptname,
        'script_args': Object.values(depth_args)
        // 'mask_blur': 2
    }
fetch(url,
        {
            method: 'POST',
            body: JSON.stringify(dic),
            headers: {
                'Content-Type': 'application/json'
              },
            mode:'cors',
        }
    )

You might not need cors. It's mostly the same in python. There should be some way of making it more accessible to fastapi's listings.

Oh yes I missed that. At the time the value was
scriptname = "DepthMap v0.3.8"
now it'll be
scriptname = "DepthMap v0.3.10"
I haven't tested this yet with v0.3.10

@graemeniedermayer
Yes, the param count has changed too now, I have contemplated removing the version number from the scriptname for this reason, and only print it to console.
It also still has the gen_normal code I put in there for my own use that i forgot to remove before a commit at some point, so I could generate it all at once instead of having to make another api call and re-generate depth etc..
I will remove this in one of the future commits, perhaps you would like to make a MR to include it again at some point..

I still have not figured out how to setup the api to interace with the depth functions directly, instead of having to go through txt2img or img2img api with script_name ..
Here's the current parameter list :
compute_device, model_type, net_width, net_height, match_size, boost, invert_depth, clipdepth, clipthreshold_far, clipthreshold_near, combine_output, combine_output_axis, save_depth, show_depth, show_heat, gen_stereo, stereo_modes, stereo_divergence, stereo_fill, stereo_balance, inpaint, inpaint_vids, background_removal, save_background_removal_masks, gen_normal, pre_depth_background_removal, background_removal_model, gen_mesh, mesh_occlude, mesh_spherical

Yah! I was thinking about how update normal maps to include zoedepth (it works so well with faces), but it probably makes more sense to work on a MR so that I don't have to integrate each new update.
Also I was wondering if there's a reason for not passing the parameters a python dictionary/**kwargs. It would probably make API calls more stable (because the number of function parameters wouldn't change and you could re-order parameters), but there might be other ramifications I'm not thinking about.

I have not looked into it in detail, other extensions seem to be doing the same thing, but it is getting cumbersome to add/change  parameters, and impossible have a consistent api in the current state, yes. I would prefer an api endpoint to link straight to some depth functions, skip the whole img2img with script_name and args ..

I think it makes a lot of sense to move the version number to command line only.
A more direct api also makes a lot of sense. Especially with controlnet and other methods using depth maps as inputs, it feels clunky to call img2img with a lot of unused parameters.

I still have not figured out how to setup the api to interace with the depth functions directly, instead of having to go through txt2img or img2img api with script_name ..

Looking at other extensions that provide their own unique API's (by that I mean you do not have to access them through scripts on txt2img or img2img api calls and they also have unique entries added to API docs, which you can view by default here http://<IP_ADDRESS>:7860/docs#/), it looks like they might just include a small file defining those things, like api.py in the controlnet extension? I also noticed the dreambooth extension might have provided its own unique API's through A1111, so it might also provide an example but I no longer have it installed.


Improved CREATE TABLE AS

Background: https://airtable.com/tblD3oZPLJgGhCmch/viwchkdQkRUw6hZ3z/recUoBdXbVnkbBmtl?blocks=hide
PM: @rolandcrosby
Eng:

Important note to call out in the docs/release notes: CREATE TABLE AS statements will run as jobs in 19.2. This means that they will complete asynchronously and their results will not be immediately available. That change means that transactions like this one, which work in CockroachDB 19.1, will not work in 19.2:
BEGIN TRANSACTION;
CREATE TABLE foo AS (SELECT 1 AS col1);
UPDATE foo SET col1 = 2 * col1 WHERE col1 = 1;
COMMIT TRANSACTION;

I'm not concerned that this will break anyone's workflow -- usage of CREATE TABLE AS is very low, according to our telemetry data, and CREATE TABLE AS currently fails with tables of any meaningful size -- but we do need to call this out as a breaking change.

https://github.com/cockroachdb/cockroach/pull/38904
https://github.com/cockroachdb/cockroach/pull/38884
https://github.com/cockroachdb/cockroach/pull/38589

Important note to call out in the docs/release notes: CREATE TABLE AS statements will run as jobs in 19.2. This means that they will complete asynchronously and their results will not be immediately available. That change means that transactions like this one, which work in CockroachDB 19.1, will not work in 19.2:
BEGIN TRANSACTION;
CREATE TABLE foo AS (SELECT 1 AS col1);
UPDATE foo SET col1 = 2 * col1 WHERE col1 = 1;
COMMIT TRANSACTION;

I'm not concerned that this will break anyone's workflow -- usage of CREATE TABLE AS is very low, according to our telemetry data, and CREATE TABLE AS currently fails with tables of any meaningful size -- but we do need to call this out as a breaking change.

Is this currently true? I ran a CTAS statement and I don't see it in SHOW JOBS. Does the CTAS need to be a certain size for it to be a job?

Note: @ericharmeling made most of the necessary edits about a month ago.

Chatted with @rolandcrosby about this today. No additional docs changes need to be added.


fix(import): Show the error message with db install guide when exist the importing db issue

SUMMARY
Add error message when user tries to import without having db driver installed
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
BEFORE:

AFTER:
https://user-images.githubusercontent.com/47900232/176767158-36c312bd-b20a-4500-ba68-b30f51bd26d3.mov
TESTING INSTRUCTIONS

Go to Connect Database Modal
Select the import database from invalid file.

In case of Invaid db file with already installed driver
In case of invaoide db fiel with not installed driver
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

/testenv up

A few text updates needed:
When the error shows up on the password screen:

Period missing before "Please" and there's an extra space between the : and here
When the error shows up on the db connection screen, a period is also missing before "Please"

@yousoph
Resolved your review. Please kindly check this.

/testenv up


Remove dependency on GOV.UK Frontend Toolkit 🎉

What
Move modules.js from govuk_frontend_toolkit into govuk_publishing_components (without changes - for now) and remove dependency on govuk_frontend_toolkit.
It's been a bit over an year since we started to slowly migrate from govuk_frontend_toolkit to govuk-frontend and this is the last final bit. The migration was a collective effort, so thanks a lot to everyone who contributed to this and made it possible! 🙌
Why
Remove dependency on deprecated projects
Fixes #500
Visual Changes
No visual changes.
Notes
This is not a breaking change, nor a feature - more of an internal change.
The tests for this seem to be flaky, so I'd like to have a look at them and try to fix them up before merging. Will do this in a separate commit to ease the review. Fixed the FilterComponents spec - no flaky tests anymore.

Most of the apps will still pull this code in from the toolkit,
Yes, there are a couple with direct dependency on govuk_frontend_toolkit. Hope we'll get rid of those too rather soon.

so until we remove/modify those dependencies it'll run twice
Nope, the migrated modules.js will only run once since they're part of dependencies.js which was introduced for and imported by projects that don't use static (e.g. Content Publisher, Content Data, Collection Publisher). All the public facing applications initialise modules via static. We should work to converge them at some point, but until then this helps moving the script to govuk_publishing_components and use with the new layouts (admin_layout and the new public-facing layout @vanitabarrett started the work on).

we should probably test if that happens safely.
Test in progress with various apps. Will update the PR comment with a checklist.

Just a note: one other alternative to removing this code would be to manually initialise components similar to what we do in GOV.UK Frontend.


'Source Control' commit message input some time block

Version: 1.52.1
Commit: ea3859d4ba2f3e577a159bc91e3074c5d85c0523
Date: 2020-12-16T16:30:02.420Z
Electron: 9.3.5
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 17.7.0
Steps to Reproduce:

I don't know how exactly reproduce this issue
Some time I just type text in input, input block, I have made a gif

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

Follow up

Can't delete 'Fix:'

I have the same problem.

Duplicate of #112621

Duplicate of #112621

Duplicate of #112621

Duplicate of #112621


Feature request: package entry point for reactive core

The current package entry points use conditional exports which make assumptions about my desired behavior, and provide different implementations based on my environment. In my case, I want to use solid as a reactive state management library on my server, and assumed I wanted SSR with no reactivity.
I want an entry point like solid-js/reactive to import the reactive core of solid-js (signals, effects, memos, etc) without any assumptions being made.

Yes.. the plan is to export the reactive core separately in our next major version.


Small improvement in syntax

module CreateGoalFeedItemMutation = [%graphql
  {|
    mutation CreateGoalFeedItem($goalFeedItem: CreateGoalFeedItemInput!) {
      createGoalFeedItem(goalFeedItem: $goalFeedItem) {
        id
      }
    }
|}
];

to:
[%graphql
  {|
    mutation CreateGoalFeedItem($goalFeedItem: CreateGoalFeedItemInput!) {
      createGoalFeedItem(goalFeedItem: $goalFeedItem) {
        id
      }
    }
|}
];

In other words skip the module declaration as we already have the name of the mutation and query which is not reflected in the data, so it is an ideal identifier we can use as the module name so we have less repetition. Any thoughts? Do I miss certain use cases?

Operation name is not required in GraphQL.
I think it’s less magical especially for newcomers when you assign result expicitly to module.

I’m against this change as it doesn’t bring any value.

I think this would break include [%graphql ...] which I frequently use

Ok I wanted this idea out there. Probably not worth it :)


fix typo

Hi @Hanope thanks for the typo fix. Please submit this change against the 2.1.x branch instead of master.

Okay. I'll reflect that.


Add reorder_extern_crates?

Would it be possible to add reordering of extern crate statements alphabetically:

Default value: false
Possible values: true, false

false:
extern crate futures;
extern crate chrono;
extern crate dotenv;

true:
extern crate chrono;
extern crate dotenv;
extern crate futures;

Thanks

I think this was part of the fmt RFC, so yes we should do it, and the default should be true, I think

Oh I see, great! Thank you!


Sometimes Baron and Steel cards are giving suboptimal results

Here's a situation where it happened:
https://efhiii.github.io/balatro-calculator/?h=gAA2DAAHMCYPQeq1AKAAFA
It optimizes to AAKK which is worth 246 chips. If you manually change the hand to AAQQ, the score jumps up to 830 chips.
If you put Two Pairs to level 1 instead of 2, it correctly optimizes to AAQQ.

That bug was harder to track down than I was expecting, but it should be fixed now.


Remove left scroll bar

Purpose

This PR will remove left scroll bar

Check List

[x] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

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

@@           Coverage Diff           @@
##           master   #17021   +/-   ##
=======================================
  Coverage   68.85%   68.85%
=======================================
  Files           5        5
  Lines         122      122
  Branches       21       21
=======================================
  Hits           84       84
  Misses         38       38

Continue to review full report at Codecov.

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


fix(styles): set tooltip opacity to 1

Preview environments are getting posted here, as soon as they are ready!


vsvg commandline silently fails when using absolute paths.

Hello. Thank you for vue-svgicon. Really enjoy having svg icons in my Vue project!
I noticed something that may be an issue, namely if I use the vsvg commandline together with absolute paths, it seems to fail without notice. This works:
vsvg -s ./build/__tmp/bologna/svg -t ./src/brand/bologna/icons Generated icon: arrow Generated icon: availability Generated icon: check Generated icon: close ...
While this doesn't:
vsvg -s /home/myuser/projects/vialer-js/build/__tmp/bologna/svg -t /home/myuser/projects/vialer-js/src/brand/bologna/icons
I would expect the same build output.

Fixed in v3.1.0


Update eosio-test-stability.md

Fix some small typos.

Change Description

Change Type
Select ONE:

[x] Documentation

[ ] Stability bug fix

[ ] Other

[ ] Other - special case

Testing Changes
Select ANY that apply:

[ ] New Tests

[ ] Existing Tests

[ ] Test Framework

[ ] CI System

[ ] Other

Consensus Changes

[ ] Consensus Changes

API Changes

[ ] API Changes

Documentation Additions

[ ] Documentation Additions

I am force-merging this pull request despite the failing unpinned macOS unit test(s) because this pull request contains a trivial pipeline documentation update in markdown with no code changes of any kind. The unit tests are failing due to a dependency issue that has since been fixed on the base branch. @bogniq and I agree that spending the manpower to rebase or merge in the latest develop and then wait for another round of CI is not advantageous compared to a force-merge.


Need at least one value for approx.match set for fuzzy map to work, and set correct default values

approx.match should be full optional

hopefully fixed with: [32ba149]
TODO: Write Test cases for this


out of date error Wow Classic

playing wow classic Version 1.16.5 (7065)
it says out of date in addon window.
when loading the addons im getting following error: .../AI_VoiceOver/Libs/CallbackHandler-1.0/CallbackHandler-1.0.lua:24: unexpected symbol near `...'

pls delete. downloaded wrong version


[WIP] Generic column type

Ref #55, #87, #88, #91

[x] pass datasource test
[ ] pass differ test

Close #55
Close #87
Close #88
Close #91


Quokka is dead, long live the Quokka! (it is being rewritten from scratch)

QuokkaCMS growed in to an amazing project and there are many users using the currrent version.
The problem is that too many feature requests lead in to too many issues to fix and implement.
The lack of contributors lead in to a slow pace development.
So I decided to kill this version! and start a brand new one[1] which is going to be more simple and many things will be moved in to external plugins.
So I'll need to maintain only the small core of the CMS and plugins would be maintained by community.
I am also removing the MongoDB dependency (it will be optional)
If you want to follow the Quokka Rewrite please take a look in to temporary repository [1] and once it is ready to release I'll archive this existing version in another branch and replace master branch of this repo with the new CMS.
The existing codebase will be kept in another branch but will not be actively maintained, only hotfixes and community PRs will be accepted, but the evolution of the project will be focused in quokka new generation
[1]  https://github.com/rochacbruno/quokka_ng/blob/master/README.md
Suggestions please use the issues on the new repo.
Cheers!
Long live the Quokka!!!

:+1:


Can't get omnisharp-vim to work on dotnet mvc projects

I'm using omnisharp-vim with neovim on ArchLinux (dotnet version 5.0.204).
When I open a solution with multiple projects, it works just fine when I edit files in projects of type "class library", but when I'm in a MVC project, nothing seems to be working (no auto-completion, no "go to definition" etc.). It does say that "OmniSharp server was loaded" for the .sln file of the project.
I tried re-creating this with a brand new project and I get the exact same issue.
I also tried completely removing omnisharp-vim multiple times, and I've tried :OmniSharpRestartServer and :OmniSharpRestartAllServers.
Am I supposed to install additional plugins of some sorts? I've followed the installation instructions from the readme.
Here is my config (omitted non-relevant parts in the interest of brevity), full one could be found here :
" Plugins
" ---------------------------------------------
call plug#begin(stdpath('data') . '/plugged')

Plug 'junegunn/fzf', { 'do': { -> fzf#install() } }
Plug 'junegunn/fzf.vim'

" C# support
Plug 'OmniSharp/omnisharp-vim'
Plug 'dense-analysis/ale'

" Syntax highlighting for various languages
Plug 'sheerun/vim-polyglot'

call plug#end()

" OmniSharp Settings (DEFAULT)
" ---------------------------------------------
let g:OmniSharp_highlighting = 0
let g:OmniSharp_server_stdio = 1
let g:OmniSharp_popup_position = 'peek'

" Use fzf
let g:OmniSharp_selector_ui = 'fzf'
let g:OmniSharp_selector_findusages = 'fzf'

" Don't autoselect first omnicomplete option, show options even if there is only
" one (so the preview documentation is accessible). Remove 'preview', 'popup'
" and 'popuphidden' if you don't want to see any documentation whatsoever.
" Note that neovim does not support `popuphidden` or `popup` yet:
" https://github.com/neovim/neovim/issues/10996
if has('patch-8.1.1880')
  set completeopt=longest,menuone,popuphidden
  " Highlight the completion documentation popup background/foreground the same as
  " the completion menu itself, for better readability with highlighted
  " documentation.
  set completepopup=highlight:Pmenu,border:off
else
  set completeopt=longest,menuone,preview
  " Set desired preview window height for viewing documentation.
  set previewheight=5
endif

" Tell ALE to use OmniSharp for linting C# files, and no other linters.
let g:ale_linters = { 'cs': ['OmniSharp'] }

augroup omnisharp_commands
  autocmd!

  " Show type information automatically when the cursor stops moving.
  " Note that the type is echoed to the Vim command line, and will overwrite
  " any other messages in this space including e.g. ALE linting messages.
  autocmd CursorHold *.cs OmniSharpTypeLookup

  " The following commands are contextual, based on the cursor position.
  autocmd FileType cs nmap <silent> <buffer> <Leader>gd <Plug>(omnisharp_go_to_definition)
  autocmd FileType cs nmap <silent> <buffer> <Leader>gr <Plug>(omnisharp_find_usages)
  autocmd FileType cs nmap <silent> <buffer> <Leader>gi <Plug>(omnisharp_find_implementations)
  autocmd FileType cs nmap <silent> <buffer> <Leader>pd <Plug>(omnisharp_preview_definition)
  autocmd FileType cs nmap <silent> <buffer> <Leader>pr <Plug>(omnisharp_preview_implementations)
  autocmd FileType cs nmap <silent> <buffer> <Leader>ost <Plug>(omnisharp_type_lookup)
  autocmd FileType cs nmap <silent> <buffer> K <Plug>(omnisharp_documentation)
  autocmd FileType cs nmap <silent> <buffer> <Leader>fs <Plug>(omnisharp_find_symbol)
  autocmd FileType cs nmap <silent> <buffer> <Leader>ufx <Plug>(omnisharp_fix_usings)
  autocmd FileType cs nmap <silent> <buffer> <C-\> <Plug>(omnisharp_signature_help)
  autocmd FileType cs imap <silent> <buffer> <C-\> <Plug>(omnisharp_signature_help)

  " Navigate up and down by method/property/field
  autocmd FileType cs nmap <silent> <buffer> [[ <Plug>(omnisharp_navigate_up)
  autocmd FileType cs nmap <silent> <buffer> ]] <Plug>(omnisharp_navigate_down)
  " Find all code errors/warnings for the current solution and populate the quickfix window
  autocmd FileType cs nmap <silent> <buffer> <Leader>gcc <Plug>(omnisharp_global_code_check)
  " Contextual code actions (uses fzf, vim-clap, CtrlP or unite.vim selector when available)
  autocmd FileType cs nmap <silent> <buffer> <Leader>ac <Plug>(omnisharp_code_actions)
  autocmd FileType cs xmap <silent> <buffer> <Leader>ac <Plug>(omnisharp_code_actions)
  " Repeat the last code action performed (does not use a selector)
  autocmd FileType cs nmap <silent> <buffer> <Leader>os. <Plug>(omnisharp_code_action_repeat)
  autocmd FileType cs xmap <silent> <buffer> <Leader>os. <Plug>(omnisharp_code_action_repeat)

  autocmd FileType cs nmap <silent> <buffer> <Leader>os= <Plug>(omnisharp_code_format)

  autocmd FileType cs nmap <silent> <buffer> <Leader>rn <Plug>(omnisharp_rename)

  autocmd FileType cs nmap <silent> <buffer> <Leader>osre <Plug>(omnisharp_restart_server)
  autocmd FileType cs nmap <silent> <buffer> <Leader>osst <Plug>(omnisharp_start_server)
  autocmd FileType cs nmap <silent> <buffer> <Leader>ossp <Plug>(omnisharp_stop_server)
augroup END

Any help would be highly appreciated.

It sounds like a server issue. Meaning that the OmniSharp-roslyn server (and the dotnet build chain) may have missing dependencies.
If you check :messages, are there errors displayed before the Loaded server for ...sln output? Check the log too, with :OmniSharpOpenLog. For more debugging info, add let g:OmniSharp_loglevel = 'debug' to your init.vim and restart.

First of all, thank you for helping out, much appreciated!
So here is what I got from :messages:
Failed to load project: /home/ddimitrov/Dev-Playground/TestProject/TestProject.Web/TestProject.Web.csproj
Loaded server for /home/ddimitrov/Dev-Playground/TestProject/TestProject.Web in 3.2s

Here is some output from :OmniSharpOpenLog (I've only included the parts with errors):
...

[dbug]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Attempting to resolve 'Microsoft.Build.Tasks.Core.resources, Version=<IP_ADDRESS>, Culture=en-US, PublicKeyToken=b03f5f7f11d50a3a'
[dbug]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        FAILURE: Could not locate '/home/ddimitrov/.cache/omnisharp-vim/omnisharp-roslyn/omnisharp/.msbuild/Current/Bin/Microsoft.Build.Tasks.Core.resources.dll'.
Can't find custom attr constructor image: /home/ddimitrov/Dev-Playground/TestProject/TestProject.Core/bin/Debug/net5.0/TestProject.Core.dll mtoken: 0x0a000001 due to: Cannot resolve dependency to assembly because it has not been preloaded. When using the ReflectionOnly APIs, dependent assemblies must be pre-loaded or loaded on demand through the ReflectionOnlyAssemblyResolve event.
JSON error: Vim(let):E474: Unidentified byte: Can't find custom attr constructor image: /home/ddimitrov/Dev-Playground/TestProject/TestProject.Core/bin/Debug/net5.0/TestProject.Core.dll mtoken: 0x0a000001 due to: Cannot resolve dependency to assembly because it has not been preloaded. When using the ReflectionOnly APIs, dependent assemblies must be pre-loaded or loaded on demand through the ReflectionOnlyAssemblyResolve event.
[fail]: OmniSharp.MSBuild.ProjectLoader
        The "Microsoft.AspNetCore.Razor.Tasks.DiscoverDefaultScopedCssItems" task could not be loaded from the assembly /usr/share/dotnet/sdk/5.0.204/Sdks/Microsoft.NET.Sdk.Razor/build/netstandard2.0/../../tasks/net46/Microsoft.NET.Sdk.Razor.Tasks.dll. Invalid Image Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.
[warn]: OmniSharp.MSBuild.ProjectManager
        Failed to load project file '/home/ddimitrov/Dev-Playground/TestProject/TestProject.Web/TestProject.Web.csproj'.
All projects loaded
/home/ddimitrov/Dev-Playground/TestProject/TestProject.Web/TestProject.Web.csproj
/usr/share/dotnet/sdk/5.0.204/Sdks/Microsoft.NET.Sdk.Razor/build/netstandard2.0/Microsoft.NET.Sdk.Razor.ScopedCss.targets(118,3): Error: The "Microsoft.AspNetCore.Razor.Tasks.DiscoverDefaultScopedCssItems" task could not be loaded from the assembly /usr/share/dotnet/sdk/5.0.204/Sdks/Microsoft.NET.Sdk.Razor/build/netstandard2.0/../../tasks/net46/Microsoft.NET.Sdk.Razor.Tasks.dll. Invalid Image Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.
[fail]: OmniSharp.MSBuild.ProjectManager
        Attempted to update project that is not loaded: /home/ddimitrov/Dev-Playground/TestProject/TestProject.Web/TestProject.Web.csproj
...

Any ideas? I did dotnet clean then dotnet restore and dotnet build multiple times with no errors.
Not sure what I'm doing wrong, mind you this is a brand new "test" project that I'm working with here.

I found a solution, for others that are facing this issue, this here is what helped me.
Not sure why it occurs or what is the problem, but apparently there were missing dependencies (my project could build fine and all, but OmniSharp was struggling).
Anyway, thank you @nickspoons for your help!

Nice find, glad to hear you got it working, thanks for reporting back with your fix.


Identification of production constraints

Need to identify and define the constraints instead of just writing headings

Identification of production constraints is completed.


feat(#121): add new design for repo-cards, closes #121, closes #118

https://github.com/max-programming/hacktoberfest-projects/assets/86684667/4d026eed-9b42-4f49-91b7-8b9817b07223

Looks so good! Thanks @sadiksaifi

@sadiksaifi Can you also make it so that the text shows a ... instead of just simply disappearing?

Ok

@sadiksaifi Can you also make it so that the text shows a ... instead of just simply disappearing?

Done in the latest commit

Thaank you so much!
@all-contributors please add @sadiksaifi for design, code


SAS Attach Does Not Auto-Detect Endpoints

Storage Explorer Version: 1.9.0 rel branch
When I attach using a SAS URI, the endpoint for the service type I'm attaching isn't filled out:

As a customer, this might make me wonder if my URI is wrong.

Verified this on build 20201209.5. Fixed.


How to schedule a notification on the specific hour in any day?

Hi,
You have to do your own logic to schedule notifications, you could use Larvel Jobs for this purpose.


Thumbnails of new maps are always centered in Morocco

Fixes #2974

@rafatower CR please

(failing tests are just because I'm now properly recalculating center and had some hardcoded values so only specs are affected)

:+1:


Home app on iPhone X can't connect to HomeBridge on Win10

Expected Behavior

I can't seem to connect HomeBridge (running on Windows 10) on the Home app on my iPhone X. All devices are on the same network.

Current Behavior

When I either scan the HomeKit barcode or enter the appropriate code, iPhone X's Home app can't seem to connect to Homebridge.

Steps to Reproduce (for bugs)

Versions

Homebridge: 0.4.38
Node: v8.9.4
OS: Windows 10 Pro

Configuration

{
    "bridge": {
        "name": "Homebridge",
        "username": "CC:22:3D:E3:CE:20",
        "port": 51826,
        "pin": "031-45-154"
    },
    "description": "Config file.",
    "accessories": [ ],
    "platforms": [
   	{
   		"platform": "Nest",
   		"clientId": "<client ID entered here>",
   		"clientSecret": "<client secret entered here>",
   		"code": "<code entered here>",
		"token": "<token entered here>"
   	}
   ]
}

Homebridge Log / Command Output

check windows firewall
Sent with GitHawk

Based on your comment, I went into Windows Firewall and specifically opened up the port. Restarted Homebridge, but the issue still persists. :(

try stopping the firewall service, just to be sure

I've stopped the firewall, but the issue persists.

Hmm, I don't have any blocked (or unblocked) Node.js entries on my inbound rules.


[SMALLFIX] Fixed self link of 'acquire' method in 'ResourcePool' class

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/6961/
Test PASSed.

LGTM


Add a license just to be explicit that people can use it.

I know some people who want to use Gilded Rose with their teams but worry about copyright & license issues. MIT license would make it clearly safe.

Done and done. Thank you for the PR.


Failed to install srecord

Please follow the general troubleshooting steps first:

[x] Ran brew update and retried your prior step?
[x] Ran brew doctor, fixed as many issues as possible and retried your prior step?
[x] If you're seeing permission errors tried running sudo chown -R $(whoami) $(brew --prefix)?

You can erase any parts of this template not applicable to your Issue.
Bug reports:
I'm sorry if this isn't entirely related to home-brew but I was trying to install srecord with brew install srecord and it just ends with some tests failing:
==> make check
Last 15 lines from /Users/tiferrei/Library/Logs/Homebrew/libgcrypt/04.make:
HMAC_SHA3_384           10ms    10ms    10ms
HMAC_SHA3_512           10ms    10ms    20ms
/bin/sh: line 1: 37854 Segmentation fault: 11  GCRYPT_IN_REGRESSION_TEST=1 ${dir}$tst
FAIL: benchmark
/bin/sh: line 1: 37872 Segmentation fault: 11  GCRYPT_IN_REGRESSION_TEST=1 ${dir}$tst
FAIL: bench-slope
SKIP: hashtest-256g
======================================
4 of 25 tests failed
(1 test was not run)
Please report to http://bugs.gnupg.org
======================================
make[2]: *** [check-TESTS] Error 1
make[1]: *** [check-am] Error 2
make: *** [check-recursive] Error 1

READ THIS: https://git.io/brew-troubleshooting
If reporting this issue please do so at (not Homebrew/brew):
  https://github.com/Homebrew/homebrew-core/issues

Sorry, moved to homebrew-core.


fix: "Reloading" spin forever when restart bot

Description
Move botStatusInterval out of TestController component, to make sure it won't create duplicated every time component reloaded.
Task Item
close #3930
Screenshots

Verified. Issue fixed.


RWA-3714 update test

JIRA link (if applicable)
Change description
Fix flaky test
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

This PR is not required so closing


Question for Translation task and Failed to reproduce Translation results

hi,
for c# java translation task.
I see  the code_bleu is not reported in the paper.  could you share the scores ? or can the translation result can be published ?
The code bleu score is important for this task.
Thanks
I downloaded the released model  and run inference on java-C# translation task. I got the result as below which not matched in the raw paper:
cs to java translation
from transformers import RobertaTokenizer, T5ForConditionalGeneration
tokenizer = RobertaTokenizer.from_pretrained(
    'path/to/codet5/cs_java')
model = T5ForConditionalGeneration.from_pretrained(
    'path/to/codet5/cs_java')
model = model.to("cuda")

def predict(samples):
    results = []
    for sample in samples:
        input_ids = tokenizer(sample, return_tensors="pt").input_ids.to("cuda")
        generated_ids = model.generate(input_ids, max_length=510)
        rst = tokenizer.decode(generated_ids[0], skip_special_tokens=True)
        results.append(rst)
    return results

cs = [line.strip() for line in open("./test.java-cs.txt.cs", "r")]
results = predict(cs)

scores
BLEU: 77.79
ngram match: 0.7778875426766637, weighted ngram match: 0.7859241463045725, syntax_match: 0.9075318329182916, dataflow_match: 0.9004485422377274
CodeBLEU score:  0.8429480160343139
EM: 0.649, = 649/1000
java to cs translation
BLEU: 81.57
ngram match: 0.8157761914953569, weighted ngram match: 0.827130874395443, syntax_match: 0.8968348170128586, dataflow_match: 0.9094303577631122
CodeBLEU score:  0.8622930601666927
EM: 0.618, = 618/1000

Hi @runningmq , sorry for the late response. It seems your replicated inference script might have some discrepancy with the one we use. I would suggest that you can try to employ our released script to reproduce the results. Please refer to here for more details.


Query Merge cells data

exceldatareader

It need to check a lots details, so right now it's not important

MiniExcel thinks mergecell must contain the cells

v 0.14.4 support this


Adding 2 openings

#1520 , #1521,
f1d85cecf85d7da38401dc58fabf1aa4294c881bb9d2c47642d1b460017f06cd

@IvanDanilov66 Single PR is not allowed to close multiple issues. Please create different PRs.

yes we should have one issues per commit. But will accept this one due to the whole frozen situation

paid


Feature Request: add unit tests

Unit testing this library would be a great addition for both you, your maintainers and people using the NPM package.
I recommend looking into Jest as it is well documented and also open-source.

Yeah I've plan to add these tests. But exam is going on so I'm not able to work  I'll be adding them after my exam.


fix bugs

Coverage remained the same at 54.431% when pulling d666574f66f40dbac78cfc85ad1cbf6fb8d6c443 on pengpengshui:master into aabfc9de6b4dbebc2428302ed86c32e00100d0f0 on vmware:master.

Coverage remained the same at 54.431% when pulling 87b0f3460e2bf7fbbcd1d62b6b5f84401699c919 on pengpengshui:master into aabfc9de6b4dbebc2428302ed86c32e00100d0f0 on vmware:master.


[GHSA-353f-5xf4-qw67] Vite Server Options (server.fs.deny) can be bypassed using double forward-slash (//)

Updates

Description

Comments
Added Extra references and provided better documentation of the fix.

Hi there @agussetyar and @patak-dev! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.
This change will be reviewed by our highly-trained Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory


[WIP] Simplify Makefile

List of targets is more logical
Use BUILD_DIR to output binaries
clean target is simpler (removes whole build dir)

Signed-off-by: Drasko DRASKOVIC<EMAIL_ADDRESS>

Alas, I have just noticed that https://github.com/edgexfoundry/edgex-go/issues/26 blocks this PR.
Should not be merged until this issue is resolved.

@jpwhitemn @janko-isidorovic @tsconn23 please do not merge this one yet. We have to see can the binaries be moved to build dir during compilation, and how to handle hard-coded config file path.
Probably Makefile will have to move the configs and put them on our build or release directory during the compilation, so we can then easily move the whole package from one computer to another.

recheck

@tsconn23 I will take a look at it and propose resolution.

Dropping this PR for now, not a priority. I will align later when we have clearer picture of where binaries actually have to go.


Unable to kill SuperAGI docker container

please refer to below back trace
Gracefully stopping... (press Ctrl+C again to force)
Aborting on container exit...
[+] Stopping 2/2
[+] Stopping 2/2eragi-celery-1  Error while Stopping                                                                                14.2s
[+] Stopping 2/2eragi-celery-1  Error while Stopping                                                                                14.2s
✘ Container superagi-celery-1  Error while Stopping

Can you try docker compose down?

Try following commands docker ps - To list the containers running docker stop <container_id> - To gracefully stop a particular container id docker kill <container_id> - To force stop

Can you try using commands as with sudo like sudo docker stop .. etc.

Can you try using commands as with sudo like sudo docker stop .. etc.

If you have a snap installed version of docker, you can do, sudo aa-remove-unknown, it will remove unknown snap packages and you can do sudo docker compose down after that

Is this solved? @mramitdas ?

Closing this issue for now. Please reopen if required


macOS compile error: /usr/local/include/Poco/Dynamic/Var.h:199: error: no matching member function for call to 'convert'

On macOS sierra I installed poco with brew and when compiling this project it shows the following compile error:
In file included from ../../../api/libs/autobahn/autobahn.cpp:19:
In file included from ../../../api/libs/autobahn/autobahn.h:37:
/usr/local/include/Poco/Dynamic/Var.h:199:13: error: no matching member function for call to 'convert'
                        pHolder->convert(result);
                        ~~~~~~~~~^~~~~~~
../../../api/libs/autobahn/autobahn.cpp:401:18: note: in instantiation of function template specialization 'Poco::Dynamic::Var::operator unsigned long long<unsigned long long>' requested here
  m_session_id = msg[1];
                 ^
/usr/local/include/Poco/Dynamic/VarHolder.h:434:24: note: candidate function not viable: no known conversion from 'unsigned long long' to 'Int8 &' (aka 'signed char &') for 1st argument
inline void VarHolder::convert(Int8& /*val*/) const
                       ^
/usr/local/include/Poco/Dynamic/VarHolder.h:440:24: note: candidate function not viable: no known conversion from 'unsigned long long' to 'Int16 &' (aka 'short &') for 1st argument
inline void VarHolder::convert(Int16& /*val*/) const
                       ^
/usr/local/include/Poco/Dynamic/VarHolder.h:446:24: note: candidate function not viable: no known conversion from 'unsigned long long' to 'Int32 &' (aka 'int &') for 1st argument
inline void VarHolder::convert(Int32& /*val*/) const
                       ^
/usr/local/include/Poco/Dynamic/VarHolder.h:452:24: note: candidate function not viable: no known conversion from 'unsigned long long' to 'Int64 &' (aka 'long &') for 1st argument
inline void VarHolder::convert(Int64& /*val*/) const
                       ^
/usr/local/include/Poco/Dynamic/VarHolder.h:458:24: note: candidate function not viable: no known conversion from 'unsigned long long' to 'UInt8 &' (aka 'unsigned char &') for 1st argument
inline void VarHolder::convert(UInt8& /*val*/) const
                       ^
/usr/local/include/Poco/Dynamic/VarHolder.h:464:24: note: candidate function not viable: no known conversion from 'unsigned long long' to 'UInt16 &' (aka 'unsigned short &') for 1st argument
inline void VarHolder::convert(UInt16& /*val*/) const
                       ^
/usr/local/include/Poco/Dynamic/VarHolder.h:470:24: note: candidate function not viable: no known conversion from 'unsigned long long' to 'UInt32 &' (aka 'unsigned int &') for 1st argument
inline void VarHolder::convert(UInt32& /*val*/) const
                       ^
/usr/local/include/Poco/Dynamic/VarHolder.h:476:24: note: candidate function not viable: no known conversion from 'unsigned long long' to 'UInt64 &' (aka 'unsigned long &') for 1st argument
inline void VarHolder::convert(UInt64& /*val*/) const
                       ^
/usr/local/include/Poco/Dynamic/VarHolder.h:482:24: note: candidate function not viable: no known conversion from 'unsigned long long' to 'Poco::DateTime &' for 1st argument
inline void VarHolder::convert(DateTime& /*val*/) const
                       ^
/usr/local/include/Poco/Dynamic/VarHolder.h:488:24: note: candidate function not viable: no known conversion from 'unsigned long long' to 'Poco::LocalDateTime &' for 1st argument
inline void VarHolder::convert(LocalDateTime& /*val*/) const
                       ^
/usr/local/include/Poco/Dynamic/VarHolder.h:494:24: note: candidate function not viable: no known conversion from 'unsigned long long' to 'Poco::Timestamp &' for 1st argument
inline void VarHolder::convert(Timestamp& /*val*/) const
                       ^
/usr/local/include/Poco/Dynamic/VarHolder.h:518:24: note: candidate function not viable: no known conversion from 'unsigned long long' to 'bool &' for 1st argument
inline void VarHolder::convert(bool& /*val*/) const
                       ^
/usr/local/include/Poco/Dynamic/VarHolder.h:524:24: note: candidate function not viable: no known conversion from 'unsigned long long' to 'float &' for 1st argument
inline void VarHolder::convert(float& /*val*/) const
                       ^
/usr/local/include/Poco/Dynamic/VarHolder.h:530:24: note: candidate function not viable: no known conversion from 'unsigned long long' to 'double &' for 1st argument
inline void VarHolder::convert(double& /*val*/) const
                       ^
/usr/local/include/Poco/Dynamic/VarHolder.h:536:24: note: candidate function not viable: no known conversion from 'unsigned long long' to 'char &' for 1st argument
inline void VarHolder::convert(char& /*val*/) const
                       ^
/usr/local/include/Poco/Dynamic/VarHolder.h:542:24: note: candidate function not viable: no known conversion from 'unsigned long long' to 'std::string &' (aka 'basic_string<char, char_traits<char>, allocator<char> > &') for 1st argument
inline void VarHolder::convert(std::string& /*val*/) const
                       ^
/usr/local/include/Poco/Dynamic/VarHolder.h:548:24: note: candidate function not viable: no known conversion from 'unsigned long long' to 'Poco::UTF16String &' (aka 'basic_string<unsigned short, Poco::UTF16CharTraits> &') for 1st argument
inline void VarHolder::convert(Poco::UTF16String& /*val*/) const
                       ^
1 error generated.

This library was never tested on a mac. I don't have access to that platform. PRs welcome though!
/usr/local/include/Poco/Dynamic/VarHolder.h:476:24: note: candidate function not viable: no known conversion from 'unsigned long long' to 'UInt64 &' (aka 'unsigned long &') for 1st argument

Looks like std::uint64_t and Poco::UInt64 are incompatible on that platform. You could change the type of m_sessoin_id to Poco::UInt64 or provide a specialization of uint64_t for VarHolder.
This might be a bug in POCO, because the doc says "Provided are specializations for all C++ built-in types" but long long and unsigned long long are appearently missing on mac.

Seems this bug: https://github.com/pocoproject/poco/issues/800 , changing all of uint64_t to Poco::UInt64 in the header and cpp files seems to compile.  Do you think that should be a PR?

Would be great, thanks. Maybe alias it as "WampId" to prevent association with Poco?
One issue is that as a library user you still might want to read your values as std::uint64_t. Even the first example in the readme does that.

Please update version in Homebrew

@k06a That's not by me or anyone I know.

Solved all similar issues by using Poco::UInt64 instead of uint64_t and unsigned long long. More info here: https://github.com/pocoproject/poco/issues/800#issuecomment-213272550


Failed to lint Untitled JavaScript file.

I just created a new Untitled file, and add some js code, then changed language mode to javascript, and got this in OUTPUT panel:
[Info  - 2:28:55 PM] ESLint server is running.
[Info  - 2:28:56 PM] ESLint library loaded from: /Users/sam/Documents/tmp/test-standard-js/node_modules/eslint/lib/api.js
(node:59569) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Request workspace/configuration failed with message: Cannot read property 'name' of undefined
(node:59569) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:59569) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): Error: Request workspace/configuration failed with message: Cannot read property 'name' of undefined

The problem is at https://github.com/Microsoft/vscode-eslint/blob/master/client/src/extension.ts#L527, since the workspaceFolder value of Untitled is undefined.
I just don't know how to fix it with the latest code.

Published 1.3.1


rpc task enters loop if nameko shell is killed

When running a service that has rpc methods we sometimes run into an issue where if an rpc endpoint A is called from a caller shell B and the caller shell is killed, A continues to run, and then just runs again when it finishes.
I'm assuming that the restarting happens when the task is through and the message acknowledgement fails, it's placed back in the queue and is picked up again.  But there is now real way to stop this other than to kill the service that provides A manually delete the problematic message from the rpc queue and then restart As service.
Is this a common issue?  If it's new I can try to dig into it to see if I can build a script to reproduce this reliably since it happens kind of intermittently at the moment.

This isn't something I've experienced or heard about before.
The health of the caller shouldn't have any impact on the callee. The message ack happens between the consumer in the callee service and the RabbitMQ broker. Even if the RPC reply queue has been removed (which it will sometime after the shell's proxy disconnects), the reply message would still be published, just discarded by the exchange. Unless you have requested mandatory delivery of RPC replies, this would not raise an error.
If you can reproduce with a script I would be interested in seeing it. The behaviour you're describing is consistent with the consumer losing connection with the RabbitMQ broker before ack'ing the RPC request message. I bet that actually is what's happening, but it's not directly related to the shell being killed.

Thanks for the answer, I think you're right that it must be the consumer losing connection.  I'm still trying to figure out why it loses the connection but can apparently still consume the message a second time.
So the timeline is something like:

RPC consumer receives the message and starts processing
Finishes the processing and tries to ack (or at least reaches the handle_result method)
Ack fails because of a disconnect
Start from the top again

I perhaps should note that I've set max_workers to 1.

The problem seems to be the same as here: https://groups.google.com/forum/#!topic/nameko-dev/A2M9YQgkM5s


fix: remove initial delay to speed up requests

The previous wait-on function has a param: initial delay = 1000, which caused the waiting time of a request to a dev server to at least 1000ms. This PR remove the param, which will be 0 by default.

Testing results can be seen here: https://github.com/Azure/static-web-apps-cli/pull/758#issuecomment-1787950192


Some capital letters disappear when printing to PDF

Reported on reddit: HERE
Brew example: https://homebrewery.naturalcrit.com/share/BkHW5PWY74
When I'm trying to print it to PDF using Chrome and Foxit Reader PDF Printer I see the following:

While the original brew looks like:

This is a Google Chrome issue. I didn't have this problem yesterday (Version 71.0.3578.98 (Official Build) (64-bit)) and just updated my chrome (Version 72.0.3626.81 (Official Build) (64-bit)) and now I have it too.

I have this issue too. Is it affecting all users or just some?
Is there any work around for this? I've spent months creating a large brew and I'd be gutted to see it go to waste.

@NathanMainwaring You can download Chromium version 71 and life goes on. Your brew isn't going to be wasted really, it is a browser problem. Homebrewery is fine on version 71 and below.

Just updated my Chrome here. So weird... It only happens on particular letters and custom fonts it looks like.
The issue also exists on GMBinder, so it's definitely not just us.
Someone else reported this on Chrome's bug reporting.

Does anyone have a safe link for downloading Chrome v71?

According to the report here, the fix has already been applied to Chrome Canary which you can download. It sounds like they are planning to apply this fix to Chrome soon as well.

This issue seems to be fixed? Can't find any vanishing letters on Version 72.0.3626.121 (Official Build) (64-bit) of chrome...

Yep. This is fixed.


Trigger Genesis According To Time

PR Description

Looks good generally.  Main thing is to replace the switch statements for comparison to handle any negative or positive values as a result from compare.


Memory Dump for very large RDB files (> 30 GBs) is Slow

For very large RDB, the memory dump can take upwards of 30 minutes.   Even slower, the "key" feature requires a sequential scan over the whole file.
Finally trying to further introspect a data structure like a hash, list, set to find out which field is taking up the most memory.   In my case I use celery as worker queue, and some tasks can be gigantic.
So I've made some enhancements such as the following
i) Reduce time to about 5 minutes to dump in quick mode
ii) Allow re-seeking for key contents in seconds, and limit mode
iii) Allow for verbose dumping of hash/list/set to file structure

Have you been able to improve it ? Would it be possible to realease it ?
As for huge DB (about 50Go / 1 Millions keys) on very faster server it takes like half a day as it's monothread.
Thanks,
Alex

I hadn't looked at this in a few years, seems like this project went stale.  The pull request I put up does work in quick mode like this if you want to give it a try

Generate a quick memory dump and index. In quick mode, only compressed_size is valid.
rdb.py -c memory -q --file redis_memory_quick.csv redis.rdb

After viewing, dump a hash/list to view contents of a offending key
rdb.py -c memory --max 1 --pos<PHONE_NUMBER> -v --key mongow --file redis_memory_mongow.csv redis.rdb

I'd be willing to fix this up if someone finds use for it, or fork the repo.


fix sbt scraper

Update version matcher to match the new sbt website version.

:tada:

You can verify this works by running ./java_helper sbt it should return:
ubuntu@levdev:~/circleci-images/openjdk$ ./java_helper sbt
0.13.16


Adds PR 511 and 537 to MTV 2.5

Adds content of https://github.com/kubev2v/forklift-documentation/pull/511, https://github.com/kubev2v/forklift-documentation/pull/536 and (intended) content of https://github.com/kubev2v/forklift-documentation/pull/537  to MTV branch 2.5.
Previews:

https://file.corp.redhat.com/rhoch/fixes_25/html-single/#vmware-prerequisites_mtv [Several rpows added to table 2.4]

https://file.corp.redhat.com/rhoch/fixes_25/html-single/#adding-source-providers [Section <IP_ADDRESS> added, including the NFC note]

https://file.corp.redhat.com/rhoch/fixes_25/html-single/#migrating-virtual-machines-cli_mtv [note after step 3]

@anarnold97 Please review. if good, please add to MTV 5.5. Thanks.


rename ExtendedMul functions to a unified unsafe_mul! interface

I opened the PR as a draft because one test does not pass yet, the QuasiUpperTriangular one.
Everything else works delightfully.
originating from the kron_mul_elem! call in runtests.jl:273, it errors when it gets from the second (abbreviated) A*B' method, to the full one, to the BLAS Ccall with the following:
ERROR: conversion to pointer not defined for QuasiUpperTriangular{Float64, Matrix{Float64}}
  Stacktrace:
    [1] error(s::String)
      @ Base .\error.jl:33
    [2] unsafe_convert(#unused#::Type{Ptr{Float64}}, a::QuasiUpperTriangular{Float64, Matrix{Float64}})
      @ Base .\pointer.jl:67
    [3] unsafe_convert(#unused#::Type{Ptr{Float64}}, A::Adjoint{Float64, QuasiUpperTriangular{Float64, Matrix{Float64}}})
      @ LinearAlgebra C:\Users\elom\AppData\Local\Programs\Julia-1.7.2\share\julia\stdlib\v1.7\LinearAlgebra\src\adjtrans.jl:197
    [4] pointer
      @ .\abstractarray.jl:1167 [inlined]
    [5] unsafe_convert(P::Type{Ptr{Float64}}, b::Base.RefArray{Float64, Adjoint{Float64, QuasiUpperTriangular{Float64, Matrix{Float64}}}, Nothing})
      @ Base .\refpointer.jl:119
    [6] _mul!(c::Vector{Float64}, offset_c::Int64, a::Vector{Float64}, offset_a::Int64, ma::Int64, na::Int64,
              b::Adjoint{Float64, QuasiUpperTriangular{Float64, Matrix{Float64}}}, offset_b::Int64, nb::Int64)
      @ KroneckerTools C:\Users\elom\.julia\dev\KroneckerTools\src\ExtendedMul.jl:75

I can confirm from a REPL:

YES! We need to do similar changes in QuasiUpperTriangular.jl, I had forgotten about it. We can't use the methods in ExtendedMul.jl for QuasiUpperTriangular.jl: we need specialized code.
To be consistent with the idea that direct multiplications with sub-arrays are only done in KroneckerProductTools.jl, we need to move and transform all the A_mul_B methods with offset... and so on from QuasiUpperTriangular.jl to ExtendedMul.jl.
Then, change the names A_mul_B to mul! for the remaining methods (without offset... and so on) in QuasiUpperTriangular.jl
In QuasiUpperTriangular.jl, we also use alpha and beta (that are always 1.0 and 0.0 in ExtendedMul.jl). This makes me think that we should add methods for alpha and beta in ExtendedMul.jl

We can't use the methods in ExtendedMul.jl for QuasiUpperTriangular.jl: we need specialized code.

Turns out we can! QuasiTriangular just was not implementing the necessary interface to be compatible with BLAS operations.
Once I defined the functions in DynareJulia/QuasiTriangular.jl#1, all the tests passed flawlessly without needing any of the A_mul_B functions from QuasiTriangular. Of course we can still port them as appropriate becase they might have a more specialized or efficient algorithm, but now the generic _mul!/Ccall OpenBLAS and LinearAlgebra.BLAS work as they should.
ie. The DynareJulia/QuasiTriangular.jl/#1 PR should make this current PR ready to merge and makes our job with QuasiTriangular much easier.
source: https://docs.julialang.org/en/v1/manual/interfaces/#man-interface-strided-arrays
more context:

https://docs.julialang.org/en/v1/base/arrays/#Base.StridedArray
https://discourse.julialang.org/t/more-specific-definition-for-densearray/33591/6
https://discourse.julialang.org/t/more-specific-definition-for-densearray/33591/11

This is because the tests in test_quasi_upper_triangular.jl only use matrices whose storage (X.data) is quasi upper triangular as they are created by a Schur decomposition. In the tests we should use matrices that have garbage in their lower triangular but not contiguous nonzero on the first sub-diagonal

I've added tests for a few branches and deleted the corresponding #FIXME: UNTESTED labels.
I was not able to quickly construct valid tests for a_mul_b_kron_c! and at_mul_b_kron_c! though.

I added the missing test cases for a_mul_b_kron_c!


Translation to Croatian (without changing layout)

Previous translation modified js/chapters/J_Sandbox.js to make space for translated text. I've since managed to squeeze it into available space.

tnx @ncase ! how 'bout publishing the new version on https://ncase.me/crowds/ ? ;)


Added Arch - GoACME.lego 4.15.0

Added missing arm arch source (arm7/32bit)

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Hi @BiosPlus,
The package didn't pass a Defender or similar security scan. This might be a false positive and we can rescan tomorrow.
(Automated response - build 720.)

Automatic Validation ended with:

Installation failed with exit code -1978335187 2024-02-08 22:16:21.037 [FAIL] Installer failed security check. Url: https://github.com/go-acme/lego/releases/download/v4.15.0/lego_v4.15.0_windows_amd64.zip Result: 0x80004005

(Automated response - build 720.)

The same URL literally passed 24 hours ago 😅

/AzurePipelines run


(SSG) astro-embed-integration should inject itself only when MDX has embeds

Currently if I use astro-embed-integration in astro.config.mjs it will inject itself (CSS and JS) post compiling to every MDX file, even if there aren't any embeds in the MDX.
I propose to check for every file which would got embeds and inject proper astro-embed plugin for each of them

any ideas as how to do it? maybe it should be implemented in auto-import  then pass the path/files list from here?
also, couldn't this be opt-in?


Create guide for Dataproc operators

It is not necessary. Let's do it later.

https://issues.apache.org/jira/browse/AIRFLOW-6293?jql=project %3D AIRFLOW AND component %3D documentation


refactor: externalise compiler

Shifts all compiler components to PlaceOS/compiler, which is a pruned fork of this repo.
See #2

Next steps from here will be to separate the test-harness and the drivers themselves, but suggest we take this one step at a time to minimise chaos.


Fail to run poetry run generate in Windows

Describe the issue:
Running poetry run generate reports an error, the following error message appears:

Repro Steps:

Run azd init --template llama-index-python.
Run azd auth login.
Runcd backend
python3 -m venv venv
source venv/bin/activate
poetry install

Run azd up.
Run azd env get-values > .env.
Run poetry run generate.

Environment:

Azd version: azd version 1.9.5 (commit cd2b7af9995d358aab33c782614f801ac1997dde)
OS: Windows

Expected behavior:
Running poetry run generate successfully.
@jongio and @marlenezw for notification.

hi, is this issue resolved? I also have this issue.
Error message : ModuleNotFoundError: No module named 'llama_index.core.storage'


added variance

Codecov Report

Merging #337 into master will decrease coverage by 20.95%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #337       +/-   ##
=========================================
- Coverage   24.15%   3.2%   -20.96%
=========================================
  Files          72     52       -20
  Lines        1718   1092      -626
  Branches      285    182      -103
=========================================
- Hits          415     35      -380
+ Misses       1217   1056      -161
+ Partials       86      1       -85

Impacted Files
Coverage Δ

atcoder-problems-backend/src/sql/streak.rs

atcoder-problems-backend/src/server/utils.rs

atcoder-problems-backend/src/sql/models.rs

...tcoder-problems-backend/src/sql/rated_point_sum.rs

...er-problems-backend/src/server/time_submissions.rs

atcoder-problems-backend/src/crawler.rs

atcoder-problems-backend/src/sql/problem_info.rs

...tcoder-problems-backend/src/sql/contest_problem.rs

atcoder-problems-backend/src/sql.rs

...er-problems-backend/src/server/user_submissions.rs

... and 10 more

Continue to review full report at Codecov.

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

これって #336 のやつですよね？

そうです。


Request detail: Action buttons

The following buttons should be added to the request details page.

[ ] Cancel button. It should allow the creator of the request to cancel it's request (so it should be available for the user that created the requests).
[ ] Decline button. It should allow the receiver of the request to reject it, opening a modal to indicate in a comment why the request was declined.
[ ] Accept/publish button. It should vary between "accept" or "accept and publish", the second one should appear if a record was published on accept, while the first, in the rest of cases-

Each of the buttons should, upon interaction, call to the associated command of the relevant request.

closed by https://github.com/inveniosoftware/invenio-requests/pull/126


Plot Merge Beta

Introduction
Introducing Plot Merge Beta
Relevant issues

#59
Changes
API changes

Merge API has been added. New fields exist to differentiate between merged checks versus normal checks.
Behavioral changes

Untested
Backwards compatibility

Not Yet Verified
Follow-up

Tests

N/A

Any News ? :(

@jasonwynn10 A big thanks 💘

👍


numba's njit 350x slower than regular Python for random list access

Reporting a bug

[ x] I have tried using the latest released version of Numba (most recent is
visible in the release notes
(https://numba.readthedocs.io/en/stable/release-notes-overview.html) --- I am using 0.59.1
[ x] I have included a self contained code sample to reproduce the problem.
i.e. it's possible to run as 'python bug.py'.

Random list access is 350x faster with regular Python than with njit. This can be somewhat alleviated by using numba's List type, but first, this probably means usage of Python's list should not be allowed in no_python mode if it makes numba so slow, and second, even with List numba is 5x slower than regular Python.
The MWE below reproduces the numbers claimed above. Note that in my real problem the list entries are not as trivial, so I can't just use arrays without lists in my real problem.
from numba import njit
from numba.typed import List
import timeit

def foo(n):
    return [(np.zeros(0), np.zeros(0))] * n

@njit
def typed_numba_foo(n):
    return List([(np.zeros(0), np.zeros(0))] * n)

def bar(a, b):
    for idx in b:
        _ = a[idx]  # the slow bit
    return None

natural_numba_foo = njit(foo)
numba_bar = njit(bar)

def call(method):
    if method == 0:
        numba_bar(natural_numba_foo(n), indices)
    elif method == 1:
        numba_bar(typed_numba_foo(n), indices)
    else:
        bar(foo(n), indices)

n = 100_000
indices = np.random.randint(0, n, n)
repeats = 10

for method, arg in [('Natural njit', 0), ('Typed njit', 1), ('Regular Python', 2)]:
    call(arg) # compile
    start = timeit.default_timer()
    for i in range(repeats):
        call(arg)
    print(method, "took", timeit.default_timer() - start, "s")

Natural njit took 66.35497103600028 s
Typed njit took 0.977979459999915 s
Regular Python took 0.1892970940007217 s

Thanks for the report. I think there may be some issues present with what is being recorded and that is what is leading to the timings reported. For instance...
numba_bar(natural_numba_foo(n), indices)

is doing something like:
tmp_lists = natural_numba_foo(n)
numba_bar(tmp_lists, indices)

and this matters to Numba because Numba stores lists in a different format to CPython. The "natural" list (as described) is what Numba stores internally as "reflected list", to go from reflected lists back to Python lists requires a "boxing" step where the data in the list is translated from Numba's format to CPython's format. This process is quite costly and in creating that temporary variable the lists have to be translated from Numba format into Python format and then from Python format back into Numba format again so they can be used in the bar function.
It may be a more representative test if the lists were allocated "outside" of the timed region, OR, built inside the compiled code. Typed lists don't suffer from this problem so much as their Numba representation is carried into their CPython representation, however, this means access from the interpreter pays the performance price for doing the data format translation.
If the above were fixed up, I would anticipate that the list access speed would be much closer and potentially even faster that what can be obtained through the Python interpreter.
Also, as a general word of warning... benchmarking functions that do very little work and then return something that has no dependency on the "work" being benchmarked can result in surprising performance results when compiled... the compiler might elect to optimise the work out as it has no impact on the returned value!
Hope this helps!

Hi @stuartarchibald

the benchmarks I provided here are very representative of the real code I'm running. It's a MWE of a real problem.
the time is spent in the call of numba_bar (reading the list), not numba_foo (allocating the list). I can prove that with more benchmarks if you're interested.
if passing an object created by a numba function  straight back into another numba function is this slow, that's a problem, no? It means that numba can't be used beyond single independent functions. If I understand your message correctly to say that natural_numba_foo returns a built-in Python list, and reading that back into another numba function is slow, then I think it should just not return built-in Python lists from no-object mode (or refuse to compile in no-object mode when built-in Python kept syntax is being used and attempted to be returned).
Even if we ignore the issues with the built-in Python lists being passed around between numba functions, is there any fix to the numba-List being that slow? Is there an explanation why it is so slow?

Here are more benchmarks proving that

The "natural" numba solution spends most time in the call of numba_bar (which accesses the list). Whether that's in actual function or in an automated conversion of the inputs, I can't tell. I'd be interested to know how to benchmark this!
The "typed" numba solution is surprisingly slow at even the typed_numba_foo (which creates the list) call. I don't know why; it outputs a numba.typed.typedlist.List and should therefore not have to do any conversions? Even the numba_bar (which accesses the list) call is still slower than the regular Python solution for small n.
Combining allocation and reading in a single numba function is still slower than regular Python when using numba.typed.List.
Combining allocation and reading in a single numba function is fastest when using regular Python list syntax within numba.

Results for n=100_000:
Natural njit -foo took 1.1867223369990825 s
Natural njit -bar took 18.94784771400009 s
Typed njit -foo took 0.15264834299887298 s
Typed njit -bar took 0.14661180000257445 s
Regular Python -foo took 0.0010774939983093645 s
Regular Python -bar took 0.07347720399775426 s
Natural combined -foo took 1.0312000085832551e-05 s
Natural combined -bar took 0.0423850199986191 s
Typed combined -foo took 1.2600998161360621e-05 s
Typed combined -bar took 0.2953695609976421 s

Results for n=10_000_000:
Natural njit -foo ---not tested----
Natural njit -bar took  ---not tested----
Typed njit -foo took 2.04352636099793 s
Typed njit -bar took 2.088136158999987 s
Regular Python -foo took 0.04432875400016201 s
Regular Python -bar took 2.4120894910010975 s
Natural combined -foo took 9.609000699128956e-06 s
Natural combined -bar took 0.8744130579980265 s
Typed combined -foo took 5.560999852605164e-06 s
Typed combined -bar took 4.209406034002313 s

from numba import njit
from numba.typed import List
import timeit

def foo(n):
    return [(np.zeros(0), np.zeros(0))] * n

@njit
def typed_numba_foo(n):
    return List([(np.zeros(0), np.zeros(0))] * n)

def bar(a, b):
    for idx in b:
        _ = a[idx]  # the slow bit
    return None

@njit
def natural_foo_bar(a, b):
    a = [(np.zeros(0), np.zeros(0))] * n
    for idx in b:
        _ = a[idx]  # the slow bit
    return None

@njit
def typed_foo_bar(n, b):
    a = List([(np.zeros(0), np.zeros(0))] * n)
    for idx in b:
        _ = a[idx]  # the slow bit
    return None

natural_numba_foo = njit(foo)
numba_bar = njit(bar)

def call_foo(method, n):
    if method == 0:
        return natural_numba_foo(n)
    elif method == 1:
        return typed_numba_foo(n)
    elif method == 2:
        return foo(n)
    elif method > 2:
        return n

def call_bar(method, foo_res_or_n, indices):
    if method == 0:
        numba_bar(foo_res_or_n, indices)
    elif method == 1:
        numba_bar(foo_res_or_n, indices)
    elif method == 2:
        bar(foo_res, indices)
    elif method == 3:
        natural_foo_bar(foo_res_or_n, indices)
    elif method == 4:
        typed_foo_bar(foo_res_or_n, indices)

n = 10_000_000
indices = np.random.randint(0, n, n)
repeats = 1

for method, arg in [
   # ('Natural njit', 0),
                    ('Typed njit', 1), ('Regular Python', 2), ('Natural combined', 3), ('Typed combined', 4)]:
    foo_res = call_foo(arg, n) # compile
    call_bar(arg, foo_res, indices) # compile
    start = timeit.default_timer()
    for i in range(repeats):
        foo_res = call_foo(arg, n)
    print(method, "-foo", "took", timeit.default_timer() - start, "s")
    start = timeit.default_timer()
    for i in range(repeats):
        call_bar(arg, foo_res, indices)
    print(method, "-bar", "took", timeit.default_timer() - start, "s")

To summarize:

numba.typed.List solutions are slower than regular Python. Whether the List is passed between allocator and consumer functions or used in a combined function doesn't make a big difference; the total is typically 2x-5x as slow as regular Python.
regular Python lists can't be passed around between numba functions (350x slowdown)
regular Python lists (or at least: the syntax for regular Python lists) used entirely within numba and not passed around provide by far the fastest solution.

@soerenwolfers thank you for asking about this. If you at the issue tracker, both Numba lists implementations(reflected-list and typed-list) may suffer performance inefficiencies depending on how they are used. I'm still in process of working out what is going on in your examples, but wanted to share a quick example to show a simpler use-case. Perhaps there is something to take-away from this.
Numba's typed list is useful and can be very quick, but your mileage may vary depending on use-case. I tried the following benchmark using a simple accumulator function over integers and got some very promising results:
In [1]: from numba import njit

In [2]: from numba.typed import List

In [3]: py_list = [i for i in range(100000)]

In [4]: numba_list = List(py_list)

In [5]: @njit
   ...: def accumulate(l):
   ...:     c = 0
   ...:     for i in l:
   ...:         c += i
   ...:     return c
   ...:

In [6]: %timeit accumulate.py_func(py_list) # python function with python list

1.91 ms ± 17.8 µs per loop (mean ± std. dev. of 7 runs, 1,000 loops each)

In [7]: %timeit accumulate.py_func(numba_list) # python function with numba typed list
78.8 ms ± 522 µs per loop (mean ± std. dev. of 7 runs, 1 loop each)

In [8]: %timeit accumulate(py_list) # numba function with numba reflected list
52.3 ms ± 210 µs per loop (mean ± std. dev. of 7 runs, 10 loops each)

In [9]: %timeit accumulate(numba_list) # numba function with numba typed list
16.6 µs ± 10.2 ns per loop (mean ± std. dev. of 7 runs, 100,000 loops each)

@soerenwolfers I re-did my benchmark again, such that the access is truely randomized (by handing in the indices )and not sequential and I get:
In [1]: from numba import njit

In [2]: from numba.typed import List

In [3]: n = 100000

In [4]: import numpy as np

In [5]: indices = np.random.randint(0, n, n)

In [6]: @njit
   ...: def accumulate(l, n):
   ...:     c = 0
   ...:     for i in n:
   ...:         c += l[i]
   ...:     return c
   ...:

In [7]: py_list = [i for i in range(n)]

In [8]: numba_list = List(py_list)

In [10]: %timeit accumulate.py_func(py_list, indices) # python function with python list
6.98 ms ± 360 µs per loop (mean ± std. dev. of 7 runs, 100 loops each)

In [11]: %timeit accumulate.py_func(numba_list, indices) # python function with numba typed list
83.3 ms ± 670 µs per loop (mean ± std. dev. of 7 runs, 10 loops each)

In [12]: %timeit accumulate(py_list, indices) # numba function with numba reflected list
52.1 ms ± 145 µs per loop (mean ± std. dev. of 7 runs, 10 loops each)

In [13]: %timeit accumulate(numba_list, indices) # numba function with numba typed list
1.12 ms ± 1.88 µs per loop (mean ± std. dev. of 7 runs, 1,000 loops each)

@esc I suspect your example might be different from mine because the list contains "value types" instead of "reference types", but that deoends in implementation details of numba that I'm not familiar with. In any case, I agree that once the list access becomes trivial compared to the work being done, numba will look good again, but I intentionally highlighted something that does cause real problems to me, which is that in the opposite case where the work is trivial and it's all about accessing non-trivial data, numba is slower than pure Python. (By lots in some cases and by a little in other cases, depending on how you use numba and what you use it on, but still)

Indeed. Numba isn't a silver bullet and the lists are known to have certain performance deficiencies, seem like you hit one of those. 😅 I doubt there will be a "workaround" for your use-case, unfortunately.

@soerenwolfers I thought about this some more, and the issue you are encountering are probably  related to so-called "reference counted" types (e.g. tuple of NumPy arrays), i.e. anything non primitive, like an int or a float. I went and dug out some pointers for you, in case you want to have a crack at improving the typed.List for your use-case:
High-level interface: https://github.com/numba/numba/blob/main/numba/typed/typedlist.py#L361-L369
Compiler code: https://github.com/numba/numba/blob/main/numba/typed/listobject.py#L689-L791
C-level backing: https://github.com/numba/numba/blob/main/numba/cext/listobject.c#L305-L323
Note that the reflected list is scheduled for deprecation, so it's probably not worth attempting to improve that.
I think there are quite a few people who would be happy if the typed list performance for more complex use-cases could be improved! 🙌
Hope this helps!

Closing because I stopped using numba and it doesn't seem this is prioritized by the dev team.

@soerenwolfers it seems like Numba isn't a good fit for your use-case at present. FWIW: I will continue to debug setitem/getitem -- we are discussing a number of potential performace improvements  with @DannyWeitekamp in this discourse thread: https://numba.discourse.group/t/performance-of-typed-list-outside-of-jit-functions/2560

I came to the same conclusion. I'm not using anything else either, I just am losing a bit of time running regular python instead of losing it on bending numba to do what it's apparently not targeted to do.

ref: https://github.com/numba/numba/issues/9374


Error in some command

i use HMSET, sometimes it is failed.
ERR Forbidden Command: multi_hset
ERR Forbidden Command: multi_hset
ERR Forbidden Command: multi_hset
ERR Forbidden Command: multi_hset
ERR Forbidden Command: multi_hset

@XiaoKa741 The error message was generated by your SDK, not Twemproxy. Can you provide more information, like the Redis/Twemproxy version, what's your client language?

go client(go-redis)，
i use HMSET, sometimes it is failed.
ERR Forbidden Command: multi_hset
ERR Forbidden Command: multi_hset
ERR Forbidden Command: multi_hset
ERR Forbidden Command: multi_hset
ERR Forbidden Command: multi_hset

sorry,it's my fault.i set db readonly by accident @git-hulk

@XiaoKa741 OK, I would close the issue later.


Governance: eligibility and end of tenure clarification

This PR makes minior changes to the governance document. It adds, for all roles:

an "eligibility" section, which explicitly states conditions on role eligibility
an "end of tenure" section, which describes how the tenure ends

In most cases, this has been already part of the respective sections, and just moved to a new section and/or explicitly clarified.

Just FYI, I should have said this before this was merged:
before, it said that "one of the CC members will have a tie breaking privilege", but it didn't say who that was.
I've changed it to the CC member with shortest tenure, that would be you, @aiwalter.
If this is contentious, we can unmerge and remove the change, but note that it wouldn't specify who exactly has the tie breaking privilege as of now.

The voting rule seemed reasonable to me


Deploy widget does not display deployment duration

The Request object has a capability to receive job duration, but the EnvironmentComponent does not allow or use the job duration in any way.
I would like this to be included in the deploy widget so deployment duration can be used as a visibility metric.

If I am understanding this correct, you would like to report from your deployment tool of choice , not just the environment and artifacts but how long the deployment process ran ?

I would like the existing duration field on DeployDataCreateRequest to be used by EnvironmentComponent.  If duration will not be used, the field should be removed from the request class.
My desire is that each of the components on the UI could show a deploy duration next to the deploy start time.  This would help to track modules that are taking longer to deploy or drift in the deploy duration.

Is that data readily available in the XLD and UDeploy API's?

@MarkRx in the XLD collector, this data would definitely be available.  It could be set using lines 7 and 12 of XLDeployApplicationHistoryItem, which is used to create the EnvironmentComponent.
I didn't see matching startDate fields for UDeploy.  I don't know the applications API, so I am not sure if this is available.

It is available in uDeploy. Let me verify again. Will keep posted.


Workload : Pondération

This issue follows a discussion with M.Mendes Reis about the weekly workload indicator that needs to be present in the monthly view (important for the final Caravel release).
A ponderation should take place to ensure that a number of little works are considered as much workload as one big report (ex : 3 little homework might not be as challenging as making the final web dev delivery, P3 project, etc...)
Some solutions have been mentionned :

Adding an "estimated workload" in hours (ex: Webdev should be 3*30h so 90h) to ponderate the workload by the estimated time of the project. This could be heavily skewed (profesors tend to underestimate, students could try to cheat the system by overestimating everything)
Ponderating by the branch credits - dangerous, as the credits are not a good indicator in the current cursus
Adding a way for the student to rate the workload of a particular project "on-the-fly"

This should be very easy to do for students (as a matter of user expenrience). An idea has been evoked : having a little "reaction" board, akin to Discord, composed of 3 emojis - happy, neutral, stressed. These emojis represent a way for the student to declare if this particular project has an heavy toll on the week, and the app could use it to help ponderate the weekly workload. This proposition is just an example of an implementation giving a voice to the students while not requiring management and logistic time.

p-s : Good luck for your bachelor, you are awesome :-)

Thanks for your input !
I agree with your arguments. I would add that we don't expect Caravel to give a precise value for the workload, I think it would be a good step forward if it could give a trend indicator.
What about using more than one of your solutions ?

branch credits shouldn't be so bad : 1 credit worth 30h and for most branches half of this time should be autonomous work
estimate the workload is a good exercise for the students for learning work time management. I think it's not a big problem if it's sometimes over or underrated : we will use it as an indicator, we don't expect an accurate value
imho, emojis should be more accurate : a student can be happy working on a projet even if he spends more time on it (as you did for Caravel), and be stressed by a less time consuming project, when its motivation is lower... What about more emojis ? and/or emojis more expressive about the time spent on the projet (over/equals/under prof's expectations)

I think it would be nice to have a link somewhere with the expected workload in the module description : it's the only objective/official reference we can use as an argument in a discussion.
I agree 100% with @M4n0x when he says Caravel can't give a precise value, but only a trend that should trigger a discussion between students and profs. But I think 3 general emojis is a little poor.
Of course, any feedback should be facultative, at the good will of the students. I trust most of the students, and I think "cheating" in overestimate workload shouldn't be a big problem, as these values are only meant to trigger a discussion.

In my opinion the most common situations should require the least effort from the user (less is more). So when a situation is normal asking students to make inputs as estimating workload seems overkill to me : first of all because it's really hard to estimate as we are learning and most of the time it's new stuff and secondly because we are all differents, for some people it could take one hour while for some others it could take four. The other point is the fact that we have a lot of homework, if every student (if we want an average score) should estimate each homework it could take a lot of time. I would be ok with that if the indicator was very precise and the most usefull thing in the app but for what it takes and what we get I really think that's not worth it.
As we have discussed previously, I think reactions is much relevant as an input when there is a problem, it requires less effort from the user and it really brings value to the information. Defining which reactions we should get is another topic (in which we need to dig a little 😄), I agree with the fact that only three reactions seems not enough. Maybe it will be a good idea to do a survey to get the most common problems students encounter in homework/project and adapt reactions from that view.
Regarding to the ECTS, I think it's also a good idea, each subject could have a new parameter ECTS. As we know the numbers of ECTS for each subject it'll be easy to create an indicator to show if a week seems overload or not. It requires almost no effort at all and can be very usefull to objectively balance workload.


illustration for the theory of partition

if we have some illustration to explain how partition works, it will be better.

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

ID: 9da32a62-a60f-1013-bb2f-688c67a446ec
Version Independent ID: 7a2bf261-0a20-30f0-837d-cf02700034aa
Content: Partitioning and horizontal scaling in Azure Cosmos DB
Content Source: articles/cosmos-db/partition-data.md
Service: cosmos-db
GitHub Login: @aliuy
Microsoft Alias: andrl

@keithcn Thank you very much for your feedback. Do you have any additional details as to what you feel would be a solid addition to the documentation? I am assigning this to the content owner to evaluate and update as appropriate but, you additional feedback is very helpful.
Thank you,
Mike

After reading the content, actually I didn’t get what’s the working model based on physical and logical partition, and behind the scenes, if we have any illustration (a picture to explain the workflow), it will be much better to understand.
发送自 Windows 10 版邮件https://go.microsoft.com/fwlink/?LinkId=550986应用

发件人: Mike Ubezzi<EMAIL_ADDRESS>发送时间: Tuesday, October 30, 2018 12:34:33 AM
收件人: MicrosoftDocs/azure-docs
抄送: Keith; Mention
主题: Re: [MicrosoftDocs/azure-docs] illustration for the theory of partition (#17801)
@keithcnhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkeithcn&data=02|01||d99099b22a504518895708d63dbc733c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636764276919324687&sdata=Y%2BhKHAKMsX7e3RY4lnid%2B8TnwDjWAqpGi4VRnwJXOSg%3D&reserved=0 Thank you very much for your feedback. Do you have any additional details as to what you feel would be a solid addition to the documentation? I am assigning this to the content owner to evaluate and update as appropriate but, you additional feedback is very helpful.
Thank you,
Mike
―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F17801%23issuecomment-433979558&data=02|01||d99099b22a504518895708d63dbc733c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636764276919324687&sdata=ho%2Blmr59IAQQRTrBMzhBjghtiu91dyqtJadzgx4aAYA%3D&reserved=0, or mute the threadhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPxbdVM2us6h_iXkHs-tV9u7_qt3swv1ks5upy4ZgaJpZM4X-iCy&data=02|01||d99099b22a504518895708d63dbc733c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636764276919324687&sdata=eOmnHustS0%2BSSSxtdnEP32YsfFcNCbo3EK8MawNfAiU%3D&reserved=0.

@keithcn thanks for the feedback, we are making some updates to the partitioning docs in the next couple of weeks and adding an illustration is in our plan. Here is a short description to clarify the partitioning details, we will have this information in the docs:
Logical partition: By using partitioning, the items in a container are divided into distinct subsets, called logical partitions, based on the value of a partition key property that is present in each item. A logical partition is, therefore, a distinct subset of items in a container.
Physical partition: Cosmos DB transparently and automatically manages the placement of logical partitions onto physical partitions (server infrastructure) to efficiently satisfy the scalability and performance needs of the container.
For example, consider a container that holds documents, each of which has a UserID property.  If UserID serves as the partition key for items in that container, and there are 1000 unique UserIDs, then there are 1000 logical partitions in the container. The 1000 logical partitions might be initially placed by Cosmos DB onto 10 servers/physical partitions.  As throughput and storage requirements of the application increase, Cosmos DB can move these logical partitions around and automatically spread the load across a greater number of servers.

@keithcn we will now close this issue. If you have further questions feel free to reopen.
#please-close


"Try Lisp In Your Browser" Doesn't work.

I cannot proceed past level 1: "Let's do a little math"
I click "Next" but nothing happens. I entered in every line and then clicked "Next"

it does for me now


Allow direct image upload in chat

This is a long time coming. Just try to copy it upload the image to https://img.doerig.dev/ and then paste the link or something.


(GH-1296) Added YAML parsing error details to the bolt logging

Closes #1296
TODO

[ ] Tests

(<unknown>): did not find expected node content while parsing a flow node at line 4 column 4
Some of these errors are really cryptic. I wonder if we're better off using the err.column and err.line only.

Testing out the IO errors for an inventory file with bad owner / read permissions results in:
Could not read inventory file: /home/nmaludy/storage/home/src/git/nmaludy/bolt/bolt/workshop/inventory.yaml
error: Permission denied @ rb_sysopen - /home/nmaludy/storage/home/src/git/nmaludy/bolt/bolt/workshop/inventory.yaml

Parsing an inventory with the following in it:
---
version: 2
config:
  transport: winrm
    ssl-verify: false
    ssl: true

results in the following error:
Could not parse inventory file: /home/nmaludy/storage/home/src/git/nmaludy/bolt/bolt/workshop/inventory.yaml
error: (<unknown>): mapping values are not allowed in this context at line 5 column 15

CLA signed by all contributors.

Cool, i think this is good to go then (as long as the CI passes)


RefinementList: ease customization with labelComponent

Do you want to request a feature or report a bug?
Feature.
What is the current behavior?
Often times, you just want to change the way the items are displayed in a RefinementList (with more than just CSS). For that, the only option so far is to use the connectRefinementList connector and rebuild the refinement list yourself.
It turns out that handling the logic around isRefined, createURL and refine is not that trivial and I was wondering whether we couldn't introduce a labelComponent which would be responsible of rendering the label based on the item.
Something like:
function MyFacetValueLabel({item}) {
  return <img src={'https://....../' + item.value + '.jpg'} />;
 // maybe if we return `false` here, we could even avoid rendering the value
}

<RefinementList attributeName="category" labelComponent={MyFacetValueLabel} />

Yes the API goal was that we did not wanted to provide such feature and rather guide through using connectRefinementList instead.
If you need to customize the rendering => use connectors was our moto since the begining.
What was your use case for being able to customize the refinementList rendering per item?
What was the struggle in using the connectRefinementList part? Today we do not feel that using connectors is complex so if it is then we will need more information on why it's hard to take a decision.
It's a tricky decision to make because then you have an API where you say "if you want you can configure the rendering a bit, but if you want to go further, use a connector" versus "if you want to configure the rendering, use a connector".
Adding more option gives the user the impression that he can be in control while he will have only some control with an option like labelComponent.

What was the struggle in using the connectRefinementList part? Today we do not feel that using connectors is complex so if it is then we will need more information on why it's hard to take a decision.

It's not really struggling; it's just that if you don't know how the createURL() works or just if you don't want/need to deeply understand how item.isRefined and refine() should be used; it's really not easy to change the label. You end up copy/pasting the RefinementList component code (and may discover how those things are working).

It's a tricky decision to make because then you have an API where you say "if you want you can configure the rendering a bit, but if you want to go further, use a connector" versus "if you want to configure the rendering, use a connector".

I think it really looks like the itemComponent for the Hits. For some widgets, it really makes sense to ease the customization without needing to go for the connectors + DYI. The labelComponent for RefinementList (and Menu) is the only one I was thinking about so far -> it's really not something I will propose for every single widget.

Adding more option gives the user the impression that he can be in control while he will have only some control with an option like labelComponent.

Yes, it's a balance we need to find.

We do want people to have to use connectors as soon as they hit a DOM rendering feature wall. We do not want them to think that custom DOM rendering features are spread amongst many features (choosing the right path then being hard to do).
If we identify clear common use cases where the need for a hit/label component is really beneficial then we will need to revisit this issue.
Also we recently introduced "transformItems" props on widget which can make it easier to inject some data/rephrase some labels (without touching the DOM).
https://community.algolia.com/instantsearch.js/react/guide/Sorting_and_filtering.html

Also we recently introduced "transformItems" props on widget which can make it easier to inject some data/rephrase some labels (without touching the DOM).

Works for me 👍


Add a Custom error case for DecodeError

This is to help users with error messaging that doesn't really fit into a type mismatch or missing key. See #211.

Looks good to me.
Not that I can think of a use for it right now, but I think this would also make materialize possible if someone really wanted it (I explained in #225 how I couldn't make the catch exhaustive).

Seems like there should be a Custom equivalent of .typeMismatch, no? .custom or .customError should work.

@jshier I passed on the helper function because it's just a custom String that the user generates. So you can use .Custom("") to make it. If you think a .custom(String) helper function would be helpful then I could add it. I could also be convinced to have it for consistency and completeness :)

I like .typeMismatch because it's slightly easier and more elegant to call rather than .Failure(.TypeMismatch(expect:"", actual:"")). While .Failure(.Custom("String")) isn't quite as bad, I do think .custom("String") is a bit better. And yes, it would feel a bit odd to have convenience functions for the other error states but not Custom.

Ah right, forgot about .Failure needing to wrap that ... ok adding ... brb

Figured .customError was a bit more explicit of what it was doing than just a function named custom on the Decoded type.

Thanks, that looks great.

:+1: from me

This looks great. I was just about to raise an issue asking if anyone else had ever needed this :)
(although I was going to suggest using .InvalidData, but .Custom gives ultimate flexibility)

@tonyd256 am I going mad, or did this merge get lost somehow? The timeline above says that 038f72a was merged into master, but https://github.com/thoughtbot/Argo/blob/master/Argo/Types/DecodeError.swift definitely doesn't contain it.

Commit history for master doesn't show it either.

I have a project that checked it out as a submodule (see screenshot below), but unfortunately my Cartfile specifically referenced the commit hash, not the branch, so I can't tell if it ever made it to master.

I... don't know!? Surely not on purpose. I suppose it's possible that I did it on accident, but how would I even know? I don't know. Maybe you merged this roughly the same time that I rebased and merged my documentation changes? Maybe I did a force-push from exactly the wrong feature branch at exactly the wrong time?

Weird. I definitely didn't force-push master, no idea where this would have gone.

Actually, I don't have that commit locally. No idea what's going on here. If anyone does have that commit locally and they want to cherry-pick it into master then open a PR I'd be eternally grateful.

I have the commit locally on my personal Mac. I'll have to do it tonight when I get home.

@tonyd256 just in case they've been lost on your local machine, I've created a gist that contains two patches - one for each lost commit.
https://gist.github.com/edwardaux/93e3108ae0dc43c1c3e7

@paulyoung @edwardaux Fixed now!

@tonyd256 did you need to force push to master to fix this?

yes ... rebases on open PRs will be harry ... but once they're done we'll be good to go.

Thanks @tonyd256. Works like a champ!


#159848844 Update README and implement the docs page

What does this PR do?
This PR creates the home page for the docs and updates readme file
How should this be manually tested?

Clone the repo

$ git clone https://github.com/asheuh/StackOverflow-lite
$ cd StackOverflow-lite

Create virtualenv

$ python -m venv venv

Run app

$ flask run

Then go to <IP_ADDRESS>:5000

What are the relevant pivotal tracker stories?
159848844

Pull Request Test Coverage Report for Build 156

5 of 6 (83.33%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.05%) to 94.475%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

stackoverflow/base/routes.py
3
4
75.0%

Totals

Change from base Build 154:
-0.05%

Covered Lines:
1214

Relevant Lines:
1285

💛  - Coveralls