Enhancement Request: Improve HTML Structure and Form Validation

GSSoC Contributor
Description:
I would like to propose enhancements to our contact form page to improve its overall structure, usability, and accessibility. Here are the key changes I suggest:

Semantic HTML: Implement semantic elements (<header>, <nav>, <main>, <footer>) for better organization and accessibility.
CSS Improvements: Centralize styles in a dedicated styles.css file and use CSS variables for color management to enhance maintainability.
Form Validation Enhancements: Improve the validation script to provide more user-friendly error messages and ensure better accessibility with aria-live attributes.
Consistent Styling: Ensure uniform styling for all form elements and buttons for a cohesive user experience.
Error Message Visibility: Implement dynamic error message visibility for better user feedback.

These changes aim to improve user experience and accessibility on our contact page. I have made the changes for the HTML code and would like to contribute if you assign this issue to me.
Thank you

@chikatlarakesh  sure go ahead

Make sure to join the discord server for further communication
Don't forget to star the repository
Complete the task in next 2 days and kindly mention your issue # in your pr like:
Closes #IssueNumber

Note: the level of the issue may change based on the quality of the PR code


All antags are now marked as having an (Unknown) job in the ghost warp menu

Description

This is EXTREMELY ABUSEABLE during a traitor round.
Reproduction

Screenshots

Additional context

i hope all meta-players were banned for a long time for abusing this 🙏

caused by https://github.com/space-wizards/space-station-14/pull/30354

I'll try to fix. 1/2 line change


[Question] Same function call twice in waterfall model

Hi @nwhitmont, I am working on a skype bot in Node.js. I am using waterfall model as shown in below example. This is something question and answer type bot. So when I type 'start', bot gives first question with five answers but if someone types answer two times within a fraction of time (for example~ type 1, press enter ->type 2, press enter) then the next function called twice. Is it possible to restrict the function being called multiple time. Any help would be appreciable.
bot.dialog('start', [
    function (session) {
        buildQuestionsAndOptions(session, session.userData.questionArray[0]);
    },
    function (session, results) {
        buildQuestionsAndOptions(session, session.userData.questionArray[1]);
    },
    function (session, results) {
        buildQuestionsAndOptions(session, session.userData.questionArray[2]);
    }
]);

@ersachit Can you provide the code for your buildQuestionsAnOptions function?

Sure~
function (session, results) {         firebaseOperations.updateLastSentMessageOfPendingFeedback(new Date().getTime(), session.userData.attendeeId,             session.userData.trainingId);         var userAnswer = results.response.entity;         var questionObject = session.userData.questionArray[0];         questionObject.answer = userAnswer;         buildQuestionsAndOptions(session, session.userData.questionArray[1]);     }
function buildQuestionsAndOptions(session, questionObject) {     var question = questionObject.question;     var options = questionObject.options;     var questionsType = questionObject.question_type;     var id = questionObject.id;     if (questionsType === 'choice') {         builder.Prompts.choice(             session,             id + ". " + question,             options,             {                 listStyle: builder.ListStyle.button,                 retryPrompt: i18n.__('retry_prompt')             });     } else if (questionsType === 'text') {         builder.Prompts.text(session, id + ". " + question);     } }

Hey stevengum97, I am using these versions in the application~
node - 6.11.1
botbuilder - 3.9.0
let me know if you required any other information.

Hey @stevengum97, I have also checked the example from here  and it's also giving the same behavior. Like when you would ask to type your name and if we type say "Test" multiple times then the next question "Hi Test, How many years have you been coding?" gets printed multiple time. I am also attaching the screenshot of the same.

Hi @stevengum97 , @nwhitmont ~ any updates on this. Actually, I am looking for the urgent solution to this issue.

What you describe as your problem is expected behavior. You sent multiple messages to the bot, and it responded multiple times. To address this edge-case, you would need to design a custom solution and write the code yourself to handle it.

Hi @nwhitmont, I agree with your point but why the same function is calling again and again as we are following waterfall model so it should call to the next function I believe? Please suggest.

@ersachit I agree with you. Even i am facing problem with water fall model. It asks for same value twice then proceeds for next function.


🔄 Synced file(s) with product-os/jellyfish-config

Synced local file(s) with product-os/jellyfish-config.

This PR was created automatically by the repo-file-sync-action workflow run #1509333853

Already bumped


Version conflict between dependency declaration (AWSSDK.DynamoDBv2) and latest AWS SDK .Net

Description
Please review this previous bug report: https://github.com/aws/aws-dotnet-session-provider/issues/5
The same behavior is happening but with the new latest version.
Since AWS SDK v.<IP_ADDRESS> has been released I can't use latest version of AWS.SessionProvider anymore due to dependency conflict.
Environment

OS Info: Windows 10
Build Environment: Visual Studio Community Edition 2019
Targeted .NET Platform:

.Net 4.7.2
AWS SDK for .NET: SessionProvider 3.3.0
Dependencies: AWSSDK.DynamoDBv2 (>= 3.3.4 && < 3.4.0)

Reproduction Steps

Go to the solution explorer
Right-click on desired project
Go to 'Manage Nuget Packages'
Click on 'Update'

Logs
Unable to find a version of 'AWSSDK.DynamoDBv2' that is compatible with 'AWS.SessionProvider 3.3.0 constraint: AWSSDK.DynamoDBv2 (>= 3.3.4 && < 3.4.0)'.
Resolution
Does it compatible with Core v<IP_ADDRESS>? Could you update dependencies restrictions accordingly?

Hi @jaimeimarin,
Thanks for reporting the issue. I will discuss the issue with the development team and post any update here accordingly.
Regards,
Ashish

Hi @ashishdhingra ,
The same issue. I am trying to update AWSSDK.Core package to version <IP_ADDRESS>. This is required to update AWSSDK.DynamoDBv2 package at least to version <IP_ADDRESS>. But due to error it is impossible: "Unable to resolve dependencies. 'AWSSDK.DynamoDBv2 <IP_ADDRESS>' is not compatible with 'AWS.SessionProvider 3.3.0 constraint: AWSSDK.DynamoDBv2 (>= 3.3.4 && < 3.4.0)'"

This should be resolved in version 4.0 which was released on 11/6/2020. Thanks.


API: Adds sorting_order to Callback

Resolves #54

Essentially, the problem is how to let NeuralNet know about callback sorting order. I don't think that communicating such information through inheritance is the most elegant solution. As an alternative, what do you think about introducing a class attribute? It can have a clean, self-explaining name (e.g. sorting_order), sorting will be simplified to just calling sorted() instead of juggling with class names, and it can support more complicated ordering preferences.
Besides, I believe the name PostponedCallback is quite confusing. When I saw the issue title, I was very curious to check the code and see what a callback with such a name will do.
Finally, most of the changes in this PR reformat the code. (Looks like black formatting is being replaced by yapf formatting.) I think this really calls for introducing official formatting style and tool recommendation.

I forgot to turn off my auto formatter before submitting this PR. 😅
I think having a class attribute is a good idea. For a good balance, I propose letting sorting_order be from 0 to 10. For callbacks that do not care about order, they would have sorting_order=5. The callback order will be ascending, thus higher sorting_orders will be last on the callbacks_ list. What do you think of this idea?

I updated this PR with the sorting_order implementation.

First of all, thanks for tackling this issue.
Before continuing to work on this PR, though, I think we should define what the actual problem is. I have the feeling that otherwise this could lead to over-engineering. Especially because issue #54
in itself is not very well fleshed out.

and it can support more complicated ordering preferences.

I don't think this is necessarily good. What cases should that be? At the moment there is only one relationship that is problematic, namely that there are output callbacks that depend on access to possibly all history values and processing callbacks that write these values. Therefore, processing callbacks need to be executed before output callbacks. And this is scenario is only problematic because we provide some of those by default (e.g., losses and output) and need to merge the default callbacks with a user-supplied list of callbacks while honoring said dependency. For every other, more complicated case, the user can handle the execution of the callbacks by themselves by ordering the list of callbacks manually. Adding another output callback? Just add it to the end. A custom callback depends on a custom score? Just add it to the list after your custom scoring.
It stands to reason if we need to change the current mechanism at all.

two classes vs. numeric ordering

One reason for my proposal of the abstract class to discern between both callback categories was that numeric ordering is very hard to implement in a meaningful way. There is no semantic, only numbers which leads to arbitrary assignments of these numbers and chaos (see also: z-index in CSS). It is easier to have well defined stages that come with an associated name and are matching the specific use-case we want to solve.

I see two  discussion points here: a) numerical vs. binary ordering; b) classes vs. attributes.
Numerical vs. binary ordering

I don't think this is necessarily good. What cases would that be?

