Issues with Timeline Entries and progress feedback

Environment

Server: TFS On Premise 15.117.26615.0

Issue Description
Trying to utilize better progress details on steps in a longer running custom build task. I have tried to leverage child steps nested with GUID's mapped to parent step guids. Didn't work. So I tried just regular steps, and couldn't get the build steps to show up in the timeline at all.  I'd like someway to show percentage complete on child steps for someone watching a long running task, but I'm not sure of how to accomplish.
Example, running a task with the following statement to generate a new timeline entry doesn't show up anything new in the timeline.
#using posh 5 class
$this.TFSStepGuid      = [Guid]::NewGuid().Guid.ToString()
$this.ActivityName = 'Example Step'
write-host ("##vso[task.logdetail id={0};name={1};type=build;order=1]{1}" -f $this.TFSStepGuid, $this.ActivityName)
write-host ('##vso[task.logdetail id={0};progress=0;state=InProgress;]{1}' -f $this.TFSStepGuid, $this.ActivityName)

Later I'd update the percentage complete here
write-host ('##vso[task.logdetail id={0};progress=50;state=InProgress;]{1}' -f $this.TFSStepGuid, $this.ActivityName)

Finally mark as complete
write-host ( '##vso[task.logdetail id={0};state=Completed;]Completed' -f  $this.TFSStepGuid)

I'm not seeing any of these timeline entries. Any feedback on why this might be and if there are better ways to report back progress that will feedback to tfs on long running builds? Any improved way with 2017 I should leverage?

@sheldonhull We have completely reworked our build logs display. If you feel it is still not sufficient for your purposes, I suggest opening a ticket with the details on the Developer Community website.


Captive Portal -> Redirect URL

Add a field in the Zone Config to redirect client to a specific URL after succesful login. Under some circumstances (not yet reproducible) some users are redirected to the msn.com website (even if that's not the startpage on any browser).

timeout


Context for keys

Hi
First of all, thanks for this great package. I was struggling with other packages for the past few days and with next-translate, I got up and running really quickly :)
However, I couldn't do one thing. Is it somehow possible to pass a context to t() to access different keys based on the context?
I tried to play around with the examples in the docs related to passing variables or plural count, but I couldn't make it work.
Underneath you will find my example - but you can also see this in i18next docs: https://www.i18next.com/translation-function/context#context
Example
declaration in /locales/en/common.json
{
    "description": "a pretty long description",
    "description_mobile": "short desc"
}

usage in index.jsx
{t('common:description')}
=> passing no context returns the value of description
=> passing a context with empty string returns the value of description
{t('common:description', {context: 'mobile'})}
=> passing context of mobile will return the value of description_mobile
I would appreciate any help and if this is currently not possible, maybe this issue can become a feature request :)
Thanks!

We can add it, I don't think it's very expensive, but I find it hard to see what this feature brings us. Can't it be done like that?
const context = '_mobile'
const description = t(`common:description${context}`)

Thanks for the quick reply and for the suggested solution. This works fine and is definitely enough. Didn't think about that. Thanks!


Fix examples project path in main

This PR fixes #315 by correcting the examples project path.

Thanks @SiboVG ! Merging

pre-commit will pass if you pull the latest main changes!


Add an example for internal link.

Add an example that how we can make a link to another section on the same page.

