Add require json to prevent NameError when using the client

I found a small bug when hooking this gem into one of my projects, the Client class can't find JSON when trying to run the gem as-is.  See my IRB session below (only modification to the output is my API key):
2.3.0 :001 > require 'usda_ndb'
 => true
2.3.0 :002 > UsdaNdb::VERSION
 => "0.0.1"
2.3.0 :003 > UsdaNdb.configure do |c|
2.3.0 :004 >     c.api_key = 'KEY'
2.3.0 :005?>   end
 => "KEY"
2.3.0 :006 > UsdaNdb.search('cheese')
NameError: uninitialized constant UsdaNdb::Client::JSON
	from /Users/swh_personal/.rvm/gems/ruby-2.3.0/gems/usda_ndb-0.0.1/lib/usda_ndb/client.rb:11:in `fetch'
	from /Users/swh_personal/.rvm/gems/ruby-2.3.0/gems/usda_ndb-0.0.1/lib/usda_ndb.rb:15:in `search'
	from (irb):6
	from /Users/swh_personal/.rvm/rubies/ruby-2.3.0/bin/irb:11:in `<main>'
2.3.0 :007 > UsdaNdb.reports('01208')
NameError: uninitialized constant UsdaNdb::Client::JSON
	from /Users/swh_personal/.rvm/gems/ruby-2.3.0/gems/usda_ndb-0.0.1/lib/usda_ndb/client.rb:11:in `fetch'
	from /Users/swh_personal/.rvm/gems/ruby-2.3.0/gems/usda_ndb-0.0.1/lib/usda_ndb.rb:11:in `reports'
	from (irb):7
	from /Users/swh_personal/.rvm/rubies/ruby-2.3.0/bin/irb:11:in `<main>'
2.3.0 :008 > exit

I version-bumped and built the gem locally, and it worked just fine. I'm guessing that JSON is being used by test dependency because it doesn't seem to be getting caught in the specs.

Thanks :) It seems that I tested it only with Rails. Also, I added a spec to cover that.


[spi_device,dv] Add spi_device_pass_cmd_filtering testcase

This is a spi_device_pass_cmd_filtering testcase.
It turns the filter on and off and verifies if the command is filtered
when it is turned on
Signed-off-by: Madhuri Patel<EMAIL_ADDRESS>

I will close this PR and @kosta-kojdic will make a new PR on this test


adding personas

please review and merge
//cc @dragon119, @francischeung, or @mj1856

Hi @bennage, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (christb). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, or work for Microsoft Open Technologies, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

Reviewed...  Looks good in terms of roles and responsibility coverage.  I see Poe can cover the DevOps story :)


Cell content drag & drop

Hi,
Is individual cell to cell drag & drop a feature which is available at the moment?
If yes, is there an example I could use to try and understand?
If not, is this something which will be possible in the near future?
Thanks!
Icarian

Hello @Icarian2021,
Please provide us with a sample of what are you talking about, for now, it's not very clear. The same description can mean multiple things.

Closed because of inactivity.


Customozing Oncoplots Maf file : adding CN.Table from data.frame with error message "Error in file.info(file) : argument 'filename' incorrect"

Hi,
I have a problem dealing with the custom functions with a Maf file.
I saw in the Customizing oncoplots R Markdown from 2022-04-26 (https://www.bioconductor.org/packages/devel/bioc/vignettes/maftools/inst/doc/oncoplots.html) that we could add copy number variations from a non-gistic file by using this function :
laml.plus.cn = read.maf(maf = laml.maf,
cnTable = custom.cn.data,
verbose = FALSE)
I have tested it on my script using the laml file from TCGA and the "dummy CN file" and this is working. Now, when testing with my own files (Maf file and customed test CN table):
#test adding CN file to Maf File

head(CN.Table)
Hugo_Symbol Tumor_Sample_Barcode Variant_Classification
1        TP53             17R02878                    Del
2      DNMT3A              6538282                    Del
3      DNMT3A              8783792             ShallowAmp
4        BAP1              8739836                   Loss
5      ARID1A                72987                    Dup

MafLIQUID.plus.CN = read.maf(MafLIQUID, cnTable = CN.Table)
-Reading
Error in file.info(file) : argument 'filename' incorrect

I have tested to merge my own CN.Table with the laml file from TCGA and this is working, meaning the issue does not come from my file format.
I am quite a rookie on R but I could not find many information on these customizing functions for Maf File : any advice on this would be very much appreciated.
Thanks so much.

Hi,
Is  custom.cn.data a data.frame or a path to the file?

The cnTable is a txt file input, so cnTable='your_cntable.txt' a path pointing to your cntable file would work. I also find not much information around and hard to find your way around. Good luck!


Third person

Activating third person switches sound perspective to third person even if switched back to first person and disables V's footstep sounds. This bug remains till a game restart occurs.

this should be fixed already, because the sound listener is still the first person camera.
Its the newest V68 update.


Export table to CSV

What would you like to be added?
If there's any way there could be a function to either export a the table view to a CSV file or even just the ability to copy/paste into Excel (or similar), this would be the godsend of all godsend plugins.
Also a note: I'm terrible with computer science so Obsidian has been a fun challenge so far (currently configuring it to support my office), and I just wanted to let you know how much I appreciate Projects, even without the export function. I was desperate to find some way to convert properties into a table of contact information/data, so imagine my relief when I enabled the plugin and only had to rearrange the fields! So thank you so much for all the work you do.
Why is this needed?
Much of what I do (along with, I'm sure, many others) involves mail merges, and the ability to compile my data is already very, very helpful. That said, it's pretty much stuck with me, on my computer screen, and I can't do much with the view provided. It could be a desktop-only feature, it could be a copy/paste function so that I could move my table to Excel or even word- I just need the ability to work with my information the tiniest bit more.

Thanks for sharing your case! Close this as a duplicate of #318, and will add this in the following iterations.


Remove restrictions on Label types

Redo of #5377
Background
Originally, label traits were essentially like Any, but with extra capabilities.

This was unnecessarily slow, as it required boxing every label even though the vast majority are simply unit structs or C-style enums.
Ignited months-long unresolved debates as to whether Box<dyn *Label> should implement the trait.
Required a long list of derives for every implementer.
O(?) comparisons due to dynamic dispatch.

In #4957, labels were simplified: they are represented as just a TypeId and a string literal.

This sped up label comparisons and dependency resolution considerably, as allocations and dynamic dispatch are no longer necessary.
Makes the use of labels more ergonomic, as their type-erased form is Copy. Additionally, none of the extra derives are required.
It introduced major restrictions on what types can be labels: labels can only have names, not data.
In most cases, this change was completely invisible to users.

Objective

Remove the restrictions: allow labels to store any data that they want.
Make complex labels faster than before #4957.
Don't pessimize simple label types -- they should be just as fast as before this PR.
Make comparisons O(1).
Optimize the stack size of type-erased labels.
Keep the user-facing API as simple as possible.

Solution

Allow arbitrary debug formatting by writing to an &mut Formatter.
For comparisons, use a u64.

Types that are 8 bytes or smaller can be encoded and stored inline.
For larger types, intern them and store their index. This also avoids duplicate allocations for identical labels.
Both of these cases are supported in the derive macro.

Keep the stack size low by storing type-related data behind a pointer to an associated const.

Examples
Basic labels get converted to an integer and stored on the stack.
#[derive(SystemLabel)]
enum MyLabel {
    One,
    Two,
}

//
// Derive expands to...

impl IntoSystemLabel for MyLabel {
    fn data(&self) -> u64 {
        match self {
            Self::One => 0,
            Self::Two => 1,
        }
    }
    fn fmt(data: u64, f: &mut fmt::Formatter) -> fmt::Result {
        match data {
            0 => write!(f, "MyLabel::One"),
            1 => write!(f, "MyLabel::Two"),
            _ => Err(fmt::Error),
        }
    }
}

Complex labels get interned, with their index stored on the stack.
#[derive(Debug, Clone, PartialEq, Eq, Hash, SystemLabel)]
#[system_label(intern)]
pub struct MyLabel<T>(Vec<T>);

//
// Derive expands to...

use bevy_utils::{AnyInterner, InternGuard};

// Global label interner for `MyLabel<T>`, for any `T`.
static MAP: AnyInterner = AnyInterner::new();

impl<T: Debug + Clone + Hash + Eq + Send + Sync + 'static> IntoSystemLabel for MyLabel<T> {
    fn data(&self) -> u64 {
        MAP.intern(self)
    }
    fn fmt(idx: u64, f: &mut Formatter) -> fmt::Result {
        let val = MAP.get::<Self>(idx).ok_or(fmt::Error)?;
        write!(f, "{val:?}")
    }
}

Benchmarks
Relative to before this PR.

Using stack-allocated labels.

# of Systems
No deps
% Change
W/ deps
% Change

100
235.51 us
-0.9142%
1.8465 ms
-9.2033%

500
782.39 us
+0.1074%
61.109 ms
-15.269%

1000
1.4279 ms
+1.0771%
310.41 ms
-13.131%

Heap-allocating everything.

# of Systems
No deps
% Change
W/ deps
% Change

100
233.20 us
+1.0003%
2.0064 ms
+1.5735%

500
789.80 us
-0.9972%
64.846 ms
-6.1881%

1000
1.4699 ms
-2.0041%
318.41 ms
-5.2037%

Notes

This PR adds parking_lot and indexmap as dependencies for bevy_utils.

indexmap only has one dependency (hashbrown), which is already a dependency of bevy_utils.

Future Work

We can clean up unused memory by emptying out the global interners after dependency resolution is complete. This would break debug formatting, but comparisons would still work perfectly.
Downcasting can easily be implemented, but the API decisions are left for a future PR.

Changelog

Made the internal representation of labels more flexible.
Added support for complex label types by interning them.

Migration Guide
The Label family of traits (SystemLabel, StageLabel, etc) is no longer object safe.

Any use of Box<dyn *Label> should be replaced with *LabelId - this family of types serves the same purpose but is Copy and does not usually require allocations.
Any use of &dyn *Label should be replaced with impl *Label if possible, or *LabelId if you cannot use generics.

For manual implementers of this family of traits, you should now implement the corresponding Into*Label trait.
enum GameLabel {
    Input,
    Physics,
}

// Before:

impl SystemLabel for GameLabel {
    fn as_str(&self) -> &'static str {
        match self {
            Self::Input => "GameLabel::Input",
            Self::Physics => "GameLabel::Physics",
        }
    }
}

// After:

impl IntoSystemLabel for GameLabel {
    fn data(&self) -> u64 {
        match self {
            Self::Input => 0,
            Self::Physics => 1,
        }
    }
    fn fmt(data: u64, f: &mut Formatter) -> fmt::Result {
        match data {
            0 => write!(f, "GameLabel::Input"),
            1 => write!(f, "GameLabel::Physics"),
            _ => Err(fmt::Error),
        }
    }
}

