Temporary Export Files Not Deleted Automatically, Leading to Storage Issues

Describe the bug
I have been using Label Studio for almost a year for image annotation (object detection, segmentation, etc.). Recently, my remote server has been running out of storage space. Upon investigation, I found that temporary files were not being deleted automatically. This issue seems related to Docker itself.
After running the Label Studio container, I noticed that the directory /var/lib/docker/overlay2/2cba2b496509f78e63274c6b9bcff18eb43c0fbe55c06ecfc684a1f883902aa3/merged/tmp (associated with the Label Studio container layer) contained thousands of zipped files introduced after each export, which were supposed to be deleted automatically.
To Reproduce

Run Label Studio using the following command:docker run -d -it -e LABEL_STUDIO_DISABLE_SIGNUP_WITHOUT_LINK=true -p 8080:8080 -v $(pwd)/mydata:/label-studio/data heartexlabs/label-studio:latest

Export any project.
Observe that the exported images are saved in the mentioned location as zipped files, which are not deleted automatically.

Expected behavior
Temporary files created during the export process should be deleted automatically to prevent storage issues.
Screenshots

Environment (please complete the following information):

OS: Ubuntu 22.04
Label Studio Version: latest

/jira create

Hi @MosbehBarhoumi - we've made some changes in this area relatively recently: https://github.com/HumanSignal/label-studio/pull/5612 - it is possible that a bug could have been introduced. We'll investigate!


Underscores inserted in enum name with mixed lowercase and numbers

Given an enum definition like
enum Format {
    mp3 = 1;
    m4a = 2;
}

the enum names in Java will be "MP_3" and "M_4A"
Expected result was "MP3" and "M4A".
If the definition is uppercased this works as expected.
This may be a regression introduced when fixing https://github.com/morimekta/providence/issues/46

Fixed, now with much more tests.


Added feature CNI_PLUGIN_INSTALL_POLICY

Signed-off-by: Pulkit Jain<EMAIL_ADDRESS>

Codecov Report

Merging #3454 (1f91476) into main (ed0ad19) will decrease coverage by 22.82%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main    #3454       +/-   ##
===========================================
- Coverage   65.28%   42.46%   -22.83%
===========================================
  Files         268      200       -68
  Lines       26900    24330     -2570
===========================================
- Hits        17563    10332     -7231
- Misses       7432    12934     +5502
+ Partials     1905     1064      -841

Flag
Coverage Δ

kind-e2e-tests
?

unit-tests
42.46% <ø> (+0.02%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/ovs/openflow/default.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/util/runtime/runtime.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/agent/openflow/groups.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/apis/controlplane/types.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/apis/controlplane/helper.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/agent/nodeportlocal/k8s/annotations.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/ovs/openflow/logs.go
9.52% <0.00%> (-90.48%)
:arrow_down:

pkg/apis/controlplane/register.go
0.00% <0.00%> (-90.48%)
:arrow_down:

pkg/agent/controller/networkpolicy/reject.go
0.00% <0.00%> (-87.91%)
:arrow_down:

pkg/flowaggregator/certificate.go
0.00% <0.00%> (-77.48%)
:arrow_down:

... and 190 more

This title may be more proper: Add SKIP_CNI_BINARIES env var to support skipping installing specified cni bins

/test-all

/test-all


kvm/ceph: Only if a port number has been specified define in the XML

Description
Ceph used to use port 6789 (no need to specify it), but with the messenger v2
from Ceph it switched to port 3300 while 6789 still works.
librados/librbd/libvirt will automatically figure out the ports to use if none is
specified.
Therefor there is no need for CloudStack to explicitely define the port in the XML
passed to Libvirt or Qemu.
Leave blank if no port number has been defined by the user.
Types of changes

[x] Enhancement (improves an existing feature and functionality)

@wido reminder - can you help do the next https://github.com/ceph/rados-java release? It would be great if we can do it soon/before 4.15 to support the latest ceph release. Thanks.
@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos7 ✔debian. JID-1629

@rhtyd I actually have rados-java 0.6.0 ready. Just need to have somebody upload it to maven central.

@blueorangutan test

@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-2252)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 41608 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr4231-t2252-kvm-centos7.zip
Intermittent failure detected: /marvin/tests/smoke/test_privategw_acl.py
Smoke tests completed. 83 look OK, 0 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

seems ready to merge, right @wido @rhtyd ?

For me it is


abn_cells

@JuliaRegistrator register()

Error while trying to register: "Pre-release version not allowed"


Prompt Python, Java, and JS users to install AppMap into mappable project

When a user opens a mappable Ruby project that does not have AppMap installed they see this:

It's not the same for Java, Python, and JS users but it should be.

It appears it has been done on purpose in https://github.com/getappmap/vscode-appland/commit/69f9936b7640c4e6c9bd22615284321324011ada — however, the commit message sadly lacks any rationale. @dustinbyrne , do you remember why it was done?

We were originally testing the prompt solely with Rails users to see how it converted.

Should this issue hold off until we've implemented some of the installer QoL fixes?

I have this already on a branch
On Mon, Jun 5, 2023 at 11:33 AM Dustin Byrne @.***>
wrote:

Should this issue hold off until we've implemented some of the installer
QoL fixes?
—
Reply to this email directly, view it on GitHub
https://github.com/getappmap/vscode-appland/issues/698#issuecomment-1577026907,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAVC6YUY73RZ7KVWPKISR3XJX33HANCNFSM6AAAAAAYURVCQY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

We were originally testing the prompt solely with Rails users to see how it converted.

Are you sure? The aforementioned commit limits it to Rails — it seems it used to had worked universally before.

@brikelly @dustinbyrne I feel like we may as well roll this out for Python + Java users now.

Agreed, let's get this one done

:tada: This issue has been resolved in version 0.101.0 :tada:
The release is available on:

v0.101.0
GitHub release

Your semantic-release bot :package::rocket:


Program Analysis tab report links broken

This came up at the sprint this week and also on a recent HUB post.
When the change from master-detail to lookup occurred (version 1.15), the report charts on the Funding Program weren't updated.  Thus causing this error.

Report chart in version 1.13

Other report chart.  I think this one was fixed, but will confirm.

Funding Program Analytics (second report) works as expected.

Tried in scratch org to fix, and recreate bug:

Maybe issue is in packaging org?  Lightning page has been changed since May 10, 2019

Program Analysis tab was removed in this WI


lang/org: Package orgit if magit is enabled

https://github.com/magit/orgit

Looks good to me. Thanks again!


proper options parsing

Implement option parsing with getopts, so that we can add more customisations in the future

Implemented  in https://github.com/ColasNahaboo/cgibashopts/releases/tag/v4.1.0


Rerquesting new template for QNAP NAS FW QTS 4.5.2

Hello there,
I am a Product Manager working with QNAP. We have released a new FW version of our NAS QTS 4.5.2 recently.
We have done a major upgrade to SNMP MIB with this version.
I would like to request your support to update the new Zabbix Template to support this new version of the firmware.
Many of our customers who use Zabbix are requesting for this update. So kindly help.
Details: https://www.qnap.com/en/release-notes/qts/<IP_ADDRESS>0/20210406
My email<EMAIL_ADDRESS>Please feel free to contact me.
Regards,
Amol Narkhede
Product Manager.
QNAP Systems Inc Taipei.

Dear Albin,
Thank you for contacting me on my company email.
As discussed we are ready to provide you access to our device. I have already sent you multiple mails. Not sure if you are receiving those. Kindly reply.
Regards,
Amol

NAS has been received and I will begin working to support the new version of the firmware. Me and Amol exchange correspondence through e-mail. I will be reaching out to you during next week.

Noted Albin.
Thank you.
Amol
On Sun, Sep 12, 2021 at 2:40 AM Albin Lindström @.***>
wrote:

NAS has been received and I will begin working to support the new version
of the firmware. Me and Amol exchange correspondence through e-mail. I will
be reaching out to you during next week.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/albinbatman/zabbix-qnap-template/issues/3#issuecomment-917454362,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AASQSPW64HVXE63S4R2BUWLUBOPBRANCNFSM43FKL5CA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Hello Albin,
Its been a long time we have been following up with you.
We have even sent NAS to you so that you can help with the above query. But even after following up for long time, we are not getting any response form you. Kindly do let us know if we should contact anyone else, who can actually  work on this matter and respond to our mails.
@Zabbix: Please check this. We are not getting ant response or support. You may assign any other person.
Thank you.
Amol

Hi @amol-narkhede,
Many apologies for the delay, it has been due to various factors. I have now pushed a template for zabbix-6.x for the new firmware OIDs. Do you want backward compatibility with lower Zabbix versions?

Hi Albin, Yes we need to have backward compatibility.

Do you want backward compatibility with lower Zabbix versions?
Answer: Yes, we would like to have it, Albin. Please do help.
Regards,
Amol
On Sat, Feb 19, 2022 at 1:22 AM Albin Lindström @.***>
wrote:

Hi @amol-narkhede https://github.com/amol-narkhede,
Many apologies for the delay, it has been due to various factors. I have
now pushed a template for zabbix-6.x for the new firmware OIDs. Do you want
backward compatibility with lower Zabbix versions?
—
Reply to this email directly, view it on GitHub
https://github.com/albinbatman/zabbix-qnap-template/issues/3#issuecomment-1044873377,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AASQSPTJSSBZJ366XXUY4KLU3Z55NANCNFSM43FKL5CA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>


Copy cpp example server code from foxglove_bridge

Public-Facing Changes

Copied cpp server implementation from https://github.com/foxglove/ros-foxglove-bridge
Migrated cpp builds to use conan 2

Description
The example cpp server implementation was heavily outdated with regards to the current specification. This PR copies most of the server code from https://github.com/foxglove/ros-foxglove-bridge with some minor adaptations to make it compatible with the existing example server.
Fixes (partially) #233
Fixes FG-1596

Once this is merged and/or released on conan will it be possible to remove the duplicated code from the ros-foxglove-bridge repo?

Note that to update the release on conan you will need to manually modify https://github.com/conan-io/conan-center-index/tree/master/recipes/foxglove-websocket

Once this is merged and/or released on conan will it be possible to remove the duplicated code from the ros-foxglove-bridge repo?

I don't think that the ros buildfarm supports conan recipes. What could work is to add this repo as a git submodule in ros-foxglove-bridge. Alternatively, release the websocket server (without the example) as a standalone ros package on which ros-foxglove-bridge could depend on

Note that to update the release on conan you will need to manually modify https://github.com/conan-io/conan-center-index/tree/master/recipes/foxglove-websocket

Should I bump the version number then to 0.1.0?

Maybe 1.0.0 since this is now in production use and being recommended?

