Vagrant setup fails running (cd openwhisk/tools/ubuntu-setup && source all.sh)

Running  ENV=shared vagrant up
on Ubuntu yields the following output.
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/trusty64-2'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: whisk-1605171549
==> default: Clearing any previously set forwarded ports...
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 22 (guest) => 2200 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: <IP_ADDRESS>:2200
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Remote connection disconnect. Retrying...
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
    default: /home/vagrant/openwhisk => /home/dani/Code/IBM/masterwhisk
==> default: Running provisioner: fix-no-tty (shell)...
    default: Running: inline script
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: executing (cd openwhisk/tools/ubuntu-setup && source all.sh) to complete setup.
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: *** installing basics
==> default: all.sh: line 6: /tmp/misc.sh: No such file or directory
==> default: 2522 finished with status 127
==> default:
==> default: *** installing python dependences
==> default: all.sh: line 6: /tmp/pip.sh: No such file or directory
==> default: 2523 finished with status 127
==> default: *** installing java
==> default: all.sh: line 6: /tmp/java8.sh: No such file or directory
==> default: 2524 finished with status 127
==> default:
==> default: *** installing ant
==> default: all.sh: line 6: /tmp/ant.sh: No such file or directory
==> default: 2525 finished with status 127
==> default:
==> default: *** install scala
==> default: all.sh: line 6: /tmp/scala.sh: No such file or directory
==> default: 2526 finished with status 127
==> default: *** installing docker
==> default: all.sh: line 6: /tmp/docker.sh: No such file or directory
==> default: 2527 finished with status 127
==> default: *** installing gradle
==> default: all.sh: line 6: /tmp/gradle.sh: No such file or directory
==> default: 2528 finished with status 127
==> default: *** installing ansible
==> default: all.sh: line 6: /tmp/ansible.sh: No such file or directory
==> default: 2529 finished with status 127
==> default: install all with total errors number 8
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

When ssh'ing into the box and sourcing all.sh, everything works as expected. I guess it's some issue of how the line SCRIPTDIR="$(cd $(dirname "$0")/ && pwd)" determines SCRIPTDIR.
@lzbj, Could you take a look?

@syntiux  I hit this in my PR #360
Fix is to modify all.sh
#!/bin/bash
SOURCE="${BASH_SOURCE[0]}"
SCRIPTDIR="$( dirname "$SOURCE" )"

@syntiux, yes, I'll sumbit a fix.
@csantanapr , thank you.

@syntiux ,I didn't test the scenario with Vagrant up, sorry for this trouble.

This is already fixed


Inline post body with parameters results in warning

When creating a post with in inline body a warning around types shows up:
No "type" specified at "/paths/~1route/post/parameters/0/schema". Automatically detected: "object"