[x ] I have read freeCodeCamp's contribution guidelines.
[x ] My pull request has a descriptive title (not a vague title like Update index.md)
[ x] My pull request targets the master branch of freeCodeCamp.
[x ] None of my changes are plagiarized from another source without proper attribution.
[x ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closed and reopened this PR to resolve the following Travis error:

Error: ValidationError: "0" is not allowed. "1" is not allowed. "2" is not allowed. "3" is not allowed. "4" is not allowed


Use more parallelism in the QKV projections of the MHA block.

We compute all three projections with one MatVec and then copy the kv part to the cache.
Benchmark results for 7b-it model that uses MHA blocks (summarization with 1600 tokens for prefill and essay writing with 500 tokens for generation):
                   Prefill speed                Generation speed
Num threads      BEFORE       AFTER            BEFORE       AFTER
32               13.75 t/s    14.80 t/s       9.22 t/s     9.77 t/s
64               19.89 t/s    24.83 t/s      12.46 t/s    13.66 t/s

Great to get rid of MatVecLoop! Just to confirm that the MQA 2B still works?

Yes, I tested that it still works.


Cactus branch is left untranslated

Describe the bug
The cactus branch is left untranslated, making it say "tile.cactusbranch.name".
To Reproduce
Steps to reproduce the behavior:

Find a cactus with branches.
Pick block the cactus branch.
The tooltip shows up, saying "tile.cactusbranch.name".

Mods List
Forge: <IP_ADDRESS>54
RLCraft mod pack Beta v2.8.2
Optifine HD E3 Ultra

was it fixed?


Status line not refreshed on vertical split resize (NeoVIM)

environment

vim: NVIM v0.1.2-353-g45b3782
vim-airline: 410429a95c67eed8eeb26681838d3766a2437806
OS: OSX 10.11.3
terminal: iTerm Build 2.9.20160206

vim version
NVIM v0.1.2-353-g45b3782
Build type: Dev
Compilation: /usr/local/Library/ENV/4.3/clang -Wconversion -O2 -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINC
LUDE_GENERATED_DECLARATIONS -DHAVE_CONFIG_H -I/tmp/neovim20160125-35185-93kxcv/build/config -I/tmp/neovim20160125-35185-93kxcv/src -I/tmp/neovim20160125-35185-93kxcv/deps-build/usr/include -I/tmp/neovim20
160125-35185-93kxcv/deps-build/usr/include -I/tmp/neovim20160125-35185-93kxcv/deps-build/usr/include/luajit-2.0 -I/tmp/neovim20160125-35185-93kxcv/deps-build/usr/include -I/tmp/neovim20160125-35185-93kxcv
/deps-build/usr/include -I/tmp/neovim20160125-35185-93kxcv/deps-build/usr/include -I/tmp/neovim20160125-35185-93kxcv/deps-build/usr/include -I/usr/local/opt/gettext/include -I/usr/include -I/usr/include -
I/tmp/neovim20160125-35185-93kxcv/build/src/nvim/auto -I/tmp/neovim20160125-35185-93kxcv/build/include
Compiled by<EMAIL_ADDRESS>
Optional features included (+) or not (-): +acl   +iconv    +jemalloc
For differences from Vim, see :help vim-differences

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/local/Cellar/neovim/HEAD/share/nvim"

airline configs
" ========== AIRLINE ==========
if !exists("g:airline_symbols")
  let g:airline_symbols = {}
endif

let g:airline_mode_map = {
    \ '__' : '-',
    \ 'n'  : 'N',
    \ 'i'  : 'I',
    \ 'R'  : 'R',
    \ 'c'  : 'C',
    \ 'v'  : 'V',
    \ 'V'  : 'V',
    \ '' : 'V',
    \ 's'  : 'S',
    \ 'S'  : 'S',
    \ '' : 'S',
    \ }

let g:airline_theme                                      = "gruvbox"
let g:airline_powerline_fonts                            = 1
let g:airline#extensions#whitespace#enabled              = 0
let g:airline#extensions#hunks#non_zero_only             = 1    " git gutter
let g:airline#extensions#tabline#enabled                 = 1
let g:airline#extensions#tabline#fnamemod                = ':t' " filename only
let g:airline#extensions#tabline#show_close_button       = 0
let g:airline#extensions#tabline#show_buffers            = 1
let g:airline#extensions#tabline#tab_nr_type             = 2    " splits and tab number
let g:airline#extensions#tabline#switch_buffers_and_tabs = 0
let g:airline#extensions#tabline#formatter               = 'unique_tail_improved'
let g:airline_section_b = ''

call airline#parts#define_accent('file', 'red')

actual behavior
Status line not refreshed to respect truncation of sections.

expected behavior
Status is refreshed after resizing a window.

workaround
Call AirlineRefresh with my mappings that resize a window.  However, this is slow if holding down a key to repeat.
"                           Grow pane horizontally
nnoremap <C-l>              :5winc >\|AirlineRefresh<CR>
"                           Shrink pane horizontally
nnoremap <C-H>              :5winc <\|AirlineRefresh<CR>
"                           Grow pane vertically
nnoremap <C-J>              :5winc +\|AirlineRefresh<CR>
"                           Shrink pane vertically
nnoremap <C-K>              :5winc -\|AirlineRefresh<CR>

I have a similar issue in NeoVim: resizing the left window of a vsplit leaves cruft on the right side:

@ilkka If you are talking about the bleeeding over of the statusline, this is a NeoVim bug, that has been fixed I believe.

Alright, thanks!

there does not seem to be an event when resizing a window within vim, so I guess, we are left with your work around. Closing.


Remove duplicate comments

A few single line comments were duplicated, probably due to bad merges.
This commit removes the obviously duplicate ones.

Thanks!

I reviewed this too fast, the changes to thirdparty code were invalid. This needs to be contributed to the respective thirdparty projects (here bullet), there's no point creating such a diff between our vendored copy and the upstream one for cosmetic reasons.
That part will be reverted since I'm updating to bullet 3.09.


capture if pushed rules have advanced and reflect when popped

This should fix #82 (the first half of https://github.com/Microsoft/vscode/issues/65983) and #49, and maybe others.
I save a hasAdvanced flag to the stack (StackElement) when pushing a rule and when popping the rule I use this flag to reset the anchorPos (in _tokenizeLine) back to -1 to disable further anchor matching.
I have been running in to similar issues trying to change the PowerShell/EditorSyntax grammer, and I believe that this is the correct behavior.  I have only so far 'inspect'ed my PowerShell with this change and it seems to work how I think it should.  I will test at another location the pug, and if it still exists, the HTML issue as well.
I do not know what affect this might have on projects dependent on this one.

I have tested my grammar using Atom, and I have no problems with it there, indicating their tokenizer must reset the match anchor point after a rule pop.
I have also 'inspect'ed both the #82 and the #49 issues and it resolves them the same as it resolves my issues in my PowerShell grammar.

@egamma, @alexandrudima, any change this could get looked at yet during this update cycle?
The reason being, in addition to the issues detailed above and those detailed as duplicated in them, as I keep working on a rewrite of the PowerShell grammar, I keep running in to this.  In many cases I can work around it, but in all the cases I go over to Atom, and the issue does not occur.
Current issue:
{
	"comment": "could be a numeric constant or a limited list of unary operators, that we should switch to expression mode",
	"begin": "(?=[\\d.!+\\x{2013}-\\x{2015}-])",
	"end": "$(?=\\n)|(?=[;|)}\\]])",
	"patterns": [
		{
			"include": "#numericConstant"
		},
		{
			"include": "#operators_preUnary"
		},
		{
			"comment": "if numeric constant advanced, switch to expression mode",
			"begin": "(?!\\G)(?!$(?=\\n)|(?=[;|)}\\]]))",
			"end": "$(?=\\n)|(?=[;|)}\\]])",
			"patterns": [
				{
					"include": "#expression_mode"
				}
			]
		},
		{
			"comment": "if numeric constant didn't advanced, try finishing command mode with a command name",
			"begin": "\\G(?!$(?=\\n)|(?=[;|)}\\]]))",
			"end": "$(?=\\n)|(?=[;|)}\\]])",
			"patterns": [
				{
					"include": "#command_name"
				}
			]
		}
	]
},

The purpose of this is to select between what might be a numeric value, which in PowerShell is a fairly complicated set of regex, or the beginning of a command name that just looks like a numeric value.  The problem is that a numeric value also uses a begin-end rule, so that it can also check for special operator circumstances, so when it returns, the anchor is left sitting at the end of the numeric value, even though it 'popped' to return.  Instead of the rule with the negative lookahead for \G matching, the non-negative \G rule matches and sends the grammar to the command name path.
JSON of this grammar can be found: https://github.com/msftrncs/PowerShell.tmLanguage/tree/argumentmode_2ndtry
Pattern that scopes erroneously:
($i=-5kb, $c, ${true} )
($i=-5kb-$c, ${true} )

In both lines, the $c should scope as a variable, but instead scopes as a function name (hence command name).  In the first line , should have scoped as a separator, but instead is glanced over by command name since its an invalid character for a command name, but command name doesn't return (end) and has no other matches so it finds the first thing valid (since the original point should have matched a command name had it not matched a numeric value).  In the second line, the - gets caught by a begin-end rule in the numeric value rule, that looks for some other possibilities, but finds nothing and pops, but the anchor point is now set at its end, and so the same thing happens when we return back to the rule shown above.
I am not sure I can find any other reliable workaround in this particular case, though I have ultimately worked around every single other places with this sort of thing has occurred, but that's just making the regex more complicated, in each case that a work around can be made reliable, and I don't think that is the route that should be taken, as it seems the other TextMate compatible editors do not require these workarounds.
If not in this update cycle, maybe shortly afterwards?  The wildcard I am unclear about is if this solution, which modifies the constructor for StackElement would potentially upset any downstream projects, and maybe needs to be implemented differently.

@msftrncs Thank you for the great analysis and the PR!
I have decided to go in a similar direction, but with a simplification:

capture the anchor position value when a stack element is pushed.
when a stack element is popped, restore the anchor position value from the popped stack element.

This has as a "side effect" the desired behaviour that the anchor position is reset if tokenization has advanced. This capturing/restoring is IMHO easier to comprehend.

Thanks for getting to this.  I am sure there are lots more ways to tackle the problem.  I was worrying about a rule pop occurring on a different line than the push did, and how to detect that, so I stayed away from pushing the actual anchor position.

Ah, I had looked over the stackelement.reset() method being used to reset the previous element each time a new line is tokenized.


Calls to map are not cached.

Describe the bug
Somehow caching does not work for me anymore. Am I doing something wrong, or is there anything that I missed?
Steps to reproduce the bug

import datasets
datasets.set_caching_enabled(True)
sst = datasets.load_dataset("sst")

def foo(samples, i):
    print("executed", i[:10])
    return samples

# first call
x = sst.map(foo, batched=True, with_indices=True,  num_proc=2)

print('\n'*3, "#" * 30, '\n'*3)

# second call
y = sst.map(foo, batched=True, with_indices=True, num_proc=2)

# print version
import sys
import platform
print(f"""
- Datasets: {datasets.__version__}
- Python: {sys.version}
- Platform: {platform.platform()}
""")

Actual results
This code prints the following output for me:
No config specified, defaulting to: sst/default
Reusing dataset sst (/home/johannes/.cache/huggingface/datasets/sst/default/1.0.0/b8a7889ef01c5d3ae8c379b84cc4080f8aad3ac2bc538701cbe0ac6416fb76ff)
#0:   0%|          | 0/5 [00:00<?, ?ba/s]
#1:   0%|          | 0/5 [00:00<?, ?ba/s]
executed [0, 1, 2, 3, 4, 5, 6, 7, 8, 9]
executed [4272, 4273, 4274, 4275, 4276, 4277, 4278, 4279, 4280, 4281]
executed [1000, 1001, 1002, 1003, 1004, 1005, 1006, 1007, 1008, 1009]
executed [5272, 5273, 5274, 5275, 5276, 5277, 5278, 5279, 5280, 5281]
executed [2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009]
executed [6272, 6273, 6274, 6275, 6276, 6277, 6278, 6279, 6280, 6281]
executed [3000, 3001, 3002, 3003, 3004, 3005, 3006, 3007, 3008, 3009]
executed [7272, 7273, 7274, 7275, 7276, 7277, 7278, 7279, 7280, 7281]
executed [4000, 4001, 4002, 4003, 4004, 4005, 4006, 4007, 4008, 4009]
#0: 100%|██████████| 5/5 [00:00<00:00, 59.85ba/s]
executed [8272, 8273, 8274, 8275, 8276, 8277, 8278, 8279, 8280, 8281]
#1: 100%|██████████| 5/5 [00:00<00:00, 60.85ba/s]
#0:   0%|          | 0/1 [00:00<?, ?ba/s]
#1:   0%|          | 0/1 [00:00<?, ?ba/s]executed [0, 1, 2, 3, 4, 5, 6, 7, 8, 9]
#0: 100%|██████████| 1/1 [00:00<00:00, 69.32ba/s]
executed [551, 552, 553, 554, 555, 556, 557, 558, 559, 560]
#1: 100%|██████████| 1/1 [00:00<00:00, 70.93ba/s]
#0:   0%|          | 0/2 [00:00<?, ?ba/s]
#1:   0%|          | 0/2 [00:00<?, ?ba/s]executed [0, 1, 2, 3, 4, 5, 6, 7, 8, 9]
executed [1000, 1001, 1002, 1003, 1004, 1005, 1006, 1007, 1008, 1009]
#0: 100%|██████████| 2/2 [00:00<00:00, 63.25ba/s]
executed [1105, 1106, 1107, 1108, 1109, 1110, 1111, 1112, 1113, 1114]
executed [2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2113, 2114]
#1: 100%|██████████| 2/2 [00:00<00:00, 57.69ba/s]

 ##############################

#0:   0%|          | 0/5 [00:00<?, ?ba/s]
#1:   0%|          | 0/5 [00:00<?, ?ba/s]
executed [0, 1, 2, 3, 4, 5, 6, 7, 8, 9]
executed [4272, 4273, 4274, 4275, 4276, 4277, 4278, 4279, 4280, 4281]
executed [1000, 1001, 1002, 1003, 1004, 1005, 1006, 1007, 1008, 1009]
executed [5272, 5273, 5274, 5275, 5276, 5277, 5278, 5279, 5280, 5281]
executed [2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009]
executed [6272, 6273, 6274, 6275, 6276, 6277, 6278, 6279, 6280, 6281]
executed [3000, 3001, 3002, 3003, 3004, 3005, 3006, 3007, 3008, 3009]
executed [4000, 4001, 4002, 4003, 4004, 4005, 4006, 4007, 4008, 4009]
#0: 100%|██████████| 5/5 [00:00<00:00, 58.10ba/s]
executed [7272, 7273, 7274, 7275, 7276, 7277, 7278, 7279, 7280, 7281]
executed [8272, 8273, 8274, 8275, 8276, 8277, 8278, 8279, 8280, 8281]
#1: 100%|██████████| 5/5 [00:00<00:00, 57.19ba/s]
#0:   0%|          | 0/1 [00:00<?, ?ba/s]
#1:   0%|          | 0/1 [00:00<?, ?ba/s]
executed [0, 1, 2, 3, 4, 5, 6, 7, 8, 9]
#0: 100%|██████████| 1/1 [00:00<00:00, 60.10ba/s]
executed [551, 552, 553, 554, 555, 556, 557, 558, 559, 560]
#1: 100%|██████████| 1/1 [00:00<00:00, 53.82ba/s]
#0:   0%|          | 0/2 [00:00<?, ?ba/s]
#1:   0%|          | 0/2 [00:00<?, ?ba/s]
executed [0, 1, 2, 3, 4, 5, 6, 7, 8, 9]
executed [1000, 1001, 1002, 1003, 1004, 1005, 1006, 1007, 1008, 1009]
executed [1105, 1106, 1107, 1108, 1109, 1110, 1111, 1112, 1113, 1114]
#0: 100%|██████████| 2/2 [00:00<00:00, 72.76ba/s]
executed [2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2113, 2114]
#1: 100%|██████████| 2/2 [00:00<00:00, 71.55ba/s]

- Datasets: 1.6.1
- Python: 3.8.3 (default, May 19 2020, 18:47:26)
[GCC 7.3.0]
- Platform: Linux-5.4.0-72-generic-x86_64-with-glibc2.10

Expected results
Caching should work.

I receive the same output after upgrading to datasets==1.6.2

Hi,
set keep_in_memory to False when loading a dataset (sst = load_dataset("sst", keep_in_memory=False)) to prevent it from loading in-memory. Currently, in-memory datasets fail to find cached files due to this check (always False for them):
https://github.com/huggingface/datasets/blob/241a0b4a3a868778ee91e767ad406f9da7610df2/src/datasets/arrow_dataset.py#L1718
@albertvillanova It seems like this behavior was overlooked in #2182.

Hi @villmow, thanks for reporting.
As @mariosasko has pointed out, we did not consider this case when introducing the feature of automatic in-memory for small datasets. This needs to be fixed.

Hi ! Currently a dataset that is in memory doesn't know doesn't know in which directory it has to read/write cache files.
On the other hand, a dataset that loaded from the disk (via memory mapping) uses the directory from which the dataset is located to read/write cache files.
Because of that, currently in-memory datasets simply don't use caching.
Maybe a Dataset object could have a cache_dir that is set to the directory where the arrow files are created during load_dataset ?


Android native debugging

Enable native debugging. It should now be as simple as running:
[ANDROID_X86=1] DEBUG=1 make -j android
make android-install
make android-debug

to run the demo with gdb attached to it. After the first run of android-debug on can quit gdb and then re-attach to the running app with android-debug-attach. With a rooted device or emulator one can also use
kill -SIGINT `ps | grep -m 1 tangram | awk -e '{print $2}'`

in adb shell to suspend the program to set breakpoints, etc.
TODO

[X] separate Release/Debug builds
[X] needs update of our stripped ndk to clang-3.6
[X] cleanups

This will be good and helpful. Thanks for getting this done.
Only if we had something for shaders :P.

Reviewing and trying this now.

I think its not possible to debug/ use ndk-gdb on devices like the s5 (no read access to /data dir).
I get the following error on doing a make android-debug:
 ✘ varun@varun-MacBookAir-Ubuntu  ~/Development/tangram-es   android-debugging  make android-debug
Android NDK installation path: /home/varun/Development/android-ndk-r10e
ADB version found: Android Debug Bridge version 1.0.31
Using ADB flags:
Using auto-detected project path: .
Found package name: com.mapzen.tangram.android
ABIs targetted by application: armeabi-v7a
Device API Level: 21
Device CPU ABIs:  armeabi-v7a armeabi
Compatible device ABI: armeabi-v7a
Using gdb setup init: ./libs/armeabi-v7a/gdb.setup
Using toolchain prefix: /home/varun/Development/android-ndk-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86_64/bin/arm-linux-androideabi-
Using app out directory: ./obj/local/armeabi-v7a
Found debuggable flag: false
Found gdbserver under libs/armeabi-v7a, assuming app was built with NDK_DEBUG=1
Found device gdbserver: /data/data/com.mapzen.tangram.android/lib/gdbserver
ERROR: Could not extract package's data directory. Are you sure that
       your installed application is debuggable?
Makefile:276: recipe for target 'android-debug' failed
make: *** [android-debug] Error 1

This is what adb shell says when I try to access the data dir:
 ✘ varun@varun-MacBookAir-Ubuntu  ~/Development/tangram-es   android-debugging  adb shell
shell@klteatt:/ $ cd /data
shell@klteatt:/data $ ll
opendir failed, Permission denied
255|shell@klteatt:/data $ ls
opendir failed, Permission denied
255|shell@klteatt:/data $ exit
 varun@varun-MacBookAir-Ubuntu  ~/Development/tangram-es   android-debugging 

Do not have any other rooted/test device me right now.
@blair1618 can you try it on your personal phone (not rooted but also not samsung)?
It sounds like the issue we were having when we were trying to use intel graphics debugging utilities with s5, which worked on your your motox.

@tallytalwar the message about debuggable flag is the key here to allow accessing the apps data dir on the device I guess. It need to be set somewhere in the android manifest file. Though it should be set in the demo.. Will look into it

@hjanetzek even with the fix you have from your last commit, I get this:
 varun@varun-MacBookAir-Ubuntu  ~/Development/tangram-es   android-debugging  make android-debug
Android NDK installation path: /home/varun/Development/android-ndk-r10e
ADB version found: Android Debug Bridge version 1.0.31
Using ADB flags:
Using auto-detected project path: .
Found package name: com.mapzen.tangram.android
ABIs targetted by application: armeabi-v7a
Device API Level: 21
Device CPU ABIs:  armeabi-v7a armeabi
Compatible device ABI: armeabi-v7a
Using gdb setup init: ./libs/armeabi-v7a/gdb.setup
Using toolchain prefix: /home/varun/Development/android-ndk-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86_64/bin/arm-linux-androideabi-
Using app out directory: ./obj/local/armeabi-v7a
Found debuggable flag: true
Found device gdbserver: /data/data/com.mapzen.tangram.android/lib/gdbserver
ERROR: Could not extract package's data directory. Are you sure that
       your installed application is debuggable?
Makefile:276: recipe for target 'android-debug' failed
make: *** [android-debug] Error 1

Showing that its the permission to access the /data dir for the installed package is the issue. This is however a device specific thingy, would like to confirm this with another device besides s5/s6.

This is the command that fails - what is the output that you get?
adb shell run-as com.mapzen.tangram.android /system/bin/sh -c pwd

It seems some devices need root for the run-as command. Could you try the modification suggested here?
http://stackoverflow.com/questions/6158953/running-ndk-gdb-with-package-not-found-error-on-motorola-phone
Someone in that thread even suggested that 'run-as' fails when you too many apps installed :D

@hjanetzek This is what I get when I do the following after installing tangram with DEBUG=1:
varun@varun-MacBookAir-Ubuntu  ~/Development/tangram-es   android-debugging  adb shell run-as com.mapzen.tangram.android /system/bin/sh -c pwd
run-as: Package 'com.mapzen.tangram.android' is unknown

So was able to debug on an LG test device we have here.
But had to modify ndk-gdb.py in my android-ndk path, as suggested here: https://groups.google.com/forum/#!topic/Android-ndk/jsY9NUc5S10.

I was able to attach gdb on my Moto X without any permission issues; they seem to only happen on some subset of phones (including many Samsung phones).

Will merge this, once Travis goes green.


Update for latest DLC patch :3

Seekers of the storm is here!! lesgoo

Working on it, though the engine changes done by Gearbox are retarded.

Score has created a fixed version, so for now use that.
In fact, it seems to properly detect when it shouldn't sprint instead of my hacky workaround of listing the EntityStates manually I, so I might just deprecate my version and let them carry the torch from now on - exactly as I originally did when I took and fixed the broken RTAutoSprint by Relocity over four years ago :)


The certificate not work

The certificate not work , i have this error 2023/05/13 00:44:19 [001] WARN: Cannot handshake client www.google.com:443 remote error: tls: bad certificate

@djallalzoldik this is fixed in dev branch with https://github.com/projectdiscovery/proxify/pull/238


feat: all tokens observable

returns all erc20 tokens
to be used with https://github.com/reef-chain/mobile-app/pull/96

Won't load all for token pairs - not optimal


[Rx -> Coroutine] : Migrate PermissionsManager, LocationManager and LocationManager to coroutine

Towards #1851

Verified the changes by manually triggering camera and location updates in the app.

@... PTAL?

/gcbrun

/gcbrun


pip: generate and install man pages

Description of changes
Generates pip man pages following the arch pip package or the sketch of a working change. As this is a change to pip's definition the full build hasn't been tested on a machine I own.

Move scipy onto pypaInstallHook avoiding infinite recursion from pipInstallHook when scipy is pulled in via checks in either myst-parser or sphinx
Add sphinxcontrib-towncrier based on the arch package
Invokes and pip_sphinxext.py to build and pass definitions to sphinx.

Couple things are some amount of incomplete

sphinx package references some? but no where near all sphinx packages
patch to sphinxcontrib-towncrier is blindly copied
intersphinx is part of the pip docs and wants to pull references from the internet. pythonDocs appears to have the needed python object file reference but pypug is not? currently packaged.

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

2. Why is this a draft? Changes look good overall.

Oh now I read your top comment.

Any suggestion about when or if this should target staging and how to validate if it's broken something unintentional? Pip being the bottom of ~all python packages means I can't really fully test this locally. (even though it "looks" innocuous)

Fished around for a commit that didn't involve building gcc and found this: https://hydra.nixos.org/jobset/nixpkgs/python-updates/evals. I'll use cdeab96 while staging hasn't been built.

I split the scipy part off in https://github.com/NixOS/nixpkgs/pull/250509

Pip being the bottom of ~all python packages means I can't really fully test this locally. (even though it "looks" innocuous). I'm unfamiliar with how PR's of this kind might need special handling.

Not anymore. With the changes on staging pip isn't a python bootstrapping package anymore. It is however still used by some packages at times.

@FRidh it looks like pip goes from ~40000 -> 3089 dependants. 1924 are python3.1{0,1}* and 739 are homeassistant-test. I have a copy of the nixpkgs-review output set if needed. That took ~8 hours of build time so I won't repeat generating it locally.
@doronbehar

Regarding Sphinx package having a few contrib packages. They were added ~early on and the pattern doesn't appear to have been continued
Regarding the patch: seems to be arch build ecosystem specific, removed as unneeded.
intersphinx is needed for html generation, snipped out with sed + explanation comment.
Regarding sphinxHook: technically I can make it work with a few extra steps. Pip's sphinx setup is a bit non-standard? so I figure matching it is less likely to surprise in future changing files to line up with the current expectations of sphinxHook (namely conf.py is in an admittedly weird place in pip source)

Seems pretty good to me overall.

Seems perfect to me now. Let's wait a few more days for this to get more comments/  hopefully a final word from FRidh as well.
On 22 August 2023 19:41:35 GMT+03:00, anund @.***> wrote:

@anund requested your review on: NixOS/nixpkgs#250398 pip: generate and install man pages.
--
Reply to this email directly or view it on GitHub:
https://github.com/NixOS/nixpkgs/pull/250398#event-10160870457
You are receiving this because your review was requested.
Message ID: @.***>


What is the interactive multi-agent simulation platform proposed in this paper?

What is the interactive multi-agent simulation platform proposed in this paper?

@Highlight123
Hi, we have added an installation guide, you can follow the instructions and try the demo.
The simulator is based on ROS and the implementation is quite simple, you can refer to the code for details (package phy_simulator). Intuitively, the simulator's node maintains the state of all agents and broadcast the information to all agents' nodes. Then, the agent's node calculates a control signal and pass it back to the simulator's node for state update.
Currently, the function of the simulator is simple. We are planning to refactor it and add more features. :)


