[Suggestion] Consider to remove height in button

https://github.com/claviska/shoelace-css/blob/master/source/css/buttons.css#L14
So it plays well with other properties like font-size or padding?

The --input-height and input-height-* properties ensure that buttons remain the same height as form controls. Otherwise, simple changes such as font size can throw things out of whack.
Setting an explicit height on buttons/inputs wasn't my first approach, but it seems to be the only way to get truly consistent results on all browsers while still allowing users to customize fonts for buttons and inputs.


bug: crashes nvim (exit status 134) when trying to animate terminals

Did you check docs and existing issues?

[X] I have read all the edgy.nvim docs
[X] I have searched the existing issues of edgy.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
v0.10.0-dev+492-gb6d2f49b4
Operating system/version
Fedora release 39 (Rawhide)
Describe the bug
nvim will crash if the plugin attempts to animate the resize of terminals. it's a bit tough for me to isolate the exact steps to repro tho, sometimes it won't animate but sometimes it does
Steps To Reproduce

<C-/> 2<C-/> 3<C-/>
See crash

Expected Behavior
Either not doing the animation or without crashing nvim.
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  {
    "folke/edgy.nvim",
    opts = {
      bottom = {
        {
          ft = "toggleterm",
          size = { height = 0.4 },
          filter = function(buf, win)
            return vim.api.nvim_win_get_config(win).relative == ""
          end,
        },
      }
    }
  },
  {
    "akinsho/toggleterm.nvim",
    config = function(_, opts)
      require("toggleterm").setup(opts)
    end,
    ---@type ToggleTermConfig
    opts = {
      open_mapping = "<c-/>",
      autochdir = true,
    },
    cmd = "ToggleTerm",
    ---@type LazyKeys{}
    keys = {
      "<c-/>",
    },
  },
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

I think I found the culprit.
Before nvim exits, it prints this shortly: screen_resize failed to update cursor position. After a quick grep shows the message comes from libvterm: https://github.com/neovim/deps/blob/master/src/libvterm/src/screen.c
If you interrupt the animation early? (see https://asciinema.org/a/fBTAzF6SwpvaxxAOaM4e9r9hA), it crashes.
I'm not very sure about the root cause.

Also, this does not happen when opts.animate.enabled is false.

This seems related: https://github.com/neovim/neovim/pull/21124

I don't get the crashes in my config, but I could indeed reproduce it with the repro and opening multiple terminals next to each other.

(gdb) where
#0  0x00007fdd9e35426c in ?? () from /usr/lib/libc.so.6
#1  0x00007fdd9e304a08 in raise () from /usr/lib/libc.so.6
#2  0x00007fdd9e2ed538 in abort () from /usr/lib/libc.so.6
#3  0x000056384bf3129b in resize_buffer (screen=0x56384eae1b80, bufidx=0, new_rows=22, new_cols=1, active=true, statefields=0x7ffc031a1380)
    at /__w/neovim/neovim/.deps/build/src/libvterm/src/screen.c:665
#4  0x000056384bf319d6 in resize (new_rows=22, new_cols=1, fields=0x7ffc031a1380, user=0x56384eae1b80) at /__w/neovim/neovim/.deps/build/src/libvterm/src/screen.c:763
#5  0x000056384bf38cd1 in on_resize (rows=22, cols=1, user=0x56384eaee480) at /__w/neovim/neovim/.deps/build/src/libvterm/src/state.c:1964
#6  0x000056384bf3a281 in vterm_set_size (vt=0x56384eaedd20, rows=22, cols=1) at /__w/neovim/neovim/.deps/build/src/libvterm/src/vterm.c:125
#7  0x000056384bebb0ed in terminal_check_size (term=0x56384eafa900) at ../src/nvim/terminal.c:407
#8  0x000056384bf0071f in win_set_inner_size (wp=0x56384eb7dcc0, valid_cursor=valid_cursor@entry=true) at ../src/nvim/window.c:6676
#9  0x000056384bf00862 in win_new_width (wp=, width=) at ../src/nvim/window.c:6702
#10 0x000056384beee373 in frame_new_width (topfrp=topfrp@entry=0x56384eab9420, width=width@entry=1, leftfirst=leftfirst@entry=false, wfw=wfw@entry=false) at ../src/nvim/window.c:3675
#11 0x000056384beeef88 in frame_setwidth (curfrp=0x56384eab9420, width=1) at ../src/nvim/window.c:6090
#12 0x000056384bef00ab in win_setwidth_win (width=, wp=0x56384eb7dcc0) at ../src/nvim/window.c:6004
#13 0x000056384bcd72d4 in nvim_win_set_width (window=, width=1, err=0x7ffc031a1530) at ../src/nvim/api/window.c:213
#14 0x000056384bca366a in nlua_api_nvim_win_set_width (lstate=0x7fdd9e5dd380) at src/nvim/auto/lua_api_c_bindings.generated.c:6183
#15 0x000056384bf904d6 in lj_BC_FUNCC ()
#16 0x000056384bf7ca72 in lua_pcall (L=L@entry=0x7fdd9e5dd380, nargs=nargs@entry=1, nresults=nresults@entry=1, errfunc=errfunc@entry=-3) at lj_api.c:1116
#17 0x000056384bdb94b3 in nlua_pcall (lstate=lstate@entry=0x7fdd9e5dd380, nargs=nargs@entry=1, nresults=nresults@entry=1) at ../src/nvim/lua/executor.c:164
#18 0x000056384bdbe23e in nlua_call_ref (ref=, name=, args=..., retval=, err=0x0) at ../src/nvim/lua/executor.c:1587
#19 0x000056384bcdb0e5 in call_autocmd_callback (ac=ac@entry=0x56384e9498f0, apc=apc@entry=0x7ffc031a1ea0) at ../src/nvim/autocmd.c:1999
#20 0x000056384bcdd212 in getnextac (c=, cookie=0x7ffc031a1ea0, indent=, do_concat=) at ../src/nvim/autocmd.c:2056
#21 0x000056384bd6c116 in do_cmdline (cmdline=, fgetline=0x56384bcdd088 , cookie=0x7ffc031a1ea0, flags=7) at ../src/nvim/ex_docmd.c:505
#22 0x000056384bcdbdd3 in apply_autocmds_group (event=EVENT_BUFWINENTER, fname=0x56384ebb7eb0 "term://~/projects/edgy.nvim//692285:/usr/bin/fish;#toggleterm#3", fname_io=,
    force=, group=group@entry=-3, buf=0x56384eb82eb0, eap=0x0, data=0x0) at ../src/nvim/autocmd.c:1787
#23 0x000056384bcdc4b7 in apply_autocmds (event=, fname=, fname_io=, force=, buf=) at ../src/nvim/autocmd.c:1460
#24 0x000056384bce3f4b in enter_buffer (buf=buf@entry=0x56384eb82eb0) at ../src/nvim/buffer.c:1671
#25 0x000056384bce43ad in set_curbuf (buf=buf@entry=0x56384eb82eb0, action=action@entry=0) at ../src/nvim/buffer.c:1594
#26 0x000056384bce452a in do_buffer (action=0, start=, dir=, count=, forceit=0) at ../src/nvim/buffer.c:1506
#27 0x000056384bcdf8e4 in goto_buffer (eap=0x7ffc031a21b0, start=1, dir=1, count=4) at ../src/nvim/buffer.c:935
#28 0x000056384bd7298c in ex_buffer (eap=0x7ffc031a21b0) at ../src/nvim/ex_docmd.c:4317
#29 0x000056384bd6a32a in execute_cmd0 (retv=retv@entry=0x7ffc031a21a4, eap=eap@entry=0x7ffc031a21b0, errormsg=errormsg@entry=0x7ffc031a21a8, preview=preview@entry=false)
    at ../src/nvim/ex_docmd.c:1634
#30 0x000056384bd6ba6b in do_one_cmd (cmdlinep=cmdlinep@entry=0x7ffc031a23f8, flags=flags@entry=7, cstack=cstack@entry=0x7ffc031a2480, fgetline=fgetline@entry=0x56384be6df4c ,
    cookie=cookie@entry=0x7ffc031a2b30) at ../src/nvim/ex_docmd.c:2293
#31 0x000056384bd6c66a in do_cmdline (cmdline=, fgetline=0x56384be6df4c , cookie=0x7ffc031a2b30, flags=7) at ../src/nvim/ex_docmd.c:592
#32 0x000056384be6e1d1 in source_using_linegetter (cookie=cookie@entry=0x7ffc031a2b30, fgetline=fgetline@entry=0x56384be6df4c , traceback_name=)
    at ../src/nvim/runtime.c:1898
#33 0x000056384be6e247 in do_source_str (cmd=, traceback_name=) at ../src/nvim/runtime.c:1947
#34 0x000056384bcd28d8 in exec_impl (channel_id=9223372036854775809, src=..., opts=opts@entry=0x7ffc031a2c40, err=err@entry=0x7ffc031a2c10) at ../src/nvim/api/vimscript.c:92
#35 0x000056384bcd2a06 in nvim_exec2 (channel_id=, src=..., opts=0x7ffc031a2c40, err=0x7ffc031a2c10) at ../src/nvim/api/vimscript.c:59
#36 0x000056384bca2211 in nlua_api_nvim_exec2 (lstate=0x7fdd9e5dd380) at src/nvim/auto/lua_api_c_bindings.generated.c:5576
#37 0x000056384bf904d6 in lj_BC_FUNCC ()
#38 0x000056384bf7ca72 in lua_pcall (L=L@entry=0x7fdd9e5dd380, nargs=nargs@entry=1, nresults=nresults@entry=0, errfunc=errfunc@entry=-3) at lj_api.c:1116
#39 0x000056384bdb94b3 in nlua_pcall (lstate=lstate@entry=0x7fdd9e5dd380, nargs=1, nresults=0) at ../src/nvim/lua/executor.c:164
#40 0x000056384bdc173e in nlua_do_ucmd (cmd=, eap=, preview=) at ../src/nvim/lua/executor.c:2239
#41 0x000056384beda68f in do_ucmd (eap=0x7ffc031a2fb0, preview=false) at ../src/nvim/usercmd.c:1642
#42 0x000056384bd6a452 in execute_cmd0 (retv=retv@entry=0x7ffc031a2fa4, eap=eap@entry=0x7ffc031a2fb0, errormsg=errormsg@entry=0x7ffc031a2fa8, preview=preview@entry=false)
    at ../src/nvim/ex_docmd.c:1626
#43 0x000056384bd6ba6b in do_one_cmd (cmdlinep=cmdlinep@entry=0x7ffc031a31f8, flags=flags@entry=3, cstack=cstack@entry=0x7ffc031a3280, fgetline=fgetline@entry=0x56384bd9bae5 ,
    cookie=cookie@entry=0x0) at ../src/nvim/ex_docmd.c:2293
#44 0x000056384bd6c66a in do_cmdline (cmdline=, fgetline=0x56384bd9bae5 , cookie=0x0, flags=3) at ../src/nvim/ex_docmd.c:592
#45 0x000056384bd2af2a in ex_execute (eap=0x7ffc031a38c0) at ../src/nvim/eval.c:7862
#46 0x000056384bd6a32a in execute_cmd0 (retv=retv@entry=0x7ffc031a38b4, eap=eap@entry=0x7ffc031a38c0, errormsg=errormsg@entry=0x7ffc031a38b8, preview=preview@entry=false)
    at ../src/nvim/ex_docmd.c:1634
#47 0x000056384bd6ba6b in do_one_cmd (cmdlinep=cmdlinep@entry=0x7ffc031a3b08, flags=flags@entry=0, cstack=cstack@entry=0x7ffc031a3b90, fgetline=fgetline@entry=0x56384bd9bae5 ,
    cookie=cookie@entry=0x0) at ../src/nvim/ex_docmd.c:2293
