Interactivity does not work in Jupyter Lab

Everything works fine in Jupyter Notebook, but not in Jupyter Lab (version 0.34.7).

Styling of the buttons does not seem to work
The buttons have no functionality; e.g. pressing the panning button does not enable panning

On the Javascript console I can the following error whenever the mouse pointer enters the area of the figure, which may or may not be related:

I had a similar problem when I was using a notebook which had output cells with plots generated by (%matplotlib notebook)
I fixed it by:

delete all output cells
save notebook
reload page
restart kernel
run with %matplotlib widget

I think that %matplotlib notebook injects some kind of javascript that kills something inside jupyter lab.

@feanor12 Thanks, it looks like you are right. After restarting and clearing all output, the buttons work (except for the "power" button, which has already been reported in #61) and also the mouse pointer coordinates are shown properly in the bottom right corner.
The buttons still look Windows 95-ish, though (not sure, if this is a bug).

So maybe this is the cause for #62 as well.

@feanor12 Yes!

Is this supposed to work with Matplotlib FuncAnimations too? All I get is a blank output and the FuncAnimation itself--which works just fine in IPython in a Terminal window--does not call the update function I defined for each frame.  Thanks in advance for any suggestions.

@pdeitel that is extremely odd.  I am a bit worried that your generator is raising someplace and the exceptions are getting snarfed incorrectly.  Internally, the animation module homgonizes all the input to generators (an integer gets turned into range).

I think that %matplotlib notebook injects some kind of javascript that kills something inside jupyter lab.

Yes, all of the js to make the plot interactive is inserted by the notebook backend (which is why it does not work in jlab as they have closed that convenient but large security hole).

Additionally to @feanor12's recipe I had to close all tabs on the right hand side (open notebooks). Probably their javascript was still interfering with ipympl

Probably another solution that works for me in both, notebook and jupyterlab (up to version 0.35.4):
import matplotlib
matplotlib.use('module://ipympl.backend_nbagg')

from matplotlib import pyplot as plt
fig, ax = plt.subplots()
ax.plot([1,2,3], [4,3,2])
fig.show()

I still see the behaviour as described by @MerlinPendragon in his original post issue #62  on Firefox. On Chromium the example runs fine.
I am on Fedora 29.
$ conda list | grep jupyter
jupyter                   1.0.0                      py_1    conda-forge
jupyter_client            5.2.4                      py_0    conda-forge
jupyter_console           6.0.0                      py_0    conda-forge
jupyter_core              4.4.0                      py_0    conda-forge
jupyterlab                0.35.3                   py37_0
jupyterlab_launcher       0.13.1                     py_2    conda-forge
jupyterlab_server         0.2.0                    py37_0

$ rpm -q firefox
firefox-64.0-4.fc29.x86_64

$ jupyter labextension list
JupyterLab v0.35.3
Known labextensions:
   app dir: /mnt/sdc1/home/gtrojan/miniconda3/envs/devel/share/jupyter/lab
        @deathbeds/jupyterlab-fonts v0.6.0  enabled  OK
        @jupyter-widgets/jupyterlab-manager v0.38.1  enabled  OK
        @pyviz/jupyterlab_pyviz v0.6.4  enabled  OK
        jupyter-matplotlib v0.3.0  enabled  OK
        jupyterlab_vim v0.10.1  enabled  OK

import matplotlib
matplotlib.use('module://ipympl.backend_nbagg')

This solution worked form me, only after restarting the kernel and jupyterlab.
Looks like the widget function has bugs. After manipulating the graph and then hitting the button to turn off interactivity the graph goes all fuzzy and turns to black and white.
I don't know what the issue is for that

What about:
Matplotlib is currently configured to use the 'notebook' backend which is suitable for the classic Jupyter Notebook and derivatives (and does not work in JupyterLab).  Matplotlib does not support changing from the 'notebook' backend to the 'widget' backend while the kernel is running. To use the 'widget' backend, which is supported by JupyterLab, it is recommended that you restart your kernel and clear all output cells. See (insert helpful link to docs) for details.

It means once you’ve run %matplotlib notebook, you can’t later switch to %matplotlib widget (because the two will use different event loops). You need to only ever use one or the other while the kernel is running.
Open to suggestions to language that would make that more clear, but unfortunately that’s exactly what the existing message says to me (but then again I’ve been doing this for way too long).

right, just restart the kernal and run %matplotlib widget

I have a similar issue - I have installed everything as required here. When I do an interactive plot in Jupyter Lab it is run without an error message, but the plot is just not displayed. Instead I have the output from the screenshot. What should I do?

None of the suggestions work currently. This was working recently.

@cottrell can you tell us how you installed ipympl? You might have missed an installation step.
I think this issue should be closed. ipympl does work in JupyterLab now.

I think this issue should be closed. ipympl does work in JupyterLab now.

As you wish. @cottrell, feel free to open a new issue with more comprehensive information about your environment and a reproducible test case.

Interesting ... I just tried at home on a Linux system (again following https://stackoverflow.com/questions/50149562/jupyterlab-interactive-plot) and everything works again.
Will try again on the work setup ... likely some interaction or version issue.

Hi,
I use %matplotlib ipympl, all the functions can work, exclude resize function at the below right corner.
Does anyone know what the problem is, and how can I fix it? thanks

I'm still facing the issue here. All I get is that Canvas(toolbar=Toolbar(toolitems=[('Home', 'Reset original view', 'home', 'home'), ('Back', 'Back to previous …
Jupyterlab 2.1.4
ipympl 0.5.6
You can find the Pipfile and Pipfile.lock files in https://gist.github.com/ijpulidos/81edbe253bdbbe270e94a0eff75f34c0 (using pipenv to manage the environment)

Ok, had to manually run jupyter labextension install @jupyter-widgets/jupyterlab-manager@2 for them to work. Not really sure why or how all of this works, but that did it for me.

Ok, had to manually run jupyter labextension install @jupyter-widgets/jupyterlab-manager@2 for them to work. Not really sure why or how all of this works, but that did it for me.

Thank you - this solution worked for me on
Jupyerlab 2.2.4
ipympl 0.5.7


SSH authentication failed

Debug
DEBUG ssh: == Net-SSH connection debug-level log END ==
 INFO ssh: SSH not up: #<Vagrant::Errors::SSHAuthenticationFailed: SSH authentication failed! This is typically caused by the public/private
keypair for the SSH user not being properly set on the guest VM. Please
verify that the guest VM is setup with the proper public key, and that
the private key path for Vagrant is setup properly as well.>

Config
# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure(2) do |config|
    config.vm.box = "dummy"
    # diable syncd folder
    config.vm.synced_folder '.', '/vagrant', :disabled => true
    config.vm.provider :aws do |aws, override|
        aws.access_key_id = 'xxxxxx'
        aws.secret_access_key = 'xxxxxx'
        aws.region = 'eu-central-1'
        aws.ami = 'ami-accff2b1'
        aws.instance_type = 't2.micro'
        aws.availability_zone =  "eu-central-1b"
        aws.security_groups = ['xxxxx']
        aws.keypair_name = 'xxxxx'
        aws.elastic_ip = 'xxxxxx'
        aws.security_groups = ['xxxxxx']
        aws.subnet_id = 'xxxxx'
        override.ssh.username = "jc"
        override.ssh.private_key_path = "/Users/jc/Documents/Keys/xxxxxx.pem"
    end
end

I can SSH through manually works fine. But I keep getting SSH authentication failed through Vagrant.

Nevermind, the override.ssh.username has to be 'ubuntu'.
Please close this, thanks.


<InlineQueryContext>.answerInlineQuery(...) throws Bad Request

Code
telegram.updates.on('inline_query', (context) => {
  console.log(message);
  return message.answerInlineQuery([{
    type: 'article',
    title: 'foo bar baz',
    input_message_content: {
      message_text: 'fiz'
    }
  }]);
});

Expected behavior
sending an inline query result
Actual behaviour
APIError: Bad Request: can't parse inline query result: Can't find field "id"
Environment

package
version

puregram
2.0.4 & 2.2.0

false positive issue
every TelegramInlineQueryResult requires an id field: documentation
imagine you have 5 equal inline results, user presses on one of them, how should Telegram determine which is where and which did user press? this is why that id field is required and throws Bad Request when not specified


[DBZ-1164] Handle time 24:00:00 supported by PostgreSQL

Issue: https://issues.jboss.org/projects/DBZ/issues/DBZ-1164?filter=allopenissues&orderby=created+DESC%2C+priority+ASC%2C+updated+DESC
For Time type in PostgreSQL, 24:00:00 is supported, but is converted to null by JDBC value converter.
After this patch, 24:00:00 is converted to<PHONE_NUMBER>0 in microsecond.

Thanks a lot! Could you cover this in the existing snapshot and streaming
producer ITs, too?

@gunnarmorling No problem!

Hi @gunnarmorling, tests for snapshot and streaming producer have added now

Looks great, @Wang-Yu-Chao! Thanks, merging.

Rebased and applied. I've pushed one more commit for some clean-up. Thanks again, @Wang-Yu-Chao!


South Asian Accent for Female

I have a question regarding the accent for female. It is good for male but not very good at female accent. Can you please tell me about why ? and also guide me to fine tune it for female voices.

Hello zahid,
Yes the model is predominantly trained on male speaker data! I had used
this repo for training maybe you can find something better:
https://github.com/152334H/DL-Art-School
Personally, i think if you want to go the finetuning route it’ll be
interesting to explore other models like XTTS!
Best regards,
Ahmed Hanzala
On Wed, 15 May 2024 at 9:24 AM, Zahid Imran @.***>
wrote:

I have a question regarding the accent for female. It is good for male but
not very good at female accent. Can you please tell me about why ? and also
guide me to fine tune it for female voices.
—
Reply to this email directly, view it on GitHub
https://github.com/ahmedHanzala/urdu-tts/issues/4, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZEDJQMYOF4Q45OWV5RCFF3ZCLPQXAVCNFSM6AAAAABHXLPOZWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI4TMOBTGUZDSMQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thanks Ahmed Hanzala


Typo in docs 'Writing upgradeable contracts'

Found a minor typo in the docs.
https://docs.openzeppelin.com/sdk/2.5/writing-contracts#avoid-initial-values-in-field-declarations
State is : Make sure that all initial values are set in an initializer function as shown above;
But it should be below, right? Cause the correct example snippet is below this paragraph?

Thanks for reporting @Maxstgt! I've fixed this https://github.com/OpenZeppelin/openzeppelin-sdk/commit/a34a6a60d516487c38b5525cb341420f1183d84a.


Add guidance on operation summary & description

Add guidance on operation summary & description so that they are clear and human readable.
The guidance should indicate:

What operation summary & description are
What they are used for and how it related to API gateways
What kind of information we are expecting

Business-oriented instead of technical docs
Human readable

How they relate to operationId
What Swagger is generated for the code sample

Our current guidance provides a good example:
/// <summary>
///     Get Health
/// </summary>
/// <remarks>Gets the current health status of the API</remarks>
[HttpGet]
[Route("health")]
[SwaggerOperation("Health_Get")]
[SwaggerResponse(HttpStatusCode.OK, "API is up & running")]
[SwaggerResponse(HttpStatusCode.InternalServerError, "API is not available")]
public IHttpActionResult Get()
{
    return Ok();
}

We moved away from [SwaggerOperation("Health_Get")] attribute with the swashbuckle 4.

This is not related to operationId but more the summary and description.
Can do this after holiday.


Add robot.txt file

Add front matter to flag drafts so search bots won't index page.
with meta element.

This partial would need to be updated: https://github.com/gc-da11yn/gc-da11yn.github.io/blob/main/src/_includes/partials/head.njk


Email font looks to narrow – how to configure it?

The font for the generated emails is Ubuntu with a small line height. How can I change that? Is there a configuration for this?
Example:

Line height can be set for each text element, but there is not currently a way to set it globally unfortunately.

I generate mjml code now that contains font attributes on each paragraph, so now it looks good.


Fixed bug in inserting literal NULL values as part of a SELECT statement

Signed-off-by: Zach Musgrave<EMAIL_ADDRESS>

This fixes #261

This fixes #261


A payId must be provided in the request body.

Expected Behavior
Create PayID
Actual Behavior
WARN 400 : ParseError[MissingPayId]: A payId must be provided in the request body.
Context
curl --location --request POST 'http://<IP_ADDRESS>:8081/users' \
--header 'PayID-API-Version: 2020-06-18' \
--header 'Content-Type: application/json' \
--data-raw '{
  "payId": "bob$<IP_ADDRESS>",
  "addresses": [
    {
      "paymentNetwork": "XRPL",
      "environment": "TESTNET",
      "details": {
        "address": "rek7FQvkQxQQNGTtfM2Fr66s7Nm3k87vdS",
        "tag": "123"
      }
    }
  ]
}'

Potential Solution
Unknown
Steps to Reproduce
Clone
Docker Compose
PostMan Request
Environment

Node version: v12.18.2
NPM version: 6.14.5
Operating System and version: OSX 10.15.6
PayID server version: 1.1.0
PayID Version header (if applicable): Above

Close postman, open postman, retry request


Add info variant for Toggle component's iconAfter element

Add missing "info" variant for iconAfter element in Toggle and ToggleGroup components


gradient/ laplacian supervision

hello, thanks for this implementation. how would you go about implementing the gradient or laplacian supervision? i wonder if it is involving the gradient of the network directly or some sort of sobel filtering over outputs (sample patches instead of pixels?), which would be much less elegant i guess?

I have not tried to implement this supervision, so I'm not sure how it will happen. According to the paper, section 3.2 of the appendix:

The ground truth gradient image is computed using the Sobel filter, and is scaled by a constant factor of 10 for training. The ground truth Laplace image is computed using a Laplace filter, and is scaled by a constant factor of 10,000 for training.

And also:

We train for 10,000 iterations, and at each iteration fit on every pixel in the gradient or Laplacian image.

But I could not find how they calculate the gradient of the Siren output. It's worthy taking a look at other implementations, and see if anyone got this working. If you find anything please link it here.

i was thinking to use torch.autograd.grad with only_inputs=True, but i never used this feature directly so i could be wrong.

i did a first version just with numerical gradient (not the complicated autodiff stuff yet)
https://gist.github.com/etienne87/0519972704e711c20706f56d55b63890
grad = [None,None]
for r in [-1,1]:
  for dim in [0,1]:
      bx2 = bx.clone()
      bx2[:,dim] += r/100
      o = net(bx2)
      if grad[dim] is None:
         grad[dim] = torch.zeros_like(o)
      grad[dim] += r * o

it more or less learns the image (when you train without the rgb supervision) up to a constant. it does not really seem to help.

with just rgb supervision it is better so far:

That's cool!
I also tried to get this working today, extracting patches from the image and using sobel filtering. My model learned the correct gradients and also started to get decent results on the laplacian, but the RGB colors are totally wrong.
Gradient of predictions:

RGB predictions:

but you learn directly the gradient, or make so that the gradient of your network match the gradient of the ground truth?

Yeah, I compare the numerical gradient of the network output against the ground truth.
The official implementation is out, and they use autograd to calculate the networks gradients.


ENH/REF: Use new view-types/transformers

Placeholder for changes related to new view-types and transformers

Reviewed with @gregcaporaso. Last remaining TODO is to handle any relevant renames that come in from @ebolyen.

this is ready for merge once the last remaining todo is completed, and the tests are passing.

Renaming is done, tests should pass once transformers passes.


Re-architect the web server

Like a lot of the code in 2.0.0, it was meant to get something in place.  The lack of direct access to metadata, etc, probably means it should get replaced with something that is multiprocess+IPC.  It should also support websockets.

https://github.com/aw-was-here/Now-Playing-Serato/tree/revamp-webserver

A quick test on Catalina w/ python 3.9 triggers https://bugs.python.org/issue32146 ☹

OK, I've found a work around... reworked the launcher a bit for pyinstaller-based setups.


Whitelist http to https domain

Hi,
may I request whitelist of domain as it block when I am passing my http image

Please can you provide a sample URL that allows someone else to reproduce. Note that we block questionable categories on our public service due to legal concerns. See: https://github.com/weserv/images/issues/285#issuecomment-828176654.

It looks like the DNS record for this domain name is either incorrect or missing. Are you sure it's a public-facing website?
https://redbot.org/?uri=http://des.aspial.sg/PMS/pmm_maxi/photo/99472-01-05-3D VIEW.jpg
https://tools.keycdn.com/performance?url=http://des.aspial.sg/PMS/pmm_maxi/photo/99472-01-05-3D%2520VIEW.jpg

There's not much we can do for this. Please report this to this website if it continues to be a problem.

Hi Kleis,
Thanks for the help, I will clarify with the website administrator.
On Thu, 11 Jul 2024, 1:39 am Kleis Auke Wolthuizen, <
@.***> wrote:

It looks like the DNS record for this domain name is either incorrect or
missing. Are you sure it's a public-facing website?
https://redbot.org/?uri=http://des.aspial.sg/PMS/pmm_maxi/photo/99472-01-05-3D VIEW.jpg
https://tools.keycdn.com/performance?url=http://des.aspial.sg/PMS/pmm_maxi/photo/99472-01-05-3D%2520VIEW.jpg
screenshot.png (view on web)
https://github.com/weserv/images/assets/12746591/b846268d-43e0-4ca6-ad82-2add187e8619
There's not much we can do for this. Please report this to this website if
it continues to be a problem.
—
Reply to this email directly, view it on GitHub
https://github.com/weserv/images/issues/426#issuecomment-2221095340, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AI5AM4AJNBMO7PMMPZKW2PLZLVWVDAVCNFSM6AAAAABKJD6WG2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRRGA4TKMZUGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hope this helped, please feel free to re-open if questions remain.


I can correlate a message without process instance id

Currently it is only possible to correlate a message if the process instance id is provided.
AT:

I don't have to provide a process instance id when correlating a message.
I can use businessKey and or variables

Example:
    runtimeService.createMessageCorrelation("stop")
      .processInstanceVariableEquals(...)
      .processInstanceBusinessKey(...)
      .correlateAll();

now can correlate on any combination of executionId, processId, business key and event name and type, still need to do the variables

Variables added as well


width overide tests added

Tests for width-override.
using git diff for checking tests is not a good option, results depends on sass compilers and versions. for me your test fails because my compiler outputs no new line between each rule set. I only commit the new css file (test-width-override.css) and didn't commit test.css to prevent test failing on your system.
a better solution for testing should be developed.
Thank you.

I closed this because of misspelled in test-width-overide.sass file


Bug pkg/encoding builtins evaluate before args are concrete

The buitin functions of the encoding packages evaluate before args are concrete.
bug.cue:
import "encoding/csv"

foo: csv.Decode(data)
data: bytes

$ cue eval bug.cue
foo: error in call to encoding/csv.Decode: runtime error: invalid memory address or nil pointer dereference:
    ./bug.cue:3:6

I've tested encoding/base64 and encoding/csv and both seem to have the issue.
This behavior is distinctly different from the crypto packages which do not have this issue:
no-bug.cue:
import "crypto/md5"

foo: md5.Sum(data)
data: bytes

$ cue eval no-bug.cue
import "crypto/md5"

foo:  md5.Sum(data)
data: bytes

this was tested using the v0.0.14 release of cuelang.

Tested encoding/hex and only Decoded seems to follow this behavior.  Encode, Dump, EncodedLen, DecodedLen seem to behave as expected.

The problem was that creating a Reader might result in an error which was unchecked, causing the function to be called with a nil error. The root cause was a failure to do the do() check after calling reader. Rather than fixing this case I'll fix it to unconditionally do this check.
hex.Decode is different, as it only takes a string argument (this is arguably too strict, but that's a different debate).

This issue has been migrated to https://github.com/cue-lang/cue/issues/178.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


Parsing Json

Hello Ivan,
Thank you for sharing this great work.
I'm trying to parse a simple Json request object from a Post request.
{"page":1, "pageSize":10}
None of the examples I found work properly. For example "class web::json::value’ has no member named ‘cbegin’".
I could see how you made a json object from scratch and it's very easy.
Do you have some easy (or not so easy) way to do the get the json object from a request?
Thanks in advance,
Diego

Hello,
io am facing the same problem...did you find the solution? If yes, can you share it?
Thanks in advance
Adrian..


Visualize document state graphically

Description
This came up as an idea during the retreat: It would be nice if the datatracker graphically visualized at which state in the process a given document is (and for how long), rather than just showing pretty cryptic state labels.
Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

Something like this?

or a progress bar type?

or an annotated FSM?

We didn't discuss specifics. Progress bar or annotated graph were what came to my mind. We want to be compact, but we also want to  include as much info as we can, so the table becomes less cluttered.

Note this is stalled awaiting more discussion - please bring it up during the 114 sprint.

Wonder if we can integrate https://ietf-wg-httpapi.github.io/ somehow.


Handle ping/pong events in ASGIWebSocketAsyncNetworkStream

We've been occasionally hitting errors in CI apparently due to our ASGI app receiving Ping events in our tests, and hitting the error just below the lines added in this PR.
I don't know if there's a reason not to make this change but figured I would propose it. If there's a better solution than what is proposed here, any insight would be appreciated.

Hey @dmontagu 👋
Good catch indeed. I think the reason why I didn't implement Ping/Pong handling in the transport is because it's not part of the ASGI specification.
I even have a unit test that was relying on Ping message to check the UnhandledWebSocketEvent exception 😅
https://github.com/frankie567/httpx-ws/blob/cd0a3dc7e9511bf926122332b3091664ea814584/tests/test_transport.py#L81-L91

The easiest solution right now is to set the keepalive_ping_interval_seconds parameter to None on the client to disable the keepalive ping, which should be okay in a CI context.
That being said, as it's enabled by default, it's true that it provokes surprising errors with the ASGI transport. I think it would probably better to automatically disable it if we detect that we work with the ASGI transport rather than trying to handle the ping. What do you think?

That being said, as it's enabled by default, it's true that it provokes surprising errors with the ASGI transport. I think it would probably better to automatically disable it if we detect that we work with the ASGI transport rather than trying to handle the ping. What do you think?

Yes.

Out of curiosity, in which project are you using it? 🙂

😉

I made a PR with my proposed solution: https://github.com/frankie567/httpx-ws/pull/63
If that looks good for you, then I'll merge it, and we can close the current one.

So, I close this in favor of #63. Will make a release in a moment.
@all-contributors add @dmontagu for bug


Improve milestone title

Don't use h2 (which is also bad for a11y reasons) for the title, instead use font-size and font-weight to make the title look better.
Forgejo issue: https://codeberg.org/forgejo/forgejo/issues/348

Pulled from:
https://github.com/go-gitea/gitea/blob/affdd40296960a08a4223330ccbd1fb88c96ea1a/web_src/less/shared/issuelist.less#L30-L32
Before:

After:

Removing item headings prevents screen readers from navigating easily. Improving size should not go against semantics. DIV is one of the least meaningful elements in an HTML structure.
The H1 should wrap the Labels|Milestones button, as in Releases (which should have an H1 and not an H2).

I don't think they can really be defined as headers. Probably role listitem would be more appropriate

I don't think they can really be defined as headers. Probably role listitem would be more appropriate

That's for the <li> which has the listitem role by default. I mean the content inside each list item, which have a title and a content. It's not very well structured but it's a unit. For that kind of content, a screen reader sequentially goes through the list reading headings until the user hears which one he wants to select to inspect its full content.
Navigation is through landmarks and by levels, and the headings serve as elements of an index.

This is no different than the issue list. If there's a good a11y solution, it also should be applied to the lists (in another PR). The milestone one is currently standing out at the moment with its <h2> (for no good documented reason).

You can just use a h3 tag, then no need to add more CSS styles.
The pre-defined styles are good enough and more general.
Screenshot: the first one is h3, the second one is h2

You can just use a h3 tag (or even h4), then no need to add more CSS styles.

That's misusing the heading elements(which currently is already happening), they should follow in logical order. MDN confirms this. Best solution is to figure out which aria attributes must be set and also apply them to the issue/pull list.

You can just use a h3 tag (or even h4), then no need to add more CSS styles.

That's misusing the heading elements(which currently is already happening), they should follow in logical order. MDN confirms this. Best solution is to figure out which aria attributes must be set and also apply them to the issue/pull list.

Misused or not, they are useful right now and they are going to be removed. That's a degradation of the poor accessibility of this page, and for a solution that only improves the appearance.
If there is another lack of a11y (with a fix in progress) it doesn't mean that the criteria should bring everything towards that state, that would be levelling down.
Fixing the bad HTML structure with aria markup is the last solution to apply for accessibility, the first one (literaly) is to use the HTML elements made for it.

I also agree that it's not worth to follow the standard too strictly. I care more about making the code clearer and easier to be maintained, and be functional enough for various situations, like a11y.

Closing.

Thank you Gusted. Since this PR is closed, there is a new one #22863 , and the new one fixes one more milestone <h2> problem (on the user dashboard, the same problem)
According to the previous comments (https://github.com/go-gitea/gitea/pull/22853#issuecomment-1426269884 , https://github.com/go-gitea/gitea/pull/22853#issuecomment-1426789013 ), and confirmed with  fsologureng , nothing is changed, so the new PR still uses the <h?> tag to keep the current a11y behavior, to prevent from uncertain changes. The a11y related problems could be fixed together in the future by new PRs.

Fine with me, issue is fixed. I don't follow what to know what to follow.


solve issue #107 (TypeError: not iterable)

solve issue #107 (TypeError: argument of type 'NewsArticle' is not iterable)
https://github.com/fhamborg/news-please/issues/107
Traceback (most recent call last):
  File "/data/anaconda/envs/giga/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/data/anaconda/envs/giga/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/mnt/data/news-please/newsplease/examples/commoncrawl.py", line 169, in <module>
    main()
  File "/mnt/data/news-please/newsplease/examples/commoncrawl.py", line 165, in main
    continue_process=True)
  File "/mnt/data/news-please/newsplease/crawler/commoncrawl_crawler.py", line 297, in crawl_from_commoncrawl
    log_pathname_fully_extracted_warcs=__log_pathname_fully_extracted_warcs)
  File "/mnt/data/news-please/newsplease/crawler/commoncrawl_crawler.py", line 208, in __start_commoncrawl_extractor
    log_pathname_fully_extracted_warcs=__log_pathname_fully_extracted_warcs)
  File "/mnt/data/news-please/newsplease/crawler/commoncrawl_extractor.py", line 338, in extract_from_commoncrawl
    self.__run()
  File "/mnt/data/news-please/newsplease/crawler/commoncrawl_extractor.py", line 292, in __run
    self.__process_warc_gz_file(local_path_name)
  File "/mnt/data/news-please/newsplease/crawler/commoncrawl_extractor.py", line 237, in __process_warc_gz_file
    filter_pass, article = self.__filter_record(record)
  File "/mnt/data/news-please/newsplease/crawler/commoncrawl_extractor.py", line 121, in __filter_record
    publishing_date = self.__get_publishing_date(warc_record, article)
  File "/mnt/data/news-please/newsplease/crawler/commoncrawl_extractor.py", line 140, in __get_publishing_date
    if 'publish_date' in article:
