SyntaxError: Unexpected token =

I'm using jest to test some of my files within Electron. It worked for a long time but now I'm getting the following error:
> jest assignment.test.js --coverage

 FAIL  tests\assignment\assignment.test.js
  ● Test suite failed to run

    SyntaxError: Unexpected token =

      at transformAndBuildScript (node_modules\jest-runtime\build\transform.js:320:12)
      at Object.<anonymous> (src\model\Compiler\SLX\SimplexCompiler.js:8:79)
      at Object.<anonymous> (tests\assignment\assignment.test.js:5:25)

I once got the following message:
[BABEL] Note: The code generator has deoptimised the styling of "E:/Masterthesis/Simplex-Electron/src/model/Simplex-Lang/SimplexParser.js" as it exceeds the max of "100KB".
But this never appears again.

@dmitriiabramov is this the issue you had with babel and bigger files?

That message should be unrelated and is coming from babel. It seems like there is an issue with your code here and without a repro (a github repo that can be cloned and npm tested) we are unable to help.

I never had this message prior to this problem.
You can clone the repository https://github.com/fdeitelhoff/Simplex-Electron. Currently all work is done within the develop branch.

@thymikee should not be related.
i just ran tests on the repro repo and all of the test ran for me (there were other unrelated errors though)
@fdeitelhoff can you try running jest with --no-cache flag?

@dmitriiabramov That's weird. Tested it with the --no-cache flag and got the same error.


Spacer stretches button to be full width on Android when being placed before button

When using a spacer before a button, the button gets stretched to full width on Android 4.4 (Litmus test) and a couple more devices. Interestingly, when a spacer is used after a button, everything is fine. On almost all other devices, everything works as expected.
How can we reproduce this bug?
Just use the following code and run a Litmus test:
<container>
    <row>
        <columns>
            <spacer size="16"></spacer>

some text

                <button class="" href="#">Click Me</button>

        </columns>
    </row>
</container>

What did you expect to happen?
Button should not be stretched to full width even if a spacer is used before in the code
What happened instead?
Button is stretched to full width
What email clients does this happen in?
Litmus Android 4.4

I don't have a Litmus account, does it behave the same if you place the spacer just before the row?
<container>
	<spacer size="16"></spacer>
    <row>
        <columns>

some text

                <button class="" href="#">Click Me</button>

        </columns>
    </row>
</container>

I was trying to reproduce this issue on emailonacid, but could not. Therefore I assume it's a litmus issue, closing this one therefore.


Add support for controlling clone depth

I'm also using my own plugins with Plug and for the sake of development I don't want the depth to be specified, so I'd like to be able to specify something like:
Plug 'git@github.com:kkoomen/vim-doge', { 'do': { -> doge#install() }, 'depth': 0 }

It should cover the following scenarios:

If it's 0 then it should not pass the --depth flag to the git clone command
If it's above 0 then it should add it to the git clone command with the given depth value: --depth {depth}
If the depth key doesn't exists then add --depth 1 as a fallback

$ vim --version
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Oct  7 2020 23:36:35)
macOS version
Included patches: 1-1800
Compiled by Homebrew
Huge version without GUI.  Features included (+) or not (-):
+acl               -farsi             +mouse_sgr         +tag_binary
+arabic            +file_in_path      -mouse_sysmouse    -tag_old_static
+autocmd           +find_in_path      +mouse_urxvt       -tag_any_white
+autochdir         +float             +mouse_xterm       -tcl
-autoservername    +folding           +multi_byte        +termguicolors
-balloon_eval      -footer            +multi_lang        +terminal
+balloon_eval_term +fork()            -mzscheme          +terminfo
-browse            +gettext           +netbeans_intg     +termresponse
++builtin_terms    -hangul_input      +num64             +textobjects
+byte_offset       +iconv             +packages          +textprop
+channel           +insert_expand     +path_extra        +timers
+cindent           +ipv6              +perl              +title
-clientserver      +job               +persistent_undo   -toolbar
+clipboard         +jumplist          +popupwin          +user_commands
+cmdline_compl     +keymap            +postscript        +vartabs
+cmdline_hist      +lambda            +printer           +vertsplit
+cmdline_info      +langmap           +profile           +virtualedit
+comments          +libcall           -python            +visual
+conceal           +linebreak         +python3           +visualextra
+cryptv            +lispindent        +quickfix          +viminfo
+cscope            +listcmds          +reltime           +vreplace
+cursorbind        +localmap          +rightleft         +wildignore
+cursorshape       +lua               +ruby              +wildmenu
+dialog_con        +menu              +scrollbind        +windows
+diff              +mksession         +signs             +writebackup
+digraphs          +modify_fname      +smartindent       -X11
-dnd               +mouse             -sound             -xfontset
-ebcdic            -mouseshape        +spell             -xim
+emacs_tags        +mouse_dec         +startuptime       -xpm
+eval              -mouse_gpm         +statusline        -xsmp
+ex_extra          -mouse_jsbterm     -sun_workshop      -xterm_clipboard
+extra_search      +mouse_netterm     +syntax            -xterm_save
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
       defaults file: "$VIMRUNTIME/defaults.vim"
  fall-back for $VIM: "/usr/local/share/vim"
Compilation: clang -c -I. -Iproto -DHAVE_CONFIG_H   -DMACOS_X -DMACOS_X_DARWIN  -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: clang   -L. -fstack-protector-strong -L/usr/local/lib -L/usr/local/opt/libyaml/lib<EMAIL_ADDRESS>-L/usr/local/opt/readline/lib  -L/usr/local/lib -o vim        -lncurses -liconv -lintl -framework AppKit  -L/usr/local/opt/lua/lib -llua5.3 -mmacosx-version-min=10.15 -fstack-protector-strong -L/usr/local/lib  -L/usr/local/Cellar/perl/5.32.0/lib/perl5/5.32.0/darwin-thread-multi-2level/CORE -lperl -lm -lutil -lc<EMAIL_ADDRESS>-lpython3.9 -framework CoreFoundation  -lruby.2.7

Type:

[ ] Bug
[ ] Enhancement
[x] Feature Request
[ ] Question

OS:

[ ] All/Other
[ ] Linux
[x] OS X
[ ] Windows

Vim:

[x] Terminal Vim
[ ] GVim
[ ] Neovim

vim-plug was primarily designed for ordinary plugin users rather than users with niche requirements, and we think it's important that we keep its feature set as small as possible. There are alternative plugin managers with extra features, so vim-plug can remain as an option that is more accessible and easier to use.
Since most users won't use the suggested feature, we're not going to implement it, but thanks for the suggestion.
Even if vim-plug doesn't provide the option, I believe you can achieve the behavior by implementing a post-update hook that runs git fetch --unshallow on fresh install.

https://github.com/junegunn/vim-plug#post-update-hooks

@junegunn Okay sure, but then how do I do
'do': { -> doge#install() } and 'do': 'git fetch --unshallow' in 1 command?

@junegunn

Write a function that does both.
function! BuildYCM(info)
  " info is a dictionary with 3 fields
  " - name:   name of the plugin
  " - status: 'installed', 'updated', or 'unchanged'
  " - force:  set on PlugInstall! or PlugUpdate!
  if a:info.status == 'installed' || a:info.force
    !./install.py
  endif
endfunction

Plug 'ycm-core/YouCompleteMe', { 'do': function('BuildYCM') }


Make extra-deps in stack.yaml optional

This seems to fix #28

@gilligan need to fix also usages :)

Sorry, should have actually tried it with some yaml with extra deps.. 😜
Or even better lets start adding some tests for this :)