#48 0x000056384bd6c66a in do_cmdline (cmdline=, fgetline=0x56384bd9bae5 , cookie=0x0, flags=0) at ../src/nvim/ex_docmd.c:592
--Type  for more, q to quit, c to continue without paging--
#49 0x000056384be08f0f in nv_colon (cap=0x7ffc031a41c0) at ../src/nvim/normal.c:3244
#50 0x000056384be07e1d in normal_execute (state=0x7ffc031a4140, key=) at ../src/nvim/normal.c:1202
#51 0x000056384be9e28a in state_enter (s=0x7ffc031a4140) at ../src/nvim/state.c:99
#52 0x000056384be003b0 in normal_enter (cmdwin=, noexmode=) at ../src/nvim/normal.c:501
#53 0x000056384bc946a8 in main (argc=, argv=) at ../src/nvim/main.c:641
(gdb) stack

https://github.com/neovim/neovim/issues/23762


Revert "userdata: add tests for write_files in containers"

Reverts lf-edge/eden#918
Since there are failures on EVE master let's revert this test till we fix it
cc:  @europaul  @milan-zededa @giggsoff

@uncleDecart @giggsoff @milan-zededa can we include the test back since the supported EVE version was bumped up to 11.7.0, which includes the necessary EVE functionality?

@uncleDecart @giggsoff @milan-zededa can we include the test back since the supported EVE version was bumped up to 11.7.0, which includes the necessary EVE functionality?

Yes we can

@europaul here's the PR https://github.com/lf-edge/eden/pull/941


Write large strings

Hi, SqlKata is an awesome project, however I've been having a few issues with some update queries that appear to be related to the use of Dapper. Everything works fine until my string gets above 4000 characters. At this point, via both Sql Kata and Dapper, the query never reaches the Sql Server (I'm watching the profiler).
I can mitigate this in Dapper using DynamicParameters:
var args = new DynamicParameters(new { });
args.Add("ActionDate", DateTime.Now);
args.Add("Structure", structure, size:Int32.MaxValue); //<-Very big string
args.Add("Id", 1);
But I dont seem to be able to do similar via Kata. Is there a better way to handle this?
The default max string length in Dapper dapper appears to be here, but I can't see how to override this with Kata:
https://github.com/StackExchange/Dapper/blob/4e62055c5775aced61b848282ed180de0ab62161/Dapper/DbString.cs#L21

I think you can pass the DbString directly as parameter in SqlKata.
var rows = db.Query("Table").Where("Name", new DbString {
  Value = "abcde",
  IsFixedLength = true,
  Length = 10,
  IsAnsi = true
}).Get();

off course change the options as per your need.

@cunnpole does the suggested solution (DbString) work for you?


Libva error when running cypress using firefox cypress/browsers:node16.14.2-slim-chrome103-ff102

