Fix Eigen::Vector3d variable definition

Description
Parent Bug Report Issue:

https://github.com/tier4/scenario_simulator_v2/issues/1302

Reference to fix:

https://eigen.tuxfamily.org/dox/TopicPitfalls.html

In short: do not use the auto keywords with Eigen's expressions, unless you are 100% sure about what you are doing. In particular, do not use the auto keyword as a replacement for a Matrix<> type.

Required change
From
const auto relative_position =

To
const Eigen::Vector3d relative_position =

This should fix it.
Link to breaking PR

https://github.com/tier4/scenario_simulator_v2/pull/1226#discussion_r1666832342_

@MertClk Can you provide information on the operating environment, such as CPU model number/compiler?
We found that this PR implementation changes the behavior of the existing scenario when we check the behavior in the internal regression test environment of TIER IV.
Perhaps the cause of #1312 is a processing or CPU architecture dependent bug due to the Expression Template and the associated computation delay.
Changing the auto type to Eigen::Vector3d seems to change the behavior in some scenarios, and a detailed investigation of the cause and confirmation of the behavior is required to accept this PR.
All computers used in TIER IV are Intel CPUs, gcc compiler and release builds.

@hakuturu583 Below you can find my system information.

Ubuntu 22.04.4 LTS 64-bit
Intel Core i9-13900HX
gcc version 11.4.0
Build Type: RelWithDebInfo

Thank you very much!
I had thought you were using an AMD CPU.
Thanks for the information.

@MertClk What eigen version are you using?
Did you install eigen via apt or build eigen by yourself?

@hakuturu583 thank you so much for your support on this issue! I'm using eigen version 3.4.0 and installed via apt.

I use same version... :thinking:
I am currently looking for the cause of the problem considering multiple possibilities, but we are unable to reproduce the problem on our end and fix it quickly.
I apologize for this.

It is unclear if it is the model number of the CPU or what is causing the problem,
const auto relative_position =

and
const Eigen::Vector3d relative_position =

There may be a slight difference in calculation results between ``bash const Eigen::Vector3d relative_position = ````.
We will now verify whether there is actually a difference or not by branching out to scenario_simulator_v2.

@hakuturu583
I asked my colleagues who has the same issue and below you can find their CPU models.

Ryzen 7 6850U
Intel i7 12700h
Intel(R) Core(TM) i9-11900H
Intel(R) Core(TM) i7-11800H

I would like to share with you a very important observation.
As a quick reminder, I had this problem re-producible on my machine. The solution from @MertClk is solving it.
I am using Intel(R) Core(TM) i9-11900H and I am always using building with RelWithDebInfo.
But I noticed in the reply from @hakuturu583 -san :

All computers used in TIER IV are Intel CPUs, gcc compiler and release builds.