TypeError: argument of type 'NewsArticle' is not iterable

Thanks for the PR! Added and updated in the latest NP version (news-please-1.4.22)


Confusion on and additional subtleties of v-bind.sync

This is a complex topic and I might be missing something, but....
I think the docs at https://vuejs.org/v2/guide/components-custom-events.html#sync-Modifier could use three updates:

There should be some mention that .sync can only be used when the expression is a proper lvalue/reference. For instance: :title.sync="title"

:title.sync="title + '!'" won't work. It will generate an error along the lines of:
SyntaxError: Left hand side of operator '=' must be a reference.
Fiddle: https://jsfiddle.net/davidkhess/vs1rxwLh/3/

When an object is used with v-bind, I think it would be worth mentioning that unlike normal bindings with .sync that update the referenced key on the Vue instance's data (i.e. 1. above), in this case it is only going to update that literal key on the object used in the v-bind.

At least, this is my understanding of things looking at the implementation:
https://github.com/vuejs/vue/commit/3965e5053a7d2f22e90f81d4a153d65c1c670897
Fiddle: https://jsfiddle.net/davidkhess/vs1rxwLh/33/

Re: this warning:

Using v-bind.sync with a literal object, such as in v-bind.sync=”{ title: doc.title }”, will not work. If you want to include multiple, unrelated data properties in the same v-bind.sync, we recommend creating a computed property that returns an object.

