Rocket's new update? Ruins every plugin

Rocket's new update ruined everything...
Plugins, Kits, Permissions, Servers...
Mind for a quick fix??

dude ik right i cant even use the normal admin commands because i don't know how to uninstall rocket :P

I uploaded a build of rocket.unturned that reverts the commit that broke it(you will still need to download arc for build 732 of rocket, then extract this replacing the Rocket.Unturned.dll file.).
https://github.com/cartman-2000/Rocket.Unturned/releases/tag/untagged-245b9142841f02ebc04e

that just comes up with a thing that says this is not what you where looking for

updated link.


change baseUrl not work

What problem does this feature solve?
when I change baseUrl: './' `，but It is not work . The file packaging path is still 'css/chunk-vendors.92e039b5.css'.Then I found source code write like this resolved.baseUrl = resolved.baseUrl.replace(/^\.\//, ''), I don't know why ?
What does the proposed API look like?
I want to the file packaging path  will change when I configure the baseUrl: './'

Can you specifiy the current version you are using? With vue-cli 3.0.0-rc.10 it works perfectly fine.

I don't understand the problem. ./ means: a relative path.
In terms of a src path for assets in an html page, that's the same as starting the path with "nothing".
So I do t understand what behaviour you want to change - this change wouldn't do anything.

./ is the same as empty in URL paths.

I want to get the  './css/chunk-vendors.92e039b5.css' after packged by change thebaseUrl: './'

Why? That has no effect whatsoever.

Thank you all，i see.


refactor: Refactor DigestBuilder

Refactored src/digest.rs to replace Vec<u8> storage with dedicated Write I/O.
Removed optional hasher and introduced dedicated factory method.
Reworked digest computation and mapping into separate functions.
Merged build and digest computation to enhance coherence.
Improved type safety with Result error propagation.

The one thing I don't like about this is that it requires materializing all the bytes, whereas I think the better solution would allow just hashing them. This would require that the hasher live in the DigestBuilder as previously. I agree this is generally cleaner, but at that cost.

I've pushed a commit that gets most of the way. However, there still remains a final knot to untie, suggesting the refactor has not yet solved the 'build should consume' issue:
error[E0502]: cannot borrow `self` as mutable because it is also borrowed as immutable
  --> src/digest.rs:92:18
   |
92 |     let digest = self.compute_digest(&self.inner)?;
   |                  ^^^^^--------------^-----------^
   |                  |    |              |
   |                  |    |              immutable borrow occurs here
   |                  |    immutable borrow later used by call
   |                  mutable borrow occurs here

Fixed now by eliminating the compute_digest method entirely.


Fix shallow clone host

@sheerun review when you have time?

I've triggered a rebuild for the appveyor builds, fingers crossed...

@vladikoff Will you find time to create failing test?

@sheerun maybe in the next few days, I shall let you know


Sample wanted for rsocket/rsocket-kotlin

About the library

Description:   RSocket is a binary protocol for use on byte stream transports such as TCP, WebSockets, and Aeron.
GitHub: https://github.com/rsocket/rsocket-kotlin
Official website: https://rsocket.io/

What the sample could do
See the examples from the README of https://github.com/rsocket/rsocket-kotlin
Wants to contribute the sample?

Say so in a comment here
Follow instructions in CONTRIBUTING.md
Submit your pull request!

I feel like I'm a bit late to the party, but I'd like to do this :)

Is this still up for grabs?

Well, I don't have a definitive answer to this, I just know I haven't done it yet. Been meaning to, but I couldn't quite find the motivation. If you can, go for it!

how can i to contribute in this repo?

Is this issue still open? May I work on it? Can someone help me as I am new to open source contribution?

Hello @jmfayard, @LouisCAD  ! Is this issue still open? If so, I would like to work on it. Can you tell me about your expectations? I was looking for some other samples, and they just cover one specific use case. Could I split it into server and client samples?

@xisvaldo can you find a way to start the client first without to start a server locally?
That would be easier than the server part, which can be discussed after
Merci!


task keeps hanging in running state on error

If an error occurs while consuming an ldes feed the task keeps hanging in a running state. This seems undesirable, ideally the task would be updated to a failed state so a new task can be created on the next interval.

Can #20 be closed as well?


[CELEBORN-369] [FLINK] Add ut for RemoteShuffleResultPartition

What changes were proposed in this pull request?
Why are the changes needed?
Does this PR introduce any user-facing change?
How was this patch tested?

Please add more details about the UT in description.

https://github.com/apache/incubator-celeborn/actions/runs/4321340760/jobs/7542460961


Stopwatch example does not run correctly on Windows

Stopwatch example does not run as expected on Windows when using
m := model{
    stopwatch: stopwatch.NewWithInterval(time.Millisecond),
}

The count changes within 1000ms for a while, but actually lasts a few seconds
When using
m := model{
    stopwatch: stopwatch.NewWithInterval(time.Second),
}

it runs as expected
BTW, runs fine on Mac

I don't know how to fix it when using time.Millisecond


Bug 2091142: Update gopkg.in/yaml.v3 to v3.0.0 for security fix

Updates gopkg.in/yaml.v3 to v3.0.0 to fix CVE-2022-28948.
Refer to go-yaml/yaml#666.
Signed-off-by: Jack Ding<EMAIL_ADDRESS>

/hold

/hold cancel


Wrong branch names

There is no skeleton or complete branch on this repository

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

ID: 370e4c33-91b6-eafb-1ced-0a079449d982
Version Independent ID: cefd38c9-5c1e-c381-0549-ded07f752f97
Content: Add sign-in to a Node.js web app in Azure Active Directory B2C
Content Source: articles/active-directory-b2c/active-directory-b2c-devquickstarts-web-node.md
Service: active-directory
GitHub Login: @davidmu1
Microsoft Alias: davidmu

And the zip link is dead

@yeya Thanks for your feedback! We will investigate and update as appropriate.

Unfortunately, this article leans heavily on a sample that is no longer supported, so the article is being taken down. If the contents in this article is highly requested, we can create a work item to prioritize the work of creating a new article. For now, please close the issue against this article.
#please-close

@yeya We will now close this issue. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


[Discussion] about  parser with eslint

Is it possible to create a package for eslint parser, just like typescript-eslint/parser.
I am not sure that it can or not get more better effects  and i find some issue with eslint about this.
https://github.com/swc-project/swc/issues/246

I think it's important for us to be compatible with eslint ecosystem without a new tools. Just like rspack is to webpack

Thank you for asking. This is a really big question, the answer is related to your familiarity with the ESLint, JavaScript ecosystem, Rust <-> JS interop etc
And FYI, I have personally asked the author of ESLint on this subject, and he is fine with this project.


[api] aborted requests still cause redirects

Using a submitbutton in a form, the api will always send a request and reload the page, even if I return false. If i return false, i even get an error message "....request aborted", but it still reloads the page.
Tried 2.2.9 and 2.2.0 with same results.

Hi, please provide a test case as per our contributing guidelines; you can fork this JSFiddle.

Hi! Here is my example. JSFiddle
It is the shortened form and does surprisingly not reload the page when used in JSFiddle, but it does reload the page when I'm using in on my own environment. Is JSFiddle using 2.2.9?

@dabeschte Yes, it’s 2.2.9. I tried the code you provided on my local machine, and it doesn’t submit the form—just like a JSFiddle. Maybe there’s something interfering with it on your end?

I can't reproduce it myself anymore. Maybe there was some bad combination of elements I used on my own page, but unfortunately I already replaced the api with my own version.
Thanks for the support, I will open a new issue once it happens again, but for now it seems like I can close this issue.


Session storage grows infinitely

We are using moquette version 0.8.1 and our mapdb session storage files constantly grows.
As far as I notice it happens only when messages are published with QoS level 1 & 2.
Is this is the source of issue #200 and it was fixed in release 0.9 ?

Yes it's the same, try version 0.9
Andrea
On Thu, May 4, 2017 at 9:19 AM, jaroslawherod<EMAIL_ADDRESS>wrote:

We are using moquette version 0.8.1 and our mapdb session storage files
constantly grows.
As far as I notice it happens only when messages are published with QoS
level 1 & 2.
Is this is the source of issue #200
https://github.com/andsel/moquette/issues/200 and it was fixed in
release 0.9 ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/andsel/moquette/issues/305, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA_Y0aIsolGbyFcVdoIL4ipSxrVIeUd5ks5r2XwVgaJpZM4NQTiT
.

Thanks for quick answer :+1:


Sapp browser view is not working.

As per the attached image, the browser view of sapp is not working for mariana-trench. Kindly help me with the same.
Looking forward to hearing from you.
Thanks in advance.

Hello @arthaud ,
Thanks for the reply.
While it is running I executed the command and I could see the following results.
akshayprasad@Akshays-MBP  ~  curl -v http://localhost:5000/

Trying ::1:5000...
Connected to localhost (::1) port 5000 (#0)

GET / HTTP/1.1
Host: localhost:5000
User-Agent: curl/7.77.0
Accept: /

Mark bundle as not supporting multiuse
< HTTP/1.1 403 Forbidden
< Content-Length: 0
< Server: AirTunes/595.13.1
<

Connection #0 to host localhost left intact

It looks like you have another server running that port, see:
Server: AirTunes/595.13.1
Please use a different port for sapp. There should be an option for it (see sapp server --help). If not, please open an issue at https://github.com/facebook/sapp

Thanks for the reply @arthaud .
Can I change the port of sapp?

Apparently, there is no option for it, but it should be easy to add.
Please open an issue at https://github.com/facebook/sapp


Error when connecting to relay server "The MLAPI Relay detected a CRC mismatch."

I'm getting the below error when connecting from unity to the relay running on a amazon EC2 instance:
[MLAPI.Relay] The MLAPI Relay detected a CRC mismatch. This could be due to the maxClients or other connectionConfig settings not being the same UnityEngine.Debug:LogError(Object) MLAPI.Transports.UNET.RelayTransport:BaseReceive(NetworkEventType, Int32, Int32&, Int32&, Byte[], Int32, Int32&, Byte&) (at C:/projects/mlapi/MLAPI/Transports/UNET/RelayTransport.cs:399) MLAPI.Transports.UNET.RelayTransport:Receive(Int32&, Int32&, Int32&, Byte[], Int32, Int32&, Byte&) (at C:/projects/mlapi/MLAPI/Transports/UNET/RelayTransport.cs:284) MLAPI.Transports.UNET.UnetTransport:PollEvent(UInt64&, String&, ArraySegment1&, Single&) (at C:/projects/mlapi/MLAPI/Transports/UNET/UnetTransport.cs:92)
MLAPI.NetworkingManager:Update() (at C:/projects/mlapi/MLAPI/Core/NetworkingManager.cs:642`
It's unclear what the correct settings for the Networking Manager script and Unet Transport should be in order to satisfy the requirement of matching up with the config.json settings of the relay.