As the title suggests, I am running into an issue in my gitlab pipeline. I am using the following image: cypress/browsers:node16.14.2-slim-chrome103-ff102
as it supports node 16 and ff 102, which most accurately reflects my local environment.
Running with the command like so:     - $(npm bin)/cypress run --config baseUrl=$BASEURL --spec "cypress/integration/*,cypress/integration/**/*" --browser firefox
And the following returns:
[STARTED] Task without title.
[SUCCESS] Task without title.
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[498:0812/004913.111233:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
====================================================================================================
  (Run Starting)
  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ Cypress:        10.4.0                                                                         │
  │ Browser:        Firefox 102 (headless)                                                         │
  │ Node Version:   v16.14.2 (/usr/local/bin/node)                                                 │
  │ Specs:          13 found (redacted.spec.js, redacted.spec.js, │
  │                 redacted.spec.js, redacted.spec.js, redacted.spec.js, │
  │                 redacted.spec.js, redacted.spec.js, redacted.spec.j │
  │                 s, redacted...)                                                    │
  │ Searched:       cypress/integration/*, cypress/integration/**/*                                │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘
────────────────────────────────────────────────────────────────────────────────────────────────────

  Running:  redacted.spec.js                                                 (1 of 13)
Timed out waiting for the browser to connect. Retrying...
Timed out waiting for the browser to connect. Retrying again...
The browser never connected. Something is wrong. The tests cannot run. Aborting...
The browser never connected. Something is wrong. The tests cannot run. Aborting...
The automation client disconnected. Cannot continue running tests.
Warning: We failed processing this video.
This error will not alter the exit code.
TimeoutError: operation timed out
    at afterTimeout (/root/.cache/Cypress/10.4.0/Cypress/resources/app/packages/server/node_modules/bluebird/js/release/timers.js:46:19)
    at Timeout.timeoutTimeout [as _onTimeout] (/root/.cache/Cypress/10.4.0/Cypress/resources/app/packages/server/node_modules/bluebird/js/release/timers.js:[76](redacted/-/jobs/1325874#L76):13)
    at listOnTimeout (node:internal/timers:559:17)
    at processTimers (node:internal/timers:502:7)

I looked around but not much seems to be showing up for others. Any ideas how to progress?

related: https://github.com/cypress-io/cypress-docker-images/issues/747

Same, we haven't run our cypress tests in 6 months due to it.

@gunslingor

Same, we haven't run our cypress tests in 6 months due to it.

Node.js 16 has reached end-of-life.

Are you able to try with a newer Cypress Docker version?
Are you also running in GitLab?
Which version of Cypress are you using?

Closing due to inactivity.


(PUP-6128) Retain case in QualifiedReference

Before this commit, all qualified references were downcased immediately
in the AST model. Attempts where then made to restore the case when
reporting errors by capitalizing all segments in the name. So names
like MyGreateResource became Mygreatresource.
This commit changes the QualifiedReference so that it instead stores
the original name and will deliver the downcased name when asked to
do so. The logic is also changed in several places to avoid repeated
downcasing and capitalizing.

Pushed a rebased commit where TypeFormatter#capitalize_segments is marked @api private


Python 3 compatibility: print function, absolute imports, ...

'stage1' automatic conversion from python-future

Does this commit run under Python 2? I'm afk for an hour or so and I can't test it.
What else needs to be done for Python 3 compatibility?

Target is code that's 2.7 and 3 compatible. Seems to be working fine for me now in Python 3. The tests, such as they are, seemed to work fine under Python 2.7.
Thanks for the library. This is really handy.

Thanks! I tested it on 2.7 as well and didn't have any trouble. Glad you're finding it useful!

By the way, we have a DTM implementation in the dtm branch. We haven't tested it thoroughly or compared it to the variational EM method yet, so it hasn't been rolled into master, but I figured you might be interested in it!

I saw that! I've linked to pgmult from my aborted attempt to get
pg-DTM working https://github.com/ariddell/horizont
On 07/09, Matthew Johnson wrote:

By the way, we have a DTM implementation in the dtm branch. We haven't tested it thoroughly or compared it to the variational EM method yet, so it hasn't been rolled into master, but I figured you might be interested in it!

Reply to this email directly or view it on GitHub:
https://github.com/HIPS/pgmult/pull/5#issuecomment-119893033


Token chaining API is error prone

Also, this might indicate that we need to do something to fix the cancel token chaining API because honestly, I've had trouble sometimes figuring out what the right order should be. Maybe we need something like token.create_child_token() rather than actually combining two tokens and thus, having to figure out the right ordering.

(From https://github.com/ethereum/py-evm/issues/1234#issuecomment-418223040)
Another thing that is problematic and may need to be redesigned (or at least documented), is the fact that sometimes a class will keep a direct reference to the token passed to its constructor (e.g. https://github.com/ethereum/py-evm/blob/master/trinity/protocol/common/managers.py#L200 and https://github.com/ethereum/py-evm/blob/master/trinity/p2p/handlers.py#L33), which means they will cancel their parents if they ever trigger their tokens. Even though some of those may never actually trigger their tokens (e.g. when they only use the token to detect when their parent has terminated), they could still pass these tokens to other classes that eventually do trigger them

So for the first issue, I propose something like the following.
# legacy
master_token = CancelToken('master')

child_token = CancelToken('child').chain(master_token)

# new
master_token = CancelToken('master')
child_token = master_token.create_child_token('child')

For the issue about things keeping reference to a parent token when they should not, I'm thinking something like this.
# legacy
master_token = CancelToken('master')

# implicit expectation that `Service` class will chain off of
# `master_token` as opposed to using it directly
child_service = Service(master_token)

# new API
child_service = Service(master_token.immutable_reference)

The immutable_reference would support all of the read operations but any calls to things like trigger() or cancellable_wait would throw exceptions.  Then anything that retains a reference to the parent token when it shouldn't will throw errors when it tries to perform operations on it.

A crazy idea:
Split the token into two parts right away: the trigger, and roughly everything else
token_maker = Canceller('master')

parent_trigger, parent_token = token_maker.make_token()

# Only BaseService would keep the parent_trigger in a private location, triggered by cancel()
# The parent_token would be public, though.

###

# Later, something that wants to "chain" can do:

child_maker = parent_token.create_child_canceller('child')

# parent_token.trigger() is NOT a thing
# parent_token.triggered still works

child_trigger, child_token = child_maker.make_token()

These names are... bad. Sorry.

I'd personally prefer the existing APIs (which are simpler) with extra checks to prevent non-owners to trigger tokens


Select tasks on UI for load test

It would be convenient if tasks could be selected from on the UI, instead of just --tags argument on the command line.

I'm in need of the same feature with a little twist, to be able to select which user classes to run.
I think that with a few changes we could be able to do that even for the distributed runner.
If I find the time, I will fork and try to implement this.

@mauriciosl This would be an gamechanger for me, is there any update on this topic ?

Hi @paulheisterkamp97 I have a fork where you will be able to select the tests based on which class they belong. The fork is not good enough to open a PR for the main locust right now, and I don't know if it will ever be, but feel free to use it and contact me if you have any problems.

Thanks, ill try it out.


Update index.html

I made it look better.

Thanks Max! I backed up the original. Best with webpage PR's to somehow get it working in your repository so that I can see the actual page live to see what I like and what I don't like.
You can now delete your fork.


Allow full overriding of open_browser_args on Windows

Thanks for the great plugin!
On Windows, when trying to configure custom open_browser_args, I noticed that default start and explorer.exe args are always forcibly prepended to the args list, no matter what is configured. I'm not sure this makes sense, as it severely restricts the available browser opening strategies for Windows users.
The change I'm proposing makes the open_browser_args behavior more consistent with the open_browser_app config, i.e. if the user provides a custom args list, assume they know what they want and use exactly what is provided.
I hope this sounds reasonable to you, but I do realize it could be a breaking change for Windows users who currently have custom explorer.exe-specific flags configured...although none of those flags seem very useful for link opening? Happy to take any feedback and suggestions.

lgtm 👍


Indexation benchmark fails

This is currently impossible to run the fresh new indexing benchmarks.
See: https://github.com/meilisearch/milli/runs/3362246256?check_suite_focus=true
Input: indexing
branch: main

Fixed by https://github.com/meilisearch/milli/pull/315


Heap corruption detected, free list is damaged

Description
Our firebase crashlytics produced these errors that we can't seem to reproduce but we have a few reported on our console.

Stack trace:
stackTrace.txt
Reproducing the issue
N/A
Firebase SDK Version
10.22.1
Xcode Version
15.3
Installation Method
Swift Package Manager
Firebase Product(s)
Storage
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

Is this still an issue with Firebase 11.x?

I am not seeing this issue anymore i will close this ticket.


Dvclive api reference

You may disregard these recommendations if you used the Edit on GitHub button from dvc.org to improve a doc in place.

❗ Please read the guidelines in the Contributing to the Documentation list if you make any substantial changes to the documentation or JS engine.
🐛 Please make sure to mention Fix #issue (if applicable) in the description of the PR. This causes GitHub to close it automatically when the PR is merged.
Please choose to allow us to edit your branch when creating the PR.
Thank you for the contribution - we'll try to review it as soon as possible. 🙏
Closes https://github.com/iterative/dvclive/issues/108

We should also open a discussion on whether to include this in docstrings. I know there was already some discussion on autogenerating docs, but I think even if we have to duplicate text, it's worth considering for dvclive. IMO docstrings are generally accepted practice for a lot of ML libraries and could encourage contributions.

I agree that it's worth to add the docstrings to dvclive even by copy-pasting content from here. I think I will wait for this P.R. to be merged and after that add the docstrings.

@jorgeorpinel Should we assign a reviewer from the docs team?

Btw, on docstrings, I do think we need to include them (way simpler version though).
Also, as a next step, do we want to write some examples for these APIs?

p.s. @daavoo I realize you may be focused on development so one option is to create a future docs improvement ticket linking to my review above. Maybe we can even work on it ourselves (docs team) — we can discuss in a planning meeting. Tanks

I guess could be part of iterative/dvclive/issues/86 but that's already a pretty long one 😅 kind of an epic?

p.s. @daavoo I realize you may be focused on development so one option is to create a future docs improvement ticket linking to my #2632 (review) above. Maybe we can even work on it ourselves (docs team) — we can discuss in a planning meeting. Tanks

I was already addressing your suggestions locally. My personal opinion is that, for dvclive, extending existing documentation would be more valuable at this point than development of new features and that is also what we have agreed at our planning.

UPDATE: I guess could be part of iterative/dvclive/issues/86 but that's already a pretty long one sweat_smile kind of an epic?

Yep. I tried to use the Github tasks feature to create new issues from the task list. Will create a new one for this API Reference updates.

@jorgeorpinel to clarify, @daavoo 's scope of work includes writing docs/README and other product things, not only engineering. It's expected that he takes of the product holistically (similar to Casper's work on CML I think).

Got it, thanks guys.


3961 Hover item on hand switch

About the PR
Fixes #3961
When switching hands, the client requests an update on the hover.
I do need some assistance on this, though- not sure if the update code is in the correct spot, because I get [WARN] net.ent: Got late MsgEntity! Diff: -3, msgT: 278, cT: 281, player: localhost@JoeGenero when the hands are switched and I'm not certain why.
Screenshots

Changelog

:cl: Moses

fix: Hand switching updates hover icon

When you open a PR to close a specific issue, please put it in the description like this: "Fixes #3961"
Putting the issue number in the title doesn't work

When you open a PR to close a specific issue, please put it in the description like this: "Fixes #3961"
Putting the issue number in the title doesn't work

Literally did it right as you said it, totally forgot

You're calling SendHoverMessage when the game state is being rolled back which means the message is getting spammed over the network.

What would be the appropriate place to call it?

Somewhere that isn't being called during prediction. (beats me)

i believe theres an event for hand switching and you can just subscribe to that?

Yea, I dunno if there's anything client side that handles or predicts the hand switching? I didn't see anything, but I could've just missed something.

electro's predicting hands so that means this would need a complete rewrite to work with it and using the roundtrip was very ehh to begin with.


Demo Player controls

Problem
We have no way of interacting with the Player.
Potential Solution
Implement a basic controller that includes:

Elapsed time.
Total duration.
Play / pause button.
Scrub bar.

Impact
There is no way to test edge cases involving scrubbing, play / pausing without deploying to a client application.

This has been done! #100


Fix for WebGL2 and HTML5 export

This PR is mainly about fixing shaders to work properly in a WebGL2 context:

Add padding to UBO data to be multiple of 16 bytes see here
Add precision definition for samplers
Replace texture2D (deprecated) with texture in shaders

Additionally, I attached to this PR 2 other small fixes:
1 - Application icon loading was broken due to NULL pointer
2 - getaddrinfo was failing due to AI_NUMERICHOST flag being set by default on HTML5 platform (see #9624 ).
(I really hope this won't break other platforms, as it shouldn't, but networking sucks)
I'm really a noob at OpenGL so don't hesitate to question this work.
Let me know also if you prefer to have a separate PR for the 2 small fixes

PR updated, removed padding from ReflectionProbeDataUBO


Bandcamp add uri from web Not working

Hi,  I am not sure why I am seeing this and did not see another format to ask.  I am not sure it is an "issue".
Problem summary:
When I browse in a Mopidy Frontend, Bancamp ext will add the correct URI to the playlist.
However, when using the Web Javascript (bookmark), or the <IP_ADDRESS>:6680/bandcamp page to add, it results in a URI like:  bandcamp:track:None-3763840907-1951117791.
More info:
Both Chromium and Firefox.
Both The JavaScript or entering using the  6680:/bandcamp webpage.
URL pointing to either looback IP or local IP
Every bandcamp page tried has the same result of bandcam:track:None-
JavaScript Bookmark URL:
javascript:s='http://<IP_ADDRESS>:6680/bandcamp/';f=document.createElement('form');f.action=s;i=document.createElement('input');i.type='hidden';i.name='url';i.value=window.location.href;f.appendChild(i);document.body.appendChild(f);f.submit();

Example From Bandcamp track URL:
https://jasonwebley.bandcamp.com/track/in-this-light
If using Mopidy Client Browse | Bandcamp the URI returned is:
bandcamp:track:2220410354-3763840907-1951117791
However, Using the Bandcamp ext Webpage (or bookmark) the URI returned is:
bandcamp:track:None-3763840907-1951117791
Steps and what is seen:
Click the JavaScript Bookmark while on URL above:
Browser warning page shows up:
The information you’re about to submit is not secure
Because this form is being submitted using a connection that’s not secure, your information will be visible to others.
Click [Send Anyway]

Popup Dialog:
  <IP_ADDRESS>:6680/ says
  URL has been added.
Click [OK]

Back In Mopidy Client (IRIS) Now Playing:
Track has been added to Queue.
Shows All correct info. EG:
In This Light
Jason Webley . In This Light - Live at Bear Creek 4:04

In Mopidy Client (IRIS) the tracks will not play.
Using the Client to see the URI with  it will show:
Error: Not found
Could not find anything with URI bandcamp:track:None-3763840907-1951117791

We can also use Copy/Paste URI to see the same bad URI above.   Used IRIS because other Front Ends like Musicbox_webclient and Muse have the same problem (as expected), but do not handle the bad URI in a way we can see it (both just fail to play, or will hang on tack info request).
Mopidy/Extensions/Python/Etc Versions:
Executable: /usr/bin/mopidy
Platform: Linux-5.10.35-v8+-aarch64-with-debian-10.9
Python: CPython 3.7.3 from /usr/lib/python3.7
Mopidy: 3.1.1 from /usr/lib/python3/dist-packages
---
Mopidy-Bandcamp: 1.1.4 from /usr/local/lib/python3.7/dist-packages
  Pykka: 2.0.3 from /usr/lib/python3/dist-packages
  Mopidy: 3.1.1 from /usr/lib/python3/dist-packages
  setuptools: 54.2.0 from /usr/local/lib/python3.7/dist-packages
---
GStreamer: <IP_ADDRESS> from /usr/lib/python3/dist-packages/gi
  Detailed information:
    Python wrapper: python-gi 3.30.4
    Relevant elements:
      Found:
        uridecodebin
        souphttpsrc
        appsrc
        alsasink
        osssink
        oss4sink
        pulsesink
        id3demux
        id3v2mux
        lamemp3enc
        mpegaudioparse
        mpg123audiodec
        vorbisdec
        vorbisenc
        vorbisparse
        oggdemux
        oggmux
        oggparse
        flacdec
        flacparse
        shout2send
      Not found:
        flump3dec
        mad
  setuptools: 54.2.0 from /usr/local/lib/python3.7/dist-packages

Using mpc had the same effect.
I do not authenticate/login to bandcamp.  So I think the answer is no to your questions 1,2.
I tried to poke at the code, but  .py is not my native language and I do not have/know a dev env for debugging in py.  Reading the code I think I figured out the line where it yanks from but did not have a way to debug or explore the text (json?) it brings back...  Are there Docs somewhere for scrape?  Or a quick script to execute scrape interactively? ( As I said .py is not my native language and I was trying vscode or thony but did not get to the point of successfully instantiating bandcampclient.scrape (before I gave up ), mainly I could not see where "config" is set, and ran into a module error when import config from mopidy ).  Or????
Thanks

I do not authenticate/login to bandcamp.

Ah ha!  That's it.   I've added the non-authenticated scrape to the unit tests (like it should have been in the first place), and it's breaking exactly as you described.  I'm working on the fix now, and will push out a new release once I'm done.
Thank you for finding this and pointing it out.

OK, Can you upgrade to v1.1.5 and let me know if that solves the issue for you?

That worked!
(After a bit of clearing caches :))
Thank you.
A


problem when compiling

i always get this error,i tried lots of ways,if i just copy this file to the project ,i will get more error.
error	C1083	can't open: “capstone.h”: No such file or directory	DdiMon	C:\Users\hunter\Desktop\fdssd\DdiMon-master\DdiMon\shadow_hook.cpp	21
i do not know how to include this file ,can you help me

Did you clone submodules?
git clone --recursive https://github.com/tandasat/DdiMon.git

when i did as you say,i got those errors and i have no idea where the problem is.my visual studio is 2019.can you help me?
error	LNK2019	Unresolved external symbol  _invoke_watson，The symbol in the function "protected: virtual void __cdecl stdext::bad_alloc::_Doraise(void)const " (?_Doraise@bad_alloc@stdext@@MEBAXXZ) Referenced	DdiMon	C:\Users\hunter\Desktop\myhv\new\DdiMon\DdiMon\shadow_hook.obj	1
error	LNK2001	Unresolved external symbol "void (__cdecl* std::_Raise_handler)(class stdext::exception const &)" (?_Raise_handler@std@@3P6AXAEBVexception@stdext@@@ZEA)	DdiMon	C:\Users\hunter\Desktop\myhv\new\DdiMon\DdiMon\shadow_hook.obj	1

It turned out that it is no longer possible to use the C++ standard library in the kernel mode with only _HAS_EXCEPTION 0 with VS 2019.
I was able to compile the project by adding those missing definitions. I do not know what the implication of this exactly but you can try and play with the project.
////////////////////////////////////////////////////////////////////////////////
//
// implementations
//

EXTERN_C
_ACRTIMP void __cdecl _invoke_watson(
    _In_opt_z_ wchar_t const* _Expression,
    _In_opt_z_ wchar_t const* _FunctionName,
    _In_opt_z_ wchar_t const* _FileName,
    _In_       unsigned int _LineNo,
    _In_       uintptr_t _Reserved)
{
}

namespace std { _Prhand _Raise_handler; }

Thank you very much.I solved this error

Hi @HuntFrank
Can you please described how did you sove it? (I am facing the same error)

Nevermind. I wrongly added ucrtd library. Now it builds.

Since google appears to be pointing to this and there appears to be an issue with the latest Visual Studio version, I'm going to resurrect this issue. Sorry about that.
I was consistently able to resolve the issue by not using /std:latest but rather /std:c++20 (which to me is less limiting than having to enable exceptions and the problems exception handling can cause with the Address Sanitizer).
Hope this helps someone.


Add emptyElementParsePolicy to main DFDL namespace.

The emptyElementParsePolicy is currently implemented as a property that is an extension to DFDL. As of DFDL 1.0, this property is now available in the main schema. This property has now been added and a deprecation message is emitted when the old property is used. The property value of treatAsMissing has been renamed to treatAsAbsent in DFDL 1.0.
DAFFODIL-2496

I just noticed that this PR needs to be merged by a Daffodil committer.  I confirm that all PR comments have been resolved, @mike-mcgann has squashed the PR to one commit, and all tests have passed successfully.


Add Eutropius's Breviarium, obtained from DCC

Dickinson College Commentaries (DCC) has published several commentaries on Latin literature under the license of Creative Common.
Although it's viable to read them on their website, I believe there is still value in making the markdown version, since you can then convert it into an epub for better reading experience.
As starter, here is the easiest classical author, Eutropius :)

Thank you so much for putting this PR together!
The one issue I'm having with merging it is that the macronization scheme is different from Wiktionary's, e.g. fīrmiōribus (Dickinson) -> firmiōribus (Wiktionary), prīvīgnam (Dickinson) -> prīvignam (Wiktionary), etc, and I've been trying to edit everything to conform to that (mostly for machine processing reasons, but also because that's how my spellcheck is set up right now). So I can accept this if you could update the header to be edited: false and rearrange the README?
Alternatively, there are existing copies of Eutropius in this repo already; an edited, but simplified copy from Clark and an full, but unedited copy from Hazzard. Eventually, I'll get to editing the Hazzard copy (I have a few other things going on this month and I'm currently slogging through a full de Bello Gallico) and the Dickinson version will be a good proof check on that either way.

I see. That's indeed problem. I didn't notice that, nice catch!
However, I'm not sure whether the discrepancies are due to they using a different macronization scheme, because they only happen a few times. I haven't checked all the way to book 10, but overall, it seems to conform to Wiktionary. Maybe it's been overlooked?
Regardless, using this version as a reference to edit the Hazzard's version is also a good idea. I'll update the status into unedited
I have a question, though. Wouldn't it be easier to just edit this version? We just need to proofread the macrons.

Thanks!
I don't know if it's a different scheme per se, but I've seen quite a few older texts that with -āgn- or -īgn- and not many contemporary ones (e.g. LLPSI or others). I wish I knew more about how those conventions got updated.
And yeah, agreed it's easier and faster to proofread this one, but I also like to have different versions to compare to each other?


Suggestions,  for AI

Make it so that bots use proxminity mines and throw laptop guns as turrets when they have more than 300 ammo.
Even if this only happens with darksims and perfect sims. ;)

If I recall correctly, technically the behavior to use the Laptop Gun's sentry gun function is already there. It's just, they'll only ever use it when they're out of ammo, because it's the same routine as using the Dragon's proximity mine function.

That's my point... I want them to do it way more often. Not hard sims though, just perfect/dark sims.


virtcontainers: Create the kata agent vsock earlier

We generate the vsock CID randomly, we know at agent init time how to
set it up. So let's simplify the agent flow and allocate the
vsock and its vhost fd when we do generate the VM socket.
Fixes: #1013
Signed-off-by: Samuel Ortiz<EMAIL_ADDRESS>

/test

/test

Thanks @sameo.
lgtm

Ping @sameo / @devimc any updates? Thx!

/retest

/test
Ping @sameo - I think everybody pretty much agreed this was a good thing, but the CIs seemed unhappy.
I'm retriggering them so you get a chance to look at the logs (as I think the last ones have rotted).

CI's are failing but have expired. Since the branch is conflicted, please could you resolve @sameo so we can re-trigger the tests?

Ping @sameo / @devimc. Any updates?  What do you want to do with it:

refresh it (no doubt needs a rebase)
drop it
spin the CI and see what happens (probably not worth it until rebased).

let us know, thanks.

@sameo - this PR is fully approved, but just needs a rebase to fix the conflict to allow us to land it.

@sameo any updates?

@sameo won't have time to rebase this PR.  If anyone wants to take a look, please grab?

Any takers for rebase?

Any takers? 😄

/test

/test-vsock

/test

fedora seems to have failed with jaeger tests failing.
Name: Container: Sandbox: Data:map[]}" commit=c657e5ec6f076de45e8f7264deb24e06478717f9 name=kata-log-parser pid=36524 source=log-parser version=0.0.1
ERROR: kata-log-parser: failed to parse file "/tmp/jenkins/workspace/kata-containers-runtime-fedora-PR/go/src/github.com/kata-containers/tests/kata-proxy.log", line 152: logfmt syntax error at pos 145 on line 152: invalid quoted value (keyvals: [{key:time value:2019-08-05T15:07:58.408626983Z} {key:level value:info}])

centos has ak8s replication controller failure.
not ok 1 Replication controller
# (from function `waitForProcess' in file ../../.ci/lib.sh, line 165,
#  in test file k8s-replication.bats, line 39)
#   `waitForProcess "$wait_time" "$sleep_time" "$cmd"' failed
# INFO: k8s configured to use runtimeclass
# replicationcontroller/replicationtest created
#   Normal  SuccessfulCreate  0s    replication-controller  Created pod: replicationtest-6f87w
# pod/replicationtest-6f87w condition met
# timed out waiting for the condition on pods/deploymenttest-685ffb4656-nhvt5
# Error from server (NotFound): pods "deploymenttest-685ffb4656-rxnvs" not found
# pod/replicationtest-6f87w condition met
# Error from server (NotFound): pods "deploymenttest-685ffb4656-nhvt5" not found
# Error from server (NotFound): pods "deploymenttest-685ffb4656-rxnvs" not found
# pod/replicationtest-6f87w condition met
# Error from server (NotFound): pods "deploymenttest-685ffb4656-nhvt5" not found
# Error from server (NotFound): pods "deploymenttest-685ffb4656-rxnvs" not found
# pod/replicationtest-6f87w condition met
# Error from server (NotFound): pods "deploymenttest-685ffb4656-nhvt5" not found
# Error from server (NotFound): pods "deploymenttest-685ffb4656-rxnvs" not found
# pod/replicationtest-6f87w condition met
# Error from server (NotFound): pods "deploymenttest-685ffb4656-nhvt5" not found
# Error from server (NotFound): pods "deploymenttest-685ffb4656-rxnvs" not found
# pod/replicationtest-6f87w condition met
# Error from server (NotFound): pods "deploymenttest-685ffb4656-nhvt5" not found
# Error from server (NotFound): pods "deploymenttest-685ffb4656-rxnvs" not found
# pod/replicationtest-6f87w condition met
# Error from server (NotFound): pods "deploymenttest-685ffb4656-nhvt5" not found
# Error from server (NotFound): pods "deploymenttest-685ffb4656-rxnvs" not found
# pod/replicationtest-6f87w condition met
# Error from server (NotFound): pods "deploymenttest-685ffb4656-nhvt5" not found
# Error from server (NotFound): pods "deploymenttest-685ffb4656-rxnvs" not found
# pod/replicationtest-6f87w condition met
# Error from server (NotFound): pods "deploymenttest-685ffb4656-nhvt5" not found
# Error from server (NotFound): pods "deploymenttest-685ffb4656-rxnvs" not found
# pod/replicationtest-6f87w condition met
# Error from server (NotFound): pods "deploymenttest-685ffb4656-nhvt5" not found
# Error from server (NotFound): pods "deploymenttest-685ffb4656-rxnvs" not found
# Error from server (NotFound): pods "deploymenttest-685ffb4656-nhvt5 deploymenttest-685ffb4656-rxnvs replicationtest-6f87w" not found
# replicationcontroller "replicationtest" deleted
Failed at 73: bats "${K8S_TEST_ENTRY}"

power8 seems to be hitting a wierd timeout with creating vsock socket. Re-kicking it for now to see if that is a consistent failure.
@jcvenegas @GabyCT the other two issues are something you have seen recently or am i the one messing them up?

centos seems to be a failure across other jobs too. https://github.com/kata-containers/tests/pull/1901 fixes that. Will re-trigger that job once the PR lands. thanks @GabyCT

Seems Power8 tests are timing out with creation of a contextID for vsock. @Pennyzct sorry if i am reaching out to the wrong person here, but is this something that you can comment on?
=== RUN   TestAgentPathAPI
coverage: 31.6% of statements
panic: test timed out after 30s

goroutine 686 [running]:
testing.(*M).startAlarm.func1()
	/usr/local/go/src/testing/testing.go:1334 +0xcc
created by time.goFunc
	/usr/local/go/src/time/sleep.go:169 +0x44

goroutine 1 [chan receive, locked to thread]:
testing.(*T).Run(0xc000472100, 0x10a653d9, 0x10, 0x10aa1978, 0x1)
	/usr/local/go/src/testing/testing.go:917 +0x310
testing.runTests.func1(0xc0003ea200)
	/usr/local/go/src/testing/testing.go:1157 +0x78
testing.tRunner(0xc0003ea200, 0xc0005839d8)
	/usr/local/go/src/testing/testing.go:865 +0xc4
testing.runTests(0xc0004c1ba0, 0x11325480, 0x1a9, 0x1a9, 0x23)
	/usr/local/go/src/testing/testing.go:1155 +0x284
testing.(*M).Run(0xc0004cf980, 0x0)
	/usr/local/go/src/testing/testing.go:1072 +0x158
github.com/kata-containers/runtime/virtcontainers.TestMain(0xc0004cf980)
	/home/jenkins/workspace/kata-containers-runtime-Power8-ubuntu-16-04-PR-initrd/go/src/github.com/kata-containers/runtime/virtcontainers/virtcontainers_test.go:145 +0xe48
main.main()
	_testmain.go:1034 +0x1e0

goroutine 491 [select]:
github.com/kata-containers/runtime/vendor/github.com/kata-containers/agent/protocols/client.commonDialer(0x4a8179d1e, 0xc0005b3bc0, 0x10be72c0, 0xc0004714f0, 0x1, 0x1, 0x10be72c0, 0xc0004714f0)
	/home/jenkins/workspace/kata-containers-runtime-Power8-ubuntu-16-04-PR-initrd/go/src/github.com/kata-containers/runtime/vendor/github.com/kata-containers/agent/protocols/client/client.go:311 +0x128
github.com/kata-containers/runtime/vendor/github.com/kata-containers/agent/protocols/client.unixDialer(0xc0004de605, 0x35, 0x4a8179d1e, 0xbf4a46ec85abb542, 0x5531190c4, 0x1137ea80, 0x4a8179d1e)
	/home/jenkins/workspace/kata-containers-runtime-Power8-ubuntu-16-04-PR-initrd/go/src/github.com/kata-containers/runtime/vendor/github.com/kata-containers/agent/protocols/client/client.go:253 +0x114
github.com/kata-containers/runtime/vendor/google.golang.org/grpc.WithDialer.func1(0x10c04fc0, 0xc0007707e0, 0xc0004de600, 0x3a, 0xc0004f82d0, 0xc000396ed0, 0xc000502600, 0xc000032540)
	/home/jenkins/workspace/kata-containers-runtime-Power8-ubuntu-16-04-PR-initrd/go/src/github.com/kata-containers/runtime/vendor/google.golang.org/grpc/clientconn.go:337 +0xc4
github.com/kata-containers/runtime/vendor/google.golang.org/grpc/transport.dial(0x10c04fc0, 0xc0007707e0, 0xc00046f190, 0xc0004de600, 0x3a, 0x7e6dab6c0068, 0x10048c64, 0xc00063d438, 0x7e6da8433830)
	/home/jenkins/workspace/kata-containers-runtime-Power8-ubuntu-16-04-PR-initrd/go/src/github.com/kata-containers/runtime/vendor/google.golang.org/grpc/transport/http2_client.go:118 +0x5c
github.com/kata-containers/runtime/vendor/google.golang.org/grpc/transport.newHTTP2Client(0x10c04fc0, 0xc0007707e0, 0x10c04f40, 0xc0004f82c0, 0xc0004de600, 0x3a, 0x0, 0x0, 0xc0004de600, 0x3a, ...)
	/home/jenkins/workspace/kata-containers-runtime-Power8-ubuntu-16-04-PR-initrd/go/src/github.com/kata-containers/runtime/vendor/google.golang.org/grpc/transport/http2_client.go:151 +0xbc
github.com/kata-containers/runtime/vendor/google.golang.org/grpc/transport.NewClientTransport(...)
	/home/jenkins/workspace/kata-containers-runtime-Power8-ubuntu-16-04-PR-initrd/go/src/github.com/kata-containers/runtime/vendor/google.golang.org/grpc/transport/transport.go:524
github.com/kata-containers/runtime/vendor/google.golang.org/grpc.(*addrConn).createTransport(0xc0003c8b40, 0x2, 0x0, 0xbf4a46ed4654a0bb, 0x6068ada3c, 0x1137ea80, 0xbf4a46f185ab8a61, 0x9fb292de2, 0x1137ea80, 0xc000032bc0, ...)
	/home/jenkins/workspace/kata-containers-runtime-Power8-ubuntu-16-04-PR-initrd/go/src/github.com/kata-containers/runtime/vendor/google.golang.org/grpc/clientconn.go:1156 +0x36c
github.com/kata-containers/runtime/vendor/google.golang.org/grpc.(*addrConn).resetTransport(0xc0003c8b40, 0x10bf6140, 0xc00046f290)
	/home/jenkins/workspace/kata-containers-runtime-Power8-ubuntu-16-04-PR-initrd/go/src/github.com/kata-containers/runtime/vendor/google.golang.org/grpc/clientconn.go:1117 +0x3a4
github.com/kata-containers/runtime/vendor/google.golang.org/grpc.(*addrConn).transportMonitor(0xc0003c8b40)
	/home/jenkins/workspace/kata-containers-runtime-Power8-ubuntu-16-04-PR-initrd/go/src/github.com/kata-containers/runtime/vendor/google.golang.org/grpc/clientconn.go:1282 +0x388
github.com/kata-containers/runtime/vendor/google.golang.org/grpc.(*addrConn).connect.func1(0xc0003c8b40)
	/home/jenkins/workspace/kata-containers-runtime-Power8-ubuntu-16-04-PR-initrd/go/src/github.com/kata-containers/runtime/vendor/google.golang.org/grpc/clientconn.go:854 +0x1c8
created by github.com/kata-containers/runtime/vendor/google.golang.org/grpc.(*addrConn).connect
	/home/jenkins/workspace/kata-containers-runtime-Power8-ubuntu-16-04-PR-initrd/go/src/github.com/kata-containers/runtime/vendor/google.golang.org/grpc/clientconn.go:845 +0xc8

goroutine 489 [select]:
github.com/kata-containers/runtime/vendor/google.golang.org/grpc.(*ccResolverWrapper).watcher(0xc000396e10)
	/home/jenkins/workspace/kata-containers-runtime-Power8-ubuntu-16-04-PR-initrd/go/src/github.com/kata-containers/runtime/vendor/google.golang.org/grpc/resolver_conn_wrapper.go:109 +0xec
created by github.com/kata-containers/runtime/vendor/google.golang.org/grpc.(*ccResolverWrapper).start
	/home/jenkins/workspace/kata-containers-runtime-Power8-ubuntu-16-04-PR-initrd/go/src/github.com/kata-containers/runtime/vendor/google.golang.org/grpc/resolver_conn_wrapper.go:95 +0x40

goroutine 490 [select]:
github.com/kata-containers/runtime/vendor/google.golang.org/grpc.(*ccBalancerWrapper).watcher(0xc0004f84c0)
	/home/jenkins/workspace/kata-containers-runtime-Power8-ubuntu-16-04-PR-initrd/go/src/github.com/kata-containers/runtime/vendor/google.golang.org/grpc/balancer_conn_wrappers.go:122 +0xc8
created by github.com/kata-containers/runtime/vendor/google.golang.org/grpc.newCCBalancerWrapper
	/home/jenkins/workspace/kata-containers-runtime-Power8-ubuntu-16-04-PR-initrd/go/src/github.com/kata-containers/runtime/vendor/google.golang.org/grpc/balancer_conn_wrappers.go:113 +0x134

goroutine 735 [runnable]:
github.com/kata-containers/runtime/virtcontainers/utils.Ioctl(0x3, 0x4008af60, 0xc0005a8f68, 0x10be82e0, 0xc000498000)
	/home/jenkins/workspace/kata-containers-runtime-Power8-ubuntu-16-04-PR-initrd/go/src/github.com/kata-containers/runtime/virtcontainers/utils/utils_linux.go:30 +0x14
github.com/kata-containers/runtime/virtcontainers/utils.FindContextID(0xc0001ff810, 0xc000080d38, 0x1, 0x1)
	/home/jenkins/workspace/kata-containers-runtime-Power8-ubuntu-16-04-PR-initrd/go/src/github.com/kata-containers/runtime/virtcontainers/utils/utils_linux.go:76 +0x170
github.com/kata-containers/runtime/virtcontainers.(*kataAgent).generateVMSocket(0xc0004cf680, 0x10a5ad26, 0x6, 0x100, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
	/home/jenkins/workspace/kata-containers-runtime-Power8-ubuntu-16-04-PR-initrd/go/src/github.com/kata-containers/runtime/virtcontainers/kata_agent.go:179 +0xc4
github.com/kata-containers/runtime/virtcontainers.TestAgentPathAPI(0xc000472100)
	/home/jenkins/workspace/kata-containers-runtime-Power8-ubuntu-16-04-PR-initrd/go/src/github.com/kata-containers/runtime/virtcontainers/kata_agent_test.go:647 +0x630
testing.tRunner(0xc000472100, 0x10aa1978)
	/usr/local/go/src/testing/testing.go:865 +0xc4
created by testing.(*T).Run
	/usr/local/go/src/testing/testing.go:916 +0x2f4

goroutine 768 [runnable]:
sync.(*Mutex).Unlock(0xc0006abd50)
	/usr/local/go/src/sync/mutex.go:175 +0x14
context.(*cancelCtx).Done(0xc0006abd40, 0x0)
	/usr/local/go/src/context/context.go:330 +0x5c
net.(*sysDialer).dialSerial(0xc0000e4200, 0x10c04fc0, 0xc0006abd40, 0xc000650e30, 0x1, 0x1, 0x0, 0x0, 0x0, 0x0)
	/usr/local/go/src/net/dial.go:518 +0xa0
net.(*Dialer).DialContext(0xc000641e78, 0x10c04f80, 0xc0000ce010, 0x10a59198, 0x4, 0xc0004de605, 0x35, 0x0, 0x0, 0x0, ...)
	/usr/local/go/src/net/dial.go:417 +0x5ac
net.(*Dialer).Dial(...)
	/usr/local/go/src/net/dial.go:340
net.DialTimeout(0x10a59198, 0x4, 0xc0004de605, 0x35, 0x4a8179d1e, 0xc000698c60, 0x0, 0x10be7e00, 0xc000720000)
	/usr/local/go/src/net/dial.go:326 +0x9c
github.com/kata-containers/runtime/vendor/github.com/kata-containers/agent/protocols/client.unixDialer.func1(0x0, 0xc000698c60, 0x10be7e00, 0xc000725360)
	/home/jenkins/workspace/kata-containers-runtime-Power8-ubuntu-16-04-PR-initrd/go/src/github.com/kata-containers/runtime/vendor/github.com/kata-containers/agent/protocols/client/client.go:249 +0x50
github.com/kata-containers/runtime/vendor/github.com/kata-containers/agent/protocols/client.commonDialer.func1(0xc000698c60, 0xc0005b3bc0, 0xc000471540, 0xc000698cc0)
	/home/jenkins/workspace/kata-containers-runtime-Power8-ubuntu-16-04-PR-initrd/go/src/github.com/kata-containers/runtime/vendor/github.com/kata-containers/agent/protocols/client/client.go:295 +0x54
created by github.com/kata-containers/runtime/vendor/github.com/kata-containers/agent/protocols/client.commonDialer
	/home/jenkins/workspace/kata-containers-runtime-Power8-ubuntu-16-04-PR-initrd/go/src/github.com/kata-containers/runtime/vendor/github.com/kata-containers/agent/protocols/client/client.go:286 +0xa4
FAIL	github.com/kata-containers/runtime/virtcontainers	30.118s
make: *** [Makefile:591: go-test] Error 1
Build step 'Execute shell' marked build as failure
Performing Post build task...
Match found for :.* : True
Logical operation result is TRUE
Running script  : #!/bin/bash

Hi @ganeshmaharaj
I have encountered similar issue on AArch64 a couple months ago.
For me, it is because that host kernel is missing this patch
commit 7fbe078c37aba3088359c9256c1a1d0c3e39ee81 (vhost/vsock: fix vhost vsock cid hashing inconsistent).
You could see more details on #1319 and #1203.
I glimpsed the latest comment on these, looks like that Ubuntu 4.15.0-55-generic has already backported this patch, and for AArch64, we have limitation for host kernel > 4.20.x, so I have already updated

Hi @ganeshmaharaj, I have bumped the kernel version to 5.0.7-050007-generic and restarted the CI. Let's see how it goes. Thnx @Pennyzct for the inputs.

Not sure why but I see the CI tests panic due to time out
=== RUN   TestAgentPathAPI
coverage: 31.6% of statements
panic: test timed out after 30s

goroutine 797 [running]:
testing.(*M).startAlarm.func1()
	/usr/local/go/src/testing/testing.go:1334 +0xcc
created by time.goFunc
	/usr/local/go/src/time/sleep.go:169 +0x44

Looks like vsock is not supported on ppc64le.
root@kata1:~# journalctl -t kata-runtime
Aug 07 13:59:31 kata1 kata-runtime[19893]: time="2019-08-07T13:59:31.414845815+05:30" level=error msg="Could not get a unique context ID for the vsock" arch=ppc64le command=create container=553c3981a2aba5e46e8b3ab0956bb05336b947938193f84195555fcad35639a9 name=kata-runtime pid=19893 source=runtime

This change triggers a test of creating a vsock file across all HWs and it seems that we are unable to create vsock files on ppc64le. See #1943 for more details. This change is blocked until we are able to fix that issue.

/test-power
As logs no longer available for reference.

/test-power

@ganeshmaharaj : Finally!   :-)

Oh, great~

This has already been incorporated with commit 5ac6e9a8
Closing this PR.


benchmarks: help/init increase number of rounds to 100

The first approach to fix #323
This change increases the execution time from 10 seconds to about 2 minutes (for both tests). So the influence on our CI should not be noticeable.

Holding for a bit before merging this, want to check if we still get failures for help/init


Time in sorting function

A not-yet-ready PoC to add time into the scoring function:

Defines a T and R keybinding to set an estimated completion time (ect), or for example, 1d, 2h, 0.5w.
Sorts overdue task first by applying an offset to it,
Defines commands such as:

:Dooing list: displays the list of tasks and their indices,
:Dooing set 1 priority important,urgent to set the priorities of the 1st task,
:Dooing set 1 ect 1d, sets an estimated completion time of 1 day for the first task.

I didn't thoroughly tested the features, so this is only a draft :)
Feel free to give me advices / feedbacks / suggestions !

I like the concept and the day/week logic.
think that colors can be same of prioritization. Here, both todos are checked as important.

and .0 can be removed just for conciseness

Thanks for your feedback, I'll change that. Also, the sorting of overdue tasks can be improved, I'll think about it 👌

Okay, here is a stable version of the feature:

Highlights are now only bound to priorities (we define a priority group in the config to attribute colors to it),
In the json file, I renamed priority to priorities for consistency with the rest of the code,
I refactored the logic behind the highlighting to make things a bit easier to read / understand,
Tasks are sorted by the distance to the due date (e.g. nearest due date first),
Tasks are can be done quickly must be done first. The current default config (which can be tweaked) forces long tasks (e.g. more than 12h to complete) to be penalized, and very quick tasks to be sorted first. Tasks that are neither important not urgent stay at the bottom.

What do you think? :)

