spawn_batch leaks memory when called with an iterator that does not have an exact size_hint

With this test case on master:
#[test]
fn spawn_batch_unexact() {
    struct Unhint<I>(I);
    impl<I: Iterator> Iterator for Unhint<I> {
        type Item = I::Item;

        fn next(&mut self) -> Option<Self::Item> {
            self.0.next()
        }

        fn size_hint(&self) -> (usize, Option<usize>) {
            (0, None)
        }
    }

    let mut world = World::new();
    world.spawn_batch(Unhint((0..100).map(|x| (x, "abc"))));
    let entities = world
        .query::<&i32>()
        .iter()
        .map(|(_, &x)| x)
        .collect::<Vec<_>>();
    assert_eq!(entities.len(), 100);
}

miri reports:
alloc4621966 (Rust heap, size: 1280, align: 8) {
    0x000 │ ╾a4468557[<11121328>]─╼ 03 00 00 00 00 00 00 00 │ ╾──────╼........
    // ... repeats ...
    0x400 │ 00 00 00 00 01 00 00 00 02 00 00 00 03 00 00 00 │ ................
    0x410 │ 04 00 00 00 05 00 00 00 06 00 00 00 07 00 00 00 │ ................
    // ... repeats ...
    0x4f0 │ 3c 00 00 00 3d 00 00 00 3e 00 00 00 3f 00 00 00 │ <...=...>...?...
}
alloc4468557 (global, size: 3, align: 1) {
    61 62 63                                        │ abc
}
alloc4622641 (global, size: 3, align: 1) {
    61 62 63                                        │ abc
}
// ... repeats ...

cargo-valgrind reports:
       Error Leaked 1.2 kiB
        Info at malloc (vg_replace_malloc.c:307)
             at alloc::alloc::alloc (alloc.rs:80)
             at hecs::archetype::Archetype::grow (archetype.rs:195)
             at hecs::archetype::Archetype::allocate (archetype.rs:159)
             at <hecs::world::SpawnBatchIter<I> as core::iter::traits::iterator::Iterator>::next (world.rs:763)
             at <&mut I as core::iter::traits::iterator::Iterator>::next (iterator.rs:3283)
             at <hecs::world::SpawnBatchIter<I> as core::ops::drop::Drop>::drop (world.rs:748)
             at core::ptr::drop_in_place (mod.rs:184)
             at tests::spawn_batch_unexact (tests.rs:355)
             at tests::spawn_batch_unexact::{{closure}} (tests.rs:340)
             at core::ops::function::FnOnce::call_once (function.rs:232)
             at call_once<(),FnOnce<()>> (boxed.rs:1076)
             at call_once<(),alloc::boxed::Box<FnOnce<()>>> (panic.rs:318)
             at do_call<std::panic::AssertUnwindSafe<alloc::boxed::Box<FnOnce<()>>>,()> (panicking.rs:297)
             at try<(),std::panic::AssertUnwindSafe<alloc::boxed::Box<FnOnce<()>>>> (panicking.rs:274)
             at catch_unwind<std::panic::AssertUnwindSafe<alloc::boxed::Box<FnOnce<()>>>,()> (panic.rs:394)
             at run_test_in_process (lib.rs:541)
             at test::run_test::run_test_inner::{{closure}} (lib.rs:450)
       Error Leaked 2.0 MiB
        Info at malloc (vg_replace_malloc.c:307)
             at alloc::alloc::alloc (alloc.rs:80)
             at hecs::archetype::Archetype::grow (archetype.rs:195)
             at hecs::archetype::Archetype::allocate (archetype.rs:159)
             at hecs::world::World::spawn (world.rs:98)
             at tests::spawn_many (tests.rs:248)
             at tests::spawn_many::{{closure}} (tests.rs:244)
             at core::ops::function::FnOnce::call_once (function.rs:232)
             at call_once<(),FnOnce<()>> (boxed.rs:1076)
             at call_once<(),alloc::boxed::Box<FnOnce<()>>> (panic.rs:318)
             at do_call<std::panic::AssertUnwindSafe<alloc::boxed::Box<FnOnce<()>>>,()> (panicking.rs:297)
             at try<(),std::panic::AssertUnwindSafe<alloc::boxed::Box<FnOnce<()>>>> (panicking.rs:274)
             at catch_unwind<std::panic::AssertUnwindSafe<alloc::boxed::Box<FnOnce<()>>>,()> (panic.rs:394)
             at run_test_in_process (lib.rs:541)
             at test::run_test::run_test_inner::{{closure}} (lib.rs:450)
             at std::sys_common::backtrace::__rust_begin_short_backtrace (backtrace.rs:130)
             at {{closure}}<closure-0,()> (mod.rs:475)
             at call_once<(),closure-0> (panic.rs:318)
             at do_call<std::panic::AssertUnwindSafe<closure-0>,()> (panicking.rs:297)
             at try<(),std::panic::AssertUnwindSafe<closure-0>> (panicking.rs:274)
             at catch_unwind<std::panic::AssertUnwindSafe<closure-0>,()> (panic.rs:394)
             at {{closure}}<closure-0,()> (mod.rs:474)
             at core::ops::function::FnOnce::call_once{{vtable-shim}} (function.rs:232)
             at call_once<(),FnOnce<()>> (boxed.rs:1076)
             at call_once<(),alloc::boxed::Box<FnOnce<()>>> (boxed.rs:1076)
             at std::sys::unix::thread::Thread::new::thread_start (thread.rs:87)
     Summary Leaked 2.0 MiB total

Note that valgrind also reported leaked memory for spawn_many, which is ignored for miri, but it seems likely that both leaks may have the same underlying reason.

Well, seems like this has a simple cause: the old allocation isn't freed in Archetype::grow! self.data = UnsafeCell::new(new_data); merely dropped the pointer, the allocation isn't freed.

Whoops, thanks for catching that! Will push a fix tonight.

Fix released in 0.2.15.


New CheckColumns constraint code change breaks usage of PrimaryKeyConstraint

If this is the case why not use issubclass(target_class, ColumnCollectionMixin)?
Originally posted by @zevisert in https://github.com/collerek/ormar/pull/730#discussion_r965487219

I'm manually using PrimaryKeyConstraint to create tables with composite foreign keys. I'm aware of #137, and would like to come up with a PR for it, but until now things were working fine.

The PrimaryKeyConstraint does not work in relations, so you use it only in the "main/parent" models? A dirty fix would be to add also pk constraint to constructors in the place you commented.

Sorry, I meant composite primary keys - we're just using it in meta.constraints  to override the primary key. We also use ForeignKeyConstraint in a similar way to create composite foreign keys, but that's not the issue here. I'll spend today working on #137 - we use ormar heavily enough, it'd be good to contribute back to it - then we can remove some of the workarounds we have internally too

#137 That is quite complex and big task. There is a branch composite_pks that implements most of the logic and most of the tests but it's not finished

Yeah, I keep coming back to read it quite frequently.. Definitely a lot of work, but maybe I can make some progress on it. I've got a branch going based on 0.11.3 with @tillspeicher's tests cherry-picked on it plus a few of my changes around how Model.pk and pkname works. I didn't notice the composite_pks branch, I'll take a look at that - thanks

There is a suboptimal design where fileds declaration is kept in dictionary as you can have different alias and real db name, that should be a class that is storing this info. Cause you can filter, order etc by those related models using those aliases but in queries they need to be resolved to actual db names with prefixes ( to make it more complicated😅)

I see some of that. What's the best way forward here - should I be attempting anew (pulling some ideas from the composite_pks branch), or should I be contributing to work that's already complete on that branch? Is this TODO list the most organized one we have?
https://github.com/collerek/ormar/blob/810b13bcb756a07b10df344f7a0d2e61f05aaa75/tests/test_model_definition/pks_and_fks/test_composite_pks_and_fks.py#L962-L1003


Vitest extension crashes on run with coverage

Describe the bug
Click on run with coverage from menu or from tests explorer crash  extesion
Reproduction

Output
[10:55:32 AM] Disposing test runner
[10:55:32 AM] Ending test run <none>
[INFO 10:55:32 AM] [API] Running Vitest v2.1.6 (darwin-web/vitest.config.ts) with<EMAIL_ADDRESS>C:\Program Files\nodejs\node.EXE
[INFO 10:55:33 AM] [API] Vitest v2.1.6 (darwin-web/vitest.config.ts) child process 10984 created
[INFO 10:55:33 AM] [API] Watching C:/Users/LQ4161/Desktop/Dev/darwin-web/vitest.config.ts
[INFO 10:55:33 AM] [VSCODE] Watching darwin-web with pattern **/*
[INFO 10:55:33 AM] [API] Collecting tests: src/tests/app/modules/devicesSensors/sideMenu/channelDataFault.test.tsx
[10:55:33 AM] Not starting the runner because tests are being collected for src/tests/app/modules/devicesSensors/sideMenu/channelDataFault.test.tsx
[INFO 10:55:34 AM] [Worker] 10:55:34 AM [vite] (client) Pre-transform error: Failed to resolve entry for package "http". The package may have incorrect main/module/exports specified in its package.json.
  Plugin: vite:import-analysis
  File: C:/Users/LQ4161/Desktop/Dev/darwin-web/node_modules/.pnpm/axios@1.7.8/node_modules/axios/lib/adapters/http.js:8:19
  6  |  import buildURL from './../helpers/buildURL.js';
  7  |  import proxyFromEnv from 'proxy-from-env';
  8  |  import http from 'http';
     |                    ^
  9  |  import https from 'https';
  10 |  import util from 'util';[39
[10:55:39 AM] There is no test run for "channelDataFault.test.tsx"
[10:55:39 AM] No test run to finish for src/tests/app/modules/devicesSensors/sideMenu/channelDataFault.test.tsx
[INFO 10:55:49 AM] [Worker] Running coverage with configuration: {
  provider: 'v8',
  enabled: true,
  all: true,
  clean: true,
  cleanOnRerun: true,
  reportsDirectory: 'C:/Users/LQ4161/AppData/Local/Temp/vitest-coverage-787d8180-fda2-455e-8888-85cd723b8e27',
  exclude: [
    'coverage/**',
    'dist/**',
    '**/node_modules/**',
    '**/[.]**',
    'packages/*/test?(s)/**',
    '**/*.d.ts',
    '**/virtual:*',
    '**/__x00__*',
    '**/\x00*',
    'cypress/**',
    'test?(s)/**',
    'test?(-*).?(c|m)[jt]s?(x)',
    '**/*{.,-}{test,spec,bench,benchmark}?(-d).?(c|m)[jt]s?(x)',
    '**/__tests__/**',
    '**/{karma,rollup,webpack,vite,vitest,jest,ava,babel,nyc,cypress,tsup,build,eslint,prettier}.config.*',
    '**/vitest.{workspace,projects}.[jt]s?(on)',
    '**/.{eslint,mocha,prettier}rc.{?(c|m)js,yml}',
    'vitest-setup.tsx'
  ],
  reportOnFailure: true,
  reporter: [ [ 'json', [Object] ] ],
  extension: [
    '.js',     '.cjs',
    '.mjs',    '.ts',
    '.mts',    '.tsx',
    '.jsx',    '.vue',
    '.svelte', '.marko',
    '.astro'
  ],
  allowExternal: false,
  excludeAfterRemap: false,
  ignoreEmptyLines: true,
  processingConcurrency: 12,
  include: [ 'src/**/*', '!src/tests/**', '!src/modules/devices-sensors/**' ],
  thresholds: { functions: 75, branches: 75, statements: 75, lines: 75 }

