adding python-click for xenial

Debian starting with stretch: https://packages.debian.org/stretch/python-click
Ubuntu starting with xenial only: http://packages.ubuntu.com/xenial/python-click
Fedora: https://admin.fedoraproject.org/pkgdb/package/rpms/python-click/
Are you hoping to package against this in Kinetic? If so because of the missing Wily version it might make sense to do the same as #12344 instead of this.

Oh I didn't realise that missing willy would mean we need a kinetic
package...
I am in the process of releasing a bunch of packages for indigo and jade
now. I jist do the rosdep keys while I am at it.
I ll get a look at kinetic after that then...
On Aug 13, 2016 2:35 AM, "Tully Foote"<EMAIL_ADDRESS>wrote:

Debian starting with stretch: https://packages.debian.org/
stretch/python-click
Ubuntu starting with xenial only: http://packages.ubuntu.com/
xenial/python-click
Fedora: https://admin.fedoraproject.org/pkgdb/package/rpms/python-click/
Are you hoping to package against this in Kinetic? If so because of the
missing Wily version it might make sense to do the same as #12344
https://github.com/ros/rosdistro/pull/12344 instead of this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ros/rosdistro/pull/12343#issuecomment-239510421, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AANgSF1Dnpm1_Mk32GXNedj_xyHqrBbJks5qfK7QgaJpZM4Ji1Zi
.

It makes sense to do a third party release for kinetic.
But it also makes sense to have it in rosdep, so that :

we can support different version than system version if needed
in any ROS package using it, we can quickly switch from the thirdparty package dependency to the system package dependency. So we can stop maintaining a release repo as soon as it is no longer necessary.

Actually thinking about this, we probably want the rosdep key for pip being different, like having a -pip suffix no ? But that would mean changing the meaning of that python-click rosdep key...
I am not quite sure about the status of rosdep pip support, or the extent to which we want to support it... Is there any reference documentation about this ?
Should I define all distros for that python-click key, and declare a pip entry in each of them ? seems to be unneeded redundancy...

There's not a strict policy. Most things are on a case by case basis and our best practices are evoloving. The use of the -pip extension we've started doing more recently than the original python-click entry. If it was to come in now we'd request it to be done differently. However, since it's already there we'd rather not change it. Using the pip rule for the older versions and the debian for the newer is probably the best path forward. Eventually the pip rules can be phased out once the older platforms are EOL.

+1

Is this key used for any Indigo package? If yes, it should have Saucy and Utopic entries, too.

Not that I can think of... but how can I be sure ? I there a way to check
all package's package.xml for a distro (without installing them) ?
On Aug 17, 2016 10:47 PM, "Dirk Thomas"<EMAIL_ADDRESS>wrote:

Is this key used for any Indigo package? If yes, it should have Saucy and
Utopic entries, too.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ros/rosdistro/pull/12343#issuecomment-240416002, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AANgSKhMjdvjOoM-n2dDAsj8_la8gkG5ks5qgxDYgaJpZM4Ji1Zi
.

Unfortuantely there's no good way to search, especially as there's potentially an unknown number of private repos which cannot be searched.
There is an alternative to use the indigo packaged version: https://github.com/ros/rosdistro/pull/12344/files but it appears to be not building on saucy due to catkin_pip not building due to too low a version of pip.
It's EOL, but we might as well add the rule for Saucy and Utopic and move on. Hopefully we'll develop a deprecation/removal process for rosdeps in the future.

Moving on then... this should be good to merge now.

+1 thanks for the iterations

Coming back to this topic after I am trying to release a package that depend on it, for indigo and jade.
I have this package.xml : https://github.com/asmodehn/rostful/blob/python_mutate/package.xml#L21
that declares a dependency on "click".
This currently resolves to a third party package that I released here : https://github.com/asmodehn/click-rosrelease. I am going to release on kinetic a third party package soon, because wily doesn't have it, so it is needed (wily is already EOL btw...)
To release this package on future (kinetic++) ROS releases (or even on kinetic in case of xenial platform) I want to switch to use the system package and not the third party ROS released package anymore. What is the best way to do this ?

I cannot have a second package.xml declaring a different set of dependencies for kinetic++ without having to maintain multiple development branches.
I could create a patch for kinetic++, but that means a user getting the source might get dependency problems (rosdep trying to resolve "click" from the unpatched package.xml from source)
I could create a third party release for kinetic++, but I would duplicate the system dependency without a proper reason (the system version already matches my requirements), and that may create problems (two similar package with 2 different build process - we don't want to duplicate all debs in main|universe|multiverse).
I cannot declare a "click" package for rosdep without duplicating the entry for the same package (unless there is an "alias" function in rosdep I am not aware of ?)

I am thinking the best way would be arguments in package.xml format, but I couldn't find any for this purpose...
Thanks for the advice !

When you switch to the system dependency the rosdep rule name should be different from the ROS package. Usually 'click' becomes 'libclick-dev' for c++ or 'python-click' for python packages. Trying to use the same name almost always ends up with.
The recommendation is to fork your repo and if you maintain things in parallel, cherry-picking things to the parallel development branches isn't too hard.
If the package is available upstream it's strongly recommended not to also release it as a ros package due to potential conflicts.

OK I ll go with multiple branches in my repos then. I kept the names different (removed the "python-" prefix) so things should be fine (albeit a bit cumbersome).
Just a small comment about
If the package is available upstream it's strongly recommended not to also release it as a ros package due to potential conflicts.
Agreed but packages on old distros are sometimes too old to be used.
And when people need an update they go the simplest way and we end up with something worse : a package installing another one without warning, like this : https://github.com/RobotWebTools/rosbridge_suite/issues/162. I would be surprised if it was an isolated case, but afaik the buildfarm does not check for this...
So I think it would be very useful to have an easy way to specify distributions in dependency declaration in package.xml. It would allow users to use an alternative third party version for specific distros whenever needed, and use upstream system package whenever possible.

Yeah, there are lots of things that could be added to the package.xml. We spent a lot of time stabilizing the current version and and making it as simple as possible. If you'd like to propose an extension we can look at it. But in the end it's going to be a balance between adding complexity to support this use case vs making the whole system more complex for everyone.


The author is still Charles Zipp

Hello, I have no idea if it is intentional but the Author is still Charles Zipp.
Is it ok like that or am I doing something wrong?

I left that because Charles is the author.  I am now the maintainer but I didn't write the code.


I had difficulties connecting to the buyer portal when I tried to deploy the application locally.

Type: Bug Report
Summary:
I had difficulties connecting to the buyer portal when I tried to deploy the application locally.
Issue report or feature request:
Configuration I added:

added the scripts to the header and footer in the stencil theme locally  (the same as provided in the documentation)
changed the env file: here is the question about app_client _d, I use

VITE_B2B_CLIENT_ID=dl7c39mdpul6hyc489yk0vzxl6jesyx
This ID is provided by the b2b edition doc (https://developers.bundleb2b.com/docs/openapi/auth). Please let me know if I need another one, and if so how to get it.
VITE_STORE_HASH="zpaqzjvja6"
This is the store hash of my store.
I don't know the absolute path, and if it is needed for local development. (I run yarn prod build and set the path to the dist folder)
VITE_ASSETS_ABSOLUTE_PATH="http://localhost:3001/apps/storefront/dist/assets"
The issue I had.

I run stencil locally on port 4000
I run the buyer portal locally on port 3001
I click on the account page in Stencil and get an infinite loading of the page and some errors like:

So I see that the storefront is connected to the buyer portal but there is some misconfiguration.
Please let me know if there is some mistake in the configuration and provide more detailed instructions on how to connect these to apps.

Hello @iyarovoy-igor
We have created a PR to updated the setup guide, please read the new changes on this PR

Hi @iyarovoy-igor
Is there any update on this? We have already updated the setup guide, it will help use a lot your feedback

Hi!
I apologize for the long response.
I will be able to setup the application on Monday.
Thank you for your help.
On Fri, Jun 14, 2024 at 10:32 PM Marco Loyo @.***>
wrote:

Hi @iyarovoy-igor https://github.com/iyarovoy-igor
Is there any update on this? We have already updated the setup guide, it
will help use a lot your feedback
—
Reply to this email directly, view it on GitHub
https://github.com/bigcommerce/b2b-buyer-portal/issues/25#issuecomment-2168638722,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A55B7FJRQHMX7YCTEY56CP3ZHNALFAVCNFSM6AAAAABI4Q25YCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRYGYZTQNZSGI
.
You are receiving this because you were mentioned.Message ID:
@.***>

@bc-marco Hi!
Using the new setup guide, I was able to run the app locally.
Thank you!

Hi!
Using the new setup guide, I was able to run the app locally.
Thank you!
On Sat, Jun 15, 2024 at 2:33 PM Igor Yarovoy @.***>
wrote:

Hi!
I apologize for the long response.
I will be able to setup the application on Monday.
Thank you for your help.
On Fri, Jun 14, 2024 at 10:32 PM Marco Loyo @.***>
wrote:

Hi @iyarovoy-igor https://github.com/iyarovoy-igor
Is there any update on this? We have already updated the setup guide, it
will help use a lot your feedback
—
Reply to this email directly, view it on GitHub
https://github.com/bigcommerce/b2b-buyer-portal/issues/25#issuecomment-2168638722,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A55B7FJRQHMX7YCTEY56CP3ZHNALFAVCNFSM6AAAAABI4Q25YCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRYGYZTQNZSGI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Excellent!
Closing this issue as is not longer present


Change latest image from first to last

Description
Changes the latest image from first to last to match the api order
Type of change
What is it?

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] I run npm run lint:js:fix to check that my code is properly formatted

Codecov Report

Merging #258 (dfccb9e) into master (7d01838) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #258   +/-   ##
=======================================
  Coverage   32.31%   32.31%
=======================================
  Files         101      101
  Lines        1993     1993
  Branches      578      578
=======================================
  Hits          644      644
  Misses       1240     1240
  Partials      109      109

Impacted Files
Coverage Δ

src/Routes/ImageManager/ImageSetsTable.js
70.00% <ø> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7d01838...dfccb9e. Read the comment docs.


check_install_release failed when upgrading

Hi @bitwalker,
thanks for your project, I've been trying it out for the last couple days and it looks very promising. I managed to deploy my application very easily.
I've had a few problems though when performing an upgrade. The last one is quite surprising. Basically it seems that the new release does not get unpacked.
I'm running it exactly as in upgrade documentation, and here's the result I get:
Using /home/deploy/apps/my_app/releases/0.0.1/my_app.sh
Release 0.0.2 is already unpacked, now installing.
Generating vm.args/sys.config for upgrade...
cp: cannot stat ‘/home/deploy/apps/my_app/releases/0.0.2/sys.config’: No such file or directory
sys.config ready!
cp: cannot stat ‘/home/deploy/apps/my_app/releases/0.0.2/vm.args’: No such file or directory
vm.args ready!
Release 0.0.2 is already unpacked, now installing.
ERROR: release_handler:check_install_release failed: {no_such_file,
                                                      "/home/deploy/apps/my_app/releases/0.0.2/start.boot"}

When I enter the releases/0.0.2 directory, I see there only my_app.tar.gz and vm.args files.
I'll try to provide a sample app that reproduces this issue later today, but if anyone already knows why this might be happening, I'll be grateful for any help.
I'm using Elixir 1.2.0 on Erlang/OTP18 with Exrm 1.0.0-rc7

It seems that I caused the problem by messing with releases numbers. At some point I couldn't make upgrade working and I decided to remove all the releases and go back to 0.0.1
I removed all the directories, but then running bin/my_app upgrade 1000.0.0 showed that release 0.0.2 already exists and is unpacked, even though I had removed all the directories.
So I think my issue is reduced to a question - where are the information about releases stored except for rel directory in the main repo and releases in the build dir?

@arnvald Sorry for the long delay :(
The file which tracks which releases are installed is releases/RELEASES, and releases/start_erl.data tracks the current release version and ERTS version. I would recommend that if you are going to start from scratch with a release that you blow away the entire deploy directory, but that's not strictly necessary - just safest. There are some caveats around versioning and building release upgrades.

Versions must be greater than the last version (i.e. 0.0.1 -> 0.0.2)
Upgrades which are built against a specific version, this is significant because if for example you are building a release for 0.0.4 and the last release on your build machine was 0.0.2, but the current deployed version is 0.0.3 because someone else built the last upgrade package, means that you can't install 0.0.4 without first downgrading to 0.0.2 and then upgrading to 0.0.4. This is because the relup instructions which tell your application how to upgrade itself are specific to the code in the version it's built against.
If you want to build upgrades, you have to have the last release around, if you blow away the rel directory on your build machine, it won't be possible to build an upgrade anymore (you'd have to deply the new version of the app with a full restart, and build upgrades starting from that release).

This should all be in the documentation, but just as a quick recap of the key points :)


