Currency fractions for ja, kr locale

In Korea, and in Japan, currencies does not used with fractions normally.
The Currincies does not written usually 1,000₩ not 1,000.00₩ and 1,000¥ not 1,000.00¥.
Yes, there's no coins for the fractions.
Only for the exact calculation fractions used like 1,000.11₩, 1,000.00¥.
There's may be the standards for this https://en.wikipedia.org/wiki/ISO_4217#Active_codes
In closure/goog/i18n/currency.js file follows that.
But not in i18n/closure/numberSymbolsExt.js , see each CURRENCY_PATTERN.
for the simple view, see:
https://github.com/google/closure-library/search?utf8=✓&q=KRW
https://github.com/google/closure-library/search?utf8=✓&q=JPY
How about change the currency pattern with no fractions?

As noted at the top of the file, this is generated from the CLDR.  You need
to request the change there and then we can pick it up.
On Jan 25, 2016 9:10 PM, "Myeongseok Seo"<EMAIL_ADDRESS>wrote:

In Korea, and in Japan, currencies does not used with fractions normally.
The Currincies does not written usually 1,000₩ not 1,000.00₩ and 1,000¥
not 1,000.00¥.
Yes, there's no coins for the fractions.
Only for the exact calculation fractions used like 1,000.11₩, 1,000.00¥.
There's may be the standards for this
https://en.wikipedia.org/wiki/ISO_4217#Active_codes
In closure/goog/i18n/currency.js file follows that.
But not in i18n/closure/numberSymbolsExt.js , see each CURRENCY_PATTERN.
for the simple view, see:
https://github.com/google/closure-library/search?utf8=✓&q=KRW
https://github.com/google/closure-library/search?utf8=✓&q=JPY
How about change the currency pattern with no fractions?
—
Reply to this email directly or view it on GitHub
https://github.com/google/closure-library/issues/636.

Okay thank you.


max_key_fee setting is either bugged or incorrectly documented

See: https://github.com/lbryio/lbry-app/pull/278
This is blocking an otherwise ready app PR.

This API call is working perfectly in the lbry-daemon, which is cloned from lbryio/lbry. This issue has to be tackled at the lbry-app level. (Check the attached calls)
$ curl 'http://localhost:5279/lbryapi' --data '{"method":"settings_get"}'

{
  "id": null,
  "jsonrpc": "2.0",
  "result": {
    "allowed_origin": "",
    "api_host": "localhost",
    "api_port": 5279,
    "cache_time": 150,
    "data_dir": "/root/.lbrynet",
    "data_rate": 0.0001,
    "delete_blobs_on_remove": true,
    "dht_node_port": 4444,
    "download_directory": "/root/Downloads",
    "download_timeout": 180,
    "is_generous_host": true,
    "known_dht_nodes": [
      [
        "lbrynet1.lbry.io",
        4444
      ],
      [
        "lbrynet2.lbry.io",
        4444
      ],
      [
        "lbrynet3.lbry.io",
        4444
      ]
    ],
    "lbryum_wallet_dir": "/root/.lbryum",
    "max_connections_per_stream": 5,
    "max_key_fee": {
      "amount": 25.9,
      "currency": "USD"
    },
    "min_info_rate": 0.02,
    "min_valuable_hash_rate": 0.05,
    "min_valuable_info_rate": 0.05,
    "peer_port": 3333,
    "peer_search_timeout": 3,
    "pointtrader_server": "http://<IP_ADDRESS>:2424",
    "reflect_uploads": true,
    "reflector_port": 5566,
    "reflector_servers": [
      [
        "reflector.lbry.io",
        5566
      ]
    ],
    "run_reflector_server": false,
    "sd_download_timeout": 3,
    "share_usage_data": true,
    "use_auth_http": false,
    "use_upnp": true,
    "wallet": "lbryum"
  }
}

$ curl 'http://localhost:5279/lbryapi' --data '{"method":"settings_set", "params":{"max_key_fee":{"amount":293.774,"currency":"LBC"}}}'

{
  "id": null,
  "jsonrpc": "2.0",
  "result": {
    "allowed_origin": "",
    "api_host": "localhost",
    "api_port": 5279,
    "cache_time": 150,
    "data_dir": "/root/.lbrynet",
    "data_rate": 0.0001,
    "delete_blobs_on_remove": true,
    "dht_node_port": 4444,
    "download_directory": "/root/Downloads",
    "download_timeout": 180,
    "is_generous_host": true,
    "known_dht_nodes": [
      [
        "lbrynet1.lbry.io",
        4444
      ],
      [
        "lbrynet2.lbry.io",
        4444
      ],
      [
        "lbrynet3.lbry.io",
        4444
      ]
    ],
    "lbryum_wallet_dir": "/root/.lbryum",
    "max_connections_per_stream": 5,
    "max_key_fee": {
      "amount": 293.774,
      "currency": "LBC"
    },
    "min_info_rate": 0.02,
    "min_valuable_hash_rate": 0.05,
    "min_valuable_info_rate": 0.05,
    "peer_port": 3333,
    "peer_search_timeout": 3,
    "pointtrader_server": "http://<IP_ADDRESS>:2424",
    "reflect_uploads": true,
    "reflector_port": 5566,
    "reflector_servers": [
      [
        "reflector.lbry.io",
        5566
      ]
    ],
    "run_reflector_server": false,
    "sd_download_timeout": 3,
    "share_usage_data": true,
    "use_auth_http": false,
    "use_upnp": true,
    "wallet": "lbryum"
  }
}

I still don't fully understand why the daemon is rejecting what appears to be valid data submitted by the app.

Can this be closed now?

@kauffj I can't find anything wrong with setting the max key fee on the daemon level at the current master.

There is no error here, it was in the release v0.13.1.


Add Vim Binding Support for CodePair Using CodeMirror 6

What would you like to be added:
In the previous version of CodePair, Vim binding was supported, which was a convenient feature for developers familiar with Vim. However, the previous version was implemented using CodeMirror 5 and used a Vim binding plugin.
With the new version of CodePair using CodeMirror 6, it would be beneficial to check if there is a Vim binding plugin available for this version as well. This will allow users who are accustomed to Vim to use the familiar key bindings in CodePair.
Why is this needed:
Adding Vim binding support will provide users with a familiar and efficient editing experience, especially for those who are comfortable with Vim. It will enhance the usability and appeal of CodePair to a wider range of developers.
Additional Information:
Additionally, we need to decide how to provide a UI for users to change editor settings, including key binding configurations.

It seems that we can use this library to implement it.
https://github.com/replit/codemirror-vim


How to get the timestamp below\besides the messages

Hello All,
I need help with integrating the timestamps from my Rasa Chatbot to the Webchat UI. I've created a tracker store which saves the conversations in a local SQLite DB. It stores the timestamp as well. Question is how am I supposed to pull that detail here in the UI. Also I'm totally novice at React and using this WebChat so a detailed explanation is appreciated. 👍

Pass this parameter initially when you load the widget:
showMessageDate: true

Gotcha @shyam-infraon.
It worked!
Thanks!


fix pull request #62

this shoul fix:
Compiling...
Using tsc v2.2.1
node_modules/feathers-errors/index.d.ts(68,3): error TS1036: Statements are not allowed in ambient contexts.
node_modules/feathers-errors/index.d.ts(68,3): error TS7028: Unused label.
node_modules/feathers-errors/index.d.ts(70,3): error TS7028: Unused label.

Is there a way for you to test those locally before we publish them? Is there anything we can do to make that more easily testable?

@daffl
You should be able to test this locally.
Also, most IDEs will give an error when you write this:


Move all the satellites to PROD

Remember

Add CORS in Sanity manage
Verify preview in Sanity

This one is pretty much done I would say. Could have a walkthrough of the setup.


Write documentation for plugin

Write documentation in Readme file to guide the users in configuring the plugin and available commands and options

Completed :white_check_mark:


Run non-interactively

Currently ffmpeg will ask you questions, which freezes the process while it waits for response. That makes it problematic to use on the web.

If the question ffmpeg is asking is if you want to overwrite the output, you can pass overwrite_output=True to  get_args or run.
https://github.com/kkroening/ffmpeg-python/blob/7669492575141c13b63fd89dde8b44ecf6bf31cb/ffmpeg/_run.py#L112-L115
https://github.com/kkroening/ffmpeg-python/blob/7669492575141c13b63fd89dde8b44ecf6bf31cb/ffmpeg/_run.py#L135-L140
You can pass any other options to ffmpeg by changing the cmd argument.
Check subprocess documentation.

@dmitrybelyakov Depaulicious is right - adding overwrite_output=True makes the prompt go away.
Perhaps it should be the default rather than having to explicitly say overwrite_output=True. What do you think, @dmitrybelyakov?

@kkroening makes sense, yes.

@Depaulicious thanks, will do that.

@kkroening I think the default should be True, but there should be a way to turn it off (e.g. overwrite_files=False, -n is added to the command line, =None nothing is added to the command line — ffmpeg will expect interaction).
It should never be interactive unless explicitly requested.

It should never be interactive unless explicitly requested.

Agreed. I'll make the change. Thanks for the input, guys.

#34 fixes this. I'll close this issue for now. Feel free to add comments on #34.


Add support for 'UseKeychain'

macOS Sierra 10.12.2 includes an new option called UseKeychain:
$ man ssh_config
     UseKeychain
             On macOS, specifies whether the system should search for passphrases in the user's keychain when attempting to use a par-
             ticular key. When the passphrase is provided by the user, this option also specifies whether the passphrase should be
             stored into the keychain once it has been verified to be correct.  The argument must be ``yes'' or ``no''.  The default is
             ``no''.

~Disclaimer: I don't know Go and don't know how to run the tests. :)~ Tests are passing 💪🏼

Hi @ocean90, thank you for this PR, and congratulations, everything seems good to me ;)


Handle attr errors

Summary:
Adds a more graceful HTML error response when the error detailed in Issue 545 occurs.
The HTML page reads:
"There was a problem generating this pdf. Ensure that required sections are filled, and please try again."

Closed this as stale


Vendor property error when used with a function (unrecognized property 'vendor')

I'm getting the following error when adding a 'vendor' property to a function.
Warning: Invalid configuration encountered at 'functions.hello': unrecognized property 'vendor'

For context, this is an attempt to keep task functions inside a Django mono-repo and have these smaller task functions utilize shared code at the app root. I wasn't able to get relative imports to work and am looking at this vendor option. I'm open to other suggestions for how others have handled this.
Additionally, I'm not entirely sure if vendor is able to take a list of project folders (example in the serverless.yml below)
Project Structure
app_root
|_ serverless.yml
|_ __init__.py
|_ core
|_ more_stuff
|_ tasks
    |_ __init__.py
    |_ handlers
        |_ __init__.py
        |_ my_handler.py

serverless.yml
configValidationMode: warn
useDotenv: true
deprecationNotificationMode: warn:summary

plugins:
  - serverless-offline
  - serverless-prune-plugin
  - serverless-python-requirements
  - serverless-step-functions
  - serverless-step-functions-local
  - serverless-wsgi