Fixed in https://github.com/MidLevel/MLAPI.Relay/commit/a220e834fba94868801519f94af0d57ecb931fde

I have the same issue these days.
"The MLAPI Relay detected a CRC mismatch."
[MLAPI.Relay] The MLAPI Relay detected a CRC mismatch. This could be due to the maxClients or other connectionConfig settings not being the same
UnityEngine.Debug:LogError(Object)
MLAPI.Transports.UNET.RelayTransport:BaseReceive(NetworkEventType, Int32, Int32&, Int32&, Byte[], Int32, Int32&, Byte&) (at C:/projects/mlapi/MLAPI/Transports/UNET/RelayTransport.cs:420)
MLAPI.Transports.UNET.RelayTransport:Receive(Int32&, Int32&, Int32&, Byte[], Int32, Int32&, Byte&) (at C:/projects/mlapi/MLAPI/Transports/UNET/RelayTransport.cs:287)
MLAPI.Transports.UNET.UnetTransport:PollEvent(UInt64&, String&, ArraySegment`1&, Single&) (at C:/projects/mlapi/MLAPI/Transports/UNET/UnetTransport.cs:93)
MLAPI.NetworkingManager:Update() (at C:/projects/mlapi/MLAPI/Core/NetworkingManager.cs:650)
The Fixed UNET configuration loading did not solve mine.

I have the same issue these days.
"The MLAPI Relay detected a CRC mismatch."
[MLAPI.Relay] The MLAPI Relay detected a CRC mismatch. This could be due to the maxClients or other connectionConfig settings not being the same
UnityEngine.Debug:LogError(Object)
MLAPI.Transports.UNET.RelayTransport:BaseReceive(NetworkEventType, Int32, Int32&, Int32&, Byte[], Int32, Int32&, Byte&) (at C:/projects/mlapi/MLAPI/Transports/UNET/RelayTransport.cs:420)
MLAPI.Transports.UNET.RelayTransport:Receive(Int32&, Int32&, Int32&, Byte[], Int32, Int32&, Byte&) (at C:/projects/mlapi/MLAPI/Transports/UNET/RelayTransport.cs:287)
MLAPI.Transports.UNET.UnetTransport:PollEvent(UInt64&, String&, ArraySegment`1&, Single&) (at C:/projects/mlapi/MLAPI/Transports/UNET/UnetTransport.cs:93)
MLAPI.NetworkingManager:Update() (at C:/projects/mlapi/MLAPI/Core/NetworkingManager.cs:650)
The Fixed UNET configuration loading did not solve mine.

Could you please post your Relay config?

I am new to Networking.
I am sorry if I misunderstood.  Do you mean Relay config.cs?

using MLAPI.Relay.Transports;
using Newtonsoft.Json;
using Newtonsoft.Json.Converters;
namespace MLAPI.Relay
{
public class RelayConfig
{
[JsonConverter(typeof(StringEnumConverter))]
public TransportType Transport = TransportType.Ruffles;
public object TransportConfig;
public ushort BufferSize = 1024 * 8;
public bool EnableRuntimeMetaLogging = true;
public int BandwidthGracePrediodLength = 60;
public int GracePeriodBandwidthLimit = 4000;
public int BandwidthLimit = 2000;
public bool AllowTemporaryAlloc = true;
public int MaxTemporaryAlloc = 1024 * 64;
public ushort ListenPort = 8888;
public uint TicksPerSecond = 64;
}
public enum TransportType
{
    Ruffles,
    UNET
}

}

I am new to Networking.
I am sorry if I misunderstood. Do you mean Relay config.cs?
using MLAPI.Relay.Transports;
using Newtonsoft.Json;
using Newtonsoft.Json.Converters;
namespace MLAPI.Relay
{
public class RelayConfig
{
[JsonConverter(typeof(StringEnumConverter))]
public TransportType Transport = TransportType.Ruffles;
public object TransportConfig;
public ushort BufferSize = 1024 * 8;
public bool EnableRuntimeMetaLogging = true;
public int BandwidthGracePrediodLength = 60;
public int GracePeriodBandwidthLimit = 4000;
public int BandwidthLimit = 2000;
public bool AllowTemporaryAlloc = true;
public int MaxTemporaryAlloc = 1024 * 64;
public ushort ListenPort = 8888;
public uint TicksPerSecond = 64;
}
public enum TransportType
{
    Ruffles,
    UNET
}

}

When you start your relay it will create a config json file in the directory where the executable lives. I need that and also a screenshot of your UnetTransport in the inspector in Unity.

Sorry for misunderstanding. Here is my config file (followed by the screenshot):
{
"Transport": "UNET",
"TransportConfig": {
"Channels": [
"ReliableFragmentedSequenced",
"ReliableSequenced",
"UnreliableSequenced",
"Unreliable",
"Unreliable",
"Reliable",
"UnreliableSequenced",
"ReliableSequenced",
"ReliableSequenced",
"UnreliableSequenced"
],
"MaxConnections": 100,
"ConnectionConfig": {
"PacketSize": 1440,
"FragmentSize": 500,
"ResendTimeout": 1200,
"DisconnectTimeout": 2000,
"ConnectTimeout": 2000,
"MinUpdateTimeout": 10,
"PingTimeout": 500,
"ReducedPingTimeout": 100,
"AllCostTimeout": 20,
"NetworkDropThreshold": 5,
"OverflowDropThreshold": 5,
"MaxConnectionAttempt": 10,
"AckDelay": 33,
"SendDelay": 10,
"MaxCombinedReliableMessageSize": 100,
"MaxCombinedReliableMessageCount": 10,
"MaxSentMessageQueueSize": 128,
"AcksType": 1,
"InitialBandwidth": 0,
"BandwidthPeakFactor": 2.0,
"WebSocketReceiveBufferMaxSize": 0,
"UdpSocketReceiveBufferMaxSize": 0,
"SSLCertFilePath": null,
"SSLPrivateKeyFilePath": null,
"SSLCAFilePath": null,
"ChannelCount": 0,
"SharedOrderChannelCount": 0,
"Channels": []
},
"GlobalConfig": {
"ThreadAwakeTimeout": 1,
"ReactorModel": 0,
"ReactorMaximumReceivedMessages": 1024,
"ReactorMaximumSentMessages": 1024,
"MaxPacketSize": 2000,
"MaxHosts": 16,
"ThreadPoolSize": 1,
"MinTimerTimeout": 1,
"MaxTimerTimeout": 12000,
"MinNetSimulatorTimeout": 1,
"MaxNetSimulatorTimeout": 12000,
"NetworkEventAvailable": null,
"ConnectionReadyForSend": null
}
},
"BufferSize": 8192,
"EnableRuntimeMetaLogging": true,
"BandwidthGracePrediodLength": 120,
"GracePeriodBandwidthLimit": -1,
"BandwidthLimit": -1,
"AllowTemporaryAlloc": true,
"MaxTemporaryAlloc": 16384,
"ListenPort": 8888,
"TicksPerSecond": 64
}

What version of the MLAPI?

I am using MLAPI v12.1.7.
I am not sure whether the version of Unity matters.
For some reasons, I have using Unity LTS 2018.
Please let me know if it is not supported.

I am using MLAPI v12.1.7.
I am not sure whether the version of Unity matters.
For some reasons, I have using Unity LTS 2018.
Please let me know if it is not supported.

Thats the problem. The latest version is designed for MLAPI 0.1.0, if you want to use it for the older 12.1.7 you need to revert this commit: https://github.com/MidLevel/MLAPI.Relay/commit/2270b08c003ac878216dcd9aebe49fb6541695d7

If the latest version may work, I will now upgrade it to 0.1.0 and try again.
For the v12.1.7:
The only changes according to the commit are the codes  from line 69 to 78.
I have tried both the one before that commit and the one after.
Both can not make 12.1.7 work.
Thanks for your advice.


Enable borrowed Json and Form extractors

https://github.com/HFQR/xitca-web/blob/119cfad2da7634055341f161a69c98251ec09508/http/src/util/service/handler.rs#L125
This requires FromRequest to have a mutable state to extract body and be able to reference it later.
Maybe change FromRequet to something similar to:
pub trait FromRequest<'a, Req>: Sized {
    type Type<'b>: FromRequest<'b, Req, Error = Self::Error>;

    type Stash: Default + 'static;
    type Error;
    type Future: Future<Output = Result<Self, Self::Error>>
    where
        Req: 'a;

    fn from_request(req: &'a Req, stash: &'a mut Self::Stash) -> Self::Future;
}

I need to think about this.
The long term goal of the whole set api is to move to async fn in trait for a unified easy to write pattern. Even this means concurrent access have to hide behind some smart pointer.
Besides this FromRequest is in http layer for generic Request type so an additional type could mean a useless &mut () for low level use case.
Maybe we can change how it's exposed at web layer since it has it's own specific implementation of FromRquest which can be &(Req, Stash). The lack of &mut reference is unfortunate but it goes back to point 1. We can't have a concurrent async fn from_request take in &mut Stash anyway.

#202


data logging

is there a way to log button inputs?

Currently there is no logging functionality implemented. It should be straight-forward to add. Pull requests are welcome :)


Support React 15 in 0.13.6

For folks who aren't able to upgrade React Router past 0.13.5 at this time, it would be really nice if 0.13.6 existed with support for React 15. Are you open to this?

I've not seen the entire source code from v 0.13.5  besides a quick look, but I know it relies on old internal modules from pre 15, ( Like this). Eventually it will take some effort to get rid of those if it's invoking deep nested Proptypes or generally proptypes with this. Another thing, of which I don't know if old version uses, is 'withContext' , which is removed from React by now.
Any way or another there's two possibilities, or actually three.

PR's

Someone from reactjs change this up

Bump up to a version that has removed these, but with side effects for users.

FWIW, that got added back with a deprecation warning in 15.0.1 exactly to avoid such breakages.
I can't assert with any certainty without testing, but I don't believe anything in the React 14 compatibility update for the v0.13.x line would be incompatible with React 15, so it's really just bumping up the peer dependency and cutting a release.

We've said before that we're not supporting pre-release versions. That's the price of using something pre-1.0.
That being said, I think the best thing here would be a PR, similar to #2262. I don't think anyone here with  commit access is going to want to drag that branch out of cold storage if they can avoid it.

I'd 👍  a PR.