I have a problem about dependency and tree in zipkin UI

I have get rest and mq span,then report the span to zipkin,but it's not show dependency in zipkin UI and show tree no serviceName

[
	{
		"traceId": "633871a0ff544636",
		"id": "633871a0ff544636",
		"name": "get",
		"timestamp":<PHONE_NUMBER>941000,
		"duration": 143838,
		"annotations": [
			{
				"timestamp":<PHONE_NUMBER>941000,
				"value": "sr",
				"endpoint": {
					"serviceName": "service2",
					"ipv4": "<IP_ADDRESS>"
				}
			}, {
				"timestamp":<PHONE_NUMBER>084838,
				"value": "ss",
				"endpoint": {
					"serviceName": "service2",
					"ipv4": "<IP_ADDRESS>"
				}
			}
		],
		"binaryAnnotations": [
			{
				"key": "http.status_code",
				"value": "200",
				"endpoint": {
					"serviceName": "service2",
					"ipv4": "<IP_ADDRESS>"
				}
			}, {
				"key": "http.url",
				"value": "/foo",
				"endpoint": {
					"serviceName": "service2",
					"ipv4": "<IP_ADDRESS>"
				}
			}
		]
	}, {
		"traceId": "633871a0ff544636",
		"id": "b204e6cdd4bc2b3a",
		"name": "get",
		"parentId": "633871a0ff544636",
		"timestamp":<PHONE_NUMBER>045000,
		"duration": 123456,
		"annotations": [
			{
				"timestamp":<PHONE_NUMBER>045000,
				"value": "ms",
				"endpoint": {
					"serviceName": "mq",
					"ipv4": "<IP_ADDRESS>"
				}
			}
		],
		"binaryAnnotations": [
			{
				"key": "mq",
				"value": "send message",
				"endpoint": {
					"serviceName": "mq",
					"ipv4": "<IP_ADDRESS>"
				}
			}
		]
	}
]