Zoom Reset (CMD + 0) dosn't work on wireless Mac Magic Keyboard

VSCode Version: 1.51.0 (master)
OS Version: macOS 10.14.6

Steps to Reproduce:

On a Mac using a wireless Magic Keyboard (i.e., no numpad), zoom the view size using CMD+ +
Try to reset the zoom to normal using CMD + 0

Instead of resetting the zoom, the side panel is focused instead

Does this issue occur when all extensions are disabled?: Yes
I have a Mac wireless Magic Keyboard with no numpad, like this one:

In browsers (Chrome, Firefox, etc) using CMD+ + will zoom in, CMD + - will zoom out, and CMD + 0 will reset the zoom level to normal.
In VSCode, this doesn't work.  I did some research, and it looks like the keybinding for zoom reset is CMD + NUMPAD_0:
https://github.com/microsoft/vscode/blob/master/src/vs/workbench/electron-sandbox/desktop.contribution.ts#L34
The binding for CMD + KEY_0 is set here in the FocusSideBarAction:
https://github.com/microsoft/vscode/blob/master/src/vs/workbench/browser/parts/sidebar/sidebarPart.ts#L317
Because there is no number pad on these keyboards, users expect CMD + 0 to reset, but this is impossible.
Could we rebind the Zoom Reset action to CMD + KEY_0?  It's more commonly known than the sidebar focus in my opinion.