LOVE THAT! gonna review and test locally later today

some conflicts is happening with the latest updates. Gonna check this out

I solved the conflicts, let me know if it's good for you :)


Chaging CI/CD variables, checking if everything is ok

[insert plane take-off gif here]

!giphy plane


 The provided API key is invalid. )"
How to do?

"The provided API key is invalid."  Use your own api


Headless script stops on boss fight

Most of the times on the boss fight Boss HP and Boss EXP stop, with only the time changing. In this case the easy boss fight has been going on for well over two hours. This happened for me on the last two days. Last boss fight was two days ago, if I recall correctly.
C:\downloads\programs\steam\salien-bot-master>node headless -l
Playing as:       dakkarino
Running for:      3h 9m 39s
Current level:    16 (9142570 / 9600000)
Exp since start:  48000
Estimated exp/hr: 18782
Current planet:   Planet of Jumpless Platformers [80.126%] (id 39)
Current zone:     (8, 3) BOSS easy [51.340%] (id: 44)
Boss HP:          20998426 / 40000000 [52.50%]
Boss EXP:         385000
log_201807011640.txt

the boss fights are working now... i had one earlier today.

what version are you running?

// @version      27

Updated to the latest 29 just now, I will keep you posted on the issue.

that's not headless version - that's in package.json
but yeah that should fix it