custom:
  pythonRequirements:
    usePoetry: false
    dockerFile: Dockerfile
    zip: true
    useDownloadCache: true
    useStaticCache: true
    dockerizePip: true
    slim: true
    strip: false
    pipCmdExtraArgs:
      - '-v'
      - '--log'
      - 'pip.log'
  stage: ${opt:stage, 'staging'}
  wsgi:
    app: core.wsgi.application
    packRequirements: false
  prune:
    automatic: true
    number: 3

functions:
  hello:
    handler: my_handler.handler
    module: tasks/handlers
    vendor:
    - ./core
    - ./more_stuff
    package:
      individually: true
        - 'core/**'
        - 'more_stuff/**'
        - 'wsgi_handler.py'
        - 'manage.py'
        - 's_app.py'
        - 'serverless_wsgi.py'
        - '.serverless-wsgi'
        - '!**/tests/**'
        - '!**/static/**'
    layers:
      - arn:aws:lambda:${self:provider.region}:770693421928:layer:Klayers-p39-boto3:1

provider:
  name: aws
  memorySize: 2056
  region: us-east-1
  runtime: python3.9
  versionFunctions: false
  stage: ${self:custom.stage}
  timeout: 30
  deploymentBucket:
    name: ${env:DEPLOYMENT_BUCKET}
  apiGateway:
    shouldStartNameWithService: true
  environment: ${file(./serverless/environment.yml)}

package:
  individually: true
  excludeDevDependencies: true
  patterns:
    - '!**'

package.json
    "@fernthedev/serverless-offline-step-functions": "^1.0.0-alpha.28",
    "serverless": "^3.7.0",
    "serverless-offline": "^8.5.0",
    "serverless-offline-lambda": "^1.0.6",
    "serverless-prune-plugin": "^2.0.1",
    "serverless-python-requirements": "^5.3.1",
    "serverless-step-functions": "^3.5.1",
    "serverless-step-functions-local": "^0.2.1",
    "serverless-wsgi": "^3.0.0"

Hello @daxiang28 - thanks for reporting. It seems like it was missed when schema was added here: https://github.com/serverless/serverless-python-requirements/blob/3edf0e0cabeeb11ffadd9dcac6f198f22aee4a16/index.js#L129
We'd be happy to accept a PR that adds that field to function schema 🙇

Additionally, I'm not entirely sure if vendor is able to take a list of project folders

It doesn't seem to be stated anywhere that it does (are there any docs other than the readme & tutorial on Serverless site?) - but 👍🏻 I would like that too.


Controls show Play button on autoplay

Having an issue when I set the video to autoplay on load, it plays but it still shows the play button and not the pause button.
Thanks

hi @2fdevs Seems like this bug has returned.
I forked a new pen from the controls example one to add vg-auto-play at http://codepen.io/pire/pen/GJqyOB
I've had a quick look but unable to find a solution. If it helps - the poster is also visible.
Would you like a new issue or could this one be re-opened?

Hi @pire thanks for testing.
Confirmed on Chrome and Firefox. It seems that the playPauseButton is showing the play state instead of the pause state.
Reopening.

Was digging around a little bit and noticed that this commit introduced the vg-over-play being in play state when vg-auto-play is true.

That was a PR that I accepted.... damn.
Well, I will try to fix it this weekend. Meanwhile maybe you can use v1.2.0 if it works for you.

Wow @ the super speedy responses @2fdevs . Thanks!
I'm back on 1.2.0 - the playPauseButton still shows the play state but the overlay is fixed.
I went further back to 1.1.0 and still had the same issue though. I'll dig some more and see if I can help you out in the mean time.

I was able to amend but I'm unsure if this is naughty or not.
This is what I'll use for my code in the meantime as callbacks only happen when the state changes and it doesn't seem like it's being over-used.
PRs
https://github.com/2fdevs/bower-videogular-overlay-play/pull/6
https://github.com/2fdevs/bower-videogular-controls/pull/6

Thank you for your PRs but those repositories are only for distribution!
This repository is the development repository and you should make your PRs agains this one. Also you can execute the tests (grunt test) on Chrome and Firefox to see if everything is ok. There are not too much tests but it should work.
I will close your PRs and wait for a new one in this repository if it's ok for you.


Apply colors if no texture found

If a material property does not have a texture, it might have a color so apply that color.

Fixed in #64


sumo breaks if there is a line doesn't match the pattern

Uploading all-logs1.log-RAT.txt…
Hi,
Sumo doesn't work if in data file, there is a line doesn't match the pattern. For example, this one doesn't work

$ cat all-logs1.log-RAT  | sumo search "https" | sumo parse " (*) - info: * - - [*]" as timezone, ip, timestamp | sumo count ip | render

Then I have to add the search "info", it works now!

$ cat all-logs1.log-RAT  | sumo search "https" | sumo search "info" | sumo parse " (*) - info: * - - [*]" as timezone, ip, timestamp | sumo count ip | render

_Id  _count  ip
0    7       ::1
1    5       ::ffff:<IP_ADDRESS>
2    1       <IP_ADDRESS>
3    2       <IP_ADDRESS>
4    1       <IP_ADDRESS>

I think it's a common sense to ignore the data line which doesn't match the input pattern.
Thank you very much!
Cheers,
Khon

That would be reasonable. I'll add that.
On Thu, Jan 12, 2017, 6:48 PM Khon Trieu<EMAIL_ADDRESS>wrote:

Hi,
Sumo doesn't work if in data file, there is a line doesn't match the
pattern. For example, this one doesn't work
$ cat all-logs1.log-RAT  | sumo search "https" | sumo parse " () - info: * - - []" as timezone, ip, timestamp | sumo count ip | render
Then I have to add the search "info", it works now!
$ cat all-logs1.log-RAT  | sumo search "https" | sumo search "info" | sumo parse " () - info: * - - []" as timezone, ip, timestamp | sumo count ip | render
_Id  _count  ip
0    7       ::1
1    5       ::ffff:<IP_ADDRESS>
2    1       <IP_ADDRESS>
3    2       <IP_ADDRESS>
4    1       <IP_ADDRESS>
I think it's a common sense to ignore the data line which doesn't match
the input pattern.
Thank you very much!
Cheers,
Khon
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/SumoLogic/sumoshell/issues/17, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAeFZ83lxEL3Cpw_R9EeB16jamYJkzKpks5rRuXpgaJpZM4LieJD
.

@rcoh: thank you very much. I really like sumoshell for the convenience it offers. Thanks in advance!

I don't think the log file uploaded if you meant to upload it.

@rcoh : I planned to upload the file but I have no idea why it failed. But you got the idea, so we can ignore that input. Thank you!

I can't reproduce the issue. Are you sure it isn't just that it's taking much longer if you don't filter info? I created this file:
matches [a=b]
matches [a=c]
no match
matches [a=d]
no match
matches [a=d]
no match
matches [a=d]

And ran this query:
➜  sumoshell git:(master) ✗ cat example/issue17 | sumo search | sumo parse "[a=*]" as a | sumo count a | render
_Id   _count   a
2     3        d
0     1        b
1     1        c

You can see the output above (correct)


FIREBASE_STORAGE_EMULATOR_HOST Environment Variable does not work with Admin SDK

My environment:

Operating System version: Mac OS Sonoma 14.0 (23A344)
Firebase Admin SDK version: 9.2.0
Firebase Product: Storage Emulator

The problem:
When setting the environment variable "FIREBASE_STORAGE_EMULATOR_HOST" to <IP_ADDRESS>:9199 (the default Storage Emulator Port and IP) to use the Firebase Storage Emulator the Admin SDK does not detect this environment variable.
Other Environment variables such as "FIREBASE_DATABASE_EMULATOR_HOST" and "FIRESTORE_EMULATOR_HOST" do work perfectly fine and as expected. They make a connection to emulators on the device.
I have gone as far to test and see if this issue is persistent on other Admin SDK's such as the Node.Js SDK. It is NOT an issue that persists on the SDK for Node.js.
As see here, this was previously an issue filed for the Firebase Admin SDKin the GO Repository for the Admin SDK (see here) and was fixed here (see here) and has been since claimed to be fixed and the logic used in the Node Admin SDK project will be implemented.
The same issue previously on the Go Repo, appears to be present on the Admin Java SDK. Even using the "STORAGE_EMULATOR_HOST" environment variable as it was changed to in the GO repo, does not work.
Documentation on the Firebase Admin SDK docs is also incorrect if this is the case.

Steps to reproduce:
Set either environment variable "STORAGE_EMULATOR_HOST" or "FIREBASE_STORAGE_EMULATOR_HOST" to your Emulator host address and port (the default is <IP_ADDRESS>:9199)
Use the Java Admin SDK to try and make a call like normal.
See it fail and use the production Cloud Storage instance.
Relevant Code:
Environment Variable Set via Intellij Run Configuration

    InputStream input = this.getClass().getResourceAsStream("/service-account.json");
    assert input != null;
    GoogleCredentials googleCredentials = GoogleCredentials.fromStream(input);

    FirebaseOptions options = FirebaseOptions.builder()
            .setCredentials(googleCredentials)
            .setProjectId("project-id")
            .setDatabaseUrl("https://project-id-default-rtdb.firebaseio.com")
            .setStorageBucket("project-id.appspot.com")
            .build();

    FirebaseApp.initializeApp(options);

    InputStream fileInput = this.getClass().getResourceAsStream("/someFile.anyExtension");
    Bucket bucket = StorageClient.getInstance().bucket();
    bucket.create("someFile.anyExtension", fileInput, "application/anyExtension");

To use the firebase storage emulator with the admin sdk use STORAGE_EMULATOR_HOST = 'http://localhost:9199' in your .env file.


Support use of servicename with oracle

Fixes #2215

Am I correct that this provides the same functionality as #2104?
If yes, I would close #2104 and try to merge this PR as soon as possible, so we slowly start to come back on track WRT to Oracle.

I get the following error when testing locally with a self-built and pre-initialized Oracle image:
    java.sql.SQLException: Result set after the last row
        at oracle.jdbc.driver.GeneratedScrollableResultSet.getInt(GeneratedScrollableResultSet.java:519)
        at com.zaxxer.hikari.proxy.ResultSetJavassistProxy.getInt(ResultSetJavassistProxy.java)
        at org.testcontainers.junit.SimpleOracleTest.testSimple(SimpleOracleTest.java:27)

I observed the same problem when trying out the non-initilalized image last week. Do you have a quick idea what is the reason for this? If not, I will try to debug this in more detail.

I didn't get this error when I was testing locally.  But I wasn't actually testing in the TestContainers project.  I did notice though that we are using oracle6 driver here:
https://github.com/testcontainers/testcontainers-java/blob/6ec63f863f760e4e4b31965695834622dbcde505/modules/jdbc-test/build.gradle#L22-L24
Can this be updated to the latest oracle8_g debug driver? https://mvnrepository.com/artifact/com.oracle.ojdbc/ojdbc8_g/<IP_ADDRESS>

