Input does not display error inside Form.Field with  form control component

Bug Report
Steps
I'm creating a table component with Input, Select and Button elements in the first row.
Click on the button should add new entry to the table.
If one of the values is empty it should set the Input and Select error attribute to true.
When creating a new Form  with  Form.Field control={Component}
and click the add button, the Input element does not display error.
Expected Result
Clicking on the Add button should display error if the Input or Select value is empty
Actual Result
Only the Select error is displayed
Version
0.86.0
Testcase
https://codesandbox.io/s/109y4wx34j

Sorry, but we don't have time to debug your code. Please come with minimal repro case if your issues still exists.
All I see, everything works fine in examples:
https://react.semantic-ui.com/elements/input/#states-error
https://react.semantic-ui.com/modules/dropdown/#states-error

@layershifter This is the most annoying and unprofessional answer I've ever seen.
@tomerjann said specifically that it happens when you use Input inside a FormField, not by itself,
and it still happens today, August 2020!
The examples / documentations are not cover this case.
EXPLANATION OF THE BUG:
.ui.form input[type=text] style is overriding the .ui.input.error>input style,
so you don't see the error style when using Input inside Form.Field.
Pretty easy to fix, but I guess you just don't have the time 🤷♂

@layershifter This is the most annoying and unprofessional answer I've ever seen.

I asked for a minimal bug reproduction as the original CodeSandbox contained too many things. And never got a response...

The examples / documentations are not cover this case.

Please provide a minimal repro case as it still unclear what happens 🤦
  <Form>
    <Form.Input error />
    <Form.Select error />
  </Form>

  <>
    <Input error placeholder='Search...' />
    <br />
    <Select error />
  </>

  <Form.Field>
    <Input error placeholder='Search...' />
  </Form.Field>

This one is not working, I don't know how it works for you.
I attached a screenshot of the CSS conflicts.
<Form.Field>
    <Input error placeholder='Search...' />
</Form.Field>

@adamhazon you export any example in one click to CodeSandbox and then edit it, this will definitely simplify the conversation and will clarify the issue 🙏

So styles will collide only in this case:
<Form> {/* <- Form is required */}
  <Form.Field>
    <Input error placeholder="Search..." />
  </Form.Field>
</Form>

https://codesandbox.io/s/laughing-babbage-y6fqb?file=/example.js
A solution there will be to move error to Form.Field or use Form.Input (it does exactly the same):
<Form>
  <Form.Field error>
    <Input placeholder="Search..." />
  </Form.Field>
  <Form.Input error placeholder="Search..." />
</Form>

@adamhazon is there a use case when Form.Input does not work for you?

@layershifter Thank you for taking the time to investigate and write a proper answer 🙏
I already fixed the problem by overriding the style,
changing the structure to use Form.Input or moving the error to Form.Field will not work in my case.
I'm just saying that using Form.Field inside a Form is pretty obvious and should be fixed. 😆
Thanks again for your time and response, now the proper answer is here for anyone who faces this issue!


path.join should respect a trailing slash

@escaped Would you sign the CLA please? I need that to accept this PR. You can find it here: https://docs.google.com/forms/d/1Npd68d32UDUKUYuCDDrW0VN5Lv8p-a6Ziaa2JFKp6Cg/viewform?c=0&w=1 If you don't mind, please let me know what your name is so I can correlate you to the data.

Signed as Alexander Frenzel.


Update azeventhubs to latest go-amqp

[ ] The purpose of this PR is explained in this or a referenced issue.
[ ] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[ ] Tests are included and/or updated for code changes.
[ ] Updates to CHANGELOG.md are included.


Fix object null reference issue while first time open VS

#85
@AndreSayreMSFT @adamdriscoll
Fix Description: Previously wait for 2 seconds for remote process creation&initialization, which seems a bit short for the first time opening VS, so it enters into error handling logic, where we try to access process id after we disposed the process project, that cause the null ref. However, in terms of the fix, we should also enlarge the timeout a bit, 10s looks fine to me, but I m open to give a larger number there..

Looks good!  Will be opening up another issue to track a general improvement item about not having a fixed timeout.

Opened up #199


Could not resolve all files for configuration ':app:debugRuntimeClasspath'.    > Could not find :ttlock-release:.

Hello,
Facing this issue after setting up ttlock related plugin configuration

i have same error, but i use version 0.2.0 for deploy android and use 0.3.0 for ios, i dont know why.

Hey @paloe, you just need to add some .aar file to your project. check out PR #29  raised to fix this issue.


@conda-forge-admin, please add bot automerge

@conda-forge-admin, please add bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/esmtools-feedstock#6.


Any channel beside sync doesn't work!

Hi, I'm using this compiler for my project but when I use any other channels like lossy sync, fifo, sync drain etc, output java file ends up in a deadlock. Even when I use the example you are providing in introduction file it doesn't work either.
Am I doing something wrong or this is a bug in compiler?!

Hi, I need more details to help you. Which binaries are you using for compilation? Some changes have been made recently (on the binaries accessible at https://reo.readthedocs.io/en/latest/installation.html), it may have altered some of the behaviour.
Could you also explain the details of the steps you are taking?

Sorry I'm responding late. I am using reo-compiler code and I have pulled from origin\master too. I run the compiler with treo file that is used in your tutorial. My treo file is:
import reo.syncdrain;
import reo.sync;
import reo.fifo1;

// The main component
main(a,b,c) { green(a) red(b) blue(c) alternator(a,b,c) }

// The atomic components
red(a!String) { #JAVA "Processes.Red" }
green(a!String) { #JAVA "Processes.Green" }
blue(a?String) { #JAVA "Processes.Blue" }

// The alternator protocol
alternator(a,b,c) { syncdrain(a, b) sync(b, x) fifo1(x, c) sync(a, c) }

and my java file is:
import nl.cwi.reo.runtime.Input;
import nl.cwi.reo.runtime.Output;

public class Processes {

	public static void Red(Output<String> port) {
	   while (true) {
	      for (int i = 0; i < 30000000; ++i);
	      String datum = "Hello, ";
	      port.put(datum);
	   }
	}

	public static void Green(Output<String> port) {
	   while (true) {
	      for (int i = 0; i < 50000000; ++i);
	      String datum = "world! ";
	      port.put(datum);
	   }
	}

	public static void Blue(Input<String> port) {
	   for (int k = 0; k < 10; ++k) {
	      for (int i = 0; i < 40000000; ++i);
	         String datum = port.get();
	         System.out.print(datum);
      }
	}

}

There will be no output and when I look at jconsole, all threads are waiting.

Few comments on your code. The treo file is supposed to have the same name as the main component of your file. In your case, the treo file should be named "main.treo" (I guess you got it right if you didn't get any error messages).
The main component can either hide all the internal ports (with an empty interface), or expose some ports for runtime i/o. In your case, ports a b c are open, and input/output request are expected at runtime. Your intention was perhaps to connect internally a and b to a producer (Red and Green) and c to a consumer (Blue). In this case, the declaration of the main component should have an empty interface: "main() { green(a) red(b) blue(c) alternator(a,b,c) }". Note that you can take inspiration from some examples in the folder examples/slides/main.
The rest looks fine, and compile&run on my side. Also, the for loop ( for (int i = 0; i < 50000000; ++i);) in your java code is used for each producer/consumer to wait? You might want to use Thread.sleep(time_ms) instead (such as: try{Thread.sleep(1000);}catch(InterruptedException e){System.out.println(e);}).
What I observe as output is "world! Hello, world! Hello, world! Hello, world! Hello, world! Hello,", which is 10 times the alternation of the two input strings.
My guess is that you want to let the interface of the main component empty. Doing that should solve your problem. Let me know if it works, if something is not clear, or if you have more questions.

Yes, you're right. I wanted to use internal ports. I used the empty interface and every thing works fine.
Thanks for your response.


[breaking change] use common data structure for all annotations

This is non-backward-compatible solution to issue #285. To be included in 2.0.

@smolkaj this should probably be an issue at this stage and not a PR against master, which we cannot merge for a while.
It is possible that time has come for us to create a development branch for P4Runtime v2.0, but even then it makes sense to have a corresponding issue that we can use for tracking.

It is entirely up to the working group how they want to handle this in the Github repo files, but an alternative to creating a branch is to have separate directories for v1 and v2 of the P4Runtime API spec, and initially populate v2 files with copies of the latest v1 files.
There are disadvantages to such an approach, but a potential advantage is to make it easier to continue to make small corrections/clarifications to the v1 files as time goes on, and easily keep them "in the file system" for operations like auto-generating HTML/PDF from both v1 and v2 without doing git checkout operations.

I created #288 to track this.

I will close this PR until it becomes relevant again.

Just opening this temporarily to incorporate updates pointed out by @chrispsommers .


Resources

Follow this checklist for submitting a pull request (PR):

[ ] Your branch is up-to-date with the main branch.
[ ] You are submitting your PR against the main branch of the repository you are contributing to from your fork.
[ ] You have linked your GitHub issue at the Resolves Issue section if it exists.
[ ] You have provided a brief description of the issue.

Description
Quick description of what this pull request does.

If this is a bug fix, what issue is this fixing?
If this is a feature, describe the feature that is being added.

Resolves Issue: closes #{issue number} (e.g. closes #123).

I figured it out
git remote set-url origin  https://github.com/FearlessTech/Reentry.git
git push --set-upstream origin testMove
testMove is the name of the branch


Custom Functions

[ ] How to implement custom jsonnet functions for this library?
[ ] If there is any way for creating custom jsonnet function than please mention it in documantation.

I suppose the feature you mention is what is called "native functions" or "native callbacks" in Jsonnet terminology.
node-jsonnet has nativeCallback function to define a native callback in the Jsonnet execution environment, whose documentation can be found at https://node-jsonnet.hanazuki.dev/master/classes/Jsonnet.html#nativeCallback with a tiny example program.

Got it. Thank you for helping


feat(functions): add Slack samples

Update: DeployTest has been fixed, so this is clear to merge. 😄

The tests are failing with:

InvalidArgumentException: Missing required property: entryPoint in /tmpfs/src/github/php-docs-samples/testing/vendor/google/cloud-tools/src/TestUtils/GcloudWrapper/CloudFunction.php:83

@grayside is this something a Kokoro re-run will solve? If so, would you mind kicking that off once you've finished merging changes to php-tools?
(If not...happy to update this PR accordingly. 🙂)


How to deploy securely using github and Heroku?

Apologies if this is a FAQ, I'm new to this and it's better to be careful with security.
I have a project built using API Platform, using JWT for authentication.  So in my .env file I have JWT_SECRET_KEY, JWT_PUBLIC_KEY and JWT_PASSPHRASE config.  My project is on Github with a pipeline set up to deploy on Heroku.
Currently it's a private project, so that's all safe, but while it works in development on Docker it's not currently working when deployed to Heroku:
Uncaught PHP Exception Lexik\Bundle\JWTAuthenticationBundle\Exception\JWTEncodeFailureException: "Unable to create a signed JWT from the given configuration." at /app/vendor/lexik/jwt-authentication-bundle/Encoder/LcobucciJWTEncoder.php line 41
Any suggestions for how I might have misconfigured the deployment?
In case it's relevant, in time I want to make the github repository public. It doesn't feel great to have an open github project with my passphrase and private key files.  What is the recommended approach to this - should I be generating the keys as part of deploying?  Doing that correctly might also resolve whatever the problem is here.

After further experimentation, this works to generate new keys on install.
        "post-install-cmd": [
            "@auto-scripts",
            "chmod -R 777 public/",
            "chmod -R 777 config/",
            "mkdir -p config/jwt",
            **"openssl genrsa -out config/jwt/private.pem 4096",
            "openssl rsa -pubout -in config/jwt/private.pem -out config/jwt/public.pem"**
        ],

Closing as solved, thank you for sharing your solution.


How can I set bigquery streaming insert timeout?

I caused Error.
How can I set timeout (read timeout?)?
com.google.cloud.bigquery.BigQueryException: Read timed out
        at com.google.cloud.bigquery.spi.v2.HttpBigQueryRpc.translate(HttpBigQueryRpc.java:86)
        at com.google.cloud.bigquery.spi.v2.HttpBigQueryRpc.insertAll(HttpBigQueryRpc.java:283)
        at com.google.cloud.bigquery.BigQueryImpl.insertAll(BigQueryImpl.java:443)
        at jp.co.xxx.BigQuerySender.insertStreamingData(BigQuerySender.java:68)
        at jp.co.xxx.BigQuerySender.insert(BigQuerySender.java:60)
        at jp.co.xxx.GcpSender.run(GcpSender.java:67)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.SocketTimeoutException: Read timed out
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
        at java.net.SocketInputStream.read(SocketInputStream.java:171)
        at java.net.SocketInputStream.read(SocketInputStream.java:141)
        at sun.security.ssl.InputRecord.readFully(InputRecord.java:465)
        at sun.security.ssl.InputRecord.read(InputRecord.java:503)
        at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
        at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930)
        at sun.security.ssl.AppInputStream.read(AppInputStream.java:105)
        at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
        at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
        at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
        at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:735)
        at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678)
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1569)
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474)
        at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
        at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338)
        at com.google.api.client.http.javanet.NetHttpResponse.<init>(NetHttpResponse.java:37)
        at com.google.api.client.http.javanet.NetHttpRequest.execute(NetHttpRequest.java:94)
        at com.google.api.client.http.HttpRequest.execute(HttpRequest.java:981)
        at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.executeUnparsed(AbstractGoogleClientRequest.java:419)
        at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.executeUnparsed(AbstractGoogleClientRequest.java:352)
        at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.execute(AbstractGoogleClientRequest.java:469)
        at com.google.cloud.bigquery.spi.v2.HttpBigQueryRpc.insertAll(HttpBigQueryRpc.java:281)

