Fix last month not being displayed if last date is selected in DateRangePicker

Description
The condition to set the _initialMonthIndex is missing the case if the lastDate is the same as initialDate, so if the lastDate is selected, then the last month will not be visible to the user at launch.

Current
With this fix

Related Issues
I've just found it.
Tests
I added the following tests:

A test which sets the initialDateRange to be the same as the lastDate supplied to the DateRangePicker. The last month should be visible in this case.
A test which sets the initialDateRange to be the same as the firstDate supplied to the DateRangePicker. The first and part of the second month should be visible in this case.
A test which does not set the initialDateRange. The month from the given currentDate should be visible in this case.

Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I signed the [CLA].
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change.

@darrenaustin Thank you for the review! I've addressed all of your comments, so please take a look when you have the time.
Also, looks like the customer_testing-linux CI failed because of a timeout. How do I trigger it to re-run the test?

Also, looks like the customer_testing-linux CI failed because of a timeout. How do I trigger it to re-run the test?

You should be able to click on the "Details" link and there should be a re-run link next the job. Perhaps this only shows up for maintainers though? I went ahead and restarted it. I will keep an eye on this and make sure it completes. Thanks again.

@darrenaustin Yeah I saw that button once I logged in to CirrusCI. Thank you so much for taking the time to review this!


[TS] Regression in handling enums

The following OpenAPI description:
openapi: 3.0.3
info:
  title: Apicurio Registry API [v3]
  version: 3.0.x
  description: Apicurio Registry.
  license:
    name: Apache 2.0
    url: https://www.apache.org/licenses/LICENSE-2.0
paths:
  "/admin/rules":
    get:
      responses:
        '200':
          content:
            application/json:
              schema:
                "$ref": "#/components/schemas/RuleType"
          description: The list of names of the globally configured rules.
      description: 'List global rules

        '
components:
  schemas:
    RuleType:
      description: ''
      enum:
      - VALIDITY
      - COMPATIBILITY
      - INTEGRITY
      type: string
      example: VALIDITY

Generates invalid code:
export const RulesRequestBuilderRequestsMetadata: RequestsMetadata = {
    get: {
        uriTemplate: RulesRequestBuilderUriTemplate,
        responseBodyContentType: "application/json",
        adapterMethodName: "sendAsync",
        responseBodyFactory:  createRuleTypeFromDiscriminatorValue,
    },
};

where createRuleTypeFromDiscriminatorValue is not defined in any of the generated files.
Found here.

I'm trying to understand "what to fix" here and I'm a bit confused.
Enum values are handled pretty much as primitive types, but this assumption cannot be used in the deserialization factory.

is not a PrimitiveTypesForDeserialization
ParseableFactory needs to return a Record

Do we want to encode Enums closer to classes or should we enable them to be used more like primitives?

Thanks for raising this @andreaTP
I believe due to the IParsable constraint on classes sent by the various SendXXX in the request adapter, the handling of enums should be handled by the sendPrimitiveAsync and the relevant methods updated to check for the enum type. In a future version of Kiota where we make breaking changes to the IRequestAdapter we could consider probably move this out to a sendEnum method and have the enum level handling on its own.
I suspect this scenario affects other languages as well as I'm not aware of a scenario that we've encountered an Enum was returned as the result object.

Thanks for the feedback @andrueastman !
Unfortunately, it's not yet clear to me what should be done to fix this issue.
Either:

the type signature of responseBodyFactory should change to include Enums (and I'm not sure how)
Enums should be treated like objects and we should generate the create{XYZ}FromDiscriminatorValue

Taking a deeper look at TS abstractions, it looks like like Parsable is an empty interface.  Which means the Parsable constraint assumed doesn't hold here. So, we may use the second option here, but this may be different for other languages.
@andreaTP Any chance you can share the link to the original openApi description for the client in the PR? I'd like to compare behaviors in different languages first.  Unfortunately, when I take a look at the GO client generated, it seems to suggest the path returns a collection and not a single value.
https://github.com/Apicurio/apicurio-registry/blob/33f348c600dbef7b2679a8e553079604eb1b3b18/go-sdk/pkg/registryclient-v3/admin/rules_request_builder.go#L90 (This would be resolvable using a sendCollectionOfEnumsValue method missing in TS abstractions that Go uses)

You are correct, the original OpenAPI definition uses a collection, I removed it as the problem can be reproduced.
This is the original description for both Go and Typescript

Taking a look across languages, looks like enums should ideally be handled separetely from either objects or primitives.
The TS abstractions is missing the sendEnum and sendEnumCollection methods that are present in other languages such as GO and java.
https://github.com/microsoft/kiota-abstractions-go/blob/a9e5a330669021f32fe021ff0e0671446e30c8d4/request_adapter.go#L26
https://github.com/microsoft/kiota-java/blob/082b0697e806823711f23abe6faa956ac10d91f4/components/abstractions/src/main/java/com/microsoft/kiota/RequestAdapter.java#L102C67-L102C85
Dotnet seems to have mapped enums to primitives(I suspect adding the methods later on would have been a breaking change. Created issue for it at https://github.com/microsoft/kiota-abstractions-dotnet/issues/199)
As this change is not breaking in TS, we should probably update the requestAdapter interface so that it includes these methods, and update the generator for enum handling, then have the relevant method call the getEnumValue/getCollectionOfEnumValues methods on the received response.

Is this work already scheduled on your side?

Thanks for the wrap-up @baywet , appreciated, I'm going to have a pretty busy schedule in the next weeks, so let's see who comes first to this one.

Can we set this to "never-stale"? We can close when completed.


feat(): send store article ID request after user editing the article

feature

store post id to firestore when the user edit or publish a post

Feature

send store article id request after editing article

@lls0308abc  fixed


Add tests for cache types

[x] add tests.yaml workflow
[x] redis
[x] memcached
[x] simple cache
[x] file system
[ ] uwsgi

Just a heads up, make sure these tests are rock solid, we had to remove the cache tests when they were still in Werkzeug because they randomly failed constantly in unrelated PRs and caused confusion.

Hey, thanks for the heads up. I remember seeing something about how the previous test suite was flaky on Werkzeug history when writing #13 so I have been doing some tests on my side and taking my time with this PR (this is why I haven't merged it along with #24). That being said, the current test suite will fail when testing entry expiration time without #26 since non-expired entries that fit idx % 3 == 0 will be removed. So we can either hold this PR until I'm done with #26 or remove the expiration time test, merge this now and submit a third PR later after merging #26 with the missing expiration tests. What do you think @davidism ?

Let's see what happens with #26

I have just finished testing with #26 and #31 changes applied and all tests are passing consistently on my env with tox for py36, py37 and py38. #31 was also necessary since memcached was not initializing entries to -delta/delta (as described in the PR) so increment/decrement tests were failing.

Uwsgi tests were throwing a SystemError: <class 'DeprecationWarning'> returned a result with an error set on execution of any uwsgi command using their python-plugin. The deprecation warning is question was DeprecationWarning: PY_SSIZE_T_CLEAN will be required for '#' formats. That seemed like a Python/C-layer problem in uwsgi, so I found that issue36381 introduced a deprecation warning about an upcoming Python C API change. The meaning of PY_SSIZE_T_CLEAN can be found in Python/C strings-and-buffers docs, but to sum up:
All buffers "#" variants of formats s#, y#, etc. can have either int or Py_ssize_t as type for their length argument. Which one is used is decided by defining the said PY_SSIZE_T_CLEAN macro. This behaviour will change in a future Python version to only support Py_ssize_t and drop int support so the python docs advise to always define PY_SSIZE_T_CLEAN.
The DeprecationWarning was introduced in py3.8 and it should work fine for lower releases but this might get troublesome in the future. Here is the respective CPython PR that introduced the changes in case anyone is interested.
We can use pytest warning capture  to get around this for now by passing -W default::DeprecationWarning so the warning still shows but will not be converted to an error. Something will need to be done in the future to avoid a possible break with py38 and higher (assuming the issue isn't handled at the C layer by Uwsgi) so i'm not sure what our next step should be here, WDYT @davidism ?

Add it to the filterwarnings pytest option in setup.cfg.

uwsgi cleans expired entries on a separate sweeper thread and so far I have found no documented way of triggering the cleaning. This might make expiration related tests specially tricky.


Setup Dap

Currently exists a minimal configuration of dap.
I need to read the dap documentation and applied a debugger to

Javascript/Typescript
C++
Rust

blocked by #21


Change the default importer to use an endpoint with a known api

We should add the option of being able to use a generic endpoint that provides a well known protocol to import data without having to deploy any connector.

Duplicate of #26


Enrich ImapFolderAgent payload

This adds message_id and rfc822 (optional) to the payload format of ImapFolderAgent.
A Message-Id value is certainly useful for identifying a mail, and the raw "RFC822" data can be used for further processing or copying to another storage/mailbox.

@dsander Considering that a raw mail is not always a valid UTF-8 byte stream, should we encode it in some way, like Base64?

@knu Tricky I guess it depends what one wants to do with the raw data. How are you using the feature? If we would base64 encode it could not really be used by anything else in Huginn, right?

Sorry for the delay...  I pass raw email data to Unix commands like sendmail/procmail/formail, so I have no problem if the data is encoded in base64.  I just need to pipe it through a decoder like base64(1) and openssl(1).

I guess it could be an option, woudln't we run into a ruby exception when the email contained invalid UTF-8?

Emails are often in a "legacy" (non-UTF-8) encoding and JSON is not capable of storing binary data, so I believe this feature, to expose raw data as is, was a mere mistake in the first place.  I guess I could pretend I'm the only user and go fix it. 🤣

Oh I see, you only want to base encode the raw data, yeah that makes sense 😄


Can it be made a more transparent drop-in for ndarray?

I'm trying to see how far I can take my ~50 GB hdf5 datasets through my processing pipeline before explicitly creating an ndarray. My pipeline uses a framework (Neuropype) that puts the ndarray in a container along with some metadata and makes extensive use of ndarray functions returning views. I think I could get a lot further in this framework with my h5 dataset if a wrapper class like DatasetViewh5py reimplemented some of those ndarray functions that return views.
Are there any downsides to renaming lazy_transpose to transpose?

I'm also considering a custom implementation of squeeze.
numpy users expect flatten() to return a copy so probably not that one.
What about min, max, argmin, argmax, any and all when an axis is provided? Even though all of the data will have to be loaded into memory eventually, it can be done sequentially row-by-row (or column-by-column) so maybe this will help avoid out-of-memory errors. I am fairly new to processing data cached-on-disk so I'm hoping others with more experience can tell me if this is a bad idea from the outset.

Hello, implementing squeeze is easy. Dropping dimensions is already happening with int indexing. If we have a dataset we want to squeeze, we can just pass it as dsetview.lazy_slice[:,0,:,:]. e.g. dsetview.lazy_slice([0 if i==1 else slice(None) for i in dsetview.shape])
It's possible to assign dsetview.transpose to dsetview.lazy_transpose for one's use case, since h5py datasets do not have a transpose method, but if there's a different underlying class it'd override its transpose method.
I'm not too sure about integrating a general lazy reshape. Perhaps when looking to reshape at chunk boundaries, in certain cases. PRs are welcome, but a general reshape working along with lazy transpose and slicing might get too complicated.
To implement min function and others, the data has to be read, or sequentially processed perhaps in chunks. Have you looked into dask?
Also, for transposing data in place fastremap maybe of help if memory constrained.

I spent much of the last week implementing lazy reshape. And yes, it was complicated. I ended up rewriting about 90% of the code. Though I got it working, and I tested quite a few combinations of transpose and reshape and slice, I'm sure some there are some corner cases where it will fail.
After I've had more time to play with it I'll push my changes to my fork, but it's such a huge change that I doubt a PR is what you want. I'll post here again when I feel it's ready for other eyes and you can let me know how you feel.
I took a quick look at dask but it didn't seem to meet my use case. I should look again.
Cheers!

@cboulay .T works as a lazy transpose

I'm not quite ready to say it's suitable for a PR, but I'll post the main commit for reference in case I get otherwise distracted and someone wants these features without waiting for me to clean it up more:
https://github.com/cboulay/lazy_ops/commit/1ef59e69a31453198710f2d5a561d6ce6ca20412
As I was working on it, I thought it would have been better to use strides as the object's state variable to manage transpose & reshape rather than the solution I came up with. I'm sure someone cleverer than myself could get it to work and it would be more elegant than my solution and probably much more flexible.


ADD: [Feature] paste expiry

Hey Sadra!
I've added a new field called expires_in to the Snippet model, which represents expiry days! This PR also includes snippet template badges and everything needed for #48 to be resolved.

Ex: if a models has expires_in value of 7 it means it will be expired in 7 days.

Thanks. :)


[release/8.0] Added ability to resolve target port

Backport of #3305 #3371 and #3372 to release/8.0
/cc @davidfowl
Customer Impact
Dapr was broken in preview5 because of the endpoint / port refactoring. This changes how we process and expose target ports to correct that break. It refactors APIs that can't be changed once we ship 8.0, so it falls under "API fit and finish".
Testing
New unit tests added.
LocalOnly Node app test now passes locally
Manual testing
Risk
Medium - the original change has already broken Node apps
Microsoft Reviewers: Open in CodeFlow

Approved in chat


Enanchment in CF Generation

Hi, I created this pull request to give some hints on CF generation @gaugup.
Regarding Random, although there is very clear and fast, finding combinations between feature sampling and substitution is unclear. The Loop inside, instead of gradually replacing more features actually in your code, only replaces one feature as :
            selected_features = np.random.choice(self.features_to_vary, (sample_size, 1),  replace=True)
1 should be replaced by num_features_to_vary and then .loc instead of .at.
This method is slower but certainly more complete and still faster than Genetic/KDtree (I have deliberately left it commented out for you).
If you want to leave a single variation, I suggest changing .at to ._get_value in the replacement for faster access.
As far as genetic is concerned, in the case of datasets with many features, a random initialization is very slow and seems never to end. For this reason, I suggest increasing the population of the KDtree initialization (which is also lowering the initialization time a lot). In addition, I recommend switching to a binary search in the case of requests for a large number of CFs.

Thanks @giandos200 for this PR. I executed all the gates. Could you please examine the failures and re-submit to make all the tests and linting pass? It looks like your PR has a lot of changes which are out of scope of the performance improvement. It will be great if you could clean all this and send out a commit focusing just on the perf improvements.
Regards,

It should be ok now, @gaugup . Maybe I have an older version because I have never changed the imports.


Double clicking an inserted link doesn't opens the edit popup in the latest version

If you have added a link in the editor and if you try to edit it by double clicking. The edit popup of link doesn't appears. Please confirm, it was working fine until we upgraded to 5.1.5 version

Sorry, I cannot reproduce. Can you give a more specific description? Text-enabled plugins work fine for me, both when editing inline and from the change plugin modal.

Sorry, I cannot reproduce. Can you give a more specific description? Text-enabled plugins work fine for me, both when editing inline and from the change plugin modal.

If you check the link which is an inbuilt inline which doesn't come under the CMS plugins. Can you check this once
In the image the blue text is a normal link which is highlighted from the mouse hover. When we double click on this blue text the editor doesn't pops up but comes when we right click on the blue text and click edit
Earlier on double clicking the blue text opens the link popup
It is happening for cms text enabled plugins but not this link.

OK, now I understand. I can confirm the behaviour.
Will need to take a look to identify the source of the behavior.

Thanks @fsbraun. Please keep us updated thanks.

I can confirm it started working now.

@fsbraun I have one more question around the html field. If we use the html field and need CMS plugins over there. Can it be possible in any way.
I checked the TextPlugin implementation which implements a Texteditor widget in which plugins are initialised using get_plugins method.
Is there a way we can give the text enabled plugins inside the htmlfield?

No.

@fsbraun Can we have this released?


Question for multiple roles

Question: Paired with your user management extension, is there a simple way to enable multiple role selection on the create/edit form. The default showing is 1, and I can't find a trait or similar listed to enable multiple roles on the blade templates.
I noticed the form didn't have:
multiple="multiple"

Hello,
No there is not, you have to alternative options:

Create a role with the permissions you want and do checks on permissions.
Create a role with the levels and check on the level.

Currently, there are no shared roles.
Thank you,


Two npm packages for this plugin.

Describe the bug
This plugin appears twice in npm which effects homebridge-config-ui-x since it also appears twice there which is confusing.
To Reproduce
Steps to reproduce the behavior:
Search for "tuya web" in homebridge-config-ui-x and identify the two identical packages, one by @milo526 and the other by @basdelfos.
Expected behavior
One one npm packages for the same plugin.
Additional context
https://www.npmjs.com/package/homebridge-tuya-web
https://www.npmjs.com/package/@milo526/homebridge-tuya-web
Should be using https://www.npmjs.com/package/homebridge-tuya-web exclusively.

I'm planning on deprecating the non-namespaced variant once I'm happy with the namespaced variant.
This is no bug with the library and can easily be prevented by just installing one of them.
Both of the packages should be using the same code. Using both of the packages at them same time is actively discouraged since they might slightly interfere (ie they share their caches).

Okay great. I'm glad you're aware of it and it's being depreciated.


Tesseract read nothing in tif files

I use Tesseract in OpenKM to read tif documents, but when execute reads nothing.

Someone have any idea?
Thanks

Please respect guidelines for posting issue: use tesseract user forum for asking questions/support.
From details you provided nobody is able to reproduce problem. Nobody can help you if you do not provide testing image.

Good morning, I think this is a bug, because from old version of tesseract works fine!
I attach I file to test.
Please if this comment not write to correct site please respon me.
Thanks.
test.zip

Tesseract is using for opening image leptonica
I used leptonica-1.80.0 (May 16 2020, 13:24:45) [MSC v.1916 LIB Release x64], and the message is: Error in pixReadFromTiffStream: old style jpeg format is not supported

Solution is: use supported input image.


Patternlab and PHP 8.1?

i am trying to upgrade PHP version of pattern lab to work with PHP 8.1. So far this is what I am getting.
Problem 1
- doctrine/collections is locked to version v1.4.0 and an update of this package was not requested.
- doctrine/collections v1.4.0 requires php ^5.6 || ^7.0 -> your php version (8.1.13) does not satisfy that requirement.
Problem 2
- doctrine/collections v1.4.0 requires php ^5.6 || ^7.0 -> your php version (8.1.13) does not satisfy that requirement.
- pattern-lab/core v2.9.0 requires doctrine/collections 1.4.0 -> satisfiable by doctrine/collections[v1.4.0].
- pattern-lab/core is locked to version v2.9.0 and an update of this package was not requested.

Seems like this is a known issue.
https://github.com/pattern-lab/patternlab-php-core/pull/176


chore(Python) : add Prime Number checker algorithm

PR Checklist:

[x] My submission is formatted according to the guidelines in the contributing guide
[x] My addition is on refer on the language README.md file
[x] My addition does not have a spelling problem
[x] My submission has a proper and user-friendly description of the algorithm
[x] My submission has the time complexity of the algorithm
[x] My submission has sample input-output of the program (NOT FOR PYTHON)

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[x] New algorithm
[ ] Optimization in previous algorithms
[ ] Code style update
[ ] Refactor
[ ] Documentation
[ ] Other, please describe:

Briefly describe the changes in this PR

Other information:

Hi, @Arsenic-ATG ! Please review.

What about edge cases like 0 and 1 ?

Updated!

Please merge @ming-tsai


Bug Solved

/* /index.html 200 // This code solve the netlify hosted web page reload error.
lazy, suspense // Lazy loading feature

Good work @SubhamB2003

Thank You


Fresco WebP dependency causes build error

Description
I want to support animated webp images on my app. Following this documentation, I added this line on the build.gradle dependencies block:
implementation 'com.facebook.fresco:animated-webp:3.1.3'
implementation 'com.facebook.fresco:webpsupport:3.1.3'

When running npx react-native build-android --mode=release, this error showed up:
> Task :app:minifyReleaseWithR8 FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:minifyReleaseWithR8'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.R8Task$R8Runnable
   > Compilation failed to complete

Steps to reproduce

Add Fresco dependencies for WebP support
Run npx react-native build-android --mode=release
It seems like proguard fails

React Native Version
0.75.4
Affected Platforms
Build - Windows
Output of npx react-native info
System:
  OS: Windows 10 10.0.19045
  CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  Memory: 1.95 GB / 15.85 GB
Binaries:
  Node:
    version: 20.14.0
    path: C:\Program Files\nodejs\node.EXE
  Yarn: Not Found
  npm:
    version: 10.8.1
    path: C:\Program Files\nodejs\npm.CMD
  Watchman: Not Found
SDKs:
  Android SDK: Not Found
  Windows SDK:
    AllowAllTrustedApps: Disabled
    Versions:
      - 10.0.18362.0
IDEs:
  Android Studio: AI-241.15989.150.2411.11948838
  Visual Studio:
    - 16.4.29806.167 (Visual Studio Community 2019)
Languages:
  Java: 17.0.8
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.75.4
    wanted: 0.75.4
  react-native-windows: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found

Stacktrace or Logs
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:minifyReleaseWithR8'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.R8Task$R8Runnable
   > Compilation failed to complete

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

BUILD FAILED in 46s
510 actionable tasks: 19 executed, 491 up-to-date

info 💡 Tip: Make sure that you have set up your development environment correctly, by running npx react-native doctor. To read more about doctor command visit: https://github.com/react-native-community/cli/blob/main/packages/cli-doctor/README.md#doctor

error Failed to build the app.
Error: Command failed with exit code 1: gradlew.bat app:bundleRelease
    at makeError (C:\Users\Vincent\Desktop\Lahelu\Codebase\Client\node_modules\execa\lib\error.js:60:11)
    at module.exports.sync (C:\Users\Vincent\Desktop\Lahelu\Codebase\Client\node_modules\execa\index.js:194:17)
    at build (C:\Users\Vincent\Desktop\Lahelu\Codebase\Client\node_modules\@react-native-community\cli-platform-android\build\commands\buildAndroid\index.js:68:22)
    at Object.buildAndroid [as func] (C:\Users\Vincent\Desktop\Lahelu\Codebase\Client\node_modules\@react-native-community\cli-platform-android\build\commands\buildAndroid\index.js:60:10)
    at Command.handleAction (C:\Users\Vincent\Desktop\Lahelu\Codebase\Client\node_modules\@react-native-community\cli\build\index.js:118:23)
    at Command.listener [as _actionHandler] (C:\Users\Vincent\Desktop\Lahelu\Codebase\Client\node_modules\commander\lib\command.js:482:17)
    at C:\Users\Vincent\Desktop\Lahelu\Codebase\Client\node_modules\commander\lib\command.js:1283:65
    at Command._chainOrCall (C:\Users\Vincent\Desktop\Lahelu\Codebase\Client\node_modules\commander\lib\command.js:1177:12)
    at Command._parseCommand (C:\Users\Vincent\Desktop\Lahelu\Codebase\Client\node_modules\commander\lib\command.js:1283:27)
    at C:\Users\Vincent\Desktop\Lahelu\Codebase\Client\node_modules\commander\lib\command.js:1081:27

Reproducer

Screenshots and Videos
No response

Solution: add these lines on your proguard-rules.pro
-dontwarn com.facebook.imagepipeline.cache.AnimatedCache
-dontwarn com.facebook.imagepipeline.cache.AnimationFrames
-dontwarn com.facebook.imagepipeline.nativecode.WebpTranscoder


Overview section of Home page is still in Dark mode when switched to Light mode

Describe the bug
Plan overview in Home page is still in Dark Mode when changed to light mode.
To Reproduce
Steps to reproduce the behavior:

Go to 'Hope Page'
Switch to Light mode
Observe the overview section where plan details is shown
The section is still in Dark mode

Expected behavior
Should be in Light mode
Screenshots

Desktop (please complete the following information):

OS: [Mac]
Browser [chrome]
Version [14.6.1]

hey @SahSantoshh , i find this issue interesting can i start working on this issue?

Hi @Bugbuster2004,
It would be better id we can have a fix. @chavda-bhavik it would be better if you suggest how we should deal with this issue.

@Bugbuster2004 @SahSantoshh I just want to remove light mode. Would you be interested?

It's lot of hassle and we analysed, no one is using light mode 😢

Sure @SahSantoshh @chavda-bhavik  i would be interested to do this


Hide client secret in settings

Treat the client_secret a bit more like a password.

[x] Use a password field to display
[x] After it's set, don't send the secret back to the browser via ajax/render/etc

The input field is now type="password".
Once the secret is set, a link with text "Change client secret" displays instead of the field and its value. When clicked, this link displays a password input, allowing users to change it if necessary.


Fix rust docs link

What type of PR is this?
/kind documentation
What this PR does / why we need it:
The create has been renamed so we should adapt the docs link as well.
Which issue(s) this PR fixes:

None
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

None

/lgtm


comments: update the comments of ConfigFiles of dfget

Signed-off-by: Starnop<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
fix the comments mistake of the filed ConfigFiles of dfget.
Ⅱ. Does this pull request fix one issue?

None.
Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
None.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

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

@@            Coverage Diff             @@
##           master     #475      +/-   ##
==========================================
+ Coverage   61.85%   61.99%   +0.14%
==========================================
  Files          72       71       -1
  Lines        3489     3481       -8
==========================================
  Hits         2158     2158
+ Misses       1192     1184       -8
  Partials      139      139

Impacted Files
Coverage Δ

dfget/config/config.go
91.66% <ø> (ø)
:arrow_up:

supernode/daemon/mgr/cdn_mgr.go

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 4f81c30...4848e30. Read the comment docs.

LGTM


Refurbish 2d-array to (table|json|csv) converters

Introduce a more reusable module for formatting 2d-array data matrices to various formats, such as:

rows: minimal formatting, just rows printed after each other (currently analogue to how CodeChecker checkers) output
table: libcodechecker.util.print_table
dictlist: zip (the list-to-tuple, not the archiver) the "header" row and each "data" rows into a list of dict objects
json: the dictlist in JSON format

dictlist_to_twodim is the inverse of dictlist.

Some of these functions might appear unused as of now, they are getting used in features that I'm introducing later. The reason for this PR is to tighten the scope of features added.

The general idea is that the user should not get any exceptions just some error message which is easy to to understand.

The end user (who is using CodeChecker) will not get any error messages because of this module.
The user (as in, the user code, client code, who uses output_formatters) will not get any error messages if the the person who writes the client code writes it in a way that it calls the methods in a way that they should be called.
Also, an error message which was borderline possible if calling to print_table (the predecessor of twodim_to_table) in a bad way (let's say the header is 3 column but every row is only 2 column) was index out of range which was updated to one of the rows contain different columns than the rest.

Ok, I see. I just did not remember that we check the choices given by the user in the argument handler.


Add CSR SpGEAM

This PR adds support for sparse matrix-matrix addition (spgeam) for CSR matrices.
It can be executed via Csr::apply(Scalar, Identity, Scalar, Csr).
The algorithm only works correctly on (column-)sorted matrices, as it's basically a merge between the rows from both matrices.
The PR also removes special treatment for zeros in advanced spgemm.
This partially addresses #555

I would say so, cuSPARSE and hipSPARSE use variations of the name. MKL uses csradd instead, but they also call their SpGEMM csrmult*

That's already present in Ginkgo, as a workaround for hipSPARSE's missing advanced spgemm from a few versions ago

I added a bit of documentation to the Csr LinOp so the SpGEMM and SpGEAM are not hidden to the users.


Add confusion matrix

This PR adds the confusion matrix metric. Some flake errors forced me to change two small type checks.

Actually looks like the doctests are failing. Did you test if the docstring example result match reality?

It should be good now :)

Sorry for all the noise with the commits. After some testing, I could pinpoint the issue of different string representations in Windows vs Ubuntu. E.g.
Ubuntu
{'confusion_matrix': array([[1, 0, 1],\n       [0, 2, 0],\n       [1, 1, 0]])}\n

Windows
{'confusion_matrix': array([[1, 0, 1],\n       [0, 2, 0],\n       [1, 1, 0]], dtype=int64)}\n

An alternative would be to just print the shape or sum of the confusion matrix, but this loses a bit of the point. This is also a bit confusing because other metrics such as mean_iou or mse don't face this issue.

Ok - the solution was to use ellipsis so it works with or without dtype. Let me know if this is ok. I also changed the Actions workflow so that if the ubuntu test fails, the windows one keeps running. This will consume more resources per workflow run, so let me know if I should revert that part - it would have been useful to identify this bug much faster.

Thanks for fixing it. Looks all good!


Migrate Hive connector to new table layout API

Other than David's comments, it looks good

@martint  Do you want to take another look before merge?

looks good

Merged #3475


Refactor NamespaceQuota and NamespaceMetadata in tenant spec

closes #369

@MaxFedotov please, make sure to commit the single YAML installer too, you can generate it using make installer


Release notes for 0.4

Make sure to mention this as the upgrade path:
cp ~/.llm/log.db "$(llm logs path)"

https://github.com/simonw/llm/compare/0.3...392f865636aa18f3d2e2360757962e9f5409455d

Changelog now lives here: https://llm.datasette.io/en/latest/changelog.html

Improved display of error messages from OpenAI. #15

Continue previous chat
You can now use llm to continue a previous conversation with the OpenAI chat models (gpt-3.5-turbo and gpt-4). This will include your previous prompts and responses in the prompt sent to the API, allowing the model to continue within the same context.
Use the new -c/--continue option to continue from the previous message thread:
llm "Pretend to be a witty gerbil, say hi briefly"

Greetings, dear human! I am a clever gerbil, ready to entertain you with my quick wit and endless energy. How can I make your day brighter today?

llm "What do you think of snacks?" -c

Oh, how I adore snacks, dear human! Crunchy carrot sticks, sweet apple slices, and chewy yogurt drops are some of my favorite treats. I could nibble on them all day long! As a gerbil, I know the importance of a healthy and balanced diet, but I also believe in indulging in some delicious snacks every now and then. After all, life is too short to not enjoy the little things.

The -c option will continue from the most recent logged message.
To continue a different chat, pass an integer ID to the --chat option. This should be the ID of a previously logged message. You can find these IDs using the llm logs command.

Need to talk about the new location of log.db and how to upgrade to it, and mention the schema changes - and the llm logs --truncate option.

New llm logs --truncate option (shortcut -t) which truncates the displayed prompts to make the log output easier to read.

Documentation now spans multiple pages and lives at https://llm.datasette.io/ #21

New mechanism for storing API keys
API keys for language models such as those by OpenAI can now be saved using the new llm keys family of commands.
To set the default key to be used for the OpenAI APIs, run this:
llm keys set openai

Then paste in your API key.
Keys can also be passed using the new --key command line option - this can be a full key or the alias of a key that has been previously stored.
See link-to-docs for more. #13
. #13

Default llm chatgpt command has been renamed to llm prompt. #17
Removed --code option in favour of new prompt templates mechanism. #24
Responses are now streamed by default, if the model supports streaming. The -s/--stream option has been removed. A new --no-stream option can be used to opt-out of streaming.  #25
The -4/--gpt4 option has been removed in favour of -m 4 or -m gpt4, using a new mechanism that allows models to have additional short names.


Bug fixed on Stack Over Flow Problem for XML nodes with no attributes

Fixes issue #2

Actually we are facing same issue which you mention you fixed. I install nuget, and give xml file which contain same child elements and it start throwing stack over flow exception. I try to find out your code in master branch but failed. can you help me where to get this latest code to fix this error?

I looked over this commit, and it doesn't really fix the bug (it mitigates the issue, but introduces another bug, which is actually more common). It seems to me that the structure of the code doesn't allow for a simple fix to the stack overflow bug.


Notfound breaks unit test suite

I am currently using mike:mocha-package and driver-package respondly:test-reporter for unit testing.
When I run my test suite and  I have a notFound route it breaks the test reporter because the router doesn't know the route and calls the notFound handler.
FlowRouter should be disabled when unit testing. It only makes sense for integration testing.
I can work around it with the appended code. But it would be nicer if this is handled in FlowRouter itself.
var drive_path_prefix = runtimeSettings.get('public.drive_path_prefix', '/');

if (MochaWeb.testOnly || !mocha) {
    FlowRouter.notFound = {
        action: function() {
            var path = FlowRouter.current().path;
            var re = new RegExp('^' + drive_path_prefix + '/');

            if (path.match(re)) {
                throw Meteor.Error(404);
            } else {
                location.href = location.origin + path;
            }
        }
    };
}

We can't decide whether it's testing or not.
But there's a way to stop flow-router. May be you can do it for your app.
See: https://github.com/meteorhacks/flow-router#flowrouterwait-and-flowrouterinitialize
I think that's the best thing to do.

@arunoda Yeah it's kind of hard to tell. So I've just moved the notFound route to the application itself. That way it doesn't get initialised in the unit test suite.

So. I'm gonna close this now.


added requirements.txt file for better automation

I am using puppet to build out a utility box and adding this file helps with automating the install.  Otherwise, 'pip install -r requirements.txt' does the job nicely.

Going to revise this to allow for multiple domain checks.


[WIP] Parser improvements

Implement #48, Parser Improvements.
This is still a work in progress and the APIs are not yet finalized.
Initial check-in has functional support for import from strings, streams, and files.  Further, it supports normal, public, and weak imports.

It has been a while since this has been touched. Keep it open?

Feel free to reopen when ready for #48 work.

I'll try and check this later next week, I managed to get round import not being processed by using a recursive function when I create types so that imports are processed in hierarchical order by the type lookup map.

Theres also another issue I have in Falanx where I require the type in the proto definition to be in topological order, it would be nice if the parser did this too...

@7sharp9 Let me know if you want this merged in for a 0.7.0.

@ctaggart To be honest Ive not had the time to test it yet.

update: I still really want this honest!  Just not had time to try it yet :-(

I updated build versioning in #101 and merged it in. Hopefully that will make it easier for you to work on. Current failure is a unit test:
Error Message:
 System.IO.FileNotFoundException : riak_kv.proto
Stack Trace:
   at Froto.Parser.Parse.fetchFromFile(IEnumerable`1 dirsList, String filename) in C:\projects\froto\Parser\Parser.fs:line 805
   at Froto.Parser.Parse.loadFromFile(String fileName, IEnumerable`1 dirsList) in C:\projects\froto\Parser\Parser.fs:line 819
   at TestParser.FileImport.Resolve File Import() in C:\projects\froto\Parser.Test\TestParser.fs:line 1334
Total tests: 118. Passed: 117. Failed: 1. Skipped: 0.
Test Run Failed.

Closing this in favor of a PR specific to processing import statements.

Sounds good. Should we delete the branch?

Done


Store off-chain note details in ProvenTransaction's output_note_details

Now that ProvenTransaction contains output note details, we could use it to store off-chain note data. As noted by Bobbin this has a couple of implications, namely that we could remove a struct from the client and also that sensitive data should be stripped in order not to be leaked when communicating with the node.
Didn't see this tracked anywhere so I didn't want it to be missed, let me know otherwise.

I think to take advantage of this on the client, we'll need to make a few other changes on the miden base side - but I'll need look into this in a bit more detail.

Might be solved by #539

Closed as resolved by https://github.com/0xPolygonMiden/miden-base/pull/673

@igamigo - since this is not merged, we may be able to refactor things a bit on the client side to get expected output notes directly from ExecutedTransaction object.


Implement orchestrated firewall distance configuration.

References https://github.com/metal-stack/metal-networker/issues/97.

Has to be tested in a real environment, but we can already review.

I think we can try this out in our test environment, review and merge this already. It does not hurt when the firewall-controller does not yet support it.
In the mini-lab during rolling update:
❯ k get fw,fwset,fwdeploy,fwmon -o wide                                                                                04:00:40
NAME                                                      PHASE      MACHINE ID                             LAST EVENT           DISTANCE   AGE   SPEC VERSION   ACTUAL VERSION
firewall.firewall.metal-stack.io/default-firewall-12e19   Running    e0ab02d2-27cd-5a5e-8efc-080ba80cf258   Phoned Home          0          13m   latest
firewall.firewall.metal-stack.io/default-firewall-d8a9e   Creating   2294c949-88f6-5390-8154-fa53d93a3313   Booting New Kernel   3          65s   latest

NAME                                                 REPLICAS   READY   PROGRESSING   UNHEALTHY   DISTANCE   AGE
firewallset.firewall.metal-stack.io/firewall-12dfb   1          1       0             0           0          13m
firewallset.firewall.metal-stack.io/firewall-d8a81   1          0       1             0           3          65s

NAME                                                  REPLICAS   READY   PROGRESSING   UNHEALTHY   AGE
firewalldeployment.firewall.metal-stack.io/firewall   1          0       1             0           19m

And for scaling:
❯ k scale fwdeploy firewall --replicas 4
firewalldeployment.firewall.metal-stack.io/firewall scaled

❯ k get fw,fwset,fwdeploy,fwmon -o wide
NAME                                                      PHASE      MACHINE ID                             LAST EVENT    DISTANCE   AGE     SPEC VERSION   ACTUAL VERSION
firewall.firewall.metal-stack.io/default-firewall-a74a9   Creating                                                        2                  latest
firewall.firewall.metal-stack.io/default-firewall-a74be   Creating                                                        2                  latest
firewall.firewall.metal-stack.io/default-firewall-a74cd   Creating                                                        1                  latest
firewall.firewall.metal-stack.io/default-firewall-d8a9e   Running    2294c949-88f6-5390-8154-fa53d93a3313   Phoned Home   0          4h52m   latest

NAME                                                 REPLICAS   READY   PROGRESSING   UNHEALTHY   DISTANCE   AGE
firewallset.firewall.metal-stack.io/firewall-d8a81   4          1       0             3           0          4h52m

NAME                                                  REPLICAS   READY   PROGRESSING   UNHEALTHY   AGE
firewalldeployment.firewall.metal-stack.io/firewall   4          1       0             3           5h11m

Looks good already, would it make sense to validate the #replicas to not exceed a certain maximum ?


React-Dom Broken

<EMAIL_ADDRESS>

Thanks — was related to peerDependencies. Fixed now


Identifying peerings

It would be nice if you could add steps to determine what peering a subscription have.

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

ID: 77567f6e-945d-22d5-50c4-1fd0b4226465
Version Independent ID: 761d0238-7929-db9d-e750-265f7e415663
Content
Content Source
Service: expressroute

@ctahok Thank you for the valuable feedback. I forwarded your feedback to the content team.

@ctahok  Thanks! Looking into it!

#in-process

I've updated the doc to include a link to view ckt and peering information for your subscription. It should publish today or tomorrow. #please-close

#please-close


Don't attempt to read password on stdin if stdin isn't a tty

Checklist:

[ ] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[ ] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[ ] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them:

Closes #6681

Even if stdin is a tty, I think we still might want to just skip this prompt. I believe @lk86 was saying that this prompt gets hidden from users by other logs and that users end up not seeing the prompt. I'll defer to @lk86 to confirm what we should/shouldn't do.

We're always instructing people to either use an environment variable or -block-producer-password, so if we don't have a password it should always fail and point people to CODA_PRIVKEY_PASS + -block-producer-password.

Updated. I've added a new function that only checks the environment variable, and changed the calls from the daemon command's sartup to go through that.
The client/accounts/etc. commands that require a password will still prompt if needed, and I don't this this causes us the same issues, so leaving the old functionality available to be used there.


Can not working in Laravel 8

I use Laravel 8 and receive error.

not working in laravel 8

Yes, it is not supporting laravel 8. We will update soon

Looking forward to it!

Looking forward to it!

Thanks for your attention, sir

Yes, it is not supporting laravel 8. We will update soon

Thanks, Sir. I appreciate it.

Any update on when 8.0 will be supported

I also wait for the laravel 8 support. Appreciate your work! Thanks

I also wait for the laravel 8 support. Appreciate your work! Thanks

I'm waiting as well. Thanks for the great package!

You can use Geocoder and PHP or MySQL commands to make similar things.
I had to do it that way.

Any update on Laravel 8 support? Thanks

Any update on Laravel 8 Support, sir?

You can use Geocoder and PHP or MySQL commands to make similar things.
I had to do it that way.

How to do it?

not support laravel 8 yet.  any update on package soon ? thank

Yes, it is not supporting laravel 8. We will update soon

I worke on Resturant mobile app , so that i need this package to install in my project to finish Map part, thanks @farhanwazir

nothing yet?

how about now?

Still no update??

Any update on Laravel 8 ?

You don't need this pakcage anymore, you can use https://github.com/bradcornford/Googlmapper to get similar results


Release v0.16.2

[Fix] Fix Typedoc generation: use tsconfig.json generated for the lib.
[Fix] Write source map for .mjs files
[Fix] Copy sources to _src when publishing a lib (#87).
[Internal] Restore continuous deployment of documentation.

Codecov Report

Merging #90 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #90   +/-   ##
=======================================
  Coverage   66.88%   66.88%
=======================================
  Files          38       38
  Lines         912      912
  Branches       99       99
=======================================
  Hits          610      610
  Misses        232      232
  Partials       70       70

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 1d6de06...5235151. Read the comment docs.


Bug: Can't compile with the implement feature

Which crate is this about?
windows
Crate version
v0.34.0
Summary
Using the implement feature causes several compiler errors.
Toolchain version/configuration
Default host: x86_64-pc-windows-msvc
rustup home:  C:\...\.rustup

installed toolchains
--------------------

stable-x86_64-pc-windows-msvc
beta-x86_64-pc-windows-msvc
nightly-x86_64-pc-windows-msvc

installed targets for active toolchain
--------------------------------------

aarch64-pc-windows-msvc
wasm32-unknown-unknown
wasm32-wasi
x86_64-pc-windows-msvc

active toolchain
----------------

stable-x86_64-pc-windows-msvc (default)
rustc 1.59.0 (9d1b2106e 2022-02-23)

Reproducible example
fn main() {
    println!("Hello, world!");
}

Crate manifest
[dependencies.windows]
version = "0.34.0"
features = [
    "alloc",
    "implement",
    "Win32_System_WinRT",
]

Expected behavior
No compiler errors.
Actual behavior
There are 90 errors, but they're all variations on these:
error[E0658]: trait bounds other than `Sized` on const fn parameters are unstable
   --> C:\...\.cargo\registry\src\github.com-1ecc6299db9ec823\windows-0.34.0\src\Windows\Win32\System\WinRT\impl.rs:939:63
    |
939 |     pub const fn new<Identity: ::windows::core::IUnknownImpl, Impl: IWeakReferenceSource_Impl, const OFFSET: isize>() -> IWeakReferenceSo...
    |                                                               ^^^^
    |
    = note: see issue #57563 <https://github.com/rust-lang/rust/issues/57563> for more information

error[E0658]: function pointer casts are not allowed in constant functions
   --> C:\...\.cargo\registry\src\github.com-1ecc6299db9ec823\windows-0.34.0\src\Windows\Win32\System\WinRT\impl.rs:951:98
    |
951 | ...:new::<Identity, OFFSET>(), GetWeakReference: GetWeakReference::<Identity, Impl, OFFSET> }
    |                                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = note: see issue #57563 <https://github.com/rust-lang/rust/issues/57563> for more information

Additional comments
No response

Ah, I missed that the implement now requires nightly.

Sorry about the confusion. I have pinned #1523 to make this more discoverable. Won't be long now. 😉


Bugs in pokemon_catch_worker?

Expected Behavior
def _get_catch_config_for(self, pokemon):
    catch_config = self.config.catch.get(pokemon)
    if not catch_config:
        catch_config = self.config.catch.get('any')
    return catch_config

Actual Behavior
def _get_catch_config_for(self, pokemon):
    catch_config = self.config.catch.get(pokemon)
    if not catch_config:
        catch_config = self.config.catch.get('any')
    if not catch_config:
        catch_config = {}
    return catch_config

Other Information
It should return the setting given by "any" instead of return {} for a "unspecified" pokemon.
BTW, I don't know how to do pull request or commit things, any one can help me out? Many thanks!

fork -> edit -> submit PR (pull request)

Thanks for helping!


VC doesn't debug python files

Hi!
I can't debug python files on my VC, I recently uninstall and re install it, but the issue still present.
My current lauch.json settings is:
"version": "0.2.0",
    "configurations": [

        {
            "name": "Python: Current File",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal"
        }
    ]

I don't know what's happening.

/needsMoreInfo including version, platform and which Python extension(s) you have installed.

/extPython

Hi @gjsjohnmurray @weinand , I add the information requested.
Visual Studio Code
Version: 1.56.2 (system setup)
Commit: 054a9295330880ed74ceaedda236253b4f39a335
Date: 2021-05-12T17:13:13.157Z
Electron: 12.0.4
Chrome: 89.0.4389.114
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19042

Extensions:
Pylance by Microsoft: v2021.6.0
Python by Microsoft: v2021.5.842923320
Jupyther by Microsoft: v2021.6.832593372
All versions all the latest.


Package.json version always 0.0.0

The version of the ruby gem always gets up dated to Major.Minor.Patch.xxx but the version set in package.json is always 0.0.0. It would be nice if this version were updated to the same as the ruby gem.

Solved


Inference script for LLama-factory after RLHF training?

@hiyouga
Where we can find inference scripts for LLama-factory after RLHF training. I trained using SFT, RM and RLHF using mistral-7B as base checkpoint.. Now after training RLHF kindly specify how to run inference using the checkpoints developed. Please kindly do the needful

If you follow the instruction in README to perform the SFT+RLHF training, the inference script would be
python src/cli_demo.py \
    --model_name_or_path path_to_llama_model \
    --adapter_name_or_path path_to_sft_checkpoint,path_to_ppo_checkpoint \
    --template default \
    --finetuning_type lora

@hiyouga  thanks for ur reply


Invalid float native values retrieved in the summary data of Workbooks using a live data source

I have a Workbook that uses float and double values, and I want to retrieve its summary data with the Embedding API.
Float values are properly displayed in the Worksheet itself:

Downloading the data in Tableau also displays the expected values:

Using the Embedding API to retrieve the underlying data also produces the expected values:

Using the Embedding API to retrieve the summary data produces invalid native values:

I unfortunately can't share the Workbook used since it only happens for a live datasource: we no longer experience the issue if we switch to a data source extract.
It looks like the value we retrieve is the Java float approximation of "1.3" rounded to the 16th decimal:

@florent-guinard  In Embedding API, How do we get data summary? can you please share code snippet ?

We're not able to reproduce the issue on Tableau Cloud 2022.4 (we were using Tableau Server 2022.3). I'll try to confirm that the issue no longer happens on Tableau Server 2023.1 and close the issue.

Closing due to age and the fact it appears to be resolved / no longer reproducible.


CCH22-1: Adjust the snippets/artifacts/defineRepository sample for configuration cache

Checking directly the local variable repoNames as it is done in the kts version

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test and merge

No milestone for this PR. Please set a milestone and retry.

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

Your PR is queued. See the queue page for details.

There's merge conflict between your PR branch and base branch. Please fix it and try again.

Updated the branch with master 🤞

@bot-gradle test and merge

OK, I've already triggered a build for you.


Bug found on initializing text attribute

I  found a bug, when you try to use "\n" escape in "text" attribute when you want to initialize your Halo object at first.
Just try Defining a Halo object like this
spinner = spinner = Halo({'text': 'Loading \n', 'spinner': 'dots'})
and then if you start it, its like you put it in a while loop and then start.

Accepted. We should strip line endings from text before rendering it.


Fix mesh_xsection

Plane.mesh_xsection was a bit of a mess, and in particular it sometimes returned a "Polyline" that was actually a disordered set of lines, not an end to end connected ring. And it relied on a hack passing edges to bodylabs.mesh.topology.connectivit.remove_redundant_verts instead of faces and relying on a bug in it that fails to verify that the "faces" are actually Nx3. So. This is closer to a correct algorithm. And now with some real tests. And wrote it as Plane.mesh_xsections which always returns a list of Polylines, one for each connected component. Then wrote a Plane.mesh_xsection that mangles that result back into the jammed together single Polyline that it used to return.
@jbwhite can you test that this still works with measurements?
@eerac just FYI.

@jbwhite Hold off on reviewing this for a moment -- it may not work with real meshes.

@algrs OK -- did try to run one measurement using it, and it did not complete (did not troubleshoot why).

Yep, there was a problem that was causing it to never terminate on a large and complex mesh. Rewrote a bunch more of it. Give it a read; most of it should make some sense at this point.

@algrs When testing the values returned for this vs master, I'm seeing the same values for vertices but in a different order (on this branch they appear sorted by the first column).
I've attached an output of results -- used pdb.set_trace() to inspect the values:
mesh_xsection_results.txt

The verts being in a different order is expected. Sorted is a bit weird.
They should be ordered in a ring around the body...
On Mon, May 22, 2017 at 4:45 PM Joseph White<EMAIL_ADDRESS>wrote:

@algrs https://github.com/algrs When testing the values returned for
this vs master, I'm seeing the same values for vertices but in a
different order (on this branch they appear sorted by the first column).
I've attached an output of results -- used pdb.set_trace() to inspect the
values:
mesh_xsection_results.txt
https://github.com/bodylabs/blmath/files/1020169/mesh_xsection_results.txt
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bodylabs/blmath/pull/4#issuecomment-303215148, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AALh1OkarOYRQIDfeoqp684E1kUwUSC-ks5r8fPwgaJpZM4Ng75P
.

--

aw

These values look pretty reasonable, like what this bug fix would be
expected to change. You can show the lines in a mesh viewer and see if the
resulting rings are sane or not.
On Mon, May 22, 2017 at 4:45 PM Joseph White<EMAIL_ADDRESS>wrote:

@algrs https://github.com/algrs When testing the values returned for
this vs master, I'm seeing the same values for vertices but in a
different order (on this branch they appear sorted by the first column).
I've attached an output of results -- used pdb.set_trace() to inspect the
values:
mesh_xsection_results.txt
https://github.com/bodylabs/blmath/files/1020169/mesh_xsection_results.txt
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bodylabs/blmath/pull/4#issuecomment-303215148, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AALh1OkarOYRQIDfeoqp684E1kUwUSC-ks5r8fPwgaJpZM4Ng75P
.

--

aw


changing relative urls to absolute urls in README

I noticed that some of the links weren't working because they were being read as relative URLs rather than absolute URLs.

Thanks, merged in 4b4f76d.


python312Packages.pynrrd: 1.0.0 -> 1.1.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.pynrrd is: Simple pure-Python reader for NRRD files
meta.homepage for python312Packages.pynrrd is: https://github.com/mhe/pynrrd
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.1.1 with grep in /nix/store/kz6p4j2cd2gmbh4ljzsx6gipdazppyfi-python3.12-pynrrd-1.1.1
found 1.1.1 in filename of file in /nix/store/kz6p4j2cd2gmbh4ljzsx6gipdazppyfi-python3.12-pynrrd-1.1.1

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

python311Packages.pynrrd
python312Packages.pynrrd

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/kz6p4j2cd2gmbh4ljzsx6gipdazppyfi-python3.12-pynrrd-1.1.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.pynrrd https://github.com/r-ryantm/nixpkgs/archive/a4cd579e4670cf1d5c1bcc8a35347b3ae77d5b30.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/a4cd579e4670cf1d5c1bcc8a35347b3ae77d5b30#python312Packages.pynrrd

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/kz6p4j2cd2gmbh4ljzsx6gipdazppyfi-python3.12-pynrrd-1.1.1
ls -la /nix/store/kz6p4j2cd2gmbh4ljzsx6gipdazppyfi-python3.12-pynrrd-1.1.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 4 packages built:

python311Packages.pynrrd
python311Packages.pynrrd.dist
python312Packages.pynrrd
python312Packages.pynrrd.dist

Maintainer pings
cc @bcdarwin for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

nptyping dep was dropped in 1.1.0.

Superseded by #360003.


FOV Modification for Image Reconstruction

Hi,
First of all, thank you for KomaMRI, it's an amazing tool!
I was trying to do some custom simulations with Koma on the EPI_SE sequence with different custom phantoms. After the simulations, I also wanted to look at some reconstructions. As my phantoms are fairly small (20x20 spins), the resulting image reconstruction is fairly zoomed out. I figured it's only a problem of FOV, but I do not understand where to change the FOV for this reconstruction. Where should I change it? In the raw signal params (reconSize)? Does that suffice? Could you please point me to the object attribute I need to change? I am new to Julia.
I have not changed any acquisition points in the resulting signal, the kspace is also the same. Thank you for the help!
Best,
Andrei

Hi,
I think you should just crop the image. In a way, changing the FOV requires changing the sequence.
Best,
Guillermo

Hi sorry for the delay, I was at ISMRM in Singapore. Can you give a little more detail to reproduce the problem?
In theory, as @gsahonero says, the FOV is encoded in the sequence. One way of scaling the FOV of the sequence is to multiply by a diagonal matrix:
julia> using KomaMRI

julia> seq = PulseDesigner.EPI_example()
Sequence[ τ = 62.846 ms | blocks: 204 | ADC: 101 | GR: 205 | RF: 1 | DEF: 5 ]

julia> seq.GR[:, 3]
3-element Vector{Grad}:
 Grad(51.0578 mT, 0.2 ms, ↑0.1021 ms, ↓0.1021 ms) # <------------------ BEFORE SCALING
 Grad(0.0 mT, 0.2 ms, ↑0.1021 ms, ↓0.1021 ms)
 Grad(0.0 mT, 0.2 ms, ↑0.1021 ms, ↓0.1021 ms)

julia> S = [2.0 0.0 0.0; 0.0 2.0 0.0; 0.0 0.0 1.0]
3×3 Matrix{Float64}:
 2.0  0.0  0.0
 0.0  2.0  0.0
 0.0  0.0  1.0

julia> seq2 = S * seq # <---------------------------------------------- APPLY LINEAR OPERATOR
Sequence[ τ = 62.846 ms | blocks: 204 | ADC: 101 | GR: 205 | RF: 1 | DEF: 5 ]

julia> seq2.GR[:, 3]
3-element Vector{Grad}:
 Grad(102.1157 mT, 0.2 ms, ↑0.1021 ms, ↓0.1021 ms) # <------------------ AFTER SCALING
 Grad(0.0 mT, 0.2 ms, ↑0.1021 ms, ↓0.1021 ms)
 Grad(0.0 mT, 0.2 ms, ↑0.1021 ms, ↓0.1021 ms)


Problem with connection to VirtualBox by Genymotions

Hi. I have last Genymotion installation:
Genymotion: 2.12.2
Genymotion emulator: Custom Phone - 6.0.0 - API 23 - 768x1280
VBox: 5.2
Adb running inside the emulator on localhost:5555. SimpleAdbClient works fine. But Jadb with the same input and environment hangs up. Tryed other local and external IPs without any effect.
I also using Jadb in vanila emulators on port 5037 without any problem.
Thx.

Thanks for reporting this. Can you post the output of adb devices here? 🤔

Thanks @TheQmaks for clarifying this use case. Let's close for now.


Select measure on the network is not correct

Dear all,
What could possibly wrong if when I click the From measure and To Measure, the X is far away from where I click.

Thanks and regards,
Brenda.

Hi all,
Both widgets do not open in the portal for me

.


Safer norm

Description
Resurrection of #14240 to solve #14126. With an extra argument of norm for specification of output data type.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[x] #14240
[x] out_dtype argument for norm
[x] Corresponding changes to backend code

Comments
@szha

cc @ptrendx

Thanks for your contributions @haojin2. Can you also look into the CI failures ?
@mxnet-label-bot Add [Operator, Backend]

@eric-haibin-lin


Blog Articles Not Showing On Index

I'm just trying to get my bearings for my middleman-blog and want to have my site index file list the most recent 5 articles on the site. While navigating to the url's specifically seem to work, using this code snippet, it's always returning nothing.
%ul
  - blog.articles[0...5].each do |article|
    %li= link_to article.title, article

My config.rb looks like:
activate :blog do |blog|
  blog.prefix = "blog"
  blog.layout = "layout_project"
end

My articles are in a folder called "blog" in this directory structure:
config.rb
source
  index.haml
  blog
    test.md
    test-article.md

I thought it might have to do with :directory_indexes but I activated after the :blog active portion in config.rb like the documentation says.

Nevermind.  So instead of "test.md" I need "2012-01-01-test.md".


[WIP] Execute stream callbacks directly when executor is the current event …

…loop.
TBH, haven't been able to reason through whether this is a correct change, but tests seem fine, and the benchmarks show that we need to do something along these lines to optimize StreamMessage performance for the standard case where everything happens on a server event loop thread. Curious what you think.
Benchmarks (due to synchronization overhead, only high values of num are relevant). Probably about 1.5-2x better stream performance in practice.
After:
Benchmark                                                    (num)   Mode  Cnt       Score       Error  Units
StreamMessageBenchmark.defaultStreamMessage_notJmhEventLoop      3  thrpt   20  238282.293 ± 11059.030  ops/s
StreamMessageBenchmark.defaultStreamMessage_notJmhEventLoop      5  thrpt   20  223524.752 ±  5595.936  ops/s
StreamMessageBenchmark.defaultStreamMessage_notJmhEventLoop     20  thrpt   20  170606.288 ±  4851.481  ops/s
StreamMessageBenchmark.defaultStreamMessage_notJmhEventLoop    100  thrpt   20   78263.884 ±  1800.286  ops/s
StreamMessageBenchmark.defaultStreamMessage_notJmhEventLoop   1000  thrpt   20   10792.808 ±   216.650  ops/s

Before:
Benchmark                                                    (num)   Mode  Cnt       Score      Error  Units
StreamMessageBenchmark.defaultStreamMessage_notJmhEventLoop      3  thrpt   20  222284.597 ± 6456.982  ops/s
StreamMessageBenchmark.defaultStreamMessage_notJmhEventLoop      5  thrpt   20  215316.254 ± 6570.347  ops/s
StreamMessageBenchmark.defaultStreamMessage_notJmhEventLoop     20  thrpt   20  173076.370 ± 5739.022  ops/s
StreamMessageBenchmark.defaultStreamMessage_notJmhEventLoop    100  thrpt   20   60886.142 ± 1018.291  ops/s
StreamMessageBenchmark.defaultStreamMessage_notJmhEventLoop   1000  thrpt   20    6617.666 ±  118.178  ops/s

I have split off a PR to first solve the reentrancy problem in the non-executor case which seems required by the spec.

@anuraaga Time to rebase :-)

@trustin Rebased :)

Thanks a lot, @anuraaga !


OpenCV debug mode VideoCapture with file is broken

I've installed OpenCV 3.4.0 from vcpkg with opencv[ffmpeg] (without ffmpeg, it doesn't work either).
In Release and RelWithDebInfo mode, both camera and reading from files (e.g. an .avi file) is fine.
In Debug mode however, reading from the camera works, but not reading from the avi file.
    std::string inputvideo("vid.avi)";
    cv::VideoCapture cap;
    if (inputvideo.empty()) {
        cap.open(0); // no file given, open the default camera
    }
    else {
        cap.open(inputvideo);
    }
    if (!cap.isOpened()) {
        std::cout << "Couldn't open the given file or camera 0." << std::endl;
        return EXIT_FAILURE;
    }

cap.isOpened() fails in this scenario.
The problem also does not occur if I build OpenCV by myself (outside of vcpkg) and also not with the binary package from opencv.org.
It also occured on OpenCV 3.3.x in vcpkg.

@ras0219-msft, is there anything we can do? I don't seem to be the only one with this issue, pointing to a problem in the vcpkg OpenCV package. And the camera input not working is quite a big issue.

Ok, so I am actually unable to reproduce this issue (it works in debug for me). Let me share my setup:
// main.cpp
#define NOMINMAX
#define WIN32_LEAN_AND_MEAN
#include <cstdio>
#include <opencv2/opencv.hpp>

int main(int argc, char** argv)
{
    if (argc < 2)
        return -1;

    std::string inputvideo(argv[1]);

    cv::VideoCapture cap;

    if (inputvideo.empty()) {
        cap.open(0); // no file given, open the default camera
    }
    else {
        cap.open(inputvideo);
    }
    if (!cap.isOpened()) {
        std::cout << "Couldn't open the given file or camera 0." << std::endl;
        return EXIT_FAILURE;
    }

    getchar();
    return 0;
}

# CMakeLists.txt
cmake_minimum_required(VERSION 3.10)

project(main CXX)

add_executable(main main.cpp)

find_package(OpenCV REQUIRED)
include_directories(${OpenCV_INCLUDE_DIRS})
target_link_libraries(main PRIVATE ${OpenCV_LIBS})

I installed opencv:x64-windows, built my program above with the vcpkg toolchain, and tried to load the SAMPLE.avi from [1]. This fails in debug and release, because it needs ffmpeg.
I then installed opencv[ffmpeg]:x64-windows and rebuilt the program. It still didn't deploy the ffmpeg dll (this is a bug we need to fix!) but that caused failures in both debug and release. Once I manually deployed the opencv_ffmpeg340_64.dll to the output folder for my application (found via vcpkg owns _ffmpeg), both debug and release ran correctly.
I suspect you might have some other OpenCV DLLs available elsewhere in your path, which are getting loaded and cause issues only in debug mode, but that's just a guess.
[1] http://www.technical-recipes.com/2011/displaying-avi-video-using-opencv/

I can confirm that it now works in all three modes - Release, Debug and RelWithDebInfo, and for camera as well as video files.
The key was indeed to copy & paste opencv_ffmpeg340_64.dll over to the build folder. I did not do that before, which caused it to fail.
Thank you very much again for helping to investigate. Finally back to using vcpkg :-)


construction, electronics and textile demonstration ontologies

construction

[ ] A number of data properties of which domains are Product and/or ProductObject could be moved to product module. For instance, hasProductDescription, hasProductionDate.
[ ] Contaminant concept and isContaminated data property could  be generalised and thus moved to product module or ...
[ ] ProductQuality also seems to be a general concept that can be moved to product module, then in specific demo ontology, one can create sub concepts such as ConstructionProductQuality .
[ ] TreatmentPolicy and PolicyOnTreatment are overlapped.

electronics

[ ] batchNumber data property can be moved to resourceODP.
[ ]  Some data properties of processes can be moved to process module. For instance, dateOfProduction, dateOfInstallation, instructionOfMaintenance, instructionOfRepair, instructionOfUseAndAssembly.
[ ] Some data properties of location can be moved to a general location module.
[ ] Detailed compliance can be moved to product module. For instance REACHCompliance (also modelled in Textile).

textile

[ ] Print is a sub-concept of Constituent. PrintStuff is a sub-concept of Matter.
[ ] The hasProperty object property has DataSheet as domain and Statement as range. It also has sub-properties but have specific ranges which do not seem to be statements. For instance, hasWaterProperty has WaterProperty as range.

moved to #287


Buble tea

Buble

Closing this due to lack of content/context, but to feel free to reopen if you have a comment or question.


Package update

updates webpack from v1 to v5
updates babel from v5 to v7 to work with the new webpack
updates all other dev-dependencies
updates all dependecies (exept jStat - see #6 for that!)
removes unused dependencies (html-webpack-plugin, webpack-dev-server)

npm run test is still "green" :tada:


pep8 compliancy.

Currently the code is not pep8 compliant, this commit fixes the issue.

Thanks @alexex! Merged, included in new release 0.1.2.


Send emails when a user receives a comment/subscription etc

Usually I'm really against this feature but if users want to turn it on it's fine.

You might want to set a delay so that there are more comments right after one another they can be gathered in to one e-mail.

Maybe. I think I'd just implement it in the most simple way, and then if a lot of people ask for the delay feature I'll implement it. That's kind of my approach to software, build it in response to real world data lol.


fix(docs-ui): doc list can't toggle

close https://github.com/dream-num/univer-pro/issues/2469

Pull Request Checklist

[ ] Related tickets or issues have been linked in the PR description (or missing issue).
[ ] Naming convention is followed (do please check it especially when you created new plugins, commands and resources).
[ ] Unit tests have been added for the changes (if applicable).
[ ] Breaking changes have been documented (or no breaking changes introduced in this PR).

还可以复现
2024_9_18 20_14_11 video.webm


Convert CI to GitHub Actions

Task
Convert CI to GitHub Actions
Context
Travis is removing its free tier for OSS projects, so this should be built with GitHub Actions instead, which is not going to add additional cost.
I would expect this to be one of the easier projects to convert given that Docker isn't used in the build.
See also:
https://github.com/mvdan/github-actions-golang
https://github.com/actions/create-release
https://github.com/actions/upload-release-asset
https://github.com/alexellis/arkade/issues/263
https://github.com/alexellis/k3sup/issues/279

Can I try this?

Yes please use the approach from k3sup and read the contribution guide before starting. Each commit needs to be signed off (not GPG)

Ok, thanks alex


Improve error handling when background services are not initialized

Often during the early stages of development, people might just try to run pytest, and not pylint every time.
This makes it hard to identify when they forget to call super().__init__() when deriving from BackgroundService.
This PR improves error handling in BackgroundService to provide a more meaningful error and a solution to an otherwise hard to debug issue.

Before
Traceback (most recent call last):
  File "/home/sahas/.local/lib/python3.11/site-packages/frequenz/sdk/actor/_background_service.py", line 237, in __del__
  File "/home/sahas/.local/lib/python3.11/site-packages/frequenz/sdk/actor/_background_service.py", line 129, in cancel
AttributeError: 'SocActor' object has no attribute '_tasks'
super().__init__()

After
Traceback (most recent call last):
  File "/home/sahas/code/sdk/ev-power-distribution/src/frequenz/sdk/actor/_background_service.py", line 244, in __del__
  File "/home/sahas/code/sdk/ev-power-distribution/src/frequenz/sdk/actor/_background_service.py", line 132, in cancel
  File "/home/sahas/code/sdk/ev-power-distribution/src/frequenz/sdk/actor/_background_service.py", line 264, in _assert_initialized
AssertionError: SocActor instance is not initialized. Make sure to call `super().__init__()` in your __init__() method.

Isn't the missing call to super()  detected by flake8 or pylint?

Isn't the missing call to super() detected by flake8 or pylint?

did you read the description?

did you read the description?

Haha, yes, but I guess I missed the first line, sorry.
I'm not sure it is worth adding the runtime cost of checking if it was initialized everywhere just to get a slightly better error message in early stages of development.
I would like more opinions on this one, @matthias-wende-frequenz @Marenz @daniel-zullo-frequenz ?

I'm not sure it is worth adding the runtime cost of checking if it was initialized everywhere just to get a better error message in early stages of development.

it is an assert that doesn't allocate and runs only when a background service is starting up or stopping, so it is not really a runtime cost.
but it makes development easy especially for external developers who might not always want to start with repo config, etc, but might just want to start coding,  and setup the tooling later, because that's what we've been showing in the demos as well.
In such a scenario, it is just annoying, and people would be more inclined to think the SDK is broken because the error message is totally unhelpful.

only when a background service is starting up or stopping,

I mean that's not exactly correct, looking at the diff it's also running on wait and is_running and a few more.
My feeling is that it's still okay as those methods are unlikely to be in a critical path and more used to start/stop things as well.

In any case, this will probably go away when we fix #826, so I'm fine with merging it. I will still give it a bit more time before the approval to see if @mathias-baumann-frequenz or @daniel-zullo-frequenz also have any opinion on the topic.

I agree the current patch is fine for this particular scenario but it shouldn't be considered as a good/general practice, otherwise all the attributes of the parent class would need to be checked as well.
And we should encourage non-frequenz users to use linters, the ones that can be configured in Editors/IDEs are already quite good.

And we should encourage non-frequenz users to use linters, the ones that can be configured in Editors/IDEs are already quite good.

a lot of people just use flake8, and that doesn't detect this issue.  And pyright (the LSP server I think most people use with editors) doesn't detect them either.

hmm Pylint detected in VS code if not calling super().__init__(name=name)

Just for the records, pyright also detects it:

interesting, I guess my pyright is just badly configured then.


AsciinemaPlayer as npm in Next.js

I have some issues in using AsciinemaPlayer as an npm package to a Next.js app.
This works just fine though when importing the npm package within a basic React app, but not in Next.js.
Whenever I try to
import * as AsciinemaPlayer from 'asciinema-player';
I got this response from Next.js

SyntaxError: Cannot use import statement outside a module.

Can anyone advice here on how to overcome this? Thanks.

I'm not sure how you fixed it, but I resolved this same issue (Next.js 12.1) this way:
useEffect(() => {
  ;(async function () {
    const AsciinemaPlayerLibrary = await import('asciinema-player')
    const currentRef = ref.current
    AsciinemaPlayerLibrary.create(src, currentRef, asciinemaOptions)
  })()
}, [src])

Using Next's dynamic import to pull the library in at runtime.

In the end, this is how I did it too.
Thanks for sharing the solution here, this might come in handy for other wandering souls :)


[Task]: Show horizontal scrollbar if the widgets are overflowing

The widgets will overflow horizontally once the widget cannot occupy in the available space. We need to show a horizontal scrollbar so that users can still use the overflowed widgets.

A PoC is created in https://github.com/appsmithorg/appsmith/pull/20878
Closing this for now since we haven't taken any decision on whether we need a scrollbar or not.


add applicability checks to fusion solver

This PR resolves a problem with #1889

@bghimireamd could you add a test to this fix? It could be in a separate PR due to urgency.

@bghimireamd  Thanks for the quick turnaround, it looks good to me. I cant approve however, since I am the author of the PR.
cc @junliume


fix: Deal with both $ref and properties in the same schema

In Draft 4-7, $ref behaves a little differently. When an object contains a $ref property, the object is considered a reference, not a schema. Therefore, any other properties you put in that object will not be treated as JSON Schema keywords and will be ignored by the validator. $ref can only be used where a schema is expected.
source: http://json-schema.org/understanding-json-schema/structuring.html#id18

wip

I haven't run into this issue yet, closing this for now.


The newest version of the DLL released is missing the main file

Your newest release does not work because the Win32 file only has a debug option, if you could add the new non-debug one that would be great

https://github.com/Omega172/Crush-Crush-Cheat/releases/tag/V.0.410


Warning: a promise was rejected with a non-error: [object Array]

Working with native Promise i got this warning.
Warning: a promise was rejected with a non-error: [object Array]
If validation errors exists, onReject function receive an array of this errors. https://github.com/ctavan/express-validator/blob/master/lib/express_validator.js#L155
Can we define own "class" of error? ex. ExpressValidationErrors which will contain property ._list (array) of errors. And .all() will return this list.
req.asyncValidationErrors().catch(errors => {
  req.flash('errors', errors.all());
  renderEdit(res);
});

This is pretty annoying as it's littering my logs with warnings and useless warnings and stack traces.

I don't always have time to get to these, however, we are always open for pull requests!

hi , look at  links, i think it is the same issue. The problem is the validation of  instance "Error".
https://github.com/petkaantonov/bluebird/issues/990
https://github.com/petkaantonov/bluebird/commit/e77224c191dc8942eb27c6ea95dce8e3fec8a570

            .fail((xhr, err) => {
                let proxy = new Error();
                proxy.message = err || 'error is null';
                proxy.name = 'ajax error';
                reject(proxy);
            });

Final errors really need to be thrown.
That way we can just pass to it to next in our controllers and have a standardised error response.
// controller

// validate request
    return req.asyncValidationErrors()
      .then(() => {
        // do stuff
      })
      .catch(next)

And then ...
/* Error handlers */
app.use(function (err, req, res, next) {
  if (err instanceof ExpressValidationError) {
    return res.status(400).send({
      code: 'api.error.validation',
      errors: err.toJSON()
    })
  }
  next(err)
})

Hello guys!
When v3.0.0 gets released (soon, I promise!), you will have a few options to avoid this problem!
req.getValidationResult().then(result => result.throw()).then(() => {
  console.log("yay, worked!");
}, error => {
  console.log("oh noes, an validation error?? " + error instanceof Error);
  console.log(errors.all()); // prints the errors array just like you're used to in v2
});

...or, if you're okay dealing with validation errors without throwing them, you don't have to:
req.getValidationResult().then(result => {
  if (result.isEmpty()) {
    console.log("I got 99 problems but validation isn't one");
  } else {
    console.log("you better check your request params, bro!");
    console.log(result.array());
  }
});

For more information, please head to the readme.
I'll let everyone know when v3.0.0 gets released.

v3.0.0 released with the above API! 🚢


extend content "sharing" functionalities

At the moment, sharing functionalities are in the content sub menu "teilen"
Let's include:

Google Classroom
Facebook
Twitter
Mail

And may be, we should replace the sharing functionalities. E.g. like in Khan Academy (below the head line) : https://www.khanacademy.org/math/trigonometry/trig-with-general-triangles/solving-general-triangles/a/laws-of-sines-and-cosines-review

@simonkoehl this issue is outdated with the new design, right?


EchoRZXWeylDecomposition incompatible with BackendV2?

Environment

Qiskit version: 1.2.0.dev0+8f6714d
Python version: 3.8.19
Operating system: MacOs

What is happening?
Why trying to move the tests from Fake27QPulseV1 to GenericBackendV2 (see https://github.com/Qiskit/qiskit/pull/12660), I noticed that EchoRZXWeylDecomposition seems to fail very deeply in because len(cr_tones) == 1 and len(comp_tones) == 2 is not a possible condition in
https://github.com/Qiskit/qiskit/blob/61805c8e166800687aa64ef3bf8d7da7540f5f2f/qiskit/transpiler/passes/calibration/rzx_builder.py#L392__
How can we reproduce the issue?
from qiskit import QuantumRegister, QuantumCircuit
from qiskit.providers.fake_provider import GenericBackendV2
from qiskit.quantum_info import Operator
from qiskit.transpiler.passes import EchoRZXWeylDecomposition

backend = GenericBackendV2(num_qubits=27, calibrate_instructions=True, control_flow=True, seed=42)

qr = QuantumRegister(2, "qr")
circuit = QuantumCircuit(qr)
circuit.cx(qr[0], qr[1])

unitary_circuit = Operator(circuit).data

after = EchoRZXWeylDecomposition(backend.instruction_schedule_map)(circuit)

qiskit.exceptions.QiskitError: 'Schedule((0, Shi [...] is undefined pulse sequence. Check if this is a calibration for cross resonance operation."

Notice that the following works:
from qiskit import QuantumRegister, QuantumCircuit
from qiskit.providers.fake_provider import Fake27QPulseV1
from qiskit.quantum_info import Operator
from qiskit.transpiler.passes import EchoRZXWeylDecomposition

backend = Fake27QPulseV1()
qr = QuantumRegister(2, "qr")
circuit = QuantumCircuit(qr)
circuit.cx(qr[0], qr[1])

unitary_circuit = Operator(circuit).data

after = EchoRZXWeylDecomposition(backend.defaults().instruction_schedule_map)(circuit)

What should happen?
I think GenericBackendV2(num_qubits=27, calibrate_instructions=True, control_flow=True, coupling_map=[[0, 1], [1, 0], [1, 2], [1, 4], [2, 1], [2, 3], [3, 2], [3, 5], [4, 1], [4, 7], [5, 3], [5, 8], [6, 7], [7, 4], [7, 6], [7, 10], [8, 5], [8, 9], [8, 11], [9, 8], [10, 7], [10, 12], [11, 8], [11, 14], [12, 10], [12, 13], [12, 15], [13, 12], [13, 14], [14, 11], [14, 13], [14, 16], [15, 12], [15, 18], [16, 14], [16, 19], [17, 18], [18, 15], [18, 17], [18, 21], [19, 16], [19, 20], [19, 22], [20, 19], [21, 18], [21, 23], [22, 19], [22, 25], [23, 21], [23, 24], [24, 23], [24, 25], [25, 22], [25, 24], [25, 26], [26, 25]], seed=42) should work like Fake27QPulseV1, but maybe I'm setting something wrong.
Any suggestions?
No response

@nkanazawa1989 can you confirm it?

This looks like it might be related to #12834, as the above works with other BackendV2s (such as qiskit_ibm_runtime.fake_provider.FakeSherbrooke.


These cells, found in particular in GW1NZ-1, also have DFFs.

Signed-off-by: YRabbit<EMAIL_ADDRESS>

thanks :)


rust-analyzer goes into "error state" in rustc repository

To reproduce this problem, open the rustc repository in vsocde with rust-analyzer installed. After some time the "rust-analyzer" text in the status bar at the bottom turns into a barely readable dark-gray-on-blue with a warning triangle in front of it. Hovering that item shows "cargo check failed" followed by some cargo output ending in "...". No error is visible in that text (I did not find a way to copy-paste all that text). Running ./x.py check on the same code works just fine.
I have no idea what this "error state" means, though...
My workspace settings JSON to make RA work on rustc looks as follows:
{
    "rust-analyzer.checkOnSave.overrideCommand": [
        "./x.py",
        "check",
        "--json-output",
        "library/std"
        //, "compiler/rustc"
    ],
    "rust-analyzer.rustfmt.overrideCommand": [
        "./build/x86_64-unknown-linux-gnu/stage0/bin/rustfmt"
    ],
    "editor.formatOnSave": false,
    "files.watcherExclude": {
        "*rustc*/src/llvm-project/**": true,
        "*rustc*/build/**": true,
    },
    "files.exclude": {
        "src/llvm-project/**": true,
        "build/**": true
    },
}

"Rust Analyzer Client" output says
INFO [4/26/2021, 2:26:35 PM]: Extension version: 0.2.574
INFO [4/26/2021, 2:26:35 PM]: Using configuration {
  cargoRunner: null,
  runnableEnv: null,
  inlayHints: {
    enable: false,
    chainingHints: true,
    maxLength: 25,
    parameterHints: true,
    typeHints: true
  },
  updates: { channel: 'stable', askBeforeDownload: true },
  server: { path: null, extraEnv: null },
  trace: { server: 'off', extension: false },
  debug: {
    engine: 'auto',
    sourceFileMap: {
      '/rustc/<id>': '${env:USERPROFILE}/.rustup/toolchains/<toolchain-id>/lib/rustlib/src/rust'
    },
    openDebugPane: false,
    engineSettings: {}
  },
  assist: {
    importMergeBehavior: 'full',
    importPrefix: 'plain',
    importGroup: true
  },
  callInfo: { full: true },
  cargo: {
    autoreload: true,
    allFeatures: false,
    features: [],
    runBuildScripts: true,
    useRustcWrapperForBuildScripts: true,
    noDefaultFeatures: false,
    target: null,
    noSysroot: false
  },
  checkOnSave: {
    enable: true,
    allFeatures: null,
    allTargets: true,
    command: 'check',
    noDefaultFeatures: null,
    target: null,
    extraArgs: [],
    features: null,
    overrideCommand: [ './x.py', 'check', '--json-output', 'library/std' ]
  },
  completion: {
    addCallArgumentSnippets: true,
    addCallParenthesis: true,
    postfix: { enable: true },
    autoimport: { enable: true }
  },
  diagnostics: {
    enable: true,
    enableExperimental: true,
    disabled: [ 'unlinked-file', 'missing-match-arm' ],
    remapPrefix: {},
    warningsAsHint: [],
    warningsAsInfo: []
  },
  files: { watcher: 'client', excludeDirs: [] },
  hoverActions: {
    debug: true,
    enable: true,
    gotoTypeDef: true,
    implementations: true,
    run: true,
    linksInHover: true
  },
  lens: {
    debug: true,
    enable: false,
    implementations: true,
    run: true,
    methodReferences: false,
    references: false
  },
  linkedProjects: [],
  lruCapacity: null,
  notifications: { cargoTomlNotFound: true },
  procMacro: { enable: true, server: null },
  runnables: { overrideCargo: null, cargoExtraArgs: [] },
  rustcSource: null,
  rustfmt: {
    extraArgs: [],
    overrideCommand: [ './build/x86_64-unknown-linux-gnu/stage0/bin/rustfmt' ]
  }
}
INFO [4/26/2021, 2:26:35 PM]: PersistentState: {
  lastCheck:<PHONE_NUMBER>202,
  releaseId: 26923638,
  serverVersion: '0.2.565'
}
INFO [4/26/2021, 2:27:02 PM]: Using server binary at /home/r/.config/Code/User/globalStorage/matklad.rust-analyzer/rust-analyzer-x86_64-unknown-linux-gnu

Can you try setting rust-analyzer.cargo.runBuildScripts to false?

I did that, then reloaded the window, but behavior is still as described above.

@RalfJung you want
{
    "rust-analyzer.cargo.runBuildScripts": false,
    "rust-analyzer.procMacro.enable": false,
}

If you don't disable proc macros, we'll still run build scripts. The error message will be marginally better with #8670.
The UX about settings is unfriendly ( Part of the problem is that VS Code doesn't allow us to distinguish unset settings...

Yes, that does get rid of the error, thanks. :)
Is it expected that these features break when used in the rustc compiler workspace?

Yes at the moment. This features require tight integration with the build system. At the moment this is hard-coded to cargo check --workspace, which fails for me in the rustc repo. There's a desire to make that configurable, so that one can plug ./x.py check there, but we haven't done that yet.

(also, to give some more context -- rust-analyzer was in this partially-error state since we enabled proc macros by deafult a while ago. What changed is that we now actually report this error as bad good as we can :)


Heap is not set when mounting /conf in 3.2

I start neo4j 3.2 community with a docker compose file and mount a local directory to /conf. All settings in the neo4j.conf file are used except heap space. It is always set to 512M (shown in debug.log and when running CALL dbms.listConfig()).
Setting heap space through the environment variable works. Setting the page cache with the conf file also works.
docker-compose.yml
version: '2'
services:
  neo4j:
    image: neo4j:3.2
    volumes:
      - ./data:/data
      - ./conf:/conf
      - ./import:/import
    ports:
      - "7475:7474"
      - "7689:7687"

Maybe this is related to the issue #102


support K25

Support k25 plot size to shorten development cycle.

Multiple developers and users want this feature, myself included, but we'll need some more work on it.  My general plan is to have it be available only as a command line option, not in the configuration file, and to provide a strong warning when executing either plotman interactive or plotman plot.  I very much want to avoid people accidentally starting plotting k25s and then coming back a couple days later with 10TiB of k25s they have to delete.  :]

close


⚠ Fortnite has degraded performance

In be75d64, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1599 ms

Resolved: Fortnite performance has improved in 6571b94.


[resource manager] Trigger Sync all resource collection After successful registration

Once the storage backend is registered, we need to trigger sync_all to collect all resources.

/move sim


Docs rewritten in MkDocs

New child folder mkdocs contains the Cider User Guide rewritten as a MkDocs instance.

The revised and original content (both in MkDocs format) can be compared at
https://lambenttechnology.com/wireframes/cider.dev/
Comments indicate room for improvement. (Search for ISSUE to find connections to issues raised.) But I propose this qualifies as a sufficient improvement on what it replaces that it can be published.
The theme is Material for MkDocs, with the colour palette drawn from the 2024 Dyalog brand guidelines.
I propose next to work out

the GitHub CI workflow to generate GH Pages from the MkDocs source
use of the mike extension for version control

In the meantime I’ve excluded from the repo the generated HTML and included it here as a ZIP.
site.zip

Now visible at https://5jt.github.io/Cider/
Posted from my command shell with mkdocs gh-deploy.
Simple enough, but I want to get a CI workflow to recompile https://aplteam.github.io/Cider whenever commits to the docs are pushed here.