to reproduce:
 /route:
    post:
      summary: Get the road information on the given route.
      description: |
        Uses a mapmatching algorithm to determine the selected roads for the given route.
        Returns the requested info for those roads at the current time.
      parameters:
        - name: location
          in: body
          type: object
          required: true
          schema:
            properties:
              polyline:
                type: string
                format: polyline
                description: |
                  [Google encoded polyline](https://developers.google.com/maps/documentation/utilities/polylinealgorithm)
                example:
                  iym|Hgtw]D?qA[sCw@}AWu@tK{Cp]QrEGhDDfCEBGR?ToExBsJhFa@d@GLKFi@vBKV}AmB]u@m@aD{AcK?ME?s@WQAsDtBbA`H}DrBZxBPGRbAt@e@CU
            required:
              - polyline

The simple workaround is to make the inline object definition into a $ref.

I ran into a similar problem, where I specified the type in in a $ref.
The configuration below results in a warning No "type" specified at "/paths/~1position/get/parameters/0". Automatically detected: "object".
      parameters:
        - name: lat
          in: query
          schema:
            $ref: '#/definitions/Latitude'
          description: Latitude of the position.
          required: true

definitions:
  Latitude:
    type: number
    format: double

When type is defined directly in parameters, this warning does not occur. I can imagine that when someone creates a $ref with a type that it should be picked up by the schema.

@asikkema the warning message provides the exact issue: you don't have type specified at /paths/~1route/post/parameters/0/schema:
schema:
     type: object # <- add `type: object` here
     properties:
          polyline:
               type: string

According to Swagger spec which uses JSON Schema Draft 4 underneath, if you do not specify type:object in the schema, it will successfully validate for example any string, number, boolean.
You can check it yourself on https://jsonschemalint.com
If you write simple schema like following:
{
  "properties": {
    "a": {
      "type": "string"
    }
  }
}

That's why ReDoc shows the warning.
You can disable warnings in UI by using option suppress-warnings.
@agboom your spec is invalid according to the swagger. If in is query you must specify type. Check details here


How to start the Printer?

Hi, How to start the Printer after I've loaded the Schematic? What are hot keys and how to open settings?

Hey, the shortcut for opening the config menu is m + c or , + c depending on your keyboard. Here you can find both the litematica settings and the printer settings. All printer settings start with easyPlace. A list with all settings can be found in the readme.md file.
In the Hotkeys tab you can change the hotkey for enabling the printer.
Good luck!

Hey, the shortcut for opening the config menu is m + c or , + c depending on your keyboard. Here you can find both the litematica settings and the printer settings. All printer settings start with easyPlace. A list with all settings can be found in the readme.md file. In the Hotkeys tab you can change the hotkey for enabling the printer. Good luck!

So after a while testing, I cannot use the mod in the server. The admin said they did not disable anything. Do you have any solution?
When I tried to place a block down, it said " Action prevented by Easy Place mode". I got the same message in Single player, but I can still print.

Could you send me the server ip? Then I could run some tests.

Its message is from ActionResult.FAIL, so instead of returning actionresult, doing continue; solves most of the problem.
Printer stopping working might mean you're trying to send packet but channel is clogged for some reason : possible reason is,

You've set max interaction too big / delay too small.
Server does not allow packets in weird way and packet is just being blocked.
You're trying to interact over reach distance?

Could you send me the server ip? Then I could run some tests.

It is a server with mod pack. I tried on 1.12 and it works. But on 1.16.5, its not.
Direwolf20 1.16 Server IP: dw16.craftersland.net

Its message is from ActionResult.FAIL, so instead of returning actionresult, doing continue; solves most of the problem. Printer stopping working might mean you're trying to send packet but channel is clogged for some reason : possible reason is,

You've set max interaction too big / delay too small.
Server does not allow packets in weird way and packet is just being blocked.
You're trying to interact over reach distance?

I think >2 have biggest chance. I'm using default values.

I'm currently struggling to install the Direwolf20 modpack with litematica to join the server.
Could you try the following printer settings:

set easyPlaceModeRange (both x,y and z) to 6
set easyPlaceModeMaxBlocks to 1
set easyPlaceModeDelay to 0.1
set easyPlaceModePaper to true
Those settings bypass most anti-cheats.


[tool_crash] NoSuchMethodError: The method 'add' was called on null.Receiver: nullTried calling: add("--enable-experiment=non-nullable")

Command
flutter run --enable-experiment non-nullable

Steps to Reproduce

...
...
...

Logs
NoSuchMethodError: NoSuchMethodError: The method 'add' was called on null.
Receiver: null
Tried calling: add("--enable-experiment=non-nullable")
#0      Object.noSuchMethod (dart:core-patch/object_patch.dart:53:5)
#1      FlutterCommand.getBuildInfo (package:flutter_tools/src/runner/flutter_command.dart:528:30)
#2      RunCommand.usageValues (package:flutter_tools/src/commands/run.dart:291:29)
<asynchronous suspension>
#3      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:715:21)
<asynchronous suspension>
#4      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:619:33)
<asynchronous suspension>
#5      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart)
#6      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:29)
#7      _rootRun (dart:async/zone.dart:1184:13)
#8      _CustomZone.run (dart:async/zone.dart:1077:19)
#9      _runZoned (dart:async/zone.dart:1619:10)
#10     runZoned (dart:async/zone.dart:1539:10)
#11     AppContext.run (package:flutter_tools/src/base/context.dart:149:18)
#12     FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:609:20)
#13     CommandRunner.runCommand (package:args/command_runner.dart:197:27)
#14     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:339:21)
<asynchronous suspension>
#15     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart)

[✓] Flutter (Channel stable, v1.17.0, on Microsoft Windows [Version 10.0.18363.778], locale en-US)
    • Flutter version 1.17.0 at C:\dev\app\flutter
    • Framework revision e6b34c2b5c (10 days ago), 2020-05-02 11:39:18 -0700
    • Engine revision 540786dd51
    • Dart version 2.8.1

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at C:\Users\incker\AppData\Local\Android\sdk
    • Platform android-29, build-tools 29.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
    • All Android licenses accepted.

[✓] Android Studio (version 3.6)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 45.1.1
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)

[!] IntelliJ IDEA Ultimate Edition (version 2019.3)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA 2019.3.3
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • For information about installing plugins, see
      https://flutter.dev/intellij-setup/#installing-the-plugins

[!] VS Code (version 1.45.0)
    • VS Code at C:\Users\incker\AppData\Local\Programs\Microsoft VS Code
    ✗ Flutter extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (1 available)
    • AOSP on IA Emulator • emulator-5554 • android-x86 • Android 9 (API 28) (emulator)

! Doctor found issues in 2 categories.

Flutter Application Metadata
Type: app
Version: 1.0.0+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: 27321ebbad34b0a3fafe99fac037102196d655ff
Plugins
firebase_auth-0.16.0
firebase_auth_web-0.1.2
firebase_core-0.4.4+3
firebase_core_web-0.1.1+2
flutter_plugin_android_lifecycle-1.0.7
google_maps_flutter-0.5.27+2
image_picker-0.6.6+1
package_info-0.4.0+18
path_provider-1.6.8
path_provider_macos-0.0.4+2
permission-565fc45490c2325fb1cc0155319bfe68b07f3de1
url_launcher-5.4.7
url_launcher_macos-0.0.1+5
url_launcher_web-0.1.1+4

This option is not supported on stable and should have been hidden

nevermind, this was already broken, but the option itself is hidden.

This is fixed in the latest beta


Travis testing fails randomly

Travis testing on PR #110 seems to fail randomly on osx
build job 199

build job 201

build job 202

The error log looks like this in both build job 199.4 and build job 202.6
HDF5-DIAG: Error detected in HDF5 (1.10.4) thread 0:
  #000: H5Dio.c line 199 in H5Dread(): can't read data
    major: Dataset
    minor: Read failed
  #001: H5Dio.c line 467 in H5D__read(): unable to set up type info
    major: Dataset
    minor: Unable to initialize object
  #002: H5Dio.c line 968 in H5D__typeinfo_init(): not a datatype
    major: Invalid arguments to routine
    minor: Inappropriate type
ERROR: LoadError: LoadError: Error reading dataset /ComplexF32
Stacktrace:
 [1] error(::String, ::String) at ./error.jl:42
 [2] h5d_read(::Int64, ::Int64, ::Int64, ::Int64, ::Int64, ::Array{Complex{Float32},1}) at /Users/travis/.julia/packages/HDF5/H0XJB/src/HDF5.jl:2250
 [3] read_complex(::HDF5.HDF5Datatype, ::HDF5.HDF5Dataset, ::Type{Array{Float32,N} where N}) at /Users/travis/build/JuliaIO/MAT.jl/src/MAT_HDF5.jl:130
 [4] m_read(::HDF5.HDF5Dataset) at /Users/travis/build/JuliaIO/MAT.jl/src/MAT_HDF5.jl:181
 [5] read(::MAT.MAT_HDF5.MatlabHDF5File, ::String) at /Users/travis/build/JuliaIO/MAT.jl/src/MAT_HDF5.jl:260
 [6] read(::MAT.MAT_HDF5.MatlabHDF5File) at /Users/travis/.julia/packages/HDF5/H0XJB/src/datafile.jl:45
 [7] test_write(::Dict{String,Array{T,2} where T}) at /Users/travis/build/JuliaIO/MAT.jl/test/write.jl:11
 [8] top-level scope at none:0
 [9] include at ./boot.jl:317 [inlined]
 [10] include_relative(::Module, ::String) at ./loading.jl:1044
 [11] include(::Module, ::String) at ./sysimg.jl:29
 [12] include(::String) at ./client.jl:392
 [13] top-level scope at none:0
 [14] include at ./boot.jl:317 [inlined]
 [15] include_relative(::Module, ::String) at ./loading.jl:1044
 [16] include(::Module, ::String) at ./sysimg.jl:29
 [17] include(::String) at ./client.jl:392
 [18] top-level scope at none:0
in expression starting at /Users/travis/build/JuliaIO/MAT.jl/test/write.jl:35
in expression starting at /Users/travis/build/JuliaIO/MAT.jl/test/runtests.jl:4
ERROR: Package MAT errored during testing
Stacktrace:
 [1] pkgerror(::String, ::Vararg{String,N} where N) at /Users/osx/buildbot/slave/package_osx64/build/usr/share/julia/stdlib/v1.0/Pkg/src/Types.jl:120
 [2] #test#65(::Bool, ::Function, ::Pkg.Types.Context, ::Array{Pkg.Types.PackageSpec,1}) at /Users/osx/buildbot/slave/package_osx64/build/usr/share/julia/stdlib/v1.0/Pkg/src/Operations.jl:1357
 [3] #test at /Users/osx/buildbot/slave/package_osx64/build/usr/share/julia/stdlib/v1.0/Pkg/src/API.jl:0 [inlined]
 [4] #test#42(::Bool, ::Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{(),Tuple{}}}, ::Function, ::Pkg.Types.Context, ::Array{Pkg.Types.PackageSpec,1}) at /Users/osx/buildbot/slave/package_osx64/build/usr/share/julia/stdlib/v1.0/Pkg/src/API.jl:273
 [5] #test at ./none:0 [inlined]
 [6] #test#41 at /Users/osx/buildbot/slave/package_osx64/build/usr/share/julia/stdlib/v1.0/Pkg/src/API.jl:255 [inlined]
 [7] #test at ./none:0 [inlined]
 [8] #test#40 at /Users/osx/buildbot/slave/package_osx64/build/usr/share/julia/stdlib/v1.0/Pkg/src/API.jl:254 [inlined]
 [9] #test at ./none:0 [inlined]
 [10] #test#39 at /Users/osx/buildbot/slave/package_osx64/build/usr/share/julia/stdlib/v1.0/Pkg/src/API.jl:253 [inlined]
 [11] (::getfield(Pkg.API, Symbol("#kw##test")))(::NamedTuple{(:coverage,),Tuple{Bool}}, ::typeof(Pkg.API.test), ::String) at ./none:0
 [12] top-level scope at none:0

build job 200

Here randomly both linux and osx jobs are failing.

setting Travis limit concurrent jobs to 1 did not help
https://github.com/JuliaIO/MAT.jl/blob/v0.4.0/test/write.jl#L3 does not call tempname(), improving it makes

https://travis-ci.org/jaakkor2/MAT.jl/builds/494823153 pass
https://travis-ci.org/JuliaIO/MAT.jl/builds/494823185 error: 203.3 Linux Julia nightly errored in building CMake

Retriggered Travis job 204 passed, so I guess tempname() fix was effective.


tests: allow brew tests to accept multiple --only args

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[x] Have you successfully run brew tests with your changes locally?

This is one of my attempts to change brew tests so that it allows multiple --only args (i.e., multiple test files and/or test methods). It doesn't work, though! 😞
I looked for documentation on the arguments that rake test accepts; if I understand correctly, then rake test does accept options that are used in Test::Unit (as mentioned here).
That led me to believe that rake test would indeed accept multiple test files or test methods as arguments (as detailed here).
Unfortunately, I haven't been able to test my changes with rake test (or bundle exec rake test) itself, since I receive this esoteric error when trying to do so:
/usr/local/Library/Homebrew/os/mac.rb:27:in `full_version': undefined method `chomp' for nil:NilClass (NoMethodError)
	from /usr/local/Library/Homebrew/os.rb:19:in `<module:OS>'
	from /usr/local/Library/Homebrew/os.rb:1:in `<top (required)>'
	from /usr/local/Library/Homebrew/extend/os/emoji.rb:1:in `require'
	from /usr/local/Library/Homebrew/extend/os/emoji.rb:1:in `<top (required)>'
	from /usr/local/Library/Homebrew/emoji.rb:24:in `require'
	from /usr/local/Library/Homebrew/emoji.rb:24:in `<top (required)>'
	from /usr/local/Library/Homebrew/utils.rb:2:in `require'
	from /usr/local/Library/Homebrew/utils.rb:2:in `<top (required)>'
	from /usr/local/Library/Homebrew/extend/pathname.rb:4:in `require'
	from /usr/local/Library/Homebrew/extend/pathname.rb:4:in `<top (required)>'
	from /usr/local/Library/Homebrew/global.rb:3:in `require'
	from /usr/local/Library/Homebrew/global.rb:3:in `<top (required)>'
	from /usr/local/Library/Homebrew/test/testing_env.rb:5:in `require'
	from /usr/local/Library/Homebrew/test/testing_env.rb:5:in `<top (required)>'
	from /usr/local/Library/Homebrew/test/test_cmd_audit.rb:1:in `require'
	from /usr/local/Library/Homebrew/test/test_cmd_audit.rb:1:in `<top (required)>'
	from /usr/local/Library/Homebrew/test/vendor/bundle/ruby/2.2.0/gems/rake-10.5.0/lib/rake/rake_test_loader.rb:15:in `require'
	from /usr/local/Library/Homebrew/test/vendor/bundle/ruby/2.2.0/gems/rake-10.5.0/lib/rake/rake_test_loader.rb:15:in `block in <main>'
	from /usr/local/Library/Homebrew/test/vendor/bundle/ruby/2.2.0/gems/rake-10.5.0/lib/rake/rake_test_loader.rb:4:in `select'
	from /usr/local/Library/Homebrew/test/vendor/bundle/ruby/2.2.0/gems/rake-10.5.0/lib/rake/rake_test_loader.rb:4:in `<main>'

Thanks!

I looked for documentation on the arguments that rake test accepts; if I understand correctly, then rake test does accept options that are used in Test::Unit (as mentioned here).
That led me to believe that rake test would indeed accept multiple test files or test methods as arguments (as detailed here).

My reading of http://rake.rubyforge.org/classes/Rake/TestTask.html is that you may only be able to specify a single test, unfortunately. That said, we could move away from using TestTask if it's limiting us in this way.

My reading of http://rake.rubyforge.org/classes/Rake/TestTask.html is that you may only be able to specify a single test, unfortunately. That said, we could move away from using TestTask if it's limiting us in this way.

Do any alternatives come to mind? I'm guessing that we would move away not just from using TestTask, but from using Rake itself, too?

Can you elaborate a bit on the motivation for this PR? What is the benefit over running brew tests (with the desired options, e.g. different --only=) multiple times in a row?

This is one of my attempts to change brew tests so that it allows multiple --only args (i.e., multiple test files and/or test methods). It doesn't work, though! 😞

I think from a user interface point of view it might be better (and also involve less changes) to teach --only= to accept multiple test files by supplying them in a single argument, delimited by a comma, e.g. --only=file1,file2 instead of --only=file1 --only=file2.

Unfortunately, I haven't been able to test my changes with rake test (or bundle exec rake test) itself, since I receive this esoteric error when trying to do so:

We should probably provide a better error message in this case or flat out refuse to run the test suite if invoked from a vanilla rake test, but the gist of why you see this esoteric error is that the Homebrew initialization code assumes quite a few environment variables to be set up in advance (in bin/brew and Library/Homebrew/brew.sh), thus loading any of the Homebrew Ruby code without going through this shell code first hasn't been really supported for quite a while.

Do any alternatives come to mind? I'm guessing that we would move away not just from using TestTask, but from using Rake itself, too?

Thinking about this: the only alternative I can think of is to run rake multiple times but then I also thought:

What is the benefit over running brew tests (with the desired options, e.g. different --only=) multiple times in a row?

which I now think I agree with, unfortunately.
Thanks for the PR anyway @eirinikos and hope it was a useful learning experience but passing on this for now 😭


 mappings no longer work

Hi,
I suspect this is related to change in syntax. I had  mappings in my vim files , for example:
vim.cmd[[nmap <space>ss<Plug>(iron-send-line)j]]

These no longer do anything.
Thanks

Hi @drusmanbashir
I'll test <Plug>() mappings here again, but I suspect this might not be related to iron. Can you try replacing your vim.cmd blocks for vim.keymap.set? Like vim.keymap.set("n", "<space>ss", "<plug>(iron-send-line)")?
Also, it can be that those mappings to <plug>() are not needed anymore and one can use iron api to map straight to the lua functions, by adding the keymaps key to the setup{} function:
local iron = require("iron.core")

iron.setup{
  -- config...
  keymaps = {
    send_line = "<space>ss",
  }
}


college student database

[Enter feedback here]

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

ID: dba1f3f2-8c1f-c913-dcfb-4c3332ef9c22
Version Independent ID: 273274cb-72b7-1696-32eb-a5d2f7d6c0dd
Content: School Sample Database - EF6
Content Source: entity-framework/ef6/resources/school-database.md
Product: entity-framework
Technology: entity-framework-6
GitHub Login: @ajcvickers
Microsoft Alias: avickers

@Sabarijothi do you have a question or an issue to be raised?


added css gradient and rounded corner

ISSUE #26
Added Rounded Corner-

Added Css gradient-

Added font color

Please add this as the main background color #b0f3ae and also change the font color because it hurt my eyes.

Main Background Fixed

Font Color Changed

Button Color Smoothend

Thank you!
@all-contributors please add @amardeep911 for code


Provide unit tests for hexaString32Validator

Provide unit tests for hexaString32Validator

Implemented in https://github.com/RedHatInsights/insights-data-schemas/pull/40

Implemented in https://github.com/RedHatInsights/insights-data-schemas/pull/40


geetest type captcha problem

Version of the software
openbullet2
Operating system
windows 10
Browser / Native
chrome 10
What happened?
I face this problem when solving a geetest captcha, although 2caprcha offers a solution for this type, how can this issue be resolved.
The error message is as follows: [Executing block Solve Gee Test Captcha] TaskSolutionException: Exception of type ‘CaptchaSharp.Exceptions.TaskSolutionException’ was thrown.

Relevant LoliCode if needed
No response

Works for me:

Maybe the data for GT and Challenge are outdated? If i remember right these are valid only for 1 use and a short timeframe.

يعمل لدي:

ربما تكون بيانات GT و Challenge قديمة؟ إذا كنت أتذكر حقًا ، فهذه صالحة للاستخدام مرة واحدة فقط ولإطار زمني قصير.

I want to communicate with you 5 minutes do you have a telegram

Works for me:

Maybe the data for GT and Challenge are outdated? If i remember right these are valid only for 1 use and a short timeframe.

How are the variables written directly in the post data that appears in the image?

It will create a variable called (in this case) solveGeeTestCaptchaOutput with the 3 values serialized as json, so you have to parse them manually. This is due to a limitation in OB2 where blocks cannot return more than 1 value. Anyways marking this as solved since there is no issue with GeeTest.

It will create a variable called (in this case) solveGeeTestCaptchaOutput with the 3 values serialized as json, so you have to parse them manually. This is due to a limitation in OB2 where blocks cannot return more than 1 value. Anyways marking this as solved since there is no issue with GeeTest.

Is it possible to form a script to make each variable separately?

As I said you have to use the PARSE block 3 times and parse each one of them to a separate variable.

As I said you have to use the PARSE block 3 times and parse each one of them to a separate variable.

ok thank you


db_sesssion is None, Using BasicAuth and only a subset of GSuite Plugins

Describe the bug
Towards #686 I've made all the changes to use the service account without any delegation to do all the GSuite API calls. However, I found a bug while creating an incident.
This is the state of what plugins are enabled, since without Domain-Wide Delegation we can't get gmail and calendar plugins to work, I've disabled them.

DEBUG:Updated the external ticket DT-40.:/usr/local/lib/python3.8/site-packages/dispatch/incident/flows.py:update_external_incident_ticket:167
DEBUG:Incident created notifications sent.:/usr/local/lib/python3.8/site-packages/dispatch/incident/messaging.py:send_incident_created_notifications:270
INFO:Dispatch Core App: Incident notifications sent:/usr/local/lib/python3.8/site-packages/dispatch/event/service.py:log:154
DEBUG:Recommendation: Documents: [] Individuals: [] Teams: [] Services: []:/usr/local/lib/python3.8/site-packages/dispatch/route/service.py:create_recommendation:128
ERROR:'NoneType' object has no attribute 'query':/usr/local/lib/python3.8/site-packages/dispatch/incident/flows.py:incident_create_flow:716
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/dispatch/incident/flows.py", line 702, in incident_create_flow
    send_incident_participant_announcement_message(
  File "/usr/local/lib/python3.8/site-packages/dispatch/incident/messaging.py", line 391, in send_incident_participant_announcement_message
    participant_info = contact_plugin.instance.get(participant_email)
  File "/usr/local/lib/python3.8/site-packages/dispatch/plugins/dispatch_core/plugin.py", line 214, in get
    individual_service.get_by_email(db_session=db_session, email=email),
  File "/usr/local/lib/python3.8/site-packages/dispatch/individual/service.py", line 32, in get_by_email
    db_session.query(IndividualContact).filter(IndividualContact.email == email).one_or_none()
AttributeError: 'NoneType' object has no attribute 'query'

Looking closely at the function below:
class DispatchContactPlugin(ContactPlugin):
    title = "Dispatch Plugin - Contact plugin"
    slug = "dispatch-contact"
    description = "Uses dispatch itself to resolve incident participants."
    version = dispatch_plugin.__version__

    author = "Netflix"
    author_url = "https://github.com/netflix/dispatch.git"

    def get(self, email, db_session=None):
        print(f"db_session is: {db_session}")
        return getattr(
            individual_service.get_by_email(db_session=db_session, email=email),
            "__dict__",
            {"email": email, "fullname": email},
        )

I found that db_session if not passed is set to None in this call:
  File "/usr/local/lib/python3.8/site-packages/dispatch/incident/messaging.py", line 391, in send_incident_participant_announcement_message
    participant_info = contact_plugin.instance.get(participant_email)

My question is:
Does this warrant the change for this line of code from:
         participant_info = contact_plugin.instance.get(participant_email)

to
        participant_info = contact_plugin.instance.get(participant_email, db_session)

to pass the db_session as needed by the get() method, because the log suggests it's passed as none or am I missing something?

You're right. I'll put out a fix for it.

@mvilanova:
So since I have docs plugin enabled and I'm using a service account for authenticating with the workspace APIs, I was testing the incident creation workflow, I seem to be stuck with this screen:

For the bug above I made the change I proposed and was able to eliminate that particular error, However, I still see the above screen and I see no real bugs on the logs side.
I was wondering if there is a default document created for every incident? Is there any artifact created using the Docs API at incident creation time?

We do try to create the incident collaboration documents on incident create if the storage plugin is enabled (see here). Did you add the document template(s) in the UI and map them to the incident type(s)?
https://github.com/Netflix/dispatch/pull/886 fixes the first issue.

If you have templates, does your service account have access to them, so the storage plugin can copy them to the incident folder?

Ah I see @mvilanova . I don't believe I setup any templates. Are there any sample templates you can share?

We do here, it looks like I didn't add them to the documentation yet though :-(

I'll test and get back to you. Thank you!

If you have templates, does your service account have access to them, so the storage plugin can copy them to the incident folder?

@mvilanova When you say add them to the UI, I've to add the document in the Knowledge -> Documents and then link that document in the Configuration -> Incident Type?

Yes, that's correct @sfc-gh-pkommini

So @kevgliss @mvilanova while adding a document, I see these items to fill out:

I have the following questions regarding this form:

May I know what are the possible document types?
Also, I'm guessing Owner is an email address? so, for adding Generic Incident Document what should I enter for owner? It is my email address as I copied the document into our shared drive?
Finally, why does the document owner need a reminder and in what context is this reminder sent out?
Does the reminder only apply if the Evergreen box is checked? This evengreen feature is not fully clear, Could you clarify what is the purpose of this checkbox?

All of the evergreen stuff is optional (enabled, owner, reminder). Evergreen is a feature for documents that should be kept up to date, for instance, if you have a runbook that you want to be reviewed once a quarter, you would set an individual or team DL to receive an email reminder notification to update the document after 90 days.
Document type is optional as well and is just used for you to define the type of document. As documents are just links it's useful to give them some additional metadata e.g. google doc, confluence doc

Oh that helps. Thank you! Makes perfect sense to have a frequency to update the runbook/playbook.

@kevgliss, Final question,
INCIDENT_CONVERSATION_COMMANDS_REFERENCE_DOCUMENT_ID=INCIDENT_CONVERSATION_COMMANDS_REFERENCE_DOCUMENT_ID
INCIDENT_ONCALL_SERVICE_ID=None
INCIDENT_DOCUMENT_INVESTIGATION_SHEET_ID=INCIDENT_DOCUMENT_INVESTIGATION_SHEET_ID
INCIDENT_FAQ_DOCUMENT_ID=INCIDENT_FAQ_DOCUMENT_ID
INCIDENT_NOTIFICATION_CONVERSATIONS=
<EMAIL_ADDRESS>INCIDENT_RESOURCE_CONVERSATION_COMMANDS_REFERENCE_DOCUMENT=google-docs-conversation-commands-reference-document
INCIDENT_RESOURCE_FAQ_DOCUMENT=google-docs-faq-document
INCIDENT_RESOURCE_INCIDENT_REVIEW_DOCUMENT=google-docs-incident-review-document
INCIDENT_RESOURCE_INCIDENT_TASK=google-docs-incident-task
INCIDENT_RESOURCE_INVESTIGATION_DOCUMENT=google-docs-investigation-document
INCIDENT_RESOURCE_INVESTIGATION_SHEET=google-docs-investigation-sheet
INCIDENT_RESOURCE_NOTIFICATIONS_GROUP=google-group-participant-notifications-group
INCIDENT_RESOURCE_TACTICAL_GROUP=google-group-participant-tactical-group

For these configs, Should I create a document in Knowledge -> Documents with name google-docs-faq-document and google-docs-investigation-document and so on? Is the name the link that uses that config and then uses the corresponding name to review the corresponding google doc?

Yes, that is how they are associated today (you shouldn't need to set any IDs in the configuration file anymore).
In the future, we will likely make this easier and more straightforward in the UI and abstract this detail from the users.

@kevgliss Do you have any template that you can share for the configs below?
INCIDENT_RESOURCE_INCIDENT_TASK=google-docs-incident-task
INCIDENT_RESOURCE_INVESTIGATION_DOCUMENT=google-docs-investigation-document

How is investigation document different from investigation sheet? I see that the investigation sheet is shared here: https://docs.google.com/spreadsheets/d/1Odk4KlL7uMF_yd7OvTOCaPWmtTA_WzFBIA4lMeU5cGY, but didn't see one for investigation document.

@kevgliss Do you have any template that you can share for the configs below?
INCIDENT_RESOURCE_INCIDENT_TASK=google-docs-incident-task
INCIDENT_RESOURCE_INVESTIGATION_DOCUMENT=google-docs-investigation-document

I'm not sure what you mean, these are just strings used to denote which documents are of a given type.

How is investigation document different from investigation sheet? I see that the investigation sheet is shared here: https://docs.google.com/spreadsheets/d/1Odk4KlL7uMF_yd7OvTOCaPWmtTA_WzFBIA4lMeU5cGY, but didn't see one for investigation document.

The sheet is just a generic sheet created for all incidents, the templates for the other documents can be found here:
Incident Investigation Document:
https://docs.google.com/document/d/1fv--CrGpWJJ4nyPR0N0hq4JchHJPuqsXN4azE9CGQiE
Incident Review Document:
https://docs.google.com/document/d/1-VwcEpVVdymoojdUg9e5XP8QGam0-B5Djxh-guuPpEc
Executive Report:
https://docs.google.com/document/d/1dab6k14p5ageo5B_d1YlB_zS9hMGHDMXy9RUbIZous4

@kevgliss
I see so investigation document == generic incident document.
My question regarding the configs below was assuming that if I have the INCIDENT_RESOURCE_INCIDENT_TASK config variable = google-docs-incident-task, then we have a document created under Knowledge -> Documents named google-docs-incident-task, and so I was requesting for the template related to google-docs-incident-task.
INCIDENT_RESOURCE_INCIDENT_TASK=google-docs-incident-task
INCIDENT_RESOURCE_INVESTIGATION_DOCUMENT=google-docs-investigation-document

Is that not how it works?

That is how it works, but confusingly, tasks don't have their own document.
Tasks have their own types to help us understand where they originate from. In this case, tasks default to originate from google doc.
So while

INCIDENT_RESOURCE_INCIDENT_TASK=google-docs-incident-task
INCIDENT_RESOURCE_INVESTIGATION_DOCUMENT=google-docs-investigation-document

seem related they are not.

Ah I see. So that's just alluding to google docs being the source of the tasks. Gotcha.
I think I have everything to continue testing the creation of docs during the incident flow. I'll let you know if I'm able to get past the screen where I'm stuck at right now that shows Creating Incident Documents ..., but doesn't really throw any error either.

If it's just waiting on Creating Incident Documents ... from a UI it's just waiting for any document to be created:
https://github.com/Netflix/dispatch/blob/master/src/dispatch/static/dispatch/src/incident/ReportReceiptCard.vue#L153
We probably need to add a check to this similar to <span v-if="activeResourcePlugins.storage"> to ensure that you actually have a plugin with the type document enabled before showing the loading bar.
I would double-check that you have that plugin enabled and see if you have any errors on the backend.


How to connect to server using IP address not by domain name?

Hi @vinniefalco ,
 I tried the websocket sync demo using the domain name 'echo.websocket.org' it works ok.

I tried the IP address '<IP_ADDRESS>' (It`s domain echo.websocket.org `IP address ).  And it failed for reason : hand shake failed.

I want to know how to connect to server using websocket by (ip address, port , target)

Has this been resolved?


if_else with more than 1 argument

Hello,
I was wondering why the if_else function doesn't take more than one argument?
In my case, I'd like to be able to call a function with multiple arguments like so:
$return = if_else($condition, $ifTrue, $ifFalse);
return $return($param1, $param2);

Is there any particular reason for this not to work currently?
Regards,

yes, the if_else function just take one argument.
I think this function may help you
function if_else(callable $if, callable $then, callable $else)
{
    return function (...$value) use ($if, $then, $else) {
        return $if(...$value) ? $then(...$value) : $else(...$value);
    };
}

What we are missing is logical operator functions here:
$cond = if_else(…, …, …);
$cond(and($param1, $param2));
$cond(or($param1, $param2));
$cond(xor($param1, $param2));

Happy to get a pull request for those


Add group features to iot

Added group related features to aws-iot. @terrycain @JackDanger please review if you time ;)

Coverage decreased (-0.3%) to 91.872% when pulling b7ef167d8d5952269781cc555c7c848d46c54334 on toshitanian:iot-group into e75f3ef4d4f7b0fa7e14dbb4431d379b68ae5502 on spulec:master.

Coverage decreased (-0.3%) to 91.872% when pulling b7ef167d8d5952269781cc555c7c848d46c54334 on toshitanian:iot-group into e75f3ef4d4f7b0fa7e14dbb4431d379b68ae5502 on spulec:master.

Coverage decreased (-0.007%) to 92.134% when pulling 92ca583d6bc48ae05cd1958c61b39453acb85534 on toshitanian:iot-group into e75f3ef4d4f7b0fa7e14dbb4431d379b68ae5502 on spulec:master.


EU GDPR

Since email addresses are personally identifiable information, how do you meet the requirements of the GDPR?

I'm no lawyer, but I think the GDPR concerns every company processing, not storing, PII.

I notice other services offer a GDPR page outlining what they're doing to secure data - we of course are fully securing any data behind firewalls and such and so I'll also add a GDPR page to help comply with GDPR more so as well


requirement.txt

Could you please release the version of the packages you use? Not just the torch version but the other packages version

Thanks!
It does a lot of help.
I am bothered by this all night.
Thank you for your fast and helpful reply.
Love from China


[Custom Components] How to create custom component with data source api url

What do you mean by data source api?

I want to get data from api for my custom checklist box component

We're currently addressing a backlog of GitHub issues, and as part of this effort, some inactive issues may be marked as closed. This isn't a dismissal, but a step toward more efficient tracking.
If you feel the issue is still relevant, please re-open and we'll ensure it gets the attention it deserves. Your understanding is appreciated as we work to enhance our open-source responsiveness.


Update RELEASING.md when minimal-plotly is released again

Follow-up to #17

Closing as captured in #23


Getregion opts

Continues of https://github.com/vim/vim/pull/13998

Add opts arguments

{pos1} and {pos2} can be list

I don't understand what is the correct argument check.
Note: I want to add winid support, but I gave up.  current routine depends on current buffer...

Thanks, It's a bit disappointing, that we first make it using string args and now we add in addition list args, plus an optional dict type. I thought we could avoid having different types for the same function. Also, initially when I suggested the type arg, I meant it to be using a dict object instead. Now we are adding yet another dict argument for additional settings.
Let's see what others think.

I have decided the 3rd argument {type} is not optional.
Because it is not only for visual mode function.  It should be explicit.

Thanks, It's a bit disappointing, that we first make it using string args and now we add in addition list args, plus an optional dict type. I thought we could avoid having different types for the same function. Also, initially when I suggested the type arg, I meant it to be using a dict object instead. Now we are adding yet another dict argument for additional settings.
Let's see what others think.

I agree.  In one of the comments for the previous PR, I mentioned this point about using a Dict
for the third argument.  The third argument should be a Dict.

I have decided the 3rd argument {type} is not optional. Because it is not only for visual mode function. It should be explicit.

You can use a default behavior.  You can add a "visualmode" item in the Dict that specifies the desired visual mode.

I agree. In one of the comments for the previous PR, I mentioned this point about using a Dict
for the third argument. The third argument should be a Dict.

We added getregion() in 9.1.120 just last week. I suppose it is okay to change the getregion() behaviour and just use
getregion({pos1}, {pos2}, {Dict})			*getregion()*
		Returns the list of strings from {pos1} to {pos2} as if it's
		selected in visual mode of {type}. {pos1} and {pos2} are list
                items. For possible values see |getpos()|
		{Dict} is a dictionary with additional properties and supports
                the following keys:
                'type':  specify the selection type, supports the following
                values: "v" for |characterwise| mode
			"V" for |linewise| mode
			"<CTRL-V>" for |blockwise-visual| mode
                'selection': specify the 'selection' mode using the values
                             from the 'selection' setting.

Something like this?

I agree. In one of the comments for the previous PR, I mentioned this point about using a Dict
for the third argument. The third argument should be a Dict.

We added getregion() in 9.1.120 just last week. I suppose it is okay to change the getregion() behaviour and just use
getregion({pos1}, {pos2}, {Dict})			*getregion()*
		Returns the list of strings from {pos1} to {pos2} as if it's
		selected in visual mode of {type}. {pos1} and {pos2} are list
                items. For possible values see |getpos()|
		{Dict} is a dictionary with additional properties and supports
                the following keys:
                'type':  specify the selection type, supports the following
                values: "v" for |characterwise| mode
			"V" for |linewise| mode
			"<CTRL-V>" for |blockwise-visual| mode
                'selection': specify the 'selection' mode using the values
                             from the 'selection' setting.

Something like this?

Yes.  That looks good to me.

OK.  I have changed {type} to {opts}.

I have changed {type} default value.

In Vim9, supporting different types for the same argument is deprecated.
From a type checking perspective, it is better to support only
one type for the arguments.

i may suggest re-thinking this "claim", IMO:

user defined func perhaps should be only one type for an argument,
but to vim native function "supporting different types for the same argument" was a tricky/classic/good design.

--
shane.xb.qian

Thanks, but I'd rather see either we change the first two position arguments to a list type and drop the string type or we do not change the type further. But let's not do both. It's also better for Vim9 type checking when compiling the function.

Thanks, but I'd rather see either we change the first two position arguments to a list type and drop the string type or we do not change the type further. But let's not do both. It's also better for Vim9 type checking when compiling the function.

I have changed the interface.  {string} is not allowed.

Can I get some comments before I merge? Everybody fine with this backwards-incompatible change?

Can I get some comments before I merge? Everybody fine with this backwards-incompatible change?

I think it is fine, I doubt anyone used getregion() in the plugins yet.

I have fixed the documentation.

Actually now that pos1 and pos2 only support lists, it should be possible to support non-current buffer as long as they have the same buffer number.

Actually now that pos1 and pos2 only support lists, it should be possible to support non-current buffer as long as they have the same buffer number.

It is possible.  But I gave up.  The PR is welcome.

Fixed.

Well, prop_remove() arguments are line numbers.  It seems getline() like interface.
Of course, I can change the behavior.  If pos1 pos2 is reversed, it can returns empty.

I have checked visual mode region behavior.  It works if visual start and cursor position is swapped.

yes, please think if it should 'order' matters,
and actually if it was a visual selection, really needed to pass pos1/2 ?

Because it is not only for visual mode.  It is just get region text from pos1 to pos2.

getregion() <- what?

maybe getregiion(vs_type) was enough?

In case of getting visual text in vimscript I don't like the idea of checking if pos1 is less than pos2 before calling the function. I often use o to extend visual from both sides...

yes, please think if it should 'order' matters,

Order should not matter. Let's not add burden to plugin authors so everybody has to figure out how to determine which position comes first. That is not so trivial

and actually if it was a visual selection, really needed to pass pos1/2 ?

Yes, let's please keep it consistent. It should be fine to always give two position as arguments. The function signature should be the same always. That's better for Vim9 scripting it can easier detect potential problems.

yes, please think if it should 'order' matters,

Order should not matter. Let's not add burden to plugin authors so everybody has to figure out how to determine which position comes first. That is not so trivial

yes, that's the why asking such "question", since now some native function was 'order' matter.

and actually if it was a visual selection, really needed to pass pos1/2 ?

Yes, let's please keep it consistent. It should be fine to always give two position as arguments. The function signature should be the same always. That's better for Vim9 scripting it can easier detect potential problems.

and further, actually to this 'getregion()' function, looked the pos1/2 not only not matter, but also seems maybe not required, or the signature should be getregion(vs_type, [pos1, [pos2]]), that maybe was the reducing plugin author or general vim user's burden.
// just my opinion, but your call.

yes, that's the why asking such "question", since now some native function was 'order' matter.

For the purpose of getting the region, we only need to know the beginning and end-points. Order shouldn't matter, Vim can figure it out on its own which one is the starting and which one is the end position, right? For all other examples, this is not the case and then order matters of course.

and further, actually to this 'getregion()' function, looked the pos1/2 not only not matter, but also seems maybe not required, or the signature should be getregion(vs_type, [pos1, [pos2]]), that maybe was the reducing plugin author or general vim user's burden.

I would think the positions are the most important parameters, so they should come first, don't you think? Then we have added another parameter, that allows you to further specify additional properties but you don't have to specify them, it's an optional dictionary. And we can later add additional settings, without changing the function signature.

I would think the positions are the most important parameters, so they should come first, don't you think?

i donot know, but please check prop_remove and prop_clear, that maybe give your answer, to me, i felt getregion is similar like prop_remove.
// all in all, i think the usage of vim should keep consistent, specially those tricky/classic/good design.

i donot know, but please check prop_remove and prop_clear, that maybe give your answer, to me, i felt getregion is similar like prop_remove.

I don't think so, it is quite different.

I would think the positions are the most important parameters, so they should come first, don't you think? Then we have added another parameter, that allows you to further specify additional properties but you don't have to specify them, it's an optional dictionary. And we can later add additional settings, without changing the function signature.

Yes.  If a builtin function needs optional arguments, then it should use a Dict as the last argument.
Instead of a Dict, if a specific type is used for the optional arguments, then when using multiple optional
arguments, to specify an optional argument all the preceding optional arguments must be specified.
For example, take the count() function as an example:
count({comp}, {expr} [, {ic} [, {start}]])
This function accepts two optional arguments.  To specify the starting position, the 'ignorecase'
argument must be specified (even if it is not needed).  This is not a good design.

to this 'getregion()' function, looked the pos1/2 not only 'order' not matter, but also seems maybe not required

it may only be not required, if you want to get the last visual selected region. But what if you want to get the region for various other marks?

to this 'getregion()' function, looked the pos1/2 not only 'order' not matter, but also seems maybe not required

it may only be not required, if you want to get the last visual selected region. But what if you want to get the region for various other marks?

then what that 3rd arg type default v for?
or was there really possible needing for other marks? or had getbufline there for them.
--
shane.xb.qian

then what that 3rd arg type default v for?

To specify what kind of a selection you want? That matters for all cases of selection of course.

or was there really possible needing for other marks? or had getbufline there for them.

Why not? Why are you trying to argue so much against it?

if "against" the passed vim classic design

So what exaclty was vim classic design? We have always added new features.

getregion(pos1, pos2, {opts})
getselection({opts})

This adds too much clutter. Why having 2 functions performing almost the same thing?

a-1. getregion({opts}, [pos1, [pos2]])
a-2. getregion({opts}, [pos1, pos2])

It doesn't make sense to {opts} as the first variable, since it is optional.  We could have made one list of position lists, but I think then it wouldn't work as -> method call

a-1. getregion({opts}, [pos1, [pos2]])
a-2. getregion({opts}, [pos1, pos2])

It doesn't make sense to {opts} as the first variable, since it is optional.  We could have made one list of position lists, but I think then it wouldn't work as -> method call

please check 'prop_remove()', similar situation, it can be -> method call, if a-1 not preferred, then perhaps a-2 was good.
and {opts} was not optional, since had to indicate a 'selection shape' anyhow as above said so, just there was a default value.
--
shane.xb.qian

but it is truly Not worthy to refactor it again,
it shoud be ok as long as if user knew that was not 'visual selection' but 'selection shape'.. :shrug:
let it be~ thanks arguing with me.. :smile:


Background Location Updates

Hi,
I have a question about this background issue. In swiftLocation documentation Location.allowsBackgroundEvents = true code writes for activate background location updates. I integrate SwiftLocation to my new project but, there is not any variable to set allowsBackgroundEvents
When I am trying to get location there is a log like
A new request is added to the queue [LOC:826CB3FC-F0BD-4CB8-B8E2-EB6B598BE02F] - Acc=Room, Fq=Significant. (Status=running, Queued=true) oYn4pRVBj3e56KTO0QXIhgABzT32 An existing request was removed from the queue [LOC:826CB3FC-F0BD-4CB8-B8E2-EB6B598BE02F] - Acc=Room, Fq=Significant. (Status=idle, Queued=false) Location monitoring failed due to an error backgroundModeNotSet
In my info.plist I insert the required background modes and I also open Location updates in Background Modes in Capabilities section.
What can be the problem ?
Thanks for any help
My code is below (taken from Demo project):
`//Taking Location
Location.onAddNewRequest = { req in
    print("A new request is added to the queue \(req)")
}
Location.onRemoveRequest = { req in
    print("An existing request was removed from the queue \(req)")
}

let x = Location.getLocation(accuracy: .room, frequency: .significant, success: { (_, location) in
    print("A new update of location is available: \(location)")
    let longitude = location.coordinate.longitude
    let latitude = location.coordinate.latitude
    self.firebaseManager.setLocation(uid: uid!, longitude: longitude, latitude: latitude)

}) { (request, last, error) in
    request.cancel() // stop continous location monitoring on error
    print("Location monitoring failed due to an error \(error)")
}
x.register(observer: LocObserver.onAuthDidChange(.main, { (request, oldAuth, newAuth) in
    print("Authorization moved from \(oldAuth) to \(newAuth)")
}))

//taking Location end`

Hi @umutdonmez8 , you need to set "Background fetch" in capabilities.

As @aliasdoc said you must also enable location UIBackground capabilities


fields that are changed by RENDERING_MAPPINGS are not synchronised

Currently, names of fields are replaced by Stipple.RENDERING_MAPPINGS when a model is rendered. Also when a field is newly pushed from the backend, the name is correctly translated.
However, for the the syncing to the backend there is no inverse translation. Particularly after loading StippleUI, a lot of fieldnames are translated.
There are two possible ways out:

include a reverse translation
don't translate at all

I, personally, was very surprised to see translation happening at all. I think it is can be quite confusing, particularly if you write templates.
In some cases it even breaks functionality, e.g. when "selected" is translated to "v-model:selected". (I knew it was not functioning for more than a year, but only found out the reason today...)
@essenciary How do we proceed?

I don't fully understand - can you provide a MWE with more details on what to look for?

Take the follwoing MWE:
@app HH begin
    @in keepcolor = true
end

ui() = toggle("test", :keepcolor)

route("/") do
    global model
    model = @init HH
    page(model, ui) |> html
end

model.keepcolor[]
# keeps being true, independent of the toggle position

The reason is that "keepcolor" is translated to "keepColor"
julia> render(HH())[:data]
Dict{String, Any} with 4 entries:
  "keepColor"    => true
  "isready"      => false
  "isprocessing" => false
  "fileuploads"  => Dict{AbstractString, AbstractString}()

During field updating we don't find the field "keepColor" and reject the incoming update request.

In case of "selected", the translation to "v-model:selected" doesn't make sense at all and the field is not exposed.

Won't removing them be breaking? People might be using them in their apps.

It's breaking, but only for potential js expressions where people must have been aware of the julia_to_view translation. I doubt that people are using it, because the synching to the backend is not working. Someone would have complained.

I think it is sufficient to remove the addition of render mappings in StippleUI.

In this context I looked where we are using julia_to_vue.
I found a stange occurrence in https://github.com/GenieFramework/Stipple.jl/blob/master/src/Stipple.jl#L1097-L1098
attr_val = isa(v, Symbol) && ! startswith(string(k), ":") ? Stipple.julia_to_vue(v) : v

as this changes the value of an attribute pair. All other occurences address the key. Maybe this is just wrong?
julia> Stipple.attributes([:mykey => :menuoffset])
(var":mykey" = "menuOffset",)

Most probably we can just remove julia_to_vue completely, as the only thing it does is converting a Symbol to a string, which will happen anyhow if we json the final dict.

fixed by #279


E2E tests fail to build contracts when using workspace dependencies

Issue in on-ink github: https://github.com/paritytech/ink/issues/1919

PR in cargo-contract: https://github.com/paritytech/cargo-contract/pull/1358
PR in ink-examples: https://github.com/paritytech/ink-examples/pull/44


Update chain.json

Update chain.json fron PPNV Service
change server

Please use a descriptive title for your PR


Thanks for the PR. I do wonder if this is something that should be added as a configurable parameter? Also, is there a reason you chose to only apply lazy loading to the markdown rendering template and not in other areas like the figure partial?

I do wonder if this is something that should be added as a configurable parameter?

Sounds reasonable, should probably work on this.

is there a reason you chose to only apply lazy loading to the markdown rendering template and not in other areas like the figure partial?

Not really, that's my mistake in missing those, which should be set to lazy-load, too.
Seems like we need to work on this more to support, I'll try to find some time.

@jpanther I think this is ready to go!

Thanks for the changes, I think this is now a complete implementation and am happy to merge it in. It will be included in the next theme release.

  Above the fold shouldn't be lazy loaded, it actually just looks weird , and shifts text down when it appears.
Better would be to not lazy load cover or featured image, then load rest - or make it option. none/all/notcover?

Thanks @hystedm. I've opened a new issue #591 to track this.


Feature/security context propagation

Hello Team,
Here is a small patch for Operator to be able to set Redis Containers securityContext.
Also I've added a simple example how to setup the securityContext fields for pod and container contexts.

Thanks, @alexeyNsorokin


scheduler: use async snapshot

What have you changed? (mandatory)
Scheduler takes snapshot via the async_snapshot API.
What are the type of the changes? (mandatory)

Improvement (non-breaking change which is an improvement to an existing feature)

How has this PR been tested? (mandatory)
Unit tests.
Does this PR affect documentation (docs/docs-cn) update? (mandatory)
No.
Does this PR affect tidb-ansible update? (mandatory)
No.
Refer to a related PR or issue link (optional)
#2111
Benchmark result if necessary (optional)

/run-all-tests


Generic shares_base module and specific s3_datasets_shares module - part 1 (renaming, enums and permissions)

Feature or Bugfix

Feature
Refactoring

Detail
As explained in the design for #1123 and #1283 we are trying to implement generic datasets_base and shares_base modules that can be used by any type of datasets and by any type of shareable object in a generic way.
In this PR:

Rename dataset_sharing as s3_dataset_shares
Create shares_base and introduce dependency (s3_dataset_shares depends on shares_base)
Move generic enums to shares_base
Move generic permissions to shares_base

Relates

#1283
#1123
#955

Security
Please answer the questions below briefly where applicable, or write N/A. Based on
OWASP 10.

Does this PR introduce or modify any input fields or queries - this includes
fetching data from storage outside the application (e.g. a database, an S3 bucket)?

Is the input sanitized?
What precautions are you taking before deserializing the data you consume?
Is injection prevented by parametrizing queries?
Have you ensured no eval or similar functions are used?

Does this PR introduce any functionality or component that requires authorization?

How have you ensured it respects the existing AuthN/AuthZ mechanisms?
Are you logging failed auth attempts?

Are you using or adding any cryptographic features?

Do you use a standard proven implementations?
Are the used keys controlled by the customer? Where are they stored?

Are you introducing any new policies/roles/users?

Have you used the least-privilege principle? How?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Testing locally:

[ ] All modules in BE are loaded
[ ] list Shares: with share owners and with dataset owners
[ ] create Share with all S3 items and approve it. Check that ECS task succeeds
[ ] revoke share


Remove unused StreamBlockPageQuerySet

This PR removes our complicated, raw sql-based, PostgreSQL-only StreamBlockPageQuerySet. For querying into stream field values, we have a more consistently reliable approach in https://github.com/cfpb/wagtail-content-audit in the form of its PageSearchQuerySet.
Checklist

[x] PR has an informative and human-readable title
[x] Changes are limited to a single goal (no scope creep)


EPersonaState

Every time that I run this code -
*
const SteamUser = require('steam-user');
const config = require('./config.json');
const client = new SteamUser();
const logOnOptions = {
accountName: config.username,
password: config.password
};
client.logOn(logOnOptions);
client.on('loggedOn', () => {
console.log('Logged into Steam');
client.setPersona(SteamUser.Steam.EPersonaState.Online);
client.gamesPlayed(440);
});
*
I get an error message saying -
*
client.setPersona(SteamUser.Steam.EPersonaState.Online);
^
TypeError: Cannot read property 'EPersonaState' of undefined
*

dat error

v4 came with many breaking changes. Please read the release notes and familiarize yourself with what changed.
In your specific case, you need to replace SteamUser.Steam.EPersonaState with SteamUser.EPersonaState.

thank u

Try this:-
client.setPersona(SteamUser.EPersonaState.Online);
Instead Of:-
client.setPersona(SteamUser.Steam.EPersonaState.Online);


No 'Access-Control-Allow-Origin' header is present

http://docs.aws.amazon.com/AmazonS3/latest/dev/cors.html

Fixed.


EPIC: Add Back-end Workflow requirements for "Curve Healthy DEGEN JuiceBOT"

Add Back-end Workflow requirements for "Curve Healthy DEGEN JuiceBOT"
Notion: https://www.notion.so/volumefi/EPIC-03-01-24-Curve-leverage-lending-bot-with-automatic-re-leveraging-aka-Curve-Healthy-DEGEN-Juic-0d634914ea9040ed933b8758d553b261

https://www.notion.so/volumefi/EPIC-03-01-24-Curve-leverage-lending-bot-with-automatic-re-leveraging-aka-Curve-Healthy-DEGEN-Juic-0d634914ea9040ed933b8758d553b261

@fieldtheory123 Anything else left here

@fieldtheory123 Anything else left here

Should be all set


Only install dataclasses dep in python 3.6

Use the PEP508 python_version environment marker in our setup.py file to correctly install the pypi dataclasses dependency only for python3.6 and not for python3.7 and above where the builtin dataclasses library must be used.
Fixes #269

Note: external-only change so GH merge should be ok, shouldn't need to be dealt w. in internal copybara.


[SPARK-24368][SQL] Removing columnPruning from CSVOptions

What changes were proposed in this pull request?
In the PR, I removed the private columnPruning value from CSVOptions. The flag is initialized in place by reading of spark.sql.csv.parser.columnPruning.enabled. It should make UnivocityParserSuite more stable.

Can one of the admins verify this patch?

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/91057/
Test PASSed.


Cannot debug in Neon.Temporal

Trying to debug the Neon.Temporal client and the vsTestRunner is throwing an exception:
System.BadImageFormatException: 'Could not load file or assembly 'testhost, Culture=neutral, PublicKeyToken=null'. An attempt was made to load a program with an incorrect format.'

This is blocking from debugging issues in the Neon.Temporal Client.

I'm not able to repro this on my workstation (running the EndToEnd_WorkflowWithNoResult test, but I am seeing a
Neon.Temporal.ConnectException : Cannot connect to Temporal cluster.
exception from the proxy.  I tried running Temporal on both Docker/WSL2 and Docker/Hyper-V with the same results.
You didn't include the stack trace in your report but I'll bet the exception is being thrown at TemporalClient.cs:875 where we launch the temporal-proxy.
I wonder if the proxy executable has gotten corrupted somehow.  Can you please try to execute this file manually and see what happens?  If you set a breakpoint at TemporalClient.cs:875 then the binaryPath variable will be the path to the executable.
I was able to manually start the proxy via the command line from the Build directory and it started OK for me.
I wonder if something wonky happened with the proxy build on your machine.  It is possible for proxy executable to be corrupted if the process terminates while the TemporalClient is extracting proxy executable and writing it to disk, resulting in the file being truncated.  But, the proxy is always re-extracted and written again the first time a connection is established in a new process and since the executable will be extracted in just a moment, this seems unlikely to be the issue..
But, you should make a note about the size of the extracted proxy executable and compare it against the executable in the Build folder just to be sure.
I'm hoping that somehow proxy executable got corrupted somehow during the build and that a clean build will fix it.  I'm now sure what's happening with the connect exception though, but once we get past the corruption issue we can have a look at that.

Fixed.  I was running projects in tests as x86 architecture.

Fixed the proxy issue as well.  DebugPrelaunch was toggled on in proxy so it was always trying to send replies to https://<IP_ADDRESS>:5001


UTF error on NixOS

When running the example code from the readme on NixOS 20.09, I get the following output:
Error: Error { source: Custom { kind: InvalidData, error: "stream did not contain valid UTF-8" }, description: None }
I have seen the issue magically fix itself on reboot twice now, but cannot reproduce that behaviour -- it seems to happen for no reason at all. This is on a ThinkPad X1 Extreme Gen 2, I've also tested the example code on Arch Linux on the same computer and it seems to work perfectly. No idea how to troubleshoot this, I'm not particularly knowledgeable about rust (I ran into the issue because rust-battery is a dependency of dwm-status). NixOS has a pretty unique package manager that stores things at weird paths, so it might be related to that? Any help would be greatly appreciated.
Side note: I don't think this is related to #72 -- I tried using rust-battery as a local dependency after altering device.rs as described in the first post of that thread, but the error persisted.

Update: I think this is the same issue as #72 after all, the unpredictability seems to come from /sys/class/power_supply/BAT0/manufacturer and cat /sys/class/power_supply/BAT0/model_name occasionally being formatted in UTF-8 upon reboot but usually being scrambled as in #72. Very bizarre, if anyone knows why that might be happening I'd love to know. Will close the issue now since I figure the unpredictability means that there's probably something I can do to fix it outside of rust-battery


Disable automatic incrementation in the download excel sheets.

What are you missing?
(PCT Workshop Feedback)
Currently i have to manually edit a lot of information in the downloaded excel sheet (sample registration/editing, measurement registration/editing). While doing so, if i drag and drop values within the cells the numerical value is incremented automatically. This is especially annoying if it happens within the URL of the instrument and organisation ontology.
Why do you need a solution?
Having to manually troubleshoot the incremented value is hard to find. Additionally, I can only get the values validated while trying to upload the sheet, which takes some time.
Ideas
Maybe the cells/sheet can be formatted so excel does not increment the value?
Code of Conduct

[X] I agree to follow this project's Code of Conduct

This is an excel feature. Simply hold Option or Alt while dragging and no incrementation takes place.

@KochTobi I also investigated this and agree, sadly there is no easy way to solve this within excel. Maybe I can update the documentation with a small warning box 🤔


Why are we not using withAuthenticator with gatsby?

The example for React / React Native is very simple using a HOC, but this repo has a more complex setup for Auth, why is that?
See: https://aws-amplify.github.io/docs/js/react#add-auth
Thanks!

If I add:
import Amplify from "aws-amplify"
import awsconfig from "./../aws-exports"
import { withAuthenticator } from "aws-amplify-react"
Amplify.configure(awsconfig)

Without any actual use, the build-html step of Gatsby crashes with a very weird error:
Error: /Users/alexander/Projects/bodycode/www/public/render-page.js:74355
      {}.DEBUG = namespaces;
        ^
  SyntaxError: Unexpected token .

Referring to render-page.js snipper:
/**
 * Save `namespaces`.
 *
 * @param {String} namespaces
 * @api private
 */

function save(namespaces) {
  if (null == namespaces) {
    // If you set a process.env field to null or undefined, it gets cast to the
    // string 'null' or 'undefined'. Just delete instead.
    delete {}.DEBUG;
  } else {
    {}.DEBUG = namespaces;
  }
}

Is there some kind of expected environment variable that is missing that is causing this?
I have no idea how to go about debugging this...

the bug I'm talking about here is worked-around using https://github.com/escaladesports/gatsby-plugin-prefetch-google-fonts/issues/18 and actually related to debug library used as dependency of gatsby.
So you can close the error part of this issue.
Still wondering why you didn't use the HOC though 😄

Hey, thanks for the issue! I'm not using withAuthenticator because many people want to have custom control over their auth, so I created this project. I would also suggest using withAuthenticator if it suits your needs though.

Also, I've updated the dependencies and upgraded the Gatsby project, this should work now. @aldegoeij

how would you access the users data after withAuthenticator() has been called and the Auth.currentAuthenticatedUser() has been called. lets say i was using withAuthenticator() to protect a profile page ... as soon as the user is authenticated the profile page will be accessible but the data from that user data is not able to be accessed before that profile page is displayed.


Improve configuration parsing

Currently there are two available options for loading configuration files.

the -c/--cfg option for providing the path of a single config file
the --cfgdir option for providing the path of a directory, from which GenHub will attempt to load all .yml files

The --cfgdir option is fine as is, but I propose the following additions and changes for other config loading options.

--cfglist option for providing a file with config files (one per line)
--cfgpath option for providing one or more directories in which to search for config files
--cfgfullpath option for indicating that value(s) provided by -c/--cfg option or --cfglist option are full file paths; by default, they are treated as relative paths and GenHub searches all directories specified by --cfgpath for these files

The option labels might need tweaking, but I think the functionality supports most/all conceivable use cases with a relatively simple interface.

Also to consider: config files that are installed pip install.

Use pkg_resources to load installed data

New plan:

-g|--genome: specify one or more genome configuration labels
-l|--genomelist: specify a list of genomes to process (no support for user-supplied lists)
-c|--cfgdir: specify one or more user-supplied directories in which to look for custom config files
genhub-genomes.py: list all genomes and genome lists


CSV Extension

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/124/


docs: fix "Pest Driven Laravel" link

Closing as resolved by https://github.com/pestphp/docs/pull/228 👍🏻


Yepph

What version of Hugo are you using (hugo version)?

$ hugo version

Does this issue reproduce with the latest release?

What version of Hugo are you using (hugo version)?

$ hugo version

Does this issue reproduce with the latest release?

Yes

$1000000

What version of Hugo are you using (hugo version)?

$ hugo version

Does this issue reproduce with the latest release?

Not at all


Dockerize tests

Here's the skeleton for dockerized tests for review tomorrow.
Things I'm explicitly seeking buy-in on. not married to existing implementation, but wanted to do something for sake of discussion:

TEST_ARGS pass-through options for docker/test.sh to test/bin/test.sh
Cache orthanc docker image. (45s on travis with no caching)
level of input validation appropriate. I'd prefer more extensive
WIP...

@gsfr Heads up

@ryansanford Per offline discussion, please minimize orthanc-config.json and rename test directory to tests to avoid bash keyword conflict.


license: Repository needs a LICENSE file

I somehow missed this before - but the repository is missing a LICENSE file. I took a quick look through the source code and did not find a license...
@andaag, would you mind adding one when you have a chance? Thank you :)

Added, sorry about the delay! Had some email filtering issues and github issues on public repos somehow slipped by me!

No worries - I just noticed that you added a license file :) Thank you for doing so!