Yeah there should be a minimal functional test (I remember @jmitchell wrote some already), but I don't know the status of that.

Superseeded by https://github.com/input-output-hk/stack2nix/pull/42


Incorrect DDC runtime cast failure.

We're seeing DDC runtime cast failures as follows:
Casting value of type '(dynamic) -> void' to incompatible type '(bottom) -> FutureOr<void>)'

This cast should succeed.

https://codereview.chromium.org/2671113002/

Is this error really in 1.22, and a blocker?  So we should merge the fix?

Yes, I will file a merge request.

https://github.com/dart-lang/sdk/issues/28654


WorkAction: Add coroutineScope member

Expected Behavior
abstract class UploadAct: WorkAction<WorkParameters.None> {
    override fun execute() {
        coroutineScope.launch {
            upload()
        }
    }

    private suspend fun upload() {}
}

Alternative:
Expose a java.util.concurrent.Executor to not depend on kotlinx-coroutines.
Current Behavior (optional)
abstract class UploadAct: WorkAction<WorkParameters.None> {
    override fun execute() = runBlocking {
      upload()
    }

    private suspend fun upload() {}
}

Context
I have a Gradle plugin written in Kotlin and I want to upload a file using WorkAction. This upload call is asynchronously and the call uses suspend, mostly enforced by the http client.
The current method void execute() does not support kotlin coroutines and you need to use runBlocking, which blocks the thread.
Gradle already supports executing tasks and work action in parallel. Ideally, the WorkQueue acts as a dispatcher and adds coroutineScope to each executing work action to not block the thread, to allow running multiple suspending work action in parallel.

Thank you for your interest in Gradle!
At this stage we won't add coroutines to our Java API. This issue will be closed.

You can have the WorkerExecutor injected in a worker action to submit more parallel work. See https://docs.gradle.org/current/userguide/custom_gradle_types.html#service_injection
If you want more concurrency control in Worker actions, please open an issue with use cases and requirements that would make it possible to e.g. use coroutines in a worker action.

@eskatos it should be great if there was a doc page about how to do that (working with coroutines in the Gradle world).
Is it planned?

If you want more concurrency control in Worker actions, please open an issue with use cases and requirements that would make it possible to e.g. use coroutines in a worker action.

What is the difference to this issue?
I understand you don't want to add kotlinx coroutines api to Gradle core, this is the reasons I added the java alternative: java.util.concurrent.Executor.
Regarding use-case: I want to upload a file to a http web server. This upload logic is already written and published in a Kotlin jvm library using suspend methods. I want to write my workaction in Kotlin to reuse my existing upload library. My current workaround blocks the whole thread of the work action by using runBlocking.
Is it okay to block the whole thread? I (and @JavierSegoviaCordoba) didn't found this in the doc page.

@hfhbd thanks for the feedback. Yes it is ok to block the task execution thread in a task action.
As for the issue management aspect, this issue is specifically geared towards coroutines and adding them. I understand you suggested another approach along the way but please, if you feel strongly about it, open another issue about exposing a managed Executor.


Updates to Ukraine content following UR

Updates to Ukraine content following UR
Trello card
Context
Changes proposed in this pull request
Guidance to review

Hi folks, this is ready for review when you get a sec @EllieNodder @GDW7
Thanks :)

Thanks for looking @EllieNodder :)


Bug: Getting thrown error message 5 times on initialization

If a user deletes the bin directory then re-launches the program and successfully creates their account they are greeted with the string
Record not found in the specified cluster printed five times in the console. Its possible that it is printed five times because of the 5 "non-special" records in the secure cluster of the _secure_.ost file.

This was happening on development branch. Not sure why but the problem seems to have been fixed before. closing

Nevermind I was able to recreate and fix


[sizing] fixes and enhancements

This PR:

fixes:

  File "/data/stas/benchmarks/cookbook/benchmarks/sizing/mm_flops.py", line 47, in <module>
    with open(args.output_file, 'w') as sys.stdout:
FileNotFoundError: [Errno 2] No such file or directory: '../results/mm.out'

now you can launch it from any dir and it'd work.

adds dependencies needed to run the scripts

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


Restore local prebuild option

The local prebuild feature appears to have been removed in version 5, specifically in this commit: https://github.com/prebuild/prebuild-install/commit/0593bf5ac5b331d9c8742e81e26866679b7d83d4
I'm bundling an NPM package that needs to be installable offline from a TGZ, since some users have firewall restrictions. One of the dependencies I'm bundling is keytar, which uses prebuild-install to install its native code.
With the local prebuild feature, I can easily make my package installable offline by adding the compiled native code for each platform to a "prebuilds" folder in my TGZ. With this feature removed in v5, it's a lot harder to do this as I need to add a preinstall script that copies the native code into the NPM cache, to fake out downloading it.
Since local prebuild seems like a useful feature for making packages installable offline, I'm not sure why it was considered unnecessary and removed. Please consider restoring this feature.

I'm not sure either. Would welcome a PR to restore it, as an opt-in feature and provided that the implementation is simple. It does feel slightly out of scope to me, considering that keytar could be using prebuildify instead.


chore: update the readme

Finetuner Client README.md needs to be updated.

do not forget to add changelog


feat(i18n): add estonian locale

Add Estonian locale

sry, this TODO comment is just a mistake. Please remove the comment line and merge


fix: attempt to map JSONSchema spec naming convention to local naming convention

…when property names from schema_extra are not found.
Description
Address rejection of schema_extra values using JSONSchema spec-compliant key names by mapping between the relevant naming conventions.
Closes
Fixes #3766

