Add a nightly channel

We'll have to think a bit how we update the version DB for that as we don't want to publish a new version in the store every night... We should probably have a separate version db for nightly builds or something like that, so that we can insulate users that don't deal with that from frequent updates of that. We also need to think about an ID scheme for nightly builds. Presumably there is one already? I'm just not familiar with it :)

Wouldn't it be better for juliaup to read in the version db from an external source instead of baking  in the db version manager with the juliaup source  itself, thereby eliminating the need to update juliaup when new nightlies are uploaded?

Having it baked in simplifies things a lot: don't have to handle the situation where a file gets corrupted, don't have to worry about the file version and the binary version drifting apart, don't have to figure out a way to download version file updates in the background somehow etc. The current approach just makes for a very stable and robust solution, with no real downside.
So I think my preference at the moment would be to come up with something special for the nightlies, and leave the "normal" case as is.

That makes sense to me. The mechanism used for nightlies can be battle-tested and if deemed reliable enough, could then be used for other channels if so desired in the future.

I just tried juliaup and immediately wanted a nightly channel.

juliaup add beta will get you the 1.8 beta.

As a start, nightlies don't even need a version database. They can just download whatever file lives at https://julialangnightlies-s3.julialang.org/bin/$os_str/$arch_dir/julia-latest-$os_append$arch_append.$extension
(see https://github.com/LilithHafner/UpdateJulia.jl/blob/main/src/UpdateJulia.jl#L111)

I think the issue with that may be knowing when to download new nightlies? But perhaps for nightlies it would be fine to try one per day? Or maybe something with ETags? I believe that S3 automatically supports ETags, so this could be pretty simple to implement.

For my use cases, yestaday's nightly is just as good as today's, so a time-based approach would be fine.
ETags would be great if they could be fetched promptly, but the queries I wrote are sometimes quite slow:
julia> @time HTTP.request("HEAD", "https://julialangnightlies-s3.julialang.org/bin/mac/x64/julia-latest-mac64.dmg")
 24.274753 seconds (632 allocations: 100.922 KiB, 0.05% compilation time)
HTTP.Messages.Response:
"""
HTTP/1.1 200 OK
Connection: keep-alive
Content-Length: 118106979
x-amz-id-2: Gbv+lpFooK5eqE8rceZGyb8gqx5r/tmBXwwLM+i5EugUBqaB2DK31ebTMTM+s4NqdZpFJY7fIrY=
x-amz-request-id: BBF9C2X78WGEEH5Q
Last-Modified: Tue, 21 Jun 2022 20:10:10 GMT
x-amz-expiration: expiry-date="Sun, 21 Aug 2022 00:00:00 GMT", rule-id="Cyberduck-u1YrSIk1"
ETag: "bc45bc4361d20c7f72a92bb2481d77ab-15"
Content-Type: application/x-apple-diskimage
Server: AmazonS3
Accept-Ranges: bytes
Age: 268
Date: Wed, 22 Jun 2022 14:32:40 GMT
Via: 1.1 varnish
X-Served-By: cache-nrt-rjtf7700065-NRT
X-Cache: HIT
X-Cache-Hits: 0
X-Timer: S1655908361.691796,VS0,VE72

"""

Oof, yeah, that's quite slow. What about spinning off a background process that does the ETag thing, updates if there's an update to be had and then exits. That way the nightly would be available the next time you run the command? Would require a bit of locking, of course, but I think that's already needed.

That sounds reasonable. I think nightly release channel is one of the few cases where it is acceptable to perform automatic silent background updates (i.e. triggered when a user invokes $ julia +nightly).
Even with automatic updates in this manner, it is possible for a user to invoke $ julia +nightly and get an old version. In this case, we should prompt them in a similar way we prompt folks with an out of date release or beta channel with an additional hint that an automatic update is underway.
Ideally, we can still support $ juliaup update nightly, even with automatic updates. If an automatic update is already underway, $ juliaup update nightly blocks until it is complete.

That sounds like a great plan to me.

Since #131 got fixed https://julialang-s3.julialang.org/bin/versions.json is used to find new versions. That JSON doesn't have nightlies. Though it does have the 1.9.0-alpha1 for instance, and with be6719e7996502122c4723b8cd18d802a48ae7e1 that is available in the alpha channel.
So I guess we need to decide if nightlies belong in versions.json, and if not, juliaup needs to get it from julialangnightlies-s3 outside of the version database. Either way the proposed fixes of #197/#384 won't apply anymore.

So I guess we need to decide if nightlies belong in versions.json, and if not, juliaup needs to get it from julialangnightlies-s3 outside of the version database.

I'm wondering what would be the problem to get nightly from julialangnightlies-s3? I think download it directly from there would be less changes to upstream?

Yeah indeed, I didn't mean to imply that julialangnightlies-s3 was a problem, just that versions.json related changes caused the previously submitted PRs for nightly to no longer be an option.

Another case in point that this should be done: Julia GtiHub action has nightly. It'd be nice to be on par with it. E.g. if the nightly-based GitHub workflow fails, it's nice to have a quick way to try it out locally.

For what is worth, it is trivial to do this yourself using the link option in juliaup in order to link to a custom executable
# download the nightly
 wget https://julialangnightlies-s3.julialang.org/bin/linux/x86_64/julia-latest-linux-x86_64.tar.gz -O /tmp/julia.tar.gz
# remove the old nightly
 rm -rf ~/.julia/juliaup/julia-nightly
# set up the new nightly and clear up the folder name
 mkdir ~/.julia/juliaup/julia-nightly
 tar -xf /tmp/julia.tar.gz -C ~/.julia/juliaup/julia-nightly
 mv ~/.julia/juliaup/julia-nightly/julia-*/* ~/.julia/juliaup/julia-nightly/

The first time you do this you also need juliaup link nightly ~/.julia/juliaup/julia-nightly/bin/julia.
Now I have a nightly managed by juliaup, and a non-juliaup command line shortcut to update it.

@Krastanov this is a good workaround, maybe worth posting somewhere visible. But also this is exactly the kind of code I was hoping to avoid when getting juliaup…

Bump, this is the last thing we need to reach feature parity with UpdateJulia.jl

Just FYI, I'm currently taking the PR from @maleadt that we reverted and am modifying that a bit with some of the new strategies we discussed since then. Will hopefully have a new PR soon.


Change work type property from String to WorkType

What this PR does / why we need it:
In order to make the API define better, an enum can be used instead of  a string field to describe the nature of the work unit resource.
Change type

[ ] New feature
[ ] Bug fix
[ ] Unit tests
[ ] Integration tests
[ ] CI
[ ] Documentation
[x] Auto generated SDK code

Impacted services

[x] Workflow Service
[ ] Notifivcation Service

Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.

/lgtm


Optimizing SetBuoyancy. Removed isnan. Added Ent:Get/SetFriction

Tested and working in one commit !

Looks good to me. Any objections?

Done ! ;D

local friction = math.Clamp(friction, -1000, 1000)
this:SetFriction(friction)

There is no need to create a variable if you use it only once. Just use
this:SetFriction( math.Clamp(friction, -1000, 1000) )

Same thing in propSetBuyoancy ;)

I know but that way is more organized and read-friendly if you know what I men ;D

There is no single word for a whole day... I guess the silence really means agreement ...

I'll pull this when I get home from work unless anybody has any more comments in the next couple of hours.


Getting AttributeError: client_secret

I have a public client/application, so I don't use client_secret.  Version 1.0.0 breaks this relationship by requiring client_secret anyway.
Breaking commit: https://github.com/idan/oauthlib/commit/539558a02edbadb8d6ef690fb0beb2510a5eeb17

@dustinfarris can you provide some detail on your issue? I think I know what the fix could be, just to be sure and build a dedicated test case. Thanks.

I confirm, I have the same issue.
with the following app
client_type: public
grant_type: password

@masci whenever my client tries to authenticate it sends
client_id=my-public-client
grant_type=password
password=mypassword
username=bob

I use django-oauth-toolkit which proxies this request to oauthlib.  As of oauthlib v1.0.0 this raises AttributeError with the following traceback:
Stacktrace (most recent call last):

  File "django/core/handlers/base.py", line 132, in get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "newrelic/hooks/framework_django.py", line 499, in wrapper
    return wrapped(*args, **kwargs)
  File "django/views/generic/base.py", line 71, in view
    return self.dispatch(request, *args, **kwargs)
  File "django/utils/decorators.py", line 34, in _wrapper
    return bound_func(*args, **kwargs)
  File "django/views/decorators/csrf.py", line 58, in wrapped_view
    return view_func(*args, **kwargs)
  File "django/utils/decorators.py", line 30, in bound_func
    return func.__get__(self, type(self))(*args2, **kwargs2)
  File "braces/views/_forms.py", line 22, in dispatch
    return super(CsrfExemptMixin, self).dispatch(*args, **kwargs)
  File "newrelic/hooks/framework_django.py", line 872, in wrapper
    return wrapped(*args, **kwargs)
  File "django/views/generic/base.py", line 89, in dispatch
    return handler(request, *args, **kwargs)
  File "django/utils/decorators.py", line 34, in _wrapper
    return bound_func(*args, **kwargs)
  File "django/views/decorators/debug.py", line 76, in sensitive_post_parameters_wrapper
    return view(request, *args, **kwargs)
  File "django/utils/decorators.py", line 30, in bound_func
    return func.__get__(self, type(self))(*args2, **kwargs2)
  File "oauth2_provider/views/base.py", line 170, in post
    url, headers, body, status = self.create_token_response(request)
  File "oauth2_provider/views/mixins.py", line 124, in create_token_response
    return core.create_token_response(request)
  File "oauth2_provider/oauth2_backends.py", line 106, in create_token_response
    headers)
  File "oauthlib/oauth2/rfc6749/endpoints/base.py", line 64, in wrapper
    return f(endpoint, uri, *args, **kwargs)
  File "oauthlib/oauth2/rfc6749/endpoints/token.py", line 100, in create_token_response
    request, self.default_token_type)
  File "oauthlib/oauth2/rfc6749/grant_types/resource_owner_password_credentials.py", line 99, in create_token_response
    if self.request_validator.client_authentication_required(request):
  File "oauth2_provider/oauth2_validators.py", line 146, in client_authentication_required
    if request.client_id and request.client_secret:
  File "oauthlib/common.py", line 409, in __getattr__
    raise AttributeError(name)

Perhaps client_secret should be added to this list?: https://github.com/idan/oauthlib/blob/master/oauthlib/common.py#L385-L400

Yep, I think that's the fix, had a similar problem, see #363 - I'm going to update the PR to cover your case.

Thanks!

Ok, I think this is an issue in DOT actually, I've already fixed OAuth2Validator.client_authentication_required method in a local branch but I need #363 to be merged before pushing the code

@masci for what it's worth: the same thing breaks in Flask-OAuthlib too

Issue is fixed in DOT v.0.9.0, still persists in Flask-OAuthlib, patch already in place in #368 waiting for merge

1.0.2 is released and includes the fix for this issue.


lumen integration

Hello,
Is it a easy way to integrate it with lumen ?
For now I encounter issues with config logic.

I'm not using Lumen myself, so I can't help you here...
I'd accept a PR that adds Lumen compatibilty


Include cmd-exclude-prefixes-k8s

Add https://github.com/networkservicemesh/cmd-exclude-prefixes-k8s to the apps.
Deploy cmd-exclude-prefixes-k8s with all examples
Provide examples to show cmd-exclude-prefixes-k8s working correctly, and exclude prefixes being excluded from IP ranges

close with https://github.com/networkservicemesh/deployments-k8s/pull/3377


gree/jose

It needs "gree/jose": "0.2" in require

Fix in commit 286234bd8b2c654e2721ef6717105295f2f8346b


What is the preferred way to refer to text/SMS messages?

What do you need?
https://github.com/AusDTO/gov-au-content-guide/issues/189

Content clinic: use "text message"

Added here http://content-guide.apps.staging.digital.gov.au/terms-phrases/#digital-terms


Ids for lambda parameters

Hello :octocat:
This PR introduces ids for lambda parameters, which unblocks several issues and allows us to report errors and provide information more precisely.
Closes #624

[X] Tests added for any new code
[X] Ran npm run format (or had formatting run automatically on all files edited)
[x] Documentation added for any new functionality
[x] Entries added to the respective CHANGELOG.md for any new functionality
[ ] Feature table on README.md updated for any listed functionality

@shonfeder This breaks compatibility with the Apalache translation, as we anticipated :disappointed:. How can we handle the broken tests? Since we don't have backwards compatibility in neither side, it might be tricky to release a new Apalache version with this change that will break every other PR tests except for this. Perhaps this should be a non-required CI check?


Race condition in all commands that expect a reply (sub/unsub/publish w QoS >0)

I'm currently tracking down a problem with publishing and I think I've hit a possible race condition in the send where a second publish message sent at the wrong time will stop the callbacks from the first happening. This is happening for QOS > 0 - when I look I can see the data from the first send actually makes it to the platform, but it appears the code for the rest of the QOS1 or 2 transaction never happens.
I am trying to do transaction counting in order to work out when I can sleep and if I leave the unit running it all seems fine, which is a bit strange because initially I send 3-4 publish messages all at once and it works fine. These gradually become separated over time and it's when they start to drift apart that they mess each other up. The big problem for me is that the publish callback is not getting called and so my transaction count is not being decremented properly.
I'll capture a log and attach.

OK I've now looked at the code and a race condition is occurring when QOS > 0 and the network latency is larger than the time between publish commands. If you publish several messages in quick succession then this doesn't have to be very large at all, and in fact my code is only working by good luck rather than on purpose - if I was publishing several messages with different QOSs then this would break very quickly, and right now if a message fails to publish it will likely report the wrong one has failed.
The problem occurs because the MQTT client only maintains one pending message - when you publish more than one message with QOS > 0 close together, you will end up with more than one message in a pending state waiting for an ACK and you lose the state for the first message published.
This is a pretty big architectural/design issue - to solve this you'd need to either:

make mqtt publishing a strictly serial process and only publish the next message once the first is fully complete. If you're on a slow network this would introduce performance overheads
save pending message state in a list/queue instead of a single variable, and then add logic to track the state of each message and pop it off the list once complete.

Either way it's quite a big change to the code.

Turns out the library has a problem with any command that requires a reply. If the timing between messages isn't right you lose all but the last message requiring a response.
The rewritten MQTT in the current RTOS SDK is really neat, and they've implemented an outbox for messages, which is a nice solution, but there's no corresponding version for NonOS.
So I'm currently in the process of porting the new library over

@davydnorris Have you been able to get this fixed, I was wondering whether you had a repo with a fix as I am experiencing the same issue.

@maverickchongo - no, at this point I have given up on this repo as it seems to no longer be actively maintained. I pulled down the ESP32 and ESP8266 RTOS MQTT code and got it to the point where it was almost working with NonOS but they have used the lwip socket API and blocking calls for the transport, which is actually a really badly performing approach.
So I have temporarily gone back to QoS 0 to get my product out the door, and then I am going to write my own completely transport agnostic MQTT based on ideas from the other libraries out there, and on messaging protocol best practice. It will use a non blocking transport layer that works with a generic inbox and outbox. These will both be processed independently using event queues and loops - that will mean both RTOS and NonOS can use the same library.

@davydnorris Just ran into this issue myself. Will your new project be open source? If so I'd be interested in helping out and/or testing for NON-OS

@someburner it absolutely will be open, and I'd love any help offered. Just got to get my sensor box out on some poles for a client and then I'll be looking at this.
The sources I've pulled to date are this one, the new RTOS and IDF versions (both ESP8266 and ESP32), the Eclipse paho sources, and the WolfMQTT sources.
My architectural goals for the new library are:

completely thread agnostic.
inbox and outbox use bip buffers so messages or message pieces are all contiguous
because of 2 above, no message copying, no double allocating, everything is in the buffers
because of 3 above, it will need mqtt_message_create(size) and mqtt_message_dispose(id) functions, but I figure that's an acceptable compromise
transport layer agnostic, even more so than the new IDF version
main control loop agnostic, so can be used with callback based, event based, thread based, RTOS or NonOS

non-blocking

Of course, if this lib could easily be hacked to include an inbox/outbox so that QoS 1 and 2 could be implemented properly then that may do us for now, but there's a lot that is good about the new IDF implementation


add set_permissions()

As I mentioned in #25, I initially left this out because I wasn't sure how to include the permissions in the error message, but I noticed that File::set_permissions already exists and also just doesn't mention the exact permissions in the message.
This does the same. With this, all free functions in std::fs have wrappers.

Thanks!

I've published version 2.4.0 with this change (plus your previous changes)


How to pull RPMs from URL

Get playbook working using cached RPMs (from Ag website repo). http://home.badc.rl.ac.uk/astephens/rpms/
repo=http://yumit.esc.rl.ac.uk/raltools/7/RPMS/
rpms=curl -XGET $repo | grep -i slurm | grep -P "19.05.5" | cut -d= -f5 | cut -d\" -f2
for r in $rpms; do
wget $repo/$r
done
And:
yum  localinstall *.rpm

Done


Invite Bot

I am a noob at coding 😢 so can you give me a link to invite your bot to my server ? Please I want to play RPG with my friend

Sorry, this bot can't be invited as it is not meant to be a standalone, and I've put the code for it on here for reference only.


MB-16120 include shipment address updates in prime api

Jira ticket
Summary
TODO

Messages

:book:
:link: MB-16120

  Generated by :no_entry_sign: dangerJS against 57720772f436392f83759643d68b6470484e9974


Required option does not work in version 0.8.3

Hi there
How can I use required settings in version 0.8.3?!
I have two controls:
    $controls[] = array(
        'type' => 'radio-buttonset',
        'setting' => 'my_bg_mode',
        'label' => 'Background Mode',
        'section' => 'my_default_section',
        'default' => 'normal',
        'priority' => $priority,
        'choices' => array(
            'normal' => 'Normal',
            'colorful' => 'Colorful',
        ),
        'transport' => 'postMessage'
    );

    $controls[] = array(
        'type' => 'color',
        'setting' => 'my_bg_color',
        'section' => 'my_default_section',
        'default' => '#cccccc',
        'priority' => $priority,
        'required' => array(
            array(
                'setting'  => 'my_bg_mode',
                'operator' => '==',
                'value'    => 'colorful')
            ),
        'transport' => 'postMessage'
    );

but my my_bg_color control is always visible!
also when I click on my_bg_mode control buttons, nothing happens, & my_bg_color control is always visible.
Any Solution?!
Thanks in advance

I fixed this issue here (https://github.com/DevelopOnline/kirki/commit/0f70a3645b78a3d563971247508367e938ac065c)

I have the same issue, both on radio buttons and image buttons, none of those required settings are working with 0.8.4

The solution by DevelopOnline works perfect for me.

This has been fixed in the master branch I'm closing this issue. :+1:


feat: highlight only keyword in no-focused-tests rule

This PR fixes/implements the following bugs/features

[ ] Bug
[x] Feature
[ ] Breaking changes

Closing issues
Addresses this comment https://github.com/veritem/eslint-plugin-vitest/pull/9#issuecomment-1359371437
The user has correctly reported that the current no-focused-tests rule is highlighting the entire test case as a failure. After this PR only the only keyword will be highlighted as a failure.
Also updates the unit test to capture this requirement.

I tried pnpm install https://github.com/veritem/eslint-plugin-vitest#47fb1fb --save-dev and now have this in package.json: "eslint-plugin-vitest": "github:veritem/eslint-plugin-vitest#47fb1fb". But after reloading ESlint I still get the whole code block highlighted. Do you know if I must do something else to try this PR?

Try adding this to your package.json:
"eslint-plugin-vitest": "veritem/eslint-plugin-vitest#pull/26/head",

No luck :/ Could not resolve pull/26/head to a commit of https://github.com/veritem/eslint-plugin-vitest.git.
Anyway if you got it working I guess it's safe to merge... 😇


Add support for Spanish dictionary

Hi there! First of all: thank you so much for creating this! I'm learning Pali and was considering asking a friend to build this as a side project, but I'm happy to see you've done most of the things I wanted (dictionary + Pali suttas with click-to-get-definition feature).
I'm wondering: how can I help you add support for a Spanish dictionary? I'm adding a link below to the Pali-Spanish dictionary my teacher suggested. What would need to happen for you to include it? I'm assuming the PDF would need to be dissected into some kind of database... I don't have the time to do that myself at the moment, but if you give me the specs of what you need, I'll be happy to hire a freelancer to help get it done.
https://www.dropbox.com/s/1rrz2ysdapykbsx/Diccionario_pali_espanol.pdf

Hi, nice to hear from you!
It's easy to add Spanish support as long as you export the PDF as some format that is easy to parse by program.
Basically I would suggest that you export the PDS as array of (key, value) pairs, where
key: the Romanized spell of the pali word. For example,

sacca

value: the string of HTML format which contains the meaning of the word. For example,

nt. sacca means truth

You can export the array of (key, value) pairs to JSON, CSV, or any popular format that is easy to read and parse by program. Thanks again for your help :)

Sounds good! I'll try to get this done and come back here with the file. It might take some time. Once this is done, I would also be happy to help translate the web app's UI itself to spanish so you can add it as a supported language. I can do that myself.
Happy new year!


[Feat]: Configure and add tests for scripts

Reason/Context

The AsyncAPI project and the number of contributors to the AsyncAPI website are growing. Sometimes things don't go as usual and may break unexpectedly when contributors work on a critical part of the website.
We need a mechanism to ensure that all the scripts inside the website/scripts/* folder are intact and working as they should be.
Writing unit tests for these scripts is the best way to ensure things don't break in production.

Description:

Research different testing engines and frameworks.
Integrate one of them into the AsyncAPI website.
Write proper test cases for all the scripts inside the /scripts folder.
Create a CI workflow to run all tests in GitHub Actions and catch errors before shipping the code.

Required skills:

JavaScript, Next.JS, Unit Testing, CI/CD

Please refrain from working on this issue directly. You may DM me on Slack to know the plans we have for this feature request.

Mentor for this project:
Primary Mentor - @anshgoyalevil
Secondary/Backup Mentor - @akshatnema

hi @akshatnema Can i work on this issue?

@anshgoyalevil @akshatnema
Hope you are doing well. I am writing to show interest in working on this issue under the GSoC 2024.
My approach to solving this problem:
Step 1. Install the testing engine
Step 2. Configure the testing engine with the project
Step 3. Write the test (Coding part) <- Construction & feedback part
Step 4. And check if it working with the local environment or not
Testing Framework
I have decided to go with the jest testing framework/engine.
Why I have chosen jest?

Correctness of tests: If there is any situation where our test depends on a global state, then Jest can run these tests in parallel.
Extensible to future uses: Jest is compatible with a variety of JS frameworks e.g. Next, Typescript, react, node etc. so Jest helps us to make a uniform test suit for other parts of projects as well if we decide to use other frameworks in future for our project.
Easy debugging: When our test fails then Jest will help us in debugging because it provides extra context as to why our test failed.
Coverage of codes: If we want a high overview of code then jest will help us to give more coverage only by adding
--coverage flag & we don't need to do any kind of additional setup for the coverage.
Open-source & community support: As Jest is a popular open-source project, it provides excellent community support.

Please correct me if I am wrong anywhere.
Best regards
Ankur

Thanks for showing interest @ankur0904 :)
I would recommend you, and everyone else eager to work on this issue, please follow the official GSoC'24 timeline.
We will be reviewing the proposals during the Contributor Proposals Open period. In the meantime, you can try exploring the project and learn more about it, or better frame your proposal with various iterations.

@anshgoyalevil
Are there any qualification tasks (similar to json-schema) for this project?

@anshgoyalevil
Are there any qualification tasks (similar to json-schema) for this project?

Hey @anshgoyalevil and @akshatnema my kind greetings. I am Ashmit Jagtap from Indian Institute of Information Technology, Pune. A Second Year Computer Science student looking forward to contribute to this project and idea. :)

@anshgoyalevil Are there any qualification tasks (similar to json-schema) for this project?

It's always better to show your knowledge by either solving issues or reviewing other PRs. Though that is not a hard requirement but is always preferred :)

Hii @akshatnema @anshgoyalevil
Hello! I'm Aditya Singh, a Computer Science undergraduate from India with a passion for open-source contributions. Previously, I had the opportunity to participate in Google Summer of Code at Rocket.chat, which was an enriching experience. This season, I'm eager to channel my skills and knowledge into contributing to AsyncAPI. This project has captured my Interest, and I'm excited about the potential impact I can make by contributing to AsyncAPI. I'm looking forward to contributing and make some impact

What interests you most about this project?

The "AsyncAPI: Enhancing Script Stability for AsyncAPI Website" project presents a compelling opportunity to contribute to the improvement of AsyncAPI's online presence and user experience. Enhancing script stability is critical for ensuring that users can access and interact with the AsyncAPI website seamlessly. I'm particularly interested in diving into the intricacies of web development and optimization techniques to address script stability issues effectively.

As mentors and project coordinators, how can we get the best out of you?

With prior experience in GSOC with Rocket.chat I value open lines of communication with mentors and project coordinators to discuss goals, expectations, and any challenges that may arise throughout the project. Additionally, I thrive in an environment that encourages creativity and problem-solving, where I can explore different approaches and technologies to achieve project objectives

Is there anything that you’ll be studying or working on whilst working alongside us?

While working on this project, I'll be diving deep into web performance optimization techniques, particularly focusing on script loading and execution strategies. Understanding how to minimize render-blocking scripts, prioritize critical resources, and leverage caching mechanisms will be essential for enhancing script stability and overall website performance. And for adding tests I would use platform like Jest for creating test cases which will

ensure things don't break in production.
Despite having many contributors everything keeps running smoothly

We'd love to hear a bit about your work preferences, e.g. how you keep yourself organized, what tools you use, etc.?

In terms of organization, I rely heavily on project management tools like Notion to keep track of tasks, deadlines, and progress. I find that breaking down larger tasks into smaller, manageable chunks helps maintain focus and momentum.
For development, I prefer using modern web technologies and frameworks that emphasize performance, maintainability, and scalability. I'm proficient in HTML, CSS, and JavaScript/TypeScipt, and I'm comfortable working with frameworks like NextJs build dynamic and responsive user interfaces. Version control with Git and collaboration via platforms like GitHub are integral parts of my workflow.
Regarding a weekly schedule with clear milestones and deliverables, here's a suggested outline:

Week 1: Review existing scripts on the AsyncAPI website and identify areas for optimization.
Week 2-3: Implement script loading optimizations, such as asynchronous loading and lazy loading, to enhance website performance.
Week 4-5: Conduct comprehensive testing and performance analysis to evaluate the impact of optimizations and identify any regressions.
Week 6-7: Address any compatibility issues and fine-tune script stability across different browsers and devices.
Week 8-9: Document the implemented optimizations and provide guidelines for future maintenance and enhancements.
Week 10-12: Collaborate with the AsyncAPI team to deploy the enhancements to the production environment and monitor performance metrics post-deployment.

Throughout the project, I'll maintain open communication with mentors and stakeholders, providing regular updates on progress, challenges, and adjustments to the schedule as necessary.

Hi! I'm Uzair KHAN, a student at BPIT India studying Comp Sci.
I am programming enthusiast and my expertise are in mern stack!
I have created several projects

uzzenger: fullstack rtc chat app using mern stack and websockets
uzzurcel: vercel clone backend, using aws S3, ecs, ecr, sockets and redis for logs,
crisp url: url shortener using ejs and express to implement server side rendering
readingTime: a chrome extension to assist in reading by creating your cursor dynamic to point to text.
....and many more
githubLink

To contact me<EMAIL_ADDRESS>What interests you most about this project?

Up until now my focus was primarily in development, but testing and its role in sdlc is what i wanted to get myself into

This project will become a major factor and incentive to learn and put those learnings to use by completing this project

pursuing this would drive me to learn more and more about designing tests and ensuring quality and functionality of code

As mentors and project coordinators, how can we get the best out of you?

Providing me with guidance by clear and frequent communication

Assisting me with my questions as I can be very curious and inquisitive

Is there anything that you’ll be studying or working on whilst working alongside us?

Learning more about collaborating and writing industry standard code and following such practices

Learning testsdesign principles and patterns, and frameworks that make it possible to create test suites

Code review and debugging

We'd love to hear a bit about your work preferences, e.g., how you keep yourself organized, what tools you use, etc.

figma for designing
i use todo list like google keep and google calendar
google meet for communicating and collaborating
vs code for coding development and testing
postman for api testing
git for version control
docker for containerizing and controlled runtime environment

Once you’ve selected a project from the ideas section, please suggest a weekly schedule with clear milestones and deliverables around it.
Week 1: Research and Selection of Testing Framework

Milestones:

Research different JavaScript testing engines and frameworks.
Evaluate compatibility with Next.js and ease of integration.

Deliverables:

Documentation outlining the pros and cons of each testing framework.
Selection of the most suitable testing framework with reasoning.

Week 2: Integration of Testing Framework

Milestones:

Set up the chosen testing framework within the AsyncAPI website project.
Configure testing environment and dependencies.

Deliverables:

Initial configuration and setup of the testing framework.
Documentation detailing the integration process.

Week 3-4: Writing Test Cases

Milestones:

Identify all scripts within the /scripts folder requiring testing.
Write comprehensive unit tests for each script.

Deliverables:

Completed test cases covering all scripts in the /scripts folder.
Detailed documentation of test cases including inputs, outputs, and edge cases.

Week 5: CI/CD Workflow Setup

Milestones:

Set up a CI workflow using GitHub Actions for the AsyncAPI website repository.
Configure automated triggering of tests upon code pushes and pull requests.

Deliverables:

Established CI/CD workflow integrated with the chosen testing framework.
Documentation on how to trigger and monitor tests within the CI/CD pipeline.

Week 6: Testing, Debugging, and Documentation

Milestones:

Execute the CI/CD workflow to run all tests in GitHub Actions.
Analyze test results and debug any failing tests or errors encountered.
Finalize documentation of the testing process and CI/CD integration.

Deliverables:

Completed execution of the CI/CD workflow with successful test results.
Comprehensive documentation covering testing process, CI/CD setup, and troubleshooting guides.

Regards
Uzair

@anshgoyalevil Hope you are doing well. I am writing to show interest in working on this issue under GSoC 2024.
I did some reaserch about JavaScript unit testing frameworks like Jest, Mocha & Chai, and I think Jest is the best and it has great Next.js support.
Here is how I would approach this project:

Setup Phase (1 week)

Add Jest and dependencies to project
Configure Jest for Next.js project

Testing Phase (2 weeks)

Review each script in /scripts folder
Write test cases to cover all functionality
Test both positive and edge cases
Add tests to scripts folder structure

CI/CD Phase (1 week)

Configure GitHub Actions workflow
Add script to run all tests on PRs
Validate tests pass before merging
Monitor tests and update for any code changes

Hey Everyone!!
Please refrain from jumping on this issue directly

@anshgoyalevil @akshatnema I cant join the slack channel I want discuss about this project with you guys,  the link is expired can someone share the link for slack channel.

Closing as completed with reference to GSoC PRs by @vishvamsinh28


Just wanted to say thanks

For making this!! I haven't had the time to try this yet but I am insanely excited.
This is the final nail in the coffin - now I'll be able to do everything in vim
style! Thanks!!
I might drop in with a couple of questions in the future :D

No problem! :)

is the  modifier key the option/alt key on mac?


About tag 9.0.2

👋 Just raise this issue to confirm whether 9.0.2 is the latest release, seeing in rubygems, but not the latest release. Thanks!
relates to https://github.com/Homebrew/homebrew-core/pull/122527

Hi @chenrui333
Yes, 9.0.2 is the latest release.

@joeyates thanks for confirming it, can you mark that tag as latest release? Thanks!! 🙏

oh, i actually mean the github release rather than git tag

OK, clear now. I've cut a new latest release.


Update Identity version to a version that is released.

Updating @azure-identity version to a version that has been released.
Update date of release.

/azp run js - communication-network-traversal - tests

/azp run js - communication-network-traversal - tests

/azp run js - communication-network-traversal - tests

@sarangan12 That is a fair point. This is a problem we face only with beta packages as they get pinned to a specific version.
@praveenkuttappan has been talking about tweaking the release pipeline to include a check that will result in the release pipeline failing if the package is depending on a version of a dependency that is not released yet. That should catch such issues. This same package is also dependent on a version of communication-common that is not released either.
@praveenkuttappan Any updates on that check in the release pipeline?


Remove yum workaround

Looks OK, thanks!

@omron93 Any idea why the rhel CI job is getting killed?

[test]

@pkubatrh There is 2h timeout for tests. And in this case testing of all dependent images is not finished before timeout is reached.
I've changed it to test only latest version of each dependent image.
[test]

Thanks! Tests are passing. Merging


I can not do git submodule update --init --recursive

Hi
I'm a student at the University of Auckland and the article I chose to research in my Cyber Security course was The Witcher. I want to download and use it, but I get an error while running it. Unable to perform the first step of the update operation. We are expecting a reply

hello ,

Should be a SSH and the problems caused by<EMAIL_ADDRESS>(https://stackoverflow.com/questions/17032637/permission-denied-for-certain-git-path)
You can also delete the submodule and re-add the submodule (resource link replaced with https). Reference: https://www.cnblogs.com/Doule/p/6544185.html

Thank you for you commit. I will try it.


Match example given in readme for session service's authorize method to the api docs

Following on from https://github.com/simplabs/ember-simple-auth/issues/884.
It was unclear in the readme that headerName and headerValue are available, whereas the api docs shows the method in full.

The actual arguments that the block is called with actually depend on the used authorizer. I'd rather have a generic example in the README, e.g.
this.get('session').authorize('authorizer:some', (/*authorization data*/) => {
  // use authorization data
});