New Example on how to configure this lib.

Any chance we can get a newer example application? A few things are not so clear, like how to use the ErrorView in phoenix etc...

@jherdman @doomspork Hey, yeah I mean an example app, showing how to setup the hex with great defaults that will work for most case scenarios.

how to handle errors
how to render relationships
how to do hypermedia
how to get the correct resource name

+1, would be very helpful to have an updated example app.  Especially for how to handle getting errors (changeset_view.ex, error_view.ex, etc) to properly show in the jsonapi spec format

@b4ugh Would very happily and quickly accept contributions!

Well, I'm struggling to figure out how to get them (the error views) to work, or else I would! 😂  But if/once I'm able to figure it out I'd be happy to lend a hand!

I've been thinking as of late that this lib should extract some of the
Phoenix-y concerns, which should also include some modules for converting
Ecto error changesets to responses. Hopefully I can find some time to
finish drafting a mega RFC soon. I'll try to post a gist of the code I'm
using for error changesets as soon as possible.
On Fri, Aug 7, 2020, 11:45 Dan Baugh<EMAIL_ADDRESS>wrote:

Well, I'm struggling to figure out how to get them (the error views) to
work, or else I would! 😂 But if/once I'm able to figure it out I'd be
happy to lend a hand!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jeregrine/jsonapi/issues/138#issuecomment-670581469,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAAZZCQBV7AJERGUA2P5E3R7QOSLANCNFSM4GA4VDHA
.