We've since upgraded: https://github.com/testcontainers/testcontainers-java/blob/master/modules/oracle-xe/build.gradle#L7
Does this help?

@kiview @rnorth Yes, the updated oracle jdbc driver worked for me.  I have updated this PR to include testing for both getting a connection using SID and Service Name.
I did update the test to run using a prebuilt oracle 18.4.0 image that I have on dockerhub... Now that 18.4.0 can be built without having to agree to a license agreement, I figured this would be fine in a testing environment.

@KyleAure Very helpful, thanks.
Can we duplicate your image in our Testcontainers DockerHub org?

Yes please 😊


instant-ngp render error

Hi
I was able to render fine with instant-ngp but I updated to the latest code (last week) and now instant-ngp fails to render
here is the shell error
> ns-render --load-config ... --traj filename --camera-path-filename ...
[21:59:33] Auto image downscale factor of 1                                                 nerfstudio_dataparser.py:290
[21:59:35] Skipping 0 files in dataset split train.                                         nerfstudio_dataparser.py:147
           Skipping 0 files in dataset split test.                                          nerfstudio_dataparser.py:147
None
Traceback (most recent call last):
  File "nerf-studio/nerfstudio/scripts/render_exr.py", line 180, in <module>
    entrypoint()
  File "nerf-studio/nerfstudio/scripts/render_exr.py", line 176, in entrypoint
    tyro.cli(RenderTrajectory).main()
  File "nerf-studio/nerfstudio/scripts/render_exr.py", line 142, in main
    test_mode="test" if self.traj == "spiral" else "inference",
  File "nerf-studio/nerfstudio/utils/eval_utils.py", line 100, in eval_setup
    pipeline = config.pipeline.setup(device=device, test_mode=test_mode)
  File "nerf-studio/nerfstudio/configs/base_config.py", line 66, in setup
    return self._target(self, **kwargs)
  File "nerf-studio/nerfstudio/pipelines/dynamic_batch.py", line 63, in __init__
    self._update_pixel_samplers()
  File "nerf-studio/nerfstudio/pipelines/dynamic_batch.py", line 67, in _update_pixel_samplers
    self.datamanager.train_pixel_sampler.set_num_rays_per_batch(self.dynamic_num_rays_per_batch)
  File "nerf-studio/venv3.7_nerfstudio/lib64/python3.7/site-packages/torch/nn/modules/module.py", line 1208, in __getattr__
    type(self).__name__, name))
AttributeError: 'VanillaDataManager' object has no attribute 'train_pixel_sampler'

let me know if you spot something obvious
thanks for your help

One thing I have found is that sometimes nerfstudio version changes are not backward compatible with prior training outputs.
Was your config trained with a prior version?  If so, you may need to retrain for this version to be able to render or export.

Thanks for your reply machenmusik. Unfortunately, it was a brand new training.


[SUPPORT] INSERT operation performance vs UPSERT operation

Tips before filing an issue

Have you gone through our FAQs?

Join the mailing list to engage in conversations and get faster support at<EMAIL_ADDRESS>

If you have triaged this as a bug, then file an issue directly.

Describe the problem you faced
INSERT operation works with almost the same performance as UPSERT operation.
There's no acceleration with using INSERT operation.
To Reproduce
We use non partitioned table with BUCKET CONSISTENT_HASHING index.
Here is config:
val hudiWriteConfigs = Map(
"hoodie.datasource.write.table.type" -> "MERGE_ON_READ",
"hoodie.write.markers.type" -> "direct",
"hoodie.metadata.enable" -> "true",
"hoodie.index.type" -> "BUCKET",
"hoodie.index.bucket.engine" -> "CONSISTENT_HASHING",
"hoodie.bucket.index.num.buckets" -> "10000",
"hoodie.storage.layout.partitioner.class" -> "org.apache.hudi.table.action.commit.SparkBucketIndexPartitioner",
"hoodie.compact.inline" -> "true",
"hoodie.compact.inline.max.delta.commits" -> "10",
"hoodie.compact.inline.max.delta.seconds" -> "3600",
"hoodie.compact.inline.trigger.strategy" -> "NUM_OR_TIME",
"hoodie.clean.async" -> "false",
"hoodie.clean.max.commits" -> "10",
"hoodie.cleaner.commits.retained" -> "10",
"hoodie.keep.min.commits" -> "20",
"hoodie.keep.max.commits" -> "30",
"hoodie.datasource.write.keygenerator.class" -> "org.apache.hudi.keygen.NonpartitionedKeyGenerator"
)
Steps to reproduce the behavior:

Run UPSERT of batch of 3000 rows
df_u.write.format("hudi").options(hudiWriteConfigs).option("hoodie.datasource.write.recordkey.field", "_Fld19066_TYPE,_Fld19066_RTRef,_Fld19066_RRRef,_Fld19067RRef,_Fld19068RRef,_Fld19069,_Fld24101RRef").option("hoodie.datasource.write.precombine.field", "_ts_ms").option("hoodie.merge.allow.duplicate.on.inserts", "true").option("hoodie.datasource.write.operation", "upsert").mode("append").option("hoodie.table.name", "_InfoRg19065").save("/warehouse/debezium_hudi_test/data/_InfoRg19065")
Run INSERT of batch of 3000 rows
df_u.write.format("hudi").options(hudiWriteConfigs).option("hoodie.datasource.write.recordkey.field", "_Fld19066_TYPE,_Fld19066_RTRef,_Fld19066_RRRef,_Fld19067RRef,_Fld19068RRef,_Fld19069,_Fld24101RRef").option("hoodie.datasource.write.precombine.field", "_ts_ms").option("hoodie.merge.allow.duplicate.on.inserts", "true").option("hoodie.datasource.write.operation", "insert").mode("append").option("hoodie.table.name", "_InfoRg19065").save("/warehouse/debezium_hudi_test/data/_InfoRg19065")
View and compare jobs executed in Spark UI
UPSERT execution

INSERT execution

Expected behavior
Expected that performance of INSERT operation would be better than of UPSERT operation
Environment Description

Hudi version : 0.13.0

Spark version : 3.2.2

Hive version :

Hadoop version : 3.3.2

Storage (HDFS/S3/GCS..) : HDFS

Running on Docker? (yes/no) : no

in this case, all of them will append to logFile in the same way in writting data stage because this is mor table which use bucket.
And in addition, the task look like exec very fast, the update/insert count is small. Other factors may have a certain impact, like task schedule time, the current maximum parallelism, scheduling situation

@awk6873 I tried to run with a bigger dataset also and it gave similar performance as @KnightChess explained.
Do you still see it a issue or need more clarifications?

@awk6873 Why are you not using Bulk insert?
Insert operation also takes the similar write path as upsert so the performance can be similar although it doesn't do index lookup. Bulk insert should be very fast, and you can do separate clustering job to handle small files problem.

@awk6873 Do you need any other info on this ticket?

@awk6873 Do you need any other info on this ticket?

No, thanks


Any plans for highlighting?

I'm still new to the tree-sitter arena, but I was wondering if there were any plans on adding any of the "queries" items, particularly highlighting.
Thanks!

The highlighting queries are in the nvim-treesitter repo, I can add here if needed

That would be great, I think. I wanted to add beancount support to the Helix editor, which appears to pull the tree-sitter repository down to build and use. I'm still figuring out how tree-sitter is consumed, so I'm not sure, although that appears what Helix wants.

Or maybe not. I'll look into it later.

Going from Helix, your Neovim repository, and a message I got, it looks like these files are generally provided in the editor, plugin, etc. so I'll take what was provided in the Helix PR and add it there. Thank you for your time and consideration.


fix: make redis cache pool settings configurable

related to AM-3974

Gravitee.io Automatic Deployment
🚀 A prerelease version of this package has been published on Gravitee's private artifactory, you can:

use it directly by updating your project with version: 6.4.4-am-3974-SNAPSHOT
download it from Artifactory here

:tada: This PR is included in version 6.4.4 :tada:
The release is available on:

6.4.4
GitHub release

Your semantic-release bot :package::rocket:


Add the boxed!() macro to "de-magic" box syntax

Box syntax (e.g. box x) is controversial due to its "magic" status in the language. This RFC proposes the addition of a boxed macro that would remove the magic syntax from this feature (e.g. boxed!(x)).
Rendered

Given that box is not stable, and neither would the macro you are proposing, this should be done as a Major Change Proposal.
As somebody who is not part of the compiler team though, the difference between unstable syntax and macros is basically zero, so this just looks like churn for the sake of churn.

Given that box is not stable, and neither would the macro you are proposing, this should be done as a Major Change Proposal.
As somebody who is not part of the compiler team though, the difference between unstable syntax and macros is basically zero, so this just looks like churn for the sake of churn.

Doing this as an RFC so that it has a clear path to stability is  fine, in terms of process.
However, I also don't see how this fixes much. box <expr> is entirely fine syntax, so we should just stabilize that if we eventually want a stable boxing syntax.

Doing this as an RFC so that it has a clear path to stability is  fine, in terms of process.
However, I also don't see how this fixes much. box <expr> is entirely fine syntax, so we should just stabilize that if we eventually want a stable boxing syntax.

I would prefer to add magic syntax and remove it in a future edition than add a macro with a magic implementation and be stuck with it in the std library forever.
I do like the motivation of trying to hide some of the magic though.

I would prefer to add magic syntax and remove it in a future edition than add a macro with a magic implementation and be stuck with it in the std library forever.
I do like the motivation of trying to hide some of the magic though.

Personally, I thought that the main reason why box wasn't stabilised wasn't because it was too magic of a syntax, but because we weren't sure how to generalise it in such a way that it would work generically for any kind of heap allocation, rather than just applying to box. And, there was the issue of box patterns, which I think has been resolved and they won't be needed anyway.
The thing I do like about using a boxed! macro instead of a box syntax that gets removed is that we already have this magic macro with vec!, and the precedent would be to add a box! macro like it. (I would call it box! instead of boxed! though, for consistency.) Ultimately, whatever generic solution is used should also work for Vec, and that would also make the vec! macro redundant as well.

Personally, I thought that the main reason why box wasn't stabilised wasn't because it was too magic of a syntax, but because we weren't sure how to generalise it in such a way that it would work generically for any kind of heap allocation, rather than just applying to box. And, there was the issue of box patterns, which I think has been resolved and they won't be needed anyway.
The thing I do like about using a boxed! macro instead of a box syntax that gets removed is that we already have this magic macro with vec!, and the precedent would be to add a box! macro like it. (I would call it box! instead of boxed! though, for consistency.) Ultimately, whatever generic solution is used should also work for Vec, and that would also make the vec! macro redundant as well.

@clarfonthey vec! macro isn't magic, it's just a normal macro. It does defer to some implementations that utilize specialization, but specialization that's no different from the rest of std. Funnily enough, vec! does utilize the box syntax internally. Again, utilizing unstable syntax/features within a macro is not a big deal. For an example of a magic macro, look no further than format_args 👀