This is not a keybinding dispatching problem, but rather a problem with our default keybindings, where we have opted to follow browser zoom keybindings for zooming in or zooming out, but not for resetting the zoom.

/duplicate https://github.com/microsoft/vscode/issues/105171


Can't sort the requests table by headers

What Happened
When I click on the track request table headers, the table isn't being sorted.
What Should Happen
Clicking on the headers should sort the table.
To Reproduce
Steps to reproduce the bug:

Go to the Track Requests page
Authenticate if needed
Click on any of the table headers to sort the table by that header (ascending/descending)

Screenshots

Additional Notes
I wonder if this is happening since we now have people requesting counts with the type of "Other" (we introduced this in the last release).

This should be fixed by previous work on #858 , marking closed.


Hystrix-dashboard not working correctly, if a context path is set

the hystrix-dashboard index.html is not working correctly, if a context path is set, because the following src url is not considering the context path:
<script src="/webjars/jquery/2.1.1/jquery.min.js" type="text/javascript"></script>

Same for the hystrix-monitor-dashboard.

FYI I'm having a problem with the hystrix dashboard in my Spring Boot 1.2.3 app (using 1.0.1.RELEASE of hystrix dashboard. The page loads, but the Monitor Stream button doesn't actually do anything. If I open the javascript console I see the following error:
[Error] ReferenceError: Can't find variable: $
sendToMonitor (hystrix, line 14)
onclick (hystrix, line 50)
If I go direct to the hystrix.stream url, I see data and it's consistently streaming. Just seems like a javascript issue... please help!

Please can you open a new issue, rather than commenting on one that is already closed?


Update code samples

Summary
Update some incorrect code samples
Fixes #Issue_Number (if available)

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: Zhu-Panda sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Hi @Zhu-Panda - could you please rebase your PR from the latest in main? This should fix the build error.

https://github.com/dotnet/docs/pull/28919/files was not able to automatically add a project file for this directory, because there were some build errors that needed to be manually fixed up. Instead, I've opened #28937 to add a project file for this directory, so that should be merged before this one.


isWebGLSupported not checking getProgramParameter

Expected Behavior
If a device passes the isWebGLSupported check, it should be able to run Pixi.
Current Behavior
Some old machine throws: Failed to execute 'getProgramParameter' on 'WebGLRenderingContext': parameter 1 is not of type 'WebGLProgram'.
Possible Solution
Check if getProgramParameter is supported.
Environment

pixi.js version: 4.6.1
Browser: Chrome 70
Device: Desktop (Win 8.1)

Do you have a piece of code that duplicates the behavior? What version of pixi are you using?

The behavior only happens in some devices (I receive the errors through Sentry). I put the pixi version in the issue, just forgot to remove some decorations. It's 4.6.1

Oh, maybe this is related to this: https://github.com/pixijs/pixi.js/issues/3822


Galileo ROS Package

This is a draft, as the galileo ros branch was specifically "rushed". I'll set it as a draft officially


[FBX] [license required; Akeytsu] Files from Akeytsu have mesh problems and one file crashes Godot

Godot_v3.2-beta5
Windows 10/1903:
FBX files from Akeytsu are not loaded correctly in Godot:
Steps to  reproduce:
drag and drop FBX files into the Filesystem of a Godot Project.
the file Akeyboy.fbx results in making Godot unresponsive/crashes it.
Doubleclicking and clicking New Inherited the fbx file called
The e-LysE.fbx doesn´t show the mesh of the figure, only a sword without animation and the rig of the figure which has animations is shown.
Foot L and Foot R are not visible bones in Godot.
The SkySurfer_BS.fbx file gets imported and parts of the mesh get rotated. blendshapes are shown.Bone animations seem to be there too.
All fbx files are here; https://www.dropbox.com/sh/9m8zmi1227tdl5g/AAB5b1j-QxVcL-tYw4YEbv91a?dl=0
Minimal reproduction project:
https://www.dropbox.com/sh/qf1t89u4v6w2zxp/AABuFYgDJL0nQo3Qxbj7vqkia?dl=0

CC @fire @RevoluPowered

We're deep in the weeds of the FBX coding.
However, if you need your project to work. I have an alternative flow.
Use fbx2gltf.

[reposted]
We're deep in the weeds of the FBX coding.
However, if you need your project to work. I have an alternative flow.
Use fbx2gltf.
https://github.com/revolufire/FBX2glTF/releases/tag/v2019-12-25T15_23-08_00
./FBX2glTF-linux-64 --pbr-metallic-roughness e-LysE.fbx
./FBX2glTF-linux-64 --pbr-metallic-roughness SkySurfer_BS.fbx

e-LysE_out.zip
SkySurfer_BS_out.zip

I don't know when the FBX importer will be fully ready for rigged skeletal animations.

Current state is still broken.

Using https://github.com/godotengine/godot/pull/38966.

https://github.com/RevoluPowered/godot/commit/89d2f6274c8f7d2e63c8f881e17d37762764c926

Hello @fire
with the Akeytsu 2020-1-4 release, there has been an FBX overhaul.
I have uploaded the updated versions of the 3 Testfiles.
https://www.dropbox.com/sh/au1ino9qaen7b6j/AAD4HkY0POLjhocxJtyhAY1Ea?dl=0
Akeyboy is the file which loads up the best with Godot 3.2.2 RC1

Godot;
the Animation Sample_Trick_One form Akeyboy changes the Bag and Foot endframe when Animation Looping is activated seems to be an undesired issue.
All those new FBX files are imported without Textures.
Blendshapes/Shapekeys are loaded into Godot and at first glance seems to work very well.(disbaled the problematic second mesh[body])

Second meshes are not correctly interpreted and look strange
Second mesh for e-LysE is ;
CHA_e-LysE2
Second Mesh for Skysurfer_BS is;
Body2

after checking, the files shouldn´t have the tag "2" added to them.
multiple skins/bindings inside the fbx are seemingly wrong interpreted by Godot.
For further testing in the below gifs, I have deleted the sword (PRP_Sabre_R) within the e-LysE example.
the skinning for Foot_R and Foot_L  inside the e-LysE are not imported correctly or missing.
there is some weird scaling happening on the jump animation.

The jump animation has been split into jump_Start jump_Loop and jump_End
and falsely loaded.

Can you retest on the development branch of 3.2?
A new fbx importer was merged.

