FreeRTOS_DNS: Repair LLMNR and FreeRTOS_gethostbyname_a function

With these changes, the non-blocking function FreeRTOS_gethostbyname_a() will work properly again.
A DNS ID is 16 bits, and not 32-bits ( see xIdentifier = ipconfigRAND32 in FreeRTOS_DNS ).
ulDNSHandlePacket() must be called for incoming DNS replies ( in FreeRTOS_UDP_IP ).
And also LLMNR requests will be responded to correctly.
Signed-off-by: Hein Tibosch<EMAIL_ADDRESS>

Thank you for proposing these patches; we're reviewing.

Hm, I think that I should have created a new branch for the above commit?
'SocketSelect_t' has nothing to do with the earlier subject DNS.

Remove another unused field 'pxSocket' from the type 'SocketSelect_t':
I think that both 'bApiCalled' and 'pxSocket' are remains from earlier testing.
All that remains in the declaration is:
typedef struct xSOCKET_SET { 	EventGroupHandle_t xSelectGroup; } SocketSelect_t;

This test in ulDNSHandlePacket() :
if( pxNetworkBuffer->xDataLength > sizeof( UDPPacket_t ) )
is misplaced.
In the function "prvProcessIPPacket()", it was proven that the received UDP-packet has 3 headers and that it has a valid UDP payload.
The length of the 3 headers ( Ethernet, IP, and UDP ) were already subtracted:
pxNetworkBuffer->xDataLength -= sizeof( UDPPacket_t );
The only test that should remain here is this one:
	if ( xPlayloadBufferLength < sizeof( DNSMessage_t ) ) 	{ 		return pdFAIL; 	}

At this point, there are only 2 changes left.
I'll describe them here in C comments:
Change-1:
/* DNS identifiers are 16-bit. */
xIdentifier = ( TickType_t )( ipconfigRAND32( ) & 0xffff );
// As for the lookup call-back routine, a matching will take place
// between the identifier received and the identifiers stored.
// An "identifier received" is always 16-bits.
// As long as 32-bit identifiers are issued here, a match is never found
// and as a result of that, "FreeRTOS_gethostbyname_a()" can not succeed.
Change-2:
// The following test is misplaced: comparing a payload buffer
// length with the size of a UDS packet of 42 bytes long:
// This test will never pass, unless it's an extremely long
// DNS/LLMNR packet:
if( pxNetworkBuffer->xDataLength > sizeof( UDPPacket_t ) )
// "sizeof( UDPPacket_t )" has already been subtracted
// from xDataLength
{
prvParseDNSReply( pucUDPPayloadBuffer,
xPlayloadBufferLength,
( uint32_t )pxDNSMessageHeader->usIdentifier );
}
I'm sorry, but at this moment, I can not find the time to write tests for these 2 changes.
Yes they are essential to get "FreeRTOS_gethostbyname_a()" working again.
Thanks, Hein

Closing this pull-request for now.
I will open a new clean pull request for "Repairing the DNS asynchronous lookup"


"insufficient funds for fee bumping anchor channel message" doesn't include amounts

Background
When opening an anchor channel using all or nearly all of your wallet balance, you get an error message from lncli:
$ lncli openchannel --node_key 03ff1efa980a8b608233a2656ff77f9b5f45df0a0f9a58c7bdfbf6411d4e6fec91 --local_amt 29807
[lncli] rpc error: code = Unknown desc = reserved wallet balance invalidated: transaction would leave insufficient funds for fee bumping anchor channel closings (see debug log for details)

This error message doesn't indicate how much additional balance is required to open the channel. When checking the debug log for detail, there's still no info on the additional balance:
2022-05-03 17:35:05.565 [DBG] LNWL: Estimated fee rate of 250 sat/kw sat/kw is too low, using fee floor of 253 sat/kw sat/kw instead
2022-05-03 17:35:05.565 [DBG] LNWL: Returning 253 sat/kw for conf target of 6
2022-05-03 17:35:05.565 [DBG] RPCS: [openchannel]: using fee of 253 sat/kw for funding tx
2022-05-03 17:35:05.565 [INF] FNDG: Initiating fundingRequest(local_amt=0.00029807 BTC (subtract_fees=false), push_amt=0 mSAT, chain_hash=00000008819873e925422c1ff0f99f7cc9bbb232af63a077a480a3633bee1ef6, peer=03ff1efa980a8b608233a2656ff77f9b5f45df0a0f9a58c7bdfbf6411d4e6fec91, min_confs=1)
2022-05-03 17:35:05.565 [DBG] LNWL: Estimated fee rate of 250 sat/kw sat/kw is too low, using fee floor of 253 sat/kw sat/kw instead
2022-05-03 17:35:05.565 [DBG] LNWL: Returning 253 sat/kw for conf target of 3
2022-05-03 17:35:05.565 [INF] CHFD: Performing funding tx coin selection using 253 sat/kw as fee rate
2022-05-03 17:35:05.565 [WRN] CHFD: Unable to find funding output for shim intent: unable to create witness script, no funding keys
2022-05-03 17:35:05.566 [DBG] LNWL: Reserved value=0.0001 BTC above final walletbalance=0 BTC with 1 anchor channels open
2022-05-03 17:35:05.566 [ERR] RPCS: unable to open channel to NodeKey(03ff1efa980a8b608233a2656ff77f9b5f45df0a0f9a58c7bdfbf6411d4e6fec91): reserved wallet balance invalidated: transaction would leave insufficient funds for fee bumping anchor channel closings (see debug log for details)
2022-05-03 17:35:05.566 [ERR] RPCS: [/lnrpc.Lightning/OpenChannel]: reserved wallet balance invalidated: transaction would leave insufficient funds for fee bumping anchor channel closings (see debug log for details)

Your environment

lnd 0.14.2

Expected behaviour
The amount of the shortage of wallet funds should be included in the error message and/or logs to help the user make a successful channel opening without having to "guess" the max channel size.

Just for reference, you'd want to keep 100k utxo available for anchors to avoid these errors

The amount required is 10K per channel 100K max. So if you have more than 10 channels, keep 100K UTXO separate from the funds locked for opening channels.


Make ret values RawObj that are guaranteed to be

What
Make return values RawObj that are guaranteed to be that type.
Why
It simplifies the SDK since the SDK will be assuming the values are RawObj's anyway, and this allows it to do so without unchecked/unsafe blocks of code.
Note that it is important that host fn inputs are only RawVals because the host should not make any assumptions about what the guest has provided as arguments.
Known limitations
N/A

The corresponding update to the SDK is this: https://github.com/stellar/rs-stellar-contract-sdk/pull/76


Create Multi-year Investments test data

Create utils/scripts/create-multiyear-data.jl to create this data.
This will be used by the next PR to implement multiyear input.
The data is created by copying the Tiny data, duplicating rows, and changing
the year of the duplicates.
The following files have been created:
Remarks:

Flows are not automatically active in 2050 if the assets are active, so the duplication of rows happened for both assets-data.csv and flows-data.csv.
The year is informed in both *-profiles.csv and profiles-rep-periods. The profile_name and year should be used to determine the used profile.

Pull request details
Describe the changes made in this pull request

List of related issues or pull requests
Closes #758
Collaboration confirmation
As a contributor I confirm

[x] I read and followed the instructions in README.dev.md
[x] The documentation is up to date with the changes introduced in this Pull Request (or NA)
[x] Tests are passing
[x] Lint is passing

@abelsiqueira Thanks for the PR. I have no comments, but I would wait until @gnawin review it to marge the changes since he has the broader picture of the multi-year development.

@abelsiqueira Thanks a lot. It looks good to me. I just got a bit confused by the use of  active regarding your remark

Flows are not automatically active in 2050 if the assets are active, so the duplication of rows happened for both assets-data.csv and flows-data.csv.
Because I see the last row of the two files have been set to false in active. Could you clarify a bit?

What I meant is that it is not sufficient to have assets exists in 2050. The flows must be defined in 2050 as well. And consequently, being active depends on that value.
In the future, it could make sense to automatically create the flows and mark them as active if they exist in a previous year, or based on lifetime, and/or assets being active.
I did not add any of that, so for now you have to make everything explicit.


Prim's Algorithm in C++

Information about Algorithm

Finds the minimum spanning tree of a graph by a greedy algorithm.
It takes two sets of vertices, those in the MST and those not in the MST.
It repeatedly finds the edges connecting the two sets of vertices and adds the one with the lowest weight to the MST.
Have you read the Contributing.md and Code of conduct

[x] Yes
[ ] No

Other context
This is my first ever open-source contribution and is also done as part of a project for a college course.

Hi I would like to contribute to this issue if anyone else is not working on it

Hi I'm interested to solve this type of issue. Can you assign me this issue ? I would like to contribute to this issue.


Controller Layouts - unable to assertViewHas()

It is currently not possible to assertViewHas() if using controller based layouts.
Here is a basic test example
// test
public function testIndex()
{
  $this->mock->shouldReceive('all')->once()->andReturn('foo');
  $response = $this->route('GET', 'users.index');

  $this->assertTrue($response->isOK());

  // this line fails if using controller based layouts
  $this->assertViewHas('foo');
}

This controller method that fails on assertViewHas() because we are using $this->layout->content
// controller method that does not work
public function index()
{
  $users = $this->users->all();

  $this->layout->content = View::make('users.index', compact('users'));
}

This controller method does not fail
// controller method that works
public function index()
{
  $users = $this->users->all();

  return View::make('users.index', compact('users'));
}

I'm using Laravel 4.2. It seems that assertViewHas does not work in layout->conent


As a user I want to list all task with the same label

so that I can view all related tasks

Done in find command


Add types for cds.utils.colors

Requires https://github.com/cap-js/docs/pull/1285 for the @see link to work.
See cap/cds/pull/4656

Since which sap/cds version is this available?  Should document this.
@daogrady do we have a @since tag or so?

Since which sap/cds version is this available?

Was merged just a week ago, so >= 8.3.0.

should document this

Yep :) https://github.com/cap-js/docs/pull/1285

seeing that the colour strings seem to be used as both primary and background-colour, would pulling them out into a separate type be desirable?

Two reasons why I kept it separate:

There are some small exceptions, e.g. GRAY is available as a foreground color, but not as a background color
While the key names are the same the constant values of RED ('\x1b[31m') and bg.RED ('\x1b[41m') are different
→ sharing a type/dict seems to imply a reuse that's semantically not there

There are some small exceptions, e.g. GRAY is available as a foreground color, but not as a background color

I see, then maybe
type Colors = {
  BLUE: string,
  GREEN: string,
  ...
}

type colors: Colors & {
  ITALIC: string,
  ...
  GRAY: string,  // exclusive to foreground colors
  bg: Colors & {
      DEFAULT: string
  }
}

?

I just found out I could type the values more explicitly using <constant escape sequence> | '', as those are the only values  they can take on. This is a tighter typing (which is good!) but it doesn't allow us to reuse the values from a type/dict.


Operator for list concatenation?