"ms" would have the endpoint of the local process, not the remote broker
(unless you've somehow implemented the broker
The messaging address("ma") will look exactly the same as how we handle the
server address ("sa")
"binaryAnnotations": [
{
"key": "ma",
"value": true,
"endpoint": {
"serviceName": "mq",
"ipv4": "<IP_ADDRESS>"
}
}
]
there has been no code for messaging span, yet. so please only
experiment with annotations how they are described in the below pull
request, but don't depend on it or expect any server changes until
they are merged. https://github.com/openzipkin/zipkin-api/pull/24

@adriancole Thank you,I will change the annotations,but why is black the serviceName in zipkin UI

the UI interprets certain annotations. best to start with the correct
usage, then if it is a still problem, ping back (don't expect the messaging
ones to turn out right since the UI doesn't know about that yet)
On Fri, Dec 16, 2016 at 1:50 PM, lijunyong<EMAIL_ADDRESS>wrote:

@adriancole https://github.com/adriancole Thank you,I will change the
annotations,but why is black the serviceName in zipkin UI
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openzipkin/zipkin/issues/1439#issuecomment-267522382,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAD615tUGx_Re-xxfKfUmlNpEhoXK-Euks5rIiaKgaJpZM4LOzjY
.

Thank you,when support 'ms','ma','mr' in zipkin UI

Thank you,when support 'ms','ma','mr' in zipkin UI

the pull request about those annotations has some discussion on it. We
shouldn't add UI until ppl are cool. Once it is merged, it would be very
easy to add to UI. (like days)

@adriancole thank you very much, very nice

if you use the "cs" "sr" practice of one-way spans, the UI should work properly, now. Here's an example https://github.com/openzipkin/brave/tree/master/brave/src/test/java/brave/features/async
I don't expect us to continue with "ms" "mr"


Add multiple endpoints support

It uses the new dogapi feature to do so.
Tests are failing because the new dogapi gem with multiple endpoints
support is not yet released.

Looks good! Let's make the tests pass once the new dogapi gem is released :)
I've found a couple of other places that'll need an update too:

handling of response(s) when posting events: https://github.com/DataDog/chef-handler-datadog/blob/v0.9.0/lib/chef/handler/datadog_chef_events.rb#L73-L94
handling of response(s) and retries when on tags' updates: https://github.com/DataDog/chef-handler-datadog/blob/v0.9.0/lib/chef/handler/datadog_chef_tags.rb#L93-L111

Also, let's not forget to update the version constraint on dogapi since we'll need the new version: https://github.com/DataDog/chef-handler-datadog/blob/master/chef-handler-datadog.gemspec#L17

Looks good to me, and well tested 💚 .

Let's merge this once the tests pass! 🎆

@degemer Could you also rebase the PR please?
All the other code changes that'll ship with the next minor release have been merged to master.

Yay, rebased, fixed the nits, finally ready to 🚀  ! Last review @olivielpeau ?

@degemer Let's rename validate_extra_endpoints, otherwise this looks ready to 🚢

Humpf, I know why I forgot it, but this is vexing. 🔥

Had 2 more comments for your consideration, apart from that I think we're getting there :)

Thanks for the review, updated the PR!

LGTM! Let's merge once https://github.com/DataDog/chef-datadog/pull/317 is ready too


feedback

great job overall, just two things...

add a description and tags, specifically add the ibmcode tag:

Step 1 (https://github.com/IBM/run-campaigns-target-customers/blob/master/README.md#1-sign-up-for-watson-studio) -- a spark service is no longer created automatically, please remove that.

Closed via https://github.com/IBM/run-campaigns-target-customers/commit/e6327c85d0231600523c81b5d51e47037a7e3f23
@balajikadambi please create a PR instead of pushing to master when closing a bug. I'm happy to review :)


Pipx unaware of uninstalled Python

Describe the bug
I had python and "pipx:httpie" installed with mise. After uninstalling Python, the executable httpie still links to the removed python interpreter.
To Reproduce
[tools]
python = "latest"
"pipx:*any tool*" = "latest"

Run mise i.
Then remove python="latest" and run mise prune.
Expected behavior
When uninstalling a python version or doing a mise upgrade, detect and reinstall affected tools;
Report such breaks in mise doctor
mise doctor output
version: 2024.11.23 linux-x64 (1980-01-01)
activated: no
shims_on_path: yes

build_info:
  Target: x86_64-unknown-linux-gnu
  Features: DEFAULT, NATIVE_TLS
  Built: Tue, 1 Jan 1980 00:00:00 +0000
  Rust Version: rustc 1.82.0 (f6e511eec 2024-10-15)
  Profile: release

shell:
  /bin/zsh
  zsh 5.9 (x86_64-pc-linux-gnu)

dirs:
  cache: ~/.cache/mise
  config: ~/.config/mise
  data: ~/.local/share/mise
  shims: ~/.local/share/mise/shims
  state: ~/.local/state/mise

config_files:
  ~/.config/mise/config.toml

backends:
  aqua
  asdf
  cargo
  core
  go
  npm
  pipx
  spm
  ubi
  vfox

plugins:
  pipx    https://github.com/yozachar/asdf-pipx.git#31db618
  rust    https://github.com/code-lever/asdf-rust.git#95acf4f
  usage   https://github.com/jdx/mise-usage.git#fe3888a

toolset:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
env_vars:
  (none)

settings:
  activate_aggressive = false
  all_compile = false
  always_keep_download = false
  always_keep_install = false
  asdf_compat = false
  cache_prune_age = "30d"
  ci = false
  color = true
  debug = false
  disable_backends = []
  disable_default_registry = false
  disable_hints = []
  disable_tools = []
  experimental = true
  fetch_remote_versions_cache = "1h"
  fetch_remote_versions_timeout = "10s"
  go_default_packages_file = "~/.default-go-packages"
  go_download_mirror = "https://dl.google.com/go"
  go_repo = "https://github.com/golang/go"
  go_set_gopath = true
  go_set_goroot = true
  go_skip_checksum = false
  http_timeout = "30s"
  jobs = 4
  legacy_version_file = true
  legacy_version_file_disable_tools = []
  libgit2 = true
  lockfile = true
  log_level = "info"
  not_found_auto_install = true
  paranoid = false
  pin = false
  plugin_autoupdate_last_check_duration = "7d"
  profile = "test"
  quiet = false
  raw = false
  trace = false
  trusted_config_paths = []
  unix_default_file_shell_args = ["sh"]
  unix_default_inline_shell_args = [
      "sh",
      "-c",
  ]
  use_file_shell_for_executable_tasks = false
  use_versions_host = true
  verbose = false
  windows_default_file_shell_args = [
      "cmd",
      "/c",
  ]
  windows_default_inline_shell_args = [
      "cmd",
      "/c",
  ]
  windows_executable_extensions = [
      "exe",
      "bat",
      "cmd",
      "com",
      "ps1",
      "vbs",
  ]
  yes = false

  [cargo]
  binstall = true

  [node]

  [npm]
  bun = false

  [pipx]
  uvx = false

  [python]
  default_packages_file = "~/.default-python-packages"
  pyenv_repo = "https://github.com/pyenv/pyenv.git"
  venv_auto_create = false
  venv_stdlib = false

  [ruby]
  default_packages_file = "~/.default-gems"
  ruby_build_repo = "https://github.com/rbenv/ruby-build.git"
  ruby_install = false
  ruby_install_repo = "https://github.com/postmodern/ruby-install.git"

  [status]
  missing_tools = "if_other_versions_installed"
  show_env = false
  show_tools = false
No warnings found

that's just how pipx works

This could be an interesting feature request rather than a bug.
It would be nice to be able to use any language package manager backends (npm/pipx/cargo) without worrying if you have the correct tooling installed to download and run them.
I'm not sure if this would be considered dependency management as mentioned in the anti-goals


chore: switch from PGVECTOR to EDB

Since the "pgvector" only reflects the use of an extension we propose to use "EDB" since it's the EDB Postgres for Kubernetes operator the one used under the hood

Please resolve the conflict


[CONTINT-52] Add new e2e tests for checks of the K8s control plane components

What does this PR do?
Add new e2e tests to validate that checks for the Kubernetes control plane components are working fine:

kube_apiserver_metrics
kube_controller_manager
kube_scheduler

Motivation
Validate that the Kubernetes control plane components checks are properly auto-configured with their default configuration.
Additional Notes
This requires DataDog/test-infra-definitions#512.
Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

/merge


initial changes

Here are my initial changes to include the project report at middle of semester.

commit accepted


Error 502

Steps to Reproduce the Problem
I have ocelot 8.0.0 working, today i was trying to update to 8.0.1 and after running it in my workstation i got an 502 http errorcode.
I tried it in our development server too and got the same results.
Has something been changed between versions?
Specifications

Version: 8.0.1
Platform: Windows 8.1/2016
Subsystem: Core 2.1.2

@margaale yes their were changes, looks like GitHub hasn't picked them up correctly :( We added support for query string parameters in upstream path templates, added a way to setup your initial ocelot state from a folder with config files in it, added a way to branch the ocelot pipeline with your own middleware.
Can you share your json configuration and program.cs / startup.cs and I will take a look?

Thanks for your reposnse.
I just removed the domain form all urls in the config.
files.zip

Ok cool I will check it out asap.

@margaale which routes do you get 502 on? Is it all of them?

No, only the one not using oauth. It's pretty simple because we are just starting with microservices..

The other one I got 401. But I didn't fully test it passing the token

@margaale can you confirm the exact url you are using to call Ocelot?
Also would it be possible to paste the logs from Ocelot when your request fails here?

for debugging purposes...
https://ocelotperformancetest.azurewebsites.net/api/values - same problem, deployed latest version of Ocelot also same problem running locally on that URL.

@margaale please try new verison 8.0.2

I will as soon as I get to work. Thanks

Awesome thanks for bringing this to my attention.


Getting grpc error when running in docker for windows

Description
Getting the same issue as #1400 but creating a new issue as per request by @neha-viswanathan
Steps to reproduce the issue:

use amp 0.11.0 or 0.12.0-dev
create a new cluster amp -s localhost cluster create
try to deploy the pinger.yml
amp -s localhost stack deploy -c pinger.yml pinger

Deploying stack pinger using pinger.yml
transport: http2Client.notifyError got notified that the client transport was broken [read tcp <IP_ADDRESS>:65152-><IP_ADDRESS>:50101: wsarecv: An existing connection was forcibly closed by the remote host.].transport: http2Client.notifyError got notified that the client transport was broken [read tcp <IP_ADDRESS>:65153-><IP_ADDRESS>:50101: wsarecv: An existing connection was forcibly closed by the remote host.].Error: transport is closing

OR
try to create a user
amp -s localhost user signup
transport: http2Client.notifyError got notified that the client transport was broken [read tcp <IP_ADDRESS>:65074-><IP_ADDRESS>:50101: wsarecv: An existing connection was forcibly closed by the remote host.].transport: http2Client.notifyError got notified that the client transport was broken [read tcp <IP_ADDRESS>:65075-><IP_ADDRESS>:50101: wsarecv: An existing connection was forcibly closed by the remote host.].transport: http2Client.notifyError got notified that the client transport was broken [read tcp <IP_ADDRESS>:65076-><IP_ADDRESS>:50101: wsarecv: An existing connection was forcibly closed by the remote host.].Error: transport: write tcp <IP_ADDRESS>:65076-><IP_ADDRESS>:50101: use of closed network connection

Output of docker version:
$ docker version
Client:
 Version:      17.03.1-ce
 API version:  1.27
 Go version:   go1.7.5
 Git commit:   c6d412e
 Built:        Tue Mar 28 00:40:02 2017
 OS/Arch:      windows/amd64

Server:
 Version:      17.03.1-ce
 API version:  1.27 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   c6d412e
 Built:        Fri Mar 24 00:00:50 2017
 OS/Arch:      linux/amd64
 Experimental: true

Docker for Mac/Windows version, if applicable:
Version 17.03.1-ce-win12 (12058)

Output of amp version:
$ ./amp version
[cloud.appcelerator.io:50101]

Client:
 Version:       v0.12.0-dev
 Build:         056e5e9f
 Server:        cloud.appcelerator.io:50101
 Go version:    go1.8.1
 OS/Arch:       windows/amd64

Server:         not connected

@alasdairhurst this issue shouldn't happen anymore with the new release (and dev version), I'm gonna close the issue, if you see it again with 0.12, please reopen it.

@ndegory Yup it's all good now, thanks.


Certificates generation process gets killed

Hi,
I followed this tutorial and almost everything is working fine 😄. In general I see that the certificates are tried to be created but they fail. When I do this manually by running the renewal script I get this:
[root@ip-x-x-x-x ec2-user]# docker exec -it 0df6c255c4e8 /app/force_renew
/etc/nginx/certs/subdomain.domain.com /app
Creating/renewal subdomain.domain.com certificates... (subdomain.domain.com)
/app/letsencrypt_service: line 118:   184 Killed                  /usr/bin/simp_le -f account_key.json -f key.pem -f chain.pem -f fullchain.pem -f cert.pem $params_d_str --cert_key_size=$cert_keysize --server=$acme_ca_uri --default_root /usr/share/nginx/html/
/app

The directory with the certificates has the folder called subdomain.domain.com but it is empty, same as the other shared volumes used for the process like vhost.d and html.
Thx for any help here.

Hi. Were you able to troubleshoot and/or solve this?

Was it working before ? What version of the container are you using ? What OS, Docker and Docker Composer version are you using ? Can you share your compose file ?

a) Well it's a first time setup for this particular project but has been used in other projects in the exact same way.
b) latest
c) Linux, 18.04.0-ce, 1.21.1, build 5a3f1a3
d) yes: docker-compose-prod.yml.txt

I have no idea how memory_limit plays with this container.
Have you tried raising the limit ? Using docker stat and manually triggering /app/signal_le_service, I just saw memory usage slightly above 30 Mib.

Good hint. This particular server had swap disabled. That's why it didn't work here but in other projects with the same setup. Cheers mate!

@kaiokenx10 I suspect your issue has the same cause.

No update from issue creator, closing.


Build error - The Broccoli Plugin: [Funnel] failed with: ng serve on windows10