fix(#1533): combobox undefined typeerror

Closes IBM/carbon-components-angular#1533
Combobox (type: single) throws TypeError because of bad
 "TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))"
Changelog
Changed

Added fallback value for combobox, specifically, when:

type: single
itemValueKey is falsey

@cal-smith i missed the notification - i'm on it now


(Flaky-Test) Possible race condition - Fix Prometheus Tests

These are intermittent errors that appear to be race conditions or concurrency issues, rather than issues with just the tests:
[ERROR] Tests run: 6, Failures: 2, Errors: 0, Skipped: 2, Time elapsed: 1.904 s <<< FAILURE! - in org.apache.pulsar.broker.stats.PrometheusMetricsTest
576[ERROR] testPerNamespaceStats(org.apache.pulsar.broker.stats.PrometheusMetricsTest) Time elapsed: 0.062 s <<< FAILURE!
577java.lang.AssertionError: expected [true] but found [false]
578 at org.testng.Assert.fail(Assert.java:96)
579 at org.testng.Assert.failNotEquals(Assert.java:776)
580 at org.testng.Assert.assertTrue(Assert.java:44)
581 at org.testng.Assert.assertTrue(Assert.java:54)
582 at

[ERROR] testPerTopicStats(org.apache.pulsar.broker.stats.PrometheusMetricsTest) Time elapsed: 0.071 s <<< FAILURE!
600java.lang.AssertionError: expected [true] but found [false]
601 at org.testng.Assert.fail(Assert.java:96)
602 at org.testng.Assert.failNotEquals(Assert.java:776)
603 at org.testng.Assert.assertTrue(Assert.java:44)
604 at org.testng.Assert.assertTrue(Assert.java:54)
605 at

They may reflect intermittent issues that are happening in production.
They can be seen here: https://github.com/apache/pulsar/pull/6202/checks?check_run_id=431093396
I've attached the logs.
logs_14078.zip
surefire-artifacts (2).zip

I found the issue. There's a race in how we're getting metrics from Prometheus (because we're expecting a particular order, but Prometheus doesn't guarantee that order). There also might be a race between our tests, so I've broken them up into separate topics and filtered the results. The tests are passing locally.

This is fixed in #6202
I'm planning on splitting that big PR into smaller ones.

Closed as stale and no recent report. Please open a new issue if it's still relevant in maintained versions.


[NEW ALGORITHM] Add 1 to a linked list

Issue will be closed if:

You mention more than one algorithm. You can create a separate issue for each algorithm once the current one is completed.
You propose an algorithm that is already present or has been mentioned in a previous issue.
You create a new issue without completing your previous issue.

Note: These actions will be taken seriously. Failure to follow the guidelines may result in the immediate closure of your issue.

Name:
Add 1 to a linked list
About:
Propose a new algorithm to be added to the repository
It will add 1 to a number stored in format of a singly-linked list
Labels:
new algorithm, gssoc-ext, hacktoberfest, level1

Assignees:

[x] Contributor in GSSoC-ext
[x] Want to work on it
Please assign this issue to me.Also can you assign me level 2.

@Arghya-Chakraborty0812 I am interested to solve this. Please assign it to me.


move image filters under libpod/images

to make things more effecient for the api work we are doing, we should
process image filters internally (as opposed to in main).  this allows
for better api responses and more closely affiliated functions.
Signed-off-by: baude<EMAIL_ADDRESS>

I don't like the public API, but we'll be reworking anyways to integrate with c/image, so we can discuss later. LGTM, let's get this landed.
/lgtm


ColaManhua (OhManhua): add Category and Char filters

Checklist:

[x] Updated extVersionCode value in build.gradle for individual extensions
[ ] Updated overrideVersionCode or baseVersionCode as needed for all multisrc extensions
[ ] Referenced all related issues in the PR body (e.g. "Closes #xyz")
[ ] Added the isNsfw = true flag in build.gradle when appropriate
[x] Have not changed source names
[ ] Have explicitly kept the id if a source's name or language were changed
[x] Have tested the modifications by compiling and running the extension through Android Studio

It seems that order by create stop working now.
https://www.colamanga.com/show?orderBy=create


MinkowskiEngine

Hello！I am very appreciated your work, but I have some problem when install MinkowskiEngine package? How can I install it successfully.

Different people might fail to install due to different reasons, could you try to install following their official installation instruction?


Hooks / Middleware support

Similar to Mongoose middlewares, in which we can provide functions that can execute before / after CRUD operations.
For example we could use to to send a notification or email out everytime a user is updated.

We already have hooks support for before and after CRUD operations. It's just not documented yet.
We already have an issue for it #39.
Thanks

Awesome, yea I just didn't see it on the readme.
Dharmesh Malam
On 28 January 2012 19:48, Pavan Kumar Sunkara <
<EMAIL_ADDRESS>
wrote:

We already have hooks support for before and after CRUD operations. It's
just not documented yet.
We already have an issue for it #39.
Thanks

Reply to this email directly or view it on GitHub:
https://github.com/flatiron/resourceful/issues/46#issuecomment-3702961

Cool idea. I know resourceful has an internal concept of hooks, but I'm not sure how exposing them to the end user would work. Something to think about!


Remove Links section at the bottom of most chapters?

Example from a preview PDF copy:

I'm proposing that we remove these sections if they don't contain any external "See also" style external links (e.g., those intended to provide more information/context).

I get it now. Those links are included at the bottom of the Markdown docs in order to provide a useful navigation link if viewing the content directly from GitHub.
Challenge: Show these links for readers using GitHub, but exclude them from generated documents (PDF, epub, mobi).

Please ignore this. There will be some +- right? We have to merge two formats and there is bound to be some issues.

Please ignore this. There will be some +- right? We have to merge two formats and there is bound to be some issues.

Acknowledged.
Per #106 I updated some of the header levels, including the Links sections. With the changes there that places the Links sections directly into the Table of Contents. That in itself isn't necessarily a bad thing, as any additional "See also" links for further reading would be a great fit for those areas.
The unintentional bit was that the navigation links for web viewing showed up there.
As you indicated, this might be something that can't be easily fixed and might not be worth spending a lot of time on. It would be nice if there was a hook script of some kind that could be triggered when the Markdown files are parsed by Leanpub to remove the references, but again, something for later perhaps.


Bug 2277928: [release-4.12] Remove default value of waitTimeoutForHealthyOSDInMinutes

Remove default value of waitTimeoutForHealthyOSDInMinutes from ocs-operator, and only update the SC CR, if a value is provided by the user.

/bugzilla refresh

Similar network issue while installing noobaa catalog 🫤

/retest

/retest-required

/test ocs-operator-bundle-e2e-aws

/retest-required

/override ci/prow/ocs-operator-bundle-e2e-aws


Add instructions for openCalendar

Document how to use openCalendar.

I'm not sure I want to "encourage" using ref with the component. If you are using ref with a React component it's usually something wrong, so let's try to fix what's wrong instead of encouraging bad practice.
What do you say? @SachaG

I don't disagree, but then what would the ideal API look like?

I guess we could just rely on open instead. My main reason for wanting to use openCalendar was to differentiate between "I want to trigger this calendar's opening" and "I want this calendar to remain in an open state", which I thought was more what open was for. But maybe that's not really a meaningful distinction.

I think it is a meaningful distinction, but can't this be done today with the open prop? If you consider it to be a state it makes sense to use it for both, then you could just write your own openCalendar:
const openCalendar = bool => bool;
<Datetime
  open={openCalendar}
/>

True. Is #510 worth fixing then? Or should people just not use openCalendar?

If your issue is solved, then feel free to close it. I'd not advise people to use that function using refs.

OK.


Async functions handled incorrectly when building in production mode

Bug report

What is the current behavior?
When an async function returns an immediate value, if the app is compiled with mode: 'production'
the optimizer doesn't wrap the returned value in a Promise, causing a
TypeError: {(intermediate value)}.then is not a function error
If the current behavior is a bug, please provide the steps to reproduce.
I've created a minimal reproducible setup here: https://github.com/artoale/webpack-babel-async-issue
The gist of it is having an async function return an object literal, and then call it expecting a promise:
const getObject = async () => ({ key: 'value' });

getObject().then(obj => console.log(obj));

That code works fine if run with mode: development (or with node directly) but breaks when run with
mode: production

What is the expected behavior?
The compiled result should be something like this:
Promise.resolve({
    key: "value"
}).then(e => console.log(e))

Other relevant information:
webpack version:  4.20.2
Node.js version:  8.11.2
Operating System: macOS High Sierra 10.13.6 (17G65)
Additional tools: babel

setting optimization.minimize to false would fix it. Seems to be bug of uglifyjs-webpack-plugin

Better switch on terser-webpack-plugin


CMAKE_CXX_COMPILER not set, after EnableLanguage

I'm trying to compile machine on a Windows 11 ARM64 Virtual Machine running on Mac M1.  Pretty close except I'm getting these errors:

Any idea of how and where to set the CMAKE_CXX_COMPILER and CMAKE_C_COMPILER variables?  I have CMake installed on my machine but is there any other compiler that I also need to compile this beyond the .NET stuff?

Unfortunately, Machine doesn't currently support Windows ARM64 for functionality with native dependencies. This includes the Sentencepiece tokenizer and the Thot statistical machine translation engine. I simply don't have an ARM64 system to test it on. Make sure that you have the MSVC C++ ARM64 Build Tools installed. Also, make sure that the version of CMake that you have installed supports building on ARM64.

Hey @ddaspit
Finally back on this and made some progress after installing the ARM64 build tools and CMAKE in Visual Studio.  The error I get now is:
Error	MSB3073	The command "cmake -S C:\Users\terrauser\Documents\GitHub\machine\src\SIL.Machine.Tokenization.SentencePiece\..\sentencepiece4c -B C:\Users\terrauser\Documents\GitHub\machine\src\SIL.Machine.Tokenization.SentencePiece\..\sentencepiece4c\build" exited with code 9009.

What is the output of running the following command?
cmake --build .\sentencepiece4c\build --target sentencepiece4c --config Release

@ddaspit
C:\Users\terrauser\Documents\GitHub\machine\src>cmake --build .\sentencepiece4c\build --target sentencepiece4c --config Release
MSBuild version 17.7.2+d6990bcfa for .NET Framework

  Checking Build System
  sentencepiece-static.vcxproj -> C:\Users\terrauser\Documents\GitHub\machine\src\sentencepiece4c\build\_deps\sentencepiece-build\src\Release\sentencepiece.lib
  sentencepiece_train-static.vcxproj -> C:\Users\terrauser\Documents\GitHub\machine\src\sentencepiece4c\build\_deps\sentencepiece-build\src\Release\sentencepiece_train.lib
  Building Custom Rule C:/Users/terrauser/Documents/GitHub/machine/src/sentencepiece4c/CMakeLists.txt
  sentencepiece4c.vcxproj -> C:\Users\terrauser\Documents\GitHub\machine\src\sentencepiece4c\bin\sentencepiece4c.dll

It looks like those commands are working properly. Where is it failing?

@ddaspit
At the end of a build for the SentencePiece project, I get this:
Error	MSB3073	The command "cmake -S C:\Users\terrauser\Documents\GitHub\machine\src\SIL.Machine.Tokenization.SentencePiece\..\sentencepiece4c -B C:\Users\terrauser\Documents\GitHub\machine\src\SIL.Machine.Tokenization.SentencePiece\..\sentencepiece4c\build" exited with code 9009.

And the build won't go further.  When I hand run that from the console:
cmake -S .\sentencepiece4c\ -B .\sentencepiece4c\build
I get the error (see few messages above above for full dump):
-- Not Found TCMalloc: TCMALLOC_LIB-NOTFOUND

That is a normal message to receive when building on Windows. TCMalloc is only available on Linux. Sentencepiece can build without it. There must be something else causing the error. Delete the build and bin directories in sentencepiece4c, rebuild the SIL.Machine.Tokenization.SentencePiece project, and post the build log.

With the TCMalloc read-herring out of the way, the build error was caused by Visual Studio not being able to find cmake.exe.  After adding that to the path, a restart of Visual Studio, I got a full build completed!
Thanks so much @ddaspit !
Feel free to close this issue after readying.


EbeanLocalDAO vs BaseLocalDAO

I am looking at the use case of BaseLocalDAO here
We also have EbeanLocalDAO class. Should not we use EbeanLocalDAO there?
We have [DatasetDaoFactory](https://github.com/linkedin/datahub/blob/master/gms/factories/src/main/java/com/linkedin/gms/factory/dataset/DatasetDaoFactory.java) which is EbeanLocalDAO instance.

It can be BaseLocalDAO or EbeanLocalDAO as DatasetDaoFactory returns EbeanLocalDAO
Any specific reason why EbeanLocalDAO is needed here ?

why DatasetDaoFactory returns EbeanLocalDAO? what's the relationship between the factory and implementation?
BaseLocalDAO is an abstract class, should its subclass(EbeanLocalDAO) be used while it has been built?

Theoretically it should be BaseLocalDAO everywhere except in the factory when the actual implementation (EbealLocalDAO) is created. I'd say we should probably change DatasetDaoFactory to return BaseLocalDAO instead.

+1, unless we ever want specific methods on EbeanLocalDAO (just as List has get(int), where as Collection does not).
In this case I believe their public interfaces are the same, so yes we should prefer the parent type.


Error due to multiple tenants

I am trying to follow the code on this page and when I try to execute code for # tutorial/01-create-workspace.py, I get login error as I have access to multiple tenants.
How do I modify the code?

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

ID: 93ab763e-565b-17d9-744f-4efbdc73b3d9
Version Independent ID: 2d591a5a-80a9-74a8-7876-aecf59bfbf17
Content: Tutorial:  Get started machine learning - Python - Azure Machine Learning
Content Source: articles/machine-learning/tutorial-1st-experiment-sdk-setup-local.md
Service: machine-learning
Sub-service: core
GitHub Login: @aminsaied
Microsoft Alias: amsaied

Thanks for the feedback! We are currently investigating and will update you shortly.

@thecpshah Can you please share the error message? It may be that you can provide the auth argument to the create method: see this documentation
This notebook has examples of using different auth options:
https://github.com/Azure/MachineLearningNotebooks/blob/master/how-to-use-azureml/manage-azureml-service/authentication-in-azureml/authentication-in-azureml.ipynb

I tried to use tenant-id in authentication and still the same problem.
My code is below:
# tutorial/01-create-workspace.py
from azureml.core.authentication import InteractiveLoginAuthentication
from azureml.core import Workspace

interactive_auth = InteractiveLoginAuthentication(tenant_id="TENANT_ID")

ws = Workspace(subscription_id="SUBSCRIPTION_ID",
               resource_group="aml",
               workspace_name="cps",
               auth=interactive_auth)

The error I get is:
You are currently logged-in to XYZ tenant. You don't have access to ABC subscription, please check if it is in this tenant.  All the subscriptions that you have access to in this tenant are =

Now, I tried to follow tutorial-1st-experiment-sdk-train.ipynb on compute instance.
I modified the code as below:
from azureml.core.authentication import InteractiveLoginAuthentication

interactive_auth = InteractiveLoginAuthentication(tenant_id="123")

This gives a code which I need to enter to sign in and select my company account. The login works and the code below detects the workspace I have created.
from azureml.core import Workspace
ws = Workspace.from_config()

However, I cannot find the config file when I cloned the tutorial repo.

So the problem is as follows:

On my local machine, I have installed pip install azureml-sdk. By default, it picks up tenant-ID = 456 and looks for subscription = ABC. When I explicitly declare the tenant-ID = 123, it still detects tenant-ID = 456.

On cloud compute instance, the same problem but when I explicitly declare tenant-ID = 123, it works.

Hope this helps to identify the problem.

On my laptop, I also get the following error:
Failure while loading azureml_run_type_providers. Failed to load entrypoint hyperdrive = azureml.train.hyperdrive:HyperDriveRun._from_run_dto with exception (flake8 3.8.3 (c:\users\chintan.b.shah\anaconda3\lib\site-packages), Requirement.parse('flake8<=3.7.9,>=3.1.0; python_version >= "3.6"')).

#assign:@sdgilley

A couple thoughts:

After using interactive_auth = InteractiveLoginAuthentication(tenant_id="123"), I usually have to run the code twice for it to work. Not entirely sure why — there must be something about creds needing to be cached somewhere. An alternative is to use DefaultAzureCredential and explicitly log in to a specific tenant using the Azure CLI.
You may safely ignore the "Failure while loading ..." warnings. These are a known bug in the SDK, and are actively being looked into. However, they shouldn't impact your runs.

@thecpshah - can you verify that executing the code twice works for you?

@thecpshah - what did you do differently that the local version now works?  Wasn't that what your first problem was?  Are you saying that adding interactive_auth now works locally?

Update:
From my local machine, both the following code blocks work:
from azureml.core import Workspace
ws = Workspace(subscription_id="ABC",
               resource_group="aml",
               workspace_name="aml")

print(ws.name)

and
from azureml.core import Workspace
ws = Workspace.create(name='testaml123',
                      subscription_id='ABC',
                      resource_group='testaml123',
                      create_resource_group=True,
                      location='West Europe')
print(ws.name)

I think I did the following steps as well:

Re-installed Anaconda

Created a conda env and installed relevant packges

Followed these:

3a. Connect-AzureRmAccount
3b. Get-AzureRmSubscription
3c. Select-AzureRmSubscription -SubscriptionId ABC

Not sure if steps 3a-3c helped.
Any thoughts?

I suspect that selecting your subscription in powershell did help.  Thanks for your info, we'll do some more testing here and then  add something about multi-tenant to the article.
#please-close

I doubt that is the case.
It still does not explain why I need to specify tenant-id when I use Azure ML Notebooks from compute cluster.
Can you please help there?

My suspicion is that in the case of your local runs, it is defaulting to the subscription you activated in PowerShell.  This would have nothing to do with using the compute instance.
Or are you saying that the notebook doesn't work on a local Jupyter instance?  I thought when you said notebook you meant on the compute instance?


rust-analyzer is not showing variable names in LSP when used with neovim or vs code.

Previously, code completion used to show all the variables present in the current method/code block, however since the latest release it is no longer showing them.

I can't reproduce on 7d1015b8d177a02dff03d2c70bc74e5d4ed34335. Can you try in a new project?

It's working in a new project? Interesting! Do I need to clean/clear some kind of cache?

Nope, the server is not crashing. I'm able to see all the other stuff like method_names and macros in my code_completion dropdown. Only variables are missing :disappointed: .

I have the same issue on a brand new Neovim 0.6 and 2021-11-29 stable...
Not sure how I can get to the log from nvim?

Same here with Neovim 0.6.  Out of curiosity, I tried with rust-analyzer nightly and a bunch of rust-analyzer releases going back to the start, and they gave the same error.  (I have no experience in this area, I was just trying to narrow down the issue.)

I'm suddenly getting the same error with neovim 0.6 and the latest rust-analyzer as well, not sure where the error lies but it seemingly happened out of nowhere using the built-in LSP and rust-tools, I tried compiling neovim from git but it didn't work either.


<class 'selenium.common.exceptions.TimeoutException'> occured! Retrying..

Looks like cloudflare is detecting firefox webdriver as a bot.
Will let you know when a solution is found.

@fluffyloopy it seems all animepahe domains have adopted cloudflare's ddos guard. So the script may not work anymore. I am currently looking for a workaround. Will update if i find a solution.


[Migrated] [minor issue] pip raises MemoryError

Originally from: https://github.com/Miserlou/Zappa/issues/1742 by eronsdc
Context
I was developing in an environment with very little memory (t3.nano instance). Most packages I had to use pip's --no-cache-dir option so that I would not run out of memory.
Expected/Actual behavior
When it came to zappa deploy dev or zappa update dev there is another pip install (here). But this one does not have pip's --no-cache-dir option so the build was failing with a MemoryError.
Traceback
(venv) [ec2-user@ip-172-31-16-41 test_zappa_lambda]$ zappa update dev
(python-dateutil 2.7.5 (/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/lib/python3.6/site-packages), Requirem                               ent.parse('python-dateutil<2.7.0,>=2.6.1'), {'zappa'})
Calling update for stage dev..
Downloading and installing dependencies..
 - pandas==0.23.4: Using locally cached manylinux wheel
 - numpy==1.15.4: Using locally cached manylinux wheel
 - markupsafe==1.1.0: Using locally cached manylinux wheel
 - sqlite==python36: Using precompiled lambda package
Packaging project as gzipped tarball.
  Cache entry deserialization failed, entry ignored
  Cache entry deserialization failed, entry ignored
  Cache entry deserialization failed, entry ignored
  Cache entry deserialization failed, entry ignored
  Cache entry deserialization failed, entry ignored
  Cache entry deserialization failed, entry ignored
Exception:
Traceback (most recent call last):
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/local/lib/python3.6/site-packages/pip/basecommand.py",                                line 215, in main
    status = self.run(options, args)
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/local/lib/python3.6/site-packages/pip/commands/install                               .py", line 335, in run
    wb.build(autobuilding=True)
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/local/lib/python3.6/site-packages/pip/wheel.py", line                                749, in build
    self.requirement_set.prepare_files(self.finder)
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/local/lib/python3.6/site-packages/pip/req/req_set.py",                                line 380, in prepare_files
    ignore_dependencies=self.ignore_dependencies))
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/local/lib/python3.6/site-packages/pip/req/req_set.py",                                line 620, in _prepare_file
    session=self.session, hashes=hashes)
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/local/lib/python3.6/site-packages/pip/download.py", li                               ne 821, in unpack_url
    hashes=hashes
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/local/lib/python3.6/site-packages/pip/download.py", li                               ne 659, in unpack_http_url
    hashes)
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/local/lib/python3.6/site-packages/pip/download.py", li                               ne 882, in _download_http_url
    _download_url(resp, link, content_file, hashes)
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/local/lib/python3.6/site-packages/pip/download.py", li                               ne 603, in _download_url
    hashes.check_against_chunks(downloaded_chunks)
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/local/lib/python3.6/site-packages/pip/utils/hashes.py"                               , line 46, in check_against_chunks
    for chunk in chunks:
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/local/lib/python3.6/site-packages/pip/download.py", li                               ne 571, in written_chunks
    for chunk in chunks:
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/local/lib/python3.6/site-packages/pip/download.py", li                               ne 560, in resp_read
    decode_content=False):
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/local/lib/python3.6/site-packages/pip/_vendor/requests                               /packages/urllib3/response.py", line 357, in stream
    data = self.read(amt=amt, decode_content=decode_content)
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/local/lib/python3.6/site-packages/pip/_vendor/requests                               /packages/urllib3/response.py", line 314, in read
    data = self._fp.read(amt)
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/local/lib/python3.6/site-packages/pip/_vendor/cachecon                               trol/filewrapper.py", line 63, in read
    self._close()
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/local/lib/python3.6/site-packages/pip/_vendor/cachecon                               trol/filewrapper.py", line 50, in _close
    self.__callback(self.__buf.getvalue())
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/local/lib/python3.6/site-packages/pip/_vendor/cachecon                               trol/controller.py", line 275, in cache_response
    self.serializer.dumps(request, response, body=body),
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/local/lib/python3.6/site-packages/pip/_vendor/cachecon                               trol/serialize.py", line 55, in dumps
    "body": _b64_encode_bytes(body),
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/local/lib/python3.6/site-packages/pip/_vendor/cachecon                               trol/serialize.py", line 12, in _b64_encode_bytes
    return base64.b64encode(b).decode("ascii")
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/lib64/python3.6/base64.py", line 58, in b64encode
    encoded = binascii.b2a_base64(s, newline=False)