tried to compile got this result ..
cowdata.h(130) : warning C4724: Mögliches Modulo durch 0 (Null)
should be this one in English
Compiler Warning (level 3) C4724. potential mod by 0
no idea how severe the compiler error might be.
anyways,I tired using the compiled 3.2.4 beta build (downloaded today 18.11.2020 at 21:20)
and with consecutive posts will use the following files;
https://www.dropbox.com/s/mz05iwm7trshopi/akeyboy_sample.fbx?dl=0
https://www.dropbox.com/s/nrr3vuo5uio2fkq/e-LysE.fbx?dl=0
https://www.dropbox.com/s/r9p2li586kg5mch/SkySurfer_BS.fbx?dl=0
root motion works well so this is just in case files;
https://www.dropbox.com/s/5uc7bxor95vv3wv/akeyboy_sample_activerootmotion.fbx?dl=0
https://www.dropbox.com/s/746yvbsygxvthl3/e-LysE_activerootmotion.fbx?dl=0
adding the 3 example files into the project folder via file manager while godot is closed and opening it - no crash.
the following output message is given;
Godot Engine v3.2.4.beta.custom_build (c) 2007-2020 Juan Linietsky, Ariel Manzur & Godot Contributors.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter: Ambientis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:AmbientColoris ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Emissiveis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:ShininessExponentis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Specularis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Ambientis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:AmbientColoris ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Emissiveis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:ShininessExponentis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Specularis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Ambientis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:AmbientColoris ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Emissiveis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:ShininessExponentis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Specularis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Ambientis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:AmbientColoris ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Emissiveis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:ShininessExponentis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Specularis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Ambientis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:AmbientColoris ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Emissiveis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:ShininessExponentis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Specularis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Ambientis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:AmbientColoris ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Emissiveis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:ShininessExponentis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Specularis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Ambientis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:AmbientColoris ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Emissiveis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:ShininessExponentis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Specularis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Ambientis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:AmbientColoris ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Emissiveis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:ShininessExponentis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Specularis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Ambientis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:AmbientColoris ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Emissiveis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:ShininessExponentis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Specularis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Ambientis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:AmbientColoris ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Emissiveis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:ShininessExponentis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Specularis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Ambientis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:AmbientColoris ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Emissiveis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:ShininessExponentis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Specularis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Ambientis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:AmbientColoris ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Emissiveis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:ShininessExponentis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Specularis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Ambientis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:AmbientColoris ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Emissiveis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:ShininessExponentis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Specularis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Ambientis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:AmbientColoris ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Emissiveis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:ShininessExponentis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Specularis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Ambientis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:AmbientColoris ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Emissiveis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:ShininessExponentis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Specularis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Ambientis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:AmbientColoris ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Emissiveis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Specularis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Ambientis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:AmbientColoris ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Emissiveis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:ShininessExponentis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Specularis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:SpecularFactoris ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Ambientis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:AmbientColoris ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Emissiveis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:ShininessExponentis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Specularis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:SpecularFactoris ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Ambientis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:AmbientColoris ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Emissiveis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:ShininessExponentis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Specularis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:SpecularFactoris ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Ambientis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:AmbientColoris ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Emissiveis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:ShininessExponentis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:Specularis ignored.  modules\fbx\data\fbx_material.cpp:289 - [Ignored] The FBX material parameter:SpecularFactor is ignored.  [doc] warning failed to find a target Model for curve: SubDeformer::Grr_UP_R  [doc] warning failed to find a target Model for curve: SubDeformer::Grr_DWN_R  [doc] warning failed to find a target Model for curve: SubDeformer::Smile_R  [doc] warning failed to find a target Model for curve: SubDeformer::Sad_R  [doc] warning failed to find a target Model for curve: SubDeformer::Small_R  [doc] warning failed to find a target Model for curve: SubDeformer::Large_R  [doc] warning failed to find a target Model for curve: SubDeformer::Mouth_UP  [doc] warning failed to find a target Model for curve: SubDeformer::Mouth_DWN  [doc] warning failed to find a target Model for curve: SubDeformer::Mouth_L  [doc] warning failed to find a target Model for curve: SubDeformer::Mouth_R  [doc] warning failed to find a target Model for curve: SubDeformer::Lips_MID_UP  [doc] warning failed to find a target Model for curve: SubDeformer::Lips_MID_DW  [doc] warning failed to find a target Model for curve: SubDeformer::U  [doc] warning failed to find a target Model for curve: SubDeformer::M  [doc] warning failed to find a target Model for curve: SubDeformer::O  [doc] warning failed to find a target Model for curve: SubDeformer::MouthBank_R  [doc] warning failed to find a target Model for curve: SubDeformer::MouthBank_L  [doc] warning failed to find a target Model for curve: SubDeformer::Hollow_R  [doc] warning failed to find a target Model for curve: SubDeformer::Inflate_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_Open_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_Close_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_Close_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_Open_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowIN_UP_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowIN_DWN_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowIN_Fronce_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowMID_UP_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowMID_DWN_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowOUT_UP_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowOUT_DWN_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_A_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_B_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_A_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_B_R  [doc] warning failed to find a target Model for curve: SubDeformer::Grr_UP_L  [doc] warning failed to find a target Model for curve: SubDeformer::Grr_DWN_L  [doc] warning failed to find a target Model for curve: SubDeformer::Smile_L  [doc] warning failed to find a target Model for curve: SubDeformer::Sad_L  [doc] warning failed to find a target Model for curve: SubDeformer::Small_L  [doc] warning failed to find a target Model for curve: SubDeformer::Large_L  [doc] warning failed to find a target Model for curve: SubDeformer::Hollow_L  [doc] warning failed to find a target Model for curve: SubDeformer::Inflate_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_Open_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_Close_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_Close_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_Open_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowIN_UP_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowIN_DWN_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowIN_Fronce_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowMID_UP_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowMID_DWN_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowOUT_UP_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowOUT_DWN_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_A_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_B_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_A_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_B_L  [doc] warning failed to find a target Model for curve: SubDeformer::Grr_UP_R  [doc] warning failed to find a target Model for curve: SubDeformer::Grr_DWN_R  [doc] warning failed to find a target Model for curve: SubDeformer::Smile_R  [doc] warning failed to find a target Model for curve: SubDeformer::Sad_R  [doc] warning failed to find a target Model for curve: SubDeformer::Small_R  [doc] warning failed to find a target Model for curve: SubDeformer::Large_R  [doc] warning failed to find a target Model for curve: SubDeformer::Mouth_UP  [doc] warning failed to find a target Model for curve: SubDeformer::Mouth_DWN  [doc] warning failed to find a target Model for curve: SubDeformer::Mouth_L  [doc] warning failed to find a target Model for curve: SubDeformer::Mouth_R  [doc] warning failed to find a target Model for curve: SubDeformer::Lips_MID_UP  [doc] warning failed to find a target Model for curve: SubDeformer::Lips_MID_DW  [doc] warning failed to find a target Model for curve: SubDeformer::U  [doc] warning failed to find a target Model for curve: SubDeformer::M  [doc] warning failed to find a target Model for curve: SubDeformer::O  [doc] warning failed to find a target Model for curve: SubDeformer::MouthBank_R  [doc] warning failed to find a target Model for curve: SubDeformer::MouthBank_L  [doc] warning failed to find a target Model for curve: SubDeformer::Hollow_R  [doc] warning failed to find a target Model for curve: SubDeformer::Inflate_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_Open_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_Close_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_Close_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_Open_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowIN_UP_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowIN_DWN_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowIN_Fronce_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowMID_UP_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowMID_DWN_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowOUT_UP_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowOUT_DWN_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_A_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_B_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_A_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_B_R  [doc] warning failed to find a target Model for curve: SubDeformer::Grr_UP_L  [doc] warning failed to find a target Model for curve: SubDeformer::Grr_DWN_L  [doc] warning failed to find a target Model for curve: SubDeformer::Smile_L  [doc] warning failed to find a target Model for curve: SubDeformer::Sad_L  [doc] warning failed to find a target Model for curve: SubDeformer::Small_L  [doc] warning failed to find a target Model for curve: SubDeformer::Large_L  [doc] warning failed to find a target Model for curve: SubDeformer::Hollow_L  [doc] warning failed to find a target Model for curve: SubDeformer::Inflate_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_Open_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_Close_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_Close_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_Open_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowIN_UP_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowIN_DWN_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowIN_Fronce_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowMID_UP_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowMID_DWN_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowOUT_UP_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowOUT_DWN_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_A_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_B_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_A_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_B_L  [doc] warning failed to find a target Model for curve: SubDeformer::Grr_UP_R  [doc] warning failed to find a target Model for curve: SubDeformer::Grr_DWN_R  [doc] warning failed to find a target Model for curve: SubDeformer::Smile_R  [doc] warning failed to find a target Model for curve: SubDeformer::Sad_R  [doc] warning failed to find a target Model for curve: SubDeformer::Small_R  [doc] warning failed to find a target Model for curve: SubDeformer::Large_R  [doc] warning failed to find a target Model for curve: SubDeformer::Mouth_UP  [doc] warning failed to find a target Model for curve: SubDeformer::Mouth_DWN  [doc] warning failed to find a target Model for curve: SubDeformer::Mouth_L  [doc] warning failed to find a target Model for curve: SubDeformer::Mouth_R  [doc] warning failed to find a target Model for curve: SubDeformer::Lips_MID_UP  [doc] warning failed to find a target Model for curve: SubDeformer::Lips_MID_DW  [doc] warning failed to find a target Model for curve: SubDeformer::U  [doc] warning failed to find a target Model for curve: SubDeformer::M  [doc] warning failed to find a target Model for curve: SubDeformer::O  [doc] warning failed to find a target Model for curve: SubDeformer::MouthBank_R  [doc] warning failed to find a target Model for curve: SubDeformer::MouthBank_L  [doc] warning failed to find a target Model for curve: SubDeformer::Hollow_R  [doc] warning failed to find a target Model for curve: SubDeformer::Inflate_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_Open_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_Close_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_Close_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_Open_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowIN_UP_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowIN_DWN_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowIN_Fronce_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowMID_UP_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowMID_DWN_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowOUT_UP_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowOUT_DWN_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_A_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_B_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_A_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_B_R  [doc] warning failed to find a target Model for curve: SubDeformer::Grr_UP_L  [doc] warning failed to find a target Model for curve: SubDeformer::Grr_DWN_L  [doc] warning failed to find a target Model for curve: SubDeformer::Smile_L  [doc] warning failed to find a target Model for curve: SubDeformer::Sad_L  [doc] warning failed to find a target Model for curve: SubDeformer::Small_L  [doc] warning failed to find a target Model for curve: SubDeformer::Large_L  [doc] warning failed to find a target Model for curve: SubDeformer::Hollow_L  [doc] warning failed to find a target Model for curve: SubDeformer::Inflate_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_Open_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_Close_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_Close_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_Open_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowIN_UP_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowIN_DWN_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowIN_Fronce_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowMID_UP_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowMID_DWN_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowOUT_UP_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowOUT_DWN_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_A_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_B_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_A_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_B_L  [doc] warning failed to find a target Model for curve: SubDeformer::Grr_UP_R  [doc] warning failed to find a target Model for curve: SubDeformer::Grr_DWN_R  [doc] warning failed to find a target Model for curve: SubDeformer::Smile_R  [doc] warning failed to find a target Model for curve: SubDeformer::Sad_R  [doc] warning failed to find a target Model for curve: SubDeformer::Small_R  [doc] warning failed to find a target Model for curve: SubDeformer::Large_R  [doc] warning failed to find a target Model for curve: SubDeformer::Mouth_UP  [doc] warning failed to find a target Model for curve: SubDeformer::Mouth_DWN  [doc] warning failed to find a target Model for curve: SubDeformer::Mouth_L  [doc] warning failed to find a target Model for curve: SubDeformer::Mouth_R  [doc] warning failed to find a target Model for curve: SubDeformer::Lips_MID_UP  [doc] warning failed to find a target Model for curve: SubDeformer::Lips_MID_DW  [doc] warning failed to find a target Model for curve: SubDeformer::U  [doc] warning failed to find a target Model for curve: SubDeformer::M  [doc] warning failed to find a target Model for curve: SubDeformer::O  [doc] warning failed to find a target Model for curve: SubDeformer::MouthBank_R  [doc] warning failed to find a target Model for curve: SubDeformer::MouthBank_L  [doc] warning failed to find a target Model for curve: SubDeformer::Hollow_R  [doc] warning failed to find a target Model for curve: SubDeformer::Inflate_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_Open_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_Close_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_Close_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_Open_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowIN_UP_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowIN_DWN_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowIN_Fronce_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowMID_UP_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowMID_DWN_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowOUT_UP_R  [doc] warning failed to find a target Model for curve: SubDeformer::BrowOUT_DWN_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_A_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_B_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_A_R  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_B_R  [doc] warning failed to find a target Model for curve: SubDeformer::Grr_UP_L  [doc] warning failed to find a target Model for curve: SubDeformer::Grr_DWN_L  [doc] warning failed to find a target Model for curve: SubDeformer::Smile_L  [doc] warning failed to find a target Model for curve: SubDeformer::Sad_L  [doc] warning failed to find a target Model for curve: SubDeformer::Small_L  [doc] warning failed to find a target Model for curve: SubDeformer::Large_L  [doc] warning failed to find a target Model for curve: SubDeformer::Hollow_L  [doc] warning failed to find a target Model for curve: SubDeformer::Inflate_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_Open_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_Close_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_Close_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_Open_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowIN_UP_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowIN_DWN_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowIN_Fronce_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowMID_UP_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowMID_DWN_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowOUT_UP_L  [doc] warning failed to find a target Model for curve: SubDeformer::BrowOUT_DWN_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_A_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidUP_B_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_A_L  [doc] warning failed to find a target Model for curve: SubDeformer::LidDWN_B_L
visual results for akeyboy_sample (added a DirectionalLight for better visuals and activated Animation Looping)