looking for help. I installed angular CLI and use ng new it works fine i think. Because i got files have been created. but after dive in folder for ng serve i got the following error.
I tried it on node 4.5.0 and not working too
Now I have this version and it is not working too :)
angular-cli: 1.0.0-beta.10
node: 6.3.1
npm :3.10.6
os: win32 ia32
anyone could help :) waiting for expert :+1:
// start of error
(node:6500) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
The Broccoli Plugin: [Funnel] failed with:
Error: EISDIR: illegal operation on a directory, symlink 'D:\training\angularjs2\helloworld\src' -> 'D:\training\angularjs2\helloworld\tmp\funnel-input_base_path-185X28Ag.tmp\0'
at Error (native)
at Object.fs.symlinkSync (fs.js:1054:18)
at symlinkWindows (D:\training\angularjs2\helloworld\node_modules\angular-cli\node_modules\symlink-or-copy\index.js:101:16)
at symlinkOrCopySync (D:\training\angularjs2\helloworld\node_modules\angular-cli\node_modules\symlink-or-copy\index.js:53:5)
at D:\training\angularjs2\helloworld\node_modules\angular-cli\node_modules\broccoli-plugin\read_compat.js:58:9
at lib$rsvp$$internal$$tryCatch (D:\training\angularjs2\helloworld\node_modules\angular-cli\node_modules\rsvp\dist\rsvp.js:1036:16)
at lib$rsvp$$internal$$invokeCallback (D:\training\angularjs2\helloworld\node_modules\angular-cli\node_modules\rsvp\dist\rsvp.js:1048:17)
at lib$rsvp$$internal$$publish (D:\training\angularjs2\helloworld\node_modules\angular-cli\node_modules\rsvp\dist\rsvp.js:1019:11)
at lib$rsvp$asap$$flush (D:\training\angularjs2\helloworld\node_modules\angular-cli\node_modules\rsvp\dist\rsvp.js:1198:9)
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickCallback (internal/process/next_tick.js:98:9)
The broccoli plugin was instantiated at:
at Funnel.Plugin (D:\training\angularjs2\helloworld\node_modules\angular-cli\node_modules\broccoli-plugin\index.js:10:31)
at new Funnel (D:\training\angularjs2\helloworld\node_modules\angular-cli\node_modules\broccoli-funnel\index.js:44:10)
at Angular2App._buildInputTree (D:\training\angularjs2\helloworld\node_modules\angular-cli\lib\broccoli\angular2-app.js:92:7)
at new Angular2App (D:\training\angularjs2\helloworld\node_modules\angular-cli\lib\broccoli\angular2-app.js:51:41)
at module.exports (D:\training\angularjs2\helloworld\angular-cli-build.js:10:10)
at Class.module.exports.Task.extend.setupBroccoliBuilder (D:\training\angularjs2\helloworld\node_modules\angular-cli\node_modules\ember-cli\lib\models\builder.js:55:19)
at Class.module.exports.Task.extend.init (D:\training\angularjs2\helloworld\node_modules\angular-cli\node_modules\ember-cli\lib\models\builder.js:89:10)
at new Class (D:\training\angularjs2\helloworld\node_modules\angular-cli\node_modules\core-object\core-object.js:18:12)
at Class.module.exports.Task.extend.run (D:\training\angularjs2\helloworld\node_modules\angular-cli\node_modules\ember-cli\lib\tasks\serve.js:15:19)
at D:\training\angularjs2\helloworld\node_modules\angular-cli\node_modules\ember-cli\lib\commands\serve.js:64:24
at lib$rsvp$$internal$$tryCatch (D:\training\angularjs2\helloworld\node_modules\angular-cli\node_modules\rsvp\dist\rsvp.js:1036:16)
at lib$rsvp$$internal$$invokeCallback (D:\training\angularjs2\helloworld\node_modules\angular-cli\node_modules\rsvp\dist\rsvp.js:1048:17)
at lib$rsvp$$internal$$publish (D:\training\angularjs2\helloworld\node_modules\angular-cli\node_modules\rsvp\dist\rsvp.js:1019:11)
at lib$rsvp$asap$$flush (D:\training\angularjs2\helloworld\node_modules\angular-cli\node_modules\rsvp\dist\rsvp.js:1198:9)
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickCallback (internal/process/next_tick.js:98:9)
and when i checked the version ng -v i got another error
"(node:6116) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
"

one more thing to add.
I am running CMD as administrator. and when I use ng new it takes a long time to create the project about 15 minutes. I just created a project to test the time and I got the following message which I don't know what does it mean ?
// start of message
Installing packages for tooling via npm
├── es6-shim (global)
├── angular-protractor (global dev)
├── jasmine (global dev)
└── selenium-webdriver (global dev)
// end of message

i'm getting the same issue as well, I've tried using the new Ubuntu integrated bash console for windows 10 as well the normal CMD as administrator  and get the same error

@Alshahranimohammed if you are using BashOnWindows then this is a dupe of https://github.com/angular/angular-cli/issues/1555, see the closing comment.
Otherwise, you seem to be having some symlink permissions issue. The webpack preview version does not use symlink so you might consider upgrading to that: https://github.com/angular/angular-cli#webpack-preview-release-update

@filipesilva thanks for the help. it works fine now no more build error. could you please help with the time ? i just create a project with ng new and it takes 20 minutes to finish !
any idea what is going on ?

ng new also does npm install, which locally installs angular-cli and it currently is a big package. See https://github.com/angular/angular-cli/issues/1263 for more information.
It shouldn't take 20 minutes though.... On my computer it takes some 2-3 minutes. The only think that comes to mind is internet speed.


Snapping in freeModeSticky with slide groups prefers previous slide

This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Swiper Version: 3.4.2 and 4.1.5

Platform/Target and Browser Versions: All

Live Link or JSFiddle/Codepen or website with isssue: https://codepen.io/lohfu/pen/oEWOrq.

What you did
See the linked codepen
Expected Behavior
When using slide groups, I would expect Swiper to snap to the next group if i have swiped more than half of the current group (even when not passing minimum velocity).
If using the mousewheel, i expect to stay at the end if i have scrolled to the end.
Actual Behavior
When swiping or scrolling you have to scroll over 80% of a slide group to go to the next one. Ie, in the codepen i linked i have to swiper past slide 4 to go the group that starts with slide 6.
If using the scroll wheel, it is not possible to get the swiper to stay in the last swipe group. If i scroll to the end, the swiper will snap back to the last full group when scrolling stops.
Is this the intended behaviour or am I missing an option to change the behaviour?

This is not the usecase. Result will be the same as just to disable freeMode, so just disable it in this case

@nolimits4web the problem is i want to be able to use the velocity option... ie in a swiper with many views/groups the user should be able to swipe with a high velocity and have the swiper page through many of the views/groups...

Fixed now


Reorganization of OpenFermion

New module structure
No functionality changes

Addresses #616

Odd that the MacOS test is segfaulting, but everything else is passing - any ideas?

@babbush this is the first and largest step of the reorg.  We are holding other PRs so this can get in and others can work off the new module structure.  A fast turn LGTM would be very helpful!


Metacontroller CRD's are in protected group

Thanks @fpetkovski for spotting,
metacontroller crd's are in group called metacontroller.k8s.io, which mean it is protected - https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/20190612-crd-group-protection.md#k8sio-group-protection
so we temporary need to add annotations marking it is unapproved - https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/20190612-crd-group-protection.md#what-to-do-if-you-accidentally-put-an-unapproved-api-in-a-protected-group - as in https://github.com/metacontroller/metacontroller/pull/53/
Final solution
Either we need to ask for approval https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/20190612-crd-group-protection.md#what-to-do-if-you-accidentally-put-an-unapproved-api-in-a-protected-group or we should change the group name.
I would firstly check if our api is approvable,and what requirements we need to met.

How about using metacontroller.github.com as the API group in the CRDs exposed in this project?
We can change the go mod to point this as well?
cc @grzesuav @fpetkovski

How about using metacontroller.github.io as the API group in the CRDs exposed in this project?

To be honest it will cause not compatible change for API. If it will be necessary we must provide seamless migration path which will not cause breaks in operations.

We can change the go.mod to point this as well?

Which part of go.mod you have in mind ?

I also have concerns that changing the API group will cause a backwards incompatible change and break existing users if not done carefully. The group field in the CRD spec is immutable, so a migration from existing users would need to include:

deploying a new version of metacontroller that watches *.metacontroller.github.io
applying CRDs with a new name in the metacontroller.github.io group
applying CompositeControllers and DecoratorControllers from the apiGroup metacontroller.github.io
removing CRDs from the old group.

Based on a basic investigation I think that it could be done without downtime, but it also involves taking some risks.

I also have concerns that changing the API group will cause a backwards incompatible change and break existing users if not done carefully. The group field in the CRD spec is immutable, so a migration from existing users would need to include:

deploying a new version of metacontroller that watches *.metacontroller.github.io
applying CRDs with a new name in the metacontroller.github.io group
applying CompositeControllers and DecoratorControllers from the apiGroup metacontroller.github.io
removing CRDs from the old group.

Based on a basic investigation I think that it could be done without downtime, but it also involves taking some risks.

agree, I guess in 1.16 there were introduced some webhook conversion API, but anyway, if it is possible, it would be good to not doing that at all.

https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/#webhook-conversion

Alright. Migration will be painful for sure. Let's ask for approval then. @grzesuav or @fpetkovski do you mind taking this up.
Eventually I am hoping we can make this CRD stuff an internal affair similar to a configuration file.  I have had good success in metac in this approach. However getting an approval should be the right thing for existing CRDs.

Sure, I wanted to take it after merging some improvements to releases, testing @fpetkovski changes (CRD change). Will try to do some discovery next week

I also did some preliminary research and managed to find the process required for getting an API approved: https://github.com/kubernetes/community/blob/master/sig-architecture/api-review-process.md#mechanics

thanks @fpetkovski !
In first place we should look at :

https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md
https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api_changes.md

to check if we comply


mere existence of ESP_LOG_BUFFER_HEX_LEVEL() line causes 10x wifi slowdown (IDFGH-7143)

Environment

Development Kit:  AiThinker  ESP-12K
Module or chip used:  esp32s2
IDF version (run git describe --tags to find it): release/v4.4
Build System:   idf.py
Operating System:   Linux
Using an IDE?: VSCode IDF Plugin
Power Supply:  external 3.3V

Problem Description
I have a send_packet() function that sends wifi packets using esp_wifi_80211_tx(). The function does many things, such as compute crc32, fragment large packets, does some logging, properly configures the mac header, and so on.
One line present is:

ESP_LOG_BUFFER_HEX_LEVEL(tag_send_packet,packet->array,PACKET_HEADER_SIZE+payload_size,ESP_LOG_VERBOSE);

