File Search (using regex) renders correct results on Windows, but no results on macOS

VS Code Version: 1.54.3
OS Version: macOS 10.13.6 High Sierra

Steps to Reproduce:

Create a file with a bunch of text, containing the words 'excel' and 'api' in random positions
Close the file editor
Perform a File Search with the following regex: ^(?=[\s\S\n]*(excel))(?=[\s\S\n]*(api))[\s\S\n]*$
On the macOS version of VS Code, no files are found. On the Windows version, the regex properly matches.

Does the macOS version us a different regex engine than the Windows version?

Does this issue occur when all extensions are disabled?: Yes

This is working for me in a file of just excel\napi. Can you share the exact file or try to reduce it?
We try to do some rewriting of \n in your regex to match \r?\n and it's possible that a case isn't handled correctly.

I created this example file:

Macaroni cheese halloumi api goat.
Caerphilly hard cheese bavarian bergkase feta fromage dolcelatte slices.
Bocconcini cheeseburger when excel the cheese comes out everybody's happy halloumi.
Cheeseburger port-salut cheesecake when the cheese comes out everybody's happy.
Say cheese parmesan jarlsberg.

I search for this regex:
^(?=[\s\S\n]*(excel))(?=[\s\S\n]*(api))[\s\S\n]*$
But no results:

Any variation, big or small, same result.

Still works for me
Please do the following

Run the command "Set log level" and change it to "Trace"
Run the search again
Show the search-related messages in the "Log (Window)" output panel

Also you could try deleting parts of the regex to see which part is causing it to not match

I've attached the log file here: search-error.log

dyld: Symbol not found: ____chkstk_darwin
Referenced from: /Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar.unpacked/vscode-ripgrep/bin/rg (which was built for Mac OS X 10.15)
Expected in: /usr/lib/libSystem.B.dylib

I am on macOS 10.13.6, could that be the issue?

The regex now works, after pulling in ripgrep via Homebrew and replacing the binary in /Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar.unpacked/vscode-ripgrep/bin.
macOS support is shown as being 10.10+ on the downloads page. So maybe the ripgrep binary needs to be replaced?

Interesting, surprised this hasn't come up before. It looks like azure devops supports 10.13, so I will move the build to that version next week.

Actually, it seems like Azure devops removed support for 10.13, and it is no longer officially supported by Apple. Is there some reason that you can't upgrade?

There's just no compelling reason for me to upgrade. Maybe once more applications start breaking. In my personal case, I'm happy with the solution of manually swapping out the ripgrep binary.

Personally I would be nervous about using an OS that is not officially supported, and I assume not receiving security patches.


Array of strings should also be allowed for Scale