@clarfonthey vec! macro isn't magic, it's just a normal macro. It does defer to some implementations that utilize specialization, but specialization that's no different from the rest of std. Funnily enough, vec! does utilize the box syntax internally. Again, utilizing unstable syntax/features within a macro is not a big deal. For an example of a magic macro, look no further than format_args 👀

Oh, I guess I should have clarified -- while vec! isn't strictly magic and mostly doesn't need anything like box to work, it's also essentially the same as Vec::from(box [...]).

Oh, I guess I should have clarified -- while vec! isn't strictly magic and mostly doesn't need anything like box to work, it's also essentially the same as Vec::from(box [...]).

Stabilizing boxed! or r#box! rather them the original box syntax has the advantage that vec::Vec and boxed::Box instances, can be created in very similar fashion, by calling a macro with the same name as the module, their return type is defined on (or the type name in lowcase in case of r#box!). In addition to not adding new syntax, boxed! or r#box!() can be defined in alloc, whereas the box syntax is awailable even when the boxed::Box type is not available at all. In case of r#box!, if we define it as a syntax extension like format_args!, we can remove the box syntax feature and the box keyword entierly. This would allow the macro to be called simply using box!.

Stabilizing boxed! or r#box! rather them the original box syntax has the advantage that vec::Vec and boxed::Box instances, can be created in very similar fashion, by calling a macro with the same name as the module, their return type is defined on (or the type name in lowcase in case of r#box!). In addition to not adding new syntax, boxed! or r#box!() can be defined in alloc, whereas the box syntax is awailable even when the boxed::Box type is not available at all. In case of r#box!, if we define it as a syntax extension like format_args!, we can remove the box syntax feature and the box keyword entierly. This would allow the macro to be called simply using box!.

I would prefer to add magic syntax and remove it in a future edition than add a macro with a magic implementation and be stuck with it in the std library forever.

I think I follow this train of thought that I don't think an intentionally temporary boxed! macro will really move us forwards, but if we did want to commit to a boxed! macro instead of the user-facing language feature to the point of linting against Box::new then I think that could be worth exploring. Once there is a stable way to avoid the stack blowup problem there's really no reason to ever consider the "broken" alternative, right?
Maybe this has come up before but have we ever thought about trying to make Box::new(expr) magically equivalent to the already magic box expr?

I would prefer to add magic syntax and remove it in a future edition than add a macro with a magic implementation and be stuck with it in the std library forever.

I think I follow this train of thought that I don't think an intentionally temporary boxed! macro will really move us forwards, but if we did want to commit to a boxed! macro instead of the user-facing language feature to the point of linting against Box::new then I think that could be worth exploring. Once there is a stable way to avoid the stack blowup problem there's really no reason to ever consider the "broken" alternative, right?
Maybe this has come up before but have we ever thought about trying to make Box::new(expr) magically equivalent to the already magic box expr?

We do have #2884 for in-place construction at library level, at the cost of spec-guaranteed RVO.
// the closure's return is guaranteed to be written to box,
// rather than written to stack then memcpy into the box
let mut hectapus = Box::with(|| Hectapus { arm_lengths: [0; 100] });

(I also think let x: Rc<T> = box T::new() is extremely confusing, since the Box type has already taken the name)

We do have #2884 for in-place construction at library level, at the cost of spec-guaranteed RVO.
// the closure's return is guaranteed to be written to box,
// rather than written to stack then memcpy into the box
let mut hectapus = Box::with(|| Hectapus { arm_lengths: [0; 100] });

(I also think let x: Rc<T> = box T::new() is extremely confusing, since the Box type has already taken the name)

Maybe this has come up before but have we ever thought about trying to make Box::new(expr) magically equivalent to the already magic box expr?

They are equivalent, aren't they? The source code of Box::new() is this:
pub fn new(x: T) -> Self {
    box x
}

Nope, because what's special about box is that it evaluates the initializer expression directly into the destination allocation, rather than first initializing an object on the stack, then allocating, and finally moving the object into the destination allocation.  In the case of Box::new, x has to already exist on the stack, and be initialized, before Box::new starts running.
Note that LLVM's optimizer will sometimes optimize away the stack object, making Box::new generate the same assembly as box – but not always, and not when optimizations are disabled.

Ah, I see what you mean. Like in the sense of x being moved into the function versus not. I was moreso just thinking about it as far as the end result of what they do.

The box syntax feature is not blocked on the syntax, but semantics. So whatever is blocking box is also blocking this proposed boxed!().
@rfcbot close


File Pathing

I cannot for the life of my figure out where to place the files in ryujinx  i cant find the directory you mentioned in the description

This will not work with the Switch version.


[API v2.0 - vendorPaymentJournal] Add an example of the response

Just a simple example - nothing too fancy here.

Docs Build status updates of commit a9f7943:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

dev-itpro/api-reference/v2.0/api/dynamics_vendorpaymentjournal_get.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Thanks for your contribution!


ci: split tests workflow into two and refactor them

Description

This PR refactor tests workflow, in order to fix problem like: https://github.com/Finschia/cosmwasm/actions/runs/8165890934
This PR changed following:

split tests workflow into two
use matrix strategy to make contract test more clearly
add missing ci tests for floaty and cyberpunk
add document test for each contract in CI via cargo test --doc
use cargo test --test integration in CI

Types of changes

[x] Bug fix (changes which fixes an issue)
[ ] New feature (changes which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] ETC (build, ci, docs, perf, refactor, style, test)

Checklist

[x] I followed the contributing guidelines.
[x] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] The PR title and commits are followed conventional commit form.

Is there some example execution of this CI?


The keyword in warning message should be the same with command line

Describe the bug
The keyword in warning message should be the same with command line
To Reproduce
Steps to reproduce the behavior:

jobs1 = %adl listjobs --page_index 0 --page_job_number 100
Result: Warning "Parameter account name can not be None"
jobs1 = %adl listjobs --account devtooltelemetryadla --page_index -1 --page_job_number 100
Result: Warning "Parameter skip must be greater than 1"
jobs1 = %adl listjobs --account devtooltelemetryadla --page_index 0 --page_job_number -1
Result: Warning "Parameter top must be greater than 1"

Expected behavior
The keyword should be the same
Command--------------warning message
account ----------------account name
page_index-------------skip
page_job_number------top
Screenshots

Desktop (please complete the following information):
OS: Win10
Browser: chrome
Jupyter Version: Python 3.6.2, Jupyter 4.4.0
Additional context
Add any other context about the problem here.

@ruixinxu  @jingyanjingyan has been fixed with the issue #28

Sorry, i should not close it. I think may be should close this issue after merge the fix branch to master branch by vincent. @jingyanjingyan @ruixinxu  @iVincentFeng

Repro at 07-25-2018


fix: [#4684] ESLint issues in botbuilder-applicationinsights

Addresses #4684
#minor
Description
This PR fixes the new ESLint errors and warnings after upgrading the ESLint packages in the botbuilder-applicationinsights project.
Specific Changes

Removed 'botbuilder-applicationinsights/eslint.config.cjs' file as it contained only the 'only-warn' plugin which was no longer needed.
Applied the auto-fix flag for all the issues (trailing commas and removing unnecessary rule exceptions).

Testing
The following images show the number of issues fixed in the library.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.3%) to 84.343%

Totals

Change from base Build<PHONE_NUMBER>1:
-0.3%

Covered Lines:
20435

Relevant Lines:
23070

💛  - Coveralls


Get missing KBs by device missing permissions

This page does not show the required application permissions. It appears to be "Software.Read.All".

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

ID: 5d43426f-11d0-0cb3-5003-1d4e58c77678
Version Independent ID: 48e15168-7127-1c42-1c03-56bca11208fd
Content: Get missing KBs by device ID
Content Source: microsoft-365/security/defender-endpoint/get-missing-kbs-machine.md
Product: w10
GitHub Login: @Dansimp
Microsoft Alias: dansimp

@MastaDisasta Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/6072
Thanks
Sri

@msbemba Thank you very much for the contribution and updating the documentation with PR. @MastaDisasta Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


fix asan check in c++ gradients

@saxenasaurabh
Let's see if this PR fixes the problems with asan. There are some more leaks indeed, but I couldn't find a fix for them and they seem related to other components of the code. Here is the list:

tensorflow::BuildImmediateExecutionContext
tensorflow::gradients::Tape::ComputeGradient
tensorflow::EagerContext::CreateOperation
tensorflow::gradients::TapeOperation::Execute

Thanks for finding and fixing this. Would you mind describing / documenting how you are debugging mem leaks. It may be useful for future contributors.

Could you please elaborate what does this args mean ? Maybe it is related to the leaks above and I could do something. Thank you !

This basically says do not perform heap leak checking for the entire program but only for annotated code blocks (using an internal API). Since there are no annotated code-blocks in this test this basically skips checking for leaks. We can remove this once the leaks are gone.

Thanks for finding and fixing this. Would you mind describing / documenting how you are debugging mem leaks. It may be useful for future contributors.

I am not sure where the documenting should go. I think it is best if we could add this option to our .bazelrc file.

Thanks for finding and fixing this. Would you mind describing / documenting how you are debugging mem leaks. It may be useful for future contributors.

I am not sure where the documenting should go. I think it is best if we could add this option to our .bazelrc file.

cc: @mihaimaruseac

This basically says do not perform heap leak checking for the entire program but only for annotated code blocks (using an internal API). Since there are no annotated code-blocks in this test this basically skips checking for leaks. We can remove this once the leaks are gone.

I found this site https://gperftools.github.io/gperftools/heap_checker.html . It seems related to that args. Could you check it out ?

This basically says do not perform heap leak checking for the entire program but only for annotated code blocks (using an internal API). Since there are no annotated code-blocks in this test this basically skips checking for leaks. We can remove this once the leaks are gone.

I found this site https://gperftools.github.io/gperftools/heap_checker.html . It seems related to that args. Could you check it out ?

Aha, yep looks like the correct link.

FYI,
When building asan without debugging, e.g only --copt -fsanitize=address --linkopt -fsanitize=address, custom_gradient_test pass. However, when adding --copt -O1 --copt -g -c dbg, there is a leak in tensorflow::BuildImmediateExecutionContext ( it is probably why we need heap-check=local ).
My guess is we could drop no_cuda_asan for gradient_checker_test.
nn_grad_test has some leaks even without debugging symbol, so we will have to leave it as-is.


I have added a "mail to" link on email address.

Added Mail To link at all the email address present in the website, so the user can directly contact via click.

@Kratika-Solanki, thank you for your pull request.

I noticed you opened and closed your own PR 3-4 times. Could you please clarify the reason behind this?

Issue No. #49


Review and remove deprecated APIs

Start by looking at all the APIs that are marked as deprecated and put together a plan. Link specific issues to this epic.
Goals

Audit all the APIs that are marked with the @deprecated tag
Check the APIs usage in the following repositories:

https://github.com/microsoft/FluidFramework
https://github.com/microsoft/FluidExamples
Partner Repos

Remove/Refactor the APIs