I think it would help to explain why a literal object doesn't work. I believe the reason is that a literal object is not going to be reactive since it isn't attached to a Vue instance's data and therefore the param on the child component will not be updated when the object's attribute is updated. The resolution is to make sure it is reactive and a computed property will do that.
However, I think the recommended solution of a computed property creates more confusion since based on 2. above, the $emit("update:...") is going to update an attribute of the object returned by the computed property which goes against the spirit of a computed property and is not easily accessible. I think it might be more useful to recommend attaching a params object to the parent's data so that the parent component can more easily watch an attribute of the params object for changes from the child component if needed.
EDIT: I'm not able to get the computed approach to work https://jsfiddle.net/davidkhess/vs1rxwLh/22/
I think it's because an object returned from a computed is not reactive.

Thanks for bringing up these concerns! 🙂

There should be some mention that .sync can only be used when the expression is a proper lvalue/reference. For instance: :title.sync="title". :title.sync="title + '!'" won't work.

Hm, I'm torn about this one, because we do explain how the syntax sugar is expanded. In this case, title.sync="title + '!'" expands to:
:title="title + '!'"
@update:title="title + '!' = $event"

And just as Vue warned you, title + '!' on the left-hand of an assignment doesn't make any sense.

When an object is used with v-bind, I think it would be worth mentioning that unlike normal bindings with .sync that update the referenced key on the Vue instance's data (i.e. 1. above), in this case it is only going to update that literal key on the object used in the v-bind.

Actually, in both cases we're updating a literal key on an object, because templates work under scope of the component instance. That means @update:title="title = $event" is really doing @update:title="this.title = $event", this being the component instance object.

Re: this warning: [...] I think it would help to explain why a literal object doesn't work.

