[Feature Request] Fall through pattern matching

Hi! I've noticed that ruta3 library which redux-saga-router is based on supports matching multiple patterns to one location. It can be useful when we want to have some general saga to be applied alongside detailed ones. For instance:
const routes = {
  '/profile/:id/': getProfileData,
  '/profile/:id/friends/': getProfileFriends,
  '/profile/:id/projects/': getProfileProjects,
}

It is easy to imagine, that on every subpage of /profile/:id we'd like to have some basic data fetched when visiting for the first time (e.g. username, photo, etc.) and also some detailed data.
I'd suggest adding such feature as an optional setting - and I am issuing a pull request for that.
BTW My pull request also includes updated README.md with detailed information on what patterns are available.

Hi, @TeoTN!
This looks like a potentially useful feature! Thanks for the issue and pull requests.
I'll review this issue and the PRs more thoroughly soon and get back to you. I may have some questions on this feature in particular that we'll need to discuss.

Thanks for the related PR @TeoTN. I wanted to keep the discussion around the feature in this issue.
The only downside I'm seeing is that we run the risk of rerunning a saga unnecessarily. I'm fuzzy on what the best experience needs to be here.
For example, assume you have the routes /foo and /foo/:id.
If you hit the /foo route first, then it runs obviously. Then, if you click a link to visit /foo/1, you'll run its saga but also force the /foo saga to run again. That may not be what you want, especially if the /foo saga makes an unnecessary HTTP request again. I'm wondering if this is the behavior we want, or if it makes sense to track currently matched routes to avoid rerunning them when the route changes. Therefore, if we go from /foo to /foo/1 it would know to only run the /foo/:id saga and not the /foo saga again.
Obviously, if you were on the /foo/1 route, visited a /bar route, and then came back to the /foo/1 route, then you would want the /foo and /foo/:id sagas to both run.
Does that make sense? What are your thoughts?