@b4ugh my changeset_view.ex looks like this https://gist.github.com/jherdman/d6c89166d4d427108629ec3d1618d199. I don't think we ought to pull this into the lib yet, I'm sure it can be tightened up (nor am I sure it belongs in this lib proper). Hopefully this gets you started.

@jherdman Looks pretty good to me!


C

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

VS Code Version:
OS Version:

Steps to Reproduce:

J

C program run then page is open launch. Json

Vah

/needsMoreInfo

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


masthead changes on list, create, detail

detail top: https://github.com/rancher/dashboard/pull/537
https://xd.adobe.com/view/6fa2a7f7-2bcf-4d5c-75de-9beb1a9b6fae-1993/screen/d37974cf-dd0a-4d3a-8983-12b0ef948dd3/detail

[ ] move namespace below h1, outside of detail top
[ ] create breadcrumbs
[ ] yaml | form toggle

Original Requirements discussed with @ibuildthecloud

ResourceName - More focus on the actual resource name
Breadcrumbs shouldn't be as dominant on the page and make it clearer that it goes back to list
Namespace - Instead of part of DetailTop, add it as part of header (i.e. masthead) as every resource has a name and is in a namespace
Switching beteen Yaml/Form - Ability to navigate between yaml/form for when viewing and editing a page. Note: buttons shouldn't exist if no custom form view exists.