This file seems to have now full support, textures ar eloaded in automatically with the fbx file, no visual bugs I found.

visual results for e-LysE.fbx (added a DirectionalLight for better visuals and activated Animation Looping)
quick notes; compensate scale fails
textures loaded correctly
all animations included

compensate scale fails for jump

compensate scale fails for jump_end

compensate scale fails for run

visual result for Skysurfer.fbx (added a Directional Light for better visuals and activated Animation Looping)
this fbx has blendshapes for facial animations.
all included animations have such a visual issue so it makes little sense to record gifs for this file.

@RevoluPowered Want to make you aware this older issue exist.

@myclay what are you using to make the models in, would be nice to know, I can look into it further then?
Right now we are working on getting a license for 3DS Max, we have a Maya license already, but they get very pricey.

Those where the included example files of Akeytsu which is sold by Nukeygara.
https://www.nukeygara.com/
https://www.nukeygara.com/akeytsu/free-characters
The rigs and animations where made with Akeytsu.
Programs used for the Skysurfer and E-lyse could be Maya and ZBrush since the creator, Etienne "Vexod14" Beschet uses those tools.
I personally use mainly Blender and ZBrush and would love to use Akeytsu too in combination with Godot.

Akeytsu is now free to use, btw https://www.nukeygara.com/blog/news/a-new-page-for-akeytsu

This is probably fixed with the new FBX importer using FBX2glTF.
You can test it in Godot 4.0 alpha 6: https://godotengine.org/article/dev-snapshot-godot-4-0-alpha-6
This new importer might also be backported for the 3.x branch eventually.
If you still find issues with these models using the new importer, we suggest opening a new issue with details about the problems in Godot 4.0 alpha 6 or later.


Page.printToPDF landscape mode not working

Howdy 👋
First of all: thanks for the awesome library 🎉  I'm trying to use it with Ember-FastBoot to build a server-side PDF render for an app (long story).
I'm trying to get it to print using landscape but it's not working: const pdfData = await Page.printToPDF({ landscape: true });
Here is the rest of my code (not that I think it's relevant):
    const chrome = await chromeLauncher.launch({
      chromeFlags: [
        // I tried swapping these around but it didn't seem to do anything
        '--window-size=1440,1080',
        '--disable-gpu',
        '--headless',
      ],
    });

    const protocol = await cdp({ port: chrome.port });

    const { Page } = protocol;
    await Page.enable();

    const datauri = new DataURI();
    datauri.format('.html', html);

    await Page.navigate({ url: datauri.content });
    await Page.loadEventFired();
    const pdfData = await Page.printToPDF({ landscape: true });

    const pdfBuffer = new Buffer(pdfData.data, 'base64');

    await writeFilePromise('./test.pdf', pdfBuffer);

As you can see I took inspiration from another issue you solved with someone else re: the datauri navigation.
Is there anything I could try to debug the landscape issue?

Hey, thanks! :)
What version of Chrome are you using? Older versions have a simpler (no parameters) Page.printToPDF method. See #157, maybe it's the same scenario.

I have tried to use Chrome Canary v61. But I still can not print with params. Could you help me check it?

@tamdao I created a wiki page for that: Print page to PDF. Does it work for you as is?

I can confirm that this is working with Chrome 61 (currently canary).
I'm happy to close this issue but should I leave it open to track @tamdao 's issues?

The issue from my css. Because I use @page css, the css change margin on page. @mansona you can close this issue. Thanks


[Build type] Reintroduce Build OnSave

Hi,
Since the v1.4.2 update, the OnSave value has been removed from the parameter Build type.
When we build with custom build, we can't relaunch it when we save a file (especially when launching hot reloads with Blazor).
Can we reintroduce the OnSave concept for custom builds ?
In my case, I have this command:
"build-css": "npx postcss ./Tailwind/css --base ./Tailwind/css --dir ./wwwroot/css --watch --verbose --poll --no-map --ext --config ./Tailwind/postcss.config.js",

Thanks

My apologies - I did not foresee that being an issue. I will be sure to re-add the feature in the next release.

Added in 1.4.3


Epic Fail if i use for Unity 2017

when i import using unity 2017 project ,it fail ,, so this project only of 2019 ?

It should work in Unity 2018.3 and newer because it uses C# 7 features.

ah ok cool


Minor code style update

Fixed up var declarations, const should be used when not reassigning vars to make sure that the assignment isn't accidentally swapped out.
Made systemButtonOpacity part of the component rather than letting it float outside
Simplify the computeActiveOpacity method

I don't find these changes to improve the code, sorry.

No problem @ide. Just out of curiosity, could you tell me why you'd prefer to keep them as lets rather than swap them to consts?

const doesn't really offer more than let in this case. At the level of individual functions it's not a problem to see if something gets reassigned or not, your brain has enough "RAM" to think about the whole function without const vs. let being that helpful. So then I find that mixing const and let in the same function makes it harder to read because syntactically there's extra visual complexity because const and let are different lengths -- one study showed that visual alignment of code was one of the things that makes it easier to read -- and if you make a change to the code in the future that adds/removes reassignment you need to change const to let or vice versa and I find the cost of that thrash higher than the benefit from the info that const or let communicates.

Thanks for taking the time out to explain this.
I see what you mean.
It's always good to hear another developer's perspective.


Base inheritance, instantiation and cloning - common problems by customization

According to #14 the inheritance, instantiation and cloning can be reduced to a description like this:
var Descendant = Ancestor.extend({x:1})

    prototype = Ancestor.prototype.clone()
        prototype = Object.create(Ancestor.prototype)
        prototype.build()
            prototype.id = id()
    prototype.merge({x:1})
        shallowCopy(prototype, {x:1})

var instance = new Descendant({x:1})

    instance = Object.create(Descendant.prototype)
    instance.init()
        instance.build()
            instance.id = id()
        instance.merge({x:1})
            shallowCopy(instance, {x:1})
        instance.configure()

var copy = instance.clone()

    copy = Object.create(instance)
    copy.build()
        copy.id = id()

Let's check scenarios where this call tree causes or does not cause problems.

Basic inheritance
What we need:

cloning the prototype - ok
shallow copy the properties - ok

What we get:
var Descendant = Ancestor.extend({x:1})
    prototype = Ancestor.prototype.clone()
        prototype.build()
            prototype.id = id()
    prototype.merge({x:1})
        shallowCopy(prototype, {x:1})

critique
The build is called as a plus function. We don't necessary need id by every single object, just the ones we want to store in a HashSet.

Calling merge by instantiation:
What we need:

using the merge to shallowCopy the properties of the constructor arguments - ok
let us configure the instance when the merge is complete, so we can use both the inherited and the newly given properties for example to connect to a database, etc... - ok

What we get:
var instance = new Descendant({x:1})

    instance = Object.create(Descendant.prototype)
    instance.init()
        instance.build()
            instance.id = id()
        instance.merge({x:1})
            shallowCopy(instance, {x:1})
        instance.configure()

critique:
The build is called as a plus function. We don't necessary need id by every single object, just by the ones we want to store in a HashSet.
possible solutions

don't call the build
remove the id creation from the build

Configuring with arguments by instantiation:
What we need:

send the arguments to the configure

What we get:
var instance = new Descendant({x:1})

    instance = Object.create(Descendant.prototype)
    instance.init()
        instance.build()
            instance.id = id()
        instance.merge({x:1})
            shallowCopy(instance, {x:1})
        instance.configure()

critique:
Merge is called with the arguments and not configure.
possible solutions

override the init() remove the merge and pass the arguments to the configure()