We explored some use of submodules in https://github.com/ros-tooling/rosbag2_storage_mcap/pull/27. I think the conclusion was it is preferable to use FetchContent. You can see how it is currently done in https://github.com/ros2/rosbag2/tree/rolling/mcap_vendor

Bumped the version numbers in https://github.com/foxglove/ws-protocol/commit/803b8a2b4d3f0439ccef22c0b66d09d7e3ec83b3 and accidentally pushed that commit to main (which automatically marked this PR as merged). I will change the setting to disallow direct pushes to main


Settings UI Improvements

Is your proposal related to a problem?
Settings modal is too big, which is not as per UI standards. Here are few issues,

Modal is too big.
To save or close, user has to scroll down the modal.
No default action (Close or Save changes)
No Close button at the title bar.
Most of the time user open settings to add/remove symbols rest all settings are not often changed. Even if a new symbol is added/removed, user has to scroll down to save the changes.

Describe the solution you'd like
Here's my proposal,

Group the different sections using accordions.
Open first accordion by default.
Make two column rows.
Have help icon and move all help text as tooltip.
Default button selected is "Save"

Describe alternatives you've considered
Alternative option is to have two options, settings and symbols. Move everything other than symbols and fiats into settings.
Additional context

This is a really good suggestion.
I will change accordingly.
Just one issue is, I am still testing #77, which had massive refactoring.
Once I am confident with that PR, then I will work on this.
Thanks @santoshbmath

This is a really professional and good looking wireframe @santoshbmath
It's nice to see people contributing in such a way.
I really like this proposal for the Global Settings page, it's much better, I had problems more than once when scrolling over the page with the mouse my numbers get changed by the scrolling wheel without me noticing it.
Let's get #77 tested and merged so @chrisleekr can move forward with new code.

@chopeta @chrisleekr glad that you liked the wireframe. :)

@santoshbmath I have updated the settings UI in PR #77. This change will be merged later.


inaccessibility of options panel