I think I see your point here but my assumption was that having set explicitly the fall-through behaviour we want to manually check whether we have to do such request at all. That is, higher-level saga (i.e. the one matched earlier) would check whether the state is incomplete.
In particular, there may exist a case where the programmer may be interested in having the request performed anyway, although I have difficulties with justifying it properly. What comes to my mind is such case: the /profile/ path is responsible for loading player up-to-date score, whereas /profile/settings would load his current name & surname (assuming that it wasn't already fetched) to fill the form. And if the score is subject to frequent changes on multiple devices and if we don't benefit (for any reason) from websockets then such additional request could be desirable.
Another story is that it'd be a kind of 'conditional fall through' which may be slightly confusing - the option would cause the matching to fall through all prefix-matches but if and only if the prefix has changed. (And what if we have multiple nested routes?)

Another story is that it'd be a kind of 'conditional fall through' which may be slightly confusing

I think at this time, it would be better to avoid the extra complexity as you mention. I may want to explore that behavior in the future, but let's keep it simple for now. We'll need to make sure devs are aware of that behavior, so they can write their sagas appropriately.
What are your thoughts on renaming the option, though? I'm not a huge fan of shouldFallThrough. What do you think of matchAll instead?

I like the matchAll, it's concise and clear :)

Released in v2.1.0. Thanks again, @TeoTN!


Fix: added test cases for Map:mouseEventToContainerPoint method.

Resolve #8379
Added two test cases for Map:mouseEventToContainerPoint method

Conflicts have been resolved.


FIX: Issue #41

According to discussion in Issue #41: fixed a blocker bug in loading a dump with filter view, added a new test about this case.

This change looks good to me, not sure why it's failing in Travis. I'll investigate and then probably merge soon.

The bug is caused by https://github.com/pouchdb/pouchdb/issues/4815 and is not your fault; I'll get on it and then merge this when green.

a99028a400584b480a1adabe707bad9a50d07d10

Thanks again, finally got around to fixing the build. :P


JUnit report's root attributes are always zero

Thanks for the fantastic work on this project. I just wanted to report that the JUnit generator has some missing bits that could be interpreted as false negatives by some parsers. The root element has "tests" and "failures" attributes set to zero always, regardless of the results. It could be easily fixed, though:
diff --git a/vacuum-report/junit.go b/vacuum-report/junit.go
index 3aa78ca..95019d1 100644
--- a/vacuum-report/junit.go
+++ b/vacuum-report/junit.go
@@ -60,6 +61,8 @@ func BuildJUnitReport(resultSet *model.RuleResultSet, t time.Time) []byte {

        parsedTemplate, _ := template.New("failure").Parse(tmpl)

+       gf, gtc := 0, 0 // global failure count, global test cases count.
+
        // try a category print out.
        for _, val := range cats {
                categoryResults := resultSet.GetResultsByRuleCategory(val.Id)
@@ -72,6 +75,7 @@ func BuildJUnitReport(resultSet *model.RuleResultSet, t time.Time) []byte {
                        _ = parsedTemplate.Execute(&sb, r)
                        if r.Rule.Severity == model.SeverityError || r.Rule.Severity == model.SeverityWarn {
                                f++
+                               gf++
                        }
                        tc = append(tc, &TestCase{
                                Name:      fmt.Sprintf("Category: %s", val.Id),
@@ -96,10 +100,14 @@ func BuildJUnitReport(resultSet *model.RuleResultSet, t time.Time) []byte {

                        suites = append(suites, ts)
                }
+
+               gtc += len(tc)
        }

        allSuites := &TestSuites{
                TestSuites: suites,
+               Tests:      gtc,
+               Failures:   gf,
        }

All PRs are welcome! Please feel free to submit this change and become part of the community!

Fixed in v0.11.0. This patch was applied manually.


[Enhancement] Support to batch drop partitions

Why I'm doing:
The current latest version lacks the functionality for batch deletion of partitions.
What I'm doing:
syntax:
alter table test.tbl1 DROP PARTITIONS IF EXISTS START("2021-02-01") END("2021-02-03") EVERY (INTERVAL 1 DAY);
alter table test.tbl1 DROP PARTITIONS IF EXISTS START("2021-02-01") END("2021-02-03") EVERY (INTERVAL 1 DAY) FORCE;
alter table test.tbl1 DROP PARTITIONS IF EXISTS (p20210201,p20210202)
alter table test.tbl1 DROP PARTITIONS IF EXISTS (p20210201,p20210202) FORCE

What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[x] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.3
[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

 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.yanglei0324 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.

@mergify rebase

@mergify rebase

@mergify backport branch-3.3

The doc  about this feature been merged to 3.3, but this feature is not.  So sad


wrong name for FractionalHex's Ulps

#[derive_float_eq(
    ulps_tol = "PointUlps",
    ulps_tol_derive = "Clone, Copy, Debug, PartialEq",
    debug_ulps_diff = "PointUlpsDebugUlpsDiff",
    debug_ulps_diff_derive = "Clone, Copy, Debug, PartialEq",
    all_tol = "f64"
)]
#[derive(Debug, Clone, Copy, PartialEq)]
pub struct FractionalHex {
...

closing.
fixed in version 0.2.1, and published.
tnx dude!


draw_line's antialiasing broken in 4.4 dev3

Tested versions

Reproducible in v4.4.dev3.official [f4af8201b]
Not reproducible in v4.4.dev2.official [97ef3c837]

System information
Godot v4.4.dev3 - Windows 10.0.19045 - Multi-window, 2 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3080 - 12th Gen Intel(R) Core(TM) i5-12400F (12 threads)
Issue description
When using draw_line to draw antialiased lines with a CanvasItem node with MSAA on, the antialiasing appears broken:

In 4.4dev2 and earlier versions:

I was also helping someone make a radar-like UI element, and this is how it looks on dev3:

The circles are antialiased correctly but the lines are not (it also looks correct on dev2). Without MSAA, it also looks correct
Steps to reproduce
I have this script that simply draws a line between two child Marker2D nodes:
@tool
extends Node2D

@export var width: float = 3.0

func _process(delta: float) -> void:
	queue_redraw()

func _draw() -> void:
	var children := find_children("", "Marker2D")
	if children.size() < 2:
		return
	draw_line(children[0].position, children[1].position, Color.WHITE, width, true)

In 4.4 dev2 it works as expected, but in dev3 it looks wrong
Minimal reproduction project (MRP)
lines.zip

This issue was already fixed in master by #98652

That's right! This will be fixed in dev 4
Closing as fixed by https://github.com/godotengine/godot/pull/98652


Update plugin-docker-slaves.yml

see https://issues.jenkins-ci.org/projects/HOSTING/issues/HOSTING-190 for details

:+1: but what I don't get is that seems you have released from your history. Did you just disable the deploy part to test it locally @ndeloof ?

You should be able to release in ~5 min Nicolas.

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project docker-slaves: Failed to deploy artifacts: Could not transfer artifact io.jenkins.plugins:docker-slaves:hpi:1.0.4 from/to maven.jenkins-ci.org (https://repo.jenkins-ci.org/releases/): Access denied to: https://repo.jenkins-ci.org/releases/io/jenkins/plugins/docker-slaves/1.0.4/docker-slaves-1.0.4.hpi, ReasonPhrase: Forbidden. -> [Help 1]

Actually I see the problem. I went too fast yesterday: you didn't suffix the path up to the artifactId @ndeloof

https://github.com/jenkins-infra/repository-permissions-updater/pull/72


Update "NIST IR" short code for series back to "NISTIR"

closes #12

@mico please see the discussion in #12 about this PR. Thanks.

@ronaldtse I updated the code, so it will parse "NISTIR" series code along with "NIST IR" code.

Thanks @mico !


[SPARK-7035] Encourage getitem over getattr on column access in the Python DataFrame API

Sorry for the mess, this time it should be OK

Can one of the admins verify this patch?

Thanks. This looks good. Merging it in now.

@rxin - Shouldn't this also be merged into branch-1.3?


TST: Less flakey tests

Fixes #350 by using flaky

I'm not sure whether this is the right way. The main reason for that kind of test is to prevent a major bug that prevents training. With these changes, it is too easy that if that bug were to happen, the test would still pass by accident (random fluctuations in score). Therefore, a reasonable margin should be set to make it very unlikely that the test passes accidentally.
Ideally, we would like to have a very high confidence that the model improved but that would probably require many runs/more data/longer training, all of which slow down testing. Using seeds everywhere is not enough because the results would still depend on the platform.
So maybe we should seriously consider libraries like flaky that would allow us to only rerun the test if it fails (though that would lower confidence in the results).

We are looking at this, will probably merge tomorrow.

Thank you.


Satellite normalisation

Normalisation introduced for satellite data utilising 2020 values for std and mean
Not entirely sure epsilon factor is truly necessary - yet left in as a safe guarding mechanism

I just re opened it to try and trigger the tests, but weirdly they dont seem to be running

Would you be able to pull main into this branch, and then add sat normalization to here too - https://github.com/openclimatefix/ocf-data-sampler/blob/main/ocf_data_sampler/torch_datasets/process_and_combine.py#L122


Modified links for documents

Hi, thanks for the awesome project !
I appreciate your maintenance and leading.
Description
When I click links for translated docs, it jumped to English page, and I modified it.
In addition to this, I added Japanese docs.

Issues about Japanese docs is related to #1484 and #1484 .

@jstarry it seems like we have improper redirects.
/docs/ja  properly directs to /docs/ja/intro/
but /docs/ja/ goes to /docs/en/intro/.

Some testing revealed that the offender here is actually a missing redirect.
/docs/:lang/ doesn't return a 301, it returns 200.
Because of the trailing slash it doesn't match any redirects, but because of the rewrite Firebase serves /index.html.
Our index file forwards to /docs/en/intro when loaded so that's why we end up there.
So two things:

We need to make sure that URLs with trailing slashes are still redirected
We should probably use a proper 404 page instead to avoid similar issues in the future

I found /docs/ja/ is redirected to /docs/en/intro but /docs/ja is to /docs/ja/intro.
You don't have to rewrite configs of Firebase.
Everything is OK with this.

Thanks, @komi1230. That's what I was trying to point out in my review.

Ah, I see. Thanks for advice.
I created each lang directory under /static/docs/ and enabled to match trailing slash.
Do you agree to this approach ?

@komi1230, please revert to the previous commit. That was enough to fix this issue.
We'll take care of updating the configuration and the rest.

Done.
Thanks for kind review.

Thanks for bringing this up!


"make ios" result in an error

When I try to do "make ios" i got this message :
make: *** [ios-framework] Error 1
cmake is version 3.7.0 and Xcode 8.1.
When i open tangram.xcodeproj in /build/ios-framework with Xcode and I build "ALL_BUILD" I got a build succeeded.
I tried to do "make cmake-ios" and the result is the same.

Does the solution of https://github.com/tangrams/tangram-es/issues/1042, fixes your issue?
gem install xcpretty

That's right, installing xcpretty solved this. Thanks.


Created getUnitSpikeFeatures and getUnitSpikeFeatureNames. Unimplemented

Added:
getUnitSpikeFeatures(self, unit_id, feature_name, start_frame=None, end_frame=None):
getUnitSpikeFeatureNames(self, unit_id):
They both throw unimplemented errors if not implemented and their implemenation is up to the discretion of the subclasses.

Looks good! I'll merge ;) Sure @magland would agree

Looks good. But I would propose a couple changes.
getUnitSpikeFeatureNames()

default return an empty list
do not take unit_id as input -- should return feature names across all the units.

I agree. I will commit and push this tomorrow.


Fix to send caddy into the http to run the ./bin/watch-*.sh [issue #17]

1. Why is this change necessary?
Because the script ./bin/watch-*.sh only have an http proxy installed.
2. What does this change do, exactly?
One has the choice whether Caddy should run in https or http mode.
3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
https://github.com/kellerkinderDE/devenv-shopware/issues/17
5. Checklist

[x] I have rebased my changes to remove merge conflicts
[ ] I have written or adjusted the documentation according to my changes

5. One more thing
Please decide if https should be the default or not?

@TumTum this change will be integrated in the next Version. Ive taken the liberty to refaktor it to our new caddy structure :) Thank you!


Add the log monitoring library/tool into application.

Add a log monitoring tool, such as log4j, to facilitate more effective debugging and troubleshooting.

logback.xml file is configured to print log into the console and export log into a file that will save in / logs folder.


TypeError: dataclass() got an unexpected keyword argument 'kw_only'

Just trying to start off simple to see how things work
from mlbstatsapi import Mlb

all_teams = Mlb.get_teams()

print(all_teams)

in running the above I get the error below:
Traceback (most recent call last):
  File "C:\Users\Matthew\PycharmProjects\MLB_data\main.py", line 2, in <module>
    from mlbstatsapi import Mlb
  File "C:\Users\Matthew\PycharmProjects\MLB_data\venv\lib\site-packages\mlbstatsapi\__init__.py", line 1, in <module>
    from .mlb_api import Mlb
  File "C:\Users\Matthew\PycharmProjects\MLB_data\venv\lib\site-packages\mlbstatsapi\mlb_api.py", line 6, in <module>
    from mlbstatsapi.models.people import Person, Player, Coach
  File "C:\Users\Matthew\PycharmProjects\MLB_data\venv\lib\site-packages\mlbstatsapi\models\people\__init__.py", line 2, in <module>
    from .people import Player, Coach, Person, Batter, Pitcher, DraftPick
  File "C:\Users\Matthew\PycharmProjects\MLB_data\venv\lib\site-packages\mlbstatsapi\models\people\people.py", line 163, in <module>
    @dataclass(kw_only=True)
TypeError: dataclass() got an unexpected keyword argument 'kw_only'

@VermiThrax423 which Python version are you using?
kw_only is introduced with Python 3. If you are using Python 2, that could be one reason for the output.

Python 3.10+ will resolve this issue.

I was still using 3.9, I installed 3.10 and 3.11 and was able to get it to work with 3.10. I appreciate the time, still kind of new to all of this and trying to use something else I love to help me grow my skill base!


[Server] codegen-server support for restXml (S3)

Signed-off-by: Guy Margalit<EMAIL_ADDRESS>Motivation and Context
See #903
The motivation is to implement the server protocol code for the s3d-rs crate - still draft code in the project but the idea is to provide an S3 gateway for edge devices that handles disconnections and caching transparently. See: https://github.com/s3d-rs/s3d
Description
This PR adds generated server code for restXml protocol types as mentioned by @crisidev in the related issue.
Please keep in mind that I am quite new to this project and to kotlin, and I would be happy to get your review and fix anything that you may suggest.
Testing
Added the S3 model namespace to the "blocklist" in ServerProtocolTestGenerator.kt because the server protocol is not fully implemented.
Checklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

you may want to install pre-commit, then run pre-commit install to pick up our pre-commit hooks (including Kotlin autoformatters)

thanks @rcoh - updated the PR with pre-commit

The CI is failing. It is important that ./gradlew :codegen-server-test:test succeeds in your local build.
It is likely some of the protocol tests we generate are not working for restXml or for the S3 model you are using. I suggest you to add the S3 model namespace to the blocklist defined in the protocol tests. You can add another check to the if condition. This is, again, because we are still working on finishing the implementation of our first protocol 😃

Hi @crisidev
So I would like to ask for some help with the current failures in the test, below is what I got locally.
The first seem simple that we don't get the <?xml tag. The other are because the bucket parsing doesn't work for some reason. Any ideas of where to look would help a lot.
There are still a couple of open questions on the changes that might affect the client codegen, that I could use your help to tag someone to review.
Thanks!

(and for your own context, the diff and doc preview tools unfortunately rely on this being a PR directly to the repo which is why they're failing We hopefully will get those setup as something standalone at some point)

should I rebase?

Rebase done, let's wait for the CI.

I am pretty sure there will still be a lot of things to tweak in both restJson and RestXml, but this is a great start! Thanks @guymguym for the help, we really appreciate it.

no problem @crisidev I will be happy to look for more opportunities to contribute

And thank you for the super fast responses and helpful approach. Same goes to @rcoh.


Control a Flying Wing

Hello!
I have a  question:
My vehicle is a flying wing. So in your documentation, the setpoints can only be set with x,y,z,yaw. Can't I control the pitch and roll angle?
Thank you!!

Not with the current implementation. You will need to check if the flight controller supports such setpoint or not in the first place. If yes, and it has a mavlink interface, then you can add it to MATMAV.

hey thanks for your answer! i am using the pixhawk 2.1 cube. is this possible? sorry i am pretty new in this hole thing and still learning. how can i add a mavlink into your matmav? isn't mavlink written in C++?

and my vehicle is a skywalker x8


Docker installation do not work

metabase/metabase-head:latest
no app folder in it, only bin and target
metabase/metabase
no app/pplugins folder, clickhouse plugin one in this folder and there is no clickohouse in database type drop down

Which version of metabase is working with this tutorial?

Hi @HKFiliatix I just updated the README for the Docker operations. I tested both methods successfully.


Generic

This PR demonstrates the changes required in order to use the generic data structures (and ICMP set) in https://github.com/np-guard/models/pull/33. 95% of the changes are renaming, but some are related to the introduction of a dedicated ICMP set.
Some tests still do not pass, due to an issue with tracking statefulness (which IMO should be part of this repo and not np-guard/models).
The line replace github.com/np-guard/models => ../models in go.mod is useful for local experimentation until https://github.com/np-guard/models/pull/33 is merged.

Updated to accommodate #634.
The tests cannot pass in github. Locally:

Some tests are updated to explicitly state the only code in ICMP types that have only single code.
Two tests fail due to what seems like an inconsistent ordering of partitions. It might be a good idea to use ordered maps instead of hash maps.

Okay, now all the tests pass. The issue was the use of CartesianRightTriple instead of CartesianLeftTriple when partitioning TCPUDPSet. The decision is currently at the library side, but it should probably move to the client side.


Report to save Excel from SALV (without displaying it): what is the recommended way?

Hello,
This use case is quite common: I want to enhance an SALV report with the ability to download an Excel instead of displaying it (similar to the output radiobutton option in the demo programs).
I don't believe I'm the first one to try it and I would like to know what everyone do.
Best attempt
My best attempt is the following.
sy-batch = abap_true.
data(excel) = new zcl_excel( ).
data(worksheet) = result->get_active_worksheet( ).
worksheet->bind_alv(
    io_alv      = salv
    it_table    = table  ).

sy-batch = abap_false.
data(writer)     = cast zif_excel_writer( new zcl_excel_writer_2007( ) ).
data(excel_xstring) = writer->write_file( excel ).

advantages:

I avoid the infamous OBJECTS_OBJREF_NOT_ASSIGNED dump on CL_SALV_TABLE->GET_METADATA
the excel columns match what is defined in layout
subtotals are displayed

inconvenient:

I don't have filter

second best
cl_salv_bs_runtime_info=>set(
  exporting
    display        = abap_false
    metadata       = abap_true
    data           = abap_true ).
salv->display( ).

data(excel) = new zcl_excel( ).
data(worksheet) = result->get_active_worksheet( ).
worksheet->bind_alv(
    io_alv      = salv
    it_table    = table  ).

data(writer)     = cast zif_excel_writer( new zcl_excel_writer_2007( ) ).
data(excel_xstring) = writer->write_file( excel ).

Inconvenient:

I don't have neither filter, nor hidden columns or subtotals from the layout (From what I understand, the layout options have not been applied to the internal SALV fieldcatalog when ZCL_EXCEL_CONVERTER_SALV_TABLECP=>LOAD_DATA does not take layout).

Thanks,
PS: I promise I'll PR a doc page with the outcome of the discussion.

Hello @AlexandreHT. I think that the second option would be the recommended one. I can reproduce the issue with the filter (via ZDEMO_EXCEL32 and button "Excel bind"). I don't reproduce the issue of hidden columns and totals (manual filter on column "booking = 1" and totals on column "amount", via ZDEMO_EXCEL32 and button "Excel bind"). Could you provide a case to reproduce your issue please? Thank you.

Hi,
In order to reproduce the issue of hidden columns and totals, with ZDEMO_EXCEL32, please :

add the following code before lo_salv->display() :

  data(layout) = lo_salv->get_layout( ).
  layout->set_key( value salv_s_layout_key( report = sy-repid ) ).
  layout->set_save_restriction( if_salv_c_layout=>restrict_none ).
  layout->set_default( abap_true ).

execute ZDEMO_EXCEL32, hide some columns and total some other, save the layout as default
replace lo_salv->display() with the following code:

*  lo_salv->display( ).
  cl_salv_bs_runtime_info=>set(
    exporting
      display        = abap_false
      metadata       = abap_true
      data           = abap_true ).
  lo_salv->display( ).

  data(excel)     = new zcl_excel( ).
  data(worksheet) = excel->get_active_worksheet( ).
  worksheet->bind_alv(
      io_alv      = lo_salv
      it_table    = gt_sbook  ).

  data(writer)        = cast zif_excel_writer( new zcl_excel_writer_2007( ) ).
  data(excel_xstring) = writer->write_file( excel ).
  data(bytecount)     = xstrlen( excel_xstring ).
  data(filename)      = lv_default_file_name.
  data path     type string.
  data fullpath type string.

  data(raw_data) = cl_bcs_convert=>xstring_to_solix( excel_xstring ).

  cl_gui_frontend_services=>file_save_dialog(
    exporting
*        window_title              =     " Window Titlez
*        default_extension         =     " Default Extension
*        default_file_name         =
*        with_encoding             =
*        file_filter               =     " File Type Filter Table
*        initial_directory         =     " Initial Directory
      prompt_on_overwrite       = abap_true
    changing
        filename                  = filename               " File Name to Save
        path                      = path                   " Path to File
      fullpath                  = fullpath                 " Path + File Name
*        user_action               = user_action            " User Action (C Class Const ACTION_OK, ACTION_OVERWRITE etc)
*        file_encoding             =
    exceptions
      cntl_error                = 1
      error_no_gui              = 2
      not_supported_by_gui      = 3
      invalid_default_file_name = 4
      others                    = 5 ).
  if sy-subrc <> 0.
    message id sy-msgid type sy-msgty number sy-msgno
               with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
  endif.

  cl_gui_frontend_services=>gui_download(
    exporting
      bin_filesize = bytecount
      filename     = fullpath
      filetype     = 'BIN'
    changing
      data_tab     = raw_data
    exceptions
      file_write_error          = 1
      no_batch                  = 2
      gui_refuse_filetransfer   = 3
      invalid_type              = 4
      no_authority              = 5
      unknown_error             = 6
      header_not_allowed        = 7
      separator_not_allowed     = 8
      filesize_not_allowed      = 9
      header_too_long           = 10
      dp_error_create           = 11
      dp_error_send             = 12
      dp_error_write            = 13
      unknown_dp_error          = 14
      access_denied             = 15
      dp_out_of_memory          = 16
      disk_full                 = 17
      dp_timeout                = 18
      file_not_found            = 19
      dataprovider_exception    = 20
      control_flush_error       = 21
      not_supported_by_gui      = 22
      error_no_gui              = 23
      others                    = 24 ).
  if sy-subrc <> 0.
    message id sy-msgid type sy-msgty number sy-msgno
               with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
  endif.

Execute ZDEMO_EXCEL32

=> no hidden columns and no total.

@AlexandreHT Thank you very much. I reproduced the problem. The program below can be used to reproduce the same as you proposed:

Run it with ALV_ONLY selected, hide some columns and total some other, save the layout as default
Run it with BINDONLY selected => no hidden columns and no total.
Run it with BIND_ALV selected => columns are hidden and total is shown.

I did some debug to understand what happens but it's a little bit complex. I will investigate further in the next days.
REPORT.
CONSTANTS gc_save_file_name TYPE string VALUE 'issue-745.xlsx'.
INCLUDE zdemo_excel_outputopt_incl.
PARAMETERS alv_only RADIOBUTTON GROUP rb2 DEFAULT 'X'.
PARAMETERS bindonly RADIOBUTTON GROUP rb2.
PARAMETERS alv_bind RADIOBUTTON GROUP rb2.
START-OF-SELECTION.
  SELECT * FROM sbook UP TO 15 ROWS
  INTO TABLE @DATA(gt_sbook).
  TRY.
      cl_salv_table=>factory(
        EXPORTING
          list_display = abap_false
        IMPORTING
          r_salv_table = DATA(lo_salv)
        CHANGING
          t_table      = gt_sbook[] ).
      cl_salv_bs_runtime_info=>clear_all( ).
      DATA(layout) = lo_salv->get_layout( ).
      layout->set_key( VALUE salv_s_layout_key( report = sy-repid ) ).
      layout->set_default( abap_true ).
      layout->set_save_restriction( if_salv_c_layout=>restrict_none ).
      IF alv_only = abap_true OR alv_bind = abap_true.
        lo_salv->get_functions( )->set_all( ).
        lo_salv->display( ).
      ENDIF.
      IF bindonly = abap_true OR alv_bind = abap_true.
        cl_salv_bs_runtime_info=>clear_all( ).
        cl_salv_bs_runtime_info=>set(
          EXPORTING
            display  = abap_false
            metadata = abap_true
            data     = abap_true ).
        lo_salv->display( ).
        DATA(excel)     = NEW zcl_excel( ).
        DATA(worksheet) = excel->get_active_worksheet( ).
        worksheet->bind_alv(
            io_alv   = lo_salv
            it_table = gt_sbook  ).
        lcl_output=>output( excel ).
      ENDIF.
    CATCH cx_root INTO DATA(lx).
      MESSAGE lx TYPE 'I' DISPLAY LIKE 'E'.
  ENDTRY.


Support null safety

Hi @rxlabz , do you have any plans to migrate this package to null safety? Looking to migrate my app and this is a blocker atm.

Hi @ethanblake4 , I wasn't sure that someone is using it :)
Cyclop is now "null safe" ! #9


Best model checkpoint allows metrics to be equal to previous best if at least one metric improves

closes #7286
Proposed changes:

Allow for equal metrics if at least one metric improves, do not allow for any metric to decrease.
Also add a test to warn users if they opt for best model checkpoint but do not allow for any examples to be used for validation and/or specify that validation should not occur, or only occur at the very end of training.

Status (please check what you already did):

[X] added some tests for the functionality
[ ] ~updated the documentation~
[X] updated the changelog (please check changelog for instructions)
[X] reformat files using black (please check Readme for instructions)

@samsucik sorry, this is the PR that never ends. Just occurred to me I tagged this as a bug in the changelog bc it was tagged as such in the issue, but now that I think about it, not sure if this is actually a bug or really an improvement. If the former, I'd retarget 2.7.x, if the latter I'd change the changelog. What do you think?

@wochinge I actually had to make a new PR because this one had targeted the wrong branch. I'm sorry for the confusion, I should have closed this one. The new PR (targeting 2.7.x) was merged in yesterday. I would like to apply your comments, can I just make a new PR from 2.7.x with just these comments and tag you as a reviewer?
Also, for future reference, enable was automatically tagged as a reviewer when I changed the base branch. Should I have added enable as a reviewer myself when I made the new PR? I thought these files were mostly our area (ted, diet, callback, train_utils..)

can I just make a new PR from 2.7.x with just these comments and tag you as a reviewer?

Yes please
Mhm, interesting. Apparently CODEOWNERS only protects main at the moment 🤔

@wochinge oh that would probably be the wonkiness arising from switching the base branch... Sorry for this mess again, I promise I have learned for the future.

no worries 😄 Having to switch the base branch happens all the time to me (GitHub is sometimes quite weird about it, too) 😆


Variation Reference Methods

Pulls some features of both the References and Variants data models into the existing variationReference.avdl, and adds a variationreferencemethods.avdl to define an API for it.

Closing this since we have #238 in now.


fix(zod): treat additionalProperties keyword

Status
READY
Description
tl;dr: additionalProperties: true isn't treated the right way during schema parsing, which results in runtime error during generation. Since #972 is stalled, decided to dig into it myself.
Related PRs
Previous attempt to fix this:

branch
PR

CxGarcia:fix/zod-additional-properties
link

Also, couldn't help but fix few typos here and there.

@TommoLeedsy can you review this also? Its related to other recent zod changes

@ixth in this other PR that has been open for a long time: https://github.com/anymaniax/orval/pull/972 he used zod.passthrough()?  not sure if your solution is better than what he was trying to do?

@melloware
Can't tell right away, have to check it more thoroughly, but I assume these two points:

additionalProperties: {} works just fine, additionalProperties: true is an alias for it, and must behave the same way, i.e. generate z.record(z.string(), z.any())
z.passthrough() is a parsing directive, and it doesn't affect inferred types, so it won't work in cases when I want to use z.infer on generated type. I might add a test case for that.

Awesome thanks for the answers @ixth

@melloware @ixth
Hey, it seemed to me that this response wasn't exactly the same as what you're trying to do with #972.
In other words, it is possible to do both. Here we will modify it so that additionalProperties works, but in #972 we will use zod to make it easier to handle properties, right? What do you guys think?

In other words, it is possible to do both.
As soon as additionalProperties: true will result in z.record(z.string(), z.any()), there will be no need to add .passthrough(): any fields with string key will be allowed and passed through.

I might not get the whole picture. What cases am I missing?

@ixth
I got it. It looks good. There is no specific case, it's just that I have doubts, so it's okay.

@soartec-lab i am going to merge as this is the correct solution and @ixth pointed out why the previous PR was actually incorrect.

Gotcha!


Support managed-idendity for aad-starter

azure-spring-boot-starter-keyvault-secret and azure-spring-boot-starter-keyvault-certificates support managed identity.
azure-spring-boot-starter-active-directory does not support managed identity,
Need to investigate whether it's possible to support managed identity in azure-spring-boot-starter-active-directory, if it's possible, user do not need to configure client-id and client-secret to use azure-spring-boot-starter-active-directory .
My current understanding is that client-id and client-secret is required according to current code.
Maybe we can extract client-id and client-secret from managed identity?

Is this a reasonable feature for the AAD starter?

@saragluna
I need more investigation. Now I'm not familiar with managed-identity.

Hi, @idg-sam .
Is this a reasonable feature-request?

Hi @chenrujun  ,
Yes, obtaining secrets/certs through key vault using managed identity is an important feature. In our app service deployment samples, we strongly encourage developers to use it. I don't have any strong opinions on how the feature should be made available, but I do have some questions for you to consider.
As your initial comment says, azure-spring-boot-starter-keyvault-secret and azure-spring-boot-starter-keyvault-certificates can be used with managed identity to get secrets/certs.
Is it currently possible to set the relevant secret/cert configuration in AAD spring boot starter client library at runtime, after obtaining the value by utilizing a key vault boot starter ?

If yes, then:

Is there a need for a new feature? Assuming the developer can run something like the pseudo-code below, before AADWebAppConfiguration.createClientBuilder() executes:// pseudo-code.
void onProgramStartupOrBeforeAADStarterInitialization() {
    // assuming the application utilizes Key Vault boot starter or something similar:
    properties.set( "azure.activedirectory.client-secret", keyVaultClient.getSecret("CLIENT_SECRET");
}

If not, then:

Should we surface a way for the developer to set the Azure AD boot starter client configuration values programatically at run time? To allow the dev the option to implement some version of the above.

In both cases (yes and no):

Should we consider automating the above process for the developer? For example, using some configuration property that tells the AAD boot starter to get secret or cert or other from vault.

Hi, @idg-sam

Is it currently possible to set the relevant secret/cert configuration in AAD spring boot starter client library at runtime, after obtaining the value by utilizing a key vault boot starter ?

Yes, it's possible.

If yes, then: Is there a need for a new feature?

Save client-id client-secret in keyvault.
Get the client-id client-secret from keyvault, then config aad-starter

This feature is already implemented.
My question is that can we avoid using client-id and client secret in keyvault, just get the value from managed-identity?

In both cases (yes and no):
Should we consider automating the above process for the developer? For example, using some configuration property that tells the AAD boot starter to get secret or cert or other from vault.

It's already implemented, just use aad-starter and keyvault-starter at the same time.

Hi @chenrujun ,

My question is that can we avoid using client-id and client secret in keyvault, just get the value from managed-identity?

I see. That's not a use-case that I am familiar with. I was under the impression that MI's main role was to help obtain secrets from AzureKV.
Do you know of an example of using MI directly for obtaining secrets, without using AzureKV?

@idg-sam

Do you know of an example of using MI directly for obtaining secrets, without using AzureKV?

No. I don't know this kind of example.
Now I'm not sure whether it's an possible feature.
This feature is required by a customer.

Closing this issue, because we decide to deprecate azure-spring-boot-starter-active-directory. Just write sample to demonstrate how to use Azure Active Directory in Spring Boot application in this repo: https://github.com/Azure-Samples/spring-boot-application-with-azure-active-directory
Refer to this issue to track this task: https://github.com/Azure-Samples/spring-boot-application-with-azure-active-directory/issues/10


Tournament profile still has access to fence

Fence should be inaccessible. As per profiles lockedByDefaultOverride profiles.json value

Originally written by chomp

Taking a look at this

Originally written by TetrisGG


Compute and store uncompressed file size information.

Currently, our file ingestors read the file size, but if the file is compressed, this is only the compressed size and the file may end up being much larger in memory.
Different file types have different ways to get the decompressed file size. It may involve some spelunking since it doesn't appear to be natively supported at at the fsspec level. In the interim, we may also want to estimate the decompressed file size by multiplying by common compression ratios.

Closing for inactivity


Google OAuth user email broken

Google OAuth user email API no longer works and needs updating. See more here:
https://github.com/grokify/oauth2more/issues/1

Fixed in fb8d74991c94c0c705f37559339600ba5df496e1


Object_detection_video.py:  ImportError: DLL load failed: The specified module could not be found.

Basically have made it through the whole tutorial but get the following error when trying to run any of the object_detection_###.py scripts from IDLE. The error looks similar to what the video shows when the script is run from the desktop, but I have made sure to open IDLE from the cmd prompt with the tensorflow1 conda environment activated.
Has anyone found a fix or run into this problem running the object detection scripts?

RESTART: C:\tensorflow1\models\research\object_detection\Object_detection_video.py
Traceback (most recent call last):
File "C:\tensorflow1\models\research\object_detection\Object_detection_video.py", line 21, in
import cv2
File "C:\Anaconda3\envs\tensorflow1\lib\site-packages\cv2_init_.py", line 3, in
from .cv2 import *
ImportError: DLL load failed: The specified module could not be found.

EDIT: Could it be that IDLE is not defaulting to the Anaconda version of python?

Could someone please help me with this? Any advice would be much appreciated. I get this error for both the "Object_detection_image.py" file AND the "Object_detection_video.py" files.

after many grueling hours working on this, the solutions here worked:
https://www.researchgate.net/post/How_to_import_cv2_into_anaconda_spyder_Python_36
Download these files and restart your computer:
https://www.microsoft.com/en-us/software-download/mediafeaturepack
Good luck to you, hopefully this helps someone.

I occurred the same problem. I solved it by following the appendix & reinstalling jupyter notebook in the working conda envs.
Hope it helps.


Invert resource copy switch names and behavior

Change this to -r, --resource-copy-verbose and default to being quiet

Got rid of resource-copy-* verbosity switches altogether.


[CentOS 7.7]Failed connection after "VNC serving server init"

I try to install xrdp on CentOS Linux release 7.7.1908 (Core)
But VNC is stopped after "VNC receiving server init"
Is there any workaround for passing this problem?
My Instruction is
sudo yum install tigervnc-server
wget http://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
rpm -ivh epel-release-latest-7.noarch.rpm
sudo yum install xrdp
sudo systemctl start xrdp
sudo systemctl enable xrdp

From seeing the code, It seems error coming from following code.
https://github.com/neutrinolabs/xrdp/blob/v0.9.14/vnc/vnc.c#L2074-L2097

from /var/log/xrdp.log

[20201210-14:14:38] [INFO ] xrdp_wm_log_msg: login successful for display 13
[20201210-14:14:38] [DEBUG] Layout from client_info (geom=1920x1080 #screens=1) : 0:(1920x1080+0+0)
[20201210-14:14:38] [DEBUG] xrdp_wm_log_msg: VNC started connecting
[20201210-14:14:39] [DEBUG] xrdp_wm_log_msg: VNC connecting to <IP_ADDRESS> 5913
[20201210-14:14:39] [DEBUG] xrdp_wm_log_msg: VNC tcp connected
[20201210-14:14:39] [DEBUG] xrdp_wm_log_msg: VNC security level is 2 (1 = none, 2 = standard)
[20201210-14:14:40] [DEBUG] xrdp_wm_log_msg: VNC password ok
[20201210-14:14:40] [DEBUG] xrdp_wm_log_msg: VNC sending share flag
[20201210-14:14:40] [DEBUG] xrdp_wm_log_msg: VNC receiving server init
[20201210-14:14:41] [DEBUG] VNC error before receiving pixel format
[20201210-14:14:41] [DEBUG] VNC error before receiving name length
[20201210-14:14:41] [DEBUG] VNC error before receiving name
[20201210-14:14:41] [DEBUG] xrdp_wm_log_msg: VNC error - problem connecting
[20201210-14:14:41] [DEBUG] Closed socket 19 (AF_INET <IP_ADDRESS>:57178)
[20201210-14:14:41] [DEBUG] xrdp_wm_log_msg: some problem
[20201210-14:14:42] [DEBUG] xrdp_mm_module_cleanup
[20201210-14:14:42] [DEBUG] VNC mod_exit
[20201210-14:14:42] [DEBUG] Closed socket 18 (AF_INET <IP_ADDRESS>:48060)

The Log of following output but over 400 lines so I omit it
sudo journalctl -S hh:mm:ss

Hi @sakaia
On CentOS 7, you'll need to install the xrdp-selinux RPM if you're using SELinux. I don't think this is causing your problem directly, but it's something else to be aware of.
That log you've omitted will be very useful. Can you please send it? If you don't want to paste it inline, you can attach it as a file. Or you can use a drop-down. I've taken the liberty of editing your comment above to use one as an example. If you click on the three dots (...) and press edit you'll be able to see how to do this.

Thanks I attach journalctl output
-- Logs begin at Mon 2020-11-30 08:39:19 JST, end at Fri 2020-12-11 14:38:30 JST. --
Dec 11 14:36:52 centosserver sshd[22767]: PAM unable to dlopen(/usr/lib64/security/pam_tally.so): /usr/lib64/security/pam_tally.so: cannot open shared object file: No such file or directory
Dec 11 14:36:52 centosserver sshd[22767]: PAM adding faulty module: /usr/lib64/security/pam_tally.so
Dec 11 14:36:52 centosserver sshd[22767]: Accepted password for sakaia from <IP_ADDRESS> port 58538 ssh2
Dec 11 14:36:52 centosserver systemd-logind[1915]: New session 283 of user sakaia.
Dec 11 14:36:52 centosserver systemd[1]: Started Session 283 of user sakaia.
Dec 11 14:36:52 centosserver sshd[22767]: pam_unix(sshd:session): session opened for user sakaia by (uid=0)
Dec 11 14:36:53 centosserver ovn-controller[2279]: ovs|132902|patch|ERR|Dropped 4 log messages in last 13 seconds (most recently, 5 seconds ago) due to excessive rate
Dec 11 14:36:53 centosserver ovn-controller[2279]: ovs|132903|patch|ERR|bridge not found for localnet port 'provnet-1557936b-0a1d-41e3-bd7c-3bf17c4f276d' with network name 'extnet'
Dec 11 14:37:05 centosserver xrdp[25955]: (25955)(139769087891904)[INFO ] Socket 12: AF_INET connection received from <IP_ADDRESS> port 61106
Dec 11 14:37:05 centosserver xrdp[25955]: (25955)(139769087891904)[DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:05 centosserver xrdp[22796]: (22796)(139769087891904)[DEBUG] Closed socket 11 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:06 centosserver xrdp[22796]: (22796)(139769087891904)[INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
Dec 11 14:37:06 centosserver xrdp[22796]: (22796)(139769087891904)[INFO ] Using default X.509 key file: /etc/xrdp/key.pem
Dec 11 14:37:06 centosserver xrdp[22796]: (22796)(139769087891904)[WARN ] TLSv1.3 enabled by config, but not supported by system OpenSSL
Dec 11 14:37:06 centosserver xrdp[22796]: (22796)(139769087891904)[DEBUG] TLSv1.2 enabled
Dec 11 14:37:06 centosserver xrdp[22796]: (22796)(139769087891904)[DEBUG] Security layer: requested 11, selected 1
Dec 11 14:37:06 centosserver xrdp[22796]: (22796)(139769087891904)[DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:06 centosserver xrdp[25955]: logging configuration:
Dec 11 14:37:06 centosserver xrdp[25955]: LogFile:       /var/log/xrdp.log
Dec 11 14:37:06 centosserver xrdp[25955]: LogLevel:      4
Dec 11 14:37:06 centosserver xrdp[25955]: EnableSyslog:  1
Dec 11 14:37:06 centosserver xrdp[25955]: SyslogLevel:   4
Dec 11 14:37:06 centosserver xrdp[25955]: [20201210-12:09:41] [INFO ] starting xrdp with pid 25955
Dec 11 14:37:06 centosserver xrdp[25955]: [20201210-12:09:41] [INFO ] address [<IP_ADDRESS>] port [3389] mode 1
Dec 11 14:37:06 centosserver xrdp[25955]: [20201210-12:09:42] [INFO ] listening to port 3389 on <IP_ADDRESS>
Dec 11 14:37:06 centosserver xrdp[25955]: [20201210-12:09:42] [INFO ] xrdp_listen_pp done
Dec 11 14:37:06 centosserver xrdp[25955]: [20201210-13:27:35] [INFO ] Socket 12: AF_INET connection received from <IP_ADDRESS> port 42664
Dec 11 14:37:06 centosserver xrdp[25955]: [20201210-13:27:35] [DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:06 centosserver xrdp[25955]: [20201210-13:27:40] [INFO ] Socket 12: AF_INET connection received from <IP_ADDRESS> port 30831
Dec 11 14:37:06 centosserver xrdp[25955]: [20201210-13:27:40] [DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:06 centosserver xrdp[25955]: [20201210-13:27:43] [INFO ] Socket 12: AF_INET connection received from <IP_ADDRESS> port 57764
Dec 11 14:37:06 centosserver xrdp[25955]: [20201210-13:27:43] [DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:06 centosserver xrdp[25955]: [20201210-13:30:55] [INFO ] Socket 12: AF_INET connection received from <IP_ADDRESS> port 60679
Dec 11 14:37:06 centosserver xrdp[25955]: [20201210-13:30:56] [DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:06 centosserver xrdp[25955]: [20201210-13:31:01] [INFO ] Socket 12: AF_INET connection received from <IP_ADDRESS> port 60682
Dec 11 14:37:06 centosserver xrdp[25955]: [20201210-13:31:01] [DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:06 centosserver xrdp[25955]: [20201210-13:34:51] [INFO ] Socket 12: AF_INET connection received from <IP_ADDRESS> port 37738
Dec 11 14:37:06 centosserver xrdp[25955]: [20201210-13:34:51] [DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:06 centosserver xrdp[25955]: [20201210-13:34:58] [INFO ] Socket 12: AF_INET connection received from <IP_ADDRESS> port 38405
Dec 11 14:37:06 centosserver xrdp[25955]: [20201210-13:34:58] [DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:06 centosserver xrdp[25955]: [20201211-14:34:39] [INFO ] Socket 12: AF_INET connection received from <IP_ADDRESS> port 61095
Dec 11 14:37:06 centosserver xrdp[25955]: [20201211-14:34:39] [DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:06 centosserver xrdp[25955]: [20201211-14:34:51] [INFO ] Socket 12: AF_INET connection received from <IP_ADDRESS> port 61099
Dec 11 14:37:06 centosserver xrdp[25955]: [20201211-14:34:51] [DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:06 centosserver xrdp[25955]: [20201211-14:37:05] [INFO ] Socket 12: AF_INET connection received from <IP_ADDRESS> port 61106
Dec 11 14:37:06 centosserver xrdp[25955]: [20201211-14:37:05] [DEBUG] Closed socket 11 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:06 centosserver xrdp[25955]: [20201211-14:37:06] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
Dec 11 14:37:06 centosserver xrdp[25955]: [20201211-14:37:06] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
Dec 11 14:37:06 centosserver xrdp[25955]: [20201211-14:37:06] [WARN ] TLSv1.3 enabled by config, but not supported by system OpenSSL
Dec 11 14:37:06 centosserver xrdp[25955]: [20201211-14:37:06] [DEBUG] TLSv1.2 enabled
Dec 11 14:37:06 centosserver xrdp[25955]: [20201211-14:37:06] [DEBUG] Security layer: requested 11, selected 1
Dec 11 14:37:06 centosserver xrdp[25955]: ssl_tls_accept: TLS connection accepted
Dec 11 14:37:06 centosserver xrdp[25955]: ssl_tls_print_error: SSL_read: I/O error
Dec 11 14:37:06 centosserver xrdp[25955]: libxrdp_force_read: header read error
Dec 11 14:37:06 centosserver xrdp[25955]: xrdp_process_main_loop: libxrdp_process_incoming failed
Dec 11 14:37:06 centosserver xrdp[25955]: got XRDP SIGPIPE(13)
Dec 11 14:37:06 centosserver xrdp[25955]: got XRDP SIGPIPE(13)
Dec 11 14:37:06 centosserver xrdp[25955]: ssl_tls_print_error: SSL_shutdown: I/O error
Dec 11 14:37:06 centosserver xrdp[25955]: [20201211-14:37:06] [DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:06 centosserver xrdp[25955]: xrdp_mcs_disconnect - socket closed
Dec 11 14:37:08 centosserver ovn-controller[2279]: ovs|132904|patch|ERR|Dropped 2 log messages in last 10 seconds (most recently, 5 seconds ago) due to excessive rate
Dec 11 14:37:08 centosserver ovn-controller[2279]: ovs|132905|patch|ERR|bridge not found for localnet port 'provnet-1557936b-0a1d-41e3-bd7c-3bf17c4f276d' with network name 'extnet'
Dec 11 14:37:09 centosserver xrdp[25955]: (25955)(139769087891904)[INFO ] Socket 12: AF_INET connection received from <IP_ADDRESS> port 61107
Dec 11 14:37:09 centosserver xrdp[25955]: (25955)(139769087891904)[DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:09 centosserver xrdp[22797]: (22797)(139769087891904)[DEBUG] Closed socket 11 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:09 centosserver xrdp[22797]: (22797)(139769087891904)[INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
Dec 11 14:37:09 centosserver xrdp[22797]: (22797)(139769087891904)[INFO ] Using default X.509 key file: /etc/xrdp/key.pem
Dec 11 14:37:09 centosserver xrdp[22797]: (22797)(139769087891904)[WARN ] TLSv1.3 enabled by config, but not supported by system OpenSSL
Dec 11 14:37:09 centosserver xrdp[22797]: (22797)(139769087891904)[DEBUG] TLSv1.2 enabled
Dec 11 14:37:10 centosserver xrdp[22797]: (22797)(139769087891904)[DEBUG] Security layer: requested 11, selected 1
Dec 11 14:37:10 centosserver xrdp[22797]: (22797)(139769087891904)[INFO ] connected client computer name: VPC-O08P1080096
Dec 11 14:37:10 centosserver xrdp[22797]: (22797)(139769087891904)[INFO ] adding channel item name rdpdr chan_id 1004 flags 0x80800000
Dec 11 14:37:10 centosserver xrdp[22797]: (22797)(139769087891904)[INFO ] adding channel item name rdpsnd chan_id 1005 flags 0xc0000000
Dec 11 14:37:10 centosserver xrdp[22797]: (22797)(139769087891904)[INFO ] adding channel item name cliprdr chan_id 1006 flags 0xc0a00000
Dec 11 14:37:10 centosserver xrdp[22797]: (22797)(139769087891904)[INFO ] adding channel item name fcchan chan_id 1007 flags 0x80000000
Dec 11 14:37:11 centosserver xrdp[22797]: (22797)(139769087891904)[INFO ] adding channel item name drdynvc chan_id 1008 flags 0xc0800000
Dec 11 14:37:11 centosserver xrdp[22797]: (22797)(139769087891904)[INFO ] TLS connection established from <IP_ADDRESS> port 61107: TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384
Dec 11 14:37:11 centosserver xrdp[25955]: logging configuration:
Dec 11 14:37:11 centosserver xrdp[25955]: LogFile:       /var/log/xrdp.log
Dec 11 14:37:11 centosserver xrdp[25955]: LogLevel:      4
Dec 11 14:37:11 centosserver xrdp[25955]: EnableSyslog:  1
Dec 11 14:37:11 centosserver xrdp[25955]: SyslogLevel:   4
Dec 11 14:37:11 centosserver xrdp[25955]: [20201210-12:09:41] [INFO ] starting xrdp with pid 25955
Dec 11 14:37:11 centosserver xrdp[25955]: [20201210-12:09:41] [INFO ] address [<IP_ADDRESS>] port [3389] mode 1
Dec 11 14:37:11 centosserver xrdp[25955]: [20201210-12:09:42] [INFO ] listening to port 3389 on <IP_ADDRESS>
Dec 11 14:37:11 centosserver xrdp[25955]: [20201210-12:09:42] [INFO ] xrdp_listen_pp done
Dec 11 14:37:11 centosserver xrdp[25955]: [20201210-13:27:35] [INFO ] Socket 12: AF_INET connection received from <IP_ADDRESS> port 42664
Dec 11 14:37:11 centosserver xrdp[25955]: [20201210-13:27:35] [DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:11 centosserver xrdp[25955]: [20201210-13:27:40] [INFO ] Socket 12: AF_INET connection received from <IP_ADDRESS> port 30831
Dec 11 14:37:11 centosserver xrdp[25955]: [20201210-13:27:40] [DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:11 centosserver xrdp[25955]: [20201210-13:27:43] [INFO ] Socket 12: AF_INET connection received from <IP_ADDRESS> port 57764
Dec 11 14:37:11 centosserver xrdp[25955]: [20201210-13:27:43] [DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:11 centosserver xrdp[25955]: [20201210-13:30:55] [INFO ] Socket 12: AF_INET connection received from <IP_ADDRESS> port 60679
Dec 11 14:37:11 centosserver xrdp[25955]: [20201210-13:30:56] [DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:11 centosserver xrdp[25955]: [20201210-13:31:01] [INFO ] Socket 12: AF_INET connection received from <IP_ADDRESS> port 60682
Dec 11 14:37:11 centosserver xrdp[25955]: [20201210-13:31:01] [DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:11 centosserver xrdp[25955]: [20201210-13:34:51] [INFO ] Socket 12: AF_INET connection received from <IP_ADDRESS> port 37738
Dec 11 14:37:11 centosserver xrdp[25955]: [20201210-13:34:51] [DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:11 centosserver xrdp[25955]: [20201210-13:34:58] [INFO ] Socket 12: AF_INET connection received from <IP_ADDRESS> port 38405
Dec 11 14:37:11 centosserver xrdp[25955]: [20201210-13:34:58] [DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:11 centosserver xrdp[25955]: [20201211-14:34:39] [INFO ] Socket 12: AF_INET connection received from <IP_ADDRESS> port 61095
Dec 11 14:37:11 centosserver xrdp[25955]: [20201211-14:34:39] [DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:11 centosserver xrdp[25955]: [20201211-14:34:51] [INFO ] Socket 12: AF_INET connection received from <IP_ADDRESS> port 61099
Dec 11 14:37:11 centosserver xrdp[25955]: [20201211-14:34:51] [DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:11 centosserver xrdp[25955]: [20201211-14:37:05] [INFO ] Socket 12: AF_INET connection received from <IP_ADDRESS> port 61106
Dec 11 14:37:11 centosserver xrdp[25955]: [20201211-14:37:05] [DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:11 centosserver xrdp[25955]: [20201211-14:37:09] [INFO ] Socket 12: AF_INET connection received from <IP_ADDRESS> port 61107
Dec 11 14:37:11 centosserver xrdp[25955]: [20201211-14:37:09] [DEBUG] Closed socket 11 (AF_INET <IP_ADDRESS>:3389)
Dec 11 14:37:11 centosserver xrdp[25955]: [20201211-14:37:09] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
Dec 11 14:37:11 centosserver xrdp[25955]: [20201211-14:37:09] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
Dec 11 14:37:11 centosserver xrdp[25955]: [20201211-14:37:09] [WARN ] TLSv1.3 enabled by config, but not supported by system OpenSSL
Dec 11 14:37:11 centosserver xrdp[25955]: [20201211-14:37:09] [DEBUG] TLSv1.2 enabled
Dec 11 14:37:11 centosserver xrdp[25955]: [20201211-14:37:10] [DEBUG] Security layer: requested 11, selected 1
Dec 11 14:37:11 centosserver xrdp[25955]: ssl_tls_accept: TLS connection accepted
Dec 11 14:37:11 centosserver xrdp[25955]: colorDepth 0xca01 (0xca00 4bpp 0xca01 8bpp)
Dec 11 14:37:11 centosserver xrdp[25955]: [20201211-14:37:10] [INFO ] connected client computer name: VPC-O08P1080096
Dec 11 14:37:11 centosserver xrdp[25955]: postBeta2ColorDepth 0xca01 (0xca00 4bpp 0xca01 8bpp 0xca02 15bpp 0xca03 16bpp 0xca04 24bpp)
Dec 11 14:37:11 centosserver xrdp[25955]: highColorDepth 0x0018 (0x0004 4bpp 0x0008 8bpp 0x000f 15bpp 0x0010 16 bpp 0x0018 24bpp)
Dec 11 14:37:11 centosserver xrdp[25955]: supportedColorDepths 0x000f (0x0001 24bpp 0x0002 16bpp 0x0004 15bpp 0x0008 32bpp)
Dec 11 14:37:11 centosserver xrdp[25955]: earlyCapabilityFlags 0x07af (0x0002 want32)
Dec 11 14:37:11 centosserver xrdp[25955]: got client client connection type 0x00000007
Dec 11 14:37:11 centosserver xrdp[25955]: xrdp_sec_process_mcs_data_CS_SECURITY:
Dec 11 14:37:11 centosserver xrdp[25955]: client supports 40 bit encryption
Dec 11 14:37:11 centosserver xrdp[25955]: client supports 128 bit encryption
Dec 11 14:37:11 centosserver xrdp[25955]: client supports 56 bit encryption
Dec 11 14:37:11 centosserver xrdp[25955]: client supports fips encryption
Dec 11 14:37:11 centosserver xrdp[25955]: [20201211-14:37:10] [INFO ] adding channel item name rdpdr chan_id 1004 flags 0x80800000
Dec 11 14:37:11 centosserver xrdp[25955]: [20201211-14:37:10] [INFO ] adding channel item name rdpsnd chan_id 1005 flags 0xc0000000
Dec 11 14:37:11 centosserver xrdp[25955]: [20201211-14:37:10] [INFO ] adding channel item name cliprdr chan_id 1006 flags 0xc0a00000
Dec 11 14:37:11 centosserver xrdp[25955]: [20201211-14:37:10] [INFO ] adding channel item name fcchan chan_id 1007 flags 0x80000000
Dec 11 14:37:11 centosserver xrdp[25955]: [20201211-14:37:11] [INFO ] adding channel item name drdynvc chan_id 1008 flags 0xc0800000
Dec 11 14:37:11 centosserver xrdp[25955]: error unknown xrdp_sec_process_mcs_data tag 0xc006 size 8
Dec 11 14:37:11 centosserver xrdp[25955]: error unknown xrdp_sec_process_mcs_data tag 0xc00a size 8
Dec 11 14:37:11 centosserver xrdp[25955]: xrdp_sec_out_mcs_data: using no security
Dec 11 14:37:11 centosserver xrdp[25955]: xrdp_load_keyboard_layout: keyboard_type [7] keyboard_subtype [2]
Dec 11 14:37:11 centosserver xrdp[25955]: xrdp_load_keyboard_layout: model [pc105] variant [] layout [jp] options []
Dec 11 14:37:11 centosserver xrdp[22797]: (22797)(139769087891904)[DEBUG] xrdp_0000590d_wm_login_mode_event_00000001
Dec 11 14:37:11 centosserver xrdp[22797]: (22797)(139769087891904)[INFO ] Cannot find keymap file /etc/xrdp/km-e0010411.ini
Dec 11 14:37:11 centosserver xrdp[22797]: (22797)(139769087891904)[INFO ] Loading keymap file /etc/xrdp/km-00000411.ini
Dec 11 14:37:11 centosserver xrdp[22797]: (22797)(139769087891904)[WARN ] local keymap file for 0xe0010411 found and doesn't match built in keymap, using local keymap file
Dec 11 14:37:16 centosserver xrdp[22797]: (22797)(139769087891904)[DEBUG] xrdp_wm_log_msg: connecting to sesman ip <IP_ADDRESS> port 3350
Dec 11 14:37:16 centosserver xrdp-sesman[25954]: (25954)(140558903937152)[INFO ] A connection received from <IP_ADDRESS> port 51690
Dec 11 14:37:16 centosserver xrdp[22797]: (22797)(139769087891904)[INFO ] xrdp_wm_log_msg: sesman connect ok
Dec 11 14:37:17 centosserver xrdp[22797]: (22797)(139769087891904)[DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait...
Dec 11 14:37:17 centosserver xrdp[22797]: (22797)(139769087891904)[DEBUG] return value from xrdp_mm_connect 0
Dec 11 14:37:17 centosserver xrdp-sesman[25954]: PAM unable to dlopen(/usr/lib64/security/pam_tally.so): /usr/lib64/security/pam_tally.so: cannot open shared object file: No such file or directory
Dec 11 14:37:17 centosserver xrdp-sesman[25954]: PAM adding faulty module: /usr/lib64/security/pam_tally.so
Dec 11 14:37:17 centosserver xrdp-sesman[25954]: (25954)(140558903937152)[INFO ] ++ created session (access granted): username sakaia, ip <IP_ADDRESS>:61107 - socket: 12
Dec 11 14:37:17 centosserver xrdp-sesman[25954]: (25954)(140558903937152)[INFO ] starting Xvnc session...
Dec 11 14:37:17 centosserver xrdp-sesman[25954]: (25954)(140558903937152)[DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:5910)
Dec 11 14:37:17 centosserver xrdp-sesman[25954]: (25954)(140558903937152)[DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6010)
Dec 11 14:37:18 centosserver xrdp-sesman[25954]: (25954)(140558903937152)[DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6210)
Dec 11 14:37:18 centosserver xrdp-sesman[25954]: (25954)(140558903937152)[DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:5911)
Dec 11 14:37:18 centosserver xrdp-sesman[25954]: (25954)(140558903937152)[DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6011)
Dec 11 14:37:18 centosserver xrdp-sesman[25954]: (25954)(140558903937152)[DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6211)
Dec 11 14:37:18 centosserver xrdp-sesman[25954]: (25954)(140558903937152)[DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:5912)
Dec 11 14:37:18 centosserver xrdp-sesman[25954]: (25954)(140558903937152)[DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6012)
Dec 11 14:37:18 centosserver xrdp-sesman[25954]: (25954)(140558903937152)[DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6212)
Dec 11 14:37:19 centosserver xrdp-sesman[25954]: (25954)(140558903937152)[DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:5913)
Dec 11 14:37:19 centosserver xrdp-sesman[25954]: (25954)(140558903937152)[DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6013)
Dec 11 14:37:19 centosserver xrdp-sesman[25954]: (25954)(140558903937152)[DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6213)
Dec 11 14:37:19 centosserver xrdp-sesman[25954]: (25954)(140558903937152)[DEBUG] Closed socket 8 (AF_INET <IP_ADDRESS>:3350)
Dec 11 14:37:19 centosserver xrdp[22797]: (22797)(139769087891904)[INFO ] xrdp_wm_log_msg: login successful for display 13
Dec 11 14:37:19 centosserver xrdp-sesman[22807]: (22807)(140558903937152)[INFO ] calling auth_start_session from pid 22807
Dec 11 14:37:19 centosserver xrdp[22797]: (22797)(139769087891904)[DEBUG] Layout from client_info (geom=1920x1080 #screens=1) : 0:(1920x1080+0+0)
Dec 11 14:37:20 centosserver xrdp[22797]: (22797)(139769087891904)[DEBUG] xrdp_wm_log_msg: VNC started connecting
Dec 11 14:37:20 centosserver systemd-logind[1915]: New session c20 of user sakaia.
Dec 11 14:37:20 centosserver systemd[1]: Started Session c20 of user sakaia.
Dec 11 14:37:20 centosserver xrdp-sesman[22807]: pam_unix(xrdp-sesman:session): session opened for user sakaia by (uid=0)
Dec 11 14:37:20 centosserver xrdp-sesman[22807]: (22807)(140558903937152)[DEBUG] Closed socket 7 (AF_INET <IP_ADDRESS>:3350)
Dec 11 14:37:20 centosserver xrdp[22797]: (22797)(139769087891904)[DEBUG] xrdp_wm_log_msg: VNC connecting to <IP_ADDRESS> 5913
Dec 11 14:37:20 centosserver xrdp-sesman[22807]: (22807)(140558903937152)[DEBUG] Closed socket 8 (AF_INET <IP_ADDRESS>:3350)
Dec 11 14:37:20 centosserver xrdp-sesman[22809]: (22809)(140558903937152)[INFO ] Xvnc :13 -auth .Xauthority -geometry 1920x1080 -depth 32 -rfbauth /home/sakaia/.vnc/sesman_passwd-sakaia@centosserver:13 -bs -nolisten tcp -localhost -dpi 96
Dec 11 14:37:20 centosserver xrdp-sesman[25954]: Xvnc TigerVNC 1.8.0 - built Nov 16 2020 16:47:50
Dec 11 14:37:20 centosserver xrdp-sesman[25954]: Copyright (C) 1999-2017 TigerVNC Team and many others (see README.txt)
Dec 11 14:37:20 centosserver xrdp-sesman[25954]: See http://www.tigervnc.org for information on TigerVNC.
Dec 11 14:37:20 centosserver xrdp-sesman[25954]: Underlying X server release 12004000, The X.Org Foundation
Dec 11 14:37:20 centosserver xrdp-sesman[25954]: Fri Dec 11 14:37:20 2020
Dec 11 14:37:20 centosserver xrdp-sesman[25954]: vncext:      VNC extension running!
Dec 11 14:37:20 centosserver xrdp-sesman[25954]: vncext:      Listening for VNC connections on local interface(s), port 5913
Dec 11 14:37:20 centosserver xrdp-sesman[25954]: vncext:      created VNC server for screen 0
Dec 11 14:37:20 centosserver xrdp-sesman[22807]: (22807)(140558903937152)[CORE ] waiting for window manager (pid 22808) to exit
Dec 11 14:37:20 centosserver xrdp-sesman[25954]: Connections: accepted: <IP_ADDRESS>::60806
Dec 11 14:37:20 centosserver xrdp[22797]: (22797)(139769087891904)[DEBUG] xrdp_wm_log_msg: VNC tcp connected
Dec 11 14:37:20 centosserver xrdp-sesman[22807]: (22807)(140558903937152)[CORE ] window manager (pid 22808) did exit, cleaning up session
Dec 11 14:37:21 centosserver xrdp-sesman[25954]: Fri Dec 11 14:37:21 2020
Dec 11 14:37:21 centosserver xrdp-sesman[25954]: SConnection: Client needs protocol version 3.3
Dec 11 14:37:21 centosserver xrdp[22797]: (22797)(139769087891904)[DEBUG] xrdp_wm_log_msg: VNC security level is 2 (1 = none, 2 = standard)
Dec 11 14:37:21 centosserver xrdp-sesman[22807]: (22807)(140558903937152)[INFO ] calling auth_stop_session and auth_end from pid 22807
Dec 11 14:37:21 centosserver xrdp-sesman[25954]: VNCSConnST:  Server default pixel format depth 32 (32bpp) little-endian rgb
Dec 11 14:37:21 centosserver xrdp[22797]: (22797)(139769087891904)[DEBUG] xrdp_wm_log_msg: VNC password ok
Dec 11 14:37:21 centosserver xrdp-sesman[25954]: max 255,255,255 shift 16,8,0
Dec 11 14:37:21 centosserver xrdp-sesman[22807]: pam_unix(xrdp-sesman:session): session closed for user sakaia
Dec 11 14:37:21 centosserver xrdp-sesman[22807]: (22807)(140558903937152)[DEBUG] cleanup_sockets:
Dec 11 14:37:21 centosserver xrdp[22797]: (22797)(139769087891904)[DEBUG] xrdp_wm_log_msg: VNC sending share flag
Dec 11 14:37:21 centosserver xrdp-sesman[22807]: (22807)(140558903937152)[DEBUG] cleanup_sockets: deleting /run/xrdp/xrdp_chansrv_socket_13
Dec 11 14:37:21 centosserver xrdp[22797]: (22797)(139769087891904)[DEBUG] xrdp_wm_log_msg: VNC receiving server init
Dec 11 14:37:22 centosserver xrdp-sesman[22807]: (22807)(140558903937152)[DEBUG] cleanup_sockets: deleting /run/xrdp/xrdpapi_13
Dec 11 14:37:22 centosserver xrdp[22797]: (22797)(139769087891904)[DEBUG] VNC error before receiving pixel format
Dec 11 14:37:22 centosserver ovn-controller[2279]: ovs|132906|patch|ERR|Dropped 11 log messages in last 9 seconds (most recently, 5 seconds ago) due to excessive rate
Dec 11 14:37:22 centosserver ovn-controller[2279]: ovs|132907|patch|ERR|bridge not found for localnet port 'provnet-1557936b-0a1d-41e3-bd7c-3bf17c4f276d' with network name 'extnet'
Dec 11 14:37:22 centosserver xrdp-sesman[22807]: (22807)(140558903937152)[DEBUG] cleanup_sockets: failed to delete /run/xrdp/xrdpapi_13
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: cket: 12
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201210-14:14:36] [INFO ] starting Xvnc session...
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201210-14:14:36] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:5910)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201210-14:14:36] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6010)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201210-14:14:36] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6210)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201210-14:14:36] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:5911)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201210-14:14:37] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6011)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201210-14:14:37] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6211)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201210-14:14:37] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:5912)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201210-14:14:37] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6012)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201210-14:14:37] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6212)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201210-14:14:38] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:5913)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201210-14:14:38] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6013)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201210-14:14:38] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6213)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201210-14:14:38] [DEBUG] Closed socket 8 (AF_INET <IP_ADDRESS>:3350)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201210-14:14:41] [INFO ] ++ terminated session:  username sakaia, display :13.0, session_pid 29088, ip <IP_ADDRESS>:60682 - socket: 12
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:35:03] [INFO ] A connection received from <IP_ADDRESS> port 51676
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:35:03] [INFO ] ++ created session (access granted): username sakaia, ip <IP_ADDRESS>:61099 - socket: 12
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:35:03] [INFO ] starting Xvnc session...
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:35:03] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:5910)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:35:04] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6010)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:35:04] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6210)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:35:04] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:5911)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:35:04] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6011)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:35:04] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6211)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:35:05] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:5912)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:35:05] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6012)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:35:05] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6212)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:35:05] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:5913)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:35:05] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6013)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:35:05] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6213)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:35:06] [DEBUG] Closed socket 8 (AF_INET <IP_ADDRESS>:3350)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:35:09] [INFO ] ++ terminated session:  username sakaia, display :13.0, session_pid 22680, ip <IP_ADDRESS>:61099 - socket: 12
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:16] [INFO ] A connection received from <IP_ADDRESS> port 51690
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:17] [INFO ] ++ created session (access granted): username sakaia, ip <IP_ADDRESS>:61107 - socket: 12
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:17] [INFO ] starting Xvnc session...
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:17] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:5910)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:17] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6010)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:18] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6210)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:18] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:5911)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:18] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6011)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:18] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6211)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:18] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:5912)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:18] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6012)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:18] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6212)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:19] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:5913)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:19] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6013)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:19] [DEBUG] Closed socket 9 (AF_INET <IP_ADDRESS>:6213)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:19] [INFO ] calling auth_start_session from pid 22807
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:20] [DEBUG] Closed socket 7 (AF_INET <IP_ADDRESS>:3350)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:20] [DEBUG] Closed socket 8 (AF_INET <IP_ADDRESS>:3350)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:20] [CORE ] waiting for window manager (pid 22808) to exit
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:20] [CORE ] window manager (pid 22808) did exit, cleaning up session
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:21] [INFO ] calling auth_stop_session and auth_end from pid 22807
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:21] [DEBUG] cleanup_sockets:
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:21] [DEBUG] cleanup_sockets: deleting /run/xrdp/xrdp_chansrv_socket_13
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:22] [DEBUG] cleanup_sockets: deleting /run/xrdp/xrdpapi_13
Dec 11 14:37:22 centosserver xrdp[22797]: (22797)(139769087891904)[DEBUG] VNC error before receiving name length
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:22] [DEBUG] cleanup_sockets: failed to deletchansrv::main: using log file [/home/sakaia/.local/share/xrdp/xrdp-chansrv.13.log]
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:20] [CORE ] main: app started pid 22820(0x00005924)
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:21] [INFO ] main: DISPLAY env var set to :13.0
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:21] [INFO ] main: using DISPLAY 13
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:21] [INFO ] channel_thread_loop: thread start
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:21] [INFO ] term_signal_handler: got signal 15
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:21] [INFO ] channel_thread_loop: g_term_event set
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: xrdp-chansrv [1347273591]: scard_deinit:
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: chansrv:smartcard_pcsc [1347273591]: scard_pcsc_deinit:
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:22] [INFO ] channel_thread_loop: thread stop
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: e /run/xrdp/xrdpapi_13
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: (25954)(140558903937152)[INFO ] ++ terminated session:  username sakaia, display :13.0, session_pid 22807, ip <IP_ADDRESS>:61107 - socket: 12
Dec 11 14:37:22 centosserver xrdp-sesman[25954]: [20201211-14:37:22] [INFO ] main: app exiting pid 22820(0x00005924)
Dec 11 14:37:22 centosserver xrdp[22797]: (22797)(139769087891904)[DEBUG] VNC error before receiving name
Dec 11 14:37:22 centosserver xrdp[22797]: (22797)(139769087891904)[DEBUG] xrdp_wm_log_msg: VNC error - problem connecting
Dec 11 14:37:23 centosserver xrdp[22797]: (22797)(139769087891904)[DEBUG] Closed socket 19 (AF_INET <IP_ADDRESS>:60806)
Dec 11 14:37:23 centosserver xrdp[22797]: (22797)(139769087891904)[DEBUG] xrdp_wm_log_msg: some problem
Dec 11 14:37:23 centosserver xrdp[22797]: (22797)(139769087891904)[DEBUG] xrdp_mm_module_cleanup
Dec 11 14:37:23 centosserver xrdp[22797]: (22797)(139769087891904)[DEBUG] VNC mod_exit
Dec 11 14:37:23 centosserver xrdp[22797]: (22797)(139769087891904)[DEBUG] Closed socket 18 (AF_INET <IP_ADDRESS>:51690)
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:11] [INFO ] TLS connection established from <IP_ADDRESS> port 61107: TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp_caps_process_order: bitmap cache v3 supported
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp_caps_process_pointer: client supports new(color) cursor
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp_caps_process_glyphcache: support level 3
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp_process_offscreen_bmpcache: support level 1 cache size 10485760 MB cache entries 100
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp_caps_process_surface_cmds:
Dec 11 14:37:28 centosserver xrdp[25955]: cmdFlags 0x00000052
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp_caps_process_frame_ack:
Dec 11 14:37:28 centosserver xrdp[25955]: max_unacknowledged_frame_count 2
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp_caps_process_codecs: nscodec, codec id 1, properties len 3
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp_caps_process_codecs: unknown codec id 5
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp_caps_process_codecs: RemoteFX, codec id 3, properties len 49
Dec 11 14:37:28 centosserver xrdp[25955]: yeah, up_and_running
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp_channel_drdynvc_start:
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp:xrdp_bitmap [1347262774]: xrdp_bitmap_create: noorders
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:11] [DEBUG] xrdp_0000590d_wm_login_mode_event_00000001
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp:xrdp_mm [1347262841]: xrdp_mm_create: bpp 32 mcs_connection_type 7 jpeg_codec_id 0 v3_codec_id 0 rfx_codec_id 3 h264_codec_id 0
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:11] [INFO ] Cannot find keymap file /etc/xrdp/km-e0010411.ini
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:11] [INFO ] Loading keymap file /etc/xrdp/km-00000411.ini
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:11] [WARN ] local keymap file for 0xe0010411 found and doesn't match built in keymap, using local keymap file
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp_wm_login_mode_changed: login_mode is 0
Dec 11 14:37:28 centosserver xrdp[25955]: in xrdp_wm_init:
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp_wm_init: channel rdpdr channel id 0 is allowed
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp_wm_init: channel rdpsnd channel id 1 is allowed
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp_wm_init: channel cliprdr channel id 2 is allowed
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp_wm_init: channel fcchan channel id 3 is disabled
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp_wm_init: channel drdynvc channel id 4 is allowed
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp_wm_init: no autologin / auto run detected, draw login window
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp:xrdp_cache [1347263246]: xrdp_cache_add_bitmap: reset detected cache_id 2
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp:xrdp_cache [1347263246]: xrdp_cache_add_bitmap: reset detected cache_id 1
Dec 11 14:37:28 centosserver xrdp[25955]: out xrdp_wm_init:
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp_wm_login_mode_changed: login_mode is 1
Dec 11 14:37:28 centosserver xrdp[25955]: drdynvc_process_capability_response: DVC version 3 selected
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp:xrdp_mm [1347263247]: xrdp_mm_drdynvc_up:
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp_wm_login_mode_changed: login_mode is 2
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:16] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip <IP_ADDRESS> port 3350
Dec 11 14:37:28 centosserver xrdp[25955]: connecting to sesman ip <IP_ADDRESS> port 3350
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:16] [INFO ] xrdp_wm_log_msg: sesman connect ok
Dec 11 14:37:28 centosserver xrdp[25955]: sesman connect ok
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:17] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait...
Dec 11 14:37:28 centosserver xrdp[25955]: sending login info to session manager, please wait...
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:17] [DEBUG] return value from xrdp_mm_connect 0
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp_wm_login_mode_changed: login_mode is 3
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:19] [INFO ] xrdp_wm_log_msg: login successful for display 13
Dec 11 14:37:28 centosserver xrdp[25955]: login successful for display 13
Dec 11 14:37:28 centosserver xrdp[25955]: loaded module 'libvnc.so' ok, interface size 4072, version 4
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:19] [DEBUG] Layout from client_info (geom=1920x1080 #screens=1) : 0:(1920x1080+0+0)
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:20] [DEBUG] xrdp_wm_log_msg: VNC started connecting
Dec 11 14:37:28 centosserver xrdp[25955]: VNC started connecting
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:20] [DEBUG] xrdp_wm_log_msg: VNC connecting to <IP_ADDRESS> 5913
Dec 11 14:37:28 centosserver xrdp[25955]: VNC connecting to <IP_ADDRESS> 5913
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:20] [DEBUG] xrdp_wm_log_msg: VNC tcp connected
Dec 11 14:37:28 centosserver xrdp[25955]: VNC tcp connected
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:21] [DEBUG] xrdp_wm_log_msg: VNC security level is 2 (1 = none, 2 = standard)
Dec 11 14:37:28 centosserver xrdp[25955]: VNC security level is 2 (1 = none, 2 = standard)
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:21] [DEBUG] xrdp_wm_log_msg: VNC password ok
Dec 11 14:37:28 centosserver xrdp[25955]: VNC password ok
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:21] [DEBUG] xrdp_wm_log_msg: VNC sending share flag
Dec 11 14:37:28 centosserver xrdp[25955]: VNC sending share flag
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:21] [DEBUG] xrdp_wm_log_msg: VNC receiving server init
Dec 11 14:37:28 centosserver xrdp[25955]: VNC receiving server init
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:22] [DEBUG] VNC error before receiving pixel format
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:22] [DEBUG] VNC error before receiving name length
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:22] [DEBUG] VNC error before receiving name
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:22] [DEBUG] xrdp_wm_log_msg: VNC error - problem connecting
Dec 11 14:37:28 centosserver xrdp[25955]: VNC error - problem connecting
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:23] [DEBUG] Closed socket 19 (AF_INET <IP_ADDRESS>:60806)
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:23] [DEBUG] xrdp_wm_log_msg: some problem
Dec 11 14:37:28 centosserver xrdp[25955]: some problem
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:23] [DEBUG] xrdp_mm_module_cleanup
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:23] [DEBUG] VNC mod_exit
Dec 11 14:37:28 centosserver xrdp[25955]: [20201211-14:37:23] [DEBUG] Closed socket 18 (AF_INET <IP_ADDRESS>:51690)
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp_wm_login_mode_changed: login_mode is 11
Dec 11 14:37:28 centosserver xrdp[25955]: xrdp_wm_login_mode_changed: login_mode is 0
Dec 11 14:37:28 centosserver xrdp[25955]: in xrdp_wm_init:
Dec 11 14:37:30 centosserver systemd-logind[1915]: Removed session c20.
Dec 11 14:37:37 centosserver ovn-controller[2279]: ovs|132908|patch|ERR|Dropped 2 log messages in last 10 seconds (most recently, 5 seconds ago) due to excessive rate
Dec 11 14:37:37 centosserver ovn-controller[2279]: ovs|132909|patch|ERR|bridge not found for localnet port 'provnet-1557936b-0a1d-41e3-bd7c-3bf17c4f276d' with network name 'extnet'
Dec 11 14:37:49 centosserver sudo[22871]:   sakaia : TTY=pts/0 ; PWD=/home/sakaia ; USER=root ; COMMAND=/bin/journalctl -S 14:36:49
Dec 11 14:37:49 centosserver sudo[22871]: pam_unix(sudo:session): session opened for user root by sakaia(uid=0)
Dec 11 14:37:52 centosserver ovn-controller[2279]: ovs|132910|patch|ERR|Dropped 4 log messages in last 14 seconds (most recently, 5 seconds ago) due to excessive rate
Dec 11 14:37:52 centosserver ovn-controller[2279]: ovs|132911|patch|ERR|bridge not found for localnet port 'provnet-1557936b-0a1d-41e3-bd7c-3bf17c4f276d' with network name 'extnet'
Dec 11 14:37:57 centosserver sudo[22871]: pam_unix(sudo:session): session closed for user root
Dec 11 14:38:09 centosserver ovn-controller[2279]: ovs|132912|patch|ERR|Dropped 12 log messages in last 15 seconds (most recently, 5 seconds ago) due to excessive rate
Dec 11 14:38:09 centosserver ovn-controller[2279]: ovs|132913|patch|ERR|bridge not found for localnet port 'provnet-1557936b-0a1d-41e3-bd7c-3bf17c4f276d' with network name 'extnet'
Dec 11 14:38:24 centosserver ovn-controller[2279]: ovs|132914|patch|ERR|Dropped 2 log messages in last 10 seconds (most recently, 5 seconds ago) due to excessive rate
Dec 11 14:38:24 centosserver ovn-controller[2279]: ovs|132915|patch|ERR|bridge not found for localnet port 'provnet-1557936b-0a1d-41e3-bd7c-3bf17c4f276d' with network name 'extnet'
Dec 11 14:38:30 centosserver sudo[22892]:   sakaia : TTY=pts/0 ; PWD=/home/sakaia ; USER=root ; COMMAND=/bin/journalctl -S 14:36:49
Dec 11 14:38:30 centosserver sudo[22892]: pam_unix(sudo:session): session opened for user root by sakaia(uid=0)