I define the scale with an array of hexadecimal strings, not numbers.
This example for a scale would work well but
Throws a ts error:j
scale: ['#C8EEFF', '#0071A4’]

Thanks, merged and published


Gateway shows Online but not used for client connections

Gateway is showing Online, but isn't being used for client connections. This is making it confusing to debug, since clients will fail to use it with Portal error: offline messages in the client logs.

It seems like the portal isn't including this Gateway in the selection algorithm for connected clients:
{"time":"2024-01-05T01:22:28.565643Z","target":"connlib_shared::control","logging.googleapis.com/sourceLocation":{"file":"connlib/shared/src/control.rs","line":"230"},"severity":"WARNING","message":"Portal error: Offline"}
{"time":"2024-01-05T01:22:28.565714Z","target":"connlib_client_shared::control","logging.googleapis.com/sourceLocation":{"file":"connlib/clients/shared/src/control.rs","line":"280"},"severity":"ERROR","message":"An offline error came back with a reference to a non-valid resource id"}

Happening with both Docker and Systemd deploys. Perhaps the Relays are having issues?

Edit: Seems like the issue is with CentOS 7 in particular. Gateway comes online OK but doesn't seem to be used by the portal for connections.

Edit: This ended up being an SELinux issue. It would be helpful if we could detect these somehow, but for the time being I'll mark this as a docs issue and refs #2944

Seems to be resolved now.


Ua

Simply ukrainian language files.

@caouecs, I suggest replacing the use of the country code uk to ua.
I did not find information that uk refers to Ukraine.

Although the country code top-level domain .gb is reserved for the United Kingdom, the UK uses the .uk country code top-level domain instead.

https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes

@rela589n, is there anything to counterbalance?

ISO 639-1 - contains alphabetic codes of languages. The letter code of the Ukrainian language is UK.
ISO 3166 - contains the alphabetic code of countries. The letter code of the country of Ukraine is UA.

ISO 639-1 - contains alphabetic codes of languages. The letter code of the Ukrainian language is UK.
ISO 3166 - contains the alphabetic code of countries. The letter code of the country of Ukraine is UA.

I suggest closing this PR, since the package uses language codes, not country codes.


"light" is not a known CSS property after update to Angular 13

Hi, just updated to angular 13 and getting this message on build:
[WARNING] "light" is not a known CSS property
style.css

light: #f0f3f5
right
Did you mean "right" instead

I've upgraded from angular 11 and @coreui/angular 2.11.3. I'm using coreui free admin template.
coreui installed packages:
"@coreui/angular": "^2.13.0",
"@coreui/coreui": "^2.1.16",
"@coreui/icons": "^2.1.0",
"@coreui/icons-angular": "^1.0.0-alpha.4",

Thank you for your hard work!

nothing to worry about - it's a build time warning only
it comes from<EMAIL_ADDRESS>css styles library
(kind of workaround for lack of support for css custom properties in internet explorer)

nothing to worry about - it's a build time warning only it comes from<EMAIL_ADDRESS>css styles library (kind of workaround for lack of support for css custom properties in internet explorer)

Thanks, but IE support was dropped in Angular 13, maybe you can remove these properties for IE?


ucontext_t is missing on aarch64-unknown-freebsd

2e3999ddf0fa added mcontext_t but not ucontext_t. FreeBSD ucontext_t is machine-independent but libc crate limits it by target_arch.
See ucontext_t definition vs. mcontext_t definition
error[E0412]: cannot find type `ucontext_t` in crate `libc`
   --> veloren-4b6c5f57e3a9/cargo-crates/wasmer-vm-2.3.0/src/trap/traphandlers.rs:219:57
    |
219 |               let ucontext = &mut *(context as *mut libc::ucontext_t);
    |                                                           ^^^^^^^^^^ help: a struct with a similar name exists: `mcontext_t`
    |
   ::: veloren-4b6c5f57e3a9/cargo-crates/libc-0.2.133/src/unix/bsd/freebsdlike/freebsd/aarch64.rs:20:1
    |
20  | / s_no_extra_traits! {
21  | |     pub struct gpregs {
22  | |         pub gp_x: [::register_t; 30],
23  | |         pub gp_lr: ::register_t,
..   |
44  | |     }
45  | | }
    | |_- similarly named struct `mcontext_t` defined here

error[E0412]: cannot find type `ucontext_t` in crate `libc`
   --> veloren-4b6c5f57e3a9/cargo-crates/wasmer-vm-2.3.0/src/trap/traphandlers.rs:259:45
    |
259 |           unsafe fn get_pc_sp(context: &libc::ucontext_t) -> (usize, usize) {
    |                                               ^^^^^^^^^^ help: a struct with a similar name exists: `mcontext_t`
    |
   ::: veloren-4b6c5f57e3a9/cargo-crates/libc-0.2.133/src/unix/bsd/freebsdlike/freebsd/aarch64.rs:20:1
    |
20  | / s_no_extra_traits! {
21  | |     pub struct gpregs {
22  | |         pub gp_x: [::register_t; 30],
23  | |         pub gp_lr: ::register_t,
..   |
44  | |     }
45  | | }
    | |_- similarly named struct `mcontext_t` defined here

error[E0412]: cannot find type `ucontext_t` in crate `libc`
   --> veloren-4b6c5f57e3a9/cargo-crates/wasmer-vm-2.3.0/src/trap/traphandlers.rs:314:54
    |
314 |           unsafe fn update_context(context: &mut libc::ucontext_t, regs: TrapHandlerRegs) {
    |                                                        ^^^^^^^^^^ help: a struct with a similar name exists: `mcontext_t`
    |
   ::: veloren-4b6c5f57e3a9/cargo-crates/libc-0.2.133/src/unix/bsd/freebsdlike/freebsd/aarch64.rs:20:1
    |
20  | / s_no_extra_traits! {
21  | |     pub struct gpregs {
22  | |         pub gp_x: [::register_t; 30],
23  | |         pub gp_lr: ::register_t,
..   |
44  | |     }
45  | | }
    | |_- similarly named struct `mcontext_t` defined here

error[E0425]: cannot find value `pc` in this scope
   --> veloren-4b6c5f57e3a9/cargo-crates/wasmer-vm-2.3.0/src/trap/traphandlers.rs:420:59
    |
420 |                     context.uc_mcontext.mc_gpregs.gp_pc = pc as libc::register_t;
    |                                                           ^^ not found in this scope

error[E0425]: cannot find value `sp` in this scope
   --> veloren-4b6c5f57e3a9/cargo-crates/wasmer-vm-2.3.0/src/trap/traphandlers.rs:421:59
    |
421 |                     context.uc_mcontext.mc_gpregs.gp_sp = sp as libc::register_t;
    |                                                           ^^ not found in this scope

error[E0425]: cannot find value `x0` in this scope
   --> veloren-4b6c5f57e3a9/cargo-crates/wasmer-vm-2.3.0/src/trap/traphandlers.rs:422:61
    |
422 |                     context.uc_mcontext.mc_gpregs.gp_x[0] = x0 as libc::register_t;
    |                                                             ^^ not found in this scope

error[E0425]: cannot find value `x1` in this scope
   --> veloren-4b6c5f57e3a9/cargo-crates/wasmer-vm-2.3.0/src/trap/traphandlers.rs:423:61
    |
423 |                     context.uc_mcontext.mc_gpregs.gp_x[1] = x1 as libc::register_t;
    |                                                             ^^ not found in this scope

error[E0425]: cannot find value `x29` in this scope
   --> veloren-4b6c5f57e3a9/cargo-crates/wasmer-vm-2.3.0/src/trap/traphandlers.rs:424:62
    |
424 |                     context.uc_mcontext.mc_gpregs.gp_x[29] = x29 as libc::register_t;
    |                                                              ^^^ not found in this scope

error[E0425]: cannot find value `lr` in this scope
   --> veloren-4b6c5f57e3a9/cargo-crates/wasmer-vm-2.3.0/src/trap/traphandlers.rs:425:62
    |
425 |                     context.uc_mcontext.mc_gpregs.gp_x[30] = lr as libc::register_t;
    |                                                              ^^ not found in this scope

Some errors have detailed explanations: E0412, E0425.
For more information about an error, try `rustc --explain E0412`.
error: could not compile `wasmer-vm` due to 9 previous errors

Note, before https://github.com/wasmerio/wasmer/commit/ca6f83c7d283 wasmer-vm crate wasn't affected due to using private definition of ucontext_t.

Thanks for the report, feel free to put up a PR for this!

libc-0.2 branch is still affected. What consumers are expected to do?

libc-0.2 branch is still affected. What consumers are expected to do?

The PR just didn't make the most recent backport. There are backports and new releases every couple weeks, it should be in the next one.


MySQL version support

According to https://docs.microsoft.com/en-us/azure/azure-sql/migration-guides/database/mysql-to-sql-database-guide?source=docs#prerequisites only MySQL 5.6 and 5.7 are supported. This looks like a doc bug:
Verify that your source environment is supported. Currently, MySQL 5.6 and 5.7 are supported.
Shouldn't it be corrected to:
Verify that your source environment is supported. Currently, MySQL 5.6 and higher are supported.

@lionelpenuchot -- Lionel, thank you for your feedback.
@cawrites -- Cheryl, please look into this issue.

@mokabiru  - please review.

#reassign:rajpo

The article currently states:

Verify that your source environment is supported. Currently, MySQL 4.1 and above is supported.

I am closing this issue is resolved.


Fix trim trace replay memory requirement mismatch error

The problem
For current trim handling, the create info of image/buffer is different between capture and replay because VK_IMAGE_USAGE_TRANSFER_SRC_BIT or VK_BUFFER_USAGE_TRANSFER_SRC_BIT is added to usage of related create info during capturing trim trace. For some hardware/driver, this makes the memory requirement different for same resource between capture and replay even on same platform, it triggers the following binding memory failure due to memory requirement mismatch for some title.
The solution
If the trace file is trim trace file, add VK_BUFFER_USAGE_TRANSFER_SRC_BIT or VK_IMAGE_USAGE_TRANSFER_SRC_BIT to related buffer or image create info during playback to make it same with the value during capture time.
Result
Tested target title with the build of the pull request, it fix the issue.

CI gfxreconstruct build queued with queue ID 62832.

CI gfxreconstruct build # 3387 running.

CI gfxreconstruct build # 3387 passed.


Add the browser next

Motivation for this change
Add the browser next.
I also had to add several Lisp libraries which are dependencies of next.
Thanks @Ambrevar for his help!
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @7c6f434c

It looks like you are adding fixes before adding the corresponding packages… It also looks like some of the generated files (like dbus.nix) are missing. And I think in general it is better to have sqlite fix in the same commit as addition (adding libraries and in the same commit adding something to help them find native dependencies is a normal workflow).

@7c6f434c oups, sorry! I added missing files and reworked the commit flow.
I patch the package iolib which was already packaged. So, i prefer to add this patch in a separated commit.
I thought the sqlite package was also already existing, which is actually not the case. I squashed this commit into the main lispPacakges commit.

@GrahamcOfBorg build next

@GrahamcOfBorg build next

@GrahamcOfBorg build next

Next only starts for me if I run it with $ export $(dbus-launch) && next. Additionally, when launched I only get blank windows.

Next only starts for me if I run it with $ export $(dbus-launch) && next. Additionally, when launched I only get blank windows.

The first part happens, I guess many people have a DBus session in a typical situation — we could wrap it like LibreOffice is to auto-launch a DBus session unless present. The second is more interesting question…

Note that Next 1.3.2 (to be released this week?) will auto-launch D-Bus.
You can configure the D-Bus path by changing the value of +dbus-launch-command+
in global.lisp.
For the blank window: is glib-networking and gsettings-desktop-schemas
in the user profile?  Those are requirements (propagated inputs) for
WebKitGTK browsers.

Unfortunately I'm still having trouble with a blank window. I tried adding glib-networking to the next-gtk-webkit nix file under propagatedBuildInputs and moving gsettings-desktop-schema to be propagated as well. I also tried just installing both of these packages in my user environment.

Do you see a minibuffer if you press C-l?
What output do you get in the shell?
Anything in ~/.local/share/next/next-gtk-webkit.log

C-l appears to work (shows recent websites) and it looks like it's able to open the websites fine too, but the problem looks like it's just with the display. Here's the full log from startup to navigating to github
** Message: 08:27:52.315: Starting platform port
** Message: 08:27:52.378: Method name: window_make
** Message: 08:27:52.378: Method parameter(s): 1
** Message: 08:27:52.409: Method result(s): window id 1
** Message: 08:27:52.418: Method name: buffer_make
** Message: 08:27:52.418: Method parameter(s): buffer ID 1, options {'cookies-path': '/home/matt/.local/share/next/cookies.txt'}
** Message: 08:27:52.422: Method result(s): buffer id 1
** Message: 08:27:52.430: Method name: window_active
** Message: 08:27:52.430: Method parameter(s): <no active window>
** Message: 08:27:52.433: Method name: window_active
** Message: 08:27:52.433: Method parameter(s): <no active window>
** Message: 08:27:52.442: Method name: minibuffer_evaluate_javascript
** Message: 08:27:52.442: Method parameter(s): window id 1, javascript (...)
** Message: 08:27:52.442: Method result(s): callback id 0
** Message: 08:27:52.445: Method name: window_set_minibuffer_height
** Message: 08:27:52.445: Method parameter(s): window id 1, minibuffer height 25
** Message: 08:27:52.445: Method result(s): minibuffer preferred height 0
** Message: 08:27:52.448: Method name: window_active
** Message: 08:27:52.448: Method parameter(s): 1
** Message: 08:27:52.457: Method name: minibuffer_evaluate_javascript
** Message: 08:27:52.457: Method parameter(s): window id 1, javascript (...)
** Message: 08:27:52.457: Method result(s): callback id 1
** Message: 08:27:52.463: Method name: window_active
** Message: 08:27:52.463: Method parameter(s): 1
** Message: 08:27:52.466: Method name: window_active
** Message: 08:27:52.466: Method parameter(s): 1
** Message: 08:27:52.469: Method name: minibuffer_evaluate_javascript
** Message: 08:27:52.469: Method parameter(s): window id 1, javascript (...)
** Message: 08:27:52.469: Method result(s): callback id 2
** Message: 08:27:52.472: Method name: window_set_minibuffer_height
** Message: 08:27:52.472: Method parameter(s): window id 1, minibuffer height 25
** Message: 08:27:52.472: Method result(s): minibuffer preferred height 0
** Message: 08:27:52.476: Method name: window_active
** Message: 08:27:52.476: Method parameter(s): 1
** Message: 08:27:52.479: Method name: minibuffer_evaluate_javascript
** Message: 08:27:52.479: Method parameter(s): window id 1, javascript (...)
** Message: 08:27:52.479: Method result(s): callback id 3
** Message: 08:27:52.483: Method name: buffer_evaluate_javascript
** Message: 08:27:52.483: Method parameter(s): buffer id 1, javascript (...)
** Message: 08:27:52.483: Method result(s): callback id 0
** Message: 08:27:52.486: Method name: window_active
** Message: 08:27:52.486: Method parameter(s): 1
** Message: 08:27:52.489: Method name: window_set_active_buffer
** Message: 08:27:52.489: Method parameter(s): window id 1, buffer id 1
** Message: 08:27:52.489: Window 1 switches from buffer (null) to 1 with URI (null)
** Message: 08:27:52.492: Method name: window_active
** Message: 08:27:52.492: Method parameter(s): 1
** Message: 08:27:52.495: Method name: buffer_evaluate_javascript
** Message: 08:27:52.495: Method parameter(s): buffer id 1, javascript (...)
** Message: 08:27:52.495: Method result(s): callback id 1
** Message: 08:27:52.498: Method name: window_set_active_buffer
** Message: 08:27:52.498: Method parameter(s): window id 1, buffer id 1
** Message: 08:27:52.498: Window 1 switches from buffer 1 to 1 with URI (null)
** Message: 08:27:52.501: Method name: window_active
** Message: 08:27:52.501: Method parameter(s): 1
** Message: 08:27:52.504: Method name: buffer_evaluate_javascript
** Message: 08:27:52.504: Method parameter(s): buffer id 1, javascript (...)

** Message: 08:32:23.559: Method result(s): callback id 4
** Message: 08:32:23.561: RPC message: minibuffer_javascript_call_back (buffer id, javascript, callback id) = (1, ..., 4)
** Message: 08:32:23.563: Method name: window_active
** Message: 08:32:23.563: Method parameter(s): 1
** Message: 08:32:23.566: Method name: minibuffer_evaluate_javascript
** Message: 08:32:23.566: Method parameter(s): window id 1, javascript (...)
** Message: 08:32:23.566: Method result(s): callback id 5
** Message: 08:32:23.569: RPC message: minibuffer_javascript_call_back (buffer id, javascript, callback id) = (1, ..., 5)
** Message: 08:32:23.570: Method name: window_active
** Message: 08:32:23.570: Method parameter(s): 1
** Message: 08:32:23.573: Method name: window_active
** Message: 08:32:23.573: Method parameter(s): 1
** Message: 08:32:23.582: Method name: window_active
** Message: 08:32:23.582: Method parameter(s): 1
** Message: 08:32:23.585: Method name: minibuffer_evaluate_javascript
** Message: 08:32:23.585: Method parameter(s): window id 1, javascript (...)

** Message: 08:32:25.651: Method result(s): callback id 7
** Message: 08:32:25.652: RPC message: minibuffer_javascript_call_back (buffer id, javascript, callback id) = (1, ..., 7)
** Message: 08:32:25.654: Method name: window_set_minibuffer_height
** Message: 08:32:25.654: Method parameter(s): window id 1, minibuffer height 25
** Message: 08:32:25.654: Method result(s): minibuffer preferred height 0
** Message: 08:32:25.657: Method name: window_active
** Message: 08:32:25.657: Method parameter(s): 1
** Message: 08:32:25.661: Method name: minibuffer_evaluate_javascript
** Message: 08:32:25.661: Method parameter(s): window id 1, javascript (...)
** Message: 08:32:25.661: Method result(s): callback id 8
** Message: 08:32:25.661: RPC message: minibuffer_javascript_call_back (buffer id, javascript, callback id) = (1, ..., 8)
** Message: 08:32:25.664: Method name: window_set_minibuffer_height
** Message: 08:32:25.664: Method parameter(s): window id 1, minibuffer height 25
** Message: 08:32:25.664: Method result(s): minibuffer preferred height 0
** Message: 08:32:25.667: Method name: window_active
** Message: 08:32:25.667: Method parameter(s): 1
** Message: 08:32:25.670: Method name: window_active
** Message: 08:32:25.670: Method parameter(s): 1
** Message: 08:32:25.688: Method name: window_active
** Message: 08:32:25.688: Method parameter(s): 1
** Message: 08:32:25.691: Method name: window_active
** Message: 08:32:25.691: Method parameter(s): 1
** Message: 08:32:25.729: Method name: buffer_evaluate_javascript
** Message: 08:32:25.729: Method parameter(s): buffer id 1, javascript (...)

** Message: 08:32:26.097: Method result(s): callback id 4
** Message: 08:32:26.100: Method name: window_active
** Message: 08:32:26.100: Method parameter(s): 1
** Message: 08:32:26.103: Method name: window_active
** Message: 08:32:26.103: Method parameter(s): 1
** Message: 08:32:26.106: Method name: window_active
** Message: 08:32:26.106: Method parameter(s): 1
** Message: 08:32:26.109: Method name: buffer_evaluate_javascript
** Message: 08:32:26.109: Method parameter(s): buffer id 1, javascript (...)
** Message: 08:32:26.109: Method result(s): callback id 5
** Message: 08:32:26.110: RPC message: buffer_javascript_call_back (buffer id, javascript, callback id) = (1, ..., 4)
** Message: 08:32:26.110: RPC message: buffer_javascript_call_back (buffer id, javascript, callback id) = (1, ..., 5)
** Message: 08:32:26.113: Method name: window_active
** Message: 08:32:26.113: Method parameter(s): 1
** Message: 08:32:26.116: Method name: window_active
** Message: 08:32:26.116: Method parameter(s): 1
** Message: 08:32:26.141: Method name: window_active
** Message: 08:32:26.141: Method parameter(s): 1
** Message: 08:32:26.144: Method name: window_active
** Message: 08:32:26.144: Method parameter(s): 1
** Message: 08:32:26.147: Method name: minibuffer_evaluate_javascript
** Message: 08:32:26.147: Method parameter(s): window id 1, javascript (...)
** Message: 08:32:26.147: Method result(s): callback id 9
** Message: 08:32:26.148: RPC message: minibuffer_javascript_call_back (buffer id, javascript, callback id) = (1, ..., 9)
** Message: 08:32:26.150: Method name: window_set_minibuffer_height
** Message: 08:32:26.151: Method parameter(s): window id 1, minibuffer height 25
** Message: 08:32:26.151: Method result(s): minibuffer preferred height 0
** Message: 08:32:26.153: Method name: window_active
** Message: 08:32:26.153: Method parameter(s): 1
** Message: 08:32:26.156: Method name: minibuffer_evaluate_javascript
** Message: 08:32:26.157: Method parameter(s): window id 1, javascript (...)
** Message: 08:32:26.157: Method result(s): callback id 10
** Message: 08:32:26.157: RPC message: minibuffer_javascript_call_back (buffer id, javascript, callback id) = (1, ..., 10)
** Message: 08:32:26.159: Method name: window_active
** Message: 08:32:26.159: Method parameter(s): 1
** Message: 08:32:26.162: Method name: buffer_evaluate_javascript
** Message: 08:32:26.162: Method parameter(s): buffer id 1, javascript (...)
** Message: 08:32:26.162: Method result(s): callback id 6
** Message: 08:32:26.165: Method name: window_active
** Message: 08:32:26.165: Method parameter(s): 1
** Message: 08:32:26.166: RPC message: buffer_javascript_call_back (buffer id, javascript, callback id) = (1, ..., 6)
** Message: 08:32:26.168: Method name: window_active
** Message: 08:32:26.168: Method parameter(s): 1
** Message: 08:32:26.171: Method name: window_active
** Message: 08:32:26.171: Method parameter(s): 1
** Message: 08:32:26.174: Method name: buffer_evaluate_javascript
** Message: 08:32:26.174: Method parameter(s): buffer id 1, javascript (...)
** Message: 08:32:26.174: Method result(s): callback id 7
** Message: 08:32:26.174: RPC message: buffer_javascript_call_back (buffer id, javascript, callback id) = (1, ..., 7)
** Message: 08:32:26.177: Method name: window_active
** Message: 08:32:26.177: Method parameter(s): 1
** Message: 08:32:26.180: Method name: window_active
** Message: 08:32:26.180: Method parameter(s): 1
** Message: 08:32:26.183: Method name: minibuffer_evaluate_javascript
** Message: 08:32:26.183: Method parameter(s): window id 1, javascript (...)
** Message: 08:32:26.183: Method result(s): callback id 11
** Message: 08:32:26.183: RPC message: minibuffer_javascript_call_back (buffer id, javascript, callback id) = (1, ..., 11)
** Message: 08:32:26.186: Method name: window_set_minibuffer_height
** Message: 08:32:26.186: Method parameter(s): window id 1, minibuffer height 25
** Message: 08:32:26.186: Method result(s): minibuffer preferred height 0
** Message: 08:32:26.189: Method name: window_active
** Message: 08:32:26.189: Method parameter(s): 1
** Message: 08:32:26.193: Method name: minibuffer_evaluate_javascript
** Message: 08:32:26.193: Method parameter(s): window id 1, javascript (...)
** Message: 08:32:26.193: Method result(s): callback id 12
** Message: 08:32:26.193: RPC message: minibuffer_javascript_call_back (buffer id, javascript, callback id) = (1, ..., 12)
** Message: 08:32:26.197: Method name: window_set_title
** Message: 08:32:26.197: Method parameter(s): 1, Next - The world’s leading software development platform · GitHub - https://github.com/
** Message: 08:32:26.200: Method name: window_set_title
** Message: 08:32:26.201: Method parameter(s): 1, Next - The world’s leading software development platform · GitHub - https://github.com/
** Message: 08:32:26.843: RPC message: buffer_did_finish_navigation ('1', 'https://github.com/')
** Message: 08:32:26.847: Method name: window_active
** Message: 08:32:26.847: Method parameter(s): 1
** Message: 08:32:26.849: Method name: window_active
** Message: 08:32:26.849: Method parameter(s): 1
** Message: 08:32:26.853: Method name: minibuffer_evaluate_javascript
** Message: 08:32:26.853: Method parameter(s): window id 1, javascript (...)
** Message: 08:32:26.853: Method result(s): callback id 13
** Message: 08:32:26.854: RPC message: minibuffer_javascript_call_back (buffer id, javascript, callback id) = (1, ..., 13)
** Message: 08:32:26.856: Method name: window_set_minibuffer_height
** Message: 08:32:26.856: Method parameter(s): window id 1, minibuffer height 25
** Message: 08:32:26.856: Method result(s): minibuffer preferred height 0
** Message: 08:32:26.864: Method name: window_active
** Message: 08:32:26.864: Method parameter(s): 1
** Message: 08:32:26.867: Method name: minibuffer_evaluate_javascript
** Message: 08:32:26.867: Method parameter(s): window id 1, javascript (...)
** Message: 08:32:26.867: Method result(s): callback id 14
** Message: 08:32:26.868: RPC message: minibuffer_javascript_call_back (buffer id, javascript, callback id) = (1, ..., 14)
** Message: 08:32:26.870: Method name: window_active
** Message: 08:32:26.870: Method parameter(s): 1
** Message: 08:32:26.873: Method name: window_active
** Message: 08:32:26.873: Method parameter(s): 1
** Message: 08:32:26.877: Method name: window_active
** Message: 08:32:26.877: Method parameter(s): 1
** Message: 08:32:26.881: Method name: minibuffer_evaluate_javascript
** Message: 08:32:26.881: Method parameter(s): window id 1, javascript (...)
** Message: 08:32:26.881: Method result(s): callback id 15
** Message: 08:32:26.882: RPC message: minibuffer_javascript_call_back (buffer id, javascript, callback id) = (1, ..., 15)
** Message: 08:32:26.884: Method name: window_set_minibuffer_height
** Message: 08:32:26.884: Method parameter(s): window id 1, minibuffer height 25
** Message: 08:32:26.884: Method result(s): minibuffer preferred height 0
** Message: 08:32:26.887: Method name: window_active
** Message: 08:32:26.887: Method parameter(s): 1
** Message: 08:32:26.890: Method name: minibuffer_evaluate_javascript
** Message: 08:32:26.890: Method parameter(s): window id 1, javascript (...)
** Message: 08:32:26.890: Method result(s): callback id 16
** Message: 08:32:26.891: RPC message: minibuffer_javascript_call_back (buffer id, javascript, callback id) = (1, ..., 16)
** Message: 08:32:26.894: Method name: window_set_minibuffer_height
** Message: 08:32:26.894: Method parameter(s): window id 1, minibuffer height 25
** Message: 08:32:26.894: Method result(s): minibuffer preferred height 0
** Message: 08:32:26.897: Method name: window_active
** Message: 08:32:26.897: Method parameter(s): 1
** Message: 08:32:26.900: Method name: buffer_evaluate_javascript
** Message: 08:32:26.900: Method parameter(s): buffer id 1, javascript (...)
** Message: 08:32:26.900: Method result(s): callback id 8
** Message: 08:32:26.900: RPC message: buffer_javascript_call_back (buffer id, javascript, callback id) = (1, ..., 8)
** Message: 08:32:26.904: Method name: window_active
** Message: 08:32:26.904: Method parameter(s): 1
** Message: 08:32:26.907: Method name: buffer_evaluate_javascript
** Message: 08:32:26.907: Method parameter(s): buffer id 1, javascript (...)
** Message: 08:32:26.907: Method result(s): callback id 9
** Message: 08:32:26.907: RPC message: buffer_javascript_call_back (buffer id, javascript, callback id) = (1, ..., 9)
** Message: 08:32:26.910: Method name: window_active
** Message: 08:32:26.910: Method parameter(s): 1
** Message: 08:32:26.913: Method name: window_active
** Message: 08:32:26.913: Method parameter(s): 1
** Message: 08:32:26.916: Method name: minibuffer_evaluate_javascript
** Message: 08:32:26.916: Method parameter(s): window id 1, javascript (...)
** Message: 08:32:26.916: Method result(s): callback id 17
** Message: 08:32:26.917: RPC message: minibuffer_javascript_call_back (buffer id, javascript, callback id) = (1, ..., 17)
** Message: 08:32:26.919: Method name: window_set_minibuffer_height
** Message: 08:32:26.919: Method parameter(s): window id 1, minibuffer height 25
** Message: 08:32:26.919: Method result(s): minibuffer preferred height 0
** Message: 08:32:26.922: Method name: window_active
** Message: 08:32:26.922: Method parameter(s): 1
** Message: 08:32:26.925: Method name: minibuffer_evaluate_javascript
** Message: 08:32:26.925: Method parameter(s): window id 1, javascript (...)
** Message: 08:32:26.925: Method result(s): callback id 18
** Message: 08:32:26.926: RPC message: minibuffer_javascript_call_back (buffer id, javascript, callback id) = (1, ..., 18)

Here's also a screenshot of window (top half is cut off since its all white anyway)

Note also that I haven't yet created an init.lisp file. I didn't see anywhere that that was necessary to get it running, but maybe I missed something.

No you don't need init.lisp.
If you can display the minibuffer, then webkitgtk is working (the
minibuffer is a webview).
Just got a hunch: try browsing http://imdb.com (not HTTPS).
I can think of 2 possible issues:

The 'Cannot create EGL window surface: EGL_BAD_MATCH' hints that
hardware acceleration is failing on your hardware.  You'll probably
have the same issue with other browsers like Epiphany.  Which video
driver do you have?

An HTTPS issue (although this should print "Unacceptable TLS certificate).

imdb doesn't work either. I'm using the nvidia proprietary drivers (v435.21)

Does any other WebKitGTK browser work for you?

Epiphany works fine.

Hmmm, I'm running out of ideas.
Can anyone else reproduce?
What if you build and run Next locally?

@matthuszagh I'm not able to reproduce your blank page issue :(
Are you able to test this package from another system/machine?
@GrahamcOfBorg build next

@Ambrevar are you saying to build it from source outside of Nix tooling? I can try although I know nothing about quicklisp so I'm not sure I'll be able to. And unfortunately I don't have another Nix machine yet... I'll keep digging and see if I can figure out what's going on.
I don't use a display manager or desktop environment, just EXWM via emacs as my window manager. Maybe there's some unmet dependency that everyone else is getting from their display manager?

I also use EXWM.
The only WM-related dependency is D-Bus, but since you can start Next
that's not your problem.
Next has an all-in-one Makefile that grabs Quicklisp and fetches the
deps for you.  You can type make and follow the instructions :)
Don't hesitate to come back to me if you need more help.

Built it in a no-DE StumpWM setup, wrapped it into a DBus session, seems to work from the first glance.
env -i DISPLAY=$DISPLAY $(nix-build /home/repos/nixpkgs-test -A nix)/bin/nix run -f /home/repos/nixpkgs-test procps next dbus -c dbus-launch next

@matthuszagh
Try running Next by exporting WEBKIT_FORCE_COMPOSITING_MODE=1 and the
WEBKIT_DISABLE_COMPOSITING_MODE=1 environment variables (separately).

WEBKIT_DISABLE_COMPOSITING_MODE=1 works! Thanks @Ambrevar

Something is wrong between the Nvidia driver and Next, but if Epiphany
can get it right, Next can too!

I think we can merge this PR since the issue encountered by @matthuszagh doesn't seems to be related to the packaging.
Moreover, we could hope this issue will be fixed on the next next release;)
WDYT?

Thanks!
And thank you a lot, @lewo, for working on this!


Add CONTRIBUTING.md

Hi ! I'd like to work on this !
Same specifications as regusabot or anything different ?


Fixed Typo in CONTRIBUTORS.md

Issue: #167
I reverted my index.html changes, and kept my CONTRIBUTORS.md changes
let me know if this is done correctly, thanks!

Awesome! Thank you so much
@all-contributors please add @stanjdev for doc

@all-contributors please add @stanjdev for doc


Redirect usejsdoc.org to jsdoc.app

Not sure if this is the right place to report, but http://usejsdoc.org appears to be down.
https://downforeveryoneorjustme.com/usejsdoc.org

Thanks for the heads up. It looks like there's a DNS issue:
$ nslookup usejsdoc.org
;; Got SERVFAIL reply from <IP_ADDRESS>, trying next server
;; Got SERVFAIL reply from <IP_ADDRESS>, trying next server
Server:		<IP_ADDRESS>
Address:	<IP_ADDRESS>#53

** server can't find usejsdoc.org: SERVFAIL

I don't own the domain, though. @micmath: Any idea what's up?

I'm working on bringing the site back up on a new domain. That might take another day or so, but it will be back up soon.

ty 🙏

That went faster than expected. The site is now available at https://jsdoc.app/.
@micmath, can you please redirect all traffic from usejsdoc.org to jsdoc.app?

Any updates please?

@micmath, can you please redirect all traffic from usejsdoc.org to https://jsdoc.app?

Hopefully this triggers a notification email for him?

I'd suggest (in the meantime waiting for the redirects) generating a sitemap and submitting that to Google Search Console to get the site indexed as only a handful of pages show up and usejsdoc.org is still dominating the SERPs.

as a temporary workaround, any reason why it wouldn't be a good idea to edit local windows 10 hosts file with:
<IP_ADDRESS> usejsdoc.org

where <IP_ADDRESS> is the result of ping jsdoc.app.
just so that any google search results for usejsdoc.org actually load content from jsdoc.app?
when i do this, i am getting a github 404 page.
any ideas how to remedy this?
thank you.

FYI the site is still down and Google doesn't index anything from the new site, all the queries show the old site.

it's on Github and hasn't been updated for 5 years so hopefully it is hunky dory privacy/security wise.

If you want something updated within a year and open-sourced, try Redirector. It even has Firefox version.

+1 Some old site pages are still shown in Google. Is the original domain name still controlled?
@FranklinYu Thanks for that :) For anyone else using Redirector, get settings for jsdoc are here

Sorry, I just saw this message. I've now added a redirect in with the
usejsdoc.org domain registrar. Hope that sorts it out.
On Mon, 19 Aug 2019 at 21:52, ithinkandicode<EMAIL_ADDRESS>wrote:

+1 Some old site pages are still shown in Google. Is the original domain
name still controlled?
@FranklinYu https://github.com/FranklinYu Thanks for that :) For anyone
else using Redirector, get settings for jsdoc are here
https://gist.github.com/ithinkandicode/daca53c3dbf8719588d7e008f9c784f1
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jsdoc/jsdoc/issues/1642?email_source=notifications&email_token=AAAT53LKIAGCYQIWCGXRL7LQFMBYTA5CNFSM4HKXLM2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4UIIOI#issuecomment-522748985,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAT53OLMYGUCBPIKUCKWMTQFMBYTANCNFSM4HKXLM2A
.

Belated thanks for setting up the redirect, @micmath!


Distance - Icon in the center button is off-centered

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

Version Number: 1.4.86-0
Reproducible in staging?: y
Reproducible in production?: n
Issue reported by: Applause - Internal Team
Action Performed:

Launch New Expensify app.
Go to FAB > Submit expense > Distance.

Expected Result:
The icon in the center button will be centered.
Actual Result:
The icon in the center button is off-centered.
Workaround:
n/a
Platforms:

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

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

Screenshots/Videos
Add any screenshot/video evidence

View all open jobs on GitHub

We think that this bug might be related to #wave-collect - Release 1

closing, raised the same issue https://github.com/Expensify/App/issues/44074


Molecular KP is not returning results

Hi Vlado,
Chris B ran this query during the last mini-hackathon, Molecular KP did not return results.
Here is the link from ARAX with results of that query run: https://arax.ncats.io/?source=ARS&id=90080f07-808c-47db-a042-21a9ce6f4281
here is the query itself, please take a look. Chris B and Anne would like to revisit the query during the next mini-hackathon which is scheduled for next week (June 3). Would you be able to get back to this issue before that time?
qg = {
"nodes": {
"n0": {
"categories": [
"biolink:ChemicalSubstance"
],
"name": "Chemical Substance"
},
"n1": {
"name": "EGFR",
"ids": ["NCBIGene:1956"]
}
},
"edges": {
"e0": {
"subject": "n0",
"object": "n1",
"predicates": [
"biolink:decreases_abundance_of",
"biolink:decreases_activity_of",
"biolink:decreases_expression_of",
"biolink:decreases_synthesis_of",
"biolink:increases_degradation_of",
"biolink:disrupts",
"biolink:negatively_regulates_entity_to_entity"
]
}
}
}

Listed predicates are not supported by MolePro. Changing predicate to "biolink:affected_by" yields results:
{
    "message": {
        "query_graph": {
            "nodes": {
                "n0": {
                    "categories": [
                        "biolink:ChemicalSubstance"
                    ],
                    "name": "Chemical Substance"
                },
                "n1": {
                    "name": "EGFR",
                    "ids": [
                        "NCBIGene:1956"
                    ]
                }
            },
            "edges": {
                "e0": {
                    "subject": "n1",
                    "object": "n0",
                    "predicates": ["biolink:affected_by"]
                }
            }
        }
    }
}

@vdancik does MolePro have any more specific predicates?   Anything that distinguishes up from down ?

OK, then if it's ok, I think we should leave this one open, as we anticipate that molepro will add such predicates.

@vdancik request for update

Vlado indicates, Waiting for Chemical WG to implement changes. Mid August

Those are predicates that we don't have in MolePro, once these are done, it will be implemented

@vdancik Mid-August check-in.

ChemInfo WG finished harmonizing predicates this week, waiting for Biolink to incorporate the proposed changes.

MolePro TRAPI version 1.2 now handles this query.

@vdancik Running the A.8 query thru the ARAX User Interface still shows no results.
  "message": {
    "knowledge_graph": {
      "edges": {},
      "nodes": {}
    },
    "query_graph": {
      "edges": {
        "e0": {
          "object": "n1",
          "predicates": [
            "biolink:decreases_abundance_of",
            "biolink:decreases_activity_of",
            "biolink:decreases_expression_of",
            "biolink:decreases_synthesis_of",
            "biolink:increases_degradation_of",
            "biolink:disrupts",
            "biolink:entity_negatively_regulates_entity"
          ],
          "subject": "n0"
        }
      },
      "nodes": {
        "n0": {
          "categories": [
            "biolink:SmallMolecule"
          ],
          "is_set": false
        },
        "n1": {
          "ids": [
            "NCBIGene:1956"
          ],
          "is_set": false
        }
      }
    },
    "results": []
  },
  "validation_result": {
    "message": "",
    "n_edges": 0,
    "n_nodes": 0,
    "provenance_summary": {
      "n_sources": 0,
      "predicate_counts": {},
      "provenance_counts": {}
    },
    "size": "1 kB",
    "status": "PASS",
    "version": "1.1.1"
  },
  "araxui_provider": "ARS",
  "araxui_response": "6868e207-f028-4541-a814-07e92f2ac29b"
}