@lencioni If you'd like support for this, please make a PR. Thanks :)

¯\_(ツ)_/¯
I got struck by a fit of curiosity as to whether it would "just work", for values of "just work" meaning npm test passes.
I believe https://github.com/taion/react-router/commit/66b20d7e0ec3c9754d1b919d42d50105562cf05e is all it takes, but I have no idea whether this would actually work on a real app, since I have nothing that uses React Router v0.13.x.
It might be a starting point if any of you want to put together a proper PR, but I'm not going to make any assertions as to whether it actually works, and I'm probably not going to do this for the next React release. 😛

I just realized I still had my branch sitting around. I'm PRing it as https://github.com/reactjs/react-router/pull/3607, if any of you care.
If not, I'm going to delete the branch.


fix datepicker browser incompatibility issue in challenge form

Fix the datepicker browser incompatibility issue - use boostrap datepicker object for all browsers since native date input type is not recognized by all
Add responsive styling to the challenge form

Nice job.


Specify v1.0.0 of Python springcloudstream module

This is needed to specify the 1.0.0 version of the Python springcloudstream module prior to publishing the tcp implementation as 1.1.0 (a breaking change) to the Pypi repo.  This addresses https://github.com/spring-cloud-stream-app-starters/python/issues/2

Closing as local-processor removed from repo


Get-PbiGroupDatasets not included in PowerBIPS.pds1 file.

Get-PbiGroupDatasets function not included in PowerBIPS.pds1 file and it's not available to use in Powershell.

Please use: Get-PBIGroup w/ the -groupId parameter


VeloVI applied to single-nuclei datasets

Good day! I would like to know whether the model can also be used for nuclei datasets and whether you have had any experience with that. Thanks in advance!

@ccruizm, in theory, you can apply it to single-nuclei data. I played around with it before and results from single-cell and single-nuclei data can differ. You'd have to check the usual assumptions and can use the new metrics to check if RNA velocity can/should be inferred in your case.


[pinmux] Reset wakeup counter upon reconfiguration

Addresses #11194.
The other way we could deal with this would be to document that SW needs to disable the wkup detector first, before changing modes.
That would save us the extra 2-3 flops per wakeup detector.
LMKWYT

Thanks Michael! I do not have any preference @tjaychen would have a better insight than me :)
Either way does not create any verification overhead ;)

@tjaychen should we just document this without actually adding the flops?

@tjaychen should we just document this without actually adding the flops?

o yeah that sounds good to me. Arguably that's probably the desired behavior anyways.

Great! Let me revise this then.

I removed the RTL change and added a note to the docs. PTAL


Include package name in error info when a version is not found.

Prior to this commit, when specifying a package version that cannot
be resolved, but other versions are available, the error message
did not state which what package failed, allowing for confusion.
For example, you might see:
bower ENORESTARGET  No tag found that was able to satisfy 1.0.2

Additional error details:
Available versions: 1.0.1, 1.0.0

After this change, in the above situation the svn and git resolvers
will produce the following:
bower ENORESTARGET  No tag found that was able to satisfy 1.0.2

Additional error details:
Available versions in somelib: 1.0.1, 1.0.0

Thank you


Enumerate tasks based on uxNumberOfItems for freertos task

For some reason I don't understand enumerating based on checking pvNext == pxListEnd fails for me and I get a lot of corruption reports. Enumerating based on uxNumberOfItems works fine and I can enumerate tasks as expected.

@cdleonard , thank you for your contribution!


Add research examples to documentation

Resolves #74
Resolves #75
This PR adds the ALS classification example and the Weston-Havens age regression example to the documentation.

Yes, the paper tags this version from Zenodo.


Add local representation of terrain objects like LocalCostMatrix

We should add a local struct type representing terrain that can be easily converted into, with the appropriate helper functions to handle the fact that the x/y coordinates are reversed compared to the layout of the bytes in a cost matrix.

#443 is a start at this, but incomplete.


Prevents all event except a click event.

Prevents all event except a click event.

Thanks for this. All changes need to be made on the CoffeeScript file and a new JavaScript file should be generated from that. Thanks.


Use indentation-sensitive grammar

Semicolons are easier to parse, but harder on the user. The grammar should allow indentation-sensitive parsing, possibly optionally so (like e.g. Haskell).

Come to think of it, maybe we're lucky and the grammar works just as well without semicolons!

Come to think of it, indentation sensititivity ought to improve parsing errors as well, because too far outdented code because of a forgotten semicolon won't be treated as e.g. another variable argument to the line above anymore.

Turns out this is

tricky to get right
takes away the ability to quickly write one-liners in GHCi
Makes quick source code hacks harder, since they have to adhere to the layout rules

I'm not sure indentation-sensitive grammar alone is a good idea anymore. Combining it with Haskell-style optional semicolons is quite a big feat however, and not good for code simplicity at all.

#56 should be reconsidered if this issue is attempted properly.


AWS CodePipeline pipeline for the tile delivery API

An AWS CodePipeline pipeline for the tile delivery API is configured.
The pipeline is supposed to be triggered when a set of commits is pushed to the master branch but I have not tested yet. Merging this pull request will trigger it.
Currently a GitHub personal access token is stored using AWS Secrets Manager, but I am going to put it into the AWS Systems Manager parameter store later. Because AWS Secrets Manager does not have a monthly free tier.

Unfortunately a SecureString in AWS Systems Manager Parameter Store cannot be used for AWS::CodePipeline::Pipeline.
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/dynamic-references.html#template-parameters-dynamic-patterns-resources


Can't close a subscription node

When using the prisma API, there's no way to stop a prisma.$subscribe.X().node - either for testing subscriptions (without mocking) or for programmatic control over subscriptions in a node process.
Expected behavior
There should be a method to call against the node() response that allows me to stop the subscription.
Versions (please complete the following information):

Connector: Postgres
prisma CLI: prisma/1.25.3 (darwin-x64) node-v10.4.0
OS: OS X High Sierra
<EMAIL_ADDRESS>
<EMAIL_ADDRESS>/Users/remy/Sites/deck/backend
├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>

@remy Thanks for raising this issue. Prisma client returns an async iterator that exposes a return method to perform cleanups.
I create a small demo here to show that the async iterator generated by the Prisma client subscription does indeed expose and respect the return method.
It is the responsibility of the caller of this async iterator to call return when the subscription is stopped, in this case the GraphQL server.
Do you have a reproduction for a specific GraphQL server that leaks subscriptions?

In my full complex app I do, but otherwise no(!)
I've had to give up using subscriptions (I switched to using the alt await
method some time ago). It would frequently miss events and it's needed for
user sign up emails (when their status changes).
I did find that combining UPDATE and CREATE event listening on a
subscription for a particular field completely fails though. It never fires
the create event. You might be able to replicate in a small repo.
On Thu, 21 Mar 2019, 14:35 Divyendu Singh<EMAIL_ADDRESS>wrote:

@remy https://github.com/remy Thanks for raising this issue. Prisma
client returns an async iterator
https://tc39.github.io/proposal-async-iteration/ that exposes a return
method to perform cleanups.
I create a small demo here https://github.com/divyenduz/prisma-3955 to
show that the async iterator generated by the Prisma client subscription
does indeed expose and respect the return method.
It is the responsibility of the caller of this async iterator to call
return when the subscription is stopped, in this case the GraphQL server.
Do you have a reproduction for a specific GraphQL server that leaks
subscriptions?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/prisma/prisma/issues/3955#issuecomment-475254582, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAA1hHN2sBVckVDzOE74j4rrclRE8gxZks5vY5ifgaJpZM4aYjW9
.


[Enhancement] Add edit timeline button next to the TimelineDropdown control in the Editor

Is your feature request related to a problem? Please describe.
No problem, but convenience enhancement. When you place a dialog node into a scene you can select the timeline at the property panel. It would be nice if there would be an edit button that straights jumps into Dialogic timeline edit with the corresponding timeline selected
Describe alternatives you've considered
The current way is: read and remember the name of the timeline you have selected, switch to dialogic tab, go to timeline, search for the correct one and click it.

@coppolaemilio merged, can be closed :)


Problem for running the code on an input video

Hello,
Thank you for this work, I am running the code for an input video with 17935 frames and 10 mins length, 30 fps, while it takes so much time, and it will go to infinite loop, and it will not finish. While for a sample video with 500 frames were ok and finish the running.
Could you please help me what is the problem?
Thank you

I think for this multithreaded streams could be used. Facing a similar use case.


Add support for termsrv.dll 10.0.16215.1000

Hello,
i use the insider preview, so every week, i got a new release of termsrv, and the program doesn't works anymore.
I actually know a bit of programming, so, if you could teach us, im pretty sure we can help you doing the boring part!
Anyway, im uploading the new file.
Thank you.
termsrv.zip

Hello.
There's a link to video tutorial in the README that shows how to add new sections into INI file.
See it and you'll be able to do it.

Gosh, i'll take a week or more to do it, but thnks
hahahah

@binarymaster after installing RDPWrap in this build, the RDP service fails to start with:
Error 577: Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be a malicious software from an unknown source.
Tried disabling completly SmartScreen, Windows Defender, Firewall, but nothing solves it

@binarymaster. Yes, I just tested and the scenario is the same of @dgadelha

Even without the update, just installing the wrap.

Well, it seems like Microsoft introduced this new feature to check digital signature for built-in services.
Try to search how to disable digital signature checking.

Cant find anything for now :/

Disabled driver digital signature enforcement (there was nothing about softwares/files, just drivers), and, unfortunately, the issue persists
C:\WINDOWS\system32>net start termservice
The Remote Desktop Services service is starting.
The Remote Desktop Services service could not be started.

A system error has occurred.

System error 577 has occurred.

Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.

Also, tried the following commands after disabling enforcement at boot:
C:\WINDOWS\system32>bcdedit /set nointegritychecks on
The operation completed successfully.

C:\WINDOWS\system32>bcdedit /set testsigning on
The operation completed successfully.

And, after rebooting, the issue persists.

It seems that in upcoming Windows 10 versions svchost.exe will only load signed service dll files.
The question is if any valid code signing certificate will be accepted or only a Microsoft-internal one.
Probably latter, since the svchost subsystem is not intended for "public use" AFAIK.
And even otherwise, nobody will volunteer to sign the wrapper dll with their code signing cert because MS might ban them.
Does this mean this project has come to an end on Windows 10?

The question is if any valid code signing certificate will be accepted or only a Microsoft-internal one.

Indeed.
Well, it still works with older Windows 10 builds. There are two major issues now.