Hi @sakaia
That's very useful. It appears that the problem is actually with your session. From the log:-
Dec 11 14:37:20 centosserver xrdp-sesman[22807]: (22807)(140558903937152)[CORE ] waiting for window manager (pid 22808) to exit
. . .
Dec 11 14:37:20 centosserver xrdp-sesman[22807]: (22807)(140558903937152)[CORE ] window manager (pid 22808) did exit, cleaning up session

What is happening is that xrdp-sesman is creating the session at 14:37:20. The session exits almost immediately, and then xrdp-sesman kills the X server. That produces the errors you're seeing on the connection.
Some questions for you:-

Do you have a desktop environment (for example GNOME, or XFCE) installed?
Is there a file /home/sakaia/.xsession-errors on your system? If so could you post it?

Thanks.

The size of  /home/sakaia/.xsession-errors is zero.

I am updating following instruction. And I succeed it on EC2 also. and my local environments successful.
I guess first two lines are effective.
Thanks for your comments.
sudo yum update
sudo yum groups install "GNOME Desktop"
sudo yum install epel-release
sudo yum install xrdp tigervnc-server
sudo rpm -qa | grep xrdp
sudo rpm -qa | grep tigervnc
sudo vi /etc/xrdp/xrdp.ini
sudo firewall-cmd --permanent --zone=public --add-port=3389/tcp
sudo firewall-cmd --reload
sudo systemctl start xrdp
sudo systemctl enable xrdp
sudo adduser sakaia
sudo passwd sakaia
sudo usermod -aG wheel sakaia