With the gathered solutions:
var Descendant = Ancestor.extend({x:1})

    prototype = Ancestor.prototype.clone()
        prototype = Object.create(Ancestor.prototype)
        prototype.build()
    prototype.merge({x:1})
        shallowCopy(prototype, {x:1})

var instance = new Descendant({x:1})

    instance = Object.create(Descendant.prototype)
    instance.build()
    instance.init()
        instance.merge({x:1})
            shallowCopy(instance, {x:1})
        instance.configure()

var copy = instance.clone()

    copy = Object.create(instance)
    copy.build()

Let's assume we need the id:
var Descendant = Ancestor.extend({x:1})

    prototype = Ancestor.prototype.clone()
        prototype = Object.create(Ancestor.prototype)
        prototype.build()
            prototype.id = id() // NOT ALLOWED
    prototype.merge({x:1})
        shallowCopy(prototype, {x:1})

var instance = new Descendant({x:1})

    instance = Object.create(Descendant.prototype)
    instance.build()
        instance.id = id() // REQUIRED
    instance.init()
        instance.merge({x:1})
            shallowCopy(instance, {x:1})
        instance.configure()

var copy = instance.clone()

    copy = Object.create(instance)
    copy.build()
        copy.id = id() // REQUIRED

How to avoid creating the id by inheritance?

we could check whether we are talking about a prototype: this.constructor.prototype === this

Do we really need calling the build() by inheritance?
I think so.

Merging with deep copy by inheritance and instantiation
What we need:

merge with deep copy by inheritance
merge with deep copy by instantiation

What we get:
Ancestor.prototype = {x: {y:1}}
var Descendant = Ancestor.extend({x:{z:2}})

    prototype = Ancestor.prototype.clone()
        prototype = Object.create(Ancestor.prototype)
        prototype.build()
            prototype.id = id() // NOT ALLOWED
            prototype.x = Object.create(Ancestor.prototype.x)
    prototype.merge({x:{z:2}})
        backup = prototype.x; // y:1
        shallowCopy(prototype, {x:{z:2}})
        prototype.x = merge(backup, {z:2})

var instance = new Descendant({x:{q:3}})

    instance = Object.create(Descendant.prototype)
    instance.build()
        instance.id = id() // REQUIRED
        instance.x = Object.create(Descendant.prototype.x)
    instance.init()
        instance.merge({x:{q:3}})
            backup = instance.x; // y:1, z:2
            shallowCopy(instance, {x:{q:3}})
            instance.x = merge(backup, {q:3})
        instance.configure()

critique:
It is complicated to create a backup for every single param. We don't need half of the build in the inheritance.
possible solutions
a.) not working move half of the build to a different method and call them from a 3rd method
Ancestor.prototype = {x: {y:1}}
var Descendant = Ancestor.extend({x:{z:2}})

    prototype = Ancestor.prototype.clone()
        prototype = Object.create(Ancestor.prototype)
        prototype.inherit()
            prototype.x = Object.create(Ancestor.prototype.x)
    prototype.merge({x:{z:2}})
        backup = prototype.x; // y:1
        shallowCopy(prototype, {x:{z:2}})
        prototype.x = merge(backup, {z:2})

var instance = new Descendant({x:{q:3}})

    instance = Object.create(Descendant.prototype)
    instance.inherit()
        instance.x = Object.create(Descendant.prototype.x)
    instance.build()
        instance.id = id()
    instance.init()
        instance.merge({x:{q:3}})
            backup = instance.x; // y:1, z:2
            shallowCopy(instance, {x:{q:3}})
            instance.x = merge(backup, {q:3})
        instance.configure()

var copy = instance.clone()

    copy = Object.create(instance)
    copy.inherit()
        copy.x = Object.create(instance.x)
    copy.build()
        copy.id = id() // REQUIRED

    prototype = Ancestor.prototype.clone()
        prototype = Object.create(Ancestor.prototype)
        prototype.inherit()
            prototype.x = Object.create(Ancestor.prototype.x)
        // NO BUILD HERE

var copy = instance.clone()

    copy = Object.create(instance)
    copy.inherit()
        copy.x = Object.create(instance.x)
    copy.build() // BUILD REQUIRED HERE
        copy.id = id()

We cannot even send a flag, because both use clone...
I defined extend() as clone() + merge(). For example:
merge([1,2,3], [4,5,6]) // the original array will be pushed
extend([1,2,3], [4,5,6]) // the clone of the original array will be pushed

The same happens by classes.
merge(prototype, {x:1}) // the prototype will be modified
extend(prototype, {x:1}) // the clone of the prototype will be modified

According to this, we have a method, which is called by the cloning and instantiation, but must not be called by inheritance. This is a problem, since we defined the inheritance as clone + merge, so everything called by cloning is called by inheritance. We have to rethink this:
inheritance = clone - y + merge
clone = x + y
instantiation = clone + merge + configure

The only thing we can do here:
Ancestor.prototype = {x: {y:1}}
var Descendant = Ancestor.extend({x:{z:2}})
    prototype = Ancestor.prototype.inherit()
        prototype = Ancestor.prototype.XXX()
            prototype = Object.create(Ancestor.prototype)
        prototype.YYY()
            prototype.x = Object.create(Ancestor.prototype.x)
    prototype.merge({x:{z:2}})
        backup = prototype.x; // y:1
        shallowCopy(prototype, {x:{z:2}})
        prototype.x = merge(backup, {z:2})

var instance = new Descendant({x:{q:3}})

    instance = Object.create(Descendant.prototype) // CANNOT BE MOVED
    instance.YYY()
        instance.x = Object.create(Descendant.prototype.x)
    instance.build()
        instance.id = id()
    instance.init()
        instance.merge({x:{q:3}})
            backup = instance.x; // y:1, z:2
            shallowCopy(instance, {x:{q:3}})
            instance.x = merge(backup, {q:3})
        instance.configure()

var copy = instance.clone()
    instance.inherit()
        copy = instance.XXX()
            copy = Object.create(instance)
        copy.YYY()
            copy.x = Object.create(instance.x)
    copy.build()
        copy.id = id() // REQUIRED

the merge is still not the best...

Ancestor.prototype = {x: {y:1}}
var Descendant = Ancestor.extend({x:{z:2}})
    prototype = Ancestor.prototype.inherit()
        prototype = deepClone({x: shallowClone}, Ancestor.prototype);
    prototype.merge({x:{z:2}})
        deepCopy.call({x:merge}, prototype, {x:{z:2}})

var instance = new Descendant({x:{q:3}})

    instance = Object.create(Descendant.prototype) // CANNOT BE MOVED
    instance.inherit(flag)
        if flag
            instance = deepClone({"": echo, x: shallowClone}, instance);
        else
            instance = deepClone({x: shallowClone}, instance);
    instance.build()
        instance.id = id()
    instance.init()
        instance.merge({x:{q:3}})
            deepCopy.call({x:merge}, instance, {x:{q:3}})
        instance.configure()

var copy = instance.clone()
    instance.inherit()
        instance = deepClone({x: shallowClone}, instance);
    copy.build()
        copy.id = id() // REQUIRED

I don't like the idea to use clone flag, but it is possible with it...
another way:
    instance = Object.create(Descendant.prototype) // CANNOT BE MOVED
    instance.inherit()
        if instance === instance.constructor.prototype
            instance = deepClone({"": echo, x: shallowClone}, instance);
        else
            instance = deepClone({x: shallowClone}, instance);

would this work by clone?
I guess yes, but I have to sleep now.

The HashSet -> Subscription inheritance is a great example that the current approach is indeed error prone. I spent about an hour to debug, forgot override the configure, because there was no bug, so addAll was called on []. Forgot that merge() is not called by init(), so the addAll was called with the sources, etc... In top of that the custom Errors was printed as Stack objects #70 It was hard to write, since the merge code too, instead of a few lines of deepCopy configuration I had to write a lot of duplicated code. #67
    items: {},
    init: function () {
        this.build();
        this.configure.apply(this, arguments);
    },
    build: function () {
        Base.prototype.build.call(this);
        var inheritedItems = this.toArray();
        this.items = {};
        if (inheritedItems.length)
            this.addAll.apply(this, inheritedItems);
    },
    configure: function (item) {
        this.addAll.apply(this, arguments);
    },

    init: function () {
        this.build();
        this.merge.apply(this, arguments);
        this.configure();
    },
    merge: function (source) {
        for (var sourceIndex in arguments) {
            source = arguments[sourceIndex];
            if (source === undefined || source === null)
                continue;
            if (!(source instanceof Object))
                throw new InvalidArguments();

            if (source.items !== undefined) {
                if (!(source.items instanceof Array))
                    throw new Subscription.ItemsRequired();
                if (source.items.length)
                    this.addAll.apply(this, source.items);
            }

            var backup = {
                items: this.items
            };

            shallowCopy(this, source);
            shallowCopy(this, backup);
        }
        return this;
    },
    configure: function () {
    },

I think I'll move the build to the constructor and let the init decide whether it wants to merge or not. by default the init() will merge and call the configure() but it will be easy to override that with custom logic.
I think the id() is something exceptional in this case, and it does not cause any issue, so I won't fix this issue until I really need to find out something new in the topic.


Correctly indicate a lack of nominating rights for logged in members

Logged in members without nominating rights see a misleading view:

The situation here should reflect the reality (the nominations are open, but you do not have permissions to nominate)

Fixed in https://github.com/WorldconVotingSystems/nomnom/commit/454e60225f6e8674ae13cff3dcb242f7e4523865


Upgrade system docker to a newer stable version

Our current system docker is based on docker 1.11.2, https://github.com/rancher/docker/commits/system-docker-v1.11.2
We need to upgrade it to solve a lot of legacy issues.
Related issues:
https://github.com/rancher/os/issues/2163
https://github.com/rancher/os/issues/2165

We have upgraded the system-docker to docker-ce 17.06.
[root@rancher rancher]# system-docker -v
Docker version 17.06-ros3, build fa7c1dad