Given that :: is used for labeled arguments, anybody know which operator is to be used instead of the double colons here?

Hey @dchambers, the list concatenation is similar to the JS's spread operator.
el :: rest in ocaml is [el, ...rest] in reason.

Love it! Thanks so much! :smile:


Enhancement: Ability to copy token description

Hi,
Device Manufacturer: Samsung
Device Model: S10
Device OS: Android
Device OS Version: 11
Application Version: apk: v0.98.30
Wallet: v1.1.5
Hi,
Is it possible to add functionality to copy text from the token description?
For example it's not possible to copy the url in this token description:

Thanks
Jazmin

good idea, add functionality to the token. maybe even a clickable link!

Fixed in v1.1.6.. now able to copy description


Get Transferable in Rust

Hi (again),
Following my work, I start a worker and I send a message to it (to an image decoder).
After the decoding I wanna to get back on the Rust object so I plan to use the onmessage method.
I cannot arrive to get back the data ArrayBuffer as I need to send it with postMessage including a transferable object.
Do you know if we can get back the ArrayBuffer in Rust ?
Thanks,
Marc-Antoine

Thanks for the report! Until SharedArrayBuffer is stable the only way to transfer data between workers on the web is to do full copies which means you can't send a Rust struct from one thread to another with workers. For that you may want to use JSON and/or the serde support!

@alexcrichton Actually, transferrable objects don't have anything to do with SharedArrayBuffer.
They're a special kind of object which can be sent between Workers without a copy.
Right now that means ArrayBuffer, MessagePort, ImageBitmap, and OffscreenCanvas (but more types might become transferrable in the future).

@MarcAntoine-Arnaud You would use the post_message_with_transfer method, like this:
let worker = ...;
let array_buffer = ...;

worker.post_message_with_transfer(&array_buffer, &Array::of1(&array_buffer)).unwrap_throw();

Then to receive it back from the Worker, you would do something like this:
let cb = Closure::wrap(Box::new(|event| {
    let array_buffer: ArrayBuffer = event.data().dyn_into().unwrap_throw();

    // Use ArrayBuffer...
}) as Box<FnMut(MessageEvent)>);

worker.set_onmessage(Some(cb.as_ref().unchecked_ref()));

I have tested it and it works like that:
// Worker in JS
postMessage(output.buffer, [output.buffer])

then I can get back the ArrayBuffer in Rust as @Pauan mentioned.
My initial wish is to send also informations about decoded frame, so I wanna to send:
// Worker in JS
postMessage({
  'frame_index': 666,
  'width': 1920,
  'height': 1080,
  'data': output.buffer
}, [output.buffer])

When I receive this message in javascript it works, I can access to all informations.
For Rust I have only access to a JsValue like:
JsValue(Object({"frame_index":666,"width":1920,"height":1088,"data":{}}))
The data seems an empty array...
Do you know how to get back information for that ?
Or if it's not supported right now with wasm-bindgen ?
Marc-Antoine

@Pauan what if I want to post a JsValue object as a message and then specifiy which parts of the object are transferable ?

@UsernameN0tAvailable It works exactly the same as in JS: you specify the Transferable objects in the Array.

@Pauan since the first argument is type JsValue, how would you go about getting a field value / reference out of it to insert into the transferable array?

@UsernameN0tAvailable You would use Reflect::get to lookup a property in the object, it works the same as object[key]. There's a lot of other useful methods in Reflect as well.
Or, you can create some bindings which specify what keys the object has... and then use unchecked_into to convert the JsValue into your custom type:
#[wasm_bindgen]
extern "C" {
    type Foo;

    #[wasm_bindgen(structural, method, getter)]
    fn some_property(this: &Foo) -> ArrayBuffer;
}

...

let array_buffer = object.unchecked_into::<Foo>().some_property();

This is faster than using Reflect::get, since it's equivalent to doing object.some_property.

@Pauan I apologize for my line of questioning, but is it even possible to serialize "into_serde" a rust vec to a TypedArray or Reflect:set it without it being transmutated into a map?

@UsernameN0tAvailable I don't understand your question, none of this has anything to do with serde, it's all just a regular JsValue.
If you want to convert a Vec into a JS Array, just use collect:
vec![...].into_iter().collect::<Array>()

You might need to convert the values into JsValue:
vec![...].into_iter().map(JsValue::from).collect::<Array>()

If you want to convert it into a TypedArray, you can use the From impl:
Uint8Array::from(&foo)

@Pauan when accessing MessageEvent.data() the TypedArray data gets mapped, so I suspect the transfer is not working.

@UsernameN0tAvailable Note that ArrayBuffer is transferrable, but TypedArrays (like Uint8Array) are not transferrable, so if you have a TypedArray then you must use the buffer method in order to get an ArrayBuffer.


Animate transitions

Is your feature request related to a problem?
When changing workspaces, the active workspace width does not animate when transitioning to a different workspace. It just abruptly changes sizes.
Describe the solution you'd like
It would be awesome to be able to add animations and transitions
Describe alternatives you've considered
It works just fine without animations, but it feels not polished

Is this just for the default "dots" appearance? Idk if a smooth size transition would work for say when the workspaces are defined using either icons or numbered workspaces. I see that this could look pretty slick for the standard dots + wider dot as the default workspace indicator.
Ie top three wouldn't work with the icon changing sizes as you transition, but the bottom one would. Doesn't necessarily rule out something like a "fade-in" for the background highlighting though I guess :man_shrugging:.
Tbh that honestly would look cool :sunglasses:

@tduarte  it's pretty easy actually. Checkout these dots https://github.com/l6174/hyprdots and look for the  animations section of hyprland. Since HyprPanel has names for notification, overview, etc, he set animations based on their names. So far, when click on, let's say, the notfication icon, the notification center does slide to the left and vice versa for the overview panel, but unfortunately, there is no animation when u close them. But I just the rechecked his animation video and he didn't have  my problem, so likely u wont either.
And regarding your workspace issue from the last pic from @smathles  i did get animation without any problems

@smathles My setup and the issue I'm having is with the example from the last screenshot you sent (where the active workspace is wider than the others).
I checked the @zielOS hyprdots Github repository and the gif in the preview also does not animate when changing workspaces. I don't think the animation section of the Hyprland config would change anything given that I'm talking about the top bar.

@tduarte I was able to achieve this kind of workspace animation by manually adding transitions to the CSS files in agsv1. However, this no longer works after the agsv2 migration.
https://github.com/user-attachments/assets/c1b0a1ea-256d-467d-bd81-471ab3597b9b


time based geoqueries

I've got a dataset with lat lon and time, and I'd like to be able to do geoqueries within a window of time.
What do you suggest would be a good approach to take here?
Ideally I could have a query system something like (lat,lon,radius,tstart,tend)
current idea is for a fixed window (say last 30min) manually removing keys with a t value > 30min but this won't work for different times

This is not possible because the underlying Firebase SDK only allows for querying against a single thing at a time. In the case of GeoFire, we need to query against the geohash. There are some pretty unpleasant ways to achieve this, but you have to manage it yourself and it is not very efficient. See https://github.com/firebase/geofire-java/issues/37 and https://github.com/firebase/geofire-js/issues/59#issuecomment-70350560 for some more details.


Don't trigger CrisisMonitor for nameblacklists in secret rooms

This makes it consistent with the behavior or /blacklist.

Is this necessary? Getting blacklisted by a trusted user for any reason is worrisome.

There's a reason I implemented it this way at first...

Dunno, that's a policy decision, I just made it consistent with the other punishment commands.
But isn't it the case that secret rooms can mostly blacklist and ban whoever they want?

Yes, mostly, but presumably with some semblance of the idea that they actually did something wrong.


update kernel-and-k8s-audit/daemonset-least-privilege.yaml with new images

Motivation
As described in the docker documentation we should update daemonset-least-privilege.yaml to reflect the usage of new images introduced recently.
Feature

Replace falcosecurity/probeloader:latest with falcosecurity/falco-driver-loader:latest and update settings as described  in the docker documentation
Replace falcosecurity/falco:0.21.0-slim with falcosecurity/falco-no-driver:latest and update settings as described  in the docker documentation
Remove comments that are not needed any more (ie. this)
Make sure volumeMounts and other options reflect the new docker image usage

Additional context
I believe we need a solution to attach the devices set. See the note about $(ls /dev/falco* | xargs -I {} echo --device in the point 2. of the Docker Least privileged documentation.
/cc @maxgio92

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale


fix: health check for neosnippet source

:checkhealth kept failing for me when using Neosnippet.vim as my snippet source. Looking at the code it turns out that the check expects a different result from string.match than what is actually returned. This PR updates the check to match the other health checks for snippets 🙂 Making the health check work properly also stopped the completion from printing several error messages related to snippets.

Thanks for the fix!


What node path of the BIP32 is ElectronCash using?

I can't seem to find the deviation the wallet uses for receiving address and change.

Create a new wallet and change the options.  It gives the opportunity to change the derivation address in there somewhere.

I'm going to assume you've done this, since it shouldn't be that hard.

My mistake sorry, the derivation paths are shown in the hardware wallet creation.  If they are shown elsewhere they are hard to find.


PSR-2 code style without errors

Fix the remaining PSR-2 code style errors.
I also added PHP Code Sniffer to Travis. The build for PHP 5.6 will fail if errors are detected (warnings are ignored).

Or we can use styleci.io :) to check if all pull request are PSR-2


Auto corrected by following Lint Ruby Style/ParallelAssignment

Auto corrected by following Lint Ruby Style/ParallelAssignment
Click here to configure it on awesomecode.io

Coverage remained the same at 96.207% when pulling 42fd6de497831bdbbe131e0d60ec6d6e1f3cf3f2 on awesomecode-lint-ruby-style-parallelassignment-47733 into bb9f383db2c3a34c61abe59643f7213772eaa77b on master.

Coverage remained the same at 96.207% when pulling 42fd6de497831bdbbe131e0d60ec6d6e1f3cf3f2 on awesomecode-lint-ruby-style-parallelassignment-47733 into bb9f383db2c3a34c61abe59643f7213772eaa77b on master.


Updating ror for require_flatten error and changes to resnet.py as per recent issues

fixes #222 and #221

@ahundt can you please look into this now? Because the error still exists.

@ahundt Please make this change as it still persists or close the issue.

@anand-sonawane can you fix the conflict?

Hello, I'm a bot! I can make mistakes, notify gabrieldemarmiesse if I made one.
I see that you modified the following file:

keras_contrib/applications/wide_resnet.py

The owner of those file is @titu1994
@titu1994 could you please take a look at it whenever
you have the time and add a review? Thank you in advance for the help.

I'll be closing this PR as it has conflicts and they were not resolved for quite some time. It should probably be easier to open a new one at this point.


Refactor Update check

What changes are proposed in this pull request?
Refactor update check to be able to be shared by master and clients.
Why are the changes needed?
Enable user to add update check for client SDKs.
Does this PR introduce any user facing changes?
NA

Will wait for 2.9 cut

@Xenorith @beinan PTAL, thanks