This is an exceptional writeup, and I agree with the motivations here. A bit annoying to increase the complexity of this niche area further, but I think the expressiveness and performance will be worth it.

@JoJoJet is this still relevant?

Nah, I have no intention to update this.


md-dialog and menu  out of md-sidnav-layour/ md-sidnav-container

Bug, feature request, or proposal:
Bug
What is the expected behavior?
md-dialog should be at center of screen and menu should act like a dropdown
What is the current behavior?
they both got squeezed at buttom of sidnav container
Which versions of Angular, Material, OS, browsers are affected?
angular2, beta.1
Is there anything else we should know?
it worked fine when using angular2.alpha.11
detailed in screenshots:
normal (using angular2.alpha.11)

abnormal  (using angular2.beta.1)

We haven't really changed that much about positioning between alpha and beta. Try clearing your node_modules and reinstalling.

i delete the modules each time i change the version.
as soon as i use beta, the problem appears

https://embed.plnkr.co/146tRVG666CtylkEHYoH/ see this.

It looks like you haven't included the a theme. Try adding this to your Plunk (these are also distributed as a part of the Material builds):
<link<EMAIL_ADDRESS>rel="stylesheet">

than you , it works now. I re-compiled my theme.

In that case I'll consider it resolved.


Consider using custom allocators

For an HTTP server, standard allocators leave much to be desired.  It might be possible to use custom allocators to improve performance.
Examples of custom allocators are NGINX's palloc system.
The allocators should use Rust's type system to ensure that invariants are not violated.  For instance, it should be a lifetime error for a reference to an arena-allocated object to outlive its arena.

The rust ecosystem has settled on this pattern: libs use the system
allocator, but rust binaries by default override that with jemalloc, which
is considered to be quite excellent.
On Sun, Oct 9, 2016, 12:46 PM Demi Marie Obenour<EMAIL_ADDRESS>wrote:

For an HTTP server, standard allocators leave much to be desired. It might
be possible to use custom allocators to improve performance.
Examples of custom allocators are NGINX's palloc system.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hyperium/hyper/issues/929, or mute the thread
https://github.com/notifications/unsubscribe-auth/AADJFzsiYMkAex0xvOk3NmL1TPp0DOUlks5qyUR-gaJpZM4KSFwz
.

@seanmonstar By "custom allocator" I mean something like arena allocation for strings, not a better malloc.

Then this sounds identical to #927

Not quite; this is more about using techniques like arena allocation, while
#927 is more about pooling.  But if you want to handle both as one issue
that's fine.
On Oct 10, 2016 1:44 AM, "Sean McArthur"<EMAIL_ADDRESS>wrote:

Then this sounds identical to #927
https://github.com/hyperium/hyper/issues/927
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/hyperium/hyper/issues/929#issuecomment-252541013, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGGWB1sYxnuEqxCvNMqI64tfArILU0oiks5qydDEgaJpZM4KSFwz
.

Proposing this issue can be closed, in such a case.

Recent benchmarks show hyper to extremely competitive. I'm not against using an arena for things in hyper, but I'd rather specific issues be opened about certain parts, when its shown that using an arena would have a meaningful improvement.


Update TFLite sound classification snippet

Update the TFLite instructions to point to a legacy copy of TFLite sound classification sample, as we'll migrate the sample to use TFLite Task Library.
Once Teachable Machine completes the migration to export models that are compatible with Task Library, I'll send another pull request to update this snippet to point to the new sample.

/gcbrun

@HalfdanJ
Could you merge this change and publish it on Teachable Machine prod? We're working on migrating the TFLite sound classification sample to use TFLite Task Library, which isn't compatible yet with models from Teachable Machine. This migration CL will be submitted in a few days. Thanks!
https://github.com/tensorflow/examples/pull/311


Allow sockaddr_ll size mismatch

Apparently the Linux kernel can return smaller sizes when the value in
the last element of sockaddr_ll (sll_addr) is smaller than the
declared size of that field.

Interesting. Did you see this happen on Ethernet, or with some other link layer?

I saw this happen on Ethernet. I don't recall on which system I tested the original, might have been some virtual fabric.

Also, you'll have to rebase after #1399 merges.

Ok


Device Control UI exists now

The documentation says "This capability (in Microsoft Endpoint Manager admin center (https://endpoint.microsoft.com/) > Devices > Configuration profiles > Create profile > Platform: Windows 10 and later & Profile: Device Control) is not yet available."
Device Control is now available in Intune -> Endpoint Security -> Attack surface reduction -> Device control policy type.
It would be great to have this page updated to incorporate this UI instead of (or in addition to) OMA-URI.

It also does not appear wildcards are supported when deploying via Intune Device Control Policy. It would be good if that is documented in where it discusses InstancePathID.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 7b7a5c17-1358-990b-968d-432a3aab2e17
Version Independent ID: 1b4d4eff-3e22-47d7-4054-6cc9ed0217d0
Content: Microsoft Defender for Endpoint Device Control Removable Storage Access Control, removable storage media
Content Source: microsoft-365/security/defender-endpoint/device-control-removable-storage-access-control.md
Product: m365-security
Technology: mde
GitHub Login: @Dansimp
Microsoft Alias: dansimp

@ssccaavvookk Thank you for your feedback. We have updated the changes via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/6499
Thanks
Sri


Deprecation of starter workflows for Draft commands

With the arrival of Draft in the AKS VS Code extension, the team will be removing and deprecating the starter workflows in the upcoming weeks. If you wish to generate starter workflows, please use the Draft Create a GitHub Workflow command. The starter workflows will continue to be in the AKS extension for the following month, with a removal after June 2024.

This is released already. Closing it.


Disjoint array handling issue with Microchip SAM L21

Greetings,
I have run into an issue while upgrading my SAM L21 crates. With the SVD file ATSAML21G16B.svd, svd2rust v0.27.2 was successful while v0.28.0 (and current master) lead to the following compilation error:
error[E0412]: cannot find type `PMUX1_0` in this scope
   --> src\port.rs:58:19
    |
58  |     pub pmux1_0: [PMUX1_0; 16],
    |                   ^^^^^^^ help: a type alias with a similar name exists: `PMUX1_`
...
111 | pub type PMUX0_ = crate::Reg<pmux0_::PMUX0__SPEC>;
    | -------------------------------------------------- similarly named type alias `PMUX1_` defined here

error[E0412]: cannot find type `PINCFG1_0` in this scope
   --> src\port.rs:60:21
    |
60  |     pub pincfg1_0: [PINCFG1_0; 32],
    |                     ^^^^^^^^^ help: a type alias with a similar name exists: `PINCFG1_`
...
117 | pub type PINCFG0_ = crate::Reg<pincfg0_::PINCFG0__SPEC>;
    | -------------------------------------------------------- similarly named type alias `PINCFG1_` defined here

For more information about this error, try `rustc --explain E0412`.
error: could not compile `atsaml21g16b` due to 2 previous errors

In the generated file port.rs, the block:
#[doc = r"Register block"]
#[repr(C)]
pub struct RegisterBlock {
    // [...]
    #[doc = "0xb0..0xc0 - Peripheral Multiplexing n - Group 1"]
    pub pmux1_: [PMUX1_; 16],
    #[doc = "0xc0..0xe0 - Pin Configuration n - Group 1"]
    pub pincfg1_: [PINCFG1_; 32],
}

has changed to:
#[doc = r"Register block"]
#[repr(C)]
pub struct RegisterBlock {
    // [...]
    #[doc = "0xb0..0xc0 - Peripheral Multiplexing n - Group 1"]
    pub pmux1_0: [PMUX1_0; 16],
    #[doc = "0xc0..0xe0 - Pin Configuration n - Group 1"]
    pub pincfg1_0: [PINCFG1_0; 32],
}

A git bisect pointed me to 874f7df2b634e7fe85388b6416c1370e84802a3f. Is this a regression in svd2rust or an error in the SVD file?
Thanks in advance!

Looks like regression. Thank you for reporting.
cc @n8tlarsen


await() error in SimpleFiber.php

(Great job with Fibers initiative!)
For test purposes I'm refactoring my app with await() function in place of promises-chains. I've got an error:
2021-11-29 21:56:23 [EXCEPTION] Error: Value of type null is not callable in ...\vendor\react\async\src\SimpleFiber.php:59
2021-11-29 21:56:23 [EXCEPTION] #0 ...\vendor\react\async\src\functions.php(92): React\Async\SimpleFiber->suspend()
2021-11-29 21:56:23 [EXCEPTION] #1 ...\MessagesProcessor.php(114): React\Async\await(Object(React\Promise\Promise))

It occurs when I try to use async() function. It's hard to say how to reproduce this bug. In the same call stack, a few promises before, I use a React\Http\Browser with async() function. If I comment this usage (replace to something like resolve(new ResultObject())) - error  doesn't occur. If I use Browser with promise-style api, the PHP process ends with error:
Process finished with exit code -1073741819 (0xC0000005)

I'm using the newest versions of all packages, ofc PHP 8.1.
Do you know what can cause these errors?

This code causes Segmentation fault error (CLI):
<?php
require 'vendor/autoload.php';
$browser = new \React\Http\Browser();
/** @var \Psr\Http\Message\ResponseInterface $response */
$response = \React\Async\await($browser->get('https://github.com'));
var_dump((string)$response->getBody());

...but only for "github.com", for "google.com" returns proper result.
This works fine in both cases:
<?php
require 'vendor/autoload.php';
$browser = new \React\Http\Browser();
$browser
    ->get('https://google.com')
    ->then(fn (\Psr\Http\Message\ResponseInterface $response) => var_dump((string)$response->getBody()));

@szado Thank you for reporting, this definitely shouldn't have happened!
I've tried reproducing this a number of times, but can not reproduce the problem you're seeing on Linux.
A segmentation fault is not something that userland PHP code should be able to trigger. There is also no platform-specific code in ReactPHP involved, so I can only suspect this is an issue with the fibers implementation in PHP itself. I don't think this boils down to an issue in ReactPHP itself, so I wonder if we can break this down to a reproducible script that also shows this segmentation fault without ReactPHP?
Accordingly, it looks like this should probably be reported upstream in PHP. Can anybody take a look at this and link/report back here?
Thank you!

@clue maybe this code will be helpful: https://github.com/szado/reactphp-connection-pool/blob/master/test.php
It triggers Segmentation fault and Error: Value of type null is not callable in ...\reactphp-connection-pool\vendor\react\async\src\SimpleFiber.php on line 59 (it can be more directly related to ReactPHP) on Windows and Linux.

