[DOC-3077] Fix typos in backup and restore SMP topic

Fix typos in SMP backup and restore topic
What Type of PR is This?

[ ] Issue
[ ] Feature
[x] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[x] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Bookmarklet (feature request) :: Date and language

Users are currently unable to enter the date and language via the bookmarklet, and staff need to go back to the admin database to edit this information. It would be very time-saving to have this bit added to the app!

@Anapo14  Info about the bookmarklet and how to use it: http://jdarchive.org/en/bookmarklet/
Files for bookmarklet: src/JDA/CoreBundle/Resources/views/Widget/widget.html.twig
and app/Resources/views/widget.base.html twig. You might have to dig around through some other files too but that's up to you to find. For now, add a "Date Created" field and a "Language" field. Look up how to get a date entry field on a form - I'm sure there's some standard way by now. The language field can be a dropdown with "Chinese" "Korean" "Japanese" "English". For actually submitting these requests to the database through the form, the date has to be in PHP's DateTime format so you'll have to figure out how to get it into that format from the date entry HTML field but it shouldn't be that difficult. And the database field is "media_date_created" for that. The database field will be "language" for language, but it doesn't actually exist yet because we don't actually have a language field in our database, so you should figure out how you'd put it in the database with the rest of the fields, but leave it commented out for now because it won't actually work until I add the database column.
For the admin dashboard, you can find it here: http://jdarchive.org/admin/zeega/data/item/list
The files that display the admin dashboard are in src/Zeega/AdminBundle/Resources/views/edit_custom.html.twig
and
src/Zeega/AdminBundle/AdminEntity/ItemAdmin.php. I think all you have to do is add the "media_date_created" and "language" (but again, leave language commented out for now because it doesn't exist yet) to the configureDatagridFilters section in the ItemAdmin.php file, it should be pretty easy. The bookmarklet will be harder but I think I know how to do that so ask if you need help.
@annawada and @meeshmon - I don't think we actually have a "language" field in our database. I can add it though. Should we limit the options to "English", "Japanese", "Korean", and "Chinese"? I can set up the field to only have those options or any list of enumerated options. I don't think a plain text field would be a good idea however. Let me know what options I should include for the field if we need any more than the 4 above.

@corinnecurcie and @Anapo14. For now we can limit the options to the four language types. You could however just add others to be more exclusive. If we ever get lots of entries other than those four languages we can add that language later.
In addition to adding two more filters the admindashboard, I think Koko and Anna (correct me @annawada  if I am wrong) want the bookmarklet to mirror the admindashboard item create page. It does not have to mirror perfectly; for example, attribution uri might not necessary but it would be nice to be able to see the url on the bookmarklet or automatically load the date of curation to reflect it on the dashboard page when an user is adding a site.

Thank you very much for adding the date and language functions.  I'd really appreciate if you could add the url field on the bookmarklet. Recently, we had duplicated urls submissions through the bookmarklet.  We would like users to see the url to make sure they are submitting the right webpage.

The bookmark language designation does not appear in the edit page field. Is someone still working on it? The date works great.  I prefer bookmarklet system rather than the contribute page date sysytem, which I have to type the year to get to 2011.

Hi @jdaKoko I believe the language should be working for the bookmarklet submission now. I will work on getting the URI on the bookmarklet as well.

Thank you! The language field is working.

A belated thank you for adding the date/language fields! It is
extremely helpful for the workflow and easy to use.
On 1/21/15, jdaKoko<EMAIL_ADDRESS>wrote:

Thank you! The language field is working.

Reply to this email directly or view it on GitHub:
https://github.com/Japan-Digital-Archives/Japan-Digital-Archive/issues/873#issuecomment-70765411

Thank you very much for adding language and dates function.  There are bookmarklet problems in Firefox and Safari.  The calender does not appear in either. In Firefox the scroll down function has disappeared and the web page becomes completely whiite after clicking Add to JDA.

@corinnecurcie  Add an additional language field [Others] to Bookmarklet to fix an issue where the users who try to upload a content in a language other than the four listed can complete an entry.

@meeshmon
I getting familiar with some of the JDA coding. I am trying to access the admin dashboard page at http://jdarchive.org/admin/zeega/data/item/list but I get error message "403 Forbidden". How do you usually access the admin dashboard? Do I need special user privileges to access it?

@jcuanm
I tried the link you put the above and was able to access the page.
It must be the case that you need special permission. @jdaKoko Can you give Javier permission?

@jcuanm you're all set to log in the admin dashboard.
Please enter your username and password for the JDA site.
If you need the instructions on how to use the admin dashboard, let me know.
http://jdarchive.org/admin/zeega/data/item/list

@jdakoko @meeshmon.
Thanks, I can access the dashboard now. @jdaKoko Could you tell me where can I read about the dashboard that can provide me a little bit of context (instructions, purpose, main users, etc)?

@jcuanm
I sent the links to your gmail.
https://docs.google.com/presentation/d/1CiZepAOM-A38wbC1mJawu8GA8XmCcnD6T0EaP2emFI/edit?usp=sharing

@jcuanm @meeshmon
We need more list of years, maybe from 2000?
I cannot edit dates in the admin edit pages.

@jcuanm can you take a look at this when you have a chance?

I'm on it.

@jdakoko @meeshmon.
I was able to access the admin dashboard in the production site at http://jdarchive.org/admin/zeega/data/item/list
and the admin dashboard in my test environment (dev server) at:
http://dev.jdarchive.org/javier2/web/admin/zeega/data/item/list
However, permissions are preventing me from accessing the source code at "dev.jdarchive.org/javier2/web/admin/zeega/data/item/list" in order to make the changes.
I cannot access the "admin" and the subsequent directories.
Do you also handle permissions to access the code? or should I contact Alex Horak for this matter?
Also, @jdaKoko the link:
https://docs.google.com/presentation/d/1CiZepAOM-A38wbC1mJawu8GA8XmCcnD6T0EaP2emFI/edit?usp=sharing
that you sent me does not work. Could you please resend it?
Thank you.

@jcuanm

Do you also handle permissions to access the code? or should I contact Alex Horak for this matter?
I am sorry I do not handle permissions to access the code.
Also, @jdaKoko the link:...
I sent the sharing invitation  to<EMAIL_ADDRESS>while ago.  In order to see the Google Slide, you have to log in to the account and open the link in the google doc.

@jdaKoko
Thank you.

@horak
Hey Alex,
Still trying to access the admin dashboard. I sent you my SSH keys so you can add them to the production site and grant me access to the directories that I need to make the changes.
Thank you.

^ granted!

@horak
I tried to access the production site with ssh but it still asks me for a password. I was not able to log in. It says "Access Denied". I did not set a password on my ssh keys.

I just did this for steve and everything worked. Can you make sure the public ssh key you gave me lines up with the one you have stored locally on machine? Where did you pull your public ssh key from?


Try to add commands and get a unexpected break issue

for some reason I feel im doing it right and it just wont register

@deadpoolex can you add more details regarding the error? (eg: screenshots, error message)


Fix undefined local variable or method `messages'

This PR fixes a small typo that causes Danger to crash in my current setup (gitlab.com repo with GitLab CI runner to execute Danger).
The "original" version of the markdown_link_to_message method (github.rb#L419) also uses message and not messages.
Crashlog
$ if [ -n "${CI_MERGE_REQUEST_ID}" ]; then bundle exec danger --version && bundle exec danger; fi
5.2.2
bundler: failed to load command: danger (/Users/ci-user/builds/7e7afdcc/0/demo-app/ios/vendor/ruby/2.4.0/bin/danger)
NameError: undefined local variable or method `messages' for #<Danger::RequestSources::GitLab:0x007fef7899c1d0>
Did you mean?  message
  /Users/ci-user/builds/7e7afdcc/0/demo-app/ios/vendor/ruby/2.4.0/gems/danger-5.2.2/lib/danger/helpers/comments_helper.rb:28:in `markdown_link_to_message'
  /Users/ci-user/builds/7e7afdcc/0/demo-app/ios/vendor/ruby/2.4.0/gems/danger-5.2.2/lib/danger/helpers/comments_helper.rb:49:in `process_markdown'
  /Users/ci-user/builds/7e7afdcc/0/demo-app/ios/vendor/ruby/2.4.0/gems/danger-5.2.2/lib/danger/helpers/comments_helper.rb:59:in `block in table'
  /Users/ci-user/builds/7e7afdcc/0/demo-app/ios/vendor/ruby/2.4.0/gems/danger-5.2.2/lib/danger/helpers/comments_helper.rb:59:in `map'
  /Users/ci-user/builds/7e7afdcc/0/demo-app/ios/vendor/ruby/2.4.0/gems/danger-5.2.2/lib/danger/helpers/comments_helper.rb:59:in `table'
  /Users/ci-user/builds/7e7afdcc/0/demo-app/ios/vendor/ruby/2.4.0/gems/danger-5.2.2/lib/danger/helpers/comments_helper.rb:98:in `generate_comment'
  /Users/ci-user/builds/7e7afdcc/0/demo-app/ios/vendor/ruby/2.4.0/gems/danger-5.2.2/lib/danger/request_sources/gitlab.rb:123:in `update_pull_request!'
  /Users/ci-user/builds/7e7afdcc/0/demo-app/ios/vendor/ruby/2.4.0/gems/danger-5.2.2/lib/danger/danger_core/dangerfile.rb:247:in `post_results'
  /Users/ci-user/builds/7e7afdcc/0/demo-app/ios/vendor/ruby/2.4.0/gems/danger-5.2.2/lib/danger/danger_core/dangerfile.rb:277:in `run'
  /Users/ci-user/builds/7e7afdcc/0/demo-app/ios/vendor/ruby/2.4.0/gems/danger-5.2.2/lib/danger/danger_core/executor.rb:27:in `run'
  /Users/ci-user/builds/7e7afdcc/0/demo-app/ios/vendor/ruby/2.4.0/gems/danger-5.2.2/lib/danger/commands/runner.rb:66:in `run'
  /Users/ci-user/builds/7e7afdcc/0/demo-app/ios/vendor/ruby/2.4.0/gems/claide-1.0.2/lib/claide/command.rb:334:in `run'
  /Users/ci-user/builds/7e7afdcc/0/demo-app/ios/vendor/ruby/2.4.0/gems/danger-5.2.2/bin/danger:5:in `<top (required)>'
  /Users/ci-user/builds/7e7afdcc/0/demo-app/ios/vendor/ruby/2.4.0/bin/danger:22:in `load'
  /Users/ci-user/builds/7e7afdcc/0/demo-app/ios/vendor/ruby/2.4.0/bin/danger:22:in `<top (required)>'

          1 Warning

:warning:
Tests were not updated

          1 Message

:book:
@ffittschen is not a contributor yet, would you like to join the Danger org?

  Generated by :no_entry_sign: Danger

Perfect. Let's get this shipped.


TunerStudio: cleanup

(cherry picked from commit 0b2d596aa1d834e6c395843b617db6b1913cb67f)

@mck1117 isn't this the best kid of PR when it just removes code and stuff is still green and functional?
poke this one and others :)


Support 'default_security_group_ids' option

[#94035130]
Signed-off-by: Zhang Hua<EMAIL_ADDRESS>

Closing. Story updated with more details.


New theme for vlc media player

I would love a dracula theme for vlc.

I will close this Issue for organizational purposes, as it is an old request without community proposals. 😅


⚠ Fortnite has degraded performance

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

HTTP code: 200
Response time: 1838 ms

Resolved: Fortnite performance has improved in 1a4e6ca.


CheckstylePluginDependenciesIntegrationTest fails on German OS (again)

Expected Behavior
CheckstylePluginDependenciesIntegrationTest shouldn't fail when run under non-english language
Current Behavior
CheckstylePluginDependenciesIntegrationTest fail, if current language settings produce alternate text
Context (optional)
running quickTest brings this false positive up again, seems that #513 don't work anymore
Steps to Reproduce

checkout current master
run ./gradlew :code-quality:embeddedIntegTest --tests "org.gradle.api.plugins.quality.checkstyle.CheckstylePluginDependenciesIntegrationTest" under German language settings

Gradle version
8.2 commit 5417d132814dd91ea76d12ec98ffa2ac494d4c16 (current master)
Build scan URL (optional)
No response
Your Environment (optional)
No response

Thank you for providing a valid reproducer.
The issue is in the backlog of the relevant team but this area of Gradle is currently not a focus one so it might take a while before a fix is made.


Adding https detection so we can load resources over https

This is aimed at resolving issue #18
There will still be an issue on the server side though. The developers.eveonline.com path redirects to CCP's cdn but does not carry with it the protocol, only directing to http. The cdn supports https but this behavior might be intentional.

You are putting protocol prefix into resourcePaths map. I'd rather not have it there - just modify the url directly.

...in the meantime I am trying to figure out what's involved in changing the redirection server...

@filipppavlov do you prefer to just overwrite this.resourcePaths['res'] or could we add this as an option passed by the developer when they call ccpwgl.initialize?

Yes, overwriting should be just fine. This is just the default path, users can override it with ccpwgl.setResourcePath anyway.

I've updated the code so it does the same thing but without creating a new index in the object


Prepare for Technigala

This includes pitches to people who walk up and knowing your code so that you can speak to it.


Add alpha to GLMS body.

Is your feature request related to a problem? Please describe.
The argument alpha in GeoLiftMarketSelection() is not used in the function body. I would like to know if you plan to use it as the threshold to decide the significant column or it will not be used in the future?
Describe the solution you'd like
Add alpha within the GLMS body.
Additional context
Thanks @yulisong

Addressed in the linked PR. Closing this issue.


Get 2D Bounding Box from ssdlite_object_detection.tflite

Hi MediaPipe team,
I am trying to use "ssdlite_object_detection.tflite" to get the 2D object detection. The raw output includes 2034 detected bounding boxes for every input image. Previously, I used "Tensorflow.image.combined_non_max_suppression" and I did not get reasonable bounding boxes. Then I found "object_detection_cpu.pbtxt" which includes the whole pipeline which is used by MediaPipe for 2D object detection.
Now my question is that what are my options to get the correct bounding boxes when I am separately using the tflite model rather than the MediaPipe?

Hi @nargeshn ,
This issue is related to Tensorflow lite without Mediapipe , we don't support for Tensorflow lite without Mediapipe.


focus jumps and makes it impossible to use context menu

Testing #129288

looks like the active cell is stealing focus, which closes the context menu

This repros even without the active text editor, e.g.

We had the same fix for cell toolbar https://github.com/microsoft/vscode/issues/103926 . I copied the code but we should have a fix in the toolbar itself.

Follow up issue https://github.com/microsoft/vscode/issues/129724


Added link to Broccoli plugin

Coverage remained the same at 89.12% when pulling dc960a1a1ff6bcfdb57761e3cd74ceb5b1609f7e on kraftwer1:patch-2 into 17d8eec7f3bd692e6346f33b03b70c575f983e24 on wix:gh-pages.


Access denied with the following error: Cannot retrieve the public link of the file. You may need to change the permission to 'Anyone with the link'

Describe the bug
A clear and concise description of what the bug is.
Google Drive Download Error
Access denied with the following error:
Cannot retrieve the public link of the file. You may need to change
the permission to 'Anyone with the link', or have had many accesses.

To Reproduce
Steps to reproduce the behavior:

Run docker-compose up -d on dev folder
See error message

Expected behavior
A clear and concise description of what you expected to happen.
docker-compose to run properly.
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: [e.g. iOS]  Windows
Browser [e.g. chrome, safari] Chrome

Additional context
Complete Error Message:
 => CACHED [ 6/13] COPY src src                                                                                0.0s
 => CACHED [ 7/13] COPY srcext srcext                                                                                0.0s
 => ERROR [ 8/13] RUN python -m src.services.facescan.plugins.setup                                                                                139.4s
------
 > [ 8/13] RUN python -m src.services.facescan.plugins.setup:
#0 1.924 Collecting tensorflow==2.1.4
#0 2.010   Downloading tensorflow-2.1.4-cp37-cp37m-manylinux2010_x86_64.whl (422.0 MB)
#0 102.5      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 422.0/422.0 MB 4.4 MB/s eta 0:00:00
#0 103.1 Collecting tf-slim~=1.1.0
#0 103.1   Downloading tf_slim-1.1.0-py2.py3-none-any.whl (352 kB)
#0 103.3      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 352.1/352.1 KB 3.1 MB/s eta 0:00:00
#0 103.6 Collecting protobuf~=3.20.1
#0 103.7   Downloading protobuf-3.20.3-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.whl (1.0 MB)
#0 103.9      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.0/1.0 MB 3.6 MB/s eta 0:00:00
#0 104.0 Requirement already satisfied: six>=1.12.0 in /usr/local/lib/python3.7/site-packages (from tensorflow==2.1.4) (1.16.0)
#0 104.0 Collecting astor>=0.6.0
#0 104.0   Downloading astor-0.8.1-py2.py3-none-any.whl (27 kB)
#0 104.0 Collecting gast==0.2.2
#0 104.1   Downloading gast-0.2.2.tar.gz (10 kB)
#0 104.1   Preparing metadata (setup.py): started
#0 104.3   Preparing metadata (setup.py): finished with status 'done'
#0 104.9 Collecting numpy<1.19.0,>=1.16.0
#0 104.9   Downloading numpy-1.18.5-cp37-cp37m-manylinux1_x86_64.whl (20.1 MB)
#0 109.5      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 20.1/20.1 MB 4.4 MB/s eta 0:00:00
#0 109.6 Collecting keras-preprocessing==1.1.0
#0 109.6   Downloading Keras_Preprocessing-1.1.0-py2.py3-none-any.whl (41 kB)
#0 109.6      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 41.9/41.9 KB 4.0 MB/s eta 0:00:00
#0 109.6 Collecting termcolor>=1.1.0
#0 109.6   Downloading termcolor-2.1.1-py3-none-any.whl (6.2 kB)
#0 109.8 Collecting h5py<=2.10.0
#0 109.8   Downloading h5py-2.10.0-cp37-cp37m-manylinux1_x86_64.whl (2.9 MB)
#0 110.5      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.9/2.9 MB 4.1 MB/s eta 0:00:00
#0 110.5 Collecting keras-applications>=1.0.8
#0 110.5   Downloading Keras_Applications-1.0.8-py3-none-any.whl (50 kB)
#0 110.5      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 50.7/50.7 KB 4.1 MB/s eta 0:00:00
#0 110.5 Requirement already satisfied: wheel>=0.26 in /usr/local/lib/python3.7/site-packages (from tensorflow==2.1.4) (0.38.4)
#0 110.6 Collecting google-pasta>=0.1.6
#0 110.6   Downloading google_pasta-0.2.0-py3-none-any.whl (57 kB)
#0 110.6      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 57.5/57.5 KB 4.9 MB/s eta 0:00:00
#0 110.6 Collecting absl-py>=0.7.0
#0 110.6   Downloading absl_py-1.3.0-py3-none-any.whl (124 kB)
#0 110.7      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 124.6/124.6 KB 3.0 MB/s eta 0:00:00
#0 110.7 Collecting opt-einsum>=2.3.2
#0 110.7   Downloading opt_einsum-3.3.0-py3-none-any.whl (65 kB)
#0 110.7      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 65.5/65.5 KB 3.7 MB/s eta 0:00:00
#0 111.9 Collecting grpcio>=1.8.6
#0 111.9   Downloading grpcio-1.50.0-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (4.7 MB)
#0 113.1      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 4.7/4.7 MB 3.9 MB/s eta 0:00:00
#0 113.2 Collecting tensorflow-estimator<2.2.0,>=2.1.0rc0
#0 113.2   Downloading tensorflow_estimator-2.1.0-py2.py3-none-any.whl (448 kB)
#0 113.3      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 449.0/449.0 KB 4.2 MB/s eta 0:00:00
#0 113.4 Collecting tensorboard<2.2.0,>=2.1.0
#0 113.4   Downloading tensorboard-2.1.1-py3-none-any.whl (3.8 MB)
#0 114.3      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 3.8/3.8 MB 4.3 MB/s eta 0:00:00
#0 114.5 Collecting wrapt>=1.11.1
#0 114.5   Downloading wrapt-1.14.1-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (75 kB)
#0 114.5      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 75.2/75.2 KB 2.8 MB/s eta 0:00:00
#0 114.8 Collecting google-auth<2,>=1.6.3
#0 114.8   Downloading google_auth-1.35.0-py2.py3-none-any.whl (152 kB)
#0 114.9      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 152.9/152.9 KB 2.8 MB/s eta 0:00:00
#0 114.9 Requirement already satisfied: setuptools>=41.0.0 in /usr/local/lib/python3.7/site-packages (from tensorboard<2.2.0,>=2.1.0->tensorflow==2.1.4) (57.5.0)
#0 114.9 Collecting google-auth-oauthlib<0.5,>=0.4.1
#0 114.9   Downloading google_auth_oauthlib-0.4.6-py2.py3-none-any.whl (18 kB)
#0 115.0 Collecting markdown>=2.6.8
#0 115.1   Downloading Markdown-3.4.1-py3-none-any.whl (93 kB)
#0 115.1      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 93.3/93.3 KB 2.6 MB/s eta 0:00:00
#0 115.1 Requirement already satisfied: requests<3,>=2.21.0 in /usr/local/lib/python3.7/site-packages (from tensorboard<2.2.0,>=2.1.0->tensorflow==2.1.4) (2.24.0)
#0 115.1 Requirement already satisfied: werkzeug>=0.11.15 in /usr/local/lib/python3.7/site-packages (from tensorboard<2.2.0,>=2.1.0->tensorflow==2.1.4) (1.0.1)
#0 115.2 Collecting cachetools<5.0,>=2.0.0
#0 115.3   Downloading cachetools-4.2.4-py3-none-any.whl (10 kB)
#0 115.3 Collecting rsa<5,>=3.1.4
#0 115.3   Downloading rsa-4.9-py3-none-any.whl (34 kB)
#0 115.4 Collecting pyasn1-modules>=0.2.1
#0 115.4   Downloading pyasn1_modules-0.2.8-py2.py3-none-any.whl (155 kB)
#0 115.5      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 155.3/155.3 KB 3.0 MB/s eta 0:00:00
#0 115.5 Collecting requests-oauthlib>=0.7.0
#0 115.5   Downloading requests_oauthlib-1.3.1-py2.py3-none-any.whl (23 kB)
#0 115.6 Requirement already satisfied: importlib-metadata>=4.4 in /usr/local/lib/python3.7/site-packages (from markdown>=2.6.8->tensorboard<2.2.0,>=2.1.0->tensorflow==2.1.4) (5.1.0)
#0 115.6 Requirement already satisfied: chardet<4,>=3.0.2 in /usr/local/lib/python3.7/site-packages (from requests<3,>=2.21.0->tensorboard<2.2.0,>=2.1.0->tensorflow==2.1.4) (3.0.4)
#0 115.6 Requirement already satisfied: urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1 in /usr/local/lib/python3.7/site-packages (from requests<3,>=2.21.0->tensorboard<2.2.0,>=2.1.0->tensorflow=
=2.1.4) (1.25.11)
#0 115.6 Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.7/site-packages (from requests<3,>=2.21.0->tensorboard<2.2.0,>=2.1.0->tensorflow==2.1.4) (2022.9.24)
#0 115.6 Requirement already satisfied: idna<3,>=2.5 in /usr/local/lib/python3.7/site-packages (from requests<3,>=2.21.0->tensorboard<2.2.0,>=2.1.0->tensorflow==2.1.4) (2.10)
#0 115.7 Requirement already satisfied: zipp>=0.5 in /usr/local/lib/python3.7/site-packages (from importlib-metadata>=4.4->markdown>=2.6.8->tensorboard<2.2.0,>=2.1.0->tensorflow==2.1.4) (
3.10.0)
#0 115.7 Requirement already satisfied: typing-extensions>=3.6.4 in /usr/local/lib/python3.7/site-packages (from importlib-metadata>=4.4->markdown>=2.6.8->tensorboard<2.2.0,>=2.1.0->tenso
rflow==2.1.4) (4.4.0)
#0 115.8 Collecting pyasn1<0.5.0,>=0.4.6
#0 115.8   Downloading pyasn1-0.4.8-py2.py3-none-any.whl (77 kB)
#0 115.8      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 77.1/77.1 KB 3.0 MB/s eta 0:00:00
#0 115.9 Collecting oauthlib>=3.0.0
#0 115.9   Downloading oauthlib-3.2.2-py3-none-any.whl (151 kB)
#0 116.0      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 151.7/151.7 KB 3.2 MB/s eta 0:00:00
#0 116.1 Building wheels for collected packages: gast
#0 116.1   Building wheel for gast (setup.py): started
#0 116.4   Building wheel for gast (setup.py): finished with status 'done'
#0 116.4   Created wheel for gast: filename=gast-0.2.2-py3-none-any.whl size=7554 sha256=ea9b926b52cd88408d4f7533b40b17ce6bfed90f147fa6a3c51ef5fd11a608dd
#0 116.4   Stored in directory: /tmp/pip-ephem-wheel-cache-9kb0a67_/wheels/21/7f/02/420f32a803f7d0967b48dd823da3f558c5166991bfd204eef3
#0 116.4 Successfully built gast
#0 117.0 Installing collected packages: tensorflow-estimator, pyasn1, wrapt, termcolor, rsa, pyasn1-modules, protobuf, oauthlib, numpy, grpcio, google-pasta, gast, cachetools, astor, absl
-py, tf-slim, requests-oauthlib, opt-einsum, markdown, keras-preprocessing, h5py, google-auth, keras-applications, google-auth-oauthlib, tensorboard, tensorflow
#0 117.9   Attempting uninstall: numpy
#0 117.9     Found existing installation: numpy 1.19.5
#0 118.0     Uninstalling numpy-1.19.5:
#0 118.2       Successfully uninstalled numpy-1.19.5
#0 134.9 Successfully installed absl-py-1.3.0 astor-0.8.1 cachetools-4.2.4 gast-0.2.2 google-auth-1.35.0 google-auth-oauthlib-0.4.6 google-pasta-0.2.0 grpcio-1.50.0 h5py-2.10.0 keras-appl
ications-1.0.8 keras-preprocessing-1.1.0 markdown-3.4.1 numpy-1.18.5 oauthlib-3.2.2 opt-einsum-3.3.0 protobuf-3.20.3 pyasn1-0.4.8 pyasn1-modules-0.2.8 requests-oauthlib-1.3.1 rsa-4.9 tens
orboard-2.1.1 tensorflow-2.1.4 tensorflow-estimator-2.1.0 termcolor-2.1.1 tf-slim-1.1.0 wrapt-1.14.1
#0 134.9 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment
 instead: https://pip.pypa.io/warnings/venv
#0 135.1 WARNING: You are using pip version 22.0.4; however, version 22.3.1 is available.
#0 135.1 You should consider upgrading via the '/usr/local/bin/python -m pip install --upgrade pip' command.
#0 136.1 2022-11-25 01:21:11.660353: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'libnvinfer.so.6'; dlerror: libnvinfer.so.6: cannot ope
n shared object file: No such file or directory
#0 136.1 2022-11-25 01:21:11.660506: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'libnvinfer_plugin.so.6'; dlerror: libnvinfer_plugin.so
.6: cannot open shared object file: No such file or directory
#0 136.1 2022-11-25 01:21:11.660533: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:30] Cannot dlopen some TensorRT libraries. If you would like to use Nvidia GPU with TensorRT, plea
se make sure the missing libraries mentioned above are installed properly.
#0 137.4 Install dependencies: {'tensorflow==2.1.4', 'tf-slim~=1.1.0', 'protobuf~=3.20.1', 'tensorflow~=2.1.4'}
#0 137.4 Checking models for facenet.Calculator...
#0 137.4 Access denied with the following error:
#0 137.4
#0 137.4        Cannot retrieve the public link of the file. You may need to change
#0 137.4        the permission to 'Anyone with the link', or have had many accesses.
#0 137.4
#0 137.4 You may still be able to access the file from the browser:
#0 137.4
#0 137.4         https://drive.google.com/uc?id=1im5Qq006ZEV_tViKh3cgia_Q4jJ13bRK
#0 137.4
#0 137.4 Traceback (most recent call last):
#0 137.4   File "/usr/local/lib/python3.7/runpy.py", line 193, in _run_module_as_main

Thanks for reporting it. It looks like Google Drive updated its API.
I updated our gdown library, so it should be fine now. Could you check and confirm?

@pospielov works fine now, thanks!


Add MIPS architecture to releases

What should restic do differently? Which functionality do you think we should add?
offer mips architecture releases
What are you trying to do? What problem would this solve?
i'm running a couple of mips devices all of which do have some state i'd like to backup with restic. they are usually so low on compute power and memory that compiling on them is wishful thinking. crosscompiling on my laptop is something i just haven't figured out, and i thought it might be an easy thing to add to the release process right here :)
Did restic help you today? Did it make you happy in any way?
srsly :* i've just automated all my backups with ansible and restic :D

Which architecture(s) do you need? There are mips and mipsle as well as mips64 and mips64le...
 That's it, done. You can then run the resulting restic binary on mips.

ui, how neat. mipsle was the arch in question, for gnubee, a little opensource nas box.
crosscompiling worked like a charm, should have looked into the docs
thanks for the help

In your opinion, is it valuable if we offer binaries for all the MIPS architectures?

In your opinion, is it valuable if we offer binaries for all the MIPS architectures?

thank you for the consideration. indeed my use case is such that i manage my own and other infrastructure with ansible, and i'm using https://github.com/arillso/ansible.restic to manage restic backups which in turn depends on this very github repo's releases. so that would be the first argument.
the second argument is the problem of resources on a lot of mips* devices. usually they are extremely low end, and in my case i wouldn't be able to compile it on the target device, so i always have another machine dependency. this is probably true for a lot of devices that could be helped to manage their backups in a consistent manner with a tried and proven tool like restic.
so if this would be just another couple of entries in your ci, and given that backups is something that every architecture should get to do as easy as possible, it'll be a great favor to the public, for sure.
if you wanna go all bonkers it would be an interesting sidequest to minimize memory footprint, because as mentioned above - low end devices, every byte counts :D

thank you for the consideration. indeed my use case is such that i manage my own and other infrastructure with ansible, and i'm using https://github.com/arillso/ansible.restic to manage restic backups which in turn depends on this very github repo's releases. so that would be the first argument.
the second argument is the problem of resources on a lot of mips* devices. usually they are extremely low end, and in my case i wouldn't be able to compile it on the target device, so i always have another machine dependency. this is probably true for a lot of devices that could be helped to manage their backups in a consistent manner with a tried and proven tool like restic.
so if this would be just another couple of entries in your ci, and given that backups is something that every architecture should get to do as easy as possible, it'll be a great favor to the public, for sure.
if you wanna go all bonkers it would be an interesting sidequest to minimize memory footprint, because as mentioned above - low end devices, every byte counts :D

Yeah, there's not so much we can do about the memory usage, but let's see how much longer our CI runs when cross-compiling for mips*

Yeah, there's not so much we can do about the memory usage, but let's see how much longer our CI runs when cross-compiling for mips*


MM-16133 - Updating css variables for 5.14

Summary
MM-16133 - Updating css variables for 5.14
Some theme variables don't seem to be working for 5.14, as they're not present there. So just adding them in.
Ticket Link
https://mattermost.atlassian.net/browse/MM-16133

@asaadmahmood
Error trying doing the automated Cherry picking. Please do this manually
+++ Updating remotes...
Fetching upstream
Fetching origin
+++ Updating remotes done...
+++ Creating local branch automated-cherry-pick-of-#3306-upstream-release-5.14-1564494489
Branch 'automated-cherry-pick-of-#3306-upstream-release-5.14-1564494489' set up to track remote branch 'release-5.14' from 'upstream'.
+++ Downloading patch to /tmp/3306.patch (in case you need to do this again)

+++ About to attempt cherry pick of PR. To reattempt:
  $ git am -3 /tmp/3306.patch

Applying: MM-16133 - Updating css variables for 5.14
Using index info to reconstruct a base tree...
M	utils/utils.jsx
Falling back to patching base and 3-way merge...
No changes -- Patch already applied.

+++ I'm about to do the following to push to GitHub (and I'm assuming origin is your personal fork):

  git push origin automated-cherry-pick-of-#3306-upstream-release-5.14-1564494489:automated-cherry-pick-of-#3306-upstream-release-5.14

+++ Creating a pull request on GitHub at mattermost-build:automated-cherry-pick-of-#3306-upstream-release-5.14

+++ Returning you to the master branch and cleaning up.


Create ENC script

Create ENC output format:
"
classes:
role::lightweight_component:
id:
- 1
- 3
"
PS: Indentation matters

Wrong place, should be in ENC repo


Kicks players on give rank

Description
When I give a rank to anyone, the server kicks a lot of people with this error: Internal Exception: java.io.IOException: Error while read(...): Connection reset by peer (this doesn't always happen, it happens very rarely, but if it happens to me at an important moment it would be really annoying)
Reproduction Steps
1 - Give a rank to anyone
2 - Console kicks to the server kicks people (almost everyone connected)
Expected Behaviour
Don't kick anyone
Server Details
spigot 1.8.8
LuckPerms Version
v5.4.30
Logs and Configs
Default
Extra Details
Nothing

can confirm happening to me also. in 1.17 paper

Do you happen to have TAB installed?

Yes, I have
El lun, 8 ago 2022 a las 17:18, Frying☆Pan @.***>)
escribió:

Do you happen to have TAB installed?
—
Reply to this email directly, view it on GitHub
https://github.com/LuckPerms/LuckPerms/issues/3453#issuecomment-1208265943,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2J5OL3QMWMWKSGVE3GB5R3VYEQNNANCNFSM55WXDSQQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

update TAB then, there was a bug that has been fixed that caused that

ohhh, okey. I will update


[feat] : Adding features to bot-verse/routes.py

Hi @kom-senapati!! Here is a list of improvements  I want to make in the file to improve functionality, readability and speed of routes:-
1.Blueprints: Introduced Flask Blueprints for better route organization.
2.Docstrings: Added docstrings to all route functions.
3.Error Handling: Improved error handling with try-except blocks for database operations.
4.Security: Ensured user inputs are validated and sanitized.
5.Performance: Used eager loading for database queries where applicable.
6.Code Consistency: Ensured consistent use of quotes and formatting throughout the file.
Please assign me this issue.
Thanks,
Yash Vashishth
(Contributor, GSSoC'24(Extd) and Hacktoberfest)

Also pls add the gssox-ext and hacktoberfest and level 2 tag to the issue

Ok go ahead

Hi @kom-senapati can you assign me this issue please

Its assigned already

Hi @PrathamChitkara and @kom-senapati im working on this issue. Will raise pr in half an hour


Further endpoint regeneration improvements

The final goal is to reduce the need to recompute all state relevant for an endpoint via a single 'kitchen-sink' approach. Ideally we can handle different types of events from different parts of the cilium-agent.
[ Several comments have been integrated into this top level description ]
High Level:

[x] reduce the number of calls to regenerate if possible for endpoints (I am trying to do this in #5359 , for instance).

[ ] Needs to split into individual tasks

[x] reduce the number of compilations per endpoint (e.g., #5294)
[x] speeding up compilation if compilation is indeed necessary (e.g., #5363 )
[ ] reducing amount of locking (#5446)
[x] improve build queue code for endpoints (@tgraf)
[x] extract configuration updates for endpoints from policy regeneration (@ianvernon)
[ ] Discuss what happens in failure cases; rollback (if so, what needs to be rolled back - PolicyMap, XDS Cache changes, BPF program itself?)
[ ] Simplification of policy calculation by removing extraneous / unnecessary fields

this will reduce the amount of state kept in the endpoint and will make testing regeneration of policy easier.

[ ] Add UUID to regenerationContext. This will make it easy to track a single regeneration for an endpoint.

Individual Tasks:

[ ] Get rid of CompilationLock (#5446)
[ ] Get rid of BuildMutex (#5446)
[x] Cache header file content to not having to do expensive IO operations before hashing header file

#5438

[ ] Don't hold endpoint mutex in regeneratePolicyAndBPF()
[x] Remove DROP_ALL from datapath (https://github.com/cilium/cilium/pull/5379)

This requires removing support for labels on creation.

[x] Remove POLICY_INGRESS and POLICY_EGRESS from datapath (#5294)
[x] Do not blindly TriggerPolicyUpdates for all endpoints when we receive a K8s endpoint update (#5359)

We also limit the entire endpoint regeneration process based off of the number of CPUs present. This includes application of updated configuration, policy regeneration, PolicyMap updates, etc. We should maintain such a queue limited by number of CPUs, but only for compilations of the programs themselves. A lot of the time now, we don't even need to re-compile the programs, especially with changes like #5332 and #5325 coming in. This would allow for a ton of concurrent endpoint regenerations to occur at once (without having a limit based off of CPUs), but have the actual compilation process for endpoints still be gated by the number of CPUs present.

For tracking purposes, these are my thoughts on multiple other angles to this as well:

reduce the number of calls to regenerate if possible for endpoints (I am trying to do this in  #5359 , for instance).
reduce the number of compilations per endpoint (e.g., #5294)
speeding up compilation if compilation is indeed necessary (e.g., #5363 )
reducing amount of locking (which this issue is tracking)
figuring out what are the main blocking operations in regeneration (which this issue has implemented)

After #5294 is merged, remove DROP_ALL from datapath.

@tgraf consider replacing https://github.com/cilium/cilium/blob/359943d562dfcf534794bb2a144706e530f758b4/pkg/endpoint/endpoint.go#L1384 with something faster like https://golang.org/pkg/encoding/gob. When doing this, it will require us to maintain that function for at least 2 releases to allow for downgrades without breaking the restore functionality.

with something faster like https://golang.org/pkg/encoding/gob. When doing this, it will require us to maintain that function for at least 2 releases to allow for downgrades without breaking the restore functionality.

I think we would have to encode both for a while as otherwise, the downgrade will be a problem.

The remaining work will be scheduled for 1.4

Moving this to be part of the Policy Engine Improvements project

All the important work on this has been completed. Closing.


[SPARK-27322][SQL] DataSourceV2: Select from multiple catalogs

What changes were proposed in this pull request?
Support multi-catalog in the following SELECT code paths:

SELECT * FROM catalog.db.tbl
TABLE catalog.db.tbl
JOIN or UNION tables from different catalogs
SparkSession.table("catalog.db.tbl")
CTE relation
View text

How was this patch tested?
New unit tests.
All existing unit tests in catalyst and sql core.

Test build #105947 has started for PR 24741 at commit c504b2f.

This PR depends on #24686. It'd easier to review commit c504b2f only.

Can one of the admins verify this patch?

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11199/
Test PASSed.

Test build #105947 has finished for PR 24741 at commit c504b2f.

This patch fails to generate documentation.
This patch merges cleanly.
This patch adds the following public classes (experimental):
trait TableIdentifierHelper extends LookupCatalog
 implicit class TableIdentifierHelper(parts: Seq[String])
case class UnresolvedRelation(table: TableIdentifierLike)
sealed trait TableIdentifierLike
case class CatalogTableIdentifier(catalog: TableCatalog, ident: Identifier)
class AstBuilder(conf: SQLConf)

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/105947/
Test FAILed.

There are 2 major design points in this PR:

Create TableIdentifierLike interface to ease the migration from legacy TableIdentifier to CatalogTableIdentifier
Resolve multipart table identifier to CatalogTableIdentifier/TableIdentifier in AstBuilder. Don't quite like this choice but it seems to minimize changes in this PR comparing to alternatives that I will list below.

I discovered these sore spots so far in the transition from TableIdentifier to CatalogTableIdentifier:

CTE relation
View text
Hints

Alternatives to resolving multipart table identifier in AstBuilder

Parser.parsePlan

Analyzer. We can switch to this choice after taking care of the sore spots.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11225/
Test PASSed.

Test build #105973 has started for PR 24741 at commit d259020.

Test build #105973 has finished for PR 24741 at commit d259020.

This patch fails to generate documentation.
This patch merges cleanly.
This patch adds the following public classes (experimental):
trait TableIdentifierHelper extends LookupCatalog
 implicit class TableIdentifierHelper(parts: Seq[String])
case class UnresolvedRelation(table: TableIdentifierLike)
sealed trait TableIdentifierLike
case class CatalogTableIdentifier(catalog: TableCatalog, ident: Identifier)
class AstBuilder(conf: SQLConf)

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/105973/
Test FAILed.

Please hold off review. Testing changes suggested by Ryan to move resolution to Analyzer.

@jzhuge and I have been working on a version that does the table resolution in the analyzer instead of in AstBuilder, which should be cleaner to keep the parser code separate from the implementation.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11299/
Test PASSed.

Test build #106049 has started for PR 24741 at commit b6eccd0.

Test build #106049 has finished for PR 24741 at commit b6eccd0.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106049/
Test FAILed.

Merged build finished. Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11300/
Test PASSed.

Test build #106050 has started for PR 24741 at commit daffc52.

Test build #106050 has finished for PR 24741 at commit daffc52.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106050/
Test PASSed.

Test build #106060 has started for PR 24741 at commit c04d3b0.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11311/
Test PASSed.

Test build #106060 has finished for PR 24741 at commit c04d3b0.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106060/
Test PASSed.

@cloud-fan @dongjoon-hyun @HyukjinKwon This PR is ready for review.
@rdblue and I have switched Relation Resolution from AstBuilder (as in the original commit) to DataSourceResolution in Analyzer. The core logic is much simpler and cleaner. We were able to overcome the obstacles I described in the first comment either with mostly minor fixes in this PR, or a separate PR #24763 for more thorough review.

Rebased and squashed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11412/
Test PASSed.

Test build #106159 has started for PR 24741 at commit b1e04cd.

Test build #106159 has finished for PR 24741 at commit b1e04cd.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  class ResolveJoinStrategyHints(
case class UnresolvedRelation(multipartIdentifier: Seq[String]) extends LeafNode

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106159/
Test PASSed.

I did a quick pass and left a few comments. @jzhuge Thank you for your work!
@jiangxb1987 Please take a look, especially about the test case coverage?

Rebase and fix review comments.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11441/
Test PASSed.

Test build #106190 has started for PR 24741 at commit 62811ff.

Test build #106190 has finished for PR 24741 at commit 62811ff.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class UnresolvedRelation(multipartIdentifier: Seq[String]) extends LeafNode

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106190/
Test FAILed.

Rebased to resolve conflicts with the base branch.
And minor fixes.

Test build #106224 has started for PR 24741 at commit 2d05b49.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11472/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11477/
Test PASSed.

Test build #106229 has started for PR 24741 at commit 3ae1816.

Test build #106229 has finished for PR 24741 at commit 3ae1816.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Test build #106224 has finished for PR 24741 at commit 2d05b49.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class UnresolvedRelation(multipartIdentifier: Seq[String]) extends LeafNode

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106229/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106224/
Test FAILed.

Retest this please.

@gatorsmile, when you have time, could you have another look at this? There are responses to your comments.

Test build #106254 has started for PR 24741 at commit 3ae1816.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11501/
Test PASSed.

Does anyone know this failure in several recent test builds?
[error] running /home/jenkins/workspace/SparkPullRequestBuilder/R/run-tests.sh ;
 process was terminated by signal 9

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11503/
Test PASSed.

Test build #106257 has started for PR 24741 at commit 8f2211c.

Test build #106254 has finished for PR 24741 at commit 3ae1816.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106254/
Test PASSed.

Test build #106257 has finished for PR 24741 at commit 8f2211c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106257/
Test PASSed.

Test build #106332 has started for PR 24741 at commit e24afd1.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11578/
Test PASSed.

Rebase and squash. Move DataSourceV2Relation to Catalyst since #24815 is merged. Move into a new rule ResolveTables because this is for table resolution and we may add a ResolveViews rule down the road.

Test build #106332 has finished for PR 24741 at commit e24afd1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106332/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11622/
Test PASSed.

Test build #106377 has started for PR 24741 at commit 01b720e.

Test build #106377 has finished for PR 24741 at commit 01b720e.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106377/
Test FAILed.

Retest this please.

@dongjoon-hyun, do you have time to review this? It is about ready to go and is blocking other DSv2 work.

Test build #106392 has started for PR 24741 at commit 01b720e.

Sure, @rdblue . Thank you for pinging me.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11637/
Test PASSed.

Test build #106392 has finished for PR 24741 at commit 01b720e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106392/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11642/
Test PASSed.

Test build #106397 has started for PR 24741 at commit 62b76e9.

Rebase and squash

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11644/
Test PASSed.

Test build #106399 has started for PR 24741 at commit 2568288.

Test build #106397 has finished for PR 24741 at commit 62b76e9.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106397/
Test PASSed.

Test build #106399 has finished for PR 24741 at commit 2568288.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106399/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11682/
Test PASSed.

Test build #106439 has started for PR 24741 at commit 2720d82.

Test build #106439 has finished for PR 24741 at commit 2720d82.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106439/
Test PASSed.

Mostly, looks correct. We need to fix INSERT OVERWRITE DIR case and the others are minor for now. Thank you, @jzhuge .

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11692/
Test PASSed.

Test build #106449 has started for PR 24741 at commit b8cdf6c.

Test build #106449 has finished for PR 24741 at commit b8cdf6c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106449/
Test PASSed.

I have only comment about adding more code comments, which can be addressed later. I'm merging it to unblock the DS v2 project, thanks for your hard work @jzhuge @rdblue !

Thanks @cloud-fan @dongjoon-hyun @gatorsmile @rdblue for the excellent reviews! Thanks @rdblue for the great help!


Search results are not updated when package is added

Steps to reproduce:
Run verdaccio.
Publish a package to it.
Try search it in the search toolbox.
Expected behavior:
Package is present.
Actual behavior:
Package is absent.
Meanwhile, package is present on the main page.
Restarting verdaccio makes it appear in the search.
Also i noticed another one strange thing: if i serach full package name, eg package is named QWERTY, typing QWERT shows it in the search, while if i type QWERTY there's no search results at all.

Thanks 🙏 for reporting this, it is duplicated there is already one reported by @DanielRuf


Potential UniFi caching issue

https://www.reddit.com/r/Ubiquiti/comments/18hgpw1/security_problem/?share_id=yUmL6IOwgoKmgd3idJqk9&utm_content=2&utm_medium=ios_app&utm_name=ioscss&utm_source=share&utm_term=1

Thank you! Added it.


Ghost CI

A long time ago we talked about running tests on multiple operating systems using Docker and Jenkins. Today, Travis offers support for docker natively so I though I'd give it a try.
Here are the results:
https://github.com/jgillich/Ghost-CI
https://travis-ci.org/jgillich/Ghost-CI

Runs tests on 6 different Linux distributions
Supports multiple versions per distribution
Works on any CI that provides Docker API access
Adding new distributions is a matter of minutes

The way it works is basically: Render handlebar templates to Dockerfiles, bundle them with Ghost in a tarball, then use the Docker API to build images and run them.
It was a fun little project, now the question is can you use any of this? Integrating this in the main repo wouldn't be a good idea because it takes tons of resources, not to mention that it only runs on VMs. I think this would be something to run maybe once a week and before releases.

This is really cool! Thanks for your work here :)

I've rewritten this to be a simple executable that is configured through a dotfile. @ErisDS if you are interested, let me know. If not, that's fine too. :wink:

I think this is really cool, but I'm struggling to think of how we can use it. We've been trying to optimise our builds for a while because they take too long and get in the way of development. Also worth noting, we're thinking of pushing towards having a single 'standard' install, which would likely be Ubuntu LTS, with much clearer documentation etc that centres around that one single platform.
The idea being that of course, Ghost will work on other platforms, but that documentation, fixes or improvements focused on any other platform would be community led. Ideally, we want to get more people into our Core Team so that this sort of thing can happen much more easily.
With regard to testing using chimera, I'm thinking it would be cool to see something like a Ghost-Nightly repo that automatically has master pushed to it each night and runs these multiple builds. Something like this could potentially be used for memory & performance testing as well - something else I'd love to see, but I just haven't had enough time to set it up.

About the standard install, maybe you could do it via Docker image, like Discourse? It's their default installation method, and I think it's pretty great.
Nightly builds sounds like a good idea, but I'm not sure how to do the push. Do we

add a after_success hook that checks the date of the last commit and pushes to the repo?
use some third-party service? (not sure if something like that exists)
Throw a cron job on some server?
Do something else?

About the standard install, maybe you could do it via Docker image, like Discourse?
We've thought about that, quite a bit, and the conclusion was it isn't any more user-friendly. Docker is dev friendly, but quite confusing to a large group. It's still a possibility though.

As for how to do nightlies then either:

use some third-party service? (not sure if something like that exists)

This.. if we can find something, maybe https://nightli.es/ ??

Prob this?

Nightlie.es looks good. There's also Travis Cron.
I've set up the repo and it will let it run for a few days to make sure things are reliable before transferring it. About distros, you probably don't want any more than these, right?  :)

https://travis-ci.org/jgillich/Ghost-Nightly/jobs/94897638#L6643
And my last comment said something about reliable testing. :grinning:

Closing this as it's pretty out of date now and the links are dead 😉


Geocoder::ConfigurationError (Please specify a valid lookup for Geocoder (:amazon_location_service is not one of

BEFORE POSTING AN ISSUE, PLEASE MAKE SURE THE PROBLEM IS NOT ADDRESSED IN THE README!
Expected behavior
Geocoder Should Work
Actual behavior
Getting Error: Geocoder::ConfigurationError (Please specify a valid lookup for Geocoder (:amazon_location_service is not one of: :location_iq, :dstk, :esri, :google, :google_premier, :google_places_details, :google_places_search, :bing, :geocoder_ca, :yandex, :nationaal_georegister_nl, :nominatim, :mapbox, :mapquest, :uk_ordnance_survey_names, :opencagedata, :pelias, :pickpoint, :here, :baidu, :tencent, :geocodio, :smarty_streets, :postcode_anywhere_uk, :postcodes_io, :geoportail_lu, :ban_data_gouv_fr, :test, :latlon, :amap, :osmnames, :baidu_ip, :abstract_api, :freegeoip, :geoip2, :maxmind, :maxmind_local, :telize, :pointpin, :maxmind_geoip2, :ipinfo_io, :ipregistry, :ipapi_com, :ipdata_co, :db_ip_com, :ipstack, :ip2location, :ipgeolocation).)
Steps to reproduce
config/initializers/geocoder.rb
Geocoder.configure(
lookup: :amazon_location_service,
amazon_location_service: {
index_name: '###',
api_key: {
access_key_id: '###',
secret_access_key: '###',
}
}
)
Environment info

Geocoder version: 1.6.7
Rails version: 6.1.4
Database (if applicable): Postgres
Lookup (if applicable): amazon_location_service

Sorry about that. The README seen on Github is for the current HEAD. The :amazon_location_service lookup was just added and will be available in the next gem version (coming very soon).


Build links ASAP

Current roomplanner code waits until rcl7/8 to build links outside of the core city limits, but link planner should run based on the number of links available (2 available at rcl5 => 1 miner should use a link)

We now build links at RCL 6. Having one miner use a link would save 1 energy/tick from decay, but would require miners to have carry parts, as well as a RCL 5 ferry.


Raycasting objects are not found where they visually are

Raycast on an object, it's not where it should be
Description

With our latest exports from v0.98.27 all of our objects that we are trying to interact with are no longer where they are, the ray caster is somehow picking them up way far off (down & to the right). Tested with a brand new scene and are getting the same results

Note: If you run the included test scene in the editor, the ray caster picks it up just fine. It's not until you save/publish for web that you then have the issue.
test_raycast.zip
Version

0.98.27

Platform

Web Version [X]
Windows [ ]
Linux [ ]

+1 for this issue. As far as we can currently tell, it's a showstopper for our project. Thanks for looking into it!

So after some more playing with this bug and now setting up our own version of nunu on our web server so we can move forward with work, I've determined that the issue is in the new default scene. When we pull in our scenes created from a pervious version of the default scene, make edits and save. No issues with our raycaster landing on the objects and returning it's found the object your mousing over. But the more intensive 3D side of our process involves basically folding the old scene into a new default scene, and that export is the one that was breaking our scenes raycaster.
Again our workaround we're testing right now is I've created a local branch of the main git repo and rolled back to the 8/5 0.98.15 version and we're using that version of the editor to iterate and work on our scenes for now.

Hello
This was caused by a bad update in the canvas size in the runtime. Thanks a lot for reporting this bug should be fixed in the last version but already available in the web (0.98.28).
I still need to perform additional testing to ensure that everything is working correctly. This may have been caused by some changes applied for the AR support.
Thanks a lot once again.
Cheers

Hey José
Unfortunately, it's still broken. Here are my steps to test/recreate:

Start with loading page with default scene (using new version 0.98.28)
Added a container, JS script, orbit controls, perspective camera
Nested the camera in the orbit controls, and the orbit controls in the container
Changed the orbit control variables as such
• set distance, max distance, & min distance to .001
• set limit up to 0.533 and limit down to -0.533
• set vector to (1.15, 0.15)
Change the container position to (3.1, 1.78, 4.87)
To the script I modified it to read:

var box = scene.getObjectByName('box')

function initialize() {
	// TODO ADD CODE
}

function update(delta) {
	// TODO ADD CODE
	var intersect = closestTappedObjectIn([box])
	if (intersect != null) {
		console.log('hovering on the box')
	}
}

function closestTappedObjectIn(objects)
{
	var intersects = [];
	intersects = scene.raycaster.intersectObjects(objects);
	var closestObject = null;
	var closestDistance = 1000000;
	for (var i = 0; i < intersects.length; i++) {
		if (intersects[i].distance < closestDistance) {
			closestDistance = intersects[i].distance;
			closestObject = intersects[i].object;
		}
	}
	return closestObject;
}

Select run:
• When you hover over the box, as expected you see printed out in the console 'hovering on the box`
Select File->Publish (set my name to ray_cast_test28)
Pointed my local web server to the downloaded unzipped director
Expected Results:
• When hovering over the box I should see the hovering on the box print out to the console
Actual Results:
• Nothing is printed when hovering over the box, but if I moved my cursor to the right and down, I'll eventually find a spot that the raycaster says my box is...

Thanks a lot for this data, it will be of great help for sure.
I Will come back with a solution as soon as possible.


Allow to opt out of zeroize dependency

Continue to provide safe buffer implementation by default but allow to opt-out of the zeroize dependency. Also bumps zeroize to 1.0.
This is done to support lower-than 1.39 MSRV and to allow the users to manage the security themselves if they want to (e.g. other crates might be used or the overhead of always zeroing every buffer might be too much)

Thanks, sounds good to me. I specified the minor version of zeroize, because they claim that a MSRV update on their side would bump the minor version, so better be cautious.


PB DynamicGo support importDirs

Kitex PB 泛化调用支持用户配置PB IDL import路径

Please use the template for the description, since some of our tools rely on this.


Incorrect agent version labeled

Describe the problem
When updating to the newest version the dashboard doesn't list the correct version
To Reproduce
Steps to reproduce the behavior:

Update the dashboard to v2
Update client to newest version
See incorrect version in dashboard

Expected behavior
The correct version listed in the dashboard
Are you using NetBird Cloud?
Netbird selfhosted: 0.25.8
OS: Debian GNU/Linux 11
CPU: Intel Xeon E5-2680 v2 (2) @ 2.799GHz
Memory: 2975MiB
Screenshots
Dashboard:

Client:

Netbird's openrc service was never restarted during the update process, this is unrelated to netbird


Integrated terminal blank commands

OS Version: Windows 10

When I use the terminal, all my commands are blank, and the colors are weird, looks like is selected, but it isn't!

It looks like your report is missing some important information, See this wiki page for more info on how to report actionable terminal issues.
/needsMoreInfo


[soil2] Add new package soil2

My comment didnt go through this is just a simple port for soil2!

Hi @nightslashs
Thanks for contributing to vcpkg!
Here's the current status of the build:

Platform
Status

arm-uwp
Fail

arm64-windows
Pass

x64-linux
Pass

x64-uwp
Fail

x64-windows
Pass

x64-windows-static
Pass

x86-windows
Pass

It is only failing on UWP, I can accept the PR as it is. But let me know if you want to tackle fixing the UWP build.

Ill look into the uwp failures it appears to be something with the opengl linkage so ill let you know!

It appears that the issue is due to the version of opengl which is linked to the UWP app. I cant quite figure out why the included gl.h doesn't seem to define the types we expect it to (ie GLint, GLenum). Looking up some stuff it may be related to this but the fixes don't seem to make any difference https://stackoverflow.com/a/3939495.
Additionally, I have attempted to include the opengl port which seems to exist for this reason in specific but to no avail!
Lastly, I have attempted to check how some of the other gl reliant ports have dealt with this issue but it appears most of them provide raw binaries rather than building from source.
If you have any ideas on where to go forward the help would be much appreciated!

It looks like fixing builds for UWP might require some investigation.
Thanks for your effort, @nightslashs!
I'm OK with merging this PR as it is, it makes for a good initial version and we can add support for the missing platforms incrementally.
Can you please file an issue with your comments regarding UWP support so we can keep track on it?


Serverless function triggers support in SDK

I am new to cvat-sdk. Is there any support for triggering serverless function with SDK? Where can I get more information on this?

Hi, currently there is only low-level API support for /api/lambda/functions/* endpoints (responsible for the whole task/job annotation), added in #6276 recently, and there are no releases with these updates yet. Unfortunately, this part lacks documentation and API schema now, but it will be improved in future.


[EC2] describe_iam_instance_profile_associations

Collect EC2 instance IAM associations

Not needed. The iam_instance_profile_associations field is already present.


Reactivate Leaderboard test after fixing flakiness.

The Leaderboard test frequently timesout and it's hard to diagnose because all tests are in one method. Different methos should be created for different tests and then we can diagnose the timeouts properly.
I've skipped it in #927.

@jsimonweb reassigning to you since you are the original writer of these tests, and might have better insights in what is happening. See also a related internal buganizer issue that I've assigned to you.
Let me know if there's something I can do to help.

Closed via #1215


rs485 pinout

hello, thank you kindly for this code and explanation.
I have a unitree A1 motor and an rs485 to usb adapter with output of GND, A+, B-.
could you tell me the pinout of the rs485 input on the driver? in what order do I need to connect those 3 connections?
also, does the motor tools work with the A1 motor?

Hello, has your issue been resolved?


The current state of the API

As you could've seen in the release description for <IP_ADDRESS>, the constructor for MObject is now static, I had to change every instance of self in every constructor, and so, I forgot some, and now it's quite broken.
Yesterday I was also talking to my friend about the __index and __newindex metamethods, I knew __index was fired when k didn't exist in t, but I didn't know that also applied for __newindex! "Crap! But it all seemed to work fine!". And that's why Mt BETA <IP_ADDRESS> is a pre-release.
I will create an actual release at the same time I release MSpinBox

But hey, at least it doesn't copy every member in the object when constructing.


Add workaround for json-minify to minify json object without line fee…

…d correctly.
Motivation:

We cannot call no-arg thrift API (service A { string mtd() }) from DocService because  json-minify minify empty json object as empty string.
Expected: JSON.minify("{}") -> "{}"
Actual:   JSON.minify("{}") -> ""

Modifications:

Append line feed to json string to avoid json-minify bug.

Result:

Invoke no-arg thrift API with the DocService debug form correctly.

Current coverage is 65.57% (diff: 100%)

Merging #287 into master will increase coverage by 0.05%

@@             master       #287   diff @@
==========================================
  Files           303        303
  Lines         11955      11955
  Methods           0          0
  Messages          0          0
  Branches       1750       1750
==========================================
+ Hits           7833       7839     +6
+ Misses         3288       3285     -3
+ Partials        834        831     -3

Powered by Codecov. Last update 2278ef7...a6b7d7c

Updated.
Modified json-minify to returns input json directly if input json doesn't have whitespaces or comments.

Thank you, @imasahiro !


Canadian Postcodes also can not start with DFIOQ or U

From http://en.wikipedia.org/wiki/Postal_codes_in_Canada#Number_of_possible_postal_codes
"Postal codes do not include the letters D, F, I, O, Q or U, and the
first position also does not make use of the letters W or Z"
I believe the previous version of this code misunderstood and read the above as "first position can only not have letters W or Z"

Whoops, too many commits in this request


Impossible to edit a document called "history"

Describe the bug
When an editor creates a new object with the name "history", it is impossible for the editor to edit that object.
To Reproduce
Steps to reproduce the behavior:

As admin
Go to https://volto.kitconcept.com/
Create a new Page with the title "History"
Page "https://volto.kitconcept.com/history" shows the front-page
Clicking on edit leads to the edit view of the front-page

Expected behavior
I'd expect that either the system prevents the user from creating content with reserved words (show a validation error, rename the content object automatically), or that we make this "just" work.

@sneridagh @plone/volto-team is there a way for editors to use reserved words like "history" in the URL? It is hard to tell clients that they can not create a page like www.mydomain.com/history. I guess the only way to solve this is to start using something like "/@@history".

I'm +1 on changing the builtin routes. I'd propose something like /+history, as not to clash with view names.

I'm +1 on changing the builtin routes. I'd propose something like /+history, as not to clash with view names.

I don't understand, aren't these exactly views? Before reading your comment I would have suggested to keep @@ for consistency with usuale Plone behavior, am I missing something?

I'm concerned that there will be confusion and inconsistency and will make it even harder to expose classic Plone views with something like https://github.com/eea/volto-middleware-vh

@tiberiuichim can you elaborate how exactly a frontend view @@history could clash with a backend view @@history? Don't we always have a way of telling exactly which is which?

In today's Volto we have a @@images and @@download proxies. They serve the Plone content 1:1, so for any @@ view I'd expect to see the Plone backend answering for it.
If we start prefixing our routes with @@, we will reach a point where, in the documentation, we'll have to say: 'this URL only works in Plone frontend', 'if you're looking for this view name in any zcml, you won't find it' and so on. Indeed, functionally the view names are the same and prefixing them similarly is enticing, but I think on long term it will cause headaches.
There's also the possibility of clashing names and even if that probability is very low, we'll still be sharing the same URI space between two different things.
And I wonder if this argument wasn't the same when it lead to the decision of prefixing plone.rest endpoints with a single @.

@tisto i had the same problem with routes /add and /edit
i solved the problem for that routes here https://github.com/plone/volto/pull/2664
maybe you have to do the same for /history

I am a bit reluctant to change all the route names at this point, (think about existing user's bookmarks). I think the problem is much more easy to tackle, let's redefine "history" view name and call it something less "common".
This is the list of the current system routes:
https://github.com/plone/volto/blob/2b062ea2b69b4ab7bad1b2fa3c3da11a5d27c9ee/src/routes.js#L85
the others are fine, the only conflictive one is "history" indeed.

Indeed, that seems to be a simpler solution for now.


Cannot rename project when importing a .jff FSA, name is blank

Description of the bug
When importing a .jff FSA file, the project that is generated has no/blank name, and cannot be renamed later on
To reproduce

Next to New Project click Import...
Select .jff file from computer
New project will open, name is blank, cannot be renamed in main menu

Expected behavior
Either a pop-up box will open with requesting a name of the project, or an auto-generated name gets assigned, like when creating a new project.
In both instances, project should be able to be renamed later.
Additional information

OS: Windows 11
Browser: Firefox

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Thanks for the report :) turns out there was an issue with importing logic where we'd set it as a blank name and it was never reaching the code to use the file name
Unfortunately there isn't currently a way to rename a project from the projects screen, so that issue isn't actually specific to the import issue - usually you have to do it from the project itself which also isn't possible if there's no name


Recurring Profiles

It doesn't look as though this module currently supports recurring payments. Any idea when this will become available?

HI, we are not plan to do this in the near future


fix(core): correct flags and feature name

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 80.74%. Comparing base (c14ade3) to head (e14cdc8).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #653   +/-   ##
=======================================
  Coverage   80.74%   80.74%
=======================================
  Files          97       97
  Lines       23945    23945
=======================================
  Hits        19334    19334
  Misses       4611     4611

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


simplify log & merge master

优化log并合并冲突

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.5 out of 8 committers have signed the CLA.:white_check_mark: lipanpan03:white_check_mark: qishipengqsp:white_check_mark: ljcui:white_check_mark: jiazhenjiang:white_check_mark: gtahoo:x: kehuang19:x: limingyao001:x: tugraphtugraph seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.5 out of 8 committers have signed the CLA.:white_check_mark: qishipengqsp:white_check_mark: jiazhenjiang:white_check_mark: ljcui:white_check_mark: gtahoo:white_check_mark: lipanpan03:x: kehuang19:x: tugraph:x: limingyao001tugraph seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


DSD-465: new icons for mobile menu

Fixes JIRA ticket DSD-465
This PR does the following:

Adds svg files for utility_account_filled, utility_account_unfilled, utility_hamburger and utility_search icons.
Exposes new icons in Icon component.

How has this been tested?

Storybook in local build of DS

Checklist:

[x] I have updated the Storybook documentation accordingly.
[x] All new and existing tests passed.

Front End Review:

[x] View the example in Storybook

Tugboat has finished building the preview for this pull request!
Link:

https://pr672-rjdkkqplawuxnutegwlilnmyrps6g8zv.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/613a5fae08cf47fb0f61a61f

@hokei and @wluisi Can one of you review this PR today?  I would like to have this ready for the release on Thursday.  I will be OOO this afternoon, but I can make any necessary adjustments tomorrow.  Thanks.


Usage question

Hello,
I have a check for a certain process that is running on serveral systems using metricbeat. I would like to know if I can make an alert if the process is missing on a system without having to create a separate rule for every system that is running that process.
Regards,
Peter

Sort of. If you use type: flatline with query_key: hostname and filter for that process, it would alert on any host where that process existed but then ceases to exist. I don't think there's an easy way to get it to alert on the initial set of hosts that don't have that process.

That's fine I can add a field which I can use to only list the hosts which should have the process running. Thank you for your answer.


Do request/notification handlers require locking?

I have a request handler that is invoked by an asp.net core controller method. If there are multiple parallel calls made to this controller, is the request handler also executed in parallel? I.e. do i need to lock my handlers?

Your request handlers will be handled in parallel. As far as locking, you don't lock handlers. You look at concurrency controls for whatever work is being done. This work may or may not have contention. As far as how you should approach that problem, there are a lot of great resources out there, this book is my favorite:
https://www.amazon.com/Designing-Data-Intensive-Applications-Reliable-Maintainable/dp/1449373321
Although if you're using SQL, the docs on concurrency are great too. In short - no, do not lock your handlers, that's almost certainly the wrong thing to do. Instead, look at concurrency controls on whatever resource the handler is working with.

Thank you so much for the response! (and the excellent library too!)
That book has been in my reading list for a while now. Will check it out
Thanks again


Allow bottom sheet title to be left aligned

Hello!
I would like to propose that there would be an additional parameter to the bottom sheet (and possibly also to the theme extension) that would allow to have the title in the navigation bar left aligned instead of centered.
The reason for this is that if an app uses titles in the app nav bar as left aligned it'd be a little incoherent to have those as centered in the bottom sheets or dialogs.
The logic for it is already implemented, see https://github.com/woltapp/wolt_modal_sheet/blob/767f4e45ed98368435731f22a6d2106eac81a54f/lib/src/widgets/wolt_navigation_toolbar.dart#L35
so it would just have to be made available to the users.
I can make a PR for it if you want :)

Ok so this is not as easy as I thought. centerMiddle on wolt_navigation_toolbar.dart does nothing, the top bar is rendered in the same way if that is set to true or false. MultiChildLayoutDelegate.layoutChild for the middle widget does so that it uses all the available space and centers the widget inside it, see for example this screenshot (where the Text widget is wrapped by a ColoredBox with red background):

So far the only way I got to have the title left align is to have it wrapped in a Row with mainAxisAlignment: MainAxisAlignment.start, this probably does not belong to the library.
I will still look into the layoutChild behaviour to see can that be altered in some way in the next days.

Handled as part of #64


test: simplify naming of yaml/targets

We allow the use of otk.define.foo or otk.target.osbuild.foo
to ensure when multiple otk.defines are done in a single file
it is still valid yaml. However in a lot of our examples we only
have a single otk.define in the file or only a single target.
Here there is no need to append a postfix.
This commit simplifies these occurances and removes unneeded
postfixes. They are still valid and some tests needs them but
the are no longer there by default.
We should probably do the same for the examples/**.
Only the last commit is relevant, the rest is just #161
[draft as it needs https://github.com/osbuild/otk/pull/161]

Can be undrafted/rebased. #161 has landed.


Can offset_encoding for Ruff be configured in Neovim?

Hello,
is it possible to configure the offset_enconding for ruff in neovim?
Background:
by default ruff has configured utf-8, when you use it together with pyright which is default to utf-16 neovim will produce a warning:
warning: multiple different client offset_encodings detected for buffer, this is not supported yet

I'm a bit confused by this warning because ruff isn't a client but a server. Ruff also negotiates the encoding with the client. That makes me suspect that another server doesn't support the position encoding negotiation and always enforces utf16 (in which case the previously negotiated utf8 encoding with ruff is outdated). But that seems like a neovim issue. Ideally neovim would re-negotiate with ruff if that happens
I found a related neovim issue https://github.com/neovim/nvim-lspconfig/issues/2184
It seems that setting the position encoding to the one encoding supported by all servers fix the warning

It seems that Neovim added support for UTF-8 and UTF-32 quite recently (last week) https://github.com/neovim/neovim/pull/31209 which means that you must be running nightly Neovim. I think this is the reason that Ruff will select UTF-8 because the client now supports it:
https://github.com/astral-sh/ruff/blob/f8c20258aec5148029da904fe1ea91c1c8f1be50/crates/ruff_server/src/server.rs#L271-L283

@Shinzu Can you try running the latest nightly version of Neovim? I don't see any warnings on the latest master branch. In the buffer, Ruff is using UTF-8 and Pyright is using UTF-16.

The function has been deprecated where the warning is being raised (https://github.com/neovim/neovim/blob/01026ba47ba8a656bb5cd09afbb25b4b33c0b752/runtime/lua/vim/lsp/util.lua#L1889-L1920) and the offset_encoding parameter is now a required parameter to be passed in to various LSP functions (https://github.com/neovim/neovim/blob/01026ba47ba8a656bb5cd09afbb25b4b33c0b752/runtime/lua/vim/lsp/util.lua#L1876-L1882).

Thank you both for your answers.
Yes i'm running nightly. I will just wait. :)

I'll close this issue because I understand that this is an issue with neovim. Let me know if there's something that's left unanswered or if there's something we could do on our side.

@MichaReiser For those one who finds this issue, this is how you can configure the offset_encoding client capabilities:
lspconfig["ruff"].setup {
  init_options = {
    settings = {
      ...,
    }
  }
  capabilities = {
    general = {
      -- positionEncodings = { "utf-8", "utf-16", "utf-32" }  <--- this is the default
      positionEncodings = { "utf-16" }
    },
  }
}

in order to set offset_encoding to be utf-16 only (pyright uses utf-16 by default). This is per the LSP 3.17 specification https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocuments

The client announces it’s supported encoding via the client capability general.positionEncodings. The value is an array of position encodings the client supports, with decreasing preference (e.g. the encoding at index 0 is the most preferred one)

Note: with the following way (conventional ways to set capabilities.offsetEncoding prior to LSP 3.17 is not a standard) will NOT work:
require"lspconfig".ruff.setup {
  init_options = {
    settings = {
      fixAll = true,
      ...
    },
  },
  capabilities = {
    offsetEncoding = 'utf-16',
  }
}

and ruff will crash: 'ruff failed\n  Cause: invalid type: string "utf-16", expected a sequence'.

I wonder if this might be a bug because this capabilities.offsetEncoding is read (expected a sequence, not a str) though this does not seem to be a standard LSP spec.

I don't think this is something that we can control on our side as the types are defined in an external crate, specifically in lsp-types: https://github.com/gluon-lang/lsp-types/blob/be7336e92a6ad23f214df19bcdceab17f39531a9/src/lib.rs#L1507-L1512 which specifies that it's an unofficial way to support UTF-8 encodings in clangd. There's a tracking issue (https://github.com/clangd/clangd/issues/1746) to add support for the new field in clangd.


Remove Encode & Help Activities and menu code

I've updated zxing-android/update.rb to automate most of the changes that I made.
In the notes section of UPDATE-ZXING.md you ask what to do with the assets, specifically you ask Completely remove the help section? I've decided to just delete all of it which might not be what you want...
I've tested my changes on Android devices running the following versions: 2.3.3, 4.0.4, 4.1.2, 4.2.2, 4.3 & 5.0.1
PS. not sure if you want the EncodeActivity & HelpActivity removed but thought I'd share my changes anyway.

Thanks.
EncodeActivity & HelpActivity should be removed. If someone finds a need for EncodeActivity, it can form a separate library.


doc: fix doxygen handling of  attribute(x)

The predefined macro list for doxygen processing had a typo error
causing attribute(x) to not be handled correctly.
kernel.h was recently updated to include use of attribute((sentinel))
and doxygen wasn't happy about processing the API doc comments for the
affected function.
Added a couple of other macros used in Zephyr here too.
Signed-off-by: David B. Kinder<EMAIL_ADDRESS>

recheck


webpack.optimize.UglifyJsPlugin failed

project url: https://github.com/synchronizingtheworld/testUglifyJsPlugin
error log:
ERROR in ./~/css-loader?sourceMap!./~/autoprefixer-loader!./css/mui.css
Module build failed:
@ ./css/mui.css 4:14-131
ERROR in ./css/mui.css
Module build failed: ModuleBuildError: Module build failed:
at DependenciesBlock.onModuleBuildFailed (/home/www/workspace/testUglifyJsPlugin/node_modules/webpack/node_modules/webpack-core/lib/NormalModuleMixin.js:315:19)
at nextLoader (/home/www/workspace/testUglifyJsPlugin/node_modules/webpack/node_modules/webpack-core/lib/NormalModuleMixin.js:270:31)
at /home/www/workspace/testUglifyJsPlugin/node_modules/webpack/node_modules/webpack-core/lib/NormalModuleMixin.js:292:15
at context.callback (/home/www/workspace/testUglifyJsPlugin/node_modules/webpack/node_modules/webpack-core/lib/NormalModuleMixin.js:148:14)
at Object. (/home/www/workspace/testUglifyJsPlugin/node_modules/css-loader/lib/loader.js:32:18)
at /home/www/workspace/testUglifyJsPlugin/node_modules/css-loader/lib/processCss.js:211:3
at runMicrotasksCallback (node.js:327:7)
at nextTickCallbackWith0Args (node.js:420:9)
at process._tickCallback (node.js:349:13)
Child extract-text-webpack-plugin:
+ 1 hidden modules
ERROR in ./~/css-loader?sourceMap!./~/autoprefixer-loader!./css/mui.css
Module build failed:

It has something to do with autoprefixer-loader. Note that it has been deprecated and you should use a postcss plugin instead. Doing that change might even fix the issue.
Feel free to re-open at Stack Overflow as that works better for support.


Denorm version into a string-sortable field

It was easier this way than using some sorting method that can do version numbers, and it seems fine for this purpose.
Fixes #111

Thanks @exonian and @ghickman!
This has now been deployed!

:tada: Thanks @meshy!


use older version of dynamodb docker image

our CI tests have started failing and it might be due to AWS releasing v2.0 of this docker image a couple of weeks ago.
relates to #59

logged #61


Check Team Project 2 Submission

We work to complete the second Team Assignment, from the link:
https://github.com/jce-il/se-class-materials/blob/master/docs/team/proj2-inception.md
Due to Sunday Murch 25th.
Tasks Distribution:

All - Every one need to add at least two rows to the Risk Managment Table in the Inception wiki page.
David - Readme and Inception.
Alex - Add info in the Readme file.
Ofek - Draw an Architecture diagram, section 8 under the Planing Page.
Dor - Team page in the wiki.
Or - Inception page in the wiki, all the section except 3 and 8.

great! done.


CommonJS modules

Here's my attempt to rewrite code in CommonJS modules. I've been using your waypoints a long time ago, and I'm happy to contribute.
This PR should solve issue #458. I didn't put files in lib/* because I don't like store code twice in repository. They can be easily added later.

+1 Is this going to be pulled yet? @imakewebthings

+1, totally would save me time

On first reading this looks good @summerisgone. Thank you. I'm currently in the middle of caring for a newborn so my time here comes in sporadic, short chunks. I'll try my best to use those chunks to test and merge this over the next few days.

@imakewebthings my congrats for your baby! Stay happy and healthy! I'm ready to discuss any solution, I've tried to keep compatibility with previous builds as much as possible.

@imakewebthings my congratulations! Tell me if I broke something :)

@summerisgone The files you added to lib, the test builds, did you edit them by hand after generating via npm run build? I get some mostly minor differences when I build locally and want to make sure I'm not missing something.

@imakewebthings as I said, I excluded lib/* files from commit, to show only code difference for convenience. Added them now.

@summerisgone Here's the plan. I've merged this PR into a branch, 5.0. I very much like this PR, and it makes it painfully obvious to me that a couple things should change in concert with this CommonJS changeset. The key ones:

No more separate shortcut files. Include it all into the main file, as you've done here. The downside of larger file size for things that not everyone uses is outweighed by the ease of use that comes with one simple file/require. This also leaves the door open for a custom build process in the future for the extremely bit-conscious users.
No more jQuery/Zepto deps. That means in the shorcuts, and those two adapters can die. The extensions can still live on, but I believe it would be best to package it as a method one can call to decorate jQuery.fn. Like so:

Waypoint.extendJquery(jQuery)
jQuery('.blah').waypoint(...)

I intend to do that work on top of your changes in the 5.0 branch. Simultaneously, there are some bug fixes and such that I would like to release as 4.x following master. Those changes will be folded into 5.0 through rebasing as I go along.

@imakewebthings thank you for submission, I'm very glad again to contribute :) I have some questions about your plan:

I didn't get, do you want to make all-in-one build or leave separate files? As third opinion, you can build two versions like full and minimal. I leaved shortcuts builds as is, and they depends on global.Waypoint so they can be just added on the page.

How do you plan to get rid from jQuery/Zepto deps, if some [useful] shortcuts depends on them?
I can try to rewrite code to var jquery = require('jquery') rather than using window.jQuery. But then the module (in CommonJS context) would depend on jquery, which lays to some overweight (so I leaved them as optional dependencies and used global context for variables).

@summerisgone The package.json main would point to an all-in-one build. If somebody were worried about file size and wanted to only include a subset of everything, there's nothing stoppng them from using require('waypoints/src/whatever.js') and building that into their final bundle. The all-in-one mostly makes things 100x easier to explain. I'm also not a fan of leaking Waypoint into the global namespace if a user is going the CommonJS route. Having the separate files would necessitate that or some other means of extending the Waypoint namespace.
For the jQuery/Zepto shortcuts, I intend to update those shortcuts to work without jQuery/Zepto.

Awesome plan @imakewebthings  I hope it will become reality soon.

I agree so much. Waypoints is awesome, but using it with Webpack etc. can be a pain in the first point. CommonJS would solve it!

If you need assistance from us @ webpack ensuring this can be bundled properly let me know. We are willing to help.

Thank you for the offer @TheLarkInn, but the following official workaround is working pretty well for me. :)
However, I would strongly vote for switching to a wider supported module in the next future. Maybe even consider es-modules via babel to supply all common module formats out there.
Here is the workaround in case somebody else is looking for a fix:
plugins: [
  new webpack.ProvidePlugin({
    $: 'jquery',
    jQuery: 'jquery',
    'window.jQuery': 'jquery'
  })
]

@axe312ger a PR on the readme would be really beneficial.

@summerisgone Here's the plan. I've merged this PR into a branch, 5.0. I very much like this PR, and it makes it painfully obvious to me that a couple things should change in concert with this CommonJS changeset. The key ones:

No more separate shortcut files. Include it all into the main file, as you've done here. The downside of larger file size for things that not everyone uses is outweighed by the ease of use that comes with one simple file/require. This also leaves the door open for a custom build process in the future for the extremely bit-conscious users.
No more jQuery/Zepto deps. That means in the shorcuts, and those two adapters can die. The extensions can still live on, but I believe it would be best to package it as a method one can call to decorate jQuery.fn. Like so:

Waypoint.extendJquery(jQuery)
jQuery('.blah').waypoint(...)

I intend to do that work on top of your changes in the 5.0 branch. Simultaneously, there are some bug fixes and such that I would like to release as 4.x following master. Those changes will be folded into 5.0 through rebasing as I go along.

Does that mean, that by default Waypoint won't use jQuery/Zepto or is it just the shortcuts?


Expanded minimum RSA Keylength to 3072

German Federal Office for Information Security requests in its technical guideline BSI TR-02102-1 RSA Keylength not shorter than 3000bits starting 2024, in the year 2023 3000bits as a recommendation. Gitea should request longer RSA Keys by default in favor of security and drop old clients which do not support longer keys.
https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Publikationen/TechnischeRichtlinien/TR02102/BSI-TR-02102.pdf?__blob=publicationFile&v=9 - Page 19, Table 1.2

CI fails, the test code also needs to be updated accordingly.
Would you like to fix them or would you like some maintainers to edit this PR to help?

Searched again and found way more occurences of 2048 bit RSA.
I do need help with: https://github.com/go-gitea/gitea/blob/a4cfeaec9cf6d50a64b98fa01acaa09f2a3146d0/models/asymkey/ssh_key_test.go#L31 and potential other RSA Keys in that file, as I do not know, how the corresponding private key is handeld.

CI still fails

Unit test need a refactor.

No worries,

Honestly dont know what to do. Please help.

Please run make test in the console.

🚀

CI passes. And IMO this is not "breaking", all uploaded/generated keys are not affected, so removed the "breaking" label.
Feel free to add the breaking label back if it is really breaking (with detailed breaking description and what users should handle the breaking)

Thank both of you!

I added a missing pr/breaking label to this.