text:
bug: keymap to toggle floaterm is not working after installing which-key

Did you check docs and existing issues?

[X] I have read all the which-key.nvim docs
[X] I have searched the existing issues of which-key.nvim
[X] I have searched the exsiting issues of plugins related to this issue

Neovim version (nvim -v)
0.8.2
Operating system/version
MacOS Ventura 13.1
Describe the bug
I use space-t-t to toggle floaterm. After installing which-key, I can still use this keymap to open floaterm, but not for closing it.
May I ask if anyone has similar issue, and how to solve it?
Thanks.
Steps To Reproduce

install which-key
can use space-t-t to open floaterm
while floaterm is open, unable to close it use the same keymap which is meant to toggle it.

Expected Behavior
should be able to toggle floaterm with the keymap.
Repro
No response

This is definitely not a which key issue. Are you sure you mapped it to float term toggle and not float term open? Either way, you'll have to figure this out yourself.

I'm pretty sure this is a which-key issue, because uninstalling which-key solves the problem.
I have the following keymaps for floaterm:
vim.g.floaterm_keymap_new    = '<Leader>ft'
vim.g.floaterm_keymap_toggle = '<Leader>tt'

What does :verbose nmap <leader>tt show?

authors: folke hopezh


text:
@fontsource/fredoka-one missing woff files

Describe the bug
The ./files/fredoka-one-all-400-normal.woff) file from index.css does not exist.
/* fredoka-one-latin-400-normal */
@font-face {
  font-family: 'Fredoka One';
  font-style: normal;
  font-display: var(--fontsource-display, swap);
  font-weight: 400;
  src: url(./files/fredoka-one-latin-400-normal.woff2) format('woff2'), url(./files/fredoka-one-all-400-normal.woff) format('woff');
  unicode-range: U+0000-00FF,U+0131,U+0152-0153,U+02BB-02BC,U+02C6,U+02DA,U+02DC,U+2000-206F,U+2074,U+20AC,U+2122,U+2191,U+2193,U+2212,U+2215,U+FEFF,U+FFFD;
}

Steps to Reproduce
Install "@fontsource/fredoka-one": "5.0.5"
Expected behavior
No response
Version
5.0.5
OS
All
Browser
All
Additional context
No response

Closing this assuming it is resolved.

source: gharchive/issue

authors: Bartozzz ayuhito

repo: fontsource/fontsource

license: MIT

license_type: permissive

license_source: github-api


text:
[feaLib]: parsing should fail if value record contains both variation and device info

Currently, the following compiles, but it should probably be an error:
languagesystem DFLT dflt;
feature kern {
    pos one <0 (wght=200:12 wght=900:12 wdth=150,wght=900:12) 0 0
        <device 11 -1, 12 -1>
        <device NULL>
        <device 11 -2, 12 -2>
        <device NULL>>;
} kern;

Agreed.

authors: behdad cmyr

repo: fonttools/fonttools

license: mit

license_source: bigquery


text:
Proposer validator info undefined

Describe the bug
Proposer Validator link undefined with link like https://testnet.explorer.agoric.net/validator/undefined
To Reproduce
Steps to reproduce the behavior:

Open blocks list, for example https://testnet.explorer.agoric.net/blocks
Click on any Height (right column)
Check Proposer Validator link (https://testnet.explorer.agoric.net/validator/undefined)

Expected behavior
https://testnet.explorer.agoric.net/validator/1AC8D58222BD4B63B301F0850388670720172945 instead of https://testnet.explorer.agoric.net/validator/undefined
Screenshots

Desktop (please complete the following information):

OS: Ubuntu 18.04.5
Browser Firefox
Version  87.0 (64-bit)

Thank you @dpodyachev ! Nice catch!

authors: dpodyachev kwunyeung

repo: forbole/big-dipper


text:
Different derivation paths using Ledger

Currently it is not possible to use a different derivation path for accounts generate with a Ledger. This makes it impossible to have multiple wallets if you are using it. It should be allowed at least to use a different account index when importing the wallet.

Unlike Ledger which can only generate the first 100 accounts and indexes, generating soft keys with derivation path accept the full range. This makes the addresses can be generated from
m/44'/852'/0/0/0

to
m/44'/852'/2147483647/1/2147483647

Please add your planning poker estimate with ZenHub @calvinkei

Please add your planning poker estimate with ZenHub @Rooty2020

@kwunyeung @calvinkei
Allow user to enter the HD Path when adding  an account using the ledger device.
https://www.figma.com/proto/w7LpoB8DejNVumjJPDrp7j/Forbole-X-_web-app_1.0?page-id=192%3A2&node-id=260%3A216&viewport=241%2C48%2C0.06&scaling=min-zoom&starting-point-node-id=4128%3A237249

repo: forbole/forbole-x


text:
deploy genAiPlanner with changes won't update UI

Summary

Having a new GenAiPlanner in the code and deploying it, won't be reflected in the org UI.
Making changes in the description of a GenAiPlanner object and deploying the change won't be reflected in the org UI.
Strange enough, with an existing object, changing GenAiPluggin objects within the planner works.

This all has been tested with type=Digital Channel
Expected result
When org is empty and doesn't have the KDA agent created and executing the following command, I expect the planner to be created.
sf project deploy start --metadata GenAiPlanner:kda_v1

Actual result
Though the CLI succeeds, the planner won't show up in the org UI.
Additionally, if the object is created by hand in the org, and pulled, changes in the descriptions have the same outcome, they can be made and pushed with the CLI but though the CLI succeeds, the change won't be shown in the UI.
Additional information
Example repo and file https://git.soma.salesforce.com/madolfi/knowledge-driven-actions-poc/blob/master/force-app/main/default/genAiPlanners/kda_v1.genAiPlanner-meta.xml
System Information
CLI:
@salesforce/cli/2.63.7 darwin-x64 node-v20.17.0

Plugin Version:
@oclif/plugin-autocomplete 3.2.6 (core)
@oclif/plugin-commands 4.1.3 (core)
@oclif/plugin-help 6.2.15 (core)
@oclif/plugin-not-found 3.2.22 (core)
@oclif/plugin-plugins 5.4.15 (core)
@oclif/plugin-search 1.2.12 (core)
@oclif/plugin-update 4.6.4 (core)
@oclif/plugin-version 2.2.15 (core)
@oclif/plugin-warn-if-update-available 3.1.19 (core)
@oclif/plugin-which 3.2.16 (core)
@salesforce/cli 2.63.7 (core)
apex 3.5.4 (core)
api 1.3.1 (core)
auth 3.6.68 (core)
data 3.7.1 (core)
deploy-retrieve 3.14.0 (core)
devops-center 1.2.24 (user)
functions 1.23.0 (user)
info 3.4.12 (core)
limits 3.3.33 (core)
marketplace 1.2.26 (core)
org 4.7.0 (core)
packaging 2.8.12 (core)
schema 3.3.36 (core)
settings 2.3.24 (core)
signups 2.5.23 (user)
sobject 1.4.42 (core)
source 3.5.21 (core)
telemetry 3.6.16 (core)
templates 56.3.24 (core)
trust 3.7.34 (core)
user 3.5.33 (core)

SF ENV. VARS.
SF_BINPATH,/Users/madolfi/.local/share/sf/client/bin/sf
SF_AUTOUPDATE_DISABLE,true
SF_DISABLE_AUTOUPDATE,true
SF_UPDATE_INSTRUCTIONS,Use "npm update --global @salesforce/cli" to update npm-based installations.

Windows: false
Shell: zsh
Channel: stable

Diagnostics
:white_check_mark: pass - salesforcedx plugin isn’t installed
:white_check_mark: pass - you don't have any linked plugins
:white_check_mark: pass - [@salesforce/plugin-trust] can ping: https://registry.npmjs.org
:white_check_mark: pass - [@salesforce/plugin-trust] can ping: https://registry.yarnpkg.com
:white_check_mark: pass - [@salesforce/plugin-trust] can ping: https://registry.npmjs.org/
:white_check_mark: pass - using latest or latest-rc CLI version
:white_check_mark: pass - [@salesforce/plugin-deploy-retrieve] sourceApiVersion matches apiVersion
:x: warn - [@salesforce/plugin-deploy-retrieve] sourceApiVersion matches default target org max apiVersion
:white_check_mark: pass - can access: https://test.salesforce.com
:white_check_mark: pass - can access: https://appexchange.salesforce.com/services/data
:white_check_mark: pass - can access: https://developer.salesforce.com/media/salesforce-cli/sf/channels/stable/sf-win32-x64-buildmanifest
:x: fail - [@salesforce/plugin-auth] CLI supports v2 crypto

@martinadolfi - thanks for reporting.  The CLI is sending the correct request to the metadata API.  This is an issue for the metadata type owner of GenAiPlanner.

This is now fixed in SFDC release 252.13

authors: martinadolfi shetzel

repo: forcedotcom/cli


text:
Allow existing components to be modified using lwc-builder

If there is an existing component we can't edit that directly with builder extension. Need an option to open an existing component and preload the existing configuration, so we can modify that and save it back to the component meta.xml file. I am planning to work on it. Let me know your thoughts.

Yes this would a much appreciated function. As it is now this is only useful for initial creation. But still VERY useful.

repo: forcedotcom/lwc-builder


text:
Ubuntu下可以运行么？

只看到写的是在WIn下，不知道Ubuntu下行不行

不行呀，用了很多windows特产:joy::joy::joy:，参考#18。

这是我发现的第一个不能在atom for linux上面运行的插件。

我写的蠢呀:joy::joy::joy:

....... 下载完了发现- - 不能在mac上用 - -

据说新版可以了，有空试试呗。

authors: Armour Fretice foreshadow noparkinghere

repo: foreshadow/atom-python-run


text:
feat: Limit route info events to 3 recent entries

Description
Issue
During extended development sessions, route information continuously accumulates in memory as new loader/action events are processed. This leads to:

Increasing memory consumption
Potential performance degradation
Unnecessary storage of old event data

Changes

Added a limit to store only the 3 most recent events for each route's loaders and actions
Applied slice(-3) to both loader and action event arrays

Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Unit tests

Checklist:

[x] My code follows the guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings or errors
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Interesting, I wonder if this could be a config option on how many you want to save instead of deciding for the user, eg you can set it to 3,5, 30

source: gharchive/pull-request

authors: AlemTuzlak ttizze


text:
Update StatsdClient.jl

Allow hostname resolution while preserving IP address string parsing - fixes https://github.com/forio/StatsdClient.jl/issues/3

Nice! Thanks a lot for figuring that out!

Sorry for the delay, tagged a new version, will merge into metatdata as soon as the tests pass: https://github.com/JuliaLang/METADATA.jl/pull/3148

authors: WestleyArgentum sbromberger


text:
Send instructions to participants

I suggest we do this 2 weeks prior to the workshop, on the 28.08.?

Thanks Malika for sending out the instructions yesterday!

authors: Maximilian-Stefan-Ernst aaronpeikert


text:
Pointing out the importance of correct key in the documentation

Hello!
I think it would be useful to point out the importance of using a unique key so the animation system knows how to identify elements correctly. I struggled for a while because I used the index on an array element as a key (as React recommends that in an error). That lead to weird behaviors in the animations (as it should) which confused me at first. I think it would help fellow noobs like me to have good results straight away!
Thanks for your work, its great!

It's already mentioned in the Vue section but maybe it could be made more prominent.

authors: patrikzudel valgeirb

repo: formkit/auto-animate


text:
hideExpression doesn't reflect the state correctly

Hello!
I'm trying to hide form fields based on validity of another fields. It looks like Formly doesn't evaluate hideExpression according to the latest state of things.
Here's the JSBin with an example:
https://jsbin.com/qazirovami/1/edit?html,js,output
The E-Mail field is initially incorrect (due to required: true), so the first name and last name fields should be hidden according to the hideExpression, but they are not. If you play with those fields you will find some other inconsistencies too.
@BarryThePenguin thinks that this could be related to the #523.
What could be done about this? Thank you!

It looks like this is a result of the validation being run before the fields are fully initialised.
I'm looking through tests now and the field validation is being run before the formControl is added to the field. This prevents validateOnModelChange from running and validating the form on first render.

Hello! Are there any news on this issue? = )

Hi! No, not yet. I managed to create a failing test for this scenario. Kent left some feedback on #603 but the solution hasn't been incorporated in a PR yet

Ok, thanks )
Too bad I can't help = /

@slavafomin, why can't you help? You're welcome to make a PR. Just make the test pass :-)

If you need help, I'm sure that someone (or I) could help point you in the right direction. You might also check the CONTRIBUTING.md :+1:

I'm afraid I'm still struggling to just use Formly, more so to develop it )
Maybe a couple of implemented projects will change this )