The HttpTransportOptions class allows to set read and connect timeouts. Please check RemoteBigQueryHelper code of an example how it can be done:
HttpTransportOptions transportOptions = BigQueryOptions.getDefaultHttpTransportOptions();
transportOptions = transportOptions.toBuilder().setConnectTimeout(60000).setReadTimeout(60000)
    .build();
BigQueryOptions bigqueryOptions = BigQueryOptions.newBuilder()
    .setRetrySettings(retrySettings())
    .setTransportOptions(transportOptions)
    .build();

BigQuery bigquery = bigqueryOptions.getService();
//bigquery.insertAll()

Please let us know if it resolves your issue.

@vam-google
Thanks you very much !
It fixed the exception, but new exception was happened like this...
  j.c.c.BigQuerySender Remote host closed connection during handshake
com.google.cloud.bigquery.BigQueryException: Remote host closed connection during handshake
    at com.google.cloud.bigquery.spi.v2.HttpBigQueryRpc.translate(HttpBigQueryRpc.java:86)
    at com.google.cloud.bigquery.spi.v2.HttpBigQueryRpc.insertAll(HttpBigQueryRpc.java:283)
    at com.google.cloud.bigquery.BigQueryImpl.insertAll(BigQueryImpl.java:443)
    at jp.co.xxx.BigQuerySender.insertStreamingData(BigQuerySender.java:71)
    at jp.co.xxx.BigQuerySender.insert(BigQuerySender.java:63)
    at jp.co.xxx.GcpSender.run(GcpSender.java:67)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:748)
Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
    at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:992)
    at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
    at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
    at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
    at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559)
    at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
    at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1316)
    at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1291)
    at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:250)
    at com.google.api.client.http.javanet.NetHttpRequest.execute(NetHttpRequest.java:77)
    at com.google.api.client.http.HttpRequest.execute(HttpRequest.java:981)
    at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.executeUnparsed(AbstractGoogleClientRequest.java:419)
    at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.executeUnparsed(AbstractGoogleClientRequest.java:352)
    at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.execute(AbstractGoogleClientRequest.java:469)
    at com.google.cloud.bigquery.spi.v2.HttpBigQueryRpc.insertAll(HttpBigQueryRpc.java:281)
    ... 11 common frames omitted
Caused by: java.io.EOFException: SSL peer shut down incorrectly
    at sun.security.ssl.InputRecord.read(InputRecord.java:505)
    at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
    ... 25 common frames omitted

My code is:
        BigQueryOptions.Builder builder =  BigQueryOptions.newBuilder()
                .setProjectId(PROJECT_ID);

        HttpTransportFactory httpTransportFactory = new ProductionHttpTransportFactory();
        TransportOptions transportOptions = HttpTransportOptions.newBuilder()
                .setHttpTransportFactory(httpTransportFactory)
                .setReadTimeout(0)
                .build();
        builder.setCredentials(ServiceAccountCredentials.fromStream(Files.newInputStream(path), httpTransportFactory)).setTransportOptions(transportOptions);
        BigQuery bigquery = builder.build().getService();

This must be authentication related issue now. Are you sure that you are using a valid json service account key? Which httpTransportFactory are you using in this example (ProductionHttpTransportFactory looks like an external class)? Please check Authentication section and try other ways of authentication. If other ways work, then most probably something is wrong with either your key or transport factory.

oops, ProductionHttpTransportFactory  is:
public final class ProductionHttpTransportFactory implements HttpTransportFactory {
    private static final Logger logger = LoggerFactory.getLogger(ProductionHttpTransportFactory.class);
    private static HttpTransport HTTP_TRANSPORT;

    static {
        try {
            HTTP_TRANSPORT = newProxyTransport();
        } catch (GeneralSecurityException | IOException e) {
            logger.error(e.getMessage(), e);
        }
    }

    private static HttpTransport newProxyTransport() throws GeneralSecurityException, IOException {
        return new NetHttpTransport.Builder()
                .trustCertificates(GoogleUtils.getCertificateTrustStore())
                .setProxy(new Proxy(Proxy.Type.HTTP, new InetSocketAddress(PROXY_SERVER, PROXY_PORT)))
                .build();
    }

    @Override
    public HttpTransport create() {
        return HTTP_TRANSPORT;
    }
}

You are using proxy in your configuration and I believe the exceptions you encounter are related to that. It is hard to tell more as there is too many unknown things:

your lib versions,
the actual proxy you are using and its configuration (honestly, I'm not even sure that using proxies is supported)
the request you are trying to make
the https.protocols you are using
have you ensured validity and compatibility of the credentials (Files.newInputStream(path)), certificates and protocols you are using?

Also, is this authentication issue related to the original timeout problem you had?

com.google.cloud:google-cloud-bigquery:0.21.1-beta
I can't confirm proxy setting, but I know this proxy is Apache HTTP server.
streaming insert. It retry succeeded to send data when this error was occured.
I don't know how to check https.protocols.
I confirmed that service account json file(using for Files.newInputStream(path)) of the GCP IAM page exists.

Timeout problem is resolved. May I open new issue?

Yes, feel free to open a new issue (putting a ling to this one). Closing this issue as resolved. If you choose to open a new issue, please clarify if you always receive this SSL error, or only sometimes (i.e. is it sporadic or no). If it is sporadic, I suspect the actual proxy you are using may be the problem, not the bigquery service or the client libraries.


unhelpful ValueError associated with positioner movement

Just now, I accidentally did this:
RE(mv(xafs_y, 173.439, xafs_y, 64.63))

(Note, I specified the same motor twice.)
The stack trace ended with this:
ValueError: Can not compose overlapping cycles

Now, I know what a cycler is, but approximately 0% of the users of my beamline will know what a cycler is.  The likelihood that that error message would result in a phone call rather than the user figuring out the problem themself seems VERY high.   An error message with an actionable hint would be of value.

Thanks, Tom.  Certainly should have been a bluesky issue.  Sorry for the poor github skillz.

Should I close this and reopen over there?

I believe the merged PR in the cycler repository should address this issue. Can it be closed?


Alt key seems to be ignored.

I type <A-d> in vim and instead of executing a mapping, it gives the key sequence <2202> and does nothing.

I'm not a VIM user. What is the expected behaviour?

It should executed whatever mapping I assigned to it. In this case,
deleting a line.
On Thu, Oct 13, 2016 at 7:46 PM Drew<EMAIL_ADDRESS>wrote:

I'm not a VIM user. What is the expected behaviour?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/shockone/black-screen/issues/821#issuecomment-253696078,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH8KTLpW5fy3zd1OMpjuVDSPSpcfUBgIks5qzuz-gaJpZM4KUOon
.

--

Alok

Sorry, I was hoping for some easy steps to follow to help me reproduce the issue. Basically, I want some instructions that I can follow in both black-screen and iTerm  the exhibit different behaviour (assuming no existing vim configuration).

To reproduce:
create a vimrc and add this line:
nnoremap <M-d> dd

Create a nonempty file. In iterm and black-screen, press  and it should recognize the keystroke in iterm and delete the line (which is what dd does). In black-screen, it should do nothing.

Hmmm for me iTerm alt+d also does nothing when I use that vimrc. It's very confusing actually, I try various combinations of different keys and commands and they do totally unpredictable things.

I suspect your iTerm alt key is not set to meta or esc+.
Go to Preferences > Profiles in iTerm. select your profile and go to the keys tab. the option is on the bottom right.
Most people seem to use esc+ according to iTerm's FAQ.

To fix it in Job.write we can check whether alt is pressed, and if it is, convert the sequence to ESC + whatever key.
https://www.w3.org/TR/uievents/#dom-keyboardevent-altkey

@Alok can you tell me what shows up in both black-screen and your usual terminal if you execute sleep 10 and then press alt+d? Having vim stuff involved is making is difficult to figure out what the correct behaviour is, and I'm not super familiar with the terminal emulation side of this project (I've mostly worked on plugins and UI stuff).