Glad you've got it working - thanks for letting us know.
I'll close this one now.


Export api to encode value to fate bytecode

For example
  const recordAci = {
    record: [{
      name: 'operation',
      type: 'string',
    }, {
      name: 'parameter',
      type: 'int',
    }],
  } as const;
  const recordDataDecoded = {
    operation: 'test',
    parameter: 42,
  };

I want to get the corresponding fate-encoded bytecode ('cb_KxF0ZXN0VANAuWU=') for my implementation of EIP-712 🙄
Currently, I'm doing it this way
import ContractByteArrayEncoder from<EMAIL_ADDRESS>import AciTypeResolver from<EMAIL_ADDRESS>
export function encodeFateValue(value, aci) {
  const contractByteArrayEncoder = new ContractByteArrayEncoder();
  const aciTypeResolver = new AciTypeResolver([]);
  aciTypeResolver.isCustomType = () => false;
  return contractByteArrayEncoder.encode(aciTypeResolver.resolveType(aci), value);
}

There is the same issue with decoding, I see only typeless decoding exported
https://github.com/aeternity/aepp-calldata-js/blob/82b5a98f9b308482627da8d7484d213e9cf87151/src/api/ContractByteArrayEncoder.js#L27

Any proposal for the API? I prefer to stick to the ACI interface/protocol as much as possible.

