Block domain metalstocks.org

Domain: metalstocks.org
Requested by @jamal77777

Spam
Scam

Hello @jamal77777
These assets have already been flagged. If you have additional wallet addresses that are involved with this scam please let us know.
Looking towards the future with you,
Rob

Will anything happen to my account if I claim some of these tokens that are coming from spam/scam addresses and convert them to xlm?Will the threat actor some how gain access to my account if I claim them?
On Saturday, April 29, 2023 at 11:22:51 AM CDT, CryptoHobbyist @.***> wrote:
Hello @jamal77777
These assets have already been flagged. If you have additional wallet addresses that are involved with this scam please let us know.
Looking towards the future with you,
Rob
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Hello @jamal77777
It is safe to accept them.  Once you have created and funded the account yourself. There are some scammers who clawback their air drops. The downside of accepting these airdrops is that you have to put 0.5 XLM in reserve to have the trustline to the asset.
Very few of the airdrops are from legitimate projects. Most are hoping that if they spread tens of thousands of small worthless (fractions of a XLM in trading value) that maybe a few hundred suckers might buy some. 100 people x 10 XLM = 1,000 XLM. For scammers in a poor country that is a nice take for an afternoon of effort. There are a few mega scammers who have elaborate narratives and networks and get tens or hundreds of thousands, or more, XLM daily in their deception.
The one scam that is a real threat is when someone creates a wallet and then has you fund it. It looks like you created it but they have the secret key and later take your investments.
This is a document I put together to help evaluate token projects.
https://docs.google.com/document/d/1Vbo1GsQWSsTCeVw0nMLX6X7tPCufXMNRTmeUvQh7tmo/edit?usp=sharing
Looking towards the future with you,
Rob

Hello @jamal77777
Please feel free to reopen this issue if you have some more information to add
Rob


iree-run-module segfaulting due to stack overflow on ARM64 8-core CPU

Below is the stacktrace produced by ASAN for IREE runtime (segfaulting during forward pass of network):
> ../iree-build-asan/tools/iree-run-module --module=first_vicuna_int8_cpu.vmfb --input=1x46xi64
EXEC @forward
AddressSanitizerAddressSanitizer:DEADLYSIGNAL
:DEADLYSIGNAL
=================================================================
==6012==ERROR: AddressSanitizer: stack-overflow on address 0x007fb4b7e340 (pc 0x007fb49e4930 bp 0x007fb4b9e550 sp 0x007fb4b7e300 T4)
    #0 0x7fb49e4930  (<unknown module>)
    #1 0x5559cbad3c in iree_hal_elf_executable_issue_call /home/nod/iree/runtime/src/iree/hal/local/loaders/embedded_elf_loader.c:203:13
    #2 0x5559cdf844 in iree_hal_cmd_dispatch_tile /home/nod/iree/runtime/src/iree/hal/drivers/local_task/task_command_buffer.c:873:26
    #3 0x5559cf0ddc in iree_task_dispatch_shard_execute /home/nod/iree/runtime/src/iree/task/task.c:799:11
    #4 0x5559cf2b78 in iree_task_worker_main /home/nod/iree/runtime/src/iree/task/worker.c:187:7
    #5 0x5559d0c798 in iree_thread_start_routine /home/nod/iree/runtime/src/iree/base/internal/threading_pthreads.c:123:29
    #6 0x7fb535e810 in start_thread nptl/pthread_create.c:444:8
    #7 0x7fb53c7d58 in thread_start misc/../sysdeps/unix/sysv/linux/aarch64/clone.S:79

SUMMARY: AddressSanitizer: stack-overflow (<unknown module>)
Thread T4 created by T0 here:
    #0 0x5559c2eea8 in pthread_create (/home/nod/iree-build-asan/tools/iree-run-module+0x1aeea8) (BuildId: 395be842437d278a)
    #1 0x5559d0bdac in iree_thread_create /home/nod/iree/runtime/src/iree/base/internal/threading_pthreads.c:173:10
    #2 0x5559cf2594 in iree_task_worker_initialize /home/nod/iree/runtime/src/iree/task/worker.c:66:26
    #3 0x5559ce84a4 in iree_task_executor_create /home/nod/iree/runtime/src/iree/task/executor.c:161:16
    #4 0x5559ce773c in iree_task_executors_create_from_flags /home/nod/iree/runtime/src/iree/task/api.c:335:14
    #5 0x5559cb99dc in iree_hal_local_task_driver_factory_try_create /home/nod/iree/runtime/src/iree/hal/drivers/local_task/registration/driver_module.c:51:3
    #6 0x5559caf6fc in iree_hal_driver_registry_try_create /home/nod/iree/runtime/src/iree/hal/driver_registry.c:314:14
    #7 0x5559caf924 in iree_hal_create_device /home/nod/iree/runtime/src/iree/hal/driver_registry.c:342:3
    #8 0x5559cad84c in iree_hal_create_device_from_flags /home/nod/iree/runtime/src/iree/tooling/device_util.c:375:3
    #9 0x5559c89644 in iree_tooling_resolve_module_dependency_callback /home/nod/iree/runtime/src/iree/tooling/context_util.c:184:3
    #10 0x5559d994e8 in iree_vm_bytecode_module_enumerate_dependencies /home/nod/iree/runtime/src/iree/vm/bytecode/module.c:231:5
    #11 0x5559c88b94 in iree_tooling_resolve_modules /home/nod/iree/runtime/src/iree/tooling/context_util.c:453:14
    #12 0x5559c8a34c in iree_tooling_create_context_from_flags /home/nod/iree/runtime/src/iree/tooling/context_util.c:578:3
    #13 0x5559c9a820 in iree_tooling_run_module_with_data /home/nod/iree/runtime/src/iree/tooling/run_module.c:138:9
    #14 0x5559c7f0a8 in main /home/nod/iree/tools/iree-run-module-main.c:43:14
    #15 0x7fb5306dbc in __libc_start_call_main csu/../sysdeps/nptl/libc_start_call_main.h:58:16
    #16 0x7fb5306e94 in __libc_start_main csu/../csu/libc-start.c:360:3
    #17 0x5559bcdf6c in _start (/home/nod/iree-build-asan/tools/iree-run-module+0x14df6c) (BuildId: 395be842437d278a)

==6012==ABORTING

Already tried increasing the stack limit but that doesn't fix the issue.
Verified that the issue doesn't occur on AMD CPU
Works when run synchronously, fails multithreaded

You'll see this when multithreading because the worker threads created by the task pool have a fixed size while the main thread in your process has an OS/compiler-defined size that is usually much larger. You can override the worker size at runtime by using the --task_worker_stack_size= flag (in bytes) but this points more at the compiler producing far too large of a stack allocation (probably somewhere on the order of 100+KB, which is too large).
The compiler is supposed to error out when too much stack space is requested (forget the flag to override it, @MaheshRavishankar would know) - are you setting any flags that may be allowing larger allocations through? If so, you'll need to set the runtime flag to match. If not it may indicate a place where the check is failing to catch an allocation that we should investigate.

Yep that resolved the issue! The stack allocation limit was set fairly high during compilation (256KB), configuring the worker stack size to match at runtime got the model running, albeit very slow. Still seems to be an ARM issue though since there were no runtime problems on AMD CPU even without configuring task_worker_stack_size.

@suryajasper Can we close? Any follow up needed?

No follow up needed, we can close :)


Add Evaluation for VOC

Support Evaluation

Hello @toandaominh1997! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file datasets/voc0712.py:

Line 126:5: E301 expected 1 blank line, found 0
Line 128:5: E301 expected 1 blank line, found 0

In the file eval.py:

Line 2:19: W291 trailing whitespace
Line 7:80: E501 line too long (86 > 79 characters)
Line 19:80: E501 line too long (97 > 79 characters)
Line 24:80: E501 line too long (98 > 79 characters)
Line 34:1: E302 expected 2 blank lines, found 1
Line 39:80: E501 line too long (103 > 79 characters)
Line 42:80: E501 line too long (121 > 79 characters)
Line 71:80: E501 line too long (83 > 79 characters)
Line 100:30: W291 trailing whitespace
Line 110:80: E501 line too long (98 > 79 characters)
Line 113:80: E501 line too long (88 > 79 characters)
Line 121:1: E302 expected 2 blank lines, found 1
Line 133:80: E501 line too long (111 > 79 characters)
Line 134:80: E501 line too long (111 > 79 characters)
Line 139:80: E501 line too long (91 > 79 characters)
Line 173:1: E302 expected 2 blank lines, found 0
Line 176:80: E501 line too long (114 > 79 characters)
Line 177:80: E501 line too long (115 > 79 characters)
Line 182:31: E225 missing whitespace around operator
Line 192:74: W291 trailing whitespace
Line 195:80: E501 line too long (94 > 79 characters)
Line 201:80: E501 line too long (96 > 79 characters)
Line 202:1: W293 blank line contains whitespace
Line 208:27: E221 multiple spaces before operator
Line 209:19: E221 multiple spaces before operator
Line 213:27: E221 multiple spaces before operator
Line 214:28: E221 multiple spaces before operator
Line 215:32: E221 multiple spaces before operator
Line 223:39: E221 multiple spaces before operator
Line 226:29: E221 multiple spaces before operator
Line 226:80: E501 line too long (97 > 79 characters)
Line 228:32: E221 multiple spaces before operator
Line 230:80: E501 line too long (104 > 79 characters)
Line 232:39: E221 multiple spaces before operator
Line 236:39: E221 multiple spaces before operator
Line 244:20: E221 multiple spaces before operator
Line 246:27: E221 multiple spaces before operator
Line 250:27: E221 multiple spaces before operator
Line 253:19: E221 multiple spaces before operator
Line 254:80: E501 line too long (111 > 79 characters)
Line 257:30: E221 multiple spaces before operator
Line 259:1: W293 blank line contains whitespace
Line 271:1: W293 blank line contains whitespace
Line 275:1: E303 too many blank lines (7)
Line 276:15: W292 no newline at end of file

In the file models/module.py:

Line 11:80: E501 line too long (83 > 79 characters)
Line 15:80: E501 line too long (90 > 79 characters)

In the file train.py:

Line 93:33: E251 unexpected spaces around keyword / parameter equals
Line 93:35: E251 unexpected spaces around keyword / parameter equals
Line 93:61: E251 unexpected spaces around keyword / parameter equals
Line 93:63: E251 unexpected spaces around keyword / parameter equals
Line 97:37: E251 unexpected spaces around keyword / parameter equals
Line 97:39: E251 unexpected spaces around keyword / parameter equals
Line 97:51: E251 unexpected spaces around keyword / parameter equals
Line 97:53: E251 unexpected spaces around keyword / parameter equals
Line 163:80: E501 line too long (87 > 79 characters)

In the file utils/metric.py:

Line 11:1: E303 too many blank lines (3)
Line 23:80: E501 line too long (111 > 79 characters)
Line 24:80: E501 line too long (111 > 79 characters)
Line 29:80: E501 line too long (91 > 79 characters)
Line 65:80: E501 line too long (94 > 79 characters)
Line 68:80: E501 line too long (93 > 79 characters)
Line 70:80: E501 line too long (81 > 79 characters)
Line 74:80: E501 line too long (84 > 79 characters)
Line 76:80: E501 line too long (82 > 79 characters)
Line 78:80: E501 line too long (96 > 79 characters)
Line 81:1: W293 blank line contains whitespace
Line 88:80: E501 line too long (103 > 79 characters)
Line 91:18: E221 multiple spaces before operator
Line 106:28: E221 multiple spaces before operator
Line 107:29: E221 multiple spaces before operator
Line 108:29: E221 multiple spaces before operator
Line 109:80: E501 line too long (148 > 79 characters)
Line 113:80: E501 line too long (106 > 79 characters)
Line 127:80: E501 line too long (80 > 79 characters)
Line 131:80: E501 line too long (83 > 79 characters)
Line 133:80: E501 line too long (101 > 79 characters)
Line 141:80: E501 line too long (90 > 79 characters)
Line 158:80: E501 line too long (80 > 79 characters)
Line 160:80: E501 line too long (98 > 79 characters)
Line 163:80: E501 line too long (80 > 79 characters)
Line 170:5: E303 too many blank lines (3)
Line 172:19: E221 multiple spaces before operator
Line 172:80: E501 line too long (147 > 79 characters)
Line 173:20: E221 multiple spaces before operator
Line 179:23: E221 multiple spaces before operator
Line 180:15: E221 multiple spaces before operator
Line 184:23: E221 multiple spaces before operator
Line 185:24: E221 multiple spaces before operator
Line 186:28: E221 multiple spaces before operator
Line 194:35: E221 multiple spaces before operator
Line 197:25: E221 multiple spaces before operator
Line 197:80: E501 line too long (93 > 79 characters)
Line 199:28: E221 multiple spaces before operator
Line 201:80: E501 line too long (100 > 79 characters)
Line 203:35: E221 multiple spaces before operator
Line 207:35: E221 multiple spaces before operator
Line 215:16: E221 multiple spaces before operator
Line 217:23: E221 multiple spaces before operator
Line 221:23: E221 multiple spaces before operator
Line 224:15: E221 multiple spaces before operator
Line 225:80: E501 line too long (107 > 79 characters)
Line 228:26: E221 multiple spaces before operator
Line 230:1: W293 blank line contains whitespace
Line 235:1: W293 blank line contains whitespace
Line 236:30: W292 no newline at end of file


Releasing 1.2.0

Coverage increased (+0.9%) to 99.475% when pulling 41bc2d2af03d7a4c0269091f9a379b6132319ce4 on yuce:releasing-1.2.0 into a5187cb9fa86b8553096b662db1cc0ff9494f424 on pilosa:master.


undefined method `elements' for nil:NilClass for windows_task resource in chef-client v13.8.0

Description
We're hitting the same error as described in https://github.com/chef/chef/issues/6585. This issue was ostensibly fixed in 13.7, however we're observing it on at least 2 machines with 13.8 as well.
Chef Version

13.8.0
Platform Version

Windows 10 Pro
Replication Case

Our resource definition is as follows:
windows_task 'chef-solo-windows' do
    command '<redacted>'
    run_level :highest
    frequency :minute
    frequency_modifier 2
    execution_time_limit '600'
    action [:delete, :create, :enable]
    ignore_failure true
end

Client Output
0m  * windows_task[chef-solo-windows] action enable[2021-06-07T08:20:39-04:00] INFO: Processing windows_task[chef-solo-windows] action enable (self::default_windows line 160)
[2021-06-07T08:20:44-04:00] ERROR: windows_task[chef-solo-windows] (self::default_windows line 160) had an error: NoMethodError: undefined method `elements' for nil:NilClass; ignore_failure is set, continuing

================================================================================
Error executing action `enable` on resource 'windows_task[chef-solo-windows]'
================================================================================

    NoMethodError
