Cocoa Pod

Could you make it installed by Cocoa Pod?

There is Cocoapods support for a long time now.
Put this in your pod file:
pod 'TLIndexPathTools'

@doanthehien Is your question answered?


live server not working

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  <!-- Please search GitHub for a similar issue or PR before submitting -->
[ ] Feature request
[ ] Documentation issue or request
[ ] Other: <!-- Please describe: -->

Current behavior

Expected behavior

Environment
Browser:

- [ ] Chrome (desktop) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] IE version XX
- [ ] Edge version XX

For Tooling issues:

- Live Server: <!-- Check which version is installed -->
- Platform:  <!-- Mac, Linux, Windows -->
- Visual Studio Code: <!-- `code --version` -->

Others

in my laptop live server extension is not working , i checked all the ways about issue but i didn't got .and i tried to reinstall many times but it didn't work .! can anyone guesses the issue


Tracker speedup

This PR fixes some speed and memory issues with the tracker (and other remote windows).
There are a couple of issues:

[x] The previous calls we 'protected' with isDestroyed() actually can never rely on that flag. We have to wrap those calls in try/catch blocks
[x] After doing a bunch of profiling our architecture of having the main renderer send updates directly to the other browserwindows actually does this entirely synchronously which was killing our cpu (and would make the main render thread dead actually). In order to keep the tooling working we still keep the store in the main renderer (we could change this later), instead we send updates to the store to the main thread, which can send async to the rest of the browser windows.
[x] Instead of keeping track of the diffs we send everyone we just have a filtering function (a real function) that we call
[x] I split out the logging calls into their own flag since console.log is synchronous and can be slow which screws up the profiling session

@keybase/react-hackers
@cjb let's discuss if this should go in for m2

Instead of keeping track of the diffs we send everyone we just have a filtering function (a real function) that we call

Was there really an improvement in using a filtering function over a simple diff? If there wasn't a noticeable improvement I'd prefer the diff because it's less manual and less error prone. Imagine if you add something new to the connect call in a component, you'll have to make sure you don't filter that new piece out only when you make a remote component.

^ @MarcoPolo yes cause we send the entire store to all new windows, so that has to be serialized. Most of the popups have some root part of the store they care about and that doesn't change that often. if we want the diff to be even smarter we can by putting that logic into these closures that are created (but it doesn't seem necessary now)

Am distracted, but dropping by with a quick opinion:  if we're going to ship this for M2 I think it should be in the RC1 build, which I'm building in about two hours -- @chrisnojima and @MarcoPolo, think you could finish a review by then and do a bit of testing?  Thanks!

LG % Comments


make api notes link rich

Description
make api notes link rich as follow-up of #357 comment
Checklist
Essentials

[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage
[x] Code is well-documented

Changes

[x] refer to classes, modules, and methods when applicable in api notes

Job PR-362/9 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-362/9/index.html


Thank you!

There is no issue. I just wanted to say thanks. bustd is incredibly resource efficient and works better than earlyoom on older hardware in my experience. If it were packaged in Debian, I bet it would be more popular than it is now.

Hey @TechnologyClassroom, thanks for the feedback :D
Glad to hear it's been working nicely for you

If it were packaged in Debian, I bet it would be more popular than it is now.

It was packaged for Debian before by popOS (https://github.com/pop-os/bustd/tree/master/debian), which is probably a good starting point


Enhancement: add command-line play

Hi,
I suggest to create a command-line play command that can read PCM audio from stdin. See this exemple:
chromecast-play.exe - IP
Where "-" references the stdin (you can use any *.pcm file as input) and "IP" is the address of the target chromecast. Also, If you need it add the option of force the format: example "-s s16l" as Stereo with 16bit in low endian order.
You agree?

I 100% agree.

Hi @acidhax ,
Great! Then I suggest to use the syntax of VideoLAN or FFMpeg. For example:
$ vlc --demux=rawaud --rawaud-channels=2 --rawaud-samplerate=44100
Perhaps it's more simple to use similar syntax than create new one. ;-)

Since I use FFmpeg, I'll most likely just use the flags given as the input :)

Perfect! Tell me if I can do something to help.

Hi Acid!
I don't found command-line support in last release (0.30). Do you implement it?


Feat/redesign (Bootstrap -> Tailwind)

In case you are wondering why build fails:
16:26:02.799 | Failed to compile.
16:26:02.800 | ./src/app/containers/LendBorrowSovryn/index.tsx
16:26:02.800 | Line 2:21:  'Row' is defined but never used  @typescript-eslint/no-unused-vars


location header not generated correctly when running make gen

Istio.io proto scraper is here: https://github.com/istio/istio.io/blob/master/scripts/grab_reference_docs.sh
example location tags are here: https://github.com/istio/api/blob/00efe7317328e74d4ae0fb2213e45c6d61e7713c/mesh/v1alpha1/config.proto#L22
this should generate HTML like this:
https://github.com/istio/api/blob/00efe7317328e74d4ae0fb2213e45c6d61e7713c/mesh/v1alpha1/istio.mesh.v1alpha1.pb.html#L2
In the case of operator, it generates vanilla header, seemingly missing the location header there:
https://github.com/istio/api/blob/00efe7317328e74d4ae0fb2213e45c6d61e7713c/operator/v1alpha1/istio.operator.v1alpha1.pb.html#L2

Is the problem here that 'make gen' is generating an incorrect html file, or that grab_reference_docs.sh is not copying the file to the correct directory?

to expand on this, the doc generation plugin is not working correctly. the proto header looks correct and protoc is outputting the right go structs, but the docs header is not being generated in the plugin.

@jasonwzm Do you have any idea why the location tag would not be generated in the html file only for operator proto? I looked at the htmlGenerator's code and didn't find anything suspicious.


Past Board Members data JSON

@Safnaj any updates on this?

I am bit busy. Shall indonit Tommorow ??
If its urgent can you add it ??


Include xDS Creds in all

This fixes the import.

Closing in favor of https://github.com/grpc/grpc/pull/25407


alertView.showCloseButton

I cannot find any alertView.showCloseButton in the new version. Any replacement function ??
Thank you.

having the same problem here!

Please use appearance:
let appearance = SCLAlertView.SCLAppearance(showCloseButton: false)
let alert = SCLAlertView(appearance: appearance)


LocationPermission.deniedForever is not "Android only"

🏗 Enhancement Proposal

The README file says LocationPermission.deniedForever status is "Android only", but it also occur on iOS if you deny the location request.
Pitch

Remove the "Android only" from README file and better describe permission status.
Platforms affected (mark all that apply)

[x] :iphone: iOS
[ ] :robot: Android

@erf you are absolutely right. I have updated the documentation to:
/// Represent the possible location permissions.
enum LocationPermission {
  /// Permission to access the device's location is denied, but you should
  /// request permission.
  ///
  /// On iOS this is the initial status indicting the App has not requested
  /// permission yet.
  /// On Android this is also the initial status, however the user can still
  /// choose to deny permissions for now, meaning the App can still request
  /// for permission anohter time.
  denied,

  /// Permission to access the device's location is permenantly denied. When
  /// requestiong permissions the permission dialog will not been shown until
  /// the user updates the permission in the App settings.
  deniedForever,

  /// Permission to access the device's location is allowed only while
  /// the App is in use.
  whileInUse,

  /// Permission to access the device's location is allowed even when the
  /// App is running in the background.
  always
}

Thank you very much for pointing this out.

Great!
I see a small typo "anohter time" in "denied".
Maybe improve the sentence in "denied" to something like: "This is the initial state on both Android and iOS, but on Android..."
Thanks!

Thanks for the suggestion it is indeed a lot better then what I came up with ;). I will update it to and make another release (there are some other documentation changes I was pointed out to):
/// Represent the possible location permissions.
enum LocationPermission {
  /// This is the initial state on both Android and iOS, but on Android the
  /// user can still choose to deny permissions for now, meaning the App can
  /// still request for permission another time.
  denied,

  ...
}


Using commit_tx.confirmations to determine the validity of etching runes can lead to inconsistent judgments on the validity of runes during node operations

When deploying a rune, it is required that the commit tx and reveal tx for the same rune are separated by at least 6 blocks. Currently, the code logic checks the confirmations of the commit_tx using block.commit_tx.confirmations. Let's consider the scenarios for two nodes:
Node A: This node is continuously running. When it reaches block X, it executes the etching rune commit tx. Then, in block X+1, it performs the reveal tx. Since the two transactions are not separated by 6 blocks, the etching rune in this case is considered invalid.
Node B: Starting from block number 0, this node backtracks the data. When it reaches block X, it discovers the etching rune commit tx. In block X+1, it finds the reveal tx. Due to the time spent on backtracking, by the time it retrieves commit_tx.confirmations, it has already exceeded 6 blocks. Therefore, the etching rune is considered valid and appears in the list of runes.
The code in question is as follows:
https://github.com/ordinals/ord/blob/master/src/index/updater/rune_updater.rs#L399
let mature = tx_info
    .confirmations
    .map(|confirmations| confirmations >= Runestone::COMMIT_INTERVAL.into())
    .unwrap_or_default();

The suggestion is to compare the block numbers of the commit_tx and the reveal tx and check the difference to determine their separation.

Excellent find!

Fixed! #3507
This would have been pretty devastating if it hadn't been fixed before launch. We don't actually have a bug bounty, but I think this definitely deserves a reward. I was thinking $1000 USD paid in bitcoin. If you feel comfortable doing so, can you drop a bitcoin address? If not, can you drop some method for me to get in touch with you so we can coordinate off GitHub?

Is this issue to fix the loss of recognizing the etching of the transaction in the testnet?https://testnet.ordinals.com/tx/d484025088ddb8f4cdf4e72908608fd1cfe01d6a8d085c053939ac8ced78235e

@wanyvic I'm not sure, but that's probably unrelated. Can you open a new issue with more details?

It seems that our node (version 0.17.1 and indexing from block 0) has overidentified some runes.

such as the reveal transaction with the hash d484025088ddb8f4cdf4e72908608fd1cfe01d6a8d085c053939ac8ced78235e in the testnet. Our node explain that it is etching a rune named CL•TEST•TUE•THREE, but the commit transaction and the reveal transaction has not been separated by at least 6 blocks actually. I believe this issue is consistent with the feedback provided by @alexha123123, so there is no need to open a new issue.


Fix unpkg links in layer documentations

Coverage remained the same at 63.768% when pulling 1befc4dae08d1e981f0fdcaccda33240b544b109 on x/doc-links into ceacb96e83bad4a2d0c6b9c612a2d253b7644de9 on master.


List all products in a shopcart

As a Developer
I need to get all products a customer selected in his/her shopcart
So that I can list all products in the shopcart to the customer
Details & Assumptions

Shopcarts are created and stored in the database for a customer

Acceptance Criteria

Given the customer has been logged in
When the customer click shopcart
Then shopcart should be listed

As a developer
I need to create an API to return a list of items in the shopcart of a given customer
So that user can browse the items in their shopcart
Details and Assumptions

Assumed corresponding database model for shopcarts is available and accessible.
The API should be implemented using the REST architectural style.
The API should follow the standard HTTP methods, with the READ operation using the GET method.
The endpoint for retrieving shopcarts should be /api/customers/{customer_id}/shopcarts.
The response should be in JSON format.
The response should include the shopcarts' details, such as item names, quantities, prices, and any other relevant information.
The API should return a status code of 200 (OK) for successful retrieval.
The API should include appropriate error handling for invalid requests, missing parameters, or shopcarts that do not exist.
Instructions on how to use the API, including the endpoint, parameters, and expected response format should be updated to README.md.

Acceptance Criteria

Assumed corresponding database model for shopcarts is available and accessible.
The API should be implemented using the REST architectural style.
The API should follow the standard HTTP methods, with the READ operation using the GET method.
The endpoint for listing shopcarts should be /api/shopcarts/{customer_id}/items.
The response should be in JSON format.
The API should return a status code of 200 (OK) for successful retrieval.
The response body should include the shopcarts' details, such as item names, quantities, prices, and any other relevant information.
The API should handle any potential errors or exceptions during the listing process and respond with appropriate error messages and status codes.
Instructions on how to use the API, including the endpoint, parameters, and expected response format should be updated to README.md.

// Happy Path or Basic Functionality
Given a valid request to retrieve shopcart items,
When the API is called with the appropriate endpoint and parameters,
Then the API should respond with a status code of 200 (OK).
And the response body should include a list of shopcarts along with their details, such as item names, quantities, prices, etc.

// Error Handling
Given a request to retrieve shopcarts that do not exist (e.g. customer_id does not exist),
When the API is called with the appropriate parameters,
Then the API should respond with a status code of 404 (Not Found).
And the response body should contain an error message indicating that the requested shopcarts were not found.

// Testing
Given a set of mock shopcarts in the database,
When the API is called to list shopcarts,
Then the API response should match the expected shopcarts based on the provided test data.
And unit tests should be written to verify the correctness of the API implementation.

// Documentation
Given the API documentation, i.e. README.md,
When developers or consumers refer to it,
Then the documentation should provide clear instructions on how to use the API, including the endpoint, parameters, and expected response format.
And the documentation should include examples and sample requests to assist users in understanding the API.

Hey team! Please add your planning poker estimate with Zenhub @LillisLuo @momo100110 @nijya @wl2484

Based on Professor's response, the Read shopcarts API actually implies 2 APIs:
GET /shopcarts/{shopcart_id} to get a shopcart by shopcart_id
GET /shopcarts/{shopcart_id}/items/{item_id} to get item details in a shopcart (such as name, unit price, and quantity) by shopcart_id and item_id
I feel like it's better to create 2 separate stories for different APIs?

Updated the description for the assignee's convenience!


Should I handle AsyncAdapterBlockingExecutionFailedException?

Type: Bug
Component: SQS
Describe the bug
In Spring 2.X, whenever I needed to reprocess a message, I'd throw an error. This caused the message processing to fail, hence, reprocessing it.
In Spring 3.X, the AsyncAdapterBlockingExecutionFailedException is being thrown together with our expected exception.
ERROR [io.awspring.cloud.sqs.sqsListenerEndpointContainer#1-120] [AbstractMessageProcessingPipelineSink] [] Error processing message 18e958e4-6820-4005-8ca0-82b47b6adeed. java.util.concurrent.CompletionException: io.awspring.cloud.sqs.listener.AsyncAdapterBlockingExecutionFailedException: Error executing action in BlockingMessageListenerAdapter
	at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:332)
	at java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:674)
	at java.base/java.util.concurrent.CompletableFuture.uniApplyStage(CompletableFuture.java:662)
	at java.base/java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:2168)
	at io.awspring.cloud.sqs.listener.pipeline.MessageListenerExecutionStage.process(MessageListenerExecutionStage.java:49)
	...