iterm: (nothing)
black-screen: ∂

@Alok How about if you press it a few times in iTerm?  Also, #852 may fix your issue but I'm not very familiar with that part of the code. If you could pull that branch and try it out to see if it fixes your issue, I would very much appreciate that.

Pressing it any number of times put no input on the screen. I'll try
pulling that and see if it helps.
-- Alok
On Sun, Oct 30, 2016 at 9:41 PM, Drew<EMAIL_ADDRESS>wrote:

@Alok https://github.com/Alok How about if you press it a few times in
iTerm?  Also, #852
https://github.com/shockone/black-screen/pull/852 may fix your issue
but I'm not very familiar with that part of the code. If you could pull
that branch and try it out to see if it fixes your issue, I would very much
appreciate that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/shockone/black-screen/issues/821#issuecomment-257212763,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH8KTOvKC09EP13EbeB3P5u8vJv7K_Voks5q5XFdgaJpZM4KUOon
.

So I tried #852 and it fixed it, though typing <a-d> in the command line (outside of vim) still puts the ∂.
Also, I don't think you shouldn't call the pull request "fix alt-d" as it's an issue with the alt key and probably has nothing to do with that letter in particular.

Thanks a lot for verifying. The fix only applies when you are sending keystrokes to a running program, not when you are typing into the command line. I think that's probably appropriate, what would alt+* do when typing into the command line anyway? We probably want to leave the up to the OS.


Gdiffsplit colours in light style are "a bit off" ;)

Thanks for that beautiful colour scheme! The cool style is my absolute favourite at the moment :)
The light is a different story though. At first sight it looks nice but if I invoke Gdiffsplit it's quite a difference ...
A screenshot says much more in this case I guess:

Oops. Looks like I forget to update some colors. I will fix it

These colors need to be updated
https://github.com/navarasu/onedark.nvim/blob/77752edb0f8378a21f92b8a4dcad984177f24c7f/lua/onedark/palette.lua#L193-L196

@wimstefan please try the latest master, it should be fixed now :)

@wimstefan please try the latest master, it should be fixed now :)

It is indeed 😁
Thank you so much 🙏🏼


Fix CI

Seems like The Session is currently down

Codecov integration not quite back yet, but maybe on the next PR..


Fix known bugs

### Tasks
- [x] Investigate the long await time for acceptance, e.g., faucet request
- [x] Error: using spent output, but faucet request went through

Issue was not caused by the spammer itself, but it happens in the node internally: https://github.com/iotaledger/iota-core/issues/462


Include configuration no longer works

When upgrading from Loom 1.2 to 1.3 the include configuration no longer works.
Error log: https://files.lostluma.net/1v8oVM.txt
Minimal set of changes to template mod for testing:
diff --git a/build.gradle b/build.gradle
index e8a8bbf..384e764 100644
--- a/build.gradle
+++ b/build.gradle
@@ -29,6 +29,8 @@ mappings variantOf(libs.quilt.mappings) { classifier 'intermediary-v2' }
        */
        modImplementation libs.quilt.loader

+       include("commons-io:commons-io:2.13.0")
+
        // QSL is not a complete API; You will need Quilted Fabric API to fill in the gaps.
        // Quilted Fabric API will automatically pull in the correct QSL version.
        modImplementation libs.quilted.fabric.api
diff --git a/gradle/libs.versions.toml b/gradle/libs.versions.toml
index 346f265..72de0b5 100644
--- a/gradle/libs.versions.toml
+++ b/gradle/libs.versions.toml
@@ -19,4 +19,4 @@ quilted_fabric_api_deprecated = { module = "org.quiltmc.quilted-fabric-api:quilt
 quilted_fabric_api = ["quilted_fabric_api", "quilted_fabric_api_deprecated"]

 [plugins]
-quilt_loom = { id = "org.quiltmc.loom", version = "1.2.+" }
+quilt_loom = { id = "org.quiltmc.loom", version = "1.3.+" }

Fixes as of cc599d8453f2a60927719ee71d45e3ae17b710dd / 1.3.2. Thanks @EnnuiL 🦫


Postgres NET8 compiled models protection level error workaround

Readiness checklist

[ ] I added/updated unit tests.
[ ] I added/updated integration tests.
[x] I ensured that the PR title is good enough for the changelog.
[x] I labeled the PR.

Description
After updating to .NET 8.0 the compiled models for Postgres began having errors due the protection level of certain value type converters. This is stated to be fixed in a future version of the Npgsql.EntityFrameworkCore.PostgreSQL package.

Don't

I have no idea where this comment came from. :D Just ignore it.


License needs a year bump

The MIT license needs a year update:
https://github.com/playcanvas/engine/blob/b7a9995038c8db9718efca759a1d40adb287c61f/LICENSE#L1

Does it? I mean, VS Code is still on 2015!
https://github.com/microsoft/vscode/blob/main/LICENSE.txt
😆

It actually says "present", meaning from 2015 till present day :)

This has now been done.


Program waits infinitely on semaphore "frameRenderingSemaphore" in GPUImageStillCamera while image capture