[INFO 10:55:50 AM] [Worker]
⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯[39
[INFO 10:55:50 AM] [Worker] Error: Cannot find module 'semver/functions/gte'
Require stack:
-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS> ❯ Module._resolveFilename node:internal/modules/cjs/loader:1144:15[39
[INFO 10:55:50 AM] [Worker]  ❯ Module._load node:internal/modules/cjs/loader:985:27
 ❯ Module.require node:internal/modules/cjs/loader:1235:19
 ❯ require node:internal/modules/helpers:176:18
 ❯ Object.<anonymous> node_modules/.pnpm/make-dir@4.0.0/node_modules/make-dir/index.js:5:19
 ❯ Module._compile node:internal/modules/cjs/loader:1376:14[39
[INFO 10:55:50 AM] [Worker]  ❯ Module._extensions..js node:internal/modules/cjs/loader:1435:10
 ❯ Module.load node:internal/modules/cjs/loader:1207:32
 ❯ Module._load node:internal/modules/cjs/loader:1023:12
 ❯ Module.require node:internal/modules/cjs/loader:1235:19

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[39
[INFO 10:55:50 AM] [Worker] Serialized Error: { code: 'MODULE_NOT_FOUND', requireStack: [<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>] }

[10:55:50 AM] [API] Vitest child_process connection closed, cannot call RPC anymore.
[Error 10:55:50 AM] [API] Failed to close Vitest RPC [Error Error] [birpc] rpc is closed, cannot call "close"
Error: [birpc] rpc is closed, cannot call "close"
    at Proxy.O (c:\Users\LQ4161\.vscode\extensions\vitest.explorer-1.8.1\dist\extension.js:19:3709)
    at At.dispose (c:\Users\LQ4161\.vscode\extensions\vitest.explorer-1.8.1\dist\extension.js:21:3346)
    at c:\Users\LQ4161\.vscode\extensions\vitest.explorer-1.8.1\dist\extension.js:21:1736
    at Array.map (<anonymous>)
    at Ws.dispose (c:\Users\LQ4161\.vscode\extensions\vitest.explorer-1.8.1\dist\extension.js:21:1727)
    at c:\Users\LQ4161\.vscode\extensions\vitest.explorer-1.8.1\dist\extension.js:25:12326
    at ChildProcess.s (c:\Users\LQ4161\.vscode\extensions\vitest.explorer-1.8.1\dist\extension.js:21:1494)
    at ChildProcess.emit (node:events:531:35)
    at ChildProcess.emit (node:domain:488:12)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:294:12)
    at Process.callbackTrampoline (node:internal/async_hooks:130:17)
[Error 10:55:55 AM] [API] Failed to close Vitest process [Error Error] Vitest process did not exit in time
Error: Vitest process did not exit in time
    at Timeout._onTimeout (c:\Users\LQ4161\.vscode\extensions\vitest.explorer-1.8.1\dist\extension.js:21:3532)
    at listOnTimeout (node:internal/timers:581:17)
    at processTimers (node:internal/timers:519:7)

Version
1.8.1
Validations

[X] Check that you are using the latest version of the extension
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Please read the "Output" requirements more carefuly:

The content of "Output" tab. You can open this tab by typing "> Show Vitest Output Channel" in a search bar or pressing "See error" on an error message if there is one. Your issue will be closed if you do not provide the full output (starting with Vitest version) - do not remove any "irrelevant" information - the maintainer will decide if it is valuable or not.

I do not see the first half of the output starting with the "Version"

@sheremet-va I updated the description
That iis the whole output I get on crash

You have a very strange environment. Do you use the public Node.js binary?

I apologize for the delayed response.
Unfortunately, as we're managed by a company admin, I couldn't provide a specific information.
However, the issue seems to have resolved itself after recent OS and VSCode updates.
Thank you for your patience and understanding.
Please feel free to close this issue.
If the problem recurs, I'll provide an update.


it seems has a lot problem.

Exercise 13.1.4  ask for the member data is uniuqe serial number for numbered class. By looking your code.it could happens the identical numbers among different objects.  as follow.
`   numbered a, b = a, c = a;
f(a);//10
f(b);//11
f(c);//11
I think about one way to solve it. defined a static member data in numbered. First initializes  zero to it outside class numbered.  The static member initializes the unique serial number ,and then increment it, for whatever copy constructor or copy assignment-operator.

As per the problem statement, output will be similar for all the cases.
Since synthesized copy constructor will basically copy the unique value of mysn object "a" to other objects.

So, if a.mysn = 999
Then f(a);//999
f(b);// 999
f(c);//999


fix: Align Save Artwork header text

Description
Align Save Artwork header text.

Before
After

PR Checklist

[ ] I have tested my changes on iOS and Android.
[ ] I hid my changes behind a feature flag, or they don't need one.
[ ] I have included screenshots or videos, or I have not changed the UI.
[ ] I have added tests, or my changes don't require any.
[ ] I added an app state migration, or my changes do not require one.
[ ] I have documented any follow-up work that this PR will require, or it does not require any.
[ ] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

Align Save Artwork sheet header text - ole

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Cross-platform user-facing changes (Align Save Artwork sheet header text - ole)

  Generated by :no_entry_sign: dangerJS against c24c09ad6c83afd6b74bb1dd9868a2e60768cde5


Android support

Adds support for Android Cmake.
Two primary changes:

Supressed test compilation for Android ... lsquic/test requires libevent and it is not included by default in android NDK. So added an option -DTESTS=NO to suppress test compilation. The test suppression is useful even for linux/win when someone wants to just generate the libs. -TESTS=NO works on all platforms.
CMakeLists.txt for Android toolchain.
clang (used by android ndk) gives error for unsigned ... signed comparison and I have added a couple of typecasts in one c code file.

Tested with android-ndk-r21b for both debug/release. Compilation command used:
$ cd lsquic
$ cmake -DTESTS=NO -DBORINGSSL_DIR=../boringssl -DCMAKE_TOOLCHAIN_FILE=$NDK/build/cmake/android.toolchain.cmake -DANDROID_ABI=armeabi-v7a  . #Debug mode

For release mode add: -DCMAKE_BUILD_TYPE=Release and the lib compiles fine.
For linking, I have used my own app links with liblsquic.a and internally uses epoll (and not libevent).
Binaries tested on Huawei Mate 20 Pro.

Thank you, @nyrahul, it's great to know that lsquic works on Android with so few changes!
It's true that the source layout is suboptimal.  Unit tests do not require libevent; only the client and server programs do.

@nyrahul  In android platform,  I compiler the release mode of lsquic, work in huawei p20 mobile device, with NDK(android-ndk-r18b) .
it alway crash in XXH32_update_endian function.    But debug mode of lsquic, is work well.  Do you have a similar situation

@heibaihei, can you post a backtrace?

@nyrahul @dtikhonov In android platform, I compiler the release mode of lsquic, work in huawei p20 mobile device, with NDK(android-ndk-r18b) .
it alway crash in XXH32_update_endian function. But debug mode of lsquic, is work well. Do you have a similar situation

@heibaihei I tested mostly with release mode on android and it worked fine. I used r21b ndk and tested with my own app.

@nyrahul @dtikhonov In android platform, I compiler the release mode of lsquic, work in huawei p20 mobile device, with NDK(android-ndk-r18b) .
it alway crash in XXH32_update_endian function. But debug mode of lsquic, is work well. Do you have a similar situation

@heibaihei I tested mostly with release mode on android and it worked fine. I used r21b ndk and tested with my own app.

@nyrahul  OK, I can try r21b ndk, I'm afraid this is an unknown risk. This bug is inevitable

@heibaihei, can you post a backtrace?

thanks, i will post later

/lib/arm/libquic_file.so (XXH32_update+192) (BuildId: bb920952dab45737c8a710716b4fe6dd3baa2abb)
/lib/arm/libquic_file.so (lsqpack_enc_encode+96) (BuildId: bb920952dab45737c8a710716b4fe6dd3baa2abb)
/lib/arm/libquic_file.so (lsquic_qeh_write_headers+44) (BuildId: bb920952dab45737c8a710716b4fe6dd3baa2abb)
/lib/arm/libquic_file.so (lsquic_stream_dispatch_write_events+130) (BuildId: bb920952dab45737c8a710716b4fe6dd3baa2abb)
/lib/arm/libquic_file.so (lsquic_engine_process_conns+498) (BuildId: bb920952dab45737c8a710716b4fe6dd3baa2abb)


Tagline brainstorm

The tagline at the top of the site — "A standard that makes the web work for you" — is nice and succinct. But I wonder if it may be describing the promise of Solid too narrowly. In my experience, it's good to set people's sights on the big vision and then explain the specifics.
With that in mind, I thought I'd try my hand at suggesting some other possibilities to see if any of them resonate.
"The foundation for the next era of the web"
"Foundational technology for the next era of the web"
"The tech stack for a secure, innovative web"
"The future of secure, innovative apps on the web"
"The web as it was meant to be"
"A web that works for everyone"
"Reshaping the web"
"A new ecosystem of data and applications"
"Reigniting the web's true potential"
"Rebuilding a web for everyone"
"Web technology for a new era of innovation"
"For a new era of innovation"
"The foundation for a new era of online innovation"
"Forging the future of the web"
"The future of the web, today"
I can keep going! But I'll stop here for now.

Thanks Kelly! The Creators are carrying out user tests that make developers understand what Solid is accurately in the shortest amount of time. One of the pieces of feedback in the past is that text doesn't covey what Solid is fast enough. Maybe you would have some ideas on how to keep aspirational and concrete?

For sure! Maybe what we need then is to give ourselves a littttle more space to explain on the top half of the page.
So we could supplement one of the short taglines with a few sentences like this:
Solid combines open standards and technologies to extend the capabilities of the world wide web. It provides a better way to structure data, applications and digital identities. It opens new possibilities for developers, organizations and users. Led by web inventor Sir Tim Berners-Lee, Solid is the way the web was meant to be.

"A standard that makes self determination online possible"

"A standard for self determination online"

The tagline now is factually incorrect, and needs urgent fixing: #203.
We can always change it to something else later, but whatever we publish must at least be factual.

Open technologies for an open Web
Open technologies for decentralizing data control on the Web
Building an open Web for you and your data

I like "Open technologies for an open Web"

Thanks for the suggestions!
I'll make sure to include this in the next round of user testing with the Creators.
If you're interested in the work that goes into writing a tagline the Explaining the Vision panel is a great place to look. There have been some very productive brainstorm sessions over calls around accuracy, clarity, and mood boards that I'd highly recommend setting up around this panel too.


CLOUDSTACK-9416 : Enabling Static NAT on an associated Public IP to one of the NICs (networks) of a multi-NIC VM fails due to a wrong (default) Guest VM IP being selected in the GUI

Bug in ACS master GUI: Enabling Static NAT on an associated Public IP to one of the NICs (networks) of a multi-NIC VM fails due to a wrong (default) Guest VM IP being selected in the GUI.
ERROR:
INFO  [c.c.a.ApiServer](catalina-exec-7:ctx-83926837 ctx-fc7aa5ed) VM ip <IP_ADDRESS> address not belongs to the vm
ACS GUI before the bug fix:

As you can see in the above attached ACS GUI screen shots, same (default) guest VM IP is being selected in the ACS GUI for both the NICs (networks) of the multi-NIC VM while enabling Static NAT on the corresponding associated Public IPs. Thus, we hit this issue.
ACS GUI after this bug fix:

As you can see in the above attached ACS GUI screen shots, this bug fix resolves the above mentioned issue.

@rhtyd  This is a shadow of PR #1592 , rebased against 4.9 as requested.
Note: The original PR #1592 has enough LGTMs to merge this PR.
Once you merge this PR, I will close the PR #1592 .
Sorry for the inconvenience !!

LGTM
this PR solves the same issue as #1778

LGTM, this fixes the same issue as #1778. Since this is a pure UI change, manual testing with screenshot confirm the fix. I'll move with the merge now. The failure at Travis is not due to this change but intermittent/env issue.


fix: use helm chart api v1

so that the chart can also be used with helm v2, in jx v2

/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: vbehar
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [vbehar]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


feat(integrations): provider in APIs list

Issue
https://gravitee.atlassian.net/browse/APIM-5172
Description

@JedrzejJanasiak not really, we can navigate to "apis derails page" from different places than the list. So we need to keep this call for integration name.


Canvas for drawing buildin

Describe the solution you'd like
It would be great if you added a canvas for drawing, like a mspaint, just to sketch things
Type of feature
Other
Additional context
No response

Nice idea but would you like to create and save them and possibly attach them to a memo or would it just be a a tool for a quick sketch or something. As a tool its no hassle to do it can be easily integrated but if you want a full feature where you can create canvase, edit them and attach them to a memo that will require allow of thought and time.


check initialization of exported block scoped variables

fixes #5221

:+1:

Thanks for your fix! :beer::sparkles:
I change issue #5221. Please also fix let declaration.

Fix should already cover all block scoped declaration. I'll test for let declaration

Thanks very much! :rose:


docs - /linode/instances/:id/ips/sharing goes to wrong place

Clicked on the link on docs page here:

Takes me here:

Thanks! This is a dup of #2454


Update to Maven 3.5

I don't quite understand this change, update what to Maven 3.5?  project asis builds fine with:
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T12:39:06-07:00)

appears to be related to https://github.com/jdillon/mvnsh/pull/18

basics of this to support mvnsh update to maven 3.5.0 has been applied; thx


Fix decoding client state for transactions containing `update_client' ABCI events

Summary
App currently throws a runtime error when attempting to decode any IBC Client updates and this should be fixed.
Description
As of now, any Transaction that contains IBC Client updates cannot be decoded by current protobuf schema handling. This is because of an internal Any schema decoding error that inevitably gets thrown by the TxResult decoder. This has occurred with anything containing an internalMsgCreateClient protobuf schema (e.g. create_client ABCI events) but occurs with other IBC Client related transactions.
This can probably be fixed by one of the following:

simply update the protobuf schemas. this might already be resolved by penumbra's core team and their recent work with IBC.
the recently released NPM packages by the web team which has converged on a set of patterns with dealing with this sort of data
monkey patching the schema directly so as to handle instances where Any are encountered

Closed by #104


Taker drops connection upon failure to open substream for rollover

Rollovers are important to keep the position alive.
If the taker fails to open a substream for rollover then something might be wrong with the connection.
To make sure we don't run into a scenario where the actor cannot open substreams the taker drops the connection in case

NoConnection is reported
we fail to open a substream over the connection

This is an emergency fallback scenario that should usually not be triggered.
It is added to avoid force closing positions due to connection problems.

This does not actually resolve https://github.com/itchysats/itchysats/issues/2554 but it should be good enough for now to avoid rare force-close scenarios where takers lose connection without the endpoint noticing.

So far I only applied this to rollover on the taker side, because it is critical to avoid force close.
It might be a good idea to add it to the collab-settlement protocol for the taker as well, because that is also critical in the sense of not losing money because the user's deamon behavior blocks an action.
For collab-settlement the dynamic might be a bit different, because it is user-triggerd, thus I am not sure about side effects for triggering a disconnect. A user hitting the button in anger might cause repeated disconnects. That's one reason why I added it only for rollover so far ;)

for some reason, my yesterday's comment didn't get published:
are we sure that this was the reason force-closures were happening?
I'm a bit sceptical it would fail to open substream for over 24h, if at the same time we had zero problems with rolling over other things... (and afterwards, his taker interacted again without restart on his part)

I understand your concerns, but unfortunately I don't trust the endpoint always detecting that the connection is "broken".
If the endpoint does not react the protocol actors will fail, potentially forever!
Rollover only happens every 2 hours. After a failed rollover we only re-trigger after 5 minutes. I don't see a problem disconnecting within these time constraints if we fail to roll over due to the two errors.
I understand that this change is not optimal from a boundaries / clean code perspective, but I don't see any harm in letting rollover take control here.
If we can still run into scenarios similar to what is described in https://github.com/itchysats/itchysats/issues/2166 this would mean that the taker gets no feedback and the positions just gets force closed.
Unless the user comes back to us with logs we will have to "hope" to run into such a scenario on testnet at some point so we can reproduce what is the problem... I'd rather have an emergency switch for now 😅
What do you think @bonomat ?

are we sure that this was the reason force-closures were happening?

If by "this" you mean the endpoint not picking up on a broken connection then yes.
I do trust the user insisting that the container was running and the internet connection worked.

are we sure that this was the reason force-closures were happening?

If by "this" you mean the endpoint not picking up on a broken connection then yes. I do trust the user insisting that the container was running and the internet connection worked.

I'm a bit sceptical it would fail to open substream for over 24h, if at the same time we had zero problems with rolling over other things... (and afterwards, his taker interacted again without restart on his part)

If it is the taker's endpoint that does not properly cleanup the connection (i.e. drop it and re-establish one if the connection is broken) then this can happen. I don't think it has anything to do with the maker.

this does not prove your hypothesis though, unless we see his logs. The connection could have been working, but auto-rollover did not trigger rollover successfully.

but auto-rollover did not trigger rollover successfully.

Did we touch that logic when we introduced the new protocol? If so we should check it. Otherwise I would argue that something that was not changed is unlikely to break. The logic has quite a lot of unit tests, but we can re-evaluate there is an edge case that is not covered.

but auto-rollover did not trigger rollover successfully.

Did we touch that logic when we introduced the new protocol? If so we should check it. Otherwise I would argue that something that was not changed is unlikely to break. The logic has quite a lot of unit tests, but we can re-evaluate there is an edge case that is not covered.

but auto-rollover did not trigger rollover successfully.

Did we touch that logic when we introduced the new protocol? If so we should check it. Otherwise I would argue that something that was not changed is unlikely to break. The logic has quite a lot of unit tests, but we can re-evaluate there is an edge case that is not covered.

please have a look below what else could have happened that cannot be covered by the unit tests and would look exactly the same in the logs on the maker side:

actor died (it's not supervised, so it would not restart),
missing DLC,
lack of connection to the DB,
CFD got moved to 'closed' for some reason,
no expiry timestamp,
user somehow started collab-settlement that never finished (this is really unlikely, because we would tell us; moreover, that protocol  would have timed out quickly)

I hope it's not any of the above, but I have seen no proof yet. First two of the list are possible, others are listed just for completeness. All I say is that we should be vigilant, and perhaps increase measures of sending feedback (either via some protocol to the maker or sending debug logs to us if something fails hard).
if I remember correctly, we have seen an instance where we had a missing DLC error at some point. And we for sure had panics triggered by some external libs as well. I will probably add supervision to this actor anyway, as this is a good idea.

this does not prove your hypothesis though, unless we see his logs. The connection could have been working, but auto-rollover did not trigger rollover successfully.

Afair, the taker in question did not send anything to the maker for a while which to me is an indication that something was wrong with the connection. I think this was what Daniel motivated do this change.
Are there alternative solutions to the problem where we just don't know?

We had recent errors in production:
We have rollover problems with 0.5.0 and our favorite taker. We saw the following error: Expected Msg2 wihtin 60 seconds. If you want to look it up, these are the order IDs and taker ID
715963df-e11f-4e90-ab69-399528916b2d, b1bed33e-4e8b-4dcb-8515-77c80cc1a67e,38cffef4-5eb0-4b37-b45d-a0e74c719b12, takerId:  10ed1d0b887ac90d8d66e0fc36131cacca4cf4b9562ba34e092fe38d77f8c84e

715963df-e11f-4e90-ab69-399528916b2d

Looking at those logs makes me less convinced that we need to act rashly and merge changes like these.
Over the last 2 days each of those CFDs had 3 rollover failures out of 24 total rollovers. They all happened at the same time (2pm, 6pm and 12am). And they all succeeded 5 minutes later.
Given that they all happened at the same time, the maker was probably struggling to process all requests for some reason. We have to fix that problem because I don't think there's any inherent reason why we should fail protocols every now and then. But it does not seem critical.

But it does not seem critical.

I give this a solid 5 out of 7 on the level-of-criticalness-scale.
More seriously: I'm not advocating for the changes discussed in this PR, but I believe we have to come up with a solution. For me, these kind of errors are critical because I can't say that it will always succeed eventually if I can't say why it was failing in the first place.

Since nobody seems to feel an emergency fallback for rollover is a good idea I am closing this PR at this point.
Please refer back to https://github.com/itchysats/itchysats/issues/2554 for noting further opens or open a separate ticket if you feel the problem comes from somewhere else.


SMB: Wrong Windows 10 version (19041) reported.

Describe the bug
CME reports the wrong Windows 10 version (Always 19041)
Tested with Windows 10 19042, 19043 & 19045
To Reproduce
Steps to reproduce the behavior:
SMB Scan of Windows 10 (19042, 19043 & 19045) systems.
Expected behavior
Correct Windows 10 version e.g. 19042, 19043 & 19045.
Crackmapexec info

OS: KALI
Version of CME 5.4.0

Related to impacket lib


Allow streaming copy output via filedescriptor

Applications like linz_bde_uploader might want to avoid writing to a temporary file before feeding the BDE data to yet another destination (ie: PostgreSQL database). This class has a copy subroutine that takes a temporary file but I could not find one to open a streaming interface for that data. The underlying bde_copy should be already capable of doing that (at least on a unix system): see https://github.com/linz/linz_bde_copy/issues/31

I'm not sure how a streaming Perl interface would look like, maybe a method returning a filehandle, like a "pipe" method to go with the "copy" one ?

\cc @palmerj

I think the interface would simply return a filehandle reference which the user then needs to manage. Back I haven't thought about that too much!

Is it acceptable to have such pipe function bail out if /dev/stdout is not supported ?

or, FIFO files (would be another way to do it)

with FIFO files we actually dont' even need any support in this library but can be done directly by caller!

See how you like #24 - no fifos used, only /dev/stdout

@strk , I can't comment on advantages of FIFO over stdout . I have no experience.

Personally I would go with stdout as it's a more standard approach

@palmerj , thanks for your comment.

It looks like it is not only windows lacking /dev/stdout:
https://github.com/linz/bde-processor-deployment/issues/66

Closing again, moving the ::pipe problem to #26


[0.4.5] Webview flashing when using with haze

Looks like haze is having issues with Webviews, Our QA's found this in our real app code we we had to revert for now, but I've created a simple example to reproduce here: Just a fork with a webview sample added. Had to drop toolchain to 17 but that's nothing to do with the issue just my current setup.
https://github.com/wezley98/haze_webview_test/commit/82427efbe9c2371c8406129b0368ed8e0c557d78
API 34 emulator
Screen_recording_20240115_105304.webm
For our usecase: most of the app is native which works fine with the bottombar and haze. But some screens are still been migrated away from webviews, when using haze with webviews we see this repeated flashing issue.

Hmmm. Looks like an invalidation issue when using AndroidViews underneath, where we need to invalidate a lot. We can look at potential issues with invalidating too much, but that's about it. I assume that you're using haze-jetpack-compose?

FYI: one of the issues in your sample is that you are calling loadUrl in the update block, which means that you'll be calling loadUrl on every composition. This is why the video above is so bad (as it's constantly reloading the URL).
Even fixing that, there is an issue here for when the web content changes. The problem seems to be something around drawing WebViews in a RenderNode with a RenderEffect. Drawing it once works fine but drawing it multiple times (for the blurred areas) leads to the flashing. If I remove the RenderEffect, but still draw the RenderNode again for the blurred areas, it works fine too.
I initially thought it might be caused by skipping loads of frames, but I don't think that is the case. See the screenshot below. We're in and around the yellow line, which is good (enough here anyway). If we were skipping enough frames to lead to the flashing above, you'd expect lots of spikes past the red line.

I'll leave this open, but I'm not sure there's much we can do here. I do want to spend some time optimizing the draw paths which might help this issue.

I'm pretty sure that this is actually fixed in Haze 0.9, so going to close this. The new drawing pipeline means that everything is drawn in the child, not the parent.

Would be interesting to know if this actually fixed the issue. As an aside, we discovered that calling setLayerType(HARDWARE,null) on our WebView resolved flickering while doing a similar technique as older haze.

Very quick demo:
https://github.com/user-attachments/assets/4df49b80-1b64-497b-b1b7-f33cf5c23d56
There's still some flickering, but nowhere near as much as previously.

That's pretty bad to be considered unusable. Try using LAYER_TYPE_HARDWARE on the webview. This has fixed the flickering for me.

@pfn can you please share some code on how you used LAYER_TYPE_HARDWARE? Thanks in advance.


"Twitter Bootstrap" => "Bootstrap"

Per http://getbootstrap.com/about/#name
See also https://github.com/twbs/bootstrap/issues/9899

Thanks!


Add configuration overrides for DaprWorkflowClient and WorkflowRuntimeBuilder

Description
This PR addresses a small limitation, it ensures that DaprWorkflowClient and WorkflowRuntimeBuilder allows configuration overrides via properties override mechanism.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #1112
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[ ] Extended the documentation

@artursouza @salaboy as I was working on this PR I have discovered that the workflow tests weren't picked up by Maven Fail Safe plugin since these were ending in Test instead of IT, so I had to rename the test files.
Please take a look and let me know if everything is looking good.

@artursouza @cicoyle and @salaboy the build 🟢, could you please review and approve. Thank you! 🙇

Great catch.. I will review and approve later today

@caniszczyk @artursouza This is ready to be merged.. please take a look, I've approved it already, but that is not enough :)

@salaboy as discussed I have simplified the TestcontainersDaprClientCustomizer and I also added the necessary tests to have proper coverage.
Could you please take another look?


Add VPN Landing Page

Work on the VPN landing page. Here's the figma design: https://www.figma.com/file/eYq43Gg6ZH0czcEunfBv4B/VPN-Landing-Page---UselesVPN?node-id=0%3A1

I would like to work on it for the hacktoberfest


share dashboard lose Global control

I set a global parameter controller in the dashboard. When I share the dashboard, I open the shared page and find that the custom parameter drop-down box is missing, which makes it impossible to filter based on conditions.
My Davinci version is  davinci-assembly_3.0.1-0.3.1-SNAPSHOT-dist-beta.9
please help me

We retested this feature and found no issues, please
provide more information to help deep tracking.

view:

Widget List:

dashboard:

share.html:

@scottsut ,I see that the bug has been closed. I re-downloaded the package davinci-assembly_3.0.1-0.3.1-SNAPSHOT-dist-beta.9. Has the bug fixed the package? Thanks  a lot

We'll update release package later, you can download it tomorrow.

I re-download new package and deploy today,found this bug still exists -_-||  @scottsut

I just downloaded and reinstalled the release package, and I'm pretty sure the problem has been fixed.

could I have your wechat account? so that I can show you detail ,my wechat account is huang_15201783921   , thanks


write /var/lib/docker/tmp/GetImageBlob220119603: no space left on device

It seems that devilbox reached the maximum docker size on my mac.
write /var/lib/docker/tmp/GetImageBlob220119603: no space left on device
running ./update-docker.sh results in:

oh, and is it really 64GB in total?

This is not related to the Devilbox, but rather due to the Docker implementation on MacOS. You can either remove unused images or increase the volume size for all your Docker images:
https://gist.github.com/stefanfoulis/5bd226b25fa0d4baedc4803fc002829e

In case anybody else is running into this problem, at docker they are discussing this since August 2016.
https://github.com/docker/for-mac/issues/371#issuecomment-315385246
Increasing the disk image size will not solve the issue.

That seems to be the solution so far: https://github.com/docker/for-mac/issues/371#issuecomment-242047368

I'm trying https://github.com/docker/for-mac/issues/371#issuecomment-407878884 right now.
If you want i'll let you know if it works or not.

Sure let me know.
When I was still on MacOS (~3 years back), I had the same issue. I was pretty sure, that deleting images solved that problem.

@krebbi did that work?

will have to look at it over some time to see if the image is growing or if it has a stable size.
coming back to you in a few days.

Here is some more input as well: https://forums.docker.com/t/no-space-left-on-device-error/10894/17
I will nonetheless close this issue, as it is not Devilbox related.

https://devilbox.readthedocs.io/en/latest/support/troubleshooting.html#no-space-left-on-device


No sound from Analog Synth X on iPad Pro

No sound at all from Analog Synth X (downloaded from app store), on ipad pro 12.9, 2017 (ios 11).
All my other synths works. Is this a known issue?
Best regards
Tomas

Probably @swiftcodex and I need to make an iOS11 release of that synth. New synths are on their way too.

We might as well look at it this weekend...

Can you see if turning off the filter makes sound work?

Indeed. Turning of “Filter” does make the sound (and everything else as far as I can see) work ...!

This is fixed in the latest version of AK, uploading a new Analog Synth X to the app store now.


destroySocket() doesn't work in Android device

I faced an issue whereby the socket query parameter doesn't refresh after destroySocket() method called:
Step to reproduce:

During app launch, the socket was initiated with query parameter id=001. On the server side, i can retrieve the value of id correctly.

socketIO = SocketIOManager().createSocketIO('http://<IP_ADDRESS>:3000', "/", query: "id=001", socketStatusCallback: _socketConnectStatus);

When i trigger a button in app to destroy the existing socket and attempt to recreate new socket with id=002

SocketIOManager().destroySocket(socketIO);
socketIO = SocketIOManager().createSocketIO('http://<IP_ADDRESS>:3000', "/", query: "id=002", socketStatusCallback: _socketConnectStatus);

The problem exist here, in the server side will still getting id=001 (expected to be 002) even through the socket is completely destroyed in app, but the query seem doesn't refresh correctly.
(This issue only happen in Android, it works fine for iOS platform)

same issue here.

I'm having the same issue, do any one fix it.  In dispose function,
I called
socketIO.unsubscribAll()
socketIO.disconnect
socketIO.destoryed
. Still does not works

Any solution for this?

I couldnt find a solution for it so I change the socket io plugin. I used adhara_socket plugin now, and it work perfectly. Try that out.

okay. thanks!


Highlight output diff in the evaluation comparison view

Preview

Related Issue
Issue #1309

@bekossy thanks for the PR.
From the screenshot you shared I personally don't like the diffs beeing struck through.
Have you considered this library https://praneshravi.in/react-diff-viewer/ instead of diff ?

@aakrem Reading the code it seems the visualization of the diff is not part of the diff library but is a choice made by Kaosi. In any case, I don't think it makes sense to switch libs now. Personally I like the way promptfoo does it, highlighting while the color of the text stays black. I think strikethough makes things clear when you are diffing one line (in contrast to diffing multiple lines as the example shown in react diff viewer).

@mmabrouk I really don't like the strikethrough.
Github style is way cleaner and clearer in my opinion.
and that's what the library above is also offering.
If the library we already use is offering same style without strikethrough then let's adjust the output of the diff

@aakrem The git style works only when you have two texts side by side. In that case, the original version get highlighted in red while the addition in the new version get changed to green, in this case, where you have one original version, you cannot highlight things in green, you need to show in each variant which part got removed and which got added.
I agree however that it makes readability difficult.
@bekossy can we please add a toggle button "Show difference" with which we can disable and enable the diff visualization.

Thanks for the review @mmabrouk
I opened a separate PR for the cypress test in order to get it merged as soon as possible
I have added the toggle button feature for the diff mode
For the last feature, I could work on it as a separate issue as it could take some time


Fix for #219

fix invalid executable path for nunit3 task

Hi @abdulkareemnalband.  Don't know if you are aware but you can specify the executable path for the tool as a workaround for this issue.
<NUnit3 Assemblies="@(TestAssemblies)" ToolPath="$(MSBuildProjectDirectory)\lib\NUnit\bin" .../>
We tend to keep the NUnit tool under CM and as such do not use the original installed location for the tool path but supply it above in the msbuild project file as it comes out with our codebase.  I obviously overlooked this when I originally implemented the task (sorry).  Many thanks for the fix, hopefully it will be merged in soon!
Regards.

@stevewi1950 thanks for reply,
As i'm new comer to to .net stack let alone msbuild, can you please point me to relevant documentation

@stevewi1950 no worries i found documentation at https://msdn.microsoft.com/en-us/library/microsoft.build.utilities.tooltask.toolpath.aspx

@abdulkareemnalband pull request #218 updates the documentation for the NUnit3 task which contains an example of it's usage.  I believe all of the MSBuildTasks implement the ability to specify where the executable path is for the tool as it is a part of the base class (ToolTask.cs) along with other standard parameters... https://github.com/Microsoft/msbuild/blob/master/src/Utilities/ToolTask.cs.
As for the parameters to the NUnit3 task are concerned, they pretty much match the NUnit3 documentation hosted here on git hub.
<NUnit3 Assemblies="@(TestAssembly)" ToolPath="PathTo nunit-console3.exe" Process="Multiple"  TestTimeout="1000"  Framework="v4.0"  Force32Bit="true"  Workers="1"  EnableShadowCopy="true"  OutputXmlFile="MyTestOutput.xml" WorkingDirectory="./" ShowLabels="All"  InternalTrace="Verbose" NoHeader="true" NoColor="true"
Verbose="true"/>.

Hope this helps.
Regards.

@stevewi1950  Thanks a lot
As issue has been resolved i'll close this ticket

My bad closed pull request


Unit test example needs a dom element

Hi Folk,
The unit test example here doesn't work out of the box with either the browserify or webpack templates.
https://vuejs.org/v2/guide/unit-testing.html#Writing-Testable-Components
The container needs to be passed in with the propsData or they are not used
function getRenderedText (Component, propsData) {
const container = document.createElement('div');
const Ctor = Vue.extend(Component);
const vm = new Ctor({
el: container,
propsData: propsData
});
return vm.$el.textContent
}
if you want a repository to look at it easily it is here
Thanks for all you are doing. It's making being a js developer more pleasant than it was by far.

Thanks for reporting this! I'll go through all the examples soon and do a little revamp.

@sdras Would it be okay to refactor this example using Vue Test Utils? Since this is the official Vue testing library, and it has new maintainers, this would probably be a better experience for users to have an example that matches what they'll learn afterward on the Vue Test Utils documentation.


AdaptVQE threshold improvements

Summary

adds a new eigenvalue_threshold setting to the AdaptVQE which allows a more fine-tuned control of the convergence based on a minimal change of the eigenvalue with respect to an increasing ansatz
renames the previously existing threshold attribute of the AdaptVQE to be called gradient_threshold in order to disambiguate it from the other (new) threshold mentioned above (using the old attribute will now log a PendingDeprecationWarning)

Details and comments

In order to be able to finalize this, I temporarily merged #9537 into this PR. Once that is merged I will rebase on main.

I do not understand why the tests fail consistently on Windows and Mac OS but work fine on Linux.
I will do some more investigation tomorrow.


feat: add heartbeat for console

Signed-off-by: João Vanzuita<EMAIL_ADDRESS>

we will come later xD


npm run start is OK ,but npm run publish will alert that can not find module simple-plist

sorry solved!

It's strange that I still have this problem when I build on Linux


Develop rules gmv

This PR implements several important things:

Generic functional message in the form of ContinuousUnivariateLogPdf distribution. This distribution supports various domains and provides an interface for further message approximation (has not been implemented yet)
Testing utilities for testing rules and their results
As an example of introduced changes almost all rules have been reimplemented and tested for NormalMeanVariance node

Related to #15


"Cannot read property 'properties' of undefined" on Collection.add()

Describe the bug
The above error occurs when adding an element to the collection on the owning side of a one-to-many-relationship. I'm sure this is an oversight on my part, but where? I tried using links instead of references as described here, but to no avail. Do the entities have to be managed to be associated in this way?
Stack trace
TypeError: Cannot read property 'properties' of undefined
    at Collection.get property [as property] (/Users/user/Documents/Diverse/Projects/autotip/node_modules/mikro-orm/dist/entity/ArrayCollection.js:91:44)
    at Collection.validateItemType (/Users/user/Documents/Diverse/Projects/autotip/node_modules/mikro-orm/dist/entity/Collection.js:199:70)
    at /Users/user/Documents/Diverse/Projects/autotip/node_modules/mikro-orm/dist/entity/Collection.js:35:32
    at Array.map (<anonymous>)
    at Collection.add (/Users/user/Documents/Diverse/Projects/autotip/node_modules/mikro-orm/dist/entity/Collection.js:35:15)
    at App.execute (/Users/user/Documents/Diverse/Projects/autotip/src/App.ts:98:21)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at App.run (/Users/user/Documents/Diverse/Projects/autotip/src/App.ts:161:7)

To Reproduce
With the one-to-many-relationship
@Entity()
export class Parent {
  @OneToMany(() => Child, (child) => child.parent)
  children = new Collection<Child>(this);
}

to
@Entity()
export class Child {
  @ManyToOne()
  parent!: Parent;
}

the following code fails:
const parent = new Parent();
const child = new Child();
parent.children.add(child);

Expected behavior
The child is added to the parent's collection and the child's reference to the parent is set.
Versions

Dependency
Version

node
12.16.3

typescript
3.9.3

mikro-orm
3.6.15

your-driver
2.1.0 (mysql2)

Are both of your entities discovered? Did you initialize the ORM before working with your entities? Enable debug mode to see.
https://mikro-orm.io/docs/debugging

Did you initialize the ORM before working with your entities?

No, I did not. Thank you for helping me out!

Hi @B4nan is it possible to not having ORM initialized before working with Entity Collections? I mean, how can i achieve this while i'm unit testing? i.e Creating dummy object examples
const parent = new Parent();
const child = new Child();
parent.children.add(child);

Nope, you need to initialize it, otherwise there is no metadata and the propagation cannot work. FYI in v6 you can use MikroORM.initSync if that is your problem.


tslint -> eslint

change generated code to use an esLint with typescipt instead of the now deprecated tsLint

This looks to already have been done


Bug Report:  Whenever you bind controls, all the controls stop working

Please check for duplicates or similar issues, as well performing simple troubleshooting steps (such as clearing cookies, clearing AppData, trying another browser) before submitting an issue.
If you are playing the game in a browser, what site are you playing it from?
Newgrounds or Itch.io? Specify below.
If you are playing the game in a browser, what browser are you using?
Chrome (or a Chromium based browser, i.e. Edge, Opera, etc.), Firefox, or Safari? Specify blow.
If you are playing a downloaded version of the game, what operating system are you using?
Windows (x86), Windows (x86_64), Linux, or macOS? Specify below. Windows
What version of the game are you using? Look in the bottom left corner of the main menu.
Have you identified any steps to reproduce the bug? If so, please describe them below. Use images if possible.
Go to the controls menu, and then rebind anything. all other controls stop
Please describe your issue. Provide extensive detail and images if possible.

This bug hasn't been fixed yet. A solution for now is to delete your ninjamuffin99 folder in your AppData/Roaming

Yea becuz playersettings always says it loads the key data { } unlike the ng build where it has info inside the {}

https://github.com/Dot-Stuff/Dot-Engine/blob/b4623d8619c084aa1d796930d956326f48fc9c6e/source/Controls.hx#L354

A temporary solution is to hardcode it for now

ye

Fixed on experimental branch


redirecting logging to a file in the README example doesn't disable color

Copying the "custom color" example code from the README to example.go and running it:
$ go run example.go 2> file
$ cat -vet file
^[[31mERRO^[[0m[0000] foo bar baz!!! 5                             $
^[[34mINFO^[[0m[0000] A group of walrus emerges from the ocean      ^[[34manimal^[[0m=walrus ^[[34msize^[[0m=10$
^[[33mWARN^[[0m[0000] The group's number increased tremendously!    ^[[33mnumber^[[0m=122 ^[[33momg^[[0m=true$
^[[31mFATA^[[0m[0000] The ice breaks!                               ^[[31mnumber^[[0m=100 ^[[31momg^[[0m=true$
exit status 1$

It looks like the color detection code is only looking at stdout. If I redirect only stdout to a file the color goes away, even though the output is still visible in the terminal!

@oconnor663 you're right. If you feel like providing a PR, that'd be great. Otherwise I'll fix it sometime in the future.

@oconnor663 I can't reproduce this issue. Do you have any special terminal ?
▶ go run examples/basic/basic.go 2> file
▶ cat -vet file
time="2016-05-24T20:30:16+02:00" level=debug msg="Started observing beach" animal=walrus number=8 $
time="2016-05-24T20:30:16+02:00" level=info msg="A group of walrus emerges from the ocean" animal=walrus size=10 $
time="2016-05-24T20:30:16+02:00" level=warning msg="The group's number increased tremendously!" number=122 omg=true $
time="2016-05-24T20:30:16+02:00" level=debug msg="Temperature changes" temperature=-4 $
time="2016-05-24T20:30:16+02:00" level=panic msg="It's over 9000!" animal=orca size=9009 $
time="2016-05-24T20:30:16+02:00" level=fatal msg="The ice breaks!" err=&{0xc8200122c0 map[animal:orca size:9009] 2016-05-24 20:30:16.035454715 +0200 CEST panic It's over 9000!} number=100 omg=true $
exit status 1$

@camilocot hmm yeah, I can't seem to reproduce it anymore either. Fixed?


Mark spec files as archived

Maybe then people won't try to edit them and submit PRs

Please add a README.md
# Archived Spec

NOTE: the files in this directory are NOT meant to be edited. They are a snapshot of the specification which is no longer being updated. We will not be accepting changes to these documents.

You can configure the bot to reject PRs on that files.

I think that this change has broken the links to the spec in the main repo README.md, as those links depend on the filenames


Sample Application Submission - Life Sciences / Molecular Modeling

Issue #, if available:
none
Description of changes:
Second submission for sample application after reflecting the previous feedback. Added a 05-Life-Sciences section to the sample application section to host the new 01-Modeling-Molecular-Structures-Graph-Data-Gremlin.ipnb notebook. Added section in the sample application read me & associated unit test for the new notebook.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Hey I am a bit confused why these tests are failing as I am passing the tests all locally. Any insight into what might be going wrong here would be appreciated.


Problem with Websocket (Django)

Hey community!
When i post data to MessageCreateAPIView class, the data is being saved in database but websocket is not working properly, after sending the data following error appears:
ConnectionError at /chat/rooms/message/create/
Connection closed by server.
Do you have any ideas to fix this?

Already fixed, the problem was that new version of channel requires daphne. You need to install it and add to apps in settings


Support mapping to private fields

This is a great library! I'm wondering however whether it's possible to support private fields. Something like this:
@MappableClass()
class MyUser with MyUserMappable {
  final String id;
  final String name;

  final String _password;

  MyUser({
    required this.id,
    required this.name,
    required String password,
  }) : _password = password;

  /// Build fails if I don't have this getter
  /// String get password => _password;

  static const fromJson = MyUserMapper.fromJson;
}

The documentation says that the getter for "password" isn't required but without it I get the following error:
[WARNING] dart_mappable_builder on lib/models/plan.dart:

Class MyUser defines constructor parameters that could not be resolved against any field or getter in the class.
This won't break your code, but may lead to unexpected behaviour when serializing this class. Also '.copyWith()' won't work on these parameters.

The following problematic parameters were detected:
- password: Cannot find field or getter related to this parameter.

Please make sure every constructor parameter can be resolved to a field or getter.
If you think this is a bug with dart_mappable and the listed parameters should be resolved correctly, please file an issue here: https://github.com/schultek/dart_mappable/issues

[WARNING] dart_mappable_builder on lib/models/plan.dart:
An unexpected error occurred.
This is probably a bug in dart_mappable.
Please report this here: https://github.com/schultek/dart_mappable/issues

The error was:
UnimplementedError: Tried to call .accessor on unresolved parameter.

#0      UnresolvedParamElement.accessor (package:dart_mappable_builder/src/elements/param/mapper_param_element.dart:232:43)
#1      ClassMapperElement.fields.<anonymous closure> (package:dart_mappable_builder/src/elements/class/class_mapper_element.dart:56:16)
#2      ClassMapperElement.fields (package:dart_mappable_builder/src/elements/class/class_mapper_element.dart:66:4)
#3      ClassMapperElement.fields (package:dart_mappable_builder/src/elements/class/class_mapper_element.dart)
#4      ClassMapperGenerator.generate (package:dart_mappable_builder/src/generators/class_mapper_generator.dart:98:26)
#5      MappableBuilder.generateMapperFile.<anonymous closure> (package:dart_mappable_builder/src/builders/mappable_builder.dart:90:60)
#6      MappedListIterable.elementAt (dart:_internal/iterable.dart:415:31)
#7      ListIterator.moveNext (dart:_internal/iterable.dart:344:26)
#8      Future.wait (dart:async/future.dart:523:26)
#9      MappableBuilder.generateMapperFile (package:dart_mappable_builder/src/builders/mappable_builder.dart:90:31)
<asynchronous suspension>
#10     Future.wait.<anonymous closure> (dart:async/future.dart:525:21)
<asynchronous suspension>
#11     MappableBuilder.build (package:dart_mappable_builder/src/builders/mappable_builder.dart:35:7)
<asynchronous suspension>
#12     runBuilder.buildForInput (package:build/src/generate/run_builder.dart:83:7)
<asynchronous suspension>
#13     Future.wait.<anonymous closure> (dart:async/future.dart:525:21)
<asynchronous suspension>

Thanks for reporting. This should definitely not throw.
I will add a testcase for this and try to fix this asap.

@brighttank Fyi this opened up a larger can of worms than intended, but I want to get this feature right.
Basically I have to look at the initializers statements to make this work. This was on my todo list anyways because it enables some more possibilities of what you can do in constructors that is also supported by this package.
I've come across a few cases that are hard to reason about, mainly the one that I described here. It would be awesome to get some more opinions on this before I decide how to continue.

My thoughts are that Option 3 is obviously wrong because:
  assert(DataMapper.fromJson({ 'a': 1, 'b': 2, }).toJson() == { 'a': 1, 'b': 2, });

must be true otherwise the universe will cease to exist.
Regarding Options 1 & 2 I think Option 2 makes the most sense. I read the constructor as saying that the class property 'a' maps to the Json property 'b'. The question is then should the switching happen in both directions which I think the answer is yes.
I could see Option 1 making sense if there were some other way of initializing the class property 'a', eg. from a different constructor but I don't think that's the primary use case. Typically a mapper library is from going from Json > Class Object > Json.
Hope that's helpful.

Thanks, I also feel option two makes the most sense.
Option 3 is actually how it is currently, but I would consider this wrong behavior as you said.

This is now added in 3.1.0


Fix RegExp in i18n status tracker

What kind of changes does this PR include?

Something else!

Description

.+ and \.+ are not the same thing in Regular Expression Land 😅
This fixes URLs in the i18n tracker. Hopefully for real this time 🤞

size-limit report 📦

Path
Size

/index.html
13.13 KB (0%)

/_astro/*.js
16.54 KB (0%)

/_astro/*.css
9.05 KB (0%)


The window when setFocusItemsOnTap?

Having mapView.setFocusItemsOnTap(true);
How do I change the font size and the windows size? When trying out on the osmdroid's provided samples, it is big enough, however mine is too small and barely readable, how do I fix it?
I've been looking into those samples and studying them, but couldn't find any code or references, which indicates where I am configuring that. Thanks in advance!
Talking about this info window, just for clearance...

See org.osmdroid.views.overlay.ItemizedOverlayWithFocus. There's a number of protected static variables that represent how it's drawn. Extend the class with your own and override the values

Hi, thanks for this information, can you provide code to show how this could be accomplished? As far as I can see, they are all finals, so I cant just override them. I have my own Itemized things which extends ItemizedOverlayWithFocus, and now?

I think i'll just make setters for all of the variables, that way you can configure them on a per marker basis.

merged to develop, see if that you meets your needs. You can also look at the "Marker" class, which has more options

operation timeout. reopen if this is still an issue for you


[Coverity CID :197611]Integer handling issues in /lib/os/printk.c

Static code scan issues seen in File: /lib/os/printk.c
Category: Integer handling issues
Function: z_vprintk
Component: Other
CID: 197611
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996

*** CID 197611:  Integer handling issues  (CONSTANT_EXPRESSION_RESULT)
/lib/os/printk.c: 166 in z_vprintk()
160     s32_t d;
161
162     if (long_ctr == 0) {
163     d = va_arg(ap, int);
164     } else if (long_ctr == 1) {
165     long ld = va_arg(ap, long);

CID 197611:  Integer handling issues  (CONSTANT_EXPRESSION_RESULT)
"ld ><PHONE_NUMBER>" is always false regardless of the values of its operands. This occurs as the logical first operand of "||".

166     if (ld > INT32_MAX || ld < INT32_MIN) {
167     print_err(out, ctx);
168     break;
169     }
170     d = (s32_t)ld;
171     } else {

This is a duplicate of 13843, Coverity triggered due to:
commit 4aa48833d812ca56b62226462d48da24fb9bf756 (upstream/topic-sensors)
Author: Patrik Flykt<EMAIL_ADDRESS>Date:   Thu Mar 14 19:42:51 2019 -0600
subsystems: Rename reserved function names


Workaround for sum reduction

A _sum function, similar to that of _mean as done in #399.
Build and test passes locally.
cc: @eaplatanios

Adding _sum is not necessary. Quote from this comment:

The PR tests integrating TensorFlow directly into a toolchain:

Delete TensorFlow module and artifacts from an existing toolchain.
Use toolchain to build swift-apis.
Copy built TensorFlow artifacts back into the toolchain.

_mean is a workaround for linker errors encountered during CI for swift-models:
<compiler-generated>:0: error: undefined reference to 'AD__$s10TensorFlow19softmaxCrossEntropy6logits6labels9reductionAA0A0VyxGAH_AGys5Int32VGA2HXFtAA0aB13FloatingPointRzlFfA1_A2HcfU___jvp_src_0_wrt_0'
<compiler-generated>:0: error: undefined reference to 'AD__$s10TensorFlow19softmaxCrossEntropy6logits6labels9reductionAA0A0VyxGAH_AGys5Int32VGA2HXFtAA0aB13FloatingPointRzlFfA1_A2HcfU___vjp_src_0_wrt_0'
<compiler-generated>:0: error: undefined reference to 'AD__$s10TensorFlow19softmaxCrossEntropy6logits6labels9reductionAA0A0VyxGAH_AGys5Int32VGA2HXFtAA0aB13FloatingPointRzlFfA1_A2HcfU___pullback_src_0_wrt_0'

Adding _mean and renaming usages was sufficient to fix these errors, so _sum is not necessary at the moment. We're debugging these linker errors so we can remove _mean ASAP.

cc @pschuh

@dan-zheng oh sorry, I just thought that the _mean and _sum direction was a good move forward.


examples/k8s: update kubernetes examples

cc @ElijahCaine for docs update
cc @cjyar per dex-dev forum
closes #518

cc @dghubble

Minor things, looks pretty great.

comments addressed.


Adding Państwowa Akademia Nauk Stosowanych w Przemyślu

Adding Państwowa Akademia Nauk Stosowanych pansp.pl domain

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

@daeidd Pull request merged. Thank you.


v2.1.3 postgresql adapt bug

postgresDialect count add every query times
it's should be set to 1


Backport "HBASE-28605 Add ErrorProne ban on Hadoop shaded thirdparty jars (#5918)" to branch-2.5

This change results in this error on master at 3a3dd66e21.
[WARNING] Rule 2: de.skuzzle.enforcer.restrictimports.rule.RestrictImports failed with message:

Banned imports detected:
Reason: Use shaded version in hbase-thirdparty
        in file: org/apache/hadoop/hbase/backup/TestBackupDelete.java
                org.apache.hadoop.thirdparty.com.google.common.collect.Sets (Line: 34, Matched by: org.apache.hadoop.thirdparty.**)

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 14s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2.5 Compile Tests _

+1 :green_heart:
mvninstall
4m 26s
branch-2.5 passed

+1 :green_heart:
compile
6m 10s
branch-2.5 passed

+1 :green_heart:
spotless
0m 49s
branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 27s
the patch passed

+1 :green_heart:
compile
6m 43s
the patch passed

+1 :green_heart:
javac
6m 43s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+1 :green_heart:
hadoopcheck
17m 47s
Patch does not cause any errors with Hadoop 2.10.2 or 3.2.4 3.3.6.

+1 :green_heart:
spotless
0m 42s
patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 22s
The patch does not generate ASF License warnings.

43m 12s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5935/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5935

Optional Tests
dupname asflicense javac hadoopcheck spotless xml compile

uname
Linux<PHONE_NUMBER>eb 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.5 / c7248ab5e4

Default Java
Eclipse Adoptium-11.0.17+8

Max. process+thread count
77 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5935/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 17s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.5 Compile Tests _

+1 :green_heart:
mvninstall
4m 18s
branch-2.5 passed

+1 :green_heart:
compile
2m 43s
branch-2.5 passed

+1 :green_heart:
shadedjars
6m 22s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
2m 42s
branch-2.5 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 22s
the patch passed

+1 :green_heart:
compile
2m 28s
the patch passed

+1 :green_heart:
javac
2m 28s
the patch passed

+1 :green_heart:
shadedjars
5m 54s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
2m  8s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
244m 48s
root in the patch passed.

281m 42s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5935/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5935

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux fd05e8fa688b 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.5 / c7248ab5e4

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5935/1/testReport/

Max. process+thread count
8050 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5935/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 17s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.5 Compile Tests _

+1 :green_heart:
mvninstall
2m 28s
branch-2.5 passed

+1 :green_heart:
compile
1m 36s
branch-2.5 passed

+1 :green_heart:
shadedjars
4m 36s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 30s
branch-2.5 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 13s
the patch passed

+1 :green_heart:
compile
1m 38s
the patch passed

+1 :green_heart:
javac
1m 38s
the patch passed

+1 :green_heart:
shadedjars
4m 35s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 31s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
317m 25s
root in the patch passed.

344m 10s

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5935/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5935

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 03c0a400ed45 5.4.0-182-generic #202-Ubuntu SMP Fri Apr 26 12:29:36 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.5 / c7248ab5e4

Default Java
Temurin-1.8.0_352-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5935/1/testReport/

Max. process+thread count
8688 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5935/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Hover effect added

📋 Description
hover effect on button as well as on cards are applied
✅ Checklist
Before submitting the PR, please make sure you have completed the following:

My code follows the style guidelines of this project.
I have performed a self-review of my own code.
I have commented my code, particularly in hard-to-understand areas.
I have made corresponding changes to the documentation (if applicable).
My changes generate no new warnings.
I have tested it locally and it works fine.
Any dependent changes have been merged and published in downstream modules.

🏷 Types of Changes
What type of changes does your code introduce? (Check all that apply)

[ ] UI enhancement (non-breaking change which enhances UI) 🎨

📸 Screenshots (if applicable)
https://github.com/user-attachments/assets/6476be4c-74da-4a8d-9663-02e0e4ef4f8f

Thank you for contributing to VigneshDevHub! We look forward to reviewing your PR and getting it merged!

Hey @MaahiVaghela ,Thank you for your efforts, but we are not fully satisfied with the implementation. The effects seem out of place and do not align well with the overall UI design.


do we want a NEWS.md file?

See for example:
https://github.com/JuliaLang/julia/blob/master/NEWS.md
But RHEOS is small so we could probably have it persistent, i.e. the entire history of significant changes is contained there.
New changes could be prepended to the current version in progress, the section at the top of the file.

Assuming not enough interest in this for now so will close this issue.


add Beer Sheva trees

https://www.beer-sheva.muni.il/residents/environment/pkidyearot/pages/invalidlicense.aspx
need to crawl in 2 phases:

get all liecences id.
construct url per id according to this format:
https://www.beer-sheva.muni.il/Residents/Environment/PkidYearot//Lists/List/DispForm.aspx?ID=3720

@GalGend @gruppin
there is also this url
https://www.beer-sheva.muni.il/Residents/Environment/PkidYearot/pages/validlicense.aspx
and in both there are very old licenses
i made a cut by date so we ignore the old
but do we want to use this second url as well?

branch issue_566_beer_sheva_tree

yes, we take as many as we can :)
On Sat, 4 Mar 2023 at 15:08, yaelal @.***> wrote:

branch issue_566_beer_sheva_tree
—
Reply to this email directly, view it on GitHub
https://github.com/meirim-org/meirim/issues/566#issuecomment-1454734577,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEMETVQ2WDJCE3ISRX4Z22DW2M5DVANCNFSM6AAAAAARTN6MWE
.
You are receiving this because you were mentioned.Message ID:
@.***>

pr https://github.com/meirim-org/meirim/pull/665


Skyline: refactor our ParseEnum method to use Enum.TryParse() instead of Enum.Parse() in a try/catch block.

When debugging, "Exceptions Settings">"Break When Thrown">(all possible exceptions) is a great way to quickly locate a test exception. Employing exceptions as normal flow of control severely limits that feature's usefulness.
We should always use things like TryParse in favor of Parse when the language provides them. Exceptions should be exceptional.
Also, fix the typo in DetectionGraphType default value that was causing this to trip in the first place.

Good point - I'm going to back out the Settings.Designer.cs change and let Rita deal with that seperately.


Added Strong password problem using python

Issue no: #10

@Sulagna-Dutta-Roy Add all 4 files in one PR

Actually I wanted to make this pr only on python. But forget to mention in issue

@Sulagna-Dutta-Roy  Just give it a try in other languages too

Sure 😄

@Sulagna-Dutta-Roy Any progress?


feat: dynamic import to interop with modules using __esModule

Problem
Dynamically importing an ESM .js file resulting in getting wrapped in {"default": ... }.
Importing the following would look like this:
export default 1234

{"default":{"default":1234}}

Changes

New core-utils transforms dynamic imports to interop with transformed modules. Although this is a feature, it's also a breaking change.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Access to compilation unit manager and fast id resolution

A compilation unit is cached and updated.
It is no longer needed that the resource to embed into the C# dll is written to disk first.
Determining which declarations exist base on lexing, without having to do the full compilation.

@bettinaheim just checking on the status of this PR. Are these changes still relevant? Any reason this hasn't been merged yet?

Closing this stale PR for now. @bettinaheim, please let me know if these changes are still relevant. If so, we should probably merge this branch with the latest code, re-test, and start a new PR.


Use Guzzle/Service/Client get Method to Set Header

Remove calls to setDefaultOption to set the headers for the
get request being generated by the AbstractProvider. This change
was made to fix Requires authentication errors being recieved
from GitHub and Unknown authentication scheme errors being
recieved from LinkedIn.
Looking into the documentation on Guzzle the get method on the
client will manage and set our headers for us, and was used in
place of setDefaultOption.
Tests were updated to reflect the removal of the call to
setDefaultOption.

@Jaspaul, is this something that will also need to be ported into the master branch for 1.0.0-dev?

@ramsey I don't think it applies to master. These changes are specific to "guzzle/guzzle": "~3.7" and master is running "guzzlehttp/guzzle": "~6.0".

This change was made to fix Requires authentication errors being recieved from GitHub and Unknown authentication scheme errors being recieved from LinkedIn.

@jaspaul, my question about whether this needs to be ported into the master branch was more to this point. Does 1.0.0-dev encounter these errors?
Additionally, does the oauth2-linkedin package have this problem? If so, this should be ported into that package.
Pinging @stevenmaguire, who maintains the oauth2-linkedin package.

Wow! I missed this ping. Sorry.
If this problem is not present in the version of the client running Guzzle 6, does this need to be addressed in the provider project? Maybe I am missing something. If so, @Jaspaul can you demonstrate the problem you are experiencing and create an issue in the linkedin project?

I don't understand how setting the headers like this:
$client->setDefaultOption('headers', $headers);
$request = $client->get()->send();

is any different from this, in Guzzle 3.7:
$request = $client->get(null, $headers)->send();

Can you show the problem so that we can reproduce it?
Thanks!
(At this point, I'm just assuming this is a bugfix for the 0.12.x series, and we will not need to port this into the 1.0.x series.)

I spent a bit more time testing the LinkedIn provider today and I did uncover a small problem with the completing the access token retrieval.
The access token request object needed to include a 'Content-Type: application/x-www-form-urlencoded` header to be successful with LinkedIn. I've included an override method in the LinkedIn provider that appends this header before completing the transaction.
@jaspaul, please pull the latest from the Linkedin provider and test this out to see if it alleviates your concerns.
https://github.com/thephpleague/oauth2-linkedin/blob/master/src/Provider/LinkedIn.php#L131
@ramsey the spec does indicate that this header must be included for Access Token retrieval. It does not appear that the "stock" behavior current sets it. Should this change be rolled into the core package prior to beta? If so, I am happy to submit a PR and roll out the changes in the LinkedIn package.
http://tools.ietf.org/html/rfc6749#section-4.1.3

@stevenmaguire I'm absolutely certain this was mentioned before and must have been forgotten. We absolutely should be sending a Content-Type header when appropriate.

Good! I will prepare a PR as there doesn't seem to be one open.

This was discussed in #340 but I never got around to making it happen. @stevenmaguire I'm happy to do that right now, unless you are already?

Oh! Sorry, @rtheunissen I was in the midst of putting the fix in. It is up at #381.

I've merged #381 into master. What should I do with this pull request? Merge into 0.12.x and tag a bugfix release there?
I'm still not sure how this change fixes the same content-type problem that #381 addresses for the 1.x series.

Is anyone able to answer my questions about this PR? How does it address the same issue that #381 fixes in 1.x? I see nothing in the diff dealing with content-type.
@Jaspaul, I'd like to merge in your pull request, so please help me understand the problem this is solving.
Thanks!

I am not up to speed on the exact problem mentioned here. I only referenced the issue that was resolved in #381 in an effort to see if @Jaspaul felt that solution or the problem it solved would alleviate the symptoms reported here.
I have nothing further to contribute to this PR until more information is available.

@Jaspaul, anything?

Closing this ticket due to lack of activity.
@Jaspaul, if you're still having this problem and want this merged in, please open a new pull request and help me understand the problem it solves and how this code solves that problem. Thanks!


display the generated cards in row fashion in desktop mode

I have gone through your readme.md file, and i would like to contribute in this repository, please assign this issue to me @piyushkdas0611

sure go for it


The requested URL /index.php/dashboard was not found on this server.

After upgrading to Apache 2.2.22 / PHP 5.4.4-14+deb7u7 i cant access the solder api any more. Error: The requested URL /index.php/dashboard was not found on this server.
Apache Error log (LogLevel debug):
[Sun Feb 09 20:55:39 2014] [error] [client XX.XX.XX.XX] File does not exist: /var/www/technicsolder/public/index.php/dashboard
[Sun Feb 09 20:55:39 2014] [debug] mod_deflate.c(615): [client XX.XX.XX.XX] Zlib: Compressed 305 to 232 : URL /index.php/dashboard

@everyone This is caused by "AllowOveride" in the Directory settings (default /etc/apache2/apache2.conf) not being set to something other than None (Default setting nowdays). I have set it to All because I cant seem to find a way to enable just rewrite.
@sct Maybe you can include this as a FYI in the solder install documentation?

@Bysokar @\everyone mentions the user everyone, not people in this thread.

 Why would GitHub Allow that... or someone to even use the username! :( @skwerlman

Put in a Request to get that looked at by github.. Haha fingers crossed.


[AutoDiff] NFC: dedupe array semantic call utilities.

Delete differentiation array semantic call utilities:

bool isArrayLiteralIntrinsic(FullApplySite applySite)
ApplyInst *getAllocateUninitializedArrayIntrinsic(SILValue v)

Use ArraySemanticsCall from ArraySemantics.h instead.
Resolves SR-12894.

@swift-ci Please smoke test


Python 2.7 support

I made some changes in my fork to support Python 2.7. I didn't do the work to make it a single 2 and 3 codebase yet, but I think it'd be very easy since the changes to make it work on 2 alone were very minimal. Would you be open to a PR for that, or is this Python 3 only and you'd like it to stay that way?

@SmileyChris are you interested in releasing your fork https://github.com/SmileyChris/pyuca to pypi?

@SmileyChris  the one you have supports 2 and 3 both, so I guess something more generic? :) Having your stuff in pypi would be awesome!

Definitely sounds like a good idea, best if @jtauber could approve this change.

@SmileyChris can you do a pull request (or is it the same as @nijel's #4?) ?
I should be able to review it in the next day or so and merge and release.

@SmileyChris oh, and make sure the AUTHORS files properly credits you and anyone else.

@jtauber It should be same, I've just updated Travis setup and fixed doctests on top of that.

@nijel did a rebase which makes the commits look a bit dirty, but the only changes were indeed his small test fixes.

@SmileyChris @nijel @pmclanahan merged and released as 1.1! Thanks for all your work

Thanks all!


Fix add/delete repeated members error in zset/set/hash types

close #1651

@ChrisZMF Very happy to see you back again!

So, this is because the input is first input in batch, and then, write to store. Should we insert to set only when the key is not existed, and should be insert to batch?

It may have a partial commit if the instance is broken in the middle of the operation.

IMO, if you already have a fix, there is no need to open an issue here.
Although there is already an issue associated with the PR, please also update the top comment (it can be copied from issue, pictures are not so convenient, those can actually be copied with block text)
Good catch btw, did not CR

IMO, if you already have a fix, there is no need to open an issue here. Although there is already an issue associated with the PR, please also update the top comment (it can be copied from issue, pictures are not so convenient, those can actually be copied with block text)
Good catch btw, did not CR

Issue is used to record and describe the details of the problem. It's more convenient to get and check it in the future.
Top comment should be updated, thx.

Issue is used to record and describe the details of the problem. It's more convenient to get and check it in the future.

yean, i get your point.
PR also can record the details (in the top comment) and then merge them in as a squash commit message.
it (commit or PR or the details) also can be got and checked in the future.
In other words, a PR can actually do everything that a issue can do.

This code LGTM. Would you mind format the code using ./x.py format? Seems that CI failed here.

Issue is used to record and describe the details of the problem. It's more convenient to get and check it in the future.

yean, i get your point.
PR also can record the details (in the top comment) and then merge them in as a squash commit message. it (commit or PR or the details) also can be got and checked in the future. In other words, a PR can actually do everything that a issue can do.

Issue is used to record and describe the details of the problem. It's more convenient to get and check it in the future.

yean, i get your point.
PR also can record the details (in the top comment) and then merge them in as a squash commit message. it (commit or PR or the details) also can be got and checked in the future. In other words, a PR can actually do everything that a issue can do.

OK

Thanks @mapleFU @PragmaTwice


Error compiling

Hello!
Thank you for a very nice project. I am trying to install it inside a docker image and have downloaded everything, but I am getting the following error:
I have no name!@c7cd63e260b5:/workspace/src/minicore$ make
g++ -DBLAZE_USE_SLEEF=1 -O3 -std=gnu++17 -march=native -Wall -Wextra -Wpointer-arith -Wformat -Wunused-variable -Wno-attributes -Wno-ignored-qualifiers -Wno-unused-function -Wdeprecated -Wno-deprecated-declarations -Wno-deprecated-copy  -I. -Iinclude -Iinclude/minicore -Iblaze -Ilibosmium/include -Iprotozero/include -Ipdqsort -Iinclude/thirdparty -Isleef/build/include -Isleef/dynbuild/include   -DBOOST_NO_AUTO_PTR -lz   -L./libkl -Lsleef/build/lib -Lsleef/dynbuild/lib -Llibkl -Llibsimdsampling -lz src/utils/alphaest.cpp -o alphaest -DNDEBUG -fopenmp -O3 libsleef.a
In file included from include/minicore/util/shared.h:2,
                 from include/minicore/utility.h:6,
                 from src/utils/alphaest.cpp:1:
./robin-hood-hashing/src/include/robin_hood.h: In member function ‘size_t robin_hood::detail::Table<IsFlat, MaxLoadFactor100, Key, T, Hash, KeyEqual>::calcMaxNumElementsAllowed(size_t) const’:
./robin-hood-hashing/src/include/robin_hood.h:1849:52: error: ‘numeric_limits’ is not a member of ‘std’
 1849 |         if (ROBIN_HOOD_LIKELY(maxElements <= (std::numeric_limits<size_t>::max)() / 100)) {
      |                                                    ^~~~~~~~~~~~~~
./robin-hood-hashing/src/include/robin_hood.h:174:59: note: in definition of macro ‘ROBIN_HOOD_LIKELY’
  174 | #    define ROBIN_HOOD_LIKELY(condition) __builtin_expect(condition, 1)
      |                                                           ^~~~~~~~~
./robin-hood-hashing/src/include/robin_hood.h:1849:73: error: expected primary-expression before ‘>’ token
 1849 |         if (ROBIN_HOOD_LIKELY(maxElements <= (std::numeric_limits<size_t>::max)() / 100)) {
      |                                                                         ^
./robin-hood-hashing/src/include/robin_hood.h:174:59: note: in definition of macro ‘ROBIN_HOOD_LIKELY’
  174 | #    define ROBIN_HOOD_LIKELY(condition) __builtin_expect(condition, 1)
      |                                                           ^~~~~~~~~
./robin-hood-hashing/src/include/robin_hood.h:1849:76: error: ‘::max’ has not been declared; did you mean ‘std::max’?
 1849 |         if (ROBIN_HOOD_LIKELY(maxElements <= (std::numeric_limits<size_t>::max)() / 100)) {
      |                                                                            ^~~
./robin-hood-hashing/src/include/robin_hood.h:174:59: note: in definition of macro ‘ROBIN_HOOD_LIKELY’
  174 | #    define ROBIN_HOOD_LIKELY(condition) __builtin_expect(condition, 1)
      |                                                           ^~~~~~~~~
In file included from /usr/include/c++/11/algorithm:62,
                 from ./robin-hood-hashing/src/include/robin_hood.h:42,
                 from include/minicore/util/shared.h:2,
                 from include/minicore/utility.h:6,
                 from src/utils/alphaest.cpp:1:
/usr/include/c++/11/bits/stl_algo.h:3467:5: note: ‘std::max’ declared here
 3467 |     max(initializer_list<_Tp> __l, _Compare __comp)
      |     ^~~
make: *** [Makefile:145: alphaest] Error 1

What can I do about this? I am not very good at C++, so the error is probably something simple from my side.
Thank you in advance!

Hi -
Sorry for the trouble! I'm hoping this was just the library getting out of date.
I've just updated the main branch (https://github.com/dnbaker/minicore/pull/64) to try to fix this issue. Could you try it again?
Best,
Daniel


package cuda-binaries fails

@madisongh I'm not sure this is really an issue or not. I'm trying to get access to the cuda tools, such as cuda-gdbserver.
I've added "cuda-binaries" to my IMAGE_INSTALL packages but I get this
ERROR: Task do_populate_sdk in /opt/oe/krogoth/meta-tempmine/recipes-core/image/core-image-mimbal.bb rdepends upon non-existent task do_populate_sysroot in /opt/oe/krogoth/meta-tegra/recipes-devtools/cuda/cuda-binaries_8.0.34-1.bb
ERROR: Command execution failed: 1

I see a lot of cuda-* packages. Maybe I'm including the wrong one? what's a good set to include?

Try "cuda-toolkit" instead.  "cuda-binaries" is just used to download the .deb repository; other recipes depend on it so they can all share the same download (which is really large).

ok, have that. thanks.
But, I don't see cuda-gdbserver on the target or things such as nvcc in my resultant sdk. Any thoughts on what i'm doing wrong?

From the cuda-toolkit recipe I see this get expanded out
cuda-gdb-src-8-0_8.0.34-1_arm64.deb

is there a way to build it?

Ah, right.  There are so many packages there, and I guess I didn't get enough of them to fully flesh out on-target development.  You probably need to add cuda-command-line-tools and cuda-core, at least, to the CUDA_PKGS definition in the recipe to get the additional programs.

hmm, tried adding command-line-tools, core, and toolkit but no joy. The gdb one in there is source code so it feels like it needs to be explicitly built. Should I use --extract and then is there a command to build for that .deb file?

ok, it's starting to sorta come together for me. I added these lines to the recipe.
install -d ${D}${prefix}/local/cuda-8.0/bin
cp -R --preserve=mode,timestamps ${B}/usr/local/cuda-8.0/bin/* ${D}${prefix}/local/cuda-8.0/bin
FILES_${PN} = "${prefix}/local/cuda-8.0/lib/*${SOLIBS} ${prefix}/local/cuda-8.0/lib/stubs ${prefix}/local/cuda-8.0/bin/*"

I now see cuda-gdbserver in the resultant filesystem.
The native/host stuff is confusing to me. Is there a way to build the tools for both the target and the host? e.g., so they show up when I do populate_sdk?

It's confusing to me, too, which is why the recipes aren't really complete.  I haven't even looked into how to fit them into a Yocto-style SDK yet.  I've only put enough pieces in place to cross-build some CUDA apps within an OE/Yocto build workspace.  I'm hoping to get more pieces together over time, but it's complicated and will take time to understand how they all fit together.
This is one of the downsides of trying to wedge these binary-only packages into something other than the specific distro that NVIDIA builds them for.

yeah, that makes sense. I'll take it as a work in progress. I'm hesitant to fork it as I don't feel good about my own recipe but fwiw the lines above will move the toolkit binaries into the target filesystem. Feel free to close this case if you feel that's appropriate.

I've updated the cuda-toolkit recipe to bring in the command line tools, similar to what you mentioned above, but I've put the .../bin/* files into the -dev package, rather than the main package.  I think that's more correct, but as you say, this is a work in progress....

thanks Matt. I'll give it a whirl tomorrow.

@madisongh looking good. Thanks for addressing this.