Thanks for reporting this and submitting a fix @charles-dyfis-net!
I'm not a fan of these regex based renaming solutions, as they can be tricky to maintain in some cases. I would prefer a more explicit approach. We could use dataclasses.field to provide an alias via metadata (e.g. multiple_of: float | None = field(metadata={"alias": "multipleOf"})

A wise objection -- going through the items one-at-a-time, there are some fixups (like schema_not) that the regex wouldn't have handled correctly.


Does GTX1070 8G memory cause memory unsatisfying?

I am using my photo which is 1000*900 size, it big, I am only using batch size 1, but it still throw this error:
 [1]    30985 killed     python3 train.py --logtostderr --train_dir=checkpoint

Means my memory is not engouh?

I think it is


🐛 fix(gen type): Allow all db users & db names

What kind of change does this PR introduce?
Bug fix. More info see: #616
Closes #616

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

8 of 8 (100.0%)  changed or added relevant lines in 1 file are covered.
22 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.009%) to 49.631%

Files with Coverage Reduction
New Missed Lines
%

internal/start/start.go
22
31.89%

Totals

Change from base Build<PHONE_NUMBER>:
0.009%

Covered Lines:
2761

Relevant Lines:
5563

💛  - Coveralls


Add BuildStream to Linguist: https://github.com/github/linguist

See original issue on GitLab
In GitLab by [Gitlab user @frazerclews] on Jul 6, 2020, 19:28
Background
//: # BuildStream doesn't show up in GitLab, GitHub, etc repositories which doesn't help it being well known. And would help those getting into a BuildStream project a better understanding of the project. Since BitBake is in the linguist list, I am sure BuildStream can be too
Task description

[ ] Add BuildStream following linguists steps https://github.com/github/linguist/blob/master/CONTRIBUTING.md#adding-a-language
[ ] Use YAML as the grammar for BuildStream

Acceptance Criteria
//: # Having BuildStream show up along side other languages in GitHub, GitLab, etc projects, and hopefully have BuildStream have grammatical highlighting if we use the YAML grammar already in linguist

In GitLab by [Gitlab user @frazerclews] on Jul 6, 2020, 19:29
changed title from Add BuildStream to {-Linguist-} to Add BuildStream to {+<Linguist>+}

In GitLab by [Gitlab user @frazerclews] on Jul 6, 2020, 19:29
changed title from Add BuildStream to {-Linguist-} to Add BuildStream to {+<Linguist>+}