Sometime while capturing an image the program waits infinitely in this line:
dispatch_semaphore_wait(frameRenderingSemaphore, DISPATCH_TIME_FOREVER); (around line number 223 in file GPUImageStillCamera.m .
I am invoking the - (void)capturePhotoAsImageProcessedUpToFilter:(GPUImageOutput<GPUImageInput> *)finalFilterInChain withCompletionHandler:(void (^)(UIImage *processedImage, NSError *error))block method to capture image
For time being I have changed the wait time to DISPATCH_TIME_NOW and prevent indefinite waiting, but that would result in not capturing any image.
Let me know what details I can provide to help you understand the issue.
Thanks

@neils4fun -- not sure if your deadlock was caused by the same issues as my deadlock, but in my case, it was because I was dispatching_async to a queue of priority/QoS QOS_CLASS_USER_INTERACTIVE. This effectively meant Thread 1, the UI thread. I was also using a long-press gesture recognizer to do capture (on Thread 1) which caused the deadlock for me. I changed the QoS to QOS_CLASS_USER_INITIATED and it seems to work fine now.


Redirect in child router (navigation strategy), when parent is using navigation strategy

I'm submitting a bug report

Library Version:
1.3.0 (also tried in 1.5.0)

Please tell us about your environment:

Operating System:
Windows 10

Node Version:
9.2.1

NPM Version:
5.7.1

JSPM OR Webpack AND Version
JSPM 0.16.53

Browser:
all (Chrome 64 | Firefox 59 | Edge 41 )

Language:
ESNext

Current behavior:
Redirecting in child router using navigation strategy is not working, when parent router also has a navigation strategy defined.
https://gist.run/?id=087cf483ccb4476a3c7cb8a76a49823e
If you uncomment app.js/line 27, navigation to rooms route stops working. The Url is being updated correctly, but the view models are not being loaded into the corresponding viewports. I could not perfectly localize the bug, but the viewport plan is empty. I think it is nearby AppRouter._dequeueInstruction method
Expected/desired behavior:
Redirect works in child router, even if parent route has used navigation strategy

What is the motivation / use case for changing the behavior?
Dynamic redirect based with navigation strategy, when parent route is using a navigation strategy

@EisenbergEffect something to consider for vNext?

If you point me to the right direction, I'm happy to contribute with a PR

This bug is a race condition. Adding the navigation strategy handler adds one too many items to the wrong queue, which causes the navigation pipeline before the navigation instruction is created.
The source of the bug is on history-browser/index.js#L235:
_loadUrl(fragmentOverride: string): boolean {
  let fragment = this.fragment = this._getFragment(fragmentOverride);

  return this.options.routeHandler ?
    this.options.routeHandler(fragment) :
    false;
}

this.options.routeHandler refers to Router.loadUrl, which returns a Promise. Once the promise is disregarded in the history-browser code, the race is on.
The right thing to do would be to

Correct the typings to return a promise,
propagate the promise upwards, and
await the promise in the Router.processResult function, here.

You'll end up with something like this:
function processResult(instruction, result, instructionCount, router) {
  if (!(result && 'completed' in result && 'output' in result)) {
    result = result || {};
    result.output = new Error(`Expected router pipeline to return a navigation result, but got [${JSON.stringify(result)}] instead.`);
  }

  let finalResult = null;
  let generateNavigationInstruction = null;
  if (isNavigationCommand(result.output)) {
    generateNavigationInstruction = result.output.navigate(router); // grab the promise
  } else {
    finalResult = result;

    if (!result.completed) {
      if (result.output instanceof Error) {
        logger.error(result.output);
      }

      restorePreviousLocation(router);
    }
  }

  // await the promise, or proceed immediately if no promise
  return Promise.resolve(generateNavigationInstruction).then(() => {
      return router._dequeueInstruction(instructionCount + 1)
    }).then(innerResult => finalResult || innerResult || result);
}

The most time consuming part of any fix is good working tests. Submitting the best tests possible will help me process your PR quickly!
Thanks for reporting this issue.

Sure, I'll check that :)

Should I create a PR in browser-history and then in router? Or is it okay to send in parallel?

@balazsmeszegeto you can send in parallel with mentions of each other.. that one depends on another if that's the case

Sure. I cannot promise to be ready during the weekend, but I'll work on it next week

@balazsmeszegeto don't promise anything.. It ends up badly usually (-:

@Alexander-Taran I've sent in the PR last week as promised :) When can I expect some review?

@balazsmeszegeto  I see that  @davismj assigned himself. Let's wait and see.


Fix README instruction on how to build using mvn

Fixes Issue
Description of Change
Please add a description of the proposed change
Have test cases been added to cover the new functionality?
yes/no

@jeremylong Could you review?


ASP.NET Core CORS policy cannot be mixed with IdentityServer4 CORS

Issue #3780 never got resolved and is valid.
If you try to mix the ASP.NET Core default CORS policy control with IdentityServer4's, IdentityServer4 seems to step over it when used as described in the documentation.
As an example here is my IDP. It has the usual endpoints and then an api for user data. Here is the Startup.cs file as the documentation says to set it up:

The default policy is defined here. The localhost origin is where my Angular client is located.

Upon trying to access the api on my IDP this debug message displays:

Which doesn't seem to make sense. I have debugged a manual service implementation and checked the source code.
It seems like the IdentityServer4 CorsPolicyProvider steps over every other piece of CORS middleware and blocks requests that aren't to the authentication paths. There have been numerous issues surrounding this but I can't seem to get an api request to go through from my client in any way. Based on other issues I've tried:

Adding a custom ICorsPolicyService service before or after IdentityServer that accepts all requests.
Adding the line described in this issue

Neither seem to work.

Fixed by reading https://docs.identityserver.io/en/latest/topics/add_apis.html


Media added to layouts

Couldn't find a fix for the nested layouts problem so came up with adding the interface and trait for the media to the layouts class.
This fixes the nested layouts error whist not needing to add the interface and trait to current/future layouts

@JKHarley the PHP wizard

@JKHarley the PHP wizard

Who needs Netflix when you can watch Laracasts aha


Showing a specific form level validator error

The Problem
When using a form level validator e.g:
<Form
  validators={{
    '': {
      isLocationValid: ({ x, y }) => {
        if (x) {
          return true;
        }
        return y;
      },
    },
  }}
>

I have found it difficult to display the correct error message for isLocationValid.
<FieldErrors
  model="."
  messages={{ isLocationValid: 'Field required' }}
  show={_ =>
    jobFormFields.location.touched &&
    !jobFormFields.location.focus
  }
/>

With FieldErrors.jsx looking like:
import React from 'react';
import { Errors } from 'react-redux-form';

const FieldErrors = props => {
  return (
    <Errors
      show={{ touched: true, focus: false }}
      wrapper={props => (

{props.children}

      )}
      {...props}
    />
  );
};

export default FieldErrors;

Now, this works, with a few edge cases, but the issue is that when I use actions.submit() that returns an error, all instances of FieldErrors with model="." (I have a few) displays the form level error that is returned from the failed submission.
Any insight in how best to approach this would be appreciated.
Reproducible Code Example
Let me know if you need to see the code, this is most likely me misusing the API.

@davidkpiano  -  do you require a code example? I assumed I was abusing model="." - I searched through every issue I could find without finding anything similar.

A code example would be helpful.

@davidkpiano  - https://codesandbox.io/s/rm4yvjo7m4
A slightly convoluted example, but close to what I am doing. If you check the box, it'll show the necessary validation message, but when you make an API request via submit(), the error returned will also be shown in the title's Error component - this makes complete sense as I am using model="." - was wondering how to get this behaviour to work so I can have one error message that will validate two fields (a good example being a salary range, or fields that are only required if another field is filled out).

@davidkpiano  - I was wondering if my code example was enough to demonstrate the problem?  Cheers!

hey @davidkpiano, was wondering if you had a chance to look this over? Thanks

Sorry, I don't. But nothing's stopping you from reading the values directly from the store and creating your own Error component that does what you want.

If anyone is unfortunate enough to have to show errors for form wide validations like me, this may be the dirty hack you need.
import React from 'react';
import { Errors } from 'react-redux-form';

const FieldErrors = props => {
  const { field, error } = props;
  let show;

  // If we have passed a field, it is a custom Form level validation error.
  if (field) {
    // If the error key we passed exists, only show if we have interacted with the field.
    // If the key no longer exists, it means the form has submitted an error and the key was wiped, thus do not show it.
    show = error ? field.touched && !field.focus : false;
  } else {
    // Generic inline form error logic.
    show = {
      touched: true,
      focus: false,
    };
  }

  return (
    <Errors
      show={show}
      wrapper={props => (

          {props.children} {props.error}

      )}
      {...props}
    />
  );
};

export default FieldErrors;

Used like so:
<FieldErrors
  model="."
  field={jobFormFields.compensation_to}
  error={jobFormForm.errors.isValidCompensation}
  messages={{
    isValidCompensation: 'Invalid salary range',
    isRequired: MESSAGES.isRequired,
  }}
/>


[Bug] create producer thread stuck

Search before asking

[X] I searched in the issues and found nothing similar.

Version
pulsar client 3.01.
pulsar broker 3.0.1
puslar proxy 3.0.1
Minimal reproduce step
It is hard to reproduce
What did you expect to see?
When you use puslar client to create producer objects synchronously, you can trigger a timeout or other exception normally, rather than the thread staying stuck
What did you see instead?
Threads keep getting stuck when creating producer objects synchronously using puslar client. To reproduce it, the pulsar cluster is stopped, and a timeout exception is reported when the produce object is created. Therefore, it is not clear how this situation has arisen. At present, it has appeared many times in the production environment.

Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

@qiaofazhan Does the thread dump contain a deadlock?

您好，邮件已收到，尽快给您回复。

@qiaofazhan Does the thread dump contain a deadlock?

There are no deadlocks in the thread dump。

@qiaofazhan is it a partitioned topic or non-partitioned topic? if partitioned, how many partitions?

@qiaofazhan is it a partitioned topic or non-partitioned topic? if partitioned, how many partitions?

It is a  non-partitioned topic.

@qiaofazhan There's a chance that this is a bug in Apache Eventmesh. I noticed from the thread dump that Apache Eventmesh is used, perhaps version v1.8.0 .
The producer cache within Eventmesh uses java.util.HashMap which isn't thread safe.
https://github.com/apache/eventmesh/blob/63ac4ec808933a64b048a3988f6c91671d2bc41a/eventmesh-connector-plugin/eventmesh-connector-pulsar/src/main/java/org/apache/eventmesh/connector/pulsar/client/PulsarClientWrapper.java#L47
I'd assume that a ConcurrentHashMap should be used if Eventmesh uses multiple threads. This is a bug that should be reported to Apache Eventmesh.

@qiaofazhan There's a chance that this is a bug in Apache Eventmesh. I noticed from the thread dump that Apache Eventmesh is used, perhaps version v1.8.0 . The producer cache within Eventmesh uses java.util.HashMap which isn't thread safe. https://github.com/apache/eventmesh/blob/63ac4ec808933a64b048a3988f6c91671d2bc41a/eventmesh-connector-plugin/eventmesh-connector-pulsar/src/main/java/org/apache/eventmesh/connector/pulsar/client/PulsarClientWrapper.java#L47 I'd assume that a ConcurrentHashMap should be used if Eventmesh uses multiple threads. This is a bug that should be reported to Apache Eventmesh.

========================
thanks, but I use concurrentHap for that problem .  And there are some other dump info:
"pulsar-client-io-112-1" #286 daemon prio=5 os_prio=0 cpu=64764.93ms elapsed=128885.97s tid=0x00007f66c407be40 nid=0x17e waiting for monitor entry  [0x00007f661458b000]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.apache.pulsar.client.impl.ProducerImpl.closeAndClearPendingMessages(ProducerImpl.java:1092)
- waiting to lock <0x000000064b01bde8> (a org.apache.pulsar.client.impl.ProducerImpl)
at org.apache.pulsar.client.impl.ProducerImpl.lambda$closeAsync$10(ProducerImpl.java:1079)
at org.apache.pulsar.client.impl.ProducerImpl$$Lambda$782/0x0000000840948c40.apply(Unknown Source)
at java.util.concurrent.CompletableFuture.uniHandle(java.base@11.0.15/CompletableFuture.java:930)
at java.util.concurrent.CompletableFuture$UniHandle.tryFire(java.base@11.0.15/CompletableFuture.java:907)
at java.util.concurrent.CompletableFuture.postComplete(java.base@11.0.15/CompletableFuture.java:506)
at java.util.concurrent.CompletableFuture.complete(java.base@11.0.15/CompletableFuture.java:2073)
at org.apache.pulsar.client.impl.ClientCnx.handleSuccess(ClientCnx.java:533)
at org.apache.pulsar.common.protocol.PulsarDecoder.channelRead(PulsarDecoder.java:252)
at org.apache.pulsar.shade.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)
at org.apache.pulsar.shade.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
at org.apache.pulsar.shade.io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
at org.apache.pulsar.shade.io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:346)
at org.apache.pulsar.shade.io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:318)
at org.apache.pulsar.shade.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)
at org.apache.pulsar.shade.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
at org.apache.pulsar.shade.io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
at org.apache.pulsar.shade.io.netty.handler.flush.FlushConsolidationHandler.channelRead(FlushConsolidationHandler.java:152)
at org.apache.pulsar.shade.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:442)
at org.apache.pulsar.shade.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
at org.apache.pulsar.shade.io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
at org.apache.pulsar.shade.io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
at org.apache.pulsar.shade.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:440)
at org.apache.pulsar.shade.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
at org.apache.pulsar.shade.io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
at org.apache.pulsar.shade.io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:800)
at org.apache.pulsar.shade.io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:499)
at org.apache.pulsar.shade.io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:397)
at org.apache.pulsar.shade.io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
at org.apache.pulsar.shade.io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at org.apache.pulsar.shade.io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(java.base@11.0.15/Thread.java:829)
Locked ownable synchronizers:
- None

thanks, but I use concurrentHap for that problem . And there are some other dump info:

Yes, indeed. Which Apache EventMesh version do you use? Custom fork?

"pulsar-client-io-112-1" #286 daemon prio=5 os_prio=0 cpu=64764.93ms elapsed=128885.97s tid=0x00007f66c407be40 nid=0x17e waiting for monitor entry [0x00007f661458b000]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.apache.pulsar.client.impl.ProducerImpl.closeAndClearPendingMessages(ProducerImpl.java:1092)

waiting to lock <0x000000064b01bde8> (a org.apache.pulsar.client.impl.ProducerImpl)

@qiaofazhan There might be a deadlock even though the JVM doesn't detect a deadlock. Have you analysed the thread dump with something like https://jstack.review/ ?
would it be possible to share the full threaddump? You could sanitize it if there's any sensitive information.

Custom fork