MemoryError
Oh no! An error occurred! :(

==============

Traceback (most recent call last):
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/local/lib/python3.6/site-packages/zappa/cli.py", line                                2712, in handle
    sys.exit(cli.handle())
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/local/lib/python3.6/site-packages/zappa/cli.py", line                                509, in handle
    self.dispatch_command(self.command, stage)
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/local/lib/python3.6/site-packages/zappa/cli.py", line                                556, in dispatch_command
    self.update(self.vargs['zip'], self.vargs['no_upload'])
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/local/lib/python3.6/site-packages/zappa/cli.py", line                                891, in update
    self.create_package()
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/local/lib/python3.6/site-packages/zappa/cli.py", line                                2185, in create_package
    venv=self.zappa.create_handler_venv(),
  File "/home/ec2-user/src/zappa_builds/test_zappa_lambda/venv/local/lib/python3.6/site-packages/zappa/core.py", line                                426, in create_handler_venv
    raise EnvironmentError("Pypi lookup failed")
OSError: Pypi lookup failed

==============

Need help? Found a bug? Let us know! :D
File bug reports on GitHub here: https://github.com/Miserlou/Zappa
And join our Slack channel here: https://slack.zappa.io
Love!,
 ~ Team Zappa!

Possible Fix
when I add --no-cache-dir option here, it works again. However, I am not sure if this is the correct thing to do? Is there any pros or cons to using --no-cache-dir option ?
I assume it will take longer to install packages? On the other hand, my particular case is probably quite a edge case. I doubt there is many people developing in low memory environments.
It would be possible to have a try/except block which tries to execute pip without --no-cache-dir option and if MemoryError, it would re run with --no-cache-dir option?
Can do a PR, but feel free to ignore if it doesn't make any sense! Any feedback would be valued.
Steps to Reproduce

find an enviroment with low memory
create venv and activate
add pandas, flask and zappa to requirements.txt
pip install -r requirements.txt should fail with MemoryError
pip install --no-cache-dir -r requirements.txt should pass
do zappa init and create an enviroment called dev
zappa deploy dev and/or zappa update dev should fail

Your Environment
t3.nano with Amazon linux
pip==9.0.1
zappa==0.47.1

your local pc seems to be out of memory, not considered a zappa issue.
closing.


Subdue the new top bar colors

A new top bar was added in #250. Let's subdue the colors in it a bit (same as the bottom bars which light up on hover) to have it attract less attention.

Fixed in #258 258


[LightGBM] [Fatal] Check failed: static_cast<size_t>(num_total_features_) == io_config.monotone_constraints.size()

When building stacked ensembles in sklearn, sometimes I got an error message in the .out file of Jupyter:
[LightGBM] [Fatal] Check failed: static_cast<size_t>(num_total_features_) == io_config.monotone_constraints.size() at /__w/1/s/python-package/compile/src/io/dataset.cpp, line 314 .
When this happens, the kernel of Jupyter would die.
I used monotone_constraints for the base LightGBM models and they all seemed fine.
Anyone knows what this error means?
Thank you.

Thanks for using LightGBM!
Can you please provide a reproducible example, including information about how you built LightGBM / the version you're using?
That would help us to give you a better answer.

It is a bit complicated. I am using FLAML (https://github.com/microsoft/FLAML) to do automl. For that, I created a few customized learners with monotone constraints, including two lightGBMs, one using GBDT and the other DART.
If I do not request to build an ensemble, the process ran well; however, when I ask for an ensemble with at least one customized LightGBM learner, I got the issue mentioned above - the kernel just died without any error message and there was an error message logged in the .out file of Jupyter.
As far as I know FLAML uses sklearn to build ensembles and it seems that the issue is not due to FLAML, but probably lightGBM itself.
The codes I used to build the customized lightGBM learner is:
class MyMonotonicLightGBMGBDTClassifier(BaseEstimator):
def __init__(self, task = 'binary:logistic', n_jobs = num_cores, **params):

    super().__init__(task, **params)

    self.estimator_class = LGBMClassifier

    # convert to int for integer hyperparameters
    self.params = {
        'n_jobs': params['n_jobs'] if 'n_jobs' in params else num_cores,
        'boosting_type':params['boosting_type'] if 'boosting_type' in params else 'gbdt',
        'learning_rate': params['learning_rate'],
        'min_split_gain': params['min_split_gain'],
        'max_depth': int(params['max_depth']),
        'min_data_in_leaf': int(params['min_data_in_leaf']),
        'min_sum_hessian_in_leaf': params['min_sum_hessian_in_leaf'],
        'subsample': params['subsample'],
        'colsample_bytree':params['colsample_bytree'],
        'n_estimators':int(params['n_estimators']),
        'subsample_freq':int(params['subsample_freq']),
        'reg_lambda': params['reg_lambda'],
        'reg_alpha': params['reg_alpha'],
        'random_state': params['random_state'] if 'random_state' in params else randomseed,
        "monotone_constraints":params['monotone_constraints'] if 'monotone_constraints' in params else monotone,

   }

@classmethod
def search_space(cls, data_size, task):

    space = {
    'max_depth': {'domain': tune.uniform(lower=4, upper=15), 'init_value': 8},
    'subsample_freq': {'domain': tune.uniform(lower=1, upper=10), 'init_value': 5},
    'n_estimators': {'domain': tune.uniform(lower = 50, upper = 800), 'init_value': 200},
    'min_data_in_leaf': {'domain': tune.uniform(lower = 1, upper = 1000), 'init_value': 100},
    'min_sum_hessian_in_leaf': {'domain': tune.loguniform(lower = 0.000001, upper = 0.1), 'init_value': 0.001},
    'subsample': {'domain': tune.uniform(lower = 0.5, upper = 1), 'init_value': 0.67},
    'colsample_bytree': {'domain': tune.uniform(lower = 0.5, upper = 1), 'init_value': 0.9},
    'learning_rate': {'domain': tune.loguniform(lower = 0.001, upper = 1), 'init_value': 0.1},
    'min_split_gain': {'domain': tune.loguniform(lower = 0.000000000001, upper = 0.001), 'init_value': 0.00001},
    'reg_lambda': {'domain': tune.loguniform(lower = 0.000000000001, upper = 1), 'init_value': 1},
     'reg_alpha': {'domain': tune.loguniform(lower = 0.000000000001, upper = 1), 'init_value': 0.000000000001},
    }
    return space

Is there anything wrong?

Are you able to share the data or code that could create a dataset that results in this error? And could you please tell me how you built LightGBM / the version you're using?
There has been a lot of work on monotone constraints stuff in the last few months, so I'd like to narrow things down a bit. I agree with the implication of this issue that that error message is hard to understand, and it should probably be caught and replaced with something a bit easier to digest. But I need some more details before I can tell you why your code hit that and how to avoid it.

Sure I will copy the codes here later tonight.

@flippercy Currently LightGBM does not check the length of features vs. length of monotone constraints before training. But we provide a description in the document of parameter monotone_constraints, which says that you need to specify all features in order. That means the user must provide the constraints of all features, if the monotone constraint is used.


cli: update to support local development with Node16 module resolution

Hey, I just made a Pull Request!
Work towards #7926. This is one of the tricky pieces since the dynamic import()s in the CLI end up being treated as ESM when we switch resolution to Node16. The proposed solution is to switch the local development execution to use ts-node in ESM mode and refactor the imports.
We need to access the exported commands on the dynamically imported module via the default export. This is because we're relying on Node.js's built-in CJS compatibility layer, which is unable to find the named exports. As far as I can tell Node.js fails to do this because it tries to parse the exports from the source file rather than the transpiled code. It reads the .ts files from the filesystem and tries to parse exports.<name> = ... from those, which of course fails. A big downside of this is that type checks and runtime are inconsistent. TypeScript claims that (await import('./build.js')).command works just fine, but at runtime it does not. This still seems to be the best solution as far as I can tell.
Overall this PR is supposed to have no impact just yet, it's just making the future move to support Node16 resolution more smooth.
This is blocked by #12558
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

I wonder if we want to keep this hanging around or if we should create a ticket based off the moduleResolution: bundler stuff that we looked at this morning when that comes around?

Closing as we'll likely end up going down the route of using the new bundler module resolution instead once that is available


Type 'ResolveTask': setter method 'setOutputPath()' should not be annotated with: @Internal

Type 'ResolveTask': setter method 'setOutputPath()' should not be annotated with: @Internal. This behaviour has been deprecated and is scheduled to be removed in Gradle 7.0. See https://docs.gradle.org/6.4.1/userguide/more_about_tasks.html#sec:up_to_date_checks for more details.
Gradle 6.4.1
Java 11

May this be related to problem with something kind a cache?
I removed previous config.
But I cannot generate new file.
It says UP-TO-DATE... even if there is no old file, just removed it. :smile:

@internal annotation removed in #3630


Missing permissions that need to be included in the JSON config for the registration role

"Microsoft.Authorization/locks/write" needs to be included in the permissions otherwise you get an AuthorizationFailed error when trying to perform the AzRegistration with the created service account due to missing the "Microsoft.Authorization/locks/write" permissions with the service user.

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

ID: aacc015e-fe7c-e95a-f8e4-def1a4fb91e2
Version Independent ID: 35d53d5c-0f68-69fa-7b6c-1bae8d3b9b8e
Content: Create a custom role for Azure Stack Hub registration - Azure Stack Hub
Content Source: azure-stack/operator/azure-stack-registration-role.md
Service: azure-stack
GitHub Login: @IngridAtMicrosoft
Microsoft Alias: inhenkel

Thanks for your comment. The feedback has been shared with the content owner for further review. Thanks for your patience.

In-review

This change has been completed.

thanks @IngridAtMicrosoft . Closing this thread based on the above.