In GitLab by [Gitlab user @frazerclews] on Jul 6, 2020, 19:30
changed title from Add BuildStream to {-<Linguist>-} to Add BuildStream to {+Linguist: https://github.com/github/linguist+}

In GitLab by [Gitlab user @frazerclews] on Jul 6, 2020, 19:30
changed title from Add BuildStream to {-<Linguist>-} to Add BuildStream to {+Linguist: https://github.com/github/linguist+}

In GitLab by [Gitlab user @sstriker] on Jul 7, 2020, 21:36
I'm a bit torn on this one.  I don't think that

BuildStream doesn't show up in GitLab, GitHub, etc repositories which doesn't help it being well known.

is a good enough reason - that is, we shouldn't think of Linguist as a marketing-tool.
I also think the reasoning is a bit backwards.  Quoting from https://github.com/github/linguist/blob/master/CONTRIBUTING.md#adding-a-language:

We try only to add languages once they have some usage on GitHub. In most cases we prefer that each new file extension be in use in hundreds of repositories before supporting them in Linguist.

I don't think we can honestly claim that yet.
While the comparison with BitBake, which has been around since 2004, may seem to make sense at a high level, I tend to think BuildStream is a different beast.  Especially looking at the BitBake syntax.

In GitLab by [Gitlab user @sstriker] on Jul 7, 2020, 21:36
I'm a bit torn on this one.  I don't think that

BuildStream doesn't show up in GitLab, GitHub, etc repositories which doesn't help it being well known.

is a good enough reason - that is, we shouldn't think of Linguist as a marketing-tool.
I also think the reasoning is a bit backwards.  Quoting from https://github.com/github/linguist/blob/master/CONTRIBUTING.md#adding-a-language:

We try only to add languages once they have some usage on GitHub. In most cases we prefer that each new file extension be in use in hundreds of repositories before supporting them in Linguist.

I don't think we can honestly claim that yet.
While the comparison with BitBake, which has been around since 2004, may seem to make sense at a high level, I tend to think BuildStream is a different beast.  Especially looking at the BitBake syntax.

In GitLab by [Gitlab user @cs-shadow] on Jul 8, 2020, 10:14

that is, we shouldn't think of Linguist as a marketing-tool

+1
Perhpas I skimmed through the actual description without much care, but my original reading of this issue was more that .bst files do not get syntax highlighting on code hosting sites like GitHub, GitLab etc. Personally, I do think this is important for developer producitivity but doesn't necessarily have to be solved in Linguist itself.
If that was indeed the motivation behind this, it may be worth mentioning at least GitHub and GitLab support language hints via .gitattributes:

GitHub: https://github.com/github/linguist#using-gitattributes
*.bst linguist-language=YAML

GitLab: https://docs.gitlab.com/ee/user/project/highlighting.html
*.bst gitlab-language=yaml

Also, for one off .bst snippets, one can also use vim/emacs style syntax highlight hints. Most code hosting sites support these already.

In GitLab by [Gitlab user @cs-shadow] on Jul 8, 2020, 10:14

that is, we shouldn't think of Linguist as a marketing-tool

+1
Perhpas I skimmed through the actual description without much care, but my original reading of this issue was more that .bst files do not get syntax highlighting on code hosting sites like GitHub, GitLab etc. Personally, I do think this is important for developer producitivity but doesn't necessarily have to be solved in Linguist itself.
If that was indeed the motivation behind this, it may be worth mentioning at least GitHub and GitLab support language hints via .gitattributes:

GitHub: https://github.com/github/linguist#using-gitattributes
*.bst linguist-language=YAML

GitLab: https://docs.gitlab.com/ee/user/project/highlighting.html
*.bst gitlab-language=yaml

Also, for one off .bst snippets, one can also use vim/emacs style syntax highlight hints. Most code hosting sites support these already.

In GitLab by [Gitlab user @frazerclews] on Jul 11, 2020, 13:33
It wasn't the idea of using it as a marketing tool, the intention is to get those getting into a project that uses BuildStream less confused, while maybe also providing benefits like syntax highlighting using the YAML grammar. When I first heard of BuildStream, I didn't think of a language, mainly because it didn't show up as one and made things quite confusing. I also understand the issue with the GitHub library not being large enough, but personally I feel it should expand to GitLab instead of just GitHub, especially as a lot of people are moving towards GitLab and other services like there own GitLab instance now, and it's not good to just stick to one service where Linguist is used a lot outside of GitHub. This is something I have brought up with the team and I am waiting for a response.

In GitLab by [Gitlab user @frazerclews] on Jul 11, 2020, 13:33
It wasn't the idea of using it as a marketing tool, the intention is to get those getting into a project that uses BuildStream less confused, while maybe also providing benefits like syntax highlighting using the YAML grammar. When I first heard of BuildStream, I didn't think of a language, mainly because it didn't show up as one and made things quite confusing. I also understand the issue with the GitHub library not being large enough, but personally I feel it should expand to GitLab instead of just GitHub, especially as a lot of people are moving towards GitLab and other services like there own GitLab instance now, and it's not good to just stick to one service where Linguist is used a lot outside of GitHub. This is something I have brought up with the team and I am waiting for a response.

In GitLab by [Gitlab user @frazerclews] on Jul 11, 2020, 13:40
Personally I find syntax highlighting very useful, and I feel just adds a level of polish which helps in the long run. .gitattributes could definitely work in the short term, but I feel it's just putting more work on a team whenever they use a BuildStream project and enforce consistency with all BuildStream projects that may not know about that or be bothered to do it due to time constraints, and would mess up things if developers fork it to different services

In GitLab by [Gitlab user @frazerclews] on Jul 11, 2020, 13:40
Personally I find syntax highlighting very useful, and I feel just adds a level of polish which helps in the long run. .gitattributes could definitely work in the short term, but I feel it's just putting more work on a team whenever they use a BuildStream project and enforce consistency with all BuildStream projects that may not know about that or be bothered to do it due to time constraints, and would mess up things if developers fork it to different services

In GitLab by [Gitlab user @cs-shadow] on Jul 17, 2020, 13:32

would mess up things if developers fork it to different services

I'm not sure how Linguist would solve this though. There are a plethora of code hosting services and linguist is far from being the ubiquitous tool for this job. We don't have to look too far to find examples of sites that don't use Linguist. Take GitLab for instance, it uses rogue to do syntax detection and highlighting.

In GitLab by [Gitlab user @cs-shadow] on Jul 17, 2020, 13:32

would mess up things if developers fork it to different services

I'm not sure how Linguist would solve this though. There are a plethora of code hosting services and linguist is far from being the ubiquitous tool for this job. We don't have to look too far to find examples of sites that don't use Linguist. Take GitLab for instance, it uses rogue to do syntax detection and highlighting.


[Regression] Regression in Supply in 2.38.0

New Issue Checklist

[ X ] Updated fastlane to the latest version
[ X ] I have read the Contribution Guidelines

Issue Description
Supply incorrectly pulls in 0.11+ of the Google Api Client gem - and 0.12.0 isn't compatible with the existing code.
Complete output when running fastlane, including the stack trace and command used

You can use: --capture_output as the last commandline argument to get that collected for you

/opt/circleci/.rvm/gems/ruby-2.2.4/gems/fastlane-2.38.0/supply/lib/supply/client.rb:146:in listing_for_language': [!] undefined method get_listing' for #Google::Apis::AndroidpublisherV2::AndroidPublisherService:0x007f8190053e80 (NoMethodError)
from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/fastlane-2.38.0/supply/lib/supply/uploader.rb:17:in block in perform_upload' 	from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/fastlane-2.38.0/supply/lib/supply/uploader.rb:13:in each'
from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/fastlane-2.38.0/supply/lib/supply/uploader.rb:13:in perform_upload' 	from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/fastlane-2.38.0/fastlane/lib/fastlane/actions/supply.rb:21:in run'
from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/fastlane-2.38.0/fastlane/lib/fastlane/runner.rb:252:in block (2 levels) in execute_action' 	from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/fastlane-2.38.0/fastlane/lib/fastlane/actions/actions_helper.rb:50:in execute_action'
from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/fastlane-2.38.0/fastlane/lib/fastlane/runner.rb:230:in block in execute_action' 	from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/fastlane-2.38.0/fastlane/lib/fastlane/runner.rb:226:in chdir'
from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/fastlane-2.38.0/fastlane/lib/fastlane/runner.rb:226:in execute_action' 	from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/fastlane-2.38.0/fastlane/lib/fastlane/runner.rb:148:in trigger_action_by_name'
from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/fastlane-2.38.0/fastlane/lib/fastlane/fast_file.rb:146:in method_missing' 	from Fastfile:70:in block (2 levels) in parsing_binding'
from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/fastlane-2.38.0/fastlane/lib/fastlane/lane.rb:33:in call' 	from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/fastlane-2.38.0/fastlane/lib/fastlane/lane.rb:33:in call'
from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/fastlane-2.38.0/fastlane/lib/fastlane/runner.rb:49:in block in execute' 	from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/fastlane-2.38.0/fastlane/lib/fastlane/runner.rb:45:in chdir'
from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/fastlane-2.38.0/fastlane/lib/fastlane/runner.rb:45:in execute' 	from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/fastlane-2.38.0/fastlane/lib/fastlane/lane_manager.rb:52:in cruise_lane'
from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/fastlane-2.38.0/fastlane/lib/fastlane/command_line_handler.rb:30:in handle' 	from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/fastlane-2.38.0/fastlane/lib/fastlane/commands_generator.rb:104:in block (2 levels) in run'
from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/commander-fastlane-4.4.4/lib/commander/command.rb:178:in call' 	from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/commander-fastlane-4.4.4/lib/commander/command.rb:178:in call'
from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/commander-fastlane-4.4.4/lib/commander/command.rb:153:in run' 	from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/commander-fastlane-4.4.4/lib/commander/runner.rb:476:in run_active_command'
from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/fastlane-2.38.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:39:in run!' 	from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/commander-fastlane-4.4.4/lib/commander/delegates.rb:15:in run!'
from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/fastlane-2.38.0/fastlane/lib/fastlane/commands_generator.rb:303:in run' 	from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/fastlane-2.38.0/fastlane/lib/fastlane/commands_generator.rb:42:in start'
from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/fastlane-2.38.0/fastlane/lib/fastlane/cli_tools_distributor.rb:66:in take_off' 	from /opt/circleci/.rvm/gems/ruby-2.2.4/gems/fastlane-2.38.0/bin/fastlane:20:in <top (required)>'
from /opt/circleci/.rvm/gems/ruby-2.2.4/bin/fastlane:23:in load' 	from /opt/circleci/.rvm/gems/ruby-2.2.4/bin/fastlane:23:in '

Thanks for letting me know, we're gonna do a hotfix release https://github.com/fastlane/fastlane/issues/9444, we'll have a new version live within a few minutes 👍
Thanks for preparing https://github.com/fastlane/fastlane/pull/9445, let's take a look at that after the hotfix release.

Sounds great - thanks for the quick hotfix!
On Mon, Jun 12, 2017 at 6:17 PM, Felix Krause<EMAIL_ADDRESS>wrote:

Thanks for letting me know, we're gonna do a hotfix release #9444
https://github.com/fastlane/fastlane/pull/9444, we'll have a new
version live within a few minutes 👍
Thanks for preparing #9445
https://github.com/fastlane/fastlane/pull/9445, let's take a look at
that after the hotfix release.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/fastlane/fastlane/issues/9441#issuecomment-307949880,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APUaZ-7Zs18QzLIxEQAvI5Yy2N2MACjzks5sDbj2gaJpZM4N3vOw
.


fix: Update with generated code from protobufjs version 7.0.0

This is the result of running update.sh script .... I am very confused as to purpose of this script, since it appears to overlap googleapis-gen.

To give you some context, the initial idea of update.sh was to split protos into smaller files, and load them separately as needed, which should improve cold start time. This is a unique thing, no other client libraries do this. I haven't looked at why the preview features get included though, the script might need some fixing. Feel free to ping me if you want extra 👀 to look at it.

In #1765 I updated protos with the latest updates from googleapis. I'm assuming this PR could be closed now.


Fix spelling errors

The lintian QA tool reported some spelling errors for the Debian package build:

Ouput -> Output
Exagerate -> Exaggerate

Regarding the Debian package, is there an ETA for the 0.24 release? 0.23 was released quite some time ago.

Thanks.  I've merged your patch and have created a v0.24 tag.  I don't know who creates the Debian package.

Francesco Paolo Lovergine initially maintained the Debian package, and I've now taken over maintenance of the GIS packages in Debian since Francesco is not very active any more.

Ah.  In that case, thank you for packaging this.  Let me know if you need any further action on my part.


Can't import  getComponentProps

Hey, can't import getComponentProps.
I'm following the documentation instructions.
import { getComponentProps } from 'figx';
Error:
Module '"figx"' has no exported member 'getComponentProps'
Thanks.

Oops. Seems like I forgot to export getComponentProps. Thanks for pointing out.
I just published a fix version. It should now work with version 0.0.18.  Please give it a try :-)

Thanks, it works now, although I think you should make it also support InstanceNode.


Ion source

An ion source term implemented as a boundary condition for the ion equations.

Question: this implemented source term seems to be able to add particles locally at the plasma edge, but not anywhere else. Would it make sense to include a source term S = S(t, r) that can be add particles inside of the plasma as well as at the edge? Would this ability even be relevant for DREAM?


change lang in forums

is there a way to change the lang through extension?

Not sure what you mean by "through extension". You can change the locale in your config/app.php, or if you want to set it dynamically at runtime based on your users' preferences, you can use app()->setLocale($locale) (doing this in your middleware or a controller constructor seems sane).
The forums respect the locale, so you don't need to do anything specific with them unless you want to display the langcode in your URLs.
More here: http://laravel.com/docs/5.1/localization#introduction

i meant like how would i go about extending your forum's en local so that i can change what's in it without having to create my own separate lang file. Kinda like how controllers and views are overwritten.

Right. You have to maintain your own copy of the lang file or edit the original. Conventionally, you'd copy it and the latest stable version of the forum does publish lang files along with views and migrations. The path should be resources/lang/vendor/forum/base.php
http://laravel.com/docs/5.1/localization#overriding-vendor-language-files

Also, I believe lang files are merged in a similar way to config, so you don't need to keep all the strings in your copy of the file, only the ones you actually want to change.


Can't install fastify-zod

Provide installed version
[Ultra] v0.7.3 (47.05ms)
Current platform
Windows
Describe the Bug
I tried running the following command
ultra install fastify-zod

And it did not install the fastify-zod package. Whereas npm successfully did it.
This is the error ultra gave to me (after 26 seconds)

This is what NPM shows after installation (after 5 seconds)

Expected Behavior
Expected that fastify-zod gets installed automatically
Template command (if applicable)
ultra install fastify-zod
To Reproduce
Run ultra install fastify-zod in a blank project

Just tried installing fastify-jwt and again got same error

Looks like it's a problem with Windows, it works on WSL2 (Ubuntu)

Just tried installing fastify-jwt and again got same error
But with an extra line

This one may be a problem with a dependency that starts with npm: those are not supported yet.

@nachoaldamav I just found out that fastify-jwt is deprecated and @fastify/jwt is recommended instead

Looks like it's a problem with Windows, it works on WSL2 (Ubuntu)

Does fastify-zod work on WSL2?

Looks like it's a problem with Windows, it works on WSL2 (Ubuntu)

Does fastify-zod work on WSL2?

My installation didn't fail, can you test it in a project that uses it?

I'm trying to fix it in this branch https://github.com/nachoaldamav/ultra/tree/fix/win-postinstall

Should be fixed in v0.7.4
npm i ultra-pkg -g

Cool!


API and models to suppport osquery distributed queries

This PR adds support for creating distributed queries in Doorman. The database model maintains a one-to-many relationship between Node's and DistributedQuery's. DistributedQuery's have a one-to-one relationship with DistributedQueryResult's. A DistributedQuery may be in one of the following statuses:

DistributedQuery.NEW = 0
DistributedQuery.PENDING = 1
DistributedQuery.COMPLETE = 2

When a DistributedQuery is created, it has a default status of DistributedQuery.NEW. DistributedQuery's in this state will be returned upon their respective node requesting the distributed read TLS endpoint, at which point their status will be updated to DistributedQuery.PENDING. The DistributedQuery will remain in DistributedQuery.PENDING status until the respective node submits the results for this DistributedQuery, identified by its guid. Upon successful processing of the results for the DistributedQuery, its status is again updated to DistributedQuery.COMPLETE. The results of the query are stored in a DistributedQueryResult object (specifically, within the data attribute).
The results for a DistributedQuery in the DistributedQuery.COMPLETE status may be easily retrieved via its result attribute, which returns a single DistributedQueryResult object.
Note: it is not possible to assign a single DistributedQuery instance to many nodes; a new DistributedQuery instance must be created for each node.

I like the design - LGTM 👍


NDI over VPN

He have a site-to-site VPN tunnel between two locations (uusing TP-Link ER605 VPN Routers). We're trying to play a NDI stream from one location to another (it's working on windows with NDI Studio Monitor).
Even if we add the IP on the "Extra NDI source IPs:" field, the stream is not being displayed in the player ("No sources found, searching...").
We're guessing this is beacuse the VPN tunnel is not properly routing multicast traffic (not showing on avahi-browse -a)
Is there any way to manually force the stream source IP, without it being discovered ?