Custom fork from EventMesh v1.8.0 ;
Now, I try to create a producer in a practical asynchronous way; Add a timeout wait when getting the producer object
private Producer<byte[]> createProducer(String topic) {
long start = System.currentTimeMillis();
log.info("init create producer start:");
Producer<byte[]> producer ;
CompletableFuture<Producer<byte[]>> future=this.pulsarClient.newProducer()
.topic(topic)
.enableBatching(false)  //enableBatch  always happen timeout in prod env（The timeout looks like it only took 1 millisecond）; there are similar issures in pulsar community about this;
//.batchingMaxPublishDelay(15, TimeUnit.MILLISECONDS)
.sendTimeout(8, TimeUnit.SECONDS)
// .batchingMaxMessages(100)
.maxPendingMessages(100)
.createAsync();
try {
producer = future.get(60,TimeUnit.SECONDS);
} catch (Exception ex) {
log.error("init create producer error ,cost time="+(System.currentTimeMillis()-start)/1000);
log.error(">>>> create pulsar producer error",unwrapCompletionException(ex));
reInitPulsarClient(topic);
throw new ConnectorRuntimeException(
String.format("Failed to create pulsar producer for %s with exception: %s", topic, ex.getMessage()));
}
return producer;
}

thanks, but I use concurrentHap for that problem . And there are some other dump info:

Yes, indeed. Which Apache EventMesh version do you use? Custom fork?

Custom fork from EventMesh v1.8.0 ;
Now, I try to create a producer in a practical asynchronous way; Add a timeout wait when getting the producer object
private Producer<byte[]> createProducer(String topic) {
long start = System.currentTimeMillis();
log.info("init create producer start:");
Producer<byte[]> producer ;
CompletableFuture<Producer<byte[]>> future=this.pulsarClient.newProducer()
.topic(topic)
.enableBatching(false)  //enableBatch  always happen timeout in prod env（The timeout looks like it only took 1 millisecond）; there are similar issures in pulsar community about this;
//.batchingMaxPublishDelay(15, TimeUnit.MILLISECONDS)
.sendTimeout(8, TimeUnit.SECONDS)
// .batchingMaxMessages(100)
.maxPendingMessages(100)
.createAsync();
try {
producer = future.get(60,TimeUnit.SECONDS);
} catch (Exception ex) {
log.error("init create producer error ,cost time="+(System.currentTimeMillis()-start)/1000);
log.error(">>>> create pulsar producer error",unwrapCompletionException(ex));
reInitPulsarClient(topic);
throw new ConnectorRuntimeException(
String.format("Failed to create pulsar producer for %s with exception: %s", topic, ex.getMessage()));
}
return producer;
}

@qiaofazhan please reply to https://github.com/apache/pulsar/issues/21900#issuecomment-1891635612 since that will help investigating the possible deadlock.


This happens when ever I try to install crouton on my chromebook....

I recently got a chromebook and I am currently trying to convert it to running ubuntu, I have followed the correct instructions but it always comes up with this:
crosh> shell
chronos@localhost / $ sudo sh -e ~/Downloads/crouton -t unity
Downloading latest crouton installer...
################################################################## 100.0%
/usr/local/chroots/precise already has stuff in it!
Either delete it, specify a different name (-n), or specify -u to update it.
Please help!

@couln016,
You didn't show us the output of sudo edit-chroot -all so we don't know what you have installed or attempted to install or the device you have so it's hard to give you advice specific to your hardware.
The installation must have failed a time or two since it's telling you:

/usr/local/chroots/precise already has stuff in it!
Either delete it, specify a different name (-n), or specify -u to update it.

It would probably be best to just delete the existing one with: sudo edit-chroot -d precise
Then, start the install over again with something like:
sudo sh ~/Downloads/crouton -r trusty -t unity,extension
Note: I prefer to use the 'trusty' release since it's an LTS and usually gives less trouble. Also, I didn't specify targets 'xorg' nor 'xiwi' since we don't know what device you're using.
I usually specify both so I can have a choice when running my desktop(s).
Hope this helps,
-DennisL

Try to powerwash your computer,(Back up your data!)
Then, redownload it
Hope this helps,
Nihar

@niharxavier,
A 'powerwash' is unnecessary and a waste of time, delete-chroot will be sufficient in this case.
-DennisL

Oh,
I did not know that.
Im just a small 10 year old boy.
Thanks anyway!

Dennis, that was nice help thx!

can someone help when i enter in Delete-chroot it just brings up options and idk what to do

@sweettttttt66666,
Linux is case sensitive so 'Delete-chroot' will never work.
You can find the name(s) of your chroot(s) by running:

sudo edit-chroot -al

Then once you know the name(s) of the chroot(s) you want to delete use this command:

sudo delete-chroot [chrootname(s)]

Substitute 'chrootname(s)' above with your actual chroot name(s) and leave out the brackets.
-DennisLfromGA


bug: File.Readdir appends trailing slash even if there is already one present

https://github.com/fclairamb/afero-s3/blob/a24edce4fd30a379d12581a2c1f9b9651b35679a/s3_file.go#L74
If I call f.Readdir where f.name is /Path/ then it appends another slash to make it /Path// which fails
in s3/minio/etc.

Thank you very much @blockloop ! And sorry for the very late answer.

No problem. Thank you


Updating image name to new ruby-20-centos7

There is a new ruby-20 image(ruby-20-centos7) and we are going to get rid of the old one(ruby-20-centos)

Can one of the admins verify this patch?

@jstrachan can you please take a look :)

ok to test

thanks @jhadvig!

@jhadvig looks good thanks :)

Refer to this link for build results (access rights to CI server needed):
https://fabric8-ci.fusesource.com/job/fabric8-quickstarts-master-pullreq/253/
Test PASSed.

@jimmidyson @jstrachan sure thing :)


Overlapping Memory Map for Runtime

@pgkeller
We have addresses hardcoded in: tt-metal/tt_metal/hostdevcommon/common_runtime_address_map.h for args/debug prints/debugger
// TODO: these could be moved to even lower addresses -- 5 RISC-V hexes combined don't need 100 KB
constexpr static std::uint32_t RUNTIME_CONFIG_BASE = 100 * 1024;
constexpr static std::uint32_t BRISC_L1_ARG_BASE = 101 * 1024;
constexpr static std::uint32_t BRISC_L1_RESULT_BASE = 102 * 1024;
constexpr static std::uint32_t NCRISC_L1_ARG_BASE = 103 * 1024;
constexpr static std::uint32_t NCRISC_L1_RESULT_BASE = 104 * 1024;

Which overlap with the actual TRISC2 regions.  It seems like we are OK for now because of holes in our memory map, but we should ensure that this file is relative to the defines we set so there is no hazardous overlaps

this is slowly getting cleaned up under other issues, closing


frontend: add Events component in frontend

There is a need for an events component in the frontend app, you can navigate to components dir and check other components as refrence.

Sir can u please describe the issue.


add badges to README

Add the following badges for easier access: travis, appveyor, coverage,
supported pypi versions, pypi version. All badges include links to the
proper urls. Badges also add better visibility into our code coverage
as well as give better visibility into the build status.
If the contributors, we can also simplify the docs by removing some
of the links at the bottom that are now included in the badges.

So be it...
I still believe there is an added value in the graphicality of it and better accessibility for build status etc...


Release new version on NPM

The latest version in NPM is 4.11.0, which seems to be a more than a few versions behind.
@tomchentw could you publish the latest stable version to NPM?
I believe either v5.1.1 or v6.0.1 is the latest stable version.

npm i --save<EMAIL_ADDRESS>worked for me

@jtomaszewski I see that that version is still in a beta flag in the registry. As @nicholasgonzalezsc  stated, 4.11.0 is still tagged as latest version.

Will do.

6.0.1 published on npm as latest.

@tomchentw Thank you!


Query Strings removed upon navigation in admin

Link to reproduction
No response
Environment Info
Binaries:
  Node: 22.6.0
  npm: 10.8.2
  Yarn: 1.22.19
  pnpm: 9.7.1
Relevant Packages:
  payload: 3.0.0-beta.99
  next: 15.0.0-canary.104

Describe the Bug
Query strings in the URL are being stripped from the URL when using the back button in the Admin
https://github.com/user-attachments/assets/88d6fa92-4df0-4781-b0ba-fcbbf5090226
Reproduction Steps

Navigate to List view of a collection
Type in a filter, note the query strings added
Click on any document
Press back button in browser
Note the query strings that were there previously are no longer there.

Adapters and Plugins
No response

Likely related to the query string rework you're doing @paulpopus . Just needed it tracked.

Can confirm it's fixed in https://github.com/payloadcms/payload/pull/8081


xmlrpc.client.Fault: <Fault -32700: 'parse error. not well formed'>

The website is using WordPress 4.7.3
when executing
wp = Client("http://www.mywebsite.com/xmlrpc.php","myusername", "mypassword")
I got an error:

File "C:/02-folks/python-auto-send/upload_articles.py", line 20, in post_article
wp = Client("http://www.mywebsite.com/xmlrpc.php","myusername", "mypassword")
File "C:\Users\Wendy Sun\AppData\Local\Programs\Python\Python35-32\lib\site-packages\wordpress_xmlrpc\base.py", line 24, in init
self.supported_methods = self.server.mt.supportedMethods()
File "C:\Users\Wendy Sun\AppData\Local\Programs\Python\Python35-32\lib\xmlrpc\client.py", line 1091, in call
return self.__send(self.__name, args)
File "C:\Users\Wendy Sun\AppData\Local\Programs\Python\Python35-32\lib\xmlrpc\client.py", line 1431, in __request
verbose=self.__verbose
File "C:\Users\Wendy Sun\AppData\Local\Programs\Python\Python35-32\lib\xmlrpc\client.py", line 1133, in request
return self.single_request(host, handler, request_body, verbose)
File "C:\Users\Wendy Sun\AppData\Local\Programs\Python\Python35-32\lib\xmlrpc\client.py", line 1149, in single_request
return self.parse_response(resp)
File "C:\Users\Wendy Sun\AppData\Local\Programs\Python\Python35-32\lib\xmlrpc\client.py", line 1321, in parse_response
return u.close()
File "C:\Users\Wendy Sun\AppData\Local\Programs\Python\Python35-32\lib\xmlrpc\client.py", line 654, in close
raise Fault(**self._stack[0])
xmlrpc.client.Fault: <Fault -32700: 'parse error. not well formed'>
Process finished with exit code 1