So I have tested scenario simulation (branch RJD-736/autoware_msgs_support without Mert's PR) with two builds

with -DCMAKE_BUILD_TYPE=RelWithDebInfo

The issue is still occurring and the vehicle is not moving.

with -DCMAKE_BUILD_TYPE=Release

The issue is still NOT occurring and the behavior looks normal.

Initially speaking, it looks like the difference in optimization level turns out to a different generated code to an extent that there is difference in the behavior producing such issue.
I hope this observation would be useful for coming to a final resolution for this issue.

@ahmeddesokyebrahim Thank you very much!
It is likely that the optimization level is affecting the Expression Template, resulting in incorrect results when calculations are performed with a delay.
The cause can be narrowed down significantly.

Now, we are investigating why this problem happens.
It is necessary for checking the regression in our regression test environment is a valid behavior or not.
Sorry for taking time.

Currently, we are writing minimal test code for this problem and verifying its operation with various build options.
The behavior is complex, with calculation results changing depending on factors such as the presence or absence of OpenMP, and we are taking time to analyze the problem.
For now, we would appreciate if you could use scenario_simulator_v2 with a Release build.


Undefined method path on Hawkular provider

After rebasing with master it has appeared some errors like this:
ERROR -- : MIQ(MiddlewareServer#first_and_last_capture) Hawkular service unavailable: undefined method `path' for #<#Class:0x007f18fa7f3c20:0x007f18fa7f39a0>
That escaped to the spec coverage.

@miq-bot assign @lucasponce

@miq-bot add_label providers/hawkular

@miq-bot add_label bug

@pilhuhn @abonas @Jiri-Kremser small fix to make current code compatible with v022 Hawkular Gem.
Please, could you take a look ?
Probably with v030 I will have to refactor some of the use of the API.
This patch is to make the code works fine with the current v022 version.

@lucasponce What type is #<#Class:0x  - is this a class that lives inside the hawkular client gem?

No, the Class is just a intermediate struct hash to pass some params into the gem api.
As there is some minor gap between fields name between the MiQ Hawkular model and the gem API.
It is not a big deal, I think we can address those in following refinements of gem + MiQ.


Replace Socket.io with Primus

Hi, i would like to suggest replacing Socket.io with Primus, which is "a simple abstraction around real-time frameworks" and "allows you to easily switch between different frameworks without any code changes". It supports Engine.IO, WebSockets, BrowserChannel, SockJS and Socket.IO as transports or "transformers" as they call them.
Advantages

Effortless switching between real-time frameworks by changing one single line of code. No more API rewrites needed when your project requirements change, the framework get abandoned or simply breaks down.
Build-in reconnect, it just works. The reconnect is controlled by an randomized exponential backoff algorithm to reduce server stress.
Offline detection, Primus is smart enough to detect when a users drop their internet connection (switching WIFI points/cell towers for example) and reconnects when they are back online.
Automatically encodes and decodes messages using custom parsers. Can be easily switched for binary encoding for example.
A clean and stream compatible interface for the client and server. You can just stream#pipe data around. In addition to that, the client works on Node.js as well, write once, run it everywhere.
Fixes various of bugs in the supported frameworks and additions stability patches to improve real-time communication.
Comes with an amazing plugin interface to keep the core library as fast and lean as possible while still allowing the server and the client to be extended.
Last but not least, Primus is build with love, passion and dedication to the real-time web.

Main motivation
The main motivation to ask you to switch to Primus is that i want to use SockJS instead of Socket.io as i don't trust too much on the latter.
There are very solid arguments from sockjs-tornado developer.
And from Primus developer:

There are small bugs in Engine.IO that are causing our tests to fail. I've submitted patches for these bugs, but they have been reject for silly reasons. The bug causes closed connections to say open. If you're experiencing this you can apply this patch.

(Engine.IO and Socket.IO are developed by the same guy and seems that Socket.IO will use Engine.IO internally in the coming versions.)
So based on all those arguments i think that Sails will benefit too from having a more solid transport and it would be great to use Primus to be able to select your preferred transport and/or take advantage of their optimizations.
Yes, i'm willing to help, but can't be done on my own as i don't know lots of things regarding the internals of Sails.
Cheers.

+1

@alejandroiglesias @andyhu Hey guys! So I talked to @3rdeden about this almost a year ago when we were both at jsconf.it and I decided to focus on socket.io 1.0 first if that was available, since @rauchg has done such an incredible job there, and particularly w/ engine.io.
Socket.io v1.0 support is included in Sails v0.11 (currently available via sudo npm install -g sails@beta)  The sockets hook is also now implemented as a separate repo so making an override for it is as simple as releasing the hook on npm and instructing others to run, e.g. npm install sails-hook-sockets-primus (and setting the appropriate properties in your hook-- see new docs on the subject in the v0.11 branch of sails-docs)

updated roadmap: https://github.com/balderdashy/sails/commit/9ee19516e54fdf330c760cce1e0aa1d998be234a

Thanks for the reply. I changed my mind a bit on voting this. Since I saw a benchmark amount all common libraries like socket.io, socksjs, engine.io, Primus etc..(Sorry I couldn't find the link again now). with socket.io it performs not too bad compares to others  (except engine.io which is a lower level thing behind socket.io) in term of maximum connection concurrency, CPU & memory utilization etc.. And since Primus tries to wrap everything around so it a bit more resources. Also I saw in the change log of Socket.io 1.0, some of the long existed memory leak issues have been fixed which one of my friends said that it's the reason stopped them from using it on a non-trivial real communication site. So I did rethink about what benefit it will bring us when change it to Primus, since socket.io covers almost all possible transportation layers.


'next' command not stepping over a line?

Apologies if I'm not understanding something, but it looks like 'next' isn't working right... it's stepping into Rails' association functions. I'm also having a similar problem with the 'debugger' gem:
'next' in byebug:
2.0.0-p247 :017 > reload!; Course.new.debuggertest
Reloading...
[1, 10] in /home/httpd/vhosts/site.org/app/models/course.rb
    1: class Course < ActiveRecord::Base
    2:   has_many :subjects, :class_name => 'CourseCurricularSubject', :foreign_key => :course_id, :dependent => :destroy, :autosave => true
    3:
    4:   def debuggertest
    5:     byebug
=>  6:     puts 'Line 2'
    7:     subject = subjects.first
    8:     puts 'Line 4'
    9:   end
   10: end
(byebug) next
Line 2
[1, 10] in /home/httpd/vhosts/site.org/app/models/course.rb
    1: class Course < ActiveRecord::Base
    2:   has_many :subjects, :class_name => 'CourseCurricularSubject', :foreign_key => :course_id, :dependent => :destroy, :autosave => true
    3:
    4:   def debuggertest
    5:     byebug
    6:     puts 'Line 2'
=>  7:     subject = subjects.first
    8:     puts 'Line 4'
    9:   end
   10: end
(byebug) next
[333, 342] in<EMAIL_ADDRESS>   333:       def load_target
   334:         if find_target?
   335:           @target = merge_target_lists(find_target, target)
   336:         end
   337:
=> 338:         loaded!
   339:         target
   340:       end
   341:
   342:       def add_to_target(record)
(byebug)

'step' in byebug:
2.0.0-p247 :001 > reload!; Course.new.debuggertest
Reloading...
[1, 10] in /home/httpd/vhosts/site.org/app/models/course.rb
    1: class Course < ActiveRecord::Base
    2:   has_many :subjects, :class_name => 'CourseCurricularSubject', :foreign_key => :course_id, :dependent => :destroy, :autosave => true
    3:
    4:   def debuggertest
    5:     byebug
=>  6:     puts 'Line 2'
    7:     subject = subjects.first
    8:     puts 'Line 4'
    9:   end
   10: end
(byebug) step
Line 2
[1, 10] in /home/httpd/vhosts/site.org/app/models/course.rb
    1: class Course < ActiveRecord::Base
    2:   has_many :subjects, :class_name => 'CourseCurricularSubject', :foreign_key => :course_id, :dependent => :destroy, :autosave => true
    3:
    4:   def debuggertest
    5:     byebug
    6:     puts 'Line 2'
=>  7:     subject = subjects.first
    8:     puts 'Line 4'
    9:   end
   10: end
(byebug) step
[39, 48] in<EMAIL_ADDRESS>   39:       end
   40:
   41:       def define_readers
   42:         name = self.name
   43:         mixin.redefine_method(name) do |*params|
=> 44:           association(name).reader(*params)
   45:         end
   46:       end
   47:
   48:       def define_writers
(byebug)

'next' in debugger:
2.0.0-p247 :002 > reload!; Course.new.debuggertest
Reloading...
/home/httpd/vhosts/site.org/app/models/course.rb:7
puts 'Line 2'

[2, 11] in /home/httpd/vhosts/site.org/app/models/course.rb
   2    has_many :subjects, :class_name => 'CourseCurricularSubject', :foreign_key => :course_id, :dependent => :destroy, :autosave => true
   3
   4    def debuggertest
   5      require 'debugger'
   6      binding.debugger
=> 7      puts 'Line 2'
   8      subject = subjects.first
   9      puts 'Line 4'
   10    end
   11  end
(rdb:1) next
Line 2
/home/httpd/vhosts/site.org/app/models/course.rb:8
subject = subjects.first

[3, 12] in /home/httpd/vhosts/site.org/app/models/course.rb
   3
   4    def debuggertest
   5      require 'debugger'
   6      binding.debugger
   7      puts 'Line 2'
=> 8      subject = subjects.first
   9      puts 'Line 4'
   10    end
   11  end
(rdb:1) next
/home/user/.rvm/gems/ruby-2.0.0-p247@rails32/gems/activerecord-3.2.13/lib/active_record/associations/builder/association.rb:44
association(name).reader(*params)

[39, 48] in<EMAIL_ADDRESS>   39        end
   40
   41        def define_readers
   42          name = self.name
   43          mixin.redefine_method(name) do |*params|
=> 44            association(name).reader(*params)
   45          end
   46        end
   47
   48        def define_writers
(rdb:1)

'step' in debugger:
2.0.0-p247 :001 > reload!; Course.new.debuggertest
Reloading...
/home/httpd/vhosts/site.org/app/models/course.rb:7
puts 'Line 2'

[2, 11] in /home/httpd/vhosts/site.org/app/models/course.rb
   2    has_many :subjects, :class_name => 'CourseCurricularSubject', :foreign_key => :course_id, :dependent => :destroy, :autosave => true
   3
   4    def debuggertest
   5      require 'debugger'
   6      binding.debugger
=> 7      puts 'Line 2'
   8      subject = subjects.first
   9      puts 'Line 4'
   10    end
   11  end
(rdb:1) step
Line 2
/home/httpd/vhosts/site.org/app/models/course.rb:8
subject = subjects.first

[3, 12] in /home/httpd/vhosts/site.org/app/models/course.rb
   3
   4    def debuggertest
   5      require 'debugger'
   6      binding.debugger
   7      puts 'Line 2'
=> 8      subject = subjects.first
   9      puts 'Line 4'
   10    end
   11  end
(rdb:1) step
/home/user/.rvm/gems/ruby-2.0.0-p247@rails32/gems/activerecord-3.2.13/lib/active_record/associations/builder/association.rb:44
association(name).reader(*params)

[39, 48] in<EMAIL_ADDRESS>   39        end
   40
   41        def define_readers
   42          name = self.name
   43          mixin.redefine_method(name) do |*params|
=> 44            association(name).reader(*params)
   45          end
   46        end
   47
   48        def define_writers
(rdb:1)

Referencing #85

I'm getting inconsistent behavior with 'next' with ruby 2.1.5p273 and byebug/byebug-pry master branches. Sometimes it skips to the next line, sometimes it goes elsewhere. Same with ruby 2.1.1p76.
Does anyone have a known working combination of byebug and ruby 2.1?

That is very weird, the only thing I can think of is that Rails 3.0.10 included code affected by #103
Could you create a sample repo reproducing the problem? Thanks.

I'm seeing this problem again with rails <IP_ADDRESS> and ruby 2.6.2

I'm also seeing this problem again with Rails 5.0.2 and ruby 2.6.3. 'Run to cursor' works fine if you position the cursor over the next line, but the 'next' command just does a 'continue'.

Also seeing this, surprised to find that I'm not the crazy one

I am also seeing a problem in Ruby 2.6.3--at times the 'next' command will behave like 'continue'.  If I roll back to Ruby 2.5.3 (and keep everything else the same) all seems to be fine. Here's my Gemfile.lock.
Just to keep the issue in an actual state with more details.
I've stuck with the same issue. I have byebug, pry and pry-byebug in my Gemfile (no bootsnap, spring, etc.). Rails 5.2.2. And ruby 2.6.3p62 (docker image - https://hub.docker.com/_/ruby/ ruby:2.6.3-stretch ). Downgrading to 2.5.3 helps. I've checked on two other machines. It is reproducible. If necessary - I can prepare a dummy app.

Seeing a same issue with ruby 2.6.3 and byebug 11.0.1, and rails 5.2.3
When I use next, it doesn't go to the next line. It seems to just jump to a random spot

I'm sorry you're all having this issue. If I can get a repro, I'll have a look at it.
These bugs are most of the times issues in the underlying TracePoint API. One thing you can try is giving ruby 2.7.0-preview1 a try, maybe those bugs are fixed there.

@deivid-rodriguez I couldn't reproduce this problem in my code using byebug, but I have a very similar problem in debase with ruby 2.6 (see https://github.com/denofevil/debase/issues/75) and 2.7.0-preview1 does seem to fix the problem there.

Wanted to echo @DeegC 's comment. We are also seeing this on ruby ruby 2.6.3p62; sometimes n will work, but sometimes it behaves like a continue. I'm currently reproducing the issue in an RSpec test.

ruby 2.6.3p62 (2019-04-16 revision 67580)
rspec-core (3.8.2)
pry-byebug (3.7.0)

byebug (~> 11.0)
pry (~> 0.10)

I guess it's clear that there was clearly an issue with byebug on ruby-2.6.3. However, upgrading the ruby version to 2.6.5 fixed it for me.

That is great to know that 2.6.5 fixes it, thanks @prashantvithani !

I can confirm that 2.6.5 fixes this, and that the issue still exists in ruby 2.5.7p206

Ruby 2.7.1, byebug 11.1.2, Rails <IP_ADDRESS> -> Still having the same issue

Please, post reproduction instructions as part of a separate issue if you want this looked at. Thanks.

I cannot reliably reproduce a setup. Sometimes it happens, sometimes it doesn't. When it does it seems to consistently happen on the same line. Currently experiencing this with Ruby 2.7.1p92, rails (<IP_ADDRESS>), byebug (11.1.3), and pry-byebug (3.9.0). I'll hit a byebug breakpoint and start stepping with n or s. At some point it just decides to continue instead of advancing. If I move the breakpoint lower and try again it will stop at the new spot, as expected, and I can maybe advance a few more steps again but eventually it will just decide to continue on a n or s command.

A coworker of mine that was also experiencing this said he got around it by using c <next_line_no> to keep stepping in or over when n or s would kick him out

This appears to be related to https://github.com/ruby/ruby/commit/3e02cd518fbe4d91c2aca7fbc3c5aafa387d3cb7 and https://github.com/deivid-rodriguez/byebug/issues/719 with Ruby 2.7.1 and appears to be fixed in upstream Ruby (upcoming version 2.7.2)

next is not jumping to next line .
$ ruby -v                                                         [11:33:22]
ruby 3.0.1p64 (2021-04-05 revision 0fb782ee38) [x86_64-darwin19]


VarSymbol.adr is required for flow analysis in Netbeans

The adr field has to be set for the new VarSymbol. The field should be there in every supported Java version, it is unchanged for 13 years.
This is a potential fix for #2612 .

great work, thank you!

@rzwitserloot @rspilker time to make a new release?

It is part of the last edge release, can you give it a try?

Yes, this works for me. Time for a stable release.


DOCS-266 - View Connections release note

Purpose of this pull request
This pull request adds a release note for the View Connections role capability.
Select the type of change

[ ] Minor Changes - Typos, formatting, slight revisions
[ ] Update Content - Revisions, updating sections
[x] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - .clabot, version updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

Ticket (if applicable)
DOCS-266

@jschwegler-sumo, could you review the release note?

Thanks, @kimsauce!


Cancel, confirm, delete buttons in create flow

Cancel doesn't cancel everything in some cases

Edit Quiz -> when a new question is added and then cancelled then the new question is still there -> talk in group if this is okay or if it needs to be changed

Could make a pop-up when cancelling out of Edit Quiz -> that remidns the user that if the user has created any questions, then they need to delete them if they don't wish them to be there before exiting

slet cancel knapperne


cmd/go: "connection refused" from git2.likeit.cn

What version of Go are you using (go version)?

go version go1.14 linux/amd64

Does this issue reproduce with the latest release?
Yes. Using the latest release.
What operating system and processor architecture are you using (go env)?
go env Output
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/xrfang/.cache/go-build"
GOENV="/home/xrfang/.config/go/env"
GOEXE=""
GOFLAGS="-insecure"
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE="git2.likeit.cn"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/xrfang/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/xrfang/git/like2api/src/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build997224249=/tmp/go-build -gno-record-gcc-switches"

What did you do?

What did you expect to see?
Expect GO to download dependencies.
What did you see instead?

go: finding module for package git2.likeit.cn/go/audit
api_log.go:6:2: cannot find module providing package git2.likeit.cn/go/audit: module git2.likeit.cn/go/audit: git ls-remote -q origin in /home/xrfang/go/pkg/mod/cache/vcs/4a99938e270e3fc121e6cd17b568b994c52f92ae31f54fc644142689f6f2d8b7: exit status 128:
	fatal: unable to access 'https://git2.likeit.cn/:go/audit.git/': Failed to connect to git2.likeit.cn port 443: connection refused

i.e. the go module system insist on using HTTPS.    As seen in the go env output above, the GOINSECURE variable is set to git2.likeit.cn.

This looks like a server issue. It appears that the server at git2.likeit.cn is returning go-import metadata pointing to the wrong repository URL.
Please verify that the server response follows the protocol described in https://tip.golang.org/cmd/go/#hdr-Remote_import_paths. (You can check the server response directly by running curl -sL https://git2.likeit.cn/go/audit?go-get=1.)

The server does NOT has https, but http returned 200:
$ curl -vsL https://git2.likeit.cn/go/audit?go-get=1

Trying <IP_ADDRESS>:443...
TCP_NODELAY set
connect to <IP_ADDRESS> port 443 failed: 拒绝连接
Failed to connect to git2.likeit.cn port 443: 拒绝连接
Closing connection 0

$ curl -vsL http://git2.likeit.cn/go/audit?go-get=1

Trying <IP_ADDRESS>:80...
TCP_NODELAY set
Connected to git2.likeit.cn (<IP_ADDRESS>) port 80 (#0)

GET /go/audit?go-get=1 HTTP/1.1
Host: git2.likeit.cn
User-Agent: curl/7.65.3
Accept: /

Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Content-Type: text/html
< Set-Cookie: lang=en-US; Path=/; Max-Age=2147483647
< Set-Cookie: i_like_gitea=7a9321142eb6abbc; Path=/; HttpOnly
< Set-Cookie: _csrf=QY55fAz3NT7dLuIyFVSOYQuA7nQ6MTU4NDk0ODk3NDE2Mzc3NjkwOQ%3D%3D; Path=/; Expires=Tue, 24 Mar 2020 07:36:14 GMT; HttpOnly
< Date: Mon, 23 Mar 2020 07:36:14 GMT
< Content-Length: 395
<
<!doctype html>

		go get --insecure git2.likeit.cn/go/audit

* Connection #0 to host git2.likeit.cn left intact

Did the curl -vsL http://git2.likeit.cn/go/audit?go-get=1 result include a <meta name="go-import" …> tag?

@bcmills yes.
$ curl -vsL http://git2.likeit.cn/go/audit?go-get=1
*   Trying <IP_ADDRESS>:80...
* TCP_NODELAY set
* Connected to git2.likeit.cn (<IP_ADDRESS>) port 80 (#0)
> GET /go/audit?go-get=1 HTTP/1.1
> Host: git2.likeit.cn
> User-Agent: curl/7.65.3
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Content-Type: text/html
< Set-Cookie: lang=en-US; Path=/; Max-Age=2147483647
< Set-Cookie: i_like_gitea=45fe72b3ffe60a55; Path=/; HttpOnly
< Set-Cookie: _csrf=6u7Yt-cdaE38e14afQ4Sxs3BkTo6MTU4NTI5MTQ0MzM2OTcyMzAyOQ    %3D%3D; Path=/; Expires=Sat, 28 Mar 2020 06:44:03 GMT; HttpOnly
< Date: Fri, 27 Mar 2020 06:44:03 GMT
< Content-Length: 395
<
<!doctype html>
<html>
	<head>
    	<meta name="go-import" content="git2.likeit.cn/go/audit git http://git2.likeit.cn/go/audit.git">
	<meta name="go-source" content="git2.likeit.cn/go/audit _ http://git2.likeit.cn/go/audit/src/branch/master{/dir} http://git2.likeit.cn/go/audit/src/branch/master{/dir}/{file}#L{line}">
</head>
<body>
	go get --insecure git2.likeit.cn/go/audit
</body>
</html>
* Connection #0 to host git2.likeit.cn left intact

I'm wondering where the : character in the URL https://git2.likeit.cn/:go/audit.git/ came from, and not having any luck finding it.
Are you still able to reproduce the original error message? (Is it possible that the server's go-import response has changed in the meantime?)

Another possibility — does your $HOME/.gitconfig contain an insteadOf rule for this host?

I didn't see ":go" in the message I posted.  I have tried insteadOf in gitconfig, but it was not there anymore.   I will try to reproduce the problem.

@bcmills the problem is reproducable:

$ go build ./...
go: finding module for package github.com/gomodule/redigo/redis
go: finding module for package github.com/go-sql-driver/mysql
go: finding module for package gopkg.in/yaml.v2
go: finding module for package github.com/boltdb/bolt
go: finding module for package git2.likeit.cn/go/audit
go: finding module for package git2.likeit.cn/go/likesync
go: finding module for package git2.likeit.cn/go/pfs-cli
go: found github.com/boltdb/bolt in github.com/boltdb/bolt v1.3.1
go: found github.com/go-sql-driver/mysql in github.com/go-sql-driver/mysql v1.5.0
go: found github.com/gomodule/redigo/redis in github.com/gomodule/redigo v2.0.0+incompatible
go: found gopkg.in/yaml.v2 in gopkg.in/yaml.v2 v2.2.8
go: finding module for package git2.likeit.cn/go/pfs-cli
go: finding module for package git2.likeit.cn/go/likesync
go: finding module for package git2.likeit.cn/go/audit
api_log.go:6:2: cannot find module providing package git2.likeit.cn/go/audit: unrecognized import path "git2.likeit.cn/go/audit": https fetch: Get "https://git2.likeit.cn/go/audit?go-get=1": dial tcp <IP_ADDRESS>:443: connect: connection refused
api_ordntfy.go:11:2: cannot find module providing package git2.likeit.cn/go/likesync: unrecognized import path "git2.likeit.cn/go/likesync": https fetch: Get "https://git2.likeit.cn/go/likesync?go-get=1": dial tcp <IP_ADDRESS>:443: connect: connection refused
pfs.go:9:2: cannot find module providing package git2.likeit.cn/go/pfs-cli: unrecognized import path "git2.likeit.cn/go/pfs-cli": https fetch: Get "https://git2.likeit.cn/go/pfs-cli?go-get=1": dial tcp <IP_ADDRESS>:443: connect: connection refused
pfs.go:7:2: package kv is not in GOROOT (/usr/local/go/src/kv)

That error message is substantially different from the one you posted originally.
All of those errors are in checksum verification, which suggests that the module is not available to the public checksum database — probably you need to set GOPRIVATE for the prefix git2.likeit.cn/go.

@bcmills setting both GOPRIVATE and GOINSECURE solved the problem. Thanks


Licensing?

I realise this may be a weird question, but I maintain an AUR package for Arch Linux for this project, and it'd greatly help if I knew under what terms it can be redistributed, or if it can be redistributed at all.
So I wondered if you'd given it any thought? GPL? Creative Commons? I'd also greatly appreciate it if you could include a LICENSE file in the repository I can optionally link to.
Thanks anyway!

Added a LICENSE.md with 66d6a88a


Why are you so long time not update with vue-material?

I want use vue-material in my project but you are so long time not update .And let me very worry about it.

See #598


Move flags

Is there a list of possible move flags combinations? In the docs, other than the single-flag string, a pc value (promotion-capture) is mentioned.
I'm not sure if there are other possible combinations like that one. Can someone enlighten me? :smile:

Off the top of my head, I believe the only two combinations are 'pc' and 'pn'.

Which would be standard move + promotion? So will I ever get promotion without anything else?

The move flags are primarily for internal use. When promoting you'll have two possible flag combinations ('np' and 'cp').  All other move types are represented by a single flag.
Here's an example of promoting capture and non-capture:
> var chess = new Chess('r7/1P6/8/8/8/8/8/k6K w - - 0 1');
undefined
> chess.moves({verbose: true});
[ { color: 'w',
    from: 'b7',
    to: 'b8',
    flags: 'np',
    piece: 'p',
    promotion: 'q',
    san: 'b8=Q' },
  { color: 'w',
    from: 'b7',
    to: 'b8',
    flags: 'np',
    piece: 'p',
    promotion: 'r',
    san: 'b8=R' },
  { color: 'w',
    from: 'b7',
    to: 'b8',
    flags: 'np',
    piece: 'p',
    promotion: 'b',
    san: 'b8=B' },
  { color: 'w',
    from: 'b7',
    to: 'b8',
    flags: 'np',
    piece: 'p',
    promotion: 'n',
    san: 'b8=N' },
  { color: 'w',
    from: 'b7',
    to: 'a8',
    flags: 'cp',
    piece: 'p',
    promotion: 'q',
    captured: 'r',
    san: 'bxa8=Q+' },
  { color: 'w',
    from: 'b7',
    to: 'a8',
    flags: 'cp',
    piece: 'p',
    promotion: 'r',
    captured: 'r',
    san: 'bxa8=R+' },
  { color: 'w',
    from: 'b7',
    to: 'a8',
    flags: 'cp',
    piece: 'p',
    promotion: 'b',
    captured: 'r',
    san: 'bxa8=B' },
  { color: 'w',
    from: 'b7',
    to: 'a8',
    flags: 'cp',
    piece: 'p',
    promotion: 'n',
    captured: 'r',
    san: 'bxa8=N' },
  { color: 'w',
    from: 'h1',
    to: 'g2',
    flags: 'n',
    piece: 'k',
    san: 'Kg2' },
  { color: 'w',
    from: 'h1',
    to: 'h2',
    flags: 'n',
    piece: 'k',
    san: 'Kh2' },
  { color: 'w',
    from: 'h1',
    to: 'g1',
    flags: 'n',
    piece: 'k',
    san: 'Kg1' } ]

Sorry if I haven't replied but I haven't got time to test it.
I asked because I need to use those flags externally, and know all the possible details about the move. Thanks for the clarification.


Add custom navbar guide

Adds guide for custom navbar title (hugo-toha/toha/pull/921)

Hi @BernatBC,
Maybe you'll go faster than me. Is it possible that you also make the modification for the index.fr.md file as follow ?
navBarTitle: "Titre"

Thank U for you help

Hi @niltied,
I could do it, but the translation might not be good enough. If you want, you can send me the translation. Otherwise, in a couple of days I could try doing it.

Re,
If you translate the index.md file, for English, it looks like this :
navBarTitle: "Title"

So, for French, it’s will be :
navBarTitle: "Ti**tr**e"

There are no other translations.

Ok, what about the following?
### Change Navbar Title
To change the title appearing on the navbar, you can modify `site.yaml` file. By defauly, the title corresponds to the website name. You can add the following line:

Hi @BernatBC,
So, it will be : "Pour changer le titre qui apparaît sur la barre de navigation, vous pouvez midifier le fichier site.yaml. Par defaut, le titre correpond au nom du site. Vous pouvez ajouter la ligne suivante:"


Default to DXC/DXIL Shader Model 6 for CMake and Windows SDK 19041

At this point, Shader Model 6 is mature and broadly supported, so I've switched these projects to use it by default:
DirectXTK_Desktop_2019_Win10.vcxproj
DirectXTK_GDK_2017.vcxproj
DirectXTK_GDK_2019.vcxproj
DirectXTK_Windows10_2019.vcxproj

The CMakeLists.txt now has a new build option which defaults to ON called BUILD_DXIL_SHADERS to control use of DXC vs. FXC.

For the Gaming.Xbox.*.x64 configurations in DirectXTK_GDK_201x.vcxproj it was already always using Shader Model 6. These updates are for Gaming.Desktop.x64

The Desktop and Windows 10 VS 2017 projects were not updated to use DXIL because they are set up for the Windows 10 SDK (17763) which was the last version to come included with VS 2017, and this version has some known bugs with the DXC compiler.

Updates for the test suite are here.

Since I haven't updated the 2017 projects, the NuGet packages will still be using FXC for a little while longer...


Make field disabling profiles after recording optional

What type of PR is this?
/kind bug
/kind regression
What this PR does / why we need it:

Make ProfileRecordingSpec.DisableProfileAfterRecording and SpecBase.Disabled optional.

This addresses CRD validation errors when upgrading to v0.8.1
See also: https://github.com/kubernetes-sigs/security-profiles-operator/pull/1712

Which issue(s) this PR fixes:
None
Does this PR have test?
N/A
Special notes for your reviewer:

I don't know exactly the impacts of making these fields optional.

Make the field disabling profiles after recording optional

/hold for test

Verification fail with 4.15.0-0.nightly-2023-12-19-033450f + code in the PR:
$ oc get csv
NAME                                    DISPLAY                      VERSION     REPLACES                            PHASE
security-profiles-operator.v0.8.0       Security Profiles Operator   0.8.0                                           Replacing
security-profiles-operator.v0.8.2-dev   Security Profiles Operator   0.8.2-dev   security-profiles-operator.v0.8.0   Pending

$ oc get sub security-profiles-operator-sub -o=jsonpath={.status.conditions} | jq -r
[
  {
    "lastTransitionTime": "2023-12-20T05:59:35Z",
    "message": "all available catalogsources are healthy",
    "reason": "AllCatalogSourcesHealthy",
    "status": "False",
    "type": "CatalogSourcesUnhealthy"
  },
  {
    "status": "False",
    "type": "BundleUnpacking"
  },
  {
    "message": "constraints not satisfiable: subscription security-profiles-operator-sub exists, subscription security-profiles-operator-sub requires @existing/openshift-security-profiles//security-profiles-operator.v0.8.2-dev, clusterserviceversion security-profiles-operator.v0.8.0 exists and is not referenced by a subscription, @existing/openshift-security-profiles//security-profiles-operator.v0.8.2-dev and @existing/openshift-security-profiles//security-profiles-operator.v0.8.0 provide ProfileBinding (security-profiles-operator.x-k8s.io/v1alpha1)",
    "reason": "ConstraintsNotSatisfiable",
    "status": "True",
    "type": "ResolutionFailed"
  },
  {
    "lastTransitionTime": "2023-12-20T06:14:31Z",
    "message": "error validating existing CRs against new CRD's schema for \"selinuxprofiles.security-profiles-operator.x-k8s.io\": error validating security-profiles-operator.x-k8s.io/v1alpha2, Kind=SelinuxProfile \"openshift-security-profiles/errorlogger-incomplete-enforcing\": updated validation is too restrictive: [].spec.disabled: Required value",
    "reason": "InstallComponentFailed",
    "status": "True",
    "type": "InstallPlanFailed"
  }
]

Codecov Report

Merging #2033 (fa33b62) into main (51d09e5) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2033   +/-   ##
=======================================
  Coverage   47.32%   47.32%
=======================================
  Files          77       77
  Lines        7352     7352
=======================================
  Hits         3479     3479
  Misses       3742     3742
  Partials      131      131

Retest with new bundle, and verification passed.
$ oc get csv
NAME                                    DISPLAY                      VERSION     REPLACES                            PHASE
security-profiles-operator.v0.8.3-dev   Security Profiles Operator   0.8.3-dev   security-profiles-operator.v0.8.0   Succeeded
$ oc get sp
NAME           STATUS      AGE
sleep-sh-pod   Installed   9m37s
$ oc get selinuxprofiles.security-profiles-operator.x-k8s.io
NAME                               USAGE                                                                  STATE
errorlogger-incomplete-enforcing   errorlogger-incomplete-enforcing_openshift-security-profiles.process   Installed

/unhold

Ugh, another one. Do you need a new release for that or can we backport the patch downstream?

I would prefer not to do a downstream patch, but if it's needed we can go this route.
I wonder if I upstream won't need a new release anyways...

Oh, I just noticed that https://github.com/k8s-operatorhub/community-operators/pull/3580 merged


Normalize asset commans

Many clauses were not getting hit depending on if
update/3 was called with a Module or a "String".
This normalizes everything early.

Coverage increased (+0.2%) to 28.154% when pulling 0536a03ff9a44c4b5d782de839e6ccced5ef290a on regimen_farm_event_update_handler3 into d3d3a3fadb10cdb35742caee979128743cccd2da on next.


"lit-element" stopped getting rendered

reboost: 0.12.0
lit-element: 2.4.0
template: lit-element
reboost.js: default
Regardless of commonJSInterop.mode value, rendering of lit-elements is over.

Can you try deleting Reboost cache dir?

Unfortunately, it does always fail.

BTW, at the same time, I very often receive errors, like Error: ENOENT: no such file or directory, open '.../reboost-le/.reboost_cache/files/...', too.

I will look into it


Docusaurus

At last, the long-awaited Docusaurus has arrived!!!
This PR aims to integrate the docs-migration branch into the main branch. Please note that we won't squash this PR into a single commit. Since it's a significant change, it's essential to ensure that the overview is included in the main branch.
Let the dinosaur ARISE! 🦖

I can hear it ROAR! 🦖


The method used to raise events on components is inconsistent

An example of this can be seen in NumberInput:
  onChange: (event: any) => void

A preferred approach might be:
  onChange: (event: React.ChangeEvent<{}>, value: number) => void

It is recommended that all components are audited to ensure a consistent approach. This will be a breaking change and needs to wait for v3.

There are also a few examples of using this style in the code base:
onFocus: React.FocusEventHandler<HTMLInputElement>


Fix handling of maven aggregator projects with no attachments

Updates AbstractGitFlowBasedRepositoryMojo to Fix #44
Updates pom.xml to add expected code level (inferred from usage of Files.createTempDirectory which is @since 1.7)
Updates AbstractGitFlowBasedRepositoryMojo to 1.7 compatibility
Pertaining to #44:
When a pom type artifact is processed, whilst the project artifact has a value it does not have a file and therefore the main artifact is not added to the catalog, this is correct behaviour. However since neither the primary artifact nor the attached artifacts contribute any entries to the catalog this results in an empty file being sent to the repository. Certain repositories, I have tested under nexus 1.9.1, do not allow empty artifacts to be uploaded and therefore this results in an error when processing the promote-master mojo.
This can be resolved by adding a section header to the catalog such that it is of the form:
[artifacts]
group:artifact:extension:classifier-1:version
group:artifact:extension:classifier-2:version

with this the empty version becomes
[artifacts]

and thus behaves as expected

Excellent catch. Thanks for tracking this down!


MGDOBR-1269: Setup Storybook for RHOSE UI

JIRA: https://issues.redhat.com/browse/MGDOBR-1269
You can see an example of the storybook created for this PR at the following URL:
https://63863b4610e04c689d81cbcc-mpawqporzz.chromatic.com
I've only added a couple of example stories, it looks a bit empty now. The idea is to add more of them after we merge the v2 PR (after we remove a bunch of stuff).
There's a new github workflow that will build&deploy a new storybook when there are new commits on main or inside PRs.
If you scroll inside this PR checks list you'll find a "Storybook Publish" entry. Clicking on the correspondent "Details" link will open the latest storybook built from the last commit of the PR.

Great job @kelvah I would just add a new section to README.md about storybook usage and the newly added commands.

@vpellegrino done.
I've only added the command to run it locally because the deployment is automated.
We could also add the public link to the one from main as soon as we have some more stuff to share.


Missing an easy way to move to next month

Hi,
In render I'm missing a easy way to move to next and previous month.
I think it could be done using startDateAt... But I have to implement it, create the arrows < > to move the months, etc...
I good idea is to have that out of box.

I see that the right way to do that is calling
this._calendar.updateCalendarDate( ) passing new date object.
 should have:
ref={component => this._calendar = component}

@bgbraga Hi Bruno,
Thank you for trying out this widget. Yes, I have been thinking about adding arrows to jump between  months and as you mentioned in your post, you can pass values to the calendar's props "startDateAt" to change the months.
And I will add arrows to next version.
:)

@bgbraga Hi Bruno,
I just updated to 0.1.4 and now support arrows to change months. :0

Thanks ;)


objects have no len() by default

undefined and null maps both to None see JSON behaviour
JSON.stringify([undefined])
JSON.stringify([null])
(not) would usually test for len() when the python implementation may not have __nonzero__ attr support ( eg pocketpy )

Thanks!


Blacklist Tags

The ability to reject bids based on tags would be really handy.
Ideally, this would include a customizable comment with a {tags} template variable for the tag that triggered the reject.

This is done and added in the last commit.


Extra '|' at end of regex breaks it

using the available burn mods function and the query was ^(has|bom|con|dro|sha|ste|blo|stormwe|) with an extra '|' after stormwe, causing it to highlight everything.

Just released a new version with a fix the moment you posted this :D

<3


How to generate Piano sound with slight delay and how to play next midi file when user in play mode

How to generate Piano sound with slight delay and how to play next midi file when user in play mode

Please be more specific.
Investigate source code of examples here
https://github.com/surikov/midi-sounds-react?tab=readme-ov-file#examples
Search answered issues.


perf(tooltip): improve the performance of tooltip.

Brief Information
This pull request is in the type of:

[ ] bug fixing
[ ] new feature
[x] others

What does this PR do?

As mentioned in #13680, the tooltip looks delayed and has an obvious lag. This brings the users a bad interaction experience.
This PR is attempting to improve the performance of the tooltip. Any idea is welcome.
Fixed issues

#13680
#14204

Details
Before: What was the problem?

The moving of the tooltip has an obvious lag.

After: How is it fixed in this PR?

https://user-images.githubusercontent.com/26999792/107198365-f6b50e00-6a2f-11eb-9b37-3081c71ca1ed.mp4
Usage
Are there any API changes?

[ ] The API has been changed.

Related test cases or examples to use the new APIs
Please refer to test/new-tooltip.html or any other test cases related to tooltip.
Others
Merging options

[ ] Please squash the commits into a single one when merge.

Other information
Related PR in zrender: ecomfe/zrender#721

Wow looks really nice

Wonderful job.


Remove unused local variable

hasOptional is assigned but unused from anywhere.

Ah, thanks! Originally I had it output an info message but I must have forgotten to remove those assignments.

Oh, I see!


Epic: Improve python test fixtures to share storage env between tests

Motivation
Our python tests take a long time.
Implementation ideas
Currently, each python test spins up a new pageserver and safekeeper, just for the one test. That's relatively expensive, the test startup and teardown steps take 3-4 s for each test. That adds up when we have a lot of small tests. Many tests don't do any special configuration or such to the pageserver or safekeepers, however, and could share them.
Sharing the storage env requires some refactoring of the python fixtures and maybe neon_local.
This is not yet a full roadmap of how to get to the end goal of sharing the storage environment, but I've identified a bunch of smaller refactoring tasks that would move us in that direction:
[ ] Clean up NeonCli so that it's more honestly just a typed wrapper around the underlying neon_local commands. Currently, it fetches some values and defaults from the NeonEnv it's attached to. Move it to a separate source file, because neon_fixtures.py is huge.
[ ] Reduce the direct calls to neon_cli from individual tests. Add functions like 'create_tenant', 'create_branch' directly to NeonEnv or other python objects. Only tests that are specifically testing neon_local functionality should call NeonCli. Others don't really care how branches are created for example, and that should be reflected in the calls they make.
[ ] Previous refactoring makes it possible to replace the neon_local calls with direct pageserver or storage_controller API calls. That allows separating the storage environment from the compute environment
[ ] Split NeonStorageEnv off from NeonEnv. NeonStorageEnv would contain only the storage-related parts, and would e.g. not carry a "pg_version" at all, because the same storage can be used with different pg versions.
[ ] Currently, most tests start with env.init_start(), which creates the environment and one initial tenant. Split it into separate calls, to start the environment, and to create the initial tenant. Tests can share the storage environment can use a fixture where the environment is already started, and go straight to creating the initial tenant

cc @MMeent, we talked about this at the offsite

FYI, in my own optimization project in https://github.com/neondatabase/neon/tree/faster-ci, I've focused mostly on making Tenant and Timeline abstractions, and make tests operate on those concepts using APIs that don't modify the shared state of the underlying SK/PS environment.
The main reasoning behind that is that as long as the test doesn't modify the shared state of SKs/PSs, one test's misbehaviour shoudn't impact another test's PS/SK operations (and if it does, that's a good reason for failure).

Yep, makes sense

Also note how my branch seems to increase test ergonomics quite significantly for tests that don't modify shared state, as you can operate on tenants and branches directly: Rather than having to keep track of the branch and tenant name and passing that through to API calls, the API makes it obvious which branch you're working on, and names are only metadata used to give things names in e.g. logging and file names.

+1


useMenuTrigger example warns about "An aria-label or aria-labelledby prop is required for accessibility."

🐛 Bug Report
When you open the useMenuTrigger example in the useMenuTrigger docs, the browser console warns about missing aria-label/aria-labelledby props. Figure out why this is happening (useMenu hook warning? But the menu has an aria-labelledby?)
🤔 Expected Behavior
No warning in the browser console
😯 Current Behavior
Browser console warns about a missing aria-label/aria-labelledby prop
💁 Possible Solution
Maybe as simple as passing an aria-label/labelledby to useMenu in the example? Or perhaps the hook need a fix?
🧢 Your Company/Team
RSP

Working on this one, it looks like the aria-labelledby is getting passed into domProps. I made a small change to pass the value directly into the MenuPopup component instead of into domProps. https://github.com/adobe/react-spectrum/pull/2642 Is this the right way to go about this?

Closed by PR mentioned


[PvP] BLM Wrath Update

Black Mage has been revisited for Patch 7.15.
Major Changes

Complete logic rework.
Fire and Blizzard spells have been condensed into one button.
Smart Paradox usage for higher damage and fire-aspected uptime.
Elemental Weave now accommodates both Fire and Ice wreaths.
Several actions now have toggles to include defensive usage.

Minor Changes

Lethargy will no longer be used against NPCs.
Xenoglossy prefers saving charges when used against NPCs.
Aetherial Manipulation removed as it no longer grants Swiftcast.

Other Changes

Removed all weaving checks and obsolete IDs.
Added missing actionIDs for Fire/Blizzard III and High Fire/Blizzard II.
Added Aetherial Manipulation Feature for quick debuff cleansing.

edited my comment above - ill play it some more and let u know if i find anything else.

Thanks.
Regarding the "staying on ice" part, this only happens when you reach Umbral Ice III as it wants to spend High Blizzard II even if you're not moving, before going back to fire - otherwise you're giving up a free 9,000 damage (+4,500 AoE) instant spell; but it does mean delaying going into fire for one GCD. This does not apply during Soul Resonance.
The movement aspect I'm still a bit undecided on, mostly because it serves as a "control stick" for which element you want to be in. For example, if you just want to finish off a low health target, start moving to use a quick ice spell; instead of hard casting fire spell.
It takes a bit of getting used to, but I feel the tight controls are better overall, but I'm open to re-evaluating it over time.


Impove logs

Make connections log by CID instance, instead direct logrus (for unification connection id in log)
Avoid conn.RemoteAddr() call without need.

Fixed in https://github.com/rekby/lets-proxy2


Scully serves old version of application

🐞 Bug report
Description.
Just changed some styles in global scss file, ran npx scully serve  and old version of application appears in browser. First I thought I need to clean my static folder or rebuild app, tried npx scully and got messages:
new Angular build imported. and Started servers in background. But new version didnt appear
🔬 Minimal Reproduction.

create minimal app and build it
change some styles/layout etc..
rebuild app
serve static version and i suggest you wont see changes

💻Your Environment
MacOS 11.5.2.
Node 16.4.2
Angular Version: ~12.1.1

Angular CLI: 12.1.4
Node: 16.4.2 (Unsupported)
Package Manager: npm 6.14.14
OS: darwin x64

Angular: 12.1.5
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1201.4
@angular-devkit/build-angular   12.1.4
@angular-devkit/core            12.1.4
@angular-devkit/schematics      12.1.4
@angular/cli                    12.1.4
@schematics/angular             12.1.4
rxjs                            6.6.7
typescript                      4.3.5

Scully Version: ^1.0.0

{
  "name": "scully-ssg",
  "version": "0.0.0",
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build",
    "watch": "ng build --watch --configuration development",
    "test": "ng test",
    "scully": "npx scully --",
    "scully:serve": "npx scully serve --"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "~12.1.1",
    "@angular/common": "~12.1.1",
    "@angular/compiler": "~12.1.1",
    "@angular/core": "~12.1.1",
    "@angular/forms": "~12.1.1",
    "@angular/platform-browser": "~12.1.1",
    "@angular/platform-browser-dynamic": "~12.1.1",
    "@angular/router": "~12.1.1",
    "@scullyio/init": "^1.1.4",
    "@scullyio/ng-lib": "^1.0.0",
    "@scullyio/scully": "^1.0.0",
    "rxjs": "~6.6.0",
    "tslib": "^2.2.0",
    "zone.js": "~0.11.4"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "~12.1.1",
    "@angular/cli": "~12.1.1",
    "@angular/compiler-cli": "~12.1.1",
    "@types/jasmine": "~3.6.0",
    "@types/node": "^12.11.1",
    "jasmine-core": "~3.7.0",
    "karma": "~6.3.0",
    "karma-chrome-launcher": "~3.1.0",
    "karma-coverage": "~2.0.3",
    "karma-jasmine": "~4.0.0",
    "karma-jasmine-html-reporter": "^1.5.0",
    "typescript": "~4.3.2"
  }
}

Didn't got any errors or exceptions but still see old version, tried to clean static folder by myself and it didnt solve problem.
Thanks everyone for help !

Are you sure you did an ng build?
If so, are you using caching?
Can you try again? use those commands in this order: (assuming mac/Linux/wsl, otherwise use the windows equivalent)
rm -fr dist
 npx ng build
 rm -fr .scully   // Only if you used the scully cache!
npx scully --scanRoutes

Let us know what happens

Closing this, as there seems nothing left to do.
We will happily reopen when needed


Syntactic sugar for mapping over a union type

Search Terms
distributed conditional types, discriminated unions, mapped types
Suggestion
It's quite arduous to map over a union type, when you need inference to each case of the union. It requires you to do symmetrical extends with an infer. A special syntax for this would be great, e.g.
type Species = 'dog' | 'cat' | 'pig';

type Animal = U in Species | { species: U; givenName: string, age: number }

/* Resolves as:
 *
 * type Animal =
 *  | { species: 'dog', givenName: string, age: number }
 *  | { species: 'cat', givenName: string, age: number }
 *  | { species: 'pig', givenName: string, age: number }
 */

I haven't put much thought into the syntax at all, but you get the idea. The reasoning behind the above suggestion was to mirror the mapped-type syntax somewhat i.e.
type Animal = {
  [P in Species]: ...
}

Whilst mirroring the union type syntax (|).
Use Cases
There is a way of yielding the type in the example above using the current lang, but it's hard to discover, the syntax is heavy and it's scary for newbies. The "Advanced Types" docs are great, but you need to read an ingest them all the way to distributed conditional types in order to do something that's feels quite intuitive if you have a little bit of experience with mapped types.
Here's how you would achieve the above, as of TS 3.8 (and a new syntax could just be sugar over this pattern):
type Species = 'dog' | 'cat' | 'pig';

type Animal = Species extends infer U ?
    (U extends Species
       ? { species: U; givenName: string, age: number }
       : never)
: never;

As @yortus pointed out, a more direct approach of achieving the same result is:
type Animal = { [U in Species]: { species: U; givenName: string, age: number } }[Species];

Examples
If you understand what the value of mapped-types are then mapping union types isn't that outrageous an idea.
Here's something from recent memory:
type PropertiesAsUnion<T> = U in keyof T | { key: U; value: T[U] }

type Model = {
  foo: string;
  bar: number;
}

type ModelProperty = PropertiesAsUnion<Model>;

/* Resolves as:
 *
 * type ModelProperty =
 *  | { key: 'foo', value: string }
 *  | { key: 'bar', value: number }
 */

const updateModelProperty = (model: Model, property: ModelProperty): Model => { ... };
updateModelProperty(model, { key: 'foo', value: 'must be a string as per discriminated union' });

As with distributed conditional types, candidates for the same type are combined:
type Vehicle = 'car' | 'truck' | 'bus'

type UnnecessaryUseOfMappedUnion = U in Vehicle | { foo: string } // Warning: 'U' is declared but its value is never read.

/* Resolves as:
 *
 * type Vehicle = { foo: string };
 */

Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

There is a simpler formulation for mapping over a union type that doesn't require extends or infer. E.g. your Animal example could be written:
type Species = 'dog' | 'cat' | 'pig';
type Animal = { [U in Species]: { species: U; givenName: string, age: number } }[Species];

That's only a little longer than your special syntax, but perhaps still a bit obscure.

@yortus, oh nice one! That's much more simple at least, will add that to my toolbox 😁 I can see how that also spreads to a union.
My vague feeling that it should mirror the existing mapped-typed syntax seems more justified now. There's less reason for a syntactic sugar over it now in my eyes, but still, ya a little bit obscure (too obscure for me to realise that solution, anyhow).

You could also write
type UnitOf<T> = T extends infer U ? { species: U; givenName: string, age: number } : never;
type Animal = UnitOf<Species>;

Declining since there are multiple ways to do this

Hey @RyanCavanaugh,
Thanks for the reply.
I guess that Animal example is quite trivial - I just wanted to demonstrate the syntax. I could have fleshed out the model property example a bit more in my original post, which I still believe is nasty enough to warrant some extended syntax, or at least some docs about mapping to a union or mapping over a union.
Suspend disbelief for a second, this example is pretty fabricated, but it actually pretty analogous to something I'm working on at the moment - reduced heavily for simplicity.
type Model = {
    foo: string;
    bar: number;
};

// Suppose I want to allow updating individual properties of a model, so that I can control how those things are updated.
type ModelProperty = PropertiesAsUnion<Model>;
/* Outputs:
 *  | { key: 'foo'; value: string }
 *  | { key: 'bar'; value: number }
 */

// Suppose there is some additional data, which drive the "how" of the updates.
type UpdateModelPropertyAction = UpdatePropertyAction<Model>
/* Outputs:
 *  | { key: 'foo'; newValue: string; isDraft: boolean }
 *  | { key: 'bar'; newValue: number; isDraft: boolean }
 */

These would be the supporting types as of 3.8:
type PropertiesAsUnion<T> = { [U in keyof T]: { key: U; value: T[U] } }[keyof T]

// I don't believe this can be collapsed to indexing out of a mapped type in this case
type UpdatePropertyAction<T> = PropertiesAsUnion<T> extends infer U
    ? (U extends PropertiesAsUnion<T>
        ? {
             key: U['key'];
             newValue: U['value'];
             isDraft: boolean
           }
        : never)
    : never

If there was a syntax for mapping over a union:
type PropertiesAsUnion<T> = U in keyof T | { key: U; value: T[U] }

type UpdatePropertyAction<T> = U in PropertiesAsUnion<T> | {
  key: U['key'];
  newValue: U['value'];
  isDraft: boolean
}

In my real-life scenario, the PropertiesAsUnion<T> is definitely a handy abstraction to have, as it's used to drive a bunch of different types in the system. Mapping over each case in that union (and not collapsing the cases) is a thing that I do in a heap of places.
I hope this sheds a little more light on the use-cases.
Cheers.

This still gets in the way for me, but mostly, I still believe the existing syntax is very unfriendly for newbies.


change invalid characters when get user data dir on Windows & Unix

Can't create user data folder when project name has \ / : * ? " < > | characters on OS_Windows & OS_Unix.
So, change it to - to be able to make folder.
fixes #4928.
It's altanative to #4986, but this one has no restriction to make project name.
It's up to @akien-mga to merge which one and close. :)

Actually, couldn't we escape those characters? i.e. cd More\ \*\*\/\ \\Characters

No, those characters are forbidden on Windows, they can't be escaped.


non-interactive login

Once we have TOTP as an option for mfa authentication, we can have non-interactive login this way:
echo $my_secret_password_variable | dds auth login --username <username> --TOTP <totp> --password-stdin

It's otherwise difficult to specify both the MFA code and the password on stdin, and we don't want to have password as a cleartext option.

Moving to Jira.


Server: Limit or configure request body buffering

Is your feature request related to a problem? Please describe.
I need to create a server that read request's bodies at low kbps even if clients send data faster.
The problem is that hyper is buffering data of bodies for several minutes ahead of the needed kbps. Body::data() is returning chunks of more or less 3 MB. We need a way to get chunks of near 16 KB.
Describe the solution you'd like
It would be nice if body buffering could be configured, or at least if someone can point me to the right location in the source where this could be changed.
I'm using hyper with http1 only, as the server sits behind a reverse proxy

Body::data() is returning chunks of more or less 3 MB

That shouldn't be the case, the default maximum buffer size is currently ~400kb. Unless told not to, hyper will increase it's read buffer until it detects optimum throughput. But it will only do 1 read at a time, until you stream that chunk from the Body.


Hub: parametrize API base path

Hub API path is not always /api/automation-hub, we'll need to work with /api (community), /api/galaxy (standalone prod, some standalone dev), /api/automation-hub (insights prod, insights dev, most standalone dev envs).
npm run hub - defaults to /api/automation-hub
npm run hub -- --env hub_api_base_path='/api/galaxy' - changes default to /api/galaxy

or would it make sense to move these up to useHubView / usePulpView , so that we'd be passing just tasks/ instead of /api/automation-hub/pulp/api/v3/tasks/ ?


GitHub merge Migrator -> swift 4.0 branch

Forgot to cherry-pick these after the branch on Monday.

@swift-ci Please test

@swift-ci Please test


Design Meeting Notes, 2/15/2019

Generic function composition
#29904

The fact that we're not doing unification is nothing new.
Inconsistency depending about strict mode is a very weird experience.
But also seems weird that we're committed to backwards compatibility, but we think strict mode is the best way to operate.
What if strict would be the default?

The problem is that strict always brings new checks in.
Even older commitments become questionable with strict mode

For example, strictness issues in #27288 have been fixed with strictFunctionTypes.

Many issues come from writing the overloads incorrectly.

Current implementation might be better written as
let pipe: <A extends any[], B, C>(
    f: (...args: A) => B,
    g: (b: B) => C):
      (...args: A) => C

Works really well... sometimes.
const fn = pipe(
    (a: number) => a * a,
    x => "hello " + x,
);
// (a: number) => string

Doesn't work when you have contextually sensitive parameters.
const fn = pipe(
    (a, b) => true, // contextually sensitive
    x => "hello",
);
// (...args: any[]) => string
// ...what?

Problem is we make no inferences for A, which jumps to the base constraint which is any[].

Shouldn't it have been constrained to unknown[]?

Maybe, but that doesn't fix the fact that it will still take an arbitrary arity (unknown[]) instead of maintaining the input arity [unknown, unknown].

So we're experimenting with a way to infer the shape for a spread-in type parameter. We're considering that a bug.

To be explicit, we're not solving the "do arbitrarily complex function composition problem"

strict by default

Returning to "strict by default" conversation

What if tsconfig-less projects were strict
Would break a lot of people using MSBuild, gulp, etc.
Could adopt a different versioning scheme and say in the next version we'll do strict.
"uhhhhhhhhhhhhhhhhhhhhhhhhhhh"

"how do you encode that sound in the design meeting notes?"

What's the behavior for checkJs?

Questionable if you want that to be strict

strict is turned on by default when you write tsc --init

Not everyone turns that on
"Well I always do"

and I'm just a humble member of the compiler team!

Could try to affect the the change by other venues

Do most boilerplates turn strict mode off?

Would love to at least have strictNullChecks and strictFunctionTypes.

Maybe that's the idea? Individual flags instead of all of strict.
How do those compose?

You get never[] with strictNullChecks without noImplicitAny.

It took us months to adopt strictNullChecks.

We should discuss what 4.0 means.

Would be reasonable to discuss a specific versioning strategy.
Not semver, but explicit expectations.

One thing this means is that if we're a dial, we start in the middle rather than at the beginning.

This means that strictness is not purely additive.

Not semver, but explicit expectations.

I know I and a bunch of other folks in the Ember community (and probably others!) would be very interested in what you all land on in that conversation. We're trying to sort out a what a SemVer-compatible strategy for official adoption of types looks like—because even if TS doesn't do SemVer, projects which use it do—and at a minimum clearer expectations about what kinds of things will and won't change in a point release would be hugely helpful for us as we work through that!

strict is turned on by default when you write tsc --init

A lot of people don't use that command to initialize the tsconfig.json file, but instead copy an old or a Googled version. Then they miss out the great features because they don't know about them. I frequently see new projects created with the strict flag missing due to nescience.


[BUGFIX] Fix helper.

Pull Request Test Coverage Report for Build 864

0 of 0   changed or added relevant lines in 0 files are covered.
6 unchanged lines in 4 files lost coverage.
Overall coverage remained the same at 67.118%

Files with Coverage Reduction
New Missed Lines
%

src/EconomicStrategy/EconomicStrategyHelpers.ts
1
92.31%

src/Actions/Helpers.ts
1
0.0%

src/Scanner/Scanner.ts
1
78.38%

src/Actions/Pending.ts
3
80.95%

Totals

Change from base Build 862:
0.0%

Covered Lines:
407

Relevant Lines:
578

💛  - Coveralls


Fix description of failureThreshold

This PR corrects the description of failureThreshold. The old description was misleading because it mentions "When a Pod starts". This makes it sound as if the failureThreshold only applies on pod start - which is not true. It applies always. The pod start isn't a special case and shouldn't be mentioned.

Thanks @MajorBreakfast


Request for pretrained model

Is there any plan to release the pretrained model?

Okay, since the model is quite big, I will send you by mail. thank you!


Send files for bisection over DRb instead of ARGV

(Addresses #2145)
When bisecting a large set of specs, the maximum argument length for open3 can be exceeded. To work around this issue, pass the list of files and directories via the DRb connection.
There are a couple things that I'm not entirely happy with in this:

some of the specs didn't make as much sense anymore. In particular, it wasn't clear to me what spec/rspec/core/bisect/runner_spec.rb:226 should be checking now that files aren't passed on the command line.

the bisect mechanism isn't particularly isolated from the rest of the system. The check in Rspec::Core::Configuration#files_or_directories_to_run works but seems messy.

run_formatter_specs sets up an odd not-entirely-realistic scenario (files passed on the command line AND via DRb). Cleaning that up would require a sizable refactor of that helper method.

client vs server naming is not clear. I can't decide if introducing RSpec::Core::Bisect::Client makes the situation worse or better.

there are now two slightly-different ways to specify the spec files to be run over DRb (via the --drb switch and via the bisect plumbing added here). They serve distinct purposes, so I'm unsure if the duplication is a problem or not.

A more significant refactor might solve some of these issues. Perhaps instead of --files-over-drb, a flag like --bisect-client that activates an alternative runner? That runner could handle setting the formatter to bisect and pulling files from DRb.

I'd appreciate any insight on what's making the builds fail. Tried running script/run_build locally but couldn't reproduce the "exiting with status 2" behavior. Is this a coverage issue?

I'd appreciate any insight on what's making the builds fail. Tried running script/run_build locally but couldn't reproduce the "exiting with status 2" behavior. Is this a coverage issue?

It is indeed a coverage issue.  Run bundle exec script/rspec_with_simplecov to run RSpec with simplecov locally.  I ran it locally and it's reporting this line as uncovered.  As it happens, it is covered, but it is only executed in another process during the execution of the test suite.  The simple solution would be to write a spec in option_parser_spec.rb to cover it.
That said, I think we can do away with the files_over_drb option entirely and improve the design of the solution you've come up with -- and I'd much prefer that we do that.  The --files-over-drb option has a few issues I see:

It's only supported during --bisect runs but is exposed as a CLI option for users to pass at any time.
It's implementation complicates RSpec::Core::Configuration making it load the bisect client (which in turn loads drb -- something we'd like to avoid if it's not needed).
It makes config.files_or_directories_to_run= confusing -- the implementation now ignores the passed argument, which is very odd.

config.files_or_directories_to_run has a setter method, so we should be able to use that to set it, without changing the RSpec::Core::Configuration implementation or requiring a new CLI option.  Specifically, I think you can call RSpec.configuration.files_or_directories_to_run = @bisect_server.files_or_directories_to_run from RSpec::Core::Formatters::BisectFormatter#initialize. The BisectFormatter is only ever loaded while bisection is happening, and is loaded in each spawned process running one set of examples, so it's a natural point to have it set that config value, particularly since it has access to the bisect server.
Thoughts?

@myronmarston I considered that approach initially, but having a formatter reach back into the core of the system and reconfigure things didn't seem particularly clean either. I'll give it a try.

@myronmarston Was this more like what you were looking for? I'm still digging into what's going on with the build failure on jruby-18mode.

@myronmarston Was this more like what you were looking for?

Yes!  I'll try to do a proper review soon so we can get this merged :).

I'm still digging into what's going on with the build failure on jruby-18mode.

We see the bisect tests intermittently fail on jruby-18mode periodically.  I've looked into it a few times and have never figured out why.  I believe it is probably due to a bug in jruby-18mode since no other ruby interpretters fail like that.  Usually we just kick the build and it passes the next time.  I just restarted that part of the build and hopefully it'll pass now.

@myronmarston Rebuild seems to have sorted it. Lemme know if you'd prefer these commits squashed to one.

Lemme know if you'd prefer these commits squashed to one.

Please do.

run_formatter_specs sets up an odd not-entirely-realistic scenario (files passed on the command line AND via DRb). Cleaning that up would require a sizable refactor of that helper method.

I don't understand this point.  Can you expand on this a bit?  Which specs in particular are odd?

The odd thing about run_formatter_specs in the bisect server spec is that it calls the subprocess with a slightly unrealistic set of arguments which includes both --format bisect and filenames on the command line. here. That shouldn't cause any issues as far as I can tell and would require some pretty significant refactoring to avoid, so I don't believe it should be changed - but I called it out in the interest of thoroughness.

@myronmarston Fixed the pending spec, cleaned up stray comments and squashed.

BTW, thanks for explaining the run_formatter_specs weirdness.  I see it now.  I think that run_example_specs_with_formatter should be refactored but it can be a separate PR.  If you want to take a stab at it, feel free, but I'm happy to do that post merge.

^^ cc @myronmarston this was updated

@myronmarston Fixed that spec string.

Thanks, @al2o3cr!

@al2o3cr Thanks for your work on this! Definitely appreciate it.


Update "double-groupby-*" for Query types

The double-groupby-1 devops query types was associate the variable of DoubleGroupByDuration .
The DoubleGroupByDuration  has been  change 24 to 12 in 46b079.
But Documentation have not been update.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.ye.wenqiang seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Tiles not properly resetting after disabling debuggable tiles for neighbors

Forcing a refresh after sending the signal might solve this problem


I can't add custom key binding to command

I can't add custom key binding to my "compile" command.
Key Binding Resolver returns true, but the command doesn't execute.
'atom-workspace':
    'f4': 'build-tools:compile'

Key Binding Resolver shows key bindings, but does not check whether their commands actually exist.
Commands for built-tools are mentioned here. Just make sure that your "compile" command is the first, second or third command in your .build-tools.cson.

Should I rename my command to "first-command" and change the key in .build-tools.cson (to F4)?

You can't access your commands by name. If your command is the first one in your .build-tools.cson, you execute it with build-tools:first-command. build-tools:second-command and build-tools:third-command execute the second and third command respectively. build-tools:commands displays a list of all available commands, allowing you to select and execute one.

Thanks. One more question, I'm using g++ and std::cout doesn't print on the console, only errors and warnings are appearing on the console. There is an option to enable it? (avoid running it in cmd)

g++ works perferctly fine on my machine. I also can't think of a configuration problem that would hide stdout but not stderr, but I also don't really have any information on your configuration. I would say it's a problem in your code until I know more.

main.cpp
#include <iostream>

using namespace std;

int main(int argc, char * argv[]) {
    int arraylength = 3;
    int input[arraylength];
    int output = 0;

    for (int i = 0; i < arraylength; i++)
        cin >> input[i];

    for (int i = 0; i < arraylength; i++)
        if (input[i] > output) output = input[i];

    cout << output << endl;

    return 0;
}

.build-tools.cson
providers: [
  {
    key: "bt"
    config:
      commands: [
        {
          project: "C:\\Users\\Danilo\\Desktop\\simple"
          source: "C:\\Users\\Danilo\\Desktop\\simple\\.build-tools.cson"
          name: "Compile"
          command: "g++ \"*.cpp\" -std=c++14 -o \"../release/simple.exe\""
          wd: "source"
          env: {}
          modifier:
            save_all: {}
          stdout:
            pty: false
            highlighting: "nh"
            ansi_option: "ignore"
          stderr:
            highlighting: "hc"
            profile: "gcc_clang"
          output:
            console:
              close_success: false
              queue_in_buffer: true
              stdin: true
            linter:
              no_trace: false
          version: 1
        }
      ]
  }
]

The input field is disappearing after a few seconds as well (impossible cin).

I guess it would make sense to also start the command. g++ just compiles it.
Also, stdin can be buggy if you don't use pty.js.

I got this error using pty.js:
Uncaught Error: File not found:

C:\Users\Danilo\.atom\packages\build-tools\node_modules\ptyw.js\lib\pty_win.js:56

Error: File not found:
    at Error (native)
    at Server.<anonymous> (C:\Users\Danilo\.atom\packages\build-tools\node_modules\ptyw.js\lib\pty_win.js:56:9)
    at emitOne (events.js:77:13)
    at Server.emit (events.js:169:7)
    at Pipe.onconnection (net.js:1427:8)

I guess there is something wrong with your configuration but I can't test it, since I don't use this OS.
*.cpp in your command shouldn't work either, but then g++ should print an error message and not Atom. I have a modifier called Execute In Shell that probably supports patterns, but the default configuration only works for UNIXs (maybe something like cmd.exe works here).

Thanks. I will change the OS. Maybe CentOS.

I'm not saying people should change their OS because of my package. I'm just saying that I do not know enough about Windows to properly support it.


Support for SENZING_ENGINE_CONFIGURATION_JSON

Pull requests:

https://github.com/Senzing/governor-postgresql-transaction-id/pull/16


Implement comment on table changing for table diff

Table diff is missing comment changing.
SQLs can look similar to this
COMMENT ON TABLE temp."Foo"
  IS 'Foo table!';

or
COMMENT ON TABLE temp."Foo"
  IS NULL;

Duplicate of #34


Compatibility with postcss-functions

Is it possible to make this plugin compatible with postcss-functions ? Is there any alternative?
I have code like:
 @each $value, $i in values($map) {

where values is a function

you tried use custom variables in function like as ?
@each $value, $i in values(var(--map)) {

Yes, not working too because functions bust be evaluated before each :(

put the plugin postcss-at-rules-variables above the plugin postcss-function in the plugins list postcss

Yes that was the first approach but nothing, I've solved my issue ussing replace plugin but not the ebst scenario xD


[top] Correct xbar reset connections

fixes #13354
isolate the xbar reset from the individual end-point resets
scripting updates required to allow for different resets

Signed-off-by: Timothy Chen<EMAIL_ADDRESS>

yep that's right!

if there are no objections to this, i will merge it in the morning.


Add Dribbble shot

400×300 pixels or @2x 800×600 pixels for HiDPI or Retina displays
Thanks :)

took some time, but done! please read the "updates" section of the readme though. https://github.com/herrhelms/social-artboards-sketch#updates


Bluetooth Printer Selection Exception

I try to print something on a thermal printer with my .NET MAUI App.
How can i specify my Bluetooth-Printer which is already connected to my device?
// USB, Bluetooth, or Serial
var printer = new SerialPrinter(portName: "COM5", baudRate: 115200);
The documentation is not that helpful, when i am using this code snippet, i 'm getting the following Exception thrown
{System.DllNotFoundException: libSystem.IO.Ports.Native
at System.IO.Ports.SafeSerialDeviceHandle.Open(String portName)
at System.IO.Ports.SerialStream..ctor(String portName, Int32 baudRate, Parity parity, Int32 dataBits, StopBits stopBits, Int32 readTimeout, Int32 writeTimeout, Handshake handshake, Boolean dtrEnable, Boolean rtsEnable, Boolean discardNull, Byte parityReplace)
at System.IO.Ports.SerialPort.Open()
at ESCPOS_NET.SerialPrinter..ctor(String portName, Int32 baudRate)
at Lobi.Pos.Printer.PrintWorker.GetBTPrinter(LobiPrinterSettings printerSetting) in D:\work\awagd\LOBI\New\src\Lobi.Pos.Printer\PrintWorker.cs:line 187
at Lobi.Pos.Printer.PrintWorker.InitiatePrinterConnection(LobiPrinterSettings lobiPrinterSettings, String deviceName) in D:\work\awagd\LOBI\New\src\Lobi.Pos.Printer\PrintWorker.cs:line 134}

I am trying to use it from android

I've successfully done this in a Xamarin Forms application, so I believe you should be able to do the same in MAUI.  Maybe there's something wrong with your build or with the DLL loading, because I see it says that the DLL for System.IO.Ports.Native wasn't found (which is probably the Android-specific implementation).
Regarding connecting to the printer, I would suggest using BLE - then you need to use a library that supports BLE to find devices, connect to them (you'd make a UI to display a list of printers when scanned from bluetooth, for example), and then you can send bytes to them.


allow setting template file or class in the config file

these updates allow you to define templates and classes in the config file instead of having to use --template and --class all the time from the command line. the same rules about not using both at the same time apply.
templates:
file: path/to/file
class: f/q/c/n

closing because of course i had a better idea. brb.

a better idea.... i have to see this :d I liked this one.
On Wed, Aug 19, 2015 at 2:01 PM, Bob Majdak Jr<EMAIL_ADDRESS>wrote:

closing because of course i had a better idea. brb.
—
Reply to this email directly or view it on GitHub
https://github.com/robmorgan/phinx/pull/622#issuecomment-132743581.


Per req cache bypass

possible Implementation for #68
I have not rebuilt the dist. On my machine, I can't build with the version of webpack-cli/webpack that's defined in this package.json.
I upgrade the packages and the problem goes away. but that should be referenced in a different pr.
The related error is here:
https://github.com/webpack/webpack-cli/issues/607

Thanks for this PR!
Very simple implementation, looks good 👍
What do you think about only accepting the ignoreCache parameters as a per request option. Because setting ignoreCache globally makes no sense right?
Although to achieve this we need to change src/config.js quite a bit. What do you think?
Else we just need to add some documentation in readme and we're good to go!

I'll merge this as is and maybe work on it a bit more.
Thanks again for your contribution @jahead 🎉

Sorry, work got a little busy here. You are correct, but I wonder if could just put a throw case in the merge code to stop someone shooting themselves in the foot. do you want me to open another issue/PR

No worries @jahead ^^
If you've got time I'll gladly accept another PR 😄
A throw should be enough.
Cheers


Add mingw support gnutls

Description of changes
Add mingw support for gnutls
part of a larger effort to add mingw support for qtmultimedia
Relevant for https://github.com/NixOS/nixpkgs/issues/274274

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg build pkgs.pkgsCross.mingw32.gnutls

@ofborg build pkgs.pkgsCross.mingwW64.gnutls

@wegank @Artturin @bjornfor

@ofborg build pkgs.pkgsCross.mingwW64.gnutls

@ofborg build pkgs.pkgsCross.mingw32.gnutls

@ofborg build pkgs.pkgsCross.mingwW64.gnutls


fix: fixing modal height by removing min-content

Description
min-content css property is behaving weirdly in the latest update of the chrome browser
Fixes https://github.com/appsmithorg/appsmith/issues/36586
Automation
/ok-to-test tags=""
:mag: Cypress test results

[!CAUTION]
If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[ ] No

/build-deploy-preview


Webpack on server

One step closer to having client and server being similar.
The reason I started doing this was so that we could actually start using CSS modules, which I think will give us a bit more clarity about how we structure components, similar to #94.

Run through with @davidpmccormick


Lack pool/snat empty logic

 % ./f5-tmsh-generator.py config/f5config.3 test/request-pool-snat-exist.txt
tmsh modify ltm pool ydbg_<IP_ADDRESS>_80_pool members add { }
tmsh modify ltm snatpool ydbg_<IP_ADDRESS>_snat members add { }
tmsh save sys config

pool and snatpool member exist
 % ./f5-tmsh-generator.py config/f5config.3 test/request-pool-snat-exist.txt
tmsh save sys config


Add an endpoint to trigger a structure

Input:

structureExternalId: the structure (and its substructures) to trigger

volunteerInternalEmail: a CRF email that owns the trigger (because a general API token can be used by an app used by many volunteers); the volunteeerInternalEmail should be owned by someone in the token's owner scope

message: a message to send

Output:

the number of triggered volunteers
the trigger URL

Done in #656


HSDS-217: Add AvatarsSelectionModal component

Problem/Feature
For the new Messages Avatar feature (spec), we need to have avatar selection modal available. Component like this has laready been created as part of work on Beacon avatars. Here's demo of how it looks right now: https://c.hlp.sc/8Lu9qYdn
This PR is adding new component to HSDS (AvatarsSelectionModal), that is a copy of the HSAPP component. Here is the original component.
Designs
The original design: https://www.figma.com/file/hOhDp1xvPMFI0kyx0y3i0y/Discovery%2F-Custom-Avatars?node-id=132%3A8152
Slightly updated design for Messages: https://www.figma.com/file/BQCNhAY4nh0AI53y0B1EXB/Spec%2F-Message-Avatars?node-id=4%3A4668
One thing I am aware of, that is not in-line with the design is the search input. It's bigger on implementation than on desgin, however, I am using standard Input component, so I think we should stick with it here. There is an option to make it smaller, but then it's not the same as on the design as well :shrug:
Changes
The component was in most part just copied from HSAPP, but a few things needed to be changed:

Enabled single selection mode. For Messages we need to allow selecting only single avatar and not force users to deselect previous to select a new one. Limiting to 1 could be done already, but the behavior was as mentioned - needed to deselect first. Change was made to set multiSelect prop on CheckMarkCard.Grid component used internally.
Adjusted texts inside the modal, based on the provided limit (it's different for 1 and anything >1)
Some refactoring to make it more generic and removed code specific to Beacon avatars
Added tests

Storybook
A few stories has been added for this component, presenting most significant features (single selection, multi selection, pre-selected avatars)
Testing
It should be enough to check the mentioned stories to verify if everything is working. Unit tests should cover most cases.

Guidelines
Make sure the pull request:

[ ] Follows the established folder/file structure
[ ] Adds unit tests
[ ] If it is a refactor or change to an existing component, have you verified it won't break existing Cypress tests or have you updated them?
[ ] Did you verify some accessibility (a11y) basics?
[ ] Adds/updates stories. Guidelines
[ ] Adds/updates documentation (ie proptypes) Guidelines
[ ] Has it been tested in Help Scout's supported browsers?
[ ] Requests review from designer of the feature
[ ] Add label (bug? feature?)

@tinkertrain This is the first time I am adding new component to HSDS, so any comments/suggestions are appreciated :smile:

@jakubjanczyk Good work! A couple of notes:

I see this is using the current or should I say "old" scrolling pattern (with the gradient when overflowing), I think you should suggest the change to the newest "solid shadow" pattern, as I believe it will get used from now on, so it will probably have to be changed anyways at some point, as a reminder here's the PR which will be released pretty soon: https://github.com/helpscout/hsds-react/pull/1001 cc @alexestrada
I'd like us to try and use SimpleModal instead of Modal, I believe it should support what you need here, and also I'd like to use the pattern of "layouts" just like the SidePanel so that we don't end up with several custom modals that are not shareable.

So the layout can be something like this, I think this will be a regularly used pattern (the modal with the header, footer and scrollable content).
Let's say you create the layout as "HeaderAndFooter" (named like the one in SidePanel, as it's basically the same thing).
You'd have something like:
// SimpleModal/SimpleModal.layouts.js

import ScrollableContainer from './ScrollableContainer'
import { BodyUI, FooterUI, HeaderUI } from './SimpleModal.layouts.css'

export function HeaderAndFooter({headerContent, footerContent, children}) {
  return (
    <ScrollableContainer
		header={<HeaderUI>{headerContent}</HeaderUI>}
        body={<BodyUI>{children}</BodyUI>}
		footer={<FooterUI>{footerContent}</FooterUI>}
    />
	)
}

Then AvatarSelectionModal would be something like:
// AvatarSelectionModal.js
import SimpleModal from '../SimpleModal'
import { HeaderAndFooter } from './SimpleModal.layouts'

<SimpleModal>
  <HeaderAndFooter headerContent={} footerContent={}>
	//.. your stuff inside the scrollable area
  </HeaderAndFooter>
</SimpleModal>

The only thing I'm unsure is whether that last one belongs in HSDS or not, conceptually I think not, but I guess it makes it easier since it's supposed to be used in Beacon and HS App UI.
Let me know what you think, I realize this suggestion is a bit more work if you need a hand just let me know! Happy to 🍐 on this.

Just want to shime in as well. I don't think this component belong in HSDS.
I can see the reasoning to build it here (to share it between hs-app and hs-app-ui) but we are trying to move away from building complex component that contains tons of smaller components within HSDS (like ChatScroller, Condition, etc).
It's not a hard no, meaning that I can change my mind if we think the HSDS context is the right one, but my stand right now would be to move it as a shared component within hs-app-ui. I think we can live with the duplicate code with the old component for now, that's the downside of having two frontend repos.
If it start to happen a lot, maybe we should find a way to make the shared component from hs-app available in hs-app-ui (maybe through git submodule....I don't know)

@plbabin Yeah I was considering where it goes and I share your doubts. The main reason is that it's in 2 repos of course, so there is no other place to put component to be used in 2 places. At the moment I don't see any other components like this in hs-app that would need to be used in hs-app-ui, so looks like one time thing.
Good thing is that, apart from the storybook, my work here would not be a waste of time :smile: I can just copy the code from here to hs-app-ui (and leave the hs-app code as it is).
If you and @tinkertrain feel strongly about not adding it here, let's close this one and I'll move the code as part of other task.
Then, per @tinkertrain comment, adding those Layouts to modal could be made in some another PR.

Thanks @jakubjanczyk and @plbabin
I think we can move forward with:

Creating a SimpleModal layout in HSDS
Moving the Avatar Selection Modal specific code to hs app ui and leave hs app as is 🤭 If it becomes an issue for whatever reason, it should be easy to port.

@jakubjanczyk Let me know if you want to create that layout (all you need is that ScrollableContainer PR to be released, which I will do today) or I can do tackle that, no problem

@jakubjanczyk One last thing to confirm before moving on with the above is to get design approval on using the "solid shadow" pattern instead of the "subtle gradient"

@tinkertrain Great! I can add it, but if you have available time, feel free to take it :smile: Feels quite straightforward and quick to add.
About the design confirmation - @alexestrada could you take a look? Details are in one of the previous comments. However, I think it wouldn't block moving the AvatarsSelectionModal to hs-app-ui either way, so I'll just go with it now and wait for the final confirmation before creating PR :)

@jakubjanczyk @tinkertrain I'm on board with using the solid shadow pattern — took a look at the PR and it looks great!

Closing this, as the component has been moved to hs-app-ui, here's the related PR: https://github.com/helpscout/hs-app-ui/pull/209


Fix RedshiftSQL Operator DAG failure

Instead of giving both resource type and client type, it works with only client type
Tested this change with both version
apache-airflow-providers-amazon==3.4.0 and latest apache-airflow-providers-amazon==4.1.0rc1

Looks good to me, but I have two asks:

Can you create a Zenhub ticket for this with appropriate description and link it under closes in the PR description
Can you also please test that the change works well with the RedshiftDataOperatorAsync DAG too?

Yeah sure

Changes made to RedshiftDataHook and RedshiftSQLHookAsync regarding the apache-airflow-providers-amazon==4.1.0rc1  rc image version changes in this PR

Looks good to me, but I have two asks:

Can you create a Zenhub ticket for this with appropriate description and link it under closes in the PR description
Can you also please test that the change works well with the RedshiftDataOperatorAsync DAG too?

Fixed and Tested for RedshiftDataOperatorAsync as well with apache-airflow-providers-amazon==4.1.0rc1 and apache-airflow-providers-amazon>=3.0.0


Sobel Edge detection

Script to perform Sobel Edge detection added
Updated README with the image after application of Canny Edge filter

Relates to issue #24

@smaranjitghose , I have added the progress bars using the tqdm library and also updated the README


[KYUUBI #3990] Support GetCatalogs for trino fe

Why are the changes needed?

Close https://github.com/apache/kyuubi/issues/3990
This pr aims to support GetCatalogs for trino fe.
How was this patch tested?

[x] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before make a pull request

cc @ulysses-you

thanks, merging to master