This is more of an ARS question. Works for MolePro's version that calls 1.2.

Post Trapi 1.2

https://arax.ncats.io/?source=ARS&id=fb3c0979-a809-4dc8-a064-931961be9717
https://github.com/NCATSTranslator/minihackathons/blob/main/2021-12_demo/workflowA/A.8_EGFR_simple.json

Molepro returning results
https://arax.ncats.io/?source=ARS&id=718eb8c4-5fbc-475c-a5f4-34ff390f28fe


unified oauth token expiration policy attribute name

Unified token expiration policy。
Before timeToKillInSeconds, maxTimeToLiveInSeconds different meanings in different tokens, misleading。
Refresh token should have number of uses limitations，
Change will allow administrators to use a more appropriate strategy：
For example, long-term effective refresh token, failure only after a defined number of times

Fix the formatting issues first so we can review. Thanks.

This will not make the cut for 5. I assigned this to @leleuj who's more familiar with this area to review.

Also I am not sure it makes sense for a refreshToken to ever expire after # number of attempts. I get that you are trying to make the organization of settings more consistent, but that change would not make sense to me.

Thanks

This will need to be rebased


[path_provider] getApplicationDocumentsDirectory() on iOS returns different values when relaunching the app

on my flutter app I use getApplicationDocumentsDirectory() to save data locally, but on IOS physical phone  getApplicationDocumentsDirectory() does not provide the same value when the app has been pushed from background apps and relaunch. Is there a workaround or do I have to use another local repository for local data ?