On the System configuration page there's a setting for Extra NDI source IPs.

On the System configuration page there's a setting for Extra NDI source IPs.

As I mentioned, I already tried that, it's not showing up on the player as available source.

Still not showing up.
I can ping the NDI server, and even connect through telnet, but still not being discovered on dicaffeine.
administrator@JPD-Test:~$ telnet <IP_ADDRESS> 5960
Trying <IP_ADDRESS>...
Connected to <IP_ADDRESS>.
Escape character is '^]'.
public


Stop mocking out numpy and scipy in sphinx conf.

On my machine, this clears up the sphinx build errors and builds useful API docs again.  Haven't tested on readthedocs, so I suppose the best way to do that is to just merge.

There seems to be a numerical failure in py27 travis:
https://travis-ci.org/choderalab/pymbar/jobs/72229057#L546-L561
Any ideas?

No idea, but that is a separate issue.

—
Reply to this email directly or view it on GitHub
https://github.com/choderalab/pymbar/pull/204#issuecomment-124139482.

Must have been an odd fluke?


Added ability to send/receive big files by using real stream instead of bytestream.

For download, the destination task request can now use the read stream from the request, permitting to save a big file to disk.
Also, when deserializing with the two 'stream' overload, the real stream is accessible, permitting to deserialize big objects if needed.  But, all code compatibility is kept and the stream is not accessible outside the request overload or deserialization object.
For upload, using the http stream permit to send big files to server.  The call back is called twice, once without the stream object (to retrieve the expected size), the second time with the stream object, for the callback to write in it.  Also, the computed size from the first call is also specified to facilitate progress code.