Should I handle this exception? Is it harmless?

Hey @rodrigo-rufino, this exception is simply a Wrapper that indicates you're using a Blocking (not async) message listener.
The original exception should be down the cause chain.
Please let me know if you have any other questions.

@tomazfernandes Is there a way to get the original exception? I'm adding an error handler to my listeners, and they log the entire wrapper exception. It would be nice if I could log only the original one.
Another question: You said I'm using a blocking message listener. Is this a bad practice that I should avoid in my application?

@rodrigo-rufino have you solved this? I'm facing the same situation but only when the input queue has an associated DLQ.

I just added a ErrorHandler to rethrow de exception: https://docs.awspring.io/spring-cloud-aws/docs/3.0.2/reference/html/index.html#error-handling.

Hi Developers, we also want to get rid of this ERROR LOG Message "AsyncAdapterBlockingExecutionFailedException". Our implemented SQSReceiver logs the error and rethrow the exception, so that after some retries the messages ends up in the Deadletter queue.
Afterwards we are alerted about this error in cloudwatch. Right now we got two alerts, because of this two different error logs!
Any ideas on how to solve the problem? Why is it not possible to override the framework errorhandling or did I do something wrong? Overwriting with rethrow does not work, we still see the error log.
        return SqsMessageListenerContainerFactory.builder()                 .sqsAsyncClient(customSqsAsyncClient)                 .configure(options -> options                         .maxMessagesPerPoll(1)                         .pollTimeout(Duration.ofSeconds(5)))                 .errorHandler(new ErrorHandler<Object>() {                     @Override                     public void handle(Message<Object> message, Throwable t) {                         // ignore AbstractMessageProcessingPipelineSink error                         ReflectionUtils.rethrowRuntimeException(t);                     }                 })                 .build();

@tomazfernandes Is there a way to get the original exception? I'm adding an error handler to my listeners, and they log the entire wrapper exception. It would be nice if I could log only the original one.

@rodrigo-rufino, you can add some logic in your error handler to unwrap the exception by traversing the causes and ignoring framework and JDK exceptions such as AsyncAdapterBlockingExecutionFailedException and CompletionException.
We can look into adding some logic to support that in the framework if that's necessary.

Afterwards we are alerted about this error in cloudwatch. Right now we got two alerts, because of this two different error logs!

@thomasgerhardt0408 we could add an option in AbstractPollingMessageSource to disable the default framework logging. Would you be interested in opening a PR for that?

Hi Developers, we also want to get rid of this ERROR LOG Message "AsyncAdapterBlockingExecutionFailedException". Our implemented SQSReceiver logs the error and rethrow the exception, so that after some retries the messages ends up in the Deadletter queue. Afterwards we are alerted about this error in cloudwatch. Right now we got two alerts, because of this two different error logs!
Any ideas on how to solve the problem? Why is it not possible to override the framework errorhandling or did I do something wrong? Overwriting with rethrow does not work, we still see the error log.
return SqsMessageListenerContainerFactory.builder()
  .sqsAsyncClient(customSqsAsyncClient)
  .configure(options -> options
       .maxMessagesPerPoll(1)
       .pollTimeout(Duration.ofSeconds(5)))
  .errorHandler(new ErrorHandler<Object>() {
     @Override
     public void handle(Message<Object> message, Throwable t) {
         // ignore AbstractMessageProcessingPipelineSink error
        ReflectionUtils.rethrowRuntimeException(t);
      }
})
.build();

Disabling the logger in my logback.xml using the parent package worked for me:
 <logger name="io.awspring.cloud.sqs.listener.sink" level="OFF"/>

Looks like a good enough solution. I'll close the issue due to lack of feedback. We can reopen if necessary.


Fix floating label overlapping username initial

Quick fix for #44 floating label overlapping username initial.

I think @keyboardsurfer is waiting for another solution :-D


Undeploy Leaves Behind Network Interfaces

Undeploy does not remove the ENI it creates when making a lambda function
Context
This appears to be for
Expected Behavior
Undeploy removes everything it creates.
Possible Fix
Remove the ENI or add tags to ease removal by other tools.
Steps to Reproduce
Deploy app with a security group and subnets.  Undeploy and try and delete the security group.
Your Environment

Zappa version used: 0.44
Operating System and Python version: 3.6

Is there any update on this issue? I met the same issue

Same issue here.
Config:
{
    "dev": {
        "app_function": "test_handler.handle_stuff",
        "profile_name": null,
        "project_name": "ops",
        "runtime": "python3.6",
        "aws_region": "us-east-1",
        "s3_bucket": "zappa-cxf6jwe32",
        "vpc_config": {
            "SubnetIds": [ "..." ],
            "SecurityGroupIds": [ "..." ]
        }
    }
}


New version: EclipseAdoptium.Temurin.11.JDK version <IP_ADDRESS>

Pull request has been created with Komac v1.6.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

Accidentally deleted the branch


Consolidate and document environment configuration and helm values override options

Overriding helm values for applications installed with Jenkins X is getting confusing.  There are lots of places where helm values exists, taking tekton for example you can configure values in the main chart
https://github.com/jenkins-x-charts/tekton/blob/master/tekton/values.yaml
or look for the right version stream configured for your cluster and check the chart template values
https://github.com/jenkins-x/jxr-versions/blob/master/charts/jenkins-x/tekton/template-values.yaml
or the app template values
https://github.com/jenkins-x/jxr-versions/blob/master/apps/jenkins-x/tekton/values.yaml.gotmpl
and also possibly the boot config repo where we would recommend folks override values
i.e. apps/tekton/values.yaml
or to be able to use jxRequirements.yaml as parameters we can also use a gotmpl file
apps/tekton/values.yaml.gotmpl
Note this is different to a Helmfile gotmpl file as only jxRequirements are supported template options.
https://github.com/roboll/helmfile#templating which again could cause confusion.
Its kinda hard to grok whats needed and which way we should go.  Right now we are working on a different boot config repos, one for Vault another for GSM, we are changing each of them a bit to tailor them for their specific needs, we need to somehow sync or share changes between boot config repos.
Folks will likely be overwhelmed by all the options and find it hard to navigate around the repos.  It would be good to see if we can find a way to cut down on all the values override options so that it's easier for users to grok and simpler examples to follow, hopefully having a single place where people can look?

@jenkins-x-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

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


Include multiple paragraphs in value

also fixes handling when the "x" in - [x] is lowercase.
I'm already using this version in production in a private repo, so I'm confident that it's working.
Also we really need to add tests that we can actually run in CI :D

If you like, we can pair on it during a https://github.com/gr2m/helpdesk/ show? I've been working on Actions tests in the past few episodes.

Would like to join, but the time conflicts with my kids bedtime. Is the schedule fixed? Otherwise let's continue async on this. Thanks for your help so far Gregor, really appreciated.


Better PicoScan lidars support

We are in the process of integrating the new PicoScan sensors through this library and we did encounter a few issues.
Performance Profile parameter
We had to modify the library to be able to change the "performance profile" parameter of the lidar. We only partially succeeded as we are only able to change to profiles from 0 to 9, and not to 10. See the pull request we did here.
Example crashing when deregistering the library
The picoScan cannot stop properly because an issue occurs when calling one of the following 3 functions at the end of the sick_scan_xd_api_test example :

SickScanApiClose
SickScanApiRelease
SickScanApiUnloadLibrary

For now, we haven't found a way to fix this issue.

Thanks for your feedback. We will discuss support of Profiling Systems with SICK.
For a clean API exit by SickScanApiClose, please checkout branch https://github.com/SICKAG/sick_scan_xd/tree/feature/api_exit and rebuild.

We still have a problem with the SickScanApiClose function. When it's called in the sick_scan_xd_api_test example, the function is never exited, so the rest, such as SickScanApiRelease, is never called (tested with breakpoints).
We've noticed that the s_scanner variable is not allocated for picoscans (in sick_generic_laser.cpp file at lines 437-439) and when stopScannerAndExit(bool force_immediate_shutdown) is called in sick_generix_laser.cpp, it never goes through s_scanner->stopScanData(force_immediate_shutdown).
We then get the impression that we're stuck at the _Thrd_join(_Thr, nullptr) level in the thread file. This may be because the scanner never stops due to s_scanner = nullptr.
Any ideas?
Thank you in advance for your time.

Many thanks for following up! The previous fix was incomplete. Please use the updated version in branch https://github.com/SICKAG/sick_scan_xd/tree/feature/api_exit and rebuild. Note that this version is collected update with several changes incl. cleanup at API exit.

The problem under Windows for picoScan doesn't seem to have been solved.
We've noticed that when calling udp_receiver->Close() (line 395 of the scansegment_thread.cpp file), the function gets stuck at m_receiver_thread->join() (line 169 of the udp_receiver file). In fact, the thread doesn't seem to stop and remains blocked on a data reception operation (line 200 in the udp_socket.h file), as the data reception cannot take place because the connection is breaking.
Thank you for taking the time to answer our questions.

@paulinelvne Many thanks for your feedback and the detailed error description! Please find an update in branch https://github.com/SICKAG/sick_scan_xd/tree/feature/api_exit, which corrects closing receiver threads at API exit.


[Performance] Upgrade from the legacy DrawerNavigator to the modern one that uses Reanimated 2

Problem

We are still using the legacy version of the Drawer Navigator which is not using Reanimated 2.

I discovered that the DrawerView is not correctly picking up that Reanimated 2 is configured so it falls back to the "legacy" version of the drawer. The new code we want here is in a newer version of the @react-navigation/drawer package.

Upgrading will give massive improvements on Android to navigating and will allow us to use the InteractionManager to properly defer some expensive things we are doing until after the drawer opens/closes

HOWEVER...
There are two major blockers for this upgrade.

When the drawer performance is improved on Android it becomes so good that you see the previous chat before we display the new chat. Without the improvement today things just hang (for a few seconds) and we navigate to the new report. We will need to solve this somehow. Perhaps by showing the loader overlay as soon as a chat is tapped

Something about this upgrade is breaking the behavior of the drawer on mobile web. It will not open or close or respond to DrawerActions at all. We cannot fallback to the useLegacyImplementation as we'll get this error:

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

View all open jobs on GitHub

I've been looking into part 2 of this and pretty confused about why the drawer transitions are breaking in App specifically. I looked at the example app in the react navigation repo and ran it locally with settings similar to ours and it works OK so doesn't seem like there is any obvious regression.
While inspecting it just looks like the html elements are not updating at all with the new styles.
We should be seeing values update like this on main:
https://user-images.githubusercontent.com/32969087/193312104-7fdfe1df-521d-43e4-986c-756d672833e9.mp4
But instead the translateX values are not updating at all 🤔

test branch: https://github.com/Expensify/App/compare/marcaaron-enableNonLegacyDrawer

Are you sure that the issue with using legacy drawer is also present on Android?
I would suspect it's only problem on web based on changes here.

No to be clear, Android works great! It's only a problem on web. But cannot seem to downgrade to the legacy drawer on web. I tried to do some debugging in the Drawer component and think it might be an issue with useAnimatedStyle, but it's the first time I've look at Reanimated so not 100% sure.

I found the issue and responded on slack

https://expensify.slack.com/files/U0395FWE6TZ/F044R9C3B7V/screenshot_2022-10-01_at_17.15.58.png

Update: Still working on this. Mainly have been blocked on a change that the upgrade caused for the native side. Before the upgrade, tapping on a drawer item would make the UI freeze up until the next chat screen is ready to view. After the upgrade we navigate immediately, but still the old chat can be seen before transitioning to the new chat.
I think both are downsides, but I'd rather have the drawer tap be responsive and then wait some time before showing the next chat. I tried experimenting with showing a loading state during the transition, but seems like the native view takes some time to drop. This was most obvious on Android, but can be seen on iOS as well.
The latest thing I tried was wrapping some expensive things in SidebarLinks and ReportScreen with <Freeze> and setting the freeze prop to depend on the drawer state. The results are pretty good on an Android release build on emulator:
https://user-images.githubusercontent.com/32969087/194616753-f88749d5-e05c-4578-83d0-7fa3c3b612b8.mp4
The only downside left is that the frozen elements show as hidden when we are swiping. I think we are planning to move away from the drawer to a stack so not sure how much more energy should be put into perfecting this.
On the other hand, Android release build performance for chat switching is starting to look really good, I suspect from some other recent changes to Onyx and improvements in App:
https://user-images.githubusercontent.com/32969087/194618968-f33fce57-3d98-4f20-b965-823c8ee84008.mp4
So, it's hard to tell the difference now 😄 but the interaction is much more responsive and snappy in the first example with the upgraded Drawer.

Coming from this Slack thread seems like we are good with having the slight white screen for now so I'll take the linked PR out of draft soon.


[bug]:GPU index search slower than version 1.x

Environment
Machine Configuration：8c30g
knowhere branch: main

Current Behavior
run :  pytest test_ivf.py -v -m 'L0 and gpu'
NQ = 10000
TOP_K = 100
nprobe : Sequential execution in this list:  [1,2,4,8,16,32,64,128,256,512]
index:
"GPUIVFFLAT"
"GPUIVFSQ"
"GPUIVFPQ"
GPUIVFFLAT
param:
{"dim":128,"gpu_id":0,"metric_type":"L2","nlist":1024}

log:
INFO     root:test_ivf.py:301 data entities: 1000000, metric_type:L2, latency_errs:0.5
INFO     root:test_ivf.py:320 GPUIVFFLAT build time: 1.7703s @-0.2624
ERROR    root:test_ivf.py:353 nprobe1 latency degraded: expected=0.0191, actual=0.0438
INFO     root:test_ivf.py:360 nprobe=1, nq=10000, topk=100, search in 0.0438s @1.2932, recall=0.2914
ERROR    root:test_ivf.py:353 nprobe2 latency degraded: expected=0.0307, actual=0.0773
INFO     root:test_ivf.py:360 nprobe=2, nq=10000, topk=100, search in 0.0773s @1.5179, recall=0.4401
ERROR    root:test_ivf.py:353 nprobe4 latency degraded: expected=0.05, actual=0.1447
INFO     root:test_ivf.py:360 nprobe=4, nq=10000, topk=100, search in 0.1447s @1.894, recall=0.6041
ERROR    root:test_ivf.py:353 nprobe8 latency degraded: expected=0.0893, actual=0.275
INFO     root:test_ivf.py:360 nprobe=8, nq=10000, topk=100, search in 0.275s @2.0795, recall=0.7588
ERROR    root:test_ivf.py:353 nprobe16 latency degraded: expected=0.167, actual=0.5306
INFO     root:test_ivf.py:360 nprobe=16, nq=10000, topk=100, search in 0.5306s @2.1772, recall=0.8809
ERROR    root:test_ivf.py:353 nprobe32 latency degraded: expected=0.3184, actual=1.0321
INFO     root:test_ivf.py:360 nprobe=32, nq=10000, topk=100, search in 1.0321s @2.2415, recall=0.9564
ERROR    root:test_ivf.py:353 nprobe64 latency degraded: expected=0.6156, actual=2.0125
INFO     root:test_ivf.py:360 nprobe=64, nq=10000, topk=100, search in 2.0125s @2.2692, recall=0.9898
ERROR    root:test_ivf.py:353 nprobe128 latency degraded: expected=1.1958, actual=3.928
INFO     root:test_ivf.py:360 nprobe=128, nq=10000, topk=100, search in 3.928s @2.2848, recall=0.9988
ERROR    root:test_ivf.py:353 nprobe256 latency degraded: expected=2.3431, actual=7.6748
INFO     root:test_ivf.py:360 nprobe=256, nq=10000, topk=100, search in 7.6748s @2.2755, recall=0.9999
ERROR    root:test_ivf.py:353 nprobe512 latency degraded: expected=4.6045, actual=15.0453
INFO     root:test_ivf.py:360 nprobe=512, nq=10000, topk=100, search in 15.0453s @2.2675, recall=0.9999
INFO     root:test_ivf.py:364 GPUIVFFLAT search on sift recalls: [0.2914, 0.4401, 0.6041, 0.7588, 0.8809, 0.9564, 0.9898, 0.9988, 0.9999, 0.9999]
INFO     root:test_ivf.py:365 GPUIVFFLAT search on sift latency: [0.0438, 0.0773, 0.1447, 0.275, 0.5306, 1.0321, 2.0125, 3.928, 7.6748, 15.0453]

GPUIVFSQ
param:
 {"dim":128,"gpu_id":0,"metric_type":"L2","nlist":1024}

log:
INFO     root:test_ivf.py:301 data entities: 1000000, metric_type:L2, latency_errs:0.5
INFO     root:test_ivf.py:320 GPUIVFSQ build time: 1.583s @-0.3404
ERROR    root:test_ivf.py:353 nprobe1 latency degraded: expected=0.0123, actual=0.0296
INFO     root:test_ivf.py:360 nprobe=1, nq=10000, topk=100, search in 0.0296s @1.4065, recall=0.2914
ERROR    root:test_ivf.py:353 nprobe2 latency degraded: expected=0.0253, actual=0.0486
INFO     root:test_ivf.py:360 nprobe=2, nq=10000, topk=100, search in 0.0486s @0.9209, recall=0.44
ERROR    root:test_ivf.py:353 nprobe4 latency degraded: expected=0.0409, actual=0.0957
INFO     root:test_ivf.py:360 nprobe=4, nq=10000, topk=100, search in 0.0957s @1.3399, recall=0.6037
ERROR    root:test_ivf.py:353 nprobe8 latency degraded: expected=0.0658, actual=0.1776
INFO     root:test_ivf.py:360 nprobe=8, nq=10000, topk=100, search in 0.1776s @1.6991, recall=0.7578
ERROR    root:test_ivf.py:353 nprobe16 latency degraded: expected=0.1157, actual=0.3269
INFO     root:test_ivf.py:360 nprobe=16, nq=10000, topk=100, search in 0.3269s @1.8254, recall=0.8788
ERROR    root:test_ivf.py:353 nprobe32 latency degraded: expected=0.2175, actual=0.5954
INFO     root:test_ivf.py:360 nprobe=32, nq=10000, topk=100, search in 0.5954s @1.7375, recall=0.9519
ERROR    root:test_ivf.py:353 nprobe64 latency degraded: expected=0.3728, actual=1.131
INFO     root:test_ivf.py:360 nprobe=64, nq=10000, topk=100, search in 1.131s @2.0338, recall=0.9822
ERROR    root:test_ivf.py:353 nprobe128 latency degraded: expected=0.7265, actual=2.1943
INFO     root:test_ivf.py:360 nprobe=128, nq=10000, topk=100, search in 2.1943s @2.0204, recall=0.9892
ERROR    root:test_ivf.py:353 nprobe256 latency degraded: expected=1.4303, actual=4.2477
INFO     root:test_ivf.py:360 nprobe=256, nq=10000, topk=100, search in 4.2477s @1.9698, recall=0.9898
ERROR    root:test_ivf.py:353 nprobe512 latency degraded: expected=2.8133, actual=8.3322
INFO     root:test_ivf.py:360 nprobe=512, nq=10000, topk=100, search in 8.3322s @1.9617, recall=0.9898
INFO     root:test_ivf.py:364 GPUIVFSQ search on sift recalls: [0.2914, 0.44, 0.6037, 0.7578, 0.8788, 0.9519, 0.9822, 0.9892, 0.9898, 0.9898]
INFO     root:test_ivf.py:365 GPUIVFSQ search on sift latency: [0.0296, 0.0486, 0.0957, 0.1776, 0.3269, 0.5954, 1.131, 2.1943, 4.2477, 8.3322]

GPUIVFPQ
param:
{"dim":128,"gpu_id":0,"m":8,"metric_type":"L2","nbits":8,"nlist":1024}

log:
INFO     root:test_ivf.py:301 data entities: 1000000, metric_type:L2, latency_errs:0.5
INFO     root:test_ivf.py:320 GPUIVFPQ build time: 3.4683s @-0.5593
INFO     root:test_ivf.py:360 nprobe=1, nq=10000, topk=100, search in 0.0164s @0.2615, recall=0.2476
ERROR    root:test_ivf.py:353 nprobe2 latency degraded: expected=0.0139, actual=0.0214
INFO     root:test_ivf.py:360 nprobe=2, nq=10000, topk=100, search in 0.0214s @0.5396, recall=0.3342
ERROR    root:test_ivf.py:353 nprobe4 latency degraded: expected=0.0164, actual=0.0338
INFO     root:test_ivf.py:360 nprobe=4, nq=10000, topk=100, search in 0.0338s @1.061, recall=0.4019
ERROR    root:test_ivf.py:353 nprobe8 latency degraded: expected=0.0261, actual=0.0549
INFO     root:test_ivf.py:360 nprobe=8, nq=10000, topk=100, search in 0.0549s @1.1034, recall=0.4444
ERROR    root:test_ivf.py:353 nprobe16 latency degraded: expected=0.0366, actual=0.0837
INFO     root:test_ivf.py:360 nprobe=16, nq=10000, topk=100, search in 0.0837s @1.2869, recall=0.4657
ERROR    root:test_ivf.py:353 nprobe32 latency degraded: expected=0.0539, actual=0.1307
INFO     root:test_ivf.py:360 nprobe=32, nq=10000, topk=100, search in 0.1307s @1.4249, recall=0.4736
ERROR    root:test_ivf.py:353 nprobe64 latency degraded: expected=0.0773, actual=0.2146
INFO     root:test_ivf.py:360 nprobe=64, nq=10000, topk=100, search in 0.2146s @1.7762, recall=0.4754
ERROR    root:test_ivf.py:353 nprobe128 latency degraded: expected=0.1508, actual=0.3382
INFO     root:test_ivf.py:360 nprobe=128, nq=10000, topk=100, search in 0.3382s @1.2427, recall=0.4757
ERROR    root:test_ivf.py:353 nprobe256 latency degraded: expected=0.2945, actual=0.6395
INFO     root:test_ivf.py:360 nprobe=256, nq=10000, topk=100, search in 0.6395s @1.1715, recall=0.4757
INFO     root:test_ivf.py:360 nprobe=512, nq=10000, topk=100, search in 1.2229s @0.4321, recall=0.4757
INFO     root:test_ivf.py:364 GPUIVFPQ search on sift recalls: [0.2476, 0.3342, 0.4019, 0.4444, 0.4657, 0.4736, 0.4754, 0.4757, 0.4757, 0.4757]
INFO     root:test_ivf.py:365 GPUIVFPQ search on sift latency: [0.0164, 0.0214, 0.0338, 0.0549, 0.0837, 0.1307, 0.2146, 0.3382, 0.6395, 1.2229]

@cqy123456 Help assign

/assign @cqy123456

/assign @cydrain

fixed by #713


Added publishing profile with plugins to upload to nexus.

Added missing maven plugins, and moved it to profile to save build time.

nexus-staging-maven-plugin used for authentication, but honestly do not know if maven is enough.


X.P.OrgMode: Fix behaviour of getLast

Description
It's funny to notice this so late; I guess non-deterministic tests do have their drawback :)
So far, while parsing strings like "", the getLast
function immediately stopped on strings of the form "".
This may be a bit confusing given the functions name.  Strings of
the—perhaps artificial—form
"a +d f 1 +d f 2"

would be cut short and parsed as
Deadline "a" (Time { date = Next Friday, tod = Just 01:00 })

instead of the more intuitive
Deadline "a +d f 1" (Time { date = Next Friday, tod = Just 02:00 }).

This is readily fixed by applying the go parser as often as possible,
only returning the longest list, and then pruning eventual leftovers at
the end of the string.  Since we were already invoking dropWhileEnd to
trim whitespace before, the added reverses should not impact
performance at all.
Fixes: https://github.com/xmonad/xmonad-contrib/issues/584
λ ⟩ pInput "a +d f 1 +d f 2"
Just (Deadline "a +d f 1" (Time {date = Next Friday, tod = Just 02:00}))

λ ⟩ quickCheck $ prop_decodeLinearity (Deadline "+d" (Time {date = XMonad.Prompt.OrgMode.Next Friday, tod = Nothing}))
+++ OK, passed 1 test.

λ ⟩ quickCheck $ prop_decodeLinearity (Deadline "+d f 1" (Time {date = XMonad.Prompt.OrgMode.Next Friday, tod = Nothing}))
+++ OK, passed 1 test.

Checklist

[x] I've read CONTRIBUTING.md

[x] I've considered how to best test these changes (property, unit,
manually, ...) and concluded: I added some regression tests for the cases that were mentioned in #584

[n/a] I updated the CHANGES.md file
Unreleased module, I don't think this is necessary.

[n/a] I updated the XMonad.Doc.Extending file (if appropriate)

I wanted to merge this today but then life interfered and I'll be afk most of tomorrow as well so please do feel free to rebase --autosquash and merge any time.


[18.03] Apache fails to start: httpd-pre-start invalid user

Issue description
While trying to create a container running apache, I run into the following error when trying to start the container:
May 01 21:19:56 www1 systemd[1]: Starting Apache HTTPD...
May 01 21:19:56 www1 httpd-pre-start[1841]: chown: invalid user: ‘root.container’
May 01 21:19:56 www1 systemd[1]: httpd.service: Control process exited, code=exited status=1
May 01 21:19:56 www1 systemd[1]: httpd.service: Failed with result 'exit-code'.
May 01 21:19:56 www1 systemd[1]: Failed to start Apache HTTPD.

Looking at nixos/modules/services/web-servers/apache-httpd/default.nix I see two chown expressions using a period delimiter between user and group instead of a colon.
https://github.com/NixOS/nixpkgs/blob/527781ebc4137d9e6cda6dd21ab0dd776f8582d5/nixos/modules/services/web-servers/apache-httpd/default.nix#L708
https://github.com/NixOS/nixpkgs/blob/527781ebc4137d9e6cda6dd21ab0dd776f8582d5/nixos/modules/services/web-servers/apache-httpd/default.nix#L711
Steps to reproduce
# /etc/nixos/configuration.nix
{ config, pkgs, ... }:

{
  imports =
    [ ./containers/www1.nix
    ];

   # ...

  users.extraUsers.container = {
    uid = 9999;
    shell = "/run/current-system/sw/bin/nologin";
  };

  users.extraGroups.container.gid = 9999;

  system.stateVersion = "17.09";
}

# /etc/nixos/containers/www1.nix
{ config, pkgs, ... }:

{
  containers.www1 = {
    autoStart = true;

    bindMounts = {
      "/var/www" = {
        hostPath = "/var/containers/www1/public";
      };
    };

    config = { config, pkgs, ... }: {
      networking.firewall = {
        enable = true;
        allowedTCPPorts = [ 80 ];
      };

      services.httpd = {
        enable = true;
        adminAddr =<EMAIL_ADDRESS>
        user = "container";
        group = "container";

        documentRoot = "/var/www";
        hostName = "test";
      };
    };
  };
}

# mkdir -p /var/containers/www1/public
# chown -R 9999:9999 /var/containers/www1
# nixos-rebuild switch
# machinectl shell root@www1
> www1# journalctl -e

Technical details
Please run nix-shell -p nix-info --run "nix-info -m" and paste the
results.
 - system: `"x86_64-linux"`
 - host os: `Linux 4.14.37, NixOS, 18.03.132164.6473360dc7d (Impala)`
 - multi-user?: `no`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.0.1`
 - channels(boxofrox): `""`
 - channels(root): `"nixos-18.03.132164.6473360dc7d"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs`

Found a mistake on my part.  I'm trying to run apache as user:group container:container, but forgot to create those IDs inside the container.
{
  containers.www1 = {
    config = { config, pkgs, ... }: {
      users = {
        extraUsers.container.uid = 9999;
        extraGroups.container.gid = 9999;
      };
    };
  };
}

That solved the problem with starting Apache.
The chown user.group syntax isn't documented in man chown, so when I saw the error mention "invalid user", I thought it was looking for a user named root.container.  Turns out, chown user.group path runs fine if both the user and group exist.
Sorry for the noise.


Update Scala.js to 0.6.16

Codecov Report

Merging #622 into master will increase coverage by 0.14%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #622      +/-   ##
==========================================
+ Coverage   82.98%   83.13%   +0.14%
==========================================
  Files          72       72
  Lines        2022     2022
  Branches      141      141
==========================================
+ Hits         1678     1681       +3
+ Misses        344      341       -3

Impacted Files
Coverage Δ

.../core/shared/src/main/scala/io/circe/Decoder.scala
88.5% <0%> (+0.38%)
:arrow_up:

...rc/main/scala/io/circe/shapes/SizedInstances.scala
92.85% <0%> (+14.28%)
: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 7a83803...1e72d96. Read the comment docs.


Collaboration and environments concept

Thank you for helping make the Radius documentation better!
Please follow this checklist before submitting:

[ ] Read the contribution guide
[ ] Commands include options for Linux, MacOS, and Windows within codetabs
[ ] New file and folder names are globally unique
[ ] Page references use shortcodes instead of markdown or URL links
[ ] Images use HTML style and have alternative text
[ ] Places where multiple code/command options are given have codetabs

In addition, please fill out the following to help reviewers understand this pull request:
Description
Created the Concept doc for Collaboration between Developers and IT Operators as well as how Environments and Recipes are the way we support that collaboration.
Auto-generated description

🤖 Generated by Copilot at 872866c
Summary
🤝🚀☁

Add a new concept page about collaboration for developers and operators. This page explains the benefits of using Radius to overcome the common challenges of IT specialization and cloud native complexity.

Radius project
Docs for dev and ops teams
Autumn of cloud native

Walkthrough

Create a new concept page about collaboration for developers and operators (link)

Issue reference
Fixes: #769 #770

Spoke with @jonvsm and we might use this for a blog post in the future.

This is a duplicate of a doc RyanN already wrote.


Force user.language as some tests are locale dependent

Description
Some tests are locale dependent. For instance PolarisServiceImplIntegrationTest is failing if user.language is not en.
Fixes #11
Type of change
Please delete options that are not relevant.

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
This PR actually fixes the tests when Locale is not US.
Checklist:
Please delete options that are not relevant.

[X] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] If adding new functionality, I have discussed my implementation with the community using the linked GitHub issue
[ ] I have signed and submitted the ICLA and if needed, the CCLA. See Contributing for details.

I think this is fine, but I also think it may make sense to scope the locale config to the place where the tests require it. Not a huge deal though.


reportlist.json is not generated

how should reportlist.json be generated in the container?
it is somehow generated with generate_reportlist.py, but this script is never run in the container? and there is no python in the container. how should this be triggered if someone uploads a new report?

You dont need to run the script when accessing the report using the url ?report=

yes, but why have a menü, if we dont use it? ;)

Menu is nice, but not needed if we know the report file name. To me it looks like menu is for convenience only.


Cuts off letters

Hi there,
Thank you for an outstanding peace of software! I tired so many plugins but none could read my m4b audio books.
I noticed sometimes it would cut off the end of the audiobook title even though its in the mp3 tag. Example Live Your Best Lif (instead of Life)
Also, I added a custom column (text) Duration (Example 01:44:23) in Calibre, could you please pretty please with suga on top add a feature to import Duration from file?
Can you please add a button to process existing files already in the library.
 Thank you so much for your plugin!!!!!

Looking at the code, I can see the issue is in the get_title_form_tag function in the first init.py file. The function is stripping "(Unabridged)" from the end but might be accidentally truncating other text.
Find this block:
def get_title_form_tag(tag):
    title = tag.album or tag.title
    if title is None:
        return None
    return title.strip().rstrip(" (Unabridged)")

Replace it with this block:
def get_title_form_tag(tag):
    title = tag.album or tag.title
    if title is None:
        return None
    if title.endswith(" (Unabridged)"):
        return title.strip()[:-13]  # remove " (Unabridged)" only if it's exactly at the end
    return title.strip()

Tested and working.


Updated sdkVersion prefix according to spec

Description

Using 'u' for unknown os
Dropping configType character
Using python agents folder as marker for RP integration.

All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.


Add job to Circle CI to test docker-compose ubuntu-cpp job

There seems to be a test failure unrelated to the PR https://app.circleci.com/pipelines/github/facebookincubator/velox/16508/workflows/02573e2c-65b5-41dd-91c6-0c0acc70d014/jobs/102349:
6: /velox/velox/common/file/tests/FileTest.cpp:176: Failure
6: Expected equality of these values:
6:   localFs->list(std::string_view(tempFolder->path))
6:     Which is: { "/tmp/velox_test_6qwkMs/2", "/tmp/velox_test_6qwkMs/1" }
6:   std::vector<std::string>({a, b})
6:     Which is: { "/tmp/velox_test_6qwkMs/1", "/tmp/velox_test_6qwkMs/2" }
6: [  FAILED  ] LocalFile.list (0 ms)
6: [ RUN      ] LocalFile.readFileDestructor

I think this is ready to merge now and we can open a ticket to investigate a possible flaky outside of this PR. @kgpai , I've rebased and changed this job to run on a nightly basis.


Bug: "Updated" time updated without change

Some of my files have their updated field updated even without any changes being applied to the note.
I noticed this by looking at the differences when committing my files on git, but I could not figure out a pattern yet and I am unable to reproduce it immediately (but it has happened ever since I started using this plugin a few months ago).
In principle, this could of course be caused by applying edits and then rolling them back, but I personally think that this is too rare to be the sole explanation for this.
Is anyone else experiencing this?

@klieret Yup, I am having this issue too, did you figure out why? So far I am thinking it's either cause of git and/or perhaps how this plugin implement it's own observers.

I just reported the same issue with the created date.
https://github.com/beaussan/update-time-on-edit-obsidian/issues/41

I'm frequently having this issue, can't tell why it happens. Weirdly enough, seems to happen even when the plugin is disabled and Obsidian restarted, changes to .obsidian/plugins/update-time-on-edit/data.json still happen
???


Separate updating from rendering

In nearly all classes, updating the state of an object is done in the draw function (or vice versa). This violates the rule that functions should do one thing.
Highly consider splitting the various draw/update functions into a separate void update(float deltaSeconds) and void draw() const or void draw(Renderer& r) const where appropriate.

We should move forward with this one.
Perhaps we need a summary of how extensive the redesign would be. In particular, how many or what classes would be affected, and how this might impact inheritance hierarchies.
We should also come up with a plan that allows for incremental improvements in small steps, without breaking large sections of code.
Perhaps initially methods can be split, where the existing method makes calls to the new split off code. That way there are no changes required for the caller. Once all functions are in place, we can then start making changes to the callers.


Text and example mismatch

Text says "Do not use implicit typing to determine the type of the loop variable in foreach loops."
But example uses implicit: foreach (var ch in laugh)
My guess is that the text is wrong. At least I always use implicit for foreach.

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

ID: 5a3c147e-2271-4d7c-712b-2f705b5ecbc5
Version Independent ID: 2c1a7cfe-364e-408e-77c1-9fae2b0da643
Content: C# Coding Conventions - C# Programming Guide
Content Source: docs/csharp/programming-guide/inside-a-program/coding-conventions.md
Product: dotnet-csharp
Technology: csharp-get-started
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

duplicate of #18900

Well, mine is a little different. I think the recommendation (text) should change; not the example.


add steps for creating a rinkeby bond

v2 bonds. I changed the README to reflect that
The bond.create call on the contract gives configuration options for each of your other questions.

It will create fixed term or fixed expiration depending on the settings you use (I noted this in the comments of each setting)
It does not require LP tokens, but could accommodate them. You have to change the _quoteToken address to whatever asset you want to bond. I noted this in the comments
_quoteToken is the asset you want to bond. It can be whatever you want. It doesn't have to be LP. It can be a single-sided asset. My example is simply DAI, not DAI LP.


[stable/metabase] add namespace argument to all templates

Currently, the namespace is not automatically added to templates, even if Helm is called with the --namespace attribute. This seems to be intended by Helm: https://github.com/helm/helm/issues/3553
Other charts have also done this for their templates, for example: https://github.com/helm/charts/pull/17712

Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] DCO signed
[ ] Chart Version bumped
[ ] Variables are documented in the README.md
[ ] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @viglesiasce

FYI the PR template includes this defunct link https://github.com/helm/helm/tree/master/docs/chart_best_practices

/assign @pmint93

/ok-to-test

@jukecraft Can you please resolve the current conflict, so that the test can run

/retest

/assign @pmint93

/lgtm

thank you!


add support for paddlenlp embedding

add support for paddlenlp embedding  issue#281

@vax521 thanks your contribution, please give your commit a sign, like git commit --amend -s

recommit later


Add docs on super regions

Fixes DOC-2581
Fixes DOC-2899
Fixes DOC-3099
Fixes DOC-3110
Summary of changes:

Add section on super regions to 'Multiregion Overview' page

Add SQL reference pages with examples:

'ADD SUPER REGION'

'DROP SUPER REGION'

'ALTER SUPER REGION'

'SHOW SUPER REGIONS'

Add links to the above statements as needed from the 'ALTER DATABASE'
and 'SQL Statements' pages

Sweet, thanks for putting this out.

Can you please confirm the permissions needed to use DROP SUPER REGION? (see note marked 'XXX' on drop-super-region.md)
Can you please confirm the permissions needed to use ADD SUPER REGION? (see note marked 'XXX' on add-super-region.md)

Good question, this one follows the general requirement for multiregion database ops which is CREATE privilege or being the owner of the database.

Similar to my question on cockroachdb/cockroach#79912, do you mind explaining what the meaning of the sql.defaults.override_alter_primary_region_in_super_region.enabled setting is? I found this comment which seems to explain it, but I was wondering: what do we mean by "modify" a primary region in that comment? as in, change the primary region A of a database to be some other region B while region A is part of a super region? (see other note marked 'XXX' on add-super-region.md)

Your understanding is correct, we have this to prevent users shooting themselves in the foot. Altering the primary region could cause say a regional table to move out of a super region it was part of, we want them to explicitly acknowledge that this can be possible through setting the cluster setting.

Also, is there a corresponding session setting to the sql.defaults.override_alter_primary_region_in_super_region.enabled cluster setting above?

Yes it is override_multi_region_zone_config

Can you please confirm the permissions needed to use SHOW SUPER REGIONS? (see note marked 'XXX' on show-super-regions.md)

The rows will only be populated if they have any privilege on the corresponding database, ie CREATE

What is the correct SQL syntax diagram to link to for SHOW SUPER REGIONS? I've tried a few variations of show_super_region*.html and have been getting 404s (see other note marked 'XXX' on show-super-regions.md)

It's part of the show_regions.html I believe which might not make that much sense

Thanks Richard!  I updated things and I this is RFAL

Sweet, thanks for putting this out.

Thanks for writing the feature!

Good question, this one follows the general requirement for multiregion database ops which is CREATE privilege or being the owner of the database.

OK thanks.  I think the stuff that's there is basically right, then

Your understanding is correct, we have this to prevent users shooting themselves in the foot. Altering the primary region could cause say a regional table to move out of a super region it was part of, we want them to explicitly acknowledge that this can be possible through setting the cluster setting.

OK - added some words around "this is off by default for your safety - do this only if you know what you are doing"

Yes it is override_multi_region_zone_config

Added

The rows will only be populated if they have any privilege on the corresponding database, ie CREATE

Updated the SHOW SUPER REGIONS to list this as a perm

It's part of the show_regions.html I believe which might not make that much sense

Oh I see.  Added it (I think it's probably fine to be one diagram, it's all to do with regions n stuff)

Hey @RichardJCai thanks for answering my questions earlier - this should now be ready for your official review
In particular please let me know if:

something in here is incorrect
something is missing that users need to understand to use super regions
you see anything else in general that could be improved

Thanks!

Thanks for the review @awoods187 !  Working on these updates now (esp. adding the ALTER SUPER REGION stuff)

One last thing actually, I think we should also call out zone config limitations here like we do in
https://www.cockroachlabs.com/docs/stable/data-domiciling.html#limitations
Notably this point since SUPER REGIONS relies on zone configs.
[Zone configs](https://www.cockroachlabs.com/docs/v21.2/configure-replication-zones) can be used for data placement but these features were historically built for performance, not for domiciling. The replication system's top priority is to prevent the loss of data and it may override the zone configurations if necessary to ensure data durability. For more information, see [Configure Replication Zones](https://www.cockroachlabs.com/docs/v21.2/configure-replication-zones#types-of-constraints).

I think we may want to document this more generally as well (the limitations) and that if constraints cannot be satisfied we prioritize durability (ie we will up replicate to a node outside of the constrained regions).
On the engineering side I think we should explore adding a zone config setting to not upreplicate in these cases and allow the data to become unavailable instead (?) if there are hard requirements for data domiciling.

@RichardJCai I'd like to merge this PR sometime tomorrow unless you have any additional feedback on my update to the Super regions section of the Multiregion Capabilities Overview page re: super regions/zcfgs being historically built for availability


Support block revert operation in blockchain cache

Extracted part of #3201 . This PR add support (under #[cfg(test)] for now) for block revert operation in cache - it truncates and (optionally) destroys unfinalized cache forks. This is required, because after #3201 blockchain cache will be used to store consensus-critical information on full nodes (changes tries configuration, which are used to build changes tries => block header is affected). Having any inconsistencies in the cache will lead to fatal errors.

Things get a bit clearer after a reread, I am rather interested in this list entry cache code because I realize I write some code with similar purpose. Do you know what are the current uses for it? A quick search, return my mostly access to authorities from consensus and light client.
For the pr in itself is seems ok to me, maybe a review from someone more familiar with the code may be needed, but it seems good.

atm the cache only exists on light clients && used to save data of consensus algorithm (authorities in Aura && era in BABE). I'm planning to use it to store CT configurations on light/full nodes as well.

So it is not strictly speaking a cache, seems like I started some work on something rather close to be able to store some child trie keyspace for #3648 (the dev intends to be extensible to other use cases but it seems like this 'cache' could have been a good way to get things done quickier).

Right, it isn't used as a cache anymore. It used to be in the very beginning, but now it is merely a storage (though it still can be used as a cache).
You can use it, of course. But please keep in mind that it is optimized for values that aren't changing often (or better - not changed at every block). If you need something that have different value at every block, then probably it is better to use simple map + separate db column for that.

one test still failing..


[material-ui][Paper] Cannot read properties of undefined reading 'paper'

Steps to reproduce
Link to live example: https://mui.com/material-ui/customization/palette/
Steps:

Install MUI v5 (5.15.1).
Import ThemeProvider and createTheme from mui/material/styles.
Using the palette from createTheme.
Using the button component
on rendering getting the error cannot read properties of undefined (reading 'paper').

Current behavior
import { createTheme, ThemeProvider } from "@mui/material";
import { PaletteOptions } from "@mui/material/styles/createPalette";
export const palette: PaletteOptions = {
};
export const theme = createTheme({
palette,
components: {
MuiButton: ButtonConfig,
},
});
export const ThemeWrapper: React.FC<PropsWithChildren> = ({
children,
}) => {children};
Using this code It was working before, but after it is throwing an error, It is working on some browsers but not working on some.
Expected behavior
Originally it was working the palette.backgroud.paper was running and working, but initially it is not working on some browsers, locally I am using MUI version 5.15.1.
Context
For creating themes, I am using the themeProvider from MUI, But due to some reasons It is throwing error on running the app, It works on refresh but again throws the error, I also tried upgrading to v5 (5.15.11), still facing the same issue.
Your environment
No response
Search keywords: paper
Search keywords:

`import { css } from "@emotion/react";
import { createTheme, Theme } from "@mui/material/styles";
import { lightVariable, darkVariable, greys } from "./colors";
const baseline = css`
.MuiDataGrid-menu {
z-index: 20 !important;
}
// somehow cannot import this css in the builder package
.react-flow__edge-path {
stroke: #333;
stroke-width: 2;
}
.temp .react-flow__edge-path {
stroke: #bbb !important;
stroke-dasharray: 5 5 !important;
}
// remove native reactflow selection window after dragging
.react-flow__nodesselection {
&.react-flow__container {
&.nopan {
display: none;
}
}
}
`;
export const lightTheme: Theme = createTheme({
palette: {
primary: {
main: lightVariable.p1,
},
secondary: {
main: lightVariable.p2,
},
mode: "light",
},
typography: {
fontFamily: "Inter", Helvetica, Arial, sans-serif,
button: {
textTransform: "capitalize",
},
},
components: {
MuiCssBaseline: {
styleOverrides:         ${baseline.styles}         a {           color: ${lightVariable.p1};           :hover {             color: ${lightVariable.p2};                       }         }      ,
},
MuiButton: {
styleOverrides: {
root: {
borderRadius: "8px",
},
},
},
},
});
export const darkTheme: Theme = createTheme({
palette: {
primary: {
main: darkVariable.p1,
},
secondary: {
main: darkVariable.p2,
},
mode: "dark",
},
typography: {
fontFamily: "Inter", Helvetica, Arial, sans-serif,
button: {
textTransform: "capitalize",
},
},
components: {
MuiCssBaseline: {
styleOverrides:         ${baseline.styles}         a {           color: ${darkVariable.p1};           :hover {             color: ${darkVariable.p2};                       }         }      ,
},
MuiButton: {
styleOverrides: {
root: {
borderRadius: "8px",
},
},
},
},
});
export const lightColors: { [key: string]: string } = {
...lightVariable,
...greys,
background: lightTheme.palette.background.paper,
primary: lightTheme.palette.primary.main,
primary_light: lightTheme.palette.primary.light,
primary_dark: lightTheme.palette.primary.dark,
secondary: lightTheme.palette.secondary.main,
secondary_light: lightTheme.palette.secondary.light,
secondary_dark: lightTheme.palette.secondary.dark,
text: lightTheme.palette.text.primary,
text_reversed: lightTheme.palette.getContrastText(
lightTheme.palette.text.primary
),
dark: lightTheme.palette.text.primary,
error: lightTheme.palette.warning.main,
warning: lightVariable.b8,
warning_light: lightTheme.palette.warning.light,
warning_dark: lightVariable.b9,
info: lightTheme.palette.success.main,
info_light: lightTheme.palette.success.light,
info_dark: lightTheme.palette.success.dark,
muted: lightTheme.palette.grey[500],
muted_light: lightTheme.palette.grey[300],
muted_dark: lightTheme.palette.grey[700],
};
export const darkColors: { [key: string]: string } = {
...darkVariable,
...greys,
background: darkTheme.palette.background.paper,
primary: darkTheme.palette.primary.main,
primary_light: darkTheme.palette.primary.light,
primary_dark: darkTheme.palette.primary.dark,
secondary: darkTheme.palette.secondary.main,
secondary_light: darkTheme.palette.secondary.light,
secondary_dark: darkTheme.palette.secondary.dark,
text: darkTheme.palette.text.primary,
text_reversed: darkTheme.palette.getContrastText(
darkTheme.palette.text.primary
),
dark: darkTheme.palette.text.primary,
error: darkTheme.palette.warning.main,
warning: darkTheme.palette.warning.main,
warning_light: darkTheme.palette.warning.light,
warning_dark: darkTheme.palette.warning.dark,
info: darkTheme.palette.success.main,
info_light: darkTheme.palette.success.light,
info_dark: darkTheme.palette.success.dark,
muted: darkTheme.palette.grey[500],
muted_light: darkTheme.palette.grey[300],
muted_dark: darkTheme.palette.grey[700],
};
`

I don't if it's the same issue but I'm also facing the
same problem

The palette.background does not have the paper property defined, hence it's throwing error.

I'm shooting in the dark here but shouldn't Mui provide all the properties and functions like getContrastText and paper itself?
As I see it createTheme is supposed to append custom styles/properties and also default functions from the library.
Any reason why the behavior of createTheme has changed suddenly?

Can you provide a CodeSandbox that reproduces the issue? It's hard for maintainer to suggest a fix without a reproducible sandbox.

Can you provide a CodeSandbox that reproduces the issue? It's hard for maintainer to suggest a fix without a reproducible sandbox.

https://codesandbox.io/p/sandbox/back-ns3wv4?file=%2Fsrc%2FApp.js%3A1%2C1-57%2C1

Are there any updates or workarounds for this? Our development team is basically fully-blocked due to this issue.

Can you provide a CodeSandbox that reproduces the issue? It's hard for maintainer to suggest a fix without a reproducible sandbox.

https://codesandbox.io/p/sandbox/back-ns3wv4?file=%2Fsrc%2FApp.js%3A1%2C1-57%2C1

@Abhay5855 is it not working? I can console.log(theme.palette.background.paper).

Are there any updates or workarounds for this? Our development team is basically fully-blocked due to this issue.

I still could not reproduce the issue. Can you share a codesandbox?


Extract production information from line between FirstLine and LastLine of one product

example of one product details in invoice given below
Serla Kostea Siivousliina 32 kpl
221443 92537  1 TU 14.160 TU  24 0.00
/     14.16
How should i extract middle line info
I have written a regular expression for FirstLine which cover the first two lines in regex101 editor but it wont work with the extract_lines() function because extracts text line by line.
firstline: (?P<desc>.+?)\s+(\d+)\s+(\d+)\s+(?P<qty>\d+\s+TU)\s+(?P<unitprice>\d+.\d+(:?\s+TU))\s+(?P<taxpercent>\d+(.\d+)?)\s+(?P<discount>\d+.\d+)

lastline: \s+/\s+(?P<totalamount>\d+.\d+)

@hbrunn
Can you have a quick look at it. I have explained the problem to the best of my abilities

you need to produce a line regex that matches the middle lines, but not the last line. And hook your expressions to the begin/end of line. Check https://github.com/m3nu/invoice2data/blob/master/invoice2data/templates/de.qualityhosting.yml as an example

My input string is
Serla Kostea Siivousliina 32 kpl
221443 92537 1 TU 14.160 TU 24 0.00
/ 14.16
I made my firstline regex match the middle line and i successfully get it but i miss the description in the first line
line: ^\s*(?P.+)$
firstline:(\d+)\s+(\d+)\s+(?P\d+\s+TU)\s+(?P\d+.\d+(:?\s+TU))\s+(?P\d+(.\d+)?)\s+(?P\d+.\d+)
lastline: \s+/\s+(?P\d+.\d+)
Result Acheived
{'qty': '1 TU', 'discount': '0.00', 'taxpercent': '24', 'unitprice': '14.160 TU', 'totalamount': '14.16'}
Results Expected
{'desc': 'Serla Kostea Siivousliina 32 kpl','qty': '1 TU', 'discount': '0.00', 'taxpercent': '24', 'unitprice': '14.160 TU', 'totalamount': '14.16'}
The result of 'desc' group is missed
I tried to learn it from the example you provided but i could not get a grasp

@hbrunn
My input string is
Serla Kostea Siivousliina 32 kpl
221443 92537 1 TU 14.160 TU 24 0.00
/ 14.16
I made my 'firstline:' regex match the middle line and i successfully get it but i miss the description in the first line
line: ^\s*(?P<desc>[\w ]+)$
firstline:(\d+)\s+(\d+)\s+(?P<qty>\d+\s+TU)\s+(?P<unitprice>\d+.\d+(:?\s+TU))\s+(?P<taxpercent>\d+(.\d+)?)\s+(?P<discount>\d+.\d+)
lastline: \s+/\s+(?P<totalamount>\d+.\d+)
Results Acheived BUT DONT KNOW HOW
{'desc': 'Serla Kostea Siivousliina 32 kpl','qty': '1 TU', 'discount': '0.00', 'taxpercent': '24', 'unitprice': '14.160 TU', 'totalamount': '14.16'}
I have successfully got what i wanted but i dont know how. With hit and trial
Can you take a minutes to explain so i can handle more cases like this in future


Change workflow secrets

See https://github.com/Senzing/aws-marketplace-evaluation/issues/134

Pull requests:

https://github.com/Senzing/aws-cloudformation-ecs-senzing-stack-basic/pull/158


Set actual length in USBIP_RET_SUBMIT message

This patch sets the actual_length field of the USBIP_RET_SUBMIT message
to the number of bytes received with the USBIP_CMD_SUBMIT message.

This fixes an issue where the number of bytes written was reported incorrectly on the host, see https://github.com/trussed-dev/pc-usbip-runner/issues/9.

Looks good to me.
Thanks a lot.

Thanks for the quick merge!

@Sawchord Hi! Thank you for a quick reaction! Do you plan to make a new release with this patch?

Oh yeah good idea. Can do


Support video.js version 8?

I found it at https://videojs.com/plugins/ and am using it.
thank you as always.
This sentence is written as a translation,
so please understand that there may be some mistakes.
package.json does not include version 8.
Are there any plans to support video.js version 8?
	"peerDependencies": {
		"video.js": ">= ^7"
	},

what i tried.
Success<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS><EMAIL_ADDRESS>--save-dev

added 2 packages, removed 3 packages, and changed 9 packages in 3s

Failed<EMAIL_ADDRESS>$ npm install<EMAIL_ADDRESS><EMAIL_ADDRESS>--save-dev
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: undefined@undefined
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/video.js
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer video.js@">= ^7" from<EMAIL_ADDRESS>npm ERR! node_modules/@theonlyducks/videojs-zoom
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ec2-user/.npm/_logs/2024-08-05T04_39_38_813Z-eresolve-report.txt

npm ERR!  ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: undefined@undefined
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/video.js
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer video.js@">= ^7" from<EMAIL_ADDRESS>npm ERR! node_modules/@theonlyducks/videojs-zoom
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ec2-user/.npm/_logs/2024-08-05T04_41_06_584Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /home/ec2-user/.npm/_logs/2024-08-05T04_41_06_584Z-debug-0.log

Hello my friend, the version compatible with video.js ^8 is now available. Thank you for reporting the issue, and I'll go ahead and close it. If you encounter any new problems, feel free to report them here. Thanks again!

Hello my friend, thank you for your work.
I was able to install successfully.
$ npm cache clean --force
npm WARN using --force Recommended protections disabled.

$ npm install<EMAIL_ADDRESS><EMAIL_ADDRESS>--save-dev

added 27 packages in 4m


calyx-py: Mark std_bit_slice as combinational

Hey repo contributors,
I found that std_slice is combinational but std_bit_slice is not. However, from the verilog template, they should be the same.
I wonder why you have such design.
module std_bit_slice #(
    parameter IN_WIDTH = 32,
    parameter START_IDX = 0,
    parameter END_IDX = 31,
    parameter OUT_WIDTH = 32
)(
   input wire logic [IN_WIDTH-1:0] in,
   output logic [OUT_WIDTH-1:0] out
);
    assign out = in[END_IDX:START_IDX];
...
endmodule

and
module std_slice #(
    parameter IN_WIDTH  = 32,
    parameter OUT_WIDTH = 32
) (
   input wire logic [IN_WIDTH-1:0] in,
   output logic [OUT_WIDTH-1:0] out
);
  assign out = in[OUT_WIDTH-1:0];
...
endmodule

in calyx/calyx-py/calyx /builder.py, line 1440,
def is_comb(self) -> bool:
        return self._cell.comp.id in (
            "std_add",
            "std_sub",
            "std_lt",
            "std_le",
            "std_ge",
            "std_gt",
            "std_eq",
            "std_neq",
            "std_sgt",
            "std_slt",
            "std_fp_sgt",
            "std_fp_slt",
        )

Maybe it should be added with more classes?

Yup, looks like an oversight! Do you want to open a pull request to fix this?

Hey, there is one more possible bug, in primitives/core.sv, line 209
module std_bit_slice #(
    parameter IN_WIDTH = 32,
    parameter START_IDX = 0,
    parameter END_IDX = 31,
    parameter OUT_WIDTH = 32
)(
   input wire logic [IN_WIDTH-1:0] in,
   output logic [OUT_WIDTH-1:0] out
);
    assign out = in[END_IDX:START_IDX];
    ...
endmodule

In order to be consistent with the docs itself (https://docs.calyxir.org/libraries/core.html),

std_bit_slice<IN_WIDTH, START_IDX, END_IDX, OUT_WIDTH>
Extract the bit-string starting at START_IDX and ending at END_IDX - 1 from in. This is computed as in[END_IDX:START_IDX].OUT_WIDTH must be specified to be END_WIDTH - START_WITH wide when instantiating the module.

it should be
assign out = in[END_IDX:START_IDX];

For example, when create a std_bit_slice by slicer = std_bit_slice(4, 2, 4, 2);, it cannot be synthesized because END_IDX is out of range in in signal.
To fixed it, the document should be changed like

std_bit_slice<IN_WIDTH, START_IDX, END_IDX, OUT_WIDTH>
Extract the bit-string starting at START_IDX and ending at END_IDX - 1 from in. This is computed as in[END_IDX-1:START_IDX].OUT_WIDTH must be specified to be END_WIDTH - START_WITH wide when instantiating the module.

and the core.sv should changed like
assign out = in[END_IDX-1:START_IDX];

I can help fix these two issues.

Sounds good, thanks!

Closed by 8d242da68ad5cfb266cd622911beafe341921d3a


Readme is outdated

Update examples please. Currently they don't work

Choose 2.x branch

I've already make 2.x the new default branch. Until I have a plan to release 3.0.0
The master branch is next branch


[NETPATH-144] Add container id to source

What does this PR do?
Adds the source container ID from connections of dynamic paths to the trace so we can resolve the source container on the back end.

Motivation
Allow us to better show connections between dynamic paths we capture with Network Path and the NPM connections that showed them

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


#683 Deployment

Resolves #683, still needs a bit of work

Wow this looks awesome. The new config page and the code read very well. I left a few minor inline comments. I'm definitely not an authority on deployment but as far as I can tell this looks ready.

I generalized the comment in setup_mail.rb but left deploy.rb alone since I don't know exactly how to proceed w/ the Capistrano stuff. Should we just take it all out / cherry pick those commits into a new branch and only leave the configuration stuff? Honestly, having the Capistrano files in the repository don't hurt (as we know since we had old ones hanging around for years), and the work necessary to separate out the commits would be a pain, so I'm inclined to leave them and rely on the #1074 to get them polished up.

Cherry picking sounds like a pain. Merge this and we'll polish in 1074

passing all but our troublesome tests (see #1059), merging!


Require date option radio button to be selected before allowing the entry of dates and require date range to have two year entries.

Similar to the embargo date issue, user should need to select either "Single date" or "Date range" before being able to enter dates to avoid the situation in the screenshot where "Single date" radio button is selected but a date is entered for the "Date range." I also think that when one of the date radio buttons is selected any previous entries for the other date option should be reset to default to avoid the situation where both  "Single date" and "Date range" have entries.
Second issue is that if the user chooses "Date Range" they should be required to enter two years at a minimum (month and day optional).
Please let me know if you have any questions about this.

I believe this is covered by #796 and #914. @peetucket can you double check me on that and close this one if this is true? Thanks.

I believe this is covered by #796 and #914. @peetucket can you double check me on that and close this one if this is true? Thanks.

See the PR attached to #796 for a pattern to use.

See the PR attached to #796 for a pattern to use.


Missing methods with SQLitePCLRaw.bundle_winsqlite3 and Microsoft.Data.SQLite.Core

Compiling release builds using SQLitePCLRaw.bundle_winsqlite3 2.0.1 (and also 2.0.0) and Microsoft.Data.SQLite.Core 3.0 is broken as it features missing methods.

This breaks the release build, and I have to revert to older versions (SQLitePCLRaw.bundle_winsqlite3 1.1.14 with Microsoft.Data.SQLite.Core 2.2.6).
is there any work around?
PS:
This is in a UWP C# application with a .NET standard 2.0 as the base target.

Full error messages:
warning :       MCG : warning MCG0007: Unresolved P/Invoke method 'dl!dlopen' for method 'System.IntPtr SQLitePCL.NativeLibrary.NativeLib_dlopen.dlopen(System.String, System.Int32)'. Calling this method would throw exception at runtime. Please make sure the P/Invoke either points to a Windows API allowed in UWP applications, or a native DLL that is part of the package. If for some reason your P/Invoke does not satisfy those requirements, please use [DllImport(ExactSpelling=true) to indicate that you understand the implications of using non-UWP APIs.
warning :       MCG : warning MCG0007: Unresolved P/Invoke method 'dl!dlsym' for method 'System.IntPtr SQLitePCL.NativeLibrary.NativeLib_dlopen.dlsym(System.IntPtr, System.String)'. Calling this method would throw exception at runtime. Please make sure the P/Invoke either points to a Windows API allowed in UWP applications, or a native DLL that is part of the package. If for some reason your P/Invoke does not satisfy those requirements, please use [DllImport(ExactSpelling=true) to indicate that you understand the implications of using non-UWP APIs.
warning :       MCG : warning MCG0007: Unresolved P/Invoke method 'dl!dlclose' for method 'System.Int32 SQLitePCL.NativeLibrary.NativeLib_dlopen.dlclose(System.IntPtr)'. Calling this method would throw exception at runtime. Please make sure the P/Invoke either points to a Windows API allowed in UWP applications, or a native DLL that is part of the package. If for some reason your P/Invoke does not satisfy those requirements, please use [DllImport(ExactSpelling=true) to indicate that you understand the implications of using non-UWP APIs.

Hmm.  That's bad.
I don't think there is a viable workaround.  This will require another release to fix it.

I'm more or less in the same boat with your comment. I've tried quite a few things to get past this, but sadly been unsuccessful in my attempts. Would the fix (on the release side) be simple or quite a complex endeavor? (aka would take awhile before being in pre-release).
Also thanks for your very fast reply!

That'd be amazing - this would really unblock my product update release at the current stage. I appreciate such a fast reply and potential turn-around of the new NuGet package release :)

OK, I just pushed up version 2.0.2-pre20191003102319 to nuget.org.
FWIW, I was able to reproduce the error reported above, and with the attempted fix in this pre version, the error goes away and a UWP project with bundle_winsqlite3 does successfully build in release mode.
Let me know how this works for you.

Yes! I can confirm that the new pre-release has fixed the release build issue.
Thank you so much!

Out of curiosity, would what be an 'expected' time-frame for this to leave pre-release?

I'll close this issue when I ship the fix in a non-pre release, which I'm guessing will happen 2-3 weeks from now

A small update on this: The latest version seems to be incompatible with Windows version 1709 and 1803 (haven't tested 1809 yet). I've been using an Azure VM to test these for older version incompatibilities.
Ref for Windows versions: https://en.wikipedia.org/wiki/Windows_10_version_history
It appears to immediately crash upon release build, however using Microsoft.Data.Sqlite 2.2.6 and winsqlite3 1.1.14 in a sample app succeeds in the release builds and runs (on version 1709).
Enabling native debugger gives a slightly nicer debug error, which is Entry Point not found. Aside from this, the debugger fails to attach itself to the exe as it crashes instantly.

Closing old/stale issue.


[Help] Proxy ips and Proxy ports

where do you find good proxy ips and ports?

ur not using a proxy for it, you're supposed to be using a Virtual Machine in the location you want to have lowping on.

ur not using a proxy for it, you're supposed to be using a Virtual Machine in the location you want to have lowping on.


Show Datatable Toolbar with No Selection (expose as optional)

Currently the datatable batch action toolbar hides when no items are selected in batch selection mode. This is an incorrect assumption imho.
Hypothetical scenario - A user wants to remove all load balancer associations and 'save'

Go to: https://carbon-components-svelte.onrender.com/framed/DataTable/DataTableBatchSelectionToolbar?theme=white
User unchecks all the load balancers
User needs to save this state (does not want any load balancers).

Released in v0.68.0


Name discussion

What do you think of the names:

"Glasses" or derivatives (glassy, glassly etc) – you see the benchmark results better with "glasses"
"Magnet" – it's the one place (magnet) for your benchmark results
"Mosaic" – you get a mosaic of results, which fit together
"Puzzle" – same idea as above.
For the names, you could, of course, put a "Bench" in front of each. I prefer simpler names, because they're catchy 😉

We can discuss the names here and then it's easy to see who said what & why. Ofc we shouldn't waste a lot of time with this!
My personal faves are: Glassy, Mosaic.


fix: don't log stacktrace if cli succeeds (regression)

Starting in v0.26.1, successful runs of the CLI (i.e. when it doesn't crash) incorrectly report an error and error stack while running tsd:
Error running tsd: Error:
  index.test-d.ts:26:0
  ✖  25:0  Expected an error, but found none.
  ✖  26:0  ) expected.

  2 errors

    at ~/node_modules/tsd/dist/cli.js:64:19
    at Generator.next (<anonymous>)
    at fulfilled (~/node_modules/tsd/dist/cli.js:6:58)

This PR restores the old behavior and makes sure that the error message and stack are only displayed when tsd crashes.

I’m not sure why the tests are failing in Node 14.

Turns out error.cause isn't supported in Node 14:
throw new Error(formatter(diagnostics, showDiff), {cause: 'tsd found diagnostics'});

It now only throws on failure, and otherwise exits with an error code if any error-level diagnostics are found:
const exit = (message: string, {isError = true}: {isError?: boolean} = {}) => {
	if (isError) {
		console.error(message);
		process.exit(1);
	} else {
		console.log(message);
		process.exit(0);
	}
};

try {
	// ...
	if (diagnostics.length > 0) {
		const hasErrors = diagnostics.some(diagnostic => diagnostic.severity === 'error');
		const formattedDiagnostics = formatter(diagnostics, showDiff);

		exit(formattedDiagnostics, {isError: hasErrors});
	}
} catch (error: unknown) {
	const potentialError = error as Error | undefined;
	const errorMessage = potentialError?.stack ?? potentialError?.message ?? 'tsd unexpectedly crashed.';

	exit(`Error running tsd:\n${errorMessage}`);
}

The formatter also needs to report the number of warnings, but I have another PR for that.


Handling connection timeout issue for ebs volume encryption

REF: https://github.com/chef/knife-ec2/pull/299

Hi!
Take a look at what I've just read, this is so interesting, read more at http://syntutraze.hsevents.com/oizmxfad
See you around<EMAIL_ADDRESS>


[LS] Only type cast code action is suggestion for class field assignments

Description:
Consider:
public class ProxyClient {

    private tcp:Client proxyClient;
    private http:Client cl;

    public function init(string proxyHost, int proxyPort) {
        self.proxyClient = new(proxyHost, proxyPort);
    }
}

At self.proxyClient = new(proxyHost, proxyPort);, only type cast code action is suggested. Need to suggest Add check code action as well.
Steps to reproduce:
See decription
Affected Versions:
SLA3
Suggested Labels (optional):
Version/SLAlpha3

Relates to #29582


pom.xml incorrectly sets IDE source language level to 17 when it should be 11

Describe the bug
The pom.xml incorrectly sets the IDE source language level to 17 when it should be 11.  The testSource should remain at 17.
To Reproduce
Steps to reproduce the behavior:
Add a JDK 12+ language feature, for example, instanceof/cast pattern matching.
Expected behavior
The maven or IDE should fail, complaining about an unsupported language feature.
Screenshots
N/A
Environment (please complete the following information):
N/A
Additional context
This is the linked IntelliJ issue, which now has a status of fixed:  https://youtrack.jetbrains.com/issue/IDEA-85478

Looks like the source is 11 to me: https://github.com/hapifhir/hapi-fhir/blob/master/pom.xml#L866-L868

If you mean the version that's in the ide profile at the bottom of the root pom.xml, that doesn't affect our built sources, it's just a workaround for an IDE limitation (more info in the comments right above that)

@jamesagnew Yes, I mean the version in. the IDE profile.  Sorry for not being clear.  I'll update the issue.
As for the comment, the linked issue seems to be fixed but the fixed version is not specified:
https://youtrack.jetbrains.com/issue/IDEA-85478
I'll try testing this and will update with what I find.

Oh! It looks in that ticket looks like 2022.1 has the fix. Maybe this isn't needed after all... that's awesome if so


Add config entry for Met.no

Description:
This PR adds a config flow for the Met.no weather integration.
Related issue (if applicable): fixes https://github.com/home-assistant/home-assistant/issues/24511
Pull request with documentation for home-assistant.io (if applicable): N/A
Example entry for configuration.yaml (if applicable):

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

If the code communicates with devices, web services, or third-party tools:

[x] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[x] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.

dear all,
I have configured the platform met. Since 0.95.0 i get the information that the platform is deprecated.
The documentation does not give any hint about that.
What does that mean?
File reference:  homeassistant/components/met/weather.py line 36

Please open an issue if you suspect a bug. If you need help please use our help channels:
https://home-assistant.io/help/#communication-channels
Merged PRs should not be used for support or bug reports. Thanks!


Release a new version compatible with Micronaut 3.0

Please follow the instructions in https://github.com/micronaut-projects/micronaut-core/issues/5607 and update that core issue with the information related to the upgrade.

As part of new version remove the Oracle Cloud Vault support that is now part of oracle cloud module.


python3Packages.weconnect: 0.37.1 -> 0.37.2, python3Packages.weconnect-mqtt: 0.30.1 -> 0.30.2

Motivation for this change
https://github.com/tillsteinbach/WeConnect-python/releases/tag/v0.37.2
The required oauthlib release is only available in staging.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

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

4 packages built:

python310Packages.weconnect
python310Packages.weconnect-mqtt
python39Packages.weconnect
python39Packages.weconnect-mqtt


Revert "XdsClient: First steps toward a ResourceType abstraction (#28…

…143)"
This reverts commit 64b2061907ee448bc055bd84cf06c2c7b42badfb.
This is possible causing problems in the import

#28254 fixes the problem, so that can probably be merged instead of this revert.


sile: 0.14.4 → 0.14.5

Minor upstream release with no relevant build system changes. See upstream release notes.

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

1 package built:

sile


change the expected package versions to be consistent with the package versions in the container instead of local computers

Done!


Multi-camera support: camera can be selected with serial number. Topics/nodes/TF names composed with camera base name.

Now the camera base name can be passed via launch file and a particular camera can be selected by passing the serial number in the launch files. Topics and TF frames are also renamed according to the camera base name.

Hi,
I added this functionality and some a bunch of other modifications to the devel branch. I hope it is working for you.


French Content issue in the Corps tab

Config: Patient, Male, Age 18 - 24, body-Organes sexual
Shows two different bubbles for the same heading "Prévenir les infections transmissibles sexuellement (ITS)". Can be just one with content managed by age.
excel rows: 10
Config: Clinicien, Femme/Homme, Age 54, body-Bone
https://osteoporosis.ca/wp-content/uploads/Quick_Reference_Guide_October_2010.pdf Hyperlink missing
excel row: 70

First issue to be done only if requested by Dr. Cleo

The second issue fixed. Please test on the latest update.

The issue is fixed. Tested and it works as expected.

Thanks, Ajay. Closing issue :)