Tested on both Windows and Linux, I didn't notice any difference. The error is present both there and there.
Here is my piece of code. I'm trying to wait for a WebSocket response and give it back. As a result, I get an error. If you don't wait for an answer, but just give out any value, everything goes well
return new Promise(function (callable $resolve) {
  ReplyRoute::reply('Server:GetValue', function (int $value) use ($resolve) {
      $resolve($value); // Error
  });

  $resolve(100); // Good
});

@szado I can reproduce that error and looking into the exact cause (probably related to PHP Fatal error:  Uncaught TypeError: Szado\React\ConnectionPool\ConnectionPool::retryWithDelay(): Return value must be of type Szado\React\ConnectionPool\ConnectionAdapters\ConnectionAdapterInterface, null returned) and then work on a fix.
The browser segfault I can't reproduce on windows. But might be the same root cause internally.

Ran into the same error.
<?php

use React\Promise\Promise;
use React\Promise\PromiseInterface;

use function React\Async\await;
use function React\Promise\resolve;

require_once __DIR__ . '/vendor/autoload.php';

function test(): PromiseInterface {
    $resolver = function ($resolve, $reject) {
      await(resolve());

      $resolve();
    };

    return new Promise($resolver);
}

await(test());

[docker://fiber:latest/]:php /opt/project/index.php

Fatal error: Uncaught Error: Value of type null is not callable in /opt/project/vendor/react/async/src/SimpleFiber.php on line 59

Error: Value of type null is not callable in /opt/project/vendor/react/async/src/SimpleFiber.php on line 59

Call Stack:
    0.0002     391640   1. {main}() /opt/project/index.php:0
    0.0886    4169192   2. React\Async\await($promise = class React\Promise\Promise { private $canceller = NULL; private $result = NULL; private $handlers = [0 => class Closure { virtual $closure = "React\Promise\Promise::React\Promise\{closure}", ... }]; private $progressHandlers = [0 => class Closure { virtual $closure = "React\Promise\Promise::React\Promise\{closure}", ... }]; private $requiredCancelRequests = 0; private $cancelRequests = 0 }) /opt/project/index.php:19
    0.0886    4174816   3. React\Async\SimpleFiber->suspend() /opt/project/vendor/react/async/src/functions.php:89

TL;DR You're only having one fiber (the main fiber) running and you want to await for a promise twice, it's simply not possible.

P.S. Will get you a longer response somewhere between tonight and the end of the weekend.

@WyriHaximus :ok_hand: It might lead to some unexpected errors when you're using a 3rd party library. Right now the example is pretty useless but replace await(resolve()) with some 3rd party function that undirectly calls await somewhere and you're stuck. Will try to find a workaround in my case.

Something like this instead?
<?php

use React\Promise\PromiseInterface;

use function React\Async\async;
use function React\Async\await;
use function React\Promise\resolve;

require_once __DIR__ . '/vendor/autoload.php';

function test(): PromiseInterface {
    return async(function () {
      await(resolve());
    });
}

await(test());

@bartvanhoutte yes, each async will create a new fiber.

Just filed #18 that helps with a few cases mentioned in this issue. And intentionally all of them (except the segfault), but I'd have to test that

A valid reason I can think of to call await in the main fiber is to determine the exit code of the application. Note that the order of things added to the event loop is important as described in @WyriHaximus's blog.
<?php

use React\EventLoop\Loop;

use function React\Async\async;
use function React\Async\await;

require_once __DIR__ . '/vendor/autoload.php';

$timer = Loop::addPeriodicTimer(1, fn() => print 'tick' . PHP_EOL);

$exit = await(async(function () use ($timer) {
    Loop::addTimer(10, fn() => Loop::cancelTimer($timer));
    return 1;
}));

exit($exit);

I can't seem to reproduce https://github.com/reactphp/async/issues/16#issuecomment-989829770 anymore, but I've got another example.
<?php

use React\EventLoop\Loop;

use function React\Async\async;
use function React\Async\await;
use function React\Promise\all;
use function React\Promise\resolve;

require_once __DIR__ . '/vendor/autoload.php';

function someThirdPartyFunction()
{
    print __FUNCTION__ . PHP_EOL;
    await(resolve());
}

function foo()
{
    print __FUNCTION__ . PHP_EOL;

    $concurrent[] = async(someThirdPartyFunction(...));
    $concurrent[] = async(someThirdPartyFunction(...));

    await(all($concurrent));
}

Loop::addTimer(5, fn() => foo());

[docker://fiber:latest/]:php /opt/project/index.php
foo
someThirdPartyFunction
someThirdPartyFunction
foo

Fatal error: Uncaught Error: Value of type null is not callable in /opt/project/vendor/react/async/src/SimpleFiber.php on line 59

Note that for some reason the timer is executed twice ("foo" in console output).
This problem occurs with both the await function in the main branch and the version in https://github.com/reactphp/async/pull/18.
Obviously not the most useful example but add a couple of calls in the call stack and the problem can occur quite fast.

I can no longer reproduce the error from https://github.com/reactphp/async/issues/16#issuecomment-989783173, however there seems to be an issue with timers using async.
<?php

use React\EventLoop\Loop;

use function React\Async\async;
use function React\Async\await;

require_once __DIR__ . '/vendor/autoload.php';

function foo()
{
    print __FUNCTION__ . PHP_EOL;

    await(async(fn() => null));
}

Loop::addTimer(5, fn() => foo());

[docker://fiber:latest/]:php /opt/project/index.php
foo
foo

Fatal error: Uncaught Error: Value of type null is not callable in /opt/project/vendor/react/async/src/SimpleFiber.php on line 59

The same error occurs when an EventLoop is created manually without using \React\EventLoop\Loop::get
SimpleFiber itself creates a new loop in Loop::run(), resulting in two loops.
https://github.com/reactphp/async/blob/main/src/SimpleFiber.php#L44
Example:
<?php

$loop = new \React\EventLoop\ExtEventLoop();

//\React\EventLoop\Loop::set($loop); // solution

$deferred = new \React\Promise\Deferred();
$loop->futureTick(static fn() => $deferred->resolve());

\React\Async\await($deferred->promise());
$loop->run();

Result: Error: Value of type null is not callable in /vendor/react/async/src/SimpleFiber.php:53
After uncommenting Loop::set the problem is solved.
But \React\EventLoop\Loop::set is marked as @internal, so this solution is not safe.

@bartvanhoutte Very good input, I can see where you're coming from! It looks like most of the issues discussed in this ticket stem from lack of documentation how to use the async() and await() functions, so I've just filed #26 to add appropriate documentation. The gist is that making your example work is as simple as updating it like this (refs #19):
<?php

use React\EventLoop\Loop;

use function React\Async\async;
use function React\Async\await;

require_once __DIR__ . '/vendor/autoload.php';

function foo()
{
    print __FUNCTION__ . PHP_EOL;

-    await(async(fn() => null));
+    await(async(fn() => null)()); // or omit as this is a NO-OP
}

- Loop::addTimer(5, fn() => foo());
+ Loop::addTimer(5, async(fn() => foo())); // or Loop::addTimer(5, async('foo'));

@Provoker Interesting find! The await() function indeed assumes it's executing the default loop, so you should simply remove any references to an explicit loop instance. See also https://github.com/reactphp/event-loop#loop


Bootstrap as Management node change

Bootstrap as Management node change

This plan was canceled and the management node approach is applied hence it can be closed.


/dev/null access

Trying to run an app using jlesage/baseimage-gui:debian-10. Its trying to write to /dev/null. It doesn't seem to be able to create a temporary file. Any suggestions. I tried running the container under privileged mode that doesn't seem to help.

Is this still an issue ?  If yes, please provide the container's log showing the errors.


Please provide the code to show how to set JSON configuration to provisioning engine

It seems like the doc doesn't provide the sample to show how to set those json configuration to the engine.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 8604e955-4a77-7abe-0138-e554fdef0b41
Version Independent ID: b03bc3e7-88ec-b808-190c-32e69f0b968e
Content: Configurating the PnP Provisioning Engine
Content Source: docs/solution-guidance/configuring-the-pnp-provisioning-engine.md
Product: sharepoint
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

Thank you for the comment. Yes, the documentation does make it a little unclear. To clarify, the configuration settings is in regards to the "Get-PnPProvisioningTemplate" command above it.
You would pass in your configuration to this command. Please see documentation here.
Get-PnPProvisioningTemplate -Out "Test.xml" -Configuration "MySchema.xml"


update headings

👷 Deploy Preview for fancy-puffpuff-df775f processing.

Name
Link

🔨 Latest commit
4f5a7a3094c26ef6a4cb730d8ae66daec438d287

🔍 Latest deploy log
https://app.netlify.com/sites/fancy-puffpuff-df775f/deploys/64dfa3d38a259400088e69e3


Implemented Whirling Zap-o-matic

I started with a simple one to get to know the project. :)
/Hjulle

Looks pretty solid so far!

Yeah, I was unsure of how to treat the "-"s with respect to CamelCase, so I just took a guess. ;)

Coverage increased (+0.0%) when pulling 62147e38d4f1e06d4fa4ebff63b18e71693fed98 on anka-213:whirling-zap into fc36a5d46bb04f605ef17b6f1503206bb48c730e on danielyule:master.

I didn't notice the spelling error, and I merged it too fast.  I fixed it to make it consistent with Alarm-o-bot.  I don't think that any one way is necessarily right, and I remember changing Alarm-o-bot back and forth a few times until settling on keeping the capitalization of the original card, and removing punctuation.


Fix broken link in "Related" Section

Link for "Rust documentation for the Windows API" - capitalised "Windows" in the link

@dacarab : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good (GitHub is case-sensitive, and the link is to a GitHub Pages site); tested and will merge. Thanks @dacarab.


Usage with Nuxt.js

Hi all,
Wondering if anyone has successfully used Clappr (+ plugins) with Nuxt.js in SSR mode?
I have Clapper (0.4.1) Installed and trying to use as an import in my vue component:
import Clappr from '@clappr/player'
This works fine when navigating to the page using the nuxt-routing etc, but if I refresh the page containing this vue component I get the error Window is not defined.
Any help will be much appreciated

I've never used Nuxt.js but I think this problem is because Clappr is being built before the DOM reference exists. Your component loaded via SSR need to use a placeholder instead of the Clappr Player and when it's loaded on the client-side (when exists the DOM reference), Clappr will have what it needs to start correctly.

Any suggestions ?
My workaround is this.
<script>
let clappr = null;
if (process.client) clappr = require('clappr');

export default {
	name: 'EventPlayer',
	props: {
		streaming: {
			type: Object,
			required: true
		}
	},
	data() {
		return {
			player: null
		};
	},
	mounted() {
		if (process.browser) {
			this.player = new clappr.Player({
				source: this.streaming.url,
				parent: this.$refs.player,
				width: '100%',
				height: '100%',
				events: {
					onPlay: () => this.play(),
					onStop: () => this.stop()
				}
			});
			this.player.setVolume(50);
			this.player.play();
		}
	},
	methods: {
		play() {
			if (!this.player) return;
			this.player.play();
		},
		stop() {
			if (!this.player) return;
			this.player.stop();
		}
	}
};
</script>


Return ok with failed tests

It looks like it returns OK even if I get failed test on verification. Can I make it return error on verification failure.
it "should allow casino10-qa.test.example.com" {
  source anon-hostheader_class.tcl

  on IP::client_addr return "<IP_ADDRESS>"
  on HTTP::host return "casino10-qa.test.example.com"
  on HTTP::uri return "/init"
  verify "service-gateway-qa-gateway-anon.ocptest.example.com" "service-gateway-qa-ERROR-anon.ocptest.example.com" == {HTTP::header Host}
  endstate pool ocp_dev_infranodes_443
  run test_suppliers.irule test.suppliers-irule
}

And results
 **************************************************************************
* it should allow casino10-qa.test.example.com
**************************************************************************
-> Test failure!!
-> -> Verification 'service-gateway-qa-gateway-anon.ocptest.example.com' failed - expression: {service-gateway-qa-ERROR-anon.ocptest.example.com} == {service-gateway-qa-gateway-anon.ocptest.example.com}
error     Verification 'service-gateway-qa-gateway-anon.ocptest.example.com' failed - expression: {service-gateway-qa-ERROR-anon.ocptest.example.com} == {service-gateway-qa-gateway-anon.ocptest.example.com}
(venv) [olanys@netman02 test-f5-config]$ echo $?
0

As you can see we get 0 (ok) as returncode, and so the test-suite says everything is OK.

Try calling “stats” command at the very end of your test file

okt. 2019 kl. 11:29 skrev olanystrom<EMAIL_ADDRESS>

It looks like it returns OK even if I get failed test on verification. Can I make it return error on verification failure.
it "should allow casino10-qa.test.example.com" {
source anon-hostheader_class.tcl
on IP::client_addr return "<IP_ADDRESS>"
on HTTP::host return "casino10-qa.test.suppliers.atg.se"
on HTTP::uri return "/init"
verify "service-gateway-qa-gateway-anon.ocptest.example.com" "service-gateway-qa-ERROR-anon.ocptest.example.com" == {HTTP::header Host}
endstate pool ocp_dev_infranodes_443
run test_suppliers.irule test.suppliers-irule
}
And results

it should allow casino10-qa.test.example.com

-> Test failure!!
-> -> Verification 'service-gateway-qa-gateway-anon.ocptest.example.com' failed - expression: {service-gateway-qa-ERROR-anon.ocptest.example.com} == {service-gateway-qa-gateway-anon.ocptest.example.com}
error     Verification 'service-gateway-qa-gateway-anon.ocptest.example.com' failed - expression: {service-gateway-qa-ERROR-anon.ocptest.example.com} == {service-gateway-qa-gateway-anon.ocptest.example.com}
(venv) [olanys@netman02 test-f5-config]$ echo $?
0
As you can see we get 0 (ok) as returncode, and so the test-suite says everything is OK.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

That works perfectly. I missed the stats in the examplefile.


Add catalog-info.yaml config file

This pull request adds a Backstage entity metadata file to this repository so that the component can be added to the Scaffolded Backstage App software catalog.
After this pull request is merged, the component will become available.
For more information, read an overview of the Backstage software catalog.

not relevant any more


fix(typescript): clean up configuration of the vscode dap extension

mason-nvim-dap.nvim adds it's own adapter filetype mappings to the vscode extension in nvim-dap (as of https://github.com/jay-babu/mason-nvim-dap.nvim/pull/129)
This also moves the type mappings for the pwa-node and node adapters to where they are defined in the typescript pack.
Now that the default internal type mappings are configured we can rely on the automatic loading of the .vscode/launch.json that nvim-dap does

Thanks!


Updates point people

I put a call out last week for anyone interested in being added as a point-person here but got no response. That's okay! If anyone would like to be added, just say so 👍 /cc @kierangillen

Thanks David! #mergeongreen


Use MockitoAnnotations.initMocks() for creating mocks

Thank you for great repository!!
Mockito can use mock annotation.
The mock annotation allows you to create mocks simply.

Your welcome

We can simply annotate test class with @RunWith(MockitoJUnitRunner.class) instead of using MockitoAnnotations.initMocks(this)


[key-locker] moonbean contract storage key docking development

pr: https://github.com/savour-labs/key-locker/pull/7


Added link of Computer Science Roadmap

Hi @mostafatouny,
I came across your repository awesome-theoretical-computer-science and found it to be a valuable resource for CS enthusiasts.
While browsing through the repository, I noticed that it was missing links to any structured guides such as the famous "Computer Science Roadmap". I took the initiative to submit a "Pull Request" adding it in "Related Awesome Lists" section.
Thank you for your time and effort in maintaining this valuable resource :)
Best,
Mouaaz