Switching beteen Yaml/Form - Ability to navigate between yaml/form for when viewing and editing a page. Note: buttons shouldn't exist if no custom form view exists.

@tfiduccia  and I specifically removed this switch to the other editor thing and added separate "edit as..." actions to choose in advance because you're going to lose whatever you've already input when you click it.  There is not always a direct, or even necessarily 1 form:1 yaml mapping from one to the other to try and preserve what they've entered so far in the other view.

Updating the requirement to show the buttons only during view mode of a resource to avoid having to preserve the changes during create/edit.

Yeah, there should be no toggle for edit or create screens.

The component shown is a button group which typically operates like a radio, one option is always selected.  So it doesn't make sense on view (the action menu already has the links to edit), or it shouldn't be a button group.

Updating the requirement to show the buttons only during view mode of a resource to avoid having to preserve the changes during create/edit.

xd file updated to reflect this

@vincent99 why doesn't a button group make sense? one option is always selected, either yaml or form for viewing a detailed resource.

Oh, you're toggling "view the detail component" and "view as yaml"?  Not links to "edit as form" and "edit as yaml"?  I guess that works, but calling the detail page with no form components on it a form is odd.

I agree that calling a "Form" is weird for viewing a detail resource, but haven't come up with a better word yet.  YAML vs . Any ideas?