Agreed, I think that and a further link to the api docs cover both scenarios?

👍🏻


community-operators [CI] mongodb-atlas-kubernetes (0.5.0)

@antonlisovenko I am removing unsupported field.
Signed-off-by: Martin Vala<EMAIL_ADDRESS>

hi @mvalarh
sure, feel free to merge the PR


[test] Guard AVR test with CODEGENERATOR=AVR

This test is only relevant for the AVR target, so it should be guarded with the CODEGENERATOR=AVR condition to avoid running it when the target is not enabled in llvm-targets-to-build.
Wasm CI does not build the target to reduce CI time https://ci.swift.org/job/oss-swift-pr-test-crosscompile-wasm-ubuntu-20_04/1187/console

@swift-ci test WebAssembly

@swift-ci smoke test


Code coverage automation + CHANGELOG.md init

This PR integrates cargo tarpaulin to report code coverage on each PR. The current code coverage is 61% (library only), which is acceptable. The goal is to gradually bring the project to 75%. An integration with Coveralls (or Codecov) is being considered for adding a badge and making a dashboard available.
An additional set of clippy checks has also been added to enhance the quality of the project.
A start of a changelog has also been generated with git cliff (in unreleased mode). Full automation of the changelog and releases will come in a subsequent PR.

You'll notice "check-external-types" and "rustfmt" aren't being completed on this PR.  You'll have to let me know which status checks to update as mandatory