Thank you for reaching out, and for your kind words.
I see your roadmap.sh project is targeted for developers, and you CS roadmap is targeted for algorithm designers with emphasis on solving real-world applications.
That is different from the theme of our repo, Theoretical CS, whose aim is to understand theoretical foundations from a pure mathematical perspective. Even in linked OSSU CS you can see there is a section devoted for math.
If you are going to create a new roadmap for math, close to the context of this book, then that would be way closer to our Theoreical CS repo.
Let me know if you are going to create a new guide for math in your roadmap.sh project


Dots in filenames lead to missing .html extension

Like any other static-site generator Lume by default processes foo.md to foo/index.html. However if the filename contains a dot, e.g. foo.bar.md then Lume currently writes the HTML to foo.bar ... rather than writing to foo.bar/index.html as you would expect (case in point Jekyll and Eleventy and I'd assume most other static-site generators behave such by default).
It's worth noting that setting prettyUrls: false doesn't change the Lume behavior: it still writes the HTML to foo.bar rather than foo.bar.html, as you would expect. The relevant code appears to be the getUrl function in core/source.ts.
While changing the Lume default behavior regarding this would be a breaking change, I'd consider conforming to user expectations and common practice to be enough justification.
As a workaround you can currently specify a relative URL in the page frontmatter, such as url: ./foo.bar/.

Right that makes sense if the last extension is a template extension such as .njk but it doesn't make sense for .md as the last extension as far as I can tell. So perhaps we could introduce some distinction?

For the vary rare case that you actually want an .md file to produce a non-HTML file you can just specify the url in the YAML front matter. I think it's much more common to have a regular .md file with another dot in the filename.

Yes, my example was very exaggerated. Other more common example is if you don't want to have pretty urls for a specific file. For example, it's common the page to show in case of 404 errors is 404.html, so you can create this page with 404.html.md.
Anyway, the thing is it's easier to simply say "If the filename contains an extension, it's used as the output extension, otherwise, the html extension is used".
If you have to add "...except for some extensions like md or pug that are formats intended to output html, so the extension in the filename will be ignored", this introduces some cognitive load in how Lume works and make its behavior less predictable.
Maybe is this a bad design choice? Perhaps, I don't know. To me, a file shouldn't have a dot in the name, because this is introduces some ambiguity. You can request the url /foo/bar.png expecting a png file but it opens the html page /foo/bar.png/index.html.
Anyway, keep in mind that this is the default way to generate url by Lume. If you want to change this behavior, it's very easy: just create a url function in the /_data.js file with your own implementation. For example:
export function url (page) {
  return `./${page.src.slug}/`;
}

so you can create this page with 404.html.md

I believe file extensions should describe the content of the file. I'd consider conflating actual file extensions describing the content of the file with file extensions describing the output format of some conversion process to be an anti-pattern. I'd consider any .html.md file to be confusing.

this introduces some cognitive load in how Lume works and make its behavior less predictable

What is more predictable?
(A)

foo.md -> foo/index.html
foo.bar.md -> foo.bar
foo.bar.baz.md -> foo.baz

or (B)?

foo.md -> foo/index.html
foo.bar.md -> foo.bar/index.html
foo.bar.baz.md -> foo.bar.baz/index.html

A) is the current default behavior of Lume and B) is the default behavior of Jekyll and Eleventy. I find B) to be much more predictable.  (Granted that this is particularly true because in A3 Lume currently omits the .bar from the output filename, which is caused by the slug regex.)

To me, a file shouldn't have a dot in the name, because this is introduces some ambiguity. You can request the url /foo/bar.png expecting a png file but it opens the html page /foo/bar.png/index.html.

Correct, you cannot assume a file type just from a URL ... this however is absolutely not a problem because web browsers determine the file type via the Content-Type HTTP header. Note that even if the default Lume behavior is changed, there is nothing stopping you from still avoiding dots in your filenames, if you prefer it that way.
On the contrary the current Lume default behavior poses an inconvenience to any user that wants to e.g. mention a version number in a file name, something even the Lume website does: https://lume.land/blog/posts/lume-1.17.0-release-notes

Okay, let's mimic the Jekyll / Eleventy behavior but I don't want to introduce a breaking change now.
I'm going to put this on hold until Lume 2.0 that will introduce many breaking changes.

Fixed in the v2 branch.


🐞[bug]: Implement Toggle Feature for Showing and Hiding Answers

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
I need to implement a toggle functionality for a FAQ-style component. Each question should reveal its corresponding answer when clicked, and if clicked again, the answer should be hidden. This feature will enhance the user experience by allowing users to view answers only when needed
Expected behavior
Each question should reveal its corresponding answer when clicked, and if clicked again, the answer should be hidden. This feature will enhance the user experience by allowing users to view answers only when needed
Add ScreenShots

What browsers are you seeing the problem on?
Chrome
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24EXTD contributor
[X] I have starred the repository

@2004vivek go ahead.


Predawn breaks mousewheel behavior over tabs

When mousing over the file tabs and using the mousewheel it should scroll between them but whenever I have predawn this behavior no longer functions.
Note (1), this is standard behavior on GNU/Linux distros.
Note (2), works as expected with Flatland.

this is working for me. are you still having an issue?


Add secure storage

Previously, we didn't store the access token after authenticating with GitHub. This PR changes the post-authentication behavior so that we storethe access token in a secret storage so that users don't have to re-authenticate on every restart.
Test plan
Tested manually on Linux. After loggign in, the token is stored encrypted in ~/.eclipse/org.eclipse.equinox.security/secure_storage. The system is managing the encryption key so it should be impossible to read the token as any other user. Sending any message through the webview shows that it has access to the token.
Requires testing on windows. The secure storage should be located in %USERPROFILE%.