https://pub.dev/packages/path_provider

Thanks @alanassis ,
Yes, @jfboisvieux , try this plugin
Closing the issue
if you disagree please write in the comments and I will reopen it
Thank you

I tested both with getTemporaryDirectory() and getApplicationDocumentsDirectory() and in both cases on the iPhone (not on the emulator) the dir/file is different when the app is relaunched

I mean using the path_provider plugin of course.

This isn't a bug.  The path that you get returned will be something like this /var/mobile/Containers/Data/Application/D0497B41-0890-4C3F-B781-CEC94DB0248B/Documents. That hash code represents the installation of the app.  When you update the app again iOS will get assigned a new hash but the documents will be transferred over.
You can verify that it works yourself with the following code:
import 'package:flutter/material.dart';
import 'package:path_provider/path_provider.dart';
import 'dart:io';
import 'package:path/path.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key key, this.title}) : super(key: key);

  final String title;

  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  int _counter = 0;

  _MyHomePageState() {
    _readState();
  }

  void _readState() async {
    Directory dir = await getApplicationDocumentsDirectory();
    String filePath = join(dir.path, "test.txt");
    File file = File(filePath);
    if (await file.exists()) {
      String oldText = file.readAsStringSync();
      setState(() {
        _counter = int.parse(oldText);
      });
    }
  }

  void _incrementCounter() async {
    setState(() {
      _counter += 1;
    });
    Directory dir = await getApplicationDocumentsDirectory();
    String filePath = join(dir.path, "test.txt");
    File file = File(filePath);
    file.writeAsStringSync('$_counter');
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            Text(
              'You have pushed the button this many times:',
            ),
            Text(
              '$_counter',
              style: Theme.of(context).textTheme.headline4,
            ),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: Icon(Icons.add),
      ), // This trailing comma makes auto-formatting nicer for build methods.
    );
  }
}

That’s a very clear answer

Thank you so much for this answer, I had also this issue in an application.
This is not a bug from Flutter, but this iOS behaviour is totally awful


ICEES DILI production instance - Workflow B.1 one-hop spins

This issue is to report that the ICEES DILI production instance does not return results for the initial one-hop in the Workflow B.1 query. This may or may not be related to caching.