Issue description:
Options panel is inaccessible. For example, the enable/disable selections are not standard checkboxes, or my screen reader cannot see the checkboxes. This makes it impossible for me to select or unselect something. If these issues could be fixed, that would be great!
Version used:
(Did you try using the develop branch from github? There's a chance your issue has already been adressed there)
Latest (TGM)
Using theme_mods or options?
theme_mods
Code to reproduce the issue (config + field(s))
'type'        => 'toggle', or may be with other 'input types'

I'm sorry for the delay here, I'll get on this as soon as possible. It might be a couple more days since I'm currently with fever.

I believe this was just fixed in the development branch for checkboxes, toggles & switches.
Tweaks will be included in the 2.4.0 version. 👍
Closing this for now, if the issue persists after 2.4.0 is released (or if you test the develop branch and see that the issue still occurs there) please reopen.


jest-circus feature parity with jest-jasmine

We need to make sure jest-circus is compatible with existing tests.
Right now i'm using Jests test suite to see if tehre's any errors.
to do that we can replace this require
https://github.com/facebook/jest/blob/19384094dc7ac5cd77e4eacf611d76abe5837063/packages/jest-runner/src/run_test.js#L63
with a path to the adapter:
{YOUR_JEST_REPO_PATH}/packages/jest-circus/build/legacy_code_todo_rewrite/jest_adapter.js`

and run
./jest --testRunner '<rootDir>/packages/jest-circus/build/legacy_code_todo_rewrite/jest_adapter.js'

PRs that i opened but never had a chance to merge (need to come back and fix a few things):
https://github.com/facebook/jest/pull/3819
https://github.com/facebook/jest/pull/3824
also this is a new feature that was added to jasmine https://github.com/facebook/jest/pull/4016/files
@suchipi

Thanks @aaronabramov, I'll take a look at this this weekend

I'm confused; I ran the tests with the jest-circus adapter (as far as I can tell) and I'm not seeing any failures.
I ran:
./jest --testRunner '<rootDir>/packages/jest-circus/build/legacy_code_todo_rewrite/jest_adapter.js'

In the repo root, and saw no failures except for some tests that failed because they depended on mercurial, which I didn't have installed.
After installing mercurial, I ran the same command again, and saw no failures.
I was expecting to see some failures and that those would lead me to the work that needed to be done. Am I misunderstanding the situation?

All the integration tests will still use Jasmine. You could probably change Jest's default config to use jest-circus and then see which integration tests fail, or go into each folder in integration_tests and run individually with circus.

Ok, changing the default for testRunner in jest-cli/src/cli/args.js and running yarn run build worked, I see the failures now. Thanks!

I'm looking at integration-tests/__tests__/location_in_results.test.js


Allow creating attributes with values in one mutation

We need to change the signature of productAttributeCreate mutation to allow creating attribute values in the same mutation. This is required by the new UI for the product attributes dashboard.

@marcingebala should we change update mutation as well?

I think we should do that only in the "create" mutation. "Update" mutation is more problematic because you would have to always pass the whole list of attributes; also, if you accidentally passed an empty list you'd remove all values. Take a look at MenuCreate and MenuUpdate, we did a similar change there recently.


Rewrite meta_description and meta_title to depend upon the current context

closes #4850

fixed meta_description and meta_title when used within a {{#foreach}}
meta_description and meta_title now depend upon the current context
to get the right string (author bio, tag description, ...).
Note: ghost_head.js and ghost_head_spec.js have been touched to add
the required context information when calling the helpers.

Just given this a quick once-over and spotted a typo, otherwise this is looking really good. Will take it for a proper spin tomorrow

Fixed the typo and rebased onto master

Thanks for merging, @ErisDS :)


Moved hue2rgb() externally to allow strict compilers (Safari) to work

This small change allows Safari 9.1 to work with the latest builds.

Checks are the same as the previous build. ;)

Ok this looks good, merged :)


Add ResNet50V2 Nhwc model tests

PTAL, thanks! @fujunwei @BruceDai

Webnn-samples and polyfill keep 101 nhwc model tests.  @fujunwei

Merge it, thanks for interating patiently.


React 16.2.0 produces Module not found error

This works fine:
"react": "16.1.1",
"react-dom": "16.1.1",

yarn run v1.3.2
$ react-static start

=> Copying public directory...
=> [✓] Public directory copied: 97.243ms
=> Building Routes...
=> [✓] Routes Built: 4.951ms
=> Building App Bundle...
=> [✓] Build Complete: 4968.120ms
=> [✓] App serving at http://localhost:3000

This produces "Module not found" errors:
"react": "16.2.0",
"react-dom": "16.2.0",

yarn run v1.3.2
$ react-static start

=> Copying public directory...
=> [✓] Public directory copied: 443.031ms
=> Building Routes...
=> [✓] Routes Built: 10.215ms
=> Building App Bundle...
=> [✓] App serving at http://localhost:3000
Failed to rebuild.
./node_modules/react-static/lib/index.js
Module not found: Can't resolve 'react-helmet' in 'd:\my\myProject\node_modules\react-static\lib'

./build/react-static-routes.js
Module not found: Can't resolve 'react-router-dom' in 'd:\my\myProject\build'

./node_modules/react-static/lib/index.js
Module not found: Can't resolve 'react-router-dom' in 'd:\my\myProject\node_modules\react-static\lib'

Versions:

Windows: 10-64
node: 9.2.0
react-static: 4.5.0

Any ideas? Thanks.

Still experiencing this issue?

@tannerlinsley Thanks for asking. Yes, indeed, I still have the same problem. I updated all packages yesterday and my working package.json now is:
{
  "name": "myProject",
  "version": "0.3.0",
  "main": "index.js",
  "license": "MIT",
  "scripts": {
    "start": "react-static start",
    "build": "react-static build",
    "serve": "serve deploy -p 3001"
  },
  "dependencies": {
    "bowser": "^1.8.1",
    "grid-styled": "^2.0.0-11",
    "lazysizes": "^4.0.1",
    "moment": "^2.20.1",
    "react": "16.1.1",
    "react-dom": "16.1.1",
    "react-router": "^4.2.0",
    "react-static": "^4.7.0-beta.0",
    "styled-components": "^2.3.3",
    "styled-system": "^1.1.1"
  },
  "devDependencies": {
    "eslint": "^4.13.1",
    "eslint-config-react-app": "^2.0.1",
    "eslint-config-react-tools": "1.x.x",
    "eslint-plugin-flowtype": "^2.40.1",
    "eslint-plugin-import": "^2.8.0",
    "eslint-plugin-jsx-a11y": "^6.0.3",
    "eslint-plugin-react": "^7.5.1",
    "prettier-eslint": "^8.4.0",
    "serve": "^6.4.3"
  },
  "resolutions": {
    "styled-system": "1.1.1"
  }
}

Changing to
    "react": "16.2.0",
    "react-dom": "16.2.0",

results still in the above mentioned error. I just tried it yesterday. If you tell me, that 16.2.0 works fine on your system, I probably have to try to narrow it down. I am not sure what changed from React 16.1.1 to React 16.2.0 that could cause the error or if this is a Windows specific error. Maybe it is a similar issue like this PR #191, but I have difficulties to understand, why it only occurs with React 16.2.0.

I tried one more thing and included
    "react-helmet": "^5.2.0",
    "react-router-dom": "^4.2.2",

directly in my package.json. Now it works, but I find it strange, that it is not working through the dependencies in the package.json of react-static.

I've got this issue replicated on my machine now :) Now I'm working on a fix.  I agree, this one is pretty strange... I'm not sure what is happening just yet.  Let me know if you find any clues!

Fixed with f96e753b6c7dd305ca476b8578dbeb34bc59236c and 457477d6d6d2db79f95c1a6f01d22cfdc0dcefbe


Is it possible to apply "retainedFileCountLimit" to archived log files

I want to delete archived files after a while. How can this be achieved? Could you please advise on this

+1

In general, the assumption is that logs are being archived for some other process to hoover them up or otherwise deal with them.
On the face of it though, this seems like a reasonable thing to add - when I get a chance, I'll take a look at this and see if there are any complications or problems with it!

@EamonHetherton thanks for getting involved 😻

Closed by #9

Hey, any updates when it will be released? I could really use this feature. Thanks in advance

@alex-pashkov97 sorry, I totally forgot this feature wasn't on NuGet yet! I'll try to get it published tomorrow.

@alex-pashkov97 Done!
https://www.nuget.org/packages/Serilog.Sinks.File.Archive/1.0.2


[Runtime] Shrink ConcurrentReadableHashMap a bit.

We're using a lot of space on the free lists. Each vector is three words, and we have two of them. Switch to a single linked list. We only need one list, as both kinds of pointers just get free()'d. A linked list optimizes for the common case where the list is empty. This takes us from six words to one.
Also make ReaderCount, ElementCount, and ElementCapacity uint32_ts. The size_ts were unnecessarily large and this saves some space on 64-bit systems.
While we're in there, add 0/NULL initialization to all elements. The current use in the runtime is unaffected (it's statically allocated) but the local variables used in the test were tripping over this.

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 5ebdd2d65d045a9dda94d4882476203be3310a61

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 5ebdd2d65d045a9dda94d4882476203be3310a61

Build failed
Swift Test OS X Platform
Git Sha - 5ebdd2d65d045a9dda94d4882476203be3310a61

@swift-ci please test os x platform

@swift-ci please test linux platform


Add jleightcap to the webring

I've enjoyed following merveilles.town members, and came across the recent post about the 256-member limit webring. If my site fits the group, I'll volunteer it: the webring icon is included in the footer: https://jack.leightcap.com/
Thanks for the consideration :)

Hey Jack :)
Nice website, I'm happy to welcome it to the webring, but there's two things:
You set the webring icon width via CSS and it distorts it:
margin: 10px;
  padding: 20px;
  min-width: 10%;
  max-width: 150px;
  max-height: 60%;

The second, could you add a landing page to your domain leightcap.com/ that isn't the domain registrar's?


Plugins not accessible by dokku user

If you're using Dokku - especially for commercial purposes - consider donating to project development via OpenCollective or Patreon. Funds go to general development, support, and infrastructure costs.
If you'd like to sponsor specific functionality, see the project's Sponsoring document.
If you need support for a version of Dokku that is more than a year old, your issue may be closed without an answer. Please upgrade to a recent version before filing an issue.

Description of problem
When installing a plugin, the files are owned by root. Given the umask we are using, the files are NOT accessible by the dokku user.
How reproducible
Every time
Steps to Reproduce
    - role: dokku_bot.ansible_dokku
      vars:
        dokku_plugins:
          - name: clone
            url: https://github.com/crisward/dokku-clone.git

ansible-playbook dokku.yml --tags dokku-plugins
Actual Results
See that all plugins are owned by dokku, but clone is not:
lrwxrwxrwx 1 dokku dokku   44 Jun 15 17:05 checks -> /var/lib/dokku/core-plugins/available/checks/
drwxr-x--- 4 root  root  4096 Jun 16 16:37 clone/
lrwxrwxrwx 1 dokku dokku   44 Jun 15 17:05 common -> /var/lib/dokku/core-plugins/available/common/

Expected Results
Correct ownership of files
Environment Information

dokku report APP_NAME output
-----> uname: Linux xxxx 5.6.1-x86_64-linode134 #1 SMP PREEMPT Wed Apr 1 22:25:48 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
-----> memory:
total        used        free      shared  buff/cache   available
Mem:           7944         233        6960           0         749        7710
Swap:           511           0         511
-----> docker version:
Client: Docker Engine - Community
Version:           19.03.11
API version:       1.40
Go version:        go1.13.10
Git commit:        42e35e61f3
Built:             Mon Jun  1 09:12:22 2020
OS/Arch:           linux/amd64
Experimental:      false
   Server: Docker Engine - Community
    Engine:
     Version:          19.03.11
     API version:      1.40 (minimum version 1.12)
     Go version:       go1.13.10
     Git commit:       42e35e61f3
     Built:            Mon Jun  1 09:10:54 2020
     OS/Arch:          linux/amd64
     Experimental:     false
    containerd:
     Version:          1.2.13
     GitCommit:        7ad184331fa3e55e52b890ea95e65ba581ae3429
    runc:
     Version:          1.0.0-rc10
     GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
    docker-init:
     Version:          0.18.0
     GitCommit:        fec3683

-----> docker daemon info:
Client:
Debug Mode: true
   Server:
    Containers: 0
     Running: 0
     Paused: 0
     Stopped: 0
    Images: 1
    Server Version: 19.03.11
    Storage Driver: overlay2
     Backing Filesystem: extfs
     Supports d_type: true
     Native Overlay Diff: false
    Logging Driver: json-file
    Cgroup Driver: cgroupfs
    Plugins:
     Volume: local
     Network: bridge host ipvlan macvlan null overlay
     Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
    Swarm: inactive
    Runtimes: runc
    Default Runtime: runc
    Init Binary: docker-init
    containerd version: 7ad184331fa3e55e52b890ea95e65ba581ae3429
    runc version: dc9208a3303feef5b3839f4323d9beb36df0a9dd
    init version: fec3683
    Security Options:
     seccomp
      Profile: default
    Kernel Version: 5.6.1-x86_64-linode134
    Operating System: Ubuntu 18.04.4 LTS
    OSType: linux
    Architecture: x86_64
    CPUs: 4
    Total Memory: 7.758GiB
    Name: XXXX
    ID: QJX4:MGZE:57RC:YUOU:OL2M:TRPY:MKIG:MJBV:ZJYF:EZEJ:TTPF:PH7Q
    Docker Root Dir: /var/lib/docker
    Debug Mode: false
    Registry: https://index.docker.io/v1/
    Labels:
    Experimental: false
    Insecure Registries:
     <IP_ADDRESS>/8
    Live Restore Enabled: false

-----> sigil version: 0.6.0
-----> herokuish version:
herokuish: 0.5.5
buildpacks:
heroku-buildpack-multi     v1.0.0
heroku-buildpack-ruby      v207
heroku-buildpack-nodejs    v166
heroku-buildpack-clojure   v84
heroku-buildpack-python    v162
heroku-buildpack-java      v66
heroku-buildpack-gradle    v31
heroku-buildpack-scala     v86
heroku-buildpack-play      v26
heroku-buildpack-php       v166
heroku-buildpack-go        v136
buildpack-nginx            v12
-----> dokku version: dokku version 0.19.11
-----> dokku plugins:
plugn: 0.3.2
00_dokku-standard    0.19.11 enabled    dokku core standard plugin
20_events            0.19.11 enabled    dokku core events logging plugin
app-json             0.19.11 enabled    dokku core app-json plugin
apps                 0.19.11 enabled    dokku core apps plugin
builder-dockerfile   0.19.11 enabled    dokku core builder-dockerfile plugin
builder-herokuish    0.19.11 enabled    dokku core builder-herokuish plugin
buildpacks           0.19.11 enabled    dokku core buildpacks plugin
certs                0.19.11 enabled    dokku core certificate management plugin
checks               0.19.11 enabled    dokku core checks plugin
cat: /var/lib/dokku/plugins/available/clone/plugin.toml: Permission denied
panic: interface conversion: interface {} is nil, not map[string]interface {}
goroutine 1 [running]:
main.TomlGet(0xc000010080, 0x2, 0x2)
github.com/dokku/plugn/plugn.go:30 +0x2d1
github.com/progrium/go-basher.(*Context).HandleFuncs(0xc000096280, 0xc000010050, 0x5, 0x5, 0x0)
/go/pkg/mod/github.com/progrium/go-basher@v0.0.0-20150902213704-ad5de635edd1/basher.go:195 +0x26d
github.com/progrium/go-basher.ApplicationWithPath(0xc000043e48, 0xc000043e78, 0x4, 0x4, 0x62cde8, 0x1, 0xc000016420, 0x18)
/go/pkg/mod/github.com/progrium/go-basher@v0.0.0-20150902213704-ad5de635edd1/basher.go:77 +0x19c
github.com/progrium/go-basher.Application(0xc000043e48, 0xc000043e78, 0x4, 0x4, 0x62cde8, 0x660d01)
/go/pkg/mod/github.com/progrium/go-basher@v0.0.0-20150902213704-ad5de635edd1/basher.go:58 +0x1ce
main.main()
github.com/dokku/plugn/plugn.go:102 +0x396
cat: /var/lib/dokku/plugins/available/clone/plugin.toml: Permission denied
panic: interface conversion: interface {} is nil, not map[string]interface {}
goroutine 1 [running]:
main.TomlGet(0xc000096030, 0x2, 0x2)
github.com/dokku/plugn/plugn.go:30 +0x2d1
github.com/progrium/go-basher.(*Context).HandleFuncs(0xc0000aa280, 0xc000096000, 0x5, 0x5, 0x0)
/go/pkg/mod/github.com/progrium/go-basher@v0.0.0-20150902213704-ad5de635edd1/basher.go:195 +0x26d
github.com/progrium/go-basher.ApplicationWithPath(0xc000073e48, 0xc000073e78, 0x4, 0x4, 0x62cde8, 0x1, 0xc0000ae180, 0x18)
/go/pkg/mod/github.com/progrium/go-basher@v0.0.0-20150902213704-ad5de635edd1/basher.go:77 +0x19c
github.com/progrium/go-basher.Application(0xc000073e48, 0xc000073e78, 0x4, 0x4, 0x62cde8, 0x660d01)
/go/pkg/mod/github.com/progrium/go-basher@v0.0.0-20150902213704-ad5de635edd1/basher.go:58 +0x1ce
main.main()
github.com/dokku/plugn/plugn.go:102 +0x396
clone                      enabled
common               0.19.11 enabled    dokku core common plugin
config               0.19.11 enabled    dokku core config plugin
docker-options       0.19.11 enabled    dokku core docker-options plugin
domains              0.19.11 enabled    dokku core domains plugin
enter                0.19.11 enabled    dokku core enter plugin
git                  0.19.11 enabled    dokku core git plugin
logs                 0.19.11 enabled    dokku core logs plugin
network              0.19.11 enabled    dokku core network plugin
nginx-vhosts         0.19.11 enabled    dokku core nginx-vhosts plugin
plugin               0.19.11 enabled    dokku core plugin plugin
proxy                0.19.11 enabled    dokku core proxy plugin
ps                   0.19.11 enabled    dokku core ps plugin
repo                 0.19.11 enabled    dokku core repo plugin
resource             0.19.11 enabled    dokku core resource plugin
scheduler-docker-local 0.19.11 enabled    dokku core scheduler-docker-local plugin
shell                0.19.11 enabled    dokku core shell plugin
ssh-keys             0.19.11 enabled    dokku core ssh-keys plugin
storage              0.19.11 enabled    dokku core storage plugin
tags                 0.19.11 enabled    dokku core tags plugin
tar                  0.19.11 enabled    dokku core tar plugin
trace                0.19.11 enabled    dokku core trace plugin

This is required! Issues missing this information may be closed.
For problems affecting all applications, the report output for a broken application is useful for our debugging.
In these cases, you may run dokku report without any arguments to display the top-level reporting information.

How (deb/make/rpm) and where (AWS, VirtualBox, physical, etc.) was Dokku installed?:
Installed using ansible-dokku

Did you install anything to harden permissions, such as pam_umask?

@josegonzalez yes, https://github.com/dev-sec/ansible-os-hardening, which sets a more conservative umask. Though the base plugins are owned by the dokku user and this is not a problem.

Did this ansible-os-hardening thing suddenly get posted somewhere fancy? Seems like it came up here as well...

I found it on ansible galaxy while searching for some other packages. I started using it a couple of months ago, and yes, the umask thing forces little changes on other procedures as well,

Do you know if there are any other issues with umask usage?

If you mean issues related to dokku, I just started using ansible-dokku to build a devel server, so first time in combination with os-hardening. I tried it because a co-worker is already using dokku, but he is using standalone installer and not in combination with os-hardening role.

Closing as this should be fixed via https://github.com/dokku/dokku/pull/4074 (and released in 0.21.3).


Fix NODE_PATH on windows

two of the mac tests have gone thru, I think it'll pass

released as 5.5.2


Porting to Python 3

Is there a timeline for implementing this?

Timeline for the final version is not yet defined.
You can check out the development branch for qpython 1.1 at: https://github.com/exxeleron/qPython/tree/qpython-1.1-dev.
Note that the documentation has not been updated yet, thus please refer to unit tests: serialization, deserialization, pandas for usage examples compatible with both Python 2.7 and 3.4.


Reward assignment during recording

What this does
Examples:

Title
Label

Item1 of Reward Classifier in issue #504
(Feature)

Those PR is meant to add the possibility for the teleoperator to add rewards when performing the tasks.
The current approach simply consists in having frames labeled 0 until the experimenter presses the space bar. Then the reward for each frame becomes 1. The experimenter can press the bar again (eg. in case of subsequent failure) and the frame labeling will return to 0.  Each time the space bar is pressed, the labeling switches
This is one way to go about it, but lmk if you have a better idea!
How it was tested
I made datasets with Moss with and without rewards. Checking that I got the expected behavior.
How to checkout & try? (for the reviewer)
python lerobot/scripts/control_robot.py record \
    --robot-path lerobot/configs/robot/moss.yaml \
    --fps 30 \
    --root data \
    --repo-id ${HF_USER}/moss_test \
    --tags moss tutorial \
    --warmup-time-s 5 \
    --episode-time-s 40 \
    --reset-time-s 10 \
    --num-episodes 2 \
    --push-to-hub 1 \
    --assign_rewards

Also style check failing was failing. Could you please run our pre-commit? :D
pre-commit install
pre-commit run --all-files

https://github.com/huggingface/lerobot/blob/main/CONTRIBUTING.md#submitting-a-pull-request-pr

closing as the changes have been brought through #528


How can i restrict landscape crop???

You should restrict device rotation by ViewController. See supportedinterfaceorientations property. https://developer.apple.com/documentation/uikit/uiviewcontroller/1621435-supportedinterfaceorientations

i want to set crop ratio potrait only.


Upgrade 5.6

General updates and placeholders for python3 migration documentation. Brief overview of the included suggestions:

Use new python3-migration.html pages under developers/ and sysadmins/ as the primary landing pages. These are based on the previous windows-migration.html page.
Each whatsnew.html page should clearly point to the python3-migration.html page (and start pointing to previous whatsnew pages)
sysadmins/python3-migration.html pages should make use of the installation and upgrade pages as necessary.

At the same time, some clean up is happening to simplify finding information:

server-overview.html has been inclined (but a redirect has been put in its place)
toctrees can now include explanations of what they are for.

Also some formatting/markup issues:

Reads good to me now.

Cheers. Merging. Happy to see bite-sized improvement PRs tomorrow and then more over the next few weeks!


BUG: wrongs filter method

Is there an existing issue raised for this?

[X] I have searched the existing issues

What happened?
The "Price range" and "Tailor rating" filter methods should be of radio buttons instead of multiselect
multiselect here doesnt makes that much sense
Ex: see in below SS price should be under 1000 & above 15000!!

Add ScreenShots

What browser are you seeing the problem on?
Chrome
Record

[X] I agree to follow this project's Code of Conduct
[ ] I'm a GSSOC'23 contributor
[X] I want to work on this issue

Hey @shobhitexe, it makes sense
make that filter in the radio, I am assigning this issue.

Just to Crosscheck, Are you contributing as GSSoC'23 Contributor?

@shobhitexe Just to Crosscheck, Are you contributing as GSSoC'23 Contributor?

Kindaa you can assign Gssoc tag but


$request->getQueryParams() should not contain question mark

I don't see any reason why getQueryParams method returns first parameter with question mark. Question mark is not part of query string, it just defines where it starts. I believe we should strip it.

It does not ...
Please see this unit test.
https://github.com/slimphp/Slim/blob/3.x/tests/Http/RequestTest.php#L537-L540

My bad, I had error in my NGINX config. I had /index.php**?**$is_args$args instead of /index.php$is_args$args.


Time out when adding whitelist

Tested on Linux with simulator.  The OpenThread Cert tests failed with timeout when nodes add WhiteList.   Python version 3.2.2.
====================================================
bash-4.2$ python Cert_5_1_02_ChildAddressTimeout.py
./ot-cli 1
1 : whitelist clear
1 : whitelist disable
1 : childtimeout 100
./ot-cli 2
2 : whitelist clear
2 : whitelist disable
2 : childtimeout 100
./ot-cli 3
3 : whitelist clear
3 : whitelist disable
3 : childtimeout 100
./ot-cli 4
4 : whitelist clear
4 : whitelist disable
4 : childtimeout 100
1 : panid 64206
1 : mode rsdn
2 : extaddr
1 : whitelist add b'e2b3540590b0fd87'
E
ERROR: test (main.Cert_5_1_02_ChildAddressTimeout)
Traceback (most recent call last):
File "/zigbee_lab/tools/python/lib/python3.3/site-packages/pexpect/init.py", line 1535, in expect_loop
c = self.read_nonblocking(self.maxread, timeout)
File "/zigbee_lab/tools/python/lib/python3.3/site-packages/pexpect/init.py", line 968, in read_nonblocking
raise TIMEOUT('Timeout exceeded.')
pexpect.TIMEOUT: Timeout exceeded.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "Cert_5_1_02_ChildAddressTimeout.py", line 49, in setUp
self.nodes[LEADER].add_whitelist(self.nodes[ROUTER].get_addr64())
File "/home/zjlu/work/openthread/tests/scripts/thread-cert/node.py", line 121, in add_whitelist
self.pexpect.expect('Done')
File "/zigbee_lab/tools/python/lib/python3.3/site-packages/pexpect/init.py", line 1451, in expect
timeout, searchwindowsize)
File "/zigbee_lab/tools/python/lib/python3.3/site-packages/pexpect/init.py", line 1466, in expect_list
timeout, searchwindowsize)
File "/zigbee_lab/tools/python/lib/python3.3/site-packages/pexpect/init.py", line 1568, in expect_loop
raise TIMEOUT(str(err) + '\n' + str(self))
pexpect.TIMEOUT: Timeout exceeded.
<pexpect.spawn object at 0x2b3ed099bd10>
version: 3.3
command: ./ot-cli
args: ['./ot-cli', '1']
searcher: <pexpect.searcher_re object at 0x2b3ed099be50>
buffer (last 100 chars): b"\r\n> whitelist add b'e2b3540590b0fd87'\r\nError 6\r\n> "
before (last 100 chars): b"\r\n> whitelist add b'e2b3540590b0fd87'\r\nError 6\r\n> "
after: <class 'pexpect.TIMEOUT'>

Turns out only minimal changes are needed to support both python2 and python3.  I just submitted #270.  Let me know if this fixes your issue.


Widgets Repo

The idea here is to create a separate repo / package(s) with more specialized widgets for Static CMS. Here people could suggest new widgets to be added that could optionally be installed without needing to be bundled with the core product. Some of the lesser used widgets in the core product will likely be moved over as well, like Map for example.
Suggested: https://github.com/StaticJsCMS/static-cms/discussions/4#discussioncomment-4871709
Core Widgets To Move (Targeted for v5)

[ ] Code
[ ] Color
[ ] Hidden
[ ] Key / Value
[ ] Map
[ ] UUID

Could at least the hidden widget remain in core? It's really useful for setting fixed parameters, for example in Hugo there's a type field you can use to specify which template should be used to render a page. I don't think it's that uncommon to do that...

Moving less used core widgets is a great idea IMHO but I wonder:  How is "less used" determined and what is the threshold? Maybe a little survey or might it be possible to search GitHub (or other public repos) to get a better idea on how often a widget is used?

Probably a better way to say it than less used is "more specialized".
Basically I want to leave in the core product only what most people will need out of the box to get started. Almost everyone will use the String widget, but the same cannot be said for Map.
Another criteria also will be bundle size. Since the additional widgets will be included one by one as needed, we can move large widgets (again like Map) to their own packages to reduce the core product's size.


Migrate to null safety

@rlazom Thank you very much for this PR, hope this will be merged soon!

Thanks for the PR!


ISV Studio closed, Updated process in Microsoft Docs, Partner Center lacks certification option as per 11/06/2024

This is now obsolete, and isv studio as domain are not accessible anymore as per
https://learn.microsoft.com/en-us/power-platform/important-changes-coming#isv-studio-removed

Once a pull request has been merged to the dev branch, the connector owner can submit the connector for certification through the Connector certification tab in ISV Studio. Once certified, the Microsoft Certification team will handle merging the updates from dev to master.

New process was published here
https://learn.microsoft.com/en-us/connectors/custom-connectors/submit-for-certification#submit-your-package-for-certification
Partner center is still not updated and the option described in the documentation is not available
New process:

Submit your package for certification
Sign in to Partner Center.
Under the Home heading, select Marketplace offers card.
On the Marketplace offers | Overview page, select Microsoft 365 and Copilot program.
On the Microsoft 365 and Copilot page, select New offer > Power Platform Connector.
In the Name field in the New Power Platform Connector screen, enter a unique name for your offer.

This name is used to help you identify your offer in Partner Center. We recommend that you include the name of your connector and associated plugin.
Next, you're taken to the Product setup page. You don't need to enter information here. The Status is marked as Complete to indicate there's nothing for you to do.

Any update on this? I cannot find my published connectors in Partner Center - I don't even see the option for Microsoft 365 and Copilot program.


Aws fopen

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

As a followup you'll need to find/replace ALL uses of fopen() in our codebase.
You can start here in aws-c-common though. There are several uses of fopen() in aws-c-common


Feature request, download missing module

I want to detect if a directive is missing, when it is, I'd like a callback to try and download it.  After looking at source, most of the functions are private and simply cannot, but I could be missing something.
I have searched for this, and as well asked in chat, I didn't get a response.

I don't think you can detect a missing directive and lazy load it. Have you looked into code splitting ?

I have.  I believe the functionality doesn't exist, but could easily be implemented as a setting perhaps.

Do you have a use case for this? When would this behaviour be useful?
It's possibly dangerous if somebody would place some malicious code into a directive called vue-laoder when you accidentally typed this instead of vue-loader.

But why? I think lazy-loading directives is too granular (introduces too much implementation/usage complexity for very little gain). I think we should keep async loading at component level.

Use case:  A crm with 100 directives, and only 2 or 3 are being used on
different pages.  Likely it would be more efficient to load only what is
needed, not the entire set of directives.
It would load just be an optional callback, so it can be handle wherever
vue is being used.
On Tue, Mar 22, 2016 at 11:52 AM, Nirazul<EMAIL_ADDRESS>wrote:

Do you have a use case for this? When would this behaviour be useful?
It's possibly dangerous if somebody would place some malicious code into a
directive called vue-laoder when you accidentally typed this instead of
vue-loader.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/vuejs/vue/issues/2533#issuecomment-199877256

--
Robert Plummer

@robertleeplummerjr you could have those directives each in a single module (file), then just import those are needed into a component where you need it to use. If you use any webpack based loading system your js-bundles will be filled only with those directives you've actually imported.

Thanks guys for your stellar feedback.  After careful consideration, I believe I'm going to have the process pull in the needed directives before vuejs processes the script here: https://github.com/Enpowi/Enpowi/blob/master/src/client/Enpowi/App.js#L321
.  I must say, vuejs is pretty fantastic, here is a blog post handler for Enpowi: https://github.com/Enpowi/Enpowi/blob/master/modules/blog/index.php#L32
For work I've had my head buried in React/Redux, and although it does a fine job, vuejs w/ Enpowi seems to do the same thing in hardly any lines:  29 lines of data setup, 47 line for user interface, 0 lines of sadness.
Thanks again guys!


Latest News Extension (API Integration)

Is your feature request related to a problem? Please describe.
I'm always frustrated when I have to visit multiple news websites to stay updated on the latest news. This process is time-consuming and inconvenient, especially when I am busy or need to quickly get a summary of current events. Additionally, the layout and advertisements on various news sites can be distracting and overwhelming.
Describe the solution you'd like
I would like a browser extension that provides a simple and streamlined way to read the latest news headlines directly from my browser toolbar. This extension should fetch news articles from a reliable API, such as the News API, and display them in a clean, easy-to-read format within the extension popup. The extension should update frequently to ensure that the latest news is always available.
What problem is this feature trying to solve?
The feature is designed to solve the problem of inefficient access to the latest news. It aims to provide users with a quick, convenient, and distraction-free way to stay updated on current events directly from their browser. This eliminates the need to visit multiple news websites or use separate news apps, saving time and enhancing productivity.

@Sulagna-Dutta-Roy please assign me this issue


Add selection display and visibility toggle logic

Closes #88

Codecov Report

Merging #89 (7dd07d1) into master (de67158) will decrease coverage by 0.21%.
The diff coverage is 16.66%.

@@             Coverage Diff              @@
##             master      #89      +/-   ##
============================================
- Coverage     70.47%   70.25%   -0.22%
- Complexity      461      462       +1
============================================
  Files            81       81
  Lines          1497     1503       +6
  Branches        151      151
============================================
+ Hits           1055     1056       +1
- Misses          399      404       +5
  Partials         43       43

Impacted Files
Coverage Δ

...rc/main/java/seedu/address/logic/LogicManager.java
71.42% <0.00%> (-3.58%)
:arrow_down:

src/main/java/seedu/address/ui/MainWindow.java
0.00% <0.00%> (ø)

...rc/main/java/seedu/address/model/ModelManager.java
94.23% <100.00%> (+0.11%)
:arrow_up:

Continue to review full report at Codecov.

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


feat: Add Arabic, Japanese, Polski, Svenska, and Kiswahili translations for Excluding

Description
Add Arabic, Japanese, Polski, Svenska, and Kiswahili translations for Excluding
Type of change

[ ] Bug fix (added a non-breaking change which fixes an issue)
[x] New feature (added a non-breaking change which adds functionality)
[ ] Updated documentation (updated the readme, templates, or other repo files)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

[x] Tested locally with a valid username
[x] Tested locally with an invalid username
[x] Ran tests with composer test
[x] Added or updated test cases to test new features

Checklist:

[x] I have checked to make sure no other pull requests are open for this issue
[x] The code is properly formatted and is consistent with the existing code style
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

Looks good to me. Do you speak all of these languages?

Looks good to me. Do you speak all of these languages?

Hmmm... I understand a little Arabic

Maybe you can just add Arabic

Thanks, while chatgpt seems to say these are all fine, I think it's better if we leave it up to native speakers to decide on how things should be translated.
I'll merge Arabic, but leave the others open to other contributors if that's fine with you.

Thanks, while chatgpt seems to say these are all fine, I think it's better if we leave it up to native speakers to decide on how things should be translated.
I'll merge Arabic, but leave the others open to other contributors if that's fine with you.

Yes, of course. I don't mind


Paning the editor panel with Ctrl +arrows does not work when several work tabs are open

How to reproduce:
Create two models so there are two tabs for the corresponding works. Press Ctrl+Up once. Try pressing any Ctrl+arrow key combinations.
Observed behaviour:
The focus gets shifted to the tabs and the editor window does not pan when Ctrl+arrow is pressed.
Expected behaviour:
A viewport of the editor window needs to be movable.

danilovesky at 2014-06-24T16:41:51Z:
It looks like the Ctrl+Up (and Ctrl+Down) are used for moving focus in standard look and feel implementation (https://www.jidesoft.com/forum/viewtopic.php?f=18&t=10023)
Either redefine the key mapping or choose a different key combination for panning.

danilovesky at 2014-07-11T17:04:34Z:
This can be fixed by redefining input map of GraphEditorPanel.
Add this code to the constructor of GraphEditorPanel:
	this.getInputMap().put(KeyStroke.getKeyStroke(KeyEvent.VK_UP, Event.CTRL_MASK), "doNothing");
	this.getActionMap().put("doNothing", new AbstractAction() {
		public void actionPerformed(ActionEvent e) {
			//do nothing
		}
	});


Create own GitHub account

[x] Read Creating an own GitHub account
[x] Create a GitHub account
[x] Send user name to<EMAIL_ADDRESS>by email
[x] Close this issue

Resolves: #2


Slack Login Link

Issue #128

Looks good. I think "Log In" is the action and "Login" is a noun, so "Log In to Slack" is probably more gramatically correct.  Sorry that I confused things with the word login in the issue title.


CAVE stops working after a few seconds

We attached the logs of the master and slaves
OutputLogs.txt

Solved with newest Version.


use key to pull plugins for ansible use

Our ansible configs are contained in one big yaml file, unlike the plugins.yml file. This just adds a key so that we can easily diff plugin changes in our ansible configs

@pwnage101

@estute I stumbled across this while looking at outstanding review requests; do you still want to merge this?


Adds fips documentation

Adds documentation in regards to the use_fips_endpoint variable..

Seems there is. bug open for checkov

Looks like we just need to get the tests passing, but looks good.


Refactor ownership and object copy semantics

Currently copying of object is disabled to prevent sharing same JNI pointer between multiple JObjects that migh release it.
We need to implement copy logic that creates new local/global/weak references when objects are copied in C++. And probably do nothing when wrapping existing jobjects. That means that JGlobalRef should probably go and instead JObject could just have getGlobalRef or getWeakRef methods that create a JObject copy with the correct reference inside of it.
Additionally maybe we need to make JString and JArray subclasses of JObject to get all the invoke and field access methods, but maybe to reduce the code duplication that will happen for the copy logic we can access underlying jobject via some method in JString and JArray. Something to brainstorm about.

Implemented in #6


Update README.md

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This PR is stale because it has been 15 days with no activity. Remove stale label or comment or this will be closed in 5 days.

Here's a response

Hey, I responded!

This PR is stale because it has been 15 days with no activity. Remove stale label or comment or this will be closed in 5 days.

another response

This PR is stale because it has been 0 days with no activity. Remove stale label or comment or this will be closed in 1 days.

This PR is stale because it has been 0 days with no activity. Remove stale label or comment or this will be closed in 1 days.

test

test this one, should remove response requested only


fix: broken group ping when used immediately after a linebreak

Because messages were only split on spaces, using a group ping immediately after a linebreak would leave the entry in the words array as something\n@group.
This PR changes splitting to whitespace in general.

Great catch on this bug, I would never have suspected this.


Be able to ponder items with an NBT

Describe the feature/addition!
Would love to be able to ponder items/blocks that have an nbt value. Like press w on an item with nbt
Why would like to see this feature/addition?
It would be really helpful.

Will be added in the future. But rn I don't know when exactly.


Consider dropping support for mutable modules

Namely:

Array
Map
NonEmptyArray
Record
Set
Tuple

As a functional library it's OK to enforce immutability.
I would get rid of all Readonly* modules and make the rest immutable.

Would love to see that readonly is the default in the whole fp-ts ecosystem but I already had my struggle to switch to the readonly instances with fp-ts@2 because fp-ts-contrib, io-ts-types and monocle-ts has not full readonly support. If we could add the readonly instances e. g. ReadonlyZipper for fp-ts-contrib, readonlyNonEmptyArray for io-ts-types and indexReadonlyNonEmptyArray for monocle-ts I would already give it a try.

and indexReadonlyNonEmptyArray for monocle-ts

@mlegenhausen https://github.com/gcanti/monocle-ts/pull/124

I would get rid of all Readonly* modules and make the rest immutable

There are two options I guess:
Option 1
Keep the Readonly* modules and simply remove the mutable counterparts (:+1: if you prefer this option)
Option 2
Remove all the mutable modules and rename Readonly<X> module to <X> (:-1: if you prefer this option)

@gcanti based on a similar conversation...
this explains my vote :)

We can see this issue in two lights:

We're dealing with a strongly-typed pure functional library. We're expecting only readonly data-structures and we're promising to give back only readonly data structures. In this case, the immutability is an axiom, and we don't need to explicitly prefix all our data-structures with a Readonly prefix. We'll have one Array module which is readonly.

...or:

We're a TypeScript library, in which the default is mutable structures. There is already a convention of prefixing with Readonly all immutable data-structures. This is aligned with the current situation, in which we have both mutable Array and immutable ReadonlyArray.

I tend to like the first philosophy.

Readonly arrays/records (using ts readonly keyword) have low adoption in general even in immutable code bases. If Array is replaced with the readonly variants, our codebase at Userlike would break because we cannot realistically make all our arrays Readonly even though all of them are immutable.

Readonly arrays/records (using ts readonly keyword) have low adoption in general even in immutable code bases. If Array is replaced with the readonly variants, our codebase at Userlike would break because we cannot realistically make all our arrays Readonly even though all of them are immutable.

Since this may hinder adoption by less pure codebases, throwing another option out there: switch the defaults, so the module Array supports only readonly Arrays but also provide e.g. MutableArray

Since this may hinder adoption by less pure codebases, throwing another option out there: switch the defaults, so the module Array supports only readonly Arrays but also provide e.g. MutableArray

I'm currently in a world of hurt working heavily with fp-ts trees and otherwise readonly data, having to constantly be converting between readonly and mutable arrays. Additionally, monocle-ts's index function only supports readonly, so I have lots of nasty casts when working with trees.
This could be solved by moving to all mutable data-structures, or all immutable.
Personally I like immutable everywhere. If my codebase is anything to go by, nearly all of my data processing is written in fp-ts. No conversion is required to pass data in (mutable is a superset of immutable), and it's trivial in most cases to perform a call such as toMutableArray and the end of processing when it's required. In most cases where it's "required" by Typescript, it isn't even necessary, it's just the developer of a library didn't add readonly to their input types. I use the following Typescript trick in those cases:
export type DeepWritable<T> = { -readonly [P in keyof T]: DeepWritable<T[P]> };

export function castWritable<T>(x: T): DeepWritable<T> {
  return x as DeepWritable<T>;
}

I have been stumbling over traverseArray: (f: (a: A) => F<B>) => (as: readonly Array<A>) => F<READONLY Array<B>> so many times. In my opinion, it's perfectly fine and admirable to type your library functions so their parameters are readonly - in essence you are making a promise to whomever uses your library, that this function won't alter its arguments.
However, if you type your functions so their return values are readonly you are in essence saying: YOU may not alter this array, and there is a good reason for it. Which in the case of traverseArray just plainly isn't true. It's just an array, it has passed over into my hands and my responsibility, why do I need to recast before I may .push()?


Natalieparry/fixdllbuild

Restoring the .lib build for the win32 dll. This is different from the static version of the entire lib and serves as an import library for the dll that is important for c++ projects trying to link the lib. See issue #979
Validation: Built the samplecpp project against the new import lib/dll. The project ran without reporting any linking failures.

Please include validation steps in the PR description. Ideally, confirm that the following sample works for the DLL case: https://github.com/microsoft/cpp_client_telemetry/tree/main/examples/cpp/SampleCpp

tagging @mkoscumb for review as this reverts #852


src/MachineLearning/Regression.hs: Ambiguous occurrence ‘<>’

From the Stackage Nightly build:
src/MachineLearning/Regression.hs:38:19: error:
    Ambiguous occurrence ‘<>’
    It could refer to either ‘Prelude.<>’,
                             imported from ‘Prelude’ at src/MachineLearning/Regression.hs:10:8-33
                             (and originally defined in ‘GHC.Base’)
                          or ‘Numeric.LinearAlgebra.<>’,
                             imported from ‘Numeric.LinearAlgebra’ at src/MachineLearning/Regression.hs:30:31-34
   |
38 |   in (LA.inv (trX <> x) <> trX) #> y
   |                   ^^

src/MachineLearning/Regression.hs:38:25: error:
    Ambiguous occurrence ‘<>’
    It could refer to either ‘Prelude.<>’,
                             imported from ‘Prelude’ at src/MachineLearning/Regression.hs:10:8-33
                             (and originally defined in ‘GHC.Base’)
                          or ‘Numeric.LinearAlgebra.<>’,
                             imported from ‘Numeric.LinearAlgebra’ at src/MachineLearning/Regression.hs:30:31-34
   |
38 |   in (LA.inv (trX <> x) <> trX) #> y
   |                         ^^

src/MachineLearning/Regression.hs:46:20: error:
    Ambiguous occurrence ‘<>’
    It could refer to either ‘Prelude.<>’,
                             imported from ‘Prelude’ at src/MachineLearning/Regression.hs:10:8-33
                             (and originally defined in ‘GHC.Base’)
                          or ‘Numeric.LinearAlgebra.<>’,
                             imported from ‘Numeric.LinearAlgebra’ at src/MachineLearning/Regression.hs:30:31-34
   |
46 |   in (LA.pinv (trX <> x) <> trX) #> y
   |                    ^^

src/MachineLearning/Regression.hs:46:26: error:
    Ambiguous occurrence ‘<>’
    It could refer to either ‘Prelude.<>’,
                             imported from ‘Prelude’ at src/MachineLearning/Regression.hs:10:8-33
                             (and originally defined in ‘GHC.Base’)
                          or ‘Numeric.LinearAlgebra.<>’,
                             imported from ‘Numeric.LinearAlgebra’ at src/MachineLearning/Regression.hs:30:31-34
   |
46 |   in (LA.pinv (trX <> x) <> trX) #> y
   |                          ^^

Okay I see you already got it re-enabled (fpco/stackage#3484)


close *Cursor on defer

otherwise, if multiple and frequent calls RunWrite causing the error ErrNoConnections

Thanks for spotting this issue, I think it actually could be causing the issue @bryfry had in #180. Ill merge this right away.
(in future please ensure code is gofmt'ed before creating a PR)


explicitly register helper, fixes #147

I haven't found official documentation on how to include helper to all controllers from Rails engine - this is analogous to what I found in some other github projects...

/cc @rwz


[move-prover] Disable two-state invariants temporarily

Motivation
This PR temporarily disables two-state invariants in the test cases to make it easier to land
the new memory model. Specifically:

Two-state invariants in invariants.move and nested-invariants.move have been commented out. invariants.exp is updated and the old file checked in as invariants.exp.old.  nested-invariants.exp did not change because the two-state invariants inside it did not result in errors.
In all other files, the use of two-state invariants was redundant since it was already covered by invariant pack/unpack.  Deletion resulted in shifted line numbers and .exp files were updated.
Disabled VarUpdate and InvariantUpdate in annotations in spec-lang/src/ast.rs. Consequently, commented out "invariant update" in the unit tests there.  Two .exp files changed.  I checked in their old version: invariants_err.exp.old, variables_err.exp.old.

After landing the new memory model, we will revisit two-state invariants.
Have you read the Contributing Guidelines on pull requests?
Yes.
Test Plan
Existing tests.
Related PRs

This looks great, but can you also please deactivate those in the type checker? This will also give you confidence that you do not missed something.
It's easy. Go to spec-lang/src/ast.rs'. Search for mentioning of VarUpdate and InvariantUpdate Remove it from all functions allowed_XXX. The context checker will then produce errors when two-state invariants are used.

Done.

@bors-libra r=wrwg

:pushpin: Commit 184b887 has been approved by wrwg

:hourglass: Testing commit 184b8874098ed471d7001b7c4d6eaa7b08ce9f7f with merge bab8ca710686b5e6062b2bb58bae38f0e22576a4...

@bors-libra retry

@bors-libra retry

@bors-libra retry

@bors-libra r=wrwg

:pushpin: Commit d8a090b has been approved by wrwg

:hourglass: Testing commit d8a090b92c360f4b468a8e4d5a428dc42d82b1ac with merge 95e9a8b452919fd69d54fb5694a44bb903488696...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: wrwg
Pushing 95e9a8b452919fd69d54fb5694a44bb903488696 to master...


Django1.7 error on DatabaseWrapper ( no attribute "data_types" )

This is my stack trace,
>>> TXCache.objects.using('redshift').count()
Traceback (most recent call last):
  File "<console>", line 1, in <module>
  File "/Users/ignaciodelamadrid/Development/venturefund.io/lib/python2.7/site-packages/django/db/models/query.py", line 338, in count
    return self.query.get_count(using=self.db)
  File "/Users/ignaciodelamadrid/Development/venturefund.io/lib/python2.7/site-packages/django/db/models/sql/query.py", line 436, in get_count
    number = obj.get_aggregation(using=using)[None]
  File "/Users/ignaciodelamadrid/Development/venturefund.io/lib/python2.7/site-packages/django/db/models/sql/query.py", line 402, in get_aggregation
    result = query.get_compiler(using).execute_sql(SINGLE)
  File "/Users/ignaciodelamadrid/Development/venturefund.io/lib/python2.7/site-packages/django/db/models/sql/query.py", line 224, in get_compiler
    connection = connections[using]
  File "/Users/ignaciodelamadrid/Development/venturefund.io/lib/python2.7/site-packages/django/db/utils.py", line 242, in __getitem__
    backend = load_backend(db['ENGINE'])
  File "/Users/ignaciodelamadrid/Development/venturefund.io/lib/python2.7/site-packages/django/db/utils.py", line 108, in load_backend
    return import_module('%s.base' % backend_name)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/Users/ignaciodelamadrid/Development/venturefund.io/venturefund/db/backends/django-redshift/base.py", line 402, in <module>
    class DatabaseWrapper(BasePGDatabaseWrapper):
  File "/Users/ignaciodelamadrid/Development/venturefund.io/venturefund/db/backends/django-redshift/base.py", line 406, in DatabaseWrapper
    data_types = deepcopy(BasePGDatabaseWrapper.data_types)
AttributeError: type object 'DatabaseWrapper' has no attribute 'data_types'

I saw Django's repo and it seems that the 1.7 version doesn't declare the data_types dictionary in the DatabaseWrapper class in the django.db.backends.postgresql_psycopg2 module. Any hint on this? Are you guys going to support 1.7? upgrading is kind of difficult for me.

Thanks for your reporting. I'll take a look.

Fixed.


chore: preparing EasyCLA

Co-authored-by: Lee Eggebroteni<EMAIL_ADDRESS>Co-authored-by: Dave Lucia<EMAIL_ADDRESS>Co-authored-by: Santiago Cabrera<EMAIL_ADDRESS>

@yordis the co-authored bit will go into the PR to otel-contrib when you have that ready. So it's create the PR to add the lib to contrib, add the co-authors in the commit itself.
https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors


Update aliasing in tf.linalg.band_part docs

URL(s) with the issue:
https://www.tensorflow.org/api_docs/python/tf/linalg/band_part
Description of issue (what needs changing):
Clear description
https://github.com/tensorflow/tensorflow/blob/56903ed0419882e004d4467dec452684b106e46f/tensorflow/core/api_def/base_api/api_def_MatrixBandPart.pbtxt#L50-L66
tf.matrix_band_part in above lines should be tf.linalg.band_part. (tf.matrix_band_part is moved to tf.compat.v1.matrix_band_part)
The below links should also be fixed

https://github.com/tensorflow/tensorflow/blob/011228639301a8ed60d39c94ab096b074091bb4a/tensorflow/go/op/wrappers.go
https://github.com/tensorflow/tensorflow/blob/0748d9a3ab284f7c9461985db478d09e2873cf1a/tensorflow/compiler/mlir/tensorflow/ir/tf_generated_ops.td

Submit a pull request?
Are you planning to also submit a pull request to fix the issue? : Yes

@jeongukjae Are you still interested to raise a PR for this?
Note that wrappers.go and tf_generated_ops.td are machine generated files therefore we should not edit manually.

@ymodak I tried to fix this issue, but I don't use Golang, so I don't know how exactly auto-generate that files. I think it would be better that other people fix this.

This is fixed with tf-nightly docs. Thanks!
https://www.tensorflow.org/api_docs/python/tf/linalg/band_part?version=nightly


Bump AWS account limit

This PR bumps the AWS account limit to unlock the account controller. It wont create more accounts it will being creating accounts from the reused failed accounts that have been reset.

/lgtm


Incorrect generated DDL for trigger (schema appears twice)

Description
Right clicking trigger > Generate SQL > DDL, or checking the Declaration section in Properties results in a code where the schema name may appear twice:

The cause seems to be that the DESCRIPTION column in USER_TRIGGERS already starts with the schema name, and I assume DBeaver automatically appends the schema name too without checking this.

DBeaver Version
Community Edition 23.0.2
Operating System
Windows 11
Database and driver
Oracle Database 12c Enterprise Edition Release <IP_ADDRESS>.0 - 64bit Production
Steps to reproduce

Create a trigger where you specify the schema name:

create or replace trigger myschema.mytrigger...

Open it from the Database Navigator

Additional context
No response

Hello @AronHK,
Thanks for the bug report.
Can you please provide the full DDL of the trigger?

I'd rather not show the full trigger from that project.
Here is an example code for a new trigger I just created:
create trigger checkout.newtrigger after insert or update on checkout_session
begin
	null;
end;

and this is what DBeaver gives me back in the trigger Properties > Declaration:
CREATE OR REPLACE trigger CHECKOUT.checkout.newtrigger after insert or update on checkout_session
begin
	null;
end;

Thank you. I was able to reproduce your issue.


Support for running arbitrary main classes

This is a proposal outlined in a feature request by @ittaiz: https://github.com/bazelbuild/intellij/issues/247
We want to support running arbitrary main methods (useful for testing/otherwise running arbitrary code that's not supposed to run outside the IDE). For this, we want to create an implicit output binary target for every scala_library, and call it explicitly, passing additional context from the IDE (specifically, the main_class value).
Perhaps this could be a joint effort to support @johnynek's idea for the repl?
WDYT?

Shouldn’t be too hard once we solve the runfiles issue I had with the repl.
So, in this case we have a wrapper script that expects a classname as a first argument and the rest are passed into main?
It would be interesting to ask the bazel people why they didn’t do this with java_library, or if they did how to copy it so it works exactly the same way.

From this comment it sounds this doesn't exist in java:

...Bazel doesn't build a runnable binary for java_library targets.

@hmemcpy can you please update here about the difficulties and what we decided to do?

@hmemcpy
Can you update about resolution and optionally close this

Oops, sorry, must have missed this!
We decided to implement this entirely in the plugin, without any additional changes in rules_scala, by creating a deployable.jar out of the module where the arbitrary main was added, and then running it with the -cp argument, passing it the fully qualified name of the main object. This supports both run and debug scenarios, allowing to quickly run any scala_library without any changes to BUILD files or other local changes!
I'm closing this issue, as well as the issue in the plugin repo!


Error im log: Unhandled promise rejection

Im log kommt Error. Instanz bleibt rot.
V.0.1.7
flow
`

host.iobroker | 2024-12-21 09:59:25.788 | info | Restart adapter system.adapter.bosch-ebike.0 because enabled
-- | -- | -- | --
host.iobroker | 2024-12-21 09:59:25.788 | error | instance system.adapter.bosch-ebike.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.iobroker | 2024-12-21 09:59:25.788 | error | Caught by controller[1]: at BoschEbike.onReady (/opt/iobroker/node_modules/iobroker.bosch-ebike/main.js:79:7)
host.iobroker | 2024-12-21 09:59:25.788 | error | Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
host.iobroker | 2024-12-21 09:59:25.788 | error | Caught by controller[1]: at BoschEbike.loginFlow (/opt/iobroker/node_modules/iobroker.bosch-ebike/main.js:198:65)
host.iobroker | 2024-12-21 09:59:25.788 | error | Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'split')
host.iobroker | 2024-12-21 09:59:25.788 | error | Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
bosch-ebike.0 | 2024-12-21 09:59:25.208 | warn | Terminated (UNCAUGHT_EXCEPTION): Without reason
bosch-ebike.0 | 2024-12-21 09:59:25.208 | info | terminating
bosch-ebike.0 | 2024-12-21 09:59:25.198 | error | Cannot read properties of undefined (reading 'split')
bosch-ebike.0 | 2024-12-21 09:59:25.198 | error | TypeError: Cannot read properties of undefined (reading 'split') at BoschEbike.loginFlow (/opt/iobroker/node_modules/iobroker.bosch-ebike/main.js:198:65) at processTicksAndRejections (node:internal/process/task_queues:95:5) at BoschEbike.onReady (/opt/iobroker/node_modules/iobroker.bosch-ebike/main.js:79:7)
bosch-ebike.0 | 2024-12-21 09:59:25.196 | error | unhandled promise rejection: Cannot read properties of undefined (reading 'split')
bosch-ebike.0 | 2024-12-21 09:59:25.196 | error | Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
bosch-ebike.0 | 2024-12-21 09:59:24.175 | info | Login to eBike flow