But that line never actually gets triggered, since I globally set the log level to ESP_LOG_WARN. Despite this, when running the code on an esp32, I get around ~900KB/s. I'm happy with that. With some tweaking I can get up to 5.8MB/s (jaw dropping). But surprisingly, when I compile for an esp32s2, with all sdkconfig settings remaining as equivalent as possible, the speed drops to 157.83 KB/s in a test setup, causing it to drop even further (~20KB/s) in a field-app, which is unbearably slow. After alot of testing, I localized the issue to that log line, simply its presence. If I comment it out, the speed jumps to 900KB/s, just like for the esp32. By uncommenting it, even though it never generates any output, the speed tanks as mentioned. Is this a bug or is there some caveat I'm not aware of?
My initial assumption was perhaps it's a caching issue. But if I place IRAM_ATTR before the definition of send_packet(), that actually makes the speed drop to about 80 KB/s. If I keep the IRAM_ATTR but again comment out ESP_LOG_BUFFER_HEX_LEVEL(), then the speed rises again to 900KB/s and is thus unaffected by the lack/presence of IRAM_ATTR in the commented case.
I've tried all thinkable combinations in sdkconfig (such as playing with the tx/rx buffer types/sizes, memory/heap protections/tracing, stack protections, compiler optimization level, etc), as well as removing all the heavy calculations from send_packet(). Nothing has any mentionable effect. It all boils down to whether I comment out ESP_LOG_BUFFER_HEX_LEVEL() or not.

Maybe there is some LOG_LOCAL_LEVEL define in one of the esp32s2 header files that is overriding your global log level

Hi @moefear85
Do you mean just adding below line will cause lower performace in ESP32S2, right?

ESP_LOG_BUFFER_HEX_LEVEL(tag_send_packet,packet->array,PACKET_HEADER_SIZE+payload_size,ESP_LOG_VERBOSE);
Seems like cache issue, can try different configration of ICache config:

Instruction cache size : 8KB or 16KB;

instruction cache line size: 16Bytes or 32 Bytes
And do you enable PSRAM?
If yes, you can try with different configration of DCache config:

Data Cache size: 8KB or 16KB;

Data Cache line size: 16Bytest or 32Bytes.
And you can refer to s2 iperf config: https://github.com/espressif/esp-idf/blob/master/examples/wifi/iperf/sdkconfig.defaults.esp32s2
Thanks.

I already have the cache settings at their maximums. No PSRAM enabled. I already tried those s3 iperf config settings.
But yeah, I guess it's a cache issue. I just commented out all occurances of that function. Performance in a test scenario is perfect. In a real-life scenario, such as SLIP over wireless, I was initially getting 200kbit/s. After tweaking everything I can think of, I bumped this up to 470kbit/s. That's good enough for me, that's half of what I get over a direct serial line. Any further improvement will require deep analysis how parts of the code are moved in/out of cache and which parts should be kept where. But now I have other priorities.

btw as far as I understand, PSRAM runs at max 80MHz, ie the max that flash can achieve. So I see PSRAM effectively as slow as flash accesses on cache misses. That's why I generally don't use it unless I really need the space.

I started caching the results of some relatively intensive calculations on each packet send. I managed to bump up wireless SLIP speed to 700Kbit/s. That's almost on par with serial, and somewhat faster than what I would get over traditional wifi (station+lwIP).

hi @moefear85

CPU is always at 240MHz. I assume CPU accesses to memory run on the order of ~240MHz?

Yes.

Also worth noting, even in the bulk/unacknowledged case, esp_wifi_80211_tx returns alot of ESP_ERR_NO_MEM values. So for accurate results, I create an inner loop around it, that endlessly retries until ESP_OK is returned, and that counts as a single outer loop.

This depends on the wireless air traffic. And you can try with esp_wifi_set_ps(0) to disable Modem sleep to improve the opportunity of 80211_tx to send. Also you can use esp_err_t esp_wifi_config_80211_tx_rate(wifi_interface_t ifx, wifi_phy_rate_t rate); to config 80211_tx pkt rate to improve performace, but this feature still only in master branch, will be backported to release/v4.4 & v4.3 soon.

This depends on the wireless air traffic. And you can try with esp_wifi_set_ps(0) to disable Modem sleep to improve the opportunity of 80211_tx to send. Also you can use esp_err_t esp_wifi_config_80211_tx_rate(wifi_interface_t ifx, wifi_phy_rate_t rate); to config 80211_tx pkt rate to improve performace, but this feature still only in master branch, will be backported to release/v4.4 & v4.3 soon.

but i'm already calling those functions. do you mean they are currently just place-holders that don't actually do anything?
also, is i use default sdkconfig, but disable power saving, does this mean the modem is still able to sleep between transfers & does it sporadically do so? if yes, for how many micro/milliseconds on average? does it sleep until the next transfer? i'm sure the channel i'm on is practically empty

Hi @moefear85

but i'm already calling those functions. do you mean they are currently just place-holders that don't actually do anything?

No, it can works, bug in release/v4.4, it can only works in 20MHz bandwidth, if you can capture wireless pkts, you can upload some pkts for me to analysis.

also, if i use default sdkconfig, but disable power saving, does this mean the modem is still able to sleep between transfers & does it sporadically do so?

No, if you set esp_wifi_set_ps(0) ,  then esp32 modem will never turn off to sleep.


updated new post section

Updated the "new post" section

Updated the "new post" section

Hi there :)
Please allow some time for the guidelines to be cleared (regarding point distribution, mentor onboarding, etc) by GSSOC team before this pr can be reviewed. Your patience is appreciated.
Meanwhile you can check your code analysis from deepsource in the checks above(by clicking on details for deepsource: Javascript) and try to resolve some of those issues (you may ignore some minor issues)
Thank you!

Thanks for your contribution!


isOpaque does not move view with keyboard

On iOS 17, having the isOpaque set to true does not allow the keyboard to move the view. The keyboard will block the view if it has isOpaque set to true on iOS 17.

Hey @Holychris56, there is a useKeyboardSafeArea parameter for bottom popups, also you might achieve what you want using system keyboard avoidance settings. If these options don't help, please provide your code, so I can reproduce your particular issue

Hey @f3dm76, ok looks good! However, the toolbars are now broken. Looks like my toolbar has disappeared lol.
            .popup(isPresented: $isPresenting) {
                TestView()
                    .preferredColorScheme(.dark)
                    .environment(\.colorScheme, .dark)

            } customize: {
                $0
                    .isOpaque(true)
                    .useKeyboardSafeArea(true)
                    .type(.toast)
                    .position(.bottom)
                    .backgroundColor(.black.opacity(0.4))
                    .closeOnTap(false)
            }

Struct TestView: View
{
var body: some View
{
test()
.toolbar
{
ToolbarItem(placement: .keyboard)
{
Button("Done")
{
            }.foregroundColor(Color(UIColor.stockOrbitTeal))
                .frame(maxWidth: .infinity, alignment: .trailing)
        }
    }
}

}
}

Hey @Holychris56, this is an Apple bug with fullScreenCover. Opaque mode is implemented using fullScreenCover since it is the only way I could find to display over navbar. Please do let me know if there is another way. Here is the code demonstrating Apple's bug:
.fullScreenCover(isPresented: $isPresented) {
    TextField("Your name", text: $name)
        .padding()
        .background {
            RoundedRectangle(cornerRadius: 12)
                .stroke(.black)
        }
        .padding(EdgeInsets(top: 37, leading: 24, bottom: 40, trailing: 24))
        .background(Color.white.cornerRadius(20))
        .toolbar {
            ToolbarItem(placement: .keyboard) {
                Button("Done") { }
                .frame(maxWidth: .infinity, alignment: .trailing)
            }
        }
}


25 add support for pd.DataFrame in CPI LOCO and PrmutationImportance

Motivation: Supporting pd.DataFrames can be convenient for variable importance inference since it allows the use of explicit variable / group of variable naming (eg a grouping dict of the format:
'mri': ['parcel_a', 'parcel_b' ...], 'fmri': ['connectivity_a', 'connectivity_b', ...])

This PR: Allow using pd.DataFrames as input in  in the .fit, .predict and .score methods of CPI, LOCO and PermutationImportance. The PR introduces minor changes including type checking in the above functions.
It also adds the corresponding tests.

Merging, then.


#4500 Modifying application.yaml as required by openshift.io osio pipeline library