Opened a follow-up issue for a security audit CODY-2311 : Get security audit on our usage of Eclipse secret storage


wip: repackage linked-token inside extras.

(This also adds an initialize method to set the linked contract after construction.)
TODO

[x] Finish the rehoming, making the tests work again.
[x] fix paths to forge scripts in Makefile
[x] define errors in LinkedToken.sol
[x] Make MultiSubnet an abstract test base (like IntegrationTestBase) that we can use as a test base to move the integration test into the new package.
[x] Replica constructor to take and pass through token details.
[ ] Plug into CI.

This improves the PR greatly! Plan - merge this PR into mikers/multisubnet-test. Add the leftover  TODO to plug into CI to PR #675 and then have that PR merged to main


[Enum request] Field "Status" in table 36/38

Please implement field 120 "Status" in table 36/38/5107/5109 as enum

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


Blog - Broken Image in Blog Article

Which area(s) of Podkrepi.bg are affected?
Images, Blog
Describe the Bug
There is a broken image in the following blog article:
https://podkrepi.bg/en/blog/s-kakvo-sie-otlichava-podkriepi-bgh-kato-daritielska-platforma
To Reproduce

Open https://podkrepi.bg/blog
Select "С какво се отличава Подкрепи бг като дарителска платформа?" Blog Article
Scroll down to find the broken image.

Alternatively, you can follow this url to the blog post in question:
https://podkrepi.bg/blog/s-kakvo-sie-otlichava-podkriepi-bgh-kato-daritielska-platforma

Expected Behavior
Image is visible.
Which browser are you using? (if relevant)
Chrome: Version 123.0.6312.106 (Official Build) (64-bit), Mozilla: 124.0.2 (64-bit)

Closing as duplicate of https://github.com/podkrepi-bg/frontend/issues/1809


mono depth estimation

Thanks for your great work! Is there any plan to use StableNormal to train a mono depth estimation model?

Thanks for you suggestion.
We will release Stable-Normal before 9.01.2024!

Thanks for you suggestion. We will release Stable-Depth before 09.01.2024!

Terrific！Thank you for your job.


[fix][authentication][branch-2.10] Store the original authentication data

Motivation
Cherry-pick #19519.
Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

/pulsarbot rerun-failure-checks

@michaeljmarshall @nodece Is this a good idea?


Remove all remaining typings except chrome-app

I couldn't remove chrome-app yet. I believe there's something wrong with the npm. I started a discussion here:

http://stackoverflow.com/questions/39903684/how-to-install-chrome-app-typings-in-typescript-2
https://github.com/DefinitelyTyped/DefinitelyTyped/issues/11809

This change is

:+1:

FYI, the change to remove the remaining typings is here: https://github.com/uProxy/uproxy/compare/master...fortuna:typings?expand=1
It's blocked on https://github.com/DefinitelyTyped/DefinitelyTyped/pull/11811 being submitted and published.


Updated cmake-tutorial

Highlights

Building projects: added simplified hello-world project creation.
Toolchain file: automated selection for CMAKE_ASM_COMPILER according to the linker technology.
Output conversion: simplified output conversion with add_custom_command().
C-Test/IAR C-SPY: uses genex for populating add_test() command options depending on target's properties availability.

Looks very good @felipe-iar!


Instead of throwing an exception, return false if the layer can't be added to the map.

Looks good to me, please commit.


ACCUMULO-4733 Implement configurable security provider for crypto

Merged and squashed in 314f9f2b2f70d28a52cb699e1c65b85e4d6be7e3

@PircDef it would be nice to update the release notes w/ info about these new config.  https://github.com/apache/accumulo-website/blob/master/_posts/release/2017-09-05-accumulo-2.0.0.md
Would you be interested in doing this?


change egress hpa name to consume operator requirement

https://github.com/istio/istio/issues/18036

@irisdingbj: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

noauth_installer
349d74a426d47946337e550c00b21b3072e546ec
link
/test noauth_installer

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test noauth_installe

/test noauth_installer


Feature Request: Hide on mouseover

Hey there!
It would be really cool to be able to check a box to add the option to hide a roof on mouseover, if a token below the roof is selected.
This is useful for maps with many roofs such as a dense forest etc.