Error: 7.255 [ERROR] Errors:
Error: 7.256 [ERROR] alluxio.server.ft.journal.JournalBackupIntegrationTest.backupRestoreZk
Error: 7.258 [ERROR]   Run 1: JournalBackupIntegrationTest.backupRestoreZk:119->backupRestoreTest:610 » FailedPrecondition
Error: 7.258 [ERROR]   Run 2: JournalBackupIntegrationTest.backupRestoreZk:119->backupRestoreTest:610 » FailedPrecondition

alluxio-bot, merge this please


Can't open vocalremover.py

Installation seemed to go fine, but when I get to opening;
This is the error I get. I have no idea what this means as I don't code or anything remotely like that.
C:\Users\The Mothership\Documents\UVR-V4GUI>python VocalRemover.py
Traceback (most recent call last):
File "VocalRemover.py", line 25, in
import inference_v2
File "C:\Users\The Mothership\Documents\UVR-V4GUI\inference_v2.py", line 4, in
import cv2
ModuleNotFoundError: No module named 'cv2'

Installation seemed to go fine, but when I get to opening; This is the error I get. I have no idea what this means as I don't code or anything remotely like that.
C:\Users\The Mothership\Documents\UVR-V4GUI>python VocalRemover.py Traceback (most recent call last): File "VocalRemover.py", line 25, in import inference_v2 File "C:\Users\The Mothership\Documents\UVR-V4GUI\inference_v2.py", line 4, in import cv2 ModuleNotFoundError: No module named 'cv2'

Try these commands...
pip install opencv-python.
pip install numpy

now this what I get;
C:\Users\The Mothership\Documents\UVR-V4GUI>python VocalRemover.py
Traceback (most recent call last):
File "VocalRemover.py", line 25, in
import inference_v2
File "C:\Users\The Mothership\Documents\UVR-V4GUI\inference_v2.py", line 5, in
import librosa
ModuleNotFoundError: No module named 'librosa'

Installation seemed to go fine, but when I get to opening; This is the error I get. I have no idea what this means as I don't code or anything remotely like that.
C:\Users\The Mothership\Documents\UVR-V4GUI>python VocalRemover.py Traceback (most recent call last): File "VocalRemover.py", line 25, in import inference_v2 File "C:\Users\The Mothership\Documents\UVR-V4GUI\inference_v2.py", line 4, in import cv2 ModuleNotFoundError: No module named 'cv2'

Try these commands... pip install opencv-python.
pip install numpy
Then try to run the application.

Installation seemed to go fine, but when I get to opening; This is the error I get. I have no idea what this means as I don't code or anything remotely like that.
C:\Users\The Mothership\Documents\UVR-V4GUI>python VocalRemover.py Traceback (most recent call last): File "VocalRemover.py", line 25, in import inference_v2 File "C:\Users\The Mothership\Documents\UVR-V4GUI\inference_v2.py", line 4, in import cv2 ModuleNotFoundError: No module named 'cv2'

Try these commands... pip install opencv-python.
pip install numpy
Then try to run the application.

now this is what i get
C:\Users\The Mothership\Documents\UVR-V4GUI>python VocalRemover.py
Traceback (most recent call last):
File "VocalRemover.py", line 25, in
import inference_v2
File "C:\Users\The Mothership\Documents\UVR-V4GUI\inference_v2.py", line 5, in
import librosa
ModuleNotFoundError: No module named 'librosa'

Installation seemed to go fine, but when I get to opening; This is the error I get. I have no idea what this means as I don't code or anything remotely like that.
C:\Users\The Mothership\Documents\UVR-V4GUI>python VocalRemover.py Traceback (most recent call last): File "VocalRemover.py", line 25, in import inference_v2 File "C:\Users\The Mothership\Documents\UVR-V4GUI\inference_v2.py", line 4, in import cv2 ModuleNotFoundError: No module named 'cv2'

Try these commands... pip install opencv-python.
pip install numpy
Then try to run the application.

Installation seemed to go fine, but when I get to opening; This is the error I get. I have no idea what this means as I don't code or anything remotely like that.
C:\Users\The Mothership\Documents\UVR-V4GUI>python VocalRemover.py Traceback (most recent call last): File "VocalRemover.py", line 25, in import inference_v2 File "C:\Users\The Mothership\Documents\UVR-V4GUI\inference_v2.py", line 4, in import cv2 ModuleNotFoundError: No module named 'cv2'

Try these commands... pip install opencv-python.
pip install numpy
Then try to run the application.

now this is what i get
C:\Users\The Mothership\Documents\UVR-V4GUI>python VocalRemover.py
Traceback (most recent call last):
File "VocalRemover.py", line 25, in
import inference_v2
File "C:\Users\The Mothership\Documents\UVR-V4GUI\inference_v2.py", line 5, in
import librosa
ModuleNotFoundError: No module named 'librosa'

Install librosa with this statement:
pip install librosa
Extra: Whenever a module not found error is raised, try to install it with this command:
pip install  module-name

Installation seemed to go fine, but when I get to opening; This is the error I get. I have no idea what this means as I don't code or anything remotely like that.
C:\Users\The Mothership\Documents\UVR-V4GUI>python VocalRemover.py Traceback (most recent call last): File "VocalRemover.py", line 25, in import inference_v2 File "C:\Users\The Mothership\Documents\UVR-V4GUI\inference_v2.py", line 4, in import cv2 ModuleNotFoundError: No module named 'cv2'

Try these commands... pip install opencv-python.
pip install numpy
Then try to run the application.

Installation seemed to go fine, but when I get to opening; This is the error I get. I have no idea what this means as I don't code or anything remotely like that.
C:\Users\The Mothership\Documents\UVR-V4GUI>python VocalRemover.py Traceback (most recent call last): File "VocalRemover.py", line 25, in import inference_v2 File "C:\Users\The Mothership\Documents\UVR-V4GUI\inference_v2.py", line 4, in import cv2 ModuleNotFoundError: No module named 'cv2'

Try these commands... pip install opencv-python.
pip install numpy
Then try to run the application.

now this is what i get
C:\Users\The Mothership\Documents\UVR-V4GUI>python VocalRemover.py
Traceback (most recent call last):
File "VocalRemover.py", line 25, in
import inference_v2
File "C:\Users\The Mothership\Documents\UVR-V4GUI\inference_v2.py", line 5, in
import librosa
ModuleNotFoundError: No module named 'librosa'

Install librosa with this statement: pip install librosa
Extra: Whenever a module not found error is raised, try to install it with this command: pip install module-name

I think that did it, thanks!

I tried to open it, but it closes on me.

I tried to open it, but it closes on me.

Please update to version 5.2.0 using the Windows installer provided on the main page.


Write a Python program to convert fahrenheit to kelvin

Description
Write a Python program to convert fahrenheit to kelvin
(1°F − 32) × 5/9 + 273.15 = 255.928K
Input  : 1
Output : 255.928

Contributed by - @KyleMcIndoe

How to contribute

Save the solution in convert-fahrenheit-to-kelvin.py file
Add convert-fahrenheit-to-kelvin.py file in program/convert-fahrenheit-to-kelvin folder

Can I work on this issue?

Hey @ammarfitwalla
You can comment !assign on any good first issue you want to contribute to, to be auto-assigned
!assign

!assign


Numba gives wrong results with global variables

Accessing global variables with Numba is not working correctly. Even worse, there is no warning that things might go wrong. Example:
""" Example for wrong handling of global variables in numba 0.9 on Ubuntu 12.04, 32 bits."""

Speed = 10.0

def setSpeed():
    global Speed
    Speed = 20.0

def residual():
    return Speed

from numba import double, jit
fast_residual = jit(double())(residual)

if __name__ == '__main__':
    setSpeed()
    print residual()
    print fast_residual()

"""
Output:
20.0
10.0

Expected output:
20.0
20.0
"""

This should be fixed, or at least there must be a warning if the keyword "global" appears anywhere in the module.

Cannot replicate in 0.45. Closing.


unwrap panic from shared state

stopping shared states being used across an axum application
pub trait FromData: Sized + Clone + Send + Sync + 'static {
    /// Gets the value
    fn get(data: &crate::data::Extensions) -> Self {
        data.get::<Self>().unwrap().clone()
    }
}

from this shared state
#[derive(Clone)]
pub struct AppState {
    config: AppConfig,
    redis_manager: RedisManager,
    orchestrator_manager: Arc<RwLock<dyn OrchestratorManager>>,
    service_register: Arc<RwLock<ServiceRegister>>,
}

passed into the worker
    let py_worker_task = WorkerBuilder::new("py-worker")
        .layer(TraceLayer::new())
        .layer(LogLayer::new("py-worker"))
        .with_storage(py_queue.clone())
        .data(state.clone())
        .build_fn(publish_request_await_py_response);