System-docker works fine when upgrading to 17.06
Close it.


Mol2 files from API link are invalid

The mol2 files from the API link are wrong for two reasons:

Every line has an extra newline
There is no file extension (.mol2) which means most programs can't recognize it

This is my fault. I'll fix it

a5d7799 was incorrect due to the mimetype. a7cc659 fixes it for good.


Just another UNKNOWN_CODE_PLEASE_REPORT

I get this with this query "select * from payments for share lock in share mode".
Thank you.

Thank you! Looks like this is code 3568 added in 8.0.1; it will be resolved with PR #2386


Add custom marker for checking validation

Add custom marker for running model validation tests

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

Project coverage is 93.05%. Comparing base (3faa7f5) to head (f6836f8).
Report is 41 commits behind head on develop.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #3209      +/-   ##
===========================================
- Coverage    93.14%   93.05%   -0.10%
===========================================
  Files           66       66
  Lines        14248    14248
===========================================
- Hits         13272    13259      -13
- Misses         976      989      +13

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


feat: Add fixtures for end-to-end transfer tests

What this PR changes/adds
Introduce helpers for testing end-to-end transfers.
Why it does that
Ease end-to-end testing in downstream repositories.
Linked Issue(s)
Closes #3282
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.

Codecov Report
Patch and project coverage have no change.

Comparison is base (60957b2) 72.41% compared to head (9fc7fef) 72.41%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3285   +/-   ##
=======================================
  Coverage   72.41%   72.41%
=======================================
  Files         843      843
  Lines       17039    17039
  Branches      949      949
=======================================
  Hits        12339    12339
  Misses       4306     4306
  Partials      394      394

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


httpcli and httpscli failure on gcc4.4 portability test

https://grpc-testing.appspot.com/job/gRPC_portability_master/481/language=c,scenario=linux_x64_gcc4.4/testReport/junit/(root)/tests/bins_dbg_httpcli_test/ and https://grpc-testing.appspot.com/job/gRPC_portability_master/481/language=c,scenario=linux_x64_gcc4.4/testReport/junit/(root)/tests/bins_dbg_httpscli_test/
D0226 22:01:27.240215380   17660 env_linux.c:77]             Warning: insecure environment read function 'getenv' used
D0226 22:01:27.240381929   17660 env_linux.c:77]             Warning: insecure environment read function 'getenv' used
E0226 22:01:27.240932752   17660 tcp_client_posix.c:173]     failed to connect to 'ipv6:[::1]:32767': socket error: connection refused
/usr/bin/env: python2.7: No such file or directory
D0226 22:01:32.242924042   17660 test_config.c:159]          test slowdown: machine=1.000000 build=1.000000 total=1.000000
D0226 22:01:32.243027323   17660 env_linux.c:77]             Warning: insecure environment read function 'getenv' used
I0226 22:01:32.243043037   17660 httpscli_test.c:79]         test_get
I0226 22:01:32.243051205   17660 httpscli_test.c:82]         requesting from localhost:1105
E0226 22:01:32.244421395   17719 tcp_client_posix.c:173]     failed to connect to 'ipv6:[::1]:1105': socket error: connection refused
E0226 22:01:32.244550439   17719 tcp_client_posix.c:173]     failed to connect to 'ipv4:<IP_ADDRESS>:1105': socket error: connection refused
E0226 22:01:32.244590640   17719 httpscli_test.c:63]         assertion failed: response

*******************************
Caught signal 6
bins/dbg/httpscli_test[0x579235]
/lib/libpthread.so.0(+0xeff0)[0x7f8cb2cb9ff0]
/lib/libc.so.6(gsignal+0x35)[0x7f8cb2970f15]
/lib/libc.so.6(abort+0x180)[0x7f8cb2973d20]
bins/dbg/httpscli_test[0x4043ca]
bins/dbg/httpscli_test[0x406202]
bins/dbg/httpscli_test[0x406731]
bins/dbg/httpscli_test[0x406687]
bins/dbg/httpscli_test[0x407ad0]
bins/dbg/httpscli_test[0x499104]
bins/dbg/httpscli_test[0x423e44]
/lib/libpthread.so.0(+0x68ca)[0x7f8cb2cb18ca]
/lib/libc.so.6(clone+0x6d)[0x7f8cb2a17abd]

See #4878

@nicolasnoble is working on it.

Seen again today.

Seen on virtually all builds today:
E.g.
https://grpc-testing.appspot.com/job/gRPC_portability_master/934/

Same today https://grpc-testing.appspot.com/job/gRPC_portability_master/966/

Not quite sure the tests got fixed, let's close after confirming the fix.

It looks #5574 has fixed httpcli_test, but httpscli_test is still failing:
https://grpc-testing.appspot.com/job/gRPC_portability_master/978/language=c,scenario=linux_x64_gcc4.4/testReport/(root)/tests/bins_dbg_httpscli_test/

Both httpcli and httpscli are failing:
httpcli:
https://grpc-testing.appspot.com/job/gRPC_portability_master/972/language=c,scenario=linux_x64_gcc4.4/testReport/junit/(root)/tests/bins_dbg_httpcli_test/
https://grpc-testing.appspot.com/job/gRPC_portability_master/970/language=c,scenario=linux_x64_gcc4.4/testReport/junit/(root)/tests/bins_dbg_httpcli_test/
https://grpc-testing.appspot.com/job/gRPC_portability_master/968/language=c,scenario=linux_x64_gcc4.4/testReport/junit/(root)/tests/bins_dbg_httpcli_test/
https://grpc-testing.appspot.com/job/gRPC_portability_master/971/language=c,scenario=linux_x64_gcc4.4/testReport/junit/(root)/tests/bins_dbg_httpcli_test/
httpscli:
https://grpc-testing.appspot.com/job/gRPC_portability_master/968/language=c,scenario=linux_x64_gcc4.4/testReport/junit/(root)/tests/bins_dbg_httpscli_test/
https://grpc-testing.appspot.com/job/gRPC_portability_master/970/language=c,scenario=linux_x64_gcc4.4/testReport/junit/(root)/tests/bins_dbg_httpscli_test/
https://grpc-testing.appspot.com/job/gRPC_portability_master/971/language=c,scenario=linux_x64_gcc4.4/testReport/junit/(root)/tests/bins_dbg_httpscli_test/
https://grpc-testing.appspot.com/job/gRPC_portability_master/972/language=c,scenario=linux_x64_gcc4.4/testReport/junit/(root)/tests/bins_dbg_httpscli_test/
etc. etc.

Seems fixed: https://grpc-testing.appspot.com/job/gRPC_portability_master/986/


Feature request resize Font on Text Size and Aligh Text

First of all I love this package and it makes my life a lot easier. I was just wondering if you were ever able to:
A.) Resize the font of the text to fit
and
B.) Align the text differently like center, left, right?

Hey @DennisRein,
Thanks for the question!
You are able to resize the text size using the fontSize option. This won't necessarily make the text fit your specified region, but it will at least let you manually set the size.
As for the alignment, this is a good feature idae! However, I don't have the bandwidth right now to create this feature. PRs are welcome though 😄


Training result

Hi. Did you reproduce the results of this paper which were the same as the original paper? I'm the beginner too, I want to try to reproduce it. Thanks.

Not yet. The result is lower than that of the paper, but you can learn the basic idea of the algorithm anyway.  You can use this code as a start and try to improve it.


How to append vim.api.nvim_get_runtime_file('', true) to Lua.workspace.library?

I don't want to manually adjust my workspace library whenever I install or remove a plugin. Luckily vim.api.nvim_get_runtime_file('', true) produces all the paths that nvim's lua interpreter looks for libraries for.
Unfortunately the settings in the coc-configurations are done with a json file and there is no syntax to do a function call there to populate any options, as far as I could gather.
Is there some way to put all those paths into Lua.workspace.library in a different way? Maybe some special string?

From what I found, you can leverage coc#config to change the configuration at runtime (or use g:coc_user_config). This works for me:
vim.cmd([[
  autocmd FileType lua call coc#config('Lua.workspace.library', nvim_get_runtime_file('', 1))
]])


Add a GitHub action to auto-assign Mentors for every PR

I would like to add a GitHub action to auto-assign mentors for every PR. It sometimes becomes hectic for the mentors to take a look at all the Projects for the PRs made by the Contributors. This action would give a nice notification about reviewing the pr and make things pretty easy for the mentor. It would automatically ask for reviews by the mentors on every pr created.
Demo :

@swapnilsparsh Can I work on this?

@swapnilsparsh Can I work on this as a part of DWOC?
Great idea.


how to get high or low prices ?

from the tutorials, the data are like:
date                      AAPL GOOG
2010-01-02     10.0     12.0
so I don't know how to get other prices, like high, low, etc.
in the run method of TradingAlgorithm class in the algorithm.py
it says:
      If pandas.DataFrame is provided, it must have the
           following structure:
           * column names must be the different asset identifiers
           * index must be DatetimeIndex
           * array contents should be price info.

any ideas?
thanks for advance.

Hi @FayolChang , It looks like the DataFrameSource yields data with only price and volume fields (and it looks like the volume is [hardcoded] (https://github.com/quantopian/zipline/blob/242175350958ed0936aa43461adc4d32d858d4ed/zipline/sources/data_frame_source.py#L86-L86)!).   It does that by ingesting a DataFrame (2D) of prices keyed by sid/datetime.  However, the [DataPanelSource] (https://github.com/quantopian/zipline/blob/242175350958ed0936aa43461adc4d32d858d4ed/zipline/sources/data_frame_source.py#L97-L97) ingests a pandas DataPanel (3D) with more attributes to each data point.  You might take a look at [this test] (https://github.com/quantopian/zipline/blob/dc964a7e7da7e975b22fabfe962d2210704c1d6b/tests/test_sources.py#L67), which uses the DataPanelSource to yield events with OHLCV from yahoo data.

Thank you very much, @richafrank , problem solved!