@savardd Thank you so much. Let me take a look and get back to you!

i think it looks really good. Can you add test downloading hug files as well? After that, this looks good to merge.

I just added two new tests, one for big file download and another to test the head request with gzip compression enabled.

Awesome!! Thank you, I will merge this in!


Running BLE and classic at the same time

Following issue 48 (everything is working fine on BLE both client and server at the same time), I'm still interested to run a BLE LE_server and a Bluetooth Classic server at the same time on the same device. Could you please explain from where comes the limitation? Is this "patch-able"? Would the limitation comes from the implementation of the btferret library and/or could the bluetooth chip prevents from doing both protocols at the same time (and how would I test that)?

I think it would be possible, but it would require a major reorganization to merge the btilb.c functions le_server and classic_server. They both have a section that waits for a connection, and a do-loop that waits for packets from the connected client and deals with them. In classic_server the connection and input sections are separate which means that only one connection is possible. In le_server the connection section is in the do loop, so multiple connections are allowed. The merged procedure would have a do-loop that waits for classic and le connections, and also waits for connected classic and le packets, tests each input for classic or le and switches the handling accordingly.

Thank you for the clear explanation.
I think that's too bad because you are very close to support such scenario.
This is where having a poll architecture WITHOUT blocking as discussed in issue #23 is highly beneficial. And it's not so much to implement, even from your existing code. You have a main poll and you dispatch depending whatever needs to be done. And the advantage of non blocking is that you are still getting events (they are queued by the kernels) and you can deal with them.
I'm closing the issue as it's more an enhancement that a bug.


K8s:  adding full metadata and some code improvements

to test look at a k8s cluster with pods and networkplocies

@safchain - rather than exposing a function to covert label to image I reverted back to exposing a map, only that I setup the map 'automatically' via setupFixedImages() function call. This does prohibit adding additional images to the map later. (to enable extending the map via config file)


Add a link to godoc from README

