Fix Incorrectly Resolved and Untested Merge Conflicts in Pipeline Configuration File

Change Description
I removed the auto-buildkite-pipelines:protocol-features-sync-nodes branch in pull request 7467 but then, in commit 2bcddd7fca4162f49db350ece8e27b49cd8e5080, someone incorrectly resolved merge conflicts and pointed the eosio-lrt and eosio-build-unpinned pipelines at this deleted branch without testing their changes.
I have restored these pipelines to their state in pull request 7467.
Tested

eosio-build-unpinned build 241

This build is expected to fail on Amazon Linux 2 NP Tests and Ubuntu 18.04 NP Tests as seen in build 221. DevOps has an open story to address that failure.

eosio-lrt build 549

Consensus Changes

[ ] Consensus Changes
None.

API Changes

[ ] API Changes
None.

Documentation Additions

[ ] Documentation Additions
None.

How come LRT is using 1.8.0?

I just reverted it back to the most recent working state.
You're right, it should be using the same IMAGE_TAG as the other pipelines.


Add system test for 'logger.log_text' and 'logger.log_struct'.

@dhermes any remaining issues?

Rebased after merging #1616 to the logging-api branch.

LGTM. The eventual consistency hack might be easier to find if you factor it out into a helper (like is done in the bigtable test).

The eventual consistency hack might be easier to find if you factor it out into a helper (like is done in the bigtable test).

I've been thinking about a more generic retry wrapper (per #1619).

@tseaver I made a generic retry wrapper in #535


Domain transfer payment

Existing documentation URL(s)
No documentation
What changes are you suggesting?
I need to know when the domain transfer process is stopped at the payment when payment method is set up

Additional information
No response

Howdy @sdobke, it sounds like you're at Step 8 of the transfer process, where the payment itself isn't the blocker... it's that you need to approve the transfer at your registrar.
That being said... this isn't a support channel, so I'd recommend you open a ticket with Cloudflare Support for more troubleshooting help.


Fix multiple users with the same name being online

This pr logs out any other user with the same name that is currently online on login, which prevents multiple users with the same name being online.

looks good


Package seems to be broken in Julia 0.4.6

I was able to install it, but I am not able to import it:
                 _
   _       _ _(_)_     |  A fresh approach to technical computing
  (_)     | (_) (_)    |  Documentation: http://docs.julialang.org
   _ _   _| |_  __ _   |  Type "?help" for help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 0.4.6 (2016-06-19 17:16 UTC)
 _/ |\__'_|_|_|\__'_|  |  Official http://julialang.org/ release
|__/                   |  x86_64-apple-darwin13.4.0

julia> using Gadfly
WARNING: New definition
    +(AbstractArray, DataArrays.DataArray) at /Users/chris/.julia/v0.4/DataArrays/src/operators.jl:276
is ambiguous with:
    +(WoodburyMatrices.SymWoodbury, AbstractArray{T<:Any, 2}) at /Users/chris/.julia/v0.4/WoodburyMatrices/src/SymWoodburyMatrices.jl:107.
To fix, define
    +(WoodburyMatrices.SymWoodbury, DataArrays.DataArray{T<:Any, 2})
before the new definition.
WARNING: New definition
    +(AbstractArray, DataArrays.AbstractDataArray) at /Users/chris/.julia/v0.4/DataArrays/src/operators.jl:300
is ambiguous with:
    +(WoodburyMatrices.SymWoodbury, AbstractArray{T<:Any, 2}) at /Users/chris/.julia/v0.4/WoodburyMatrices/src/SymWoodburyMatrices.jl:107.
To fix, define
    +(WoodburyMatrices.SymWoodbury, DataArrays.AbstractDataArray{T<:Any, 2})
before the new definition.

You should be able to use the package, despite the ambiguity warnings. These are due to a change in base Julia and will go away on v0.5. Sorry for the inconvenience.


No repo license/description causes a TypeError