`

hier sieht man das log besser:
https://forum.iobroker.net/topic/55902/test-adapter-bosch-ebik-connect-flow/95?_=1734778368475

looks for me, that Bosch altered the requirments (again) - the post of the login/email now also make use of an additional form field h-captcha-response (but I could be totally wrong here)

mit der 0.1.9 besteht der error noch:
`

host.iobroker | 2024-12-30 10:22:28.476 | error | instance system.adapter.bosch-ebike.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
-- | -- | -- | --
host.iobroker | 2024-12-30 10:22:28.476 | error | Caught by controller[1]: at BoschEbike.onReady (/opt/iobroker/node_modules/iobroker.bosch-ebike/main.js:79:7)
host.iobroker | 2024-12-30 10:22:28.476 | error | Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
host.iobroker | 2024-12-30 10:22:28.476 | error | Caught by controller[1]: at BoschEbike.loginFlow (/opt/iobroker/node_modules/iobroker.bosch-ebike/main.js:204:65)
host.iobroker | 2024-12-30 10:22:28.476 | error | Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'split')
host.iobroker | 2024-12-30 10:22:28.475 | error | Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
bosch-ebike.0 | 2024-12-30 10:22:27.893 | warn | Terminated (UNCAUGHT_EXCEPTION): Without reason
bosch-ebike.0 | 2024-12-30 10:22:27.892 | info | terminating
bosch-ebike.0 | 2024-12-30 10:22:27.883 | error | Cannot read properties of undefined (reading 'split')
bosch-ebike.0 | 2024-12-30 10:22:27.883 | error | TypeError: Cannot read properties of undefined (reading 'split') at BoschEbike.loginFlow (/opt/iobroker/node_modules/iobroker.bosch-ebike/main.js:204:65) at processTicksAndRejections (node:internal/process/task_queues:95:5) at BoschEbike.onReady (/opt/iobroker/node_modules/iobroker.bosch-ebike/main.js:79:7)
bosch-ebike.0 | 2024-12-30 10:22:27.881 | error | unhandled promise rejection: Cannot read properties of undefined (reading 'split')
bosch-ebike.0 | 2024-12-30 10:22:27.880 | error | Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
bosch-ebike.0 | 2024-12-30 10:22:27.150 | info | Login to eBike flow