-------------
undefined method `elements' for nil:NilClass

The debug output (chef-client -l debug) may be useful, but please link to a gist, or truncate it. -->

Stacktrace

13.8 is not a version of Chef Infra Client we support. You'll need to reproduce this issue on 16.x or later. If you're still running into the problem feel free to open this again.

Thanks for your response @tas50 . We shall try the same and get back to you.


[Bug]: Annoying "Deployment operation progress" stuck/duplicate in console

Brief description of your issue
See Actual behavior
Steps to reproduce
Find a Manifest with a few MSIX packages, or do a loop in Mozilla.Firefox.Nightly
Expected behavior
A much cleaner view and to not be visible on the PR submitting screen
Actual behavior
Much worse than this
Deployment operation progress: C:\Users\Esco\AppData\Local\… [Completed🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨 ]
Deployment operation progress: Mozilla.MozillaFirefoxNightly… [Completed🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨 ]
Deployment operation progress: C:\Users\Esco\AppData\Local\… [Completed🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨 ]
Deployment operation progress: Mozilla.MozillaFirefoxNightly… [Completed🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨 ]
Deployment operation progress: C:\Users\Esco\AppData\Local\… [Completed

🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨
🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨Deployment operation progress: Mozilla.MozillaFirefoxNightly… [Completed
🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨Deployment operation progress: C:\Users\Esco\AppData\Local\… [Completed
🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨  [N] Nont operation progress: Mozilla.MozillaFirefoxNightly… [Processing
Deployment operation progress: C:\Users\Esco\AppData\Local\… [Completed🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨 ]
Deployment operation progress: Mozilla.MozillaFirefoxNightly… [Completed🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨 ]
Deployment operation progress: C:\Users\Esco\AppData\Local\… [Completed🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨 ]
Deployment operation progress: Mozilla.MozillaFirefoxNightly… [Completed🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨 ]
Deployment operation progress: C:\Users\Esco\AppData\Local\… [Completed

🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨
🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨Deployment operation progress: Mozilla.MozillaFirefoxNightly… [Completed
🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨Deployment operation progress: C:\Users\Esco\AppData\Local\… [Completed
🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨Deployment operation progress: Mozilla.MozillaFirefoxNightly… [Processing
Deployment operation progress: C:\Users\Esco\AppData\Local\… [Completed🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨 ]
Deployment operation progress: Mozilla.MozillaFirefoxNightly… [Completed🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨 ]
Deployment operation progress: C:\Users\Esco\AppData\Local\… [Completed🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨 ]
Deployment operation progress: Mozilla.MozillaFirefoxNightly… [Completed🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨 ]
Deployment operation progress: C:\Users\Esco\AppData\Local\… [Completed

🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨
🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨Deployment operation progress: Mozilla.MozillaFirefoxNightly… [Completed
🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨Deployment operation progress: C:\Users\Esco\AppData\Local\… [Completed
🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨Enter Choice (default is 'Y'): Mozilla.MozillaFirefoxNightly… [Processing
Deployment operation progress: C:\Users\Esco\AppData\Local\… [Completed🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨 ]
Deployment operation progress: Mozilla.MozillaFirefoxNightly… [Completed🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨 ]
Deployment operation progress: C:\Users\Esco\AppData\Local\… [Completed🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨 ]
Deployment operation progress: Mozilla.MozillaFirefoxNightly… [Completed🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨 ]
Deployment operation progress: C:\Users\Esco\AppData\Local\… [Completed

🟨🟨]
Deployment operation progress: Mozilla.MozillaFirefoxNightly… [Completed
🟨🟨]
Deployment operation progress: C:\Users\Esco\AppData\Local\… [Completed
🟨🟨]
Deployment operation progress: Mozilla.MozillaFirefoxNightly… [Processing
🟨🟨]

Environment
Its been a issue for a looong time since we added the MSIX stuff

❯ $host

Name             : ConsoleHost
Version          : 7.2.1
InstanceId       : c9c31913-a267-48bc-9f0d-b25cae997779
UI               : System.Management.Automation.Internal.Host.InternalHostUserInterface
CurrentCulture   : en-150
CurrentUICulture : en-US
PrivateData      : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy
DebuggerEnabled  : True
IsRunspacePushed : False
Runspace         : System.Management.Automation.Runspaces.LocalRunspace

I don't see any deployment progress on my side; Do you have something that could be overriding the $ProgressPreference = 'SilentlyContinue' of the script?

Interesting, nope i don't change those variables
PS7
❯ git checkout origin/master -q && .\Tools\YamlCreate.ps1 -AutoUpgrade -PackageIdentifier Mozilla.Firefox.Nightly -PackageVersion 96.0a1 -SkipPRCheck

Found Existing Version: 96.0a1

Updating Manifest Information. This may take a while...
Reading Installer Database. This may take some time. . .
Closing Installer Database. . .
Reading Installer Database. This may take some time. . .
Closing Installer Database. . .
Reading Installer Database. This may take some time. . .
Closing Installer Database. . .
Reading Installer Database. This may take some time. . .
Closing Installer Database. . .

Yaml file created: C:\Users\Esco\GitHub\winget-pkgs\manifests\m\Mozilla\Firefox\Nightly\96.0a1\Mozilla.Firefox.Nightly.locale.en-US.yaml

Yaml file created: C:\Users\Esco\GitHub\winget-pkgs\manifests\m\Mozilla\Firefox\Nightly\96.0a1\Mozilla.Firefox.Nightly.installer.yaml

Yaml file created: C:\Users\Esco\GitHub\winget-pkgs\manifests\m\Mozilla\Firefox\Nightly\96.0a1\Mozilla.Firefox.Nightly.yaml

Do you want to submit your PR now?
  [Y] Yes
  [N] No

Enter Choice (default is 'Y'):
Deployment operation progress: C:\Users\Esco\AppData\Local\… [Processing                                            ]
Deployment operation progress: Mozilla.MozillaFirefoxNightly… [Processing                                            ]
Deployment operation progress: C:\Users\Esco\AppData\Local\… [Completed                                             ]
Deployment operation progress: Mozilla.MozillaFirefoxNightly… [Processing                                            ]

It appears to be a issue with PS7 cuz PS5 is clean
❯ git checkout origin/master -q | .\Tools\YamlCreate.ps1 -AutoUpgrade -PackageIdentifier Mozilla.Firefox.Nightly -PackageVersion 96.0a1 -SkipPRCheck

Found Existing Version: 96.0a1

Updating Manifest Information. This may take a while...
Reading Installer Database. This may take some time. . .
Closing Installer Database. . .
Reading Installer Database. This may take some time. . .
Closing Installer Database. . .
Reading Installer Database. This may take some time. . .
Closing Installer Database. . .
Reading Installer Database. This may take some time. . .
Closing Installer Database. . .

Yaml file created: C:\Users\Esco\GitHub\winget-pkgs\manifests\m\Mozilla\Firefox\Nightly\96.0a1\Mozilla.Firefox.Nightly.locale.en-US.yaml

Yaml file created: C:\Users\Esco\GitHub\winget-pkgs\manifests\m\Mozilla\Firefox\Nightly\96.0a1\Mozilla.Firefox.Nightly.installer.yaml

Yaml file created: C:\Users\Esco\GitHub\winget-pkgs\manifests\m\Mozilla\Firefox\Nightly\96.0a1\Mozilla.Firefox.Nightly.yaml
Manifest validation succeeded.

Do you want to submit your PR now?
  [Y] Yes
  [N] No

Enter Choice (default is 'Y'):

Hold up, my ProgressPreference is actually Continue, is the default SilentlyContinue?

No difference >:c

Still Continue on both Powershell versions

Can you dotsource (. .\Tools\YamlCreate.ps1) and then check what $ProgressPreference is set to?

I put Write-Host "$ProgressPreference" above every Add-AppxPackage and its actually set to SilentlyContinue 🤷♂
PowerShell 7.2.1
Copyright (c) Microsoft Corporation.

https://aka.ms/powershell
Type 'help' to get help.

PS C:\Users\User> C:\Users\User\Documents\winget-pkgs\Tools\YamlCreate.ps1 -AutoUpgrade -PackageIdentifier Mozilla.Firefox.Nightly -PackageVersion 96.0a1 -SkipPRCheck
SilentlyContinue

Found Existing Version: 96.0a1

Updating Manifest Information. This may take a while...
SilentlyContinue
Deployment operation progress: C:\Users\User\AppData\Local\T. [Processing                                            ]
Deployment operation progress: Mozilla.MozillaFirefoxNightly. [Processing                                            ]

Hmm. Can you try this to see if it's an issue with Add-AppxPackage or if it's with the progress setting in general?
You should only see one progress bar, if the preference starts as continue
$max = 100000
Write-Output "Current Progress Preference: $ProgressPreference"
Write-Output "Initializing Progress Test"
(1..$max) | % {Write-Progress -Activity 'Testing Progress Bar. . .' -PercentComplete ($_*100/$max) -Status 'Progress bar should be visible'}
Write-Output 'Progress Test Complete'
Write-Output "Setting new progress preference"
$ProgressPreference = 'SilentlyContinue'
Write-Output "New Progress Preference: $ProgressPreference"
Write-Output "Initializing Progress Test"
(1..$max) | % {Write-Progress -Activity 'Testing Progress Bar. . .' -PercentComplete ($_*100/$max) -Status 'Progress bar should be hidden'}
Write-Output 'Progress Test Complete'
Write-Output 'Press any key to exit. . .'
$null = $Host.UI.RawUI.ReadKey('NoEcho,IncludeKeyDown');

I think we need to get the PS7 team to help us here, since I don't know why the progress preference isn't being respected on your machine or your vm, when on my machine, sandbox, and Vedant's machine we don't see the progress bars at all

@OfficialEsco - I think I found the root cause of this while implementing #180 - take a look at https://github.com/PowerShell/Microsoft.PowerShell.Archive/issues/77#issuecomment-601947496
Either way, this should be resolved once https://github.com/microsoft/winget-pkgs/pull/129186 gets merged in


268 docs gtfs tutorial

Description

Fixes #268
Motivation and Context

Tutorial for inspecting & filtering GTFS
I have also made a few changes to the index structure in order to have the site sub-indexes render the table listings correctly.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

rendered locally with quarto
Advice for reviewer

Checklist:

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

Additional comments

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

Project coverage is 98.13%. Comparing base (8f3e4bd) to head (c6ef15f).

Additional details and impacted files
@@           Coverage Diff           @@
##              dev     #284   +/-   ##
=======================================
  Coverage   98.13%   98.13%
=======================================
  Files          21       21
  Lines        1927     1927
=======================================
  Hits         1891     1891
  Misses         36       36

Flag
Coverage Δ

unittests
98.13% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

Thanks @r-leyshon for putting this together - it's a really great job! I love the tutorial hints and solutions too, it's a great way to pick up the package API! The content is great and covers all major aspects of the MultiGtfsInstance class.
I have a few thoughts, and was wondering what you think about these before merging?

I can see you've added a sub-listing structure to cater for multiple GTFS tutorials. I think this is a good idea, but I'm unsure whether or not there would be more than one GTFS tutorial. What do you think?
When explain GTFS, I think it's useful to add this link. -it's a great resource for understanding GTFS. What do you think? If you agree, this is a tiny change and I'm happy to do it as I'm finalising the PR.
What do you think about adding in the HTML report functions?

Curious to get your thoughts, but on the whole I'm good to merge 👍 Really great job again, I enjoyed reading through the tutorial - it's going to be a brilliant template to reuse for the others!

Hi @ethan-moss , I'd agree with all those points in principle.

I couldn't work out how the articles I would write would be navigable from the site index. I updated things so I could see how it would work, but in doing so may have shifted Chesterton's Fence. I probably just need to see what the original intention was and go with that - no hard opinions from me.
Yes to that, good idea.
I couldn't get html_report to work. It may have been the ZeroDivisionError that we already know about but I should confirm to be sure. But it's a shame as that was a really helpful functionality that I originally wanted to make the main outcome for the tutorial.

Are you happy to implement the suggestions?

@ethan-moss I added in the summarise_routes/trips task we discussed yesterday. I revisited the problem with html_report not working for one of the instances. It is a long standing issue, specifically where the feed is missing a shape_id field in shapes.txt. This is also throwing printing the following message with the new GTFS file we included yesterday:             "KeyError. Feed was not cleaned.".
My thoughts are that trying to populate the required shape_ID field of the table (without reverse engineering the entire shapes.txt from available data) should be a good shout.

@ethan-moss I added in the summarise_routes/trips task we discussed yesterday. I revisited the problem with html_report not working for one of the instances. It is a long standing issue, specifically where the feed is missing a shape_id field in shapes.txt. This same issue is also causing the following message to be printed with the new GTFS file we included yesterday: "KeyError. Feed was not cleaned.".
My thoughts are that trying to populate the required shape_ID field of the table (without reverse engineering the entire shapes.txt from available data) should be a good shout.

OK great, thanks Rich! I'll take a look. For the hmtl_report side, i'm fairly sure this is fixed in the large GTFS PR we have waiting 👍


Plugin using graphql-codegen for schema gen

Implementation
Custom plugin using graphql-codegen. The implementation follows this approach

Use visitor pattern to return type names along with the respective fields.
Build a context object which has the following structure

interface Context {
  types: string[]
  nodes: Definition[]
  inputFields: Definition[]
  filterFields: Definition[]
  queries: string[]
  mutations: string[]
  subscriptions: string[]
}

Use the context in string templates to generate the schema as string.

Great work! Is it possible to try adding missing elements in this PR?

Great work! Is it possible to try adding missing elements in this PR?

Working on it

Is this finished. I see context being build but we still not used to build functions

From my point of view I'm happy with everything you think it is best but lets have discussion on how we see this working in this PR

From my point of view I'm happy with everything you think it is best but lets have discussion on how we see this working in this PR

Updated the PR description

Use visitor pattern to return type names along with the respective fields. The fields are returned as string.

We will need to know the types of fields. Can we do that?

Build a context object which has the following structure.

This structure looks very strange. Can you explain the reason why we have it.
Our case will be that we always supply only the busines model type and generate everything else. Really confused.


Expose execa Options for Configuring Its Child Process Spawning Behavior

Description
I try to use lint-staged to run a custom script. The script reads input from different source based on process.stdin.isTTY.
The code structure is roughly like this:
// custom-script.js
...
const inputStream = process.stdin.isTTY ? Readable.from(process.argv.slice(2)) : process.stdin;

inputStream.on('data', ...);
...

However, when this script is invoked by lint-staged with configured command node custome-script.js, it wrongfully expects input from process.stdin while the input is from process.argv. This is due to how nodeJS's child_process module works: https://nodejs.org/api/child_process.html#child_process_options_stdio
The default pipe stdio option marks process.stdin.isTTY false in spawned child process. Hence, my script gets confused and waits for input while letting lint-staged hang forever...
I'd like to be able to adjust the child_process.spawn's behavior via lint-staged's configuration somehow.
Related code segment: https://github.com/okonet/lint-staged/blob/0ef25e81a150ae59749d28565b305c97ec932baa/lib/resolveTaskFn.js#L92-L105
Steps to reproduce
Try to invoke below script with lint-staged:
const { once } = require('events');
const { Readable } = require('stream');

const inputStream = process.stdin.isTTY ? Readable.from(process.argv.slice(2)) : process.stdin;

(async () => {
  inputStream.on('data', console.log);
  await once(inputStream, 'end');
}())

Debug Logs
N/A

Environment

OS: macOS Big Sur
Node.js: v12.13.1
lint-staged: 11.1.2

Would it make sense to expose an execaOptions key in the Node.js API? This would make it an advanced configuration option, and keep the cli simple.
https://github.com/okonet/lint-staged#can-i-use-lint-staged-via-node

@iiroj it would in general. By looking at the code, I wonder if the author wanted to have some behavior control on the execa. Otherwise, giving users full control on execa is the most straight-forward approach. :)

Hello,
the current execa options are hard-coded as follows:

preferLocal: true so that you can more easily run binaries installed into the current project's node_modules/
reject: false so that the child doesn't throw and lint-staged can more easily print its stderr
shell passed directly as an option, to enable built-in shell behavior
possibly cwd = gitDir, when the executed command is git, so that those are always run in the repo root (instead of possible subdirectory).

I can see the last option being problematic when overidden, but having a new execaOptions object spread over the defaults would IMO be easy, powerful, and advanced, so I guess leaving it unadvertised would be preferable.

@iiroj Interesting. With the consideration of cwd, I personally prefer to selectively exclude cwd from the execOptions. It's a good decision the tool makes for users to prevent unexpected behaviors. The need to change cwd should be rare, given how commands are invoked by lint-staged.
Alternatively, if the change will allow configuring all execa options, I think one detailed debug message that highlights cwd change (if overridden) should also help a lot when weird things happen.
I'm not sure about the idea of unadvertised APIs. Personally, I'm not a fan of it. I usually find it discouraging and disappointing if some undocumented API is discovered after going through a whole bunch of code...Such API usually makes me hesitate to use it as well. :)


question: how did you guys manage Chinese characters?

In English (ascii), a word is defined as anything that is separated by space, what about for Chinese character? :)

@roylee0704 There is no clear separator in Chinese

@medcl  ah, so each key contains exactly one Chinese character in a typical indexing database, I see.

fell free to reopen


Added Python_ADDITIONAL_VERSIONS to cmake so python 2 is default.

When installing on systems such as Arch Linux where the default python version is 3 the build will fail. To fix this instead of changing the python link in the shell it is more efficient to set the default python version allowed by cmake.

Oh I did not know about this cmake functionality, thanks for finding this!

I'm not sure this is the best way of resolving this issue. Addtionally, if I use this on Arch it still finds python3 binaries and libraries. Currently I am building with this command:
cmake ..


[REQ] Option to sort tweets from old to new

Description
Currently, tweets are sorted by new to old. Sometimes people tweet something in reference to an older tweet and you have to go down to get the context for that tweet to understand it.
Solution
I would like if the tweets are sorted in chronological order (old to new). This would make them easier to follow.
An option can be added to only display tweets newer than X time (6 hr, 12 hr, 1 day, etc). Then the tweets can be sorted from old to new.

Unfortunately, I don't think this is going to be possible - at least not efficiently possible. I'm not using any official API from Twitter, so Fritter is at the mercy of their unofficial web APIs, and those have very limited sorting capabilities.
For this to work efficiently, I'd need to have the ability to limit how far back a search using the API can go, and another option to sort reverse chronologically (or rather, chronologically), but that's not possible, as far as I can tell.
I'll keep this open for now, but I can't commit to it until I know for sure that it's possible.

Closing as the feed has now been removed, due to Twitter blocking access permanently. Please see https://github.com/jonjomckay/fritter/issues/668#issuecomment-1528784190


feat: Added PrivateApiKeyAuthHeader for all endpoints currently supporting PublicApiKey

Closes #https://github.com/Woosmap/openapi-specification/issues/112

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

v1.20.0
GitHub release

Your semantic-release bot :package::rocket:


Flesh out the python/Flask/S3 example

I found FineUploader very good to work with; but the python Flask example for s3 took me a while to get to grips with.
This pull request fleshes it out to a fully-working example, supporting python 2 or 3.  The only thing needed to use it are the Amazon settings/credentials, supplied as environment variables.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

Thanks for this! Just a few things I'd like to see even before I take a closer look at the code, if you could:

Going forward, it would be great for all server-side examples to exist in their own GitHub repository underneath the FineUploader organization. This would be a good opportunity to create a python-flask repo.
I'd like to see all non-server-side code removed. Checking Fine Uploader client-side code means that this code will be stale at some point since it is unlikely I will remember to update the client-side code in this example every time the fine-uploader repo is updated. Instead, users can be directed to download Fine Uploader using any of the available methods, documented in the getting started guide.

I agree - at least separating them out by language would make sense.

Feel free to remove static files.  However, as a newcomer to using FineUploader it took me several hours to work through the integration between client side and server side, making mistakes, debugging, chasing through options and configuration.  In addition to the FineUploader files themselves, this pull request includes javascript that configures FineUploader client-side, and "joins the dots" to the server code.  Admittedly, I made my own choices when doing so.I would have loved a fully-fleshed "fire it up and run it" example like this - to see how it's all put together.  Either the server-side code goes stale because of a backwards-incompatible change in FineUploader client code, in which case it's good to have an example that keeps working, or it doesn't, and the example will continue to work when the client side code is updated to the latest version.  One solution could be to publish FineUploader as a bower package or similar?  Then a precise version could be specified without checking in static files.  npm install seems an unusual way to do this (location of node_modules folder could be anywhere, whereas .bowerrc is intended for speccing static file requirements)

as a newcomer to using FineUploader it took me several hours to work through the integration between client side and server side

Was the server-side guide not helpful? If not, I'd like to figure out where it is lacking so other developers who need to create their own server-side code not based on existing examples can do so easily.

Either the server-side code goes stale because of a backwards-incompatible change in FineUploader client code

That never happens. In fact, I don't recall ever pushing out a change like this, since changing server-side code is often much more difficult than making a few client-side adjustments.

One solution could be to publish FineUploader as a bower package or similar?

It is published to npm and bower. Bower is becoming a less common repository for JS files. You'll find most, if not all, new JS projects publish to npm exclusively. And node_modules is always located on the same level as your package.json file, which all of your web projects should have.
Your best course of action when integrating Fine Uploader (though this could apply to any JS library) is:

Add an appropriate entry to package.json
npm install
Server-side, create a path alias, such as /static that points at the node_modules directory
Client-side, reference /static/fine-uploader/... when pulling JS/CSS files.

no activity in a while, so closing


Self update failed because the file is in used and being occupied (version after 3.0.10)

The self update failed on replacing the file because the origin executive is still running and being protected by Windows.
Strange problem: this failure only happened when the file name doesn't have a space. File name like GBCL.exe, GBCL123.exe will get this problem while GBCL -.exe, GBCL 1.exe won't.
It also means 3.11 still have to be download manually or manually replacing the file and rename it.
Maybe you can write a tip on the next release on the release note XD.
Exception trace:
System.IO.IOException: The process cannot access the file because it is being used by another process.
   at System.IO.FileSystem.MoveFile(String sourceFullPath, String destFullPath, Boolean overwrite)
   at System.IO.File.Move(String sourceFileName, String destFileName, Boolean overwrite)
   at System.IO.File.Move(String sourceFileName, String destFileName)
   at GBCLV3.Services.Download.UpdateService.Update()
   at GBCLV3.ViewModels.Windows.UpdateViewModel.Update()
   at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__139_0(Object state)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
[Launcher Version: <IP_ADDRESS>]

Oh man...This is gonna haunt me for a while...

🤕IDK…… it works fine on my computer.... I admit I am using some sort of “magic code” to do this self replacement trick, and maybe there could be undefined behaviors lurking👾.

That's a bit sad... Maybe we need more information to solve it...
I don't know it would help but I provide my environment information here:
OS    : Windows 10 Pro 10.0.19041.153, x64, en-CA
Runtime: from .NET Core SDK 3.1.200
EXE Path: C:\Programz\Minecraft\GBCL.exe

Problem signature from reliability monitor:
Problem Event Name:	CLR20r3
Problem Signature 01:	C:\Programz\Minecraft\GBCL.exe
Problem Signature 02:	<IP_ADDRESS>
Problem Signature 03:	5e222541
Problem Signature 04:	System.IO.FileSystem
Problem Signature 05:	4.700.20.6702
Problem Signature 06:	e7838d9b
Problem Signature 07:	1a6
Problem Signature 08:	15
Problem Signature 09:	System.IO.IOException
OS Version:	10.0.19<IP_ADDRESS>.256.48
Locale ID:	4105
Additional Information 1:	442b
Additional Information 2:	442b26075653361de256bf7ac264eb4b
Additional Information 3:	f542
Additional Information 4:	f542e93d5c29a502e50bd86dce03e428

Maybe using start-up parameters on updating would avoid the undefined behaviours, I think. (Or to say, let's play it safe?)

The update module downloads the update;
The launcher starts the temp file with an argument like -update, if it starts successfully, ends the launcher;
The temp executive does the replacement, and starts the new launcher if everything goes as expected (and can send an argument to tell it "update performed successfully 😁" to do the final cleaning); else if something goes wrong can restore it to the origin status (and tells it "failed ☹");
The new launcher starts and reads the argument, then does the final cleaning.

This maybe safe enough, and it needs a parameter processing - maybe troublesome.

如果不使用单独的update程序的话最简单的方法是使用脚本（cmd/vbs）
CMD示例：
rem gbcl_update.cmd
@echo off
if not exist GBCL.update goto :eof
rem kill all processes (if exist).
taskkill /f /im GBCL.exe
rem delay.
timeout -t 3
rem delete old files.
del /f /q GBCL.exe
rem Replace new file.
ren GBCL.update GBCL.exe
rem run new version.
start GBCL.exe
del /f /q gbcl_update.cmd
rem pause

至于楼上说的利用临时文件传参数的方法也可以（甚至不需要传参，检查自身后缀名即可）
只不过还得主程序启动后再去删除临时文件😂

再贴一个直接创建进程的
        public void Update()
        {
            try
            {
                Process cmd = new Process();
                cmd.StartInfo.FileName = "cmd.exe";
                cmd.StartInfo.Arguments = "/c taskkill /f /im GBCL.exe & timeout -t 3 & del /f /q GBCL.exe & ren GBCL.update GBCL.exe & start GBCL.exe";
                cmd.StartInfo.WorkingDirectory = Directory.GetCurrentDirectory();
                cmd.StartInfo.UseShellExecute = false;
                cmd.StartInfo.RedirectStandardInput = true;
                cmd.StartInfo.RedirectStandardOutput = true;
                cmd.StartInfo.CreateNoWindow = true;
                cmd.StartInfo.WindowStyle = ProcessWindowStyle.Hidden;
                cmd.Start();
                Application.Exit();
            }
            catch (Exception e)
            {
                Console.WriteLine(e);
            }
        }


Added a constructor submodule.

Stack:

#1855 ⬅
#1854
#1853
#1852
#1851

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

This change is

crates/cairo-lang-starknet/src/contract_class.rs line 112 at r1 (raw file):

        external: get_entry_points(db, &external_functions, &replacer)?,
        l1_handler: vec![],
        constructor: get_entry_points(db, &constructor_functions, &replacer)?,

we should check that the length of this list <= 1
and that if its 1 than the selector is get_selector_from_name('constructor').
Code quote:
get_entry_points(db, &constructor_functions, &replacer)?


[BUG] Modal does not close after connecting wallet, if opened with setOpen

Describe the bug
After using setOpen to programatically open modal, modal no longer closes upon connecting wallet.
To reproduce

ConnectKit version 1.2.1
Use setOpen to open the modal
Connect a wallet (I used coinbase wallet)
Say yes to everything and wallet has been connected
Wallet address shows in the <ConnectKitButton />
Modal hangs, and stays open

Expected behavior

Using setOpen to open the modal should behave just like clicking on <ConnectKitButton />
Use setOpen to open the modal
Connect a wallet
Wallet connected
Modal closes upon wallet connection

Screenshots

As you can see in the screenshot, I have connected my wallet and the modal still stays open
Environment details
Latest chrome
Windows 10 \ latest macOS
On localhost and also on deployed versions of the website
Additional context
This also triggers another little bug. If you can get this to happen, try disconnecting. Then click connect again. The modal will open for a fraction of a second and close. If you click again, modal will open normally.

hey @Jeremy-Park, do you have an example where I can test this? I'm unable to reproduce in our testing environments

mb accidentally closed-with-comment instead of just comment 😅

I am working on the same project and trying to debug it. This issue won't occur in an isolated case, outside our project scope. So we cannot provide an example code for you to reproduce. Let me provide you with more details of what we see.

Nice @ZiyongHe, that's great to know for if anyone else has a similar issue. Thanks!


Integrate realm and rd

This PR contains the refactoring commits related to the earlier discussion (#230). Realm and Rd (Realm Descriptor) have almost the same purpose. It aims to keep only Rd which is defined by spec.
Summary of changes
-pub struct Realm {
-   id: usize,
-   pub vmid: u16,
-   pub state: State,
-   pub vcpus: Vec<Arc<Mutex<VCPU>>>,
-   pub page_table: Arc<Mutex<Box<dyn IPATranslation>>>,
-   pub measurements: [Measurement; MEASUREMENTS_SLOT_NR],
-}

pub struct Rd {
-   realm_id: usize,
+   vmid: u16,
    ...
+   s2_table: Arc<Mutex<Box<dyn IPATranslation>>>,
    hash_algo: u8,
+   pub measurements: [Measurement; MEASUREMENTS_SLOT_NR],
+   pub vcpus: Vec<Arc<Mutex<VCPU>>>,
}

Notes

vmid is integrated with id so that only vmid, passed by the Host, is used
VMID_SET is used instead of the previous RMS (Realm Map Struct?)
trait Context and redundant enum State have been removed

Changes in the caller side
[before]
   let (s2tte, last_level) = get_realm(realm_id)
          .ok_or(Error::RmiErrorOthers(NotExistRealm))?
          .lock()
          .page_table
          .lock()
          .ipa_to_pte(GuestPhysAddr::from(ipa), level)
          .ok_or(error_code)?;

[after]
   let (s2tte, last_level) = rd
          .s2_table()
          .lock()
          .ipa_to_pte(GuestPhysAddr::from(ipa), level)
          .ok_or(error_code)?;

[before]
   let measurements = crate::realm::registry::get_realm(realmid)
        .ok_or(Error::RmiErrorOthers(NotExistRealm))?
        .lock()
        .measurements;

[after]
   let measurements = rd.measurements;

A caution

Two data aborts are newly generated during realm creation for some reasons which will be analyzed and fixed later

This refactoring is what I have been wanting to see! Thanks for bringing this up :)

Do you think it is better to leave the definition of realm, Rd, inside rmi? I think it is more appropriate to place it inside realm.

Good question! I also think that most of the data structures including realm and Rd are better to be placed outside the current rmi module.

Do you have plan to integrate vcpu and rec too?

Partly yes, but not in the near time. I've refactored Realm in order to help verify Realm-related RMIs. So, the integration of vcpu and rec would be required before verifying Rec-related RMIs. The refactoring task itself could be done by another.


False failure on Stage 7

In .gitignore, I put:
**/*.swp
Which successfully ignores ALL .swp files in the repository.
The game only accepted '*.swp'.
A better evaluation is probably to check the output of 'git status' for any untracked .swp files.

Thanks for the report.
If you are happy looking at changing this then feel free to submit a PR, your solution definitely sounds like a better way of checking. If not then I can look in to doing it.

The text editor 'vim' creates files ending in .swp (swap files) for all files that are currently open.

I believe the expectation of this level is to ignore files ending in .swp instead of files named as .swp.
I've made a PR (#216) to clarify the level description (no level check logic changed).


[BROWSER] Support for edge on Linux

Describe the browser and provide any links if available
Browser name: Edge
List the platforms supported by the browser to be added
Platforms: Linux
Additional Context:
https://twitter.com/eMarcusNet/status/1308433470012747777?s=09
https://www.microsoftedgeinsider.com/en-us/
This issue will have to wait until the browser is released. :P

Since Edge support is already present for MacOS and Windows, this should take much time. @Samyak2 tag it with good-first-issue?

Done

Since Microsoft Edge (Preview) is now on Linux, this can be taken up. Edge is gaining popularity very quickly, we should add support soon.

Since Microsoft Edge (Preview) is now on Linux, this can be taken up. Edge is gaining popularity very quickly, we should add support soon.


Define and properly handle specific throw errors

We could define behavior for specific kinds of throws, for example {input_error, ...}, and use those to detect that we need to send a 400, for example. By defining classes of errors like this, applications could throw early and still expect to have the right status code sent to the client.

What do you think about making it generic like elli: is_allowed(Req) orelse throw({403, [], <<"Permission denied">>})?

It's not readable. I wrote an HTTP server and even I don't really know what 403 does off the top of my head.

Changing my answer a bit to be clearer.
This is not the use case. If you need to handle most status codes properly, you write a resource (cowboy_rest). This ticket is not really about the user code (with exceptions) but about having cowboy_req functions throw on error and Cowboy catching those and sending the right reply without having to look at where the crash occured.

Has been implemented. It's exits with request_error tuples.


add(unit-test): Write unit test of all components

#25

Thanks, reviewing

very well done thanks


Incorrect error response when a policy rejection occurs (in REST API flavor context)

Description and expected behavior
I expect to receive a 403 error response indicating a lack of permission.
Screenshots

Environment (please complete the following information):

ZenStack version: [e.g., 1.0.0-alpha.122]
Prisma version: [e.g., 4.14.0]
Database type: [e.g. Sqlite]

Additional context
Response detail: Cannot read properties of undefined (reading 'PrismaClientKnownRequestError')\nTypeError: Cannot read properties of undefined (reading 'PrismaClientKnownRequestError')\n    at prismaClientKnownRequestError (/Users/augustin/Documents/Dev/Test/zenstack-rest-turbo/apps/express-api/dist/index.js:15890:50)\n    at PolicyUtil.deniedByPolicy (/Users/augustin/Documents/Dev/Test/zenstack-rest-turbo/apps/express-api/dist/index.js:24086:58)\n    at PolicyProxyHandler. (/Users/augustin/Documents/Dev/Test/zenstack-rest-turbo/apps/express-api/dist/index.js:24460:30)\n    at Generator.next ()\n    at fulfilled (/Users/augustin/Documents/Dev/Test/zenstack-rest-turbo/apps/express-api/dist/index.js:24200:28)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

It seems to be an issue on my side since it's working fine in dev mode...

Got it. @Azzerty23 let me know in case you find something suspicious on ZenStack side.

Hi @ymc9, I have identified the source of my issue and found a way to resolve it by modifying how the ZenStack runtime loads the Prisma module. You can find the relevant code here: https://github.com/zenstackhq/zenstack/blob/afa23882422d0fdf772d9a23e4cc157399b19a99/packages/runtime/src/enhancements/utils.ts#LL65C13-L65C45.
By replacing this line with: return require('@prisma/client/runtime');, everything works as expected.
=> When I build the project with esbuild, require(loadPath).Prisma; returns undefined... hence my problem.
However, I don't understand one thing :
const loadPath = path.dirname(prisma._engineConfig.datamodelPath); returns my dist/ folder.
So what does .Prisma refer to in require(loadPath).Prisma;? Am I supposed to have a Prisma folder in my dist/ directory?
Is it possible to fix this by checking that require(loadPath).Prisma; does not return undefined? I can create a pull request for that if the solution is acceptable to you.
For more context, here is a demo repository with the build script (inside apps/express-api folder): https://github.com/Azzerty23/zenstack-rest-turbo.

Hey @Azzerty23 , thanks a lot for digging into this issue!
The reason why I chose to load from prisma._engineConfig.datamodelPath first is to be more resilient and support cases where Prisma client is generated to non-standard locations (so not loadable from @prisma/client/runtime). But I don't know why it ends up undefined ... Let me check your repro and understand it.
Yes, checking if require(loadPath).Prisma is undefined and fallback to loading from @prisma/client/runtime makes good sense. If you already have the code ready in a fork, sending a PR (merge to dev branch) would be great!
Thank you!

Fixed by #461

Hi @Azzerty23 , I've merged the change and published a new version. Welcome to the contributors team!

Thank you very much :D


SIMD implementation for Salsa20

Looks like this is also missing.

This is probably the highest priority, too, as it's used by box public key & secret key boxes.


[feature request][SoC2019] support prometheus in Dragonfly

Why you need it?

Prometheus has been very popular in the container ecosystem. And it is also a project in cncf, graduated. We have a feature request to support Prometheus in native Dragonfly.
How it could be?

We wish to support Prometheus metric in both dfdaemon and supernode.
dfdaemon and supernode should expose metrics API for prometheus.
At the runtime, we should show metric status of Dragonfly when using some display tools, like grafana.

Other related information

I think we should define the metrics first, and kick the ball.
For the metric definition, please help to make it. @Starnop
It is one topic in https://github.com/dragonflyoss/Dragonfly/issues/527

Hi I want to work on this project in Alibaba Summer of Code. So can you tell me what are perquisites for this project. And how can I show my pro efficiency for getting selected in this project.

Please reply @allencloud

If the project(SoC2019) needs collaboration, you can talk to me @allencloud  ：）

@allencloud  Hi, I' m interested in implementing this feature. And I see that currently the progress of refactoring of supernode is slow. Do I have to implement this feature for both Go and Java version of supernode?

Do I have to implement this feature for both Go and Java version of supernode?

We just need to implement the Golang version. Thanks. @yeya24

Hi, I'm a graduate students, I‘d like to work on this project in ASoC(2019). What do I need to submit for applying？

@cnTedMa , Please refer to @lowzj

@allencloud After a discussion with @lowzj offline, we found that the metric definition is a good test for participants, so we should not provide the metrics for now. And we can put forward some opinions on the basis of the author's proposal when it comes to coding stage. WDYT?

I think this is already solved. Close now.


Nodejs - acting as client to other services (windows authentication)

Hey,
Node.js Version: 6.11.3
OS: Windows Server 12
Scope (install, code, runtime, meta, other?):
Module (and version) (if relevant):
I’m working a problem this week and looking for nodejs experience/insight. Problem:
Our nodejs server running on prem on windows server 2016 has to make some rest calls to another on prem web service.
The other web service has windows authentication enabled through IIS.
We enabled windows authentication for our nodejs server but it still cannot communicate with the support service as it’s not passing through credentials (i.e., token info). Any REST request I make to the other on premise service is 401/unauthorized.
So we see if our server was not nodejs but asp, asp has an option on WebClient to UseDefaultCredentials which enables pass through of windows authentication info from client to server service; we do not see options for this in nodejs web requests. Any knowledge or guidance here? We see some statements about rolling your own NTLM support and some packages (e.g., passport, sspi) but they still seem to require reauthentication (i.e., instead of simply passing through credentials known similar to asp WebClient UseDefaultCredentials).
Any thoughts? Thanks.
Reference from node js issue:
https://github.com/nodejs/help/issues/1089

Express is just a server; there is nothing in Express to enable connecting to other services.

What module are you using to make those requests that need auth?

Request, superagent, http, none of this package are taking care to the hand shake to a windows auth server.

I would probably ask in one of those packages, unless there is an issue in express. If there is an issue in express or question about an Express API let us know and I can reopen the issue :+1:


Add tests

This fixes issue #6

Changes Unknown when pulling 6b1940c4623459f68f4526bd8984cc9d8f4e0e5b on tests into ** on master**.

Changes Unknown when pulling 40cc315e5acac15771d5c6767a46c1fc660adbd5 on tests into ** on master**.

Changes Unknown when pulling<PHONE_NUMBER>d0c416b0b46881a8b1257ddcfda811 on tests into ** on master**.

Changes Unknown when pulling 7645bd909afb6b210ef0768e3477218ef09bce6d on tests into ** on master**.

Also fixes #5


Vulnerability roundup 112: nomad-1.1.8: 4 advisories [7.5]

search, files

[ ] CVE-2022-24683 CVSSv3=7.5 (nixos-21.11, nixos-unstable)
[ ] CVE-2022-24685 CVSSv3=7.5 (nixos-21.11, nixos-unstable)
[ ] CVE-2022-24684 CVSSv3=6.5 (nixos-21.11, nixos-unstable)
[ ] CVE-2022-24686 CVSSv3=5.9 (nixos-21.11, nixos-unstable)

CVE details
CVE-2022-24683
HashiCorp Nomad and Nomad Enterprise 0.9.2 through 1.0.17, 1.1.11, and 1.2.5 allow operators with read-fs and alloc-exec (or job-submit) capabilities to read arbitrary files on the host filesystem as root.
CVE-2022-24685
HashiCorp Nomad and Nomad Enterprise 1.x before 1.0.17, 1.1.x before 1.1.12, and 1.2.x before 1.2.6 has Uncontrolled Resource Consumption.
CVE-2022-24684
HashiCorp Nomad and Nomad Enterprise before 1.0.17, 1.1.x before 1.1.12, and 1.2.x before 1.2.6 has Uncontrolled Resource Consumption.
CVE-2022-24686
HashiCorp Nomad and Nomad Enterprise 0.3.0 through 1.0.17, 1.1.11, and 1.2.5 artifact download functionality has a race condition such that the Nomad client agent could download the wrong artifact into the wrong destination. Fixed in 1.0.18, 1.1.12, and 1.2.6

Scanned versions: nixos-21.11: efea022d6fe; nixos-unstable: 710fed5a248.
Cc @endocrimes
Cc @kalbasit
Cc @maxeaubrey
Cc @pradeepchhetri
Cc @rushmorem
Cc @techknowlogick

Fixed in #170275 #170152


Can RDF be source?

@pmaria @DylanVanAssche @dachafra @andimou
https://github.com/kg-construct/rml-io/issues/42 talks about using CONSTRUCT as source, but the discussion has become muddied with considerations about other reference formulations, so I'd like to post this as a separate question.
AFAIK, so far RML hasn't been thought about as an RDF transformation tool (RDF to RDF)
but as an RDFization tool (other formats to RDF).
So this idea is completely new to me.
IMHO the "best" RDF transformation tool is SPARQL

CONSTRUCT to dump data while reformatting it
UPDATE to reformat data inside a semantic database (a best practice is: INSEERT to another graph or repo)

(https://gist.github.com/VladimirAlexiev/cf2de89b692bbc2ae70917aae021ec07 includes some complex examples of such queries)
Various RDFization tools take this approach:

TARQL exposes each table row as variable bindings, then you use CONSTRUCT
SPARQL Anything exposes data from CSV, JSON, XML, doc, html, zip etc etc to some raw RDF, then you use SPARQL to shape it the way you like

Hi @VladimirAlexiev
I think the idea of having RML to do RDF2RDF was there since a decade ago! 😄
Have a look here: https://doi.org/10.1145/2814864.2814873
If it's a good idea or not, that's a different discussion.
Back then we did it mostly to reuse URI identifier which already existed in other RDF graphs.

From #55
If we allow RDF terms for Source, we also need to define NULL values with rml:null for resources based on RDF and SPARQL?

@andimou I don't dispute the value of rdf2rdf with rml.
The reason I raised this is so that we can have more examples, and iron out any small issues we may encounter.


feat: run host-built containers as non-root

:gift: Containers built by the Host builder run as a non-root user.
Impetus is PR #1886 which hardens pod security for services deployed by the Knative Deployer, which causes #1913, an error running host-built function containers which were still attempting to run as root.
/kind enhancement
(partially fixes #1913)

Shouldn't we also set group?

/approve
/lgtm
/hold if you want also set gid

/unhold


[Event Request] Table 5080 To do - OnBeforeSetDuration

Hi Team,
In table 5080 we need possibility to replace and avoid using standard code with our own. Having event with handling in the beginning of procedure SetDuration:

    [IntegrationEvent(false, false)]
    local procedure OnBeforeSetDuration(Todo: Record "To-do"; var IsHandled: Boolean)

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Direct Projection onto Unit Simplex

Implement a direct projection onto unit simplex insted of an alternating projection.
See https://math.stackexchange.com/questions/2005154/how-to-project-onto-the-unit-simplex-as-intersection-of-two-sets-optimizing-a-c

I have finished projection (both direct one and the L1-Normalization in Morup and Hansen) and PGDs for NumPy in wangzcl/archetypes@7b3d07d93279857108be9e2141c01579c015ffef. I will explain my design a little bit later.

_projection.py:
I wrote an abstract base class Projector and two derived subclasses, UnitSimplexProjector (for the naive algorithm 1 mentioned in Condat, 2015) and L1NormalizeProjector (first non-negative, then normalize, mentioned in Morup and Hansen). The Projector.project(x) method projects (or maps) each row of NumPy matrix x onto the unit simplex. To initialize the projector, shape of the array to project has to be provided. Call the class method Projector.from_array(x) to init the instance.
The reason for doing so is, projection requires additional memories for all kinds of intermediate arrays. If memories allocated every time we do the projection, the performance would be intolerable. Projector allocates memories for all (or most of) temporal memories used in the projection in the first place when an object is initialized. This takes advantage of the fact that in the optimization loops of one AA instance, we are dealing with arrays of fixed shapes.
The current unit simplex projection algorithm may not be the fastest on, but it is easy to implement and vectorize. However, there is still some unavoidable memory allocation in UnitSimplexProjector, which is unavoidable unless 1. applying a Python loop on ndarray; 2. rewrite in Cython or 3. switch to more complicated methods.

_optimize.py

PGD

PGD_AA

PGD_Optimize_A
PGD_Optimize_B

The same memory allocation issue may also be in PGD processes. To improve the performance and reduce repetition in the code, I created an abstract base class PGD that defines generic behavior of PGD optimizers. To define a PGD optimizer for a specific problem, one just need to inherit PGD, defining the objective function and gradient manually (and perhaps allocate memory for intermediate arrays). I use an abstract PGD_AA class to describe some common features used in optimizing A and B in archetypal analysis, and two subclasses of this class, PGD_Optimize_A and PGD_Optimize_B to perform the PGD steps. I also defined two class decorators, @line_search to add line search in the PGD steps, and @l1_norm_proj to modify the form of gradient to fit the L1NormalizeProjector. This architecture takes advantage of Python type system's features, is easy to extend, avoids most of the repetition and runtime memory allocation.

The new projection and PGD has not finished yet. I haven't done any tests for the new utilities, but if you think this possible improvement works for you, I can go on finishing, testing and benchmarking all those.


Local installment bugs

Installing issue: https://backstage.io/docs/getting-started/running-backstage-locally#clone-and-build
Expected Behavior
"yarn install" runs without issue
Current Behavior
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
info<EMAIL_ADDRESS>The platform "win32" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "win32" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[4/5] Linking dependencies...
warning "@backstage/core ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "@backstage/core ><EMAIL_ADDRESS>has unmet peer dependency "history@>=5".
warning "@backstage/core ><EMAIL_ADDRESS>has unmet peer dependency "history@>=5".
warning "@backstage/core ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "@backstage/core > @backstage/cli ><EMAIL_ADDRESS>has incorrect peer dependency "eslint@^3 || ^4 || ^5 || ^6".
warning "@backstage/core > material-table ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > @backstage/plugin-rollbar ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "lerna > @lerna/version > @lerna/github-client > @octokit/rest ><EMAIL_ADDRESS>has unmet peer dependency "@octokit/core@>=3".
warning " ><EMAIL_ADDRESS>has unmet peer dependency "eslint@>=6".
warning "@spotify/eslint-config-oss ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > example-app ><EMAIL_ADDRESS>has unmet peer dependency "eslint@>= 3.2.1".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook ><EMAIL_ADDRESS>has unmet peer dependency "@storybook/api@>= 6.x".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook ><EMAIL_ADDRESS>has unmet peer dependency "@storybook/components@>= 6.x".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook ><EMAIL_ADDRESS>has unmet peer dependency "@storybook/core-events@>= 6.x".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook ><EMAIL_ADDRESS>has unmet peer dependency "@storybook/theming@>= 6.x".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > @backstage/plugin-api-docs ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > @backstage/plugin-kafka ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-links ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-links ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-storysource ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-storysource ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-storysource ><EMAIL_ADDRESS>has unmet peer dependency "react@>= 0.14.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addons ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addons ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addons ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addons ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addons ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addons ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/react ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/react ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/react ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/react ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/react ><EMAIL_ADDRESS>has unmet peer dependency "typescript@>= 3.x".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > @backstage/plugin-api-docs > graphiql ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > @backstage/plugin-catalog-graphql > @graphql-modules/core ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > @backstage/plugin-catalog-graphql > apollo-server ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^0.11.3 || ^0.12.0 || ^0.13.0 || ^14.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions > @storybook/api ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| 16.x || 16.4.0-alpha.0911da3".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions > @storybook/api ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| 16.x || 16.4.0-alpha.0911da3".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions > @storybook/components ><EMAIL_ADDRESS>has unmet peer dependency "react@>= 0.14.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions > @storybook/components ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions > @storybook/components ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions > @storybook/components ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions > @storybook/theming ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions > @storybook/theming ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions > @storybook/theming ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/react > @babel/preset-flow ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/react > @storybook/core ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/react > @storybook/core ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/react > @storybook/core ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/react > @storybook/core ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/react > @storybook/core ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/react > @storybook/core ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/react > react-docgen-typescript-plugin ><EMAIL_ADDRESS>has unmet peer dependency "typescript@>= 3.x".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > @backstage/techdocs-common > @aws-sdk/client-s3 > @aws-sdk/middleware-retry ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > @backstage/plugin-catalog-graphql > apollo-server > apollo-server-core ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>- 14".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions > @storybook/api > @reach/router ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions > @storybook/components > react-color ><EMAIL_ADDRESS>has unmet peer dependency "react@*".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions > @storybook/components > react-popper-tooltip ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17".
omponents > react-textarea-autosize ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions > @storybook/components > react-textarea-autosize ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions > @storybook/theming > @emotion/styled ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/react > @babel/preset-flow > @babel/plugin-transform-flow-strip-types ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/react > @storybook/core > @storybook/ui ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/react > @storybook/core > @storybook/ui ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/react > @storybook/core > @storybook/ui ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/react > @storybook/core > @storybook/ui ><EMAIL_ADDRESS>has unmet peer dependency "react@>= 0.14.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/react > @storybook/core > @storybook/ui ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^15.0.0-0 || ^16.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/react > @storybook/core > @storybook/ui ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^15.0.0-0 || ^16.0.0".
warning "workspace-aggregator-11fc14f4-4610-4c78-a4d1-03781092aa56 > storybook > @storybook/addon-actions > @storybook/components > react-textarea-autosize > use-latest ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[5/5] Building fresh packages...
Done in 2344.47s.
Your Environment

NodeJS Version (v12):14.15.4
Operating System and Version (e.g. Ubuntu 14.04): windows 10 pro buid 18363.1316
Browser Information: chrome

Done in 2344.47s.

Looks like it worked. All these warnings are expected. 😁

Done in 2344.47s.

Looks like it worked. All these warnings are expected. 😁


v1.11: images/runtime: update CNI plugins to 1.1.1

This allows Cilium to run in environments using containerd which do not
have a loopback CNI plugin binary available.

/test-backport-1.11

all failures are expected. merging as they will be fixed by https://github.com/cilium/cilium/pull/19752


CustomMenuItem only translates name when menu is not open

As you can see in https://github.com/BigBasket/ra-treemenu/blob/9f526d6791f44b3e6062bc7707f0cbfd443d1ecf/src/CustomMenuItem.js#L36 when the menu is not collapsed, CustomMenuItem does not translate the name of the item.
But when it is collapsed, it does: https://github.com/BigBasket/ra-treemenu/blob/9f526d6791f44b3e6062bc7707f0cbfd443d1ecf/src/CustomMenuItem.js#L46
This is inconsistent.

As can be read in commit https://github.com/edulix/ra-treemenu/commit/adaf0a07d9f81e0459d8c54fe9cdb310345986f5 the usage of translate in current ra-treemenu code is wrong. The translate function imported in https://github.com/BigBasket/ra-treemenu/blob/9f526d6791f44b3e6062bc7707f0cbfd443d1ecf/src/CustomMenuItem.js#L46
should not receive the string to translate but a component to wrap.
The best way to solve it is to solve this using useTranslate() function as in commit (that solves the issue) https://github.com/edulix/ra-treemenu/commit/adaf0a07d9f81e0459d8c54fe9cdb310345986f5.


Discriminator for interfaces responses fields

Existing way of creating multiple possible response model built around JsonInheritanceConverter and KnowTypeAttribute.
It is extremely awful way cause:

Requires reference to NJsonSchema nuget package just for 1 class
Doesn't work for interfaces, cause KnowTypeAttribute can not be placed on interface
Required explicit JsonConverter that can conflict with already existing

My suggestion is:

add another attribute to NSwag.Annotation namespace (smth like OpenApiDiscriminator) that can be placed on interfaces
change processing of this attribute moving away of explicit json conveter (new converter can be placed to NSwag.Generation namespace
attribute also can be placed on custom JsonConverter inherited from base JsonConveter from Newtonsoft.Json that already referenced by almost all existing WebApi projects.

Some of this thoughts can be outdated. The most issues and questions dated by 2017-2018 years.

Requires reference to NJsonSchema nuget package just for 1 class

I think you can also copy the class and provide your own implementation - as long as the class name is "JsonInheritanceConverter".


Image Classification

This is Image Classification based on scraped data.

@1subodh thanks for your first contribution! Please integrate MLflow into your pull request. At AI Platform, we use MLflow to manage machine learning models and log results.

@slavakurilyak I have added MLFLOW for logs and model.Please look into it.

@1subodh thanks very much! Please add MLproject file as well. Here's a simple example on how to accomplish this.

@slavakurilyak  added mlproject and conda.yaml files

Hi @slavakurilyak. I'm not sure what a good naming system would be for different tasks that tackle the same issue (e.g. image classification). A UUID is probably the best option for least conflict, but a proper name (such as StyleGAN) would be more descriptive. We might want to look into a database system.

@mlaradji we need to merge all image classification models into one. We need to make our AI Platform more flexible to allow for any dataset depending on user input. For inspiration, check out
Uber's Ludwig project.

@1subodh Please revert your last commit and create a new pull request for your few-shot learning model. This will make it easier for other developers to review your work. Thanks in advance.

@1subodh Please revert your last commit and create a new pull request for your language modeling task. Separating your models into individual pull requests will make it easier for the Produvia team to provide you with feedback. Thanks again.


[Notification] OpenSearch Dashboards will bump to Node.js 18

As part of our continued efforts to improve OpenSearch Dashboards, we are planning to upgrade the underlying Node.js version from v14 to v18. This change will enhance performance, add new features, and bolster security. However, such major version changes might also affect the compatibility of existing plugins. Here is more introduction: https://github.com/opensearch-project/OpenSearch-Dashboards/issues/3601.
We will merge the change into main and backport to 2.x. Target release is 2.8.
Therefore, we want to notify the build team asap since Centos 7 doesn't support Node.js 18 and we might need extra research and effort working on it. Here is a testing branch that could be used to build new image:
https://github.com/AMoo-Miki/OpenSearch-Dashboards/tree/node-18-webpack-4

This is also related to issue https://github.com/opensearch-project/opensearch-build/issues/1563

We will bump to the latest LTS version 18.16.0.

Close this as the main issue will be synced to:

#1563


Curve fitting using Matlab

We ask that you please be patient as our team works through approving and publishing all articles/tutorials in a timely manner. Allow 1-3 days for a topic to be reviewed and/or approved - allow 3-7 days for an articles to be reviewed and/or published.
Be sure to visit our Resources Page for tools, resources, and example articles to go over.
NOTE: (Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
NOTE: We tend to stray away or tend not to publish reviews/comparisons of commercial product offerings.
We're looking for the first 2-3 paragraphs of the article that appropriately summarize what your article will be about.
Curve fitting using Matlab
Introduction:
Curve fitting is the process of fitting models to data and analyzing the accuracy of the fit. Engineers and scientists use data fitting techniques, including mathematical equations and nonparametric methods, to model acquired data.
 You can perform data fitting interactively using the MATLAB Basic Fitting tool or programmatically using MATLAB functions for fitting. In this article, we will see how to fit Matlab using the curve fitting toolbox
Key takeaways:

Importance of curve fitting.
How to use curve fitting toolbox.
Data visualization

References:
Please list links to any published content/research that you intend to use to support/guide this article.
Templates to use as guides

How To Guide Template
Software Review Template
Tutorial Template

@linetachieng
Good afternoon and thank you for submitting your topic suggestion.
Your topic form has been entered into our queue and should be reviewed (for approval) as soon as a content moderator is finished reviewing the ones in the queue before it.

Great topic 🚀 @linetachieng, make sure it matches the following:

Adds value beyond what is in the official docs and what is covered in other blog sites.
To avoid any potential article closure, It should not overlap with any existing EngEd articles or incoming topic suggestions.

Please reference any relevant EngEd articles in yours and build a unique project - Approved.


perf: Problem in USB Debugging

Type: perf
Platform: android 4.1 webview
Hi! you are working great!
I am getting a problem after my new installation of window and up-gradation of ionic+cordova. When I run the command [ionic run android] to debug the app directly with device it does not installs the app on the device but the command prompt shows the message that launch successful but actually the app is not installed.
I can only test the app by manually copying and installing of .apk file from the platforms\android\build\outputs\apk directory to my phone.

.

Greetings @rizvanhaider!
My sensors indicate that you need to update your issue through our custom issue form. We are now requiring all issues to be submitted this way, to ensure that we have all of the information necessary to fix them as quickly as possible.
Click Here To Update Your Issue
I will have no choice but to close this issue if it is not resubmitted through the form. Please fill out the rest of the form, so that I may use my friendly robot powers to assist you.
Thank you!

Can you try ionic run android --device

having still same issu... :(

Could you provide the output of ionic info

Following is the ionic info

This issue was moved to driftyco/ionic-cli#457

Moving this to the cli since it is related to that. Please continue the conversation over there.


[WIP] Bypass kube-apiserver flowlimit

What type of PR is this?

/kind feature
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Bypass kube-apiserver flowlimit

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

NONE

There is no gain in speed.


Fixed extent handling in batched mode

While introducing batched mode I did not correctly handle computing the extents. This PR consists of two main fixes, a) the GenericOverlayPlot now correctly computes the extents for a batched plot, and b) the bokeh backend now correctly detects framewise normalization modes (via a property) and always makes sure no NaNs are set on the axis ranges (which can cause the plot to blow up).

Other than my two comments (one of which you have already addressed) this looks fine and I am happy to merge.

Addressed both comments now, ready to merge whenever.

Looks good and seems to have fixed the notebooks I was working on.
As this involves a change to get_extents which is fairly basic plotting functionality, I think it is worth making sure the tests pass. Once that happens, I will merge.

Ok great! The tests passed. Merging.


fix: auto focus/exposure by default

What
On some iOS devices (e.g. on my iPod) the auto focus/exposure is not enabled by default. The focus/exposure is done when the camera is loaded and does not change afterwards.
Changes
Enable the auto focus/exposure when a format is loaded.
Tested on

iPhone 12, iOS 17.4.1
iPad Air 2, iOS 15.8.2
iPod, iOS 12.5.7

oh wow interesting! is that really the case? I thought it was always continuous by default...

Does that need to be done in configureFormat? What if no Format is selected?

Yeah :( At least that's the case on my iPod.
And once, I had the case where the continuous autofocus/autoexposure (i don't remember which one) was not available, so it's important to test first if it's available otherwise it crashs.

I just pushed another commit - can you test if this still works fine on your iPod?

I will test that tomorrow :)
Thank you!

I just tested on my iPod and it works perfectly fine 😊

nice!

Still not working for me Ipad Pro 11inch 2nd Gen


Documentation for CLI options?

Are those documented somewhere else?

This is where they are documented:
$ seiso
Keeps your Kubernetes projects clean

Usage:
  seiso [command]

Available Commands:
  configmaps  Cleans up your unused ConfigMaps in the Kubernetes cluster
  help        Help about any command
  images      Cleans up your image registry from unused image tags
  secrets     Cleans up your unused secrets in the Kubernetes cluster

Flags:
  -h, --help               help for seiso
  -b, --log.batch          Use Batch mode (disables logging, prints deleted images only)
      --log.level string   Log level, one of [debug info warn error fatal] (default "info")
  -v, --log.verbose        Shorthand for --log.level debug
  -n, --namespace string   Cluster namespace of current context (default "example-django")
      --version            version for seiso

Use "seiso [command] --help" for more information about a command.

$ seiso configmaps --help
Sometimes ConfigMaps are left unused in the Kubernetes cluster.
This command deletes ConfigMaps that are not being used anymore.

Usage:
  seiso configmaps [flags]

Aliases:
  configmaps, configmap, cm

Flags:
  -d, --delete              Effectively delete ConfigMaps found
  -h, --help                help for configmaps
  -k, --keep int            Keep most current <k> ConfigMaps; does not include currently used ConfigMaps (if detected) (default 3)
  -l, --label strings       Identify the ConfigMap by these labels
      --older-than string   Delete ConfigMaps that are older than the duration, e.g. [1y2mo3w4d5h6m7s] (default "1w")

Global Flags:
  -b, --log.batch          Use Batch mode (disables logging, prints deleted images only)
      --log.level string   Log level, one of [debug info warn error fatal] (default "info")
  -v, --log.verbose        Shorthand for --log.level debug
  -n, --namespace string   Cluster namespace of current context (default "example-django")

$ seiso secrets --help
Sometimes secrets are left unused in the Kubernetes cluster.
This command deletes secrets that are not being used anymore.

Usage:
  seiso secrets [flags]

Aliases:
  secrets, secret

Flags:
  -d, --delete              Effectively delete Secrets found
  -h, --help                help for secrets
  -k, --keep int            Keep most current <k> Secrets; does not include currently used secret (if detected) (default 3)
  -l, --label strings       Identify the Secret by these labels
      --older-than string   Delete Secrets that are older than the duration, e.g. [1y2mo3w4d5h6m7s] (default "1w")

Global Flags:
  -b, --log.batch          Use Batch mode (disables logging, prints deleted images only)
      --log.level string   Log level, one of [debug info warn error fatal] (default "info")
  -v, --log.verbose        Shorthand for --log.level debug
  -n, --namespace string   Cluster namespace of current context (default "example-django")

$ seiso image --help
Cleans up your image registry from unused image tags

Usage:
  seiso images [command]

Aliases:
  images, image, img

Available Commands:
  history     Clean up excessive image tags
  orphans     Clean up unknown image tags

Flags:
  -h, --help   help for images

Global Flags:
  -b, --log.batch          Use Batch mode (disables logging, prints deleted images only)
      --log.level string   Log level, one of [debug info warn error fatal] (default "info")
  -v, --log.verbose        Shorthand for --log.level debug
  -n, --namespace string   Cluster namespace of current context (default "example-django")

Use "seiso images [command] --help" for more information about a command.

Do you think we should create a dedicated documentation (à la readthedocs.org) or would it be sufficient to mention this in the README?

Ah, yes, I guess I should have thought of that.
Since it’s now clear in the readme how to find more information, I think that should be good enough for most people.

Thanks @mikl for helping to make Seiso more useful! :1st_place_medal:
Let us know what else you see missing or features you'd like to have. Your feedback is always more than welcome!


Android annotations: implement new Symbol class

Android annotations API proposal implementation PR as a part of https://github.com/maplibre/maplibre-native/issues/1491. Closes #1493.

Symbol class is now usable.
Updates should propagate correctly, except for icon updates in case a Symbol is attached to a manager directly.
Existing tests for SymbolManager have been updated, and pass.
To avoid conflicts, the following classes have temporary names that differ from their intended names:

Symbol → KSymbol
Annotation → KAnnotation
AnnotationContainer → KAnnotationContainer

Some unresolved TODOs will be resolved later on.

Why are existing tests commented out?

@louwers I had to commented out the following classes:

Circle, CircleManager, CircleManagerTest
Line, LineManager, LineManagerTest
Fill, FillManager, FillManagerTest

This was needed to make changes to AnnotationManager without adapting these classes (yet – since it is planned as a next step). Namely, AnnotationManager now deals with instances of KAnnotation and not AbstractAnnotation.
These classes have been commented out because they will be removed, but are still useful for reference in the next step:

CircleOptions
LineOptions
FillOptions
all subclasses of OnAnnotationClickListener, OnAnnotationLongClickListener, OnAnnotationDragListener (will be replaced with type aliases as well)

Some questions and suggestions, but overall looks good!

@artakka Thank you for reviewing. I have added https://github.com/maplibre/maplibre-native/pull/1637/commits/b3c65a17d2732674f94686088a1e023cbbd80ad7 as a new commit to address your feedback; feel free to Resolve the conversations above if you think everything is in order now.


Beta warning

added in https://github.com/pbca26/hw-kmd-wallet/commit/70ac330f5ebaa85d6a0c5a7ea4e4b84ce73ef069