Microsoft then should offer CAL's for Windows 10 Professional editions...
I set all my clients that rely on connecting to some remote PC's (it's just POS systems) to Business branch,  365 days of prolonging updates, and 30 days of "quality" updates, which I am scared of. It works with 1703, but when and if they cut us the possibility of connecting concurrent users, I don't see any viable alternative then. It's impractical to have Server versions on POS systems.


Randaugment has no tests

We should have unit test coverage for randaugment.

Closing. Tracking elsewhere as low pri


Request: More settings when importing to Sonarr needed

While trying to import my series to Sonarr from My Anime List, i encountered some settings I needed to manually do in Sonnar after the import, something that i know kan be done with some extra plugin settings in the sonarr-list to get it fully automatic.
Whats missing when importing to Sonarr:

Enable "Monitored" (and maybe choose how to monitor, like when adding new series manually)

Its disabled by default

Enable "Use Season Folder"

Its disabled by default

Choose "Series Type"

Its just choosing "Standard" (Not optimal for anime when downloading)

An option for Path and Profile. I dont need it, bout maybe someone will later?

Its more or less choosing the first ting in the list atm.

Config:
tasks:
  MAL to Sonarr:
    all_series: yes
    my_anime_list:
      username: ******
      status:
        - watching
        - on_hold
        - dropped
        - plan_to_watch
      type: series
    list_add:
      - sonarr_list:
          base_url: http://localhost
          port: 8989
          api_key: ******

Additional information:

Flexget Version: 2.10.22
Python Version: 3.6
Installation method: pip
OS and version: Windows 10

Nice to know people are even using this 😄

Please reopen in feathub


Added Cucumber web for iOS to run through appium on simulator

@sebv @bootstraponline  I have fixed your review comment. I have removed calaculator2.feature in iOS as it is redundant.
Let me know your thoughts.

@bootstraponline  Fixed your comments. i replaced with Selenium::WebDriver::wait
When i tried $driver.wait, i got the following error timed out after 3 seconds (undefined method `call' for nil:NilClass) (Selenium::WebDriver::Error::TimeOutError)

When i tried $driver.wait, i got the following error timed out after 3 seconds (undefined method `call' for nil:NilClass) (Selenium::WebDriver::Error::TimeOutError)

That means something is wrong in the initialization of the driver. $driver shouldn't ever be nil. Maybe try an unprefixed wait as seen in this working example.


Make list of items in InfoStation scrollable

Adding more than about 10 items in an InfoStation instance results in additional items being hidden.  Ideally the list of items should be scrollable, in the same way that the text of each item already is if it goes over a page.
We have a project where we have many more than 10 items, and this is a showstopper for us.

Actually, seems like an easy fix.
--- infostation.css_ORIG        2024-04-22 12:11:58.222395113 -0400
+++ infostation.css     2024-04-22 12:12:01.914452375 -0400
@@ -201,4 +201,5 @@
 #buttonRow {
   height: calc(6vmax * var(--button-rows));
+  overflow-y: scroll;
 }

I am not a web developer -- just figured this out from some creative searching. :-)

Hi @David-S-Morgan, thanks for another good bug report! None of our uses so far have had enough tabs to trigger this situation (seems to be 10 tabs in the default text size).
InfoStation needs to handle both the cases of a horizontal orientation (where your solution is right!) and vertical orientation (where tabs could stack into multiple rows or scroll horizontally). But that doesn't seem tricky.
I've fleshed this out in a new Issue on the Exhibitera repo (where we have moved development to):
https://github.com/Cosmic-Chatter/Exhibitera/issues/1

Thanks! I'll mark this as closed and see you over on the other GH page.


Raw query failed. Code: 42601. Message: db error: ERROR: syntax error at or near "$1" Postgresql INTERVAL

Bug description
const time = 5

await this.prisma.$executeRaw`
UPDATE public.user SET chat_banned_time = NOW() + INTERVAL '${time} MINUTES' WHERE id = ${userId}
`;

PrismaClientKnownRequestError:
Invalid `prisma.executeRaw()` invocation:

  Raw query failed. Code: `42601`. Message: `db error: ERROR: syntax error at or near "$1"`
    at Object.request (C:\disapp\api\node_modules\@prisma\client\runtime\index.js:45629:15)
    at async Proxy._request (C:\disapp\api\node_modules\@prisma\client\runtime\index.js:46456:18)
    at async Service.handler (C:\disapp\api\services\player\chat\chat.service.js:581:22)
    at async Service.callAction (C:\disapp\api\node_modules\moleculer-web\src\index.js:636:16)
    at async C:\disapp\api\node_modules\moleculer-web\src\index.js:461:22 {
  code: 'P2010',
  clientVersion: '3.13.0',
  meta: {
    code: '42601',
    message: 'db error: ERROR: syntax error at or near "$1"'
  }
}

How to reproduce
const time = 5

await this.prisma.$executeRaw`
UPDATE public.user SET chat_banned_time = NOW() + INTERVAL '${time} MINUTES' WHERE id = ${userId}
`;

Expected behavior
No response
Prisma information
model User {
  id               Int              @id @default(autoincrement())
  chatBannedTime   DateTime?        @map("chat_banned_time")
}

Environment & setup

OS:
Database:
Node.js version:

Prisma Version
"prisma": "^3.13.0"

Same trouble

i have a similar issues.
const result = await this.prismaService.$queryRaw(Prisma.sql${raw})
above line return the same error as yours.
i also tried
 const result = await this.prismaService.$queryRaw${raw}
but return the same error.
this is my raw content
        let rawSU: string = "SELECT type, null as hotel_id, action, old_value, new_value, change, creator_type, created_by, created_at FROM system_user_activity_log"
        let rawSC: string = "SELECT type, null as hotel_id, action, old_value, new_value, change, creator_type, created_by, created_at FROM system_configuration_log"
        let rawHS: string = "SELECT type, hotel_id, action, old_value, new_value, change, creator_type, created_by, created_at FROM hotel_subscription_log"

        let from: string
        let to: string
        if (query.change) {
            rawSU = rawSU + ` where change like '%${query.change}%'`
            rawSC = rawSC + ` where change like '%${query.change}%'`
            rawHS = rawHS + ` where change like '%${query.change}%'`
        }
        if (query.user) {
            rawSU = rawSU + ` and where change = ${query.user}`
            rawSC = rawSC + ` and where change = ${query.user}`
            rawHS = rawHS + ` and where change = ${query.user}`
        }
let raw = `${rawSU} UNION ALL ${rawSC} UNION ALL ${rawHS}`
        raw = raw + ` offset 0 limit 10`
        // const result = await this.prismaService.$queryRaw(Prisma.sql`${raw}`)
        const result = await this.prismaService.$queryRaw`${raw}`

but if i copy the content of raw it's working fine.
const result = await this.prismaService.$queryRaw(Prisma.sql`SELECT type, null as hotel_id, action, old_value, new_value, change, creator_type, created_by, created_at FROM system_user_activity_log UNION ALL SELECT type, null as hotel_id, action, old_value, new_value, change, creator_type, created_by, created_at FROM system_configuration_log UNION ALL SELECT type, hotel_id, action, old_value, new_value, change, creator_type, created_by, created_at FROM hotel_subscription_log offset 0 limit 10`)

Can reproduce in 3.13.0 but not in 4.0.0 or current internal dev version.
This seems to be already fixed. Please upgrade your version.
Note: a workaround would be to use $executeRawUnsafe() like
 const test1 = await prisma.$executeRawUnsafe(`
  UPDATE "User" SET chat_banned_time = NOW() + INTERVAL '${time} MINUTES' WHERE id = ${userId}`);

I can reproduce in 4.0.0 and in 4.3.1.
My query is way more complex and it was working with 3.x

Maybe share your query with us then so we can try to reproduce? Optimally open a new issue and provide all the information the bug issue template is asking for.

I am unfortunately not able to do that in next few days.
Anyhow it would not be the query I would have to share, but the generation using template strings.
Queries are generated, by a function. Table names are dynamically added and some conditions based on functions params will be added.
Though, it is now working with prisma.$rawQuery and actually that is totally fine. My queries are for calculating statistics and filling other tables. None of the params are changeable by any user.

I'm having the same problem with queries such as
prima.$execureRaw`CREATE SCHEMA "${schemaName}"`
prima.$execureRaw`CREATE TABLE "${tableName}"`
on version version 4.3.1
wrapping them on Prisma.sql, such as Prisma.sql`${schemaName}` has the same result
they end up creating a schema/table with the name "$1" if i wrap them on quotes, or error when I don't (syntax error at or near "$1")

Same for you then @patrickJramos:

Optimally open a new issue and provide all the information the bug issue template is asking for.

Any updates on this?

@fP4rad0x  @kivi  use queryRawUnsafe to fix the issue.

See my previous message @fP4rad0x. There will be no more updates in this closed issue.

I am not sure why this was closed.  It is a very easily reproducible bug even in V5.0.0.  It does not actually crash anymore, but the result of date-field  = NOW() + INTERVAL '${days} days' does not give you the result you expect.  It seems no matter what days contains, date-field will end up as todays date. It only works without a variable - like 14 days

@kpturner Please open a new issue about your original query that did not work, and we can dig into that. Thanks.

For some reason, Prisma does not accept the use of variables for table names and field names.
One way I found to solve this problem was to use an auxiliary variable to assemble the query and then use this variable with queryRaw.
See an example below:
const query = `
  SELECT * FROM "${options.table}"
  WHERE "${options.column}" = '${value}'
`;

const row: any[] = await prisma.$queryRaw`${Prisma.raw(query)}`;

Important:

If the name of the table or field contains double quotes, they must be placed in the query.
It is necessary to use Prisma.raw() for the query to work.

Not any of the OPs, but I think almost every one of the issues described here are byproducts of not understanding how Prisma injects query parameters.
For instance, @lucasjribeiro - if you want to have a dynamic table value, there isn't any database engine which can parameterize it (which is what you're doing).  As an alternative, try something like this:
    const query = Prisma.sql`
      SELECT * FROM "${Prisma.raw(options.table)}"
      WHERE "${Prisma.raw(options.column)}" = ${value}
    `;

    const row: any[] = await prisma.$queryRaw(query);