Proposed methodology
There are a bunch to deprecated APIs used in Fluid Framework repository and others used in both Fluid Framework and partner repositories. The plan is to start with replacing and deleting the APIs used only in Fluid Framework repository and later on start making changes to the APIs used by partner teams. Some of the APIs have considerable usage by partner teams and will require more investigation and planning to fully remove. These are captured in the categories below.
Planning Work Items

[x] #8109
[x] #8110
[x] #8111
[x] #8112
[x] #8114
[x] #8113

API Breakdown Work Items
Go here to query for all open GitHub issues related to API deprecation.
Completed

[x] #8185
[x] #8190
[x] #8279
[x] #8290
[x] #8289
[x] #8280
[x] #8192
[x] #8189
[x] #8284
[x] #8223
[x] #8285
[x] #8295
[x] #8275
[x] #8188
[x] #8276
[x] #8281
[x] #8278
[x] #8270
[x] #8450
[x] #8187
[x] #8268
[x] #8288
[x] https://github.com/microsoft/FluidFramework/issues/8438
[x] #8277
[x] #8191
[x] #8274
[x] #8186
[x] #8272
[x] #8283
[x] #8286

In progress

[ ] #8193

I have removed tracking "needs solutioning" and "blocked" to bring this epic towards conclusion. We have new guidelines going forward around tracking/managing deprecation work. The tickets under those 2 categories are still tagged with "API deprecation" so we can track them more easily.


Verilog with 'disableRegisterRandomization' fails in Xilinx Vivado synthesis

Verilog generated with disabled RANDOMIZATION logic ("--emission-options", "disableRegisterRandomization") will fail in Xilinx Vivado synthesis. Other synthesis tools might be affected too.

I ran the basic 3.5.0-RC2 example from @jackkoenig https://scastie.scala-lang.org/tcZC6RDhTKSmuwjLcWmIIg through Vivado:
module Example(
  input        clock,
  input        reset,
  input        a,
  input        b,
  input        c,
  input        d,
  input        e,
  input        f,
  input  [7:0] foo,
  input  [7:0] bar,
  output [7:0] out
);
  reg [7:0] myReg = myReg; // @[main.scala 11:22]
  assign out = myReg; // @[main.scala 12:7]
  always @(posedge clock) begin
    if (reset) begin // @[main.scala 11:22]
      myReg <= 8'h0; // @[main.scala 11:22]
    end else if (d & e & f) begin // @[main.scala 17:22]
      myReg <= bar; // @[main.scala 18:11]
    end else if (a & b & c) begin // @[main.scala 14:22]
      myReg <= foo; // @[main.scala 15:11]
    end
  end
endmodule

The problem is in line 14 reg [7:0] myReg = myReg, which will cause Vivado to error with: ERROR: [Synth 8-1002] myReg is not a constant [Example.v:14]. The initialization of myReg to itself is specifically caused by disabling the randomization logic.

Type of issue: bug report

Impact: unknown

Development Phase: request
Other information

If the current behavior is a bug, please provide the steps to reproduce the problem:
For a quick test, run Vivado in tcl mode vivado -mode tcl with the following commands:
set_part xc7z020clg484-1
read_verilog Example.v
synth_design -top Example -mode out_of_context -verbose

Please tell us about your environment:

version: 3.5.0-RC2
Xilinx Vivado 2021.1

This should be fixed in https://github.com/chipsalliance/firrtl/pull/2449


Route event page to What's On service

[x] Need to inform event team
[x] Needs #3022 to be completed

https://github.com/wellcometrust/wellcomecollection.org/pull/3151


Store only the resolved reference in DocumentationContext.symbolIndex

Bug/issue #, if applicable: rdar://106654403
Summary
This changes DocumentationContext.symbolIndex from a lookup that return DocumentationNode values to a lookup that return ResolvedTopicReference values.
Storing all nodes both in the documentation cache and in the symbol index makes it easy to accidentally hold on to old versions of nodes if the value in the documentation cache is updated without also updating the value in the symbol index. By instead only storing the node's resolved reference in the symbol cache and using it to find the node in the documentation cache, various places in the code that modify documentation nodes only need to update the value in one place.
This makes up for the previous peak memory usage increase from https://github.com/apple/swift-docc/pull/498#issuecomment-1458992556.
Dependencies
None.
Testing
None. This is a non-functional change. Everything should continue to work the same as before.
Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[x] Added tests
[x] Ran the ./bin/test script and it succeeded
[x] Updated documentation if necessary

In my local benchmarking across two different machines this lowers peak memory usage by ~1.5-2% while also making small improvements to the total covert time:
Local benchmark results on one machine:
┌──────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Metric                                   │ Change          │ main                 │ current              │
├──────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Duration for 'bundle-registration'       │ no change¹      │ 5.624 sec            │ 5.588 sec            │
│ Duration for 'convert-total-time'        │ -0.4889%²       │ 8.333 sec            │ 8.292 sec            │
│ Duration for 'documentation-processing'  │ no change³      │ 2.483 sec            │ 2.48 sec             │
│ Duration for 'finalize-navigation-index' │ no change⁴      │ 0.117 sec            │ 0.115 sec            │
│ Peak memory footprint                    │ -2.077%⁵        │ 1,013.8 MB           │ 992.7 MB             │
│ Data subdirectory size                   │ change          │ 280.4 MB             │ 280.4 MB             │
│ Index subdirectory size                  │ no change       │ 2.5 MB               │ 2.5 MB               │
│ Total DocC archive size                  │ change          │ 295.5 MB             │ 295.5 MB             │
│ Topic Anchor Checksum                    │ no change       │ a8c40d797627683c5d7c │ a8c40d797627683c5d7c │
│ Topic Graph Checksum                     │ no change       │ da82bd7f35eae4bb56e8 │ da82bd7f35eae4bb56e8 │
└──────────────────────────────────────────────────────────────────────────────────────────────────────────┘

 1: No statistically significant difference.
    The values are similar enough that the most probable explanation is that they're random samples from the same data set.
    t-statistic : +1.815          degrees of freedom : 28       95% confidence critical value : +2.042

 2: There's a statistically significant difference between the two benchmark measurements.
    The values are different enough that the most probable explanation is that they're random samples from two different data sets.
    t-statistic : +2.079          degrees of freedom : 28       95% confidence critical value : +2.042

 3: No statistically significant difference.
    The values are similar enough that the most probable explanation is that they're random samples from the same data set.
    t-statistic : +0.483          degrees of freedom : 28       95% confidence critical value : +2.042

 4: No statistically significant difference.
    The values are similar enough that the most probable explanation is that they're random samples from the same data set.
    t-statistic : +1.924          degrees of freedom : 28       95% confidence critical value : +2.042

 5: There's a statistically significant difference between the two benchmark measurements.
    The values are different enough that the most probable explanation is that they're random samples from two different data sets.
    t-statistic : +9.628          degrees of freedom : 28       95% confidence critical value : +2.042

Local benchmark results on the other machine:
┌──────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Metric                                   │ Change          │ main                 │ current              │
├──────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Duration for 'bundle-registration'       │ -1.184%¹        │ 8.723 sec            │ 8.619 sec            │
│ Duration for 'convert-total-time'        │ -0.6942%²       │ 14.529 sec           │ 14.428 sec           │
│ Duration for 'documentation-processing'  │ no change³      │ 5.376 sec            │ 5.377 sec            │
│ Duration for 'finalize-navigation-index' │ no change⁴      │ 0.228 sec            │ 0.229 sec            │
│ Peak memory footprint                    │ -1.412%⁵        │ 1,019.1 MB           │ 1,004.7 MB           │
│ Data subdirectory size                   │ no change       │ 280.8 MB             │ 280.8 MB             │
│ Index subdirectory size                  │ no change       │ 2.6 MB               │ 2.6 MB               │
│ Total DocC archive size                  │ no change       │ 401.3 MB             │ 401.3 MB             │
│ Topic Anchor Checksum                    │ no change       │ a8c40d797627683c5d7c │ a8c40d797627683c5d7c │
│ Topic Graph Checksum                     │ no change       │<PHONE_NUMBER>84b5131a37 │<PHONE_NUMBER>84b5131a37 │
└──────────────────────────────────────────────────────────────────────────────────────────────────────────┘

 1: There's a statistically significant difference between the two benchmark measurements.
    The values are different enough that the most probable explanation is that they're random samples from two different data sets.
    t-statistic : +3.770          degrees of freedom : 28       95% confidence critical value : +2.042

 2: There's a statistically significant difference between the two benchmark measurements.
    The values are different enough that the most probable explanation is that they're random samples from two different data sets.
    t-statistic : +2.143          degrees of freedom : 28       95% confidence critical value : +2.042

 3: No statistically significant difference.
    The values are similar enough that the most probable explanation is that they're random samples from the same data set.
    t-statistic : -0.026          degrees of freedom : 28       95% confidence critical value : +2.042

 4: No statistically significant difference.
    The values are similar enough that the most probable explanation is that they're random samples from the same data set.
    t-statistic : -0.443          degrees of freedom : 28       95% confidence critical value : +2.042

 5: There's a statistically significant difference between the two benchmark measurements.
    The values are different enough that the most probable explanation is that they're random samples from two different data sets.
    t-statistic : +9.061          degrees of freedom : 28       95% confidence critical value : +2.042

@swift-ci please test

Is there a test that we can write that asserts that the references from the different stores are the consistent?

Good idea. I think that'd be easy to test with one of the test bundles.