I don't want to get too deep in the weeds here, but I added a little more detail about the difficulty of parsing complex expressions. 🙂

EDIT: I'm not able to get the computed approach to work: jsfiddle.net/davidkhess/vs1rxwLh/22

The returned object would have to define setters for the unrelated properties it wants to update, e.g. here. But tying this back to your earlier suggestion:

I think it might be more useful to recommend attaching a params object to the parent's data so that the parent component can more easily watch an attribute of the params object for changes from the child component if needed.

We already imply that recommendation before this comment - and as I consider it more, I've never actually encountered a use case for grouping truly unrelated properties like that, so I just removed that bit.
What do you think?

On 1., I think it could be a common mistake for less experienced developers to make since arbitrary expressions are otherwise supported in v-bind. It's only when .sync is added that an lvalue is required. The error message doesn't specifically mention a possible misuse of .sync – maybe adding a mention to the error message is another option?
On 2., true enough – however this is the only use of v-bind (as far as I know) where the reference updating isn't rooted on data of the Vue instance. I think it's easy to mistake (or forget) that behavior as some unbendable rule in all situations and expect the keys on the object to represent references to keys on data.
Ah, your solution for 3. is not what I was envisioning when I read that warning. I think enhancing the language to imply the need for setters and getters on each property would help.
Yes, rereading, I see that's really the same as the usage of doc in the example. What about updating this bit:

This passes each property in the doc object (e.g. title) as an individual prop, then adds v-on update listeners for each one.

to something like

This passes each property in the doc object (e.g. title) as an individual prop, then adds v-on update listeners for each one that update each of the respective properties on the doc object.

Bottom line, from my perspective, I've been working with Vue since about 0.6 and have used this particular feature multiple times (as it came and went in support) and still have always had a hard time wrapping my head around the implications of it until I read the source code that implements it. It's one of those concepts that I think can easily get wrapped up in "magic behavior".

So, what prompted this ticket was updating some code using this feature and not liking what we've discussed above.
After wrangling with this more, I came up with this strategy as the cleanest.

Do use v-bind="" but don't use .sync.
Do use a computed but return a simple object (no getters/setters).
Use a custom event to notify the parent that something has updated and it can set it directly on data. The parent is now updated and the computed will update for the child component.

Yeah, I agree that if some people are having a problem with it, there are definitely ways we could improve our explanation for it. 🙂
To give some more background, thinking about :title.sync="title" like a normal binding with extra behavior is really the wrong way to think about it, because two-way bindings are fundamentally different.  The .sync modifier works essentially like v-model, which is Vue's other syntax sugar for creating a two-way binding. The main difference is that it expands to slightly different pattern that allows you to have multiple two-way bindings on a single component, rather than being limited to just one.
Does that make sense?
Also, for the suggested rephrasing to:

This passes each property in the doc object (e.g. title) as an individual prop, then adds v-on update listeners for each one that update each of the respective properties on the doc object.

I think could use some clarification to better understand the intent of the change. When it just ended with "for each one", what was the misunderstanding we're trying to avoid? The subject of the sentence ("each property in the doc object") hasn't changed, but it sounds like you understood "for each one" as referring to something else?

On the first, I think that's a pretty good explanation to help people understand that v-bind down is very different from .sync coming up in terms of implementation of the two behaviors. But it's not intuitive that .sync fundamentally changes the behavior of the v-bind it is being used on. If so, then shouldn't it just be a differently named directive? Something like v-bind-sync?
Maybe just focusing on how the implementation of down is very different from up is sufficient.
On the rephrasing, the issue I kept struggling with was the straightforward (but wrong) assumption that v-bind with an object is just the same thing as combining multiple individual v-binds. With that mistaken assumption, it's easy to then assume there is syntactic sugar that makes the values on the objects somehow the lvalues for the .sync instead of the object and it's key.
In reality, it's actually a pretty different mechanism and that difference is easy to overlook until you try to start using and understanding .sync in combination with it.


Include Lordi :: Hard Rock Hallelujah

I hereby declare that:

[x] I preserved the structure of the playlist.org file!
[x] I preserved the alphabetical order!
[x] I used spaces instead of tabs for indentation!

If you can tick all of those requirements, this Pull Request is likely to get merged.
This pull request closes issue #21.

Please remove my merge and rebase.

Rebased twice since I f-ed up the first time. (thank git reflog) Should work by now and should be able to be merged.


Add a non-blocking reallocate function

Something I need in an application for HydroNet use case. There are points where I determine I want to adjust the allocation between tasks and don't need to wait for that to happen.

Merging as I've used this in an application w/o problems


rerun e5 and cohere  with custom embeddings

Seems like we were a bit too hasty with merged #92. We still have to update the scores (at least to see if everything works correctly)

I don't think it was too hasty, I know for a fact that it works correctly, I did some tests locally with some debugging statements and in asymmetric tasks the correct functions are getting called. I agree that we should update the results though.

We still have to rerun the models though

#127 reran coheres (and it seems to indeed improve as expected)

Added a while back


Add [Notify] for partial auto-properties.

This (in theory) allows you to use .NET 9's partial auto-properties to generate default behavior.
A declaration like so:
public partial class MyNode : Node
{
    // Minimal example
    [Notify]
    public partial float Value1 { get; set; }

    // Complex example:
    // - Additional modifiers are preserved (like "virtual").
    // - Access modifiers of get/set are preserved ("protected get;").
    // - Omitted implementations are likewise omitted in the output (no "set").
    [Notify]
    public partial virtual float Value2 { protected get; }
}

Should generate this:
// Minimal example
#if NET9_0_OR_GREATER
    public partial float Value1
    {
        get => _value1.Get();
        set => _value1.Set(value);
    }
#endif

// Complex example
#if NET9_0_OR_GREATER
    public partial virtual float Value2
    {
        protected get => _value2.Get();
    }
#endif

Unfortunately, it's not clear to me how I'm supposed to actually test the implementation nor how I might write, build, & execute a formal test class/scene to verify the behavior. Was hoping you could provide guidance on that or review/verify the implementation yourself.

Very good.  Thanks for that - I'll merge it in and add some tests.

All done.  New pre-release uploaded :)


Feature: Disabling Commands Server-wide

Have the ability to enable and disable certain commands server-wide.
Current thoughts:

Command Name: command (aliases: cmd)
Arguments: <command name> [enable | on | disable | off] (if given the command name it will let the user know if it's enabled or disabled (does not require claim))
When enabling or disabling commands (i.e., not !cmd <command name>) the manage_commands claim is required.
Only applies to a command or a group of commands. You cannot disable a sub-command, i.e., !tag add.
Possible idea: have another claim to bypass disabled commands? Probably named bypass_disabled_commands?
Command Service

Might have to rename from CommandMetricsService just to CommandService if we don't want to add another service.
On each command run, the bot will request from the API whether or not that command is disabled. If so, the user will be notified that it's been disabled server-wide.

Additions to Commands Route

[GET] bot/commands/{GuildId}/{CommandName} - Will check against a List<string> from the API and will return a boolean, true if enabled, false if disabled.

First of all, excellent work. some thoughts
1. we still need data model design
2. we should consider adding an option to either fail silently or report that the cmmand is disabled
3. This will require additions to the docs site
4. we will need a put end and delete endpoint to add and delete mappings

overall youve covered most of the bases


The directory names in the database navigation are not displayed completely

Description
This is when the directory name is incomplete:

The directory name looks like this when fully displayed:

DBeaver Version
<IP_ADDRESS>403241413
Operating System
macOS Monterey 12.7.2
Database and driver
No response
Steps to reproduce
No response
Additional context
No response

Thank you for bug report.
I can't reproduce it on windows 10, maybe it's a mac-specific issue

Looks like double https://github.com/dbeaver/dbeaver/issues/22412
It probably should be fixed after updating of Exlipse


Cannot specify more than one scope in New-PartnerAccessToken cmdlet despite it having "scopes"

Steps to reproduce
[String[]]$ScopesTest = 'https://api.partnercenter.microsoft.com/user_impersonation'
[String[]]$ScopesTest += 'https://management.azure.com/user_impersonation'

PS C:\Windows\system32> $ScopesTest
https://api.partnercenter.microsoft.com/user_impersonation
https://management.azure.com/user_impersonation

PS C:\Windows\system32> $RefreshTokenForTestingAuthSPNFull = New-PartnerAccessToken -ApplicationId 'xxxxx-xxxx-xxxx-xxxx-xxxx' -Scopes $ScopesTest -ServicePrincipal -Credential $Credentials -Tenant "xxx-xxx-xxx-xxx-xxxxx" -UseAuthorizationCode
WARNING: Attempting to launch a browser for authorization code login.
WARNING: We have launched a browser for you to login. For the old experience with device code flow, please run 'New-PartnerAccessToken -UseDeviceAuthentication'.
New-PartnerAccessToken : AADSTS28000: Provided value for the input parameter scope is not valid because it contains more than one resource. Scope
https://api.partnercenter.microsoft.com/user_impersonation https://management.azure.com/user_impersonation offline_access openid profile is not valid.
Trace ID: 55a1357c-a6dd-4337-9b9f-473cbbe74200
Correlation ID: def32739-9e85-48fb-a4e2-8248d697d91f
Timestamp: 2019-09-26 11:08:05Z
At line:1 char:38
+ ... thSPNFull = New-PartnerAccessToken -ApplicationId 'xxx-xxx-xxx...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [New-PartnerAccessToken], MsalServiceException
    + FullyQualifiedErrorId : Microsoft.Identity.Client.MsalServiceException,Microsoft.Store.PartnerCenter.PowerShell.Commands.NewPartnerAccessToken

Expected behavior
Should add scopes to the authorisation but instead the code parses all the strings into the cmd.
GET /xxxx-xxx-xxxx-xxxx-xxxxx/oauth2/v2.0/authorize?scope=https:%2F%2Fapi.partnercenter.microsoft.com%2Fuser_impersonation+https:%2F%2Fmanagement.azure.com%2Fuser_impersonation+offline_access+openid+profile&response_type=code&client_id=xxxx-xxxx-xxxx-xxxx-xxxxxxx&redirect_uri=http:%2F%2Flocalhost:8400%2F&client-request-id=558d721e-afa2-4082-a5ac-8b3d8fb74033&x-client-SKU=MSAL.CoreCLR&x-client-Ver=<IP_ADDRESS>&prompt=select_account HTTP/1.1

Version:
PS C:\Windows\system32> Get-Module -Name PartnerCenter

ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Script     2.0.1909.5 PartnerCenter                       {Add-PartnerCustomerCartLineItem, Add-PartnerCustomerUserRoleMember, Connect-PartnerCenter, Disconnect-Part...

[String[]]$ScopesTest = "https://graph.windows.net/Directory.Read"
[String[]]$ScopesTest += "https://graph.windows.net/Directory.Write"

PS C:\Users\Administrator> $RefreshTokenForTestingAuthSPNFull = New-PartnerAccessToken -ApplicationId 'xxx-xxx-xxx-xxx-xxxxxx' -Scopes $ScopesTest -ServicePrincipal -Credential $Credentials -Tenant "xxx-xxx-xxx-xxx-xxxxxx" -UseAuthorizationCode
WARNING: Attempting to launch a browser for authorization code login.
WARNING: We have launched a browser for you to login. For the old experience with device code flow, please run 'New-PartnerAccessToken -UseDeviceAuthentication'.
New-PartnerAccessToken : AuthorizationCode can not be null or whitespace
Parameter name: AuthorizationCode
At line:1 char:38
+ ... thSPNFull = New-PartnerAccessToken -ApplicationId 'xxxx-xxxx-xxx...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [New-PartnerAccessToken], ArgumentException
    + FullyQualifiedErrorId : System.ArgumentException,Microsoft.Store.PartnerCenter.PowerShell.Commands.NewPartnerAccessToken

This should be a better example because it should work as per:
https://docs.microsoft.com/en-us/azure/active-directory/develop/msal-net-migration#scopes-for-a-web-api-accepting-v10-tokens

The return we got from the API is:
GET http://localhost:8400/?error=invalid_client&error_description=AADSTS650053%3a+The+application+%27Partner+Center+Web+App%27+asked+for+scope+%27Directory.Read%27+that+doesn%27t+exist+on+the+resource+%2700000003-0000-0000-c000-000000000000%27.+Contact+the+app+vendor.%0d%0aTrace+ID%3a+39311888-5dce-4c7f-9059-9f35cf116400%0d%0aCorrelation+ID%3a+xxx-xxx-xxx-xxx-xxxx%0d%0aTimestamp%3a+2019-09-27+14%3a51%3a23Z HTTP/1.1
Accept: text/html, application/xhtml+xml, image/jxr, */*
Referer: https://login.microsoftonline.com/
Accept-Language: en-GB,en;q=0.5
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; Touch; rv:11.0) like Gecko
Accept-Encoding: gzip, deflate
Cache-Control: no-cache
Host: localhost:8400
Connection: Keep-Alive
Pragma: no-cache

@cblackuk with the last example you shared were you using an Azure Active Directory that had the Azure Active Directory Graph permissions assigned correct?

No, it was more to show that it shows 200 in the "GUI"/Website but the error is just inside the GET - it obviously all failed. Unless you are asking if my SPN has got correct permissions - in which case - yes it does but you still cannot do anything from the cmdlet as shown above.

@cblackuk my apologizes for not updating this sooner. This particular issue was addressed with the 2.0.1911.1 release. If you are curious you can see what was done here. Please let us know if you have any other issues.

Thanks @isaiahwilliams! I will test it soon :-)

the cmdlet for token still does not accepts more than one scope.
New-PartnerAccessToken : AADSTS28000: Provided value for the input parameter scope is not valid because it contains more than one resource. Scope https://api.partnercenter.microsoft.com/user_impersonation ht
tps://management.azure.com/user_impersonation offline_access openid profile is not valid.

Sad ;-(

Why is this issue closed? I'm also experiencing the same problem. Unable to use more than 1 scope. Using version 3.0.10

Why is this issue closed? I'm also experiencing the same problem. Unable to use more than 1 scope. Using version 3.0.10


petab_select.Model.to_petab not working

Wanting to try out the package, i've ran into a snag, potentially a wrong petab version. The error message is:
  petab_select/petab_select/model.py in to_petab(self, output_path)
      330         if output_path is not None:
      331             petab_yaml_path = \
  --> 332                 petab_problem.to_files_generic(prefix_path=output_path)
      333
      334         return (petab_problem, petab_yaml_path)

maybe it should be to_files rather than to_files_generic.

Hi Frank, thanks for reporting! Sorry, should be fixed in the latest release of libpetab-python (v0.1.20).


Run ondemand-storm-workflow for 27 storms with 6 different lead times

Setup and run workflow for storms and lead times as listed in https://github.com/saeed-moghimi-noaa/Next-generation-psurge-tasks/issues/14
Run directories structure on NHC_COLAB_2: /nhc/hurricanes/<storm>_<track>_<lead_time>hr_<sampling_method>_<no_of_perturbations>
where:

storm (Ref.): {Gustav_2008, Ike_2008, IreneNC_2011, IreneNJ_2011, Isaac_2012, Sandy_2012, Hermine_2016, MatthewSC_2016, MatthewFL_2016, Harvey_2017, IrmaFL_2017, Nate_2017, Florence_2018, Gordon_2018, Michael_2018, Barry_2019, Dorian_2019, Beta_2020, Cristobal_2020, Delta_2020, Eta_2020, Hanna_2020, Isaias_2020, Laura_2020, Marco_2020, Sally_2020, Zeta_2020}
track: OFCL
lead_time: [12, 24, 36, 48, 60, 72]
sampling_method: korobov
no_of_perturbations: 30

Example run directory: /nhc/hurricanes/florence_2018_OFCL_48hr_korobov_30/

Thank you for the update @FariborzDaneshvar-NOAA. Please let me know if I can assist you in any way.

As we discussed during the biweekly P-Surge meeting on Thursday, December 14th, first we will run and analyze one storm (Florence) to ensure workflow is working as expected, before running the remaining 24 storms (listed above).

For the post-processing each leadtime of a storm:

Run the following command (on a compute node) to combine results
combine_results --schism --adcirc-like-output ./analyze
Follow the steps provided here to use dask and a big memory, then run analyze_ensemble.py
Path to a notebook used to analyze ensemble on NHC_COLAB_2 cluster: /home/Fariborz.Daneshvar/notebooks/analyze_ensemble_dask.ipynb

Ensemble runs for hurricane Sandy 2012 completed on Hercules . See more updates here: https://github.com/saeed-moghimi-noaa/Next-generation-psurge-tasks/issues/25
I will then be running Harvey 2017 and Michael 2018 and conduct analyzes of the surrogate models before NHC meeting on Feb. 8.
Run directories for 6 leadtimes (12, 24, 36, 48, 60, and 72) on Hercules are:

/work2/noaa/nos-surge/shared/nhc_hurricanes/sandy_2012_OFCL_{leadtime}hr_korobov_30/
/work2/noaa/nos-surge/shared/nhc_hurricanes/harvey_2017_OFCL_{leadtime}hr_korobov_30/
/work2/noaa/nos-surge/shared/nhc_hurricanes/michael_2018_OFCL_{leadtime}hr_korobov_30/

Runtime summaries for hurricane Sandy on Hercules:

Mesh generation ~ 25 min
SCHISM run for 72hr leadtime with pschism_HERCULES_PAHM_TVD-VL binary on 1 node: ~01:53:00
SCHISM run for 72hr leadtime with pschism_HERCULES_PAHM_BLD_STANDALONE_TVD-VL binary on 10 nodes : ~01:48:00
SCHISM run for 72hr leadtime with pschism_HERCULES_PAHM_BLD_STANDALONE_TVD-VL binary on 10 nodes & 80 tasks per node): ~00:36:00
Post-process (combine results, subset, KL-PC phase, surrogate expansion, sensitivity, but no plots): ~03:20:00 !!

Number of days simulated for each leadtime: 12hr: 6.25 ; 24hr: 6.5 ; 36hr: 7.0 ; 48hr: 7.5 ; 72hr: 7.75

Finished Sandy runs for 12,24,36,48, and 72 hr leadtimes. The meshing step of 60hr leadtime failed with PermissionError! (maybe due to an issue with the domain) @SorooshMani-NOAA is looking into it.
This is the error I got:
2024-02-09:18:04:53,827 INFO     [hurricane_mesh.py:79] The mesh command is subset_n_combine.
Traceback (most recent call last):
   File "/opt/conda/envs/ocsmesh/lib/python3.10/runpy.py", line 196, in _run_module_as_main
      return _run_code(code, main_globals, None,
   File "/opt/conda/envs/ocsmesh/lib/python3.10/runpy.py", line 86, in _run_code
      exec(code, run_globals)
   File "/scripts/hurricane_mesh.py", line 548, in <module>
      main(args, [hurrmesh_client, subset_client])
   File "/scripts/hurricane_mesh.py", line 97, in main
      clients_dict[cmd].run(args)
   File "/opt/conda/envs/ocsmesh/lib/python3.10/site-packages/ocsmesh/cli/subset_n_combine.py", line 113, in run
      self._main(
   File "/opt/conda/envs/ocsmesh/lib/python3.10/site-packages/ocsmesh/cli/subset_n_combine.py", line 573, in _main
      poly_clipper = self._calculate_clipping_polygon(
   File "/opt/conda/envs/ocsmesh/lib/python3.10/site-packages/ocsmesh/cli/subset_n_combine.py", line 162, in _calculate_clipping_polygon
      geom_cutoff = Geom(
   File "/opt/conda/envs/ocsmesh/lib/python3.10/site-packages/ocsmesh/geom/geom.py", line 74, in __new__
      return GeomCollector(geom, **kwargs)
   File "/opt/conda/envs/ocsmesh/lib/python3.10/site-packages/ocsmesh/geom/collector.py", line 197, in __init__
      in_item.clip(clip_shape)
   File "/opt/conda/envs/ocsmesh/lib/python3.10/site-packages/ocsmesh/raster.py", line 1217, in clip
      with self.modifying_raster(**meta_update) as dest:
   File "/opt/conda/envs/ocsmesh/lib/python3.10/contextlib.py", line 135, in __enter__
      return next(self.gen)
   File "/opt/conda/envs/ocsmesh/lib/python3.10/site-packages/ocsmesh/raster.py", line 385, in modifying_raster
      tmpfile = tempfile.NamedTemporaryFile(prefix=tmpdir)
   File "/opt/conda/envs/ocsmesh/lib/python3.10/tempfile.py", line 559, in NamedTemporaryFile
      file = _io.open(dir, mode, buffering=buffering,
   File "/opt/conda/envs/ocsmesh/lib/python3.10/tempfile.py", line 556, in opener
      fd, name = _mkstemp_inner(dir, prefix, suffix, flags, output_type)
   File "/opt/conda/envs/ocsmesh/lib/python3.10/tempfile.py", line 256, in _mkstemp_inner
      fd = _os.open(file, flags, 0o600)
PermissionError: [Errno 13] Permission denied: '/tmp/ocsmesh/gpon_sdn'
ERROR conda.cli.main_run:execute(49): `conda run python -m hurricane_mesh sandy 2012 subset_n_combine /work2/noaa/nos-surge/smani/data/grid/stofs3d_atl_v2.1_eval.gr3 /work2/noaa/nos-surge/smani/data/grid/WNAT_1km.14 /work2/noaa/nos-surge/shared/nhc_hurricanes/sandy_2012_ba17b72f-7589-494e-9ce3-103419600198/windswath --rasters /work2/noaa/nos-surge/smani/data/dem/GEBCO/gebco_2020_n0.0_s-90.0_w-180.0_e-90.0.tif /work2/noaa/nos-surge/smani/data/dem/GEBCO/gebco_2020_n0.0_s-90.0_w-90.0_e0.0.tif /work2/noaa/nos-surge/smani/data/dem/GEBCO/gebco_2020_n0.0_s-90.0_w0.0_e90.0.tif /work2/noaa/nos-surge/smani/data/dem/GEBCO/gebco_2020_n0.0_s-90.0_w90.0_e180.0.tif /work2/noaa/nos-surge/smani/data/dem/GEBCO/gebco_2020_n90.0_s0.0_w-180.0_e-90.0.tif /work2/noaa/nos-surge/smani/data/dem/GEBCO/gebco_2020_n90.0_s0.0_w-90.0_e0.0.tif /work2/noaa/nos-surge/smani/data/dem/GEBCO/gebco_2020_n90.0_s0.0_w0.0_e90.0.tif /work2/noaa/nos-surge/smani/data/dem/GEBCO/gebco_2020_n90.0_s0.0_w90.0_e180.0.tif --out /work2/noaa/nos-surge/shared/nhc_hurricanes/sandy_2012_ba17b72f-7589-494e-9ce3-103419600198/mesh` failed. (See above for error)

There was an issue with the leadtime jason file, so I had to re-run workflow with the updated file in input.conf:

L_LEADTIMES_DATASET=$DATA/leadtimes.json --> L_LEADTIMES_DATASET=$DATA/lead.json

All 6 runs with updated leadtimes of Sandy have been completed. Here are start time of new simulations (which start two days before given leadtime by NHC):

leadtime
simulation start date/time

12-hr
2012-10-27 12:00:00

24-hr
2012-10-27 06:00:00

36-hr
2012-10-26 18:00:00

48-hr
2012-10-26 06:00:00

60-hr
2012-10-25 18:00:00

72-hr
2012-10-25 06:00:00

Sandy leadtimes from NHC jason file:
These are leadtimes from the file:
"2012103000": 0,
"2012102912": 12,
"2012102906": 24,
"2012102818": 36,
"2012102806": 48,
"2012102718": 60,
"2012102706": 72

@SorooshMani-NOAA I noticed that the first two leadtimes (12, and 24) are 6 hours apart! shouldn't it be 12 hours? Other leadtimes are 12 hours apart! Should we tag Laura or Andy on this issue (or post it on the other board)?

The post processing steps for Sandy did not complete. This issue will be investigated here: https://github.com/oceanmodeling/ondemand-storm-workflow/issues/43

@SorooshMani-NOAA with the new node/task setup (mentioned here), Michael runs are finishing in less than 15 min! Thanks :)

Ensemble runs for hurricane Sandy 2012 completed on Hercules . See more updates here: saeed-moghimi-noaa/Next-generation-psurge-tasks#25
I will then be running Harvey 2017 and Michael 2018 and conduct analyzes of the surrogate models before NHC meeting on Feb. 8.
Run directories for 6 leadtimes (12, 24, 36, 48, 60, and 72) on Hercules are:

/work2/noaa/nos-surge/shared/nhc_hurricanes/sandy_2012_OFCL_{leadtime}hr_korobov_30/
/work2/noaa/nos-surge/shared/nhc_hurricanes/harvey_2017_OFCL_{leadtime}hr_korobov_30/
/work2/noaa/nos-surge/shared/nhc_hurricanes/michael_2018_OFCL_{leadtime}hr_korobov_30/

Just finished re-running all these storms with updated leadtimes, binaries, and new configurations (10 nodes & 80 tasks per node)

Completed runs for Dorian, 2019, Delta, 2020, and Laura, 2020!
Post-processing step did not complete for high leadtimes of Dorian (48hr, 60hr. and 72hr). Investigating it here https://github.com/oceanmodeling/ondemand-storm-workflow/issues/43

There was an issue with the storm track of Marco 2020, @SorooshMani-NOAA is working on it https://github.com/noaa-ocs-modeling/EnsemblePerturbation/issues/137 Thanks!

Post-processing step for some leadtimes of Irene, Isaac, Matthew, Irma, and Isaias did not complete, so I need to run them with dask separately.

Random SCHISM runs for ike_2008 with 24 hr leadtime failed! I posted the issue here: https://github.com/oceanmodeling/ondemand-storm-workflow/issues/45

@SorooshMani-NOAA thanks for fixing Marco issue (no COOPS station in the domain). With that, I was able to run the workflow for 12-, 24-, 36-, and 48-hr leadtimes of Marco.
As we discussed before, 60-, and 72-hr leadtimes failed with this error:
2024-03-07:01:41:17,347 INFO     [hurricane_data.py:107] Creating OFCL track for 60 hours before landfall forecast...
Traceback (most recent call last):
  File "/opt/conda/envs/info/lib/python3.9/runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/opt/conda/envs/info/lib/python3.9/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/scripts/hurricane_data.py", line 327, in <module>
    main(args)
  File "/scripts/hurricane_data.py", line 127, in main
    forecast_start = candidates[
  File "/opt/conda/envs/info/lib/python3.9/site-packages/pandas/core/indexing.py", line 1191, in __getitem__
    return self._getitem_axis(maybe_callable, axis=axis)
  File "/opt/conda/envs/info/lib/python3.9/site-packages/pandas/core/indexing.py", line 1752, in _getitem_axis
    self._validate_integer(key, axis)
  File "/opt/conda/envs/info/lib/python3.9/site-packages/pandas/core/indexing.py", line 1685, in _validate_integer
    raise IndexError("single positional indexer is out-of-bounds")
IndexError: single positional indexer is out-of-bounds
ERROR conda.cli.main_run:execute(124): `conda run python -m hurricane_data
--date-range-outpath /work2/noaa/nos-surge/shared/nhc_hurricanes/marco_2020_f94800f8-e299-4bd4-bd41-d92fe82f5e54/setup/dates.csv
--track-outpath /work2/noaa/nos-surge/shared/nhc_hurricanes/marco_2020_f94800f8-e299-4bd4-bd41-d92fe82f5e54/nhc_track/hurricane-track.dat
--swath-outpath /work2/noaa/nos-surge/shared/nhc_hurricanes/marco_2020_f94800f8-e299-4bd4-bd41-d92fe82f5e54/windswath
--station-data-outpath /work2/noaa/nos-surge/shared/nhc_hurricanes/marco_2020_f94800f8-e299-4bd4-bd41-d92fe82f5e54/coops_ssh/stations.nc
--station-location-outpath /work2/noaa/nos-surge/shared/nhc_hurricanes/marco_2020_f94800f8-e299-4bd4-bd41-d92fe82f5e54/setup/stations.csv
--past-forecast
--hours-before-landfall 60
--lead-times /work2/noaa/nos-surge/smani/data/lead.json marco 2020` failed. (See above for error)

Re-ran Eta 2020 after the new fix in stormevents.

Random SCHISM runs for ike_2008 with 24 hr leadtime failed! I posted the issue here: oceanmodeling/ondemand-storm-workflow#45

Successfully ran ike_2008 with 24-hr leadtime (with updated schism.sbatch from Soroosh directory)

The only remaining runs are 60- and 72-hr leadtimes of Marco.

Results will be reviewed here: https://github.com/saeed-moghimi-noaa/Next-generation-psurge-tasks/issues/33


[Tests] Test Theme model

I noticed that there aren't any tests for Theme model. I'd like to add some. Can I work on this?

@rgenchev That would be great, thank you!

I noticed that there isn't any logic in the model. I think that this one can be closed.


BUG: Initialize itk::ExhaustiveOptimizer::m_MinimumMetricValue

Provide an initial value to the
itk::ExhaustiveOptimizer::m_MinimumMetricValue ivar.
Fixes:
UMC ==18288== Conditional jump or move depends on uninitialised value(s)
==18288==    at 0x663E1F8:
__printf_fp_l (printf_fp.c:387)
==18288==    by 0x6659639:
__vfprintf_internal (vfprintf-internal.c:1687)
==18288==    by 0x666E119:
__vsnprintf_internal (vsnprintf.c:114)
==18288==    by 0x64D4C3F:
??? (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.28)
==18288==    by 0x6506245:
std::ostreambuf_iterator > std::num_put > >::
_M_insert_float(std::ostreambuf_iterator >, std::ios_base&, char, char, double) const
(in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.28)
==18288==    by 0x6514972:
std::ostream& std::ostream::_M_insert(double) (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.28)
==18288==    by 0x489F46D:
itk::ExhaustiveOptimizer::PrintSelf(std::ostream&, itk::Indent) const (itkExhaustiveOptimizer.cxx:229)
==18288==    by 0x53B4B19:
itk::LightObject::Print(std::ostream&, itk::Indent) const (itkLightObject.cxx:125)
==18288==    by 0x16536A:
itkExhaustiveOptimizerTest(int, char**) (itkExhaustiveOptimizerTest.cxx:158)
==18288==    by 0x12F2E7:
main (ITKOptimizersTestDriver.cxx:222)

Uncovered by the dynamic analysis in:
https://open.cdash.org/viewDynamicAnalysisFile.php?id=9074678
PR Checklist

[X] No API changes were made (or the changes have been approved)
[X] No major design changes were made (or the changes have been approved)

Related to PR #3102.


show conan remote packages, set package editable

Load and view implementation of Conan packages for selected items in Conan Remote. “vsconan.explorer.treeview.remote.item.selected” is not implemented. You can load all available packages from the repo using the command “conan search “*” -r=conancenter” or other repos.

Implementation of the change package in editable. It would be good if you could change the package to editable.
'Conan editable, add "path" "package name""
Path and package name sould be inserted.

Hi @imanSaberi
thanks for using my extension and providing this feedback.
Are you using the extension for conan2 or conan1? As the latest release, I have to admit there are some missing features for conan2.
The topic number 1. -> If i am not mistaken, it should be implementeed already.
The topic number 2. -> needs to be implemented for conan2
Sorry for the late reply, I was in vacation and then so much work, but i will always try to find time to continue  this extension :) I hope you are still willing to use the extension and it can help you with your work! Your feedback is really appreciated :)
PS: Pull request can be also considered :)

Hi @imanSaberi,
I splitted this issue into two different issues #41 and #42.
Therefore I will close this issue. To track the issues please follow the referenced issues I created.


Patch method in the properties change is not allowed

The properties change method in the proerties sections contain a POST method.
I'm submitting a ...  (check one with "x")
[X] bug report => search github for a similar issue or PR before submitting
[ ] feature request

Current behavior

The actions can't be perform because obtin a 404 error.
Expected behavior

The method implemented in the console should be a Patch method, to consume the patch method defined in earlgrey.

It's done


Missing square in RBF kernel gradient

The following code snippet from the adversarial robustness toolbox computes the gradient of an RBF kernel:
grad = (
    2
    * self.model._gamma
    * (-1)
    * np.exp(-self.model._gamma * np.linalg.norm(x_sample - sv, ord=2))
    * (x_sample - sv)
)

According to the scikit-learn docs, the RBF kernel is defined as \exp(-\gamma \|x-x'\|^2). Using the same definition for the RBF kernel, Section 4.2.1 in this paper by Biggio et al., which is also referenced in the code, describes the corresponding gradient as -2\gamma \exp(-\gamma \| x - x' \|^2) (x - x').
Shouldn't the norm in the code be squared?

Hi @btlorch Thank you very much for raising this issue! I think you are right, the derivation of the exponential function term should not change it and therefore square of x - x' is missing in the code.
Did you try out how much it changes the behavior of attacks?
Would you be interested to open a pull request to fix it?

Thanks for the swift response, I'll be happy to open a pull request.
Here is a comparison on the binary classification toy example with projected gradient descent from classifier_scikitlearn_SVC_LinearSVC.ipynb.
Projected gradient descent, current implementation, missing square in RBF kernel gradient

Projected gradient descent, after fixing the square

It looks like the current implementation leads to the more desirable behavior, i.e., adversarial examples are moving towards the decision boundary. After fixing the missing square, some adversarial examples move in the direction of quickest descent. Nevertheless, this is the behavior reported in the paper (see Fig. 4). In the paper, the authors propose to introduce an additional loss term that penalizes moving into low density regions. I suppose this additional loss term could be integrated into a future version of the ART.
Despite this observation, it looks like the Carlini & Wagner L2 attack is still successful in finding adversarial examples.
C&W L2 attack, current implementation, missing square in RBF kernel gradient

C&W L2 attack, after fixing the square

Hi @btlorch This is very nice and interesting! Thank you very much sharing your insights and opening a pull request! I think the additional loss term against low density regions would indeed be a nice addition to future versions of ART.

Thanks for merging the pull request, I am closing this issue.


Impossible to create sms and tel links

When creating links to telephone numbers http is always appended in the front of links.

You can pass processURL function as a prop which will receive whatever user has entered and you can modify it however you want and then return that string which will be set as the final url


Remove redundant UTF_8 params

Separated from #6986.

And if we can reuse this
contentType?.charset(UTF_8) ?: UTF_8

as defaultCharset() in MediaType?

Why do you think these parameters are redundant?

As they use UTF_8 as default parameters.
public inline fun String.toByteArray(charset: Charset = Charsets.UTF_8): ByteArray = (this as java.lang.String).getBytes(charset)

OMG you're right! I know Java’s String.getBytes() defaults to the platform charset, and didn't realize Kotlin broke with that here. I apologize for my tone; I thought this PR introduced a behavior change and was frustrated by a PR that caries tiny benefits (slightly less code) yet introduces an invisible behavior change.
i don't particularly like these ‘cleanup’ PRs in general because of this asymmetry. Also because it's exhausting to spend my time reviewing changes that don’t solve user’s problems.
Going forward, could you please limit PRs to problems that manifest as a user-visible bug?

Ugh, I merged before seeing you added a commit, MediaType?.charset(). I dislike extensions on nullable types because I find them surprising. I'd like to revert that commit.

ok


Some controls do not respond to inputs when inside of a stretched Viewbox.

They work fine if Stretch=None or if they are pressed in a location they would be at if there was no stretching.

The gif shows that the textboxes do work. I also had DropDowns inside of the Viewbox that worked (but see #2631)

It probably has something to do with this check

This bug also occurs with Checkboxes. I think it is safe to say most controls will need to have their logic take into account this situation, since it was probably overlooked when creating them.

Some time between 0.8.1.cibuild0002893-beta and 0.8.1-cibuild0003053-beta this got fixed. I'm not sure exactly when, but I will close this

I think it was probably #2539 that fixed it.


3.11.3 breaks CommonJS require

We use this in an older component that still uses syntax var ReactTooltip = require("react-tooltip"); 3.11.3 broke this component for all of our library users.
Looks like the module.exports was changed to export default though the comment above says "/* export default not fit for standalone, it will exports {default:...} */"
https://github.com/wwayne/react-tooltip/commit/08289a8de72598f0c1e5ef8c972ea67e85dc178a#diff-1fdf421c05c1140f6d71444ea2b27638R615
And the .babelrc explicitly says "modules:false". Was there a reason for this change? @Rogger794
https://github.com/wwayne/react-tooltip/commit/08289a8de72598f0c1e5ef8c972ea67e85dc178a#diff-e56633f72ecc521128b3db6586074d2cR7

In my opinion this change should not have been made in a patch version.

Hi @tylerthegrove, the change was thought to replace the standalone with the new version using rollup by using export default for name your variable reference as you want.

@Rogger794 A breaking change like that should probably wait for a major version, but never be part of a patch version.
We automatically pull patch versions with the expectation that they only contain bug fixes and are backwards compatible. This broke for all projects using our shared library. I'd suggest adding {modules: true} to the .babelrc and waiting for 4.0.0 for a breaking change.

@tylerthegrove, would you make a PR with the changes that fit your issue? Later I will upgrade the release to 4.0.0 with the original new configuration. Seems that after the merge for the rollup build, versioning automatically upgrade as a patch version for the semantic release package.

@tylerthegrove maybe this link can help you .

Thanks @gersongams but I know what the issue is. My point is just that there shouldn't be breaking changes like this in patch versions.
Likely we will move away from this package to prevent breaks in the future.


⚠ Bofrost.at has degraded performance

In 7bcd273, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1537 ms

Resolved: Bofrost.at performance has improved in 635ba7f.


Expose the Falco Engine version through the gRPC Version API

Motivation
Rules depend on the Falco Engine version (and the fields a specific version supports) in order to work.
It can be useful to know this version value (and also the fields and rules a version supports) in order to create external tooling (eg., test harness) aware of such knowledge and behaving accordingly.
Feature
Expose the Falco Engine version through the existing gRPC Version API.
Alternatives
Read the Falco Engine version from built files or from source files. Not ideal because it implies a dependency of artifacts on them, imho.

The need for this emerged while reviewing this.

/help

@leogr:
This request has been marked as needing help from a contributor.
Please ensure the request meets the requirements listed here.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

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

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

/assign nibalizer


Add OOBI methods

TODO: OOBI Challange

There is already a ticket for that here: https://github.com/WebOfTrust/signify-ts/issues/15


👩🔬 [Investment Day] Add Smart Invert Support

📲 What
Adds Smart Invert support
🤔 Why
Smart invert allows inverting the "chrome" of our app while keeping images untouched. This is only supported on iOS 11 so it's behind availability check.
🛠 How
"Simply" applied style to all UIImageViews that qualify as displaying user generated content.
👀 See

Before
Smart Invert ⚫
Normal ⚪

♿ Accessibility
To toggle Smart Invert on or off you can go to Settings > General > Accessibility > Display Accommodations > Invert Colors > Smart Invert or enable Accessibility Shortcut in Settings > General > Accessibility > Accessibility Shortcut (all the way in the bottom) > Smart Invert

[ ] All user generated content preserves its colors while Smart Invert is enabled

✅ Acceptance criteria

[x] All snapshot tests pass (ensures previous behaviour stays untouched)

I've included Smart Invert support for CircleAvatarImageView and tried to play with inverting the tab bar item but without luck. I'd suggest we defer it to some future work for now.

Forgot about appearance proxy 😅
This seems to fix the profile avatar:
UIImageView.appearance(whenContainedInInstancesOf: [UITabBar.self]).accessibilityIgnoresInvertColors = true

And placing this line in one place might be all we need:
UIImageView.appearance().accessibilityIgnoresInvertColors = true

But as you mentioned IRL there might be image views where we do want to invert.


Exception is thrown when object with no setters is mapped to.

I have an object that is populated via the constructor, so the properties have no setters (not even private ones).  Mapping to this object causes a failure.  The workaround is to add private setters, but would be nice if it's not necessary to have these as it clutters the objects.

This is because I treat immutable object as primitives. It cannot be destination. My scenario is when I use Url and DbGeography as properties in v1. I will got error on transformation.
But how you expect Mapster to work? Mapster doesn't support map to constructor yet. At this time, you could use MapWith to map manually, and then model can have no setter.

In this case, I'm constructing using ConstructUsing(src => new dest(src.x, src.y, src.z...)) to set up the constructor.  MapWith would just be a replacement...sounds good.

Another idea to solve if you have a lot of record types to map. You can create new adapter inherit from BaseAdapter. I haven't put this into document as it is a bit advance.
The class will need to override Priority method to determine which type pair will map with the adapter. If it cannot map, it should return null, otherwise return priority.
You can also override CanInline method to always return true, because map to record type can use only one line.
After that you can override CreateInlineExpression, and put logic to create your mapping there.
After you finish, you can register by TypeAdapterConfig.GlobalSettings.Rules.Add(new YourAdapter().CreateRule()).
After that Mapster should be able to map record type. This could be starting point to support #28 and it also be starting point to support third party add-in in the future.

I'm closing this per this issue being solved by MapTo and @chaowlert adding #37  for better messages


"Temporary" fix for segfault caused by exception code bug

Hi @SeanTAllen,
The changelog - fixed label was added to this pull request; all PRs with a changelog label need to have release notes included as part of the PR. If you haven't added release notes already, please do.
Release notes are added by creating a uniquely named file in the .release-notes directory. We suggest you call the file 4372.md to match the number of this pull request.
The basic format of the release notes (using markdown) should be:
## Title

End user description of changes, why it's important,
problems it solves etc.

If a breaking change, make sure to include 1 or more
examples what code would look like prior to this change
and how to update it to work after this change.

Thanks.


Facing issue with amplify push/pull on Mac OS

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
14.19.1
Amplify CLI Version
8.3.1 & 12.0.0
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Describe the bug
For the last few days (4-5), I have been trying to push my code but it continuously throws the same error. i.e.  An error occurred during the push operation: Client network socket disconnected before secure TLS connection was established
I have tried it with two different machines with different OS versions -- MacBook Pro (Retina, 15-inch, Mid 2015  with Catalina) and MacBook Pro (13-inch, M1, 2020 with Monetery). I had faced this issue before but that was because of a slow network but this time my network is fast and everything else is working fine.
I have attached the error screen short and the network speed.

Expected behavior
It should push the code the way it was doing before.
Reproduction steps
The only step I am doing is to push the code with

amplify push --y

Project Identifier
No response
Log output

# Put your logs below this line

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hey @Mubashir1044 :wave: thanks for raising this! Are you working behind a VPN or proxy by chance?

I do not think this would resolve the issue but can you try using node 18?

@evcodes I don't think that would change anything. Few days ago with the same node and amplify version everything was working fine. I have tested it with node 16 and amplify 12 but still the same issue

Hey @Mubashir1044 thanks for clarifying! These errors typically arise from some network-related issue, where the CLI is unable to communicate. I have a few follow-up questions:

are you able to reproduce this consistently? on every push?
do any other node.js-based CLI's on your machine experience this?
can you post the project ID output from amplify diagnose --send-report?

@josefaidt I tried to pull the project with that version and got the same issue

Hey @Mubashir1044 thanks for clarifying. Do you have any network filters applied in your macOS settings? Do you experience this when connected to a different network? Any antivirus software running?

Nothing is applied to the network of the macOS settings. One of my colleague (who is in another country) also tried (5-10 tries) with his own machine but he was also facing the same issue.

Hey @Mubashir1044 can you try setting up a new project in a separate directory to see if this is specific to this project?

Hey, @josefaidt got the same issue with the new project initialization.
Screen shots:

Network speed:

Hey @Mubashir1044 thanks for checking that! Are you geographically distant from the target region us-west-2? In an attempt to reproduce this issue I targeted ap-southeast-2 and although the deployment was slow it completed without error.
Do you experience this issue when specifying a region closer to your location? What does your ping look like when specifying a speedtest node in Oregon?

Hey @Mubashir1044 are you still experiencing this?

Closing due to inactivity


Fix HTML and SVG's

Removed duplicate headers on almost every page
Removed duplicate ids
Cleaned useless id's
Fixed invalid HTML

:+1:


[graphql] Add build sha as a header

Description
Add the build sha as a header: x-sui-rpc-build-sha. This PR also switches from tokio::once_cell to once_cell crate.
Test Plan
👀
🚀 ~ % curl -i -X POST http://localhost:8000 \
     --header 'Content-Type: application/json'             \
     --data '{
          "query": "query { epoch { referenceGasPrice } }"
     }'
HTTP/1.1 200 OK
content-type: application/json
content-length: 47
x-sui-rpc-version: 2024.2.0
x-sui-rpc-build-sha: 7f345517b0c7
access-control-allow-origin: *
vary: origin
vary: access-control-request-method
vary: access-control-request-headers
date: Tue, 19 Mar 2024 22:04:20 GMT

If your changes are not user-facing and do not break anything, you can skip the following section. Otherwise, please briefly describe what has changed under the Release Notes section.
Type of Change (Check all that apply)

[ ] protocol change
[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

@stefan-mysten is short commit hash our only option?

@stefan-mysten is short commit hash our only option?

Good question, I do not know why it gets truncated... Hmm 🤔

@stefan-mysten is short commit hash our only option?

Good question, I do not know why it gets truncated... Hmm 🤔

Well, I'm dumb. Because we've set it to 12 characters. Fixed it to 40, so should be good now!

[year].[month].[patch]-[sha].
Wouldn't this be a breaking change? If already folks are using it to parse current version? Otherwise, agreed, that'd be the best and easiest.

dashboard
We had it at 12 characters previously, but the uptime_metric from mysten_metrics seems to create a full commit SHA somehow.

The full 40 characters was asked by Eugene. What's your concern here, it is just that there's more data to transport?
If we are strong against having the full 40 characters (I honestly do not know what's the right choice here), then we could probably use git rev-parse and hope it works ok.

the versioning middleware

That's the part where I got stuck, maybe I did not look where I should have. I think I got it, I need to use from_fn_with_state

The full 40 characters was asked by Eugene. What's your concern here, it is just that there's more data to transport?

Yeah, just the extra data in every request, but if this is what @ebmifa asked for then let's do it.


Statement.execute should return true even if result set has no rows

Same check I use here https://github.com/DataGrip/cassandra-jdbc-driver/blob/35c7b593aaa6ffbfc355765400be525a56157e37/driver/src/main/java/com/dbschema/CassandraResultSet.java#L68

Thanks for your contribution @kornilova203!


Package request: spotube

Project description
An open source, cross-platform Spotify client compatible across multiple platforms
utilizing Spotify's data API and YouTube (or Piped.video or JioSaavn) as an audio source
Metadata

homepage URL: https://spotube.krtirtho.dev/
source URL: https://github.com/KRTirtho/spotube
license: BSD-4-Clause
platforms: linux, darwin, windows

Duplicate of https://github.com/NixOS/nixpkgs/issues/200120


Updated contributing.md

changed to Do not add the issue number in the PR title or commit message..

Pre-Submission Checklist

[x] Your pull request targets the staging branch of FreeCodeCamp.
[ ] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[ ] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[ ] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[ ] Tested changes locally.
[ ] Closes currently open issue (replace XXXX with an issue no): Closes #XXXX

Description

@camperbot I'm sorry i didn't understand. Can you explain in detail?

@SanjayPatel16 If you check at the top of this thread, you will notice that the PR is from a branch named patch-1 on your fork.
We have guidelines to have it from something like 'fix/some-meaningful-name`
And apologies, @camperbot can't revert, it's a silly bot (not a person).

@SanjayPatel16  You should go through the Guidelines for Contributing.

On that note, I am going to close this in favor of #12152 because it's already under QA. I do understand that your PR came first, and should have been considered, but the changes in the other are looking more relevant.
Please do not be discouraged, we have tons of help wanted issues. And we would love to see your contribution. Thanks a lot for your time and effort!
Happy Fixing!
/cc @dhcodes

Yeah, sorry I didn't see this one. The form that says "closes current issue #XXXX" connects the PR to the thread so I saw the other one first. My apologies; we look forward to your future contribution @SanjayPatel16


obstacle avoid with Autoware 1.12.0 open_planner

Hi, I have some problem.
I want to avoid obstacle with autoware, but my car is breaking through the obstacle.
I have vector map(dtlane), points_raw, current_pose.
So, I didn't launch 'ndt_matching'.
I launched these below nodes.

vector_map loader
TF (world to map, map to mobility, baselink to localizer)
ray_ground_filter
lidar_euclidean_cluster_detect
imm_ukf_pda_track
naive_motion_predict
op_global_planner
op_common_params
op_trajectory_generator
op_trajectory_evaluator
op_behavior_selector
pure_pursuit
twist_filter

This picture is the current my situation.

In the photo, the color of the roll_out does not appear 'RED' even though there are obstacles in the driving path.
How can I solve this problem?
I already ask at ROS Answers, but there's no answer to this question..
I look forward to hearing from you in the near future.
Thank you. :)

@c1hong Can you please link to the ROS Answers question? I will see if I can get some help there. This is not a good place for visibility for others in the community..

https://answers.ros.org/question/365289/how-to-implement-avoid-obstacle-with-open_planner-in-autoware/
This is the link.


Hi
my server.go was working fine before. But now each time I get the following error:
server_1 | <stream:stream from="gcm-xmpp.googleapis.com" id="11B9885B7CAD20E3" version="1.0" xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client">
server_1 | stream:featuresX-OAUTH2X-GOOGLE-TOKENPLAIN</stream:features>
server_1 | <not-authorized/>
can you please help!
Thanks,
Rajesh

hey!
did you manage to find a solution.


esp hanging

i just started using this library. i am using esp32 with HVD230 and a provided example.
i already have a can bus working with a raspi and an arduino both mcp2515. raspi is running candump for me to see the traffic.
the esp32 is working fine at 500kbps for sone time: it receives the traffic, send frames. but at some point in time it stops working and only a hard reset makes it work again. is this a known issue?

If you lose connection to the CAN bus and the ESP32's transmissions go unacknowledged, I've found that the whole thing hangs. See https://github.com/miwagner/ESP32-Arduino-CAN/issues/27