You need to provide the actual, raw values (without parameterization) for anything which isn't a value.  If you had a dynamic function, that also needs to be injected raw without parameterization.  If you just template the values into the query they'll all be treated as parameters which is invalid syntax.
Same for @kpturner - your date-field  = NOW() + INTERVAL '${days} days' sample would need to make your days parameter raw since you're already quoting it (e.g. date-field  = NOW() + INTERVAL '${Prisma.raw(days)} days').  If you wanted it to be parameterized, you could've just concatenated the interval string like this: date-field  = NOW() + INTERVAL concat(${days}, 'days').
And same for @patrickJramos where both the schema and the table references need to be raw.
Even the OP had this problem in their query: UPDATE public.user SET chat_banned_time = NOW() + INTERVAL '${time} MINUTES' WHERE id = ${userId} should have been UPDATE public.user SET chat_banned_time = NOW() + INTERVAL concat(${time}, ' MINUTES') WHERE id = ${userId} since the interval function expects a single interval string spec.
All of that being said, @janpio - maybe it'd be worth just creating a Prisma.identifier type which behaves similarly to Prisma.raw just to make it clearer that there are scenarios where a template variable isn't going to play well with parameterization.  Worth noting, parameters can actually be applied to identifiers in certain scenarios (e.g. here's the Postgres doc on that).
It'd also be amazing if any more information can be logged when a raw query fails.  At the moment the error doesn't even provide the failing query content so it can be incredibly frustrating to triage.  I actually ended up on this ticket for entirely unrelated reasons but the error logging is so generic that any syntax error ends up looking the same.  Maybe there's already a ticket for this?  I'd be happy to create coverage if not.

Those are both excellent suggestions @bsplosion, thanks for taking the time to write it up and trying to help your fellow users.
Do you maybe want to open new issue for both your suggestions and expand even a tiny bit more? Then we can take these into our plannings and make sure they happen (vs. probably loosing them here in this closed issue). Thanks!

@janpio I'll try to put together something soon to cover the suggestions.  On further thought I'm not sure whether it'd be wise to try and do a Prisma.identifier concept since it'll be so frequently inapplicable - it'd be trying to solve for a user education issue but would probably just open its own can of worms.  I think there might already be an existing issue for queryRaw error logging so I'll hunt around for that before creating a new one.

For some reason, Prisma does not accept the use of variables for table names and field names. One way I found to solve this problem was to use an auxiliary variable to assemble the query and then use this variable with queryRaw.
See an example below:
const query = `
  SELECT * FROM "${options.table}"
  WHERE "${options.column}" = '${value}'
`;

const row: any[] = await prisma.$queryRaw`${Prisma.raw(query)}`;

Important:

If the name of the table or field contains double quotes, they must be placed in the query.
It is necessary to use Prisma.raw() for the query to work.

@lucasjribeiro I just wanted to call out an additional major issue with this approach since it looks like several users have upvoted your comment.    This might occasionally be fine if each of those variables are entirely trustworthy, but I'd be surprised.
For instance, if you're using this options table to decide which are available to a user, we could just inject with something like this to get every option from that table: const value = '\' OR 1=1 OR \'\' = \''.  You want to be extremely careful when using Prisma.raw - whenever you apply that, you're just issuing a string and need to sanitize carefully for SQL injection yourself.

For some reason, Prisma does not accept the use of variables for table names and field names. One way I found to solve this problem was to use an auxiliary variable to assemble the query and then use this variable with queryRaw.
See an example below:
const query = `
  SELECT * FROM "${options.table}"
  WHERE "${options.column}" = '${value}'
`;

const row: any[] = await prisma.$queryRaw`${Prisma.raw(query)}`;

Important:

If the name of the table or field contains double quotes, they must be placed in the query.
It is necessary to use Prisma.raw() for the query to work.

Thank you , its worked

Suppose your code has string parameters. then try this. it worked for me
//example 1
let userTable = 'User'
let result = await prisma.$queryRawUnsafe(`SELECT * FROM ${userTable}`)

//my code
const lastMonday = `'${lastMonday}'`;
const thisMonday = `'${thisMonday}'`;

const userInterest =
    await prisma.$queryRawUnsafe<InterestUser>(`Select user_id, SUM(interest_amount) as weekly_amount  from "Interest"
        where
        created_date between ${lastMonday} AND ${thisMonday}
         GROUP BY user_id
         HAVING SUM(interest_amount) > 1`);

This bug still happens

Why is this closed? @Jolg42
I came from the docs on how to run a raw query - nothing works until i looked/read this issue.
Please either fix this or update the docs on having to use these strange methods

This issue still existing on INTERVAL queries


baddish, genecological

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[b,g]

/trunk merge


Gridded lapse rate plugin

Converted application of gridded lapse rate into a plugin so as to make use of the abstract base class functionality for updating post-processed attributes.
Testing:

[x] Ran tests and they passed OK

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver_tests/lapse_rate/test_ApplyGriddedLapseRate.py  2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver_tests/lapse_rate/test_ApplyGriddedLapseRate.py  2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 1

Complexity increasing per file
==============================
- improver_tests/lapse_rate/test_ApplyGriddedLapseRate.py  2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver_tests/lapse_rate/test_ApplyGriddedLapseRate.py  2

See the complete overview on Codacy


When to shop when you're at risk

If you can afford to have groceries delivered, or can have someone shop for you, so.
Else, if you are elderly or immunocompromised go to the store first thing in the morning when things are less touched.
Some stores are extending their hours for these vulnerable populations.
https://twitter.com/mcuban/status/1239244137834127362

Grocery delivery may not be available right now. My Mom is in the bay area and said her grocery delivery was going to take a week. I looked amazon prime in my area and there were no delivery times available.

related to https://github.com/flattenthecurve/guide/issues/151


Variable height items stretching and compressing in sortable list

Hi guys
We just switched to this package from react-dnd and while initially it seemed great, we ran into a weird issue when using the sortable context/hook.

It seems that when having variable height items in a list, the dragged items shrinks or stretches depending on the item it hovers over.
My code is the following:
List:
    <DndContext>
      <SortableContext items={parts} strategy={verticalListSortingStrategy}>

          {parts.map((p) => (
            <PartItem item={p} key={p.slug} bookSlug={bookSlug} />
          ))}
          <FormCreate bookSlug={bookSlug} />

      </SortableContext>
    </DndContext>

Item:
export function PartItem(props) {
  const { item } = props;

  const { attributes, listeners, setNodeRef, setActivatorNodeRef, transform, transition } =
    useSortable({
      id: item.id,
    });

  const style = {
    transform: CSS.Transform.toString(transform),
    transition,
  };

  return (

            <DragIndicator className="w-4 h-4 text-gray-500 " />

            {item.title}

        <OptionsMenu part={item} />

        <NestedPartList items={item.children} />

  );
}

I tried adding a specific height but that also didn't work. Any help would be greatly appreciated!

@reinvanimschoot I was having a similar issue and this helped to solve it - https://github.com/clauderic/dnd-kit/issues/117

The items are stretched because you're using CSS.Transform.toString(), use CSS.Translate.toString() if you don't want to have the scale transformation applied.

Hope this helps!

 Thank you very much!

disabling this prop also solved my issue:
<DragOverlay adjustScale>

I am also facing the same issue with @dnd-kit/core 6.0.8

how to apply adjustScale to the useSortable?


1530: Change warning text in the application form

Short description
Change warning text in the application form when the applicant and the approver are identical
Side effects
no?
Resolved issues
Fixes: #1530
Fixes: #1490

Added commit for #1490, as this is also a minor adjustment to the application form


[Bug]: Loader data gets undefined when an error is thrown in a child route

Which Remix packages are impacted?

remix (Remix core)

What version of Remix are you using?
1.0.3
Steps to Reproduce
I couldn't reproduce the bug with the remix template on Codesandbox, but this happens 100% of the time with the Remix Jokes tutorial. You can watch the bug in action at this moment in @kentcdodds's lifestream yesterday. He asked if someone could open up an issue for it, so here I am.
I have created a public repo on Github with the code you are supposed to have when you have been following along the Jokes tutorial, just before beginning the "SEO with Meta tags" part. Here's how to see the bug in action:

Clone this repo
Run npm i
Create a .env file and add DATABASE_URL="file:./dev.db" in it, along with SESSION_SECRET="whatever"
Seed the DB: npx prisma db seed
Run the app: npm run dev
Click "Read jokes", then "Add your own" (or go to http://localhost:3000/jokes/new)
Submit the form
Kaboum!

Expected Behavior
An error thrown in a route action should be caught by the route's error boundary (or the closest one above). The parent's loader data shouldn't become undefined when this happens.
Actual Behavior
The error occurring in the /jokes/new route action function isn't handled by the route's error boundary, instead, the /jokes route loader data becomes undefined, triggering an error that is caught by the root error boundary:
TypeError: Cannot read property 'user' of undefined
    at `{data.user ? (` (./app/routes/jokes.tsx:50:16)
    [...]

I've added empty CatchBoundary to routes/jokes.tsx like this and it fixed it for me.
export function CatchBoundary() {}

Not sure why

Indeed, it fixed it for me too. But I'm definitely keen to know why the loader data becomes undefined when a child route throw an error in the action, if someone got an explanation.

The bug does not need database and secret to be reproduced. Here are slightly faster steps:

check out git@github.com:Xiphe/remix-error-action-loader-undefined.git
run npm install && npm run dev
open localhost:3000/nested/new
Click the button
See Cannot read properties of undefined (reading 'demos') which results from this useLoaderData returning undefined

Found another way of fixing it instead of creating empty CatchBoundary in /jokes you can:

Add <Scripts /> to root.tsx
Use Remix <Form> instead of HTML <form> for delete action.

The way it works <Form> will actually do request via fetch and prevent browser reload. I suspect if action throws error in no-JS environment with full page reload Remix fails to properly load entryContext from which useLoaderData takes its data.

Created a PR with explanation why it works this way.

As a temporary fix I suggest to include placeholder ErrorBoundary and CatchBoundary in parent routes if children can throw an error.

I suspect if action throws an error in no-JS environment with full page reload Remix fails to properly load entryContext from which useLoaderData takes its data.

This makes a lot of sense to me, thanks @andmayorov for the explanation and the PR

Sweet! Thanks to both of you 👏

Hi,
Is there a fix for it (not a temporary fix)?
If not, in the meanwhile, can you add the temporary fix to the docs?

Still happening in 1.3.3 as of March 2022.

Yup, still happening in 1.3.3 as of April 2022.

Same here 👋

Why should empty boundaries be needed? I don't think the official solution should be to add empty ErrorBoundarys to every component with an <Outlet />? Maybe Remix can add that automatically though.
This is still a bug with 1.5.0 with the no-JS server side submit of a form in the Jokes app tutorial.

Still happening in 1.5.1 as of May 2022.

Super confusing, and very frustrating.  part of the Jokes tutorial, and getting errors of not being able to read "user" from undefined when I try to click the delete button. The error happens in jokes.tsx, which is the parent route of $jokeId.tsx and it makes no sense. What does the loader data of the parent route have to do with the child route? How can a child route cause a parent route loader data to suddenly be undefined? That's very confusing, and makes no sense at all to me. Frankly, kind of killed my liking of Remix a bit for now, because I no longer feel I can trust/understand what's going on.
Telling people to throw random catch/error boundaries around is not a solution.
Is this being actually fixed?

@brophdawg11 do we have/can we add a test for this scenario in the @remix-run/router?

@Svish I get that you're frustrated but it sounds like software that has been open sourced for only 6 months is out of your risk tolerance. Workarounds are part of it story in the beginning--always has been, always will be, for every project.
We definitely should have fixed this by now, I agree, but we're not cool with messages like yours. You have three more productive options:

use a different framework
write a failing test case
fix it yourself with a PR

At this stage of my life and career in open source I have a pretty low tolerance level for comments like yours. Happy to have you here but consider this a warning. Please tone it down and be a productive member of the community.

Sorry for the frustration and negativity. Hope you can forgive me.
I was very excited to try out Remix, and got quite bummed out when I ran into this confusing bug while going through the main tutorial (the in-depth one) in the docs. I was prepared for things not being optimal, but was kind of expecting to at least be able to get through the tutorial without hitting a road-block there already. And when I found this bug-report that was reported several months ago, which seemed a bit forgotten(?), I just felt like sharing that frustration because it seems many beginners going through that tutorial run into the very same issue.
Hitting weird bugs like these when going through official beginner-tutorials feels kind of bad, because it's very easy to enter "obviously, it's unexperienced me who must have missed something, I must be dumb, because according to the tutorial that just did, this should be working"-headspace. Could have shared my experience in a less negative and aggressive way though. Sorry again.
Fully aware that this is a very new framework that's still under construction, and also fully aware that there's probably a bunch of other things that are even more important for you guys to get fixed.
I've read about so many awesome features, and loved the presentations you guys had at the recent Remix and Reactathon-conferences. I just wanted to check it out for myself finally, instead of just reading blog posts and watching talks, and finally got the chance on a "look into whatever you want"-day at work today. 🙃
Excited to see how things develop further. Am subscribed to this bug, and will check out the tutorial and try to continue when this issue gets fixed. 🚀👍

@brophdawg11 do we have/can we add a test for this scenario in the @remix-run/router?

I'll take a look and confirm this is handled over there 👍

If you want to run the root loader on 404s you need to match them in a splat route.  Usually you can just render your 404 page from the splat route component.  But if you want to use the error boundary you can also just throw a 404 from the splat route loader: https://stackblitz.com/edit/remix-run-remix-lsjcid


refactor

refactor

[x] clean up root directory
[ ] split up utils.py
[x] cache.py, mylist.py & favourites.py have grown too tightly coupled. db.py to the rescue
[x] remove unnecessary functions
[x] lint

might have to refactor some tables in the database, potentially wiping the users mylist

[x] renamed database from cache.db to tver.db. Besides being the better name this also allows users to recover their previous mylist.


Case when (solar_voltage < battery_voltage + solar_voltage_offset_stop)

I'm a bit confused on how will the solar panel behave when the voltage starts to drop and reach the minimum input voltage of the DC/DC converter. The charging process will stop, then the current will drop and the voltage of the solar panel will rise again.
You placed a 4V hysteresis to prevent charging continuous recycles. ( difference between "solar_voltage_offset_start" and  "solar_voltage_offset_stop")
Can we actually change the cutoff behavior and try to squeeze more power from the panels by trying to reduce the charging current (if possible) until charging current is smaller than the minimum?
another question that's lurking in the back of my mind is: I'm new to this solar panels thing and never tested or worked with any. I'm curious to know what will I lose if I use those 40V max open voltage panels to charge a 12V li-ion battery pack. A buck converter that will shutdown the charging voltage at 12.6+5=17.6V seems an awful decision compared to a buck-boost converter (specifically I'm also studying microchips AN1521 circuit).
I want to ask you, in your opinion, will I face this condition very often? Do you think I'll regret using this circuit over a buck boost converter?
Huge respect mate... your work is more precious than gold

In the current version of the software, I also added a dcdc restart interval of 60s (in addition to the voltage hysteresis). You are completely right. With only the voltage hysteresis, the MPPT might toggle between on and off for some minutes during dusk because the open circuit potential of the PV panel is still too high.
The charging current is measured at the output. When it reaches the minimum cut-off limit, this was already the maximum you can get, as the input is still in the maximum power point.
For a 12V system with 40V panel, the additional yield if the solar voltage can go below the battery voltage (buck-boost converter) is negligible. It's already almost dark under these conditions.
The software is currently under heavy rework in order to integrate the CAN communication. I hope to clean up and upload a new version soon.


Revert "Create NextGreaterElementOnTheRight.java"

Reverts sharduln30/Java#1

Added a new problem. Please review it.


Bump identity apps core version

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/6315670076

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/6315670076
Status: failure


Not available on pypi

The package is not there on pypi, and consequently the pip install command mentioned in README fails.

I haven't published this package quite yet. I'll probably wait until discord.py releases 1.5 in a few weeks. For now, you should be able to do the following:
pip install git+https://github.com/bryanforbes/discord-ext-typed-commands.git@master

I'll leave this open until I publish.

Alright, thanks!

I went ahead and published this package on pypi so installing via pip install discord-ext-typed-commands should work


[main < 869-memgraph-mage-installation-update] Add instructions for dependencies

Description

Added instructions for installation of Rust and Python dependencies

Pull request type
Please check what kind of PR this is:

[ ] Fix or improvement of an existing page

Related PRs and issues
PR this doc page is related to:
(especially necessary if the PR is related to a release)
Closes:
(paste the link to the issue it closes)
https://github.com/memgraph/documentation/issues/869
Checklist:

[ ] Check all content with Grammarly
[ ] Perform a self-review of my code
[ ] Make corresponding changes to the rest of the documentation (consult with the DX team)
[ ] The build passes locally
[ ] My changes generate no new warnings or errors
[ ] Add a corresponding label
[ ] If release-related, add a product and version label
[ ] If release-related, add release note on product PR

I've created the issue in the MAGE repo: https://github.com/memgraph/mage/issues/489. I'll merge the docs, and we can update it again once the MAGE issue is investigated.


Add GitHub Action to execute tests and improve code quality

Add GitHub Actions to the project to ensure, everythings works.

For some reason the Actions are not running: https://github.com/lvgl/lv_i18n/pull/69/checks

Actions are enabled:

It will only run the actions after you merged them into the master branch. Currently they come from my branch and will not be executed until PR is done.
If you have merged, I can issue a new (trivial) PR so that you see, that they get executed.

If you merge this PR (and any other) I would recomment to use "squash", so that my commit history is combined into a single commit

Okay, let's see. :slightly_smiling_face:

Running but failing. :slightly_frowning_face:

I see the problem. Good that we have the GitHub Actions, as there are smaller "lint" bugs. I will sent you PR this evening or tomorrow.


add pagination to the ui

It would be great to split tasks into multiple pages since scrolling becomes a bit painful when there are a lot of deployments

Closed in #94


New release / update v12 tag

Can we please get a new tag here as well, to bubble up the fix for https://github.com/DavidAnson/markdownlint/issues/945 via markdownlint-cli2 to here?

Soon: https://github.com/DavidAnson/markdownlint/blob/main/doc/ReleaseProcess.md

v13 is now available.


What license is this model released under?

Could you please an a LICENSE
Fantastic work on the model! We at Replicate are eager to showcase it on our website. To ensure you're credited correctly, could you please share the license details?

Thank you. I have added the MIT LICENSE to my repo.

Thank you so much :)