defined as follows
pub async fn publish_request_await_py_response(
    job: PyWorkerJob,
    state: Data<AppState>,
    _worker_id: WorkerId,
) -> Result<(), JobError> {

This looks really weird and unexpected. Could you try a few things:

Have the data layer before the with_storage call.
Ensure that state is of type AppState

I will try and replicate the issue.
Related to #393

yes confirmed with point no 2. AppState was wrapped in an Arc and the panic made it hard to debug. Perhaps a #[debug_worker] macro like in Axum could help with these details?

Sure, this will be fixed by #393


[Bug]: IngestionPipeline Cache does not work with num_workers > 1

Bug Description
When num_workers > 1, the llama_cache file is empty. When num_workers=1, the IngestionPipeline can cache normally
Version
0.11.17
Steps to Reproduce
if __name__ == '__main__':
    pipeline = IngestionPipeline(
        transformations=[
            FooNodeParser(),
            OpenAIEmbedding(
                model="text-embedding-3-small"
            )
        ],
        vector_store=vector_store
    )
    documents = SimpleDirectoryReader(path).load_data(
            show_progress=True, num_workers=4)
    nodes = pipeline.run(documents=documents, num_workers=4)
    pipeline.persist("cache")

Relevant Logs/Tracbacks
No response

I need to remove this parameter, it doesn't work half the time, and tbh is usually broken
set it to 1. Or use async with pipeline.arun() to achieve concurrency. Or multi-thread it outside of the class in your code

When num_workers > 1, the llama_cache file is empty.

I also wasted tons of time trying to understand why caching was not working, and the main reason was this.

If I remember correctly, setting num_workers > 1 caused my program to spawn multiple instances of the main process, despite using the main-guard: if __name__ == '__main__':.


Add comment about support for cursor metrics

What does this PR do?
Adds comments on cursor metrics to note support depending on mongo version
Motivation
In Mongo v2.4 and before, the format for the cursors metrics were cursors.totalOpen and cursors.timedOut. This was changed in v 2.6
Review checklist

[ ] PR has a meaningful title or PR has the no-changelog label attached
[ ] Feature or bugfix has tests
[ ] Git history is clean
[ ] If PR impacts documentation, docs team has been notified or an issue has been opened on the documentation repo

Additional Notes
Anything else we should know when reviewing?

@gzussa I think we should update the metadata.csv file in order to specify in the metrics description directly the minimum/maximum mongo version supported for their collection.

@dixonscottr Did you update the metadata file like mentioned by @l0k0ms ?


Add application.get example using the application slug

Change-type: patch
Signed-off-by: Thodoris Greasidis<EMAIL_ADDRESS>
Contributor checklist

[ ] Includes tests
[ ] Includes typings
[ ] Includes updated documentation
[ ] Includes updated build output

@balena-ci I self-certify!


ntr PMID:19942659 (galactosylation)

decreased protein galactosylation during vegetative growth
normal  protein galactosylation during vegetative growth
decreased UDP-glucose 4-epimerase activity
normal UDP-glucose 4-epimerase activity
decreased UDP-galactose level
increased cytosolic UDP-galactose level

decreased protein galactosylation during vegetative growth FYPO:0007287
normal protein galactosylation during vegetative growth FYPO:0007288
abnormal UDP-glucose 4-epimerase activity FYPO:0007289
decreased UDP-glucose 4-epimerase activity FYPO:0007290
decreased cellular UDP-galactose level FYPO:0007291
increased cytosolic UDP-galactose level FYPO:0007292
edit file: 22a612b4ff712f692916cf9c9eed8cfe54911461
release: 66f82ff26aaf76c5f756b258b6b939b9af2197e2


Fix connection issue to VSCode instance

fix(Launcher): fix Launcher.connect method
This patch fixes Launcher.connect  so that it works with existing Visual Studio code instance.
The is an issue when connecting to the existing Visual Studio Code instance.
Visual Studio Code seems not supporting the protocol command Target.getBrowserContexts
So when trying to connect to the Visual Studio Code instance by these steps, it will failed

Open a Visual Studio Code instance, code . --remote-debugging-port=9222
Get the WSEndPoint in http://localhost:9222/json/version
Connect to this WSEndPoint by puppeteer.connect({browserWSEndpoint:'...'})

The issue raises from
const {browserContextIds} = await connection.send('Target.getBrowserContexts');
in Launcher.js
I take a look the value when VSCode is lanuched with puppeteer.Lanuch, and it is null. So null is set for this parameter, and the Browser.js need to updated to check if contextIds is not null when trying to loop the contextIds.
With this fix, I could connect to an existing Visual Studio Code instance.

@caslt we have #4283 to support various electron applications.
We explicitly avoid this kind of workarounds. I believe you can just use an older pptr version, e.g. v1.4.0, to drive VSCode instance.

@aslushnikov
So actually I should ask the Visual Studio Code team to support the protocol command Target.getBrowserContexts, right?

Rather electron team; I believe they have a bunch of issues already

OK. Thanks for the information.

I find the related issue in electron https://github.com/electron/electron/issues/17776


Update pritunl to 1.0.1356.36

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Thank you for the contribution. It was merged directly as 9b52dd274ed7a7a071a61dcf99ef8897170f5a54. Your contribution is still credited to you.


sp_GetAppLock writes to the transaction log

There is no logical reason I can think of that requires sp_GetAppLock to write to the transaction log. This causes multiple issues (and is not mentioned in the documentation).
1/ excessive logs if you use this function to gate access to other resources
2/ extreme slowdown on servers with Always On when locking on the primary database.
The following script executes all locks in about 3 seconds on my i9 standalone database.
declare @i int = 0;
while @i < 100000 BEGIN
set nocount on;
begin tran
declare @locked int = 0;
exec @locked = sp_getAppLock 'MyResource', 'Exclusive', 'Transaction'
if @i % 1000 = 0 Begin
print @i;
end;
rollback
set @i +=1;
end
Run multiple copies - all play well together, but you will see log file usage increase quickly (to about 6 megabytes/sec)
Then try running against a readonly database on an Always On Secondary. It still runs fast.
Then try running on a primary Always On database. It executes about 50 locks a second, instead of about 35,000.
Changing the database to async helps...
Please change the logic in sp_GetAppLock to be identical on primary and secondary server. I hope the secondary isn't logging at all, but I expect it to be logging in either TempDB or master...

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

ID: 1bfc5142-4589-ac67-69c2-65d7760719e4
Version Independent ID: 02464294-1e91-30e6-8489-51ee2ee45a31
Content: sp_getapplock (Transact-SQL) - SQL Server
Content Source: docs/relational-databases/system-stored-procedures/sp-getapplock-transact-sql.md
Product: sql
Technology: system-objects
GitHub Login: @stevestein
Microsoft Alias: sstein

@brettshearer - thanks for the feedback!  This area is primarily for doc issues so I'm closing this issue. The best way to reach out and report product issues and provide suggestions is at the UserVoice  site.
Thanks!


Configuration Help - documentation has dead links

Describe your desired configuration
Hi there,
I'm trying to use your software, but all of the documentation for the effects lead to 404s.
https://moshimoshi0.github.io/TTController/effects/perledcoloreffect
Also, is there any default config I can have the program pre-populate (or do you have any that I can see?) so that I can see what is needed to configure the fans? A bunch of empty lists will take a long time to look through documentation for. I just want some static patterns on specific fans (and even this is too much for tt...), so it shouldn't be too difficult using your software, but really hard to use it without examples.
Hardware info
---

Current configuration
---

Yes sorry, I just recently stated to write the docs so its missing pages. I'll try to complete it asap.
Simple config would be something like this:
{
  "Profiles": [
    {
      "Name": "Default",
      "Ports": [
        [9802, 8101, 1],
        [9802, 8101, 2],
        [9802, 8101, 3],
        [9802, 8101, 4],
        [9802, 8101, 5]
      ],
      "SpeedControllers": [
        {
          "Type": "PwmSpeedController",
          "Config": {
            "CurvePoints": [
              [30, 30],
              [45, 50],
              [55, 60],
              [65, 75],
              [75, 100]
            ],
            "Sensors": ["/intelcpu/0/temperature/8"],
            "Trigger": {
              "Type": "AlwaysTrigger"
            }
          }
        }
      ],
      "Effects": [
        {
          "Type": "FullColorEffect",
          "Config": {
            "Color": [255, 0, 0],
            "Trigger": {
              "Type": "AlwaysTrigger"
            }
          }
        }
      ]
    }
  ]
}

Uses custom pwm curve for speed, and full red color.
Ofc you need to update it with your port identifiers in the Ports list, and your sensor identifier in Sensors list.
If you want static colors but not all leds the same you would need to replace the effect with this:
        {
          "Type": "PerLedEffect",
          "Config": {
            "Colors": [
            	[255, 0, 0],
            	[255, 0, 0],
            	[255, 0, 0],
            	[255, 0, 0],
            	...
            ],
            "Trigger": {
              "Type": "AlwaysTrigger"
            }
          }
        }

and fill the Colors list with your desired colors. It has to have the same amount of colors as your fans have leds.
Hope that helps.


Cap. Bank texture Borders

Textures Borders of Cap. banks fit there respective Capacitor (The Creative one got a black-yellow hazard like texture)
In game:
http://i.imgur.com/7rKyZ6U.png
http://i.imgur.com/4GB8lRr.png

@CyanideX's retexture has this covered now


LND isn't starting anymore.

Hello, LND is not running anymore on a rasp pi 3. It has been running smoothly this year, then I shut down the whole PI for 2 months.
Now I have turned the pi 3 on again but the lnd for some reasons fails after a Restart loop.
https://termbin.com/fl8f

I noticed that with TOR disabled LND is able to start.

But TOR itself does not look connected.

TOR logs.
https://termbin.com/zcbl

The v1.2 had some problems with TOR - those should be fixed with v1.3 that is not final yet, but you can try the v1.3 Release Candidate 5 see for download here: https://github.com/rootzoll/raspiblitz/tree/v1.3#installing-the-software

I found some docs and issues around a "dormant" feature of Tor which could be related.
If Tor has a state when not used for a while it needs some unique command/action to change this state?? It also looks like there have been changes related to this in the most recent Tor releases (so potentially affecting RB v1.3? : https://blog.torproject.org/new-release-tor-0401-alpha

ran into this too... fix my specific situation required: sudo chown bitcoin:bitcoin /run/tor/ and remove User bitcoin and PortForwarding 1 from /etc/tor/torrc
I'll monitor further..


set annotation automatically when EnableGangScheduling is set to true

To allow the gang-scheduling with using kube-batch, we need to create podGroup and set the annotation scheduling.k8s.io/group-name: $PODGROUP_NAME to each pod.
When EnableGangScheduling is set to true tf-operator create the podGroup automatically but doesn't set the annotation.
This PR fixes the problem by setting the annotation when create the pods.
fix #1031

This change is

/assign @gaocegege @richardsliu
thanks!

Coverage remained the same at 76.744% when pulling c05002df3f86b2b128b89e626d2a7ff0bf25687c on ChanYiLin:master into fd76deec5cf9c1305a92b9e4c699b0379bcb5456 on kubeflow:master.

Coverage remained the same at 76.744% when pulling c05002df3f86b2b128b89e626d2a7ff0bf25687c on ChanYiLin:master into fd76deec5cf9c1305a92b9e4c699b0379bcb5456 on kubeflow:master.

Currently, we don't have tests for gang scheduling feature.  How are these annotations used when feature is enabled? Is it a must fix?

/cc @k82cn

I think it's necessary.
According to gang-scheduling,

kube-batch will watch PodGroup, and the annotation scheduling.k8s.io/group-name identify which group the pod belongs to

Should I open a issue for adding the tests for gang-scheduling?

I think it's necessary.
According to gang-scheduling,

kube-batch will watch PodGroup, and the annotation scheduling.k8s.io/group-name identify which group the pod belongs to

Should I open a issue for adding the tests for gang-scheduling?

Yes. This  means that this feature is broken now ? Can you add tests ?

Great,  we need this, for now when we enable gang scheduling,  we need set the annotation manually and it is not friendly to users.

/lgtm
Thanks for working on this. Can you open an issue for adding tests? It can be done in a separate PR.

@wackxu Thanks for the update.
/approve


Ensemble for PyTorch Geometric

Hi,
I want to use Ensemble-PyTorch with PyTorch-Geometric. However, it doesn't recognize the dataloaders.
Is this under development or a bug.

Hi @ParasKoundal, could you provide the code snippet on using dataloaders with graph data, so that we can take a closer look.

@xuyxu
It is simple.
`.....
from torch_geometric.loader import DataLoader
.......
train_loader = DataLoader(train_dataset, batch_size= batch_s, shuffle=True,drop_last=True)
val_loader = DataLoader(val_dataset, batch_size=2,drop_last=True)
test_loader = DataLoader(test_dataset, batch_size=2,drop_last=True)
.......
`
I have created a custom class to preprocess dataset before loading into dataloader.
After that I was trying as given in https://ensemble-pytorch.readthedocs.io/en/latest/quick_start.html. For regression I tried initially with VotingRegressor, doesn't work (error given in the initial issue raised). Similar with others too.

Could you further provide the full exception traceback, thanks!

@xuyxu
Here's that
test_loader=test_loader
  File "/cr/data02/koundal/applications/gpu-project/lib/python3.7/site-packages/torchensemble/bagging.py", line 329, in fit
    self.n_outputs = self._decide_n_outputs(train_loader)
  File "/cr/data02/koundal/applications/gpu-project/lib/python3.7/site-packages/torchensemble/_base.py", line 267, in _decide_n_outputs
    _, target = split_data_target(elem, self.device)
  File "/cr/data02/koundal/applications/gpu-project/lib/python3.7/site-packages/torchensemble/utils/io.py", line 84, in split_data_target
    raise ValueError(msg)
ValueError: Invalid dataloader, please check if the input dataloder is valid.

This could possibly be the side-effect of the commit from issue #75. Will see if this could be fixed in a few days, thanks for reporting @ParasKoundal !

@xuyxu Any update on this?

Hi @ParasKoundal, sorry, I am kind of busy these days, and will take a look during the next weekend.

In torchensemble, at each iteration the input loader is expected to return a list in the following forms:

[data_tensor, target_tensor]
[data_tensor_1, data_tensor_2, ..., target_tensor]

The first kind of form is the most widely-used form of the dataloader (i.e., for batch_idx, (data, target) in enumerate(loader)), while the second one comes from the feature request from #75 to support multiple input tensors.
However, the dataloder in pytorch geometric conforms to neither of them:

(positive_batch, negative_batch)

which does not contain a target tensor since the label is simply the index of the batch in the tuple returned.
Here is a simple solution, please let me know if it solves your problem on using torchensmeble models in pytorch geometric. The general idea is to override the _sample method. Taking metapath2vec as an example, we could declare a new class like:
from torch_geometric.nn import MetaPath2Vec

class CustomMetaPath2Vec(MetaPath2Vec):

    def _sample(self, batch: List[int]) -> Tuple[Tensor, Tensor]:
        if not isinstance(batch, Tensor):
            batch = torch.tensor(batch, dtype=torch.long)

        pos_sample = self._pos_sample(batch)
        neg_sample = self._neg_sample(batch)

        data = torch.cat((pos_sample, neg_sample), dim=0)
        target = torch.cat(
            (torch.ones(pos_sample.size(0)), torch.zeros(neg_sample.size(0))),
            dim=0
        )

        return [data, target]

Using this new class, the positive_batch and negative_batch will be concatenated as one tensor data, and you can identify them via the target tensor.
In addition, some extra steps are required in the forward function of downstream base estimators.
Looking forward to your kind reply @ParasKoundal


Function for quitting in the middle of a song

What is your question?
Is there a function that checks if the player quits in the middle of a song, whether from the pause menu, the game over screen, and hell, even restarting the song? I have onEndSong functions and I also want them to trigger when the player leaves so the player doesn't have to go back to the Settings menu to re-enable or re-disable the options I changed for the song.

Store client preferences in a variable then restore them under function onDestroy()


Non-free test data

While looking further into #114, I found that some of the docs in tests/input are copyrighted and non-free, and thus should not be included in GitHub unless there is some explicit permission from the rights holders.  As one of them is https://www.sciencedirect.com/science/article/abs/pii/S1464343X10000865 , it is quite likely that rights holder has not, and will not, give free-libre rights for its redistribution.
I suggest finding alternative PDFs for testing, and delete the copyrighted PDFs before another release is cut.

You're absolutely right. It should be pretty easy to use LaTeX and some lorem ipsum text to generate our own test documents.


Using TCP tunneling for faster messages updates

Hi,
The API has the the TCP feature on top of the http one.
It means that we can connect via one TCP session, instead of sending http requests to the server in order to get new messages.
Via TCP, messages are delivered asap without having to poll.
Is there a way to use this feature with Kotlogram ? I need to receive a message asap within a known time interval, where every milisecon counts.

Kotlogram is currently relying on a TCP socket only, the HTTP transport is not implemented.

What a good news. Thank you.


Warning: componentWillMount is deprecated

Issue
I'm receiving a warning about componentWillMount is deprecated.
Warning: componentWillMount is deprecated and will be removed in the next major version. Use componentDidMount instead. As a temporary workaround, you can rename to UNSAFE_componentWillMount.

Please update the following components: AnimatedComponent

Learn more about this warning here:
https://fb.me/react-async-component-lifecycle-hooks

Versions:
"react": "16.8.6",
"react-native": "0.60.4",
"react-native-reanimated": "^1.1.0",

As a workaround you can go into 'react-native-reanimated/src/core/createAnimatedComponent.js and change componentWillMount() to UNSAFE_componentWillMount()
I also haven't had any problems with my animations after moving this._attachProps(this.props); into the componentDidMount() lifecycle method.

@jhainaua, that is not a workable solution, you'd need to change the upstream code every time you reinstall or in CI environments and such.

@jbrodriguez would creating your own fork and installing that while waiting for a solution not solve the problem you posited?
Regardless, I apologize for the confusion; I believed that starting the comment with "workaround" would have carried the implications through for the rest of the comment. I've since updated the phrase "workable solution," to "workaround that can solve the problem," as "workaround" implies a temporary fix. Hopefully that language is clearer.
Also, after checking some of the pull requests, it looks like a solution is also being discussed in pull request #342 .

Until resolved in upstream, this tool can be used to apply the workaround directly in the node_modules directory without having to create a fork: https://github.com/ds300/patch-package

I think that the best workarround, if you know that you are not using ComponentWillMount in your own code, and it's just a library deprecation, is to add an ignore warning at index.js in root directory
import { YellowBox } from 'react-native';
//TODO:CHECK NOT USING THIS LIFECYCLE METHODS. Ignoring change of lifecycle react-native
YellowBox.ignoreWarnings([
'Warning: componentWillMount is deprecated',
'Warning: componentWillReceiveProps is deprecated',
'Warning: componentWillUpdate is deprecated',
]);

@cargallo That's not a workaround. It just hides the warning which is not a good thing to do

@cargallo That's not a workaround. It just hides the warning which is not a good thing to do

Yes It's. The Warning just says that the componentWillMount is deprecated and will be removed in the next major version. Until you change the version of your project you will not have any problem and at that time probably the library will be corrected. That's why I talked about workarround and not solution.

@jbrodriguez Until resolved in upstream, this tool can be used to apply the workaround directly in the node_modules directory without having to create a fork: https://github.com/ds300/patch-package

Unfortunately this is not helping me! I followed the directions but every time I install a dependency it reverts back.

The fix has been pushed to master, but isn't on npm yet. I would rather not blanket ignore cpm deprecation warnings, in-case any others come along that could be missed.

The fix seems to be merged in master branch but not on NPM.
As a workaround, you can install the current master branch - but you'd lose the version number
yarn add https://github.com/kmagiera/react-native-reanimated.git\#master
// OR npm install https://github.com/kmagiera/react-native-reanimated.git\#master

@pistou
You can use commit hash instead of branch to achieve some sort of locking version:
yarn add https://github.com/kmagiera/react-native-reanimated.git#cd5a319eb6afd6efe5fb6750f7cef332fd17bdbd
// OR npm install https://github.com/kmagiera/react-native-reanimated.git#cd5a319eb6afd6efe5fb6750f7cef332fd17bdbd

Changes has been merged in 1.3.0. You can close this issue.

Thanks for this! I was still getting the warning after upgrading, but clearing the transform cache fixed that:
npm start -- --reset-cache

Upgrading react-native-reanimated should resolve warnings


Test Device ID is not working properly in Banner.

I am using Ads with my test device id. Sometimes Banner load real ads, but Interstitial all the time showing dummy ads. Something is wrong with Banner.

I have the same problem. Banner ads rarely show for me.

In v2 (available as beta) a lot has been refactored, so I'm pretty sure this issue is now obsolete. Might that not be the case then please open a new issue.


Re-export tippy core in typings file

Missing types after d08169019f62382a9c6374b7eab99b3ce4193d7f

I think there is no reason to actually export everything from core in framework packages. You can just use the core instead. The core re-export is just a convenience more than anything, for small/unsupported cases.
The core package is installed as a dependency, so it will be always available, even if it is not present in package.json, but one can always add it if they need to have everything explicit :man_shrugging:


Create daily paper processing job

To mark as complete, create a workflow that does the following, in a single command:

[ ] runs a query for list of new papers
[x] runs pipeline for a each of N papers (let's say 10 to start), in the same container

[x] pipeline stages includes symbols and citations (for now, do not process sentences, as this will potentially greatly increase the run time)

[x] sends a processing summary by email to Andrew

See the comments below for ideas for deployment requirements for this PR.
Processing summary: To enable the processing summary, we may want to add a --notify-email option to the pipeline. The summary should include:

Counts of how many citations were detected
Counts of how many equations were found
Counts of how many symbols were found
A link to the paper
A link to the log on S3 for Andrew's review
A link for submitting a bug if a paper was not processed well

This summary should also include a template that can be readily plugged into a bug report.
Emergent tasks: For the job submission UI, new options:

[x] "Dry run (process the paper, but don't upload entities to the database. Papers processed with this option will not be made interactive. Useful for debugging purposes.)"
[x] "Process papers one entity at a time. Set this if you want the paper to be processed more accurately."
[x] (optional, probably skip) select which kinds of entities you want to process
[x] Update the counting of entities for citations and symbols. Current messages are not helpful

Create other issues soon for:

[ ] Versions of data; serve only the most recent uploads for a paper
[x] Send email on pipeline fail

One option for running the job in the long term might be to use Fargate and schedule ECS tasks each day using CloudWatch. See https://docs.aws.amazon.com/AmazonECS/latest/developerguide/getting-started-fargate.html

Here are the tasks for setting up a pipeline on AWS:

[ ] Set up a Job Queue on AWS Batch
[ ] Create two Docker images: one for the daily job, one for on-demand paper processing
[ ] Upload the images to an EWR repository
[ ] Create CloudWatch events that trigger each job; one on a cron job, and one listens for a new file to be uploaded to an S3 container with a work queue

Also see this for triggering Batch jobs when files are added to S3 https://linuxacademy.com/hands-on-lab/e0a688e2-15d0-49e1-b1c0-d3b53fd757d3/

Instructions for passing along the keys of objects that were added to S3 to the batch jobs that should process them. https://docs.aws.amazon.com/batch/latest/userguide/batch-cwe-target.html

Getting very close! We now have an online service for submitting paper processing requests at https://processmypaper.scholarphi.com/

A couple more tasks for the user interface:

[ ] "Dry run (process the paper, but don't upload entities to the database. Papers processed with this option will not be made interactive. Useful for debugging purposes.)"
[ ] "Process papers one entity at a time. Set this if you want the paper to be processed more accurately."
[ ] (optional, probably skip) select which kinds of entities you want to process

This issue is being dropped because Russell is currently working on our solution for scaling the paper processing, which does not look like it will involve daily paper processing.


Always cross compile

Exherbo, another linux distribution that has done good work with cross-compiling, always builds cross compilers---i.e. --host --build and --target are always passed to gcc's build system even if some of those platforms are the same: http://git.exherbo.org/arbor.git/tree/packages/sys-devel/gcc/gcc.exlib#n187. The big advantage here is by using the cross-compiling code path in all cases, there's less to maintain, and actual cross compilation is less likely to rot assuming native compilation will always be better tested.
In https://github.com/NixOS/nixpkgs/pull/21268 (specifically https://github.com/NixOS/nixpkgs/pull/21268/commits/633feb4e39a24c7da9ff4ae1b5f4219e0c2a1bb6 but I'll probably rebase at some point breaking that link), I introduce always-defined buildPlatform hostPlatform and targetPlatform for the same reasons (I keep around nullable crossSystem and not-always present stdenv.cross for compatibility). So if/when that PR is merged would be a good time to tackle this. that PR will probably be closed as a bunch else happened separately, including always defining buildPlatform hostPlatform and targetPlatform and removing crossSystem and stdenv.cross altogether.
Naturally this would be a gcc-caused mass rebuild on Linux. Darwin shouldn't be as affected as LLVM, by default, includes all the targets we care about.

@DavidEGrayson's work in https://github.com/DavidEGrayson/nixcrpkgs/ should greatly accelerate this!

@cleverca22 points out https://github.com/taktoa/arcane-chat/blob/master/default.nix has a bunch of hacks needed to get windows to work. Would be good to keep these things in mind.

OK, hope this actually happens this cycle :crossed_fingers:.

This will be seriously amazing!
So after a quick look, this change requires changing all occurrences of crossSystem to hostPlatform or targetPlatform? Is there no way to guess the correct value at evaluation time?
In other words, it's a huge single-shot change and after that it will just work?
If so, I propose we declare a week "cross-compile week" and only merge changes that make this work. Once everything builds on staging we merge to master and we're done?
Or is there more to it? Will there be things that break?

The crossSystem vs hostPlatform things are actually all taken care of, now! What's left is:

[ ] #36867 LLVM-based cross compilation
[ ] Change configureFlags on binutils and gcc to be [ "host" "build" "target" ]. Watch out for this arm (armv5 I think it is?) case where then things fail to build. Also do for ghc and any other compiler where we have configureFlags set today. Also make the various cases of targetPrefix unconditionally hostPlatform.config "-". (Must be done with the previous.

Said alternative is setting the build_alias, host_alias and target_alias environment variables. However, I'm not sure if this is really a desirable solution, both because it'll only work for autotools-based configure scripts and because I'm not sure this way of setting the platforms is actually considered a public/documented/stable interface by autotools.

So when everything is cross-compiled, will the hashes of something
cross-compiled on platform A to platform T be the same as platform B to T?
On Tue, Mar 27, 2018 at 1:15 PM Linus Heckemann<EMAIL_ADDRESS>wrote:

Said alternative is setting the build_alias, host_alias and target_alias
environment variables. However, I'm not sure if this is really a desirable
solution, both because it'll only work for autotools-based configure
scripts and because I'm not sure this way of setting the platforms is
actually considered a public/documented/stable interface by autotools.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/issues/21471#issuecomment-376487828,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADWlkAUjoLYAcY44QQdUpda1jG27RR7ks5tih9pgaJpZM4LXFz4
.

No. The derivation hashes will be different, and as a result the output hashes will also be different. In an ideal scenario the only differences between cross-compiled and natively-compiled outputs will be the store paths, but I highly doubt that we'll achieve that in practice.

Well, maybe we can achieve that with a CAS store, but only if the bytecode
is 100% the same… It would be great if we could exclude the host platform
from the input hashes…
On Tue, Mar 27, 2018 at 2:04 PM Linus Heckemann<EMAIL_ADDRESS>wrote:

No. The derivation hashes will be different, and as a result the output
hashes will also be different. In an ideal scenario the only differences
between cross-compiled and natively-compiled outputs will be the store
paths, but I highly doubt that we'll achieve that in practice.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/issues/21471#issuecomment-376500123,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADWloXVPFtZbrT_4rK4ySTA-nSuIEG_ks5tiirYgaJpZM4LXFz4
.

@wmertens Yes that is a goal, but it will be very hard. CAS / intentional store is necessary, but not sufficient, as the input binaries for the build tools would not be anywhere near bit-for-bit the same.
[Also, you mean build platform not host platform, BTW. The names are indeed awful.]

@dezgeg raised the concern of tests not being run when cross-compiling. Does exherbo maybe have a solution that we can steal?

@lheckemann: My experience on Exherbo has been that tests run just fine when build == host (build == run), and would likely run just fine any time host (run) is runnable (such as i686 or x32 on a 64-bit builder). That could be further expanded using binfmt_miscand qemu-user.

I can't find it well on my phone, but the answer must be in https://git.exherbo.org/paludis/paludis.git/

This is the relevant bit, but is overconservative - it just checks for build == host (build == run) - though it misnames 'run' as 'target'.

@Eternaleye err we mean how are (autoconf-based) configure scripts invoked. I see default_src_configure but not where the various env vars it uses are defined.

@Ericson2314: All the DEFAULT_SRC_TEST_* variables are set by individual packages.
You probably want to look at the definition of econf instead.

@eternaleye
https://git.exherbo.org/paludis/paludis.git/tree/paludis/repositories/e/ebuild/exheres-0/build_functions.bash?h=cross#n155 huh so --build and --host indeed are always passed if CBUILD and CHOST are defined. Do you all indeed never have configure run programs then? Brave!

That's a work in progress. The most problematic cases are actually thing like gobject-introspection, which is inherently incompatible with cross-compilation at the architectural level. Things like that work in practice when build == host (build == run), but fail when "really" cross-compiling. The ability to ban commands in the environment is the main tool used to fix such issues where possible - for example, we ban unprefixed pkg-config so we can learn what needs patched to respect --host.

Neat patch!

Indeed that patch looks like it solves many of those problems in practice. But my general point stands, aka even if you do "cross compilation" with e.g. both build and host set to x86, you still wouldn't detect those problems, you still would have to do e.g. and x86 -> ARM cross compile to actually detect them, right?

@degzeg Yes; there's really no feasible way to do static analysis of autotools-based buildsystems.

I'm running into this when trying to compile for aarch32 on aarch64. I've been sending PRs to set configurePlatforms = ["host" "build"]; on a per-package basis, but is there anything stopping us from doing it globally at this point?

Let's put it in staging and watch the world burn :)

Still pertinent, and in fact https://github.com/NixOS/nixpkgs/pull/87909 is getting new attention.

We did make some progress towards this: #123419, #119625, … (?)

One future concern: would we be ok with declaring cross-compiled binaries as equivalent, no matter what the build platform was?
If so, provided we have a trusted mapping (being looked at with the intensional efforts), how would we go about generating all the input hashes that map to the same build?

@wmertens I don't think we should calculate them up front. The space of possible build platforms is very, very large.

@Ericson2314 another option would be to somehow replace the build platform input hash with a placeholder when calculating the input hash? Then all cross-compiling build tools for a target platform would map to the same dependency input hash?

I'll use this chance to mention that I've been looking into cross compilation with Nix, and my conclusion is that the build platform shouldn't go into an input hash at all. It makes no sense to have two bit-for-bit identical packages with different hashes simply because one was built natively and another one cross compiled. The host platform (on which the package will be used) should be the one included in the input hash. And for packages that have no native code (for example text files, like configuration or Python programs) platform shouldn't matter at all.
If you get rid of that, then the other source of difference is the compiler. Here, you basically want native and cross compilers built from the same source with the same codegen options to have different store paths, but affect input hashes in the same way. I don't think this is possible without extending Nix, and even then this kind of rule bending feels like it goes against the core Nix philosophy.

@lahvuun I suspect with CA derivations we could do "cache cheating as a plugin" to allow people to experiment with mixing builds without baking in logic in Nix contra to our morals.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/nixlang-how-do-you-find-all-uses-of-a-declaration/18369/13

This PR is just about done now: https://github.com/NixOS/nixpkgs/pull/87909
I'm thinking it might be merged just after branch-off of 22.05?

Only a step towards it, however, since prefixing the compiler by default is still missing.

Yeah, that'll be an interesting exercise


Fix rebranding

Fixed pype > openpype issues
Saner default for chunk_size (0 is not working at all)

Saner default for chunk_size (0 is not working at all)

There should be probably validation of the value in usage. Like if it's 0 or less then use default (not filled)?


Investigate golang/build

Following discussions with @jbenet, we need a network of machines we can use to:

run builds for various platforms
run tests in various platforms
run longer network/protocol tests on demand

Let's properly investigate golang/build for the above goals. Here are some steps:

[ ] evaluate golang/build (do our homework first, figure out things on our end)
[ ] figure out what has to change, with bradfitz' help.

Some information from a quick look at the golang/build source code:

Some things look specific to Gerrit, see https://github.com/golang/build/tree/master/gerrit and https://github.com/golang/build/blob/master/app/build/notify.go#L150
Other things look specific to Google App Engine.
There are some hardcoded values that should be put in config files, see https://github.com/golang/build/blob/master/build.go#L5 https://github.com/golang/build/blob/master/app/build/notify.go#L27
It looks like the config system of the dashboard relies on the Datastore Viewer in the App Engine, see https://github.com/golang/build/blob/master/app/build/config.go

So it looks like we will have to at least make some changes to make it work with GitHub instead of Gerrit. If we don't use Google App Engine, then we will have more changes to make.

Closing this in favor of https://github.com/ipfs/golang-build/issues/2


[main] Update community files (#224)

Update community files
Signed-off-by: Knative Automation<EMAIL_ADDRESS>

OCF Webhook is merging this PR


Security policy

Could I request for a security policy to be set so that I can make a report?

Hi @ishmeals , this has been added.


Git: commit box grabs focus after reload

Steps to Reproduce:

open SCM viewlet
focus into the editor
reload window

=> focus ends up in the git commit box
Any other view does not steal focus from the editor, so it must be something in the SCM viewlet that passes DOM focus to the commit field.

@joaomoreno okay if I take this one as well?

@itamark Be my guest!

@bpasero Interesting. I was able to reproduce in my regular Insiders build but not in my vscode dev build. Have you seen cases where this doesn't happen?

Maybe you have multiple repositories in your insiders, but not in dev?

Ah I was just about to commit and see it's already dealt with. I'll grab something else.


exporting change action with formKey

Hi, @erikras
Is there any reason why only 'initialize' action for each formKey is exported as 'initializeWithKey' ?
In my page, there are buttons to complete all input and to reset all values, and I guess I need 'changeWithKey' action or something like that.
Or am I supposed to use plugin feature?

Added in v3.1.1.

Wow, really first! Thanks!!


Update for DruxtViews 0.5.0

Is your feature request related to a problem? Please describe.
DruxtViews 0.5.0 uses the DruxtComponent Mixin, requiring minor changes.
Describe the solution you'd like
Update module and relevant theme components.
Describe alternatives you've considered
N/A
Additional context
N/A

Requires an update to DruxtSite module.


Memory Leak

I noticed a memory leak, after about 5 to 10 dictation my system was getting nearly frozen, because all 16 GB ram and 8 GB swap were used.
Then i looked further into it:
Freshly opened the site: 41 MB
One dictation with 100 words: 2 GB
Second dictation with 100 words: 5 GB
Measured with the built in task manager in Firefox, system task manager showed similar results.
OS: Arch Linux, Kernel 6.6.2
Browser: Firefox 120.0 64 bit
Layout: Mine
Logged in, Keyboard hidden

It starts rising as soon as I start a lessons, about 100-200 MB per Minute.
No difference if typing fast or slow, as soon as the timer starts the ram usage rises.
When i press pause it slows down or even stops to rise, can't tell for sure.
When the lesson is finished or canceled it also stops to rise, but it stays on the current ram usage level.
I have tried it with Chromium, there i don't have this problem, it stays under 100 MB ram usage the whole time.
I have some browser add-ons installed in Firefox, so i tried it in a private tab, where all add-ons are disabled, but no difference.
Here is my browser info, from: https://toolbox.googleapps.com/apps/browserinfo/

If you have some idea what else i could try to enclose the problem i will try.
As workaround i just refresh the page after every lesson right now.
Btw: I really like the app, its so simple yet so good and motivating to learn a new keyboard layout. While training I had some ideas for improvements. If you don't mind, i open some feature requests.

Please feel free to submit feature requests. I will try to reproduce the issue again.

Could not reproduce :< / not relevant on newer firefox versions


Bug Report: duplicate talismans

You might already know this, but opening the missing Talisman menu Shows all Missing talismans, including downgrades of already owned Talisman, Like Pot affinity ring/talisman, Speed affinity talisman/ring, scarfs xxx(the Dungeon Xp boost one), Slayer defense talismen and rings, Red claw Ring/Talisman and some Other i might have missed, although i own the maxed version. Really Happy you included a "Missing Talisman" Feature though, thats one Thing i Always missed in skylea

This is intentional, I merged this version into master. I just wanted to release it bcs it was taking a while. Expect a fix soon!

Fixed #26


Optional Chaining doesn't work for Out-of-range array indexes

What
Using the Playground with the newest version 1.16 I expected Posts[10]?.Title to result in undefined whereas it throws
reflect: slice index out of range (3:6)
 | Posts[10]?.Title
 | .....^

Just like in JS [][1]?.a also works and yields null/undefined making things like [][1]?.a ?? 42 work where as Posts[10]?.Title ?? "default" does not work currently in with this library.
Or is this expected/deliberate?

In JS Posts[10] return undefined. This is why it is working in JS. In Expr Posts[10] will raise an error.
Not sure what is the best solution here.

Expr for this purpose have a special builtin function get(array, index).
It will return nil instead of raised error:
get(Posts, 10)?.Title

Another solution I'm looking into is adding an option to Expr to make all . access optional changing and to return nil insted of error on out of bound check.

Expr for this purpose have a special builtin function get(array, index)

But this would get bulky very fast wouldn't it?
I mean get(get(myDeepObject?.Prop, 10)?.NestedList, 1)?.value

Another solution I'm looking into is adding an option to Expr to make all . access optional changing and to return nil insted of error on out of bound check.
I would love that!
I already thought of writing a Patcher that makes all MemberNodes Optional by default. This as an global option would be greatly appreciated and I also do see value here for other people as it makes the syntax a whole lot easier to write for non technical users and everyone can decide if they want to turn this option on or off

I would love that!
I already thought of writing a Patcher that makes all MemberNodes Optional by default. This as an global option would be greatly appreciated and I also do see value here for other people as it makes the syntax a whole lot easier to write for non technical users and everyone can decide if they want to turn this option on or off

I agree. Let's make an option to set all MemberNodes as optional.

Posts[10]

Make array access should return nil instead of rasing error by default. And have an option like expr.PanicOnOutOfBound().

Love it


Rebrand "NPS" plugin to "User Satisfaction Surveys"

@esethna Can you rebase to v5.14-documentation branch?


Rename this project to  windows-persian-keyboard-for-linux

As this script worked on my Manjaro installation so it does work on Arch based distros as well as Debian based distros (like Ubuntu).
So it's safe to assume that it would work on any Linux distribution therefore the project no longer needs to be named "
windows-persian-keyboard-for-ubuntu" and you could rename it to "windows-persian-keyboard-for-linux".

Dear @MasterKia,
I assume it would work on other distros but for making sure I have to check this myself.
Currently, I do not own any Linux-based system to test it. but I can ask my friends and colleagues to test it for me.
further updates will be available here.
Thanks for letting me know that.

Came to say that it does work on Fedora 35 (with wayland).

Came to say that it does work on Fedora 35 (GNOME + Wayland).

thank you for investigating that. I will make a proper change later.


Update vdc_demo to leverage 1912 update of caf_foundations

Currently vdc_demo is not updated to leverage:

new blueprints introduced in 1912 (foundations security, foundations governance, foundations accouting)

naming convention introduced in 1912

Target to use landing_zones stacking (caf_foundations to be used as a prerequisites)
Update modules used in the blueprint with latest available


pthread_setname_np expects 2 arguments, 1 provided (FreeBSD 14.2)

This looks like a re-emergence of #743 - New FreeBSD releases (at least 14.2-RELEASE, and presumably anything after) no longer have the one-argument version of pthread_setname_np so it's breaking in the #ifdef around src/cxx_supportlib/oxt/implementation.cpp line 403.
The easiest solution appears to using the Linux code for FreeBSD (move FreeBSD into the first #ifdef).
That's tested and working on my systems :)

src/cxx_supportlib/oxt/implementation.cpp line 403.

This file does not belong to the libre project.


Notebook explanation

In the example notebook it would be cool to have an introduction section of text explaining what the notebook is about.

All notebooks/workflows that are available on the front page have been reviewed, so I'd close this issue.


ConnectionResetError

All keys matched successfully>
Initiating prediction with a crepe_hop_length of: 128
2023-12-06 22:25:13 | INFO | httpx | HTTP Request: POST http://<IP_ADDRESS>:7860/api/predict "HTTP/1.1 200 OK"
2023-12-06 22:25:13 | INFO | httpx | HTTP Request: POST http://<IP_ADDRESS>:7860/reset "HTTP/1.1 200 OK"
2023-12-06 22:25:13 | ERROR | asyncio | Exception in callback _ProactorBasePipeTransport._call_connection_lost(None)
handle: <Handle _ProactorBasePipeTransport._call_connection_lost(None)>
Traceback (most recent call last):
File "C:\Users\Wesley\AppData\Local\Programs\Python\Python310\lib\asyncio\events.py", line 80, in _run
self._context.run(self._callback, *self._args)
File "C:\Users\Wesley\AppData\Local\Programs\Python\Python310\lib\asyncio\proactor_events.py", line 165, in _call_connection_lost
self._sock.shutdown(socket.SHUT_RDWR)
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host
I get this error every time I make an AI cover and it seems to be related to poor generation

I am getting this error as well but audio generation seems to work though. Did you ever solve this problem?

@Pleb6381 I have solved this error at my fork of this repo at : https://github.com/JackismyShephard/ultimate-rvc


tasks overview

Scan for proposed motions.
* setup a background task
* create a service to read from a github path.
* implement fake repo
* clear any previous proposed motions that are no longer relevant.
* parse the data and push it to redis.
* create a real version
Read proposed motions from redis
* create code to read from RedisProposedMotionRepo instead of the fake one.
Code to automatically open votes
* setup a background task
* For proposed motions that should be currently be open.
* check if they haven't already been created in the local DB, if not create them
Vote api endpoint
* setup an api endpoint
* that takes a user id, motion id, question and vote as parameters
* validate those all look sensible.
* record the vote in the DB
Vote delete endpoint
* setup an api endpoint
* that takes a user id, motion id, and vote id
* removes that vote
Open votes endpoint
* setup an API endpoint
* that reads from the open votes and returns that data. this should be the complete list of which votes are currently open.
Voting score endpoint
* endpoint to get the details of how voting is going
* create fake repo to make it easier to test.
* read from the actual DB from production.
Event logging
* Add event logging code to the 'scan for proposed motions code'.
* Push those events into redis
* Add event logging code to both the voting api endpoints
I'll need to write more notes on events.....this is yet another experimental bit of code.
Event log end point for scanner
* Create an api end point
* that returns all of the events related to scanning for proposed motions
Event log end point for voting
* Create an api end point
* that returns all of the events related to scanning for voting
Event log end point for opening and closing of votes
* Create an api end point
* that returns all of the events related to scanning for opening
and closing of votes.
Integration tests for proposed votes.
* write a vote to git
* make sure it appears in the system
Way more integration tests.

yarp, the files can be listed directly through the api for github like:
https://api.github.com/repos/alwaysseptember/voting/contents/test/data

I'm not going to open this is a separate issue, I don't see the need, but just a reminder, can you share your .idea folder? So that my code formatting will be the same. It can be uploaded to my OneDrive or something so that it doesn't have to be changed in .gitignore.


fix(menu-button): close menus containing selected items when re-clicking the menu button

Description
This PR fixes a small issue with <MenuButton> not correctly closing a <Menu> containing <MenuItem> children with selected=true.
Currently, when you click the <MenuButton> whilst open:

handleBlur is triggered, which closes the menu
the click handler on the button itself is triggered, which currently toggles the menu boolean state
this then causes the menu to re-open

Example arcade showing the issue
This fix stops propagation on the original menu button whilst the menu is open. This allows menu open state to be purely handled by handleBlur / handleClickOutside.

This should also address the somewhat esoteric issue where hovering over a nested <MenuItem> before clicking the <MenuButton> to dismiss the menu would also fail – e.g.
https://github.com/sanity-io/ui/assets/209129/b72b6c84-b2f3-4bf3-bb98-9dea6b43272a


Turn on ASAN by default for dev mode builds

Once #1047 is fixed, we can turn ASAN on by default (for non-release mode builds). We don't want to turn it on by default yet b/c all the memory leaks make output too noisy.
This is beneficial b/c ASAN can catch entire classes of memory issues before we're burned by them. eg using uninitialized memory, use-after-free, etc. Memory leaks are probably the easiest thing it catches.

I've not worked with ASAN before - does it have any negative impacts like longer compile times?

Not sure about compile times. Maybe a little. But there’s usually a 2x or 3x performance penalty at runtime (bc every read and write is instrumented by the compiler).
My hope is that the slightly slower runtime is paid off by catching hard to find bugs earlier.
On Tue, Dec 31, 2019, at 12:09 PM, Alastair Robertson wrote:

I've not worked with ASAN before - does it have any negative impacts
like longer compile times?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/iovisor/bpftrace/issues/1048?email_source=notifications&email_token=AAGJKJYGMECLB723LBXFG63Q3ODENA5CNFSM4KBXA632YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH4QMOY#issuecomment-569968187, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGJKJ73XANQ24XW6PVFMK3Q3ODENANCNFSM4KBXA63Q.

--
Daniel Xu
<EMAIL_ADDRESS>

side comment: I found that target_link_options require CMake 3.13 and newer.
https://github.com/iovisor/bpftrace/blob/04d015e1796b6da57d192d6e357ddac9f14cc3d5/src/CMakeLists.txt#L81

Which distro are you on? Do we need to use an older cmake feature here?
On Tue, Dec 31, 2019, at 6:03 PM, Masanori Misono wrote:

side comment: I found that target_link_options
https://cmake.org/cmake/help/v3.13/command/target_link_options.html
require CMake 3.13 and newer.
https://github.com/iovisor/bpftrace/blob/04d015e1796b6da57d192d6e357ddac9f14cc3d5/src/CMakeLists.txt#L81
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/iovisor/bpftrace/issues/1048?email_source=notifications&email_token=AAGJKJZFFPUAIFB4WMJXDHDQ3PMVVA5CNFSM4KBXA632YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH4Z66A#issuecomment-570007416, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGJKJ3PJLJVARTKQWMSSNLQ3PMVVANCNFSM4KBXA63Q.

--
Daniel Xu
<EMAIL_ADDRESS>

Ubuntu 18.04 and Cmake version is 3.10.2
Well, I don't think older CMake support is needed since it is mainly for developers and easy to build a newer CMake. I created #1054 to print an error message if using old cmake.

We're now running ASAN builds in the CI (#1920) so I don't think that it's necessary to hard-code ASAN as a part of the dev build (and slow down runtime).


Python Version

The Skript is loking very cool for me. I wonder if it'l work with python3.
I hope that it will work.
Have a nice week
APOnCode

it does work on python3 not python2


It generate mnemonic everytime lookup

My environment version:
pdftotext version: 0.46.0
Emacs version (compiled from source code): <IP_ADDRESS>

The index file in ~/.cache/x86-lookup/ is generated.
I run edebug on function x86-lookup, found problem is on function x86-lookup--load-index. And the let binding variables index-file and cache-path are correct, but x86-lookup--load-index returns nil. Then I checked out the index cache file with command cat. Found it is nil.
I will take a try with Emacs 24.

Problem is solved, Emacs 24.5 generate index cache successfully.


Added livenessProbe configuration spec

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Anil Kumar Taya seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Update docs from Request.local to Request.ext

The method was renamed in Tide 0.9.
Just 2 cents, it was a bit confusing to me to use "local state" and "global state" as the names because IMHO those terms are normally associated with entire programs. Other frameworks call "local state" as "per request state" or "request scoped state". The "global state" is sometimes referred to as "application scoped state" as well. I'm not familiar with the design and terminology of this framework, but my suggestion would be to clarify/rename those concepts.

I added a commit to change the "local"/"global" state doc references since the first commit is trivial. Feel free to modify/discuss if needed.

@bluk I think CI is failing because of #531; I'm trying a fix in https://github.com/http-rs/tide/pull/552. Could you rebase on master once we merge? Thanks heaps!

Rebased and squashed to one commit. If there's anything else, please feel free to leave a comment.


feat: use featureFlagGroup claim for feature flags

In #320 we added local evaluation of feature flags. Local evaluation calculates the feature flags for the user, but only has user data from the session token. That works for feature flags which are either on or off, but we sometimes want feature flags for a specific group of users, like the AI team or external testers
This work:

Adds featureFlagGroup to the labs Clerk metadata. We can manually populate this with ai-team for the team
Passes the featureFlagGroup into the feature flag evaluation, so that we can calculate the user's flags without needing their email address

Testing:

See that the download-all-button feature flag is enabled for the group ai-team
Log in with a user with ai-team set in clerk metadata (I've set it for all of our Oak emails)
Load the homepage

Look for Bootstrapping feature flags { 'download-all-button': true } in the server log

Sign in with another account

Look for Bootstrapping feature flags { 'download-all-button': false } in the server log

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


Updated to Bevy 0.13

I didn't realize people were actually using this crate. Just made it on a whim for a project I was working on.

@martinlindhe If I merge this PR, would you make another PR that puts us on Bevy 0.14?

Glad this got merged thank you!

@martinlindhe If I merge this PR, would you make another PR that puts us on Bevy 0.14?

Sure! Incoming soon.


Not compiling everytime that I add a new file

Hi @basarat! Im been playing with the editor and I dont know If Im doing something wrong.
I will try to detail the steps to reproduce this error.

First I initialize the project with alm -i
Then I add a file with the a command in the file tree panel.
Then I add some code there and try to call the command to toggle output js file and Im receiving this error

When I stop alm tool in the command window, and start it again, the autocompile options is working on the files that I added before and If I try to add a new file following the steps before is doing the same behavior.
This is how my tsconfig file looks:
{
  "compilerOptions": {
    "target": "es5",
    "module": "commonjs",
    "moduleResolution": "node",
    "isolatedModules": false,
    "jsx": "react",
    "experimentalDecorators": true,
    "emitDecoratorMetadata": true,
    "declaration": false,
    "noImplicitAny": false,
    "removeComments": true,
    "noLib": false,
    "preserveConstEnums": true,
    "suppressImplicitAnyIndexErrors": true
  },
  "compileOnSave": true,
  "exclude": [
    "node_modules",
    "typings/browser",
    "typings/browser.d.ts"
  ]
}

Hi @basarat I discovered how to make it work, again I don't know if this behavior is normal (in the case that it is i think that may be confusing!) .
The workaround is to add a new file normally as I described before and then press shift + F6 to sync the project, and after that I'm receiving intellisense and my file is compiled!. See the image:

What I expect is to get that behavior automatically when I add a new file; as a user I'm not expecting to press shift + F6 to make it work!
Again thanks for this wonderful project :smile:

Sync should definitely not be required for such a common clase. I'll try and fix it today.
Background
I do have some automatic detection of is sync required here. I think it failed to match the file in this case. Again, I'll have a look after work today :rose:

Released with 0.0.59 :rose:


Adding support for Pydantic2

I've tested this on my flask backed and am able to send emails. Was not able to run tests fully without having issues running the default_checker fixture.

Hello @CharlesTWood
Thanks for the PR.
Shortly I well merge these changes with Master and release a new version.


Sampling of singular kernels

Hello,
Thank you for releasing the code. In the Readme file you specified the command with --random-mask parameter
https://github.com/yuehniu/modeldecomp-fl/blob/04e213968afd2dc7ae4097f8bc1d33b8bdb66ee2/README.md?plain=1#L19-L24
while according to the source code, this leads to uniform inclusion probabilities of singular values.
https://github.com/yuehniu/modeldecomp-fl/blob/04e213968afd2dc7ae4097f8bc1d33b8bdb66ee2/fl/server_orth_drop_v2.py#L278-L281
However, even if self.args.random_mask == False, the inclusion probabilities are computed with softmax instead of raising to the power of prob_factor, see
https://github.com/yuehniu/modeldecomp-fl/blob/04e213968afd2dc7ae4097f8bc1d33b8bdb66ee2/fl/server_orth_drop_v2.py#L274-L277
So, currently the source code and provided commands are clearly different from the hyperparameters described in the paper. Could you please advise, which recipe should I follow to in order to reproduce the results from TMLR manuscript?
Thank you in advance!

Thanks for pointing out the issue.  Yes, you are right, if random_mask is True, then a uniform sampling will be performed. Also, for the softmax based sampling, I should have commented on line 277 and uncommented line 276. Line 276 performs the sampling process described in the main method. I’ll post an update soon.


Remove date format zero-padding

Doesn't add leading zeroes to day of the month when displaying the date.

:+1: looks good.  I had a quick check of functional tests and I'm 99% sure there are no displayed dates that get checked, so should be fine.


UTF-8-BOM for files by default

There is some encoding for new files that I can choose as a default encoding. But there is no way to set UTF-8 with BOM. Please add the new checkbox to turn BOM on or add UTF-8-BOM to the listbox.
Now we have to change UTF-8 to UTF-8-BOM via extarnal text editor after creating each new file..

Hello @zMotoR,
Can you please explain why would you need UTF-8 with BOM? Its use is optional for UTF-8 since it's a variable length encoding, it makes sense only for UTF-16/UTF-32.
Moreover, it might be simply impossible to do as all these encodings are provided and handled by Java.

We independently automate the execution of scripts on our servers. BOM allows you to know for sure that the files are written in UTF-8 encoding. Without BOM we do not know is the file encoding. This could be ANSI, Windows-1251, UTF-8, etc.

Thanks for the provided information. We are going to discuss this issue with our development team.


3.5 - injectSaga: Expected a valid saga descriptor

I'm in the process of upgrading my existing app built off of 3.4 to 3.5 and my "Sagas" are all throwing the following error.
injectSaga: Expected a valid saga descriptor
Here is a sample of one of my sagas in the 3.4 release...
export function* loginUserRequest() {
const watcher = yield takeLatest(LOGIN_USER_REQUEST, callLoginUser);
// Suspend execution until location changes
yield take(LOCATION_CHANGE);
yield cancel(watcher);
}
export function* loginGoogleRequest() {
const watcher = yield takeLatest(LOGIN_GOOGLE_REQUEST, callGoogleLogin);
// Suspend execution until location changes
yield take(LOCATION_CHANGE);
yield cancel(watcher);
}
export function* loginFacebookRequest() {
const watcher = yield takeLatest(LOGIN_FACEBOOK_REQUEST, callFacebookLogin);
// Suspend execution until location changes
yield take(LOCATION_CHANGE);
yield cancel(watcher);
}
export default [
loginUserRequest,
loginGoogleRequest,
loginFacebookRequest,
];
It seems that with the 3.5 release, I do not receive the error if I only export 1 of my saga functions. What's the proper way to conform to this structure with having multiple functions within a saga?

Same as #1899

@gillven Thank you, exactly what I was looking for, closing.


Update Django instructions to fix South migrations

Instructions are broken when using South / Django 1.6 as South will try to use the default 'migrations' directory and fail.
This tells South to use the alternate directory.

Thanks!


Allow unknown thermostats to work instead of failing silently.

Allow unknown thermostats to work instead of failing silently.
Based on fork of 1.2

Great! Do you plan to rebase this to the master branch, or shall I?

I don't have the time now.
You have my blessings. I shouldn't take long and will make all of the Home
Assistant users happy.
On Sat, Jun 23, 2018 at 9:52 PM clayton craft<EMAIL_ADDRESS>wrote:

Great! Do you plan to rebase this to the master branch, or shall I?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mhrivnak/radiotherm/pull/37#issuecomment-399722675,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABsbQPXjgZxiZEXbsWQhHDC7YTC3iIEhks5t_vDkgaJpZM4U09bG
.

Sounds good, I'll take a look at it then. Thanks for your help!

@JerryWorkman I didn't want to push to your master branch to update this PR, so I created a new branch and new PR (#38), and will close this one. You're still the author of one commit to that branch, so I would appreciate it if you could look it over before I merge it :)
Thanks for the help, I really appreciate it!