Fix implicit marking of parameters as nullable, deprecated in PHP 8.4

Fix implicit marking of parameters as nullable, deprecated in PHP 8.4

Hi, it would be nice if this PR was merged :D

hello could this PR be merged? It would be really nice :-)


MB-14156: global scroll to top

Jira ticket for this change
Summary
Is there anything you would like reviewers to give additional scrutiny?
this article explains more about the approach used.
Setup to Run Your Code

💻 You will need to use three separate terminals to test this locally.
Terminal 1
Start the Storybook locally.
make storybook

Terminal 2
Start the UI locally.
make client_run

Terminal 3
Start the Go server locally.
make server_run

Additional steps

Access the
Login as a

Verification Steps for Author
These are to be checked by the author.

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

Frontend

[ ] User facing changes have been reviewed by design.
[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] There are no new console errors in the browser devtools
[ ] There are no new console errors in the test output
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.

Backend

[ ] Code follows the guidelines for Logging
[ ] The requirements listed in Querying the Database Safely have been satisfied.

Database
Any new migrations/schema changes:

[ ] Follows our guidelines for Zero-Downtime Deploys
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

Screenshots

Warnings

:warning:
This PR does not include changes to storybook, even though it affects component code.

:warning:

Files located in legacy directories (src/shared or src/scenes) have
been edited. Are you sure you don’t want to also relocate them to the new file structure?
View the frontend file org ADR for more information