I build this off a test repo so there were some things missing. I noticed that the action crashes if the repo is missing a description or a license. Usually these would be set on a non-test repo but it might be good to either document the requirements, have a default fallback or allow the user to set these in the workflow, especially description.
Having no license set causes a TypeError error.
Traceback (most recent call last):
  File "/homebrew_releaser/app.py", line 197, in <module>
    main()
  File "/homebrew_releaser/app.py", line 193, in main
    App.run_github_action()
  File "/homebrew_releaser/app.py", line 121, in run_github_action
    template = Formula.generate_formula_data(
  File "/homebrew_releaser/formula.py", line 45, in generate_formula_data
    license_type = repository['license']['spdx_id']
TypeError: 'NoneType' object is not subscriptable

Having no description set causes a TypeError error.
Traceback (most recent call last):
  File "/homebrew_releaser/app.py", line 197, in <module>
    main()
  File "/homebrew_releaser/app.py", line 193, in main
    App.run_github_action()
  File "/homebrew_releaser/app.py", line 121, in run_github_action
    template = Formula.generate_formula_data(
  File "/homebrew_releaser/formula.py", line 46, in generate_formula_data
    description = re.sub(r'[.!]+', '', repository['description'][:max_desc_field_length]).strip().capitalize()
TypeError: 'NoneType' object is not subscriptable

Thanks!

Fixed via https://github.com/Justintime50/homebrew-releaser/commit/730005e8f80f4309d9f7620a1733deae1d8cc68d

Thanks! 🎉


word header and footer

Hallo,
The html-docx works realy great. Could get realy good results till now.
What would be the way to add header and footer in the resulting word document?

changing the .tpl file
using the htmlDocx.asBlob(content, header, footer) function and adding html for header and footer options/parameters
how to add page numbers to the footer

Thx for any hint,
regeads, Willi

Sorry for the delayed response. We haven't tried including headers, but according to this documentation, it would involve both changing the template and adding extra files to the resulting ZIP.
Let me know if you had any progress on this, otherwise I will try to give it a shot myself.

Hi,
Any news or progress about the header/footer feature? Thanks

Header/footers would be awesome! Any progress on this?

Hi @anowak,
Adding the header relationship requires core ZIP generating logic as you mentioned. Here I added sample header relationship to document.tpl just to mention additional sections to be added.  Can you help us on adding headers and footers since its a basic requirement in most of the cases?
Thanks!

Hi!
Any news or progress on the resolution for this issue?

It can be add to the .mht file.
http://sebsauvage.net/wiki/doku.php?id=word_document_generation

can i download svg images using html-docsx-js?

@prasadKodeInCloud has anyone forked and added this feature, or does anyone have experience with adding this feature? I see that you added a sample, but I still have no clue where to start.

@prasadKodeInCloud has anyone forked and added this feature, or does anyone have experience with adding this feature? I see that you added a sample, but I still have no clue where to start.

The problem is that Word (at least, the latest Word for Mac) doesn't seem to accept altchunks with HTML in either header or footer.
I haven't managed to make this one work, but I'm also skeptical regarding its compatibility with altchunks.
The bottom line is that the only way to have header/footer in the generated document would be to pass the content in WordProcessing ML, for example:
<w:hdr xmlns:w="http://schemas.openxmlformats.org/wordprocessingml/2006/main">
  <w:p>
    <w:pPr>
       <w:pStyle w:val="Header"/>
    </w:pPr>
    <w:r>
       <w:t>Header text</w:t>
    </w:r>
  </w:p>
</w:hdr>

To sum up -- it is possible, but header content cannot be specified using HTML. The easiest would be to use Word to create an empty document with a header, unzip the DOCX file and extract the definition of header/footer from it. Would such workflow suit your needs?

It could suit our needs if altchunks is the limitation. Could it potentially accept plaintext for extremely simple headers/footers though?

Hi ! Would anyone have an example of such way of doing ? It's the first time i'm playing with docx files and i'm not sure how to "extract the definition of header/footer from it". Thanks a lot

Any update on this issue? I am successfully able to generate docx with header using html-docx-js.
I have mentioned header in the main html file like below

            Name: ________________________
            Class:________________
            Date:___________

and used mso-header: h1; style
This is working and can view header on every page of generated document.
But my requirement is to restrict header on first page only. So I have tried to apply below styles
mso-title-page: yes;
mso-first-header: h1;
But header is not visible. Does anyone know how to do this? Thanks in advance.

Any one able to fix the Header/Footer or Is it possible to pass template document with header and footer which can only convert HTML to Word ?

yes, it can be added to .mht file, but first page header is not working

mso-header: h1

how to add footer?


feat: add global recently used store

Feature aims to persist keyboard state between components, without using context or external libs.

TODO: combineReducer for further state growth


l2cap coc: send() broken since #414

Issue
As happy as I was when it got merged, it seems that #414 introduced some problems for sending data via l2cap_(coc_)send(). The STALLED state is not resolved properly, leading to the sending node getting stuck in an endless loop sending out some random packet.
Test setup

running Nimble@RIOT
branch: https://github.com/haukepetersen/RIOT/tree/opt_nimble_ver370305a -> https://github.com/RIOT-OS/RIOT/pull/11273
two nrf52dk nodes, running Nimble host and controller
Node A:
l2cap echo server -> https://github.com/haukepetersen/RIOT/tree/opt_nimble_ver370305a/tests/nimble_l2cap_server
any payload that is received via the configured l2cap coc is echoed on the same channel
Node B:
l2cap 'sender' -> https://github.com/haukepetersen/RIOT/tree/opt_nimble_ver370305a/tests/nimble_l2cap
'floods' the configured l2cap coc by sending out data as fast as possible

The send function looks as following
    do {
        res = ble_l2cap_send(_coc, txd);
        if (res == BLE_HS_ESTALLED) {
            thread_flags_wait_all(FLAG_TX_UNSTALLED);
        }
    } while ((res == BLE_HS_EBUSY) || (res == BLE_HS_ESTALLED));

The thread_flags_wait_all() is simply a RIOT specific IPC function, and the flag itself is set whenever the BLE_L2CAP_EVENT_COC_TX_UNSTALLED is triggered:
[in the l2cap event callback]
        case BLE_L2CAP_EVENT_COC_TX_UNSTALLED:
            thread_flags_set(_main, FLAG_TX_UNSTALLED);
            break;

(Bad) results
Trying to send 100 chunks or 100byte each (similar results for different sized chunks), the nodes end up in the following state:
Node A (echo server):
2019-05-16 12:20:19,090 - INFO # main(): This is RIOT! (Version: 2019.07-devel-289-g8ccf8-opt_nimble_ver370305a)
2019-05-16 12:20:19,092 - INFO # NimBLE L2CAP test server
2019-05-16 12:20:19,094 - INFO # # now advertising
2019-05-16 12:20:26,780 - INFO # # GAP event 0
2019-05-16 12:20:26,833 - INFO # # L2CAP: CONNECTED
2019-05-16 12:20:26,836 - INFO # # MTUs: our 250, remote 250
2019-05-16 12:20:30,386 - INFO # # Received: len   100, seq     1
2019-05-16 12:20:30,389 - INFO # # Received: len   100, seq     2
2019-05-16 12:20:30,393 - INFO # # Received: len   100, seq     3
2019-05-16 12:20:30,396 - INFO # # Received: len   100, seq     4
2019-05-16 12:20:30,400 - INFO # # Received: len   100, seq     5
2019-05-16 12:20:30,403 - INFO # # Received: len   100, seq     6
2019-05-16 12:20:30,406 - INFO # # Received: len   100, seq     7
2019-05-16 12:20:30,410 - INFO # # Received: len   100, seq     8
2019-05-16 12:20:30,413 - INFO # # Received: len   100, seq     9
2019-05-16 12:20:30,417 - INFO # # Received: len   100, seq    10
2019-05-16 12:20:30,420 - INFO # # Received: len   100, seq    11
2019-05-16 12:20:30,423 - INFO # # Received: len   100, seq    12
2019-05-16 12:20:30,427 - INFO # # Received: len   100, seq    13
2019-05-16 12:20:30,430 - INFO # # Received: len   100, seq    14
2019-05-16 12:20:30,434 - INFO # # Received: len   100, seq    15
2019-05-16 12:20:30,437 - INFO # # Received: len   100, seq    16
2019-05-16 12:20:30,440 - INFO # # Received: len   100, seq    17
2019-05-16 12:20:30,444 - INFO # # Received: len   100, seq    18
2019-05-16 12:20:30,447 - INFO # # Received: len   100, seq    19
2019-05-16 12:20:30,450 - INFO # # Received: len   100, seq    20
2019-05-16 12:20:30,453 - INFO # # Received: len   100, seq    21
2019-05-16 12:20:30,457 - INFO # # Received: len   100, seq    22
2019-05-16 12:20:30,491 - INFO # # Received: len   100, seq    23
2019-05-16 12:20:30,537 - INFO # # Received: len   100, seq     0
2019-05-16 12:20:30,542 - INFO # # Received: len   100, seq 6555648
2019-05-16 12:20:30,546 - INFO # # Received: len   100, seq 6555648
2019-05-16 12:20:30,588 - INFO # # Received: len   100, seq 6555648
[ the last line is repeated forever ]

Node B (client):
2019-05-16 12:20:26,664 - INFO #  main(): This is RIOT! (Version: 2019.07-devel-289-g8ccf8-opt_nimble_ver370305a)
2019-05-16 12:20:26,667 - INFO # NimBLE L2CAP test application
2019-05-16 12:20:26,668 - INFO # # Scanning now
2019-05-16 12:20:26,782 - INFO # # Found Server, connecting now# GAP event: 0
2019-05-16 12:20:26,883 - INFO # # L2CAP: CONNECTED
2019-05-16 12:20:26,885 - INFO # # Connection established
2019-05-16 12:20:26,887 - INFO # # MTUs: our 250, remote 250
2019-05-16 12:20:26,889 - INFO # # Shell is now available
> flood 100 100
2019-05-16 12:20:30,355 - INFO #  flood 100 100
2019-05-16 12:20:30,358 - INFO # # Sending: size   100 seq     1
2019-05-16 12:20:30,361 - INFO # # Sending: size   100 seq     2
2019-05-16 12:20:30,364 - INFO # # Sending: size   100 seq     3
2019-05-16 12:20:30,367 - INFO # # Sending: size   100 seq     4
2019-05-16 12:20:30,370 - INFO # # Sending: size   100 seq     5
2019-05-16 12:20:30,373 - INFO # # Sending: size   100 seq     6
2019-05-16 12:20:30,375 - INFO # # Sending: size   100 seq     7
2019-05-16 12:20:30,378 - INFO # # Sending: size   100 seq     8
2019-05-16 12:20:30,381 - INFO # # Sending: size   100 seq     9
2019-05-16 12:20:30,384 - INFO # # Sending: size   100 seq    10
2019-05-16 12:20:30,387 - INFO # # Sending: size   100 seq    11
2019-05-16 12:20:30,391 - INFO # # Sending: size   100 seq    12
2019-05-16 12:20:30,395 - INFO # # Sending: size   100 seq    13
2019-05-16 12:20:30,398 - INFO # # Sending: size   100 seq    14
2019-05-16 12:20:30,401 - INFO # # Sending: size   100 seq    15
2019-05-16 12:20:30,404 - INFO # # Sending: size   100 seq    16
2019-05-16 12:20:30,408 - INFO # # Sending: size   100 seq    17
2019-05-16 12:20:30,411 - INFO # # Sending: size   100 seq    18
2019-05-16 12:20:30,414 - INFO # # Sending: size   100 seq    19
2019-05-16 12:20:30,417 - INFO # # Sending: size   100 seq    20
2019-05-16 12:20:30,421 - INFO # # Sending: size   100 seq    21
2019-05-16 12:20:30,424 - INFO # # Sending: size   100 seq    22
2019-05-16 12:20:30,428 - INFO # # Sending: size   100 seq    23
[stuck]

Node B gets stuck in the send loop, endlessly stalling and unstalling without ever leaving the loop (see code snip above).
Theory
Though don't fully understand the issue (yet), it seems to me that this has something to do with concurrency:
ble_l2cap_coc_send() is called in the thread context of the user application, leading subsequently to ble_l2cap_coc_continue_tx() also being called from that same context. In the same time, ble_l2cap_coc_continue_tx() is also called in the context of Nimbles host stack whenever there is a l2cap_coc related event. My guess is, that calling this function in parallel from two threads leads to some scrambled state and so the send function will never exit properly.
Any idea what we can do to fix this?

Ok, found it - seems like I was using the API in a bad way.
Simple changing the sending code to:
    res = ble_l2cap_send(_coc, txd);
    if (res == BLE_HS_ESTALLED) {
        thread_flags_wait_all(FLAG_TX_UNSTALLED);
    }

seems to solve my sending issues for good.
I am still not sure if there might be some concurrency issues left with ble_l2cap_coc_continue_tx(), but since my test cases are running fine with the code stated above, I consider this issue solved for now.

Just for completeness: I found the most efficient way to use the send function is:
    do {
        res = ble_l2cap_send(_coc, txd);
        if (res == BLE_HS_EBUSY) {
            // OS primitive to block the thread and wait for the
            //BLE_L2CAP_EVENT_COC_TX_UNSTALLED event, e.g.
            thread_flags_wait_all(FLAG_TX_UNSTALLED);
        }
    } while (res == BLE_HS_EBUSY);


iOS 8 filters many EXIF metadata fields. Example

This is a great component. Unfortunately it seems to fall foul of iOS's metadata filtering. The observation I'm making here seems to be supported pretty widely.
I'm not expecting there to be a fix for this. Just providing some documentation.
I provide two different views of exif data for an image on MacBook and iPhone.  If the image accessed from the iphone is sent by email, it still contains the full data. It's only when accessed through the browser that the data is filtered.
This is the image after transfer to MacBook, accessed in Photos folder via Chrome.
JsJpegMeta Demo

Choose JPEG file:

Image preview
JPEG File [JpegFile undefined Baseline DCT 3264x2448 Depth: 8]
General
Depth: 8
Pixel Height: 2448
Pixel Width: 3264
Type: Baseline DCT
Exif
Aperture Value: 2.2750072066878064
Brightness: 9.521337946943483
Color Space: 1
Exif Version: undefined
Exposure Bias Value: 0
Exposure Mode: 0
Exposure program: 2
Exposure time: 1 / 1319
FNumber: 2.2
Flash: 24
FlashPix Version: undefined
Focal Length: 4.15
Focal length in 35 mm film: 29
ISO Speed Ratings: 32
Manufacturer notes: undefined
Meaning of each component: undefined
Metering Mode: 5
Pixel X Dimension: 3264
Pixel Y Dimension: 2448
Scene Capture Type: 0
Scene Type: undefined
Sensing Method: 2
Shutter Speed: 10.365514501390544
Subject Area: 1631,1223,1795,1077
White Balance: 0
TIFF
Exif tag: 102
Orientation of image: 6
Resolution Unit: 2
X Resolution: 72
Y Resolution: 72
Y and C positioning: 1

This is the data viewed on the iPhone in Safari, on iOS 8.3. Masses of interesting data are filtered out.
JsJpegMeta Demo

Choose JPEG file:

JPEG File [JpegFile undefined Baseline DCT 3264x2448 Depth: 8]
General
Depth: 8
Pixel Height: 2448
Pixel Width: 3264
Type: Baseline DCT
Exif
Color Space: 1
Pixel X Dimension: 3264
Pixel Y Dimension: 2448
IPTC
JFIF
Density Unit: 0
JFIF Version: 1.1
Version Major: 1
Version Minor: 1
X Thumbnail: 0
X density: 72
Y Density: 72
Y Thumbnail: 0
TIFF
Exif tag: 38
Orientation of image: 6

Blueimp also is able to dump loads more data from the same file accessed via Chrome on a MacBook than via iOS.
https://blueimp.github.io/JavaScript-Load-Image/

Pretty conclusive
http://stackoverflow.com/questions/16297730/image-upload-from-iphone-strips-exif-data


Sudden drop in computing performance?

Hi, I was running the code from my computer (Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz and 12 GB RAM). I tried to train with 30k rows and 318 variables. But, it seems strange that there was sudden drop in the computing task that I didn't make any progress in fitting model/continue to next fold (I use 5 fold cross validation, 8 models in first layer and 1 model in second layer. And, I also use all of my 4 threads). Basically, with this data, I had sudden drop after 30 minutes running StackNet. Here is my screenshot from my last work.

I also tried to play with threads command, but nothing changed.

I have seen that before in windows...Strangely if you just press enter into the screen it continues. Not sure why this happens.... Can you try that and let me know?

Already tried it but nothing happened.

Strangely enough, this event also occurred when I ran the code from ubuntu.

That is indeed strange.  I have not seen that before... Does it always hang at the same place ? could you send me the file you run this and the parameters' file (as well as the command you run)  and tell me where I should expect the pause in order to try and replicate?

I'm also on Ubuntu 16.04 LTS I can give it a try if you wish.

Thanks guys. Here are the files.

ok got the files. just started stacknet on win8.1 and will let you know.

If you happen to produce output file, could you please send it back to me? Thanks.

Yeh sure ;-)
By the way looking at the param file I saw that RandomForest had 5 threads when you have 4 logical cores. Did you try reducing that number?
I'm just wondering if StackNet is not waiting for that thread to complete.

Ah I see. You seems right, but it should break at first fold, right? But now I try to run it again with modified threads param.

Issue reproduced. perf drops at 30% on the 5th fold and 4 first models.
3 metrics are displayed but not the 4th one.

Reducing the number of threads does not change the problem. However after reducing the number of estimators or iterations of the models I managed to get StackNet go through the all process...

OK. Could you please share that modified params?

I am also running it right now and will let you know the results . I have many cores available and did not encounter a problem at 2nd fold (e.g. I am in 4th now) , which makes me think this is in general related with threading...

It is reproduced.  Don't know why , but it seems to be at the predict() of the Softmaxclassifier . The reason CPU stops is not relevant - it has to do with the fact that we are in scoring and threading is not used. For some reason there must be a bug the code causing an infinite loop somewhere.
It does not throw error though..

I will try to find a workaround.

@arisbw, the reduced estimators were really low like 3 or 4... so it won't help you.
As @kaz-Anova said above, you may want to remove softmaxclassifier for now.

OK, I'll make sure to remove softmaxclassifier for now. Thank you @goldentom42 @kaz-Anova

@arisbw .
You dont need to remove it . You just change the seed of Softmax to 10 it works fine:
softmaxnnclassifier usescale:True seed:10 Type:SGD maxim_Iteration:35 C:0.0005 learn_rate:0.001 smooth:0.0001 h1:50 h2:40 connection_nonlinearity:Relu init_values:0.05 verbose:false
Honestly I have not a single clue why...
These are the results of all models:
Average of all folds model 0 : 0.7867379723430724
 Average of all folds model 1 : 0.7929649557885149
 Average of all folds model 2 : 0.7866359111370649
 Average of all folds model 3 : 0.7764824969782087
 Average of all folds model 4 : 0.7805320681382869
 Average of all folds model 5 : 0.7754102012289547
 Average of all folds model 6 : 0.7642405924462954
 Average of all folds model 7 : 0.7817682598159342

...... now it goes much weirder that I can imagine.


docs: cleanup storybook examples and clear warnings

Summary
Cleanup tasks uncovered as part of #488.

Remove mobile stories (those were a workaround before we had the storybook viewport installed)
remove deprecated props in our storybook examples (use size enum instead)
addParameters is deprecated

This will cause a Happo change since we remove 3 stories.
How To Test

tests run without errors
No other Happo changes besides the removed stories.

Warnings

:warning:
This PR does not include changes to tests, even though it affects source code.

  Generated by :no_entry_sign: dangerJS against 7f5c322138e2b3848dbd2b40486b723fff182c88


[bulk] Validation: add missing descriptions

Validation: add missing descriptions.
This PR fixes 30 files.

Docs Build status updates of commit 66208f3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

dynamics-nav/IMPORTSTREAM-Function--MediaSet-.md
:white_check_mark:Succeeded

dynamics-nav/INCSTR-Function--Code--Text-.md
:white_check_mark:Succeeded

dynamics-nav/INIT-Function--Record-.md
:white_check_mark:Succeeded

dynamics-nav/INIT-Function--RecordRef-.md
:white_check_mark:Succeeded

dynamics-nav/Import-Worksheet.md
:white_check_mark:Succeeded

dynamics-nav/ImportTranslate.md
:white_check_mark:Succeeded

dynamics-nav/InFooterBar-Property.md
:white_check_mark:Succeeded

dynamics-nav/IncludeCaption-Property.md
:white_check_mark:Succeeded

dynamics-nav/IncludeInDataSet-Property.md
:white_check_mark:Succeeded

dynamics-nav/IncludeSender-Property.md
:white_check_mark:Succeeded

dynamics-nav/Including-Microsoft-Dynamics-Online-Connect-on-Role-Centers.md
:white_check_mark:Succeeded

dynamics-nav/Indentation-Property--Query-.md
:white_check_mark:Succeeded

dynamics-nav/Indentation-Property--Reports-.md
:white_check_mark:Succeeded

dynamics-nav/Indentation-Property--XMLports-.md
:white_check_mark:Succeeded

dynamics-nav/IndentationColumnName-Property.md
:white_check_mark:Succeeded

dynamics-nav/IndentationControls-Property.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit a9968ec:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

dynamics-nav/IMPORTSTREAM-Function--MediaSet-.md
:white_check_mark:Succeeded

dynamics-nav/INCSTR-Function--Code--Text-.md
:white_check_mark:Succeeded

dynamics-nav/INIT-Function--Record-.md
:white_check_mark:Succeeded

dynamics-nav/INIT-Function--RecordRef-.md
:white_check_mark:Succeeded

dynamics-nav/INSERT--MODIFY--MODIFYALL--DELETE--and-DELETEALL-Functions.md
:white_check_mark:Succeeded

dynamics-nav/INSERT-Function--MediaSet-.md
:white_check_mark:Succeeded

dynamics-nav/INSERT-Function--RecordRef-.md
:white_check_mark:Succeeded

dynamics-nav/INSSTR-Function--Code--Text-.md
:white_check_mark:Succeeded

dynamics-nav/Import-Worksheet.md
:white_check_mark:Succeeded

dynamics-nav/ImportTranslate.md
:white_check_mark:Succeeded

dynamics-nav/InFooterBar-Property.md
:white_check_mark:Succeeded

dynamics-nav/InStream.EOS-Function.md
:white_check_mark:Succeeded

dynamics-nav/InStream.md
:white_check_mark:Succeeded

dynamics-nav/IncludeCaption-Property.md
:white_check_mark:Succeeded

dynamics-nav/IncludeInDataSet-Property.md
:white_check_mark:Succeeded

dynamics-nav/IncludeSender-Property.md
:white_check_mark:Succeeded

dynamics-nav/Including-Microsoft-Dynamics-Online-Connect-on-Role-Centers.md
:white_check_mark:Succeeded

dynamics-nav/Indentation-Property--Query-.md
:white_check_mark:Succeeded

dynamics-nav/Indentation-Property--Reports-.md
:white_check_mark:Succeeded

dynamics-nav/Indentation-Property--XMLports-.md
:white_check_mark:Succeeded

dynamics-nav/IndentationColumnName-Property.md
:white_check_mark:Succeeded

dynamics-nav/IndentationControls-Property.md
:white_check_mark:Succeeded

dynamics-nav/InitValue-Property.md
:white_check_mark:Succeeded

dynamics-nav/InlineSchema-Property.md
:white_check_mark:Succeeded

dynamics-nav/InsertAllowed-Property.md
:white_check_mark:Succeeded

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Global effort to fix build validation errors
@edupont04
The Content & Learning team is fixing build validation errors on docs.microsoft.com for the rest of H2. This will eliminate potential accessibility, security, and usability issues. This PR includes only build validation fixes and does not change other content. Please review within five business days and merge or comment in the PR with any changes you’d like to see. Thank you!


Add eodag stub package

When I run mypy on a code which import eodag, it claims that  Skipping analyzing "eodag": module is installed, but missing library stubs or py.typed marker
It is related to this page : https://mypy.readthedocs.io/en/stable/stubs.html
So for the moment I add a type ignore in the mypy config file but it could be interesting to create the stub package for eodag

Thanks for this feature request @savmickael !


Provide summary output format

It would be useful for testing of ORT on different systems and for the CI pipeline to get only a human readable summary of the analysis.
An example output that I use after parsing the analyzer-result.json file:
Elapsed time:14.979767084121704
Environment:
ort_version:0.1.0-SNAPSHOT
java_version:11.0.6
os:Linux
variables:{'SHELL': '/bin/bash', 'TERM': 'xterm-256color'}
tool_versions:{}
Has Issues: True
Issues:
analyzer ERROR:Multiple projects with the same id 'NPM:@netflixadseng:an-ER-fade-in:1.0.0' found. Not adding the project defined in 'https://github.com/NetflixDev/an-ER-fade-in.git/dist/npm/package.json' to the analyzer results as it duplicates the project defined in 'https://github.com/NetflixDev/an-ER-fade-in.git/src/package.json'.
Dependencies: 476
Dependencies while ignoring version numbers: 406
NPM::acorn-jsx:3.0.1
NPM::acorn:3.3.0
NPM::acorn:5.4.1
NPM::ajv-keywords:2.1.1
...

Closing this as it could easily be implemented with custom post-processing of the existing YAML / JSON result files.


chore: Support spotbugs running anywhere

Issue #, if available: n/a
Because spotbugs relies on a relative path to find its configuration and license-header, you can't run mvn install from arbitrary subdirectories in the project successfully. For instance - powertools-parameters - mvn install will fail here with an inability to find the license-header file. This maven.multiModuleProjectDirectory variable only gets set to the actual project root if a .mvn directory exists.
By doing this we can easily use it to find files relative to the root without having to specify some relative path property in every single POM.

Checklist

[ ] Meet tenets criteria
[ ] Update tests
[ ] Update docs
[ ] PR title follows conventional commit semantics

Breaking change checklist

RFC issue #:

[ ] Migration process documented
[ ] Implement warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

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

:exclamation: No coverage uploaded for pull request base (v2@b139a96). Click here to learn what that means.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@          Coverage Diff          @@
##             v2    #1537   +/-   ##
=====================================
  Coverage      ?   87.21%
  Complexity    ?      530
=====================================
  Files         ?       61
  Lines         ?     1854
  Branches      ?      230
=====================================
  Hits          ?     1617
  Misses        ?      163
  Partials      ?       74

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

If I understand correctly, it's not only spotbugs but also checkstyle


docs: blogpost 1.9.0

📜 Description
Added new blogpost for upcoming 1.9.0 release.
💡 Motivation and Context
I want to highlight new key features of the release.
Additionally I want to make an overview of achievements, so I've decided to combine everything into a single blogpost 🙂
📢 Changelog
Docs

added a new blogpost;

🤔 How Has This Been Tested?
Tested on localhost:3000 and via preview.
📝 Checklist

[x] CI successfully passed

Thanks @hirbod @IvanIhnatsiuk @ksugaevskaya @MarceloPrado @mrtawil for your help and support! 🙌


[VM] _JsonUtf8Parser fails on UTF-8 with BOM

Dart SDK 2.0.0-dev.58.0
import 'dart:convert';

void main() {
  final data = [0xEF, 0xBB, 0xBF, 0x7B, 0x7D]; // BOM { }

  print(json.decode(utf8.decode(data))); // prints "{ }"

  print(utf8.decoder.fuse(json.decoder).convert(data)); // fails in VM
}

The code above runs fine when compiled to JS but fails in Dart VM:
Unhandled exception:
FormatException: Unexpected character (at offset 0)
#0      _ChunkedJsonParser.fail (dart:convert-patch/dart:convert/convert_patch.dart:1362)
#1      _ChunkedJsonParser.parseNumber (dart:convert-patch/dart:convert/convert_patch.dart:1258)
#2      _ChunkedJsonParser.parse (dart:convert-patch/dart:convert/convert_patch.dart:926)
#3      _JsonUtf8Decoder.convert (dart:convert-patch/dart:convert/convert_patch.dart:65)
#4      main

That should probably be accepted.
While a BOM is not recommended for UTF-8 encoding, it does happen.

I'm more concerned that there's a difference between Dart VM and compiled JS behavior. It complicates writing portable code.
Normative docs on this matter are kinda mixed.
From RFC-7159 (JSON), section 8.1

Implementations MUST NOT add a byte order mark to the beginning of a JSON text.  In the interests of interoperability, implementations that parse JSON texts MAY ignore the presence of a byte order mark rather than treating it as an error.

But the ES 5.1/6.0 (ECMA-262) definitions of JSON white-space don't include BOM, so JSON.parse shouldn't accept it. But since the code above works, I suspect that JS runtime removes BOM from the string beforehand.

@lrhn Is there any chance that someone from Dart team will be able to fix this soon?
If not, I could prepare a CL myself because it's apparently a blocking issue for me (so instead of putting the workaround into my app it could be implemented in the SDK).

I'll look into it today. If it turns out to be easy, I'll fix it, otherwise it'll have to wait until we fine some idle resource to handle it.


adding pattern to go from tensor.reshape to flow.tensor.reshape

working on one more optimization, will reopen once done

You can leave PRs open and push more changes to reduce noise. Marking them as draft tells reviewers that you aren't ready for the full review.
RE this change: please describe why this is required now (it hasn't been until now) and add tests.

We were working on adding a fallback case in torch-mlir for aten.view that lowers into tensor::reshape. This tensor op is not supported in IREE and needs to be converted to a flow.tensor.reshape operation. Therefore, this change. Although we are not proceeding with the tensor::reshape fallback in torch-mlir, we decided we can still add the IREE implementation just so that tensor::reshape is supported.

had to make some changes (realized that for flow tensor you only add to the result dims if it is dynamic). So, now it successfully lowers and here is the IR Dump if it helps: `// -----// IR Dump After ConvertToFlow (iree-flow-convert-to-flow) //----- //
module {
func.func @static_tensor_reshape(%arg0: tensor<2x4xf32>, %arg1: tensor<2xindex>) -> tensor<1x8xf32> {
%0 = flow.tensor.reshape %arg0 : tensor<2x4xf32> -> tensor<1x8xf32>
return %0 : tensor<1x8xf32>
}
}
module {
func.func @static_tensor_reshape(%arg0: tensor<2x4xf32>, %arg1: tensor<2xindex>) -> tensor<1x8xf32> {
%0 = flow.tensor.reshape %arg0 : tensor<2x4xf32> -> tensor<1x8xf32>
return %0 : tensor<1x8xf32>
}
}
// -----
// -----// IR Dump After ConvertToFlow (iree-flow-convert-to-flow) //----- //
module {
func.func @dynamic_tensor_reshape(%arg0: tensor<2x4xf32>, %arg1: tensor<2xindex>) -> tensor<?x?xf32> {
%c0 = arith.constant 0 : index
%c1 = arith.constant 1 : index
%0 = flow.tensor.load %arg1[%c0] : tensor<2xindex>
%1 = flow.tensor.load %arg1[%c1] : tensor<2xindex>
%2 = flow.tensor.reshape %arg0 : tensor<2x4xf32> -> tensor<?x?xf32>{%0, %1}
return %2 : tensor<?x?xf32>
}
}
module {
func.func @dynamic_tensor_reshape(%arg0: tensor<2x4xf32>, %arg1: tensor<2xindex>) -> tensor<?x?xf32> {
%c0 = arith.constant 0 : index
%c1 = arith.constant 1 : index
%0 = flow.tensor.load %arg1[%c0] : tensor<2xindex>
%1 = flow.tensor.load %arg1[%c1] : tensor<2xindex>
%2 = flow.tensor.reshape %arg0 : tensor<2x4xf32> -> tensor<?x?xf32>{%0, %1}
return %2 : tensor<?x?xf32>
}
}`

Change looks good to me. One thing to verify though. The shape of the tensor should be created from tensor.from_elements. Can we make sure (and maybe add a lit test) to ensure that the tensor.from_elements gets folded away. (you probably will need to add -canonicalize to the RUN command).

Added in the tensor.from_elements test and have updated the IR dump with new tests in previous comment (works fine).


Bind source to Observable

Hi, guys.
Is it possible to bind the source property to an Observable? It seems it only supports array or string.
My use case: I have a method in a service that does some async processing and then returns an Observable array. I want to bind the auto-complete to this method.
Thanks!

I agree with you. We should accept a Observable or Promise as source. Will try Observable first.

Agreed, thank you. I was going to request accepting an error handling function when binding to a URL so that the error isn't ignored (line 174 autocomplete.component.ts). My use case is that the URL is an internal restful service that requires authentication, and I need to handle 401. But binding to an Observable would allow me to call the service the way I normally do rather than using the URL directly, and to handle the response.

This has been released with 0.6.4.

@andregs Is the issue resolved now? if so we need to close the issue

Thank you!


Support export to multiple repositories

related to: https://github.com/cstanislawski/grafana-db-exporter/issues/1
but since that wasn't possible then there's no need more justified need to export to multiple repos


updates olm template to remove avo config

Removes the AvoConfig ConfigMap from olm template as this is being moved into FR App Interface using Namespace files
Updates the README to highlight the locations of various configurations for this operator for the FedRAMP environment

/lgtm
/approve


[TASK] Implement logic/UI for staking tokens from DOT to tgDOT

Description
Develop the staking flow (stake, bond, mint) for converting DOT to tgDOT. This flow should be generalized for other tokens (i.e., GLMR to tgGLMR, MANTA to tgMANTA, ASTR to tgASTR etc.) The Stake/Unstake interface/components can be reused from the Hubble Bridge UI.
Requirements
Parachain Selection:

User can select their source parachain via a dropdown icon. This selection will determine the display of the token that is being staked.

Dynamic Rendering of tgTokens:

Post chain selection and amount input, the interface should dynamically calculate and display the estimated LST (Liquid Staking Token) that the user will receive on the Tangle Parachain.

Tx Details Section:

The 'Details Section' above the stake button must display the staking 'Rates', 'Cross-chain Fees', and the 'Unstake Period' clearly for user reference.

Transaction Process:

The staking process will consist of two key transactions:

Cross-in Transaction: Users sign to transfer tokens from the source parachain (e.g., Polkadot) to the Tangle Parachain.
Staking Transaction: Users stake the transferred tokens on the Tangle Parachain to mint tgTokens (e.g., tgDOT).

Overview Card:

Staking: Display the total amount of tokens currently being staked (e.g., DOTs) on Tangle Parachain.
Available: Show the total amount of liquid tokens (e.g., tgDOTs) that have been minted from staking and are presently available on the Tangle Parachain. It is imperative that this amount adjusts dynamically if tokens are being bridged out of Tangle Parachain to the Tangle Mainnet, reflecting real-time availability.
Unstaking: the total amount of tokens that are currently in the process of unstaking or unbonding. This gives users a clear view of assets that are exiting the staking process but are not yet fully liquid.
APY: Provide the current Annual Percentage Yield (APY) associated with the token. We can consider displaying a historical view in future iteration.
Explorer Button: provide users with the ability to view detailed tgToken information via a direct link to the blockchain explorer.
After successful transactions, the Overview Card must refresh to show updated balances including the newly minted LST amounts.

Error Handling:

Implement comprehensive error handling strategies to manage and inform users of insufficient balances, invalid inputs, or transaction failures. Confirmation dialogs and success messages should confirm the completion of each transaction stage.

Screenshot

Figma Link

Claiming this one if you don't mind! 🙂 @devpavan04


fix (Apple)Clang warnings (and maybe errors)

Warnings: https://github.com/Microsoft/LightGBM/pull/1522#issuecomment-404970003
They should be fixed:

@guolinke

I think all these warning should be fixed, at least set some ignore tags in cmake.

Errors: https://github.com/Microsoft/LightGBM/pull/1522#issuecomment-404973928 https://github.com/Microsoft/LightGBM/pull/1522#issuecomment-404983245
ping @guolinke @chivee @henry0312

according to this , thread_local was supported since AppleClang 8. I think we might set the minimum version to that.
as for the std::move error, I'll create an patch for that.
ref

@chivee Thank you!
Unfortunately, AppleClang 8.0 fails with segfault: https://github.com/Microsoft/LightGBM/pull/1522#issuecomment-404983245

@StrikerRUS Then we could change the title and leave it for people searching for answers.

@chivee "... and below" is already answered by you previously :-)

according to this , thread_local was supported since AppleClang 8. I think we might set the minimum version to that.

However, warnings https://github.com/Microsoft/LightGBM/pull/1522#issuecomment-404970003 are still not fixed.
To be honest, I'd like close this issue after fixing warnings. 8.1 is good version to start support and users are protected from 8.0 segfaults by these lines
https://github.com/Microsoft/LightGBM/blob/c78f26ed9e20575ab770d0dfa2800d9438c0f4c6/CMakeLists.txt#L28-L30

@StrikerRUS  Yes, I mean to change to the title so that the user knows well why we don't offer the support of version below 8.1

@chivee Of course, as you wish!


Allow omitting flags by passing None [phab:D2000]

Created by shahms at 2017-10-30 20:47:31:
Allow omitting flags by passing None
Indexers don't always support all of the same flags, so allow omitting them.

schroederc accepted this revision at 2017-10-30 20:51:51

shahms closed via commit 52ea8c6fa9cd8218bc0f9f852162093b2a52cf4c at 2017-10-30 21:08:27


fix(dict): emit the property access explicitly in @dict classes,

even though the usage is allowed without it.
Fixes #82.

LGTM

merged as 38f2049


Move MethodDescriptor out from JavaModuleWrapper

Move MethodDescriptor out from JavaModuleWrapper. This pr aim to enable MethodDescriptor instance out of JavaModuleWrapper and make auto generated code more graceful.
Test Plan
BaseJavaModuleTest.java had been changed to cover these changes

This pr is one of a series prs derive from old PR, which had proved to accelerate getMethodDescriptors and invoke methods
of native modules by nearly 60x, checkout and run benchmark: BenchMark.
The plan as follows:

Move MethodDescriptor out from JavaModuleWrapper
Add AcJavaModuleWrapper and replace JavaModuleWrapper with AcJavaModuleWrapper
Add ReactNativeModuleProcessor to handle ReactMethod annotations
Add library project to enable ReactNativeModuleProcessor and ReactPropertyProcessor
Update build.gradle file to enable annotations processors during build time
Provide compiler to optimize code write by app developers.


[Content Experience ]fix wrong column resizing handle insertion

Summary
This is an adoption of a fix from https://github.com/ProseMirror/prosemirror-tables/pull/79 but I included test to make sure that number of decorations are returning back properly.
Asana tasks:
https://app.asana.com/0/1117482789486653/1199983280453673/f
Relevant deployment: webapp (product + JS API)
Reason this is safe to merge before code review
N/A -- I plan to have this code reviewed before merging.


Add new comment counter

Hello @tarikbouari ,
please review my task.

I successfully added a counter for the comments in the application.
I ensured there were no linter errors.
I ensured I followed html, css and javascript best practices.

Hi @summyalena ,
Good job so far. Your project is approved. it's time to merge it
Highlights

Good documentation ✔
Good usage of Githubflow ✔

Cheers and Happy coding!👏👏👏 💻
Please feel free to reach out or leave any questions or comments on the issue if you find anything unclear


feat(reporting): add PR status indicator for a11y audit

This PR adds a status reporter for our a11y audit, which can now be ran automatically as part of a standard build on travis.
After a travis build is kicked off, the audit runs. Once the audit has started, a new status will be reported to the PR in a "pending" status. For example, like the screenshot below.

Once the audit has completed:
If the total number of violations has increased beyond the threshold we've set (currently 18) we'll fail the build and include a status reported back to the PR so users can understand what went wrong more quickly. For example, like in the screenshot below.

If the total number of violations is below the active threshold, we include a status back to the PR indicating success scenario. For example, like in the screenshot below.

Status can also be seen from commit view. For example, like in the screenshot below.

Steps taken toward making our a11y audit tool available "as a service" by allowing configuration to be passed in like node ./test-a11y/ -c path/to/config.json
Contents of a config file could look like
{   "toleranceThreshold": 1 }
use github statuses api for reporting back to open PR's
refactor a11y audit control flow to rely on promises
introduce utils and config
allow for passed in config with -c flag

Deploy preview for pf-next ready!
Built with commit 3d556859e83e228ebfa4e16e88c269ba089bbe71
https://deploy-preview-636--pf-next.netlify.com

@seanforyou23 looks like this is good to merge once we get the conflicts resolved. Great work!

:tada: This PR is included in version 1.0.31 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


405 (Method Not Allowed) PUT

Hello,
I have been using this tool weekly for years with great pleasure, but recently something changed/broke (on Spotify's side I think):
When clicking the "Make Playlist" button, I get an error:
PUT 405 (Method Not Allowed), on the clearPlaylist method.

It would be great if you can look into this

Oh hey, thank you for using my ancient web app! It seems that, in the nearly 8 years since I looked at the implementation, the Spotify API has been updated such that the endpoints for listing and viewing playlists have remained the same, but endpoints for editing playlists have changed. I'm going to implement the API changes soon so I can get this back up and running again.

Hey @ricardodebeijer; everything should be good now. I've pushed a new Docker image, updated my website with the newest version, and tested that I can create playlists. Let me know if it works for you.

Yes, pulled the latest version and now the playlist is created.
Thanks for the quick fix 👍


Start macOS client on login

Add settings checkbox to enable/disable "Start Firezone application at login". Note this is different from #2307

Closing, not a requested feature. Can reopen if/when that's so


Wechaty account logout unexpectedly

Description
Since account login successfully, wechaty run in Ubuntu Server, but after several hours, the account logout unexpectedly.
Trace

^[[31m[2016-10-06 22:19:26.753] [ERROR] console - ^[[39mERR PuppetWebServer initEventsFromClient() client on error: TypeError: Cannot read property 'bridge' of undefined
    at new MediaMessage (/root/git/chatbot-mvp/philly-wechat/node_modules/wechaty/src/message-media.js:18:33)
    at PuppetWeb.onServerMessage (/root/git/chatbot-mvp/philly-wechat/node_modules/wechaty/src/puppet-web/event.js:365:11)
    at emitOne (events.js:96:13)
    at Server.emit (events.js:188:7)
    at Socket.client.on.data (/root/git/chatbot-mvp/philly-wechat/node_modules/wechaty/src/puppet-web/server.js:149:14)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at Socket.onevent (/root/git/chatbot-mvp/philly-wechat/node_modules/socket.io/lib/socket.js:335:8)
    at Socket.onpacket (/root/git/chatbot-mvp/philly-wechat/node_modules/socket.io/lib/socket.js:295:12)
    at Client.ondecoded (/root/git/chatbot-mvp/philly-wechat/node_modules/socket.io/lib/client.js:193:14)
^[[32m[2016-10-06 22:19:26.755] [INFO] console - ^[[39mINFO Bot 小白 logouted
^[[32m[2016-10-06 22:20:12.745] [INFO] console - ^[[39mINFO Bot error: [object Object]
^[[33m[2016-10-06 22:20:12.893] [WARN] console - ^[[39mWARN PuppetWebEvent onBrowserDead() will not init browser because browser.targetState(close) !== open

Is it a bug? Or what is the solution to keep it steady?
One solution is auto restart when getting crash.

this problem is fixed yesterday.
u can pull the latest code to hav a try.
and please be careful because master branch is in heavy developing this week.
I will tag  a stable version later.

fixed by this commit:
https://github.com/wechaty/wechaty/commit/c589150e4bf42e66cb1f1690fffb89652ec9977c

verified. problem is fixed.


sops: 3.7.1 -> 3.7.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/mozilla/sops/releases.
meta.description for sops is: "Mozilla sops (Secrets OPerationS) is an editor of encrypted files"
meta.homepage for sops is: "https://github.com/mozilla/sops"
meta.changelog for sops is: "https://github.com/mozilla/sops/raw/v3.7.2/CHANGELOG.rst"
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/l7q8wlwx6j6fcbwqif3pni3m374q9cbr-sops-3.7.2/bin/sops had a zero exit code or showed the expected version
0 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 3.7.2 with grep in /nix/store/l7q8wlwx6j6fcbwqif3pni3m374q9cbr-sops-3.7.2
found 3.7.2 in filename of file in /nix/store/l7q8wlwx6j6fcbwqif3pni3m374q9cbr-sops-3.7.2

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
sops

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/l7q8wlwx6j6fcbwqif3pni3m374q9cbr-sops-3.7.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A sops https://github.com/r-ryantm/nixpkgs/archive/1a0517507818f0ca726f8daf3708e732e8511ccd.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/l7q8wlwx6j6fcbwqif3pni3m374q9cbr-sops-3.7.2
ls -la /nix/store/l7q8wlwx6j6fcbwqif3pni3m374q9cbr-sops-3.7.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

sops

Maintainer pings
cc @marsam @kalbasit for testing.

This release only has some bugfixes which are also interesting for stable.


import custom data

Hi,
Thanks for this new package, I am excited to try it out.
I had some troubles importing custom data. Just to let you know, I finally managed to resolve them by assigning
file_name="test"
before running the summarizing analysis. Is that expected ?
This is what happened :
I have one file ('xlsx' transformed to tsv) with each sample as one column. I have made an import file scheme that seems to be working with warnings
Here is what it looks like :
category	column_defined	column_import	pattern_extract	pattern_remove	pattern_split	pivot
sample	sample		(?<=abundance_)[:alnum:]+_R[0-9]
sample	sample_file		abundance_[:alnum:]+_R[0-9]
identifier	protein	^accession$
quantitative	abundance_raw	^abundance_*				TRUE
accounting	num_peptides	peptides
accounting	num_unique_peptides	Quantified peptides
The column with the abundance are named : abundance_sample_replicate (ex : abundance_1h_R2)
the error :
`> data_prot="data_import.tsv" %>% import("test","proteins",path=lib_scheme)
ℹ Importing test:
ℹ ... no homology detected
ℹ ... match between runs not found in data
✔ ... parsing data_import.tsv [341ms]
✔ ... tidying the data and finishing up [229ms]
Warning message:
One or more parsing issues, call problems() on your data frame for details, e.g.:
dat <- vroom(...)
problems(dat)

data_prot %>% summary()
Error in "id" %in% names(args):
! Could not evaluate cli {} expression: basename(file_name).
Caused by error in basename(file_name):
! object 'file_name' not found
Type .Last.error to see the more details.

.Last.error
<rlib_error_3_0/rlib_error/error>
Error in "id" %in% names(args):
! Could not evaluate cli {} expression: basename(file_name).
Caused by error in basename(file_name):
! object 'file_name' not found

Backtrace:

data_prot %>% summary()
base::summary(.)
tidyproteomics:::summary.tidyproteomics(.)
tidyproteomics:::tidyproteomics_summary(object, ...)
data %>% stats_summary()
tidyproteomics:::stats_summary(.)
cli::cli_progress_cleanup()
cli::cli_progress_done(clienv$progress[[n]]$id)
h$complete(pb, .envir = .envir, result = result)
cli::cli_status_clear(bar$cli_statusbar, result = result, msg_done = bar$format_done %||% …
cli:::cli__message("status_clear", list(id = id %||% NA_character_, …
"id" %in% names(args)
cli:::glue_cmd(msg_done, .envir = .envir)
cli:::glue(str, .envir = .envir, .transformer = transformer, .cli = TRUE, …
(function (expr) …
.transformer(expr, .envir) %||% character()
local .transformer(expr, .envir)
cli:::glue(text, .envir = envir, .transformer = sys.function(), .cli = TRUE)
(function (expr) …
.transformer(expr, .envir) %||% character()
local .transformer(expr, .envir)
cli:::glue(text, .envir = envir, .transformer = sys.function(), .cli = TRUE)
(function (expr) …
.transformer(expr, .envir) %||% character()
local .transformer(expr, .envir)
eval(expr, envir = envir) %??% cli_error(call. = caller, "Could not evaluate cli {.code {{}…
cli:::chain_error(expr, err, srcref = utils::getSrcref(sys.call()))
| base::withCallingHandlers({ …
base::eval(expr, envir = envir)
base::eval(expr, envir = envir)
base::basename(file_name)
base::.handleSimpleError(function (e) …
| local h(simpleError(msg, call))
| cli:::throw_error(err, parent = e)
`

while I have no issue with the plot_pca() function...
Sorry for the messy message,

Thank you for the feedback. I am assuming (perhaps incorrectly) you are unfamiliar with the %>% operator -- this allows you to place the object on the "left" into the first variable required by the function, in this case the file has been assigned "data_import.tsv", with "test" being assigned to the Platform (eg. ProteomeDiscoverer) and "proteins" assigned to the analyte type. I can't fined the location of the error message in the current version v1.7.1, which looks like it is coming from summary(). If you would like to email the corresponding author in the publication with and example of your data and import file, I can attempt to track it down and/or provide an improved import definition file.

I seen, I am familiar with the "%>%". I am not sure what the problem is but as it is fixed(-ish), no need to email the authors. Thanks !


A tab which shows the covid cases distribution in every state

@aakash1313 Discuss this with our designer Vanessa Milan. Ask her to share our Figma design files with you. And make sure this is brought up at sync so it gets sign off from the others. If this is to be included, it will need to go through some design reviews with Vanessa and a couple others of us.
I know that Vanessa is trying to add some designs that take into account some comments by behavioral scientists like to add "health points" and other things.


Add iproute2 package to heroku-18

This will add the ip command, which is already present on cedar-14 and heroku-16. It is required for heroku-exec.

@tt done

@dmathieu this will end up blocking heroku-18 from shipping, so you might want to do it yourself if I don't get to it soon.

If it helps, the quick way to ensure all the necessary files are updated (and because local testing is quicker than waiting for Travis :-)), is to follow the steps here:
https://github.com/heroku/stack-images/blob/master/BUILD.md#building-stack-images-locally
After building the images, the script updates the installed-packages.txt files locally for you.


Incomplete documentation

Type of issue
Code doesn't work
Description
The documentation on the Learn Microsoft website is not fully developed and there is only confusion, no simplicity, no ease in understanding everything, which costs a lot of nerves on this website, please do something about it so that everything changes for the better. :-(
Page URL
https://learn.microsoft.com/pl-pl/dotnet/desktop/wpf/get-started/create-app-visual-studio?view=netdesktop-8.0
Content source URL
https://github.com/dotnet/docs-desktop/blob/main/dotnet-desktop-guide/net/wpf/get-started/create-app-visual-studio.md
Document Version Independent Id
cce4458e-b162-09f3-48ea-b4481aa4c183
Article author
@adegeo

I hear you. The content for .NET Framework WPF is still available and is 90% compatible with .NET WPF. Is there something you want to see specifically for .NET WPF?


State Graphs

For facets, use best judgement if by state, decade, year, or region.

maybe make all states light grey and just choose outline outlier states and maybe regional averages.

Party by state and year
Min Wage by state and year (include fed (facet or use by decades where necessary)
Adjusted Min Wage by state and year (include adjusted fed (facet or use by decades where necessary)
Union employment, CB employment, and full employment (facet by decade)
percent union and percent collective bargaining

graph 3
figure out spacing of graph
can't do a line for federal minimum wage unless faceted by year instead of decade

graph 5
should we take the average value per decade?
add labels for each type of employment
fix spacing because union employment count is not visible

we did this


About the Coarse and Fine acoustic modeling

Hi, I try to using your code to reproduce AudioLM.  I found that your  CoarseTransformer model is based on self-attention. In the AudioLM paper, they assert ". During training, we use random cropping to equivalent input lengths of 30, 10 and 3 seconds for the three stages". Considering their soundstream is 320 downsample, which means that 1s audio including 50 tokens. 10s audio inlcudes 500 tokens for one codebook, and soundstream inlcudes more than 4 codebook. I want to know whether CoarseTransformer  can deal with such long sequence?  Do you have any idea to solve the long sequence problem?

It's a good question. Obviously the compute required for Transformers doesn't scale nicely with sequence length but I would just try and train a model with the maximum sequence length your compute budget can allow and see how you get on. @lucidrains has already implemented a bunch of Transformer models that are more efficient on long sequences but it would appear that most folks are sticking with fairly vanilla architectures for audio language models right now. It's definitely something that should be investigated though.

FWIW, I was able to lower data_max_length when training fine transformers (after initially running into an OOM), and still proceed to generate samples later on.  So I think to some degree you can accomplish this already by adjusting data_max_length in each training stage (i.e. it does not need to be fixed).

i don't have the most optimal sampling code, but can code it up once people have something trained
the repository now has the best length extrapolation positional embeddings fwiw

i don't have the most optimal sampling code, but can code it up once people have something trained
the repository now has the best length extrapolation positional embeddings


Support publishing to Amazon SQS FIFO

Publishing to FIFO Amazon SQS queues take 2 additional message parameters not covered in message attributes: MessageGroupId which is required and MessageDeduplicationId which is optional.
Benthos would benefit from being able to parse metadata with this specific key name as these special message options when publishing to SQS.

@AdamGlazerMW, implemented: https://github.com/Jeffail/benthos/commit/8e2c7cdf08d1ab91b3961098d3200ba318818c2c


Remove strict version requirement for myst-parser

Describe the problem/need and solution
Myst-nb pins the myst-parser version; however, newer myst-parser versions have useful features I want to use in my docs.
Guide for implementation
No response
Tasks and updates
No response

Heya, this is already being handled, as part of #380.
It's not as simple as un-pinning though, there are numerous changes to the mys-parser API (I know, because I author both of them 😉)

Heya #380 is now merged supporting the latest MyST-Parser, and there should be a new release soon


In Search By Course Name, GE Search, and Search by instructor make the table invisible initially.

User Story
As a user I do not see the table header before I have searched so that I am not confused about missing data.
Acceptance Criteria

[ ] The table is not visible before the first search on the 3 searches indicated in the title
[ ] The table is still visible after the search, as usual.

Implementation Todos
Front end:

[ ] First thing that must be done in the front end code.
[ ] Second thing that must be done in the front end code.

Back end:

[ ] First thing that must be done in the back end code.
[ ] Second thing that must be done in the back end code.

Testing:

[ ] Front end tests pass and there is adequate coverage
[ ] Back end tests pass and there is adequate coverage

Closed because fixed by another PR, i.e. #273


Suggestion to change defaults

Hello.
I have a suggestion to change two defaults:

d3d9_filter: from 2 to 3. As I understand it, there's not an obvious reason not to prefer the best mode.
vsync: from false to true. Input lag would probably be barely noticeable due to the games being very old, and it would also fix tearing by default in cases where it is present (and FPS is already limited to the screen's refresh rate by default anyway).

Thanks for your attention.

hi!
The problem with 3 is that it doesn't look good for games that run on 256 colors (it's too sharp) - 2 does work for any games. Another problem is that 3 doesn't work on older hardware because it's too slow (10+ year old hardware will not get 60FPS)
vsync doesn't need to be enabled by default, there will be no tearing because cnc-ddraw doesn'T use fullscreen exclusive mode by default (DWM is always active) - The only exception to this rule are 2 C&C games (Red Alert 2 and Tiberian Sun), in those I kept fullscreen exclusive enabled by default


Add API switch and version to config

Graphics API and version should be provided and read from config::GraphicsSettings.

Closing - no current plans for other API support and we're currently sticking to an exact minor version to minimize development cost.


Add show/hide toggle to markdown preview panel

closed with https://github.com/yogthos/memory-hole/commit/0a8e84ad4f5e30d373b9d682a9942872028f29a5


with_terminal does not capture CSV.write output

with_terminal() do
	CSV.write(stdout, DataFrame(x=[1,2,3],y=[2,3,4]))
end

output is shown in the terminal which launched Pluto, and not inside the notebook:

I encountered the same problem with Pluto v0.17.1. Using a plain println works fine, specifying stdout causes the same effect described above:

together with
      From worker 2:	foo

in the terminal that launched Pluto.
I didn't check whether the problem still exists in the most recent version of Pluto (v0.18.1), though. Is there any progress on this? Working with Pluto is really fun, btw!

Is there an update on this problem?
I'm not sure whether it is related, but when I have a macro containing a println, the result is not printed either:
macro foo(e)
	println("In Foo")
	e
end

foo(1)


[Bugs] SCTP connection from ueransim VM to free5gc VM is not connecting

Describe the bug
I am trying to connect the free5gc from Ueransim VM through sctp connection. While trying to connect below are the error we are getting
root@ueransim:~/UERANSIM# build/nr-gnb -c config/free5gc-gnb.yaml
UERANSIM v3.2.6
[2023-10-03 05:42:06.270] [sctp] [info] Trying to establish SCTP connection... (<IP_ADDRESS>:38412)

Expected behavior
SCTP should connect to Free5GC VM
free5gc machine ip is <IP_ADDRESS>
ueransim machine ip is <IP_ADDRESS>
ping is also happening
root@ueransim:~/UERANSIM# ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=63 time=1.33 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=63 time=1.45 ms

from both sides
root@free5gc:~/free5gc/config# ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=63 time=1.33 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=63 time=0.877 ms

Screenshots
Please find attached screenshots
Environment (please complete the following information):

free5GC Version: [e.g. v3.3.0-15-g8b2ae3b]
OS: [e.g. Ubuntu 20.04 Server]
Kernel version: [e.g.5.4.0-163-generic ]
go version: [e.g. go1.20.8 linux/amd64]
c compiler version (Option): [e.g. gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0]

Trace File
Configuration File
Provide the configuration file here.
attached amf config file for refrence
UERANSIM VM - free5gc-gnb.yaml file
root@ueransim:~/UERANSIM/config# cat free5gc-gnb.yaml
mcc: '208'          # Mobile Country Code value
mnc: '93'           # Mobile Network Code value (2 or 3 digits)

nci: '0x000000010'  # NR Cell Identity (36-bit)
idLength: 32        # NR gNB ID length in bits [22...32]
tac: 1              # Tracking Area Code

#linkIp: <IP_ADDRESS>   # gNB's local IP address for Radio Link Simulation (Usually same with local IP)
linkIp: <IP_ADDRESS>   # gNB's local IP address for Radio Link Simulation (Usually same with local IP)
ngapIp: <IP_ADDRESS>   # gNB's local IP address for N2 Interface (Usually same with local IP)
gtpIp: <IP_ADDRESS>    # gNB's local IP address for N3 Interface (Usually same with local IP)
# List of AMF address information
amfConfigs:
  - address: <IP_ADDRESS>
    port: 38412

# List of supported S-NSSAIs by this gNB
slices:
  - sst: 0x1
    sd: 0x010203

# Indicates whether or not SCTP stream number errors should be ignored.
ignoreStreamIds: true

PCAP File
Tried to capture SCTP using - sudo tcpdump -i any sctp -nn and also with sudo tcpdump -i any host <IP_ADDRESS> -nn
No packets captured when trying to run free5gc-gnb.yaml
Log File
Free5GC VM:
log path: ./log/20231003_062751/
2023-10-03T06:27:51.422309591Z [INFO][UPF][Main] UPF version:
	free5GC version: v3.3.0-15-g8b2ae3b
	build time:      2023-10-02T08:32:38Z
	commit hash:     b192a9a8
	commit time:     2023-10-01T09:39:46Z
	go version:      go1.17.8 linux/amd64
2023-10-03T06:27:51.422427580Z [INFO][UPF][CFG] Read config from [./config/upfcfg.yaml]
2023-10-03T06:27:51.422778436Z [INFO][UPF][CFG] ==================================================
2023-10-03T06:27:51.422811041Z [INFO][UPF][CFG] (*factory.Config)(0xc00009c820)({
	Version: (string) (len=5) "1.0.3",
	Description: (string) (len=31) "UPF initial local configuration",
	Pfcp: (*factory.Pfcp)(0xc00009b290)({
		Addr: (string) (len=9) "<IP_ADDRESS>",
		NodeID: (string) (len=9) "<IP_ADDRESS>",
		RetransTimeout: (time.Duration) 1s,
		MaxRetrans: (uint8) 3
	}),
	Gtpu: (*factory.Gtpu)(0xc00009b440)({
		Forwarder: (string) (len=5) "gtp5g",
		IfList: ([]factory.IfInfo) (len=1 cap=1) {
			(factory.IfInfo) {
				Addr: (string) (len=13) "<IP_ADDRESS>",
				Type: (string) (len=2) "N3",
				Name: (string) "",
				IfName: (string) "",
				MTU: (uint32) 0
			}
		}
	}),
	DnnList: ([]factory.DnnList) (len=1 cap=1) {
		(factory.DnnList) {
			Dnn: (string) (len=8) "internet",
			Cidr: (string) (len=12) "<IP_ADDRESS>/24",
			NatIfName: (string) ""
		}
	},
	Logger: (*factory.Logger)(0xc0000a4a80)({
		Enable: (bool) true,
		Level: (string) (len=4) "info",
		ReportCaller: (bool) false
	})
})
2023-10-03T06:27:51.422872483Z [INFO][UPF][CFG] ==================================================
2023-10-03T06:27:51.422891782Z [INFO][UPF][Main] Log level is set to [info]
2023-10-03T06:27:51.422909115Z [INFO][UPF][Main] Report Caller is set to [false]
2023-10-03T06:27:51.422943370Z [INFO][UPF][Main] starting Gtpu Forwarder [gtp5g]
2023-10-03T06:27:51.422965889Z [INFO][UPF][Main] GTP Address: "<IP_ADDRESS>:2152"
2023-10-03T06:27:51.434874944Z [INFO][UPF][BUFF] buff netlink server started
2023-10-03T06:27:51.435075232Z [INFO][UPF][Perio] perio server started
2023-10-03T06:27:51.436275553Z [INFO][UPF][Gtp5g] Forwarder started
2023-10-03T06:27:51.437435160Z [INFO][UPF][PFCP][LAddr:<IP_ADDRESS>:8805] starting pfcp server
2023-10-03T06:27:51.437655245Z [INFO][UPF][PFCP][LAddr:<IP_ADDRESS>:8805] pfcp server started
2023-10-03T06:27:51.437914986Z [INFO][UPF][Main] UPF started
./run.sh: line 111: mongo: command not found
Current Mongosh Log ID:	651bb4670deff48f0caf3d1c
Connecting to:		mongodb://<IP_ADDRESS>:27017/free5gc?directConnection=true&serverSelectionTimeoutMS=2000&appName=mongosh+2.0.1
Using MongoDB:		7.0.2
Using Mongosh:		2.0.1

For mongosh info see: https://docs.mongodb.com/mongodb-shell/

------
   The server generated these startup warnings when booting
   2023-10-03T02:35:47.509+00:00: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine. See http://dochub.mongodb.org/core/prodnotes-filesystem
   2023-10-03T02:35:48.305+00:00: Access control is not enabled for the database. Read and write access to data and configuration is unrestricted
   2023-10-03T02:35:48.306+00:00: vm.max_map_count is too low
------

true
2023-10-03T06:27:53.583297358Z [INFO][NRF][Main] NRF version:
	free5GC version: v3.3.0-15-g8b2ae3b
	build time:      2023-10-03T03:44:20Z
	commit hash:     dbb285a4
	commit time:     2023-10-01T10:14:28Z
	go version:      go1.20.8 linux/amd64
2023-10-03T06:27:53.583485018Z [INFO][NRF][CFG] Read config from [./config/nrfcfg.yaml]
2023-10-03T06:27:53.584195709Z [INFO][NRF][Main] Log enable is set to [true]
2023-10-03T06:27:53.584262113Z [INFO][NRF][Main] Log level is set to [info]
2023-10-03T06:27:53.584299650Z [INFO][NRF][Main] Report Caller is set to [false]
2023-10-03T06:27:53.584329577Z [INFO][NRF][Init] nrfconfig Info: Version[1.0.2] Description[NRF initial local configuration]
2023-10-03T06:27:53.584566183Z [INFO][NRF][Init] Server starting
2023-10-03T06:27:53.585560647Z [INFO][NRF][Init] Binding addr: [<IP_ADDRESS>:8000]
2023-10-03T06:27:53.669464193Z [INFO][AMF][Main] AMF version:
	free5GC version: v3.3.0-15-g8b2ae3b
	build time:      2023-10-02T14:56:37Z
	commit hash:     +7907d3c
	commit time:     2023-05-20T15:04:00Z
	go version:      go1.17.8 linux/amd64
2023-10-03T06:27:53.669711679Z [INFO][AMF][CFG] Read config from [./config/amfcfg.yaml]
2023-10-03T06:27:53.671380150Z [INFO][AMF][Main] Log enable is set to [true]
2023-10-03T06:27:53.671417209Z [INFO][AMF][Main] Log level is set to [info]
2023-10-03T06:27:53.671437031Z [INFO][AMF][Main] Report Caller is set to [false]
2023-10-03T06:27:53.671461810Z [INFO][AMF][Util] amfconfig Info: Version[1.0.9]
2023-10-03T06:27:53.671582351Z [INFO][AMF][Init] Server started
2023-10-03T06:27:53.671812792Z [INFO][AMF][Util] amfconfig Info: Version[1.0.9]
2023-10-03T06:27:53.672300384Z [INFO][AMF][Ngap] Listen on <IP_ADDRESS>:38412
2023-10-03T06:27:53.674216106Z [INFO][NRF][NFM] Handle NFRegisterRequest
2023-10-03T06:27:53.676384746Z [INFO][NRF][NFM] urilist update
2023-10-03T06:27:53.735783288Z [INFO][NRF][NFM] Create NF Profile
2023-10-03T06:27:53.743125077Z [INFO][NRF][NFM] Location header:  http://<IP_ADDRESS>:8000/nnrf-nfm/v1/nf-instances/6ad2a9b2-338f-4ef2-993c-de61525389a3
2023-10-03T06:27:53.743847206Z [INFO][NRF][GIN] | 201 |       <IP_ADDRESS> | PUT     | /nnrf-nfm/v1/nf-instances/6ad2a9b2-338f-4ef2-993c-de61525389a3 |
2023-10-03T06:27:53.780098679Z [INFO][SMF][Main] SMF version:
	free5GC version: v3.3.0-15-g8b2ae3b
	build time:      2023-10-03T03:43:33Z
	commit hash:     ad97e3db
	commit time:     2023-10-01T10:20:36Z
	go version:      go1.20.8 linux/amd64
2023-10-03T06:27:53.780323537Z [INFO][SMF][CFG] Read config from [./config/smfcfg.yaml]
2023-10-03T06:27:53.784702439Z [INFO][SMF][CFG] Read config from [./config/uerouting.yaml]
2023-10-03T06:27:53.785486352Z [INFO][SMF][Main] Log enable is set to [true]
2023-10-03T06:27:53.785520793Z [INFO][SMF][Main] Log level is set to [info]
2023-10-03T06:27:53.785542362Z [INFO][SMF][Main] Report Caller is set to [false]
2023-10-03T06:27:53.785689911Z [INFO][SMF][CTX] smfconfig Info: Version[1.0.7] Description[SMF initial local configuration]
2023-10-03T06:27:53.785831473Z [INFO][SMF][CTX] Endpoints: [<IP_ADDRESS>]
2023-10-03T06:27:53.785902030Z [INFO][SMF][Init] Server started
2023-10-03T06:27:53.787953134Z [INFO][NRF][NFM] Handle NFRegisterRequest
2023-10-03T06:27:53.789432826Z [INFO][NRF][NFM] urilist update
2023-10-03T06:27:53.790249032Z [INFO][NRF][NFM] Create NF Profile
2023-10-03T06:27:53.791239352Z [INFO][NRF][NFM] Location header:  http://<IP_ADDRESS>:8000/nnrf-nfm/v1/nf-instances/80d8353c-e6b0-4763-8c5b-8775c2c59c4b
2023-10-03T06:27:53.791339936Z [INFO][NRF][GIN] | 201 |       <IP_ADDRESS> | PUT     | /nnrf-nfm/v1/nf-instances/80d8353c-e6b0-4763-8c5b-8775c2c59c4b |
2023-10-03T06:27:53.791965099Z [INFO][SMF][Init] SMF Registration to NRF {80d8353c-e6b0-4763-8c5b-8775c2c59c4b SMF REGISTERED 0 0xc0004ec150 0xc0004ec180 [] []   [<IP_ADDRESS>] [] <nil> [] [] <nil> 0 0 0 area1 <nil> <nil> <nil> <nil> 0xc0000ac1c0 <nil> <nil> <nil> <nil> <nil> map[] <nil> false 0xc0004ec048 false false []}
2023-10-03T06:27:53.792300535Z [INFO][SMF][PFCP] Listen on <IP_ADDRESS>:8805
2023-10-03T06:27:53.792365003Z [INFO][SMF][Main] Sending PFCP Association Request to UPF[<IP_ADDRESS>]
2023-10-03T06:27:53.792597400Z [INFO][UPF][PFCP][LAddr:<IP_ADDRESS>:8805] handleAssociationSetupRequest
2023-10-03T06:27:53.792731881Z [INFO][UPF][PFCP][LAddr:<IP_ADDRESS>:8805][CPNodeID:<IP_ADDRESS>] New node
2023-10-03T06:27:53.792884256Z [INFO][SMF][Main] Received PFCP Association Setup Accepted Response from UPF[<IP_ADDRESS>]
2023-10-03T06:27:53.905107105Z [INFO][UDR][Main] UDR version:
	free5GC version: v3.3.0-15-g8b2ae3b
	build time:      2023-10-03T03:41:09Z
	commit hash:     635ce049
	commit time:     2023-10-01T10:24:38Z
	go version:      go1.20.8 linux/amd64
2023-10-03T06:27:53.905298509Z [INFO][UDR][CFG] Read config from [./config/udrcfg.yaml]
2023-10-03T06:27:53.906213227Z [INFO][UDR][Main] Log enable is set to [true]
2023-10-03T06:27:53.906271709Z [INFO][UDR][Main] Log level is set to [info]
2023-10-03T06:27:53.906298437Z [INFO][UDR][Main] Report Caller is set to [false]
2023-10-03T06:27:53.906342744Z [INFO][UDR][Init] UDR Config Info: Version[1.0.2] Description[UDR initial local configuration]
2023-10-03T06:27:53.906739765Z [INFO][UDR][Init] Server started
2023-10-03T06:27:53.907184634Z [INFO][UDR][Util] udrconfig Info: Version[1.0.2] Description[UDR initial local configuration]
2023-10-03T06:27:53.909189717Z [INFO][NRF][NFM] Handle NFRegisterRequest
2023-10-03T06:27:53.910718584Z [INFO][NRF][NFM] urilist update
2023-10-03T06:27:53.911477163Z [INFO][NRF][NFM] Create NF Profile
2023-10-03T06:27:53.912491458Z [INFO][NRF][NFM] Location header:  http://<IP_ADDRESS>:8000/nnrf-nfm/v1/nf-instances/c11acb3c-1136-4917-beaf-d1c6cd0b9ae1
2023-10-03T06:27:53.912587126Z [INFO][NRF][GIN] | 201 |       <IP_ADDRESS> | PUT     | /nnrf-nfm/v1/nf-instances/c11acb3c-1136-4917-beaf-d1c6cd0b9ae1 |
2023-10-03T06:27:54.007143134Z [INFO][PCF][Main] pcf
2023-10-03T06:27:54.007233703Z [INFO][PCF][Main] PCF version:
	free5GC version: v3.3.0-15-g8b2ae3b
	build time:      2023-10-03T03:41:16Z
	commit hash:     56840a6e
	commit time:     2023-10-01T10:18:33Z
	go version:      go1.20.8 linux/amd64
2023-10-03T06:27:54.007548106Z [INFO][PCF][CFG] Read config from [./config/pcfcfg.yaml]
2023-10-03T06:27:54.009115207Z [INFO][PCF][Main] Log enable is set to [true]
2023-10-03T06:27:54.009154576Z [INFO][PCF][Main] Log level is set to [info]
2023-10-03T06:27:54.009252007Z [INFO][PCF][Main] Report Caller is set to [false]
2023-10-03T06:27:54.009283372Z [INFO][PCF][Util] pcfconfig Info: Version[1.0.2] Description[PCF initial local configuration]
2023-10-03T06:27:54.009500422Z [INFO][PCF][Init] Server started
2023-10-03T06:27:54.011473486Z [INFO][PCF][Util] pcfconfig Info: Version[1.0.2] Description[PCF initial local configuration]
2023-10-03T06:27:54.014927902Z [INFO][NRF][NFM] Handle NFRegisterRequest
2023-10-03T06:27:54.016400148Z [INFO][NRF][NFM] urilist update
2023-10-03T06:27:54.017220828Z [INFO][NRF][NFM] Create NF Profile
2023-10-03T06:27:54.018023114Z [INFO][NRF][NFM] Location header:  http://<IP_ADDRESS>:8000/nnrf-nfm/v1/nf-instances/cc516942-eb45-41f8-bb29-9c5e1f023db0
2023-10-03T06:27:54.018146131Z [INFO][NRF][GIN] | 201 |       <IP_ADDRESS> | PUT     | /nnrf-nfm/v1/nf-instances/cc516942-eb45-41f8-bb29-9c5e1f023db0 |
2023-10-03T06:27:54.018738657Z [INFO][NRF][DISC] Handle NFDiscoveryRequest
2023-10-03T06:27:54.019761760Z [INFO][NRF][GIN] | 200 |       <IP_ADDRESS> | GET     | /nnrf-disc/v1/nf-instances?requester-nf-type=PCF&service-names=nudr-dr&target-nf-type=UDR |
2023-10-03T06:27:54.103541026Z [INFO][UDM][Main] UDM version:
	free5GC version: v3.3.0-15-g8b2ae3b
	build time:      2023-10-03T03:41:25Z
	commit hash:     3aacf1cb
	commit time:     2023-10-01T10:22:20Z
	go version:      go1.20.8 linux/amd64
2023-10-03T06:27:54.103726807Z [INFO][UDM][CFG] Read config from [./config/udmcfg.yaml]
2023-10-03T06:27:54.104898048Z [INFO][UDM][Main] Log enable is set to [true]
2023-10-03T06:27:54.104939294Z [INFO][UDM][Main] Log level is set to [info]
2023-10-03T06:27:54.104956172Z [INFO][UDM][Main] Report Caller is set to [false]
2023-10-03T06:27:54.104971716Z [INFO][UDM][Init] UDM Config Info: Version[1.0.3] Description[UDM initial local configuration]
2023-10-03T06:27:54.105088112Z [INFO][UDM][Init] Server started
2023-10-03T06:27:54.105302614Z [INFO][UDM][Util] udmconfig Info: Version[1.0.3] Description[UDM initial local configuration]
2023-10-03T06:27:54.106988324Z [INFO][NRF][NFM] Handle NFRegisterRequest
2023-10-03T06:27:54.108529925Z [INFO][NRF][NFM] urilist update
2023-10-03T06:27:54.109278823Z [INFO][NRF][NFM] Create NF Profile
2023-10-03T06:27:54.110345164Z [INFO][NRF][NFM] Location header:  http://<IP_ADDRESS>:8000/nnrf-nfm/v1/nf-instances/2db0a209-0321-461b-82ae-4168ac15d81d
2023-10-03T06:27:54.110474766Z [INFO][NRF][GIN] | 201 |       <IP_ADDRESS> | PUT     | /nnrf-nfm/v1/nf-instances/2db0a209-0321-461b-82ae-4168ac15d81d |
2023-10-03T06:27:54.223359002Z [INFO][NSSF][Main] NSSF version:
	free5GC version: v3.3.0-15-g8b2ae3b
	build time:      2023-10-03T03:41:34Z
	commit hash:     8d35182a
	commit time:     2023-10-01T10:16:35Z
	go version:      go1.20.8 linux/amd64
2023-10-03T06:27:54.223543957Z [INFO][NSSF][CFG] Read config from [./config/nssfcfg.yaml]
2023-10-03T06:27:54.225913331Z [INFO][NSSF][Main] Log enable is set to [true]
2023-10-03T06:27:54.225971336Z [INFO][NSSF][Main] Log level is set to [info]
2023-10-03T06:27:54.225997532Z [INFO][NSSF][Main] Report Caller is set to [false]
2023-10-03T06:27:54.226079387Z [INFO][NSSF][Init] Server started
2023-10-03T06:27:54.228169422Z [INFO][NRF][NFM] Handle NFRegisterRequest
2023-10-03T06:27:54.229734201Z [INFO][NRF][NFM] urilist update
2023-10-03T06:27:54.230566272Z [INFO][NRF][NFM] Create NF Profile
2023-10-03T06:27:54.231656550Z [INFO][NRF][NFM] Location header:  http://<IP_ADDRESS>:8000/nnrf-nfm/v1/nf-instances/c441b909-484c-456e-9a43-1abde2910d17
2023-10-03T06:27:54.231797629Z [INFO][NRF][GIN] | 201 |       <IP_ADDRESS> | PUT     | /nnrf-nfm/v1/nf-instances/c441b909-484c-456e-9a43-1abde2910d17 |
2023-10-03T06:27:54.338336839Z [INFO][AUSF][Main] AUSF version:
	free5GC version: v3.3.0-15-g8b2ae3b
	build time:      2023-10-03T03:40:25Z
	commit hash:     d8b1a70c
	commit time:     2023-10-01T10:08:36Z
	go version:      go1.20.8 linux/amd64
2023-10-03T06:27:54.338470647Z [INFO][AUSF][CFG] Read config from [./config/ausfcfg.yaml]
2023-10-03T06:27:54.339397158Z [INFO][AUSF][Main] Log enable is set to [true]
2023-10-03T06:27:54.339433699Z [INFO][AUSF][Main] Log level is set to [info]
2023-10-03T06:27:54.339449352Z [INFO][AUSF][Main] Report Caller is set to [false]
2023-10-03T06:27:54.339623770Z [INFO][AUSF][Init] ausfconfig Info: Version[1.0.3] Description[AUSF initial local configuration]
ausf context =  &{{{0 0} {[] {} <nil>} map[] 0} {{0 0} {[] {} <nil>} map[] 0} 4ba5899b-6993-43cb-bb04-8289f19eba56 ausfGroup001 8000 <IP_ADDRESS> <IP_ADDRESS> http://<IP_ADDRESS>:8000 http http://<IP_ADDRESS>:8000 map[nausf-auth:{4ba5899b-6993-43cb-bb04-8289f19eba56 nausf-auth 0xc0000119b0 http REGISTERED   0xc000011998  [] <nil> [] [] <nil> 0 0 0 <nil> <nil>  }] [{208 93} {123 45}]  0xc0005da460 false}
2023-10-03T06:27:54.340136199Z [INFO][AUSF][Init] Server started
2023-10-03T06:27:54.344396000Z [INFO][NRF][NFM] Handle NFRegisterRequest
2023-10-03T06:27:54.345879864Z [INFO][NRF][NFM] urilist update
2023-10-03T06:27:54.346523073Z [INFO][NRF][NFM] Create NF Profile
2023-10-03T06:27:54.347476921Z [INFO][NRF][NFM] Location header:  http://<IP_ADDRESS>:8000/nnrf-nfm/v1/nf-instances/4ba5899b-6993-43cb-bb04-8289f19eba56
2023-10-03T06:27:54.347575443Z [INFO][NRF][GIN] | 201 |       <IP_ADDRESS> | PUT     | /nnrf-nfm/v1/nf-instances/4ba5899b-6993-43cb-bb04-8289f19eba56 |
2023-10-03T06:27:54.464615145Z [INFO][CHF][Main] CHF version:
	free5GC version: v3.3.0-15-g8b2ae3b
	build time:      2023-10-03T03:43:45Z
	commit hash:     f3762fe5
	commit time:     2023-10-01T10:09:44Z
	go version:      go1.20.8 linux/amd64
2023-10-03T06:27:54.464758022Z [INFO][CHF][CFG] Read config from [./config/chfcfg.yaml]
2023-10-03T06:27:54.465640333Z [INFO][CHF][Main] Log enable is set to [true]
2023-10-03T06:27:54.465677185Z [INFO][CHF][Main] Log level is set to [info]
2023-10-03T06:27:54.465696697Z [INFO][CHF][Main] Report Caller is set to [false]
2023-10-03T06:27:54.465713278Z [INFO][CHF][Init] chfconfig Info: Version[1.0.3] Description[CHF initial local configuration]
chf context =  &{f2f810a2-988c-4be1-a30d-027731814e91 CHF http://<IP_ADDRESS>:8000 http <IP_ADDRESS> <IP_ADDRESS> 8000 map[nchf-convergedcharging:{f2f810a2-988c-4be1-a30d-027731814e91 nchf-convergedcharging 0xc00090ded8 http REGISTERED   0xc00090dec0 http://<IP_ADDRESS>:8000 [] <nil> [] [] <nil> 0 0 0 <nil> <nil>  }] map[] 0 http://<IP_ADDRESS>:8000 {{0 0} {[] {} <nil>} map[] 0} 0xc00090f0e0 0xc00090f140 0xc000967470 0xc0009674d0}
2023-10-03T06:27:54.465883973Z [INFO][CHF][Init] Server started
2023-10-03T06:27:54.466301226Z [INFO][CHF][CGF] FTP server Start
2023-10-03T06:27:54.467217308Z [WARN][CHF][CGF] Login to Webconsole FTP fail: dial tcp <IP_ADDRESS>:2122: connect: connection refused, retrying [1]
2023-10-03T06:27:54.468407760Z [INFO][CHF][Acct] Open Account Balance Management Server
2023-10-03T06:27:54.471462992Z [INFO][NRF][NFM] Handle NFRegisterRequest
2023-10-03T06:27:54.473867317Z [INFO][NRF][NFM] urilist update
2023-10-03T06:27:54.474547210Z [INFO][NRF][NFM] Create NF Profile
2023-10-03T06:27:54.475336170Z [INFO][NRF][NFM] Location header:  http://<IP_ADDRESS>:8000/nnrf-nfm/v1/nf-instances/f2f810a2-988c-4be1-a30d-027731814e91
2023-10-03T06:27:54.475398834Z [INFO][NRF][GIN] | 201 |       <IP_ADDRESS> | PUT     | /nnrf-nfm/v1/nf-instances/f2f810a2-988c-4be1-a30d-027731814e91 |
2023-10-03T06:27:55.476152815Z [WARN][CHF][CGF] Login to Webconsole FTP fail: dial tcp <IP_ADDRESS>:2122: connect: connection refused, retrying [2]
2023-10-03T06:27:56.482458706Z [WARN][CHF][CGF] Login to Webconsole FTP fail: dial tcp <IP_ADDRESS>:2122: connect: connection refused, retrying [3]
2023-10-03T06:27:57.483586136Z [INFO][address:<IP_ADDRESS>:2121][category:FTP][component:CHF] Listening...
2023-10-03T06:27:57.483905790Z [INFO][category:FTP][component:CHF] Starting...
^C2023-10-03T06:29:04.051780516Z [INFO][AMF][Init] Terminating AMF...
2023-10-03T06:29:04.052189550Z [INFO][AMF][Consumer] [AMF] Send Deregister NFInstance
2023-10-03T06:29:04.052350094Z [INFO][UPF][Main] Shutdown UPF ...
2023-10-03T06:29:04.052511044Z [INFO][UPF][PFCP][LAddr:<IP_ADDRESS>:8805] Stopping pfcp server
2023-10-03T06:29:04.052874967Z [ERRO][UPF][PFCP][LAddr:<IP_ADDRESS>:8805] read udp4 <IP_ADDRESS>:8805: use of closed network connection
2023-10-03T06:29:04.052950870Z [INFO][UPF][PFCP][LAddr:<IP_ADDRESS>:8805] pfcp reciver stopped
2023-10-03T06:29:04.053048784Z [INFO][UPF][PFCP][LAddr:<IP_ADDRESS>:8805] pfcp server stopped
2023-10-03T06:29:04.052922295Z [INFO][PCF][Init] Terminating PCF...
2023-10-03T06:29:04.052980941Z [INFO][SMF][Init] Terminating SMF...
2023-10-03T06:29:04.053213780Z [INFO][SMF][Consumer] Send Deregister NFInstance
2023-10-03T06:29:04.053220718Z [INFO][PCF][Consumer] Send Deregister NFInstance
2023-10-03T06:29:04.053801796Z [INFO][NSSF][Init] Terminating NSSF...
2023-10-03T06:29:04.054185084Z [INFO][AUSF][Init] Terminating AUSF...
2023-10-03T06:29:04.055720871Z [INFO][AUSF][Consumer] Send Deregister NFInstance
2023-10-03T06:29:04.055278312Z [INFO][NSSF][Consumer] Send Deregister NFInstance
2023-10-03T06:29:04.056915554Z [INFO][UDM][Init] Terminating UDM...
2023-10-03T06:29:04.057172847Z [INFO][UDM][Consumer] Send Deregister NFInstance
2023-10-03T06:29:04.057758922Z [INFO][CHF][Init] Terminating CHF...
2023-10-03T06:29:04.057983041Z [INFO][CHF][Consumer] Send Deregister NFInstance
2023-10-03T06:29:04.058145053Z [INFO][UDR][Init] Terminating UDR...
2023-10-03T06:29:04.058829085Z [INFO][UDR][Consumer] Send Deregister NFInstance
2023-10-03T06:29:04.060138092Z [INFO][NRF][NFM] Handle NFDeregisterRequest
2023-10-03T06:29:04.062146119Z [INFO][NRF][NFM] Handle NFDeregisterRequest
Receive SIGINT, terminating...
2023-10-03T06:29:04.063760208Z [INFO][NRF][NFM] Handle NFDeregisterRequest
2023-10-03T06:29:04.064708307Z [INFO][NRF][NFM] Handle NFDeregisterRequest
2023-10-03T06:29:04.065083975Z [INFO][NRF][NFM] Handle NFDeregisterRequest
2023-10-03T06:29:04.065588198Z [INFO][NRF][NFM] Handle NFDeregisterRequest
2023-10-03T06:29:04.065964104Z [INFO][NRF][NFM] Handle NFDeregisterRequest
2023-10-03T06:29:04.067801436Z [INFO][NRF][NFM] Handle NFDeregisterRequest
2023-10-03T06:29:04.112344383Z [INFO][UPF][Perio] recv event[TYPE_SERVER_CLOSE][{eType:4 lSeid:0 urrid:0 period:0}]
2023-10-03T06:29:04.112423325Z [INFO][UPF][Perio] perio server stopped
2023-10-03T06:29:04.112447512Z [INFO][UPF][Main] Terminating UPF...
2023-10-03T06:29:04.112464899Z [INFO][UPF][Main] UPF terminated
2023-10-03T06:29:04.112481289Z [INFO][UPF][Main] UPF exited
kill: (14715): No such process
kill: (14713): No such process
2023-10-03T06:29:05.094392461Z [INFO][NRF][GIN] | 204 |       <IP_ADDRESS> | DELETE  | /nnrf-nfm/v1/nf-instances/f2f810a2-988c-4be1-a30d-027731814e91 |
2023-10-03T06:29:05.096468584Z [INFO][CHF][Init] Deregister from NRF successfully
2023-10-03T06:29:05.096609192Z [INFO][CHF][Init] CHF terminated
2023-10-03T06:29:05.106855713Z [INFO][NRF][GIN] | 204 |       <IP_ADDRESS> | DELETE  | /nnrf-nfm/v1/nf-instances/c441b909-484c-456e-9a43-1abde2910d17 |
2023-10-03T06:29:05.107766909Z [INFO][NSSF][Init] Deregister from NRF successfully
2023-10-03T06:29:05.107948185Z [INFO][NSSF][Init] NSSF terminated
2023-10-03T06:29:05.110702517Z [INFO][NRF][GIN] | 204 |       <IP_ADDRESS> | DELETE  | /nnrf-nfm/v1/nf-instances/cc516942-eb45-41f8-bb29-9c5e1f023db0 |
2023-10-03T06:29:05.111181410Z [INFO][NRF][GIN] | 204 |       <IP_ADDRESS> | DELETE  | /nnrf-nfm/v1/nf-instances/4ba5899b-6993-43cb-bb04-8289f19eba56 |
2023-10-03T06:29:05.111684272Z [INFO][NRF][GIN] | 204 |       <IP_ADDRESS> | DELETE  | /nnrf-nfm/v1/nf-instances/2db0a209-0321-461b-82ae-4168ac15d81d |
2023-10-03T06:29:05.113014511Z [INFO][AUSF][Init] Deregister from NRF successfully
2023-10-03T06:29:05.113135636Z [INFO][AUSF][Init] AUSF terminated
2023-10-03T06:29:05.112750959Z [INFO][UDM][Init] Deregister from NRF successfully
2023-10-03T06:29:05.113346887Z [INFO][UDM][Init] UDM terminated
2023-10-03T06:29:05.114493874Z [INFO][PCF][Init] Deregister from NRF successfully
2023-10-03T06:29:05.114577327Z [INFO][PCF][Init] PCF terminated
2023-10-03T06:29:05.116955208Z [INFO][NRF][GIN] | 204 |       <IP_ADDRESS> | DELETE  | /nnrf-nfm/v1/nf-instances/6ad2a9b2-338f-4ef2-993c-de61525389a3 |
2023-10-03T06:29:05.117210494Z [INFO][NRF][GIN] | 204 |       <IP_ADDRESS> | DELETE  | /nnrf-nfm/v1/nf-instances/80d8353c-e6b0-4763-8c5b-8775c2c59c4b |
2023-10-03T06:29:05.117536570Z [INFO][SMF][Init] Deregister from NRF successfully
2023-10-03T06:29:05.117761465Z [INFO][AMF][Init] [AMF] Deregister from NRF successfully
2023-10-03T06:29:05.117213617Z [INFO][NRF][GIN] | 204 |       <IP_ADDRESS> | DELETE  | /nnrf-nfm/v1/nf-instances/c11acb3c-1136-4917-beaf-d1c6cd0b9ae1 |
2023-10-03T06:29:05.118098577Z [INFO][AMF][Init] Send AMF Status Indication to Notify RANs due to AMF terminating
2023-10-03T06:29:05.118575787Z [INFO][AMF][Ngap] Close SCTP server...
2023-10-03T06:29:05.118710705Z [INFO][AMF][Ngap] SCTP server closed
2023-10-03T06:29:05.119012751Z [INFO][AMF][Init] AMF terminated
2023-10-03T06:29:05.119614898Z [INFO][UDR][Init] Deregister from NRF successfully
2023-10-03T06:29:05.119690013Z [INFO][UDR][Init] UDR terminated
2023-10-03T06:29:06.059182774Z [INFO][NRF][Init] Terminating NRF...
2023-10-03T06:29:06.059559646Z [INFO][NRF][Init] Remove NF Profile...
2023-10-03T06:29:06.062872237Z [INFO][NRF][Init] NRF terminated

amfcfg.txt

Hi, @chethantk
In this version, you should launch webconsole before free5gc, since the new feature CHF login to Billing Domain (FTP server) which serves in webconsole.

Hi @brianchennn
I solved the below issue
root@ueransim:~/UERANSIM# build/nr-gnb -c config/free5gc-gnb.yaml
UERANSIM v3.2.6
[2023-10-04 14:26:06.892] [sctp] [info] Trying to establish SCTP connection... (<IP_ADDRESS>:38412)
[2023-10-04 14:31:11.354] [sctp] [error] Connecting to <IP_ADDRESS>:38412 failed. SCTP could not connect: Connection timed outy

By adding ueransim and free5gc in same network
root@ueransim:~/UERANSIM# build/nr-gnb -c config/free5gc-gnb.yaml
UERANSIM v3.2.6
[2023-10-05 06:07:18.479] [sctp] [info] Trying to establish SCTP connection... (<IP_ADDRESS>:38412)
[2023-10-05 06:07:18.495] [sctp] [info] SCTP connection established (<IP_ADDRESS>:38412)
[2023-10-05 06:07:18.496] [sctp] [debug] SCTP association setup ascId[3]
[2023-10-05 06:07:18.496] [ngap] [debug] Sending NG Setup Request
[2023-10-05 06:07:18.501] [ngap] [debug] NG Setup Response received
[2023-10-05 06:07:18.501] [ngap] [info] NG Setup procedure is successful


"Isolating the planes" documentation for Deis v2

Deis v1 had some documentation on isolating the planes: http://docs.deis.io/en/latest/managing_deis/isolating-planes/
This made it possible to prevent apps from being scheduled on the same machine as deis-builder for example, which uses a lot of CPU during builds.
It would be nice if a similar procedure was documented for Deis v2 in the documentation.

deis-builder is significantly better (referring to CPU) than it once was in v1 and in early versions of v2. You can achieve the same thing by modifying the existing charts for workflow and attaching nodeSelector labels to the charts. However we are not going to document how to do this as the charts will change over time, it requires extra administrative effort on the k8s cluster (whereas before we had total control over the setup process of the cluster), and we haven't seen a large amount of users who want this feature. That being said, you are more than welcome to maintain a fork of the charts with these changes and document the process yourself :)
Here's the document on Kubernetes' side for using nodeSelectors in manifests for reference: http://kubernetes.io/docs/user-guide/node-selection/


Fix emitter to throw when dotnet generator doesn't succeed

Fixes https://github.com/microsoft/typespec/issues/3384

API change check
API changes are not detected in this pull request.


Eggtab prevent enchants from showing in REI

All of Fabric 5 modpack
With Eggtab enabled

With Eggtab disabled

This happens with the creative items tab enabled. Furthur investigation necessary, you can disable that tab in the config screen/file in the meantime.


Enhancement: Mouse interaction in StoryMenuState

Please check for duplicates or similar issues before creating this issue.
What is your suggestion, and why should it be implemented?
My suggestion is: Clickable weeks aka the Mouse interaction with the week score.
Reason: Idk.

Sorry, no.

Sorry, no.

It's fine :)


OLS-83: Fix docstring mood in order to be able to enable D401 check

Description
Fix docstring mood in order to be able to enable D401 check
Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[x] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library

Related Tickets & Documents

Related Issue #OLS-83

Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] PR has passed all pre-merge test jobs.
[ ] If it is a core feature, I have added thorough tests.

Testing

N/A

/lgtm

/approve


add state transitions and timer back to moveSync

this allows you to log when you move from "idle" to "running" to "done" and log it in the serial console.  Hard to do this without the FSM due to interrupt code.

The UI reverts to Startup mode after completeing a Bounce or Move Synced to Spindle move. I don't think it was this way when I started running it. I am running the same version on the same browser. It is consistent in Bounce, but it sometimes stays on the Move Synced screen before it reverts to Startup.

ya, i think this is because I use the same code for halt as I do for finishing the bounce.  should be a fairly easy fix  when I have time.


Fix multi-team support

This is a Bug Report
Description
Davis seems to be running into a number of issues when in a multi-team environment.  It appears as though the Slack payload changes slightly.
The message object contains "source_team" instead of "team".
For bug reports:

Configure Davis with at least two Slack teams
Attempt to talk to Davis via Slack

after testing this appears to not be a bug anymore? I'm not really happy closing this without knowing more about what caused it but it seems that it is fixed either way. I'm going to close this. @beeme1mr can reopen it if he feels it should be open.


Update packages

Upgrade all packages to latest versions (especially Discord.js)

[ ] Discord.js
[ ] Axios
[ ] ytdl

I highly recommend delendabot
https://github.com/dependabot
It autoupdates packages without breaking changes.

Currently, many packages are outdated and have been re-architectured.
The scope of this issue is to fix logic that is caused by upgrading packages.
I will look into adding dependabot to autoupdate packages though


Add config to wordpress service

Fixes #1848
Add missing config to deploy the wordpress service without failing containers.

🎖 for finding a problem with our docs, filing an issue, and creating a PR that fixes that issue!


Fix aggregation of RH and T values for download

This fixes a serious bug in the download feature that would lose three out of four data points, see the commit message below.
Even after fixing this bug, there are still more strange issues, I documented them here: #31.
When downloading logged RH/T values, these do not arrive in pairs,
but independently. Also, they arrive in packets, so several RH values
might arrive before the corresponding T value does. The code to
aggregate these values in pairs did not account for this, losing
three out of four values by overwriting them in the aggregator.
There are now two different aggregation strategies for live and
logged data: for live values, the timestamp is ignored, for historic
values it is not.

While writing unit tests, I also noticed that one existing test fails: RHTSensorFacadeTest in the setUp method.

I also don't see the benefit of aggregating RH and T in pairs. Are they used as a pair anywhere in the app?

Thanks, this patch is much appreciated! Also, thanks for taking the time to write tests. We're reviewing and testing the code.
As to aggregating RHT, this may originally have been done for consistency with other gadgets which report the value in pairs. I believe that the combined value is currently cached on some of the fragments to quickly display the last reading again. We could of course extend the caching code, but it's definitely not a priority.

Merged as d2f821d47713ed7678827dd9917d6b6d21c5dcdd
Thanks again, closing this.


Untangle ConfigurationCacheIO

This is a pure refactoring PR that tries to split the ConfigurationCacheIO implementation with a large API surface into smaller interfaces actually required by consumers.
Changes:

DefaultConfigurationCache.Host --> ConfigurationCacheHost
ConfigurationCacheIO --> DefaultConfigurationCacheIO, and now it implements these new interfaces:

ConfigurationCacheBuildTreeIO
ConfigurationCacheUserTypesIO
ConfigurationCacheIncludedBuildIO

These changes also allow to replace the ProjectStateStore dependency on ConfigurationCacheIO with a much more lightweight ConfigurationCacheUserTypesIO and remove some duplicate code.

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

The merge queue build has failed. Click here to see all failures.