Are you able to solve this issue?
I am using wordpress 4.8 version on php7. I am trying to draft posts to wordpress using python2.7, got same error Fault: <Fault -32700: 'parse error. not well formed'> .

The same problem

I also met this problem. After I read the Wordpress source code, I found that the problem is cased by "PHP's XML extension is not available. Please contact your hosting provider to enable PHP's XML extension."
So you just run the command: sudo apt-get install php-xml -y && sudo service apache2 restart and you will solve it.
more detail will found here: http://milier.me/solved-wordpress-parse-error-not-well-formed.html

I appear to be getting this problem even when I have php-xml installed.
php -m | grep -i xml, outputs:
libxml
SimpleXML
xml
xmlreader
xmlrpc
xmlwriter

I appear to be getting this problem even when I have php-xml installed.
php -m | grep -i xml, outputs:
libxml
SimpleXML
xml
xmlreader
xmlrpc
xmlwriter

try
php -v
then,
for example,
apt install php7.1-xml


Cannot delete realm file from iPad.

Original title: BUG : Cannot delete realm file from iPad.
Goals
I started to use Realm to read and save class on the iPad. For some reason, I want to rid all files on the iPad that are related to Realm. I can delete the default.realm file but there is 2 files that are still remaining, impossible to delete (manually or by code):

default.realm.management folder
default.realm.note

Formatting the iPad is not an option.
I need some code, some steps, some ideas, please, to delete those files.
Thanks,
Olivier
Code Sample
I tried:
do {
    try FileManager.default.removeItem(at: Realm.Configuration.defaultConfiguration.fileURL!)
} catch { }

I've also tried:
guard var path = Realm.Configuration.defaultConfiguration.fileURL?.absoluteString else {
    fatalError("no realm path")
}

path = path.replacingOccurrences(of: ".realm", with: ".realm.note")
do {
    try FileManager().removeItem(atPath: path)
} catch {
    print(error.localizedDescription)
    fatalError("couldn't remove at path : ")
}

Without success. Is it impossible to delete default.realm.note?
Version of Realm and Tooling

Realm framework version: Realm Swift 2.5.1
Realm Object Server version: ?
Xcode version: ?
iOS/OSX version: iOS 10.1.1 on iPad
Dependency manager + version: ?

Hi @ormaa. Thanks for reaching out about this. I've edited your issue to use the template that's available here and I wanted to let you know that we've received your issue and that someone will follow-up soon.

Odds are that you still have some instances of Realm objects in memory. Realm read transaction lifetimes are tied to their memory lifetimes, so as long as you have a strong reference to a Realm either directly or indirectly and haven't taken precautions to explicitly drain the autoreleasepool(s) managing their life cycle, those instances will stick around, causing Realm to continue accessing its backing files.
You can also call Realm.invalidate() explicitly on all Realm instances for each thread that is still holding a strong reference to a Realm instance at that disk location. This will cause any further access to the Realm at that location (say via Results, Realm Objects, etcetera to fail.

Hopefully that answered your question @ormaa! Please feel free to re-open the issue if you have any followup questions! :)


"Bălilești" is listed in the drop-down menu

Description:
"Bălilești" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Bălilești" in the search bar.

Expected results
The location is listed in the drop-down menu as "Bălilești, Argeș".

ENVIROMENT: ui.orase
URL: https://peviitor-ro.github.io/ui.orase/
Browser: Chrome
Device: Laptop
OS: Windows 11 Pro
STEPS TO REPRODUCE:
Open URL in browser
Type "Bălilești" in the search bar
EXPECTED RESULTS:
The location is listed in the drop-down menu as "Bălilești, Argeș".
ACTUAL RESULTS:
"Bălilești, Argeș" doesn't exist in the drop-down menu, the "Arges" is doubled.

Fixed! Poti sa retestezi


Remove trailing space

Yes, again - ansible-lint marks my build red due to this ¯\_(ツ)_/¯

Thanks! Appreciated.
Someone© should put that into travis.