Any suggestions on a temporary work around?

Hey!
I'm using something like this:
$scope.formState = {
  formInvalid: null
};
// @todo: remove this ugly hack! (https://github.com/formly-js/angular-formly/issues/602)
$scope.$watch('forms.form.$invalid', function (value) {
  $scope.formState.formInvalid = value;
});

And then add formState.formInvalid to your hideExpression.

In my case, I was loading my fields via an ajax call, so on the initial compile of the angular-formly directive, my model was set to an empty object, and the fields were an empty array. After retrieving my fields, angular-formly would draw them out, but not run hideExpressions. I found that if I leave my model as undefined until after the fields have been defined, that the hideExpressions will run.

I'm experiencing a similar issue, how exactly do you leave the model as undefined until after the fields are defined?  I have looked through the source code to try to fix this bug myself, but am also new to Formly so I was unable to find a way to change Formly so that hideExpressions gets run as expected.

As I'm loading my data through an asynchronous call, and displaying fields based on that information, what worked for me was wrapping the form in an ng-if watching the field that gets populated on return from the server, ensuring all of my model data is populated before the form gets generated.

So if your html looks like this:
<formly-form model="vm.user" fields="vm.userFields">
  <button type="submit" class="btn btn-default" ng-click="vm.submit(vm.user)">Submit</button>
</formly-form>