Hi Kara, could you post the query raw json so we can reproduce this issue please?

Sure thing. I tested the below query with one and with both input CURIES.
{
"message": {
"query_graph": {
"edges": {
"e00": {
"subject": "n00",
"object": "n01",
"predicates": [
"biolink:has_real_world_evidence_of_association_with"
]
}
},
"nodes": {
"n00": {
"ids": ["MONDO:0005359", "SNOMEDCT:197354009"],
"categories": [
"biolink:DiseaseOrPhenotypicFeature"
]
},
"n01": {
"categories": [
"biolink:DiseaseOrPhenotypicFeature"
]
}
}
},
"knowledge_graph": {
"nodes": {},
"edges": {}
},
"results": []
}
}

Note that Kenny was able to run a one-hop via direct CURL. In my experience, if Swagger fails, then CURL fails, and vice versa, but that appears to be an incorrect assertion. Alternatively, the issue may be related to connectivity issues on my end.

Oh no, I ran things through Swagger.

Oh, thanks for the clarification. In that case, I think we can close this issue.


model: add ActionDropIndexes

What problem does this PR solve?
Support to delete multiple indexes in one statement.
What is changed and how it works?
Add "ActionDropIndexes".
Check List
Tests

Unit test

Code changes

Has exported variable/fields change

Side effects

None

Related changes

Need to cherry-pick to the release branch
Need to update the documentation
Need to be included in the release note

@zimulala Hello,  I close the previous PR.

/LGTM

/cc @AilinKid


Local wifi pairing

Hello,
is there a way to pair climate with my wifi network in local mode, without to use app (and its cloud)?

No, I suggest that you can prevent the device from accessing the Internet after pairing
mac_zhou
在 2020年5月25日，21:17，bit111<EMAIL_ADDRESS>写道：
Hello,
is there a way to pair climate with my wifi network in local mode, without to use app (and its cloud)?

Ok, thanks.
So, can you tell me where I can find a tutorial to use your lib (eg. set temperature, move fan, etc.)?
Thanks.