Hello! It seems you haven't read the Before Posting an issue as indicated at the top of the Repository Readme (https://github.com/theripper93/Levels/blob/v9/ISSUES.md) The Issue has been closed.
If you are reporting a bug, feel free to follow the steps here (https://theripper93.com/#/faq/issues) and reopen the issue with all the relevant information.


Additional Google charts

@nicolaskruchten
I noticed Google has different charts like Geo, Pie Chart, donut chart, and etc
seems like Pie chart is part of the core package
so when we include it:
google.load("visualization", "1", {packages:["corechart", "charteditor"]});

it doesn't show up
https://pivottable.js.org/examples/gchart.html
can those charts be added?

duplicate #457


Garadget: Invalid Config after updating HA to 0.86.1

Last working Home Assistant release (if known):
0.85.1
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io
Component/platform:
https://www.home-assistant.io/components/cover.garadget/
Description of problem:
After updating to 0.86.1 Garadget Component continually says invalid config in configuration.yaml even when it's correct.  No changes were made to the component config during upgrade.
Message Recieved:
Invalid config for [cover.garadget]: [37002XXXXXXXXXXXXXXX] is an invalid option for [cover.garadget]. Check: cover.garadget->covers->37002XXXXXXXXXXXXXXX. (See ?, line ?). Please check the docs at https://home-assistant.io/components/cover.garadget/
Config entry:
cover:

platform: garadget
covers:
37002XXXXXXXXXXXXXXX:
access_token: 084dXXXXXXXXXXXXXXXXXXXXX

Additional information:
Log Error
INFO:homeassistant.util.package:Attempting install of colorlog==4.0.2
Testing configuration at /config
Failed config
cover.garadget:
- Invalid config for [cover.garadget]: [37002XXXXXXXXXXXXXXX] is an invalid option for [cover.garadget]. Check: cover.garadget->covers->37002XXXXXXXXXXXXXXX. (See ?, line ?). Please check the docs at https://home-assistant.io/components/cover.garadget/
- platform: garadget
covers: [source /config/configuration.yaml:35]
37002XXXXXXXXXXXXXXX: [source /config/configuration.yaml:36]
access_token: 084dXXXXXXXXXXXXXXXXXXXXX
Successful config (partial)
cover.garadget:

Except the name of the cover is no longer tied to the device. I.E., I've got garage left/right and they show up as garadget and garagdet_2... And upon a homeassistant restart those cover names swapped (assume assigned names upon discovery). This is a step backward as my devices uses to be named cover.right, cover.left.

Except the name of the cover is no longer tied to the device. I.E., I've got garage left/right and they show up as garadget and garagdet_2... And upon a homeassistant restart those cover names swapped (assume assigned names upon discovery). This is a step backward as my devices uses to be named cover.right, cover.left.

You should be able to resolve this appropriately using the name: key.


getUpdates() returns error

OK. I managed to sniff out an auth_token to use. But when I call getUpdates(), it returns this error:

401 UNAUTHORIZED

Error: UNAUTHORIZED

My bad. It works.

What did you do to fix it?
On Tuesday, April 7, 2015, rpw98<EMAIL_ADDRESS>wrote:

My bad. It works.
—
Reply to this email directly or view it on GitHub
https://github.com/mgp25/Snap-API/issues/71#issuecomment-90769193.


Provide default value for Asana notes

This value cannot be nil according to Asana's API.
cc @codeclimate/review

LGTM

LGTM


400 Bad Request error in case of Android push

I am sure that it worked before, but recently I found the following log in laravel.log.
local.ERROR: exception 'Sly\NotificationPusher\Exception\PushException' with message '400 Bad Request; invalid message' in /mnt/home/apache/....../vendor/sly/notification-pusher/src/Sly/NotificationPusher/Adapter/Gcm.php:72

I tested it by creating a simple program, and I confirmed that it works for iOS, meaning that the contents of the message would be OK. But I faced the same error of '400' in case of Android.
I found the following source code in the server.
    public function push(PushInterface $push)
    {
        $client        = $this->getOpenedClient();
        $pushedDevices = new DeviceCollection();
        $tokens        = array_chunk($push->getDevices()->getTokens(), 100);

        foreach ($tokens as $tokensRange) {
            $message = $this->getServiceMessageFromOrigin($tokensRange, $push->getMessage());

            try {
                $this->response = $client->send($message);
            } catch (ServiceRuntimeException $e) {
                throw new PushException($e->getMessage());
            }

            if ((bool) $this->response->getSuccessCount()) {
                foreach ($tokensRange as $token) {
                    $pushedDevices->add($push->getDevices()->get($token));
                }
            }
        }

        return $pushedDevices;
    }

The error occurred at $this->response = $client->send($message);
(When I checked the source code in GitHub, and I found that the source code is slightly different. Should I update it??)
This is my first time to open an issue in GitHub, so I am not sure how I should do...
Anyway, any information is very helpful because I am now in stuck ....

Well. After the investigation, I found that GCM would be terminated... We need to use Firebase?
If so, how should I update it?

I updated the all to the new one and the error message has gone. But, push message does not reach devices though there is no error log.
I also tried $params['notificationData'] method described in https://github.com/Ph3nol/NotificationPusher/issues/181.
(I have not changed any in Android App. It still just supports GCM.)

Up ! I have exactly the same error when i send pushnotification for android !
And it's works before !!!
Have you find a solution @maedamin ?

GCM is not working anymore. It needs to update accordingly FCM.
Getting same 400 bad request error


Monolithic Browser Build

It would be great to have a monolithic browser build of VX. If that existed, VX examples could run in browser-based coding/publishing environments like CodePen, Blockbuilder, and bl.ocks.org.
Currently, each package has its own browser build that appends properties to the vx global. While this partially solves the puzzle, one needs to include many <script> tags to get it to work, and they need to be in topological order of the dependencies between them (if there are any). Also, these builds do not bundle smaller dependencies like classnames.
Ideally, users could pull in all the VX packages with a single <script> tag.
One subtle thing is that the browser build should ideally bundle the smaller dependencies like classnames and prop-types, while excluding the larger ones like react and d3 (and instead pull them in from browser globals).
As @pedroapfilho mentioned in a separate discussion:

it’s a lerna project, to create this monolith the only thing you should do is to create another package and put everything together in one build.

This seems like a good approach to me! The monolith index could look something like that of D3: https://github.com/d3/d3/blob/master/index.js
Related to Code Sandbox(or something similar) for all examples in gallery. #432

@vx/vx exists for these purposes. Is it not working for your use case? It was added a couple of years ago: https://github.com/hshoff/vx/pull/131

Ah amazing! Somehow I missed that. Thanks for pointing it out. It looks like a great starting point, but doesn't actually solve the issue I'd like to solve, namely the ability to load it in a <script> tag and have the global vz be populated with all the packages.
Having a look at that "UMD" build, I see it's not actually UMD https://unpkg.com/<EMAIL_ADDRESS>That build appears to support AMD and CommonJS, but does not define a browser global.
It would be amazing if that build were tweaked such that:

A global were populated with the content of all packages, and
Small dependencies were included in the bundle (e.g. classnames)
Large dependencies were excluded from the bundle (e.g. React, D3)

I'm not sure where the build settings are defined in this project, but these are the desired outcomes.
I would know how to set this up with Rollup. Need to investigate further, where the UMD build is configured.


Cloud event support

Summary
Support nodes in a workflow that either consume or produce events.
Motivation
Consuming events:

Suspending a workflow waiting for an event.
A daily job that waits for a file to appear.

Producing events:

Trigger other workflows.
Send messages to cloud events consumers, e.g. Kafka.

Proposal
In an Argo Events compatibly way.

Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

@jessesuen @whynowy  FYI

This can be fixed by generic webhook support, #2667


Prepare release 0.4.0

Note: A mistake led to the deletion and re-creation of the branch 0.4.x used in this PR. If you have an issue that may be related to this, remove your local branch 0.4.x (old) and fetch/check it out again.

Changelog

August monthly update (already in the branch main)
#125

#146

Disable dependabot dependencies

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 60.917%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1660

Relevant Lines:
2725

💛  - Coveralls

Replaced by #149 and the branch develop.


Compatibility with Kgar's tidy5e rewrite

the only issue that seems to be outstanding with compatibility is your dndbeyond black and red button doesn't show on either version of the sheet, npc/pc.  Its still in alpha but he's already issued a bunch of PR's to various modules to adjust to it.  Yours just got missed.

Closing in favour of #449


Disable FP8 in Mcore integration test on older GPUs

Description
We have experienced test failures in the Mcore integration tests on older GPUs, so this PR checks the GPU arch before enabling FP8. It also generates synthetic data so it can be run without needing to access a specific data path.
Type of change

[ ] Documentation change (change only to the documentation, either a fix or a new content)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Infra/Build change
[ ] Code refractor

Changes

Disable FP8 in Mcore integration test on older GPUs
Remove data dependency in Mcore integration test

Checklist:

[x] I have read and followed the contributing guidelines
[x] The functionality is complete
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

/te-ci pytorch L1


Problem with StreamBuilder

Good Morning
Guys I am in need of help, first I would like to thank you for creating a fantastic plugin that sqlcool helped me a lot, however I am setting up a chat screen using sqlcool + dashchat where I create my block using sqlcool I pass to my streambuilder and consequently for dashchat, the first time the data is displayed on the screen perfectly.
However I use Firebase Messanging for push I intercept the onmessage event in Firebase Messaging and insert it into my database using sqlcool, this works perfectly but the stream created does not update. I already tried to put a break point in some places and unfortunately the screen is not updated anyone would know how to tell me how to proceed to resolve this.
Just in advance I got sqlcool using the same feature for a simpler notification screen and it worked normally but I can't update it

Did you set reactive = true on your select bloc? Maybe I should set this one to true by default

Thanks for answering I actually discovered the problem at a certain point in the insert, a field that was passing was a string and the field that I was going to receive was whole, generating the problem.


Date input support

Something which lets users choose a date field's value.

This issue has been fixed.  Now the default Chrome date picker will be displayed.


Unnecessary variables in config files

Since v21.10.0, config files are used as input-parameters file, there are some parameters that do not related with computation: WantCIFexport and draw_graphs. Is it possible to move them as arguments to the gpawsolve.py command?

Yes, you are right. Firstly, there is no need for WantCIFexport variable. It can export every time after ground-state calculations. And for draw_graphs, yes it can be a new argument, therefore gg.py can call it everytime with that argument.
I think, it is a simple task.


Bug fix for :open from settings menu

Fix a bug when :opening the settings menu
The entries had not yet been converted to dictionaries
Update fixtures and add test for opening the menu in vi

This will get reworked after #1087


Allow omitting name in template literal strings

Search Terms
ignore infer template literal omit name template literal infer
Suggestion
Can we omit the inferred names in string template literal types if we don't need their values?
Use Cases
Suppose you want to use a template literal type to find strings matching a template, but don't care what's in those inferred strings. You could use a name like ${infer _}, but that's a little extra verbosity.
type OnlyKeysContainingSmoosh<T> = keyof {
    [Key in keyof T as Key extends `${infer _}Smoosh${infer _}` ? Key : never]: T[Key];
};

// "Smoosh" | "PreSmoosh" | "SmooshPost"
type FilteredKeys = OnlyKeysContainingSmoosh<{
    Smoosh: 1,
    PreSmoosh: 2,
    SmooshPost: 3,
    NoKeyForYou: 4,
}>;

Examples
The proposal here would allow omitting the  _ and  _ in the above example:
type OnlyKeysContainingSmoosh<T> = keyof {
    [Key in keyof T as Key extends `${infer}Smoosh${infer}` ? Key : never]: T[Key];
}

(Separately, I also find it spooky that it's ok to have the same name for the two inferred types, but that might just be a separate issue...)
Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

I think you can now write string in those slots and it will work kind of like an existential type parameter (e.g. ? extends string). Is that what you want?

Oh geez. My TSConf 2020 talk is going to be a little outdated... thanks! 😅

Just use a lockfile 🙂


HF generator + 1D integration

rename https://github.com/alpa-projects/alpa/pull/706

2D:
- It takes 0.5734632015228271
time (ms) | enter: 4.34 | compute: 417.48 | move logits: 82.36
- It takes 0.5725359916687012
time (ms) | enter: 4.40 | compute: 416.53 | move logits: 82.44
- It takes 0.5667464733123779
time (ms) | enter: 4.31 | compute: 412.95 | move logits: 80.81
- It takes 0.5672206878662109
time (ms) | enter: 4.32 | compute: 413.46 | move logits: 80.85
- It takes 0.566702127456665
time (ms) | enter: 4.17 | compute: 413.36 | move logits: 80.85
- It takes 0.5686218738555908
time (ms) | enter: 4.37 | compute: 413.81 | move logits: 81.55
- It takes 0.5689420700073242
time (ms) | enter: 4.46 | compute: 413.27 | move logits: 82.04
- It takes 0.5692567825317383
time (ms) | enter: 4.45 | compute: 413.72 | move logits: 81.70`

1D:
- It takes 0.39173364639282227
time (ms) | enter: 8.41 | compute: 205.71 | update: 51.64 | reshape: 53.11
- It takes 0.39749836921691895
time (ms) | enter: 8.53 | compute: 205.74 | update: 51.45 | reshape: 58.65
- It takes 0.3908195495605469
time (ms) | enter: 8.44 | compute: 205.68 | update: 51.25 | reshape: 52.39
- It takes 0.3907952308654785
time (ms) | enter: 8.35 | compute: 205.58 | update: 51.54 | reshape: 52.67
- It takes 0.3899571895599365
time (ms) | enter: 8.40 | compute: 205.53 | update: 51.22 | reshape: 52.19
- It takes 0.39054274559020996
time (ms) | enter: 8.37 | compute: 205.63 | update: 51.17 | reshape: 52.65
- It takes 0.389878511428833
time (ms) | enter: 8.27 | compute: 205.49 | update: 51.19 | reshape: 52.71
- It takes 0.3915371894836426
time (ms) | enter: 8.25 | compute: 208.23 | update: 51.17 | reshape: 51.82
- It takes 0.3890964984893799
time (ms) | enter: 8.23 | compute: 205.48 | update: 51.11 | reshape: 52.25


Call to undefined function ctype_alpha()

I read about Timber on Chris Coyier's blog and thought I would give it a shot. Is there anything additional we have to do to get this starter theme up and running? I've performed a clean install of Wordpress 4.3 and installed the Timber plugin, but when I activate this theme I get the following error:
Fatal error: Call to undefined function ctype_alpha() in /plugins/timber-library/vendor/twig/twig/lib/Twig/Lexer.php on line 378

Same here. @JMcM ever found a fix?

Closing as outdated


RFC: I've created a variant of connect() that is a tailored for using with reselect

I wasn't quite happy with the API for connect() so I went about recreating my own. A few design goals:

Simpler API. Replace the 3 functions with 1, by having access to state, props, and dispatch all at once.
Make the API reselect friendly, and use it to cache results
Be able to partially apply state/props as args of an action creator

An example of starting with no reselect selectors and building up from there:
Version 1: this works, but the onLoad arrow function will be recreated everytime props/state change:
  connectToStore(() => (state, props, dispatch) => ({
    Branding: customization.signIn[state.account.signIn.customSignIn] || MainBranding,
    loaded: state.account.signIn.loaded,
    onLoad: () => dispatch(actionCreators.getSignInConfig(props.location)),
  }))(SignIn);

Version 2: uses reselect's createSelector to solve the function issue, but gets verbose:
  connectToStore(() => createSelector(
    state => customization.signIn[state.account.signIn.customSignIn] || MainBranding,
    state => state.account.signIn.loaded,
    createSelector(
      (_, __, dispatch) => dispatch,
      (_, props) => props.location,
      (dispatch, location) => () => dispatch(actionCreators.getSignInConfig(location)),
    ),
    (Branding, loaded, onLoad) => ({ Branding, loaded, onLoad })
  ))(SignIn);

Version 3: this version users createStructuedSelector to make it less verbose:
  connectToStore(() => createStructuredSelector({
    Branding: state => customization.signIn[state.account.signIn.customSignIn] || MainBranding,
    loaded: state => state.account.signIn.loaded,
    onLoad: createSelector(
      (_, __, dispatch) => dispatch,
      (_, props) => props.location,
      (dispatch, location) => () => dispatch(actionCreators.getSignInConfig(location)),
    ),
  }))(SignIn);

Version 4: utilize dispatchable to make the actionCreator call less verbose:
  connectToStore(() => createStructuredSelector({
    Branding: state => customization.signIn[state.account.signIn.customSignIn] || MainBranding,
    loaded: state => state.account.signIn.loaded,
    onLoad: dispatchable(actionCreators.getSignInConfig, (_, props) => props.location),
  }))(SignIn);

Version 5: make createStructuredSelector implicit if a plain object is returned instead of a function
  connectToStore(() => ({
    Branding: state => customization.signIn[state.account.signIn.customSignIn] || MainBranding,
    loaded: state => state.account.signIn.loaded,
    onLoad: dispatchable(actionCreators.getSignInConfig, (_, props) => props.location),
  }))(SignIn);

Current source with some explanatory comments is here
The main exports are connectToStore(selectorFactory, options) and dispatchable(actionCreator, ...selectorsToPartiallyApply). connectToStore is the variant of react-redux's connect() while dispatchable wraps action creators in a selector that binds it to dispatch.
The signature for selectorFactory is () => (state, props, dispatch) => {newProps}. Any reselect selectors, including those created by dispatchable created inside the factory function are scoped to that component instance.
selectorFactory has a shorthand that I use 99% of the time: () => {inputSelectors}, where inputSelectors is passed to createStructuredSelector to create the selector.
I think it's coming along nicely, although I don't yet have hot reloading support (I'm not sure what that will entail) or any argument validation. Any constructive criticism would be welcome.

You've clearly put a bunch of work into this, but to be honest I'm still not really clear on what your issues are with the standard connect() function.  What specific use cases were you having trouble with?  How is this implementation more "Reselect-friendly" than the current version?
The one thing I'm grasping so far is that you want to state available when binding action creators, but as far as I've seen that's a pretty niche use case, and connect() supports that through use of mergeProps(), as you've seen.

@markerikson In addition to what you mentioned, the other issue I started running into was when I was using createSelector in mapStateToProps, mapDispatchToProps and mergeProps, because they each have different parameters, I had to organize my selectors by which method they aligned with. (Using createSelector to memoize my functions is useful for partially applying args from state/props, so that a new function isn't created every time an unrelated prop is changed.) It also looks like mergeProps doesn't have the same "advanced" option like the other two, so any selectors I want to use in there have to be singletons instead of being bound to the lifetime of the component instance.
So I started looking at the source for connect() to see if it would be possible to modify it to just supply dispatch as a 3rd param to mapStateToProps, but I found the source for connect() to be very difficult to mentally parse. There's a lot of magic in there to track all the various moving parts. I don't think I could make the changes I'd like to connect() without breaking something. There's 10 "cache" fields on the component and another 5 temp variables in the render() method mixed inside a lot of if/else blocks.
That's why I decided to create my own implementation using reselect to track all those moving parts instead.

Fair enough.
The implementation of connect() has certainly grown rather complex.  It's trying to do caching and other optimizations, allow per-instance selector memoization, etc.  I think there's some related issues that are trying to rework things, like #269 , #368 , and #373.  But, that said, it's the public API we've got, and it does cover the vast majority of use cases.  Given that you've spent some time looking into this, I'd be a bit curious if you have any suggestions for improvements to the current implementation that would maintain the public API.
Beyond that, I'm not seeing anything specifically actionable about this issue.  It's not a bug or feature request against React Redux itself, and since it's basically a one-off implementation for your own use case, I'm not quite sure what feedback you're looking for.  I'll leave the issue open for the moment just so it's a bit more visible if someone's browsing the repo issues list, but will probably close soon if there's no further discussion.

I just whipped this up and haven't tested it at all, but this could be wrapper around my connectToStore that gives a compatible API to the current connect (except for the advanced scenarios for mapStateToProps and mapDispatchToProps. I'd say people that need those, probably just use connectToStore directly.
export function connectClassic(
  mapStateToProps,
  mapDispatchToProps,
  mergeProps,
  {
    pure = true,
    withRef = false,
  }
) {
  function selectorFactory() {
    const ownPropsSelector = createShallowEqualSelector(
      (_, props) => props,
      props => props
    );

    function getStatePropsSelector() {
      if (!mapStateToProps) return () => null;

      return createSelector(
        state => state,
        ownPropsSelector,
        mapStateToProps
      );
    }

    function getDispatchPropsSelector() {
      if (!mapDispatchToProps) return (_, __, dispatch) => ({ dispatch });

      if (typeof mapDispatchToProps === 'function') {
        return createSelector(
          (_, __, dispatch) => dispatch,
          ownPropsSelector,
          mapDispatchToProps
        );
      }

      return createSelector(
        (_, __, dispatch) => dispatch,
        dispatch => bindActionCreators(mapDispatchToProps, dispatch)
      );
    }

    return createShallowEqualSelector(
      getStatePropsSelector(),
      getDispatchPropsSelector(),
      ownPropsSelector,
      mergeProps || defaultMergeProps
    );
  }

  return connectToStore(
    selectorFactory,
    {
      pure,
      withRef,
      getDisplayName: name => `Connect(${name})`,
      recomputationsProp: null,
      shouldIncludeOriginalProps: !mergeProps,
      shouldUseState: Boolean(mapStateToProps),
    }
  );
}

I still need to hoist statics, support hot reloading, and add some argument validation; but at that point I think I'd have feature parity with the existing implementation.
I'll need a moment to look at those linked issues to see how they'd impact my implementation. I agree there's nothing directly actionable here for react-redux, so the issue could be closed, but unfortunately I don't know of a more appropriate place to have this discussion. I would love to get more eyeballs on this from devs that have different requirements than my own.

Yeah, I do follow the reasoning for posting this here.  Perhaps raise the question over in Reactiflux, just to see if anyone else has feedback?

@markerikson So I wrote a version of connect() that builds a selector from its args and passes along to connectToStore(). All react-redux tests pass with 1 breaking change for when mapStateToProps / mapDispatchToProps are factory methods and a couple tweaks to some spy counts because my implementation does things slightly different behind the scenes.
Fork is here


add calendar extension?

I just ran into this where without the calendar extension, functions (such as the one I use, easter_days()) are missing? What's the possibility of having that added?

Hi there 👋
That's a good idea. To be honest I had no idea that we had to manually install them. I'll add this to the pipeline.
Here is a similar PR made for another DockerFile that could help: https://github.com/Monogramm/docker-dolibarr/issues/12.


Configuration of the sensors : the ros2 SetIp service

Hi all,
I tried running the
ros2 service call /smart_radar/set_ip_address umrr_ros2_msgs/srv/SetIp "{value_ip:<PHONE_NUMBER>, sensor_id: 100}"
and each time it results in
waiting for service to become available...
and nothing happens my radar is connected to a T1 MEDIACONVERTER that converts can to ethernet my ip is <IP_ADDRESS> "the recommended ip" and when i run
sudo tcpdump -i enp3s0
this is the output
14:48:29.694604 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
is it possible for you to walk me through how to get this command to work and what exaclty should I do
OS: Ubuntu 20.04
ros: foxy

Hey,
There could be a few potential reasons why you might be getting the waiting for service to become available... message when trying to call the ROS2 service :
Make sure the /smart_node is launched and running correctly. It seems that the service is not running: The most common reason is that the service /smart_radar/set_ip_address is not actually running.
ROS2 environment not sourced: Make sure you've sourced your ROS2 environment in the terminal where you're running the command.
Package not built or installed: Ensure that the umrr_ros2_msgs is built and installed correctly.
To troubleshoot:
Check if the service is listed when you run ros2 service list
Verify that the /smart_node providing the service is running with ros2 node list
Check for any error messages in the terminal where the smart_node is running
After, you have verified and are able to send the service, you would need to adopt your param file with the new ip address that you have allocated. Rebuild and relaunch the package with the new configs for the changes to take place.
Furthermore, I also see an issue here with the tcpdump that you have provided:
The output shows that <IP_ADDRESS> is not able to find <IP_ADDRESS> because clearly the ip address has not been set.
A tipp I would give is to have the driver running with the default ip address of sensor which is <IP_ADDRESS>. Once you are up and running than you can go ahead and make changes.
The main problem I see here is that the driver is not being properly launched which is also what you have posted in you other issue.

This issue was closed because it has been inactive for over 30 days.


outOfMemory error when running on PharmGKB genes.tsv

genes.tsv from https://www.pharmgkb.org/downloads raise a stackOverflow outOfMemory error issue when running r2rml after AutoR2RML. Even if the genes.tsv files is only a couple Mo
What have been tried by Ammar:

Loading the TSV file in LibreOffice, saving it and processing it

Solves the issue. LibreOffice might do some preprocessing solving our error. But they also modify the content of some files

Removing some columns from the mapping.trig

Note: could be related to COHD issue (outOfMemory error on 1G SQL table)

Still same issue with the new Apache Drill configuration for COHD 27G dataset
R2RML aborting generation of triples after getting error:
2020-03-25 11:15:03 ERROR TriplesMap:293 - R2RMLException.
r2rml.engine.R2RMLException: RESOURCE ERROR: External Sort encountered an error while spilling to disk


Docs for rawGrafanaDashboards field

Propose in this https://github.com/brancz/kubernetes-grafana/pull/78

@Deepak1100 I think you need to rebase on master to get the fix from #264, which should sort out the pipeline failure.

Done

lgtm :+1: thanks!


LET-IN Branch Indistinguishability

Currently, branches inside LET-IN assignments may not be reported as expected.
Consider the following:
LET X == a' = 1 : UID(u)
IN \/ X /\ A
   \/ X /\ B

Because assignments/branches are found based on UIDs, branches of the disjuncts X /\ A and X /\ B are indistinguishable, in the sense that they intersect the set {u} in the same way (assuming no assignments in A or B). Consequently, slices of the formula would contain either both disjuncts or neither.
Fundamentally, the \/-invariant - that at most one branch of a sub-term intersects any given assignment selection - does not hold under LET-IN assignment.
We need to rethink assignment strategies/branches/slicing if LET-IN operators may contain assignments.

This is not really a bug, but more of an issue with expectations. Additionally, there's no problem from a correctness perspective. The only downside is that there are now potentially fewer symbolic transitions (i.e. 2 or more of what would previously have been separate transitions now come merged), which might be slower (though unlikely by any OOM).

Well, it is true, that in this case it should not hurt. However, this is counterintuitive.

Shall we closed it as a result of #366?

Yes


wrap DSYTRD

(Moved over from https://github.com/numpy/numpy/issues/9584.)
I would like to make LAPACK's DSYTRD available to use from Python proper. Where do I have to look in the code? Where are the tests going?

LAPACK wrappers unfortunately don't have tests. Because often a Python-level function is also provided and that function is tested and hence the wrapper is also tested indirectly under the hood. But so far things are pretty consistent.
For direct addition of wrappers, here is recent #7643 as a minimal example about which files are affected. You can send a pull request based on that.
f2py syntax is mostly black magic so in case it doesn't go through, let us know and we can have a look at it too.

LAPACK wrappers unfortunately don't have tests.

There are tests for a number of LAPACK functions in linalg/tests/test_lapack.py. If these functions aren't tested via a Python-level function, then adding a new test there looks like the way to go.

There are tests for a number of LAPACK functions in linalg/tests/test_lapack.py. If these functions aren't tested via a Python-level function, then adding a new test there looks like the way to go.

Ouch, I've forgotten that file. After a quick glance, it looks like it needs some update though 😃

f2py syntax is mostly black magic

You weren't kidding. With bit of work and luck, I've managed to make myself familiar with it and coughed up https://github.com/scipy/scipy/pull/7780. I'll be glad to take comments.


Need few changes on Custom Field Page.

Need to ask following things while creating custom field,

Who's going to fill this field?

Client
Staff

Review required or Not?

Boolean

Need two new types of Custom fields,

File
Password

#624 #552


⚠ GitLab Server has degraded performance

In 2082bdf, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 6435 ms

Resolved: GitLab Server performance has improved in a527896.


Fix error log showing every time when Unity refreshes

Fix error log showing every time Unity refreshes. Added a check if the directory path to the icon exists in Assets directory otherwise use the Packages directory.

Thanks for the PR @JoseLSDev. We must consider the correct Path.DirectorySeparatorChar though, to support both Windows and macOS.

@endel committed an update to address cross platform

Awesome, thanks! 🎉


[$500] Emoji Picker - Emoji recents has been wiped, no new recents stored

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

Version Number: v1.4.24-7
Reproducible in staging?: Unknown
Reproducible in production?: Unknown
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @JmillsExpensify
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1705221634718409
Action Performed:

Open App
Go to any chat
Access comment action menu
Choose emoji option

Expected Result:
All of a user’s most frequent emojis appear
Actual Result:
Every recently-used emoji has been wiped, and only the laughing emoji appears
Workaround:
N/A
Platforms:

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

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

Screenshots/Videos

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01f55fadddcc0d33f2
Upwork Job ID:<PHONE_NUMBER>114589696
Last Price Increase: 2024-01-30

I'm checking with the tester team if anyone is experiencing the same issue on any of their test accounts.

i am not able to reproduce this

also can someone send me a invite to the slack open source channel, its almost a month i am have not got the reply :(, i am very interested in regularly contributing to the project so please send me a invite, my slack email id<EMAIL_ADDRESS>

So far no one has experienced a similar issue in the tester team. The only known account affected by this is @JmillsExpensify's atm.

Asking @stitesExpensify who was close to this implementation to see if he might have an indication as to what conditions could cause us to wipe the emoji favourites: https://expensify.slack.com/archives/C049HHMV9SM/p1705507817127169?thread_ts=1705221634.718409&cid=C049HHMV9SM

Still trying to figure this out in the slack thread, as only Mills is experiencing it.

I also wanted to mention here that not only where his emojis wiped, but all new emojis used are also not being added to his frequently used...

Issue not reproducible during KI retests. (First week)

Confirmed that Jason's favourite emojis were wiped, so that's still something we need to try and figure out. @stitesExpensify perhaps we can add some logging or something, so we have a better handle on investigating it if it ever happens again?

Bump on that question, @stitesExpensify.

Asked in thread about adding logging or something!

Responded in slack. I don't think that this is worth addressing right now given that we only have a single case, is not associated with any wave, and requires backend work

Cool, I'm going to close it for now then.


Plotly JS used by dashboard is out of date by 10 months

The dashboard is currently using Plotly JS version 2.26.0 which was released in Aug 2023. We should update it to the latest version (2.32.0 at time of creating this issue) and determine how to automate keeping it up to date.

I have an action that may be useful to you if you consumed it from a CDN: https://github.com/martincostello/update-static-assets
I use it to keep stuff like swagger-ui and font-awesome up to date: https://github.com/martincostello/website/pull/1805


PHP: add more-examples link

Preview: https://deploy-preview-3712--opentelemetry.netlify.app/docs/instrumentation/php/automatic/#next-steps

Thanks! Made a suggestion.

thanks @runtu666 , please fix the linter issues.
Run npx gulp lint-md and npm run fix:format for that

thanks @runtu666 , please fix the linter issues.
Run npx gulp lint-md and npm run fix:format for that

done @svrnm

@theletterf please re-review if your changes have been applied and you're satisfied now


Support for IliRepository20

Hi Stefan, does v0.0.41 also support IliRepository20 or just IliRepository09? Thanks in advance!

Ciao Michael, as far as I remember and wit a wuick look the the code, its supports only "IliRepository20".
https://github.com/edigonzales/ili2repo/blob/main/app/src/main/java/ch/so/agi/ili2repo/ListModels.java#L42
Stefan


Sync

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.

Files with missing lines
Patch %
Lines

src/main/java/seedu/address/MainApp.java
0.00%
3 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files with missing lines
Coverage Δ
Complexity Δ

src/main/java/seedu/address/MainApp.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)


Add possibility to show emergency warnings

Acceptance criteria

~Emergency warning will be special article in knowledgebase api~
~if the article is present, it means there is some emergency to be displayed to customer~
~if the article is not present, it means there is no warning to be displayed~
SmartFAQ will accept list of emergency banners as prop and show if any emergency is active
SmartFAQ qill also close yellow banners on froronend when SmartFAQ is opened

Zeplin: https://zpl.io/V1qE7ZJ
UPDATE: There will be no title for an emergency now.

The symbol of the exclamation mark should be higher, I think. Where is a title of emergency warning?

If it is acceptable, please move it into right column :) Thank you :) 👍

since we use exponea instead of knowladgebase API, we don't have data for a specific location or a title, should we use a generic title? or is ok for now? @mjancik

Well, I just found out, that we are going to use exponea instead of knowledgebase. Which basically makes it just a banner you can't open into an article. That also means we need to visually adjust it, because now it looks the same as an article and suggests that it can be clicked on and opened.

If it is just an alert it should use alert message component from orbit.


⚠ ClamAV has degraded performance

In 8be0992, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 193 ms

Resolved: ClamAV performance has improved in c455876.


Clean API

It fixes #62

Coverage increased (+0.1%) to 91.656% when pulling 342f6a2d764f8a6859073a20e665b7265af08bab on clean-api into c5468ec8028267c73cada777ef46d782e77ea32e on master.


Migrations do not support multiple workers

I'm building an application using dotnet core 2.1 and efcore. The application runs migrations on startup. When running in a kubernetes cluster, multiple workers often start in quick succession, especially after a deployment. Do migrations support multiple workers trying to run migrations simultaneously? Should we be preventing multiple workers from calling Migrate() on startup? We often see the following errors in this scenario.
Exception message:
Application startup exception: System.Data.SqlClient.SqlException (0x80131904): Violation of PRIMARY KEY constraint 'PK___EFMigrationsHistory'. Cannot insert duplicate key in object 'dbo.__EFMigrationsHistory'. The duplicate key value is<PHONE_NUMBER>5221_AddIndecies)
Stack trace:

   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite, String methodName)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.EntityFrameworkCore.Storage.Internal.RelationalCommand.Execute(IRelationalConnection connection, DbCommandMethod executeMethod, IReadOnlyDictionary`2 parameterValues)
   at Microsoft.EntityFrameworkCore.Storage.Internal.RelationalCommand.ExecuteNonQuery(IRelationalConnection connection, IReadOnlyDictionary`2 parameterValues)
   at Microsoft.EntityFrameworkCore.Migrations.Internal.MigrationCommandExecutor.ExecuteNonQuery(IEnumerable`1 migrationCommands, IRelationalConnection connection)
   at Microsoft.EntityFrameworkCore.Migrations.Internal.Migrator.Migrate(String targetMigration)

Steps to reproduce
I am working on putting together a project with many long running migrations that I can then run side by side which contains no business sensitive code.
Further technical details
EF Core version: 2.1.0
Database Provider: Microsoft.EntityFrameworkCore.SqlServer
Operating system: Ubuntu (microsoft/dotnet:2.1-aspnetcore-runtime via docker), RHEL host
IDE: Visual Studio 2017 15.8.3

@jblantonhiperos We generally recommend against running migrations on application startup. One of the reasons for this is that it is important that one and only one process/thread attempts to migrate the database, and that this happens before any other process/thread attempts to use the database. This is increasingly hard to coordinate when going beyond the simple single process, single database model. It also requires that the running application has permission to change the database structure, which is usually not recommended.
Instead, the database migration should be considered a deployment task. Usually this just means generating SQL scripts from the migrations and executing those against the database as part of application deployment.


Preview

I found something which is becoming an issue for my use case: Preview.
Let's say I have several multi-line text snippets copied and these are related or almost identical but not equal.
When I bring up the clipboard, I can only see the first line with :"(5 lines)" at the end.
So  If the difference between these clips are not on line 1, I have no idea which clip I need to select.
So what do I do now?  I cannot paste the clips one at a time (if I have 10, for example) then delete each incorrect one until I find the right one to paste (trial and error).  That is a problem for me.
What do you suggest?
Clipmenu is not right for me/does not fit my use case?
Or do you any ideas?

If you can find a launcher that allows differentiating multi-line clips, we could do this, but otherwise this is a limitation of dmenu.

Let me reflect.  Transforming clipmenu into something which it is not meant to be is not an objective here.

I generally know which is which by the ordering (assuming most recent) in clipmenu.
Would be nice if dmenu could do this feature of collapsing to one line in a selection, but expanding once selected.
Another very random thought would be some sort of checksum of the string and then that mapped to a colour. Though again I don't think dmenu supports coloured lines.

Just a couple of ideas; for better or for worse--as far as potential previews.

libnotify
zenity

Could it be possible to use the fzf preview to show the content of a clip? I often copy large chunks of text and it's not always obvious which is which by the first line only.
Thank you for clipmenu, it's great!

It may be possible, but fzf is community supported only, so I likely wouldn't look at it other than reviewing the changes :-)

Ok, sounds fair! I'll look at the source code. Unfortunately my scripting abilities are very limited, and I've ever only used git to publish my website to github pages…


Fix lodash isElement, isFunction and trim imports

There is no need to import all the exported symbols when lodash has the default export.
https://github.com/lodash/lodash/blob/master/trim.js#L38
https://github.com/lodash/lodash/blob/master/isElement.js#L23
https://github.com/lodash/lodash/blob/master/isFunction.js#L30

Thanks @gotik you're right.


Update copyright 2024

coverage: 97.875%. remained the same
when pulling 8219ee52176a85d15a6df4771973a119b603a3fb on copyright
into 03c45c1f53258bfe40f9b06a1ff7e6591a149eb1 on main.


Fix declaration emit for JS default re-exports that resolve to modules through synthesized default exports

Fixes #55082
I think this is too narrowly targeted—@weswigham is this on the right track?

One day we should try swapping that to a generated Alias symbol, or at least making a bespoke symbol for the export, rather than just returning the module symbol directly.

This would make things much easier to reason about. I wonder how much memory penalty it would incur.

@weswigham can you take a look at my latest commit?