It's conventional for Go packages to add a godoc badge on their READMEs.
You can use the package site badge creator, https://pkg.go.dev/badge/:
[![Go Reference](https://pkg.go.dev/badge/google.golang.org/genai.svg)](https://pkg.go.dev/google.golang.org/genai)

reference link added


Sets PolicyDocument return type to dict in generated documentation.

Addresses boto/boto3#229
Accepting the dict for put is beyond the scope of this commit.

Let's get the tests to pass first before reviewing it. I am not sure about the root cause for the test error, but the test failure is a python3 thing where bytes types cannot be equal to string types.

There were going to be some merging conflicts, so I rebased to fix them.

This will fix the issue that was linked but I do not think it will fix all of the possible cases. Based on this handler, all members with the policyDocumentType shape will have the customization applied. To get the most complete fix, you will have to traverse the shape/document searching for policyDocumentType and replacing it where needed. Fortunately, I implemented the functionality in boto3: https://github.com/boto/boto3/blob/develop/boto3/docs/utils.py#L93. I would suggest looking to see if you can use the class in boto3 in botocore.

It would also be good to add a functional test here.  The doc internals have a tendency change so it would be great to have a high level functional test to ensure the docs are updated.  I would even suggest just picking a single operation and ensuring the return type is correct.

Updated to use the more re-usable modification code from Boto3 and added a functional test.

Looks good. Just had a few comments about the tests.

:+1:

Closing while a more general solution is investigated


Replace parboiled2

Parboiled2 does not work on Dotty.  The effort to upgrade it is stalled.  I tried for a weekend, and it's a heavy lift.
Similar performance has been observed with Parsley.
Much worse performance, but a project with more familiarity among the maintainers, is Atto.  It's unclear how much performance would suffer in practice vs. in contrived benchmarks.
Both choices come with their own risk.  We need to decide on one and start porting parsers.
This is what's most likely to break API and force an 0.22 release, though we've tried to internalize every parboiled2 reference, so, maybe not?

I wonder should this effort imply replacing the obsolete RFC rules we have now with their successors?

What about fastparse?
I've had good experience with it, both as ease of use and performances. I haven't seen a benchmark comparing it to other parsers.
Is it something that can be considered? If there is a benchmark somewhere I can integrate fastparse to see how it performs compared to the others.

Fastparse is very macro-driven and is not a path towards dotty, unless there is some effort to port it.

I wonder should this effort imply replacing the obsolete RFC rules we have now with their successors?

Absolutely, though we should be thoughtful about whether resulting semantic changes are considered bugfixes, or breaking changes that deserve a version bump.  I'm leaning toward calling them bugfixes, but let's be mindful as we go.

What about fastparse?

I looked at porting that, and it seemed about the same order of difficulty or worse as parboiled2, for the reasons @hamnis describes.  I did some JSON benchmarking with it -- not HTTP, but something that was easy to compare across libraries -- and it was on the same order as parboiled2 and parsley.  For similar performance and similar Dotty upgrade work, I'd be inclined to stick to parboiled2 and not also rewrite our parsers.  But if someone does make it work on Dotty, and soon, then sure!

I'm engaging with Parsley upstream:

cross-build: https://github.com/J-mie6/Parsley/pull/6
publish: https://github.com/J-mie6/Parsley/pull/7

A (temporary?) fork for our exploration: https://github.com/http4s/Parsley

I just released parsley-1.5.0-M2 under org.http4s.  I won't be awake to see it hit Maven Central tonight.

I created a parsley branch and added a dependency.
It branched off series/0.21.  There's nothing dotty-specific about it.  My guess is that it ultimately merges to the dotty branch, which will ultimately become series/0.22, but we've got options.  We can start trying out this parser library without immediately dealing with the other dotty failures.

By the way, if you have any problems with your transition just let me know and I'll try to help out a bit!

There is also a proposed cats-parse, which is worth a look as well.  As we proceed, please remember to be kind:

Both authors have been kind to us.
One author is watching.
Regardless, be kind.

https://github.com/typelevel/cats-parse - Now created

Just curious – is it a private repo? Cannot open this link, GitHub shows a Jedi instead.

cats-parse is being extracted from bosatsu and getting a build to ready it for the public ASAP. Meanwhile, you can see the original, or read Oscar's blog.
In Parsley news, I cut another milestone in our repackage with Dotty support: "org.http4s" %% "parsley" % "1.5.0-M3".

Re-organized with some steps and examples on #3984.


Force to use the Spark's system default precision and scale when inferred data type contains DecimalType.

The return type inference sometimes fails when the inferred type contains DecimalType to infer the precision or the scale smaller.
>>> from decimal import Decimal
>>> kdf = ks.DataFrame({'a': [Decimal('1.1'), Decimal('2.2'), Decimal('10.01')]})
>>> kdf
       a
0   1.10
1   2.20
2  10.01
>>> kdf.spark.print_schema()
root
 |-- a: decimal(4,2) (nullable = false)

>>> with ks.option_context("compute.shortcut_limit", 1):
...   kdf.transform(lambda x: x).spark.print_schema()
...
root
 |-- a: decimal(3,2) (nullable = true)

>>> with ks.option_context("compute.shortcut_limit", 1):
...   kdf.transform(lambda x: x)
...
Traceback (most recent call last):
...
pyarrow.lib.ArrowInvalid: Decimal type with precision 4 does not fit into precision inferred from first array element: 3
...

We should use the Spark's system default precision and scale instead to avoid as many such cases as possible:
>>> with ks.option_context("compute.shortcut_limit", 1):
...   kdf.transform(lambda x: x).spark.print_schema()
...
root
 |-- a: decimal(38,18) (nullable = true)

>>> with ks.option_context("compute.shortcut_limit", 1):
...   kdf.transform(lambda x: x)
...
                       a
0   1.100000000000000000
1   2.200000000000000000
2  10.010000000000000000

Codecov Report

Merging #1904 (bcb403d) into master (44d45f2) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #1904   +/-   ##
=======================================
  Coverage   94.16%   94.17%
=======================================
  Files          41       41
  Lines        9975     9989   +14
=======================================
+ Hits         9393     9407   +14
  Misses        582      582

Impacted Files
Coverage Δ

databricks/koalas/accessors.py
93.00% <100.00%> (ø)

databricks/koalas/frame.py
96.73% <100.00%> (ø)

databricks/koalas/groupby.py
91.48% <100.00%> (ø)

databricks/koalas/namespace.py
83.33% <100.00%> (+0.03%)
:arrow_up:

databricks/koalas/spark/utils.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

Thanks! merging.


Remove bin and obj

Update .gitignore to exclude bin and obj
Remove bin and obj

My git sklls are weak. I created a PR to remove bin and obj directories, then did a new commit to the same branch rather than a different one, so this PR has both.
In the future I'll branch properly but hopefully this is OK for this one.


Unblock logic from freezing

Is your feature request related to a problem? Please describe.
When you drag your window or resize it game logic stop processing. Its not good. I can live with blocking rendering. But systems must work when you drag window.
It is a bug.
It made networking much harder bc you will loose messages each time when drag. it will cause disconnections / desyncs.
Also it's good practice when your game logic running permanently
Describe the solution you'd like
Run game logic independently.
Additional context
After researching i found how to fix that issue.
Example for SDL:
https://pastebin.com/FGqiXhj2
Here are some questions that can aid in the description of the feature request:

What are the usecases?

networking

What kind of options/settings are expected/wanted?

i can update source code for both sdl and winforms to use that

What would the (pseudo) code look like?

pastebin. actual code for SDL. https://pastebin.com/FGqiXhj2

Is the feature affecting behaviour in the editor?

not editor related

Is there a component or datastructure?

engine lifecycle

what kind of documentation is needed or needs to be updated?

nothing. just mention it in release notes

Should there be an example project?

no

This is also solution for #709

pastebin. actual code for SDL. https://pastebin.com/FGqiXhj2

Could you open a pull request so we can see a proper diff of the changes in the file?

@tebjan Yes. i will do it tommorow (today but not now). Im tired for a long day and thats all what i can provide for now. Ull get PR tommorow

@tebjan https://github.com/ParadiseFallen/stride/blob/e7720bf3752995c18aa3f4ef5ae57256ca50317b/sources/engine/Stride.Games/SDL/SDLMessageLoop.cs#L196

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request

https://github.com/stride3d/stride/pull/1486 @tebjan

conversation will goes into https://github.com/stride3d/stride/issues/1488


FullHDに対応

個人的にはスキンごとに解像度を指定できるとありがたいです。（4:3比スキンの作成等）

I agree with shiren here, having the resolution as a parameter in SkinConfig.ini files would not only keep the older skins compatible, but would also allow to scale up the game's skins (to resolutions like 4K) in the future, I labeled the ticket as 0.6.2 considering making all the textures positions changeable would be mandatory beforehand

Mostly done


waiting for file chooser failed on Github Actions

The problem still persists. I'm using version 1.3.70. Here's my code
import { upload } from "youtube-videos-uploader";
import dotenv from "dotenv";
dotenv.config();

const res = await upload(
  {
    email: process.env.EMAIL,
    pass: process.env.PASSWORD,
    recoveryemail: process.env.RECOVERY_EMAIL,
  },
  [
    {
      path: "./video.mp4",
      title: `My test video`,
      description: "Test description",
      language: "english",
      skipProcessingWait: true,
      onProgress: (progress) => console.log("Progress: ", progress),
      onSuccess: (url) => console.log("Uploaded: ", url),
      channelName: "Code Weather Videos",
    },
  ],
  {
    headless: true,
    args: ["--no-sandbox", "--disable-setuid-sandbox", "--disable-extensions"],
  }
);

console.log(res);

The github actions workflow
name: Upload video
on:
  workflow_dispatch:
jobs:
  render:
    name: Upload video
    runs-on: ubuntu-latest
    env:
      EMAIL: ${{ secrets.EMAIL }}
      PASSWORD: ${{ secrets.PASSWORD }}
      RECOVERY_EMAIL: ${{ secrets.RECOVERY_EMAIL }}
    steps:
      - uses: actions/checkout@main
      - uses: actions/setup-node@main
      - run: sudo apt update
      - run: sudo apt install gconf-service libasound2 libatk1.0-0 libc6 libcairo2 libcups2 libdbus-1-3 libexpat1 libfontconfig1 libgcc1 libgconf-2-4 libgdk-pixbuf2.0-0 libglib2.0-0 libgtk-3-0 libnspr4 libpango-1.0-0 libpangocairo-1.0-0 libstdc++6 libx11-6 libx11-xcb1 libxcb1 libxcomposite1 libxcursor1 libxdamage1 libxext6 libxfixes3 libxi6 libxrandr2 libxrender1 libxss1 libxtst6 ca-certificates fonts-liberation libnss3 lsb-release xdg-utils wget libgbm-dev
      - run: npm i
      - run: node index.js

Here's the error

I'm having a similar issue that might be related : the scripts simply never stops, it's stuck on this line of code :
https://github.com/fawazahmed0/youtube-uploader/blob/db8c5b14f655b105d7ab89b67d8b186fd1822b9e/src/upload.ts#L177
Added a line of code before to take a screenshot of the page, and changed the timeout for 5 minutes and screenshoted after 5 minutes, and in both cases, it shows a disabled upload button :

I did a few tests, and I get this issues consistantly in headless mode, but it works fine in headful mode.

I tested a few things, but I can't pin point what exactly goes wrong.
I can't manage to reproduce consistantly on another machine than on my server on which I have the issue.

@pierreminiggio did you figure this out by any chance? Having the same issue running in a VM

It's been more than 6 months, the code is a bit different now.
On my own instance it's working just fine.


Review upgraded contracts (Audits)

Issue Type
One of the handover tasks.
Current Behavior
Audit contracts on testnet deployed:
https://github.com/bobanetwork/boba/pull/841/files#diff-8d11ed14eb8cf05e01f92a358f954362bfb66f425d7695cd79134f855da5d0f5
Expected Behavior
Evaluate for proxy collisions, test, etc.

[~] (Boba) ETH testnet: waiting for Goerli upgrade, as reset
[X] (Boba) BNB testnet looks fine
[ ] (Boba) Opera outstanding
[ ] (Boba) Fuji outstanding
[ ] (Boba) Base outstanding (although it will be stopped?)

Opera:

L1 looks fine
L2:

need to check if it's just a display error of our block explorer:
L2LiquidityPool contracts in PR don't seem to exist:
0xE7Da2a8EBcbBa0Dc6082B8D0faBAcA0176920760 and 0xB9CeA621C2C9BE002747F2DdB7eB6a7dd0F8F20E
L1NFTBridge looks fine, while L2NFTBridge also doesn't seem to be deployed on
0x30C18d90a6f9B161b8c0BB720b31BcF215FEc12b and `0xEecAD665ca933eeA4a9a2db600E538c1391930d1
--
TeleporterProxy:

New implementation contract deployed, but proxy still points to old one on 0x502310dade5bab1065c788f6b98b78f5fc49fc09

Fuji:

L1: Looks fine, some minor remarks:

L1NFTBridge implementation not verified

L2:

Teleportation proxy points to 0x502310dade5bab1065c788f6b98b78f5fc49fc09, which is neither the old (constructor arg) nor the new implementation contract.

New teleportation contract address (that is documented) doesn't seem to be a contract: 0x2001F1B2b72000C34a630a58861E1b5CDe1f63eb. While the "invalid" address in 1) is - but 7 months old (thus also being a previous version).

Moonbeam:

L1: LiquidityPool and NFTBridge contracts either deployed on different addresses or blockexplorer display error (need to check)

L2: - same as for L1 -

TeleportationProxy points to: 0x502310dade5bab1065c788f6b98b78f5fc49fc09 which is 7 months old. On documented implementation address 0x92F4E3796324b916A69c98c96bBd939af19C4AD2 nothing is deployed.

@souradeep-das @InoMurko @Boyuan-Chen

Fuji:

L1: Looks fine, some minor remarks:

L1NFTBridge implementation not verified

L2:

Teleportation proxy points to 0x502310dade5bab1065c788f6b98b78f5fc49fc09, which is neither the old (constructor arg) nor the new implementation contract.
New teleportation contract address (that is documented) doesn't seem to be a contract: 0x2001F1B2b72000C34a630a58861E1b5CDe1f63eb. While the "invalid" address in 1) is - but 7 months old (thus also being a previous version).

The L1NFTBridge contract is verified.
You might look at the wrong block explorer. The teleportation was updated 22 days ago.
Proxy: https://blockexplorer.testnet.avax.boba.network/address/0xd68809330075C792C171C450B983F4D18128e9BF/transactions#address-tabs
Implementation:
https://blockexplorer.testnet.avax.boba.network/address/0x2001F1B2b72000C34a630a58861E1b5CDe1f63eb

We don't upgrade contracts for Moonbeam L2 and Fantom L2, because we will shut them down.

Just confirmed! Thanks @Boyuan-Chen

Goerli: https://github.com/bobanetwork/boba/pull/941/

Awesome looks good to me! thanks Boyuan!

closing as completed

opening this since, some of these things remain to be done:
i) New (implementation) contracts need to be registered on the AddressManager
ii) DiscretionaryExitFee needs to be redeployed (and UI changes probably, gateway needs to point to this contract instead)
iii) L2NFTBridge (Fuji) contracts needs to be verified

@souradeep-das https://github.com/bobanetwork/boba/pull/976

@sk-enya Please confirm that the gateway loads the DiscretionaryExitFee address from the local json file in the register folder.

Thanks @Boyuan-Chen!

@Boyuan-Chen yes DiscretionaryExitFee address is loaded from local json file from register folder.

Closing as last PR has been merged, please feel free to reopen if there seems something missing.