Does LuaJIT require coxpcall ?

coxpcall is mandatory with PUC Lua 5.1.
But with LuaJIT, there is a mismatch between these 2 files:
http://github.com/keplerproject/copas/blob/master/src/copas.lua#L28-L30 --> not required
http://github.com/keplerproject/copas/blob/master/src/copas/limit.lua#L13-L15 --> required

Coxpcall is not required under LuaJIT, the line in limit.lua can be fixed. Although latest version of coxpcall is clever enough to return standard (x)pcall instead of co(x)pcall when using LuaJIT.

PR #64 was merged.


SSL configuration is Failed - [BRIEF DESCRIPTION]

App Id: d1d3pjzug73mv2
Region: us-east-2
Step: SSL configuration
Status: Failed

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
A clear and concise description of what the issue/question is.
Error message
If there is an error message, please include it here.
Note: Be sure to check the message for sensitive information.
Additional information
Please add any other relevant information. Please feel free to include screenshots.

Hi @rajibganguly -- I see that there is an SSL certificate attached to your app.  Are you still experiencing this issue?


About storage of Extstore

Hello guys, I have some questions about Extstore's storage on disk.

Does Extstore have anything like partition? Example that you store 100gb data, it split into 4 files and each of that stores 25gb. I see only one file on disk when I used Extstore, I read document and quickly take a look on memcached's code, but I didn't see anything about partition. If it have anything like partition, please tell me !

What is the structure of data in a Extstore's file ?
This is an example about structure of file in Kyoto Cabinet

I really want to know memcached Extstore's structure.

Thanks for reading my issue!

it's just one file. There's a PR in progress for expanding on that: https://github.com/memcached/memcached/pull/432
the storage format is literally the same as in-memory object storage. it just copies the object to disk with some small modifications to the header. When being read back in the object is recombined with what was left in memory (some timestamp values mainly). After being written to disk a pointer remains in memory. The pointer knows the exact position of the original item in extstore, so there's no need for a tree or anything in the file itself.
It does split the file into pages of data (64m each), but within each page it's just items packed together.
There's no specific documentation, sorry.
What are you trying to accomplish?

Thanks for your reply, Mr.Dormando.
I just want to understand about Extstore, I read documents and some files of source code to understand, but there are many things which I can not understand well or can not make sure that I'm right, so I usually open issue to ask.

Yeah, I've read that document before, and it really good for tuning/running, it also has some technical things there. It a good one, thanks again, Mr.Dormando.
I will close the issue now!
Hope you have a nice day!


fix Issue 17293 - 'Using C++ Classes From D' example no longer works

BTW I just had the idea to show linker commands, s.t. an unexperienced reader has an easier time:
https://github.com/dlang/dlang.org/pull/1679

but what changed here? Are extern (C++) interface-s no longer supported?

Hmm at least with recent compilers it seemed to have never worked.
Maybe at some point the interface mangling was changed as its an abstract class on the C++ side as well.

2.071 has the important change of ABI, as the Issue 15644.
It must be strongly highlighted.


Auto wrapping quotes does not auto surround the text with quotes

Testing #57317

Have following surrounded pairs configuration

{

	"surroundingPairs": [
		["{", "}"],
		["[", "]"],
		["(", ")"],
		["`", "`"]
	]

}

Have following settings

"editor.autoWrapping": "quotes"

Open a new document with language having above configuration
Type some text and select the text and type "
Expected: Text should be auto surrounded by ". But not.

I have the same issue. I had the expectation that quotes and brackets would be two lists of symbols that get auto wrapping. What they really are are quotes and brackets in the surrondingPairs of a language configuration file.

The surroundingPairs are still defined by a language configuration. In this case, the language configures {}, [], () and `` as surrounding pairs. That means that someone looked at the syntax of the language and in this language, "" and '' are not used.
The user facing setting will use the set provided by the language configuration. i.e. if in this language, "" and '' are meaningful from a syntactical point of view, then you should file an issue to the language author to include them in there.


⚠ RPC server - Binance BSCT has degraded performance

In 118c958, RPC server - Binance BSCT ($BINANCE_BSCT_RPC_URL) experienced degraded performance:

HTTP code: 502
Response time: 727 ms

Resolved: RPC server - Binance BSCT performance has improved in f7984dd.


[ISSUE] Non-Clickable Refresh, Invite, and Language Buttons

See below, tested on FireFox, OperaGX & Safari:

I have the same problem, as a tentative solution what you can do is to inspect the page and delete the entire Create&Watch #speedtyperdev Tiktoks button from the html, attached is a GIF of what I am referring to

I've got the same issue. Needs to fixed soon


About rounding the balance number

For example, if the real balance is 1.537356754, the display balance should be 1.5373 instead of 1.5374
reason:

don't set a wrong expectation, users will expect they can get the full display balance available to use
since we don't have a "send maximum balance" function, users may manually key in the number display in balance, they will key in 1.5374 which will trigger "insufficient balance" or if it is a contract call, will result in transaction fail (I did many times😢）

@zhangzhongnan928 can you check the latest build to see if this is now fixed?

fixed


Blog updates Oct 3, 2024

Looks good!
One thing we may want to investigate is making the iFrame larger for bigger screens so the controls are easier to see / navigate.

Thanks @roberthunterjr . I updated the iFrame to be bigger and responsive to screen size.


Check arguments

!test hello
if argument is hello send message. How can do it?

Here's an easy way to do what you're looking for:
user.on('friendMessage', function(steamid, message) {
    const parts = message.split(' ');

    console.log(`Command: ${parts[0]}`);
    console.log(`Argument 1: ${parts[1]}`);
});

nothing happen in console?

Make sure you send the bot a message while it's online. If you do (and don't get any errors anywhere), that could should work fine.

When only !test
Command: !test
Argument 1: undefined
But !test hello
nothing happen

How can fix it?