Base64 encode the "code" query parameter.

This changes the "code" query parameter to "enc", encoded as URL-safe base64.
The "code" query parameter for unencoded code is still present, allowing old playpen links to remain functional.
Addons such as NoScript would often flag playpen URLs as potential XSS attacks, due to liberal usage of sequences such as <T> in Rust code. Encoding the query parameter prevents this from happening.
Unfortunately, this results in somewhat longer URLs.  However, even with the encoding, the 5000 character limit is still quite permissive for typical playpen usage.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @brson (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see CONTRIBUTING.md for more information.

The reason for the extra layer of encoding is outlined on this page: https://developer.mozilla.org/en-US/docs/Web/API/WindowBase64.btoa#Unicode_Strings
... however I left out the extra usage of unescape, which turns out to be quite significant.  It seems the code on that page intentionally clobbers any unicode characters via unescape() after encoding with encodeURIComponent(), which encodes them correctly.  The reverse is then performed when decoding (re-encode with escape(), then decode it properly via decodeURIComponent() to restore any unicode characters).
The code I submitted should in fact use both functions as currently it will unnecessarily bloat the size of the encoded data.
However, I'm not sure if being totally unicode-safe with the catch of using wholly deprecated functions is worth it.  Regardless, the single extra encodeURIComponent() should not be there without the accompanying unescape().  Perhaps it would be better to include non-internal base64 routines that properly handle unicode?

Could we perhaps take a more conservative route where only the < and > characters are encoded? If that's really the only problem with various extensions, then perhaps that's all that needs to be taken care of?

Forgot about this PR for a while, but ultimately I've reached the conclusion that this isn't really worth it.
The best solution for encoding the flagged characters without bloating the URL that I've come up with is to replace them with the antiquated ASCII control characters (like BEL, ACK, ENQ, etc).  While it would work, I don't really like that solution very much and it just smells very hacky.
NoScript users can add the following exception pattern instead (NoScript Options -> Advanced -> XSS):
^https://play\.rust-lang\.org/\?code=


WIP: resolve issue #36

make the idToReplicaset map immutable by convention
instead, we create an entirely new object instead of updating the old one

need just tests


Add tty debug

really simple tty_debug function that takes a string and writes it to the tty. Infer redirects stdout and stderr internally under some circumstances. This function is only intended to be used for printf-style debugging (hopefully the comment makes that clear).

Sorry for the late reply. It would be good to have something like what you propose. Logging.progress always prints on stderr too, but it's not very discoverable due to the name.
I think it would be better for the new function to be implemented similarly to Logging.progress (or even be a simple alias to it) to be able to take a format string as argument. I'd also prefer a name like Logging.dev_debug to make it clearer that it can be used for debugging in development. If you add a tag [@@deprecated "don't commit this, use Logging.debug instead"] in the .mli it will make sure that uses do not get committed in the repo.
Could you also update the PR to remove changes to the facebook-clang-plugins submodule?

What's the status of this PR?

The idea of this PR is good: it would be useful to have a way to send things to the console without fearing that the output will get swallowed somehow. However, I would like something more involved than what this PR was going for originally, otherwise nothing will guarantee that leftover debugging instructions do not make it into the code base. I think we can close it and I'll send a diff implementing what I suggested.


Move the spdm_device_validator_sample to SPDM-Responder-Validator

Fix: #148

Make the SPDM-Responder-Validator independent.
Delete the CI check for SPDM-Responder-Validator.

The SPDM-Responder-Validator will not be submodule after this PR.
Signed-off-by: Wenxing Hou<EMAIL_ADDRESS>

It seems too many changes in https://github.com/DMTF/SPDM-Responder-Validator/pull/36.
Let's postpone it.


Custom MAC adress

When I try to use a custom MAC Adress for the ESP (I guess it should be possible to do that) I can't acess the input box because something always adds a pointer-event:none to the box and I can not find where this comes from.
If it was planned that you can change the MAC to a custom value this could be a bug if it was not a planned feature see this issue as a feature request.

Hi @Cadybara,
It's not a bug. The custom Mac address feature was intentionally removed for some reason. It will be needed and released in the next update.

okay thanks for the fast answer and this usefull repo


[SPARK-13976][SQL] do not remove sub-queries added by user when generate SQL

What changes were proposed in this pull request?
We haven't figured out the corrected logical to add sub-queries yet, so we should not clear all sub-queries before generate SQL. This PR changed the logic to only remove sub-queries above table relation.
TODO: for long term, we should find a way to add sub-queries correctly, so that arbitrary logical plans can be converted to SQL string.
How was this patch tested?
LogicalPlanToSQLSuite

cc @liancheng @yhuai

Test build #53435 has started for PR 11786 at commit ee5a437.

Test build #53435 has finished for PR 11786 at commit ee5a437.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53435/
Test PASSed.

How about we add a before/after comparison in the description (show the difference of the generated query)?

LGTM

merging to master!


save modification variable to file, and refresh variable in memory

Hello, I am a Kettle fan from China
When I develop plugins, sometimes I want to save variables to the kettle.properties file in real time, but it seems that no similar tools are provided? So I wrote this method

:white_check_mark: Build finished in 22m 54s
Build command:
mvn clean verify -B -e -Daudit -amd -pl core

:ok_hand: All tests passed!
Tests run: 4845, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message


Data used for training and validation in the paper

Can you please provide the exact subsets of the data that was used for training the EndoSfM learner models? I would be very grateful if you pointed me to the subsets that have been used for training and validation, and also for the trajectory plots as predicted by the Pose estimation network.
The paper states: "The training and validation dataset consist of 2039 and 509 colon images generated in the Unity simulation environ- ment, respectively." Can you please provide this subset?
Thank you.

I am also curious about the training and verification data because I found that these data are not included in the Endoslam provided.


Remove Sendable diagnostics for nonisolated declarations.

Non-isolated declarations in general do not require Sendable
diagnostics. However, we do need to make sure that nonisolated let
accesses to actor-isolated state are always cross-actor.
Fixes rdar://83371627.

@swift-ci please smoke test


docker-compose v3 and index of the compose file reference

Problem description
PR #11744 creates a regression:
the item "Version 3" point to the https://docs.docker.com/compose/compose-file/ instead of https://docs.docker.com/compose/compose-file/compose-file-v3/

Problem location

I saw a problem on the following URL: https://docs.docker.com/compose/compose-file/

Suggestions for a fix

I'm having the same issue, was very confused until I got it from the wayback machine.

Temporary workaround for anyone looking for the v3 reference: visit the link directly.
At the moment, the v3 reference doesn't seem to be accessible from the menu and at least some search engines.

This is fixed by https://github.com/docker/docker.github.io/pull/11959, which will be published to docs.docker.com soon

This is fixed by https://github.com/docker/docker.github.io/pull/11959, which will be published to docs.docker.com soon


Fix intermittent failure in TestManageResults

I believe that this change will fix the intermittent failure in TestManageResults.
If two status updates come in at the same time for the same file, then we would create two FileProgress controls. Also, we would throw a "item with the same key already added" exception, and that would get displayed as an import failure error.
(This error was made possible between the work I did to make the AllChromatogramsGraph a little faster when importing thousands of files at once: the controls get added to flowFileStatus with one "AddRange" call instead of one at a time. The fact that I moved the adding to "_fileProgressControls" made it possible to create controls for the same URI more than once, but it could only happen if we were processing two statuses for the same URI in the same batch, which I think only became possible to happen because of this 3array work)

Seems proper - a small enough change, certainly.


No Releases ?

There aren't any public releases to install the studio SDK ..
https://github.com/TIBCOSoftware/tci-webintegrator/releases/download//wi-studio.tar.gz

Hi! We noticed a small error so we had to change the zips. The releases are back again now


More code examples of int.publish function

Really awesome, thank you. Got the example working, (Esp8266 to Mosquitto server) but having difficultly tayloring the example. I combined the DHT(Temp/humidity sensor) Sketch and it compiled and prints out all of the data to serial but can't publish through MQTT just to serial. Get an error because of float variable when I play with the client.publish function. Can we not publish a float variable?...(Temp and Humidity), Can you provide some tips/examples for publishing? Ideally float data i.e. from the DHT sensor(See last section (void loop) of code below, I want to build a motion, Relay, light sensor and will comment and contribute these examples)
#include <ESP8266WiFi.h>
#include <PubSubClient.h>
#include "DHT.h"

DHT dht;
WiFiClient espClient;
PubSubClient client(espClient);
long lastMsg = 0;
char msg[50];
int value = 0;

const char* ssid = "XXXXX";
const char* password = "XXXXXXX";
const char* mqtt_server = "XXXXXXXXX";

//setting up Wifi

void setup_wifi() {

  delay(10);
  // We start by connecting to a WiFi network
  Serial.println();
  Serial.print("Connecting to ");
  Serial.println(ssid);

  WiFi.begin(ssid, password);

  while (WiFi.status() != WL_CONNECTED) {
    delay(500);
    Serial.print(".");
  }

  Serial.println("");
  Serial.println("WiFi connected");
  Serial.println("IP address: ");
  Serial.println(WiFi.localIP());
}

void callback(char* topic, byte* payload, unsigned int length) {
  Serial.print("Message arrived [");
  Serial.print(topic);
  Serial.print("] ");
  for (int i = 0; i < length; i++) {
    Serial.print((char)payload[i]);
  }
  Serial.println();

  // Switch on the LED if an 1 was received as first character
  if ((char)payload[0] == '1') {
    digitalWrite(BUILTIN_LED, LOW);   // Turn the LED on (Note that LOW is the voltage level
    // but actually the LED is on; this is because
    // it is acive low on the ESP-01)
  } else {
    digitalWrite(BUILTIN_LED, HIGH);  // Turn the LED off by making the voltage HIGH
  }

}

void reconnect() {
  // Loop until we're reconnected
  while (!client.connected()) {
    Serial.print("Attempting MQTT connection...");
    // Attempt to connect
    if (client.connect("ESP8266Client")) {
      Serial.println("connected");
      // Once connected, publish an announcement...
      client.publish("outTopic", "Reconnecting");
      // ... and resubscribe
      client.subscribe("inTopic");
    } else {
      Serial.print("failed, rc=");
      Serial.print(client.state());
      Serial.println(" try again in 5 seconds");
      // Wait 5 seconds before retrying
      delay(5000);
    }
  }
}

void setup()  ///Starting the magic
{
pinMode(BUILTIN_LED, OUTPUT);     // Initialize the BUILTIN_LED pin as an output
  Serial.begin(115200);
  setup_wifi();
  client.setServer(mqtt_server, 1883);
  client.setCallback(callback);
  Serial.println();
  Serial.println("Status\tHumidity (%)\tTemperature (C)\t(F)");
dht.setup(13); // data pin 13
}//--(end setup )---

void loop()  //Now the problems
{
  if (!client.connected()) {
    reconnect();
  }
  client.loop();
delay(dht.getMinimumSamplingPeriod());

**#   float humidity = dht.getHumidity();
  float temperature = dht.getTemperature();
**//Testing output on serial
  Serial.print(dht.getStatusString());
  Serial.print("\t");
  Serial.print(humidity, 1);
  Serial.print("\t\t");
  Serial.print(temperature, 1);
  Serial.print("\t\t");
  Serial.println(dht.toFahrenheit(temperature), 1);
  long now = millis();
  if (now - lastMsg > 2000) {
    lastMsg = now;
    ++value;
   snprintf (msg, 75, "hello world #%ld", value);
    Serial.print("Publish message: ");
    Serial.println(msg);
**    client.publish("Current Humidity","Humidity", humidity);
    client.publish("Current Temperature","Temperature", temperature);

**  }

}

Hi,
there's an example of how to publish a float value here: http://forum.arduino.cc/index.php?topic=241222.0
You have to convert it to a String first.
Nick

Thank you Nick, that helped, I have added the new example and will commit

Thank you again Nick,
Updated the post you referred to below to include the example.
http://forum.arduino.cc/index.php?topic=241222.0
From: knolleary<EMAIL_ADDRESS>Sent: Friday, February 26, 2016 1:19 AM
To: knolleary/pubsubclient<EMAIL_ADDRESS>Cc: Kerr1st<EMAIL_ADDRESS>Subject: Re: [pubsubclient] More code examples of int.publish function (#134)
Hi,
there's an example of how to publish a float value here: http://forum.arduino.cc/index.php?topic=241222.0
You have to convert it to a String first.
Nick
—
Reply to this email directly or view it on GitHub https://github.com/knolleary/pubsubclient/issues/134#issuecomment-189181182 .  https://github.com/notifications/beacon/AQVdWOiOCO7iVxckkNQPOqaFchL_4KHPks5poA_tgaJpZM4HjiYg.gif


Build fix when using a C compiler

Check if __cplusplus is defined before checking its value.
Signed-off-by: Leandro Pereira<EMAIL_ADDRESS>

Patch is good but unnecessary.
Prior to evaluation, macro invocations in the list of preprocessing tokens that will become the controlling constant expression are replaced (...), just as in normal text. [...] After all replacements due to macro expansion and the defined unary operator have been performed, all remaining identifiers are replaced with the pp-number 0, and then each preprocessing token is converted into a token.

So an undefined __cplusplus will expand to 0. Since the check is for larger than a non-zero quantity, this should not break the build.

@thiagomacieira commented on Sep 25, 2015, 12:44 PM GMT-3:

So an undefined __cplusplus will expand to 0. Since the check is for larger than a non-zero quantity, this should not break the build.

Tell that to GCC 5.1.1. :)

No problems here with GCC 5.2.1. What exactly is wrong?

I'm closing this PR.
I'm building TinyCBOR as part of Soletta which uses -Wundef by default -- and I always develop with -Werror on:
error: "__cpp_static_assert" is not defined [-Wundef]
 #if __STDC_VERSION__ >= 201112L || __cplusplus >= 201103L || __cpp_static_asser

I'm adding -Wno-undef for TinyCBOR in the Soletta build as this is harmless; the exception will be removed as soon as TinyCBOR's Makefile is used.


added DnsDB Data Source

PR for adding DnsDB Data Source

@himanshudas Thanks for making this PR. I already checked out your Fork and was going to merge it myself if you couldn't do it soon :).
Thanks for contributing to the tool

@himanshudas Did you copy paste my own code which i wrote earlier ? Which was not working By the way?

It doesn't even works


Update README.md

Thanks, @jdime, and welcome to the contributor club!

Thanks, @jdime, and welcome to the contributor club!

Thanks for keeping up this great initiative!


Who gets messages sent to<EMAIL_ADDRESS>

I think it would be good to clarify who (precisely) are the people who get an email when a message is sent to<EMAIL_ADDRESS>and possibly outline a process whereby people get added and taken off this list.

Any maintainer can, in principle, check this account. I'm not sure how many actually do check it regularly.
https://github.com/bids-standard/bids-specification/blob/master/Maintainers_Guide.md#current-bids-maintainers

At this moment it's at least any maintainer and also me. I was recently added related to the payment for the election system we are using.
If this is our point of entry for COC complaints, it needs to be pretty clear who can see these. Alternatively, I wonder if we need to have one specific designated person as the point of contact for CoC complaints, so it's very clear whether there is any potential for conflict. The revised CoC will also include a list of alternative people. Yet another option is to say: "you can contact any of these people individually or by cc'ing several of them on your message", so people registering a complaint can choose how to go about it.

I guess I would say let's have a list of contact people rather than a shared address. I would suggest we should have at least a maintainer and a steering group member at all times, avoid clustering at any given institution, and ideally not all be male. I'm okay being listed as an point of contact.

Any reason for the "potential contact" list not to be all of the maintainers and all SG members?


Code completion functional

@devoncarew @lukechurch

#570

lgtm; one question about potentially unused vars.

#575 Bug that came up while testing
Merging.


Source-archive-based cross-project dependencies broken

After the changes in ceylon/ceylon to support namespaces, the source archive of a required project is not found. The error is the following:
module.ceylon(4,11): cannot find module artifact referencedCeylonProject:1.0.0-.src.car
	- dependency tree: mainModule/1.0.0 -> referencedCeylonProject/1.0.0

To me it seems as if referencedCeylonProject:1.0.0 is passed as a module name somewhere with either a null or empty version string. (Artifact names are normally built up from name + "-" + version + suffix). The .src.car is really weird though.

In fact the ArtifactContext constructor call with 3 arguments didn't change, but the meaning of the three arguments did change since the addition of namespace at the first place. By the way I already fixed it but didn't push for now.

I've already fixed that some times ago


JavaScript heap out of memory

We recently update sassc from 2.2.1 to 2.4.0 to fix #146
It worked fine but a new issue appeared since then that I suspect to be related to sassc.
When we build the assets of our project on computers with 2 Gb of RAM, the compilation fails with one of the following error message:
<--- Last few GCs --->
[56:0x7f30929e52a0]   490833 ms: Mark-sweep (reduce) 995.6 (1002.6) -> 994.9 (1004.1) MB, 2029.7 / 0.0 ms  (average mu = 0.089, current mu = 0.023) allocation failure scavenge might not succeed

<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

The compilation succeed on computers with 4 Gb of RAM. Previously, using sassc 2.2.1 we had no issues with only 2 Gb of memory.
Steps to reproduce :
run this script on a computer with 2 Gb of available memory, it will fail during the assets compilation phase.

the error comes from some JavaScript engine (I guess it could be a js minifier / parser?). This gem uses C extensions, but it has nothing to do with JavaScript, so I think the problem lies elsewhere.

Ok thanks for your reply, I will check on that side.


Install clang in our runner image

Currently clang/clang++ is not installed in our self-hosted runner.
Please help to rebuild the image and redeploy the runner.
https://github.com/intel/graph-compiler/blob/23269d7882419924ff1f4290e2668468ba1525db/.github/dockerfiles/runner/Dockerfile#L12-L17

Ok, will do

What about moving the build to clang? It seems a bit faster.

Rebuilt runners with clang, testing it here https://github.com/intel/graph-compiler/actions/runs/10743821428

I have also unified pvc and cpu runner images, the only difference now is in /dev/dri/renderD128 access

for nightly test


Update Developer Guide with Target User Profile, Value Proposition and User Stories

Codecov Report

Merging #30 (825045c) into master (c4d50eb) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #30   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Refreshing a page with a route that has Portals leads to an Invariant Violation exception

Version
4.3.1
Test Case
https://codesandbox.io/s/82zwpzjr80
Steps to reproduce
In the codesandbox example, if you route from /home to /about via the links, then it's all fine. However, if you are on the about page and then do a refresh, then you get the following exception:
Invariant Violation
Target container is not a DOM element.

I would imagine that portalling to a DOM node that's a route that's not rendered would not be possible, but the div that's being portalled to in this case is outside of the router.
Expected Behavior
I expect to be able to use Portals to DOM nodes outside of the route where I use a portalled component in.
Actual Behavior
Refreshing the page leads to an error

This isn't a React Router issue. You're attempting to select an element in the DOM that does not exist.
Your provided code works when navigating from home to about because the element is rendered into the DOM at that point.
You should either a. add an element outside of your React tree to create the portal to or b. create a new element like they do in the portals guide.

// b
class BottomBar extends React.Component {
  constructor(props) {
    super(props);
    this.el = document.createElement("div");
  }
  render() {
    return ReactDOM.createPortal(<Thing />, this.el);
  }
}

If you have any other support issues, please use StackOverflow or Reactiflux. The issues section here is intended for bug reports, while those venues are setup for helping people with implementation problems. Thanks!


Unit Deployment Management

How to deploy Units. Select unit in UI and deploy it, and it will be instantiated to specific position. NOTE: do we have resource management as own feature?

Yes, resource management as its own feature please. Keep the tickets as small as possible.


[C++] Provide a Sync() abstraction on writable file abstractions provided in arrow::io

Describe the enhancement requested
Operating systems don't immediately commit data provided by userland code into storage devices. This is usually not a problem because (1) the kernel will not take very long to asynchronously commit the data on its own, (2) the kernel mediates access to the filesystem and guarantees all processes sees the writes performed to the same file so far [1], and (3) applications can handle missing data due to power loss or kernel crashes (e.g. a file used for caching getting corrupted can be easily re-downloaded).
Applications with more stringent durability requirements (e.g. SQLite) will force commit of pending data on the kernel by calling fsync on transaction commit. But even databases avoid doing this for every file and opt to fsync only a special file storing the Write-Ahead Log [2] containing batched updates. Don't think of Sync() as a flushing mechanism that you should always call —fsync can add a lot of unnecessary latency (in the many hundreds of milliseconds) and wear down storage devices.
Network and Distributed File Systems
Networked file systems usually provide commands that ensure durability of the pending writes on the server storage media — Sync would delegate to these commands in these cases.
Distributed filesystems that rely on data replication might provide operations to ensure writes are propagated before returning (Quorum Writes). Since late 2020 this is not an issue with AWS S3, so Sync on S3 [3] files would be a no-op.
Masking Latency
If you must issue Sync calls, one way to mask the latency caused by them is to issue writes as soon as possible, do some other work, and only then call Sync.
file.Write(data);
file.Write(more_data);
FunctionThatTakesSomeTimeAndDoesUsefulWork();
file.Sync();  // it's very likely the kernel has no pending data on file at this point and `Sync` will return quickly
// more work with file and possibly another Sync
file.Close()

[1] exceptions to this exist with the use of flags like O_DIRECT on Linux's open syscall https://www.man7.org/linux/man-pages/man2/open.2.html
[2] then in the event of a power loss, the database can replay the write-ahead log and complete any missing write to the more complex structures of the database like indexes
[3] https://aws.amazon.com/blogs/aws/amazon-s3-update-strong-read-after-write-consistency/
Component(s)
C++

Let's call it ExpensiveDataSync?

we want to call out that this would synchronize the file data, not necessary its directory metadata (which on some filesystems /OSes at least would require a different system call?)

My understanding of fsync() man page is that you have to also call it on the directory.

As well as flushing the file data, fsync() also flushes the metadata information associated with the file (see inode(7)).
Calling fsync() does not necessarily ensure that the entry in the directory containing the file has also reached disk.  For that an explicit fsync() on a file descriptor for the directory is also needed.

Either way, maybe you could add the details of what is used under the hood for each implementation?

@pitrou Would DurableSync() be OK? ExpensiveDataSync() still sounds like something you should call at least once. DurableSync(), by sounding cryptic, can deter people who don't understand the semantics from calling it (hopefully).

Ok, then DurableDataSync? :-)