@mantis-toboggan-md We should make sure that these changes also work for the Namespace resource since we're moving Namespace into the masthead component. Ideally for when using  Namespace resource, it should say Project with the project name.

Friendly, Detail, Overview, Visual?
Only some resources are namespaced, projects are optional, and you'll have similar primary relationships to show in global resources soon.. so something like:

  Namespace: <nuxt-link ...>{{namespace}}</nuxt-link>

  Project:
  <nuxt-link v-if="project" ...>{{project.nameDisplay}}</nuxt-link>
  (None)

Instead of Form, let's try Overview @mantis-toboggan-md

Cluster is showing id instead of nameDisplay
YAML/Overview states are backwards; Blue should be the one that you're currently on (use ButtonGroup component)
I don't have any particular logic but feel like it should be Overview/YAML, not YAML/Overview.
Created (and any other dates that go in the header, removed?) should be a LiveDate

@mantis-toboggan-md Let's do a separate issue/PR to update all the DetailTops in all resources to remove the Namespace in detailTop.
As a side note, we have talked about moving Description into mastHead as well, but haven't filed an issue.
Switching the order of Overview/YAML makes sense to me.
I'll figure out what we want the common items to be in detailTop. I'll do a review of detailTop across all the resources to determine what the standard items should be in it.

There are some small pixel changes I want to request, but I'll file a separate issue for them.
Generic