On the initial compile of your view, $scope.user needs to be undefined (meaning you haven't defined $scope.user, or you have assigned it a value of undefined. Then in some async call where you are get getting your field definitions:
$http.get('/my/fields/endpoint')
  .then(function(response) {
    $scope.userFields = response.data;
    // Now you can give vm.user a value
    $scope.user = {};
  });

My code had a bit more complexity to it, but i'm pretty sure this is what worked for me. The only difference could be that you need to wrap $scope.user = {} with a $timeout.

authors: BarryThePenguin kentcdodds misterwise pos1tron slavafomin

repo: formly-js/angular-formly


text:
Prerequisites

Hi there! Could you tell me what are the prerequisites for compiling the project? Like libs, packages, module, maybe version of VS also matters?

I compiled in visual studio 2022 adding crc32.h and ntos.h

Can you upload ntos.h and crc32.h pls?

I compiled in visual studio 2022 adding crc32.h and ntos.h

Can you upload ntos.h and crc32.h pls?

Well, these two solved the issues related to ntos.h and crc32.h, but still wasn't able to compile due to a ton of other errors..
https://github.com/hfiref0x/NtCall64/blob/master/Source/NtCall64/ntos.h
https://gist.github.com/timepp/1f678e200d9e0f2a043a9ec6b3690635

What errors!
El jue, 13 de abr de 2023, 04:01, abedtuded @.***>
escribió:

I compiled in visual studio 2022 adding crc32.h and ntos.h
[image: image]
https://user-images.githubusercontent.com/8556494/225966216-849b99a1-1579-4e27-9b01-da3c18b45a11.png
Can you upload ntos.h and crc32.h pls?
Well, these two solved the issues related to ntos.h and crc32.h, but still
wasn't able to compile due to a ton of other errors..
https://github.com/hfiref0x/NtCall64/blob/master/Source/NtCall64/ntos.h
https://gist.github.com/timepp/1f678e200d9e0f2a043a9ec6b3690635
—
Reply to this email directly, view it on GitHub
https://github.com/fortra/CVE-2022-37969/issues/1#issuecomment-1506452682,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACBI7TWDDM6TRSU5F27CCBTXA6QDPANCNFSM6AAAAAAV6NW7PE
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

use the ntos.h and crc32.h provided and change to not unicode

Thanks for this one, mate!! Compiled just fine with a few minor changes to the code! Was really stuck with those issues..

authors: abedtuded ricnar456 trowx


text:
Automatically delete previews on merge

Can we adapt the preview workflow to automatically remove previews once a PR is merged? Otherwise we will end up with several stale previews which have to be deleted from time to time.

Fixed in my repo, will be merged in upcoming repo.
Thanks and Regards,
Henil Shalin Panchal
CC @awvwgk

repo: fortran-lang/webpage


text:
Add Country Population Density and Gender Ratio Endpoints

I would like to enhance the Country Data functionality by adding new endpoints that provide additional demographic insights. Specifically, aim to introduce two new endpoints: one for calculating the population density of a country and another for determining the gender ratio. These endpoints will offer valuable data for users interested in detailed demographic statistics.
I am Participating in GSSOC'24.

dear PA,
Please assign this issue to me under GSSoc'24, I'm a contributor for GSSoC.
Looking forward to get assigned ASAP.

Existing endpoint can be modified

Please assign this issue to me.


text:
fix : Layout Overlap Fix

Fixes #255
Changes:

Moved the layout inside the scrollview

@liveHarshit the UI doesn't look any different. But in devices in which overlapping was happening, it will not happen.

@liveHarshit I don't own a xhdpi device else I could have provided the screenshots. This should fix the issue though

repo: fossasia/badge-magic-android


text:
fix: issue bookmark status in SpeakerDetailsActivity resolved

Fixes #1238
Changes:
Resolved bookmark status issue in SpeakerDetailActivity
Screenshots for the change:

@the-dagger @mananwason
please review!

@the-dagger @mananwason
please review!

repo: fossasia/open-event-android


text:
Auto Deployment to GH-pages is failing

Actual Behaviour
It seems like since last few commits, the auto deployment of the sample event(FOSSASIA Summit) on the repo's GH-pages is not working. To be precise, since #1272.  Because of this, the improvements made in the recent PRs are not reflected on the GH-pages.
Expected Behaviour
The sample site should automatically be deployed to the GH-pages on every PR merge.
Log for the issue
It throws the following error at the end while executing the gh_deploy.sh script.
remote: Invalid username or password.
fatal: Authentication failed for 'https://[secure]@github.com/fossasia/open-event-webapp.git/'

Would you like to work on the issue?
Yes. Working on it to find the cause of this issue.

Error fixed.

repo: fossasia/open-event-webapp


text:
New release

Hi,
Can you create a new realease? So I can create a voidlinux package with the #4 fix
Thanks
see void-linux/void-packages#2119

done! let me know if anything else is needed

authors: fosu kojicomics

repo: fosu/crud


text:
add support for rank0 only profiler

To address https://github.com/foundation-model-stack/fms-fsdp/issues/58

@nairbv pushed a new change based on your feedback.

repo: foundation-model-stack/fms-fsdp


text:
middle positioned labels do not correctly work

What should happen?
The <label> should be centered vertically against the input element
What happens instead?
The <label> element is vertically centered in its own box which is higher (42px in the example https://get.foundation/sites/docs/forms.html#label-positioning) than the input (39px). The label height changes (along with its line-height and font-size changes) make it impossible to stay centered.
Possible Solution
.label.medium {
    padding: get-side($input-padding, 'top') 0 get-side($input-padding, 'bottom');
    line-height: ($input-font-size * unitless-calc($input-line-height))  - rem-calc(1);
}

Test Case and/or Steps to Reproduce (for bugs)
https://get.foundation/sites/docs/forms.html#label-positioning
examine the label/inout heights with web-dev-tools and try changing the label font size
PS
Why is - rem-calc(1) used in input height calculation?
I usually add twice the border size to set the height of inputs to match button's height with same line-height, font-size, v-padding and v-border.
kind regards

Please provide a codepen for reproduction purposes.

Hello @DanielRuf ,
https://codepen.io/pine3ree/pen/dyMRMrK
Labels 1,2,3 are standard foundation labels with default, and increased font-size. I added a light background to show that the label height does not match the input height
Labels 4,5,6 have the same font size of 1,2,3 respectively, but the suggested solution is applied.

Well, normally you set the values in the settings.scss using the correct variables:
https://github.com/foundation/foundation-sites/blob/develop/scss/forms/_text.scss#L23
https://github.com/foundation/foundation-sites/blob/develop/scss/forms/_text.scss#L31
https://github.com/foundation/foundation-sites/blob/develop/scss/forms/_label.scss#L15
https://github.com/foundation/foundation-sites/blob/develop/scss/forms/_label.scss#L23
Changing the values for the label does not affect the input values.
https://github.com/foundation/foundation-sites/blob/develop/scss/forms/_label.scss#L35-L40
Also your issue title does not reflect the actual issue. I've changed that.
I'm a bit confused because if you do not use the sass version and the mixins you always have to adjust the line-heights and font-sizes as needed. This is how it has always worked. Foundation Sites is still a foundation of styles which are configurable with Sass and for quick prototyping. So far I've used the mixins and font-size + line-height adjustments as needed. I see no bug / error here tbh.

Possible Solution

I'm not sure how the medium class is connected to the middle class. And I see no medium class in your codepen.
I think you expect more from Foundation Sites then it covers (it does not cover all edge cases and such cases where you overwrite single values instead of generating the values using the mixins).

Hello @DanielRuf , right...middle, sorry for the typo...
But you can see that even the default lable is not vertically centered. It is just a lot more centered than the not ".middle" version. To be perfectly centered the box height of the labels should be identical to the box height of the inputs.

@DanielRuf ,
I've tried with $form-label-font-size: rem-calc(20); and I get a label almost bottom aligned. Only setting changed in build.
kind regards.

Probably just a small regression when we merged old branches into the develop branch. I will check the issue with the label that is too heigh. But the proposed solution is not needed.

Hm, seems this was always like that. At least this is the same for 6.4.3 and earlier too.
I think this is the same like in https://github.com/foundation/foundation-sites/issues/11662
When you set the height to auto for the input it works.
I guess we have to adjust the calculation of the height value. Not sure why we had it always like this.

Hm, seems this was always like that. At least this is the same for 6.4.3 and earlier too.
I think this is the same like in https://github.com/foundation/foundation-sites/issues/11662

Hm, seems this was always like that. At least this is the same for 6.4.3 and earlier releases too.
I think this is the same like in https://github.com/foundation/foundation-sites/issues/11662

@DanielRuf ,
this is how I usually achieve equal heights in forms:
https://codepen.io/pine3ree/pen/qBZjNzG
(only a few basic input examples here)

See https://github.com/foundation/foundation-sites/pull/12143
Everything else out of our Foundation Sites styleguide may require custom styles as it was always the case.

Hello @DanielRuf,
I don't believe https://github.com/foundation/foundation-sites/pull/12143 will completely solve the issue.
Using $global-line-height (decimal or %) for labels will result in a total label height still depending on the label font-size. What we actually need is to have the label height identical to the input height. There are 2 ways to achieve that:

setting zero vertical padding and giving the label the same height of inputs (this will work just fine for symmetrical vertical padding)
use the method I suggested above: use the same absolute (i.e. rem/px, not decimal, % or em) vertical padding and absolute line-height of the inputs.

kind regards.

What we actually need is to have the label height identical to the input height.

No, I don't think so. Labels can and should grow. Same for this case. It is just basically aligned from the top. Setting the height would be a breaking change and introduce other issues.

setting zero vertical padding and giving the label the same height of inputs (this will work just fine for symmetrical vertical padding)

This will not work with multiline labels.

absolute (i.e. rem/px, not decimal, % or em) vertical padding and absolute line-height of the inputs

The paddings already use rem. It is 9 * 2 px for the label and 8 * 2 + the border for the input.

Using $global-line-height (decimal or %) for labels will result in a total label height still depending on the label font-size.

This is correct imho. This was also the case before (1.8 as labels should have more space / higher line heights than inputs) but for aligning it with the input it has to be 1.5 - the same for the input.
Regarding same / other font-sizes (in Foundation we set label = input - 2px, this is how it is defined in our styleguides), you can and should apply custom styles in your project as previously explained.
Foundation Sites is a framework that applies a specific style and rules. If you want to modify it and this is not a normal use case like yours, apply custom styles.

As far as I can see your change introduces some side effects like issues when you increase the label font size which will not apply the correct line height. line height values should be numeric to react to the elements font size, not the root font size. This is not correct imho.

repo: foundation/foundation-sites


text:
State diff tracer

Component
Anvil
Describe the feature you would like
Anvil is an extremely useful tool for simulating a sequence of unsigned transactions and determining if any will revert. The eth_sendUnsignedTransaction appears to be without analogy in any other client/tool and is awesome! However, being able to simulate state diffs is important to many workflows as well.
Geth has several built in tracers, including one that is exceedingly useful called the prestateTracer.
It would be great if Anvil could incorporate a similar tracer to provide state diffs for simulated, unsigned transactions.
Additional context
No response

This would be really awesome

Having support for prestateTracer as a tracer argument would be really useful

+1, would really like to see this!

going to track prestateTracer (and other tracers built in Reth) support in https://github.com/foundry-rs/foundry/issues/5855 and close this one as dupe

repo: foundry-rs/foundry


text:
Is there a naming convention for test in foundry?

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (721eb94 2024-05-01T00:20:21.524571876Z)
What command(s) is the bug in?
forge test
Operating System
Windows
Describe the bug
I am declaring a test to check the functionality of the contract,  when I used this function the test passes.
function testFundFailsWithoutEnoughEth() public {
        vm.expectRevert();
        fundMe.fund();
    }

Output:
hercules@DESKTOP-5K9O493:~/foundry-f24/foundry-fund-me-f24$ forge test --mt testFundFailsWithoutEnoughEth
[⠒] Compiling...
No files changed, compilation skipped

Ran 1 test for test/FundMeTest.t.sol:FundMeTest
[PASS] testFundFailsWithoutEnoughEth() (gas: 22972)
Suite result: ok. 1 passed; 0 failed; 0 skipped; finished in 733.30µs (88.10µs CPU time)

Ran 1 test suite in 13.09ms (733.30µs CPU time): 1 tests passed, 0 failed, 0 skipped (1 total tests)

But when I change the function name a little-bit (I removed Fund from the function name) it fails:
function testFailsWithoutEnoughEth() public {
        vm.expectRevert();
        fundMe.fund();
    }

Output:
hercules@DESKTOP-5K9O493:~/foundry-f24/foundry-fund-me-f24$ forge test --mt  testFailsWithoutEnoughEth
[⠒] Compiling...
[⠒] Compiling 1 files with 0.8.25
[⠢] Solc 0.8.25 finished in 1.86s
Compiler run successful!

Ran 1 test for test/FundMeTest.t.sol:FundMeTest
[FAIL. Reason: assertion failed] testFailsWithoutEnoughEth() (gas: 22994)
Suite result: FAILED. 0 passed; 1 failed; 0 skipped; finished in 747.60µs (79.50µs CPU time)

Ran 1 test suite in 14.04ms (747.60µs CPU time): 0 tests passed, 1 failed, 0 skipped (1 total tests)

Failing tests:
Encountered 1 failing test in test/FundMeTest.t.sol:FundMeTest
[FAIL. Reason: assertion failed] testFailsWithoutEnoughEth() (gas: 22994)

Encountered a total of 1 failing tests, 0 tests succeeded

I researched that using Fail immediately after the test is the same as vm.expectRevert.


text:
Attempting to unpack a V10 NEDB database fails because it is looking for a V11 LevelDB lockfile

The isFileLocked function is called regardless of whether the dbMode is "nedb" or "classic-level" but this lock file will only exist if the dbMode is classic-level. This prevents pack/unpack operations from being possible in a pure v10 environment.

Closed as of v0.0.8

authors: aaclayton cswendrowski

repo: foundryvtt/foundryvtt-cli


text:
Tallow Bomb doesn't display damage button.

An attack with a Tallow Bomb just results in a hit/miss post, with no way to display the persistent damage or splash.

Based on a discord conversation, it sounds like the issue is the bomb having zero base damage.

I'm able to replicate the behavior on other bombs by setting the base damage to zero

Testing Environment:

I believe this is fixed by recent changes.

authors: MarsMage simonward


text:
Add Compass support

Is it possible to make this work with Compass? Currently getting:
/Users/kevin/meteor/apps/scheduler/sass/screen.scss: Sass compiler error: :1: error: error reading file "compass"

Yes, Meteor-Compass works great.
 meteor add francocatena:compass

Check README for package configuration.

You need just sass and bower
bower install compass-sass-mixins

@import "bower_components/compass-sass-mixins/lib/compass"
//@import "node_modules/compass-sass-mixins/lib/compass"

/*
use your sass mixins here
*/

repository and list of funtions
https://github.com/askucher/compass-sass-mixins

authors: LeCoupa askucher wizonesolutions

repo: fourseven/meteor-scss


text:
Data discontinuities in data coming from data platform are not plotted correctly.

Description
Data discontinuities should be skipped in plots but currently we connect them in data streamed from data platform.

Version: 1.2.0
Platform: All

Steps To Reproduce

Open a long file from data platform.
Plot some topic from the file.
Use the play bar to jump to different sections of the file.
Observe the plot try to connect the gaps.

Expected Behavior
Gaps should be excluded from the plot.
Actual Behavior
Gaps are connected.

@foxymiles is this an "mcap" issue or a studio one?

Studio

Closing in favor of https://github.com/foxglove/studio/issues/2956

authors: foxymiles jtbandes wkalt

repo: foxglove/mcap


text:
Update aws-java-sdk-dynamodb to 1.12.290

Updates com.amazonaws:aws-java-sdk-dynamodb from 1.11.1034 to 1.12.290.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws", artifactId = "aws-java-sdk-dynamodb" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "com.amazonaws", artifactId = "aws-java-sdk-dynamodb" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #331.

repo: fp-in-bo/api


text:
OOM on Travis for store-0.4.1 on GHC 7.10.3 while building Stack

In the past few days I've noticed a few failures like the following, mentioning OOM
https://travis-ci.org/commercialhaskell/stack/jobs/234558520#L321-L324 (https://travis-ci.org/commercialhaskell/stack/jobs/234737983 was also one, but I had to restart it).
Building stack took lots of memory in other situations. Can anything be done to improve the situation? (I'd be open to workarounds on the stack/Travis side).
 --  While building package store-0.4.1 using:
      /home/travis/.stack/setup-exe-cache/x86_64-linux/Cabal-simple_mPHDZzAJ_1.22.5.0_ghc-7.10.3 --builddir=.stack-work/dist/x86_64-linux/Cabal-1.22.5.0 build --ghc-options " -ddump-hi -ddump-to-file"
    Process exited with code: ExitFailure (-9) (THIS MAY INDICATE OUT OF MEMORY)
    Logs have been written to: /home/travis/build/commercialhaskell/stack/.stack-work/logs/store-0.4.1.log

This one fails on this file:
    [ 9 of 11] Compiling Data.Store.Streaming ( src/Data/Store/Streaming.hs, .stack-work/dist/x86_64-linux/Cabal-1.22.5.0/build/Data/Store/Streaming.o )

Other failure in https://travis-ci.org/commercialhaskell/stack/jobs/234811762, it seems on Data.Store.TypeHash.Internal.

Version 0.4.3.1 has quite a bit fewer uses of INLINE, which will likely help with that issue.

Just adding some more info: had OOM problems with CircleCI build (VM with 4G memory limit), and noticed store is the culprit (after trying to build some selected deps first, to fill the CircleCI' cache).
Surprisingly, it was failing when build in separate step (via stack build store), but after trying stack build store --verbose it succeeded, so don't know when exactly it was failing before.

authors: BartAdv Blaisorblade mgsloan

repo: fpco/store


text:
packer: update kubespray build and parameterize docker tag

Update kubespray build and parameterize docker tag to address https://github.com/fpco/terraform-aws-foundation/issues/123

this is the green build image output.

repo: fpco/terraform-aws-foundation


text:
Add AppleCare+ support

Need a way to specify AppleCare+ coverage in repair creation.

Done

repo: fpsw/Servo


text:
🛑 Municipalidad de Paracas is down

In 2fadf95, Municipalidad de Paracas (https://muniparacas.gob.pe/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Municipalidad de Paracas is back up in a2c006e.


text:
Update stealth-facebook.gemspec

Hello @mgomes,
My name is Francel, i'm ruby and rails junior web developer and i love the ruby langage .
This is the first time that I have contributed to a project on github. I started using this gem to learn how to create messenger chatbots.
Please, could you look at the changes I made and then see if it's okay and merge that with the master branch?
Thank you

@francelwebdev Thanks for your contribution and welcome to the Ruby community! Always exciting to welcome new members.
I would be happy to merge this PR in, but the only issue is that the PR you created is against your own repository. When creating the PR, make sure you select hellostealth/stealth-facebook for base fork. There's more info here, but the docs aren't great: https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork

authors: francelwebdev mgomes

repo: francelwebdev/stealth-facebook


text:
Prevent inspecting a process that doesn't exist

Sometimes, the __done_is_tmux_window_active function will try to access the root process (PID 1). It is happening to me using byobu (tmux).
When that happens(tmux_fish_pid=1), ps -o ppid= -p $tmux_fish_pid | string trim will return 0, causing a failure when we access basename (ps -o command= -p $tmux_fish_ppid)
To ensure we don't get ugly errors if that is the case, we can check it we reached that case before checking the process' basename.
There might be a better solution, this is just a quick fix, so if someone with better fish skills has a better suggestion, I am open to changes :+1:

@peng1999 you wrote the original code. Do you understand why this is happening? Is tmux not being found and is the while loop running all the way until the end where pid = 0 ?

@joao-p-marques is there any chance that you are/were launching tmux with another path in the params? e.g.
/usr/bin/tmux new-session -c /some/start/dir

Askng to understand if this error might be fixed by https://github.com/franciscolourenco/done/pull/124

@joao-p-marques have you experienced this problem with the latest version?

authors: franciscolourenco joao-p-marques

repo: franciscolourenco/done


text:
🛑 SIU Guarani is down

In 34a8755, SIU Guarani (https://siufai.uncoma.edu.ar/informatica) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SIU Guarani is back up in b5a75e9 after 4 hours, 8 minutes.


text:
Incorrect behavior of basic arithmetic operations

According to the documentation:

This math operations returns a new Fxp object with automatic precision enough to represent the result. So, in all these cases we can assign the result to a (Fxp) variable, or to the same (overwritting the old Fxp object).

However, this is clearly not working at all. Taking some examples directly from the documentation:
x = Fxp(-7.25)
y = x**3
z = 3.25 * (x - 0.5)

This results in y = z = -8.0.

hello @hcommin,
Thank you for this report.
There are some (special) functionalities that you should be aware of here. One of them is when you do a math operation like Fxp (.) Constant, the resulting Fxp object has the same size as the Fxp used as operand.
x = Fxp(-7.25)
x.info(3)

...
Upper		=	7.75
Lower		=	-8.0
...

You can see that (-7.25)**3 = -381.078125 < -8.0, and that's because the value of y is -8.0.
Depending of what you're trying to modeling, there are different ways to procedure:
x = Fxp(-7.25, dtype='fxp-s16/6') # fixed point space is enough to store the result
y = x ** 3
y

fxp-s16/6(-381.078125)

If you want that resulting Fxp has optimal size you could do:
x = Fxp(-7.25)
y = x ** Fxp(3) # 3 is converted to Fxp with optimal size before pow operation
y

fxp-s17/6(-381.078125)

or change the behavior of x when operates with constants:
x = Fxp(-7.25)
x.config.const_op_sizing = 'optimal'  # default value is 'same'
y = x ** 3
y

fxp-s16/6(-381.078125)

You can find more details about behaviors in this example v0_4_0_new_functionalities.ipynb

@francof2a If there is any functionality that I should be aware of, then it should be documented. None of what you wrote addresses the fact that the documentation is wrong:

This math operations returns a new Fxp object with automatic precision enough to represent the result.

There's a lot of things that remains undocumented. Be aware is a beta release (0.x.x).
The name of issue es about behavior and not about documentation. So my answer was wrote in that way. I consider that there's not problem about behavior, so I'm going to close the issue.
I thank you, by the way, about notice that in documentation (it is not updated).


text:
Support React

This adds experimental support for React. Closes #7

We dont need to React.hydrate()?

@subhendukundu The hydration happens in vite-ssr package. Vitedge is basically wrapping it to add CFW support 🙃

Oh yes, I remember now! 🙈 Sorry, forgot!

authors: frandiox subhendukundu

repo: frandiox/vitedge


text:
OnsenUI with Rails

Please provide sample example with Rails as well.

@kirantpatil I'm sorry but I don't understand what's the relation between Onsen UI and Rails. Rails is a framework for the backend and OnsenUI is for the user interface in the frontend. Onsen UI is completely independent of what you use in the backend so I think there is nothing to show in an example here.

Sure Sir, I agree with you, but let it open so that people can share if they have one. We are planning to use it with rails and will share the github link here.
Thanks.

The steps have been mentioned in issue https://github.com/OnsenUI/OnsenUI/issues/1336, so closing this issue.

authors: frankdiox kirantpatil

repo: frankdiox/OnsenUI-Material-Tabbar


text:
Larva improvements

Without changing functionality, trying to improve the code base quality of Larva. Added a TestConfig class to hold the configuration and writers of a test run. Removed the writers property everywhere.
This is not making Larva run in parallel, but just a first try to clean the code. It should be made easier to add that functionality later.
Important note: this is not making Larva perfect, just making it a little better.

Pfff elke keer als ik die code zie...

repo: frankframework/frankframework


text:
No IE support

Charts not showing in IE 11. Empty white box in place of chart.

With IE 11 having been released 4 years ago and with virtually no users  maybe its not worth catering for?

IE11 (unfortunately) still has over 3% browser share (more than Firefox)

While I agree with @system19 and @andriijas, I'm not very experienced with browser support and do feel sad about this. But there just seems no way to do it other than using a polyfill. https://github.com/frappe/charts/pull/16

@dkrasniy I notice you use Bootstrap over at https://github.com/middlebury/frontend/issues/126 and need percentage charts. Those are pretty easy to do with Bootstrap progress bars ;)

repo: frappe/charts


text:
How to detect changes?

How can I detect changes to the rating control?
So that I can save the rating value?

The rating value is on your scope.  So, you can $watch it if you need to or use ng-change.

That's what I hoped for but I can't get it to work.
$watch never triggers since the scope value never change
$scope.$watch('rating', function() {
  console.log('value: '+$scope.rating);
});

However, ng-change triggers, but the scope value is the same:
$scope.change = function() {
  console.log('value: '+$scope.rating);
}

It's probably because you're using a primitive : $scope.rating.
Try this instead (this well solve LOTS of problems with Angular).  You need to understand  this better:
https://github.com/angular/angular.js/wiki/Understanding-Scopes
$scope.data = {
  rating :  1,
  max : 5
}

$scope.$watch('rating', function() {
  console.log('value: '+$scope.rating);
});

Then in the view use :
<rating ng-model="data.rate" max="data.max"></rating>

Here's a sample : http://codepen.io/calendee/pen/zxygJe

Thank you, now it's works great!

authors: calendee sverin

repo: fraserxu/ionic-rating


text:
🛑 Prep School Website is down

In 176e752, Prep School Website (https://www.cranprep.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Prep School Website is back up in c6a17cb.

repo: fredbradley/upptime


text:
🛑 Prep School Website is down

In c9ed22a, Prep School Website (https://www.cranprep.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Prep School Website is back up in eb5c9cc.


text:
🛑 TUT Website is down

In f745fdf, TUT Website (https://www.tut.ac.za) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TUT Website is back up in 6934581 after 7 minutes.

repo: fredre/ecMonitor


text:
[Bugs] SD case mismatch

Describe the bug
Use SD in S-NSSAI containing alphabetic characters in hexadecimal representation.
In the 5GC’s YAML configuration file, SD is written in capital letters.
SD in Subscirber registration on webconsole is written in lowercase.
In this case PDU session cannot be created correctly.
To Reproduce

Apply attached patch
Run make upf && ./test.sh -o TestRegistration

Expected behavior
Test passed
Screenshots
If applicable, add screenshots to help explain the problem.
Environment (please complete the following information):

free5GC Version: 662c0191c140da976d403d98190658e3ebc70ee0
OS: Ubuntu 20.04
Kernel version: 5.15.0-67-generic
go version: 1.20.2

Log File
nishi@GTP-U:~/free5gc-deb/free5gc$ make upf && ./test.sh -o TestRegistration
make: Nothing to be done for 'upf'.
2023-03-16T13:46:48+09:00 [INFO][UPF][Main] UPF version:
        free5GC version: v3.2.1-14-g662c019
        build time:      2023-03-16T04:30:36Z
        commit hash:     e05c3433
        commit time:     2022-09-02T01:58:48Z
        go version:      go1.20.2 linux/amd64
2023-03-16T13:46:48+09:00 [INFO][UPF][Cfg] Read config from [./config/upfcfg.test.yaml]
2023-03-16T13:46:48+09:00 [INFO][UPF][Cfg] ==================================================
2023-03-16T13:46:48+09:00 [INFO][UPF][Cfg] (*factory.Config)(0xc0004066e0)({
        Version: (string) (len=5) "1.0.3",
        Description: (string) (len=31) "UPF initial local configuration",
        Pfcp: (*factory.Pfcp)(0xc000420e10)({
                Addr: (string) (len=14) "10.200.200.101",
                NodeID: (string) (len=14) "10.200.200.101",
                RetransTimeout: (time.Duration) 1s,
                MaxRetrans: (uint8) 3
        }),
        Gtpu: (*factory.Gtpu)(0xc000420fc0)({
                Forwarder: (string) (len=5) "gtp5g",
                IfList: ([]factory.IfInfo) (len=1 cap=1) {
                        (factory.IfInfo) {
                                Addr: (string) (len=14) "10.200.200.102",
                                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) "10.60.0.0/16",
                        NatIfName: (string) ""
                }
        },
        Logger: (*factory.Logger)(0xc0003eadc0)({
                Enable: (bool) true,
                Level: (string) (len=4) "info",
                ReportCaller: (bool) false
        })
})
2023-03-16T13:46:48+09:00 [INFO][UPF][Cfg] ==================================================
2023-03-16T13:46:48+09:00 [INFO][UPF][Main] Log level is set to [info] level
2023-03-16T13:46:48+09:00 [INFO][UPF][Main] starting Gtpu Forwarder [gtp5g]
2023-03-16T13:46:48+09:00 [INFO][UPF][Main] GTP Address: "10.200.200.102:2152"
tcpdump: listening on any, link-type LINUX_SLL (Linux cooked v1), capture size 262144 bytes
2023-03-16T13:46:48+09:00 [INFO][UPF][Buff] buff server started
2023-03-16T13:46:48+09:00 [INFO][UPF][Pfcp][10.200.200.101:8805] starting pfcp server
2023-03-16T13:46:48+09:00 [INFO][UPF][Pfcp][10.200.200.101:8805] pfcp server started
2023-03-16T13:46:48+09:00 [INFO][UPF][Main] UPF started
tcpdump: listening on lo, link-type EN10MB (Ethernet), capture size 262144 bytes
Run TestRegistration
2023-03-16T13:46:52+09:00 [INFO][NRF][CFG] config version [1.0.1]
2023-03-16T13:46:52+09:00 [INFO][AMF][CFG] config version [1.0.3]
2023-03-16T13:46:52+09:00 [INFO][SMF][CFG] SMF config version [1.0.2]
2023-03-16T13:46:52+09:00 [INFO][SMF][CFG] UE-Routing config version [1.0.1]
2023-03-16T13:46:52+09:00 [INFO][UDR][CFG] config version [1.0.1]
2023-03-16T13:46:52+09:00 [INFO][PCF][CFG] config version [1.0.1]
2023-03-16T13:46:52+09:00 [INFO][UDM][CFG] config version [1.0.2]
2023-03-16T13:46:52+09:00 [INFO][NSSF][CFG] config version [1.0.1]
2023-03-16T13:46:52+09:00 [INFO][AUSF][CFG] config version [1.0.2]
2023-03-16T13:46:52+09:00 [INFO][NRF][Init] NRF Log level is set to [info] level
2023-03-16T13:46:52+09:00 [INFO][NRF][Init] Server started
2023-03-16T13:46:52+09:00 [INFO][NRF][Init] nrfconfig Info: Version[1.0.1] Description[NRF initial test configuration]
2023-03-16T13:46:52+09:00 [INFO][NRF][Init] Binding addr: [127.0.0.10:8000]
2023-03-16T13:46:52+09:00 [INFO][AMF][Init] AMF Log level is set to [info] level
2023-03-16T13:46:52+09:00 [INFO][LIB][NAS] set log level : info
2023-03-16T13:46:52+09:00 [INFO][LIB][NAS] set report call : false
2023-03-16T13:46:52+09:00 [INFO][LIB][NGAP] set log level : info
2023-03-16T13:46:52+09:00 [INFO][LIB][NGAP] set report call : false
2023-03-16T13:46:52+09:00 [INFO][LIB][FSM] set log level : info
2023-03-16T13:46:52+09:00 [INFO][LIB][FSM] set report call : false
2023-03-16T13:46:52+09:00 [INFO][LIB][Aper] set log level : info
2023-03-16T13:46:52+09:00 [INFO][LIB][Aper] set report call : false
2023-03-16T13:46:52+09:00 [INFO][AMF][Init] Server started
2023-03-16T13:46:52+09:00 [INFO][AMF][Util] amfconfig Info: Version[1.0.3] Description[AMF initial test configuration]
2023-03-16T13:46:52+09:00 [INFO][AMF][NGAP] Listen on 127.0.0.1:38412
2023-03-16T13:46:52+09:00 [INFO][NRF][MGMT] Handle NFRegisterRequest
2023-03-16T13:46:52+09:00 [INFO][NRF][MGMT] urilist update
2023-03-16T13:46:52+09:00 [INFO][NRF][MGMT] Create NF Profile
2023-03-16T13:46:52+09:00 [INFO][NRF][MGMT] Location header:  http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/776938bb-c354-4c68-921e-0871ac0ef5d9
2023-03-16T13:46:52+09:00 [INFO][NRF][GIN] | 201 |       127.0.0.1 | PUT     | /nnrf-nfm/v1/nf-instances/776938bb-c354-4c68-921e-0871ac0ef5d9 |
2023-03-16T13:46:53+09:00 [INFO][SMF][Init] SMF Log level is set to [info] level
2023-03-16T13:46:53+09:00 [INFO][LIB][NAS] set log level : info
2023-03-16T13:46:53+09:00 [INFO][LIB][NAS] set report call : false
2023-03-16T13:46:53+09:00 [INFO][LIB][NGAP] set log level : info
2023-03-16T13:46:53+09:00 [INFO][LIB][NGAP] set report call : false
2023-03-16T13:46:53+09:00 [INFO][LIB][Aper] set log level : info
2023-03-16T13:46:53+09:00 [INFO][LIB][Aper] set report call : false
2023-03-16T13:46:53+09:00 [INFO][LIB][PFCP] set log level : info
2023-03-16T13:46:53+09:00 [INFO][LIB][PFCP] set report call : false
2023-03-16T13:46:53+09:00 [INFO][SMF][CTX] smfconfig Info: Version[1.0.2] Description[SMF initial single test configuration]
2023-03-16T13:46:53+09:00 [INFO][SMF][CTX] Endpoints: [10.200.200.102]
2023-03-16T13:46:53+09:00 [INFO][SMF][Init] Server started
2023-03-16T13:46:53+09:00 [INFO][NRF][MGMT] Handle NFRegisterRequest
2023-03-16T13:46:53+09:00 [INFO][NRF][MGMT] urilist update
2023-03-16T13:46:53+09:00 [INFO][NRF][MGMT] Create NF Profile
2023-03-16T13:46:53+09:00 [INFO][NRF][MGMT] Location header:  http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/ad66edc4-12b1-479d-b38e-93c65e136d93
2023-03-16T13:46:53+09:00 [INFO][NRF][GIN] | 201 |       127.0.0.1 | PUT     | /nnrf-nfm/v1/nf-instances/ad66edc4-12b1-479d-b38e-93c65e136d93 |
2023-03-16T13:46:53+09:00 [INFO][SMF][Init] SMF Registration to NRF {ad66edc4-12b1-479d-b38e-93c65e136d93 SMF REGISTERED 0 0xc0005ef380 0xc0005ef3b0 [] []   [127.0.0.2] [] <nil> [] [] <nil> 0 0 0  <nil> <nil> <nil> <nil> 0xc000302dc0 <nil> <nil> <nil> <nil> <nil> map[] <nil> false 0xc0005ef278 false false []}
2023-03-16T13:46:53+09:00 [INFO][SMF][PFCP] Listen on 10.200.200.1:8805
2023-03-16T13:46:53+09:00 [INFO][SMF][App] Sending PFCP Association Request to UPF[10.200.200.101]
2023-03-16T13:46:53+09:00 [INFO][UPF][Pfcp][10.200.200.101:8805] handleAssociationSetupRequest
2023-03-16T13:46:53+09:00 [INFO][UPF][Pfcp][10.200.200.101:8805][rNodeID:10.200.200.1] New node
2023-03-16T13:46:53+09:00 [INFO][LIB][PFCP] Remove Request Transaction [1]
2023-03-16T13:46:53+09:00 [INFO][SMF][App] Received PFCP Association Setup Accepted Response from UPF[10.200.200.101]
2023-03-16T13:46:53+09:00 [INFO][UDR][Init] UDR Log level is set to [info] level
2023-03-16T13:46:53+09:00 [INFO][UDR][Init] UDR Config Info: Version[1.0.1] Description[UDR initial test configuration]
2023-03-16T13:46:53+09:00 [INFO][UDR][Init] Server started
2023-03-16T13:46:53+09:00 [INFO][UDR][Util] udrconfig Info: Version[1.0.1] Description[UDR initial test configuration]
2023-03-16T13:46:53+09:00 [INFO][NRF][MGMT] Handle NFRegisterRequest
2023-03-16T13:46:53+09:00 [INFO][NRF][MGMT] urilist update
2023-03-16T13:46:53+09:00 [INFO][NRF][MGMT] Create NF Profile
2023-03-16T13:46:53+09:00 [INFO][NRF][MGMT] Location header:  http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/1d2635f4-a5eb-4e60-ad5e-fb58d0e6ba23
2023-03-16T13:46:53+09:00 [INFO][NRF][GIN] | 201 |       127.0.0.1 | PUT     | /nnrf-nfm/v1/nf-instances/1d2635f4-a5eb-4e60-ad5e-fb58d0e6ba23 |
2023-03-16T13:46:53+09:00 [INFO][PCF][Init] PCF Log level is set to [info] level
2023-03-16T13:46:53+09:00 [INFO][PCF][Init] Server started
2023-03-16T13:46:53+09:00 [INFO][PCF][Util] pcfconfig Info: Version[1.0.1] Description[PCF initial test configuration]
2023-03-16T13:46:53+09:00 [INFO][NRF][MGMT] Handle NFRegisterRequest
2023-03-16T13:46:53+09:00 [INFO][NRF][MGMT] urilist update
2023-03-16T13:46:53+09:00 [INFO][NRF][MGMT] Create NF Profile
2023-03-16T13:46:53+09:00 [INFO][NRF][MGMT] Location header:  http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/469f9951-c983-40c7-9908-40656921fd90
2023-03-16T13:46:53+09:00 [INFO][NRF][GIN] | 201 |       127.0.0.1 | PUT     | /nnrf-nfm/v1/nf-instances/469f9951-c983-40c7-9908-40656921fd90 |
2023-03-16T13:46:53+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2023-03-16T13:46:53+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?requester-nf-type=PCF&service-names=nudr-dr&target-nf-type=UDR |
2023-03-16T13:46:53+09:00 [INFO][UDM][Init] UDM Log level is set to [info] level
2023-03-16T13:46:53+09:00 [INFO][UDM][Init] UDM Config Info: Version[1.0.2] Description[UDM initial test configuration]
2023-03-16T13:46:53+09:00 [INFO][UDM][Init] Server started
2023-03-16T13:46:53+09:00 [INFO][UDM][Util] udmconfig Info: Version[1.0.2] Description[UDM initial test configuration]
2023-03-16T13:46:53+09:00 [INFO][NRF][MGMT] Handle NFRegisterRequest
2023-03-16T13:46:53+09:00 [INFO][NRF][MGMT] urilist update
2023-03-16T13:46:53+09:00 [INFO][NRF][MGMT] Create NF Profile
2023-03-16T13:46:53+09:00 [INFO][NRF][MGMT] Location header:  http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/f44adc11-850a-4c45-9516-74e8094b278a
2023-03-16T13:46:53+09:00 [INFO][NRF][GIN] | 201 |       127.0.0.1 | PUT     | /nnrf-nfm/v1/nf-instances/f44adc11-850a-4c45-9516-74e8094b278a |
2023-03-16T13:46:53+09:00 [INFO][NSSF][Init] NSSF Log level is set to [info] level
2023-03-16T13:46:53+09:00 [INFO][NSSF][Init] Server started
2023-03-16T13:46:53+09:00 [INFO][NRF][MGMT] Handle NFRegisterRequest
2023-03-16T13:46:53+09:00 [INFO][NRF][MGMT] urilist update
2023-03-16T13:46:53+09:00 [INFO][NRF][MGMT] Create NF Profile
2023-03-16T13:46:53+09:00 [INFO][NRF][MGMT] Location header:  http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/9b8592ad-8323-4a8e-a423-0b30d5b1e0c1
2023-03-16T13:46:53+09:00 [INFO][NRF][GIN] | 201 |       127.0.0.1 | PUT     | /nnrf-nfm/v1/nf-instances/9b8592ad-8323-4a8e-a423-0b30d5b1e0c1 |
2023-03-16T13:46:54+09:00 [INFO][AUSF][Init] AUSF Log level is set to [info] level
2023-03-16T13:46:54+09:00 [INFO][AUSF][Init] Server started
2023-03-16T13:46:54+09:00 [INFO][AUSF][Init] ausfconfig Info: Version[1.0.2] Description[AUSF initial test configuration]
ausf context =  &{{{0 0} {[] {} <nil>} map[] 0} {{0 0} {[] {} <nil>} map[] 0} 7c65f526-285d-4898-bc2b-073eb7857ac4 ausfGroup001 8000 127.0.0.9 127.0.0.9 http://127.0.0.9:8000 http http://127.0.0.10:8000 map[nausf-auth:{7c65f526-285d-4898-bc2b-073eb7857ac4 nausf-auth 0xc000127e30 http REGISTERED   0xc000127e18  [] <nil> [] [] <nil> 0 0 0 <nil> <nil> }] [{208 93} {123 45}]  0xc0001f9ea0 false}
2023-03-16T13:46:54+09:00 [INFO][NRF][MGMT] Handle NFRegisterRequest
2023-03-16T13:46:54+09:00 [INFO][NRF][MGMT] urilist update
2023-03-16T13:46:54+09:00 [INFO][NRF][MGMT] Create NF Profile
2023-03-16T13:46:54+09:00 [INFO][NRF][MGMT] Location header:  http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/7c65f526-285d-4898-bc2b-073eb7857ac4
2023-03-16T13:46:54+09:00 [INFO][NRF][GIN] | 201 |       127.0.0.1 | PUT     | /nnrf-nfm/v1/nf-instances/7c65f526-285d-4898-bc2b-073eb7857ac4 |
=== RUN   TestRegistration
2023-03-16T13:46:54+09:00 [INFO][AMF][NGAP] [AMF] SCTP Accept from: 127.0.0.1:9487
2023-03-16T13:46:54+09:00 [INFO][AMF][NGAP] Create a new NG connection for: 127.0.0.1:9487
2023-03-16T13:46:54+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] Handle NG Setup request
2023-03-16T13:46:54+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] Send NG-Setup response
2023-03-16T13:46:54+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] Handle Initial UE Message
2023-03-16T13:46:54+09:00 [INFO][LIB][FSM] Handle event[Gmm Message], transition from [Deregistered] to [Deregistered]
2023-03-16T13:46:54+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1] Handle Registration Request
2023-03-16T13:46:54+09:00 [INFO][LIB][FSM] Handle event[Start Authentication], transition from [Deregistered] to [Authentication]
2023-03-16T13:46:54+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1] Authentication procedure
2023-03-16T13:46:54+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2023-03-16T13:46:54+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?requester-nf-type=AMF&target-nf-type=AUSF |
2023-03-16T13:46:54+09:00 [INFO][AUSF][UeAuthPost] HandleUeAuthPostRequest
2023-03-16T13:46:54+09:00 [INFO][AUSF][UeAuthPost] Serving network authorized
2023-03-16T13:46:54+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2023-03-16T13:46:54+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?requester-nf-type=AUSF&service-names=nudm-ueau&target-nf-type=UDM |
2023-03-16T13:46:54+09:00 [INFO][UDM][UEAU] Handle GenerateAuthDataRequest
2023-03-16T13:46:54+09:00 [INFO][UDM][Suci] suciPart: [suci 0 208 93 0 0 0 00007487]
2023-03-16T13:46:54+09:00 [INFO][UDM][Suci] scheme 0
2023-03-16T13:46:54+09:00 [INFO][UDM][Suci] SUPI type is IMSI
http://127.0.0.10:8000
2023-03-16T13:46:54+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2023-03-16T13:46:54+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?requester-nf-type=UDM&target-nf-type=UDR |
2023-03-16T13:46:54+09:00 [INFO][UDR][DRepo] Handle QueryAuthSubsData
2023-03-16T13:46:54+09:00 [INFO][UDR][GIN] | 200 |       127.0.0.1 | GET     | /nudr-dr/v1/subscription-data/imsi-2089300007487/authentication-data/authentication-subscription |
2023-03-16T13:46:54+09:00 [INFO][UDR][DRepo] Handle ModifyAuthentication
2023-03-16T13:46:54+09:00 [INFO][UDR][GIN] | 204 |       127.0.0.1 | PATCH   | /nudr-dr/v1/subscription-data/imsi-2089300007487/authentication-data/authentication-subscription |
2023-03-16T13:46:54+09:00 [INFO][UDM][GIN] | 200 |       127.0.0.1 | POST    | /nudm-ueau/v1/suci-0-208-93-0-0-0-00007487/security-information/generate-auth-data |
2023-03-16T13:46:54+09:00 [INFO][AUSF][UeAuthPost] Add SuciSupiPair (suci-0-208-93-0-0-0-00007487, imsi-2089300007487) to map.
2023-03-16T13:46:54+09:00 [INFO][AUSF][UeAuthPost] Use 5G AKA auth method
2023-03-16T13:46:54+09:00 [INFO][AUSF][5gAkaAuth] XresStar = 3535363736633238363364373233363239306161313664656134313836353364
2023-03-16T13:46:54+09:00 [INFO][AUSF][GIN] | 201 |       127.0.0.1 | POST    | /nausf-auth/v1/ue-authentications |
2023-03-16T13:46:54+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1] Send Authentication Request
2023-03-16T13:46:54+09:00 [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Send Downlink Nas Transport
2023-03-16T13:46:54+09:00 [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Uplink NAS Transport (RAN UE NGAP ID: 1)
2023-03-16T13:46:54+09:00 [INFO][LIB][FSM] Handle event[Gmm Message], transition from [Authentication] to [Authentication]
2023-03-16T13:46:54+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1] Handle Authentication Response
2023-03-16T13:46:54+09:00 [INFO][AUSF][5gAkaAuth] Auth5gAkaComfirmRequest
2023-03-16T13:46:54+09:00 [INFO][AUSF][5gAkaAuth] res*: 3535363736633238363364373233363239306161313664656134313836353364
Xres*: 3535363736633238363364373233363239306161313664656134313836353364
2023-03-16T13:46:54+09:00 [INFO][AUSF][5gAkaAuth] 5G AKA confirmation succeeded
2023-03-16T13:46:54+09:00 [INFO][UDM][UEAU] Handle ConfirmAuthDataRequest
2023-03-16T13:46:54+09:00 [INFO][UDR][DRepo] Handle CreateAuthenticationStatus
2023-03-16T13:46:54+09:00 [INFO][UDR][GIN] | 204 |       127.0.0.1 | PUT     | /nudr-dr/v1/subscription-data/imsi-2089300007487/authentication-data/authentication-status |
2023-03-16T13:46:54+09:00 [INFO][UDM][GIN] | 201 |       127.0.0.1 | POST    | /nudm-ueau/v1/imsi-2089300007487/auth-events |
2023-03-16T13:46:54+09:00 [INFO][AUSF][GIN] | 200 |       127.0.0.1 | PUT     | /nausf-auth/v1/ue-authentications/suci-0-208-93-0-0-0-00007487/5g-aka-confirmation |
2023-03-16T13:46:54+09:00 [INFO][LIB][FSM] Handle event[Authentication Success], transition from [Authentication] to [SecurityMode]
2023-03-16T13:46:54+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] Send Security Mode Command
2023-03-16T13:46:54+09:00 [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Send Downlink Nas Transport
Security Header Type Integrity Protected With New 5g Nas Security Context
cmac value: 0x61ee5924
err <nil>
2023-03-16T13:46:54+09:00 [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Uplink NAS Transport (RAN UE NGAP ID: 1)
2023-03-16T13:46:54+09:00 [INFO][LIB][FSM] Handle event[Gmm Message], transition from [SecurityMode] to [SecurityMode]
2023-03-16T13:46:54+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] Handle Security Mode Complete
2023-03-16T13:46:54+09:00 [INFO][LIB][FSM] Handle event[SecurityMode Success], transition from [SecurityMode] to [ContextSetup]
2023-03-16T13:46:54+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] Handle InitialRegistration
2023-03-16T13:46:54+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2023-03-16T13:46:54+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?requester-nf-type=AMF&supi=imsi-2089300007487&target-nf-type=UDM |
2023-03-16T13:46:54+09:00 [INFO][UDM][SDM] Handle GetNssai
2023-03-16T13:46:54+09:00 [INFO][UDR][DRepo] Handle QueryAmData
2023-03-16T13:46:54+09:00 [INFO][UDR][GIN] | 200 |       127.0.0.1 | GET     | /nudr-dr/v1/subscription-data/imsi-2089300007487/20893/provisioned-data/am-data |
2023-03-16T13:46:54+09:00 [INFO][UDM][GIN] | 200 |       127.0.0.1 | GET     | /nudm-sdm/v1/imsi-2089300007487/nssai?plmn-id=%7B%22mcc%22%3A%22208%22%2C%22mnc%22%3A%2293%22%7D |
2023-03-16T13:46:54+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2023-03-16T13:46:54+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?requester-nf-type=AMF&supi=imsi-2089300007487&target-nf-type=UDM |
2023-03-16T13:46:54+09:00 [INFO][UDM][UECM] Handle RegistrationAmf3gppAccess
2023-03-16T13:46:54+09:00 [INFO][UDM][UECM] UEID: imsi-2089300007487
2023-03-16T13:46:54+09:00 [INFO][UDR][DRepo] Handle CreateAmfContext3gpp
2023-03-16T13:46:54+09:00 [INFO][UDR][GIN] | 204 |       127.0.0.1 | PUT     | /nudr-dr/v1/subscription-data/imsi-2089300007487/context-data/amf-3gpp-access |
2023-03-16T13:46:54+09:00 [INFO][UDM][GIN] | 201 |       127.0.0.1 | PUT     | /nudm-uecm/v1/imsi-2089300007487/registrations/amf-3gpp-access |
2023-03-16T13:46:54+09:00 [INFO][UDM][SDM] Handle GetAmData
2023-03-16T13:46:54+09:00 [INFO][UDR][DRepo] Handle QueryAmData
2023-03-16T13:46:54+09:00 [INFO][UDR][GIN] | 200 |       127.0.0.1 | GET     | /nudr-dr/v1/subscription-data/imsi-2089300007487/20893/provisioned-data/am-data?supported-features=%7B%22mcc%22%3A%22208%22%2C%22mnc%22%3A%2293%22%7D |
2023-03-16T13:46:54+09:00 [INFO][UDM][GIN] | 200 |       127.0.0.1 | GET     | /nudm-sdm/v1/imsi-2089300007487/am-data?plmn-id=%7B%22mcc%22%3A%22208%22%2C%22mnc%22%3A%2293%22%7D |
2023-03-16T13:46:54+09:00 [INFO][UDM][SDM] Handle GetSmfSelectData
2023/03/16 13:46:54 http2: server connection error from 127.0.0.1:49810: connection error: PROTOCOL_ERROR
2023-03-16T13:46:54+09:00 [INFO][UDR][DRepo] Handle QuerySmfSelectData
2023-03-16T13:46:54+09:00 [INFO][UDR][GIN] | 200 |       127.0.0.1 | GET     | /nudr-dr/v1/subscription-data/imsi-2089300007487/20893/provisioned-data/smf-selection-subscription-data |
2023-03-16T13:46:54+09:00 [INFO][UDM][GIN] | 200 |       127.0.0.1 | GET     | /nudm-sdm/v1/imsi-2089300007487/smf-select-data?plmn-id=%7B%22mcc%22%3A%22208%22%2C%22mnc%22%3A%2293%22%7D |
2023-03-16T13:46:54+09:00 [INFO][UDM][SDM] Handle GetUeContextInSmfData
2023-03-16T13:46:54+09:00 [INFO][UDR][DRepo] Handle QuerySmfRegList
2023-03-16T13:46:54+09:00 [INFO][UDR][GIN] | 200 |       127.0.0.1 | GET     | /nudr-dr/v1/subscription-data/imsi-2089300007487/context-data/smf-registrations |
2023-03-16T13:46:54+09:00 [INFO][UDM][GIN] | 200 |       127.0.0.1 | GET     | /nudm-sdm/v1/imsi-2089300007487/ue-context-in-smf-data |
2023/03/16 13:46:54 http2: server connection error from 127.0.0.1:50268: connection error: PROTOCOL_ERROR
2023-03-16T13:46:54+09:00 [INFO][UDM][SDM] Handle Subscribe
2023-03-16T13:46:54+09:00 [INFO][UDR][DRepo] Handle CreateSdmSubscriptions
2023-03-16T13:46:54+09:00 [INFO][UDR][GIN] | 201 |       127.0.0.1 | POST    | /nudr-dr/v1/subscription-data/imsi-2089300007487/context-data/sdm-subscriptions |
2023-03-16T13:46:54+09:00 [INFO][UDM][GIN] | 201 |       127.0.0.1 | POST    | /nudm-sdm/v1/imsi-2089300007487/sdm-subscriptions |
2023-03-16T13:46:54+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2023-03-16T13:46:54+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?requester-nf-type=AMF&supi=imsi-2089300007487&target-nf-type=PCF |
2023-03-16T13:46:54+09:00 [INFO][PCF][Ampolicy] Handle AM Policy Create Request
2023-03-16T13:46:54+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2023-03-16T13:46:54+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?requester-nf-type=PCF&target-nf-type=UDR |
2023-03-16T13:46:54+09:00 [INFO][UDR][DRepo] Handle PolicyDataUesUeIdAmDataGet
2023-03-16T13:46:54+09:00 [INFO][UDR][GIN] | 200 |       127.0.0.1 | GET     | /nudr-dr/v1/policy-data/ues/imsi-2089300007487/am-data |
2023-03-16T13:46:54+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2023-03-16T13:46:54+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?guami=%7B%22plmnId%22%3A%7B%22mcc%22%3A%22208%22%2C%22mnc%22%3A%2293%22%7D%2C%22amfId%22%3A%22cafe00%22%7D&requester-nf-type=PCF&target-nf-type=AMF |
2023-03-16T13:46:54+09:00 [INFO][AMF][Comm] Handle AMF Status Change Subscribe Request
2023-03-16T13:46:54+09:00 [INFO][AMF][Comm] new AMF Status Subscription[1]
2023-03-16T13:46:54+09:00 [INFO][AMF][GIN] | 201 |       127.0.0.1 | POST    | /namf-comm/v1/subscriptions |
2023-03-16T13:46:54+09:00 [INFO][PCF][GIN] | 201 |       127.0.0.1 | POST    | /npcf-am-policy-control/v1/policies |
2023-03-16T13:46:54+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] Send Registration Accept
2023-03-16T13:46:54+09:00 [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Send Initial Context Setup Request
2023-03-16T13:46:54+09:00 [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Handle Initial Context Setup Response
2023-03-16T13:46:54+09:00 [INFO][NAS][Message] Encode ExtendedProtocolConfigurationOptions in EncodePDUSessionEstablishmentRequest
2023-03-16T13:46:54+09:00 [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Uplink NAS Transport (RAN UE NGAP ID: 1)
2023-03-16T13:46:54+09:00 [INFO][LIB][FSM] Handle event[Gmm Message], transition from [ContextSetup] to [ContextSetup]
2023-03-16T13:46:54+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] Handle Registration Complete
2023-03-16T13:46:54+09:00 [INFO][LIB][FSM] Handle event[ContextSetup Success], transition from [ContextSetup] to [Registered]
2023-03-16T13:46:54+09:00 [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Uplink NAS Transport (RAN UE NGAP ID: 1)
2023-03-16T13:46:54+09:00 [INFO][LIB][FSM] Handle event[Gmm Message], transition from [Registered] to [Registered]
2023-03-16T13:46:54+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] Handle UL NAS Transport
2023-03-16T13:46:54+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] Transport 5GSM Message to SMF
2023-03-16T13:46:54+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] Select SMF [snssai: {Sst:1 Sd:fedcba}, dnn: internet]
2023-03-16T13:46:54+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2023-03-16T13:46:54+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?requester-nf-type=AMF&target-nf-type=NSSF |
2023-03-16T13:46:54+09:00 [INFO][NSSF][NsSelect] Handle NSSelectionGet
2023-03-16T13:46:54+09:00 [INFO][NSSF][GIN] | 200 |       127.0.0.1 | GET     | /nnssf-nsselection/v1/network-slice-information?nf-id=776938bb-c354-4c68-921e-0871ac0ef5d9&nf-type=AMF&slice-info-request-for-pdu-session=%7B%22sNssai%22%3A%7B%22sst%22%3A1%2C%22sd%22%3A%22fedcba%22%7D%2C%22roamingIndication%22%3A%22NON_ROAMING%22%7D |
2023-03-16T13:46:54+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2023-03-16T13:46:54+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?dnn=internet&requester-nf-type=AMF&service-names=nsmf-pdusession&snssais=%7B%22sst%22%3A1%2C%22sd%22%3A%22fedcba%22%7D&target-nf-type=SMF&target-plmn-list=%7B%22mcc%22%3A%22208%22%2C%22mnc%22%3A%2293%22%7D |
2023-03-16T13:46:54+09:00 [INFO][SMF][PduSess] Receive Create SM Context Request
2023-03-16T13:46:54+09:00 [INFO][SMF][PduSess] In HandlePDUSessionSMContextCreate
2023-03-16T13:46:54+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2023-03-16T13:46:54+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?requester-nf-type=SMF&target-nf-type=UDM |
2023-03-16T13:46:54+09:00 [INFO][SMF][PduSess] Send NF Discovery Serving UDM Successfully
2023-03-16T13:46:54+09:00 [INFO][SMF][CTX] Allocated UE IP address: 10.60.0.1
2023-03-16T13:46:54+09:00 [INFO][SMF][CTX] Selected UPF: UPF
2023-03-16T13:46:54+09:00 [INFO][SMF][PduSess] UE[imsi-2089300007487] PDUSessionID[10] IP[10.60.0.1]
2023-03-16T13:46:54+09:00 [INFO][UDM][SDM] Handle GetSmData
2023-03-16T13:46:54+09:00 [INFO][UDM][SDM] getSmDataProcedure: SUPI[imsi-2089300007487] PLMNID[20893] DNN[internet] SNssai[{"sst":1,"sd":"fedcba"}]
2023-03-16T13:46:54+09:00 [INFO][UDR][DRepo] Handle QuerySmData
2023-03-16T13:46:54+09:00 [INFO][UDR][GIN] | 200 |       127.0.0.1 | GET     | /nudr-dr/v1/subscription-data/imsi-2089300007487/20893/provisioned-data/sm-data?single-nssai=%7B%22sst%22%3A1%2C%22sd%22%3A%22fedcba%22%7D |
2023-03-16T13:46:54+09:00 [INFO][UDM][GIN] | 200 |       127.0.0.1 | GET     | /nudm-sdm/v1/imsi-2089300007487/sm-data?dnn=internet&plmn-id=%7B%22mcc%22%3A%22208%22%2C%22mnc%22%3A%2293%22%7D&single-nssai=%7B%22sst%22%3A1%2C%22sd%22%3A%22fedcba%22%7D |
2023-03-16T13:46:54+09:00 [INFO][SMF][GSM] In HandlePDUSessionEstablishmentRequest
2023-03-16T13:46:54+09:00 [INFO][NAS][Convert] ProtocolOrContainerList:  [0xc000b699c0 0xc000b699e0 0xc000b69a00]
2023-03-16T13:46:54+09:00 [INFO][SMF][GSM] Protocol Configuration Options
2023-03-16T13:46:54+09:00 [INFO][SMF][GSM] &{[0xc000b699c0 0xc000b699e0 0xc000b69a00]}
2023-03-16T13:46:54+09:00 [INFO][SMF][GSM] Didn't Implement container type IPAddressAllocationViaNASSignallingUL
2023-03-16T13:46:54+09:00 [INFO][SMF][PduSess] PCF Selection for SMContext SUPI[imsi-2089300007487] PDUSessionID[10]
2023-03-16T13:46:54+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2023-03-16T13:46:54+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?requester-nf-type=SMF&target-nf-type=PCF |
2023-03-16T13:46:54+09:00 [INFO][PCF][SMpolicy] Handle CreateSmPolicy
2023-03-16T13:46:54+09:00 [INFO][UDR][DRepo] Handle PolicyDataUesUeIdSmDataGet
2023-03-16T13:46:54+09:00 [INFO][UDR][GIN] | 404 |       127.0.0.1 | GET     | /nudr-dr/v1/policy-data/ues/imsi-2089300007487/sm-data?dnn=internet&snssai=%7B%22sst%22%3A1%2C%22sd%22%3A%22fedcba%22%7D |
2023-03-16T13:46:54+09:00 [WARN][PCF][SMpolicy] Can't find UE[imsi-2089300007487] SM Policy Data in UDR
2023-03-16T13:46:54+09:00 [INFO][PCF][GIN] | 400 |       127.0.0.1 | POST    | /npcf-smpolicycontrol/v1/sm-policies |
2023-03-16T13:46:54+09:00 [ERRO][SMF][PduSess] setup sm policy association failed: 400 Bad Request {  400 Can't find UE SM Policy Data in UDR  USER_UNKNOWN []}
2023-03-16T13:46:54+09:00 [INFO][SMF][GIN] | 403 |       127.0.0.1 | POST    | /nsmf-pdusession/v1/sm-contexts |
2023-03-16T13:46:54+09:00 [WARN][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] PDU Session Establishment Request is rejected by SMF[pduSessionId:10]
2023-03-16T13:46:54+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] Send DL NAS Transport
2023-03-16T13:46:54+09:00 [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Send Downlink Nas Transport
    registration_test.go:218:
                Error Trace:    registration_test.go:218
                Error:          Should be true
                Test:           TestRegistration
                Messages:       No PDUSessionResourceSetup received.
2023-03-16T13:46:54+09:00 [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Handle PDU Session Resource Setup Response
2023-03-16T13:46:54+09:00 [ERRO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] SmContext[PDU Session ID:10] not found
2023-03-16T13:46:56+09:00 [INFO][AMF][NGAP] Handle SCTP Notification[addr: <nil>]
2023-03-16T13:46:56+09:00 [INFO][AUSF][Init] Terminating AUSF...
2023-03-16T13:46:56+09:00 [INFO][AUSF][App] Send Deregister NFInstance
2023-03-16T13:46:56+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] SCTP_SHUTDOWN_EVENT notification, close the connection
2023-03-16T13:46:56+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] Remove RAN Context[ID: <PlmnID: {Mcc:208 Mnc:93}, GNbID: 000102>]
2023-03-16T13:46:56+09:00 [INFO][AMF][NGAP] Handle SCTP Notification[addr: <nil>]
2023-03-16T13:46:56+09:00 [WARN][AMF][NGAP] RAN context has been removed[addr: <nil>]
2023-03-16T13:46:56+09:00 [INFO][NRF][MGMT] Handle NFDeregisterRequest
2023-03-16T13:46:57+09:00 [INFO][NRF][GIN] | 204 |       127.0.0.1 | DELETE  | /nnrf-nfm/v1/nf-instances/7c65f526-285d-4898-bc2b-073eb7857ac4 |
2023-03-16T13:46:57+09:00 [INFO][AUSF][Init] Deregister from NRF successfully
2023-03-16T13:46:57+09:00 [INFO][AUSF][Init] AUSF terminated
2023-03-16T13:46:57+09:00 [INFO][NSSF][Init] Terminating NSSF...
2023-03-16T13:46:57+09:00 [INFO][NSSF][App] Send Deregister NFInstance
2023-03-16T13:46:57+09:00 [INFO][NRF][MGMT] Handle NFDeregisterRequest
2023-03-16T13:46:58+09:00 [INFO][NRF][GIN] | 204 |       127.0.0.1 | DELETE  | /nnrf-nfm/v1/nf-instances/9b8592ad-8323-4a8e-a423-0b30d5b1e0c1 |
2023-03-16T13:46:58+09:00 [INFO][NSSF][Init] Deregister from NRF successfully
2023-03-16T13:46:58+09:00 [INFO][NSSF][Init] NSSF terminated
2023-03-16T13:46:58+09:00 [INFO][UDM][Init] Terminating UDM...
2023-03-16T13:46:58+09:00 [INFO][UDM][Consumer] Send Deregister NFInstance
2023/03/16 13:46:58 http2: server connection error from 127.0.0.1:57732: connection error: PROTOCOL_ERROR
2023-03-16T13:46:58+09:00 [INFO][NRF][MGMT] Handle NFDeregisterRequest
2023-03-16T13:46:59+09:00 [INFO][NRF][GIN] | 204 |       127.0.0.1 | DELETE  | /nnrf-nfm/v1/nf-instances/f44adc11-850a-4c45-9516-74e8094b278a |
2023-03-16T13:46:59+09:00 [INFO][UDM][Init] Deregister from NRF successfully
2023-03-16T13:46:59+09:00 [INFO][UDM][Init] UDM terminated
2023-03-16T13:46:59+09:00 [INFO][PCF][Init] Terminating PCF...
2023-03-16T13:46:59+09:00 [INFO][PCF][Consumer] Send Deregister NFInstance
2023-03-16T13:46:59+09:00 [INFO][NRF][MGMT] Handle NFDeregisterRequest
2023-03-16T13:47:00+09:00 [INFO][NRF][GIN] | 204 |       127.0.0.1 | DELETE  | /nnrf-nfm/v1/nf-instances/469f9951-c983-40c7-9908-40656921fd90 |
2023-03-16T13:47:00+09:00 [INFO][PCF][Init] Deregister from NRF successfully
2023-03-16T13:47:00+09:00 [INFO][PCF][Init] PCF terminated
2023-03-16T13:47:00+09:00 [INFO][UDR][Init] Terminating UDR...
2023-03-16T13:47:00+09:00 [INFO][UDR][Consumer] Send Deregister NFInstance
2023-03-16T13:47:00+09:00 [INFO][NRF][MGMT] Handle NFDeregisterRequest
2023-03-16T13:47:01+09:00 [INFO][NRF][GIN] | 204 |       127.0.0.1 | DELETE  | /nnrf-nfm/v1/nf-instances/1d2635f4-a5eb-4e60-ad5e-fb58d0e6ba23 |
2023-03-16T13:47:01+09:00 [INFO][UDR][Init] Deregister from NRF successfully
2023-03-16T13:47:01+09:00 [INFO][UDR][Init] UDR terminated
2023-03-16T13:47:01+09:00 [INFO][SMF][Init] Terminating SMF...
2023-03-16T13:47:01+09:00 [INFO][SMF][Consumer] Send Deregister NFInstance
2023-03-16T13:47:01+09:00 [INFO][NRF][MGMT] Handle NFDeregisterRequest
2023-03-16T13:47:02+09:00 [INFO][NRF][GIN] | 204 |       127.0.0.1 | DELETE  | /nnrf-nfm/v1/nf-instances/ad66edc4-12b1-479d-b38e-93c65e136d93 |
2023-03-16T13:47:02+09:00 [INFO][SMF][Init] Deregister from NRF successfully
2023-03-16T13:47:02+09:00 [INFO][AMF][Init] Terminating AMF...
2023-03-16T13:47:02+09:00 [INFO][AMF][Consumer] [AMF] Send Deregister NFInstance
2023-03-16T13:47:02+09:00 [INFO][NRF][MGMT] Handle NFDeregisterRequest
2023-03-16T13:47:03+09:00 [INFO][NRF][GIN] | 204 |       127.0.0.1 | DELETE  | /nnrf-nfm/v1/nf-instances/776938bb-c354-4c68-921e-0871ac0ef5d9 |
2023-03-16T13:47:03+09:00 [INFO][AMF][Init] [AMF] Deregister from NRF successfully
2023-03-16T13:47:03+09:00 [INFO][AMF][Init] Send AMF Status Indication to Notify RANs due to AMF terminating
2023-03-16T13:47:03+09:00 [INFO][AMF][NGAP] Close SCTP server...
2023-03-16T13:47:03+09:00 [INFO][AMF][NGAP] SCTP server closed
2023-03-16T13:47:03+09:00 [INFO][AMF][Producer] [AMF] Send Amf Status Change Notify to http://127.0.0.7:8000/npcf-callback/v1/amfstatus
2023-03-16T13:47:03+09:00 [WARN][PCF][Callback] [PCF] Handle Amf Status Change Notify is not implemented.
2023-03-16T13:47:03+09:00 [INFO][PCF][GIN] | 204 |       127.0.0.1 | POST    | /npcf-callback/v1/amfstatus |
2023-03-16T13:47:03+09:00 [INFO][AMF][Init] AMF terminated
2023-03-16T13:47:03+09:00 [INFO][NRF][Init] Terminating NRF...
2023-03-16T13:47:03+09:00 [INFO][NRF][Init] Remove NF Profile...
2023-03-16T13:47:03+09:00 [INFO][NRF][Init] NRF terminated
--- FAIL: TestRegistration (9.41s)
FAIL
exit status 1
FAIL    test    11.069s
2023-03-16T13:47:06+09:00 [INFO][UPF][Main] Shutdown UPF ...
2023-03-16T13:47:06+09:00 [INFO][UPF][Pfcp][10.200.200.101:8805] Stopping pfcp server
2023-03-16T13:47:06+09:00 [ERRO][UPF][Pfcp][10.200.200.101:8805] read udp4 10.200.200.101:8805: use of closed network connection
2023-03-16T13:47:06+09:00 [INFO][UPF][Pfcp][10.200.200.101:8805] pfcp reciver stopped
2023-03-16T13:47:06+09:00 [INFO][UPF][Pfcp][10.200.200.101:8805] pfcp server stopped
18 packets captured
18 packets received by filter
0 packets dropped by kernel
1436 packets captured
2872 packets received by filter
0 packets dropped by kernel
2023-03-16T13:47:06+09:00 [INFO][UPF][Buff] buff server stopped
2023-03-16T13:47:06+09:00 [INFO][UPF][Main] Terminating UPF...
2023-03-16T13:47:06+09:00 [INFO][UPF][Main] UPF terminated
2023-03-16T13:47:06+09:00 [INFO][UPF][Main] UPF exited
nishi@GTP-U:~/free5gc-deb/free5gc$

Patch is here
diff --git a/test/consumerTestdata/UDR/TestRegistrationProcedure/RegistrationProcedure.go b/test/consumerTestdata/UDR/TestRegistrationProcedure/RegistrationProcedure.go
index 4851b94..2c34a4b 100644
--- a/test/consumerTestdata/UDR/TestRegistrationProcedure/RegistrationProcedure.go
+++ b/test/consumerTestdata/UDR/TestRegistrationProcedure/RegistrationProcedure.go
@@ -23,7 +23,7 @@ func init() {
 			DefaultSingleNssais: []models.Snssai{
 				{
 					Sst: 1,
-					Sd:  "010203",
+					Sd:  "FEDCBA",
 				},
 				{
 					Sst: 1,
@@ -33,7 +33,7 @@ func init() {
 			SingleNssais: []models.Snssai{
 				{
 					Sst: 1,
-					Sd:  "010203",
+					Sd:  "FEDCBA",
 				},
 				{
 					Sst: 1,
@@ -49,7 +49,7 @@ func init() {

 	TestSmfSelDataTable[FREE5GC_CASE] = models.SmfSelectionSubscriptionData{
 		SubscribedSnssaiInfos: map[string]models.SnssaiInfo{
-			"01010203": { // sst:1, sd:010203
+			"01FEDCBA": { // sst:1, sd:FEDCBA
 				DnnInfos: []models.DnnInfo{
 					{
 						Dnn: "internet",
@@ -74,9 +74,9 @@ func init() {

 	TestSmPolicyDataTable[FREE5GC_CASE] = models.SmPolicyData{
 		SmPolicySnssaiData: map[string]models.SmPolicySnssaiData{
-			"01010203": {
+			"01FEDCBA": {
 				Snssai: &models.Snssai{
-					Sd:  "010203",
+					Sd:  "FEDCBA",
 					Sst: 1,
 				},
 				SmPolicyDnnData: map[string]models.SmPolicyDnnData{
@@ -103,7 +103,7 @@ func init() {
 		{
 			SingleNssai: &models.Snssai{
 				Sst: 1,
-				Sd:  "010203",
+				Sd:  "FEDCBA",
 			},
 			DnnConfigurations: map[string]models.DnnConfiguration{
 				"internet": {
diff --git a/test/ngapTestpacket/build.go b/test/ngapTestpacket/build.go
index c5ea31b..90a4423 100644
--- a/test/ngapTestpacket/build.go
+++ b/test/ngapTestpacket/build.go
@@ -90,7 +90,7 @@ func BuildNGSetupRequest() (pdu ngapType.NGAPPDU) {
 	sliceSupportItem.SNSSAI.SST.Value = aper.OctetString("\x01")
 	// optional
 	sliceSupportItem.SNSSAI.SD = new(ngapType.SD)
-	sliceSupportItem.SNSSAI.SD.Value = aper.OctetString("\x01\x02\x03")
+	sliceSupportItem.SNSSAI.SD.Value = aper.OctetString("\xfe\xdc\xba")

 	sliceSupportList.List = append(sliceSupportList.List, sliceSupportItem)

diff --git a/test/ngsetup_test.go b/test/ngsetup_test.go
index 9b8e1db..d9429f4 100644
--- a/test/ngsetup_test.go
+++ b/test/ngsetup_test.go
@@ -322,7 +322,7 @@ func amfConfig(testID string) error {
 				},
 				SNssaiList: []models.Snssai{{
 					Sst: 1,
-					Sd:  "010203",
+					Sd:  "fedcba",
 				}, {
 					Sst: 1,
 					Sd:  "112233",
@@ -446,7 +446,7 @@ func smfConfig(testID string) error {
 			SNssaiInfo: []smf_factory.SnssaiInfoItem{{
 				SNssai: &models.Snssai{
 					Sst: 1,
-					Sd:  "010203",
+					Sd:  "fedcba",
 				},
 				DnnInfos: []smf_factory.SnssaiDnnInfoItem{{
 					Dnn: "internet",
@@ -491,7 +491,7 @@ func smfConfig(testID string) error {
 						SNssaiInfos: []smf_factory.SnssaiUpfInfoItem{{
 							SNssai: &models.Snssai{
 								Sst: 1,
-								Sd:  "010203",
+								Sd:  "fedcba",
 							},
 							DnnUpfInfoList: []smf_factory.DnnUpfInfoItem{{
 								Dnn: "internet",
@@ -846,7 +846,7 @@ func nssfConfig() error {
 				},
 				SupportedSnssaiList: []models.Snssai{{
 					Sst: 1,
-					Sd:  "010203",
+					Sd:  "fedcba",
 				}, {
 					Sst: 1,
 					Sd:  "112233",
@@ -919,7 +919,7 @@ func nssfConfig() error {
 			}, {
 				Snssai: &models.Snssai{
 					Sst: 1,
-					Sd:  "010203",
+					Sd:  "fedcba",
 				},
 				NsiInformationList: []models.NsiInformation{{
 					NrfId: "http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances",
diff --git a/test/registration_test.go b/test/registration_test.go
index 19a75ef..7dd7f7f 100644
--- a/test/registration_test.go
+++ b/test/registration_test.go
@@ -200,7 +200,7 @@ func TestRegistration(t *testing.T) {

 	sNssai := models.Snssai{
 		Sst: 1,
-		Sd:  "010203",
+		Sd:  "fedcba",
 	}
 	pdu = nasTestpacket.GetUlNasTransport_PduSessionEstablishmentRequest(10, nasMessage.ULNASTransportRequestTypeInitialRequest, "internet", &sNssai)
 	pdu, err = test.EncodeNasPduWithSecurity(ue, pdu, nas.SecurityHeaderTypeIntegrityProtectedAndCiphered, true, false)

Hi @ShouheiNishi
Could you please help to create the pull request for this patch?
Thanks.

Hi @ShouheiNishi
Could you please help to create the pull request for this patch?
Thanks.

We created https://github.com/free5gc/free5gc/pull/437.

Hi @ShouheiNishi , can you test this on v3.3.0 and show the log please?
Make sure your ubuntu version, linux kernel version and go version comply to the ones specificed on free5gc.org.

@ShouheiNishi
We are going to sync all sd value to lower case and use strings.EqualFold() to compare 2 sd value. Please wait for the PR of amf, smf, nssf . Now we have finished the webconsole and udr is in PR request.


text:
Turn an Image into a Link . I am stuck!

Challenge Turn an Image into a Link has an issue.
User Agent is: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

<link href="https://fonts.googleapis.com/css?family=Lobster" rel="stylesheet" type="text/css">

CatPhotoApp

Click here for cat photos.

Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.

Purr jump eat the grass rip the couch scratched sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip scratched.

Your code is not right.
You should turn the existing image to a link. Instead you have created a new image element( last line) and turned that into a link.
Make sure you visit help room, for further assistance regarding this issue.

@radq83
Thanks for reporting this. But your code is incorrect.
GitHub Issues are for reporting bugs on the website only.
Please use the Help chat room for getting challenge related help.
Happy Coding.

repo: freeCodeCamp/freeCodeCamp


text:
Lesson: ES6: Write Arrow Functions with Parameters - allows pass with incorrect code

Describe your problem and how to reproduce it:
The lesson on page will allow the user to pass the test using the following answer;
const myConcat = (arr1, arr2) => arr1.push(arr2);
console.log(myConcat([1, 2], [3, 4, 5]));
And the console below displays "3"
Further testing reveals it will also pass with the following code;
const myConcat = () => {};
console.log(3);
*The HINT answer also advises to use the .concat method, which likely hasn't been presented to the user before.
Add a Link to the page with the problem:
https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures/es6/write-arrow-functions-with-parameters
Tell us about your browser and operating system:

Browser Name: Firefox
Browser Version: 77.0.1 (64-bit)
Operating System: Linux Mint 19.3 Tricia

If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):

Confirmed. It you really want to go crazy and break the thing, even this is accepted:
const myConcat = eval("(func"+"tion(){})");

I think this is the culprit:
  - text: myConcat() should return [1, 2, 3, 4, 5].
    testString: assert(() => { const a = myConcat([1], [2]); return a[0] == 1 && a[1] == 2; });

That assert passes no matter what. If it's changed to
  - text: myConcat([1, 2], [3, 4, 5]) should return [1, 2, 3, 4, 5].
    testString:  assert.deepEqual(myConcat([1, 2], [3, 4, 5]), [1, 2, 3, 4, 5]);

it should be fine.  @Teredell @bjorno43 seem reasonable?  If you think so, I'll open this up for first-timers.

@ojeytonwilliams Yup. Seems fine to me. Go ahead and give it to first-timers.

Hey,
I'm a beginner and wanted to do this can you please help me.
Thank You.

Hey,
I'm a beginner and wanted to do this can you please help me.
Thank You.

if you want to contribute, you should start with the contributing docs, and if need help you are welcome to ask in the gitter contributors room, discord channel or contributors subforum on the forum

@rajatgupta24 we'd like to reserve this for first time contributors for a bit.  If none of them takes it, we'll open it up to the rest of the community.

@ojeytonwilliams sure 😊.

Is this issue still open?

@faraz16iqbal : the issue is still open, but someone is working on it, there is the status: fix in progress label to say that

Hey!
I am new too. As I was reading the comments I saw you have a discord channel as well. However unfortunately I can't find your server room there? Can I join?
Thanks!

Look at this article for the discord channel:
https://www.freecodecamp.org/news/freecodecamp-discord-chat-room-server/amp/
Il giorno mar 14 lug 2020 alle 14:46 Anjali Chaturvedi <
notifications@github.com> ha scritto:

Hey!
I am new too. As I was reading the comments I saw you have a discord
channel as well. However unfortunately I can't find your server room there?
Can I join?
Thanks!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/freeCodeCamp/freeCodeCamp/issues/39049#issuecomment-658158517,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGLL4HBOF724V3QTGUBEHM3R3RHR3ANCNFSM4N3II55Q
.

Hey I am looking for an issue to make a first contribution to and I stumbled upon this one! It seems like someone is working on this issue, but I don't see any updates since Jul 14.
Is someone still working on this issue?

@bkbranden The current PR does resolve the current issue. So, I suggest you look for another issue to work on with the help wanted label. Thank you, for your interest.

Is it still open? I'd like to contribute to it.


text:
Test a For loop doesn't work using short syntax.

Describe your problem and how to reproduce it:
Test a For loop doesn't work using short syntax.
If we got this code:
for(let user in usersObj) usersObj[user].online ? ++count : null;
The tests fail, but it works if we use the brackets syntax for the loop:
for(let user in usersObj){usersObj[user].online ? ++count : null};
Add a Link to the page with the problem:
https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures/basic-data-structures/iterate-through-the-keys-of-an-object-with-a-for---in-statement
Tell us about your browser and operating system:

Browser Name: Chrome
Browser Version:  87
Operating System: Windows 10

  - text: The function countOnline should use a `for in` statement to iterate through the object keys of the object passed to it.
    testString: assert(code.match(/for\s*\(\s*(var|let|const)\s+[a-zA-Z_$]\w*\s+in\s+[a-zA-Z_$]\w*\s*\)\s*{/));

The test for this challenge specifically looks for the opening curly brace. This could be adjusted, but then I'd worry about the test erroneously passing for code that does not work.

Yes, I also check the associated .md file.
I think the regex can be redefined to allow the non curly braces condition
if the loop hasn't a newline character. But I don't know the implications
of this on other tests.
El sáb., 21 de nov. de 2020 19:13, nhcarrigan notifications@github.com
escribió:

text: The function countOnline should use a for in statement to iterate through the object keys of the object passed to it.
testString: assert(code.match(/for\s*(\s*(var|let|const)\s+[a-zA-Z_$]\w*\s+in\s+[a-zA-Z_$]\w*\s*)\s*{/));

The test for this challenge specifically looks for the opening curly
brace. This could be adjusted, but then I'd worry about the test
erroneously passing for code that does not work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/freeCodeCamp/freeCodeCamp/issues/40277#issuecomment-731644366,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOP3X76DFMSEY4ZH7XDBL33SRA3O3ANCNFSM4T6BM3EA
.

How about looking for the curly brace and looking for the ; character at most 2 times ? (one for the instruction after the for loop and one for the return statement)

@nhcarrigan I will see it better later and try to test  alternatives, but I think if we remove the curly brace on the regex, we don't change the important stuff of the expression. In fact, the regex only tests if there is an opening curly brace, not the closing one, so isn't it for syntax review either. The point here is to test the good syntax of the For In expression, so maybe it's unnecessary.
Please correct me if I'm wrong.

authors: Ismailtlem JeremasPosta nhcarrigan


text:
Add a test bypass mode in development

Testing challenges in development can be tough. I propose a TEST_BYPASS_MODE we can use in development to make the challenges always pass the tests.

Are you proposing just a flag to ignore all tests? Or, the ability to submit without passing?
Or, something more like AUTOMATICALLY_ADD_EXPECTED_SOLUTION_MODE?

Either way would work. Ignore the tests was what I had in mind and would probably quite easy to implement.


text:
(JavaScript Course) Learn Form Validation by Calorie Counter, Step 47, 66-75 and probably more.

Describe the Issue
I forgot to put a semicolon when declaring a variable in Step 66, which should have produced a syntax error, however the test passed. Then I tried to make the same syntax error in steps 67-75, but they also all passed. Then I tried the same error in step 47, but it also passed. So, I'm not sure how many, or if all of the steps in the challenge can't detect this syntax error. I stopped tracking them down after testing step 47, since it was slowing my course progress.
Affected Page
Step 47, 67-75
Your code
Sorry, too lazy to write them all down. Please just check for yourself. :)

Expected behavior
Program did not detect syntax error.
Screenshots
No response
System

Device: [e.g. iPhone 6, Laptop]
OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04]
Browser: [e.g. Chrome, Safari]
Version: [e.g. 22]

Additional context
No response

Hey @Rods10
Thank you for opening this issue.
In JavaScript semicolon can be often omitted, that's not a syntax error. Because of that I'm going to close the issue.
If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding.


text:
Update Intro to Semantic Tags

Clarify what semantic and non-semantic tags are. Provide examples of each.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thanks @mdowis and congrats on your first contribution! 👍 👻

authors: joshalling mdowis


text:
Added relevant Medium FCC Article

[ x] I have read freeCodeCamp's contribution guidelines.
[x ] My pull request has a descriptive title (not a vague title like Update index.md)
[ x] My pull request targets the master branch of freeCodeCamp.
[ x] None of my changes are plagiarized from another source without proper attribution.
[ x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@galwaybeard Thanks for this pull request (PR).
Unfortunately, we are marking this PR invalid for hacktoberfest. We believe it does not follow the recommended guidelines:

Quality Standards
In line with Hacktoberfest value #2 (Quantity is fun, Quality is key), we have provided examples of the quality >standards we encourage. This applies mainly to beginners.

PRs that are automated e.g. scripted opening PRs to remove whitespace / optimize images.
PRs that are disruptive e.g. taking someone else's branch/commits and making a PR.
PRs that are regarded by a project maintainer as a hindrance vs. helping.
Something that's clearly an attempt to simply +1 your PR count for October.

Learn more at https://hacktoberfest.digitalocean.com/details

authors: galwaybeard nikrb


text:
Update russian translation

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

This PR was closed and then re-opened in an attempt to clear a specific Travis build failure

authors: corpsepk greggubarev


text:
add align properties and code samples

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Congrats @marcosetm on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝

authors: RandellDawson marcosetm


text:
fixed spelling craftsmanship

[x ] I have read freeCodeCamp's contribution guidelines.
[ x] My pull request has a descriptive title (not a vague title like Update index.md)
[ x] My pull request targets the master branch of freeCodeCamp.
[ x] None of my changes are plagiarized from another source without proper attribution.
[ x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@Recelis Good eye!

authors: Recelis paulywill


text:
Fix/minor issues

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.

Not related to this PR but I see, two footers on the profile page for some reason. Maybe due to merging a recent PR. If it's all the same, can you take a look and fix it in this one?

@raisedadead I don't believe this is a real bug, just an artifact of Gatsby's way of showing 404s in development.  It should be fine once the site has been built.
Here's what it looks like when I go to a non-existent page, donate/asgasdg, after running

npm run develop

and the same page after going to client and running
npm run build
node node_modules/gatsby-cli/lib/index serve

You get the same behaviour for pages like not-a-user, too.
Development 404 pages on the guide really show what's going on:

Again this goes away once you build.
These screenshots are of the current master.

Okay, thanks for confirming that @ojeytonwilliams I have merged this and will see how this behaves in the staging environment, that I am working hard to bring forward soon.

authors: ValeraS ojeytonwilliams raisedadead