https://github.com/openshiftio/openshift.io/issues/4500
This changed include the below which is required by osio pipeline library (https://github.com/fabric8io/osio-pipeline) :
1. Adds parameter - RELEASE_VERSION which is basically the
build number and will be used to differentiate between
the resources of the particular build.
2. Adds parameter - SUFFIX_NAME which is an identifier to
differentiate between the master build or other branches.
 So whenever there is
a change in the resources of a particular branch, it applies
to the resource of that branch only. The SUFFIX_NAME variable
is used in the name of all resources.

test please

test this please

@geoand , could you guys have a look at this PR ?

@Ladicek @geoand could you guys take a look at this PR we fixed the suggestion mentioned by you guys

@Ladicek @geoand could you guys take a look at this PR we fixed the suggestion mentioned by you guys

bump ^^

@metacosm
I thought of making it consistent and while testing it it failed for not resolving the image and latest was working fine. But now I tested again with the RUNTIME_VERSION I am changing it back the way it was before in a separate PR for which have been merged.


AttributeError: 'NoneType' object has no attribute 'problem'

Hi,
I encountered a similar error discussed here: https://forum.qiime2.org/t/q2-micom-grow-pluggin-error-nonetype-object-has-no-attribute-problem/17655. I updated GUROBI and checked system requirements but everything seemed okay.
You can find the log file of the corresponding error as attached:
2021-03-25T225721.134097.snakemake.log
Thank you in advance.

Hi,
Yep, unfortunately Gurobi is currently broken in optlang (https://github.com/micom-dev/micom/issues/24) and this propagates to MICOM. We can hopefully fix that soon. This problem won't occur with CPLEX so if you have access to this solver this would be a workaround.


Remove generated shaders from source control

The shaders/generate_shader_code.js script generates shaders.

[ ] Use add_custom_command with CMake and a genrule with Bazel to generate the shader code.
[ ] Install the needed npm dependencies with each respective build tool as well.
[ ] Remove the generated shaders from source control, add the generated files to .gitignore.

Related ticket #310

Superseded by https://github.com/maplibre/maplibre-native/issues/1298


Update Message even with new Version

I Just downloaded the Latest master.zip from today.
After extracting it says V 3.0.1 and still Updates available
chriz

Just downloaded the lastest master and it says "3.0.4". Maybe you bypassed some files while updating.


Major BUG!

Describe the bug
A user posted a public memo that when the administrator deletes the user account, the exploration function will be unavailable!
Steps to reproduce

The administrator creates a user account
The new user posts a public memo
The administrator deletes the account
The exploration function is unavailable

The version of Memos you're using.
v0.22.3
Screenshots or additional context
No response

rpc error: code = Internal desc = runtime error: invalid memory address or nil pointer dereference

got same issue.

Same here. As soon as you archive and then delete the user, the posts from that deleted user are gone, but also the "Explore" page shows nothing. Version 0.22.3 here.

Fixed with https://github.com/usememos/memos/commit/7564c40c8d846c4c30b8fb1357d23b924e16bd6c
The main reason is that there is dirty data, which can be cleaned up manually at this moment. And we'd like to implement the relevant logic in next release.

太好了


SVG Transcoder Gradle Plugin uses incorrect property annotation

In TranscodeTask the outputDirectory property here is annotated with @get:InputDirectory, which should probably be @get:OutputDirectory instead. I have a commit on my fork that can be cherry-picked or I can send a proper PR if required.

Thanks, this has been fixed now


Yatin: Watch puertaslevadizas.org.pe

Yatin requests the watch of the watch_keyword puertaslevadizas\.org\.pe. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

puertaslevadizas\.org\.pe has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Spevacus in Charcoal HQ


[BUG:] Reason Duplicate

When I ban someone, it says the reason twice, once under the reason tab and once under the ends by tab. I have a photo;
Click for photo

this error is already known.

So why don't you fix it?

I fixed it in this commit.


Implement background and title

Latest commit also fixes up CSS and makes colors the same in sidebar and nodes


Histogram not working properly, according to example

I believe there is an issue with the histogram examples (or perhaps with histograms itself). I have created a simple js histogram rendering using https://github.com/mipt-npm/plotly.kt/blob/master/examples/src/main/kotlin/histogram/BasicHistogram.kt as a reference. The code is the following: (version 0.3.1)
    document.addEventListener("DOMContentLoaded", {
        val element = document.getElementById("test") as? HTMLElement
            ?: error("Element with id 'test' not found on page")

        console.log("element loaded")

        val rnd = Random
        val values = List(500) { rnd.nextDouble() }

        element.plot {

            histogram {
                x.numbers = values
                name = "Random data"
            }

            layout {
                bargap = 0.1
                title {
                    text = "Basic Histogram"
                    font {
                        size = 20
                        color("black")
                    }
                }
                xaxis {
                    title {
                        text = "Value"
                        font {
                            size = 16
                        }
                    }
                }
                yaxis {
                    title {
                        text = "Count"
                        font {
                            size = 16
                        }
                    }
                }
            }
        }
    })

I believe this should produce a good looking histogram however what is produced is the following:

Also there is another issue in the examples, the usage of Random, which according to the documentation (https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.random/-random/) should be called like Random.nextDouble() instead of Random().nextDouble() as it is written in the examples.

Thanks, I've reproduced it on JS (works perfectly fine on the JVM). For some reason, it ignores the trace type parameter when used directly from JS.
The Random is not the issue. Random() function creates a new generator with a random seed whereas Random singleton (companion object) represents the default generator that is created on start. In this context, there is no difference.

Thanks, I've reproduced it on JS (works perfectly fine on the JVM). For some reason, it ignores the trace type parameter when used directly from JS.
The Random is not the issue. Random() function creates a new generator with a random seed whereas Random singleton (companion object) represents the default generator that is created on start. In this context, there is no difference.

For some reason I couldn't get the Random() to work on my plot, I had to change it to Random as you see on the code in order to work. Probably some issue with dependencies on my side. (I imported import kotlin.random.Random to access Random).

Just for educational purposes. The problem is that I used the direct dynamic conversion of Kotlon structures to Json and the enum class is converted into structure instead of value. Like this:

I will fix that shortly.

Fixed and will be available in 0.4.0

Fixed and will be available in 0.4.0

Is the fix available in the currently published development version? 0.3.1-dev6 (if exists) when are those released? Thanks.

No, we need to migrate to a new version because there are some breaking changes and the package version change (kscience->space.kscience). I've published the 0.4.0-dev-2 to the dev repository. So you can use right now via
reposirories{
  maven("https://repo.kotlin.link")
}

depdendencies{
  implementation("space.kscience:plotlykt-core:0.4.0-dev-2")
}

There are breaking changes in package names, so be sure to check examples in dev branch.


Advanced app on the same domain: Bad Request (#400) Unable to verify your data submission

i have setup an advanced application and i have kept the cookie and session different from the front end application. I have also included  in all my layout files.
i am facing a problem { Bad Request (#400) Unable to verify your data submission. } when i am logged in with two different users one for frontend and the another for backend on the same browser window, every time i tried to logout from either of the application i get the following message.
Bad Request (#400)
Unable to verify your data submission.

I have the same issue here is my config
'request' => [
'csrfParam' => '_backendCSRF',
'csrfCookie' => [
'httpOnly' => true,
'path' => '/admin',
],
],
'user' => [
'identityCookie' => [
'name' => '_backendIdentity',
'path' => '/admin',
'httpOnly' => true,
],
'identityClass' => 'common\models\User',
'enableAutoLogin' => true,
],
'session' => [
'name' => 'BACKENDSESSID',
'cookieParams' => [
'path' => '/admin',
],
],
What is wrong don't know

Hello Touqeer,
Please try comment the path attributes.
On Mar 9, 2015 2:45 PM, "Touqeer"<EMAIL_ADDRESS>wrote:

I have the same issue here is my config
'request' => [
'csrfParam' => '_backendCSRF',
'csrfCookie' => [
'httpOnly' => true,
'path' => '/admin',
],
],
'user' => [
'identityCookie' => [
'name' => '_backendIdentity',
'path' => '/admin',
'httpOnly' => true,
],
'identityClass' => 'common\models\User',
'enableAutoLogin' => true,
],
'session' => [
'name' => 'BACKENDSESSID',
'cookieParams' => [
'path' => '/admin',
],
],
What is wrong don't know
—
Reply to this email directly or view it on GitHub
https://github.com/yiisoft/yii2/issues/6123#issuecomment-77820781.

I have changed the path attribute with my "my-application/admin" now it's working.


Crash on backspace.

When file has more then one line program can panic when backspacing for some reason.
'main' panicked at 'assertion failed: start <= end',
/home/cowboy8625/.cargo/registry/src/github.com1ecc6299db9ec823/ropey-1.1.0/src/rope.rs:605:9

note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

Looks like this has been fixed.


Adopt the RISC-V template

Details in issue #84
-Signed-off-by: Jeff Scheel<EMAIL_ADDRESS>

Closing.  Will re-submit with a cleaner PR.


Consider adding harrow-downloader to SeaORM showcase!

Hey @System-rat, thanks for adopting SeaORM!
It's our pleasure to see more inspirational projects were built on top of SeaORM :)
Let us know if you have any feature recommendation or feedback.
Some learning resources for you: Documentation, Tutorial, Cookbook, Q&A
Join our Discord server to chat with others in the SeaQL community!
Feel free to submit a PR to showcase your project, https://github.com/SeaQL/sea-orm/issues/403.

@billy1624 First of all thank you for noticing my little throwaway project (it was useful for its purpose and still might be useful for someone else), I am very honored to be noticed by one of the head honchos themselves. However, I am uncertain if the project is worth mentioning (since it's just a throwaway one for my personal use and whoever has the same need), I wouldn't want to clutter the showcase with what is, arguably, not the best code I've written. But feel free to convince me otherwise!

Hey @System-rat, thanks for the love and support!! I'm reaching out to collect feedback.
This is just an invitation so it's up to you to showcase the project :)


Fix accessibility

Signed-off-by: Jordi Noguera<EMAIL_ADDRESS>

LGTM
https://webhint.io/scanner/1dfee79c-edc1-48b1-909b-e6288c8ce29f


(cannot read property Symbol(Symbol.iterator))

Review the documentation: https://docs.sentry.io/platforms/javascript/electron/
Search for existing issues: https://github.com/getsentry/sentry-electron/issues
Use the latest release: https://github.com/getsentry/sentry-electron/releases
Provide a link to the affected event from your Sentry account

Versions + Platform

SDK version -<EMAIL_ADDRESS>Electron version -<EMAIL_ADDRESS>Platform - Windows

Description
We used the 2.1.0 version of the backend sentry and now we have updated the sentry/electron to find this error frequently and how to handle it or which version the author has recommended to use. Looking forward to your reply

This is also happening to us. We released a new Electron build yesterday that upgraded @sentry/electron to 2.0.4 from 1.3.0 and we now have about 260, 000 occurrences of this error in Sentry.

We also upgraded from 1.3.0 to 2.1.0. Have you found a solution？

We updated the app to use the same version of Sentry Electron for both the main and renderer processes (they're both on 2.2.0 now). We're not seeing this error on the newer version of the app as far as I can tell.

Thank you for your advice. Which version number of Electron do you use? And then I have another question to ask you, about electron crashReporter. Start only available in the main process or does it also need to start in the rendering process? Looking forward to your reply

If you run different versions in the main and renderer it'll only be luck if anything works.
The renderer passes events and content through the main process and much has changed between those version numbers.

zhaoxiaolei519109457, we're on Electron 11.2.3.


App adds padding on top and bottom for PDF but not for vertical images

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open the app in mac safari, android chrome, mac chrome
Open any report
Click plus and click on add attachment
Select any PDF and observe padding on top and padding increase on bottom after scroll
Send the PDF, reopen the PDF after sending and observe the padding on top and bottom
Send vertical image and observe the padding on top and bottom while sending and in attachment preview

Expected Result:
App should not add padding on top and bottom for PDF OR App should add padding on top and bottom for vertical image too
Actual Result:
App adds padding on top and bottom for PDF and does not add padding for vertical image
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[x] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: 1.2.91-1
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

https://user-images.githubusercontent.com/43996225/228656398-7d251acc-30df-4439-a10e-c6e0ccc8ce91.mov
Expensify/Expensify Issue URL:
Issue reported by: @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1680103327417349
View all open jobs on GitHub

Triggered auto assignment to @arielgreen (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

Hi @dhairyasenjaliya, I agree we don't require padding on top and bottom in PDF to utilize maximum content But currently, mac safari, mac chrome, android chrome adds padding on top and bottom of PDF which is the main issue (android app does not add padding which is ideal). Let me know your thoughts on that and let me know for any confusion on reason to raise it as bug.

agree this isn't a problem. closing


Chunking implmentation seems to be broken

While developing gelfino (a tiny gelf server) I used your gelf client as a bench to test message send, the sequence and count fields are wrong (I get 52 53 as values) I think its related to the way int's are converted to bytes (gelf4r seems to do this right)
Iv used both gelf4r and gelf4j and they work fine,
Thanks
Ronen

I am getting this error on the graylog2 server, which appears to be caused by the issue reported here.
2012-02-03 01:14:25,018 ERROR: org.graylog2.messagehandlers.gelf.GELFClientHandlerThread - Invalid GELF header in message: org.graylog2.messagehandlers.gelf.InvalidGELFChunkException: Invalid GELF chunk: Sequence number must be lower than sequence count.
org.graylog2.messagehandlers.gelf.InvalidGELFHeaderException: org.graylog2.messagehandlers.gelf.InvalidGELFChunkException: Invalid GELF chunk: Sequence number must be lower than sequence count.
        at org.graylog2.messagehandlers.gelf.ChunkedGELFClientHandler.<init>(ChunkedGELFClientHandler.java:74)
        at org.graylog2.messagehandlers.gelf.GELFClientHandlerThread.run(GELFClientHandlerThread.java:58)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
        at java.lang.Thread.run(Thread.java:636)
Caused by: org.graylog2.messagehandlers.gelf.InvalidGELFChunkException: Invalid GELF chunk: Sequence number must be lower than sequence count.
        at org.graylog2.messagehandlers.gelf.GELFClientChunk.checkStructure(GELFClientChunk.java:159)
        at org.graylog2.messagehandlers.gelf.ChunkedGELFMessage.insertChunk(ChunkedGELFMessage.java:52)
        at org.graylog2.messagehandlers.gelf.ChunkedGELFClientManager.insertChunk(ChunkedGELFClientManager.java:70)
        at org.graylog2.messagehandlers.gelf.ChunkedGELFClientHandler.<init>(ChunkedGELFClientHandler.java:72)
        ... 4 more

It seems to happen pretty consistently given a specific log message input.

Hi,
Thanks for finding this!
Anton

I submitted a https://github.com/t0xa/gelfj/pull/24 to fix this -- the current code didn't seem to be following the correct GELF header spec as per https://github.com/Graylog2/graylog2-docs/wiki/GELF.

I haven't tried it with < 0.9.6, but I don't think so... if you look at the GELF wiki history it seems like it has always been this way, except for during one day on Jul 15th when someone changed it, and than lennart reverted the change.
Besides, if graylog has changed it in 0.9.6 you are going to have to release the changes anyway, with a note that it only works with 0.9.6 and above.

Also, take a look at:
https://github.com/Graylog2/graylog2-server/commits/develop/src/main/java/org/graylog2/messagehandlers/gelf/GELFHeader.java

I'll note that on Wiki.


打包后运行不了

打包后运行不了呢

页面一直在加载
Access to script at 'file:///E:/runtime-es2015.d8d5c60e17c725000a90.js' from origin 'null' has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, chrome, chrome-extension, https.
runtime-es2015.d8d5c60e17c725000a90.js:1 Failed to load resource: net::ERR_FAILED
index.html:1 Access to script at 'file:///E:/polyfills-es2015.85ea611aafc2ca9484ce.js' from origin 'null' has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, chrome, chrome-extension, https.
polyfills-es2015.85ea611aafc2ca9484ce.js:1 Failed to load resource: net::ERR_FAILED
index.html:1 Access to script at 'file:///E:/main-es2015.0f38eaa8a3f8e89da331.js' from origin 'null' has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, chrome, chrome-extension, https.

build后的文件，需要反向代理运行1. 本地用http


Add Connectable operators: :<=, :>=, :<>=, and :#=

Background
In general, Chisel's connection operators are very broken; their semantics change depending on import Chisel._ vs import chisel3._. Even chisel3._'s semantics are not clean; you cannot reason about what will be connected to what unless you know whether the things you are connecting are Wires or IOs. Part of this stems from the fact that we got rid of relative-flippedness for declaring things, instead relying on using Input/Output.
This PR defines four new operators which have very clean semantics which depend solely on the hardware type of the things you are connecting. Using them, we plan to migrate all existing operators semantics to compositions of them, but for now we define them independently of Chisel/chisel3, and thus they have more verbose syntax to make them compatible with both imports.
As we continue, we may rename them etc., but their semantics are composable which is an important property. In fact, there are only actually two operators which, when composed in different ways, can implement the semantics of other kinds of operators: :<= and :>=. While these operators may not be the most common ones to use, understanding them will help users reason about how all the connection operators work.
I've written a lot of ScalaDoc and mdoc to describe their semantics.
TODO:

[x] Clean up tests (moving examples to own section, looking through old commented out ones to see if there are any useful ones to preserve, deleting ignored ones)
[x] Remove changes from := to :#= and changes to test, as migration flag is off
[x] Add Scaladoc to WaivedData
[x] Clean up random things (commented out printlns, etc.)

Current requested reviewer feedback

Scaladoc and mdoc explanations are clear

Contributor Checklist

[x] Did you add Scaladoc to every public function/method?
[x] Did you add at least one test demonstrating the PR?
[ ] Did you delete any extraneous printlns/debugging code?
[x] Did you specify the type of improvement?
[x] Did you add appropriate documentation in docs/src?
[x] Did you state the API impact?
[x] Did you specify the code generation impact?
[x] Did you request a desired merge strategy?
[x] Did you add text to be included in the Release Notes for this change?

Type of Improvement

new feature/API

API Impact

No impact on current code. Adds new operators and documentation.
Desired Merge Strategy

Squash: The PR will be squashed and merged (choose this if you have no preference.

Release Notes

Added new operators :<>=, :<=, :>=, :#=
Added new Scaladoc to :=, <>

Reviewer Checklist (only modified by reviewer)

[ ] Did you add the appropriate labels?
[ ] Did you mark the proper milestone (Bug fix: 3.4.x, [small] API extension: 3.5.x, API modification or big change: 3.6.0)?
[ ] Did you review?
[ ] Did you check whether all relevant Contributor checkboxes have been checked?
[ ] Did you do one of the following when ready to merge:

[ ] Squash: You/ the contributor Enable auto-merge (squash), clean up the commit message, and label with Please Merge.
[ ] Merge: Ensure that contributor has cleaned up their commit history, then merge with Create a merge commit.

Note that I left so many comments, many are hidden.


Can't use NLog-Config-Variables to control the enabled-flag for relevant Logging Rules

I need to use an NLog config variables to control the enabled-flag for logging rules. My intention is to assign the values of those NLog config variables from the appsettings.json, which allows me to override them using stage-based environment variables in my CI/CD Pipeline.
The following snippet of the  NLog config works as expected by instructing NLog to not log to the file target
    <rules>
		<logger name="*" minlevel="debug" writeTo="file" enabled="false"/>
    </rules>

while the following snippet returns the error: "Warn Error has been raised. Exception: NLog.NLogConfigurationException: 'enabled' hasn't a valid boolean value '${fileLogEnable}'."
    <variable name="fileLogEnable" value="false" />

    <rules>
		<logger name="*" minlevel="debug" writeTo="file" enabled="${fileLogEnable}"/>
    </rules>

NLog version: 5.0.0
Platform:  .NET6
Current NLog config
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      autoReload="true"
	  internalLogToConsole="true"
	  internalLogFile="/LogFiles/NLog_internal.log"
	  internalLogLevel="Warn"
	  >

    <extensions>
		<add assembly="NLog.Web.AspNetCore"/>
    </extensions>

    <targets async="true">

        <target
			xsi:type="File"
			name="file"
			fileName="/LogFiles/Test_NLog_Rules.log"
			layout="${longdate}|${event-properties:item=EventId.Id}|${machinename}|${aspnet-request-ip}|${aspnet-request-host}|${aspnet-request-method}|${uppercase:${level}}|${logger}|${message} ${exception}"
			archiveFileName="/LogFiles/Test_NLog_Rules{#}.log"
			archiveNumbering="DateAndSequence"
			archiveAboveSize="10485760"
			maxArchiveDays="14"
			maxArchiveFiles="14"
		/>

    </targets>

    <!--<variable name="fileLogEnable" value="${configsetting:item=EnableLogTarget.File}" />-->
    <variable name="fileLogEnable" value="false" />

    <rules>
		<logger name="*" minlevel="debug" writeTo="file" enabled="${fileLogEnable}"/>
		<!--<logger name="*" minlevel="debug" writeTo="file" enabled="false"/>-->
    </rules>
</nlog>

What is the current result? Rules logger's enabled flag of true/false cannot be controlled from a NLog config variable
What is the expected result? Control the rules logger's enabled flag from a NLog config variable
Did you checked the Internal log? Yes
Please post full exception details (message, stacktrace, inner exceptions) See attached "NLog_internal.log"
Are there any workarounds? Unknown
Is there a version in which it did work? Unknown
Can you help us by writing an unit test? .NET Core API Project attached

NLog_internal-when_enabled_is_assigned_false.log
NLog_internal-when_enabled_is_assigned_fileLogEnable_variable.log
Test_NLog_Rules.zip

You can use NLog-variables for minlevel="..." where Off / None means the same as enabled=false.

I'll use that then. It works. Thank you!


Adding extension to partials

I saw you are mixing partials with and without the html extension. Any reason why? I would advise sticking to the extension as a standard.

No special reasons. I use extension for some main partial blocks. You are right, I'll make the change.


"detail": "Authentication credentials were not provided."

hey i just try to run ur reset api but it didnt work can u help to fix it

Sorry for late, I  dont know what you mean with reset api, but it seems you have not created an user with this endpoint POST http://<IP_ADDRESS>:8000/rest-auth/registration/ username="USERNAME" password1="PASSWORD" password2="PASSWORD"


Add separate PR diff comments for Nunjucks rendered HTML

This PR adds a separate Nunjucks rendered HTML diff
We added "Other changes" in https://github.com/alphagov/govuk-frontend/pull/4511 but we never get to see the output Nunjucks → HTML render
How to diff HTML
Our built npm package includes template.njk for each component, but where's the HTML?
This PR uses Nunjucks to generate all non-hidden component examples into the npm package
The new HTML files are ignored by npm publish using .npmignore but appear in the diff output:
  packages/govuk-frontend/dist/govuk/components
  ├── _all.scss
  ├── _all.scss.map
  └── accordion
     ├── README.md
     ├── _accordion.scss
     ├── _accordion.scss.map
     ├── _index.scss
     ├── _index.scss.map
     ├── accordion.bundle.js
     ├── accordion.bundle.js.map
     ├── accordion.bundle.mjs
     ├── accordion.bundle.mjs.map
     ├── accordion.mjs
     ├── accordion.mjs.map
     ├── fixtures.json
     ├── macro-options.json
     ├── macro.njk
+    ├── template-default.html
+    ├── template-with-additional-descriptions.html
+    ├── template-with-all-sections-already-open.html
+    ├── template-with-focusable-elements-inside.html
+    ├── template-with-long-content-and-description.html
+    ├── template-with-one-section-open.html
+    ├── template-with-translations.html
     └── template.njk

Diff examples
See https://github.com/alphagov/govuk-frontend/pull/4522#issuecomment-1835821530 for Button component Nunjucks rendered HTML

We brought this up in dev catch up and agreed it was useful
There's currently no visibility of our HTML output unless the Review app js-beautify HTML formatter is turned off

@36degrees Sounds good
Think you'd rather have this PR than all the fixtures.json single-line html changes we have currently?
Or could this PR make the fixtures.json diff output show multiple lines for \n somehow?

Minor, but I think the two new imports added in 81a20275d76d044719ab2e94fb99f24725e3df9a belong with the changes in f1de6bd1fb8ddab90435e1c9ca3c9aa82caaca43.

@36degrees Thanks for spotting that
Definitely merge this as a trial, we can always tweak things
I'll make a temporary change to show what the diff looks like


Fixed unscrollable slide in presentation mode

Issue that this pull request solves
Closes: #432
Proposed changes
Made changes in the new-board.component.scss file in the newboard component
Brief description of what is fixed or changed
Added overflow-y property and set its value to auto along with important to the existing class which is '.reveal .slides' incoming from reveal.css
Types of changes
Put an x in the boxes that apply

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update (Documentation content changed)
[ ] Other (please describe):

Checklist
Put an x in the boxes that apply

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] My changes does not break the current system and it passes all the current test cases.

Screenshots
Please attach the screenshots of the changes made in case of change in user interface

Other information
Any other information that is important to this pull request

Hello @Aniket-508,
Thanks for the enhancement!


⚠ ClamAV has degraded performance

In 3724281, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 70 ms

Resolved: ClamAV performance has improved in 09d43a9.


Reacting to verbose rename

Reacting to https://github.com/aspnet/Logging/pull/314.
Need to test locally.

Hi @JunTaoLuo, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;


support node v6.0

when I compiled using debowerify,I get follow message.
(node:6292) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.

fortunately,I using nvm,so I switched simply,but supporting wide range is important.

sorry.
maybe occurred by bowerify.
this package was not related.
see https://github.com/eugeneware/debowerify/issues/83

+1

closed.


Massive amounts of Ram used.

Ok this is a odd problem.
I have tried about 6 different versions of FFMPEG but still happens, I have however noticed a pattern!
When the script runs as a post-process and hits a file that's over 1.5gb it will use almost double that in ram for some reason, BUT if I run the same file via the Manual script it will not go above 800mb of ram!!
I can not see a single thing in the logs to explain it or even work it out as Manual works wonders and has little impact on my ram, but running as a post-process from either Deluge or sabnzbd then we hit high numbers.

Ok after some more playing around, I think I have identified the problem and am wondering if something can be added to the script to avoid it?
It seems that it only happens to files that have E-AC3 or DTS-HD audio but namly E-AC3 is there a way to to add a trigger that will skip these files so I can sort them out by other means?

Update time, I found the memory leak and it was FFMPEG at fault took them almost a month to fix but its done :)


TA2 Scripts for Evaluation

We need script(s) to submit along with our TA2 system for evaluation.
The script(s) should do:

Run our TA2 system to generate fitted pipelines (search mode)
Run a fitted pipeline (test mode)
Run our TA2 system in server mode (TA3 mode)

We have to modify this sample d3mStart.sh file to call our script(s):
https://gitlab.datadrivendiscovery.org/d3m/d3m-summer2018-run-example/blob/master/d3mStart.sh
Our script(s) should look up shell environment variables for number of CPUs, RAM and Timout. See this sample Kubernetes script that set these environment variables:
https://gitlab.datadrivendiscovery.org/d3m/d3m-summer2018-run-example/blob/master/example.yaml
In search mode the config file will always be at /input/search_config.json
In test mode the config will always be at /input/test_config.json
TA3 mode does not require config files

Also, here is the ta2 jump server account for testing the scripts
ssh<EMAIL_ADDRESS>-i ~/.ssh/dsbox_rsa

Tested on jump server, it works. Done


add stipram

@raymundusrendra First stage of verification passed, official domain is stipram.ac.id as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@raymundusrendra Please provide us with an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course.

https://stipram.ac.id/mahasiswa-23-pkm.html

@raymundusrendra I am sorry, this domain seems to represent an tourist industry school, not a specific technical university or a college. The page you have provided us with has no information about long-term (> 1 year of study) course related to software development.
If you individually study an IT-related course in the school, please apply for free educational license with an official document, which proves that you are a student. You can do it using "OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students.
I have to close the request without merging.
Thank you for your understanding!


[BUG]Rancher UI on first screen when Installing Harvester using IPXE Boot

Describe the bug
When trying to install Harvester using ipxe Boot, the first screen which pops up on first login is Rancher UI
To Reproduce
Steps to reproduce the behavior:

Install Harvester using instructions on https://github.com/harvester/ipxe-examples/tree/main/vagrant-pxe-harvester

Expected behavior
Harvester Ui Login page should appear
Support bundle

Environment:

Harvester ISO version: Master
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): IPXE Harvester Boot

Additional context
Add any other context about the problem here.

Not sure if what i'm seeing is different from this bug but i wanted to put it here just in case. I'm not using IPXE but after the first login i get to /dashboard/home which shows the "welcome to rancher" dashboard. After some more time (~5 minutes for me) on the same url after refreshing the message changes to "welcome to harvester" and navigating to / opens the harvester ui. I also noticed that on the terminal the harvester-installer shows Ready while its still serving the rancher ui.

that's exactly the reason why some rancher elements are showing on the single Harvester. On the console, we should already display the server as NotReady when the Harvester server is not running, but since the Rancher server is ready, so as long as the user is visiting the correct URL we can't disable the webUI as it is managed by the Rancher.

@guangbochen can we find a way to disable Rancher server UI temporarily until the Harvester setup is done? We might need to reach out to the Rancher team to see if there is a way.

closed in favor of master-48c97ea7-head, currently on the Harvester UI and name was pop up.


tests: Group assertions

This way, if one "subtest" fails the other ones can give more useful information about the failure rather than exiting early.

Thanks


Fix rtapp tasknames matching

Here is a small set of changes required to update rt-app to a more recent version.
We basically get back RTATestBundle working which is broken since:
https://github.com/scheduler-tools/rt-app/pull/53
has been merged to forcing all generated rt-app task to have a -NUMER suffix.
Since we are at that we update also rt-app with the current master, right after we drop support for ppc64le since there are not main users our there: @jlelli scream if you really need it ;)

LGTM. Minor thing only, can you update the commit message to remove this line?
I saw the approved badge and hit the merge button without looking at the comments :'(


Make it more visible that cssnext is a plugin pack / a preset

Should we use "plugin pack" or "preset" like Babel? poke @ai

Plugin pack is a simplier and cleaner word for preset. But preset is more popular. So I have no idea.

I prefer "plugin pack" because it's more clear what's going on. Preset could mean a number of different things.

How about
cssnext is a plugin pack (or "preset")…

Another world used in php world is metapackage.
But anything would be helpful

postcss-cssnext has been deprecated in favor or postcss-preset-env. Read more at https://moox.io/blog/deprecating-cssnext/


Change cert-policy history message

Related to https://github.com/stolostron/cert-policy-controller/pull/250/

/cherry-pick release-2.10


Primitives for inline variables

This is experimental code based on some of the existing reflink pattern.
Due to the huge number of variations in link blocks, I went with double [] instead of single.
Example Brew code:
[a]:b
[[$b="this is a ;"]]

[[$b]]

With the quiet macro

[[a; $g="Hello";:q ]]

Without the quiet macro

[[a; $g="Hello" ]]

[[a]]

this is a ;

    this is a ;

    With the quiet macro

    Without the quiet macro

    Hello

    b

Just a start. Fails are few things, like, I can't seem to make it bold...

I'm going to close this for the other PR, though I may lift some things from it later. :)