Assertion failed in async.lua:108

nvim --version:

NVIM v0.11.0-dev-3643+g0cdeb06db-Homebrew
Build type: Release
LuaJIT 2.1.1720049189

git --version:

git version 2.45.2

Operating system/version:

macOS Sonoma 14.5

Terminal name/version:

wezterm 20240715-080945-c9116830

Steps to reproduce

Save content of Plugin specification file(s) to some.lua
nvim -nu some.lua
:Pckr sync

Actual behaviour
Could't find setting/plugin combo that causes it, seems to be happening even on pretty simple plugin list. Bisecting lead to:
e200b7724ecb0e9c07a32e505592f990266fc819 is the first bad commit.
Error executing Lua callback: ...oune/.local/share/nvim/pckr/pckr.nvim/lua/pckr/async.lua:29: The coroutine failed with this message: ...oune/.local/share/nvim/pckr/pckr.nvim/lua/pckr/async.lua:108: assertion failed!

stack traceback:
        [C]: in function 'assert'
        ...oune/.local/share/nvim/pckr/pckr.nvim/lua/pckr/async.lua:108: in function 'do_clean'
        ...ne/.local/share/nvim/pckr/pckr.nvim/lua/pckr/actions.lua:332: in function 'sync'
        ...ne/.local/share/nvim/pckr/pckr.nvim/lua/pckr/actions.lua:396: in function <...ne/.local/share/nvim/pckr/pckr.nvim/lua/pckr/actions.lua:395>
stack traceback:
        [C]: in function 'error'
        ...oune/.local/share/nvim/pckr/pckr.nvim/lua/pckr/async.lua:29: in function 'step'
        ...oune/.local/share/nvim/pckr/pckr.nvim/lua/pckr/async.lua:52: in function 'run'
        ...oune/.local/share/nvim/pckr/pckr.nvim/lua/pckr/async.lua:110: in function 'cmd_func'
        .../gegoune/.local/share/nvim/pckr/pckr.nvim/lua/pckr/cli.lua:89: in function <.../gegoune/.local/share/nvim/pckr/pckr.nvim/lua/pckr/cli.lua:74>

Expected behaviour
No error, do the sync.
pckr files

Plugin specification file(s)
local function bootstrap_pckr()
  local pckr_path = vim.fn.stdpath('data') .. '/pckr/pckr.nvim'

  if not vim.uv.fs_stat(pckr_path) then
    vim.fn.system({
      'git',
      'clone',
      '--filter=blob:none',
      'https://github.com/lewis6991/pckr.nvim',
      pckr_path,
    })
  end

  vim.opt.rtp:prepend(pckr_path)
end

bootstrap_pckr()

require('pckr').setup({})

require('pckr').add({ 'tpope/vim-repeat' })

I have the same error when trying to install any plugin.
My environment:

nvim:NVIM v0.9.5
Build type: RelWithDebInfo
LuaJIT 2.1.1707061634

git: git version 2.46.0
OS: Fedora Linux 39
Terminal: QTerminal 1.3.0

Steps to reproduce:

Follow Quickstart.

Try to add any plugin. What I've tried:

pckr.lua
local function bootstrap_pckr()
  local pckr_path = vim.fn.stdpath("data") .. "/pckr/pckr.nvim"

  if not (vim.uv or vim.loop).fs_stat(pckr_path) then
    vim.fn.system({
      'git',
      'clone',
      "--filter=blob:none",
      'https://github.com/lewis6991/pckr.nvim',
      pckr_path
    })
  end

  vim.opt.rtp:prepend(pckr_path)
end

bootstrap_pckr()

require('pckr').add{
  -- My plugins here
  -- 'foo1/bar1.nvim';
  -- 'foo2/bar2.nvim';
  'mbbill/undotree';
  { 'nvim-treesitter/nvim-treesitter', run = ':TSUpdate' },
}

Error and stack traceback
Error detected while processing /home/user/.config/nvim/init.lua:
E5113: Error while calling lua chunk: ...user/.local/share/nvim/pckr/pckr.nvim/lua/pckr/async.
lua:108: assertion failed!
stack traceback:
        [C]: in function 'assert'
        ...user/.local/share/nvim/pckr/pckr.nvim/lua/pckr/async.lua:108: in function 'install'

        /home/user/.local/share/nvim/pckr/pckr.nvim/lua/pckr.lua:52: in function 'add'
        /home/user/.config/nvim/lua/default/pckr.lua:19: in main chunk
        [C]: in function 'require'
        /home/user/.config/nvim/lua/default/init.lua:1: in main chunk
        [C]: in function 'require'
        /home/user/.config/nvim/init.lua:1: in main chunk

I have noticed that I am no longer getting this assertion, instead pckr (sync) works on first invocation after starting nvim only. Consequent runs result in only pckr.nvim being updated (with all other plugins not listed at all).
I am not sure if that's anyhow related to original issue, so please close it if you believe those are unrelated.

I just migrated my configuration from packer to pckr within the past hour or two, and received this error among several others. This error, concerns me the most out of the batch, as it is correlated with the internals of pckr itself, and not external packages.

I've never once had this issue or any similar issue. I'm not sure how to go about debugging this.

I've never once had this issue or any similar issue. I'm not sure how to go about debugging this.

I am running Kali Linux Rolling Release, for which Neovim is installed from, if that is any help.
This issue could be caused by the stale remnants of the packer installation. Like cache.

Do you know how Kali linux builds Nvim?

Correction: I thought I was running NeoVIM installed from the package repo, which would have given me NeoVIM version 9.5, but it appears I was mistaken, and NeoVIM was manually built and installed with version 10.0.
I will pull updates from sources and perform another build. This will bump my minor version up from 10 to 10.2.

Error executing luv callback:
...user/.local/share/nvim/pckr/pckr.nvim/lua/pckr/async.lua:29: The coroutine failed with this message: vim/shared.lua:0: s: expected string, got nil
stack traceback:
        [C]: in function 'error'
        vim/shared.lua: in function 'validate'
        vim/shared.lua: in function 'gsplit'
        vim/shared.lua: in function 'split'
        .../share/nvim/pckr/pckr.nvim/lua/pckr/plugin_types/git.lua:276: in function 'resolve_tag'
        .../share/nvim/pckr/pckr.nvim/lua/pckr/plugin_types/git.lua:317: in function 'checkout'
        .../share/nvim/pckr/pckr.nvim/lua/pckr/plugin_types/git.lua:508: in function 'update'
        .../share/nvim/pckr/pckr.nvim/lua/pckr/plugin_types/git.lua:552: in function 'updater'
        ...os/.local/share/nvim/pckr/pckr.nvim/lua/pckr/actions.lua:229: in function <...os/.local/share/nvim/pckr/pckr.nvim/lua/pckr/actions.lua:219>
stack traceback:
        [C]: in function 'error'
        ...ser/.local/share/nvim/pckr/pckr.nvim/lua/pckr/async.lua:29: in function 'cb'
        ...ser/.local/share/nvim/pckr/pckr.nvim/lua/pckr/async.lua:68: in function 'callback'
        ...user/.local/share/nvim/pckr/pckr.nvim/lua/pckr/jobs.lua:25: in function 'on_exit'
        /usr/local/share/nvim/runtime/lua/vim/_system.lua:300: in function </usr/local/share/nvim/runtime/lua/vim/_system.lua:270>
Press ENTER or type command to continue

I am going to be looking into this some more. I just got a feeling it is somehow something small that is causing the error message to generate.

I also share this issue, running Fedora41. It may be of note that coroutine.running() seems to never return nil on my build, even in my init.lua. I don't know what the assert is there for, so I can't promise stability, but commenting out the assert allowed pckr to be usable again.

I'm guessing fedora builds LuaJIT with 5.2 compat enabled.
Might not be the same issue as everyone else. People see async in the error and just think it's the same thing even though the error message is different.

hm, interesting, apologies if this isn't the same issue, but the error appeared to stem from the same line, async.lua:108.
Running :Pckr sync produces the following:
Error executing Lua callback: ...user/.local/share/nvim/pckr/pckr.nvim/lua/pckr/async.lua:108: assertion
failed!
stack traceback:
        [C]: in function 'assert'
        ...user/.local/share/nvim/pckr/pckr.nvim/lua/pckr/async.lua:108: in function 'cmd_func'
        ...e/user/.local/share/nvim/pckr/pckr.nvim/lua/pckr/cli.lua:89: in function <...e/user/.local/sha
re/nvim/pckr/pckr.nvim/lua/pckr/cli.lua:74>

Neovim needs to be built with Lua 5.1. nothing newer. And preferably LuaJIT. I know fedora has packaged LuaJIT with a 5.2 compat flag enabled which can cause issues (like this).

I shouldn't have been so eager to respond, regardless of the eagerness to find a solution to the problem. Yes, Kali did upgrade to Luajit 5.2, but this would have no effect on the build of nvim as long as luajit 5.1 is set as the requirement. Which it is in cmake/FindLuaJit.cmake.
cmake/FindLuajit.cmake
find_path2(LUAJIT_INCLUDE_DIR luajit.h
          PATH_SUFFIXES luajit-2.1)
  list(APPEND LUAJIT_NAMES libluajit libluajit-5.1)
  list(APPEND LUAJIT_NAMES luajit-5.1)

Furthermore, the init.el file was copied from Kali Linux to my OpenBSD desktop for testing. The OpenBSD distribution of NeoVIM is maintained with a more recent release of NVIM, so it is simply installed from the package manager. Regardless of being on a completely different operating system, and installed onto that system in a completely different manner, the same set of errors occurred. This rules out completely, or in the least significant lowers, the chance of the error being derived from an improper compilation method.
There still is the potential for the error being a result of the configuration file itself, which has been reviewed several times without finding fault.  Admittedly, the file needs to be cleaned up, but was sound enough to run without error previously. To allow for testing it out, I have created a public gist with the contents of it.
https://gist.github.com/anoduck/643c955ff98188b19e206d9ce34a1341
Using it should reproduce the error seen and reported on this thread, and that error should be encountered upon first run.
Below is the screenshot of the error occurring on the first run on my OpenBSD Desktop.

So, now we have a means to reproduce the error and therefore can work towards its elimination.