if you use home assistant, you can use (https://github.com/mac-zhou/midea-ac-py)
or you can write code like this #5

if you use home assistant, you can use (https://github.com/mac-zhou/midea-ac-py)

It was exactly what I was looking for!

Looking at the SDK docs, it should probably be possible to send whatever MSmartUserDeviceManager.startConfigureDevice sends to provision the climate device.
I'd assume that it's using the same local interface used for controling the device?

As it turns out, the official app uses http which means that we can easily spin up a mock server.
This way it is possible to provision the device without using the cloud at all 🎉

@Hypfer were you able to get anywhere with this? I'm interested in doing this too

@kueblc
I didn't try local communication since my goal was to replace the cloud. While decryption of the first few cloud messages works, it seems like they're doing some kind of handshake there to get a session key or something.
After that, I wasn't able to decrypt further communication.
Since it's a replaceable USB dongle, it might make sense to just ditch it altogether and build a replacement.
https://community.home-assistant.io/t/any-support-for-midea-a-c/18742/151
According to this post it's possible but there wasn't any answer since that.
I tried attaching the dongle to multiple USB controllers. none of them recognized it so maybe it's just the USB form factor but actually speaks UART on the data pins?
If you feel like it, i'd suggest adding a logic analyzer there to take a look at what's happening.
You could use some cheap usb extension cord so that you don't have to solder stuff onto the USB dongle

Thanks for your quick response @Hypfer.
My goal is also to replace the cloud, but without physically disassembling the air conditioner. While it looks like @mac-zhou has reverse engineered most of the control over local communication, he still requires that you do the initial provisioning with the cloud. I'm interested in replacing this step with a local mock cloud and replicating the mechanism of the app, as you mentioned.
I started taking a look into the Android app and came to the same conclusion you did, that MSmartUserDeviceManager.startConfigureDevice is the entry point for whatever the app is doing to provision the device. This is how I found this issue thread. The obfuscated code is pretty dense however, so it's taking me some time to figure out. I was hoping that you could share your findings so far so that I don't end up repeating work.
It might be easier to understand if I could listen in on a device being provisioned, but as I do not want to connect my device to the cloud even once (in addition to sharing my information, it could potentially force a firmware update), I have no real world data to work from. If you have any captures of the provisioning process, would you mind sharing these as well?

@kueblc
I cannot share provisioning data since that would mean sharing my wifi credentials.
You can however use this mock backend to provision it yourself without any cloud access.
Be aware though that this is extremely hackish code.
mideamock.zip
I've used the Midea app Version <IP_ADDRESS>5 and redirected all the traffic to the mock backend via my router:
/etc/dnsmasq.d$ cat midea.conf
address=/appsmb.com/<IP_ADDRESS>
address=/www.appsmb.com/<IP_ADDRESS>
address=/mapp.appsmb.com/<IP_ADDRESS>
address=/app.appsmb.com/<IP_ADDRESS>
address=/jump.appsmb.com/<IP_ADDRESS>
address=/module.appsmb.com/<IP_ADDRESS>
address=/mapptest.appsmb.com/<IP_ADDRESS>
address=/midea.com/<IP_ADDRESS>
address=/www.midea.com/<IP_ADDRESS>
address=/qrcode.midea.com/<IP_ADDRESS>
address=/obm.midea.com/<IP_ADDRESS>
address=/air.midea.com/<IP_ADDRESS>
address=/airtest.midea.com/<IP_ADDRESS>

You can log-in with anything and then simply follow the provisioning procedure.
Furthermore, there are a few real messages in the testMideaMsg.js class.
Ignore the Header for switch-on/off & query-status command and Header for non-power-related command
Thats wrong. They don't differ at all apart from timestamps.

Thanks very much @Hypfer, I really appreciate you sharing your work so far. I will be sure to post back with any new findings.

Actually, I probably know how to do it.
But I am now mainly focused on the decryption of new network protocols.
Because after disconnecting the cloud, I must ensure that the local communication is normal.

i created a telegram group https://t.me/joinchat/BhU6LRytPXLsiqTIar0jqg 7
So that everyone can communicate better :joy:

I provide an easy way
After power off and restart, track DNS requests of midea devices
You will find 1 DNS request. After shielding this domain name resolution, the cloud is disconnected.
For example, on my side: iot1.midea.com.cn


Readme bug with all contributors and centered paragraphs

Will file a bug upstream

The all-contributors repo seems abandoned. Not much going on there, so I just fixed the README myself.


Use automatic broadcast and force_array

Jenkins, test this please.

Jenkins CI test (for commit f72d9c9fc0fd6f76077661cf2800b86b5440178e, target branch master) succeeded!


enums for cl_khr_image2d_from_buffer

While making the changes in #41 I noticed that we do not currently define enums for cl_khr_image2d_from_buffer in cl_ext.h.  Instead, the enums for this extension are in cl.h, protected by #ifdef CL_VERSION_1_2, and do not have the KHR suffix.  This doesn't seem correct.
One solution is to add suffixed versions of the enums to cl_ext.h, similar to what was done in #33 for the mipmap extension.  Note however, the extensions doc currently does not include a KHR suffix on the enums, so this may not be the right thing to do in this case.
Alternatively, we could add the un-suffixed enums to cl_ext.h if they aren't defined in cl.h, similar to what was done for subgroups (see #2).  This solution preserves source backwards compatibility.

In the March 5th teleconference we decided to:

Add KHR suffixed versions of these enums and add to cl_ext.h.
Change the #ifdef in cl.h so the un-suffixed enums are protected by CL_VERSION_2_0, not CL_VERSION_1_2, since the extension became a core feature in OpenCL 2.0.
Update the extension spec to refer to the KHR suffixed enums and not the un-suffixed enums.

I will create a PR in this repo for the first two changes and a PR in the spec repo for the last change.

Both the spec change and the headers change are merged, so I am closing this issue.


LevelZero sustained power limit support

Relates to #2449 feature request from github issues
Fixes #2449 change request from github issues.

This PR adds signals, controls, pruning, and save/restore logic for the sustained power limit interval, power, and enable defined in the sysman spec here
This support is based upon the 1.3.7 release and does not use the newer power limit extension (here).  Until the new extensions can be tested with GEOPM this should provide basic power capping support
Tasks keeping this in draft

[ ] Further testing of enable/disable control and pruning on live systems
[ ] Plan for supporting new vs old API interfaces in Level Zero or a roadmap of when the changes will be implemented for GEOPM.

Closing as the API has been deprecated.

This may be possible via SysfsIOGroup instead. See #3556


Design System > Components > File Management Tree> Default > Vertical node does not display proper.

Describe the bug
Vertical node does not display proper.
Steps to reproduce bug

Go to 'https://stage-react.raaghu.ai/'
Navigate to 'Design System > Components > File Management Tree> Default'

Actual result-
Vertical node does not display proper.
Screenshots

Expected result-
Vertical node display proper.
Desktop (please complete the following information):
-OS: [Windows 10 Enterprise]
-Browser [ edge]
-Version [ 125.0.2535.92]

Issue still exist on dev Vertical node does not display proper.

Fixed on staging

Reopen on staging

Fixed on stage


Add test for CFG alteration by compact IDs

The Compact IDs pass can corrupt the CFG, but first the CFG has to
be setup. To do this, a test that builds the CFG, then performs the
compact IDs pass, then checks context consistency.
Fixes https://github.com/KhronosGroup/SPIRV-Tools/issues/1648

@s-perron will probably want to take a look at this.


Create dataset loader for CCMatrix

Dataloader name: ccmatrix/ccmatrix.py
DataCatalogue: http://seacrowd.github.io/seacrowd-catalogue/card.html?ccmatrix

Dataset
ccmatrix

Description
The CCMatrix dataset was collected from web crawls and released by Meta. The dataset is constructed based on the margin-based bitext mining which can be applied to monolingual corpora of billions of sentences to produce high quality aligned translation data.

Subsets
-

Languages
jav, eng, vie, ind, tgl, mya, zlm

Tasks
Language Modeling, Machine Translation

License
BSD license family (bsd)

Homepage
https://opus.nlpl.eu/CCMatrix/corpus/version/CCMatrix

HF URL
https://huggingface.co/datasets/yhavinga/ccmatrix

Paper URL
https://aclanthology.org/2021.acl-long.507/

#self-assign


Integrate Mocha with TypeScript

This issue proposes considering the use of TypeScript again to write the test files. While there is a TS-Mocha package available to integrate Mocha with TypeScript, it should be noted that there is an issue with Yarn P'n'P, which is currently being used in this project.

Deprecated after #102.


feat(tier4_autoware_api_launch): add tier4_autoware_api_launch package

Signed-off-by: mitsudome-r<EMAIL_ADDRESS>Description
This PR adds tier4_autoware_api_launch package to the repository which is required to connect Autoware with TIER IV's scenario simulator.
For the details, please refer to https://github.com/autowarefoundation/autoware.universe/issues/656.

Related links
https://github.com/autowarefoundation/autoware.universe/issues/656

Tests performed
Follow the installation instruction from the documentation and confirm that it build without an error.

Notes for reviewers
This PR depends on https://github.com/autowarefoundation/autoware/pull/156

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@mitsudome-r Where did you copy these files from?
It seems to be a bit different from https://github.com/tier4/autoware_launch/tree/tier4/universe/autoware_api_launch. :thinking:
@isamu-takagi Could you check this just in case? :pray:

@mitsudome-r Where did you copy these files from? It seems to be a bit different from https://github.com/tier4/autoware_launch/tree/tier4/universe/autoware_api_launch. thinking

I apologize that I forgot to mention in the description. I have copied from the same link, but I removed the ones that are not necessary for the scenario simulator at the moment. I was thinking it might be better if we add:

path_distance_calculator once we agree on how we handle safety
rosbridge_websocket_launch once we agree on how we communicate through web interface


Don't sync unconfirmed txids when syncing bdk

This is what @notmandatory recommended we do in discord, this seems a little unsafe to me as we aren't getting the status of these txs anymore, but maybe its fine because it'd always be associated with our spks anyways.

this seems a little unsafe to me as we aren't getting the status of these txs anymore

Is this when the transaction confirms? If there's any problems, a resync should fix it, right?

Is this when the transaction confirms? If there's any problems, a resync should fix it, right?

Well when we sync we only check unused spks, but since this address would have a transaction it would be used and we'd stop checking it

Made no difference, still 117 requests on my mainnet wallet.

Feel free to test this on mainnet too @benthecarman

wasn't needed


Generate a trimmed down version of the JSON

We don't use all the information that's the in JSON, yet we ship all of it off to browserify. That's 600K; on its own that's 20% of the Reader (another 25% being jsonld.js).

We should start on this soon as the latest @context is significantly bigger see https://github.com/scienceai/schema.org/commit/81b3ca16ac3be90b0ad4f1b992724b181705a4db.


Reduce build time when cranelift only used for wasm

Feature
Currently I use wasmtime as a WASM runtime for embedding wasm execution in my rust project.
Compiling wasmtime and dependencies is quite a bit longer than the other wasm runtime my project supports.
I see the cranelift compile for cranelift-native included and was wondering if it could be made optional via a feature.
Benefit
Faster compile times, locally and in CI.
Implementation
Use rust "features" to allow opt-in or opt-out (via disable-all and then opt in on some) of some subset of wasmtime/cranelift functionality.
Alternatives
Can't think of any obvious ones.

There are pretty much no features of cranelift-codegen that aren't used that aren't required for wasm compilation. There are a couple of other smaller crates that are part of cranelift, but wasmtime only depends on those that are actually needed for wasm compilation (eg cranelift-wasm and it's dependency cranelift-frontend)

I see the cranelift compile for cranelift-native included and was wondering if it could be made optional via a feature.

Wasmtime doesn't depend on the cranelift-native crate, so it shouldn't be compiled in the first place.
You can disable the default features of wasmtime. This will disable support for perf jitdump (only compiled on linux anyway and used to assist with profiling using perf), disable reading textual wat files, disable parallel compilation (avoids a dependency on rayon), and disable support for wasi-nn (neural networks). If you are using wasmtime as library instead of executable, disabling the default features will also disable cranelift entirely (instead you have to load files pre-compiled by wasmtime, you probably want to re-enable the feature), disable support for caching compilation results and disable support for async fn.
https://github.com/bytecodealliance/wasmtime/blob/937b319e2d45497dc7a87ff8c18c3b10fa9e1b97/crates/wasmtime/Cargo.toml#L54
Together this will reduce the dependency count to just 57 crates.

I guess there could be an option to disable WASI support entirely, which should save some time.

Reviewing output, I stand corrected. It's docs and checking that hit the native stuff:
   Compiling cranelift-codegen v0.77.0
 Documenting flowsamples v0.36.0 (/Users/andrew/workspace/flow/samples)
    Checking cranelift-frontend v0.77.0
    Checking cranelift-native v0.77.0
    Checking cranelift-wasm v0.77.0

Thanks for the other suggestions, I will try them!
(Feel free to close issue if you agree)

Maybe for the benefit of others, I ended up with this, which is enough for me to load and execute a WASM module (compiled with rustc) to .wasm
wasmtime = { version = "0.30.0", default-features = false, features = ["cranelift"], optional = true }

I'm going to close this issue because I don't think there's an obvious low-hanging fruit to pick here and otherwise refactoring to reduce build times is always a welcome improvement and doesn't necessarily need an issue to track.


flaky test: test_crafted_wal_end , could not compact, repartitioning keyspace failed

Steps to reproduce
https://neon-github-public-dev.s3.amazonaws.com/reports/pr-7053/8235220820/index.html#suites/d8ba47b82ce2682e74c5199a236af4ab/a84a41f87b2d1240/
Expected result
Actual result
/github/home/.cache/pypoetry/virtualenvs/neon-_pxWMzVK-py3.9/lib/python3.9/site-packages/allure_commons/_allure.py:221: in __call__
    return self._fixture_function(*args, **kwargs)
test_runner/fixtures/neon_fixtures.py:1365: in neon_env_builder
    yield builder
test_runner/fixtures/neon_fixtures.py:943: in __exit__
    pageserver.assert_no_errors()
test_runner/fixtures/neon_fixtures.py:2334: in assert_no_errors
    assert not errors
E   AssertionError: assert not [(126, '2024-03-11T15:34:01.787585Z ERROR compaction_loop{tenant_id=939fc7c48bff336ad16d17d5e7ce2c64 shard_id=0000}:compact_timeline{timeline_id=601c2df30d55ec1f16106c4e1bf0ae69}: could not compact, repartitioning keyspace failed: Bad state (not active)\n')]

seems like a race condition?
Environment
Logs, links

https://neondb.slack.com/archives/C033RQ5SPDH/p1710401132362199

Is this a duplicate of https://github.com/neondatabase/neon/issues/4691 ?  Until this test is stable we can probably use that one ticket to track it.

yep thanks for the pointer


DocsArchive-<IP_ADDRESS>Auto archive content

Auto archive content from https://github.com/VSC-Service-Account/docs-archive-test-source.git

Docs Build status updates of commit 0441d57:
:warning: Validation status: warnings

File
Status
Preview URL
Details

archiveTargetFolder/content/someContent.md
:warning:Warning
View
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

.openpublishing.redirection.json
:white_check_mark:Succeeded

archiveTargetFolder/TOC.yml
:white_check_mark:Succeeded
View

archiveTargetFolder/breadcrumb/E2EArchiveTarget_8f5f98ab-837b-468d-a0a7-b1a116914b39/toc.yml
:white_check_mark:Succeeded

archiveTargetFolder/content/sql-database-engine.png
:white_check_mark:Succeeded
View

archiveTargetFolder/docfx.json
:white_check_mark:Succeeded

archiveTargetFolder/content/someContent.md

[Warning-author-missing] Missing attribute: author. Add the current author's GitHub ID.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Error when try to update

Hello.
Thanks for make amazing hugo theme. I use anatole for my personal blog.
Describe the bug
I try to update my anatole theme with run this command in my terminal.
hugo mod get -u github.com/lxndrblz/anatole
but it showing error:
go: go.mod file not found in current directory or any parent directory.         'go get' is no longer supported outside a module.         To build and install a command, use 'go install' with a version,         like 'go install example.com/cmd@latest'         For more information, see https://golang.org/doc/go-get-install-deprecation         or run 'go help get' or 'go help install'.
To Reproduce
Run hugo mod get -u github.com/lxndrblz/anatole in terminal
Screenshots

Desktop (please complete the following information):

OS: Linux (Zorin OS 16,2)
Version of the Theme
Version of Hugo (run a hugo version if unsure)

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version of Hugo: Hugo Static Site Generator v0.68.3/extended linux/amd64 BuildDate: 2020-03-25T06:15:45Z

Thanks.

@lxndrblz Can you please confirm that you executed the command in the correct directory? Based on the error message it sounds as the mod go.mod file could not be located.

go.mod? Sorry, Am i must run go mod init before update?

This problem solved, with run go mod init.
Thanks @lxndrblz


embedding Mac frameworks crashes with an exception

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

create a basic flutter app: flutter create basic_app
from the flutter app, build mac frameworks: flutter build macos-framework
create an XCode app
insert the two previously built frameworks (FlutterMacOS & App) to the XCode app (I had to add an explicit copy step to codesign the added frameworks)
add a Swift Window class with the skeleton described in FlutterViewController.h (example code below)
in the storyboard, assign the above window class to the main window
try to run the XCode app; it will stop with an exception where the FlutterViewController is created

I tried the same thing with a previous flutter version (iirc, ca. 2 months ago) and back then it worked as expected. I'm using the latest MacOS (13.4) and the latest XCode (14.3), but the same happened with an older MacOS (12.x)
Expected results
FlutterViewController being created without exception
Actual results
When creating the view controller (let flutterViewController = FlutterViewController()), an exception is raised and the program stops. The exception says
"-[MacApp4.AppDelegate setTerminationHandler:]: unrecognized selector sent to instance 0x600003c3c000"
Code sample
Code sample
import Cocoa
import FlutterMacOS

class MainFlutterWindow: NSWindow {
  override func awakeFromNib() {
    let flutterViewController = FlutterViewController()
    let windowFrame = self.frame
    self.contentViewController = flutterViewController
    self.setFrame(windowFrame, display: true)

    //RegisterGeneratedPlugins(registry: flutterViewController)

    super.awakeFromNib()
  }
}

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.10.1, on macOS 13.4 22F66 darwin-x64, locale de-DE)
[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
[✓] Chrome - develop for the web
[!] Android Studio (not installed)
[✓] VS Code (version 1.78.2)
[✓] Connected device (2 available)
[✓] Network resources

! Doctor found issues in 2 categories.

Hi @woolfman007
Can you please share the complete sample project? It would be appreciated if you could push it into a GitHub repository so we can pull and try reproducing it. Thank you!

sure, here you go:
https://github.com/woolfman007/flutter_framework_embedding.git
Just clone, run flutter build macos-framework in the flutter project folder, then run the XCode project. I'm trying that on an Intel Mac, haven't tried it on silicon yet.

Thank you for providing the complete sample. I can see the issue as well.
Taking a look at the error message, it seems to be similar to https://github.com/flutter/flutter/issues/124829, Steps to reproduce are not the same, though.
Also, I checked this on Flutter 3.7.12 but it had another crash. Do you remember which Flutter version the issue doesn't happen?

Hi huycozy, the actual project is on a different machine, which is a little tricky to access right now; however, I have the resp. pubspec.yaml at hand. There it says:
  sdk: ">=2.17.0 <3.0.0" ```

So, it seems it's pre-3.0 Does that help in any way?

Thanks for your response.
Per https://github.com/flutter/flutter/issues/124829#issuecomment-1509312490, that issue doesn't happen on stable 3.7.11 but still on beta and master. Keeping this open for further insights.
Flutter stable & master: unrecognized selector sent to instance

crash stack
2023-05-26 11:33:21.381895+0700 MacApp4[76733:12245020] -[MacApp4.AppDelegate setTerminationHandler:]: unrecognized selector sent to instance 0x6000028901a0
2023-05-26 11:33:21.397660+0700 MacApp4[76733:12245020] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[MacApp4.AppDelegate setTerminationHandler:]: unrecognized selector sent to instance 0x6000028901a0'
*** First throw call stack:
(
	0   CoreFoundation                      0x00007ff81a53743b __exceptionPreprocess + 242
	1   libobjc.A.dylib                     0x00007ff81a086e25 objc_exception_throw + 48
	2   CoreFoundation                      0x00007ff81a5ce56b -[NSObject(NSObject) __retain_OA] + 0
	3   CoreFoundation                      0x00007ff81a4a169b ___forwarding___ + 1324
	4   CoreFoundation                      0x00007ff81a4a10d8 _CF_forwarding_prep_0 + 120
	5   FlutterMacOS                        0x00000001072d610d -[FlutterEngineTerminationHandler initWithEngine:terminator:] + 237
	6   FlutterMacOS                        0x00000001072d7390 -[FlutterEngine initWithName:project:allowHeadlessExecution:] + 496
	7   FlutterMacOS                        0x00000001072f6d04 _ZL10CommonInitP21FlutterViewControllerP13FlutterEngine + 116
	8   FlutterMacOS                        0x00000001072f70fe -[FlutterViewController initWithNibName:bundle:] + 126
	9   MacApp4                             0x0000000101639f73 $sSo21FlutterViewControllerCABycfcTO + 19
	10  MacApp4                             0x0000000101639b9f $sSo21FlutterViewControllerCABycfC + 31
	11  MacApp4                             0x0000000101639989 $s7MacApp417MainFlutterWindowC12awakeFromNibyyF + 89
	12  MacApp4                             0x0000000101639bec $s7MacApp417MainFlutterWindowC12awakeFromNibyyFTo + 28
	13  CoreFoundation                      0x00007ff81a4b3976 -[NSSet makeObjectsPerformSelector:] + 231
	14  AppKit                              0x00007ff81d5bef17 -[NSIBObjectData nibInstantiateWithOwner:options:topLevelObjects:] + 1367
	15  AppKit                              0x00007ff81d634f9b -[NSNib _instantiateNibWithExternalNameTable:options:] + 656
	16  AppKit                              0x00007ff81d634c16 -[NSNib _instantiateWithOwner:options:topLevelObjects:] + 143
	17  AppKit                              0x00007ff81de53e0f -[NSStoryboard _instantiateControllerWithIdentifier:creator:storyboardSegueTemplate:sender:] + 470
	18  AppKit                              0x00007ff81d5a5010 NSApplicationMain + 745
	19  MacApp4                             0x000000010163a2b4 $sSo21NSApplicationDelegateP6AppKitE4mainyyFZ + 36
	20  MacApp4                             0x000000010163a287 $s7MacApp411AppDelegateC5$mainyyFZ + 39
	21  MacApp4                             0x000000010163a318 main + 24
	22  dyld                                0x00007ff81a0b3310 start + 2432
)
2023-05-26 11:33:21.398180+0700 MacApp4[76733:12245020] [General] An uncaught exception was raised
2023-05-26 11:33:21.398236+0700 MacApp4[76733:12245020] [General] -[MacApp4.AppDelegate setTerminationHandler:]: unrecognized selector sent to instance 0x6000028901a0
2023-05-26 11:33:21.398322+0700 MacApp4[76733:12245020] [General] (
	0   CoreFoundation                      0x00007ff81a53743b __exceptionPreprocess + 242
	1   libobjc.A.dylib                     0x00007ff81a086e25 objc_exception_throw + 48
	2   CoreFoundation                      0x00007ff81a5ce56b -[NSObject(NSObject) __retain_OA] + 0
	3   CoreFoundation                      0x00007ff81a4a169b ___forwarding___ + 1324
	4   CoreFoundation                      0x00007ff81a4a10d8 _CF_forwarding_prep_0 + 120
	5   FlutterMacOS                        0x00000001072d610d -[FlutterEngineTerminationHandler initWithEngine:terminator:] + 237
	6   FlutterMacOS                        0x00000001072d7390 -[FlutterEngine initWithName:project:allowHeadlessExecution:] + 496
	7   FlutterMacOS                        0x00000001072f6d04 _ZL10CommonInitP21FlutterViewControllerP13FlutterEngine + 116
	8   FlutterMacOS                        0x00000001072f70fe -[FlutterViewController initWithNibName:bundle:] + 126
	9   MacApp4                             0x0000000101639f73 $sSo21FlutterViewControllerCABycfcTO + 19
	10  MacApp4                             0x0000000101639b9f $sSo21FlutterViewControllerCABycfC + 31
	11  MacApp4                             0x0000000101639989 $s7MacApp417MainFlutterWindowC12awakeFromNibyyF + 89
	12  MacApp4                             0x0000000101639bec $s7MacApp417MainFlutterWindowC12awakeFromNibyyFTo + 28
	13  CoreFoundation                      0x00007ff81a4b3976 -[NSSet makeObjectsPerformSelector:] + 231
	14  AppKit                              0x00007ff81d5bef17 -[NSIBObjectData nibInstantiateWithOwner:options:topLevelObjects:] + 1367
	15  AppKit                              0x00007ff81d634f9b -[NSNib _instantiateNibWithExternalNameTable:options:] + 656
	16  AppKit                              0x00007ff81d634c16 -[NSNib _instantiateWithOwner:options:topLevelObjects:] + 143
	17  AppKit                              0x00007ff81de53e0f -[NSStoryboard _instantiateControllerWithIdentifier:creator:storyboardSegueTemplate:sender:] + 470
	18  AppKit                              0x00007ff81d5a5010 NSApplicationMain + 745
	19  MacApp4                             0x000000010163a2b4 $sSo21NSApplicationDelegateP6AppKitE4mainyyFZ + 36
	20  MacApp4                             0x000000010163a287 $s7MacApp411AppDelegateC5$mainyyFZ + 39
	21  MacApp4                             0x000000010163a318 main + 24
	22  dyld                                0x00007ff81a0b3310 start + 2432
)
libc++abi: terminating with uncaught exception of type NSException
(lldb)

flutter doctor -v (stable and master)
[✓] Flutter (Channel stable, 3.10.2, on macOS 13.0.1 22A400 darwin-x64, locale en-VN)
    • Flutter version 3.10.2 on channel stable at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 9cd3d0d9ff (22 hours ago), 2023-05-23 20:57:28 -0700
    • Engine revision 90fa3ae28f
    • Dart version 3.0.2
    • DevTools version 2.23.1

[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 32.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] VS Code (version 1.78.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.64.0

[✓] Connected device (3 available)
    • RMX2001 (mobile) • EUYTFEUSQSRGDA6D • android-arm64  • Android 11 (API 30)
    • macOS (desktop)  • macos            • darwin-x64     • macOS 13.0.1 22A400 darwin-x64
    • Chrome (web)     • chrome           • web-javascript • Google Chrome 113.0.5672.126

[✓] Network resources
    • All expected network resources are available.

• No issues found!

[!] Flutter (Channel master, 3.11.0-14.0.pre.26, on macOS 13.0.1 22A400 darwin-x64, locale en-VN)
    • Flutter version 3.11.0-14.0.pre.26 on channel master at /Users/huynq/Documents/GitHub/flutter_master
    ! Warning: `flutter` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 6c2041e1e9 (54 minutes ago), 2023-05-25 22:17:26 -0400
    • Engine revision 593d4d6b1f
    • Dart version 3.1.0 (build 3.1.0-147.0.dev)
    • DevTools version 2.23.1
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 32.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] VS Code (version 1.78.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.64.0

[✓] Connected device (3 available)
    • RMX2001 (mobile) • EUYTFEUSQSRGDA6D • android-arm64  • Android 11 (API 30)
    • macOS (desktop)  • macos            • darwin-x64     • macOS 13.0.1 22A400 darwin-x64
    • Chrome (web)     • chrome           • web-javascript • Google Chrome 113.0.5672.126

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

Flutter 3.3.10 & 3.7.12: Out of memory

crash stack
2023-05-26 11:30:03.376563+0700 MacApp4[75889:12237263] Metal API Validation Enabled
Exhausted heap space, trying to allocate 32 bytes.
../../third_party/dart/runtime/vm/object.cc: 2727: error: Out of memory.
version=2.18.6 (stable) (Tue Dec 13 21:15:14 2022 +0000) on "macos_x64"
pid=75889, thread=259, isolate_group=vm-isolate(0x7f896689fc00), isolate=vm-isolate(0x7f89668a4800)
isolate_instructions=110e9d180, vm_instructions=110e9d180
  pc 0x0000000110ffb185 fp 0x00007ff7b5163770 dart::Profiler::DumpStackTrace(void*)+0x85
  pc 0x0000000110e9d394 fp 0x00007ff7b5163850 dart::Assert::Fail(char const*, ...) const+0x84
  pc 0x0000000110f72cfe fp 0x00007ff7b51638a0 dart::Object::Allocate(long, long, dart::Heap::Space, bool)+0x12e
  pc 0x0000000110fa2d70 fp 0x00007ff7b5163910 dart::Code::FinalizeCode(dart::FlowGraphCompiler*, dart::compiler::Assembler*, dart::Code::PoolAttachment, bool, dart::CodeStatistics*)+0xc0
  pc 0x0000000110fa31cf fp 0x00007ff7b5163940 dart::Code::FinalizeCodeAndNotify(char const*, dart::FlowGraphCompiler*, dart::compiler::Assembler*, dart::Code::PoolAttachment, bool, dart::CodeStatistics*)+0x2f
  pc 0x000000011107de18 fp 0x00007ff7b5163a80 dart::StubCode::Generate(char const*, dart::compiler::ObjectPoolBuilder*, void (*)(dart::compiler::Assembler*))+0xb8
  pc 0x000000011107dcc0 fp 0x00007ff7b5163b30 dart::StubCode::Init()+0xd0
  pc 0x0000000110ee862f fp 0x00007ff7b5164160 dart::Dart::DartInit(Dart_InitializeParams const*)+0x4df
  pc 0x0000000110ee88f1 fp 0x00007ff7b5164180 dart::Dart::Init(Dart_InitializeParams const*)+0x31
  pc 0x0000000110e5955d fp 0x00007ff7b51642e0 DartVMInitializer::Initialize(Dart_InitializeParams*, bool, bool)+0x2d
  pc 0x0000000110e58157 fp 0x00007ff7b5164500 flutter::DartVM::DartVM(std::__1::shared_ptr<flutter::DartVMData const>, std::__1::shared_ptr<flutter::IsolateNameServer>)+0xbb7
  pc 0x0000000110e5746d fp 0x00007ff7b5164cb0 flutter::DartVM::Create(flutter::Settings, fml::RefPtr<flutter::DartSnapshot const>, fml::RefPtr<flutter::DartSnapshot const>, std::__1::shared_ptr<flutter::IsolateNameServer>)+0x12d
  pc 0x0000000110e5a0d2 fp 0x00007ff7b5165460 flutter::DartVMRef::Create(flutter::Settings, fml::RefPtr<flutter::DartSnapshot const>, fml::RefPtr<flutter::DartSnapshot const>)+0x232
  pc 0x0000000110cb8644 fp 0x00007ff7b51662b0 flutter::Shell::Create(flutter::PlatformData const&, flutter::TaskRunners, flutter::Settings, std::__1::function<std::__1::unique_ptr<flutter::PlatformView, std::__1::default_delete<flutter::PlatformView> > (flutter::Shell&)> const&, std::__1::function<std::__1::unique_ptr<flutter::Rasterizer, std::__1::default_delete<flutter::Rasterizer> > (flutter::Shell&)> const&, bool)+0x144
  pc 0x0000000110e868ba fp 0x00007ff7b5166ac0 flutter::EmbedderEngine::LaunchShell()+0x9a
  pc 0x0000000110e705fb fp 0x00007ff7b5166c00 FlutterEngineRunInitialized+0x17b
  pc 0x00000001105bc07b fp 0x00007ff7b5166f60 -[FlutterEngine runWithEntrypoint:]+0x6eb
  pc 0x00000001105d91a4 fp 0x00007ff7b5166f90 -[FlutterViewController launchEngine]+0x54
  pc 0x00000001105d8f35 fp 0x00007ff7b5166fc0 -[FlutterViewController viewWillAppear]+0x65
  pc 0x00007ff81d70c08c fp 0x00007ff7b5166fe0 -[NSViewController _sendViewWillAppear]+0x28
  pc 0x00007ff81d70bf4d fp 0x00007ff7b5167010 -[NSViewController _windowWillOrderOnScreen]+0x62
  pc 0x00007ff81df123c9 fp 0x00007ff7b5167110 -[NSView _windowWillOrderOnScreen]+0x43
  pc 0x00007ff81df1245f fp 0x00007ff7b5167210 -[NSView _windowWillOrderOnScreen]+0xd9
  pc 0x00007ff81d70bdd6 fp 0x00007ff7b5167240 -[NSWindow _doWindowWillBeVisibleAsSheet:]+0x3b
  pc 0x00007ff81df2a7b1 fp 0x00007ff7b5167360 -[NSWindow _reallyDoOrderWindowAboveOrBelow:]+0x53a
  pc 0x00007ff81df2b413 fp 0x00007ff7b5167390 -[NSWindow _reallyDoOrderWindow:]+0x63
  pc 0x00007ff81df2b689 fp 0x00007ff7b5167450 -[NSWindow _doOrderWindow:]+0x127
  pc 0x00007ff81d6ff62a fp 0x00007ff7b5167470 -[NSWindow makeKeyAndOrderFront:]+0x2f
  pc 0x00007ffa361d180a fp 0x00007ff7b51674f0 -[QLSeamlessDocumentOpener showWindow:contentFrame:withBlock:]+0xa9
  pc 0x00007ff81d802900 fp 0x00007ff7b51675a0 -[NSWindowController showWindow:]+0x2a0
  pc 0x00007ff81d5a510c fp 0x00007ff7b51675f0 NSApplicationMain+0x3e5
  pc 0x000000010ad9c2b4 fp 0x00007ff7b5167610 $sSo21NSApplicationDelegateP6AppKitE4mainyyFZ+0x24
  pc 0x000000010ad9c287 fp 0x00007ff7b5167630 $s7MacApp411AppDelegateC5$mainyyFZ+0x27
  pc 0x000000010ad9c318 fp 0x00007ff7b5167650 main+0x18
  pc 0x00007ff81a0b3310 fp 0x00007ff7b51678f0 start+0x980
-- End of DumpStackTrace
(lldb)

Hi @huycozy,
thanks very much for your investigations. Does that mean, that it'll work on 3.7.11? I'll check that. Otherwise, will there be a fix?

Does that mean, that it'll work on 3.7.11?

@woolfman007 No, this issue still appears as I mentioned above (Out of memory error). I mean issue #124829 didn't appear on 3.7.11.
What I am summarizing above is: there is a difference between the two issues on Flutter versions (for some specific reason that needs further investigation). The error message on the latest version can be seen to be similar, though (unrecognized selector sent to instance). Hope this explanation is more clear :)

@huycozy thanks for the clarification. I just made a test with 2.13 and also encountered the out of memory issue. Can you tell when there might be a fix? I'm facing a major strategic decision in this regarding the product I'm building...

@woolfman007 Please see https://github.com/flutter/flutter/wiki/Issue-hygiene#when-will-my-bug-be-fixed

This looks like your app delegate isn't extending FlutterAppDelegate.  If you extend that, then it should support the missing selector.

@woolfman007 I have the same use case as you, running Flutter as a plug-in hosted in another app. I figured out a workaround for the time being. But it would be nice if Flutter would check if the app delegate responds to the selector before invoking it.
Workaround:

void setTerminationHandler_(_Nonnull id self, _Nonnull SEL cmd, _Nullable id handler) {
    // We don't need to handle termination.
}

/// Makes the current NSApplication's delegate understand the selector "setTerminationHandler:". Flutter calls this on initialization and fails
/// if the app delegate doesn't understand it (https://github.com/flutter/flutter/issues/124829#issuecomment-1608228991).
/// Host app delegate doesn't understand it of course, so we need to add it on-the-fly. The handler doesn't need to do anything in our case.
NS_INLINE void modifyAppDelegate() {
    Class appDelegateClass = [[[NSApplication sharedApplication] delegate] class];
    const SEL selector = @selector(setTerminationHandler:);
    if ([appDelegateClass instancesRespondToSelector:selector]) {
        printf("Modifying app delegate was not necessary");
        return;
    }
    printf("Modifying the app delegate...\n");
    class_addMethod(appDelegateClass, selector, (IMP)setTerminationHandler_, "v@:@");
}

@woolfman007 I have the same use case as you, running Flutter as a plug-in hosted in another app. I figured out a workaround for the time being. But it would be nice if Flutter would check if the app delegate responds to the selector before invoking it.
Workaround:
void setTerminationHandler_(_Nonnull id self, _Nonnull SEL cmd, _Nullable id handler) {
    // We don't need to handle termination.
}

/// Makes the current NSApplication's delegate understand the selector "setTerminationHandler:". Flutter calls this on initialization and fails
/// if the app delegate doesn't understand it (https://github.com/flutter/flutter/issues/124829#issuecomment-1608228991).
/// Host app delegate doesn't understand it of course, so we need to add it on-the-fly. The handler doesn't need to do anything in our case.
NS_INLINE void modifyAppDelegate() {
    Class appDelegateClass = [[[NSApplication sharedApplication] delegate] class];
    const SEL selector = @selector(setTerminationHandler:);
    if ([appDelegateClass instancesRespondToSelector:selector]) {
        printf("Modifying app delegate was not necessary");
        return;
    }
    printf("Modifying the app delegate...\n");
    class_addMethod(appDelegateClass, selector, (IMP)setTerminationHandler_, "v@:@");
}

phantastic, thanks for sharing! It seems to be a viable workaround for now! Still let's hope they provide a real fix soon

I am working on a "real" fix in this PR: https://github.com/flutter/engine/pull/43425

oh, brilliant! I missed that you already mentioned that. Thanks so much!


Fix user.update username not working

Type of change

[x] 🐛 Bug fix

Packages affected

[x] @clerk/types

Description

[x] npm test runs as expected.
[x] npm run build runs as expected.

Removes username from the user.update method (which does not work).
Fixes issue number #1494.

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


Container-level SAS URL does not include specific blob name even when blob is selected

Storage Explorer Version: 1.0.0 and 0.9.x
OS Version: Windows and other
Steps to Reproduce:

Use Azure Storage Explorer to browse to a specific blob in a storage account container
Right-click the specific blob and select "Get Shared Access Signature..." context menu option
Check the "Generate container-level shared access signature URI"
Click "Create"
Review the URL value generated on the next page and notice that it does not include the specific blob name but only the container name (e.g. https://storageaccount1.blob.core.windows.net/container1?st=2018-04-18T02%3A44%3A43Z&se=2018-04-19T02%3A44%3A43Z&sp=rl&sv=2017-04-17&sr=c&sig=FdqPP3vI%2BACAsignatureD3it2Yqrc%3D)

Expected Experience:
Users of previous versions of Azure Storage Explorer are used to being able to generate container-level SAS for specific blobs and had the URL contain the blob name when right-clicking specific blob (e.g. https://storageaccount1.blob.core.windows.net/container1/my/specific/blob1.vhd?st=2018-04-18T02%3A44%3A43Z&se=2018-04-19T02%3A44%3A43Z&sp=rl&sv=2017-04-17&sr=c&sig=FdqPP3vI%2BACAsignatureD3it2Yqrc%3D)
Actual Experience:
Latest version of Azure Storage Explorer (including 1.0.0) only includes container name in the container-level SAS URL even if user explicitly selects a specific blob prior to generating the SAS URL. Granted, users can append the blob name into the container-level SAS URL manually, but this process is error prone. In addition, users who are used to previous behavior copy the generated SAS URL assuming it contains blob-name within it while it does not.

Can you pinpoint what version this last worked as expected?

Merged into master


Wiki page

what is the purpose of this ticket?

@h1alexbel do something like this to reach an audience

@l3r8yJ looks inspiring!


Using 'latest' for a few of docker images

Using the 'latest' tag in a docker image definition is a dangerous practice, especially if the that can point at unstable images. That's the case for both the 'geth' and the 'prysmctl' images.
The recent problem with prysmctl, related to inclusion of incoming Electra work, was mentioned in #55 or #49, but there are more example of user hitting unstable image (e.g. #41).
One of the recent changes to geth caused the Failed to get EIP-1559 fees issue, which seems to be related to https://github.com/ethereum/go-ethereum/issues/29880.
The solution is to lock the version of all images (at least the ones not using the stable tag).

Example of a fix: https://github.com/ivy-net/eth-pos-devnet/pull/2


Pass currentSlide and slideCount props to arrow components

My use case for this was to change the last slide's arrow from saying "Next" to "Done". The default arrows have access to these props and use them to set a disabled class. It seems only fair that custom arrows have these props as well 😄 .
I found it difficult to use the beforeChange handler alone to achieve this without causing the entire carousel to re-render. That was bad because it prevented the slide transitions from animating.

This is now causing in 0.14.6:
warning.js?8a56:36 Warning: Unknown props `currentSlide`, `slideCount` on <button> tag. Remove these props from the element. For details, see https://fb.me/react-unknown-prop
    in button (created by PrevArrow)
    in PrevArrow (created by InnerSlider)
    in div (created by InnerSlider)
    in InnerSlider (created by Slider)
    in Slider (created by Categories)
    in div
    in Categories (created by Unknown)
    in MediaQuery
    in div
    in Unknown
    in div
    in div
    in DayPlanner
    in div
    in div
    in Planner (created by PlannerHandler)
    in PlannerHandler

same warning here


⚡ Omdet Turbo autodistill package

Search before asking

[X] I have searched the Autodistill issues and found no similar feature requests.

Description
☄ Actions
I have created a package for Omdet-Turbo in autodistill, (https://github.com/german36-del/autodistill-omdet_turbo).
You can check the paper here https://arxiv.org/abs/2403.06892 and the original code here https://github.com/om-ai-lab/OmDet.
💭 Theory
Omdet Turbo is a lightweight model for zero-shot detection that achieves impressive detection speed while maintaining state of the art detection performance making it a perfect option for real time zero shot detection or for speeding up the autolabeling process.
Use case
This feature can be used in real time applications and also for accelerating the process of autolabeling for testing or when working with big amounts of data.
Additional
No response
Are you willing to submit a PR?

[X] Yes I'd like to help by submitting a PR!

This could help to address #177 also.

Hello @capjamesg is this repo still in development? I could add more models like rt-detr if you see it convenient. Thanks!


Add app insights connection string to env. Remove env duplicates.

Resolves #3201 #3354 #2956

App Insights is deprecating APPINSIGHTS_INSTRUMENTATIONKEY and docs point people towards using the connection string env variable instead, so this adds that to our common env files.
This also fixes and issue with duplicate values in the env file. If for some reason differing values are added to the same key, those will remain.
Starting a changelog for stress-test-addons changes.

/check-enforcer override


GRID-274: Avoid formatting on type-to-edit

@joneit I don't have the confidence to review this. You can use your judgement here


Consistency of repaq, and readiness for production

Hi! We're considering using repaq due to the significant space savings, but have some concerns about lossless-ness. Some of the other issues (#11, #12, #13) seem to suggest that repaq isn't lossless, but there isn't enough detail on some (#12, #13) to determine the severity.
How production ready is repaq?

@sfchen

Actually my company has already used repaq for production since 2018.
But I will address these issues in about 2 months.

addressed