[ ] Cluster is showing id instead of nameDisplay in the breadcrumbs

[ ] Add in Description as part of masthead. Basically, only show the description under the Namespace section using font in a lighter color, if there is a description. Otherwise, show nothing.

Edit Pages

[ ] Namespace is showing up in masthead when creating and editing resources in the form input and the yaml input. This should be hidden as it's an input option when you're editing/creating the resource.
[ ] From the multi-action menu, the Edit as YAML and Clone as YAML takes me to edit the form version instead of YAML.
[ ] For Create <ResourceType>, can we enable so that the breadcrumbs link works for going back to the list of resources?

Remove the link on the <ResourceType>:

[ ] Edit <ResourceType>: <ResourceName>
[ ] Create <ResourceType
[ ] Clone from <Resourec Type>

Detail Pages

[ ] YAML/Overview states are backwards; Blue should be the one that you're currently on (use ButtonGroup component)
[ ] Reverse the order of the buttons. Overview first and then YAML.

Let me know if you want me to track these as a separate issue, but seems to make sense as part of here since it's part of the fact that we're moving this info into masthead.

[ ] Remove Namespace from DetailTop for all resources.
[ ] Remove Description from DetailTop for all resources.

[ ] Can we remove the padding/spacing next to Namespace so that it lines up with the resource?


Using the keyboard shortcut to search for method seNders in the Coder can cause the image to freeze

This happens if arguments are also selected when highlighting the method name.
If the mouse is simply positioned in the method name, it works correctly.

fixed and very well covered with examples!


File format saving problem

File format saving problem
Hi, we have a question about saving files. When we choose Ascll_ply or binary_ply, the saved file format is .bin format, we want to save it as .ply format. Maybe because we may not really understand the meaning of the paper, so we have two questions to ask: First, whether the point cloud can be saved after multi-view registration, and second, whether the point cloud after multi-view registration can be saved .ply format?

Hi,
Yes the data can be saved to .ply format.
During recording the .bin file is treated as a temporary buffer by the client.
Once the recording is finished, the clients send the recorded frames to the server, which subsequently saves them as .ply files in the directory specified in the main window of the server app.
Let me know if that answers your questions.
Thanks,
Marek

Hi Marek,
When Savingframes, Clients  read the frame which is recorded (which has points and colors). However, when Clients sends to sever, they send points + colors+ m_vLastFrameBody. Thus, the Skeleton will not synchronize with the points and colors right?
To solve the problem, maybe in WriteFrame, we also need to write the Bodies information, then read it and send to Sever. Am I right?
Thanks,
Chien

Hi Chien,
That's a good point. While in the current version the skeleton data is not saved during sequence recording, this might be confusing to someone who wants to add that option.
Thanks,
Marek


interop_testing_te9 branch not working because of missing thirdy_party/telink_sdk

interop_testing_te9 branch not working because of missing thirdy_party/telink_sdk
Can fix the link ?

@q7777777hk Are you referring to this link? https://github.com/SiliconLabs/matter/tree/release_0.4.0/third_party/telink_sdk
Please indicate the steps you followed to initialize your local repo and any other steps required to reproduce this issue.

When you check the telink_sdk in https://github.com/SiliconLabs/matter/tree/interop_testing_te9/third_party/telink_sdk,
you will see 404
After "git clone -b interop_testing_te9 --recursive https://github.com/SiliconLabs/matter.git"
Run "git submodule update --init --recursive" will cause fail
Then cannot run "source third_party/connectedhomeip/scripts/activate.sh"
And cannot build any project

Please note that the TE9 branch is quite old and not up to date at all. Is there a specific reason why you are trying to use this older branch vs the newest release (i.e.: 0.4.0)?

Considering the TE9 branch will not be supported going forward and most likely removed once Matter 1.0 is released, I recommend trying out the latest release, 0.4.0. If you need further assistance, please open a ticket on the community here.


Fails when source code isn't found

It seems your latest changes using stack_data cause a crash when the source code isn't found, e.g:
import friendly_traceback
import traceback
try:
  exec("1/0")
except:
  try:
    friendly_traceback.explain_traceback()
  except:
    traceback.print_exc()

Output:
Fatal error - aborting
Please report this issue.
Traceback (most recent call last):
  File "main.py", line 4, in <module>
    exec("1/0")
  File "<string>", line 1, in <module>