My understanding of fsync() man page is that you have to also call it on the directory.

That depends what your needs are? Since I don't know how SSD-to-GPU works, it's difficult to know if that's what you want.
Also, regardless, FileOutputStream does not have any knowledge of the directory it writes in...

@pitrou DurableDataSync might be too close to the fdatasync syscall whereas DurableSync makes the definition of "sync" more open to what's more adequate to each implementation.
@NicolasDenoyelle the answer about the directory question is easy: no.
Reasons: as @pitrou said, (1) a file handle doesn't (can't) have a reference to the directory it's currently in (imagine how hard that would be in a multi-threaded environment!), and (2) an application that needs the directory entry update might have multiple files to sync and it should sync all files before it syncs the directory and it should do that once.
You should also note that fsync doesn't eschew the app from doing its own concurrency control. If you fsync a file, then another thread updates that file, before you fsync the directory, you could fsync the directory with inconsistent data. It's the application's responsibility to prevent that.

Well, the manpage seems to indicate that fdatasync is what we want here?

fdatasync() is similar to fsync(), but does not flush modified metadata unless that metadata is needed in order to allow a subsequent data  retrieval  to be  correctly  handled.   For example, changes to st_atime or st_mtime (respectively, time of last access and time of last modification; see inode(7)) do not require flushing because they are not necessary for a subsequent data read to be handled correctly.  On the other hand, a change  to  the  file  size (st_size, as made by say ftruncate(2)), would require a metadata flush.

+1 on this idea. And from description, seems it would not have any gurantee on object-store when part-upload enabled?