`


[DOOR-11] Handle returned results from DOS scanner

DOS scanner should return the scan results from DOS scanner and convert them to suitable data structures, to be used by ORT.
From SyncLinear.com | DOOR-11

Now tested with real DOS API response.


Why is stylecop.json at the project, not solution, level?

I know how to create a single stylecop.json file and link it from the root level of my solutions.  The question is: why should I have to?  The majority of stuff in there doesn't apply at a project level, you likely want it to apply to your whole solution.  Either allowing the file to be at the .sln level, or moving its config into .editorconfig would seem to make sense.
Is it only at the project level for historical reasons or is there any other justification?

Why is stylecop.json at the project, not solution, level

This project is not opinionated on whether the file exists at the project or solution level. It can be in either location equally well.

I thought it had to be at the root of the project?

No, it can be anywhere on disk. The <AdditionalFiles> line that includes it in the project specifies the path.
https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/84e2324d71f1ee692784410efad56f96df371669/StyleCop.Analyzers/Directory.Build.props#L76-L80

@sharwell I just did a test.  If I put a stylecop.json at my .sln file level with the following contents:
{ // see https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/Configuration.md
    "$schema": "https://raw.githubusercontent.com/DotNetAnalyzers/StyleCopAnalyzers/master/StyleCop.Analyzers/StyleCop.Analyzers/Settings/stylecop.schema.json",
    "settings": {
        "indentation": {
            "indentationSize": 4,
            "tabSize": 4,
            "useTabs": true
        },
        "layoutRules": {
            "newlineAtEndOfFile": "require"
        }
    }
}

I don't get a StyleCop analyzer warning if there's no newline at the end of Program.cs.  If I then add a Directory.Build.props with:
<Project>
	<!-- Import stylecop.json into every project -->
	<ItemGroup>
		<AdditionalFiles Include="$([MSBuild]::GetPathOfFileAbove('stylecop.json', '$(MSBuildThisFileDirectory)'))" Link="stylecop.json" />
	</ItemGroup>
</Project>

It starts giving the warning.  But this means that the stylecop.json file must be at the project level to work.  Is this a limitation of analyzers in general, or is there a way StyleCop can just read the solution-level file without needing the additional Directory.Build.props?

But this means that the stylecop.json file must be at the project level to work.

Your example shows a file which works and is located at the solution level.

is there a way StyleCop can just read the solution-level file without needing the additional Directory.Build.props

The file must be added to the build in some manner. Some projects have NuGet packages that inject build logic directly into the project, but the only true difference in this case is the location of the .props file.


feat: provide SwaggerUI middleware to serve spec file

Problem statement
I wasn't able to find a middleware to serve the generated spec file via SwaggerUI.
Swaggo looks similiar and provides an additional package for this https://github.com/swaggo/http-swagger
It would be nice to have this too.
Environment
swagger version: latest
go version: latest
OS: all

We have 3 of them:

https://github.com/go-openapi/runtime/blob/master/middleware/swaggerui.go
https://github.com/go-openapi/runtime/blob/master/middleware/redoc.go
https://github.com/go-openapi/runtime/blob/master/middleware/rapidoc.go


chore: use a more reliable solution to get changes

Using Git database API does not work for merged PR as the reference of
the deleted branch vanish faster.
This leverages the search API instead.
Depends-On: #511

This pull request is part of a stack:

chore: move more things in Changes/LocalChange object (#507)
chore: move retrieval of change IDs and pull inside get_remote_changes() (#508)
fix: all short sha are wrong (#509)
refactor: pre compute the action to do for each change of the stack (#510)
refactor: check API response globally (#511)
chore: use a more reliable solution to get changes (#512) 👈
fix: logging in debug mode (#513)
chore: add timing to HTTP request logs (#514)


Full version is not working?

I spent money to unlock the full version but it still says it's a trial version, and now it says server error.

I also have an error

I'm the same way, how do I solve it?

I'm the same way, how do I solve it?

Idk, maybe wait until rikka fixes the server

There is a ssl problem in the server
it should be fixed in 2 days or less

Now it's fixed


Missing text "Signature" in image output after entire page OCR refactor

After entire page OCR refactor PR, text Signature was removed from ingest output in file change as "Signature Individieale"
The text was coming from image IRS-form-1987.png:

While for the PDF IRS-form-1987.pdf we still have the text Signature
Expected behavior
Ingest output for IRS-form-1987.png should have text Signature even the quality is not good

looks like the scaling from table OCR refactor PR is bring it back:


fix ToC listing

Hello!
I presume that it's OK in the future for such small, non-content changes to be "Commit[ed] directly to the master branch." Just being careful at the first PR ;-)
Cheers!

I actually prefer a PR—even if you then merge it yourself, because then everyone who is following the repo sees what is happening on it.
Thanks for the fix 🌷

Will do! 🌻  Didn't realise that was possible until after submitting the PR & comment.


Recaptcha Verification

As mentioned the recaptcha site key is required and it seems that the key is wrong .I went through the contact site and I can improve the frontend slightly.

https://hackathon-starter.walcony.com/contact is working fine when I navigate to it.
Regarding the potential improvements, please detail them here and get sign-off before sending a PR.  Because of Haktoberfest I have had to mark some incoming PRs as spam, unnecessary, and invalid, and I rather not have your time wasted.  The current focus is the issues marked with "Hacktoberfest" at https://github.com/sahat/hackathon-starter/issues .  If there is a different kind of task that you are looking for (i.e. frontend only), I can potentially come up with something, let me know what you are looking for.  Thanks!


Installing VMAgent

Page needs a complete make over but the must important change is to update the AllowExtensionOperations option after manually installing the VMAgent on a VM that was deployed from image without ProvisionVMAgent enable.
$vm.OSProfile.AllowExtensionOperations = $true
$vm | Update-AzureRmVM

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

ID: ab75f449-661d-bd1e-3ebd-61e2384a911a
Version Independent ID: e7c93a31-6076-26b8-a53d-d36df01ec6bc
Content: Azure Virtual Machine Agent Overview
Content Source: articles/virtual-machines/extensions/agent-windows.md
Service: virtual-machines-windows
GitHub Login: @roiyz-msft
Microsoft Alias: roiyz

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

#reassign: @MicahMcKittrick-MSFT

I added a note about that. I am working on a re-write of this doc as well.


Measurement points smaller since v7.0.0

Hi Team,
I've noticed that since upgrading to the latest major version of the charting component the measurement points now appear smaller.  I can see there have been a good few other styling changes also, but the measurement points in particular seem rather small, which we think might impact readability.
Would it be possible to increase the default size of these measurement points or otherwise make it customisable in MeasurementStyle?
Ideally would like to do this while still being able to use the predefined themes.
Any advice you have would be much appreciated!
Current instance is using v7.0.4
Chart rendered in v6.1.15:

Chart rendered in v7.0.4:

Very possibly the default may have changed. The points dynamically size when bunched together, but there is a default setting in the styles.
If you are interested in submitting a PR we would be glad to look at it. Or if not I can apply a patch next week?
Thank you again @dmc-cambric - loving all the observations and suggestions you make.

Thanks man, its a great piece of kit!

Thanks again for the reports @dmc-cambric, keep them coming! Can I just check the names and NHS numbers in your screenshots are for test data not real people?

Yeah, this is all test data @mbarton
Just an FYI @eatyourpeas I won't be able to investigate so appreciate anything you find out!

Hi Team,
We had a Scottish Morse User Group demonstrating the introduction of the mid-parental + bone age features to our software and the existing users weren't keen on the smaller dots, likely to affect usability.
With the latest fix the measurement points still seem really small, even when spaced out. I think both the minimum size and maximum size might need to be increased for this to be readable, ideally so the points are the same size as in v6.1.15.
The only change in the codebase I could see from the v7 release was to isCrowded.ts - Line 23-25, could be the cause?
Some additional examples:
v7.0.7:

v6.1.4

Sorry about that @dmc-cambric - there was a definite change in size in storybook when i tried it, but i did not test in the client before releasing.
The isCrowded function determines if the points are close together and makes them smaller if so. The reason for this is, particularly in the neonatal period, babies are sometimes weighed every day and if the points are too big it looks quite ugly. The function sets a default size, which it then reduces if the neighbour is too close.
I am not sure if the bone age 'x's are covered by this function though. I think I left bone ages out of this because you only ever do a bone age once a year, so there should be no really danger of crowding. If it is just the bone age plots that users are unhappy with I can increase the size of those and release a further patch?

The bone age measurements seem fine size-wise, the main concern is the size of the measurement points themselves which still seem smaller than v6. Good to know about the neonatal reasoning btw, makes sense! Although I still think they're very hard to read when they're this small.
We've gathered some feedback regarding this directly from a health board that has clinicians testing the tool, will send you their insights via. email.
I think there might be an additional problem with the scaling, (see above screenshot for v7.0.7 in my last comment), It seems that if any two measurement points are close together it shrinks them and every other measurement point on the chart, even the ones that are very spaced out. (see the leftmost section of the chart for the close-together points).


fix(json): not escape forward slash when stringify

Fix #893

Pull Request Test Coverage Report for Build 2890
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.02%) to 83.846%

Files with Coverage Reduction
New Missed Lines
%

json/lex_string.mbt
1
73.68%

Totals

Change from base Build 2883:
-0.02%

Covered Lines:
3841

Relevant Lines:
4581

💛  - Coveralls


Add ability to set custom registry for verlero-plugin-for-csi

Currently I am attempting to do a non-olm deployment in a disconnected environment, and so far I have been able to edit the operator.yaml to include the internal registry we use to sync external image registries for the operator image and the registry var seems to work for the rustic images but not for the csi plugin.

The above works for everything except the csi plugin.
Whenever the operator creates the velero deployment it is using docker.io/velero/velero-plugin-for-csi:main to try to pull the csi plugin. I assume I need it since I am deploying oadp/velero in openshift.
The operatory.yml only gives the following to modify for this plugin.

perhaps it could also include a registry var so I can give it the internal registry where we pull docker.io images through.
I hope this makes sense.
Below is what I find in the velero deployment, and if I edit the deployment the operator overwrites it.

Ok my apologies, I review the documentation more closely and I believe I should be able to work around this by specifying the csi plugin as a custom plugin so I can specify where the image should come from?

Ill try this, and hopefully close this issue!

Let us know if you still need further assistance.

I was able to do the following, and the CSI plugin image was able to pull.

However I am running into a new problem. When I check the Velero POD logs I see the following over and over again.

I assume I have something wrong with the minio storage bucket I am trying to use.

Ahh yes. I recently also encountered this issue while trying to reproduce another issue.
You basically need to specify a valid AWS region eve though you are giving a s3forcepath.
We are rearchitecting the operator and this limitation will no longer apply but it is not yet generally available. Thanks for clarifying the solution!


feat(app): support module JSON v6 commands in run log

closes #11228
Overview
This adds module (all 4 modules) JSON v6 command support to run log as well as waitForDuration
Changelog

add a bunch of cases to StepText and add test coverage for each case
add HeaterShakerDeactivateShakerRunTimeCommand to a type of ModuleRunTimeCommand

Review requests

upload a v6 command protocol with modules (you can do this by running PD with the H-S ff turned on), look through the run log, the text should display the command text correctly instead of only displaying the commandType
text should match what is mentioned in the ticket https://github.com/Opentrons/opentrons/issues/11228

Risk assessment
low

Created a follow up ticket to clean up what Brian mentioned: https://github.com/Opentrons/opentrons/issues/11253


Truncate descriptions in JSON-LD metadata to 5000 characters for compatibility with Google

One of the relevant places in the code: https://github.com/biosimulations/biosimulations/blob/10c713886ea555e8f2b0dbbdb76d3dcd882cc9d7/apps/simulators/src/app/simulators/view-simulator/view-simulator.service.ts#L322

It seems to be the other way around. The text that was flagged was ""Boolean model of the budding yeast cell cycle" which is 45 characters, short of the minimum 50 characters

I know the error is because the description is too short. We can't make descriptions longer, but we can truncate them to the 5,000 character limit if needed.


Fix publishing of shaded JCTools

Publishing currently fails with:
2020-08-13 08:41:13.921Z error [SonatypeClient] [close] Failed  - (SonatypeClient.scala:184)
2020-08-13 08:41:13.921Z error [SonatypeClient] Activity name:close, started:2020-08-13T08:40:44.348Z  - (SonatypeClient.scala:462)
2020-08-13 08:41:13.923Z error [SonatypeClient]     Failed: sources-staging, failureMessage:Missing: no sources jar found in folder '/io/monix/monix-internal-jctools_2.13/3.2.2+40-67cbea18'  - (SonatypeClient.scala:380)
2020-08-13 08:41:13.924Z error [Sonatype] [STAGE_FAILURE] Failed to close the repository.  - (Sonatype.scala:406)
##[error]Process completed with exit code 1.

As part of this PR I'm also trying to activate automatic backporting. Let's see how this goes.

Ahh, I have only checked with publishLocal


Update identifier module to version 1.0 of W3C specs

Specification can be found here: https://www.w3.org/TR/did-core/#core-properties

The not-in-code documentation is WIP, but I'll open another pr for that, meanwhile the implementation is reday for prime time


Perceptual Loss

Thanks for sharing your amazing work.
In the paper you mentioned that  "  adversarial loss for the generator is combined with the Laplacian pyramid loss to
form the perceptual loss for ST-MFNet fine-tuning" can you please let us know the value for lambda used and after how many epochs of training with just Laplacian pyramid loss this perceptual loss term was introduced.
Thanks

Thanks for the quick reply


Fix incorrect counts for capsuled models with the same name

If I have 2 models that share the same name but are encapsulated in different modules the entity counts on the dashboard page are incorrect. This happens as the counts are stored in a hash using the value AbstractModel#pretty_name as key. This method itself uses Model#model_name which strips the module name. In this specific case this results in the same key for different models and therefore in wrong counts.
This can be fixed by using Model#name instead of Model#model_name for the key.

Write tests, please!

Sorry. Here they are :)

Please also create User::Confirmed model for mongoid.

Looks okay, thank you!