ZeroDivisionError: division by zero

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/virtualenvs/python3/lib/python3.8/site-packages/friendly_traceback/core.py", line 373, in __init__
    self.tb_data = TracebackData(etype, value, tb)
  File "/opt/virtualenvs/python3/lib/python3.8/site-packages/friendly_traceback/core.py", line 124, in __init__
    self.locate_error()
  File "/opt/virtualenvs/python3/lib/python3.8/site-packages/friendly_traceback/core.py", line 272, in locate_error
    node_info = self.records[-1].node_info  # noqa
  File "/opt/virtualenvs/python3/lib/python3.8/site-packages/stack_data/utils.py", line 145, in cached_property_wrapper
    value = obj.__dict__[self.func.__name__] = self.func(obj)
  File "/opt/virtualenvs/python3/lib/python3.8/site-packages/friendly_traceback/frame_info.py", line 210, in node_info
    return None, (0, len(self.current_line.text)), self.current_line.text
  File "/opt/virtualenvs/python3/lib/python3.8/site-packages/stack_data/utils.py", line 145, in cached_property_wrapper
    value = obj.__dict__[self.func.__name__] = self.func(obj)
  File "/opt/virtualenvs/python3/lib/python3.8/site-packages/friendly_traceback/frame_info.py", line 236, in current_line
    return only(
  File "/opt/virtualenvs/python3/lib/python3.8/site-packages/executing/executing.py", line 164, in only
    raise NotOneValueFound('Expected one value, found 0')
executing.executing.NotOneValueFound: Expected one value, found 0

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "main.py", line 7, in <module>
    friendly_traceback.explain_traceback()
  File "/opt/virtualenvs/python3/lib/python3.8/site-packages/friendly_traceback/__init__.py", line 88, in explain_traceback
    session.explain_traceback(redirect=redirect)
  File "/opt/virtualenvs/python3/lib/python3.8/site-packages/friendly_traceback/config.py", line 197, in explain_traceback
    self.exception_hook(etype, value, tb, redirect=redirect)
  File "/opt/virtualenvs/python3/lib/python3.8/site-packages/friendly_traceback/config.py", line 226, in exception_hook
    info = self.get_traceback_info(etype, value, tb)
  File "/opt/virtualenvs/python3/lib/python3.8/site-packages/friendly_traceback/config.py", line 272, in get_traceback_info
    self.friendly_info.append(core.FriendlyTraceback(etype, value, tb))
  File "/opt/virtualenvs/python3/lib/python3.8/site-packages/friendly_traceback/core.py", line 376, in __init__
    debug_helper.handle_internal_error(e)
  File "/opt/virtualenvs/python3/lib/python3.8/site-packages/friendly_traceback/debug_helper.py", line 75, in handle_internal_error
    sys.exit()
SystemExit

The essential part:
  File "/opt/virtualenvs/python3/lib/python3.8/site-packages/friendly_traceback/frame_info.py", line 236, in current_line
    return only(
  File "/opt/virtualenvs/python3/lib/python3.8/site-packages/executing/executing.py", line 164, in only
    raise NotOneValueFound('Expected one value, found 0')
executing.executing.NotOneValueFound: Expected one value, found 0

I'm guessing it breaks trying to find a matching line in an empty list.
Demo link<EMAIL_ADDRESS>Does the repo have tests for missing source code?

I thought it did; I'll check. Actually, I did find that I had to remove a test (circular import) as it was failing when run with all the other tests.
Thanks for the report.
BTW, I'd really welcome your help in figuring out how to do highlight when a node is effectively spread over multiple lines. I see that IPython handles that, but my code does not.

IPython leaves it to Pygments and stack_data.style_with_executing_node:
https://github.com/ipython/ipython/blob/8520f3063ca36655b5febbbd18bf55e59cb2cbb5/IPython/core/ultratb.py#L830
Here's how stack_data.Formatter does it without Pygments (when there's no colour):
https://github.com/alexmojaki/stack_data/blob/637e10e59daae92f5f3bafc97aedbb119c6151e7/stack_data/formatting.py#L181-L188
In particular it uses Line.executing_node_ranges.

Actually, I just checked with an older version and the bug was always there. I thought I had tested that before, but obviously did not.

This particular case (using exec) should be fixed now. I need to add a unit test and probably make it more robust in case someone uses compile() followed by exec() with a filename that is of the form <...> and whose source is not saved.
Would you mind testing the new version on pypi?

Very nice! Here are my thoughts:

The default red background looks great, much better than the yellow in IPython, for which I take the blame. It's also weird that the traceback in IPython isn't syntax highlighted.
Note that IPython will show values from pure_eval with %xmode verbose
Typo in "so as to no overwhelm": *not
Regarding highlighting imports, this is just one of many kinds of node that executing doesn't highlight, so it's a stretch to say that you're ensuring a node is highlighted. Hopefully 3.11 will allow changing this.
Regarding the highlighting of indentation in multiple lines: I don't know if your version is an improvement. I think the ideal would be to only skip the common leading indentation in the same style as dedent, so the 12 and ( are part of a common highlighted block but it still looks nice and contained.

Thanks Alex. I wrote a few lines at the top of the blogpost as an update, mentioning %xmode verbose and the possibility of using a different highlighting strategy - which I will try to do soon.  I also fixed the typo you mentioned.

Ok, I managed to do the highlight as you suggested (I think), and I do find that it looks the best.
IPython's way (highlighting to the beginning of the line):

My previous way of doing the highlight:

The new way:

The way I have done it is to find the minimum indentation of the 2nd and subsequent lines, and use that as the column from which to highlight. This will look "nice" if the code is indented properly;
however, it might not be as good if the code is not indented so as to follow the natural block structure.

Do you have examples where it doesn't look good?
Either way it'd be great if you could contribute this to stack_data, then IPython and others could use it too.

Do you have examples where it doesn't look good?

No, I don't. I was mostly thinking of cases where the highlighting of the first line started before what would be the code block that followed it ... but I made another version to take care of this.
As for contributing to stack_data, I could have a look, but I don't know if the approach I use would be easily doable.
Given the following lines that need to be highlighted (taken from the previous pictures)
def bar():
    return foo(0) + foo(
        12
    ) + foo(2)

I first use stack_data in friendly_traceback to produce the following set of lines:
    5: def bar():
 -->6:    return foo(0) + foo(
                          ^^^^
    7:        12
              ^^
    8:    ) + foo(2)
          ^

while keeping track of the indentation used for each added line containing carets (^).
If there is more than one such line, I look for the minimum indentation, and parse the output
line by line to make the required adjustments so that the carets are aligned vertically,
ignoring the first line which is assumed to remain unchanged.
    5: def bar():
 -->6:    return foo(0) + foo(
                          ^^^^
    7:        12
          ^^^^^^
    8:    ) + foo(2)
          ^

I probably could implement something like this for stack_data.
However, I do not know how well this approach would work when using pygments with stack_data.
Friendly takes the output from friendly-traceback and highlights the result line by line.
The problem is that the new input (with line numbers included) is not valid Python syntax.

If a line needs to be highlighted, I do my own tokenization and use the Text class from Rich to highlight each token in a style that is roughly similar to what Pygments does.
However, this line by line highlighting can fail spectacularly when encountering multi-line
triple quoted strings.  I prevent problems by first identifying if such strings are present.
If so, I do not bother with tokenization and, other then the line numbers, I consider the
output to be either "code" or "highlighted code".  Here's an example:

As you can see, the syntax highlighting is not consistent in the different parts - but the red background is treated correctly and a casual reader is likely not going to notice the difference
in the rest of the code.
The whole thing is an inelegant hack, but I consider the final result to be good enough for me, at least for now.
If the syntax.stylize() method mentioned in https://github.com/Textualize/rich/issues/1829 is ever implemented, then, perhaps something better could be done.  Given that I take the output from friendly-traceback that contain line numbers, there might still be problems with triple quoted strings yielding line numbers highlighted in green such as on line 7 of the example below, but that would be less problematic.

From what I can see from IPython, it does not do syntax coloring of the output

I did that initially, but I liked the full syntax colored version better - when it works!
===
Anyway, I will try to have a look at stack_data (hopefully this week) and see if I can come up with something acceptable.

Friendly takes the output from friendly-traceback and highlights the result line by line.

Well there's your problem. IMHO friendly-traceback should be similar to stack_data in that its primary responsibility should be to provide structured information that other code can use effectively however it wants. It can still include helpers for formatting to make things easier for users, but friendly should have access to more than a formatted string which it then has to parse and reformat.

From what I can see from IPython, it does not do syntax coloring of the output

I don't know what's happening in your system, but I can see that it's bolding the keywords def and return, and in your blog post I can see that Jupyter has syntax highlighting in its tracebacks. Here's a screenshot from IPython in my system:

Here's how that happens:

IPython.core.ultratb._format_traceback_lines calls stack_line.render(pygmented=has_colors) for each line, then adds its own line numbers, arrows etc. around that.
stack_data.core.Line.render calls self.frame_info._pygmented_scope_lines which returns a list of cached strings representing rendered lines, and picks the correct one.
stack_data.core.FrameInfo._pygmented_scope_lines constructs the appropriate ranges based on executing and passes them to _pygmented_with_ranges(formatter, code, ranges), from which it extracts the relevant lines.
stack_data.utils._pygmented_with_ranges calls pygments.highlight(code, lexer, formatter).splitlines(). So pygments receives a full syntactically valid code block and it can deal with multiline strings properly, but IPython can still work with individual lines.

Friendly takes the output from friendly-traceback and highlights the result line by line.

Well there's your problem. IMHO friendly-traceback should be similar to stack_data in that its primary responsibility should be to provide structured information that other code can use effectively however it wants. It can still include helpers for formatting to make things easier for users, but friendly should have access to more than a formatted string which it then has to parse and reformat.

I completely agree; I should have thought of this before, when I first struggled to "unparse" the information given by friendly_traceback so that it could be properly shown by friendly within IDLE.
I need to have friendly_traceback provide its own formatted output and to also provide the raw information in a structure way (code, line_numbers including the one to flag as containing the error, location/range of markers) so that other programs can make use of it in their own way. This is what I already do for all the other information provided by friendly_traceback, which you know since you already use some of them selectively for futurecoder.
This will likely mean that I'll have to reimplement my own version of what Rich currently does for me "out of the box".  Since I already use stack_data, perhaps I can bypass Rich for this part of the information provided by friendly.
Also, thanks for the added explanation of the logical steps followed for IPython formatting. This will  be a useful guide when reading the code, and seeing how much information I can reuse from stack_data.
However, my next order of business will be to see if I can modify stack_data to highlight multiple lines following your suggestion. If I can do this (perhaps later today if I can do enough of my paid work first), I'll submit a pull request so that you can decide if it is worthwhile or not.