I prefer to stick to the ACI interface/protocol as much as possible.

Sure, it should accept a subset of ACI defining a value to encode/decode.
Other than that a would prefer a functional approach 🙄


[SPARK-14535][SQL] Remove buildInternalScan from FileFormat

What changes were proposed in this pull request?
Now HadoopFsRelation with all kinds of file formats can be handled in FileSourceStrategy, we can remove the branches for  HadoopFsRelation in FileSourceStrategy and the buildInternalScan API from FileFormat.
How was this patch tested?
existing tests.

CC @marmbrus @liancheng @yhuai

Test build #55523 has started for PR 12300 at commit 6c9ede0.

Test build #55523 has finished for PR 12300 at commit 6c9ede0.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test FAILed.

We can also remove these pattern match guard conditions and the spark.sql.sources.fileScan SQL option.

And the ORC data source, which lives in the sql/hive, hasn't been cleaned yet.

Test build #55551 has started for PR 12300 at commit 35682a8.

Test build #55551 has finished for PR 12300 at commit 35682a8.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #55564 has started for PR 12300 at commit 35462d2.

Test build #55564 has finished for PR 12300 at commit 35462d2.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

Ah. sorry. Maybe the commit I just made caused the conflicts...

np, I already fixed it :)

Test build #55585 has started for PR 12300 at commit ca2a94b.