Checkpoint callback? Needs to go after default processing callbacks (access to _best column), but before logging callback (writes to event_ column, as discussed in #246).

Numeric ordering is very hard to implement in a meaningful way [...] It is easier to have well defined stages that come with an associated name and are matching the specific use-case we want to solve.

Agree, but we need to come up with such names. How would you classify Checkpoint callback?
Classes vs. attributes
Callbacks already have a hierarchy that is induced by their placement in different source files. I don't think introducing a second (orthogonal) hierarchy via inheritance is a good idea. I still hold that sorting order is better expressed by putting a "tag" on a class.

Checkpoint callback? Needs to go after default processing callbacks (access to _best column), but before logging callback

And this is what is already happening in the current implementation. Default callbacks are prepended (with exception of PrintLog because output), ordered user callbacks are appended and finally PrintLog is added. It is only problematic if you mess up the ordering in the user supplied callback list and add Checkpoint before your own scoring callbacks.

How would you classify Checkpoint callback?

It is not a separate class from my point of view. It is a normal callback as it does not output anything in the sense that PrintLog is outputting something.

I still hold that sorting order is better expressed by putting a "tag" on a class.

I have no strong opinion here, I think tags would work fine. I just don't think that numerical tags are a good idea. If there's an attribute that says that this callback is an output callback, it would be fine as well.

I think adding ordering is important to clean up the following:
https://github.com/dnouri/skorch/blob/64b54e458d53f158ed27744806999a9a5656d4e6/skorch/net.py#L346-L349
Right now it only checks PrintLog because it is one of the default callbacks. The Checkpoint callback should also be called last, but since its not in default callbacks it is not check. From a user point of a view, there are no issues, since self.callbacks are appended at the end. From a code structure point of view, having _yield_callbacks depend on the default callbacks "has a bad code smell".
I agree that having numeric tags may be too flexible. It seems like @taketwo wants to have three levels:

Calculates metrics. (EpochScoring)
Use metrics from 1. and calculates more metrics. (Future Checkpoint)
Log all metrics from 1 and 2. (PrintLog)

We can restrict the tags to three tags, using enum.Enum.

I think an important question here is whether we want to reorder user-supplied callbacks to respect ordering tags (no matter numeric or enum) or not.

Currently, we are already reordering user callbacks, based on class type, PrintLog. If a user was to provide an additional Printlog callback, it will be placed at the end. Reordering callbacks to make sure everything works, sounds like a benefit to me.
Stepping back for a second, this issue stems from wanting to resolve dependencies between callbacks. A full solution would be to have an actual graph that lays out the dependencies between callbacks, but that feels over engineered for this issue. Using an ordered list, with finite levels, provides a simpler solution.
Another solution is to make no changes, and just document that a user must supply the callbacks in an specific order.

+1 this starts to feel most reasonable. As long as the default callbacks have only two types (those that should be strictly first, and those that should be strictly last), ordering of the rest can be done by the user.

Agreed. This is already partially documented in http://skorch.readthedocs.io/en/latest/user/neuralnet.html#callbacks.

Another solution is to make no changes, and just document that a user must supply the callbacks in an specific order.

+1 this starts to feel most reasonable. As long as the default callbacks have only two types (those that should be strictly first, and those that should be strictly last), ordering of the rest can be done by the user.

Agreed. This is already partially documented in http://skorch.readthedocs.io/en/latest/user/neuralnet.html#callbacks.

I also agree. We should postpone further changes to how callbacks are ordered until we notice many users struggling with the current solution.
The only thing the documentation appears to be missing is to mention that all PrintLogs are moved to the end, including user-supplied ones, which is so fringe that I don't even see the need for a change here. We could probably mention that user-supplied order is important in the NeuralNet docstring.
A little bit more meta: Before implementing features like this, it is probably a good idea to pass us a sketch of the intended changes in an issue. That way discussion can happen before code changes that may never be merged (which is why we need contributing guidelines #229).


Update index-filters.blade.php

Targets #{ISSUE_ID}

#865

Description

Added "Email Invoices" button with a modal view input textfield to send the recipient email address.
The requirement is to assist the Finance team with sending invoice emails to the clients on specific dates.
Checklist:

[ ] I have performed a self-review of my own code.

Closing this as it is not being worked on.


PR: LLMWrapper restart, shutdown and supervision

Hey Guys,
Fabian and I fullfilled #2, #17, #18 and #21 therefore the LLMModel class is able to deploy a model, can restart it, perform a shutdown and check the health status periodically. The way multiple / concurrent restart or shutdown requests are handeld is that the wrapper checks the state of the llm and if its already performing a restart or shutdown, it will continue and ignore the new request. @ruppfabian1997 and I would suggest to first reconsider the behaviour after we have merged the interface for registry and prompting service.

Comment from Didi on first PR draft:
If you are trying to make multiple requests at the same time how are you going to split the resource usage between the processes/ prompts?


Fix ext_proc flaky streaming integration test

ext_proc streaming_integration_test is flaky due to:

The test created a test server to be used as the side stream gRPC server.
Based on the logs, a lot of times the gRPC stream between this server and Envoy closed randomly, which leads to the test failure since the tests are not considering these.

Solution:

Changing the failure_mode_allow to true to make sure the messages are still flowing through ext_proc filter even the side stream gRPC channel is down.
extending the timeout value to 2s.
Disable some of the tests which requires the gRPC channel has to be up.

Sometimes, the autonomous fake upstream also leads to flaky test failure during test shutdown and d'tor of autonomous_upstream. The long term solution to avoid the flakiness and re-enable the above tests is converting stream_integration_test to not use test server and autonomous upstream. Instead,  just using normal fake upstream as what is used in ext_proc_integration_test.cc.  Or maybe even simpler, just convert these into unit tests and put them into filter_test.cc.

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/assign-from @envoyproxy/envoy-maintainers

@yanavlasov could you take a look since this is potentially blocking the release?

There is one more flaky issue here: sometimes, an ext_proc server response somehow is sent to the Envoy listener port, which trigger the ext_proc filter decodeHeader()/decodeData() code get called again unexpectedly, and cause the test failure.  I am still trying to understand how this happened.   The happens pretty rare based on my local test tries.

There is one more flaky issue here ... The happens pretty rare based on my local test tries.

so my reading of current pr is that its its fairly assuredly an improvement and should be good to land - currently this is one of the only remaining release blockers
if remaining issues are known (and esp if we resolve quickly) then it should be easy to backport any fixes, happy to help there
tldr - lets land unless we think this will worsen the situation

[ RUN      ] StreamingProtocols/StreamingIntegrationTest.PostAndProcessBufferedRequestBody/IPv4_GoogleGrpc_NoDeferredProcessing
[2023-10-18 04:32:59.387][12][info][testing] [test/integration/fake_upstream.cc:665] starting fake server at <IP_ADDRESS>:36013. UDP=false codec=http2
[2023-10-18 04:32:59.388][12][debug][misc] [test/integration/base_integration_test.cc:194] Setting up file-based LDS
[2023-10-18 04:32:59.391][12][debug][misc] [test/config/utility.cc:1045] Not overriding preset port
[2023-10-18 04:32:59.404][12][debug][misc] [test/integration/base_integration_test.cc:236] Running Envoy with configuration:
static_resources:
...
[2023-10-18 04:32:59.540][337][info][main] [source/server/server.cc:942] starting main dispatch loop
[2023-10-18 04:32:59.551][12][debug][testing] [test/integration/base_integration_test.cc:418] registered 'http' as port 34783.    <<<<<< 34783 is the listener port
[2023-10-18 04:32:59.586][341][trace][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:420] decodeData(1000): end_stream = false
[2023-10-18 04:32:59.586][341][trace][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:300] onData: Buffering
[2023-10-18 04:32:59.586][341][trace][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:422] decodeData returning 1
[2023-10-18 04:32:59.586][341][trace][http] [source/common/http/filter_manager.cc:704] [Tags: "ConnectionId":"47","StreamId":"4634651194543927278"] decode data called: filter=envoy.filters.http.ext_proc status=1
[2023-10-18 04:32:59.586][341][trace][http2] [source/common/http/http2/codec_impl.cc:1061] [Tags: "ConnectionId":"47"] about to recv frame type=0, flags=0, stream_id=1
[2023-10-18 04:32:59.586][341][trace][http2] [source/common/http/http2/codec_impl.cc:1087] [Tags: "ConnectionId":"47"] recv frame type=0
[2023-10-18 04:32:59.586][341][trace][http2] [source/common/http/http2/codec_impl.cc:2138] [Tags: "ConnectionId":"47"] track inbound frame type=0 flags=0 length=1000 padding_length=0
[2023-10-18 04:32:59.586][341][trace][misc] [source/common/event/scaled_range_timer_manager_impl.cc:60] enableTimer called on 0x25feff532fc0 for 300000ms, min is 300000ms
[2023-10-18 04:32:59.586][341][trace][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:420] decodeData(1000): end_stream = false
[2023-10-18 04:32:59.586][341][trace][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:300] onData: Buffering
[2023-10-18 04:32:59.586][341][trace][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:422] decodeData returning 1
[2023-10-18 04:32:59.586][341][trace][http] [source/common/http/filter_manager.cc:704] [Tags: "ConnectionId":"47","StreamId":"4634651194543927278"] decode data called: filter=envoy.filters.http.ext_proc status=1
[2023-10-18 04:32:59.586][341][trace][http2] [source/common/http/http2/codec_impl.cc:989] [Tags: "ConnectionId":"47"] dispatched 16144 bytes
[2023-10-18 04:32:59.586][341][trace][connection] [source/common/network/connection_impl.cc:614] [Tags: "ConnectionId":"47"] socket event: 3
[2023-10-18 04:32:59.586][341][trace][connection] [source/common/network/connection_impl.cc:737] [Tags: "ConnectionId":"47"] write ready
[2023-10-18 04:32:59.586][341][trace][connection] [source/common/network/connection_impl.cc:654] [Tags: "ConnectionId":"47"] read ready. dispatch_buffered_data=0
[2023-10-18 04:32:59.587][341][trace][connection] [source/common/network/raw_buffer_socket.cc:25] [Tags: "ConnectionId":"47"] read returns: 9
[2023-10-18 04:32:59.587][341][trace][connection] [source/common/network/raw_buffer_socket.cc:39] [Tags: "ConnectionId":"47"] read error: Resource temporarily unavailable, code: 0
[2023-10-18 04:32:59.587][341][trace][http2] [source/common/http/http2/codec_impl.cc:954] [Tags: "ConnectionId":"47"] dispatching 9 bytes
[2023-10-18 04:32:59.587][341][trace][http2] [source/common/http/http2/codec_impl.cc:1061] [Tags: "ConnectionId":"47"] about to recv frame type=0, flags=1, stream_id=1
[2023-10-18 04:32:59.587][341][trace][http2] [source/common/http/http2/codec_impl.cc:1087] [Tags: "ConnectionId":"47"] recv frame type=0
[2023-10-18 04:32:59.587][341][trace][http2] [source/common/http/http2/codec_impl.cc:2138] [Tags: "ConnectionId":"47"] track inbound frame type=0 flags=1 length=0 padding_length=0
[2023-10-18 04:32:59.587][341][debug][http] [source/common/http/conn_manager_impl.cc:1177] [Tags: "ConnectionId":"47","StreamId":"4634651194543927278"] request end stream
[2023-10-18 04:32:59.587][341][trace][misc] [source/common/event/scaled_range_timer_manager_impl.cc:60] enableTimer called on 0x25feff532fc0 for 300000ms, min is 300000ms
[2023-10-18 04:32:59.587][341][trace][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:420] decodeData(0): end_stream = true
[2023-10-18 04:32:59.587][341][debug][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:290] Sending request body message
[2023-10-18 04:32:59.587][341][debug][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:538] Sending a body chunk of 99000 bytes, end_stram true
[2023-10-18 04:32:59.587][341][debug][ext_proc] [source/extensions/filters/http/ext_proc/processor_state.cc:30] Traffic direction INBOUND: 2000 ms timer enabled
[2023-10-18 04:32:59.587][341][trace][grpc] [source/common/grpc/google_async_client_impl.cc:233] Queued message to write (99010 bytes)
[2023-10-18 04:32:59.587][341][trace][grpc] [source/common/grpc/google_async_client_impl.cc:276] Write op dispatched
[2023-10-18 04:32:59.587][341][trace][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:422] decodeData returning 3
[2023-10-18 04:32:59.587][341][trace][http] [source/common/http/filter_manager.cc:704] [Tags: "ConnectionId":"47","StreamId":"4634651194543927278"] decode data called: filter=envoy.filters.http.ext_proc status=3
[2023-10-18 04:32:59.587][342][trace][grpc] [source/common/grpc/google_async_client_impl.cc:61] completionThread CQ event 3 true
[2023-10-18 04:32:59.587][341][trace][http2] [source/common/http/http2/codec_impl.cc:989] [Tags: "ConnectionId":"47"] dispatched 9 bytes
[2023-10-18 04:32:59.587][341][trace][connection] [source/common/network/connection_impl.cc:614] [Tags: "ConnectionId":"48"] socket event: 3
[2023-10-18 04:32:59.587][341][trace][connection] [source/common/network/connection_impl.cc:737] [Tags: "ConnectionId":"48"] write ready
[2023-10-18 04:32:59.587][341][trace][connection] [source/common/network/connection_impl.cc:654] [Tags: "ConnectionId":"48"] read ready. dispatch_buffered_data=0
[2023-10-18 04:32:59.587][341][trace][connection] [source/common/network/raw_buffer_socket.cc:25] [Tags: "ConnectionId":"48"] read returns: 510
[2023-10-18 04:32:59.587][341][trace][connection] [source/common/network/raw_buffer_socket.cc:39] [Tags: "ConnectionId":"48"] read error: Resource temporarily unavailable, code: 0
[2023-10-18 04:32:59.587][341][trace][http2] [source/common/http/http2/codec_impl.cc:954] [Tags: "ConnectionId":"48"] dispatching 510 bytes
[2023-10-18 04:32:59.587][341][trace][http2] [source/common/http/http2/codec_impl.cc:1061] [Tags: "ConnectionId":"48"] about to recv frame type=4, flags=1, stream_id=0
[2023-10-18 04:32:59.587][341][trace][http2] [source/common/http/http2/codec_impl.cc:2138] [Tags: "ConnectionId":"48"] track inbound frame type=4 flags=1 length=0 padding_length=0
[2023-10-18 04:32:59.587][341][trace][http2] [source/common/http/http2/codec_impl.cc:1087] [Tags: "ConnectionId":"48"] recv frame type=4
[2023-10-18 04:32:59.587][341][trace][http2] [source/common/http/http2/codec_impl.cc:1061] [Tags: "ConnectionId":"48"] about to recv frame type=1, flags=4, stream_id=1
[2023-10-18 04:32:59.587][341][trace][http2] [source/common/http/http2/codec_impl.cc:2138] [Tags: "ConnectionId":"48"] track inbound frame type=1 flags=4 length=289 padding_length=0
[2023-10-18 04:32:59.588][341][debug][http] [source/common/http/conn_manager_impl.cc:391] [Tags: "ConnectionId":"48"] new stream
[2023-10-18 04:32:59.588][341][trace][misc] [source/common/event/scaled_range_timer_manager_impl.cc:60] enableTimer called on 0x25feff53f180 for 300000ms, min is 300000ms
[2023-10-18 04:32:59.588][341][trace][http2] [source/common/http/http2/codec_impl.cc:1087] [Tags: "ConnectionId":"48"] recv frame type=1
[2023-10-18 04:32:59.588][341][debug][http] [source/common/http/conn_manager_impl.cc:1194] [Tags: "ConnectionId":"48","StreamId":"3222402010705002608"] request headers complete (end_stream=false):
':path', '/envoy.service.ext_proc.v3.ExternalProcessor/Process'
':authority', '<IP_ADDRESS>:34783'
':method', 'POST'
':scheme', 'http'
'content-type', 'application/grpc'
'te', 'trailers'
'grpc-accept-encoding', 'identity, deflate, gzip'
'user-agent', 'grpc-c++/1.56.2 grpc-c/33.0.0 (linux; chttp2)'
'x-request-id', 'ac11bbc7-5c95-4364-8ec0-fafbe03c4f46'
[2023-10-18 04:32:59.588][341][debug][connection] [./source/common/network/connection_impl.h:98] [Tags: "ConnectionId":"48"] current connecting state: false
[2023-10-18 04:32:59.588][342][trace][grpc] [source/common/grpc/google_async_client_impl.cc:61] completionThread CQ event 2 true
[2023-10-18 04:32:59.588][341][trace][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:232] decodeHeaders: end_stream = false
[2023-10-18 04:32:59.588][341][debug][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:162] Opening gRPC stream to external processor
[2023-10-18 04:32:59.589][342][trace][grpc] [source/common/grpc/google_async_client_impl.cc:61] completionThread CQ event 0 true
[2023-10-18 04:32:59.589][341][debug][ext_proc] [source/extensions/filters/http/ext_proc/processor_state.cc:30] Traffic direction INBOUND: 2000 ms timer enabled
[2023-10-18 04:32:59.589][341][debug][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:224] Sending headers message
[2023-10-18 04:32:59.589][341][trace][grpc] [source/common/grpc/google_async_client_impl.cc:233] Queued message to write (375 bytes)
[2023-10-18 04:32:59.589][341][trace][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:244] decodeHeaders returning 1
[2023-10-18 04:32:59.589][341][trace][http] [source/common/http/filter_manager.cc:572] [Tags: "ConnectionId":"48","StreamId":"3222402010705002608"] decode headers called: filter=envoy.filters.http.ext_proc status=1
[2023-10-18 04:32:59.589][341][trace][misc] [source/common/event/scaled_range_timer_manager_impl.cc:60] enableTimer called on 0x25feff53f180 for 300000ms, min is 300000ms
[2023-10-18 04:32:59.589][341][trace][http2] [source/common/http/http2/codec_impl.cc:1061] [Tags: "ConnectionId":"48"] about to recv frame type=0, flags=0, stream_id=1
[2023-10-18 04:32:59.589][341][trace][http2] [source/common/http/http2/codec_impl.cc:1087] [Tags: "ConnectionId":"48"] recv frame type=0
[2023-10-18 04:32:59.589][341][trace][http2] [source/common/http/http2/codec_impl.cc:2138] [Tags: "ConnectionId":"48"] track inbound frame type=0 flags=0 length=194 padding_length=0
[2023-10-18 04:32:59.589][341][trace][misc] [source/common/event/scaled_range_timer_manager_impl.cc:60] enableTimer called on 0x25feff53f180 for 300000ms, min is 300000ms
[2023-10-18 04:32:59.589][341][trace][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:420] decodeData(194): end_stream = false
[2023-10-18 04:32:59.589][341][trace][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:263] Header processing still in progress -- holding body data
[2023-10-18 04:32:59.589][341][debug][ext_proc] [source/extensions/filters/http/ext_proc/processor_state.cc:400] Watermark raised on decoding
....
[2023-10-18 04:33:01.601][341][trace][main] [source/common/event/dispatcher_impl.cc:124] clearing deferred deletion list (size=2)
test/extensions/filters/http/ext_proc/streaming_integration_test.cc:232: Failure
Expected equality of these values:
body_req.request_body().body().size()
Which is: 194
total_size
Which is: 99000
Stack trace:
0x2124710: Envoy::Extensions::HttpFilters::ExternalProcessing::StreamingIntegrationTest_PostAndProcessBufferedRequestBody_Test::TestBody()::$_3::operator()()
0x2123db2: std::__invoke_impl<>()
0x2123d42: std::__invoke_r<>()
0x2123c32: std::_Function_handler<>::_M_invoke()
0x220a865: std::function<>::operator()()
0x220a39b: Envoy::Extensions::HttpFilters::ExternalProcessing::ProcessorWrapper::Process()
0x220c028: envoy::service::ext_proc::v3::ExternalProcessor::Service::Service()::$_0::operator()()
0x220bfd5: std::__invoke_impl<>()
0x220bf1f: std::__invoke_r<>()
0x220bddf: std::_Function_handler<>::_M_invoke()
0x221ec42: std::function<>::operator()()
0x221eb97: grpc::internal::BidiStreamingHandler<>::BidiStreamingHandler()::{lambda()#1}::operator()()
0x221eb3d: std::__invoke_impl<>()
0x221eaaa: std::__invoke_r<>()
0x221e85a: std::_Function_handler<>::_M_invoke()
0x222080d: std::function<>::operator()()
0x2220786: grpc::internal::TemplatedBidiStreamingHandler<>::RunHandler()::{lambda()#1}::operator()()
0x221f0d4: grpc::internal::CatchingFunctionHandler<>()
0x221e37f: grpc::internal::TemplatedBidiStreamingHandler<>::RunHandler()
0x326f11a: grpc::Server::SyncRequest::ContinueRunAfterInterception()
0x326ece2: grpc::Server::SyncRequest::Run()
0x326e7f3: grpc::Server::SyncRequestThreadManager::DoWork()
0x3291cf0: grpc::ThreadManager::MainWorkLoop()
0x3291a0c: grpc::ThreadManager::WorkerThread::Run()
0x3292689: grpc::ThreadManager::WorkerThread::WorkerThread()::$_0::operator()()
0x3292665: grpc::ThreadManager::WorkerThread::WorkerThread()::$_0::__invoke()
0x3a0b315: grpc_core::(anonymous namespace)::ThreadInternalsPosix::ThreadInternalsPosix()::{lambda()#1}::operator()()
0x3a0b1e5: grpc_core::(anonymous namespace)::ThreadInternalsPosix::ThreadInternalsPosix()::{lambda()#1}::__invoke()
0x7fb6318293ec: (unknown)
[2023-10-18 04:33:03.206][12][debug][init] [source/common/init/watcher_impl.cc:31] init manager RTDS destroyed

There is one more flaky issue here ... The happens pretty rare based on my local test tries.

so my reading of current pr is that its its fairly assuredly an improvement and should be good to land - currently this is one of the only remaining release blockers
if remaining issues are known (and esp if we resolve quickly) then it should be easy to backport any fixes, happy to help there
tldr - lets land unless we think this will worsen the situation

I think with this change, the flakiness went down to 0.1% based on my local test: runs_per_test  = 1000.  We can land it first then take time to root cause the  above issue.   In the worst case, we can completely disable the test target of streaming_integration_test.  There are significant amount of STREAMED mode tests added in filter_test.cc recently, which give us pretty good coverage there.


Add logging functionality

logs should be written to a file with the connect and disconnect as events and client ip and timestamps as data


New layers image for introduction (from Audrey)

🚀 Deployed on https://6531cbe857cce929ca144918--cozy-fox-0defec.netlify.app


all: unset

Reset all CSS properties. Will be available in January 2014 in Firefox 27.
http://tanalin.com/blog/2013/10/css-unset/

Implemented in Social Likes Next.


Move to pyproject.toml, set up renovate

This moves from setup.py and various requirements files to a single pyproject.toml, which is The Future. It also sets up renovate so we can automatically get version updates.

I dislike not being able to declare the "all" extra as a sum of all other ones.


Can not bind micro api to 80 port ?

Hi !
Tried to use the go-micro directly over network, but it seems like it dislikes the default port 80 for the HTTP.
[ec2-user bin]$ ./micro api --handler=api --address=<IP_ADDRESS>:80
2019-12-11 07:58:01.846903 I | [api] Registering API Request Handler at /
2019-12-11 07:58:01.847164 I | [api] listen tcp <IP_ADDRESS>:80: bind: permission denied

Is this a bug ?
Thanks in advance !

You cannot bind to any port below 1000 without root privilege. This is not micro specific.


Added set_spark_home_env_var()

It's useful for users to be able to set the SPARK_HOME environment variable without having to hunt for where it is.

Thank you @richierocks! A few minor comments inline, but otherwise looking good!

Nice, thank you @richierocks! Merging...


Translation function compatible for 2D and 3D

Fixing data format problem causing error in translation function after transfer to 2/3D compatible format.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@9ff909d). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #27   +/-   ##
=========================================
  Coverage          ?   18.45%
=========================================
  Files             ?       12
  Lines             ?      298
  Branches          ?        0
=========================================
  Hits              ?       55
  Misses            ?      243
  Partials          ?        0

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9ff909d...04a4fa2. Read the comment docs.

One last tip, after merging you can delete the branch. Otherwise https://github.com/jona125/REALMSupport.jl/branches/active will fill up.

Sorry for my long delay in getting back to this package. I have a question about https://github.com/jona125/REALMSupport.jl/blob/424f4d5bfaadcc16652df3c7b2993aabfca29bb0/src/translation.jl#L36: am I right in understanding that the final dimension of mm is actually the stack index? Is that something you should really be interpolating over?
Since the first three dimensions are continuous but the "which image volume did I collect?" index is not really continuous (some will translate x, others y, others z), I might consider making this a list-of-volumes rather than a 4d array of volumes. If you'd be OK with that change I could make it, or allow you to do so yourself. Just let me know what you prefer.
And if I'm just confused about this, don't hesitate to straighten me out.


[FR] Allow extensions to show images inline

Per this question, it's not possible to make a vscode extension that adds inline preview for images to markdown files, like this:

Duplicate of #85682


Update Yara/Go/Action versions; pin Actions to digests

I'm all for upgrading to higher versions, but I don't understand why one would want to use digests for these actions.
Are you worried that actions/checkout and actions/setup-go might be tampered with malicious actors?

Are you worried that actions/checkout and actions/setup-go might be tampered with by malicious actors?

Yep, exactly -- it's not super critical but I figured that I'd offer the suggestion. Totally up to you!


manager: only sync label when label key exists

Ⅰ. Describe what this PR does

Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist

[ ] I have written necessary docs and comments
[ ] I have added necessary unit tests and integration tests
[ ] All checks passed in make test

/lgtm


Does Rubocop provide a basic stats?

Is your feature request related to a problem? Please describe.
I'm always thinking about what needs to be fixed first so basic stats would be very helpful
Describe the solution you'd like
I found the python script that done something similar but would be nice to see it as a flag like --stats
Example output:
spec/services/notify_researcher_service_spec.rb
└─┬ TotalOffenses: 16
  ├── RSpec/NestedGroups: 12
  ├── RSpec/ContextWording: 2
  └── RSpec/RepeatedExampleGroupDescription: 2

app/services/reports_service.rb
└─┬ TotalOffenses: 12
  ├── Metrics/AbcSize: 4
  ├── Metrics/CyclomaticComplexity: 4
  ├── Style/MultilineIfModifier: 2
  ├── Metrics/ClassLength: 1
  └── Metrics/PerceivedComplexity: 1

No, it doesn't, but this seems like a cool idea.

I didn't quite get the benefits of this.
Can you, please, elaborate more (provide an example(-s)) on how knowing this info can help in fixing offenses?

I didn't quite get the benefits of this.
Can you, please, elaborate more (provide an example(-s)) on how knowing this info can help in fixing offenses?

I would say that each time when I add Rubocop to an existing project, I want to know what needs to be fixed/disabled first.
So it will be nice to see the stats before I do any changes.
having additional -s/--stats argument sounds good

I want to know what needs to be fixed/disabled first.

So why does the order matters if you should have all the offenses fixed/disabled at the end anyway? 🤔

So why does the order matters if you should have all the offenses fixed/disabled at the end anyway? 🤔

Well, there are always priorities like 100+ offenses vs 1 offense. I'll focus on the first one and the second can be disabled

I've faced this recently (new project, starting without .rubocop). A list of the different cops involved would have been nice, as I wanted to handle each in turn.

I'm guessing --stats can just be a different formatter, as that would fit naturally in RuboCop's current architecture.

@marcandre I understood your use case, I was thinking about something similar. But in your case, compared to OP's original request, looks like files should be replaced with cop names?
Something like this
Metrics/AbcSize
└─┬ TotalOffenses: 16
  ├── some/path/to/file.rb: 12
  ├── another/file.rb: 2
  └── yet_another_file.rb: 2

?

I completely misread the request 🤦♂
I'm not even sure I'd want the paths 😅
Metrics: 20
└─┬─ Metrics/AbcSize: 16
  └─ Metrics/MethodLength: 4

Or with paths and grouped as you proposed, that works too.
It seems to me that offenses are best handled one kind at a time, not one path at a time.

I love your example 👍 I'm not seeing much value in the paths.
If no one would think about implementing this, I can implement it by the end of the week.

Just found. Won't this be enough https://github.com/rubocop-hq/rubocop/blob/master/lib/rubocop/formatter/offense_count_formatter.rb ?
Example output:
 111/111 files |=========================================================== 100 ============================================================>| Time: 00:00:00

44  Metrics/MethodLength
4   Layout/HashAlignment
4   Metrics/ClassLength
2   Style/IfUnlessModifier
--
54  Total

Just found. Won't this be enough https://github.com/rubocop-hq/rubocop/blob/master/lib/rubocop/formatter/offense_count_formatter.rb ?
Example output:
 111/111 files |=========================================================== 100 ============================================================>| Time: 00:00:00

44  Metrics/MethodLength
4   Layout/HashAlignment
4   Metrics/ClassLength
2   Style/IfUnlessModifier
--
54  Total

wow, this is exactly what I was looking for rubocop --format offenses 🥳
If you guys don't mind, I'll go ahead and lose this issue


Startup performance

We have a large monorepo (50+ Maven projects). We want to use VS Code dev containers for local development, but it takes forever to start up (i.e., import projects, etc.).
For context, our laptops are running Windows 11 and we're using Podman Desktop with WSL as the container host. We are using volumes rather than the default bind mount, which has improved performance. We are building the images locally which also decreases the time it takes to create or rebuild a dev container.
On a fresh volume the initial import takes a very long time. Maybe 2 hours? Just a guess. Reloading the window or rebuilding the container also takes a long time. Maybe 30 minutes - 1 hour?
Is this expected? Is there anything we can do to improve performance?

Is it a single Maven project with 50+ sub-modules?
Do you need to open all those modules together, or you just need to use some of them for development?

Is it a single Maven project with 50+ sub-modules?

No submodules. Every project has it's own pom. It's roughly half services and half libraries.

Do you need to open all those modules together, or you just need to use some of them for development?

Ideally they are all opened together.

If all the projects are required to open in vscode. Maybe you can try to turn off the auto build. The side effect is that, if you turn off the auto build, you may not be able to find some errors at the first time. You need manually trigger build on demand.
The setting is java.autobuild.enabled

What about java.maxConcurrentBuilds? I see the default value is 1. I changed the value to 4. The change seems to have increased how quickly building occurs, but does it only apply to building (i.e., not importing, etc.). If so, is there any way to increase the number of concurrent imports and refreshes etc.?

java.maxConcurrentBuilds can boost the build time.
Meanwhile, you can increase the JVM memory via the setting java.jdt.ls.vmargs, which should help with the perf as well.


✂`🥢  Ecrec snips n' nits

Description
Suggestions as snips and nits to save gas() in various ecrecover functions. Security comments useful obv. I'm just snippin` over here.
Checklist
Ensure you completed all of the steps below before submitting your pull request:

[x] Ran forge fmt?
[x] Ran forge snapshot?
[x] Ran forge test?

Pull requests with an incomplete checklist will be thrown out.

@z0r0z  good catch. I will not recommend changes because it is save very tiny amount of gas(around 20-25), it poses a security risk.Let's consider a hypothetical example of a contract that uses Solady's ECDSA library and a storage mapping of signature hashes. (please ignore nonce protection for this contract)
import {ECDSA} from "solady/utils/ECDSA.sol";

contract Signature {
          mapping (bytes32 sigHash => bool used) public signs;

          function name1(bytes memory signature) public {

                   // checking signature is not used
                  require(!signs[keccak256(signature)], "already used");

                  // do some stuff

                 // assume ECDSA is solady  lib
                ECDSA.recover(msgHash, signature);

                signs[keccak256(signature)] = true;
          }
}

In the above given contract where an attacker can append random data to the end of a valid signature.
@Vectorized what you think about this?

Thanks for checking this out @atarapra ~~ I def appreciate the subtle way the library distinguishes between EIP- 2098 compact signatures and ordinary 65 byte-length ones with that check (and the return (1) as ecrecover dest is cool), but I think there might not be a problem as far as security goes, thankfully, because if users provide more bytes than expected, those are simply ignored and not passed into the 128 bytes sent into ecrecover staticcall? For sure respect mind towards security, but I guess if Solady doesn't enforce 64 bytes in EIP-2098 case, why enforce in 65 bytes vanilla case?  🚬 👓 💭  Maybe we add a comment putting it on users to ensure extra bytes don't get used by their smart contract in a weird way, but it might be ok overall as this function just recovers and cleans context after.

@z0r0z for EIP2098 signature types there are separate function and it's enforcing 64 bytes in two separate parameters. Putting comments is fine but most off time dev didn't read comments. Currently solady has too much comments for these type of common mistake.

I'll leave the check in.
EIP-2098 is implemented via the (r,sv) variant.

fair, but what do ya think of first nit @Vectorized: https://github.com/Vectorized/solady/pull/625/commits/02e181027fea5f98e30616f8fa31ca79e82a75bd
lowers gas and codesize so looks legit to me

@atarapra @z0r0z
https://github.com/Vectorized/solady/blob/main/audits/cantina-solady-report.pdf
Scroll down to see 4.2.3: ECDSA: Empty signature can result in valid recovered address.
Finding by @Philogy.

Most likely won't merge, but leaving open for some time.

@Vectorized This PR first commit is valid for saving gas. @z0r0z could revert all other changes and we good to go.


Is there a way to set the request header limitation?

I lunched the node express on my localhost:3000..
http://localhost:3000
curl -H 'samlresponse:12323' -v http://localhost:3000 , this command line works fine.
but if I tried following...
curl -H 'samlresponse:{here is the entire samlresponse, it's very long..}' -v http://localhost:3000 , the server always return "Empty reply from server", is there a way to passby or fix this issue?

We won't be able to find out the cause without looking at the source code.
Please post general queries, such as this one, at https://gitter.im/expressjs/express.

I tried to replicate the issue, i don't know if you send the samlresponse like you wrote, but in this case the problem is with the quotation mark in "it's"

https://github.com/nodejs/node/blob/master/deps/http_parser/http_parser.h
/* Maximium header size allowed. If the macro is not defined

before including this header then the default is used. To
change the maximum header size, define the macro in the build
environment (e.g. -DHTTP_MAX_HEADER_SIZE=). To remove
the effective limit on the size of the header, define the macro
to a very large number (e.g. -DHTTP_MAX_HEADER_SIZE=0x7fffffff)
*/
#ifndef HTTP_MAX_HEADER_SIZE

define HTTP_MAX_HEADER_SIZE (80*1024)
#endif


url's missing geography prefix

Data Plane API - Pull Request

API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.

Link to API Spec engagement record issue:

Is this review for (select one):

[ ] a private preview
[ ] a public preview
[ ] GA release

Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified. Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.

Design Document:
Previous API Spec Doc:
Updated paths:

❔Got questions? Need additional info?? We are here to help!

 Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

💬 Teams Channel
💌 email

Click here for links to tools, specs, guidelines & other good stuff
Tooling

Open API validation tools were run on this PR. Go here to see how to fix errors
Spectral Linting
Open API Hub

Guidelines & Specifications

Azure REST API Guidelines
OpenAPI Style Guidelines
Azure Breaking Change Policy

Helpful Links

Azure DevTools Wiki

@jhendrixMSFT I am not sure about the Swagger breaking change error. It was first flagged after the first push, even though my change was unrelated. I then tried to address it by modeling it after an existing API (see "Avoids" in Microsoft.Maps\Route\preview\1.0\route.json) with a similar bitmask\flags enum but it didn't make a difference.
As I am running out of options\clues, I'd appreciate some guidance to expedite the publishing of this fix. thanks!

@jhendrixMSFT can we move forward with merging into main?


Need Multicall contract on Optimistic network

To add support to the Optimistic network we need a Multicall contract to be deployed on their network
There is already multicall deployed in Optimism, as mentioned in docs: 0x90f872b3d8f33f305e0250db6a2761b354f7710a  the method is almost the same as MakerDAO's multicall but the names are different multicall  instead of aggregate
we need something like these :
https://github.com/makerdao/multicall
https://etherscan.io/address/0xeefba1e63905ef1d7acba5a8513c70307c1ce441#code

@ChaituVR so I just need to copy paste the contract and deploy it to Optimistic Network?

@ChaituVR should I use MultiCall2 or Multicall?
As you can see they forked Optimistic network forked Multicall2

It doesnt look like Optimistic deployment would be done any soon due to issues with contract deployments on optimistic kovan

I tried to deploy multicall to optimistic kovan but I am getting few errors:
ParserError: OVM: BLOCKHASH is not implemented in the OVM.
Same error for BALANCE, DIFFICULTY, and COINBASE
https://community.optimism.io/docs/protocol/evm-comparison.html
we can ignore others but balance is used by eth-balance strategy

https://optimistic.etherscan.io/address/0x35A6Cdb2C9AD4a45112df4a04147EB07dFA01aB7#code
This one is working well


Permission problem when launching webui.py

folder permission is set to 100 resulting in permission problem loading ./extensions/PromptGallery-stable-diffusion-webui/index.html when starting up webui.py. Permission always seem to reset on launching webui.py. This is the only extension that has this problem. Workaround is to suspend webui.py after message of permission problem starts flooding the screen, and do a chmod 755 on /extensions/PromptGallery-stable-diffusion-webui
Issue seen on WSL2-Ubuntu22.04

Removed permission change.

still same for me

@Lalimec @martianunlimited It should be ok now. I forgot to push the change.

Please reopen if it still happended.

Still happening for me on the latest commit. I commented out this line:
https://github.com/dr413677671/PromptGallery-stable-diffusion-webui/blob/f2375cfa241ca2bb473e6422a90c7262cca1eb0e/scripts/prompt_gallery.py#L36
This fixed the issue for me. Not sure why there is even a need to change any permissions?

I'm having this same problem. The permission on the folder extensions/PromptGallery-stable-diffusion-webui is changed. I have to go into the Finder and give myself read and write permissions on it.

I wanted to give this a try, but I had the same problem. I tried removing and then reinstalling but the problem persists. Looking through scripts/prompt_gallery.py, I can't find anything setting permissions. Even with the workaround, this makes the extension very difficult to deal with.

Pulled the latest version today. This is still happening. I'm going to disable Prompt Gallery until this is fixed.

@jbnv @jpidelatorre @h-sahin
I commented line 36 as h-sahin suggested. Could please you try?
The purpose of line 36 is to solve some corner case when some user have a readonly file system and the extension could not generate preview file in the folder.


let vs2019 execute new terminal

find Microsoft.VisualStudio.ProjectSystem.VS.Implementation.ni.dll
use winhex .
replace "cmd.exe" to "wt.exe "
"%s /c ""%s" %s & pause"" to "      ""%s" %s        ""

find your wt.exe path

use mklink

ok.ctrl+f5 build and run console

I'm sorry, is there a question here?
It's definitely clever to do this hack to get VS to open in Windows Terminal instead of conhost (the vintage console).
I think as a broader solution, we're working on #492, which will allow users to set a "default terminal emulator" on windows, and have the OS automatically open new commandline applications in Windows Terminal.
There doesn't really seem like anything actionable here, so I'm gonna close this issue. Thanks!


Getting error: pattern does not mention field is_dir

As of half an hour ago, I'm getting this error in the 6.4.2 version of rust-embed. This is not happening on the newest version 6.5.0, but the 6.4.2 was also working yesterday and an existing version randomly breaking is pretty weird.
Full stacktrace:
error[E0027]: pattern does not mention field `is_dir`
  --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/rust-embed-impl-6.3.1/src/lib.rs:20:7
   |
20 |   for rust_embed_utils::FileEntry { rel_path, full_canonical_path } in rust_embed_utils::get_files(folder_path, &includes, &excludes) {
   |       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ missing field `is_dir`
   |
help: include the missing field in the pattern
   |
20 |   for rust_embed_utils::FileEntry { rel_path, full_canonical_path, is_dir } in rust_embed_utils::get_files(folder_path, &includes, &excludes) {
   |                                                                  ~~~~~~~~~~
help: if you don't care about this missing field, you can explicitly ignore it
   |
20 |   for rust_embed_utils::FileEntry { rel_path, full_canonical_path, .. } in rust_embed_utils::get_files(folder_path, &includes, &excludes) {
   |                                                                  ~~~~~~

For more information about this error, try `rustc --explain E0027`.
error: could not compile `rust-embed-impl` due to previous error

Will be yanking 6.5.0, impl - 6.4.0 and utils 7.4.0 now so that we can address this issue https://github.com/pyrossh/rust-embed/issues/196 as well.
And reverting all changes to make it stable again.

@jaztec I updated all the versions and then published so that couldn't have happened. It seems like rust-embed-utils got updated to v7.4.0  by cargo and is conflicting with the other packages.  @askonomm what version was the rust-embed-utils crate if you remember. I don't think its possible to recreate it now though.

@jaztec I updated all the versions and then published so that couldn't have happened. It seems like rust-embed-utils got updated to v7.4.0 by cargo and is conflicting with the other packages. @askonomm what version was the rust-embed-utils crate if you remember. I don't think its possible to recreate it now though.

Unfortunately I don't remember, and can't check anymore as I've already updated to 6.5 which works just fine for me. Sorry about that, wish I could be of more help.

No probs thanks.

@pyrossh The addition of the new public field in a public struct without a major version bump is probably the reason for this error.

@AzureMarker  Yep didn't think through it after the merge and ended up releasing a minor version instead.


UI - "Edit" option for ingress entries does nothing.

**Rancher versions: 2.0 build from master
Steps to reproduce the problem:
Create Ingress.
From the ingress list view , click on "Edit" option.
Edit view for ingress is not launched.

Version - 2.0 master 3/1
Verified fixed


Adding dark-theme to Footer

Is your feature request related to a problem? Please describe.
Project is looking awesome with this amazing dark mode, but footer remains with same theme for light as well as dark!
So, i would like to add dark theme to footer.
I had attached preview ..
https://user-images.githubusercontent.com/56510414/112715439-33689600-8f06-11eb-979a-cbb0bb762285.mp4

Pls, assign me this issue
Have you read the Code of Conduct?
Yes

@Kajol-Kumari , pls review this issue

Hey @ShubhamSj07 I am not sure if this color combination you have used will look consistent with the rest.
@Coder-Srinivas Can you please help us with the color combination pick for the dark theme? Btw feel free to open up the PR for this @ShubhamSj07 we will let you know if any change is required.

@ShubhamSj07, the input tag has no styling effect when active. Have a look at the contact us section. Implement the same here.
Regarding the sign up button, use the following colors :
 background: #69a9dd;   border: 2px solid #69a9dd;   color: #171717;
And on hovering, use the following gradient :
  background: linear-gradient(     45deg,     #2b5876 0%,     #4e4376 90%   );   color: whitesmoke;
Colors used in dark mode :
#69a9dd
#282c35
#333333
#414a4c
Try to align the background theme with that of the website.

@ShubhamSj07 I'm a GSSOC'21 participant. I would like to contribute to this issue and can get started ASAP. Could you assign this to me? I propose that we use a toggle button to switch themes.

@pragati-kumar , lol I am working on this issue!


Create redirection when user accesses restricted routes

Coverage decreased (-0.2%) to 83.333% when pulling 7e027ea8216e49af396192a48977fef368952307 on auth into 40742fe43654adbc4025d4d28165b734b9790054 on master.


⚠ Samsung has degraded performance

In ab25337, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2698 ms

Resolved: Samsung performance has improved in abe4b38.


How to Open Solr 8.4.0 Core Index

Hi.  I'm extremely new to this.  I have Solr 8.4.0 installed on Centos 7 server.  I have installed Luke v. 8.0.0.  My index is located at: /opt/solr/server/solr/test01/data/index
java version "9.0.1"
When I open Luke and select that directory, it tells me: "Cannot open path.  Not a valid lucene directory or corrupted?"
I've tried all of the options, but none of them work.  How do I proceed?

Please use Lucene bundled Luke for latest Solr index.
https://medium.com/@mocobeta/luke-become-an-apache-lucene-module-as-of-lucene-8-1-7d139c998b2

You cannot open Solr 8.4.0 index via Luke 8.0.0.
Please use Lucene bundled Luke for latest Solr index.
https://medium.com/@mocobeta/luke-become-an-apache-lucene-module-as-of-lucene-8-1-7d139c998b2

Thank you.  I am finally able to run luke successfully.
I should mention (for others who might have similar issues) that /opt/solr/server/solr/test01/data is a symbolic link to /var/solr/data/test01/data.  Apparently luke doesn't like using sym linked directories.
And, I have to use /test01/data (not /test01/data/index).


How to re-call .rating() function on new DOM elements with Vue.JS

I have a problem. I'm using Vue.js and Laravel to paginate. I have Vue.js code:
new Vue({
            el: '.container',
            data: {
                reviews: [],
                pagination: {}
            },
            created: function () {
                this.fetchStories();
            },
            methods: {
                fetchStories: function (page_url) {
                    let vm = this;
                    page_url = page_url || '{{ route('admin.products.get-all-reviews') }}';
                    this.$http.get(page_url)
                        .then(function (response) {
                            vm.makePagination(response.data);
                            vm.reviews = response.data.data;
                        }).then(function () {
                            $('.container').find('.all-reviews-rating').rating();
                        });
                },
                makePagination: function(data){
                    let pagination = {
                        current_page: data.current_page,
                        last_page: data.last_page,
                        next_page_url: data.next_page_url,
                        prev_page_url: data.prev_page_url
                    };
                    this.pagination = pagination;
                }
            }
        });

I'm calling $('.container').find('.all-reviews-rating').rating(); after fetching data, but when I get second page it leaves first element's value to second page:
First Page:

Second Page:

As you can see. On the second page I have 1 star but it get's 5 stars. In HTML in input value it displays correctly.

Uhm, I think that they are not actually new DOM elements but existing ones that are being modified/updated. I suspect that because it seems that the second and subsequent calls to rating() are being ignored. It is because the plugin prevents multiple instantiations.
Could you try to destroy the instances before recreating them again? Something like this:
$('.container').find('.all-reviews-rating').each(function () {
  // This is internal plugin structure that we will move to the destroy method
  $(this).prev().remove();
  $(this).removeData('rating');
});
$('.container').find('.all-reviews-rating').rating();

If it works we could just add a destroy method to the plugin.


7Scenes Depth and RGB Intrinsics/focal lengths

Hello,
How do you handle the difference in focal lengths between the RGB and depth maps for 7Scenes? Are you cropping the RGB images down to match depth or reprojecting depths given the intrinsics of both?
Thanks!

Hi,
As we mention in the paper Section 4.1:
"The official distribution of [16] does not supply aligned color and depth images, so we use the rendered depth maps provided by [7] for evaluation."
You can check this out: https://github.com/vislearn/LessMore#data-structure

Hi,
Ah we missed this in the paper, thanks!


self-ci: use hooks.datakit.ci as callback address

This address should be more stable than the previous one.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "hooks-addr" git@github.com:talex5/datakit.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.


Prerequisites

[X] I have searched all issues/PRs to ensure it has not already been reported or fixed.

Criteria

[X] Reasonably well-known and widely used (e.g. if it's a GitHub project, it should have at least 100 stars and/or 50 forks)
[X] English interface (or at least English documentation)
[X] Latest stable version
[ ] Full version (i.e. not a trial version)
[X] Fairly standard install (e.g. uses a version-specific download URL, no elaborate pre/post install scripts)

Name
Rune
Description
Rune Player is a music player that offers audio analysis and recommendation features. It introduces a new, modern music management paradigm to enhance your experience with cross-platform support.
Homepage
https://github.com/Losses/rune
Download Link(s)
https://github.com/Losses/rune/releases/download/v1.0.0/Rune-v1.0.0-windows-amd64.zip
Some Indication of Popularity/Repute
Rune is an actively developed open-source project with a strong community presence, indicated by 710 stars and 20 forks on GitHub.
You can find it on major platforms including Steam, Microsoft and Apple Store.
Although Rune is open-source, it requires a license for legal use, with a starting price of $10. A trial version is provided, which provides the same features as the full versions on each store, allowing users to thoroughly test the software before committing to a purchase. The developers do not accept feature requests from unpaid users.
Publish on Scoop Extras is offered with the permission of @Losses, the developer of Rune.

This request is approved by the developer of Rune


Extra Folders in Test Folder

Not sure why we have extrac folders in the test folder, they may be created programmatically, but they need to be removed, they have no data and we should not be saving data there, or are they part of tests being run?

^^^ The empty folders up above should probably be removed


Add 2 more environments for Supernova

Changes

Add 2 more Supernova environments (demo and staging)

/review


Upstream changes

@lukebaker It looks like I don't have write access to this repo, any chance you can take a look at this? Thanks!

@jeffmon I've given you write access. Do you still want me to take a look at this?

@lukebaker Thanks for that! Would it be wise to merge in all of the things from their dev branch in the first place? And yes, would you be able to take a look? 😬

Seem my changes in #4. I think that does what we want.


[Java][Packaging] java-jars failing on maven module

Describe the bug, including details regarding any error messages, version, and platform.
java-jars job is failing: https://github.com/ursacomputing/crossbow/actions/runs/10103282092/job/27945082133
[FATAL] Non-readable POM /Users/runner/work/crossbow/crossbow/arrow/java/maven: /Users/runner/work/crossbow/crossbow/arrow/java/maven (No such file or directory) @

Component(s)
Java

Issue resolved by pull request 43431
https://github.com/apache/arrow/pull/43431


various minor style, docs and cpplint improvements

Refer to https://github.com/microsoft/LightGBM/pull/2699#issuecomment-580747526 and #1990.

For Appveyor failures refer to https://github.com/ContinuumIO/anaconda-issues/issues/11598.


APIException on Search endpoint

Recently I started getting APIExceptions whenever I use SpotifyClient.Search. There doesn't seem to be any description in the exception
Unhandled exception. SpotifyAPI.Web.APIException: Exception of type 'SpotifyAPI.Web.APIException' was thrown.
   at SpotifyAPI.Web.Http.APIConnector.ProcessErrors(IResponse response)
   at SpotifyAPI.Web.Http.APIConnector.DoRequest(IRequest request)
   at SpotifyAPI.Web.Http.APIConnector.DoSerializedRequest[T](IRequest request)
   at SpotifyAPI.Web.Http.APIConnector.SendAPIRequest[T](Uri uri, HttpMethod method, IDictionary`2 parameters, Object body, IDictionary`2 headers)

The exception has a Response field. Either have a look at that or the message field.

perhaps this isnt the right place to ask about this (maybe you know where that would be) but its literally just not returning anything and i dont really see any reason why that would happen

This looks like a legit request, very weird...
Did you catch this request with a proxy using this library or did you manually send it?

I used Fiddler to get that screenshot but it does the same thing without. I'm just using the library normally with ClientCredentialsAuthenticator & SimpleRetryHandler. The call for that request is
var response = spotifyClient.Search.Item(new SearchRequest(SearchRequest.Types.Album, $"upc:{release.Barcode}"))
                .GetAwaiter()
                .GetResult();

but it seems to do it for every (occassionally it seems to go through without any issues) SearchRequest

Due to the 404, I suspect that the issue is actually on spotify's side. It's especially confusing since the fiddler request looks valid. I will close this for now, if you have any more infos, feel free to share them and I will reopen! :)


refactor(webpack): bring mini-css-extract-plugin back

Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

Revert to mini-css-extract-plugin since it has supported HMR
Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[ ] All new and existing tests are passing.

Codecov Report

Merging #5825 into dev will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##              dev    #5825   +/-   ##
=======================================
  Coverage   95.68%   95.68%
=======================================
  Files          82       82
  Lines        2687     2687
  Branches      689      689
=======================================
  Hits         2571     2571
  Misses         98       98
  Partials       18       18

Flag
Coverage Δ

#e2e
100% <ø> (ø)
:arrow_up:

#fixtures
50.42% <100%> (ø)
:arrow_up:

#unit
92.66% <0%> (ø)
:arrow_up:

Impacted Files
Coverage Δ

packages/webpack/src/utils/style-loader.js
94.11% <ø> (ø)
:arrow_up:

packages/webpack/src/config/base.js
94.94% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 74e5920...ce3925c. Read the comment docs.

Hi @ScriptedAlchemy , thanks for the wonderful HMR support pr in mini-css-extract-plugin
I found that you've made a lot great changes in both mini-css-extract-plugin and extract-css-chunks-webpack-plugin, so I think you're the right expert that I should ask.
What do you think that we revert to mini-css-extract-plugin ?

Damn. Tough one. But I appreciate you seeking my advise. Appreciate your interest in anything I have to say on the subject ❤
It really depends on what you need out of the plugin. In general, extract-css-chunks is going to have newer features - at least from my contributions. I roll most work to my own plugin first, then roll it to webpack.
I do keep them in sync most of the time, so I’ll take contributions from mini-css and other authors and roll them back and forward. So either way the same features of mini-css should be in my plugin  (extract-css-chunks)
As I work on both and maintain them, I can say that mini-css has a way larger user base, it’s much harder to release code or add features at will. We have to be careful and there’s not a lot of contributors, so if we screw something up... it’s a huge wave of GitHub issues and not a lot of coders who can resolve them.
Mini-css is generally more stable due to this. I tend to open many “v4.3.6-beta.0” beta style releases to npm for extract-css-chunks. My @ next version is usually more advanced because I have found that my users are pretty happy to upgrade and help me test new code. If you like updating to the latest often, mini-css might be a slightly safer choice.  However, I also have complete control over extract-css-chunks so I can add features or change the code to help a project. It would be harder to get core webpack projects to cater to the needs of a handful of projects.
For example, right now HMR doesn’t work in mini-css if the css file is served off another port or is a url (regex issue) But I was able to easily fix that issue on extract-css and push it out :) the fix for mini-css which I myself will use as well, takes longer because we need to deal with more use cases.
There’s also just the attitude to how the project is treated. Webpack has a very enterprise feel to it in many ways. Where as on my project, I have ultimate control and make changes that can be drastically but bring a major improvement. I’m one person and I’ll do as I wish with the project - many see that as a risk - but I respect my users hugely and often seek their input before making a decision.
At the end of the day, you will likely get the same experience from either plugin. Mine will usually move faster or at least stay in sync with mini-css. But I’m also one person, so webpacks mini-css might be better and have more capacity when it comes to support.
what do I do I use both projects, big complex ones get my plugin, smaller ones get mini-css. Again I do this because I can offer big projects better control.

There’s also the server-side rendering aspect. We are the original authors of code-split SSR. when new innovations happen or drastic technological changes were needed - we own the whole stack. We push to standardize technology so there’s not much ecosystem, but if webpack 5 caused major SSR challenges, it’s my group who’d be first responders and extract-css-chunks would be the first in line to become operational in SSR environments if it were to ever stop.
There’s alternate SSR systems out there now, many based on our original work. We are friends with others in the industry so there’s no competitive aggression towards each other.
For me, use whatever works best and you feels fit your system best :) be that extract-css or mini-css.
Hopefully I’ve provided enough info

@ScriptedAlchemy Thank you so so so much for your quick and detailed reply, it will definitely help use a lot.
If I understood correctly, extract-css normally have more brilliant features and mini-css has a larger user group and more stable functionality
@Atinux @pi0 What do you think about this? Is it necessary to provide the possibility to switch the plugin is used since they have almost exact same options ?

 Appreciate your support and use of my work!
More or less. In no official capacity of course. I just happen to maintain both plugins and release all my contributions to my users ahead of time. I sync changes from others on mini css so that my plugin generally carries all the fixes plus a little extra.
Your understanding is correct.

Thank you so much for your input @ScriptedAlchemy and the take taken to guide us.
@clarkdo I believe we could update the build.extractCSS option to accept a string equals to 'mini-css-extract-plugin' so our userbase can start testing it and give us feedback on it?

As alternative we can create a community module that replaces loader. (If mini-css has advantages at a point of time)

Is it able to fix this issue?
https://github.com/nuxt/nuxt.js/issues/4219

I know there was an ordering issue which was fixed @jasonc08 - I'm pretty sure i rolled the patch over, ill diff the projects again and re-check.

@clarkdo 	I guess this PR can be closed in favor of #5906 ?

This pr is not for fixing extract css bug, it’s for consideration of which lib is more proper, personally I prefer mini-css since it has larger user amount and stable functionality


withAuth and authScopes don't dombine

Hey, I noticed that while you can use both withAuth and authScopes on the same field, it does not actually combine declarations despite what type declarations lead to think
https://github.com/hayes/pothos/blob/3cebfed6f033ee92c2b3492a3fd6d3002906ab08/packages/plugin-scope-auth/src/field-builders.ts#L58C7-L58C26
Example:
builder.mutationField('updateUserPropery', (t) =>
  t.withAuth({ user: true }).boolean({
    authScopes(_, args, context) {
      // Here `context` will be typed according to `AuthContexts`
      // but `{ user: true }` will be overwritten by this function
    },
    resolve() {
      // ...
    }
  })
)

Instead, I'd like both { user: true } and authScopes(){} to be merged

That seems reasonable to me, I think modifying this line https://github.com/hayes/pothos/blob/3cebfed6f033ee92c2b3492a3fd6d3002906ab08/packages%2Fplugin-scope-auth%2Fsrc%2Ffield-builders.ts#L58
To do something like this would work
authScopes: options.authScopes ? { $all: [scopes, options.authScopes] : scopes,

It's probably a little more complex, i think my example works if the new scopes are an object, but not if it's a function.  Handling the function case should be pretty easy though by wrapping it to return the merged scopes


This page doesn't clarify key points

We have customers asking us why some types of operations are allowed through the storage firewall (e.g. Azure portal can see properties of storage account / list containers / some APIs like "GetBlobServiceProperties")...
While we can answer these - it would be a lot easier if it was documented on this page already. Is it possible that it could be?
Thanks
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 2632af75-7664-b79b-ac5b-c7c17e6a609a
Version Independent ID: 6ecf71b6-77c4-3ab6-8ec9-353ea407d70f
Content: Configure Azure Storage firewalls and virtual networks
Content Source: articles/storage/common/storage-network-security.md
Service: storage
Sub-service: common
GitHub Login: @normesta
Microsoft Alias: normesta

@NickEales
Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.

@normesta
Can you please check and add your comments on this doc update request as applicable.

#reassign:@jimmart-dev

Thank you for your dedication to our documentation.
We sincerely apologize for the delayed response. After a careful review, we are closing this issue. If you feel that the problem persists, please respond to this issue with additional information.
Please continue to provide feedback about the documentation. We appreciate your contributions to our community.
#please-close

Thanks for your dedication to our documentation.
We sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary due to various constraints. Therefore, we've created an internal work item to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary.
#please-close


Create refs on FRCE for mm10

Problem

Currently pipeline functions with hg38 on FRCE but mm10 is likely to be a requested ref type

Solution

need to add ref files on FRCE
need to create json for FRCE pull; ensure pipeline reads files correctly

Config created with commit: b6f8ad0222bb16b3425311073c6ad8e01112fd26
Need to check file locations exist; waiting for group changes to get access to dir

Assigning to @escauley

See the attached file for mm10 source and destination locations. All files from source will need to be ported to frce in order for mm10 to run.

frce_mm10.csv

Files copied from helix to FRCE

Need to use Samtools to rebuild index files

"build" option does not currently exist for XAVIER, documentation on how to use mm10 resources will be added by Darryl

https://github.com/CCBR/XAVIER/issues/23 is a pre-req

mm10.frce.json updated. See https://github.com/CCBR/XAVIER/commit/4b70a94edb7a06b58ed75133745d7b6c8fcf2aa4
XAVIER pipeline was tested with mm10 genome and is now available on FRCE.


thirdparty .wasm usage from C

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Are there any ability to use C compiled code?
I noticed nightly build provide an ability to compile/link C code
example: https://github.com/rafaelbeckel/test-c-rust-wasm
discussion: https://github.com/rustwasm/wasm-bindgen/pull/2209
I tried to reuse solutions, but got an exceptions:
Added lib like this: rbg_calculator = { path = "../test-c-rust-wasm/crates/5_rust_bindgen" }

But CloudFlare worker fails:  service core:user:memgraph: Uncaught TypeError: WebAssembly.Instance(): Import #6 "env": module is not an object or function

Final goal is to add this one: https://github.com/memgraph/mgclient
It has an ability to be compiled in wasm:
Building WASM (Linux only)
Compiling mgclient for wasm requires the Emscripten sdk. This is automated in the following steps:
mkdir build && cd build
cmake .. -DWASM=ON

I also tried it, but the same error
Any suggestion on this?

It fails directly there - var B = new WebAssembly.Instance(N, { "./index_bg.js": g });
What does it mean? What is index_bg? I tried to find any files but worker-build doesn't ptoduce any

My understanding is that workers-rs just compiles to wasm32-unknown-unknown and that poses some limitations.
But under the hood, the plain wasm file is loaded by the engine and you can use that, to access some additional support that might be present:
https://developers.cloudflare.com/workers/runtime-apis/webassembly/javascript/
And apparently there is a way to get emscripten to work (it seems required by your final goal in wasm)
https://github.com/cloudflare/worker-emscripten-template

It fails directly there - var B = new WebAssembly.Instance(N, { "./index_bg.js": g }); What does it mean? What is index_bg? I tried to find any files but worker-build doesn't ptoduce any

These errors seem to be originating from the JavaScript shim that we auto-generate for you. Can you share a full reproduction repository?

Seems C static library was incorrect. I asked on there repository, have no answer. One question: Can I use thirdparty .wasm from Rust? I think wasmtime, but all bindings will be without any validation. Any suggestion to use from wasm?
I see it is possible to use memgraph from js: https://github.com/memgraph/jsmgclient/tree/main
But are there any standard/easy approach you can recommend?

@aviplayer, sorry for my late answer; I was on vacation and didn't see your message.
This issue arises because C symbols are not exported to a dylib unless you wrap them explicitly in Rust. This thread can give you some context: https://github.com/rust-lang/rfcs/issues/2771.
In the case of WASM, all missing symbols are expected to be provided from the env variable in the WASM imports table.
In my example, the memory.js file injects the missing symbols and provides a simple bump allocator from JS for malloc() and free() calls. Check out the build_with_wasm_pack.sh file in my example.
This was my first iteration for a POC and quite a hack-ish approach. In production, I'm using musl-libc (instead of the OpenBSD subset in the calculator) and have malloc() and free() implemented in Rust directly from the tinylibc crate, so we don't have to provide it from the imports table.
I will update the examples later on.


issue on probing different nodes for the same signal give different waveform

Hi,
I coded a simple counter and probe the signal at the io boundary and at the flipflop itself.
It shows two different waveforms on GTK.
May I know if there is somebody can point out what is wrong with my code?
class pwminCount extends Module {
  val io = IO(new Bundle {
    // Outputs
    val testReg = Output(UInt(4.W))
    // Inputs
  })

  // For testing only
  val testReg = RegInit(UInt(4.W), 0.U)
  testReg := testReg + 1.U
  io.testReg := testReg

}

class pwminCountTests(c: pwminCount) extends PeekPokeTester(c) {
  println("\ntesting pwminCount...\n")
  var finishTime = 50

    for(i <- 0 until finishTime){
      println("test=" + peek(c.io.testReg))
    step(1)
  }
}

I will take a look at this in the next day or so, I suspect this is an artifact of the interpreters synthetic view of timing.  Can you confirm, that this is occurs when using the interpreter back end

Thanks for your help! Yes, I use Firrtl to simulate and use GTK to view the waveform.
Here is the code that showing the Firrtl part.
object pwminCount {
  def main(args: Array[String]): Unit = {
    val manager = new TesterOptionsManager {
      testerOptions = testerOptions.copy(backendName = "firrtl", testerSeed = 7L)
      interpreterOptions = interpreterOptions.copy(setVerbose = false, writeVCD = true)
    }
    iotesters.Driver.execute(() => new pwminCount, manager) {
      c => new pwminCountTests(c)
    }
  }
}

We believe this is fixed. Please reopen if issue was not resolved.


Feature request: ability to play buttons

Would be awesome if there was a input mode where the buttons acted like a piano so you can play your sequence

Duplicate of #126


Supporting properties only for read or write

What is the best way to support properties such as _id or createAt that should only exist in GET but never POST.

You can define such properties as readOnly: true. There's also writeOnly for write-only properties.
https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.3.md#user-content-schemareadonly

You can define such properties as readOnly: true. There's also writeOnly for write-only properties.
https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.3.md#user-content-schemareadonly

Thanks @hkosova exactly right. Please also note that in the upcoming 3.1 release, we have the notion of annotations inherited from JSON Schema, and the interaction between readOnly / writeOnly and the required keyword will no longer apply.
Please chase if this doesn't resolve your issue.

Thanks @hkosova exactly right. Please also note that in the upcoming 3.1 release, we have the notion of annotations inherited from JSON Schema, and the interaction between readOnly / writeOnly and the required keyword will no longer apply.
Please chase if this doesn't resolve your issue.


Add to why distributed image processing is hard

This issue and figures perfectly show why it is hard

https://github.com/dask/dask-image/pull/94

Thanks @kmader. Could you expound on this a bit? For instance, are you imagining this should go in the docs somewhere?


Write a C++ program to convert octal to binary

Description
Write a C++ program to convert octal to binary
Octal is a base-8 number system. It uses only eight digits: 0, 1, 2, 3, 4, 5, 6, and 7. The digits are called octits. An octit is the smallest unit of information in a computer. An octit can be used to represent a single value, such as 0, 1, 2, 3, 4, 5, 6, or 7, or it can be used to represent a single state, such as on or off.
Binary is a base-2 number system. It uses only two digits: 0 and 1. The digits are called bits. A bit is the smallest unit of information in a computer. A bit can be either 0 or 1. A bit can be used to represent a single value, such as 0 or 1, or it can be used to represent a single state, such as on or off.
To convert an octal number to binary, we can use the following algorithm:

Convert the octal number to decimal.
Convert the decimal number to binary.

Input  : 12
Output : 1010

How to contribute

Save the solution in program/ConvertOctalToBinary.cpp file
Add ConvertOctalToBinary.cpp file in convert-octal-to-binary folder

!assign


[Bug]: BTD6 (34.3) Melon Loader (0.6.0 x64) crush "Caught Exception invoking Initialize! System.IO.IOException: Wrong descriptor"

All of the following criteria must be met

[X] All Requirements must be installed.
[ ] Full Latest.log file included. If no file exists then leave this unchecked and state so.

All of the following are optional to answer

[X] Tried reinstalling the Game.
[X] Tried reinstalling MelonLoader.
[X] Tried restarting PC.
[ ] Was able to see the Start Screen.

Describe the issue.
MelonLoader v0.6.0 (5.7.0 too) x64
Windows 7(looks like 2000, but its just a interface style)
Starting a game, like in every install guide.
Then instead of MelonLoader version, OS and Hash Code,
I get "Caught Exception invoking Initialize! System.IO.IOException: Wrong descriptor"
and some other stuff (on photo(cmd show entire thing, word moves to a new line))
I tried use x86(5.7.0 x86 too), but melonloader doesnt even shows(cmd and no melonloader loading menu things), but game said "Modded Client, most game modes are not avaible"(like in guides)

Did you attach your log file?

[ ] Yes, I attached my log file to the text box above.
[X] No, I could not find a log file at {Game_Directory}\MelonLoader\Latest.log

Windows 7 is officially out of support, and we don't support it either.


same() with Map, Set

The lib used for deep coercive comparisons, only-shallow, takes into account objects like Date instances but not ES2015+ Map and Set (it considers any two to be matches regardless of their content).
There’s no one right answer re: object comparison, and I know node-tap isn’t aiming to be a decked out assert lib, but it seems like same() handling Map and Set by comparing membership (but probably not iteration order) might be the most broadly friendly and least surprising choice. Or at least, the current behavior (comparing true) is kind of a false-positives foot gun.
I would open the issue at only-shallow, but it seems like that repo might be abandoned (open PRs & issues w/o responses for > 1 year).

, and I know node-tap isn’t aiming to be a decked out assert lib,

Ahem...
Yes, this is a bug.  I think there's a PR or issue to switch away from only-shallow, probably not a bad idea to either switch to something different or fork and fix it.  I'm a bit hesitant to drop it entirely, because it means either a breaking change, or a lot of work to evaluate the options.
https://github.com/tapjs/tmatch is the thing that does t.match() and the like, so it would have to get addressed over there.

Oh, I guess it'd have to be done on only-shallow and deeper as well.

So, I got started merging these two modules into tsame, and I want to implement this.  Here's a question and a proposed answer:
const a = new Set()
const b = new Set()

// similar, not the actual equal same objects
const arr1 = [1,2,3]
const arr2 = [1,2,3]
const obj1 = { a: 1 }

a.add(arr1)
a.add({a: 1})

// this should fail, of course.
t.sameStrict(a, b)

// but what about these?
// for each key in a, there's a "same" key in b
// but this means looping through and testing every key every time,
// which is (at least) O(n^2), vs the O(n) test using Set.has()
t.same(a, b)
t.match(a, b)

I'm gonna make it require that every actual key in a has to be in b as well, and vice versa, strict or not.  t.match(a, b) will pass if every key in b is in a, but not require b to have all the keys from a.
When testing Maps, the same thing, but the values will be tested using t.same() or t.sameStrict() or t.match(), as appropriate.
So, keys will always be somewhat stricter than values (effectively, using t.equal()), but key order won't ever matter (which means it can't just convert to an array and compare that way).
Feedback welcome, proceeding forward with this plan unless anyone objects.

I think that’s a good solution. In a situation where shape-matching on keys is needed, if the user does have a predictable iteration order they just need an extra array cast in the test, and if they don’t, well, it seems niche enough to not worry about unless there ends up being consistent evidence of a need.

Added in 10.5


fix: RowDesiredWidth was missing the RowHeaderWidth

What does the pull request do?
If one has row headers visible, the last column was clipped by the size the header column uses. This PR should fix it.
What is the current behavior?
See #8323
What is the updated/expected behavior with this PR?
Last column is completely visible, also if row headers are visible
How was the solution implemented (if it's not obvious)?
Add the missing header width during arrangement
Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes
The DataGrid will now look different, BUT imo this is the intended behavior. So from my point of view no breaking change
Obsoletions / Deprecations
None
Fixed issues
Fixes #8323
Backport?
Dear Avalonia-team. I don't say this often, but this bug is really bugging me. I've an ugly workaround for now, but I would like to see this issue fixed if possible. So if you see the chance to backport this PR, please do. Thank you in advance 🙏
Happy coding
Tim

This ! 👍

You can test this PR using the following package version. 0.10.999-cibuild0022110-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

YOLO merging this, scream if it's a fail :)


Support .NET Standard (for iOS, Android, Mac with via Xamarin)

Need a .NET Standard build of this for Xamarin apps...

There's a high chance we'll rewrite this, and when we do it'll probably be done in .NET standard. No ETA though.


Tweak --config and --config-dir help text

I thought that these options would also be used when running other subcommands, e.g. ord index. I think this PR clarifies that they're only used for ord server.

@raphjaph: Will #1527 mean that the config file will also be used for other commands, e.g. ord index?

Might this be something that we just wind up undoing in the future? I.e. we start using the config file for other commands, and now the help text is out of date. I'm not opposed though, especially if it's something you found confusing.
https://www.youtube.com/watch?v=CxK_nA2iVXw

Might this be something that we just wind up undoing in the future? I.e. we start using the config file for other commands, and now the help text is out of date.

Very much yes. It might. But we can't predict the future and I strongly feel we should try to have the best help output for the present behavior. To put it differently: If we change the behavior of ord, of course we have to make sure that the help texts get updated.

I'm not opposed though, especially if it's something you found confusing.

Yeah, I found it very confusing. I was hoping to be able to put the --data-dir setting into the config file. I ended up looking at the code and using rust-analyzer to figure out that the config is only used for ord server.

One issue I see is that really, the config file only supports a subset of the CLI configuration. It isn't just specific to the server, it's also specific to hiding inscriptions, since that's the only config option. So this change would make someone not look at the config file when trying to configure non-server commands, but wouldn't help someone who was trying to use the config file to configure options other than hiding things.
This makes me think that perhaps the best solution to this problem is actually just documenting which options are supported in the config file, and pointing to that documentation. That documentation (probably in the form of an example config file with all options) would then make it obvious that the only supported config option is hiding inscriptions when using the server.

@casey: I think what you say is true and makes sense. I still think it shouldn't stop this PR from being merged. This PR does make the help texts more accurate and helpful, while not solving all problems you point out. So I would still merge this. And -- if this is a high priority -- further improve documentation of the config file in other issues and PRs.

Closing in favor of #2044.

'sever deleted _0fd079902825c00ed761eab06ff2f5cd8c544d57#*


chore(main): release 1.27.0

:robot: I have created a release beep boop
1.27.0 (2024-12-13)
Features

DNS query & latency rolling effect cfg (f7896c5)

Bug Fixes

latency countup performance (86ea651)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.27.0
:sunflower:


Discussions

Hi Sirnejj,
I'm sorry for opening an issue (maybe turn on discussions for the repo?), but I've been following your work here as I'm implementing similar protocols for my business (Rust backend on a Sveltekit frontend), and I find your work incredible!
I've been thinking of extending this to use the Deno integration through yum, and then serving the SvelteKit site on deno. I don't know how well it would work, but though you might be interested!
I also have redone my version to use SeaORM and TypeShare (by 1Password FOSS) to allow full type-safety between my typescript front end and rust backend.
Overall amazing work! I would love to collaborate if you're wanting :)

Hello Annie,
It seems that your plan is awesome and I am willing to collaborate.
Between, I have turned on "discussions" for this repo. I really appreciate your compliments.


postgres: implement all fields (can reuse from elasticsearch) and add doc for that in wiki

Any plans to support Postgres?

most definitely, but we dont have resources available to implement this feature in the near future. would gladly accept PRs though including changes in the code, doc and tests

I added the Postgresql Storage pipeline - https://github.com/fhamborg/news-please/pull/140, please take look

addressed by your PR, thank you!


Ruby group capstone - Catalog of my things

In this project we did the following:
Logic

Each class from the UML class diagram is created in a separate .rb file.
All associations (1-to-many relationships) and aggregations (parent-child relationships) between classes are implemented.
All properties visible in the diagram are defined and set up in the constructor method. Exception: properties for the 1-to-many relationships are NOT set in the constructor method. Instead, they have a custom setter method created.
All methods visible in the diagram are implemented:

add_item method (in all classes that have that method)

Takes an instance of the Item class as an input.
Adds the input item to the collection of items.
Adds self as a property of the item object (by using the correct setter from the item object).

can_be_archived?() in the Item class

Returns true if published_date is older than 10 years.
otherwise, it returns false.

move_to_archive() in the Item class

Reuses can_be_archived?() method.
It changes the archived property to true if the result of the can_be_archived?() method is true.
It does nothing if the result of the can_be_archived?() method is false.

can_be_archived?() in the Book class

Overrides the method from the parent class.
Returns true if parent's method returns true OR if cover_state equals to "bad".
otherwise, it returns false.

can_be_archived?() in the MusicAlbum class

It overrides the method from the parent class.
Returns true if parent's method returns true AND if on_spotify equals true.
otherwise, it returns false.

can_be_archived?() in the Movie class

It overrides the method from the parent class.
Returns true if parent's method returns true OR if silent equals true.
otherwise, it returns false.

can_be_archived?() in the Game class

It overrides the method from the parent class.
It returns true if parent's method returns true AND if last_played_at is older than 2 years.
otherwise, it returns false.

Added unit tests for all implemented methods.

User interface

We created a main.rb file that will serve as our console app entry point.
All data is preserved by saving collections in .json files.

Database

We created a schema.sql file with tables that will be analogical to the structure of the classes in our app.

We have added the video of presentation in the Readme file

Thank you @thecodechaser, we truly appreciate your time and efforts in reviewing our work

Thank you @MahmoudBakr23 , we truly appreciate your time and efforts in reviewing our work