Also note LuaJIT can be built with some 5.2 features using DLUAJIT_ENABLE_LUA52COMPAT (see https://luajit.org/extensions.html). If it has then coroutine.running() will never be nil.
I know fedora in the past has packaged LuaJIT with this flag.

Oh just looked at your error. It has nothing to do with async.lua, the problem is in git.lua line 276. The tag resolution logic probably has an issue.

@lewis6991 Do you want me to open up a different issue report?

I've done a large overhaul in #42 and I think this issue has become quite stale with lots of other users using it to report other problems. Closing and locking. Please raise more specific issues with enough information to debug.

@anoduck: your issue should be fixed in https://github.com/lewis6991/pckr.nvim/commit/3554de23ff49236e1f80924912473da5328b306b

@sage-etcher: your issue should be fixed in https://github.com/lewis6991/pckr.nvim/commit/dec2361b76478eea7503c89c9be4d1576cf59c22


[feature] psr-2 code style fix

Codecov Report

Merging #3 into master will increase coverage by 0.03%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master       #3      +/-   ##
============================================
+ Coverage     88.64%   88.67%   +0.03%
  Complexity      185      185
============================================
  Files            14       14
  Lines           370      371       +1
============================================
+ Hits            328      329       +1
  Misses           42       42

Impacted Files
Coverage Δ
Complexity Δ

src/Annotation/Table/Index.php
100% <ø> (ø)
6 <0> (ø)
:arrow_down:

src/Annotation/Column.php
100% <ø> (ø)
13 <0> (ø)
:arrow_down:

src/Annotation/Relation/Inverse.php
89.47% <ø> (ø)
14 <0> (ø)
:arrow_down:

src/Annotation/Relation/Traits/InverseTrait.php
100% <ø> (ø)
2 <0> (ø)
:arrow_down:

src/Annotation/Relation/Embedded.php
100% <ø> (ø)
2 <0> (ø)
:arrow_down:

src/Annotation/Relation/Relation.php
92.3% <ø> (ø)
7 <0> (ø)
:arrow_down:

src/Annotation/Embeddable.php
81.81% <ø> (ø)
8 <0> (ø)
:arrow_down:

src/Annotation/Table.php
100% <ø> (ø)
4 <0> (ø)
:arrow_down:

src/Embeddings.php
80% <ø> (ø)
10 <0> (ø)
:arrow_down:

src/Configurator.php
82% <ø> (ø)
40 <0> (ø)
:arrow_down:

... and 2 more

Continue to review full report at Codecov.

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


Pull request for issue #16 Xconst instruction

#16

add all xconst instructions
add test cases

changes in new pull request.
Closing this PR


Evaluation and Inference of Incremental Learning to Support Heterogeneous Chips

What would you like to be added/modified:
Evaluation and inference in incremental learning can be heterogeneous, and possibly training.
Why is this needed:
Heterogeneous deployment scenarios exist in the actual environment. For example, the evaluation is performed on the NPUA chip and the inference is performed on the NPUB chip.

Since the Evaluation is designed to simulate the Inference phase and choose a better-performing model, Why not unify the deployment of the two scenarios?


Add new invocation context class.

resolves #
Description
Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
[x] I have run changie new to create a changelog entry

Codecov Report
Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (e852e77) 51.07% compared to head (0a29faa) 51.26%.
Report is 1 commits behind head on main.

Files
Patch %
Lines

dbt_common/context.py
85.71%
3 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #52      +/-   ##
==========================================
+ Coverage   51.07%   51.26%   +0.19%
==========================================
  Files          47       49       +2
  Lines        2798     2846      +48
==========================================
+ Hits         1429     1459      +30
- Misses       1369     1387      +18

Flag
Coverage Δ

unit
51.26% <85.71%> (+0.19%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Feature: [dev-8409] dashboard filter refactor

To configure Dashboard filters you now need to drag and drop a filter widget to the visualizations panel and then select the tools icon to configure.

@mpallansch

So legacy configuration is supported but I don't think we should support the edit capability beyond what can be done via the Advanced Editor. changes in dev-8574 should make editing easier. What that would entail is user drags over a filter editor and then goes into advanced editor and assigns all of the indexes of the dashboard.shared filters to that new visualization. It should be done this way as I'm not sure how many edge cases we would run into by trying to do this manually.
I'm not sure I follow the issue?
I'll fix this bug, thanks for catching

@mpallansch

So legacy configuration is supported but I don't think we should support the edit capability beyond what can be done via the Advanced Editor. changes in dev-8574 should make editing easier. What that would entail is user drags over a filter editor and then goes into advanced editor and assigns all of the indexes of the dashboard.shared filters to that new visualization. It should be done this way as I'm not sure how many edge cases we would run into by trying to do this manually.
I'm not sure I follow the issue?
I'll fix this bug, thanks for catching

How would they go about removing their existing filters to recreate them in the current system? Or would they have to recreate the entire dashboard config if they have filters and need to update them?
We can have a meeting to discuss if that's easier, but the need is to be able to configure a dropdown filter a single time, then have it show multiple times on the dashboard


⚠ CrackingItaly has degraded performance

In 4d06cf6, CrackingItaly (https://crackingitaly.to) experienced degraded performance:

HTTP code: 200
Response time: 9274 ms

Resolved: CrackingItaly performance has improved in acdd0cb.


Unique DataValues

RussNelson[CodePlex] There's a bit of a conflict in the definition of DataValues. In MySQL (at least), UNIQUE KEY doesn't consider NULL to be equivalent to NULL. Therefore (in 1.1.1 ODM Spec's definition of DataValues on page 31) rule #2 says quotEach record in this table
must be unique.quot but rule #6 (and others) says quotWhere no offset is used, both of these fields should be set to NULLquot. Once you set any value to NULL, it's automatically unique. I don't think that's what the spec means when it says quotuniquequot.
Instead of using NULL, there should be a value (e.g. the null string or 0) which means quotthis field has no offsetquot or is not derived, or not part of a sample, etc.
As a work-around, I'm going to change the table definition in my database so it doesn't include the values we're otherwise setting to NULL in the UNIQUE KEY.

RussNelson[CodePlex] Like this:
ALTER TABLE DataValues DROP KEY DataValues_UNIQUE_DataValues;
ALTER TABLE DataValues ADD UNIQUE KEY DataValues_UNIQUE_DataValues (DataValue,LocalDateTime,UTCOffset,DateTimeUTC,SiteID,VariableID,CensorCode,Method
ID,SourceID,QualityControlLevelID);


bug in function handler

encountered a repeated failure traced down into conn.go, function handler, in the receive loop where the the log message Response for unknown request with xid # is sent.
existing code is
} else {
			c.requestsLock.Lock()
			req, ok := c.requests[res.Xid]
			if ok {
				delete(c.requests, res.Xid)
			}
			c.requestsLock.Unlock()

			if !ok {
>>				log.Printf("Response for unknown request with xid %d", res.Xid)
			} else {
				_, err := decodePacket(buf[:blen], req.recvStruct)
				req.recvChan <- err
			}
		}

changed the
log.Printf("Response for unknown request with xid %d", res.Xid)

to be
req.recvChan <- errors.New("UNKWNREQ: Response for unknown request with xid " + string(res.Xid))

basically the channel needs a reply, otherwise we just hang
the error message I'm sending back is something you probably want to align with your error handling, but I did need to see this specific error so I could attempt recovery in my client code, in my case I just retry if I get this error
Bill

We experienced the same issue and I have traced down the root cause. When requests are generated from different goroutines several requests may be assigned the same xid due to the fact that conn.lastZxid is not updated right after a request is created, but after a response is received. I am going to submit a pull request to fix that.


catch sync errors from http/s protocols and add abort option on the output

http/s protocol when requesting make a first parse and other actions that are sync, and we need to catch those errors.
Once we make a request and we get the output stream we require a way to abort the request,
even if we destroy the stream the request connections is open and then this can cause some weird
errors like connect ENOBUFS or some failing timeouts.

Hey @sacabuche! I'm liking the out.abort method but I'm not sure about the try/catch wrapping the whole request call, specially if we're not specifying what kind of errors are we expecting to catch, plus no tests to ensure that we're actually catching them.
Can you show an example scenario (codewise) that would make use of this two bits of logic? (Both the .abort() method and the try/catch block)

Hi @tomas I will try to make a different pull, and add the test in each case, sorry for not responding earlier

@sacabuche No news?

@tomas Oh sorry men I will add that, and check if it is still failing


add contentlayer

Please review @huntabyte - should be good now.
The deploy still fails on Vercel, but I can't check those logs. The build locally works for me.

Thanks @multiplehats!


error, unsupported genome: 'hg19'

My used-to-working-fine codes gave me this error. I hope it is temporary. Anyone else has the same?
> setGenome(igv, "hg19")
error, unsupported genome: 'hg19'

Hi Otto,
Sorry for the trouble.   Can you run
sessionInfo()
and provide the results?   That will help me track down the problem.

Paul

On Oct 18, 2019, at 5:22 AM, Otto Bergman<EMAIL_ADDRESS>wrote:
My used-to-working-fine codes gave me this error. I hope it is temporary. Anyone else has the same?

setGenome(igv, "hg19")
error, unsupported genome: 'hg19'

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

hi, Paul, thank you for such a prompt reply.
I restarted a clean session and had the same error. Here is my sessionInfo.
The only suspicious action I can think of is, I updated to macOS Catalina.
/Otto
> sessionInfo()
R version 3.6.1 (2019-07-05)
Platform: x86_64-apple-darwin15.6.0 (64-bit)
Running under: macOS Catalina 10.15

Matrix products: default
BLAS:   /Library/Frameworks/R.framework/Versions/3.6/Resources/lib/libRblas.0.dylib
LAPACK: /Library/Frameworks/R.framework/Versions/3.6/Resources/lib/libRlapack.dylib

locale:
[1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8

attached base packages:
[1] parallel  stats4    stats     graphics  grDevices utils     datasets  methods   base

other attached packages:
 [1] igvR_1.5.34                 BrowserViz_2.7.18           httpuv_1.5.2                jsonlite_1.6
 [5] GenomicAlignments_1.21.7    Rsamtools_2.1.7             Biostrings_2.53.2           XVector_0.25.0
 [9] SummarizedExperiment_1.15.9 DelayedArray_0.11.8         BiocParallel_1.19.4         matrixStats_0.55.0
[13] Biobase_2.45.1              GenomicRanges_1.37.17       GenomeInfoDb_1.21.2         IRanges_2.19.17
[17] S4Vectors_0.23.25           BiocGenerics_0.31.6

loaded via a namespace (and not attached):
 [1] httr_1.4.1               bit64_0.9-7              assertthat_0.2.1         askpass_1.1              BiocFileCache_1.9.1
 [6] blob_1.2.0               BSgenome_1.53.2          GenomeInfoDbData_1.2.1   progress_1.2.2           pillar_1.4.2
[11] RSQLite_2.1.2            backports_1.1.5          lattice_0.20-38          glue_1.3.1               digest_0.6.21
[16] promises_1.1.0           colorspace_1.4-1         Matrix_1.2-17            XML_3.98-1.20            pkgconfig_2.0.3
[21] biomaRt_2.41.9           zlibbioc_1.31.0          purrr_0.3.2              scales_1.0.0             later_1.0.0
[26] Rtsne_0.15               tibble_2.1.3             openssl_1.4.1            GenomicFeatures_1.37.4   randomcoloR_1.1.0
[31] splitstackshape_1.4.8    magrittr_1.5             crayon_1.3.4             memoise_1.1.0            tools_3.6.1
[36] data.table_1.12.2        prettyunits_1.0.2        hms_0.5.1                stringr_1.4.0            V8_2.3
[41] munsell_0.5.0            cluster_2.1.0            AnnotationDbi_1.47.1     compiler_3.6.1           rlang_0.4.0
[46] MotifDb_1.27.0           grid_3.6.1               RCurl_1.95-4.12          VariantAnnotation_1.31.6 rappdirs_0.3.1
[51] bitops_1.0-6             DBI_1.0.0                curl_4.2                 R6_2.4.0                 dplyr_0.8.3
[56] seqLogo_1.51.0           rtracklayer_1.45.6       bit_1.1-14               zeallot_0.1.0            stringi_1.4.3
[61] Rcpp_1.0.2               vctrs_0.2.0              dbplyr_1.4.2             tidyselect_0.2.5

Thanks, Otto.  I am puzzled.  Your versions are quite (but not completely) up to date.  And setGenome(igv, “hg19”) is the most basic test - which (for me) runs daily.
Can I trouble you to upgrade to yesterday’s version,  1.5.36?  For that version I added more genomes.
intall_github(“paul-shannon/igvR”) ought to do it.
Then:
igv <- igvR()
getSupportedGenomes(igv)
"hg38"     "hg19"     "hg18"     "mm10"     "gorgor4"  "pantro4”
"panpan2"  "susscr11" "bostau8"  "canfam3"  "rn6"      "danrer11”
"danrer10" "dm6"      "ce11"     "saccer3"  "tair10"   "pfal3d7”
setGenome(igv, "hg19”)  # works

Paul

On Oct 18, 2019, at 6:10 AM, Otto Bergman<EMAIL_ADDRESS>wrote:
hi, Paul, thank you for such a prompt reply.
I restarted a clean session and had the same error. Here is my sessionInfo.
The only suspicious action I can think of is, I updated to macOS Catalina.
/Otto

sessionInfo()
R version 3.6.1 (2019-07-05)
Platform: x86_64-apple-darwin15.6.0 (64-bit)
Running under: macOS Catalina 10.15

Matrix products: default
BLAS:   /Library/Frameworks/R.framework/Versions/3.6/Resources/lib/libRblas.0.dylib
LAPACK: /Library/Frameworks/R.framework/Versions/3.6/Resources/lib/libRlapack.dylib
locale:
[1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8
attached base packages:
[1] parallel  stats4    stats     graphics  grDevices utils     datasets  methods   base
other attached packages:
[1] igvR_1.5.34                 BrowserViz_2.7.18           httpuv_1.5.2                jsonlite_1.6
[5] GenomicAlignments_1.21.7    Rsamtools_2.1.7             Biostrings_2.53.2           XVector_0.25.0
[9] SummarizedExperiment_1.15.9 DelayedArray_0.11.8         BiocParallel_1.19.4         matrixStats_0.55.0
[13] Biobase_2.45.1              GenomicRanges_1.37.17       GenomeInfoDb_1.21.2         IRanges_2.19.17
[17] S4Vectors_0.23.25           BiocGenerics_0.31.6
loaded via a namespace (and not attached):
[1] httr_1.4.1               bit64_0.9-7              assertthat_0.2.1         askpass_1.1              BiocFileCache_1.9.1
[6] blob_1.2.0               BSgenome_1.53.2          GenomeInfoDbData_1.2.1   progress_1.2.2           pillar_1.4.2
[11] RSQLite_2.1.2            backports_1.1.5          lattice_0.20-38          glue_1.3.1               digest_0.6.21
[16] promises_1.1.0           colorspace_1.4-1         Matrix_1.2-17            XML_3.98-1.20            pkgconfig_2.0.3
[21] biomaRt_2.41.9           zlibbioc_1.31.0          purrr_0.3.2              scales_1.0.0             later_1.0.0
[26] Rtsne_0.15               tibble_2.1.3             openssl_1.4.1            GenomicFeatures_1.37.4   randomcoloR_1.1.0
[31] splitstackshape_1.4.8    magrittr_1.5             crayon_1.3.4             memoise_1.1.0            tools_3.6.1
[36] data.table_1.12.2        prettyunits_1.0.2        hms_0.5.1                stringr_1.4.0            V8_2.3
[41] munsell_0.5.0            cluster_2.1.0            AnnotationDbi_1.47.1     compiler_3.6.1           rlang_0.4.0
[46] MotifDb_1.27.0           grid_3.6.1               RCurl_1.95-4.12          VariantAnnotation_1.31.6 rappdirs_0.3.1
[51] bitops_1.0-6             DBI_1.0.0                curl_4.2                 R6_2.4.0                 dplyr_0.8.3
[56] seqLogo_1.51.0           rtracklayer_1.45.6       bit_1.1-14               zeallot_0.1.0            stringi_1.4.3
[61] Rcpp_1.0.2               vctrs_0.2.0              dbplyr_1.4.2             tidyselect_0.2.5
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

hi, Paul. Thanks. I have upgraded to the latest on github.
> getSupportedGenomes(igv)
 [1] "hg38"     "hg19"     "hg18"     "mm10"     "gorgor4"  "pantro4"  "panpan2"  "susscr11" "bostau8"  "canfam3"  "rn6"
[12] "danrer11" "danrer10" "dm6"      "ce11"     "saccer3"  "tair10"   "pfal3d7"
> setGenome(igv, "hg19")
error, unsupported genome: 'hg19'
> setGenome(igv, "hg38")
error, unsupported genome: 'hg38'

And the sessionInfo is
> sessionInfo()
R version 3.6.1 (2019-07-05)
Platform: x86_64-apple-darwin15.6.0 (64-bit)
Running under: macOS Catalina 10.15

Matrix products: default
BLAS:   /Library/Frameworks/R.framework/Versions/3.6/Resources/lib/libRblas.0.dylib
LAPACK: /Library/Frameworks/R.framework/Versions/3.6/Resources/lib/libRlapack.dylib

locale:
[1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8

attached base packages:
[1] parallel  stats4    stats     graphics  grDevices utils     datasets  methods   base

other attached packages:
 [1] igvR_1.5.37                 BrowserViz_2.7.18           httpuv_1.5.2                jsonlite_1.6
 [5] GenomicAlignments_1.21.7    Rsamtools_2.1.7             Biostrings_2.53.2           XVector_0.25.0
 [9] SummarizedExperiment_1.15.9 DelayedArray_0.11.8         BiocParallel_1.19.4         matrixStats_0.55.0
[13] Biobase_2.45.1              GenomicRanges_1.37.17       GenomeInfoDb_1.21.2         IRanges_2.19.17
[17] S4Vectors_0.23.25           BiocGenerics_0.31.6

loaded via a namespace (and not attached):
 [1] bitops_1.0-6             fs_1.3.1                 usethis_1.5.1            devtools_2.2.1           bit64_0.9-7
 [6] progress_1.2.2           httr_1.4.1               rprojroot_1.3-2          tools_3.6.1              backports_1.1.5
[11] R6_2.4.0                 colorspace_1.4-1         seqLogo_1.51.0           DBI_1.0.0                splitstackshape_1.4.8
[16] withr_2.1.2              tidyselect_0.2.5         prettyunits_1.0.2        processx_3.4.1           bit_1.1-14
[21] curl_4.2                 compiler_3.6.1           cli_1.1.0                desc_1.2.0               rtracklayer_1.45.6
[26] scales_1.0.0             callr_3.3.2              askpass_1.1              rappdirs_0.3.1           stringr_1.4.0
[31] digest_0.6.21            pkgconfig_2.0.3          sessioninfo_1.1.1        dbplyr_1.4.2             BSgenome_1.53.2
[36] rlang_0.4.0              RSQLite_2.1.2            dplyr_0.8.3              VariantAnnotation_1.31.6 RCurl_1.95-4.12
[41] magrittr_1.5             GenomeInfoDbData_1.2.1   Matrix_1.2-17            munsell_0.5.0            Rcpp_1.0.2
[46] stringi_1.4.3            zlibbioc_1.31.0          Rtsne_0.15               pkgbuild_1.0.6           BiocFileCache_1.9.1
[51] grid_3.6.1               blob_1.2.0               randomcoloR_1.1.0        promises_1.1.0           crayon_1.3.4
[56] lattice_0.20-38          GenomicFeatures_1.37.4   hms_0.5.1                zeallot_0.1.0            ps_1.3.0
[61] pillar_1.4.2             biomaRt_2.41.9           pkgload_1.0.2            XML_3.98-1.20            glue_1.3.1
[66] V8_2.3                   data.table_1.12.2        remotes_2.1.0            vctrs_0.2.0              testthat_2.2.1
[71] openssl_1.4.1            purrr_0.3.2              assertthat_0.2.1         later_1.0.0              MotifDb_1.27.0
[76] tibble_2.1.3             AnnotationDbi_1.47.1     memoise_1.1.0            cluster_2.1.0            ellipsis_0.3.0

Let me try to find more symptom.

Thank, Otto.  Let’s figure this out.
A clue may come from the Javascript console.  After I call
R> setGenome(igv, “hg19”)
the console shows:
--- igvApp.js,  initializeIGV
(index):666  actual genome name we will use: hg19

On Oct 18, 2019, at 6:40 AM, Otto Bergman<EMAIL_ADDRESS>wrote:
hi, Paul. Thanks. I have upgraded to the latest on github.

getSupportedGenomes(igv)
[1] "hg38"     "hg19"     "hg18"     "mm10"     "gorgor4"  "pantro4"  "panpan2"  "susscr11" "bostau8"  "canfam3"  "rn6"
[12] "danrer11" "danrer10" "dm6"      "ce11"     "saccer3"  "tair10"   "pfal3d7"
setGenome(igv, "hg19")
error, unsupported genome: 'hg19'
setGenome(igv, "hg38")
error, unsupported genome: 'hg38'

And the sessionInfo is

sessionInfo()
R version 3.6.1 (2019-07-05)
Platform: x86_64-apple-darwin15.6.0 (64-bit)
Running under: macOS Catalina 10.15

Matrix products: default
BLAS:   /Library/Frameworks/R.framework/Versions/3.6/Resources/lib/libRblas.0.dylib
LAPACK: /Library/Frameworks/R.framework/Versions/3.6/Resources/lib/libRlapack.dylib
locale:
[1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8
attached base packages:
[1] parallel  stats4    stats     graphics  grDevices utils     datasets  methods   base
other attached packages:
[1] igvR_1.5.37                 BrowserViz_2.7.18           httpuv_1.5.2                jsonlite_1.6
[5] GenomicAlignments_1.21.7    Rsamtools_2.1.7             Biostrings_2.53.2           XVector_0.25.0
[9] SummarizedExperiment_1.15.9 DelayedArray_0.11.8         BiocParallel_1.19.4         matrixStats_0.55.0
[13] Biobase_2.45.1              GenomicRanges_1.37.17       GenomeInfoDb_1.21.2         IRanges_2.19.17
[17] S4Vectors_0.23.25           BiocGenerics_0.31.6
loaded via a namespace (and not attached):
[1] bitops_1.0-6             fs_1.3.1                 usethis_1.5.1            devtools_2.2.1           bit64_0.9-7
[6] progress_1.2.2           httr_1.4.1               rprojroot_1.3-2          tools_3.6.1              backports_1.1.5
[11] R6_2.4.0                 colorspace_1.4-1         seqLogo_1.51.0           DBI_1.0.0                splitstackshape_1.4.8
[16] withr_2.1.2              tidyselect_0.2.5         prettyunits_1.0.2        processx_3.4.1           bit_1.1-14
[21] curl_4.2                 compiler_3.6.1           cli_1.1.0                desc_1.2.0               rtracklayer_1.45.6
[26] scales_1.0.0             callr_3.3.2              askpass_1.1              rappdirs_0.3.1           stringr_1.4.0
[31] digest_0.6.21            pkgconfig_2.0.3          sessioninfo_1.1.1        dbplyr_1.4.2             BSgenome_1.53.2
[36] rlang_0.4.0              RSQLite_2.1.2            dplyr_0.8.3              VariantAnnotation_1.31.6 RCurl_1.95-4.12
[41] magrittr_1.5             GenomeInfoDbData_1.2.1   Matrix_1.2-17            munsell_0.5.0            Rcpp_1.0.2
[46] stringi_1.4.3            zlibbioc_1.31.0          Rtsne_0.15               pkgbuild_1.0.6           BiocFileCache_1.9.1
[51] grid_3.6.1               blob_1.2.0               randomcoloR_1.1.0        promises_1.1.0           crayon_1.3.4
[56] lattice_0.20-38          GenomicFeatures_1.37.4   hms_0.5.1                zeallot_0.1.0            ps_1.3.0
[61] pillar_1.4.2             biomaRt_2.41.9           pkgload_1.0.2            XML_3.98-1.20            glue_1.3.1
[66] V8_2.3                   data.table_1.12.2        remotes_2.1.0            vctrs_0.2.0              testthat_2.2.1
[71] openssl_1.4.1            purrr_0.3.2              assertthat_0.2.1         later_1.0.0              MotifDb_1.27.0
[76] tibble_2.1.3             AnnotationDbi_1.47.1     memoise_1.1.0            cluster_2.1.0            ellipsis_0.3.0
Let me try to find more symptom.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Thanks Paul. I have little knowledge on Javascript.
I will try it after a system reboot but I am in the middle of something now.
Let me know if there is any test I can do from my end.

Sure - let me help when you have time to pursue this.
Which web browser do you use?   Almost all have an easy command, usually available from a menu, which opens the Javascript console.   Nothing else is needed:  our Javascript code writes messages to the console, and we may be able to figure out what the problem is.  I can add more diagnostic code that will appear there.
If you use chrome, you can open the Javascript console like this:
View -> Developer -> Javascript Console
Thanks for your patience!

Paul

On Oct 18, 2019, at 6:51 AM, Otto Bergman<EMAIL_ADDRESS>wrote:
Thanks Paul. I have little knowledge on Javascript.
I will try it after a system reboot but I am in the middle of something now.
Let me know if there is any test I can do from my end.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Thanks Paul. This is the contents in my Chrome after I initiated igvR().
== localhost addOnDocumentReadyFunction
(index):198    typeof(func): function
(index):203 == after push, count: 1
(index):393 === starting bv.start, state? loading
(index):379 === starting bv.init
(index):232 browserViz.js, initializeWebSocket, uri: ws://localhost:15003/
(index):387 === concluding bv.init
(index):218 23 jan 1:45p
(index):221  doc ready functions, count: 1
(index):224 browserviz.js, calling on ready function
(index):121 === BrowserViz.js, websocket connection now open.
(index):130 === BrowserViz.js, message received: setWindowTitle
(index):264 === BrowserViz.js, dispatchMessage: setWindowTitle
(index):276   dispatching for setWindowTitle
(index):334 ==== entering browserviz.setWindowTitle, whose notion of this is:
(index):335 Object
(index):336 ==== msg:
(index):337 Object
(index):339 Object
(index):285 === BrowserViz send:
(index):286 Object
DevTools failed to parse SourceMap: http://localhost:15003/igv.min.js.map
DevTools failed to parse SourceMap: http://localhost:15003/igv.css.map

Good!  Can you also send me the text which appears in the console when you enter the R command:
R> setGenome(igv, “hg19”)

On Oct 18, 2019, at 8:01 AM, Otto Bergman<EMAIL_ADDRESS>wrote:
Thanks Paul. This is the contents in my Chrome after I initiated igvR().
== localhost addOnDocumentReadyFunction
(index):198    typeof(func): function
(index):203 == after push, count: 1
(index):393 === starting bv.start, state? loading
(index):379 === starting bv.init
(index):232 browserViz.js, initializeWebSocket, uri: ws://localhost:15003/
(index):387 === concluding bv.init
(index):218 23 jan 1:45p
(index):221  doc ready functions, count: 1
(index):224 browserviz.js, calling on ready function
(index):121 === BrowserViz.js, websocket connection now open.
(index):130 === BrowserViz.js, message received: setWindowTitle
(index):264 === BrowserViz.js, dispatchMessage: setWindowTitle
(index):276   dispatching for setWindowTitle
(index):334 ==== entering browserviz.setWindowTitle, whose notion of this is:
(index):335 Object
(index):336 ==== msg:
(index):337 Object
(index):339 Object
(index):285 === BrowserViz send:
(index):286 Object
DevTools failed to parse SourceMap: http://localhost:15003/igv.min.js.map
DevTools failed to parse SourceMap: http://localhost:15003/igv.css.map
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

I don't know what to say. It worked! And I definitely did nothing...

@duleise  I suppose that's good news!   But far better it would be if I could figure out what caused the problem.  Will you let me know if it comes up again?   Along with any other problems you encounter, requests for features you would like to see?

Thank you so much, Paul. What happened today is unexplainable, at least to me. I will surely report it if it comes again.
I have been constantly using your package since before this summer and will most likely continue using it for quite a while. It's been a pleasure.
I have asked about a trivial feature in another thread and you have answered.
Working on a paper now and will definitely thank you in it.


rfc3339 6.2 is not supported on this platform

Solution to issue cannot be found in the documentation.

[X] I checked the documentation.

Issue
Hi,
I'm getting this error in another build: rfc3339 6.2 is not supported on this platform
After some online searching, it seems that that could maybe be fixed by rebuilding the package, but not sure. Would you mind rerendering it and releasing a new version?
Info: https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=1008089&view=logs&jobId=656edd35-690f-5c53-9ba3-09c10d0bea97&j=656edd35-690f-5c53-9ba3-09c10d0bea97&t=986b1512-c876-5f92-0d81-ba851554a0a3
Thanks!
Installed packages
Azure Pipelines

Environment info
Azure pipelines

Sure, worth a try I suppose :)
@conda-forge-admin, please rerender

@BastianZim Done, please confirm if this has resolved the issue.

That fixed it, thank you!


Wolfe site refresh

@naomiblack @ericjim @chalin
Ok, here's my branch. It's not ready for merging yet, I'm still adding some stuff but creating a PR so you an get ahead of reviewing the changes. Will be adding more items tomorrow morning... 👍

Merging with master broke travis :(
Hope someone is fixing this issue?

On my list for today's fixes.

@Foxandxss awesome, thanks 👍

merged


All urls in site index file pointing to localhost

I remember having this problem before. When serving to GitHub Pages, assets aren't found. I've checked my config, the content.html file, and the _site index file.  Here you can add your Google Analytics Tracking code. If you do so, do not
forget to set the include_analytics attribute to true on the _config.yml file -->

Tiffany White

Check Yo Self: A Markdown Grammar Checker for Blog Posts

About Check Yo Self

Check Yo Self has a simple purpose: to check your markdown for grammatical errors and misspellings.

Features

Responsive design

Mobile friendly

You can pick up right were you left off with an account.

For more information, including setup and configuration instructions, head over to The Docs.

For bug reports and feature requests, pop on over to GitHub and leave an issue.

              GitHub Repository

              The Author

As you can see, some of these files are being served via localhost. Not sure how to solve it.
My repo

Fixed it by only building before deploying and commenting out baseurl.


Allow GltfLoader to swap out StandardMaterial.

Objective
Allow GltfLoader to load materials other than StandardMaterial. This allows the default material to be a user defined toon shader, for example.
Solution

Allow GltfPlugin, GltfLoader to specify a generic parameter Material, by default StandardMaterial.

Added FromStandardMaterial that constructs a new material from a StandardMaterial and gltf_extras.
Notable types that implement this are StandardMaterial and ExtendedMaterial<StandardMaterial, impl FromStandardMaterial>, which can serve to extend the StandardMaterial's functionalities.

Testing
TODO
Changelog
Added a generic parameter Material to most Gltf related types.
Added FromStandardMaterial trait that constructs a new material from a StandardMaterial and gltf_extras json string.
Migration Guide
GltfLoader now has a PhantomData field.
Multiple types from the bevy_gltf crate now has a generic with default StandardMaterial.
The breakage should be minimal since no other crate, test or example in bevy is affected by these changes.

@MalekiRe you wanted this as well, correct?

I'm not sure this solves my issue. As described, the PR swaps out every material in a GLTF, and they must all be the same type. That doesn't describe my use case at all:

When loading a GLTF, some materials will be swapped out, while others will not be.
Not all swapped materials will be the same type.

Here's an example: Say I have a fireplace created in Blender. The fireplace has a special "flames" material that uses an animated texture. In Blender, I create a custom property "flames: true" an add it to the material. However, the rest of the fireplace - the bricks and so on - use normal materials.
When I load the model (in my previous non-Bevy engine), I examine the GLTF extras field and decide what type of material to substitute based on the custom properties. For most meshes I leave the material as-is - the standard material is good enough. However, for the flames material, I replace the standard material with the special animated shader material.
There are more complex scenarios. In my blender files, I also have a custom property called "outline", which creates a cartoon outline around the object. This requires two materials (because the outline is a separate pass). There are two ways to accomplish this:

Clone the mesh, and replace the clone's material with the outline shader.
Insert two materials into a single mesh - because of the way Bevy's pipeline works, a mesh with two different material components (which must be different types) will be rendered twice.

As you can see, simply globally replacing the standard material with a different type isn't useful to me at all.

I'm not sure this solves my issue. As described, the PR swaps out every material in a GLTF, and they must all be the same type. That doesn't describe my use case at all:

When loading a GLTF, some materials will be swapped out, while others will not be.
Not all swapped materials will be the same type.

Here's an example: Say I have a fireplace created in Blender. The fireplace has a special "flames" material that uses an animated texture. In Blender, I create a custom property "flames: true" an add it to the material. However, the rest of the fireplace - the bricks and so on - use normal materials.
When I load the model (in my previous non-Bevy engine), I examine the GLTF extras field and decide what type of material to substitute based on the custom properties. For most meshes I leave the material as-is - the standard material is good enough. However, for the flames material, I replace the standard material with the special animated shader material.
There are more complex scenarios. In my blender files, I also have a custom property called "outline", which creates a cartoon outline around the object. This requires two materials (because the outline is a separate pass). There are two ways to accomplish this:

Clone the mesh, and replace the clone's material with the outline shader.
Insert two materials into a single mesh - because of the way Bevy's pipeline works, a mesh with two different material components (which must be different types) will be rendered twice.

As you can see, simply globally replacing the standard material with a different type isn't useful to me at all.

I've made the PR use dynamic typing and untyped handles (still stuck on a few thing so not ready yet.)
I think what we can do on top of this is load the json as an internally tagged enum, register deserializers on the GltfLoader and do the typetag thing.

@MalekiRe you wanted this as well, correct?

Yes

As you can see, simply globally replacing the standard material with a different type isn't useful to me at all.

The new version should fit your use case better.


Support cubemap(cubestrip) for old mobile browsers

Below is known browsers that have unstable canvas 2d, webgl implementation.

Chrome at Android 4.3
Samsung internet 4.x
Samsung internet at Android 5.0.2(galaxy device)
Samsung internet at Android 5.1.1(galaxy note 5)
Samsung internet at Android 5.0(galaxy s5)
Safari at iOS 9.0
Safari at iOS 8.0
ie11

Check if there is an issue on 1x6, 6x1, 2x3, 3x2 cubemap images.

#147 is more specific.


potential ideas of optimizations

discussed with @xgaozoyoe, here are a list of potential optimizations that we want to look at

[ ] using a non-overflow version of non-native field multiplication

currently we use an optimized version to handle overflow in non-native mul; this reduces the number of rows but in the meantime, multiplication takes variable length and is bad for parallelization. We want to consider using a fixed-rows non-optimized mul -- this trades MSMs for parallel witness generation

[ ] customized layouter

the layouter runs in two phases and operates over mock witnesses during the first phase; real witnesses during second phase. The first phase, although does not have any real witnesses, still goes through all the operations that real witnesses are performed over. We may skip these ops.

[ ] remove witness labels

@zhenfeizhang  shall we move this to our asana?

@zhenfeizhang shall we move this to our asana?

oh yeah. I will do it


[DOC] Link to extension_templates folder

Reference Issues/PRs
Fixes #2602
What does this implement/fix? Explain your changes.
Added link to extension_templates in github repo
Does your contribution introduce a new dependency? If yes, which one?
No
What should a reviewer concentrate their feedback on?

Any other comments?

PR checklist

For all contributions

[ ] I've added myself to the list of contributors.
[ ] Optionally, I've updated sktime's CODEOWNERS to receive notifications about future changes to these files.
[ ] I've added unit tests and made sure they pass locally.
[ ] The PR title starts with either [ENH], [DOC] or [BUG] indicating whether the PR topic is related to enhancement, documentation or bug

For new estimators

[ ] I've added the estimator to the online documentation.
[ ] I've updated the existing example notebooks or provided a new one to showcase how my estimator works.

@fkiraly I think one link on a single page should be okay ; max two links but more than that will be a bit weird imo .

@Ris-Bali, thanks.
I think the link you added is broken, kindly check.

okay I'll make the correction

@fkiraly is there any way to test these .rst files . Like to see whether they work

@fkiraly is there any way to test these .rst files . Like to see whether they work

Yes, look at the readthedocs build based on the PR, by clicking "details" next to the readthedocs check.

@fkiraly  link fixed now . Pls Review


Add command line tools for math

Desired behavior

Ignition math has a lot of handy APIs, but they can only be used by writing a C++ program. It would be nice to expose some of these as a handy command line tool. Some nice tools to offer:

Convert degrees :arrows_counterclockwise:  radians
Convert euler angles :arrows_counterclockwise: quaternions
Get the moments of inertia for a shape given its dimensions and mass

Alternatives considered

GUI tools could also be handy. What I currently do for the use cases above is opening a website that does it for me, or opening a calculator, or doing it by hand...
Implementation suggestion

Use ign-tools, see an example on ign-transport.
Commands could look like this:
ign math --quaternion_to_euler "0 0 0 1"

Is this issue closed?

Convert euler angles 🔄 quaternions

Commands could look like this:
ign math --quaternion_to_euler "0 0 0 1"

we have examples for converting between Euler angles and quaternions:

https://github.com/ignitionrobotics/ign-math/blob/ign-math6/examples/quaternion_from_euler.cc
https://github.com/ignitionrobotics/ign-math/blob/ign-math6/examples/quaternion_to_euler.cc

we could use that as a reference when implementing this

Why do I get this error when I run the ruby file in examples ?
Traceback (most recent call last):
	2: from angle_example.rb:23:in `<main>'
	1: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
/usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require': cannot load such file -- ignition/math (LoadError)

Why do I get this error when I run the ruby file in examples ?

@NickNair , please direct questions to http://answers.gazebosim.org. If you believe you found a bug, please ticket a new issue filling the template and explaining how to reproduce your problem.

I'm sorry for posting this here but. Could you tell me how to compile and install the ruby interface library

@chapulina I would like to work on this issue. Could you tell me which files I need to change in order to implement this?


Generate hash list

Some minor problems with directory path in the hashlist dictionary. I fixed it in my pull request. But test keeps failing...

since siyao says she fixed it in her pull request im going to close this


BUG: scipy 1.10.0 crashes when using a large float in skellam distr on apple silicon

Describe your issue.
Scipy 1.10.0 is crashing my script if I use a large float as a parameter for the skellam distribution on apple silicon.
Reproducing Code Example
from scipy.stats import skellam

skellam.pmf(0, 1.0,<PHONE_NUMBER>677555.0)
# or skellam.cdf(0, 1.0,<PHONE_NUMBER>677555.0)

Error message
libc++abi: terminating with uncaught exception of type boost::wrapexcept<boost::math::rounding_error>: Error in function boost::math::itrunc<double>(double): Value<PHONE_NUMBER>677555 can not be represented in the target integer type.
zsh: abort      /usr/bin/python3 /Users/japoco/Programming/model/test.py

SciPy/NumPy/Python version information
blas_mkl_info:   NOT AVAILABLE blis_info:   NOT AVAILABLE openblas_info:     libraries = ['openblas', 'openblas']     library_dirs = ['/opt/arm64-builds/lib']     language = c     define_macros = [('HAVE_CBLAS', None)]     runtime_library_dirs = ['/opt/arm64-builds/lib'] blas_opt_info:     libraries = ['openblas', 'openblas']     library_dirs = ['/opt/arm64-builds/lib']     language = c     define_macros = [('HAVE_CBLAS', None)]     runtime_library_dirs = ['/opt/arm64-builds/lib'] lapack_mkl_info:   NOT AVAILABLE openblas_lapack_info:     libraries = ['openblas', 'openblas']     library_dirs = ['/opt/arm64-builds/lib']     language = c     define_macros = [('HAVE_CBLAS', None)]     runtime_library_dirs = ['/opt/arm64-builds/lib'] lapack_opt_info:     libraries = ['openblas', 'openblas']     library_dirs = ['/opt/arm64-builds/lib']     language = c     define_macros = [('HAVE_CBLAS', None)]     runtime_library_dirs = ['/opt/arm64-builds/lib']

@mborland Not sure if it's Boost or our wrapper, but I can reproduce this on Windows.
from scipy.stats import skellam

skellam.pmf(0, 1.0,<PHONE_NUMBER>677555.0)

Fatal Python error: Aborted

Main thread:
Current thread 0x000008c0 (most recent call first):
  File "C:\Users\mhaberla\Desktop\scipy\scipy\stats\_discrete_distns.py", line 1432 in _pmf
  File "C:\Users\mhaberla\Desktop\scipy\scipy\stats\_distn_infrastructure.py", line 3379 in pmf
  File "C:\Users\mhaberla\AppData\Local\Temp\ipykernel_13728\3470758036.py", line 3 in <cell line: 3>

Yeah I don't think this is specific to an architecture or platform because I just noticed I'm getting this exact same crash on a digital ocean droplet running debian

A quick fix for SciPy would be to change the np.where(x < 0... to np.where(x <= 0... because _boost._ncx2_pdf(2*mu2, 2*(1-x), 2*mu1)*2 has no problem.
https://github.com/scipy/scipy/blob/dde50595862a4f9cede24b5d1c86935c30f1f88a/scipy/stats/_discrete_distns.py#L1424-L1432

I'll have to see what integer type we are trying to convert the double to if the error is coming out of itrunc.

Right now nc is limited to<PHONE_NUMBER> because it is represented by an integer. I could make it as large as<PHONE_NUMBER>854775807 which would fit the OPs case. Is there sensical upper bound to what nc could be?

Fair enough. Linked PR should solve it.

Great - will this fix the CDF, too? I didn't look into whether the CDF uses the PDF in this implementation.

It does now

Fixes for both PDF and CDF have been merged.

Thanks for taking care of this Matt, just to clarify, if the non-centrality parameter exceeded a long long then it would become impossible to implement because we would be unable to enumerate values of nc even in a double.  By which I mean nc + 1 would still be nc.  I assume this issue only effected platforms with a 32-bit int?

Thanks for taking care of this Matt, just to clarify, if the non-centrality parameter exceeded a long long then it would become impossible to implement because we would be unable to enumerate values of nc even in a double. By which I mean nc + 1 would still be nc. I assume this issue only effected platforms with a 32-bit int?

Yes. Are there any systems that define int as 64-bits? I only know that metal systems can go the other way and make it 16-bits.

Yes. Are there any systems that define int as 64-bits? I only know that metal systems can go the other way and make it 16-bits.

Ah no, my bad, I was thinking about size_t.  Ignore me it's getting later here...

This also seems to occur for the noncentral t-districution:
from scipy.stats import nct

nct.cdf(2, 2, float(2**16))

Results in
terminate called after throwing an instance of 'boost::wrapexcept<boost::math::rounding_error>'
  what():  Error in function boost::math::itrunc<double>(double): Value<PHONE_NUMBER> can not be represented in the target integer type.
Aborted

@mborland @jzmaddock we fixed this for ncx, but is the same true for nct?

Reproduced.  We can up the integer type to a long long which will push this well into the long grass, beyond that the implementation becomes impossible/unknown.

Thank you!

As noted in https://github.com/boostorg/math/pull/955 this can only be somewhat fixed: the largest term in the series occurs near the square of the non-centrality parameter.  So we can still only handle non-centrality up to 2^32.  I spent a little time looking through the literature on this today and don't see an obvious way forward.  I also don't see an obvious use case for really large non-centralities ;)

I do wonder how people come across these cases. @jabamiyumeko @agkphysics how did you encounter this?

I was using Pingouin to do statistical tests, but in one case a pair of samples had almost zero variance, such that the effect size was some huge number. I'll also file an issue with them to maybe check whether the variance is too low when calculating effect size.

I do wonder how people come across these cases. @jabamiyumeko @agkphysics how did you encounter this?

I was fitting a model's parameters with scipy.optimize.minimize.

I was fitting a model's parameters with scipy.optimize.minimize.

That would explain things, root finders and function minimisers often generate crazy-out-of-bound values while clomping around looking for "the" solution.  I'll have another quick scan of the literature to see if there are other evaluation methods.

Yeah that is exactly the problem. It happens very rarely, when the gradient estimation is very flat I guess. I “fixed” this on my end by adding bounds to my optimisation.

Thanks @jzmaddock.
If you don't come across other evaluation methods, could it give an error indicating that the function is not implemented for such large values of the parameter? That would be preferable to the crash of ncx2 and a bit more helpful than the message we get with nct. If we receive a report about it in the future, I would just consider it an enhancement that would be nice but does not need to happen on any timeline.

Nod.  I was just thinking that, a domain_error I guess?
Aside: it's ironic but in the root finding case, the older C libraries probably "work" because they tend to fail and just return 0 everywhere once the non-central parameter becomes large.  Benton & Krishnamoorthy papers address this, but the assumption is that the integers values adjacent to the largest terms are representable.

Ah. yes, domain_error sounds appropriate to me. Thanks!


In the postPackage hook，I copied some files to the program root directory, but after npm run make, only the DLL file is left

Pre-flight checklist

[X] I have read the contribution documentation for this project.
[X] I agree to follow the code of conduct that this project uses.
[X] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Electron Forge version
6.1.1
Electron version
24.1.1
Operating system
Windows 10 (1803)
Last known working Electron Forge version
6.1.1
Expected behavior
Hope all files in the root directory are copied
Actual behavior
In the postPackage hook，I copied some files to the program root directory, like this:
postPackage: async (forgeConfig, options) => {
await fs.copy(path.resolve(__dirname, "./packages/xxx/build/Release"), resolve(options.outputPaths[0]));
}
but after npm run make, only the DLL file is left
Steps to reproduce
ditto
Additional information
No response

You can use the additionalFiles field in the package.json file. That's how I resolved it.


GC events changes

interpret more fields from the perheap hist event;
add more types for the mark event for .net 6;

this runtime change requires this perfview change otherwise you'll get an exception for the GCStats view.

@dotnet/gc PTAL

@brianrob my runtime changes would require perfview users to get a new version (that includes this change) to work with .NET 6 traces in order to see the GCStats view, are you ok with it?

Is there a way to detect and report this to the user?  Presumably the exception could just do that.  Ideally, we make things just work and you don't get the new functionality, but I'm assuming that there was a reason to break compat at the event level?

Is there a way to detect and report this to the user?

without code changes in perfview, all you see is an exception with a callstack that parses the GCMarkWithType event when you try to open the GCStats view. not sure if you meant "Is there a way to detect and report this to the user" in perfview (it would require changes to do that and that would require folks to get a new version anyway). if this is a serious compatibility concern I could bump up the version of the event so without an updated perfview you won't be able to interpret this event for 6.0 traces but will be able to for previous runtime versions

From PerfView's perspective, probably not a huge deal.  For the runtime, though, we document the events, and so I wonder if we should increment the version just to be sure that those who parse the events themselves have this info.  At the same time, I don't see a change to the parser - are the event fields staying the same, but interpretation changing?
Also, will .NET 5 and below (including Framework) continue functioning?  From the code change, it looks like yes, since I don't see any changes to the event payloads themselves, but want to make sure.

all previous versions of runtime should still work. I added more values to an enum for a field of that event so the array I allocated in perfview (more preciously TraceEvent) to store info for this field is not big enough now (so I'm adding a bigger array now). as long as the field doesn't use the new enum value it should work fine.


Modify plot_friends.py

Add compatibility with JSON data
Improve gitignore

Signed-off-by: Tushar Mittal<EMAIL_ADDRESS>

Yes, we can make an examples folder wherein we can include some sample data, so that the user can also run it without using his own data.


Fix driver tests

provides fallback for testing on gpus that are not yet public

pushed it in manually, this one had some bit rot


It's still not serving and opening the default page

$  gulp build serve --dev.
[17:19:03] Using gulpfile C:\Dev\buybe4me\gulpfile.js
[17:19:03] Starting 'build'...
[17:19:03] Starting 'serve'...
[17:19:03] Starting 'clean'...
[17:19:03] Starting 'parallel'...
[17:19:03] Starting 'watch'...
[17:19:03] Starting 'livereload'...
[17:19:04] Server started http://localhost:8080
[17:19:04] LiveReload started on port 35729
[17:19:04] Finished 'clean' after 237 ms
[17:19:04] Starting 'parallel'...
[17:19:04] Starting 'lesslint'...
[17:19:04] Starting 'tslint'...
[17:19:04] Finished 'lesslint' after 426 ms
[17:19:04] Finished 'tslint' after 521 ms
[17:19:04] Finished 'parallel' after 523 ms
[17:19:04] Starting 'parallel'...
[17:19:04] Starting 'less'...
[17:19:04] Starting 'ts'...
[17:19:04] less all files 443 B
[17:19:06] ts all files 11.72 kB
[17:19:06] Finished 'less' after 2.28 s
[17:19:06] Finished 'ts' after 2.29 s
[17:19:06] Finished 'parallel' after 2.3 s
[17:19:06] Starting 'lib'...
[17:19:06] lib all files 1.2 MB
[17:19:07] Finished 'lib' after 188 ms
[17:19:07] Starting 'index'...
[17:19:07] gulp-inject 3 files into index.html.
[17:19:07] Finished 'index' after 78 ms
[17:19:07] Starting 'typedoc'...
Rendering [========================================] 100%
[17:19:11] Finished 'typedoc' after 4.55 s
[17:19:11] Finished 'build' after 7.88 s

This is it nothing more...

It won't open the browser automatically for you.
Have you tried opening a new tab and entering the URL http://localhost:8080?

Cool! Add it to install.md please

Done.


pipenv lock: hangs when internet is slow. So is it ok to skip pipenv lock and do it once in a while when we have good internet speed

Recently i observed that pipenv lock gets hanged.
I have read about the issue at many places
But practically i found on my pc that when its connected to slow internet speed (200-700 kbps) it stucks and when it is connected to good internet speed (2-3 Mbps) it works fine
Also i found that whenever ever i do pipenv lock it downloads 200-300 Mb data. Thats fine but just to know
So what i want to do is whenever i install a new package i want to skip the pipfile.lock getting updated using --skip-lock option
 i.e pipenv install --skip-lock somepackage

Later when i am connected to good internet speed i can do
pipenv lock

Locking [dev-packages] dependencies…
✔ Success!
Locking [packages] dependencies…
✔ Success!

I am just curious will this have any drawback in terms of identifying the versions installed at the time of installation

This properly describes the issue here: #3827
It's much slower than just the speed it would take to download the amount of data that ends up getting downloaded, because there is a lot of back and forth to install the packages.
It's like SQL where you have 50 queries due to an N+1 query issue. If you're close to the database, it might not be noticeably slow, but once you're far away from the database, it's sloooooow.

I generated a flamegraph of what happens inside the main function of the resolver.py, see: https://github.com/pypa/pipenv/issues/3827#issuecomment-784446651
on a poor internet connection pipenv install's bottleneck is downloading stuff

I think the answer to the OP is yes it should be fine to do this when your internet connection is having slowness.


Update dependencies

There is nelmio/alice 2.0.0 available. Bundle should support it.

+1

See https://github.com/hautelook/AliceBundle/pull/58.

Done and the v1.0.0 beta has been released.


Add back curl/deps for celery

Otherwise we get errors:
2023-08-09T12:44:26.98+0100 [APP/PROC/WEB/0] ERR raise ImportError('The curl client requires the pycurl library.')
2023-08-09T12:44:26.98+0100 [APP/PROC/WEB/0] ERR ImportError: The curl client requires the pycurl library.
2023-08-09T12:44:29.26+0100 [APP/PROC/WEB/0] ERR scripts/run_app_paas.sh: line 45: kill: (62) - No such process

It's a good question - will try it out 🤞

@sakisv good call - I built and deployed dcda8842c26c96e9f95306c3b9e2120dccd5ead3 on preview and it does pass the template-preview functional tests, so that seems a better option 👍


[GURPS] Update

Changes / Comments
Files Changed
GURPS/gurps.html
Changes

Removed the select attribute in the option tag, added in version 2ba6f9635cff2eca5ece697a943fa88f21a4f040.
Because of this bug: https://app.roll20.net/forum/permalink/10269294/.

Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

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

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

Character Sheet Info Roll20 Internal Use only.


Link libpthread into the spawn_worker trampoline

It apparently leads to race conditions if libpthread and libc aren't loaded at the same time. In this case a library linking against libpthread is dlopen()'ed dynamically from the trampoline.
It led to interesting libc memory corruptions, like in getaddrinfo:
#2  0x00007fe45328df67 in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fe4533a05d0 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:196
#3  0x00007fe453296329 in malloc_printerr (ar_ptr=0x7fe4535dc760 <main_arena>, ptr=<optimized out>, str=0x7fe4533a06d8 "double free or corruption (out)", action=3) at malloc.c:4967
#4  _int_free (av=0x7fe4535dc760 <main_arena>, p=<optimized out>, have_lock=0) at malloc.c:3843
#5  0x00007fe453283247 in _IO_new_fclose (fp=0x7fe448001d20) at iofclose.c:84

etc. on older glibc versions.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 67.76%. Comparing base (f63cff5) to head (5321f68).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #452   +/-   ##
=======================================
  Coverage   67.76%   67.76%
=======================================
  Files         193      193
  Lines       24476    24476
=======================================
  Hits        16585    16585
  Misses       7891     7891

Components
Coverage Δ

crashtracker
19.34% <ø> (ø)

datadog-alloc
98.76% <ø> (ø)

data-pipeline
51.45% <ø> (ø)

data-pipeline-ffi
0.00% <ø> (ø)

ddcommon
85.24% <ø> (ø)

ddcommon-ffi
74.93% <ø> (ø)

ddtelemetry
56.09% <ø> (ø)

ipc
81.27% <ø> (ø)

profiling
78.09% <ø> (ø)

profiling-ffi
60.05% <ø> (ø)

serverless
0.00% <ø> (ø)

sidecar
36.58% <ø> (ø)

sidecar-ffi
0.00% <ø> (ø)

spawn-worker
54.98% <ø> (ø)

trace-mini-agent
69.12% <ø> (ø)

trace-normalization
97.79% <ø> (ø)

trace-obfuscation
95.74% <ø> (ø)

trace-protobuf
30.76% <ø> (ø)

trace-utils
78.29% <ø> (ø)


What options can change to hid prefix class of svg file?

The className of text tag has named virtualBox_TextInSvg, but it carry a prefix that is filename after outputed, What should I do?
I want to keep the same classname in svgfile

svgo --disable=prefixIds should disable the prefixIds plugin that prefixes IDs + classes.

Is there a way to only prefix IDs, but not classes? I have a case where the classes should stay as is, but IDs prefixed to avoid conflicts.
Since the config option is named prefixIds you'd think it would only affect IDs in the first place.

How to use prefix only for class ?

@litinskii: Hm, this would probably require code changes in the prefixIds plugin.
Only one method would have to be called then, addPrefixToClassAttr(https://github.com/svg/svgo/blob/master/plugins/prefixIds.js#L212).

@strarsis Thanks for answer. I'm asking this, because I'm trying to migrate from https://github.com/jkphl/svg-sprite, and there was an option like

(https://github.com/jkphl/svg-sprite/blob/master/docs/configuration.md)
and it was very useful, I mean allow to specify if you want to add namespace only for class for example.
I thinks it would be cool if we have some king of options for prefixIds plugin. @strarsis What you think about this ?

@litinskii: You can try the PR here: https://github.com/svg/svgo/pull/1106

@strarsis Thanks will try.

@strarsis seems it work for my case. Thanks.


fix #49

Hi Jacob,
could you specify what this code fixes?
Thanks

Sure,
Here's an example of the dictionary causing problems {'added_at': '2020-05-29T19:36:17Z', 'added_by': {'external_urls': {'spotify': 'https://open.spotify.com/user/*********'}, 'href': 'https://api.spotify.com/v1/users/*********', 'id': '*********', 'type': 'user', 'uri': 'spotify:user:*********'}, 'is_local': False, 'primary_color': None, 'track': None, 'video_thumbnail': None} I've replaced my friends id with *'s
the "track" key is None and causes a KeyError on line 135 if song["is_local"]:
I'm not sure why the API returns a faulty dictionary for the last track of a specific playlist as I also tried it with an identical copy of this playlist and that cached fine.

Great, thanks Jacob. I'll merge this now


Fix and more

fixes the patch for guild tooltip and transfers the patch for member list to plain text patch so that it would patch only member list instead of every scrollable list like channels, dms, etc.

Fixed separately


[BUG] Table column mismatches if llm throws exception

Describe the bug
The problem happens, when this line throw an exception and add_raw_output is set to True: https://github.com/argilla-io/distilabel/blob/ed88585a0b60a785ec9a8010a2c69eab22394ca2/src/distilabel/steps/tasks/base.py#L198
When the exception is raise, "distilabel_metadata" is not able to added to the output, which causes this line fail: https://github.com/argilla-io/distilabel/blob/ed88585a0b60a785ec9a8010a2c69eab22394ca2/src/distilabel/pipeline/write_buffer.py#L135
If this happened, pipeline crached. I found that the pipeline hung when recovered from cache, which means cache is corrupted somewhere.
I could submit a pull request but please advise what is the best way to address the issue. (I am currently add the empty output in impute_step_outputs as follows:)
    def _impute_step_outputs(self, batch: "_Batch") -> List[Dict[str, Any]]:
        """Imputes the step outputs columns with `None` in the batch data.

        Args:
            batch: The batch to impute.
        """
        result = []
        for row in batch.data[0]:
            data = row.copy()
            for output in self.step.outputs:
                data[output] = "N/A"
            if isinstance(self.step, Task):
                if self.step.add_raw_output or self.step.add_raw_input:
                    data[DISTILABEL_METADATA_KEY] = {}
            result.append(data)
        return result

Moreover, personally I think the following code could be safer:
if not last_schema.equals(table.schema):
    new_schema = pa.unify_schemas([last_schema, table.schema])
    self._buffer_last_schema[step_name] = new_schema
    table = table.cast(new_schema)

into something like, otherwise cast could fail even if schema are the same except the column order
if not last_schema.equals(table.schema):
    if set(last_schema.names) == set(table.schema.names):
        table = table.select(last_schema.names)
    else:
        new_schema = pa.unify_schemas([last_schema, table.schema])
        self._buffer_last_schema[step_name] = new_schema
        table = table.cast(new_schema)

To Reproduce
See above

**Expected behaviour**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Desktop (please complete the following information):**
 - Package version:
 - Python version:

**Additional context**
Add any other context about the problem here.

@gabrielmbmb do you think it is better to add interface of self.impute_step_outputs at step level?

Hi @zye1996! Yes, I think it makes sense to have impute_outputs as a method in the _Step class. The other change for the schema creation looks good too!


Add "open source" phrase to homepage and community page

Resolves #368

Summary

Use Cases

Checklist

[ ] I have viewed, signed, and submitted the Contributor License Agreement.
[ ] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[ ] I have added an integration test, if necessary.
[ ] I have reviewed the styleguide for guidance on my code quality.
[ ] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

I've chosen not to capitalize "open source" based on Google's "Open Source Comms" style guide: https://opensource.google/docs/comms/style-guide/#:~:text=Open source%3A Don't capitalize,source is not a monolith.


Bug: selection changes to null when selecting text after node selection on mobile devices

Lexical version: 0.5.0

This is actually to be expected on touch devices. Moving from node selection to range selection will require an extra touch. Whilst we can force the adjusted behavior, it leads to strange bugs when you try and do things like drag and drop + resizing. So for those reasons, closing for now as I don't see this as too big an issue.

This is actually to be expected on touch devices. Moving from node selection to range selection will require an extra touch. Whilst we can force the adjusted behavior, it leads to strange bugs when you try and do things like drag and drop + resizing. So for those reasons, closing for now as I don't see this as too big an issue.

Hi there!
I was wondering if this could be fixed, it was working as expected before this commit https://github.com/facebook/lexical/commit/382766a
can you review it?


Pedestrians not working in Synchronous mode

Hello all,
I am creating a scenario where there are multiple pedestrians walking around in the environment. It works completely fine in normal mode. However, when I try this in synchronous mode, pedestrians are spawned but are immediately invisible. I am using world.tick() for every time step, but it still does not work.

Hi, did you manage to solve this issue? I have the same problem.

I have a somewaht similar problem. After having spawned the pedestrian model, I spawned an ai walker controller attached to the pedestrian. But after a few ticks, as the pedestrian disappeared, the ai controller was respawned to a random location near the origin.
I set a tick() right after spawning the pedestrian, and the problem when away.


[Docs] Get-started/prerequisites strange "." after "react" in

Problem description
style bug - there is a . after the link to react in the first ul on http://www.material-ui.com/#/get-started/prerequisites
Steps to reproduce
go here
Images & references

ZOOMING IN NOW

While we're discussing this page:
Should it really be called "prerequisites"? To me that normally refers to this you must have / have installed, rather than things you must know. That would be "prerequisite knowledge, or more simply "required knowledge?
Secondly, is this page really that useful? Is it likely that anyone considering a React gui lib doesn't already know about React or SPAs?
When many users struggle to read and implement the salient technical  prereqs, this page "may attack at any time, we must deal with it". :smile:

"required knowledge?

@mbrookes I agree, that seems to better describe the content.
I'm gonna rename it.


fix typo in check for Texture2D creation

Branch would execute when Create() function returned valid result, instead of the other way around.

Hey @ademets. Thanks for this pull request.


Dart compiler exited unexpectedly after flutter upgrade

Steps to reproduce
I am experiencing the exact same issue as described in #148611 .
The linked issue is closed so couldn't comment there.
Comment says that fix wasn't cherry picked into 3.22.2, but I am using 3.22.3.
Was it cherry picked into 3.22.3 at least? Am I encountering some other issue?
Expected results
Flutter app runs successfully.
Actual results
Flutter app build fails.
Code sample
Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
Unhandled exception:
Crash when compiling:
Concurrent modification during iteration: Instance(length:6) of '_GrowableList'.

#0      ListIterator.moveNext (dart:_internal/iterable.dart:348)
#1      BodyBuilder._unaliasTypeAliasedConstructorInvocations (package:front_end/src/fasta/kernel/body_builder.dart:1640)
#2      BodyBuilder.performDelayedActions (package:front_end/src/fasta/kernel/body_builder.dart:1755)
#3      SourceLoader.buildOutlineExpressions (package:front_end/src/fasta/source/source_loader.dart:2827)
#4      KernelTarget.buildOutlines.<anonymous closure> (package:front_end/src/fasta/kernel/kernel_target.dart:549)
<asynchronous suspension>
#5      withCrashReporting (package:front_end/src/fasta/crash.dart:133)
<asynchronous suspension>
#6      KernelTarget.buildOutlines (package:front_end/src/fasta/kernel/kernel_target.dart:415)
<asynchronous suspension>
#7      IncrementalCompiler.computeDelta.<anonymous closure> (package:front_end/src/fasta/incremental_compiler.dart:367)
<asynchronous suspension>
#8      CompilerContext.clear (package:front_end/src/fasta/compiler_context.dart:139)
<asynchronous suspension>
#9      IncrementalCompiler.compile (package:vm/incremental_compiler.dart:77)

Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.22.3, on Arch Linux 6.6.40-1-lts, locale en_US.UTF-8)
    • Flutter version 3.22.3 on channel stable at /opt/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision b0850beeb2 (2 weeks ago), 2024-07-16 21:43:41 -0700
    • Engine revision 235db911ba
    • Dart version 3.4.4
    • DevTools version 2.34.3

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /home/matija/Android/Sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_SDK_ROOT = /home/matija/Android/Sdk
    • Java binary at: /opt/android-studio/jbr/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.11+0-17.0.11b1207.24-11852314)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /usr/bin/google-chrome-stable

[✓] Linux toolchain - develop for Linux desktop
    • clang version 18.1.8
    • cmake version 3.30.1
    • ninja version 1.12.1
    • pkg-config version 2.1.1

[✓] Android Studio (version 2024.1)
    • Android Studio at /opt/android-studio
    • Flutter plugin version 80.0.2
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.11+0-17.0.11b1207.24-11852314)

[✓] IntelliJ IDEA Community Edition (version 2024.1)
    • IntelliJ at /usr/share/idea
    • Flutter plugin version 79.2.3
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] Connected device (3 available)
    • sdk gphone64 x86 64 (mobile) • emulator-5554 • android-x64    • Android 14 (API 34) (emulator)
    • Linux (desktop)              • linux         • linux-x64      • Arch Linux 6.6.40-1-lts
    • Chrome (web)                 • chrome        • web-javascript • Google Chrome 126.0.6478.182

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Was it cherry picked into 3.22.3 at least? Am I encountering some other issue?

You most probably are hitting the same issue, as the fix doesn't seem to be in 3.22.3 looking at hotfix list.
You can track the commit by referring to https://github.com/flutter/flutter/blob/master/docs/releases/Where's-my-commit.md
The fix most likely will be available in next stable release which will be sometime this month.


Improved UI scaling, and also arena now always has the same scale as the host window.

Sorry which file?

Sorry which file?

Settings_RotwkGeneral.xaml.cs

No idea how that hapened... Fixed now


[LIVY-568][BUILD] Upgrade jackson version to 2.9.8

What changes were proposed in this pull request?
Due to security issues of jackson databind module (https://github.com/FasterXML/jackson-databind/issues/2186) proposing to upgrade jackson version to 2.9.8.
How was this patch tested?
Existing UTs.

Codecov Report

Merging #153 into master will increase coverage by 0.05%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #153      +/-   ##
============================================
+ Coverage     68.59%   68.65%   +0.05%
  Complexity      904      904
============================================
  Files           100      100
  Lines          5662     5662
  Branches        848      848
============================================
+ Hits           3884     3887       +3
+ Misses         1225     1223       -2
+ Partials        553      552       -1

Impacted Files
Coverage Δ
Complexity Δ

...ain/java/org/apache/livy/rsc/driver/RSCDriver.java
78.81% <0%> (+0.84%)
41% <0%> (ø)
:arrow_down:

...cala/org/apache/livy/scalaapi/ScalaJobHandle.scala
55.88% <0%> (+2.94%)
7% <0%> (ø)
:arrow_down:

Continue to review full report at Codecov.

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

Merging to master.


Remove obsolete dependencies

Currently the 4.0 release still relies on older implementations of formatters, these should be removed/updated
See: https://ci.appveyor.com/project/serilog/serilog-sinks-mongodb/branch/master
C:\projects\serilog-sinks-mongodb\src\Serilog.Sinks.MongoDB\Sinks\MongoDB\MongoDBJsonFormatter.cs(62,33): warning CS0672: Member 'MongoDBJsonFormatter.WriteJsonProperty(string, object, ref string, TextWriter)' overrides obsolete
member 'JsonFormatter.Write
JsonProperty(string, object, ref string, TextWriter)'. Add the Obsolete attribute to 'MongoDBJsonFormatter.WriteJsonProperty(string, object, ref string, TextWriter)'.
C:\projects\serilog-sinks-mongodb\src\Serilog.Sinks.MongoDB\Sinks\MongoDB\MongoDBJsonFormatter.cs(50,13): warning CS0618: 'JsonFormatter.JsonFormatter(bool, string, bool, IFormatProvider)' is obsolete: 'The omitEnclosingObject
parameter is obsolete and wil
l be removed in a future Serilog version.'
C:\projects\serilog-sinks-mongodb\src\Serilog.Sinks.MongoDB\Sinks\MongoDB\MongoDBJsonFormatter.cs(79,17): warning CS0618: 'JsonFormatter.WriteJsonProperty(string, object, ref string, TextWriter)' is obsolete: 'Extension of
JsonFormatter by subclassing is o
bsolete and will be removed in a future Serilog version. Write a custom formatter based on JsonValueFormatter instead. See https://github.com/serilog/serilog/pull/819.'

Thanks for the suggestion.


The link in document 'example' was 404

https://github.com/react-community/react-navigation/tree/master/examples/NavigationPlayground

see the Contributors Guide for instructions on running these example apps.

Contributors Guide 404

Thanks for reporting, here's the doc: https://reactnavigation.org/docs/guides/contributors

thanks！


RFC 0092 Return Route --> ACCEPTED; Deadline: 2019.12.16

I have issues with the way the semantics of this decorator introduce coupling between layers of an agent's internals.
From reading through these RFCs I get the sense that all these "features" should be composed into mutually independent layers in an agent's implementation.
The General Patterns section of RFC 0004 seems to imply so.
It also aligns very well with the efforts to enable plugin functionality for a lot of these components.
In particular, a protocol handler should be decoupled from the underlying transport handler. If I were to draw the layers, it would look like this:
|--------------------|
|     Controller     |
|--------------------|
|  Protocol Handers  |
|--------------------|
| Packers/Unpackers  |
|--------------------|
|     Transports     |
|--------------------|

What ~transport effectively does is couple the Protocol Handlers and Transports layers together (or Packers/Unpackers <-> Transports). A higher layer needs to inform the transport layer to release/close the connection on which the incoming message was received if no ~transport decorator was received.
To address this concern, I think an Agent should mark a serviceEndpoint as either full-duplex or simplex in its DID document. Other Agents may connect to it on whichever endpoint they wish. full-duplex and simplex would simply become different Transport implementations and no coupling would occur with higher layers.
Either of these two modes is enabled from the context (ie the serviceEndpoint) as opposed to being evaluated on a per-message basis.

@llorllale I agree that the ~transport decorator does violate the layered approach. So does the ~timing decorator IMO, in that it should be handled independently of the handler that produces the message.
Encoding that behaviour in the DID Document might be a bit cleaner in terms of separating those layers, but it seems like the complexity of handling duplex connections is going to be about the same. Maybe it would be useful in order to indicate such support.
Personally, I think this information would be better represented at the envelope layer, in the ciphertext but not in the message itself. Message signatures could go there as well. That would require an update to the envelope format which is definitely out of scope for the 1.0 interop profile I think, although I have some notes on that. For now, there are multiple implementations supporting this method and it's been critical to us supporting mobile clients.

I'd be curious to learn more about your thinking @andrewwhitehead I had similar ideas very early on about using the ciphertext for routing, but not transport layer. We eventually decided against it for privacy reasons, but I have little reason to believe transport data would introduce similar concerns. The devil always seems to be in the details though.

Adding more to my previous thoughts: this decorator seems a weak attempt to reverse the natural dynamics between a client and a server.
At the request of the client agent, this decorator turns a simplex connection into a duplex one if the server agent honors it. It follows that the server agent will honor it only if they are interested in serving such clients. As per the RFC (emphasis mine):

Compliance with this indicator is optional for agents generally, but required for agents wishing to connect with client based agents.

It is the server agent that somehow needs to broadcast support for this feature, not the client.
Furthermore, implementations of synchronous and asynchronous architectures are sufficiently distinct to the point where it doesn't make much sense to serve both under the same endpoint (DIDComm messages are routed by their type as opposed to a path). A server agent allocates resources one way or the other depending on which they intend to serve.
For these reasons, it should be the server agent that should signal support for this feature, not the other way around.

It's useful to have the server advertise support for duplex communication, as the alternative is having a client with no public endpoint sending a message and simply getting no response (or possibly an error code if the transport supports it, and if the server explicitly rejects messages requesting return routing).
Return routing is not necessarily all-or-nothing either - it is still useful for the client to request only specific responses to be returned (by thread ID at the moment) which this decorator supports. It seems natural to assume that a server which supports duplex connections can also handle routing messages to an endpoint, if only for delivery of responses to a client which lost its connection, so we don't necessarily want all responses to be returned on the same socket just because the transport (and server) supports it.

I've always felt like this RFC has the kernel of an important idea in it, but that I was always uneasy that we weren't exposing it or describing its semantics right. I haven't pushed on it because I figured experience would tell us what we needed to learn.
If I apply the semantics of ACCEPTED meaning "incubating on a standards track", then I am okay with the status change. I would not vote for ADOPTED, however.

@tplooker @andrewwhitehead - I think both of you have opinions on why this is not the way we should go.  I think we do need something in place, so what do we do?
@mickrau heads up on this issue as there may be a move to remove this from the RFCs list in favour of another approach.  I know that your team is using this capability.

@swcurran can you update this to be mergeable?

@TelegramSam I think it is now ready.  Let me know if I need to do something index.md.  Right now it's just waiting on approval.

Discussed on today's community call; consensus was to merge.


[tiered-storage] fix jcloud-shaded version to build in IDEA

Motivation
pin the jclouds-shaded version to make the pulsar build friendly to intellij
Modifications
jclouds-shaded version fix to 2.3.0
Verifying this change

[✔ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API: (yes / no)
The schema: (yes / no / don't know)
The default values of configurations: (yes / no)
The wire protocol: (yes / no)
The rest endpoints: (yes / no)
The admin cli options: (yes / no)
Anything that affects deployment: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

@merlimat I believe this change is to pin the version of jcloud-shaded to a specific version as what we did for protobuf-shaded. I don't think we have to update it for each release. we are using 2.1.0-incubating for protobuf-shaded.

run integration tests


Implement back off for jobs that are continually failing

This starts limiting jobs after 24 failures (or GHA triggers) and then limits them to 1 run every 24 job triggers. Since the trigger-[arch] jobs runs hourly (triggered from the meta job), this equates to a full day of retries and then once a day thereafter.
Also track GHA triggers so they can also have back off when they have triggered many times (i.e. failed to build and push to staging).
Example runs:

https://doi-janky.infosiftr.net/job/wip/job/new/job/trigger-gha/10592/
https://doi-janky.infosiftr.net/job/wip/job/new/job/trigger-arm32v7/9108/

Hide whitespace is useful for the later section starting on new line 224.

Nice, this will be really useful for cutting down on the number of builds that we're pretty sure will fail :muscle: :heart:
In the implementation, I don't love how much duplication we have to have, especially those duplicated and reversed conditionals.  Let's spend some time noodling on it to see if we can come up with a clean enough way to merge those together (I'll be working on/thinking about it, but I don't want to discourage other input :smile:). :bow:

Rebased now that #92 is merged. Also, removed the setFailedJob function since it can be done in one spot. I'm still considering how to reduce groovy usage and stop it from interfering with the json (why there is the (long) cast on times) and how to unify the duplicated jq filters.

Ok, new approach pushed. Grab and use pastFailedBuilds.json just for creating current queue. Use jq to create and modify the record of "failing"/skipped builds (which now includes all builds triggered since they'll be filtered out on the next successful run). Moved most of the jq code to create the queue and job record to small functions in jenkins.jq. The should hopefully make it a little easier to test in locally (still needs some automated tests). Also, a bunch of renaming to remove "failed" since it now records all builds.

@yosifkit noticed after testing this one more time that a queue which is 100% failing but also 100% skipped should be marked as "unstable" in Jenkins (instead of successful), so that's going to be a follow-up


Fixed, always open Drawer not possible?

It seems it isn't (easily) possible to have a fixed Drawer which always stays open because the opacity gets in the way. Turning off the opacity also disappears the Drawer.
This layout is extremely useful for larger screens where screen space isn't an issue and the navigation drawer should always be visible/open. I should add that this is also a very common pattern in Google apps. Google's official Material Design for web apps suggests such layouts in their docs.

You are totally right. It makes a lot of sense to have a way to create a permanent Drawer. For now, it's not possible but we'll try to have it ready for the next iteration.
Thanks!

Awesome! Look forwarding to using it.

@javivelasco this would work well as part of responsivizing everything

All of the app-bar + drawer combos and their optional UX patterns (such as auto opening + locked above X width) should be possible ideally after everything is made to meet the adaptive UI requirements of the spec.

Yep

Closing in favour of #224


Get docker-compose from developer-script repo

issue #295
variable RELEASE to select specific release, the default is nightly-build
variable FOR_REDIS=ture to select redis-no-secty.yml
variable SECURITY_SERVICE_NEEDED=true to select security compose file
It successfully run on my local(macOS Catalina), but gets errors on jenkins sandbox.
Running core data test:

Signed-off-by: Ginny Guan<EMAIL_ADDRESS>

This PR is working in process.  We can run on local machine, but encounter issue on Sandbox.
We need more time to resolve it.

We have resolved the permission issue, and it could pass on sandbox now

@jinlinGuan please rebase and resolve the conflict

@jinlinGuan I am diffing developer-scripts and blackbox-test and noticed that blackbox has /etc/newman mounted to several places.  Can you plain this more? What is this volume mount used for?

@bnevis-i It only exists in volume and mongo as I see.  There are some historical reasons, but they are useless right now.  This PR will eliminate those /etc/newman folder from other containers.

This PR doesn't seem to address the requirement to use kong-centos and kong-ubuntu vs kong-alpine in the CI environment.

sync.sh needs to be chmod +x

@lranjbar please help review again when you are back.  thanks

Blocking issue: docker-edgex-consul was not rebuilt after https://github.com/edgexfoundry/docker-edgex-consul/pull/16 was merged:
https://nexus3.edgexfoundry.org/#browse/search/docker=format%3Ddocker AND attributes.docker.imageName%3Ddocker-edgex-consul:912d0fe7b8192392cfe750c17f11e329:a1f3edd8e1b06cfadf6408e1d7903880 (last updated: Thu Dec 12 2019 09:20:57 GMT-0800 (Pacific Standard Time)

Holding off on further validation until docker-edgex-consul Jenkins pipeline is fixed.  Looks nearly ready to merge.

@lranjbar Please re-review.

thanks for all you review!


Resend mechanism blocking valuable io thread

Change the resend/retry mechanism so that the reties are performed by the user thread. I currently blocks the io threads.

Related to issue https://github.com/hazelcast/hazelcast-cpp-client/issues/227
This will be fixed once the resend mechanism is changed as in Java client.

fixed by https://github.com/hazelcast/hazelcast-cpp-client/pull/392


help wanted: smoltcp integration

It would be cool to have network capabilities from driverspace, and later pushed through to userspace via the mstd interface.
To start, it would be good to have:

A driver service that handles the "net" layer, essentially a wrapper over smoltcp, or potentially embassy-net as it is already async
A driver service that handles the "phy" layer, something on linux for melpo that plugs into smoltcp at layer 2/3. Later this could be used for the wifi or ethernet or usb-networking-gadget kind of interface

I'm not sure what the messaging service interface needs to look like, but my first guess is:

Register the smoltcp-based net service w/ no phys

Maybe register two services, one for phy and one for net

Start each phy, have it take a smoltcp-phy service client handle. They are not registered on service discovery, they are just tasks holding smoltcp-phy handles
Users of the network interface can get a smoltcp-net/embassy-net service handle to open sockets, send/recv, etc.
Write a melpo demo showing ping or a hand crafted GET response or something

For future research: Maybe we just want to give tasks a capability table at spawn time. Could be based on current_task info. Probably totally out of scope for the initial impl.

Came here to check if smoltcp integration is planned o:3

Hey @whitequark, likely soon! @hawkw has started working on getting an ESP32C3-based wifi firmware going in #191, which will likely act as a "dumb" 802.3 interface, with smoltcp handling the actual network stack on the host.
We'll likely use (or base?) our work on embassy's embassy-net crate, as it already provides an async wrapper for smoltcp.

Nice!


--no-history option

Lets you create just the items table with the latest version of everything deduped by ID.

Could even skip the commits table with this option?

No that should stay to support the feature where we start against only the newly added commits.

I don't think this feature is necessary. Will add it if someone asks for it.


Bump internal jellyfish dependencies

Change-type: patch
Signed-off-by: Josh Bowling<EMAIL_ADDRESS>

@balena-ci I self certify!