if(${parts[1]} == "123") {
^
SyntaxError: Unexpected token {
how can fix it?

Fixed, nevermind. Thanks ^^

@vortexcodes If you could, please post how you fixed it.


Db.doc updates

Just as a note...do we want to change the package "website" to point to the docs page once it is up?

Just as a note...do we want to change the package "website" to point to the docs page once it is up?

What do you mean by package website?

Just as a note...do we want to change the package "website" to point to the docs page once it is up?

What do you mean by package website?

https://github.com/SalesforceCommerceCloud/commerce-sdk/blob/0fc7a682ca979d4d06d5546e3da69c82c4648f11/packages/generator/package.json#L5
"homepage" in the package.json, primarily used by npmjs.com to link to projects.

Ahh I see. I don't know if I'd have a preference to this pointing to CCDC and it having a reference to our SDK doc. Thoughts?


Curtain switch under Product Category "qt"

Device normal info
Zemismart Electric WiFi Smart Roller Shade Motor Tuya Alexa Google Home Motorized Curtain Switch
Expected behavior
Would like it to work. It has 3 modes - Up, Stop, Down.
Proposed solution:  use  clkg Curtain Switch code to make it work?
Device info (please complete the following information, which can be found in log):

Product Name
Curtain switch

Device ID
43001313807d3a28a295

Product Category
qt

Device Status
Online

Activated At
2021-04-30 16:49:30

Device specifications (please complete the following information, which can be found in log):

Product Name
Curtain switch

Device ID
43001313807d3a28a295

Product Category
qt

Device Status
Online

Activated At
2021-04-30 16:49:30

Additional context
It works fine on Google Home / Google Assistant natively.  To get it working in HA, I hacked a nasty workaround:

install assistant relay
create a mock cover entity
have it send text "close the blinds" to Assistant, which closes them

 assistant_relay:     url: http://<IP_ADDRESS>:3000/assistant     method: POST     content_type: 'application/json'     payload: '{"command":"{{ command }}", "user":"Veli"}'
`cover:

platform: cover_rf_time_based
devices:
shade:
name: shade
travelling_time_up: 29
travelling_time_down: 29
close_script_entity_id: script.close_cover_script
stop_script_entity_id: script.stop_cover_script
open_script_entity_id: script.open_cover_script
send_stop_at_ends: False #optional
...
 open_cover_script:
sequence:
service: input_text.set_value
target:
entity_id: input_text.assistant_relay
data:
value: open bedroom blinds
 - alias: Notify - assistant_relay
id: assistant_relay
mode: queued
max: 3
trigger:
platform: state
entity_id: input_text.assistant_relay
action:
service: rest_command.assistant_relay
data:
command: '{{ states.input_text.assistant_relay.state }}'
`

Pls take also a look at this: https://github.com/tuya/tuya-home-assistant/issues/717


KeyError from git remote package installation

[X] I have searched the issue tracker and believe that this is not a duplicate.

Make sure you run commands with -v flag before pasting the output.
Steps to reproduce

Create a repo with some name
Prepare that repo as a python package (appears to have something to do with name?)
Attempt to install from the remote repo

We observed this works with packages that have single word names such as just "example", and that this happen to match the project name. But for a project name such as "project-name", "project_name", etc, this error is observed.
See this repo for a short example of the issue. Run pdm add<EMAIL_ADDRESS>-v to demonstrate (this is already in add.sh). We observed this to occur with the package being named "example" and with "pdm-name-example" in all relevant locations, with the project being named "pdm-name-example".
Actual behavior
A KeyError (specifying the in-repo package name, as opposed to the repo name) leading into a CalledProcessError -> BuildError
gregdan3@Theros ~/g/o/pdm-name-example (master)> ./add.sh
Adding packages to default dependencies: pdm-name-example
======== Start resolving requirements ========
        pdm-name-example<EMAIL_ADDRESS>        Adding requirement pdm-name-example<EMAIL_ADDRESS>Preparing isolated env for PEP 517 build...
Requirement already satisfied: pdm-pep517 in /usr/lib/python3.9/site-packages (from -r /tmp/pdm-build-reqs-d8n107la.txt (line 1)) (0.5.7)
 - Adding setup.py
Traceback (most recent call last):
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pep517/in_process/_in_process.py", line 280, in <module>
    main()
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pep517/in_process/_in_process.py", line 263, in main
    json_out['return_val'] = hook(**hook_input['kwargs'])
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pep517/in_process/_in_process.py", line 204, in build_wheel
    return _build_backend().build_wheel(wheel_directory, config_settings,
  File "/usr/lib/python3.9/site-packages/pdm/pep517/api.py", line 48, in build_wheel
    return Path(builder.build(wheel_directory)).name
  File "/usr/lib/python3.9/site-packages/pdm/pep517/wheel.py", line 47, in build
    self._write_metadata(zip_file)
  File "/usr/lib/python3.9/site-packages/pdm/pep517/wheel.py", line 114, in _write_metadata
    dist_info = self.dist_info_name
  File "/usr/lib/python3.9/site-packages/pdm/pep517/wheel.py", line 104, in dist_info_name
    name = to_filename(self.meta.project_name)
  File "/usr/lib/python3.9/site-packages/pdm/pep517/metadata.py", line 245, in project_name
    return safe_name(self.name).lower()
  File "/usr/lib/python3.9/site-packages/pdm/pep517/utils.py", line 23, in safe_name
    return re.sub("[^A-Za-z0-9.]+", "-", name)
  File "/usr/lib/python3.9/re.py", line 210, in sub
    return _compile(pattern, flags).sub(repl, string, count)
TypeError: expected string or bytes-like object
Traceback (most recent call last):
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/resolver/core.py", line 23, in _merge_into_criterion
    crit = self.state.criteria[name]
KeyError: 'pdm-name-example'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/models/builders.py", line 85, in log_subprocessor
    subprocess.check_call(
  File "/usr/lib/python3.9/subprocess.py", line 373, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/bin/python3', '/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pep517/in_process/_in_process.py', 'build_wheel', '/tmp/tmpuenxrrt6']' returned non-zero exit status 1.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/gregdan3/.local/bin/pdm", line 8, in <module>
    sys.exit(main())
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/core.py", line 76, in __call__
    return self.main(*args, **kwargs)
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/core.py", line 131, in main
    raise err.with_traceback(traceback)
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/core.py", line 127, in main
    f(options.project, options)
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/cli/commands/add.py", line 35, in handle
    actions.do_add(
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/cli/actions.py", line 174, in do_add
    resolved = do_lock(project, strategy, tracked_names, reqs)
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/cli/actions.py", line 69, in do_lock
    mapping, dependencies, summaries = resolve(
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/resolver/core.py", line 152, in resolve
    result = resolver.resolve(requirements, max_rounds)
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/resolvelib/resolvers.py", line 453, in resolve
    state = resolution.resolve(requirements, max_rounds=max_rounds)
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/resolvelib/resolvers.py", line 318, in resolve
    name, crit = self._merge_into_criterion(r, parent=None)
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/resolver/core.py", line 25, in _merge_into_criterion
    crit = Criterion.from_requirement(self._p, requirement, parent)
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/resolvelib/resolvers.py", line 79, in from_requirement
    cands = build_iter_view(provider.find_matches([requirement]))
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/resolvelib/structs.py", line 148, in build_iter_view
    matches = list(matches)
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/resolver/providers.py", line 120, in find_matches
    yield from super().find_matches(requirements)
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/resolver/providers.py", line 42, in find_matches
    can.get_metadata()
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/models/candidates.py", line 149, in get_metadata
    built = self.environment.build(ireq, self.hashes, allow_all_wheels)
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/models/environment.py", line 343, in build
    ret = builder.build_wheel(output_dir)
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/models/builders.py", line 251, in build_wheel
    filename = self._hook.build_wheel(out_dir)
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pep517/wrappers.py", line 204, in build_wheel
    return self._call_hook('build_wheel', {
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pep517/wrappers.py", line 265, in _call_hook
    self._subprocess_runner(
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/models/builders.py", line 177, in subprocess_runner
    return log_subprocessor(cmd, cwd, extra_environ=env)
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/models/builders.py", line 93, in log_subprocessor
    raise BuildError(f"Call command {cmd} return non-zero status.")
pdm.exceptions.BuildError: Call command ['/usr/bin/python3', '/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pep517/in_process/_in_process.py', 'build_wheel', '/tmp/tmpuenxrrt6'] return non-zero status.

Expected behavior
pdm add should successfully install a package at some git remote, given a properly formed installation string, regardless of the repo's name.
Environment Information
gregdan3@Theros ~/g/o/pdm-name-example (master)> pdm info && pdm info --env
PDM version:        1.4.0
Python Interpreter: /usr/bin/python3 (3.9.2)
Project Root:       /home/gregdan3/git/open/pdm-name-example
{
  "implementation_name": "cpython",
  "implementation_version": "3.9.2",
  "os_name": "posix",
  "platform_machine": "x86_64",
  "platform_release": "5.11.2-arch1-1",
  "platform_system": "Linux",
  "platform_version": "#1 SMP PREEMPT Fri, 26 Feb 2021 18:26:41 +0000",
  "python_full_version": "3.9.2",
  "platform_python_implementaiton": "CPython",
  "python_version": "3.9",
  "sys_platform": "linux"
}

You can't install a repo that doesn't have a project name. And the name should be specified in pyproject.toml as PEP 621 says.

My bad- I've corrected that now.
The reason I made that mistake, I realize now: I was trying to transition from using pipenv to pdm, and importing from a Pipfile does not include those fields.
Here is a small example Pipfile, to demonstrate this behavior:
[[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"

[packages]
requests = "*"

[dev-packages]

[requires]
python_version = "3.9"

And here is the pyproject.toml produced from pdm install in a directory with that Pipfile:
[project]
requires-python = ">=3.9"
dependencies = [
    "requests",
]
dev-dependencies = []

[tool]
[tool.pdm]
[[tool.pdm.source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"

[build-system]
requires = ["pdm-pep517"]
build-backend = "pdm.pep517.api"

I matched the pyproject.toml to the one that is created from pdm init/ described in PEP 621 (which I committed in the same repo) and got the following different error:
Preparing isolated env for PEP 517 build...
Requirement already satisfied: pdm-pep517 in /usr/lib/python3.9/site-packages (from -r /tmp/pdm-build-reqs-5f6ukyui.txt (line 1)) (0.5.7)
 - Adding setup.py
 - Adding pdm_name_example-.dist-info/WHEEL
 - Adding pdm_name_example-.dist-info/METADATA
 - Adding pdm_name_example-.dist-info/RECORD
Traceback (most recent call last):
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/resolver/core.py", line 23, in _merge_into_criterion
    crit = self.state.criteria[name]
KeyError: 'pdm-name-example'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/gregdan3/.local/bin/pdm", line 8, in <module>
    sys.exit(main())
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/core.py", line 76, in __call__
    return self.main(*args, **kwargs)
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/core.py", line 131, in main
    raise err.with_traceback(traceback)
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/core.py", line 127, in main
    f(options.project, options)
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/cli/commands/add.py", line 35, in handle
    actions.do_add(
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/cli/actions.py", line 175, in do_add
    resolved = do_lock(project, strategy, tracked_names, reqs)
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/cli/actions.py", line 70, in do_lock
    mapping, dependencies, summaries = resolve(
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/resolver/core.py", line 152, in resolve
    result = resolver.resolve(requirements, max_rounds)
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/resolvelib/resolvers.py", line 453, in resolve
    state = resolution.resolve(requirements, max_rounds=max_rounds)
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/resolvelib/resolvers.py", line 318, in resolve
    name, crit = self._merge_into_criterion(r, parent=None)
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/resolver/core.py", line 25, in _merge_into_criterion
    crit = Criterion.from_requirement(self._p, requirement, parent)
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/resolvelib/resolvers.py", line 79, in from_requirement
    cands = build_iter_view(provider.find_matches([requirement]))
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/resolvelib/structs.py", line 148, in build_iter_view
    matches = list(matches)
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/resolver/providers.py", line 120, in find_matches
    yield from super().find_matches(requirements)
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/resolver/providers.py", line 42, in find_matches
    can.get_metadata()
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/pdm/models/candidates.py", line 169, in get_metadata
    self.wheel = Wheel(built)
  File "/home/gregdan3/.local/pipx/venvs/pdm/lib/python3.9/site-packages/distlib/wheel.py", line 173, in __init__
    raise DistlibException('Invalid name or '
distlib.DistlibException: Invalid name or filename: 'pdm_name_example--py3-none-any.whl'


Heap-alloc-free Model Nodes, Growable Model Containers

Sorry for the monster PR 👹
Concerns the following issues:

#18 (Resolved)
#19 (Resolved)
#20 (Resolved)

Can you push again? CI was not triggered for some reason…

Some numbers from bulk performance testing from NDS MapViewer (512 tiles, 131523 Features) using perfect initialCapacities for arrays/objects:

Model got 11-15% bigger
Query performance seems to be unchanged. This is unexpected, I would have thought that the removed heap allocs have an effect.  This ArrayRange could then be used in the Node::iterate() impls. This will remove the overhead from the head/continuation chunk lookups for every at() call.

With arena::iterate():
32: Query typeof Recursive                         100             1     4.02004 s
32:                                         38.5438 ms    38.4231 ms    38.6848 ms
32:                                         661.456 us    543.953 us    822.811 us
32:
32: Query field id Recursive                       100             1     2.87265 s
32:                                         28.6523 ms    28.5987 ms    28.6979 ms
32:                                         251.096 us    213.424 us    304.459 us
32:
32: Query field id                                 100             1    53.2869 ms
32:                                         527.767 us    523.889 us    537.298 us
32:                                         28.7552 us     8.7424 us    50.7735 us

I created #38 and #39 to hold on to some ideas for further performance improvements.


update and reads users from the zuri core

This API endpoints to update by id and read data from zuri core.
Issue #380
Test Link for reading data
https://chess.zuri.chat/api/dbRead
[
Method : GET,
payload: None
]
Test Link for updating data
https://chess.zuri.chat/dbUpdate/:id
(e.g id =6132727ba921b9ec34e20331)
[
method : PUT,
payload : {
"organization": String [required],
"userName": String [required],
"wins": Number [required],
}
]

who requested you to work on this?

who requested you to work on this?

from the backend


Tighten mouse and keyboard events for opening and closing the combobox

The combobox should ignore the following keys when focused and not open:

arrow left
arrow right
meta keys (fn, shift, command, alt, etc)
tab
capslock

When already open, the following actions should close the combobox:

hitting escape
hitting enter
clicking an item
clicking outside of the box
hitting alt+arrow up

PR #16


Convert NULL values to NaN when reading into pandas DataFrames

This is a feature request (however, the current behaviour can lead to bugs as in the example above).
One consequence of SQL->CSV->DataFrame conversion is that NULL values are converted into empty strings:
dolt_database> SELECT * FROM mytable;
+----+---------+---------+
| id | name    | comment |
+----+---------+---------+
| 1  | Alice   | A       |
| 2  | Bob     |         |
| 3  | Charlie | NULL    |
+----+---------+---------+

In [16]: df = read_pandas_sql(dolt, "SELECT * from mytable")

In [17]: df
Out[17]:
  id     name comment
0  1    Alice       A
1  2      Bob
2  3  Charlie

In [18]: df.at[1, "comment"]
Out[18]: ''

In [19]: df.at[2, "comment"]
Out[19]: ''

This makes it impossible to differentiate between empty cell contents and NULL values.
With this feature implemented, the expected result would be:
In [22]: df
Out[22]:
  id     name comment
0  1    Alice       A
1  2      Bob
2  3  Charlie     NaN

See https://github.com/dolthub/doltpy/issues/179#issuecomment-1142679492


Ideas for improving Analytics detail

1. So far can't track no-keyword search page views and search-led sales in KMC.
So here have an idea for  improving Analytics detail.
Can improve it =>  track no-keyword search page views and search-led sales in KMC.
The case user visit /search page without a keyword is also normal case. Usually we also need to analytics this case data.
2. So far can't know single keyword's search-led sales detail data.
It would be great if KMC could track search-led sales for individual keywords. Search-led sales will be clearer.
For example:
keyword => search-led sales
'Ray' => USD 144
'Tom' => USD 200
'*' => USD 120
''=>100

I believe the easiest way to accomplish your first request is to use * as the search term. It is a valid search term and allows Klevu to return the most raw results. This is what happens when Klevu displays the trending products. I'm almost positive the algorithm relies on the search term for the context of each request to Klevu, so there can't be ML without a search term outside of *.
Regarding the second request, Klevu does work that way, but only when an individual keyword is used for the search term. The general idea is that searching for "Ray", "Tom", and "Ray Tom" are technically different. Because NLP (Natural Language Processing) is applied, there is no value in treating the individual keywords as different searches. The beauty in my opinion of Klevu's approach is to avoid single keyword based searching when multiple words are used as the search term since the intent could be completely different. For example, looking for a "table lamp" is completely different than searching for a "lamp table". If Klevu treated these as individual keywords a user would see tables when they are looking for lamps and visa versa. I hope this information is helpful.

Hi @jerrypena1
Yes, I also think can use * as the search term. And tried to do it before.

But we can't see the * analytics data on the Klevu dashboard.

Do you confirm it works well?

@canyan1989 I am so sorry, but I missed your last reply. You are correct. I've never heard of showing search-led sales for *, but I would contact Klevu support to see if that is possible. If it is not, my next suggestion would be to submit it as a feature request within Klevu's admin (KMC) as this sounds like a valid use-case to me.


Update CI workflow

Codecov Report
Patch and project coverage have no change.

Comparison is base (943e6b0) 100.00% compared to head (c530a28) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #313   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           14        14
  Lines         1304      1304
  Branches       149       149
=========================================
  Hits          1304      1304

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Cloud publishing with CLI step-by-step on front page

When visiting the site I want an overview of how I use Flowershow to publish my stuff so that I have a better idea how to use it and if i want to use it

Have your content on disk
Download flowershow app/cli (npm install flowershow or even npx flowershow publish or download it)
In your directory run flowershow publish [filename]
Get a response like: live at https://xyz.flowershow.sites/

Inspiration from https://www.contentlayer.dev

Acceptance

[X] Front page has a step by step guide even with bullet points and headings **✅ 2022-08-17 basic version - How it works section with 3 steps **
[x] Nicely illustrated like contentlayer (Bonus)

@rufuspollock I've created a very simple version of it with 3 steps, you can see it live

@olayway looks good - now we can make it fancy 😄

@olayway this was what we could term "cloud" publishing. I think we could do the same for self-publishing given feedback in e.g. #119. Opened new issue for that in #125 and clarified title of this issue.


Fix: Correct Footer Display in MoneyRequestConfirmationList Component

Details

Fixes footer display condition in MoneyRequestConfirmationList component to ensure correct rendering when editing
Fixed Issues

$ https://github.com/Expensify/App/issues/39559
PROPOSAL: https://github.com/Expensify/App/issues/39559#issuecomment-2066409074
Tests

Validate Footer Display:

Create a request of each IOU type (send, split, request, track-expense) using both manual, scan, and distance request types.
Verify that the footer (Confirmation/Next button and formError if validation error occurs) is visible on the Confirmation Page for each request type.
Ensure the footer is not visible on the Request Details Page, except for Scan SplitBill.

Edit Scan SplitBill:

Create a Split Bill request in Scan mode.
Confirm that the footer is visible in the SplitBillDetailsPage.
Ensure all fields are editable and the "confirmation button" works.

[x] Verify that no errors appear in the JS console

Offline tests

Same as Tests
QA Steps

Same as Tests
PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

@eh2077 PR ready for review. Thank you!

@brunovjk Can you add Screenshots/Videos?

@brunovjk Can you add Screenshots/Videos?

Sure :D give me a moment. What did you about the Test Steps here?

@brunovjk Can you add Screenshots/Videos?

Sure :D give me a moment. What did you think about the Test Steps here?

They look good! I think you can just test all flows on web and pick up one random case to test on other platforms.

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

@eh2077 I believe that the next Deploy Checklist will be focused soon, do you think we should/can warn about this error, before the QA team reviews the first PR?

@brunovjk Just want to confirm - only this flow Split expense => Scan receipt can be edited, right?

@brunovjk Just want to confirm - only this flow Split expense => Scan receipt can be edited, right?

As far as I know, yes. Do we ask someone else?

@brunovjk Can you update tests and recordings? Please let tag me when you complete them, thanks.
Btw, you can run npx react-native start, open the App from iOS/Android and then trigger reload from terminal - to avoid rebuilding the App every time.

Awesome @eh2077, Im on it.
Thank you very much for the tip.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 1.4.64-1 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 1.4.64-1 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/mountiny in version: 1.4.64-6 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Novel View Synthesis

I appreciate your work, but I have some simple problems.
1.When I use re10k to Novel View Synthesis, I get outputs/test/output/re10k/ file where has lots of files.

The photos in each folder are different, and there are three 256X256 color photos in each folder.
I want to know, are these three pictures the final output of the project? What do they represent respectively?
2.When I use re10k to Pose Estimation, the command
python -m src.eval_pose +experiment=re10k +evaluation=eval_pose checkpointing.load=./pretrained_weights/mixRe10kDl3dv.ckpt<EMAIL_ADDRESS>dataset.re10k.view_sampler.index_path=assets/evaluation_index_re10k.json，mixRe10kDl3dv.ckpt is need to be replaced by re10k.ckpt？
I use re10k.ckpt and program stuck here without moving.

The three images saved in each folder are novel views of our method. The one you show does not work well because it is a dynamic scene and we did not design it for that purpose.
Both mixRe10kDl3dv.ckpt and re10k.ckpt should work. In our paper, we also report results using these two checkpoints. The code is already printing out the AUC results, so it should have completed. I'm not sure why it didn't finish as expected, can you provide more details?

Thinks，it needs time.


cmake: kconfig: llvm: arm64: Add baseline clang/llvm support for arm64/aarch64

This patch aims to establish a baseline level of support for building with clang/LLVM when targeting aarch64/arm64 by:

Making sure clang's --target flag and the -mcpu/-mtune/-mfpu flags are set appropriately when targeting aarch64/arm64
Allowing TLS to be configured when building with clang/llvm as TLS seems to be well supported for aarch64 in clang/lld

Currently, when trying to target arm64/aarch64 with clang in Zephyr I see errors along the lines of error: invalid instruction mnemonic 'mrs' due to the default target in my clang not being aarch64 (and --target not having been set, etc.).

Needs rebase

Needs rebase

Rebased!

Gentle ping.


WIP: Add Snapshot Expiry via TTL to NodeTool

These changes are a current WIP
Summary
This functionality allows users of Cassandra to remove snapshots ad-hoc, based on a TTL. This is to address the problem of snapshots accumulating. For example, an organization I work for aims to keep snapshots for 30 days, however we don't have any way to easily clean them after those 30 days are up.
This is similar to the goals set in: https://issues.apache.org/jira/browse/CASSANDRA-16451 however would be available for Cassandra 3.x.
Functionality
This adds a new command to NodeTool, called expiresnapshot with the following options:
NAME
        nodetool expiresnapshots - Removes snapshots that are older than a TTL
        in days

SYNOPSIS
        nodetool [(-h <host> | --host <host>)] [(-p <port> | --port <port>)]
                [(-pw <password> | --password <password>)]
                [(-pwf <passwordFilePath> | --password-file <passwordFilePath>)]
                [(-u <username> | --username <username>)] expiresnapshots [--dry-run]
                (-t <ttl> | --ttl <ttl>)

OPTIONS
        --dry-run
            Run without actually clearing snapshots

        -h <host>, --host <host>
            Node hostname or ip address

        -p <port>, --port <port>
            Remote jmx agent port number

        -pw <password>, --password <password>
            Remote jmx agent password

        -pwf <passwordFilePath>, --password-file <passwordFilePath>
            Path to the JMX password file

        -t <ttl>, --ttl <ttl>
            TTL (in days) to expire snapshots

        -u <username>, --username <username>
            Remote jmx agent username

The snapshot date is taken by converting the default snapshot name timestamps (epoch time in miliseconds). For this reason, snapshot names that don't contain a timestamp in this format will not be cleared.
Example Use
This Cassandra environment has a number of snapshots, a few are recent, and a few outdated:
root@cassandra001:/cassandra# nodetool listsnapshots
Snapshot Details:
Snapshot name Keyspace name  Column family name True size  Size on disk
1529173922063 users_keyspace users              362.03 KiB 362.89 KiB
1629173909461 users_keyspace users              362.03 KiB 362.89 KiB
1629173922063 users_keyspace users              362.03 KiB 362.89 KiB
1599173922063 users_keyspace users              362.03 KiB 362.89 KiB
1629173916816 users_keyspace users              362.03 KiB 362.89 KiB

Total TrueDiskSpaceUsed: 1.77 MiB

To validate the removal runs as expected, we can use the --dry-run option:
root@cassandra001:/cassandra# nodetool expiresnapshots --ttl 30 --dry-run
Starting simulated cleanup of snapshots older than 30 days
Clearing (dry run):<PHONE_NUMBER>063
Clearing (dry run):<PHONE_NUMBER>063
Cleared (dry run): 2 snapshots

Now that we are confident the correct snapshots will be removed, we can omit the --dry-run flag:
root@cassandra001:/cassandra# nodetool expiresnapshots --ttl 30
Starting cleanup of snapshots older than 30 days
Clearing:<PHONE_NUMBER>063
Clearing:<PHONE_NUMBER>063
Cleared: 2 snapshots

To confirm our changes are successful, we list the snapshots that still remain:
root@cassandra001:/cassandra# nodetool listsnapshots
Snapshot Details:
Snapshot name Keyspace name  Column family name True size  Size on disk
1629173909461 users_keyspace users              362.03 KiB 362.89 KiB
1629173922063 users_keyspace users              362.03 KiB 362.89 KiB
1629173916816 users_keyspace users              362.03 KiB 362.89 KiB

Total TrueDiskSpaceUsed: 1.06 MiB

Next Steps
To be completed:

Tests
Documentation updates

I am a new to this repository, and am fuzzy on a few details even after reading the contribution guide 😅 Any advice on the following would be greatly appreciated!

What branch would this type of change be merged into? Currently, I'm targeting apache:trunk by default
Is there a test strategy/pattern for this type of change? I was not able to find any existing tests for similar nodetool commands

Thanks! 😄

This looks to be a very useful addition for operators. 👍
For posterity, I'm posting my suggestions here from ASF Slack:

log a ticket here https://issues.apache.org/jira/secure/CreateIssue.jspa?pid=12310865 with details of your proposal
then post the ticket + details to the dev@ mailing list so you'll get better traction
you might also want to post in #cassandra-dev and request someone to mentor/coach you on your first contribution so it's a smoother process

Cheers! 🍻


Updated max nimble supported os version to 5.3.2

Signed-off-by: vidhut-kumar-singh<EMAIL_ADDRESS>

Its a README.md file update

thanks @rkumpf


Update kubeflow common to 0.3.2

As titled, upgrade kubeflow common to 0.3.2.

Coverage remained the same at 71.59% when pulling 4c879588b9af706447f839c02273a9da90482f0e on shaowei-su:shaowei--update-common-0.3.2 into 5f002e4a3377c98d74ab267851fa4536061fcc6c on kubeflow:master.

Coverage remained the same at 71.59% when pulling 4c879588b9af706447f839c02273a9da90482f0e on shaowei-su:shaowei--update-common-0.3.2 into 5f002e4a3377c98d74ab267851fa4536061fcc6c on kubeflow:master.


Fix types resolution for esm and cjs.

Fix exports property in package.json so declaration files are split between import and require.
Add extension to imported files so they can be imported in ESM and CJS mode. See https://www.typescriptlang.org/docs/handbook/esm-node.html
Add script to package.json to rename ESM files so they are not mislabed as CJS files.

Sorry to bother you with this again, but I have been trying to improve my previous PR.
With this configuration, your package will now comply with https://publint.dev/ and https://arethetypeswrong.github.io/


[Feature] Function Tooling

Motivation
This PR provides support for function calling #2429 . Currently function tooling implemented for tokenizer apply_chat_template. Streaming not support as well for function tooling.
Modifications

Checklist

[x] Format your code according to the Contributor Guide.
[ ] Add unit tests as outlined in the Contributor Guide.
[x] Update documentation as needed, including docstrings or example tutorials.

Based on the communication in Slack, I have left some of my review comments. 😄
Would @Ying1123 please assign an official reviewer? Thank you!


fix(custom-mocking): reverse pattern matching

Released: v0.2.0 🎉
This has been released in v0.2.0!

📄 Release notes
📦 npm package

Make sure to always update to the latest version (npm i mocktory@latest) to get the newest features and bug fixes.

Predictable release automation by @ossjs/release.


Add Emmet Mode

I was wondering if you could add an emmet mode, or explain to me exactly how to load ace's ext-emmet. Either would work.
I find loading requirejs modules through the JSON configuration mode hard to understand (as in what modules would actually work). Maybe you could add a list of requirejs modules compatible with Zed (as from what I understand you have an extra layer over ace that is Zed, so I can't exactly use any ace module).
Thanks

+1. Any quick fixes for this, anyone?


added 2022 lineup - new devices (14, 14 Pro, 14 Pro, 14 ProMax)

This PR adds the 14, iPhone14Plus,  iPhone14Pro, and iPhone14ProMax devices for snapshot testing.
I took the numbers for the device config from: https://useyourloaf.com/blog/iphone-14-screen-sizes/
I believe the traits should be the same as iPhone 13

It would be great to get this merged to get the new devices! Any idea of what is holding this up? 🤔

Can we get this reviewed or merged?

Can we get an update on when this change will be merged in and if the plan is to continue to actively maintain this library as there hasn't been any merge to master for about 6 months now.

Can we get this merged in order to support iPhone 14?

@stephencelis I see you have merged several other PRs in this repo. Is there a process this PR needs to go through to get merged? Our team is working on updating to the latest devices now and would love to go to iPhone 14 if possible. Thanks!

Is this library a dead project?

@mbrandonw / @stephencelis is Point-Free still maintaining this repo?

Hi @tinder-owenthomas, yes we do maintain this repo, and merge pull requests that we think are important. However, this project, more so than any of our others, has parts that need constant updating due to Apple's release schedule, and it's just not feasible to keep up-to-date with it all the time.
For example, even in this PR we think there are potentially some mistakes, such as having forceTouchCapability set to .available even though it seems that 3D touch hasn't been supported on Apple devices for a very long time. And it's probably just copy-pasta from other parts of the library, but keeping track of all of these nitty-gritty details in Apple's ecosystem doesn't really seem like a good responsibility for this library.
Further, we feel that a lot of these little utilities can be implemented outside the library, and probably should be. For example, the contents of the PR can be copy-pasted into any project. It does not require any internals from the library. The fact that we haven't yet merged this PR should not hold anyone up from bringing it into their own projects. And the same is true of almost all of the snapshot strategies that are very difficult to maintain in the face of Apple's ever changing frameworks and bugs.
In the end we'd like to evolve this library into a state where nearly all of the strategies are moved out into separate projects, largely supported by the community, so that all that is left is the core of the snapshotting tools.

So you won't be adding the support for the iPhone 14 devices?

Hi @rfodge, we are open to merging it, but there are some potential problems with it currently, such as auditing the usage of forceTouchCapability, and making sure all of the other properties are correct.
But I want to re-iterate that the library does not need to support these devices. The ViewImageConfig type is a public struct with a public initializer. It is just a few fields for describing a few aspects of the view. I think it would be perfectly reasonable for you to define static lets for the few device configurations you support in your project, and to not depend on us keeping a 100% accurate list of devices in this library.

Ok I will give that a try thank you for the quick response

Half a year has passed :(


Move olx.layer.* to ol/layer/*

Continuation of #8016, move the remaining ol.layer.* externs to ol/layer/*, see #7947 for an overview of this ongoing work.
Last commit: Fix setting of the useInterimTilesOnError in ol/layer/VectorTile.
Notes
All default values were moved from documentation text to the JSDoc syntax [opacity=1], which will be supported for documentation generation according to https://github.com/openlayers/openlayers/issues/7838.
Sometimes this would lead to minor changes in the documentation text, e.g.

Preload. Load low-resolution tiles up to preload levels. By default preload is 0, which means no preloading.

was transformed to

Preload. Load low-resolution tiles up to preload levels. 0 means no preloading.

Questions
Other things I stumbled over while working on this, not necessarily to be addressed in this PR, but I would by happy to get some feedback from someone more familiar with ol:

The options Object is optional everywhere except for ol/layer/Base and ol/layer/Layer, but neither of them have any mandatory options-attributes. Should the options Object be optional everywhere?
Is there a preferred order for attributes in the Options typedefs? I was currently following more or less the existing order and generally putting all inherited options first for easy copy-pasting.
Minor: Is there a preference for putting one or two spaces after periods in documentation text?

Closing and re-opening to trigger new CI build, tests were passing locally...

@romanzoller, answering your other questions:

The options Object is optional everywhere except for ol/layer/Base and ol/layer/Layer, but neither of them have any mandatory options-attributes. Should the options Object be optional everywhere?

Good question. Since both layer/Base and layer/Layer are base classes that are not used for anything but extending them, it does not matter. For any class that can be constructed in an application, options should be optional when an instance can be created without any option.

Is there a preferred order for attributes in the Options typedefs? I was currently following more or less the existing order and generally putting all inherited options first for easy copy-pasting.

We should sort options by importance, i.e. those that are mandatory or recommended first, and those for special configuration cases last. This does not need to happen as part of this current effort, but should be done eventually.

Thanks fo working on this, and for the good summary of the changes you made. I'm reviewing in detail now.

Thanks for the quick review and for the clarifications @marcjansen and @ahocevar!


Started website

Description
Started a website to contribute towards #2
Todo:

[x] Basic landing page
[x] Hugo skeleton
[ ] Populate Hugo page with more content
[ ] Use CI to automatically generate API reference
[ ] Use CI to build Hugo pages
[ ] Use CI to deploy final site to GitHub Pages

Superseded by #483


export of Executive dashboard group for importing and minor tweaks

This includes an export of the dashboard group for those not using terraform.
Also some minor color and typo fixes.

I have read the CLA Document and I hereby sign the CLA


Fix Unicode character literal

Github issue https://github.com/Shopify/yarp/issues/569
Changes:

add error when \u{nnnn} contains more than 6 digits
add error when \u{nnnn} contains not hexadecimal characters
add error when ?\u{nnnn} literal contain more than one codepoint (e.g. ?\u{0000 0001})

Also wondering if there should be added some new tests.
I suppose a proper place for them is a test/errors_test.rb file.

Done.


perf: add fts index to snippets table

Description

Adds a full-text search index to the snippets table that we had on the old production DB.
@remy was reporting performance hits using the new DBs, we identified this as the probable culprit.
The snippets table we're applying this too is pretty hefty, but as we're not writing to it it shouldn't be an issue.

Issue(s)
Fixes #ENG-985
How to test

Once applied to production, test the transcripts API route on the Open API.

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


Fatal error [getReports]: Line 4: Illegal return statement - Mac OS X

Executing:
cr  --forin --trycatch --newmi --filepattern '(?:app(?!\/vendor)|test\/*)[\/\w]*\.js' -m 10 .

I get only this error:
Fatal error [getReports]: Line 4: Illegal return statement
Mac OS X 10.9

Closing due to lack of feedback, but feel free to reopen and comment if there's still an issue.


Migrate to .NET 6.0 and packages upgrade.

Thanks, @RWander

Thank you, @ernado-x.
Could you please make a new release?


Visual Studio Code pins CPU when invalid CSS entered

VSCode Version: Code 1.17.0 (be377c0faf7574a59f84940f593a6849f12e4de7, 2017-10-05T06:07:51.906Z)
OS Version: Darwin x64 17.0.0
Extensions:

Extension
Author (truncated)
Version

vscode-docker
Pet
0.0.18

Steps to Reproduce:
I believe this happened twice today (I used Code for about 12 hours.)
Entire OS grinds to a halt. Mouse cursor still moves, nothing receives clicks. Fan begins to ramp up like an aircraft taking off. Had just entered wavy-green-underlined code in a div element. Forced to do hard restart of machine.

Reproduces without extensions: Yes/No

Given the above steps this is difficult to analyze.  The next time it happens can you please try to find out which process is causing this.
To find out more about this issue, we need to get at the process that is causing the high load. VS Code creates multiple processes, each with different tasks. Depending on your OS you can get at the full command line of the process and paste it here. On Mac, the Activity Monitor allows to find the PID of the process and from a terminal ps aux | grep <pid> reveals its arguments.

Once you have the information please update this issue with it. Thanks!

@jonathanapp can you share the CSS file and describe what the invalid CSS was?

When it freezes, the UI and entire OS become unresponsive (even the clock stops ticking).
I'm going to try to reproduce with a simple example...

This might be of use:
Code Helper_2017-10-09-205304.crash.txt

@jonathanapp thanks for the additional info. So did it happen to you with 1.18 again?
Adding @bpasero for his insights.

After experiencing this (almost) every day and doing more research, I'm now confident this is a issue introduced in macOS High Sierra issue that can be triggered by any UI doing decent amount of rendering. I was seeing it often with Code simply because Code was my top-level app.
For those who are curious: there are system reports named "WindowServer_YYYY_MM_DD_[...].userspace_watchdog_timeout.spin" for every instance the OS grinds to a halt and becomes unresponsive. Others have experienced similar issues. I've tracked down a 3rd party display kext (DisplayLink) and removed it; I believe this (or another) extension is now incompatible with High Sierra.
Sorry for any confusion, this is the most vexing issue I've experienced in a couple years at least!

Top stack from Electron seems to be this:
gl::GLFence::Create() (in Electron Framework) (gl_fence.cc:61)
gpu::ImageTransportSurfaceOverlayMac::SwapBuffersInternal(gfx::Rect const&) (in Electron Framework) (image_transport_surface_overlay_mac.mm:221)
gpu::ImageTransportSurfaceOverlayMac::GetFormat() (in Electron Framework) (image_transport_surface_overlay_mac.mm:307)
gpu::gles2::GLES2DecoderImpl::HandlePostSubBufferCHROMIUM(unsigned int, void const volatile*) (in Electron Framework) (gles2_cmd_decoder.cc:11832)
gpu::error::Error gpu::gles2::GLES2DecoderImpl::DoCommandsImpl<false>(unsigned int, void const volatile*, int, int*) (in Electron Framework) (gles2_cmd_decoder.cc:5278)


0535-encode-and-decode-tinyurl.java

File(s) Modified: 0535-encode-and-decode-tinyurl.java
Language(s) Used: java
Submission URL: _https://leetcode.com/problems/encode-and-decode-tinyurl/submissions/860047904/_

Thanks!


Auto Closing Overtype option should work for HTML tags too

There is "Auto Closing Overtype" option to control overtype behavior for autocompleted quotes and brackets. It should be applied to all "bracket-like" sequences like HTML tags. Currently there's no way to overtype auto-closed tags (or I couldn't find one).
On additional note, "overtype" should be enabled by default for every and all autocompleted text for consistent typing behavior.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

I think we need editor support for this
The HTML auto insert features (auto-close, auto-quote) have both the same problem.
They use the insertSnippet API to insert some smartness. If the user doesn't pay attention and types exactly the same thing (or the beginning of if), the snippet should be removed again.

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Integrate react test framework

For epic #1
Determine the test framework to be used and integrate within the template.

Added test framework (Jest) & libraries (react-test-library, react-test-renderer). Everything seems to be working as expected. PR into dev & stage has been completed, so this story is done.
Created #11 and #12 as follow-ups.


Be able to connect using a self signed certificate

The app now only lets you connect if you have a valid certificate installed on your TIP. Please make a options to also allow self signed or other wise "invalid" certificates. This used to be an checkbox in the old app. This is especially useful in a test setup.
Same change as https://github.com/eclecticiq/intelligence-center-app-splunk-ta/issues/19

Hi Folks, I just wanted to clarify that there is more than one solution here and we should be aiming for the most secure option.
They are as follows:

Allow the admin to manually import a CA cert or self-signed certificate (e.g. a PEM / DER file) and have it be added to the trusted-certs / CA bundle used by the App going forward. The cert can also be removed from the bundle as needed.

Allow the admin to enter a https:// URL for the TIP and have the App fetch the certificate to be trusted using a once-off TLS request that is manually invoked by the admin. This cert is then added to the trusted-certs / CA bundle used by the App going forward. The cert can also be removed from the bundle as needed. In theory an attacker could intercept this request, but they would only have one chance and would have to be ready for it. Bonus points for allowing the admin to inspect the new cert before saving it. This option is the best compromise between security and convenience for the user.

A check-box to ignore TLS warnings and trust any cert. This should ONLY be used for testing and should carry a strong warning. This is the least secure option and opens the App up to potential MITM attacks in production.

If we only support one option, I would suggest we go with option 2, allowing the admin to inspect the cert before saving it.

For the option 2 you mentioned. So will there be a separate URL where the certificate (.pem file ) will be kept and with certain credentials does it need to be downloaded?

Also can I have any such url so that I can download the cert and check for testing.

@puja-sacumen The certificate chain would be extracted directly from a TLS connection initiated by the App to the TIP server.
The hostname of the TIP server should already be configured and stored somewhere in the App.
Having the ability to manually supply a PEM cert-chain via pasted-text, URL fetch, or file-upload, would be closer to option 1.

To confirm in the interests of transparency, we have decided to go with option 2:
https://github.com/eclecticiq/intelligence-center-app-qradar/issues/26#issuecomment-1303785501

fixed in 6e44b00


adding cluster and fleet agent overrides to automation framework

Issue:

https://github.com/rancher/rancher/issues/41035
Problem

new variables were added for cluster and fleet agent.
After looking at existing code, new features like this will not scale in the existing create funcs
lastly, some k8s native resources were causing trouble, most likely due to not including yaml in the struct parameter definitions. Specifically for affinity.
Solution

I had to take a similar approach to what was done for hosted clusters in order to get cluster customization to read in properly
this is also introducing the advancedOptions variable (discussed this approach with Israel before completing this PR)

Testing

local testing - done with all variables included with a preferred node scheduling affinity
Engineering Testing
Manual Testing

Automated Testing

tbd: will include jenkins runs for:
fresh install (no variables)
fresh install, all new variables

with node affinity
with pod affinity
with pod antiaffinity

QA Testing Considerations

Regressions Considerations

yes, this is a new feature that won't be backported to 2.6, since it is EOM


Please update dependency

Node version (or tell us if you're using electron or some other framework):
18.20.2
ShellJS version (the most recent version/Github branch you see the bug on):
0.8.5
Operating system:
Windows
Description of the bug:
npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported

It seem inflight was dependency of glob@7 so maybe just need update to glob@10 ?
Example ShellJS command to reproduce the error:
npm install shelljs

Duplicate of issue #1149


How to modify the code to get a single point(x,y) tracking?

This code uses meshgrid to generate N no. of points.
How to modify it to track a single 2d point(x,y) and save trajectories into an .mp4 file ?

I was able to do this myself simply by replacing the meshgrid generated points with a mouse clicked set of points.


Modify run tests

This allowed me to run run_tests.py all the way through counting the errors as it went.  This combined with #21  should fix the tests error we were seeing.

This was was also fixed in #26, so I'm going to close this.

sounds good. yes, fine to delete the branch.


request: provide a way to set labels on the machines created by the controlplane provider

when creating a machine deployment in cluster-api one can set labels on the created machines by specifying them in .spec.template.metadata. it would be nice if we could do something similar for the controlplane machines created by the k3s controlplane provider.
it would be nice if controlplane machines could be created as MachineDeployments in order to benefit from MachineHealthChecks, however that's a separate discussion. given they are now created as Machines i propose we add a MachineLabels map[string]string optional field to the KThreesControlPlaneSpec and set them onto the created machine in generateMachine().
@zawachte if you prefer a different approach let me know, otherwise i'll get started on a PR to do this.

high level looks go to me. I just want to double check how its being done for kubeadmcontrolplane.
On the control plane machine as machine deployment topic, I don't think we want to go that route as it diverges too much from how the kubeadmcontrolplane works. We probably need to just implement the proper logic in this controlplane provider to get MHCs working.

Maybe we should follow their pattern of using a ObjectMeta as the struct to pass in the labels? https://github.com/kubernetes-sigs/cluster-api/blob/8ba3f47b053da8bbf63cf407c930a2ee10bfd754/controlplane/kubeadm/api/v1alpha4/kubeadm_control_plane_types.go#L93C2-L93C67

Maybe we should follow their pattern of using a ObjectMeta as the struct to pass in the labels? https://github.com/kubernetes-sigs/cluster-api/blob/8ba3f47b053da8bbf63cf407c930a2ee10bfd754/controlplane/kubeadm/api/v1alpha4/kubeadm_control_plane_types.go#L93C2-L93C67

I agree, following the conventions setup out by KCP would be a good approach. However, this would require a new API version (i.e. v1beta2) as it would require changing KThreesControlPlaneSpec so that InfrastructureTemplate is moved into a new struct. With a bump in API version thsi would enable conversion webhooks so that the old version can be converted automatically.

Maybe we should follow their pattern of using a ObjectMeta as the struct to pass in the labels? https://github.com/kubernetes-sigs/cluster-api/blob/8ba3f47b053da8bbf63cf407c930a2ee10bfd754/controlplane/kubeadm/api/v1alpha4/kubeadm_control_plane_types.go#L93C2-L93C67

I agree, following the conventions setup out by KCP would be a good approach. However, this would require a new API version (i.e. v1beta2) as it would require changing KThreesControlPlaneSpec so that InfrastructureTemplate is moved into a new struct. With a bump in API version thsi would enable conversion webhooks so that the old version can be converted automatically.

I agree @richardcase. This should be the north star. But can we figure out a way to split the difference until we are ready to take an api version bump? For now, can we stick ObjectMeta in an "undesirable" place while we maybe begin to think about what a new apiversion would look like?

Cool I'll do this 👍 thanks

On the control plane machine as machine deployment topic, I don't think we want to go that route as it diverges too much from how the kubeadmcontrolplane works. We probably need to just implement the proper logic in this controlplane provider to get MHCs working.

Ah okay. Sounds good to me. I was mistaken in thinking that MHCs required MDs 👍 happy to contribute to this work at some point

i have taken this intermediate approach that avoids the version bump by mimicking what kubeadm does. i understand that this additional spec field should someday go somewhere else. hopefully this is the middle-ground you're looking for.
https://github.com/cluster-api-provider-k3s/cluster-api-k3s/pull/59

This should be the north star. But can we figure out a way to split the difference until we are ready to take an api version bump? For now, can we stick ObjectMeta in an "undesirable" place while we maybe begin to think about what a new apiversion would look like?

Thats a good point @zawachte. Off the top of my head there are a couple of ways to do this:

It could be added directly to KThreesControlPlaneSpec
It could be added to a new KThreesControlPlaneMachineTemplate along with the InfrastructureRef. This would then introduce a duplicate InfrastructureRef but you could part the existing one as deprecated and also add validation to the webhooks to ensure that users don't supply values for both.

I didn't see an issue to track future API changes so i created #62


deleting already existing files

making changes to the stop_container.sh/scripts  to delete already existing files

changing the stop_container.sh file


Chrome v.66: Invalid regular expression: /(^|.)slick.(?:.*.|)slick-0(.|$)/: Stack overflow

General Info
In Google Chrome v.66 independent from JQuery version I face next error:

Uncaught SyntaxError: Invalid regular expression: /(^|.)slick.(?:.*.|)slick-0(.|$)/: Stack overflow>
at RegExp.test ()
at Object.remove (jquery.min.js:3)
at jquery.min.js:3
at Function.each (jquery.min.js:2)
at r.fn.init.each (jquery.min.js:2)
at r.fn.init.off (jquery.min.js:3)
at c.b.cleanUpEvents (slick.min.js:17)
at c.b.destroy (slick.min.js:17)
at c.b.refresh (slick.min.js:17)
at c.b.checkResponsive (slick.min.js:17)

More Details

Jquery/Browser
Chrome50
Chrome66
Firefox

jquery 1
n.a.
no
yes

jquery 2
n.a.
no
n.a.

jquery 3
yes
no
yes

I used Slick 1.6.0 and also last version from npm.
I also tryed on two different PCs with Win7 and Win10 in two different networks and places.

I fogot one important detail - the problem occures in mobile mode of DevTools or on mobile phone.

Has someone found a solution to this?

Hey @LevShipulin, can you reproduce this in all browsers?
I experience it only in Chrome (v. 67). However, the exception is not thrown in incognito tabs, which leads me to thinking this is caused by some of the Chrome Extensions.
Hope this helps.

Hi @coasterka, no, only in Chrome (v. 66 and above) and unfortunately in inconito tabs also.
I also tryed it on real mobile phone and fresh intalled Chrome - same issue.
At the same time in Firefox works everywhere. In Safari browser with some style issues.
In old Chrome version (v. 50) also issue dooes not occures.
One more interesting detail I found: it works great if you just resize the browser window.

@LevShipulin I don't know the specific details of your situation, but here is my workaround for this issue, maybe it will work for you too. It worked like a charm for me.
I have multiple slick carousels on a single page (around 40). Each of them is initialized in the same way - with multiple responsive breakpoints.
Since the issue was appearing on window resize, my solution is to 'unslick' every carousel while resizing, and then, when the resizing has stopped, slick it again with the same settings. I've had no worries since then.
More info on the 'resizing stopped' event here

Any news on this?

Yes this issue is happening with me too. Very annoying.

Also i had this weird issue and i added the "overflow:hidden" style to the parent element that contains slider and error is gone.


how istio gateway and virtualservice support  cookie and request arg_xxx

(This is used to request new product features, please visit https://discuss.istio.io for questions on using Istio)
Describe the feature request
Describe alternatives you've considered
Affected product area (please put an X in all that apply)
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Additional context
according the official document，gateway and virtualservice support url route rule，but how i  can set the route rule according the request agrs or request cookie. and  satisfied request agrs  and request cookie at the same time

https://istio.io/docs/reference/config/networking/v1alpha3/destination-rule/
//
// The following example sets up sticky sessions for the ratings service
// hashing-based load balancer for the same ratings service using the
// the User cookie as the hash key.
//
// ```yaml
//  apiVersion: networking.istio.io/v1alpha3
//  kind: DestinationRule
//  metadata:
//    name: bookinfo-ratings
//  spec:
//    host: ratings.prod.svc.cluster.local
//    trafficPolicy:
//      loadBalancer:
//        consistentHash:
//          httpCookie:
//            name: user
//            ttl: 0s
// ```


[feature] Support duplication checking.

When import new URL, delete duplicated import?

This seems to be broken if the existing URL has a filter added. When imported, the app adds the same URL multiple times.

can anyone supply the issue with some actual concrete information?
version, platform, etc etc
exact steps to reproduce
@kazerniel

Python on Windows
app v0.45.9
steps that ended in the bug for me:

add an URL
add a filter to it
go to import the same URL either as xlsx or via the textarea
the app creates a duplicate entry

It seems not to happen if the URL didn't have a filter when re-imported.


WIP k8s integration fixes

Fixes to serviceSchema generation
Data serializer for service
serviceEvent processing: Locate service/env by rancher uuid first, if not set, use externalId

Closing the PR as we've decided to go with another rancher-k8s sync model


Enhancements

These are some small changes that i would really like
Give type information of the dumped NetVars/Schemas.
Some Examples:
m_pWeaponServices       = 0x968(CPlayer_WeaponServices*)
m_pMovementServices   = 0x9A8(CPlayer_MovementServices*)
v_angle                           = 0x9B8(QAngle)
m_iHideHUD                   = 0x9D4(uint32)
Add another optional arg to get rid of the timestamps useing println! instead of !log::info

Thanks, added in 6d04af2758b0f6cc7243c786a05e0cac2997cecd
For printing verbose messages, you can now pass the -v or --verbose flag.


AMD module built with webpack serve returns undefined (Webpack 5 only)

Bug report

What is the current behavior?
When using webpack serve the defaut AMD module returns undefined.
If the current behavior is a bug, please provide the steps to reproduce.

Webpack config is very simple:
const path = require("path");

module.exports = {
  entry : path.join(__dirname, "src/index.js"),
  output : {
    path : path.join(__dirname, "dist"),
    filename : "main.js",
    libraryTarget : "amd",
    libraryExport : "default"
  }
};

And main.js also:
export default {
  foo : "bar"
};

Clone https://github.com/yvele/webpack-5-amd-devserver
Then
npm install
npm run build
npm run start

The AMD module built with webpack works as expected.
The AMD module built with webpack serve return undefined.

I also tried to set inline to false and deactivate hot.. But still lots of code if injected and the AMD module returns undefined with webpack serve.
Note that I don't have the bug with Webpack 4.
What is the expected behavior?
webpack serve should build a valid AMD module.

Other relevant information:
webpack version:  5.8.0
webpack-cli version:  4.2.0
webpack-dev-server: 3.11.0
Node.js version: 12.19.0
Operating System: macOS 10.15.7
Additional tools:
  System:
    OS: macOS 10.15.7
    CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
    Memory: 1.84 GB / 16.00 GB
  Binaries:
    Node: 12.19.0 - ~/.nvm/versions/node/v12.19.0/bin/node
    npm: 6.14.8 - ~/.nvm/versions/node/v12.19.0/bin/npm
  Browsers:
    Chrome: 87.0.4280.67
    Firefox: 81.0.2
    Safari: 14.0

Fixed, please try webpack-dev-server@4

Thanks!
But hum.. is there any workaround or any related webpack-dev-server issue where I can maybe find a workaround by myself?
The problem is that<EMAIL_ADDRESS>is so breaking.. and lacks of documentation.. It's nearly impossible to switch to<EMAIL_ADDRESS>🤔

No workarounds, only migrate on<EMAIL_ADDRESS>(what is so breaking?)

Ok everything works fine with<EMAIL_ADDRESS>👌
(lots of options has changed and there is no documentation.. but I figured out, thanks!)


Failing at 22/31 - iOS 12.4 iPhone SE (see logs)

Not sure what the issue is, please see logs for more details
To Reproduce
Steps to reproduce the behavior:

Go to 'Unc0ver.'
Click on '..exploit.'

Device (please complete the following information):

iOS Version: 12.4
iOS Device: 5SE
unc0ver Version: latest

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce
[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled
[ ] this issue is present after a rootfs restore
[X ] this issue is present on the latest version of unc0ver

[] runCommandv(1042): Removing net.angelxwind.appsyncunified (8.2) ...
[] runCommandv(1042): dpkg: error processing package net.angelxwind.appsyncunified (--remove):
[] runCommandv(1042):  subprocess installed pre-removal script was killed by signal (Killed: 9)
[] runCommandv(1042): dpkg: error while cleaning up:
[] runCommandv(1042):  subprocess installed post-installation script was killed by signal (Killed: 9)
[] runCommandv(1042): Removing org.coolstar.cctools (895) ...
[] runCommandv(1042): Removing tcpdump (3.9.8-4) ...
[] runCommandv(1042): Errors were encountered while processing:
[] runCommandv(1042):  net.angelxwind.appsyncunified
[] runCommandv(1042): W: Unable to read /etc/apt/''/ - DirectoryExists (2: No such file or directory)
[] runCommandv(1042): E: Sub-process /usr/bin/dpkg returned an error code (1)
[] runCommandv(1042) completed with exit status 100
[*] Unable to repair system.

Resolved. I think because it was already rooted using 10.3.2 Cydia and there were dependencies the phone couldn't remove. I wiped the phone and it worked fine.


[Catch2] update to 2.13.4

Fix #16938
Update catch2 to the latest version 2.13.4
Note: no feature need to test

Duplicate of #14503


Eliminate as much as possible Python API's manual object lifecycle management

Currently the Python API has a lot of context management and "start"/"stop" pairing directly corresponding to the gRPC C Core's many "X object must be destroy before Y time" semantics.
I think I smell an opportunity to eliminate a lot of that manual object lifecycle management, but I'd have to know a lot more about Python's garbage collection semantics and then turn that knowledge into well-formed and plausible feature requests against the gRPC C Core API.
If this happens at all it will happen in a post-beta time frame.

IIRC, Python's GC doesn't actually 'collect' anything so much as breaks reference cycles at arbitrary locations and lets the __del__ functions run from there. That said, there's no reason for us to necessarily have reference cycles, because the dependencies are basically acyclic in the C core, with temporary 'sibling' dependencies according to events (which can correspondingly be tracked by tags).
I don't think we actually need to make any feature requests against the gRPC C core API to handle this. We'd just need to entirely refactor grpc._adapter and especially make more sophisticated our tagging mechanism.

@soltanmm what's the latest on this issue?

This is addressed as far as the API is concerned; we don't require explicit closing anymore.


Step 5 of certificate rotation procedure is no longer optional

Starting in Ops Manager 2.8, it is now required that operator delete the original certificate authority after doing a certificate authority rotation.
Relevant story: https://www.pivotaltracker.com/story/show/168269283

Looks good. Thank you!


org.zaproxy.clientapi.core.ClientApiException: Invalid or missing API key

Using ZAP_2.4.2 with default configuration and ZAProxy 1.1.8.
Any simple flow ends with the exception mentioned in the title. I can see the ZAP is being started with -config api.key=ZAPROXY-PLUGIN. However, I can't change/set the key value.
The OWASP ZAP documentation mentions a way to disable the key via api.disablekey = true but this doesn't work either.
Editing ZAP's xml/config.xml doesn't seem to work either.

Can you attache a Jenkins log ? This error never occurred to me after the version 1.1.7.

There is a complete stdout from the ZAP job: http://pastie.org/private/jqiinnzmjj3v1z72nxosrw
Jenkins log seems not to contain any ZAP job related info - I have always ran the ZAP job manually.

I m not able to reproduce this error.
can you try to reinstalling zap and zaproxy plugin.

OK, removed the plugin along with the Cusotm Tools one. Restarted Jenkins and now it works as a charm. Thanks

no problem. have a good time.


Make sure Core aware of gevent Cython objects

Fixes #20299

As discussed in https://github.com/grpc/grpc/pull/20874, the root cause of #20299 is gevent doesn't have a chance to clean-up during shutdown.
So, in https://github.com/grpc/grpc/pull/20874, the PR ensures Core gives gevent a chance to clean-up.
In this PR, I ensures Core do not shutdown before all gevent Cython objects go away.

Interesting. Any way we can add a test to verify this fix?


Migration Process Won't Complete

Expected Behavior
I would expect that after migrating to version 10 of Foundry and running with Perfect Vision (PV) that the migration process that is initiated by PV wouldn't fail and log me out of the server.
Current Behavior
After I upgraded to version 10 of Foundry and the latest version of Perfect Vision (PV) (4.0.49) I keep running into problems with the PV migration. It keeps failing with a "websocket.js:143 WebSocket connection to 'wss:///socket.io/?session=<redacted session 1>=4&transport=websocket' failed: WebSocket is closed before the connection is established." error message and boots me out of the server. When I log back on the migration process begins again only to encounter the same problem.
Steps to Reproduce

Update to foundry version 10 (any version)
Update PV
Logon to server
Click on migration button

Context
"websocket.js:143 WebSocket connection to 'wss:///socket.io/?session=<redacted session 1>=4&transport=websocket' failed: WebSocket is closed before the connection is established."
Version
4.0.19
Foundry VTT Version
v10.290
Operating System
Raspbian GNU/Linux 10 (buster)
Browser / App
Chrome
Game System
dnd5e 2.0.3
Relevant Modules
No response

Not sure if this is relevant but here is my module list:
Active Modules:
About Time v;
Active-Auras v;
Active Token Effects v;
Advanced Macros v;
All Goblins Have Names v;
Always HP v;
Ambient Doors v;
Ammo Tracker v;
Arbron’s Improved HP Bar v;
Automatic Journal Icon Numbers v;
Backgroundless Pins v;
Compendium Folders v;
Crash's Automatic Blind Rolls (5e) v;
DFreds Convenient Effects v;
DFreds Droppables v;
DFreds Pocket Change v;
Dice Tray v;
Disable Mouse Wheel Control for Sliders v;
Drag Ruler v;
Dynamic Active Effects SRD v;
Dynamic effects using Active Effects v;
Easy Target v;
Encounter Statistics v;
Enhanced Terrain Layer v;
Follow Me! v;
Force Client Settings v;
Forien's Quest Log v;
Foundry Community Macros v;
Foundry Community Tables v;
FXMaster v;
GM Notes v;
Group Initiative v;
Health Estimate v;
Initiative Quick Change v;
Item Piles v;
Less Fog v;
lib - Color Settings v;
libWrapper v.0;
Maestro v;
Midi QOL v;
Monk's Active Tile Triggers v;
Monk's Little Details v;
Monk's TokenBar v;
Monk's Wall Enhancement v;
Party Overview v;
PopOut! v;
Quick Encounters v;
Quick Insert - Search Widget v;
✋ Raise My Hand v;
Shared Data v;
Simple Calendar v;
Smart Target v;
socketlib v;
Terrain Ruler v;
Tidy5e Sheet v;
Tidy UI - Game Settings v;
Times Up v;
Token Action HUD v;
Token Animation Tools v;
Token Auras v;
Token HUD Wildcard v;
Token Magic FX v;
Token Mold v;
User Latency v;
Weather Control v;

I'm facing the same issue as well.

@maxphoenix01 Does it also disconnect you once you click Migrate Compendium Packs but not before? Is your Foundry version 10.290 too?
How many (how big) compendium packs do you have in your world?

Please try 4.0.50 and let me know whether it fixes the problem.

The issue persists, unfortunately. The update didn't seem to change anything.

Please try 4.0.50 and let me know whether it fixes the problem.

@maxphoenix01 Could you share the complete console log with me?
Also: could you execute this without PV enabled. Paste it in the console and enter. It loads all world compendium packs. I want to make sure loading the packs isn't the issue. Let me know whether that triggers web socket disconnect.
for (const pack of game.packs) {
    if (pack.metadata.packageType !== "world") continue;
    console.log(`Loading ${pack.collection}...`);
    await pack.getDocuments();
    console.log(`Loaded ${pack.collection}!`);
}

for (const pack of game.packs) {
    if (pack.metadata.packageType !== "world") continue;
    console.log(`Loading ${pack.collection}...`);
    await pack.getDocuments();
    console.log(`Loaded ${pack.collection}!`);
}

I ran this command without PV enabled, and I saw the same exact error where I get disconnected from the server.
In regards to the compendiums, I'm not sure how to quantify this, but I do have some pretty large packs. In particular, I have a large (~10,000) monsters in various packs.

@jburrows127 That leaves me wondering how the system's (dnd5e) migration even succeeded, which would have loaded the packs too. You didn't have problems with the system migration, correct?

So it turns out that dnd5e doesn't actually migrate world compendium packs at the moment because of a bug. I'm not quite sure what happens once that is fixed, but I assume either both dnd5e and PV successfully migrate or dnd5e's pack migration will trigger a disconnect too.

for (const pack of game.packs) {
    if (pack.metadata.packageType !== "world") continue;
    console.log(`Loading ${pack.collection}...`);
    await pack.getDocuments();
    console.log(`Loaded ${pack.collection}!`);
}

I ran this command without PV enabled, and I saw the same exact error where I get disconnected from the server.
In regards to the compendiums, I'm not sure how to quantify this, but I do have some pretty large packs. In particular, I have ~10,000 monsters in various packs.

@jburrows127 Did you try this with all modules disabled?

If you haven't tried to run PV's migration with all other modules disabled, do that first. Let me know whether that succeeds.
If the migration failed with other modules disabled: You may manually run the dnd5e world compendium pack migration. Please make a backup before doing this! It should be safe; that's what the system would to at least if it wasn't for this bug. But please make a backup just in case.
for (const pack of game.packs) {
    if (pack.metadata.packageType !== "world") continue;
    await game.dnd5e.migrations.migrateCompendium(pack);
}

Run this with all modules disabled. If you try this, let me know whether it succeeds. If it doesn't, it confirms that this isn't a PV specific problem. Assuming it isn't limited to PV it would preferable to address this problem before dnd5e 2.1.0, which will run this migration and would therefore prevent you from updating to 2.1.0. If it succeeded, try to run PV's migration again and let me know the results.

Thanks for the recommendation on this. I did try originally to do the migration with all other modules disabled, and it still didn't work. However, it's no longer an issue because I ended up refactoring some of my compendiums so they are smaller, which resolved the problem.

Glad you have solved it. I tried to reproduce it by generating gigantic compendium packs. It took forever but I was unable to crash it. I tested it only locally though. I suspect a server with more limited resources and limited bandwidth might refuse/fail to process such a huge request.

dnd5e 2.1.0 was released, which fixed the broken compendium migration of the system. So, if PV's migration broke things for you, @maxphoenix01, it might break on the system level now. So make sure to backup your data before you update the system in case it doesn't work (you should always backup before a system update anyway). This allows you do roll back and reduce the compendium size as @jburrows127 did.


Added the semicolon in the example provided

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Closes #XXXXX

sdhkhd

dhkck

{"body":"jhfbk"}

hi

hd


Misc tweaks

Modules don't need to exist as (tiny) files.
Enums without a non-exhaustive attribute may as well be changed to be copyable.
to_vec copies, but into can reuse existing allocation.

It'd be nice to change &self to self on execute to avoid copying in other cases.

Thanks for the PR, looks like some tests are failing. I can try to look into this more in-depth next week.

Yeah, these tests print "wip" for me, so I assume that's something unrelated unfinished.


Add development help

There are no explanations on how to help developing Swiftly.
I personally had to:

Use SSWG's VSCode extension and set up a dev container to develop Swiftly on macOS, because otherwise there are some macOS-related errors, and also Swiftly doesn't yet support macOS.
Create a file at /root/.local/share/swiftly/config.json containing the json below, because otherwise swiftly would complain about the file and wouldn't work:

{
  "platform" : {
    "nameFull" : "ubuntu22.04",
    "name" : "ubuntu2204",
    "namePretty" : "Ubuntu 22.04.1 LTS"
  },
  "inUse" : null,
  "installedToolchains" : []
}

Use swift run swiftly [subcommand].

@MahdiBM we don't really have a contributors guide at the moment. But, we do have a subcommand of swiftly devoted to configuring and installing itself that should work in dev too.
swift run swiftly init

And then you could try things like:
swift run swiftly install main-snapshot

But then, if you are already using swiftly it will tend to overwrite it and in each of these examples it might use a different version of swift.