LGTM

Test build #55585 has finished for PR 12300 at commit ca2a94b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

Thanks. Merging to master.


docs: 修正一些错误文档

👀 PR includes

🔧 Chore

[ ] Test case
[x] Docs / demos update
[ ] CI / workflow
[ ] Release version
[ ] Other ()

📝 Description

去除冗余的 S2Constructor 类型
修复一些文档参数格式 和 Typo

:tada: This PR is included in version @antv/s2-v1.20.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version @antv/s2-react-v1.18.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version @antv/s2-vue-v1.0.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


(C#) SetMultiplayerAuthority is an int instead of a long

Godot version
4.1.beta.1
System information
Fedora 38
Issue description
When using the default peer ids all are long.
But when using Node#SetMultiplayerAuthority it wants to have an int
Steps to reproduce
Try to type SetMultiplayerAuthority in C#
Minimal reproduction project
There is nothing to debug.
There should be something wrong with the c# class generator.

It's an int parameter in the API, so that's correct, where are the peer IDs coming from that are long?

Oh I see.
But why has these methods an id of type long
- ENetMultiplayerPeer#PeerConnected
- ENetMultiplayerPeer#PeerDisconnected
- MultiplayerAPI#PeerConnected
- MultiplayerAPI#PeerDisconnected

Probably because the API doesn't support different sized INT, the bindings int is int64_t

But are these peer ids not the same?

They will probably never larger than valid int32_t, so it's safe afik

Then why not decide on one type of peer id?
It's a bit confusing to use different ones?
Should I cast them to ints when settings setmultiplayerAutority?

Probably because the API doesn't support different sized INT, the bindings int is int64_t

This
I don't know how C# works

Then the bindings should be changed?
I don't see an advantage to have multiple types for peer ids

You're missing the point, the signal bindings are unable to handle different types of INT, it's always long
SetMultiplayerAuthority can't be changed without breaking compatibility, that's not desired
While I get this is a confusing thing, but this isn't really a reason to make this kind of change
It's a limitation of the bindings system

Hmm okay, should we keep this issue open?
Maybe this can be fixed/changed in the future

I mean I don't think this is a bug, the sending of a long is fully valid, as long as it'll never be an invalid int, which it doesn't look like in the code
It being a different type is annoying sure, but it doesn't really qualify as a bug, at least not enough to justify breaking compat

Okay, maybe I will add then this "confusion" to the proposal repo

In C#, methods will use int or long as specified by ClassDB. So if the C++ method uses a 32-bit int we will use int, and if it uses a 64-bit int we will use a long.
Signals don't have this information, so we always assume it's a 64-bit int to make sure it fits. In this case, if the peer ID is always a 32-bit int it's safe to cast it to int.
Changing how signals are generated would indeed break compatibility.
This issue sounds like a duplicate of https://github.com/godotengine/godot/issues/75396 which was a duplicate of https://github.com/godotengine/godot/issues/65749. So closing as a duplicate.

Oh okay sorry, i searched for multiplayer autority


Incorrect labels for Open file window

Description:
The Open file window does not have the correct labels. It can be mistaken for Save file window thus it can confuse the user.
Steps to Recreate:

Open LaTex Studio
Navigate to menu bar File > Open File

Expected Result:
The Open File window have the correct labels
Actual Result:
The Open File window have incorrect labels
Screenshot:
Windows 7

Linux - Ubuntu 14.04.2

Labels have been fixed and should now display approperiately, depending on the selected action.

Issue is not 100% fixed. Linux environment still has the incorrect labels as seen in the screenshot.