Building and Integrating Spring Interceptors In Java [Duplicate #7025]

Article checklist
Attention
Our Peer Reviewer and Content Moderator teams do NOT provide any revisions services. All revisions and edits should be completed on your own forked repo (as to not take up room in the queue) in order for our team to review them all in a timely manner.
ANY ARTICLE SUBMITTED WITH GLARING ERRORS WILL BE IMMEDIATELY CLOSED.

As a rule of thumb - please be sure to only submit articles (pull requests) that are fully polished and ready to be published. Be sure to go through our resources documents for extra and 3rd party (vetted) resources to help improve overall technical writing.

Pre-submission checks

Please ensure that you have only one open topic suggestion (issue) + in-review article (linked pull request) at a time. This will ensure that we complete the review process in a timely manner from inception to publishing

If you have not already, please go over our Resources Page for more tips and tricks on how to improve your overall technical writing so reviews are swifter, increase the chance of a payout and provide more value to our readers.

For first-time contributors and for more details on our submission guidelines, see our Contributing Guidelines.

Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[ ] Have you included a hero image that is 600x400 pixels, under 300KB in size, and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[ ] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[x] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[x] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes

Remove the backticks and add the issue number below to link and close your Topic Suggestion (issue) when your article has been published (PR has been merged). See this video for more details.

This closes #6798

@srishilesh  @hectorkambow
Hello @lalith1403 , Thank you for your time in looking through my previous PR and consequently, I have opened a new PR. There has been a few over-sight I believe and I would like to go through them here:

The first three paragraphs of my article (just before the prerequisite) are originally my texts. They are the explanation I gave in creating my issue (with the issue number #6798). Read this issue and you'll see that I basically just used my own words in the article. That should be original to me.

There are keywords and configurations that are native to a programming language and cannot be modified. For instance, to use the web dependency in Spring/Spring Boot, there is ONLY ONE configuration  and that is exactly what I used. But your tool flagged, which I believe should not really be the case

Just as number 2 above, annotations cannot be modified or you will kill the purpose or gain nothing at all or introduce a bug.
@Slf4j is a logging library and that is the only way to wire it into your project. Your tool flagged this too and I believe it shouldn't be counted. The same goes for import statements. I am not in charge of these; Spring Boot automatically generates it for me when I use some classes. For example, the statement import org.spring framework.web.servlet.HandlerInterceptor is not necessarily a part of the code I wrote, but is essential for the code to run well.

The other things are basically me adapting what I had learnt in ways that I mostly understood and I think your tool was hyper-active this time. For instance, it flagged the word CONCLUSION (just that word alone and with a red tick).

This is my fifth article and I believe I got better with each passing one. Also, I appreciate all you and everyone does (especially those tagged) but I would like that you take a look at the reports. If they still don't meet your desires, I am happy to look wholly at it again.
Looking forward to hearing from you

@john-amiscaray Here is a resubmission. I thought to reach out to one of my last reviewers. I hope this meets you well. Thank you
@lalith1403

@lalith1403 I believe he is right here and that the content doesn't seem to be plagiarised based on the report (assuming the first three paragraphs have been marked as identical due to it matching with what he wrote in his issue which I think might be the case). Am I good to start the review then?

Yes. If the plagiarism issues are resolved, then we can proceed to review the article. Thank you.

@john-amiscaray Hello. Thank you for your comments. I have made adjustments accordingly and added a hero image too.. I look forward to hearing from you

@john-amiscaray Hello. Thank you for your comments. I have made adjustments accordingly and added a hero image too.. I look forward to hearing from you

Looks good. Just resize your hero image to be as close to 600x400 pixels as possible

@john-amiscaray Hi John, all changes mentioned have been implemented. Looking forward to hearing from you

@teevyne I looked through it and fixed a couple more minor errors in the code but it should be good now. Next time, please try to compile and run your code before submitting the article.

@teevyne A couple of quick things before we are done. Please resize your hero image so it is as close to 600x400 as possible. Also, please remove the unnecessary .idea folder that your IDE generates.

@teevyne Btw, I'm going to rename this pull request to match the title of this article. Please ensure you do that next time.

@john-amiscaray Thank you for everything. All the observations and corrections you made are duly noted and will be taken into account in my very next PR. Changes stated have been implemented also. Thank you again

@teevyne You're welcome that's what I'm here for 😄 . We should be ready for a final review now.

Thank you @john-amiscaray for everything.
@hectorkambow and @Kayere This should interest you to have a look at. Thanks

@hectorkambow @Kayere

jumping on this one


Cache invalidation doesn't work on aliased queries

Hi, thanks for such a useful library for Apollo-client. Recently I decided to apply it to my project and found the following error:
If you use alias for query, the cache will not be invalidated:
query getMetersByAddressKey($where: MeterWhereInput!, $first: Int!, $skip: Int!) {
    meters: allMeters(
        where: $where
        first: $first
        skip: $skip
    ) {
        id
    }

    meta: _allMetersMeta(where: $where) {
        count
    }
}

I've started digging into why this was happening and discovered the following:

When you call super.diff right here it returns result in format like so (aliases as keys):

{
  "meters": [
    {"id": 123, "__typename": "Meter"},
    {"id": 456, "__typename": "Meter"},
  ]
  "meta" {}
}

When it goes to cacheResultProcessor.processReadResult and here you obtain fieldName (allMeters in my case) and resultKeyName (meters in my case) and then pass fieldName to processReadSubResult function
The first thing processReadSubResult does is extracting field from result. So in my case it tries to get result['allMeters'], which resolved in undefined and processReadSubResult  returns Completed status.

I propose to fix this by passing in processReadSubResult in step 2 value like so resultKeyName || fieldName.
What do you think?

lgtm! Merging


Provide configuration options for to_csv method

Is your feature request related to a problem? Please describe.
As of now DataFrame.to_csv() method returns comma-separated values. But, the issue is data becomes corrupted when the value itself contains a comma.
Describe the solution you'd like
We can provide value separator config , Like in pandas  df.to_csv(path, sep=',').
There are other options as well which are very helpful like line_terminator, header list, column list

Is your feature request related to a problem? Please describe.
As of now DataFrame.to_csv() method returns comma-separated values. But, the issue is data becomes corrupted when the value itself contains a comma.
Describe the solution you'd like
We can provide value separator config , Like in pandas df.to_csv(path, sep=',').
There are other options as well which are very helpful like line_terminator, header list, column list

Great request, I’ll add this feature to the new build.

Thanks, @risenW
If possible, I would like to work on this issue.

Thanks, @risenW
If possible, I would like to work on this issue.

Awesome! You can read our contribution guide here, and let me know if you need any help.

Fixed in latest version v0.3.0


qs-app-2 to 0.0.1

Promote qs-app-2 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@amegas: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

promotion-build
19ff19a0f738ce1836e5844e1b8e8334fe3e67c1
link
/test this

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


hallo! what dataset do you used?

It was a data that a professor let me use for a project. I believe that they wish to keep it private


Seamless upgrade control

Now that scope detects new versions, we should provide a one-click upgrade (via controls), that:

Upgrades all probes
Upgrades the app
Refreshes the web UI

To avoid shooting ourselves in the foot, we need #697 first.

related: #1061.


Modify "NavCoin" to "Navcoin"

Description
Just another action item: Good if we could have “NavCoin” modified to “Navcoin” on the site at some point.

working on it


When a visitor wants to cancel a visit and forgets to check a checkbox, the app doesn't blow up.

Do we need to change the outcomes from symbols to strings throughout? The only reason I can see (but I may be missing something…) is to remove a to_sym in MetricsLogger#visit_status and to use %w{} instead of [:whatever, :other_thing] in VisitMetricsEntry?

Yup. Strange, I thought I made that change...

When you save a symbol to the DB and then retrieve it, you get a string. It's easier to just use strings every time.

Ah, yeah, of course it does. Fair enough.

Please could you add a test to make sure an email is only sent when a 'visit' is cancelled and not a 'request'?

Is this good to go?

I'm happy with it. @matharden? And have @tonyduarte or @RoseFaulkner tested it?

Looks good to me. Let's put it on pre-prod first thing tomorrow and I'll run through it.


1166 detail short url

Fixes #1166
Were any Django, import pipeline, table_schema, or dictionary files modified? N

If YES:

Database used: opus3_test_210526
All Django tests pass: NA
FLAKE8 run on modified code: NA

Were any JavaScript or CSS files modified? Y

If YES:

JSHINT run on all affected files: Y/NA
Tested on Chrome, Firefox, Safari, Edge, and iOS: Y/NA
(Remember to test all browser sizes)
Tested for race conditions (with delayed API calls if applicable): Y/NA

Description of changes:
Known problems:

Both of those last two are definitely bugs. I thought we had found and fixed that second one in the production version but I guess not. Please go ahead and fix it as well.


UiIconButton open-popover-on

Need some sort of way to allow it to open on hover. Could be added to the slot or probably better as open-popover-on for more consistency.
http://josephuspaye.github.io/keen-ui/#/ui-icon-button-docs

I didn't say this in the docs but the openDropdownOn prop also applies to popovers as well, not just menus.

Fixed: https://github.com/JosephusPaye/keen-ui/commit/e0fc946816efa5639e418203b399dfb0b1db35eb


Markdown relative image is not shown in Preview on windows

VSCode Version: 1.40.2
OS Version: Windows 10 x64

This seems to be a regression. Previous versions of VSCode allowed relative images to preview. But it is no longer working.
This the same issue as closed and locked issue https://github.com/microsoft/vscode/issues/45155 (which I am unable to reopen or comment on).

For a folder structure:
images/
cat.png
doc.md

With doc.md:

Open doc.md directly (don't open the folders)

Open preview

Bug:
No image shown in preview.

Does this reproduce in the latest VS Code insiders build?
Also, please include the source of the markdown file (as text)

It is NOT reproducible on Version: 1.41.0-insider (user setup).
It IS reproducible on Version: 1.40.2 (user setup)
both on OS: Windows_NT x64 10.0.14393

I open the local folder containing my repo, containing images in the 'media' folder:

In markdown I reference an image like this:

Preview in Version: 1.40.2 (user setup) only shows this:

Closing since it is fixed in insiders. The current insiders will be released as 1.41 sometime next week


add static Class.count() and Class.list() methods to classes

Person.count()
Person.list()
You can also add needed methods in comments that could be useful.

Implemented in v0.1.2


Application note should only be queryable by administrators

Currently, applicants and organizations that are linked to an application can query the application note.
As this note is private to the administrators, this should not be the case.

So whats your proposed solution @michael-markl ?
To create a separate ApplicationView for Administrators that include the note and remove it from ApplicationView

Hmm not sure what the best approach is... As the field is nullable (if I remember correctly) we could just not populate it for the corresponding endpoints.

its indeed nullable. just created a pr. not sure if this goes in the right direction


Provide separate caching methods

Rationale:

the Server class is getting bloated
the Server class has too many public functions:
compileFile() - always recompiles
checkedCompile() - compiles scss if cache doesn't exist
checkCachedCompile() - recompiles if necessary
serve() - the original purpose of this class

Cache:

never - no caching; always (re)compiles
read - read only if cache exists; doesn't create
once - compiles only if cache doesn't exist
surface/shallow - recompile if main .scss file changes (note: this has no current API equivalent)
deep - recompile if main .scss file or any of its imports changes

Technical considerations:

bust up the Server class and change bin/pscss
Server::setCache()
Cache/*.php implementations
"deep" should detect changes in setVariables()

I think we also need to detect changes to setVariables

See #321


backend/drm: move primary wlr_swapchain handling out of backend

This is https://github.com/swaywm/wlroots/pull/2505 but with the DRM backend changes too.

[ ] Migrate DRM backend

[x] Implement get_primary_formats
[x] Allocate an empty buffer on modeset, if we don't have one
[ ] Allow direct scan-out with legacy KMS API as long as the format/modifier doesn't change
[ ] Perform a test-only commit with the buffer when mode-setting an output
[ ] Fallback to modifier-less buffers
[ ] Remove buffer allocation on modeset in DRM backend

[ ] Remove legacy interfaces

[ ] Nuke wlr_backend_impl.get_renderer
[ ] Nuke wlr_output_impl.{attach,rollback}_render
[ ] Nuke wlr_output_state.buffer_type
[ ] Nuke wlr_output_impl.export_dmabuf

Depends on: https://github.com/swaywm/wlroots/pull/2505
Depends on: https://github.com/swaywm/wlroots/pull/2829

Seems like I'm hitting synchronization issues with this PR, on both AMD and Intel. The buffers seem to be scanned out by KMS before the draw is complete, or cleared before KMS is done with them.

Seems like I'm hitting synchronization issues with this PR

Fixed by https://github.com/swaywm/wlroots/pull/3027

This is now ready to review.

Overall LGTM, I don't think I understand fully everything but I got the gist of it. Do you want another reviewer on it?

@kennylevinsen, if you had a bit of time to double-check this PR, that would be helpful! Let me know if you don't, no worries. :)
@bl4ckb0ne, let me know if you have any specific questions about this PR.

Fails in test:
00:00:00.450 [DEBUG] [wlr] [backend/drm/drm.c:1096] Reallocating CRTCs
00:00:00.450 [DEBUG] [wlr] [backend/drm/drm.c:1107] State before reallocation:
00:00:00.450 [DEBUG] [wlr] [backend/drm/drm.c:1113]   'DP-1' crtc=0 state=1 desired_enabled=1
00:00:00.450 [DEBUG] [wlr] [backend/drm/drm.c:1113]   'HDMI-A-1' crtc=-1 state=0 desired_enabled=0
00:00:00.450 [DEBUG] [wlr] [backend/drm/drm.c:1113]   'DP-2' crtc=1 state=1 desired_enabled=1
00:00:00.450 [DEBUG] [wlr] [backend/drm/drm.c:1113]   'HDMI-A-2' crtc=-1 state=0 desired_enabled=0
00:00:00.450 [DEBUG] [wlr] [backend/drm/drm.c:1113]   'DP-3' crtc=-1 state=0 desired_enabled=0
00:00:00.450 [DEBUG] [wlr] [backend/drm/drm.c:1113]   'HDMI-A-3' crtc=-1 state=0 desired_enabled=0
00:00:00.450 [DEBUG] [wlr] [backend/drm/drm.c:1164] State after reallocation:
00:00:00.450 [DEBUG] [wlr] [backend/drm/drm.c:1171]   'DP-1' crtc=0 state=1 desired_enabled=1
00:00:00.450 [DEBUG] [wlr] [backend/drm/drm.c:1171]   'HDMI-A-1' crtc=-1 state=0 desired_enabled=0
00:00:00.450 [DEBUG] [wlr] [backend/drm/drm.c:1171]   'DP-2' crtc=1 state=1 desired_enabled=1
00:00:00.450 [DEBUG] [wlr] [backend/drm/drm.c:1171]   'HDMI-A-2' crtc=-1 state=0 desired_enabled=0
00:00:00.450 [DEBUG] [wlr] [backend/drm/drm.c:1171]   'DP-3' crtc=-1 state=0 desired_enabled=0
00:00:00.450 [DEBUG] [wlr] [backend/drm/drm.c:1171]   'HDMI-A-3' crtc=-1 state=0 desired_enabled=0
00:00:00.450 [INFO] [wlr] [backend/drm/drm.c:1453] connector DP-1: Requesting modeset
00:00:00.450 [DEBUG] [sway/desktop/output.c:839] New output 0x1ec6230: DP-1
00:00:00.450 [DEBUG] [sway/config/output.c:351] Turning on output DP-1
00:00:00.450 [DEBUG] [sway/config/output.c:329] Output DPI: 162.560000x161.364706
00:00:00.450 [DEBUG] [sway/config/output.c:382] Auto-detected output scale: 1.000000
00:00:00.450 [DEBUG] [sway/config/output.c:412] Committing output DP-1
00:00:00.450 [DEBUG] [wlr] [types/wlr_output.c:694] Attaching empty buffer to output for modeset
00:00:00.450 [DEBUG] [wlr] [types/wlr_output.c:513] Choosing primary buffer format 0x34325241 for output 'DP-1'
00:00:00.450 [DEBUG] [wlr] [render/swapchain.c:105] Allocating new swapchain buffer
00:00:00.454 [DEBUG] [wlr] [render/gbm_allocator.c:127] Allocated 3840x2160 GBM buffer (format 0x34325241, modifier 0x100000000000004)
00:00:00.454 [DEBUG] [wlr] [render/gles2/renderer.c:139] Created GL FBO for buffer 3840x2160
00:00:00.455 [DEBUG] [wlr] [backend/drm/atomic.c:35] connector DP-1: Atomic test failed (modeset): Invalid argument
00:00:00.455 [DEBUG] [wlr] [types/wlr_output.c:712] Output modeset test failed, retrying without modifiers
00:00:00.455 [DEBUG] [wlr] [types/wlr_output.c:513] Choosing primary buffer format 0x34325241 for output 'DP-1'
sway: types/wlr_output.c:661: output_attach_empty_buffer: Assertion `!(output->pending.committed & WLR_OUTPUT_STATE_BUFFER)' failed.

Fixed up multi-GPU issues: with drm_surface_lock gone, the multi-GPU copy was gone too, and we were trying to use direct scanout without copying. Also we shouldn't strip LINEAR from the format if allow_modifiers = false.


pip3 install -v -e

This command in installation is giving error.
-e option requires 1 argument
Also, the command python3 setup.py develop  gives following error
[Errno 13] Permission denied: '/usr/local/lib/python3.8/dist-packages/test-easy-install-10715.write-test'

pip3 install -v -e . --user

Running command python setup.py egg_info
WARNING: Discarding file:///home/adc_1/scaledyolov4/YOLOX. Command errored out with exit status -11: python setup.py egg_info Check the logs for full command output.
ERROR: Command errored out with exit status -11: python setup.py egg_info Check the logs for full command output.
i am gettng this erro when running the command


update with openShift Local

Fix #705

Codecov Report
Base: 67.92% // Head: 67.92% // No change to project coverage :thumbsup:

Coverage data is based on head (2ce56eb) compared to base (3b86ecd).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #706   +/-   ##
=======================================
  Coverage   67.92%   67.92%
=======================================
  Files         114      114
  Lines        6619     6619
  Branches     1157     1157
=======================================
  Hits         4496     4496
  Misses       2123     2123

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


ModuleNotFoundError

Trying this plugin hoping to move from "Domoticz-TinyTUYA-Plugin" and I'm getting the following the following errors:
2024-12-04 07:51:49.515 Error: LocalTUYA: (tinytuyalocal) failed to load 'plugin.py', Python Path used was '/opt/domoticz/userdata/plugins/Domoticz-TinyTUYA-Local-Plugin/:/usr/lib/python39.zip:/usr/lib/python3.9:/usr/lib/python3.9/lib-dynload:/usr/local/lib/python3.9/dist-packages:/usr/lib/python3/dist-packages:/usr/lib/python3.9/dist-packages'.
2024-12-04 07:51:49.522 Error: LocalTUYA: Traceback (most recent call last):
2024-12-04 07:51:49.522 Error: LocalTUYA: File "/opt/domoticz/userdata/plugins/Domoticz-TinyTUYA-Local-Plugin/plugin.py", line 39, in <module>
2024-12-04 07:51:49.522 Error: LocalTUYA: import tinytuya
2024-12-04 07:51:49.522 Error: LocalTUYA: File "/usr/local/lib/python3.9/dist-packages/tinytuya/__init__.py", line 92, in <module>
2024-12-04 07:51:49.522 Error: LocalTUYA: from .core import *
2024-12-04 07:51:49.522 Error: LocalTUYA: File "/usr/local/lib/python3.9/dist-packages/tinytuya/core.py", line 121, in <module>
2024-12-04 07:51:49.522 Error: LocalTUYA: raise ModuleNotFoundError('No crypto library found, please "pip install" cryptography, pycryptodome, or pyaes')
2024-12-04 07:51:49.522 Error: LocalTUYA: ModuleNotFoundError: No crypto library found, please "pip install" cryptography, pycryptodome, or pyaes

I'm running both plugins in the same container, will that work? I have installed cryptography.
When running the wizard inside the container all seems to work fine until polling the devices where I'm greeted with the following errors:
Scanning local network for Tuya devices...
    0 local devices discovered

Polling local devices...
    [Hanglamp                 ] Error: No IP found
    [Kachel woonkamer         ] Error: No IP found
    [Kantoor                  ] Error: No IP found
    etc

My devices are on a separate IoT network, could this be causing this issue? The plugin probably only scanning the current subnet?

I have always had the log level "info" of "Domoticz-TinyTUYA-Plugin" turned off, when turning it on I'm getting similar errors as shown above, so I'm guessing this not to be the issue:
2024-12-04 09:15:07.683 Error: TinyTUYA: (tinytuya) failed to load 'plugin.py', Python Path used was '/opt/domoticz/userdata/plugins/Domoticz-TinyTUYA-Plugin/:/usr/lib/python39.zip:/usr/lib/python3.9:/usr/lib/python3.9/lib-dynload:/usr/local/lib/python3.9/dist-packages:/usr/lib/python3/dist-packages:/usr/lib/python3.9/dist-packages'.
2024-12-04 09:15:07.686 Error: TinyTUYA: Traceback (most recent call last):
2024-12-04 09:15:07.686 Error: TinyTUYA: File "/opt/domoticz/userdata/plugins/Domoticz-TinyTUYA-Plugin/plugin.py", line 67, in <module>
2024-12-04 09:15:07.686 Error: TinyTUYA: import tinytuya
2024-12-04 09:15:07.686 Error: TinyTUYA: File "/usr/local/lib/python3.9/dist-packages/tinytuya/__init__.py", line 92, in <module>
2024-12-04 09:15:07.686 Error: TinyTUYA: from .core import *
2024-12-04 09:15:07.686 Error: TinyTUYA: File "/usr/local/lib/python3.9/dist-packages/tinytuya/core.py", line 121, in <module>
2024-12-04 09:15:07.686 Error: TinyTUYA: raise ModuleNotFoundError('No crypto library found, please "pip install" cryptography, pycryptodome, or pyaes')
2024-12-04 09:15:07.686 Error: TinyTUYA: ModuleNotFoundError: No crypto library found, please "pip install" cryptography, pycryptodome, or pyaes

Think it's my subnet.

Think I have it working now, although I'm not sure if part of this comes from the fact the devices already were imported from the cloud plugin.
Still have one question though: I'm getting 6 new devices tomorrow, will those be added to Domoticz automagically?

Spun up a separate Domoticz instance, added the plugin, ran the wizard and I'm greeted with the following error and no devices were added:
2024-12-04 09:54:15.905 Error: LocalTuya: handleThread: 'ip' line 183
So I'm still thinking it's my subnet.

Eureka! I removed a device from my Tuya account just to add it again but now on my main LAN instead of my IoT LAN and now the IP address was found. A restart of Domoticz and the device was added there too.
So: it would be great if the plugin would also scan over multiple subnets or (probably better) the possibility to add a subnet other than the one Domoticz is on.
Still testing what happens when I add the IP addresses to devices.json by hand.


Rework internal session handling and revive session API

Maintaining connection state is just part of the story - RIG is also about keeping track of who is online, that is, users and their devices/frontends/connections.
Terminology

A session is identified by the JWT's ID claim (jti). Consequently, connections not associated with a JWT do not belong to any session.
All connections a user creates with a single JWT (same jti) belong to the same session. Likewise, a user using multiple JWTs (different jti) can create connections that belong to different sessions. RIG has no notion of user, but instead handles sessions only.

Note: The Session module introduced by #217 is specific to the longpolling feature and it's meaning is not related to what is described here.

Implementation details

One session manager per node
Conn procs send heartbeat to their local manager
Heartbeats contains remote socket and decoded JWTs, if available
Session managers adds heartbeat info to DeltaCrdt.AWLWWMap
Session manager join pg2 group and periodically sets up delta_crdt neighbors using that group

Note: If this works well, we should probably follow up with using the same technique for filter supervisors - currently, conn procs periodically refresh subscriptions with all filter supervisors, but it probably suffices to tell only the local one and let delta_crdt take care of state dissemination.

The Session Manager

receives blacklist requests
checks jwt expiration
sends connection termination messages
publishes “user/device went online (+jwt +nConnections)” and “user/device went offline (+jwt +reason)” events to kafka
provides the list of online users/connections to :rig_api

Session API

How many connections are associated to a session?

Possible enhancements to the Session API a.k.a. open issues

Is user x online? <-- to answer this, we'd need a relation between JWT IDs and user IDs. Perhaps provide an endpoint to query for sessions that have a certain property set in their associated JWT?
Who is online? <-- same thing here: easy to do for sessions, but we'd have to use configuration or a query parameter to extract the user ID from the associated JWTs.
Also: Do we need to find out about the online state of users with certain properties?

This feature-set can be further described with the following user stories:
Story 1
Alice has a subscription for a service x. Alice has a problem with said service and wants to create a ticket on the service's customer support page. An employee of the customer support department of service x sees that Alice just created a ticket and, furthermore, sees that Alice is currently online.
Story 2
[..] The employee can now react and send out a co-worker to get in touch with Alice.
Story 3
[..] The employee also sees that Alice's device's locale is set to "en-US" and specifically asks for an english-speaking co-worker to get in touch with Alice
Story 4
[..] The employee also sees that Alice's device's locale is set to "en-US" and she is located in the US and sends out an english-speaking co-worker who is familiar with service's x products in the US to get in touch with Alice.
[..] ... Story is a continuation of Story 1


Need only single date picker

I would like to use a single date picker. Where there is no timepicker on the button, there will be only a datepicker.

Please let me know.

@Jasenkoo thank you so much
I was able to hide the time picker
:enableTimePicker = "false"


Complete Pocket Loot Generation Code (NOT TESTED)

I have completed the loot generation in pockets, i haven't tested it out yet but would like if anyone would test it out for me. if its working.

By the way, check the last commit. Its where the complete code for generation of loot is.


drivers: mpu9250: magnetometer data read fix

The magnetometer data read from AK9863 is assumed to be big endian
(like the accelerometer & gyroscope data).
However it is in little endian, which means the appropriate byteorder function is sys_le16_to_cpu().
See the MPU925 register map: https://3cfeqx1hf82y3xcoull08ihx-wpengine.netdna-ssl.com/wp-content/uploads/2017/11/RM-MPU-9250A-00-v1.6.pdf
At 5.6 HXL to HZH: Measurement Data
Signed-off-by: Loris Schmit<EMAIL_ADDRESS>

cc: @dchat-nordic

I can confirm - the data is actually little endian.

Please fix the compliance failure:
Error: See https://docs.zephyrproject.org/latest/contribute/#commit-guidelines for more details

1a268bbab1b15f489f5509b07e84b6eab1168809: author email (lschmit<EMAIL_ADDRESS>needs to match one of the signed-off-by entries.
1a268bbab1b15f489f5509b07e84b6eab1168809: author email (lschmit<EMAIL_ADDRESS>does not follow the syntax: First Last <email>.
Error: See https://docs.zephyrproject.org/latest/contribute/#commit-guidelines for more details

1: UC2 Signed-off-by: must have a full name
3: UC4 Line exceeds max length (210>75): "The magnetometer data read from AK9863 is assumed to be big endian (like the a

This still needs to be fixed

Hi, I fixed the compliance failure. However the compliance checks and license scan don't run. Could please check up on that?

Hi, I believe I finally got it right. Please run the compliance checks again. Sorry for the trouble, this is my first contribution.

@gmarull @teburd @avisconti will one of you please take a look?

Nice fix


replace clipboard-win by copypasta

https://github.com/alacritty/copypasta
Should fix #637

copypasta depends on clipboard-win...


Add hyperlinks to some notes

Fixes #1462 add a hyperlink to the comment for whole project.
Make sure that:

[x] You have read the contribution guidelines.
[x] You submit test cases (unit or integration tests) that back your changes.
[x] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

@THyyy Please fix the ci.

maven-checkstyle-plugin‘s 3.1.0 version makes a new question.

maven-checkstyle-plugin‘s 3.1.0 version makes a new question.

@THyyy Please fix the new ci failure.

I suggest you run the mvn clean install instead of mvn clean install -Dmaven.javadoc.skip=true in local to have a test first.


Issue 5 generate metrics

Generating metrics and bike usage data in csv and json format.

Cannot be merged


No new constructor call

Just faced with a situation when I tried to init Swiper calling a constructor with no new expression, like so:
var s = Swiper(selector, options);

instead of
var s = new Swiper(selector, options);

Supporting both cases became a somewhat common practice within components, for example, component-tip has a line handling such initialization cases.
Usually, it looks similar to:
if (!(this instanceof Swiper)) return new Swiper(el, options);

Is there a sense to add a such detection, or you better prefer keeping more strict version of initialization call?

I prefer to keep it strict and syntax-correct, but such addition will be useful, will add such line


Run example pipelines in SAP Data Hub, developer edition 2.4

Tutorial URL: https://developers.sap.com/tutorials/datahub-docker-v2-examples.html
Please specify the step you are referring to
Copy any row of the terminal output and paste it in the frame below and click on Validate.
[2019-04-16 20:22:47.813] 0,4,25.555219261860465,47.41223556836962,532.4126972690706,1.017645583549283,23.99690674702611,59.746879572444016,0,719.2882102905135,409.22321564322885
Sorry, that’s incorrect. Please try again.
Why is this wrong?

I'm having the same issue. That checker does not seem to work until you get to Store Sensor Data in HDFS in SAP Data Hub.

This should work for now.

Thank you for your feedback. We haven't heard from you in the past 30 days, so we are closing the issue.
If you still have questions, feel free to reopen the issue.

Thanks ist it works


Warn last user unsubscribing from a private stream

Only current subscribers can add others to a private stream, so when the last subscriber is remove, the stream becomes archived automatically.
When the only user currently subscribed to a private stream attempts to unsubscribe from it, we should add a warning explaining this situation to the confirmation modal.
Current modal:

Additional text to be added below (as its own paragraph) in this situation:

Because you are the only subscriber, this stream will be automatically archived.

Please be sure to tag the new string for translation.

@zulipbot claim

@zulipbot claim

@TusharMinche Please pick one unclaimed issue to work on to start with.

@TusharMinche Please pick one unclaimed issue to work on to start with.

Can you assign me some unclaimed Good First Issue to start?


Add Google.Cloud.Diagnostics.AspNet 4.0 support

It would be really nice to continue to support asp.net. ASP.NET is supposed to be a supported framework and if Google.Cloud.Diagnostics.AspNet isn't upgraded like the .net core version, then we can't use GAX 3.0. Which means we can't use the updated versions of any of the other libraries.

Hi Brett,
While I agree that we'd do this in an ideal world, it's not clear that there's enough demand for this to be worth the maintenance burden. The 3.0.0 release of the NuGet package has only had 120 downloads in over three months, for example. Supporting ASP.NET involves significantly more maintenance burden in terms of integration tests etc, compared with ASP.NET Core.
We could potentially revive it for just long enough to produce a 4.0 that depends on GAX 3.0.0, but then deem that "end of line" for anything other than patching significant issues.
Adding Amanda to the conversation now, for her perspective.

Thanks @jskeet. I understand the reasoning. But just wanted to point out that this library does claim to support ".NET Framework 4.5+". And while maybe not a lot of people use it, certainly some do. It's definitely nice to have stackdriver error logging built into our asp.net applications that we've moved over to google cloud.
GAX 3.0 support alone would be sufficient for our needs.

Ah, we need to update our list of supported platforms - from GAX 3.0 onwards, it's .NET 4.6.1+, not 4.5.
I'll talk it through with Amanda tomorrow - I think we could probably do a "just this one release" but then drop ASP.NET again - basically to just support the existing feature set with GAX 3.0, but no further development.
(There will always be things that "not a lot of people use, but some do" - that in itself doesn't justify us spending time on something, where that time could be spent on something that would benefit more users. We need to balance our use of resources carefully.)

That alone would be good enough for me! Thanks Jon.

I've released 4.0.0-beta01 now. @amanda-tarafa is going to do some local testing on it next week and then we can do a GA.

This has now been released: https://www.nuget.org/packages/Google.Cloud.Diagnostics.AspNet/

Thanks @jskeet and @amanda-tarafa for doing this. Works perfectly!


How to set action column as the last column of a table in  ?

By default action column shows as a first column of a table .But i want to customize it as a last column.


Allow to exclude test files from conda package

Currently, whenever a recipe specifies test files, these test files end up in the final conda package. For example,
source:
  path: ../
build:
  number: 0
  noarch: python
package:
  name: test
  version: v1
requirements:
  run:
    - python >=3.9
tests:
  - script: test -f foo.txt
    files:
      source:
        - foo.txt

causes foo.txt to end up in /etc/conda/test-files/test/0 of the final package.
In some cases, it would be desirable to not include these test files into the final package. Would it be possible to introduce a flag to prevent this behavior?

@pavelzw suggested that this might even make sense to do when --no-include-recipe is specified, I personally can't comment on that in detail :smile:

Yeah this is how tests currently work. We could also think about creating additional -test packages automagically with a flag.

Side-note: I also just realized that specifying --no-test still copies these files 🫣


Add count to join and batch node labels

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Proposed changes

This PR adds the configured count number to the join node when in manual mode. It also adds a + if set to "and all subsequent messages" mode.
It also adds the count to the batch node label, or the timeout value when in timeout mode.
Checklist

[x] I have read the contribution guidelines
[x] For non-bugfix PRs, I have discussed this change on the forum/slack team.
[x] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Coverage: 68.241%. Remained the same when pulling 47bacaf58ad97decefff6d50407fbdcdc850f648 on Add-count-to-join-and-batch-node-labels into a607ee90e0b0edd59c83adebaf7d9589af1e8dd2 on dev.


Expose UI based system configuration for update/upgrade settings

https://github.com/subutai-io/subos/issues/291

done


Added command line option for custom northstar directory

Added command line option for custom northstar directory
https://github.com/orgs/R2Northstar/projects/1#card-76312632

Can you also add this to the wiki section on command line args?

NorthstarWiki#31