Messages

:book:
:link: MB-14156

  Generated by :no_entry_sign: dangerJS against 77a75e592e5d468c5db6f79ed350970a4e0d896c

@ronaktruss The flows I worked through on the Customer app all looked really good.
The only edge case I came across was in the office app on the Move Task Order page where we replace notifications.  So if you request a reweigh on a shipment it displays a notifciation, then if you scroll to request a diversion the notification changes but we aren't scrolled back up to the top to see the change.

@ronaktruss The flows I worked through on the Customer app all looked really good.
The only edge case I came across was in the office app on the Move Task Order page where we replace notifications. So if you request a reweigh on a shipment it displays a notification, then if you scroll to request a diversion the notification changes but we aren't scrolled back up to the top to see the change.

Is there a specific user/scenario that you tried this on? This seems to be working on my end in both chrome and firefox.


Question: How to save JSON to file with proper new line return?

Dear all:
I am trying to export the processed json using the lib like that
let representation = try! json.rawData()
try! representation.write(to: URL(fileURLWithPath: path))
That gives me this exported JSON in a file
{"rss":{"green":255,"red":255,"url":"http://www.abc.es/rss/feeds/abc_ultima.xml","blue
But original JSON it's more much human readable
{
"rss" : {
"green" : 255,
"red" : 255,
"url" : "http://www.abc.es/rss/feeds/abc_ultima.xml",
"blue" : 255,
"ypos" : 960
}, [...]
}
Is there something I can do to export the JSON like that?
Thanks in advance for helping me

Try this: http://json.parser.online.fr/

Thanks for that!


refactor [jitpack] service

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @chris48s!

  Generated by :no_entry_sign: dangerJS against 062d9a06e9a334b2f8a920e79261b6b61c4985af


Docker Deployment

Hello all,
please let me know the steps to do a docker deployment on jenkins slave after CI

Build Images Part
Install docker on jenkins slave.
Add jenkins user to docker group
usermod -aG docker jenkins
execute docker build statements from jenkins invoke shell in build steps
push the image built into some repo.
Deployment Part
Login as user in deployment machine & execute docker run for docker deployments
If kubernetes deployment execute kubectl apply commands

From: Sravan-jk<EMAIL_ADDRESS>Sent: 31 October 2018 12:10
To: QT-DevOps/DevOpsIssues
Cc: Subscribed
Subject: [QT-DevOps/DevOpsIssues] Docker Deployment (#252)
Hello all,
please let me know the steps to do a docker deployment on jenkins slave after CI
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/QT-DevOps/DevOpsIssues/issues/252, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACU0reLaq494c8tRzc9J4GNyspbT0dFtks5uqUXigaJpZM4YDcZ9.

@Sravan-jk
Have you done?


Advice for debugging a communication issue when using pyusb

Hi @jonasmalacofilho and @mcuee,
I'm using pyusb in my spectrometer library python-seabreeze and a user reported an issue where communication with a specific spectrometer model via pyusb works on Windows, but fails on Linux.
Another different type of spectrometer works on both of the user's operating systems, so we can rule out some library installation issue.
We have debug logs that were created with LIBUSB_DEBUG=4 and PYUSB_DEBUG=debug from the Linux and the Windows machine. On both machines the pyusb backend is libusb1 and the libusb library version is v<IP_ADDRESS>84
❌    Here is the linux log: https://github.com/ap--/python-seabreeze/issues/133#issuecomment-926065589
✅    And here the windows log: https://github.com/ap--/python-seabreeze/issues/133#issuecomment-926073213
The linux log shows that a timeout occurs when it's trying to read information back after the first command. But I'm out of ideas what the issue could be.
Could you give me some advice how to best proceed with the debugging here?
Thank you so much,
Cheers,
Andreas 😃

I will recommend using wireshark to capture the low level USB traffic. It uses usbmon capability of the Linux kernel. I suspect it to be a kernel USB host controller issue.
https://www.kernel.org/doc/html/latest/usb/usbmon.html

If possible, please ask the user to try a different Linux distribution to see if he can still reproduce the issue or not.
The first post seems to indicate a Raspberry Pi host. In that case, it should be not so difficult to use another Linux distro by popping in another MicroSD card.
https://github.com/ap--/python-seabreeze/issues/133#issue-1001304371

Thank you so much for the quick reply.
So we now have logs for:
❌    Raspberry Pi (I assume running Raspbian) [libusb v<IP_ADDRESS>12]: https://github.com/ap--/python-seabreeze/issues/133#issuecomment-926631864
❌    Virtual Machine with Ubuntu [libusb v<IP_ADDRESS>84]: https://github.com/ap--/python-seabreeze/issues/133#issuecomment-926065589
✅    Windows [libusb v<IP_ADDRESS>84]: https://github.com/ap--/python-seabreeze/issues/133#issuecomment-926073213
And we'll collect a packet capture soon. Is there anything specific we should look out for?
We will also try to increase the read timeout to see if that fixes the issue.
Cheers,
Andreas 😊

We do have packet captures for windows and from the vm now: https://github.com/ap--/python-seabreeze/files/7237325/pcap_files.zip
But I'm not sure what I would need to be looking for specificly.
We also tried to increase the read timeout, but the issue persistet.
Thanks again for your help,
Cheers
Andreas :blush:

Thank you so much for your help @mcuee
I'll go and ask the linux-usb mailing list then.
In the meantime I will close this issue, and report back with whatever I find out.
Thanks again,
Andreas :smiley:


CDC module start/stop procedures

Implement a couple of procedures (as for the sink module) in order to provide an option to pause/resume the CDC module
https://neotechnology.zendesk.com/agent/tickets/11503

@conker84 closeable by previously merged tickets?


ci: [NPM] add bash directive to scale scripts

Reason for Change:
Runs scheduled for master branch have failed since the /bin/sh interpreter does not support double bracket syntax:
./test-scale.sh: 62: [[: not found

Now we explicitly direct these scripts to use /bin/bash.
Requirements:

[x] uses conventional commit messages
[ ] includes documentation
[ ] adds unit tests
[x] relevant PR labels added

/azp run Azure Container Networking PR

/azp run NPM Scale Test

/azp run Azure Container Networking PR

/azp run NPM Scale Test

/azp run NPM Scale Test

First scale test failed since the cluster was no longer reachable


挂载节点名称混乱 磁盘使用信息错误

The new version 3.5+ already supports Apple M1/M2/M3 and other chips.
Sorry for taking so long to update, because before that there was no good way to solve the compatibility problem of the new version of the system.
Fortunately, we have now been authorized by Apple to support the new version of the system kernel, so that we can fully support all macos systems through kernel drivers. Please experience it again, and if you have any questions, please update and communicate.


Discuss content identifiers

Should we use content addressable identifiers (i.e., hash of the content)? What are the privacy implications here if other people may have the same file? Should we consider peppering it prior to hashing?
What about S3 bucket-style key-value naming, so it's possible to address a content by that looks like a path, such as pictures/vacation/island3821.png?
What other approaches exist? Should we support one or many?

@chunningham

IMO deterministic content-addressing is essential for use cases involving crypto assets and commitments. We could encrypt the CID with an OID-derived key such that the content without the orbit is unaddressable, but that may have implications. We can support arbitrary KV naming using something like Textile or IPNS, exactly how this works may be implementation specific (e.g. if S3 is being used, it might be quite a hassle to implement IPLD CAS on top and then use Textile on top of that just to get back to human readable paths). IMO enabling Textile would be a huge value-add and it's possible we could short-circuit some of the complexity (in theory it just means supporting IPLD).

Do you think valid IPLD can be expressed as valid JSON-LD? cc @clehner

it can, all JSON-LD docs are valid json, and DAG-JSON is valid IPLD which can be in the shape of JSON-LD


Enterprise support improvements

Improvements for Github enterprise. Enterprise-specific endpointpatterns are being generated from the github enterprise openapischema.
Thanks @DocEmmetBrown for the contribution and insights!

The go-kit/log dependency was removed. Related to: https://github.com/migueleliasweb/go-github-mock/issues/68.


bug: Cannot close last window

Did you check the docs and existing issues?

[X] I have read the docs
[X] I have searched the existing issues

Neovim version (nvim -v)
0.9.4
Operating system/version
macOS 14.1.1
Describe the bug
Often I get following error when I create a new file and immediately want to open it:
E5108: Error executing lua: ...s/me/.local/share/nvim/lazy/oil.nvim/lua/oil/init.lua:507: Vim:E444: Cannot close last window
stack traceback:
        [C]: in function 'nvim_win_close'
        ...s/me/.local/share/nvim/lazy/oil.nvim/lua/oil/init.lua:507: in function <...s/me/.local/share/nvim/lazy/oil.nvim/lua/oil/init.lua:412>

After that error I have to close nvim completely, otherwise I get this error over and over again in oil.nvim. It looks like that this check https://github.com/stevearc/oil.nvim/blob/05cb8257cb9257144e63f41ccfe5a41ba3d1003c/lua/oil/init.lua#L515 always returns true and thinks that a preview window is open even when that's not the case.
Steps To Reproduce

nvim in any directory
:Oil --float
o (new line + insert mode)
type any filename like foo.ts
ESC
:w to write
o (OK) to create the file
the line with foo.ts is pre selected
Enter to open the file

Now I'm getting this error.
Expected Behavior
Should open the file after I created it.
Directory structure
It doesn't matter. I'm also getting this error at the root directory.
Repro
With the default `repro.lua` the issue is gone. Because I have a lot of plugins and configuration it would take a while. Maybe this is issue is fixable without a `repro.lua`? If not I will try to comment out every single line of my neovim config setup and try to find the collision.

Did you check the bug with a clean config?

[X] I have confirmed that the bug reproduces with nvim -u repro.lua using the repro.lua file above.

It seems that it is somehow related to https://github.com/rmagatti/auto-session wich I'm using to restore previous open sessions in different projects 🤔 When I delete the session for a project oil.nvim works fine as expected until I restore a session.


LLamaLogLevel: ensure numbering matches llama.cpp

LLamaLogLevel appears to be wrong. In C# DEBUG = 1 but in C++ DEBUG = 5.

https://github.com/SciSharp/LLamaSharp/pull/529#issuecomment-1956735043
https://github.com/SciSharp/LLamaSharp/pull/529#issuecomment-1958379875

https://github.com/SciSharp/LLamaSharp/blob/06ffe3ac95389d18a2e8ca87bd5494c479b205c7/LLama/Native/LLamaLogLevel.cs#L6-L27

C++ ref: https://github.com/ggerganov/llama.cpp/blob/7c8bcc11dc61cf5930b70cd0168b84afcebe12a9/ggml.h#L510

Fixed a while ago so I'll close this.