@rndmh3ro
It should be as simple as adding the following to .travis.yml before tests:
ansible-lint /etc/ansible/roles/ansible-os-hardening/tasks/*.yml

Almost!
  - pip install --user ansible-lint
  - ansible-lint ./

Thanks for the suggestion.


Implement PagedFlux in Keyvault

Just did one function, more to come.

@JonathanGiles ,
We will need to add samples showing byPage() iteration.
Should we do it in this PR?

@JonathanGiles ,
We will need to add samples showing byPage() iteration.
Should we do it in this PR?

I think we could probably just centralise the docs around pagination by page, rather than have to describe it in every client library.

/azp run java - template - ci


Add RuctcEncdoable and RustcDecodable to derive attribute for Cookie

It was recommended in this pull request for servo that I placed the derive attribute for the RustcEncodable and RustcDecodable traits for the cookie_rs:Cookie to avoid encoding and decoding manually.  I noticed in the time library that the  #[cfg] attribute is used to make the encodable/decodable attribute optional.  If you would like me to add the #[cfg] attribute just let me know!
Edit: Actually I went ahead and added the #[cfg] attribute because rustc-serialize is marked as optional in Cargo.toml

Maybe update .travis.yml to run cargo test --features "rust-serialize"

Nevermind my comment, didn't realize it's a default  feature.

I think this is better, I was not sure if I should include secure in the feature or have feature "secure" and "serialize" contain rustc-serialize.  I also added a line for the serialize feature to travis.yml to address the previous suggestion of @frewsxcv .

Thanks! On second thought, could you name the feature serialize-rustc? That leaves the door open to add serialize-serde in the future.
Also for now let's have secure include rustc-serialize as it shouldn't also enable the RustcSerialize impls (even though the dependency is available). Right now we just need base64 which should in theory come from something other than rustc-serialize and otherwise that'd be a breaking change.

Changed feature name to serialize-rustc

Thanks!

@alexcrichton can we get a crates.io release?

Opened a PR to bump the version: https://github.com/alexcrichton/cookie-rs/pull/45


Add sideEffects: None to MutatingWebhookConfiguration

This is for supporting kubectl --server-dry-run feature.
It fixes #2186.
[Kubernetes APIServer dry-run](https://kubernetes.io/docs/reference/using-api/api-concepts/#dry-run) is supported.

/assign @munnerz

/ok-to-test
/cherrypick release-0.11

Thanks for this PR 😄
/lgtm
/approve

/retest


h1 is added on homepage

Fixes Issue
fix #7032

Changes proposed

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[ ] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

In GitHubAccelerator.js we have an h1 tag at the bottom of the components which fails. we may have to change the test to be more specific.


Add support for global types in the Python Matter codegen.

No argument; I'll see if I can get the folks maintaining the Python stuff in general to add some tests, and will think about some for the Darwin bits.
Or better yet, move some of these helpers out of ZAP and back into the Matter SDK.  ;)


Wrong error line indicator position of Static typed for loop

Tested versions

Reproducible in 4.3 Beta 1

System information
Win11  4.3 Beta 1 win64
Issue description
(this is originally written as GIP here as I was unsure if such behavior is intentional or not)
Assignment error for typed for loop marks error indicator at end of loop which could cause confusion.

For given MRE this is not an issue, but if the last line of the loop was assignment operations of Similar Types - then error message alone won't be helpful, and user might spend minutes or hours to debug nonexistence bug or file wrong bug report to godot repo, consuming already busy dev's time further.
Best example for this is when fixing the breaking changes happened during upgrade of 4.2 to 4.3.

^ godot 4.3 beta 1 win64
Godot 4.3 introduced PhysicsBoneSimulator3D node, and it's now being Sliently added to Skeleton3D Only In Remote, not in local.
Therefore, if there's pre-4.3 codes that iterate thru bones and fetch meshs from it - it will break the code, and show error on unhelpful position and user will have no idea what happened.
Even more, if the last line of the for-loop is also confusing enough - it won't be easy day for that user finding that until navigating the long trees in remote to find what is going on.
Steps to reproduce
write a for loop that triggers assignment error by giving it wrong type node/element for corresponding iterator.
Minimal reproduction project (MRP)
MRE: for_loop_test.zip

Possibly related:

https://github.com/godotengine/godot/issues/81046


[orchestrator] Collect cluster resources

What does this PR do?
Collecting kubernetes cluster resources.
Enabling it by collecting information about nodes, apiversions and namespaces.
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
Describe your test plan
Write there any instructions and details you may have to test your PR.

damn, I merged an old prod version. Will reopen. Sorry for the spam.


sequoia-sq: 0.39.0 -> 0.40.0

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

We don't wait for CI anymore? I wanted to see ofborg's build attempt on Darwin..

Not an appropriate attitude to display here.
Also since you do not maintain this package this is not your call.
Please refrain from acting in that way.

I appreciate the quick merge, and I think that rejection of proprietary targets for Nixpkgs is a valid opinion, even if a strong one.
For what it's worth, Darwin is not one of the test targets upstream.
No need for additional fuss on this minor release bump. v1.0 should come in a few weeks.


Create a mechanism for making it clear what people need to change/update when they use this template

Option 1: Use automatic issue creation with github actions.

Downsides: triggering the issue creation requires an additional effort beyond creating the repo w/ the template, you need to star it or do some other event we can key off of. Additionally, we don't yet know how to template the issues so they can link to specific files in the repo (since each repo will have a different URL than the parent template). We were able to do this kind of thing with repo and username variables in the training modules, but aren't sure how to do that outside of labs

Option 2: Use a pull request GH action or a travis CI to run a simple checker script that looks that the template defaults have been changed in the two appropriate yamls: the remake.yml and the in_txt/text_data_release.yml.

Downsides: don't know how clear these test fails will be - will it be easy to see which of these fields you didn't change or will you just get an ❌  and have to dig into logs? Or can we have the PR kick off several isolated checkers, with each one able to comment pass/fail on the PR in some kind of verbose way? unknown.

Oh wow - option 2 would be really cool! If all of the information we want to convey can just be summed into a pass/fail for needed changes to the repo, then that would be great. Only issue I see is that we will need to still put instructions somewhere so that people know what needs to get done.
I think we can be able to figure out how to get the issues to link to the current repo URL. Just would need to spend a bit of time researching how to do that. It wasn't high priority for me before, so I really didn't look into it. I don't think there would be a way around needing to star the repo, but we can always put that as an instruction in the initial README and then edit the README during that setup action so that it is ready for the actual template. I don't see needing to star the repo as that different from knowing that you need to use this template, especially if we say to do that in the instructions.
I don't really know what actions people must do when using this repo, so it is hard to say if issues or automated PR checks would be best.


Suddenly no resources menu showing up after connecting to a cluster, just a black page

Describe the bug
Suddenly a cluster I previously frequently interacted with through Lens, became inaccessible; at least GUI-wise.
Lens successfully connects, but the left side menu with resources is not shown for this cluster, so I cannot do anything (not choose between e.g. “Pods”, “Namespaces”, “Services”, etc.).
The console log reveals a lot of HTTP status 500 responses from the backend:

BrowserConsole.js:47 [KUBE-API] watch (customresourcedefinition-7538) error response /apis/apiextensions.k8s.io/v1/customresourcedefinitions?watch=1&resourceVersion=1488403 {status: 500}

From kubectl I am still able to see these resources on that same cluster, though.
BTW, a colleague on Windows has exactly the same problem, so not OS-related.
To Reproduce
Steps to reproduce the behavior:

Go to the particular cluster in the sidebar

Expected behavior
The menu of resources on the left side (next to the sidebar with cluster icons) should appear. (Or at least a clear error message that I can investigate further or act upon.)
Screenshots

Environment (please complete the following information):

Lens Version: 5.5.1-latest.20220526.1
OS: macOS, 10.15.7 (19H1922)
Installation method (e.g. snap or AppImage in Linux): download (almost sure)

Logs:
When you run the application executable from command line you will see some logging output. Please paste them here:
/Applications/Lens.app/Contents/MacOS/Lens
info:    ▪ 📟 Setting Lens as protocol client for lens:// +0ms
info:    ▪ 📟 Protocol client register succeeded ✅ +2ms
info:    ▪ [EXTENSIONS-STORE]: LOADING from  ... +17ms
info:    ▪ [EXTENSIONS-STORE]: LOADED from /Users/vovtz/Library/Application Support/Lens/lens-extensions.json +7ms
info:    ▪ [FILESYSTEM-PROVISIONER-STORE]: LOADING from  ... +8ms
info:    ▪ [FILESYSTEM-PROVISIONER-STORE]: LOADED from /Users/vovtz/Library/Application Support/Lens/lens-filesystem-provisioner-store.json +3ms
info:    ▪ 🚀 Starting Lens from "/Applications/Lens.app/Contents/MacOS/Lens" +8ms
info:    ▪ 🐚 Syncing shell environment +0ms

Kubeconfig:
Quite often the problems are caused by malformed kubeconfig which the application tries to load. Please share your kubeconfig, remember to remove any secret and sensitive information.

apiVersion: v1
kind: Config
clusters:
- name: kube-test.internal.degiro.eu
  cluster:
    certificate-authority-data: LS…Cg==
    server: https://<IP_ADDRESS>:6443
contexts:
- name: default-context
  context:
    cluster: kube-test.internal.degiro.eu
    namespace: default
    user: rigid-admin
current-context: default-context
users:
- name: rigid-admin
  user:
    token: ey…1A

Additional context

Faced the same issue in my mac, deleting the ~/Library/Application Support/Lens folder not helps,
Upgrading to 5.5.2-latest.20220530.1 version solved the issue
https://api.k8slens.dev/binaries/Lens-5.5.2-latest.20220530.1.dmg

Thanks @sann3 , I’ll try that version (cannot update from within Lens, but will download it manually).


feat: move parameter tests into market sim from research internal

Description
Dump of Parameter Test code from research-internal into public repo. No major changes other than renaming some folders.

I'm just wondering why not to move the latest parameter-test in research-internal, but it's totally okay to use the origin one if better.

This was meant to be a straight dump of the latest code (barring some moving of files about) from research-internal to here. Do you mean I used an old version/missed changes?


serverid in FilePond:removefile

Dear @rikschennink,
FilePond:removefile does not contain serverid => i.e. it is always null.
I urgently need to know the serverid of the removed file.
var x = document.getElementById('fpo-file');

x.addEventListener('FilePond:removefile', e => {
    console.log('File r', e.detail);
});

Using newest version of filepond on Windows, Chrome 76.
I hope you are able to help me out here as I am kind in a very pressured time environment. :/
Best,
Manuel

You can find the server id here:
document.body.addEventListener('FilePond:removefile', e => {
  console.log('File r', e.detail.file.serverId);
});

No, as shown above, this does not work. is always null.
Tested it with window, document.body and as shown above with the element itself.

Then you're probably not returning it in your server.process method?
https://codesandbox.io/s/vanilla-filepond-2oltb

I am returning in the process call and I see & get it fom FilePond:processfile.
When I am clicking the undo cross in UI the call gets to the server, reverts and in JS I get the FilePond:removefile callback. In this callback the serverid is null.
Per your docs I have to return an empty resonse: https://pqina.nl/filepond/docs/patterns/api/server/#revert

@rikschennink Further information, I have deleted all sensitive data:
        FilePond.registerPlugin(
            FilePondPluginImagePreview,
            FilePondPluginImageExifOrientation,
            FilePondPluginFileValidateSize
        );

        FilePond.setOptions({
            server: {
                process: '/api/v1/filepond/process',
                revert: '/api/v1/filepond/revert',
                restore: '/api/v1/filepond/restore/',
                load: '/api/v1/filepond/load/',
                fetch: '/api/v1/filepond/fetch/'
            }
        });

        [HttpDelete("revert")]
        public async Task<IActionResult> Revert()
        {
            return Ok();
        }

        [HttpPost("process")]
        public async Task<IActionResult> Process(IFormFile file)
        {
            return Ok("test");
        }

@rikschennink Did further testing.
When I only have:
FilePond.setOptions({
            server: {
                process: '/api/v1/filepond/process'
            }
        });

... the FilePond:removefile file element contains serverid correct, but then it does not call my revert method on the server.
If I add the
FilePond.setOptions({
            server: {
                process: '/api/v1/filepond/process',
                revert: '/api/v1/filepond/revert'
            }
        });

... the serverid is null in the element of FilePond:removefile.

Hm, weird, will take a look later this week.

@rikschennink But I am collecting the serverid's I get from processing (uploading) the files so I can provide them on form submit. If a user removes the file, I have to remove the file too from the form, right?

If the upload has been reverted the file is no longer on the server so it doesn't have to be in the list when the form is submitted (FilePond also generates hidden input fields with the file server ids).

@rikschennink Thank you! It was exactly this. I also figured this out.  Anyway, thank you very much.
But just to give you  a feedback on this:
If the revert http call is denied / fails / Bad Request / whatever, the serverid field is still set. That was what confused me. Maybe it still would be nice to have the serverid on the remove event. :)

A follow up almost three years later :stuck_out_tongue_winking_eye:
I also encountered the same "issue" after migrating from a very old version (1.8.8), which I was using with the vue adapter (2.1.6).
In the previous versions, the serverId was provided in the remove event.
It was useful to me, since I am maintaining a store with enriched infos on my media. So I need a way to know which media has successfully been removed, to keep my store up to date, which does not seem possible with this "new" behaviour.

@fbruffaert I'll take this into account when designing a new api for v5


Update migrate-your-extension-from-manifest-v2-to-v3.md

Removed mentions of old Edge versions and related text per
DELIVERABLE 36566120

Docs Build status updates of commit 187ace6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/developer-guide/migrate-your-extension-from-manifest-v2-to-v3.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


rules_cc runfiles library does not provide BAZEL_CURRENT_REPOSITORY

Description of the problem / feature request:
The runfiles library has been deprecated in bazel-tools and now points to the library in rules_cc, but the instructions ported over refer to BAZEL_CURRENT_REPOSITORY, which is not present in the rules_cc runfiles library.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
I made a branch off something I was working on. You should be able to run touch data/inputs/01.txt && bazel build //src/day/01 using //https://github.com/flurie/aoc-2024/tree/demo-rules-cc-runfiles if you install the prereqs (nix and devenv) and it should work on macOS and Linux.
What operating system are you running Bazel on?
macOS 14.5
What's the output of bazel info release?
release 7.4.1- (@non-git)
If bazel info release returns "development version" or "(@non-git)", tell us how you built Bazel.
It is built from nixpkgs 24.11.
What version of rules_cc do you use? Can you paste the workspace rule used to fetch rules_cc? What other relevant dependencies does your project have?
http_archive(
    name = "rules_cc",
    urls = ["https://github.com/bazelbuild/rules_cc/releases/download/0.0.17/rules_cc-0.0.17.tar.gz"],
    sha256 = "abc605dd850f813bb37004b77db20106a19311a96b2da1c92b789da529d28fe1",
    strip_prefix = "rules_cc-0.0.17",
)

What Bazel options do you use to trigger the issue? What C++ toolchain do you use?
.bazelrc:
build --host_platform=@rules_nixpkgs_core//platforms:host
build --crosstool_top=@nixpkgs_config_cc//:toolchain

for completeness, the output when the repro command is run with --announce_rc:
INFO: Reading 'startup' options from /nix/store/zsyc077bgm4g3xq3h0a2qfzw4g4jzjfi-bazel-rc: --server_javabase=/nix/store/dd8l9acgfnax38j7wvz0lh96c2vkxyg3-zulu-ca-jdk-21.0.4
INFO: Options provided by the client:
  Inherited 'common' options: --isatty=1 --terminal_columns=104
INFO: Reading rc options for 'run' from /nix/store/zsyc077bgm4g3xq3h0a2qfzw4g4jzjfi-bazel-rc:
  Inherited 'build' options: --extra_toolchains=@bazel_tools//tools/jdk:all --tool_java_runtime_version=local_jdk --java_runtime_version=local_jdk
INFO: Reading rc options for 'run' from /Users/flurie/Repos/github.com/flurie/aoc-2024/.bazelrc:
  Inherited 'build' options: --host_platform=@rules_nixpkgs_core//platforms:host --crosstool_top=@nixpkgs_config_cc//:toolchain

toolchain:
nixpkgs_git_repository(
    name = "nixpkgs",
    revision = "release-24.11",
)

nixpkgs_cc_configure(
    name = "nixpkgs_config_cc",
    repository = "@nixpkgs",
)

Have you found anything relevant by searching the web?
No
Any other information, logs, or outputs that you want to share?
No

After some additional digging, I see what is going on here.
the cc_* rules all end up calling the native rules under the hood, but the native rules in 7.4.1 and even 8.0.0rcs don't recognize the new runfiles library label, only master does. So that check likely needs to move over to rules_cc.

FYI my current work-around is to add a redundant entry in deps just so that bazel adds the correct definition:
    deps = [
        "@rules_cc//cc/runfiles",
        # The next line is a hack to get BAZEL_CURRENT_REPOSITORY working.
        "@bazel_tools//tools/cpp/runfiles",
    ],

looks like this is still being fixed in bazel itself, not rules_cc, and looks like it'll be in 8.1.0 https://github.com/bazelbuild/bazel/issues/24465

@jwnimmer-tri's workaround or just using @bazel_tools//tools/cpp/runfiles for now is recommended until 8.1.0 lands. @bazel_tools//tools/cpp/runfiles will keep working, so there is no rush to migrate.


sbclPackages.nyxt-gtk: 3.11.3 -> 3.11.4

Description of changes
Changelog: https://nyxt.atlas.engineer/article/release-3.11.4.org
The nyxt pinned swank(slime) cannot build with sbcl 2.4.2 updated recently.

nix build '.#sbclPackages.nyxt failed due to swank failed.
nix build '.#sbcl_2_4_1.nyxt successed

To fix this, I update the swank used by nyxt to the newest release instead of pinned one.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 293729 run on x86_64-linux 1

2 packages built:

nyxt
sbclPackages.nyxt


Translation problems of starter

There is no additional button for "update" translation in the launcher settings. It should be divided into two parts
It should be like this:
Update initiator     update

I mean, changing the updateoption will also affect its buttons. It should be divided into two parts

@Iqrar99


Add Factor platform as an SSR option

Thanks for your contribution. However, a more suitable place for this would be https://github.com/dobromir-hristov/vuecommunity.

Why's that? @phanan You have two equivalents already on the same page?


Custom relationships input form issues

Environment

Python version:
Nautobot version: 1.0.0b3

Steps to Reproduce

Create a custom relationship

Name               | Descr | Type | Source Object | Destination Object |   |
------------------ | -   | ------------- | -------- | ------ | -----|---------- --
circuitcustomerip  | -   | One to Many | circuits  | circuit | ipam | IP address |   |
circuitproviderip  | -   | One to Many | circuits  | circuit | ipam | IP address

Try to fill relationship with Circuit <> IP address with database containing thousands of objects

Expected Behavior
Search forms for objects auto-completes or permits manual inputs.

Observed Behavior
Search forms do not allow to input values. Instead console logs shows :
nautobot_1  |   "GET /api/circuits/circuits/?q=&limit=50&offset=250&brief=true HTTP/1.1" 200 8403
nautobot_1  | 19:51:01.110 DEBUG   nautobot.core.api.views.ModelViewSet views.py                  get_serializer_class() :
nautobot_1  |   Request is for 'brief' format; initializing nested serializer
nautobot_1  | 19:51:01.110 DEBUG   nautobot.core.api.views.ModelViewSet views.py                  get_serializer_class() :
nautobot_1  |   Using serializer <class 'nautobot.circuits.api.nested_serializers.NestedCircuitSerializer'>
nautobot_1  | 19:51:01.119 INFO    django.server :
nautobot_1  |   "GET /api/circuits/circuits/?q=&limit=50&offset=300&brief=true HTTP/1.1" 200 8550
nautobot_1  | 19:51:01.166 DEBUG   nautobot.core.api.views.ModelViewSet views.py                  get_serializer_class() :
nautobot_1  |   Request is for 'brief' format; initializing nested serializer
nautobot_1  | 19:51:01.166 DEBUG   nautobot.core.api.views.ModelViewSet views.py                  get_serializer_class() :
nautobot_1  |   Using serializer <class 'nautobot.circuits.api.nested_serializers.NestedCircuitSerializer'>
nautobot_1  | 19:51:01.176 INFO    django.server :
nautobot_1  |   "GET /api/circuits/circuits/?q=&limit=50&offset=350&brief=true HTTP/1.1" 200 8456
nautobot_1  | 19:51:01.217 DEBUG   nautobot.core.api.views.ModelViewSet views.py                  get_serializer_class() :
nautobot_1  |   Request is for 'brief' format; initializing nested serializer
nautobot_1  | 19:51:01.218 DEBUG   nautobot.core.api.views.ModelViewSet views.py                  get_serializer_class() :
nautobot_1  |   Using serializer <class 'nautobot.circuits.api.nested_serializers.NestedCircuitSerializer'>
nautobot_1  | 19:51:01.227 INFO    django.server :
nautobot_1  |   "GET /api/circuits/circuits/?q=&limit=50&offset=400&brief=true HTTP/1.1" 200 8249
nautobot_1  | 19:51:01.278 DEBUG   nautobot.core.api.views.ModelViewSet views.py                  get_serializer_class() :
nautobot_1  |   Request is for 'brief' format; initializing nested serializer
nautobot_1  | 19:51:01.278 DEBUG   nautobot.core.api.views.ModelViewSet views.py                  get_serializer_class() :
nautobot_1  |   Using serializer <class 'nautobot.circuits.api.nested_serializers.NestedCircuitSerializer'>
nautobot_1  | 19:51:01.288 INFO    django.server :

I was just about to file a very similar issue, glad I saw this first!
It looks like the DynamicModelChoiceField that's auto-created for any relationship on a model is operating under the expectation that the related model has a name field, and doesn't work well if the related model (such as IPAddress) doesn't have such a field.
DynamicModelChoiceField has a display_field parameter (defaulting to "name") that can be used to change its behavior in this regard, but the Relationship model doesn't currently expose a way to influence that field. We might need to add a couple of fields to the Relationship model to handle this.

Re-Tested OK!


[BUG] Backup created in prior release takes considerable time to show up on the backup page first time.

Describe the bug
For the first time, the backups created in prior release take lot of time to show up on backup page.
50 Volumes with 10 backups each, takes about 7-10 min to load properly on the backup page. (User will have to refresh the page to see the all the backups getting loaded.
At first user might get confused that the older backups are not appearing but should see them after a while.
To Reproduce
Steps to reproduce the behavior:

Deploy Longhorn v1.1.2
Create 50 volumes and take 10 backups of each volume.
Deploy Longhorn v1.2.0-preview-1 on another cluster.
The backup page in second cluster fails to list initially and slowly load them in about 7-10 min.

Expected behavior
UI can have some indication message that backup sync up is in progress.
Environment:

Longhorn version: v1.2.0-preview1
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): Kubectl
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: RKE - K8s 1.21.4

Number of management node in the cluster: 1
Number of worker node in the cluster: 3

Node config

OS type and version: Ubuntu 20.04
CPU per node: 2
Memory per node: 4
Disk type(e.g. SSD/NVMe): SSD
Network bandwidth between the nodes: Upto 10 Gi

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): DO
Number of Longhorn volumes in the cluster: 0

I think the problem is the same as https://github.com/longhorn/longhorn/issues/2915#issuecomment-905111637

UI can have some indication message that backup sync up is in progress.

For this, we'll add Backup state https://github.com/longhorn/longhorn/issues/2916#issuecomment-904319017 to indicate the current backup status.
We also move backup creation from the HTTP API layer to the backup_controller layer. It means that backup creation is also asynchronous. 50 Volumes with 10 backups each will cause 500 backup CRs created and need to wait for the backup_controller to perform 500 backups in parallel. Every backup creation completed would request backup_target_controller/backup_volume_controller/backup_controller to pull the latest information from the remote backup target.
I'm thinking that how to achieve show the backup sync up is in progress indication message.

If without local cluster backup creation, it seems doable by set spec.syncRequestedAt=time.Now().UTC() of the BackupTarget CR, and waits all the BackupVolume and Backup CRs status.lastSyncedAt >= spec.syncRequestedAt=time.Now().UTC().
If with local cluster backup creation, we have to make sure all the Backup CR status=Completed and as above, set spec.syncRequestedAt=time.Now().UTC() and waits all the BackupVolume and Backup CRs status.lastSyncedAt >= spec.syncRequestedAt=time.Now().UTC().

@khushboo-rancher We had added the WebSocket support on the Backup page on v1.2.0. Could you please double verify it to check if it meets the requirement?

Validating in progress,
Cluster info:

1 control node + 3 worker nodes
Node spec:

EC2 t2.large, 2 cpus, 8GB ram

K8s distro:

v1.20.10 deploy via rancher 2.5.9

Test:

Setting up two identical clusters, 1 with v1.2.0-preview1 and the other one with master-head version (2021-09-14)
On the first cluster, deploy 50 volumes (size 128Mi) with 10 backups of each volume
Then point the 2nd cluster to the same s3 bucket

then observe the backup page
Result:
I can tell with latest master version it is much faster also the display will be showing the backup-volumes when they are being pulled.
But I would like to find a way to get a metric/measurement before close this issue.

@khushboo-rancher please take a look.
By observing v1/ws/1s/backupvolumes with today's master (ui: 4de5ec1), the WS messaging stops in about 2.5mins.
And the in-progress backups will look like this:

HAR file for reference: ui-50x3-backups.har.zip

I see, there is improvement.
Earlier with 50 volumes having 10 backups each, it was taking around 7 mins. Now on the master, it takes around 2 mins.
@jenting As @kaxing has mentioned that WS messaging stops in about 2.5mins, so user have to refresh the page to see the backups loaded after 2.5 min.
For example, 50 volumes with 50 backups takes around 8 mins, in that case backups stop getting updated the backup page after 2.5 min and user has to refresh the page to see all the backups.

We'll check the culprit is backend or frontend first. Thanks for the testing effort.

Hey @jenting @khushboo-rancher, sorry for the miswording here.
When I say WS messaging stops, means the communication finished loading the information for backupvolumes.
Attaching screen recording for clarifying, you can see the backup polling is about to finished, and data will silently fill up in the table: Click to open the clip

Testing again with v1.2.1-rc2, with more than 100 volumes, the backups items can be downloaded in about 5mins. cc @khushboo-rancher maybe there is other combination(size x volume numbers) to be tested with, but as for now I don't have to refresh page to see all the backupvolumes being downloaded.


docs: add body-parser

Overview
Closes #160.
This pull request adds section for body-parser and its alternative (namely, milliparsec)

Discussion on a discord server revealed that we should probably wait until default post limit is implemented into millisec. Don't want to give malicious people the ability to DDoS a server from this recommendation.

It may also be worth explaining that some simple use cases don't need a package
Maybe we list "native" as an alternative and give some examples?