[BUG] Crop image origin !

Hello, i have a problem on ios ! When with an iphone you save an image cropped in your gallery, photo_manager keep the original file !
Did you have any solution ?
Thx for your time 😇

I don't know your mean.

Ok sorry i have a video :
https://youtu.be/-XETyR8qIa0

Currently, photo_manager sorting only supports creation time, not modification time.
Editing images such as crops of iOS photos is done on the original image, it will only affect the original asset, not create a new asset.

https://youtu.be/nhC-Wr_8chU

After you modify the picture, you need to call getThumb / file / originFile and other methods to get the picture information again
If it is still invalid, you may need to refresh the asset information. For example, if the asset is located at index 1, then use path.getAssetListRange (1,2) to retrieve the asset and replace it with the original location.
The easiest way is PhotoManager.getAssetPathList().
As in my youtube video, the thumb will refresh.
By the way, the example code come from photo library

I have the same problem if i reload my application
// CHECK PERMISSION AND GET PHOTOS
  void _checkPermission(bool _openSetting) async {
    try{
      var result = await PhotoManager.requestPermission();
      if (result) {
        int count = 1000;
        List<AssetEntity> imageList = [];
        List<AssetPathEntity> list = await PhotoManager.getAssetPathList(type: RequestType.image, onlyAll: true);

        if (list != null)
          for (AssetPathEntity path in list)
            imageList.addAll(await path.getAssetListRange(start: 0, end: path.assetCount));

        if (imageList.isNotEmpty) {
          List<AssetEntity> imageListNew = imageList.length > count ? imageList.sublist(0, count) : imageList;
          List<AssetEntity> imageListPush = [];

          for (AssetEntity assetEntity in imageListNew)
            imageListPush.add(assetEntity);

          setState(() => data = imageListPush);
        }
      } else if (_openSetting) {
        AppSettings.openAppSettings();
      } else {
        Navigator.of(context).pop();
      }
    } catch (e, s) {
      if (context != null) {
        PCrashlytics.reccordError(context, e, s);
        Navigator.of(context).pop();
      }
    }
  }

I use this code for get images !
I don't know why i have the original image and not the cropped 🙁

Maybe you need update new version?

0.5.1 working fine 🔥
Thx for your time 😇

Still not working. just thumDataWithSize working.
// current album becomes below code
     _albums = await PhotoManager.getAssetPathList(type: RequestType.image);
        if (_albums.isNotEmpty) {
          final isAllAlbum = _albums.firstWhere((element) => element.isAll,
              orElse: () => _albums.first);
          setState(() {
            _currentAlbum = isAllAlbum;
          });
        }

  Future<void> _fetchMedia(AssetPathEntity currentAlbum) async {
    if (_assets.isEmpty) {
      final ret = await currentAlbum.getAssetListRange(start: 0, end: 5000);

      final List<AssetEntity> assets = [];
      for (final asset in ret) {
        if (asset.type == AssetType.image) assets.add(asset);
      }

      setState(() {
        _assets = assets;
      });
    }
  }


Portal seems to have changed  - no longer accurate-- Navigate to Global Settings > Account Settings and click Define under SSO Authentication.

[Enter feedback here]
This is no longer accurate- specifically  Navigate to Global Settings > Account Settings and click Define under SSO Authentication.

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

ID: 193ac564-5141-3964-008c-1777ecfdb3e7
Version Independent ID: 55473104-deb0-bada-525b-b74f69cdf061
Content: Tutorial: Microsoft Entra SSO integration with Check Point Infinity Portal - Microsoft Entra ID
Content Source: docs/identity/saas-apps/checkpoint-infinity-portal-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @jeevansd
Microsoft Alias: jeedes

@thomasjsweet
Thanks for your feedback! We will investigate and update as appropriate.

@thomasjsweet
Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can take a look at it accordingly.
@jeevansd
Can you please check and add your comments on this doc update request as applicable.

@thomasjsweet, we're working on the document changes to the latest UI and it will be going to update soon.
#please-close


Disabling & Enabling IEBehaviors may leave kinematics off

Disabling and Enabling InteractionBehaviors may result in kinematics being left off.
MobileUXTests has an earlier commit to ActivityManager.cs of code from Adrian that fixed this.  But overwrote this when merging latest UnityModules from upstream.  Poke me if that would be helpful.

  If this issue is still present we should get a specific repro case so we can add it to the tests.


Project Endpoints List is not showing correctly

The endpoint APIs (Already Registered APIs) is not clearly displayed
see this image to know the issue:
https://dl.dropboxusercontent.com/u/63101982/RestBug.png
Expected outcome
the list should be opened and I should see all the method names
the vertical scrolling is working fine, but the horizontal scrolling is not, and now I can't see the methods name
Actual outcome
When you have list of predefined APIs added and you open that list, it will not be displayed correctly
Versions
App: <IP_ADDRESS>-stable
Chrome: 49.0.2623.112
Platform: Windows (8.1)
Steps to reproduce

Add Project Name
Add any numbers of APIs
the list will not be displayed correctly.

Hi,
Thank you for issue report.
It was fixed in latest update.


Jenkins: shortcut keys to troubleshoot

When there's trouble, it would be nice to have shortcut keys for:

proposed key
action
URL path

m
Monitoring
/monitoring

t
Controller's threads view
/monitoring?part=threads

l
All Jenkins Logs
/manage/log/all

Another option for threads is /threadDump


How to get label or id of Datachannel.

@#Is your feature request related to a problem? Please describe.
Hi. I am Akioalex. Now I am developing flutter webrtc app using your plugin. Thanks for your awesome project.
I have one issue. I am created datachannel with label and id. But I can not get label or id of datachannel on OnDataChannel method.
RTCDatachannel label or Id variant is private.
Describe the solution you'd like
So Is it possible to make public or add get method?
I will wait for your response. Thanks and regards

Is it in your plan? Now I am using your plugin with local import.
Please let me know your suggestions. Thanks


Current line is changed when creating a new vertical split

I've been using focus.nvim for hell of a long time. I noticed it's changing current line when using vsp. Only recently I figured that it's this plugin causing it. here is a video.
https://github.com/user-attachments/assets/afad5915-12e1-4005-bf4d-1c447af6ab17

See the Note at the end the Configuration section: of https://github.com/nvim-focus/focus.nvim?tab=readme-ov-file#configuration


feat!: disallow dunders in study prefixes

Description
Based off a conversation we had about this - figured I'd whip this up.
This allows us to use double underscores (dunders) as separator tokens in tables without fear of collisions.

Checklist

[x] Consider if documentation (like in docs/) needs to be updated
[x] Consider if tests should be added
[x] Run pylint if you're making changes beyond adding studies

Per a convo with Matt, he's got a PR that will obsolete this, so I'm closing to avoid conflicts.


npm run test (ng test) "Breakpoint set but not yet bound" Angular CLI

I can't debug my tests following the instructions on Angular CLI.
When I run my "ng test" launcher, my breakpoints say "Breakpoint set but not yet bound".

Debugging works with my chrome browser if I initiate my breakpoint on my Chrome dev tools.
ng serve debugging works fine.

Context:

My angular cli version is 8.3.8
Debugger for Chrome is 4.12.1
Chrome is installed in its default location, on C:\Program Files (x86)\Google\Chrome\Application

Does anyone else have this issue?

I followed through the issues #175 and #585. I have had no luck...
My .scripts point to the correct files. If I click the link that comes from .scripts , VS Code will opens up the instance of that file, "c:\Users.......{workspace}\src\app.component.spec.ts" and the breakpoint works there. So it's like pointing to the right place, but the break points don't hit when I use it from ng test.
Some help would be very much appreciated.

Same here - breakpoints are set okay (full red dots) , but as soon as I start the debug run, they become unbound (white/hollow) and do not get hit. Tried variations (as proposed) of the debug configuration, but without success.

I had the same problem.

I have the same problem. Tried bunch of different solutions without any luck.

@chrisdias any luck making this work?

Same problem.

It might be related to the Path mapping to the launch file being missing. Just add this line along with the instructions found in the Angular CLI for the ng test. I also opened a issue here which explain it a little more: Unit Test Issue
"pathMapping": {
"/karma_webpack": "${workspaceFolder}"
}

@tasdevani21
I tried, but it doesn't work.

@tasdevani21 idea led me to the right solution. Add this path mapping to your launch.json:
"pathMapping": {
  "/_karma_webpack_": "${workspaceFolder}"
}

@tasdevani21 brilliant.  Thanks!

@tasdevani21  i added the snippet to launch.json but still code doesn't stop at breakpoint. it says Breakpoint set but not yet bound

This answer here seems to be working fine with latest updates.
Your launch.json should be as follows
{
   "type": "chrome",
   "request": "launch",
   "name": "Launch Chrome",
   "url": "http://localhost:4200",
   "webRoot": "${workspaceFolder}",
   "sourceMaps": true,
   "sourceMapPathOverrides": {
       "/./*": "${webRoot}/*",
       "/src/*": "${webRoot}/*",
       "/*": "*",
       "/./~/*": "${webRoot}/node_modules/*"
    }
}


task(global): Improve State Management on Emoji Selector and Render Messages

1. Find better ways to use state and re render less components possible in the app
2. This ticket is just for emoji selector and render messages for now

We think #699 addresses this . . . . let me know if not @lgmarchi and we can re-open?


fix hardcoded function in lazyframe.with_column

Thanks

@nevi-me calculation expression only takes column as input, is that expected? do you plan to change it to also support constants like number and strings?


Export to CoL with serious problems

I am very curious to see if the upgrade to the export system affected in any way my ability to have my database straight.
But it seems that the upgrade caused same major problem.
I'm trying for half an hour now to export something -- but nothing happens, as opposed to 3-4 minutes in the recent past.

Duplicate of #1715


1.12 can't craft fluid when storage contains some already

there's no 'Display Mode' button in the Fluid Grid, so it's impossible to see the crafting item in the grid when there's already some of that fluid in the storage.
Version (make sure you are on the latest version before reporting):
FTB Academy

Minecraft: 1.12.2
Forge: <IP_ADDRESS>46
Refined Storage: 1.6.15

Does this issue occur on a server? yes

You can ctrl + shift click to craft even when there is already an item/fluid of that type in the system.

The issue has been remedied in the 1.14 version of the mod. The feature may or more likely may not be ported over to the older 1.12 version.

You can ctrl + shift click to craft even when there is already an item/fluid of that type in the system.
doh! thanks for that.


Update licenses

The current MIT license only covers the former maintainer and only gives 2019 as copyright year.
The current Apache license uses Copyright 2018 Yoshua Wuyts.

That's a copy-pasta. And yes please. Let's change both to "Paperclip Contributors". Can't believe I had his name for so long.

This is fixed by #470, so it can be closed 💯


Support for true plugin architecture

The idea to have simnet as one of potentially many plugins (and users being able to contribute plugins):
(a) we need a config entry that lists folders where plugins can be found;
(b) each plugin should provide a package-level function like get_plugin_instance() which returns an instance of an object with several standard methods, like:

parse_args()
marshal()

and others.
(Design to be further discussed and developed.)

@thehunmonkgroup: with ddb5e97, there's an initial implementation of a simple plugin framework with simnet being refactored to fit that framework. Currently working for normal command line invocations, AFAICT.
TODO:

[ ] Get this working for config-file-defined profiles
[ ] figure out how to organize plugin tests so they (a) are provided by the plugin package; (b) become integral part of the test suite;
[ ] make sure all examples are working properly;
[ ] experiment with setup.py for the pyltc core part AND any plugins; fix any related issues;
[ ] clean up (esp. FIXMEs and TODOs).

@thehunmonkgroup: Chad, please check out the 20-support-plugin-architecture feature branch and test ("real world") that it works fine for you as a drop-in replacement for the master branch version. It should, after commit 3aed78e. If not, please communicate any issues here in this thread (or via Skype if you prefer). Thanks a bunch.


WIP Update resources in Hub Metrics collection & Fix e2e

Toggling hubselfmanagement multiple times creates addon-observability namespace in hub cluster intermittently. This PR ensure we skip any reconcile in MCO touching local-cluster object
Update hub metrics collections resources when modified
FIx e2e tests

/retest

/retest

continued here -> https://github.com/stolostron/multicluster-observability-operator/pull/1371


Spinner in config should increment by 1 instead of 0.01

Please describe the feature that you want to propose
In most cases, the values are integer and not decimals

should be doable once there is new uniforms-patternfly build with this included - https://github.com/kiegroup/kie-tools/pull/1579


Without grouped option, its hard to see what files are what

End up with "8 files ..." etc., and are unsure which file is related to which card.
This mostly occurs with phylotyper runs. We could either:

Write a function to merge the results for phylotyper so we don't need to have non-grouped results.
Modify reactapp to show which files are which card.

The second option would be a quick fix, so we'll go with that for now. Though both could be done in the future.

Fixed in https://github.com/superphy/reactapp/pull/75


fix: bodyScrollLock not working on safari

Adapt the fix from Vueuse

@zernonia
I'm not 100% sure, but this commit seems to break the usage of the Apple Pencil within dialogs, popovers, alert dialogs, etc.
I'm relatively new to Radix-Vue (using it through Shadcn-Vue).
For now, I've reverted my Radix-Vue dependency to the version before this commit.
Could this issue be investigated? My current user base primarily consists of iPad users with Apple Pencil (I know this is a very specific case), but others might encounter similar issues.


Ensure consistency between docs and Jupyter Notebook demos

The MLTE documentation uses some examples that may be outdated in comparison to code in the Jupyter Notebook demos, and in some cases may be using parts of one demo or the other, which can be confusing. Review and ensure it is consistent.

Academic Lit papers to include:

[Habibullah 2022]
[Habibullah 2023]
[Li 2023]
[Nakamichi 2020]
[Pons 2019]

And grey-lit

[Kästner 2022]

Real issue here was iris vs oxford dataset in the notebooks and the sample data store. Should be all in terms of oxford. Not sure if there are other refs to iris in the docs.

@krmaffey offered to review the external facing documents.

External-facing documentation has been reviewed, and I submitted a pull request (#503) with a few changes where it was referencing the wrong dataset (Iris vs. Oxford) and using outdated code. Let me know if you want me to look at the internal docs next, I can create a different issue for that if we want!

Properly addressed by #503


Add more creative templates

Is your feature request related to a problem? Please describe.
It will be good to have more readme templates to choose from
Describe the solution you'd like
More templates are needed

I would like to work in this.
Is it about writing additional templates in https://github.com/rishavanand/github-profilinator/blob/master/src/config/demo.ts or implementing a select box to choose between different templates?

Hey @silltho,
It's about both, adding a new template and also adding a drop-down selection for it. But I've already started working on this one. Could you look for another issue?

@silltho I've simplified the process of adding new templates to Profilinator and also added a new template currently deployed on https://dev-profilinator.rishav.dev/. If you wish, I can assign you this issue for adding another template. I've also added steps for adding a new template in CONTRIBUTING.md file.


Fix linter check for local deployment.

This change is

Fixes #329

Jenkins job mixer/presubmit passed

Jenkins job manager/mixer-pr passed


RFC/Spec: wrangler init with flag --from-dash

Why should we do wrangler init --from-dash?
Furthering the discussion from #1346, we want to provide a bridge from the dashboard where previously it was easy to get up and going with a new Worker. Now we want to encourage the user to an improved developer experience with the CLI and their local developer ecosystem. Since the goal is for the user to develop locally we want to be sure this is a one-time initialization process and not a way to develop Workers simultaneously in the dashboard and local machine.
Solution
The idea of working off the wrangler pull discussion is to leverage work already done with wrangler init creating a flag that can be used --from-dash (that can be bikeshedded). The flag would have an input that would allow targeting a Worker that would utilize the source code for the initialization of the project, eventually including the Configurations of the Worker to be generated as well; I think this should be done in phases, getting the Worker source code project initialization first. The idea is to focus on the "migration" from the dashboard to the local development ecosystem leveraging the DX of Wrangler, meaning there will be safeguards necessary to prevent "synchronizing" behaviors from dash to and from local. Part of the benefit of wrangler init being utilized for this bridging is two-fold

We can increase its safeguards around not initializing into existing projects, preventing "sync" or source control-like behaviors.
The initialization features currently built-in can be augmented and used to encourage things like TypeScript, GitHub repo creation, etc... furthering the improvement of DX and local development best practices.

Notes:
Additional discussion: https://github.com/cloudflare/wrangler2/issues/1346#issuecomment-1197368012

This implementation should be agnostic from any source control & storage.
Encourage augmenting projects, i.e. TypeScript, and source storage (we currently provide GitHub repo creation).
The flag should only be done in empty projects.

Concerns:
As previously mentioned avoid any quasi-source control or quasi-source storage patterns or behaviors. This is another primary reason for moving away from wrangler pull and making sure safeguards are in place to make it a one-off usage. Tangentially related corrupting existing projects could be a problem which is an additional reason to make this a one-off command for initialization of a project locally from the dashboard.
Alternatives

wrangler pull was suggested #1346 now my main concern with this was source control & storage confusion,
wrangler pull -> git pull and the dashboard would seem like where the source is "stored" much like GitHub. We would also not have all the benefits of leveraging wrangler init features directly.
A dashboard download button was another suggestion that was considered.

Phases of work:

[ ] The Worker source code project initialization
[ ] The configuration auto-generation (i.e. wrangler.toml )

Thanks for the spec @JacobMGEvans. I'm in favor of your proposal.
If we are going to split the implementation into two steps, then let's ensure that we don't advertise the feature until it's ready, or clearly mark it as experimental. Thank you

Since the goal is for the user to develop locally we want to be sure this is a one-time initialization process and not a way to develop Workers simultaneously in the dashboard and local machine.

👍🏻
I think this looks good! +1

@JacobMGEvans could you please add one more deliverable to this project: let's make this Wrangler feature easily discoverable by modifying the Dash UI to promote this feature when visiting projects that have been deployed only via the Dash.
(We'll likely need to identify these projects first, or maybe we can show the info/prompt only in the dash editor? We can work with our design folks to determine the best way to surface this.)
Thank you

@IgorMinar @JacobMGEvans i chatted with design about surfacing this feature as well as the UX/workflow implications for using --from-dash -- they will review and follow up with any initial questions 👍


POP OAuth support updates

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

File
Status
Preview URL
Details

docs/legacy-protocols/how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Fixes [N/A N/A] attribute tag display issue

Direction and Significance N/A attribute displays on Evidence summaries now show a text 'Not applicable'. These attribute displays now use an empty-value component that can help standardize the display N/A, Unspecified, Missing messages throughout the app. I also similarly updated the rest of the Evidence attributes w/ potentially empty or N/A values and applied the same updates to Assertions and Molecular Profile summary templates.

I also moved over the prettier.json config settings from my forms2 branch. VSCode prettier formatting may not  been working due to an empty config.


[AutoPR sql/resource-manager] [DO NOT MERGE]update swaggers for azure elastic pool operation

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/2520

Codecov Report

Merging #2052 into restapi_auto_sql/resource-manager will increase coverage by 3.21%.
The diff coverage is 0%.

@@                          Coverage Diff                          @@
##           restapi_auto_sql/resource-manager    #2052      +/-   ##
=====================================================================
+ Coverage                              49.64%   52.86%   +3.21%
=====================================================================
  Files                                   4818     4705     -113
  Lines                                 134686   116690   -17996
=====================================================================
- Hits                                   66871    61689    -5182
+ Misses                                 67815    55001   -12814

Impacted Files
Coverage Δ

...mt-sql/azure/mgmt/sql/models/database_operation.py
25% <0%> (-4.42%)
:arrow_down:

...efabric/azure/servicefabric/models/health_event.py
41.66% <0%> (-11.67%)
:arrow_down:

...servicefabric/models/resolved_service_partition.py
50% <0%> (-11.54%)
:arrow_down:

...c/azure/servicefabric/models/health_information.py
38.46% <0%> (-11.54%)
:arrow_down:

...dis/azure/mgmt/redis/models/redis_firewall_rule.py
50% <0%> (-11.54%)
:arrow_down:

...azure/servicefabric/models/property_description.py
55.55% <0%> (-11.12%)
:arrow_down:

...efabric/models/application_capacity_description.py
55.55% <0%> (-11.12%)
:arrow_down:

...ic/models/create_compose_deployment_description.py
55.55% <0%> (-11.12%)
:arrow_down:

...fabric/azure/servicefabric/models/property_info.py
55.55% <0%> (-11.12%)
:arrow_down:

...rvicefabric/models/put_property_batch_operation.py
55.55% <0%> (-11.12%)
:arrow_down:

... and 692 more

Continue to review full report at Codecov.

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


[FLOC-3926] Remove duplicate documentation.

The AWS and the Rackspace drivers had duplicate documentation with the actual docs at http://doc-dev.clusterhq.com/. They also had links to that documentation. Removing the duplicate in favor of the reference to the official documentation.

A good idea.
Can you please add dict as the type for provider_config, and describe the parameter as a dictionary parsed from the (platform) section of the acceptance testing configuration file.

Thanks for the comment, fixed. I'm going to wait til I get a green tests for lint before I submit.

Lint passed and this only changes docstrings. I'm going to submit as is.


[HUDI-1049] 0.5.3 Patch - In inline compaction mode, previously failed compactions needs to be retried before new compactions

This is a patch in 0.5.3 to unblock user noticing this issue - [HUDI-1049] In inline compaction mode, previously failed compactions needs to be retried before new compactions

I was running this bug fix on two large tables updated every 10 minutes for 3 days. I don't see any lingering  compactions that are INFLIGHT mode. also ran this code change on old table that already had several compactions stuck INFLIGHT, verified that lingering INFLIGHT compaction were restarted successfully

@zuyanton This is great.. Thanks for testing it out.. We will work on getting this landed onto master first..

any updates ?

@zuyanton .I am going to rebase this onto master and then land for 0.6.0.

Closing this in favor of #1857


Can't useFieldset on zod optional object

When creating a zod schema containing an optional object, I am unable to use useFieldset on it because the field config for it is possibly undefined. I would expect the field config to always be there, and only have the validation handle the optional part of it.
Example schema:
const schema = z
  .object({
    email: z
      .string()
      .min(1, "Email is required")
      .email("Please enter a valid email"),
    address: z
      .object({
        street1: z.string().min(1, "Street 1 is required"),
        street2: z.string().min(1).optional(),
        city: z.string().min(1, "City is required"),
        state: z.string().min(1, "State is required"),
        postalCode: z.string().min(1).max(5),
      })
      .optional(),
  })

address would come back as type FieldConfig<{street1: string, street2?: string, ...}> | undefined, meaning I couldn't pass it to useFieldset.
Example code sandbox: https://codesandbox.io/p/sandbox/peaceful-mclean-g1mygf?file=%2Fapp%2Froutes%2Findex.tsx%3A8%2C1-28%2C5
See routes/index.tsx:67

Thanks for the bug report @baker-travis! It should be fixed now on v0.6.3.


Model Compiler Creates 2 DPU Subgraphs

Framework: PyTorch
Model: ResNet18
DPU: DPUCZDX8G
The model compiler creates 2 DPU subgraphs. The split happens after the convolutional layers with AdaptiveAvgPool2D. However this operation is listed as supported in the vitis ai user guide:

In attempts to debug I replaced the adaptive average pooling with a standard average pooling. The issue still persisted.
based on: https://github.com/Xilinx/Vitis-AI/issues/427 I replaced the flatten operation with Torch's reshape operation. The issue remains.
Any ideas?

Adaptive average pooling from my understanding infers the kernel size. Its downsampling a (1,7,11,512) shaped feature vector to a (1,1,1,512) feature vector. To try the normal average pooling I used a kernel size of (7,11). So I'm guessing this is my issue.


Replace incorrect figure in documentation

Update figure with correct quarterback numbers in readme file.

Fixed here: d51485dcac62653338959c7f030706765588ab4e


Tweaks to logging in Copy-CodeQL-Workitems-to-Github pipeline

Fixes #minor
Description
Tweaks to log output in CopyAdoWorkitemsToGithubIssues.ps1

Pull Request Test Coverage Report for Build 325066

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+79.08%) to 79.076%

Totals

Change from base Build 325049:
79.08%

Covered Lines:
25581

Relevant Lines:
32350

💛  - Coveralls


Additional characters

Can't type "А" or "а" characters in MPV chat (first letter of cyrillic alphabet). Maybe problem is here:
https://github.com/Syncplay/syncplay/blob/406e9a4af50f30f2291b2887ec52988a3f89bee5/resources/syncplayintf.lua#L63

Thanks for reporting this omission. Does replacing your /resources/syncplayintf.lua file with https://raw.githubusercontent.com/Syncplay/syncplay/master/resources/syncplayintf.lua succeed in  allowing the input of the first letter of the Cyrillic alphabet through mpv? Are there any other characters that need adding?

succeed in allowing the input of the first letter of the Cyrillic alphabet through mpv?

Yes.

Are there any other characters that need adding?

Now i can input every cyrillic character.

This issue should now be resolved by the Syncplay 1.5.2 Official Release so I'll close the issue for now. If the issue persists then please let me know.


code and dataset release

Hi, thanks for your excellent work, I wonder if you would release the code and the dataset you use?

Sorry but we are not able to release the dataset for RemoteCLIP pretraining.
Our implementation is based on OpenCLIP and ITRA (which is derived from OpenCLIP). If you plan to re-implement RemoteCLIP, I feel OpenCLIP is a good codebase to get started.


MultiVI issue with PyTorch

The multiVi fails at the mvi.train in batch_correct_multivi.py.
Traceback (most recent call last):
  File "[path]/panpipes/panpipes/python_scripts/batch_correct_multivi.py", line 256, in <module>
    mvi.train( **multivi_training_args, **multivi_training_plan)
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/scvi/model/_multivi.py", line 351, in train
    return runner()
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/scvi/train/_trainrunner.py", line 98, in __call__
    self.trainer.fit(self.training_plan, self.data_splitter)
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/scvi/train/_trainer.py", line 219, in fit
    super().fit(*args, **kwargs)
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/lightning/pytorch/trainer/trainer.py", line 544, in fit
    call._call_and_handle_interrupt(
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/lightning/pytorch/trainer/call.py", line 44, in _call_and_handle_interrupt
    return trainer_fn(*args, **kwargs)
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/lightning/pytorch/trainer/trainer.py", line 580, in _fit_impl
    self._run(model, ckpt_path=ckpt_path)
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/lightning/pytorch/trainer/trainer.py", line 989, in _run
    results = self._run_stage()
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/lightning/pytorch/trainer/trainer.py", line 1035, in _run_stage
    self.fit_loop.run()
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/lightning/pytorch/loops/fit_loop.py", line 202, in run
    self.advance()
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/lightning/pytorch/loops/fit_loop.py", line 359, in advance
    self.epoch_loop.run(self._data_fetcher)
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/lightning/pytorch/loops/training_epoch_loop.py", line 136, in run
    self.advance(data_fetcher)
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/lightning/pytorch/loops/training_epoch_loop.py", line 242, in advance
    batch_output = self.manual_optimization.run(kwargs)
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/lightning/pytorch/loops/optimization/manual.py", line 92, in run
    self.advance(kwargs)
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/lightning/pytorch/loops/optimization/manual.py", line 112, in advance
    training_step_output = call._call_strategy_hook(trainer, "training_step", *kwargs.values())
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/lightning/pytorch/trainer/call.py", line 309, in _call_strategy_hook
    output = fn(*args, **kwargs)
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/lightning/pytorch/strategies/strategy.py", line 382, in training_step
    return self.lightning_module.training_step(*args, **kwargs)
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/scvi/train/_trainingplans.py", line 567, in training_step
    inference_outputs, _, scvi_loss = self.forward(batch, loss_kwargs=self.loss_kwargs)
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/scvi/train/_trainingplans.py", line 278, in forward
    return self.module(*args, **kwargs)
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
    return forward_call(*args, **kwargs)
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/scvi/module/base/_decorators.py", line 32, in auto_transfer_args
    return fn(self, *args, **kwargs)
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/scvi/module/base/_base_module.py", line 203, in forward
    return _generic_forward(
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/scvi/module/base/_base_module.py", line 739, in _generic_forward
    inference_outputs = module.inference(**inference_inputs, **inference_kwargs)
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/scvi/module/base/_decorators.py", line 32, in auto_transfer_args
    return fn(self, *args, **kwargs)
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/scvi/module/_multivae.py", line 600, in inference
    qzm_acc, qzv_acc, z_acc = self.z_encoder_accessibility(
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
    return forward_call(*args, **kwargs)
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/scvi/nn/_base_components.py", line 282, in forward
    dist = Normal(q_m, q_v.sqrt())
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/torch/distributions/normal.py", line 56, in __init__
    super().__init__(batch_shape, validate_args=validate_args)
  File "[path]/panpipes_gpu/lib/python3.10/site-packages/torch/distributions/distribution.py", line 68, in __init__
    raise ValueError(
ValueError: Expected parameter loc (Tensor of shape (128, 12)) of distribution Normal(loc: torch.Size([128, 12]), scale: torch.Size([128, 12])) to satisfy the constraint Real(), but found invalid values:
tensor([[nan, nan, nan,  ..., nan, nan, nan],
        [nan, nan, nan,  ..., nan, nan, nan],
        [nan, nan, nan,  ..., nan, nan, nan],
        ...,
        [nan, nan, nan,  ..., nan, nan, nan],
        [nan, nan, nan,  ..., nan, nan, nan],
        [nan, nan, nan,  ..., nan, nan, nan]], device='cuda:0',
       grad_fn=<AddmmBackward0>)

Similar to this issue in scArches: https://github.com/theislab/scarches/issues/206

Hi Wojiciech, thanks for reporting this issue.
I thought the tensor issue was solved in the latest scvi version (see this PR) and https://github.com/scverse/scvi-tools/issues/2581
but it seems a slightly different version of the same error.
can you post the packages versions? thanks!


{acs} | Updating default values to the description

Fixes https://github.com/Azure/azure-cli/issues/21725
Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

acs


fix: apply only supported attributes from resources decorator in batch

Changes the way BatchDecorator pulls values from ResourcesDecorator if any are set. This limits the values to only ones supported through resource_defaults in batchdeco.
Should unblock #1500 which currently breaks for batch as it introduces a disk= attribute which is not supported for the batch deco, yet gets pulled in by the current implementation.

also relates to #1609


Switch nginx to listen on internal only for direct marathon/chronos.

Removed old nginx location.
Switched from 7777 to jinja var.
Added basic var file for localmesos and as example.

@amitbose327

LGTM


Symbol tab Dark theme visibility

[x] text boxes are while color they should be dark boxes with white text

(currently)

(should be this style)

[x] Symbol Attributes window is white, should match dark theme of regular attributes window

(should be this style)

[x] Add to Map button is white, should match dark theme buttons

(currently)

(should match this style)

Addressed in #206, #207

PR #207 has fixed this issue


feat(composed-schema-restrictions): add new spectral-style rule

PR summary
This commit introduces the new spectral-style
'composed-schema-restrictions' rule, which will verify that oneOf and anyOf compositions comply with the restrictions imposed by the SDK generator.
PR Checklist
General checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)
[ ] Dependencies have been updated as needed
[ ] .secrets.baseline updated as needed?

Checklist for adding a new validation rule:

[x] Added new validation rule definition (packages/ruleset/src/rules/*.js, index.js)
[x] If necessary, added new validation rule implementation (packages/ruleset/src/functions/*.js, updated index.js)
[x] Added new rule to default configuration (packages/ruleset/src/ibm-oas.js)
[x] Added tests for new rule (packages/ruleset/test/*.test.js)
[x] Added docs for new rule (docs/ibm-cloud-rules.md)

@dpopp07 I think I've addressed all your review comments.  Ready for a re-review.

Closing this PR out. Dan will open a new PR when he's ready.


Skip first time experience on Appveyor

@ryanbrandenburg,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

Error parsing appveyor.yml: Invalid setting or section: env (Line: 17, Column: 1)


Add IPv6 support

Currently Maple does not support IPv6 address, please add IPv6 support, which is very useful in CERNET.
目前Maple不支持IPv6地址，请添加对IPv6的支持，这在教育网中很有用。

AFAIK Leaf does not support IPv6 yet, see https://github.com/eycorsican/leaf/issues/13#issuecomment-723417867 . Maple could not implement it without Leaf supporting it first. Besides, neither iLeaf nor aleaf provides an IPv6 address for local VPN interface.
May I know if Leaf itself works in your network environment? If so, please provide more details about your use cases in that network environment. Otherwise, please consider reporting a feature request to Leaf.

See https://github.com/eycorsican/leaf/issues/126

It seems that IPv6 support in Leaf is ready and merged into Maple. @waynon Could you test out the main branch to see if IPv6 works? Unfortunately I have no access to IPv6 network.

I am going to close this issue since IPv6 support is already merged. Please let me know in case any related problems still exist.

IPv6 address is still not supported, both in official release 0.3.0 and my custom build.

Please reopen the issue.

IPv6 address is still not supported, both in official release 0.3.0 and my custom build.

How did you find that IPv6 does not work? Please explain what you have done if possible.

IPv4 config that is working:
[General]
# Log are for debug only
loglevel = error
# Do not remove tun-fd option
tun-fd = 233
dns-server = <IP_ADDRESS>, <IP_ADDRESS>

[Proxy]
VMess = vmess, 107.173.87.xxx, xxx, username=xxxxxxxx

[Proxy Group]
Fallback = VMess, interval=600, timeout=5

[Rule]
FINAL, Fallback

IPv6 config that is not working:
[General]
# Log are for debug only
loglevel = error
# Do not remove tun-fd option
tun-fd = 233
dns-server = <IP_ADDRESS>, <IP_ADDRESS>

[Proxy]
VMess = vmess, 2001:470:1f04:316::2, xxx, username=xxxxxxxx

[Proxy Group]
Fallback = VMess, interval=600, timeout=5

[Rule]
FINAL, Fallback

The only difference is the IP address. It's working in Leaf (proxy mode).
Logs:
[2021-05-18 23:25:32][DEBUG] added udp session <IP_ADDRESS>:58004 -> <IP_ADDRESS>:443 (1)
[2021-05-18 23:25:32][TRACE] pick route failed: no matching rules
[2021-05-18 23:25:32][DEBUG] picked default route [VMess] for <IP_ADDRESS>:58004 -> www.facebook.com:443
[2021-05-18 23:25:32][TRACE] socket bind <IP_ADDRESS>:0
[2021-05-18 23:25:32][DEBUG] dispatch udp <IP_ADDRESS>:58004 -> www.facebook.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)
线程 0x6f9c 已退出，返回值为 0 (0x0)。
[2021-05-18 23:25:34][DEBUG] added udp session <IP_ADDRESS>:52063 -> <IP_ADDRESS>:1900 (1)
[2021-05-18 23:25:34][TRACE] pick route failed: no matching rules
[2021-05-18 23:25:34][DEBUG] picked default route [VMess] for <IP_ADDRESS>:52063 -> <IP_ADDRESS>:1900
[2021-05-18 23:25:34][TRACE] socket bind <IP_ADDRESS>:0
[2021-05-18 23:25:34][DEBUG] dispatch udp <IP_ADDRESS>:52063 -> <IP_ADDRESS>:1900 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)
[2021-05-18 23:25:34][TRACE] netstack tcp new <IP_ADDRESS>:56203
[2021-05-18 23:25:34][TRACE] pick route failed: no matching rules
[2021-05-18 23:25:34][DEBUG] picked default route [VMess] for <IP_ADDRESS>:56203 -> heartbeat.dm.origin.com:80
[2021-05-18 23:25:34][TRACE] active proxied tcp connections +1: 1
[2021-05-18 23:25:34][TRACE] socket bind <IP_ADDRESS>:0
[2021-05-18 23:25:34][DEBUG] dispatch tcp <IP_ADDRESS>:56203 -> heartbeat.dm.origin.com:80 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)
[2021-05-18 23:25:34][TRACE] netstack tcp shutdown <IP_ADDRESS>:56203
[2021-05-18 23:25:34][TRACE] active proxied tcp connections -1: 0
[2021-05-18 23:25:34][TRACE] netstack tcp drop <IP_ADDRESS>:56203
[2021-05-18 23:25:37][DEBUG] added udp session <IP_ADDRESS>:52063 -> <IP_ADDRESS>:1900 (1)
[2021-05-18 23:25:37][TRACE] pick route failed: no matching rules
[2021-05-18 23:25:37][DEBUG] picked default route [VMess] for <IP_ADDRESS>:52063 -> <IP_ADDRESS>:1900
[2021-05-18 23:25:37][TRACE] socket bind <IP_ADDRESS>:0
[2021-05-18 23:25:37][DEBUG] dispatch udp <IP_ADDRESS>:52063 -> <IP_ADDRESS>:1900 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)
[2021-05-18 23:25:38][TRACE] netstack tcp new <IP_ADDRESS>:56205
[2021-05-18 23:25:38][TRACE] pick route failed: no matching rules
[2021-05-18 23:25:38][DEBUG] picked default route [VMess] for <IP_ADDRESS>:56205 -> api.github.com:443
[2021-05-18 23:25:38][TRACE] active proxied tcp connections +1: 1
[2021-05-18 23:25:38][TRACE] socket bind <IP_ADDRESS>:0
[2021-05-18 23:25:38][DEBUG] dispatch tcp <IP_ADDRESS>:56205 -> api.github.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)
[2021-05-18 23:25:38][TRACE] netstack tcp shutdown <IP_ADDRESS>:56205
[2021-05-18 23:25:38][TRACE] active proxied tcp connections -1: 0
[2021-05-18 23:25:38][TRACE] netstack tcp drop <IP_ADDRESS>:56205
[2021-05-18 23:25:39][TRACE] netstack tcp new <IP_ADDRESS>:56206
[2021-05-18 23:25:39][TRACE] pick route failed: no matching rules
[2021-05-18 23:25:39][DEBUG] picked default route [VMess] for <IP_ADDRESS>:56206 -> heartbeat.dm.origin.com:80
[2021-05-18 23:25:39][TRACE] active proxied tcp connections +1: 1
[2021-05-18 23:25:39][TRACE] socket bind <IP_ADDRESS>:0
[2021-05-18 23:25:39][DEBUG] dispatch tcp <IP_ADDRESS>:56206 -> heartbeat.dm.origin.com:80 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)
[2021-05-18 23:25:39][TRACE] netstack tcp shutdown <IP_ADDRESS>:56206
[2021-05-18 23:25:40][TRACE] active proxied tcp connections -1: 0
[2021-05-18 23:25:40][TRACE] netstack tcp drop <IP_ADDRESS>:56206
[2021-05-18 23:25:40][DEBUG] added udp session <IP_ADDRESS>:58004 -> <IP_ADDRESS>:443 (1)
[2021-05-18 23:25:40][TRACE] pick route failed: no matching rules
[2021-05-18 23:25:40][DEBUG] picked default route [VMess] for <IP_ADDRESS>:58004 -> www.facebook.com:443
[2021-05-18 23:25:40][TRACE] socket bind <IP_ADDRESS>:0
[2021-05-18 23:25:40][DEBUG] dispatch udp <IP_ADDRESS>:58004 -> www.facebook.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)
[2021-05-18 23:25:40][DEBUG] allocate <IP_ADDRESS> for clients4.google.com
[2021-05-18 23:25:40][TRACE] netstack tcp new <IP_ADDRESS>:56207
[2021-05-18 23:25:40][TRACE] pick route failed: no matching rules
[2021-05-18 23:25:40][DEBUG] picked default route [VMess] for <IP_ADDRESS>:56207 -> clients4.google.com:443
[2021-05-18 23:25:40][TRACE] active proxied tcp connections +1: 1
[2021-05-18 23:25:40][TRACE] socket bind <IP_ADDRESS>:0
[2021-05-18 23:25:40][DEBUG] dispatch tcp <IP_ADDRESS>:56207 -> clients4.google.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)
[2021-05-18 23:25:40][TRACE] netstack tcp shutdown <IP_ADDRESS>:56207
[2021-05-18 23:25:40][TRACE] active proxied tcp connections -1: 0
[2021-05-18 23:25:40][TRACE] netstack tcp drop <IP_ADDRESS>:56207
[2021-05-18 23:25:40][TRACE] netstack tcp new <IP_ADDRESS>:56208
[2021-05-18 23:25:40][TRACE] pick route failed: no matching rules
[2021-05-18 23:25:40][DEBUG] picked default route [VMess] for <IP_ADDRESS>:56208 -> clients4.google.com:443
[2021-05-18 23:25:40][TRACE] active proxied tcp connections +1: 1
[2021-05-18 23:25:40][TRACE] socket bind <IP_ADDRESS>:0
[2021-05-18 23:25:40][DEBUG] dispatch tcp <IP_ADDRESS>:56208 -> clients4.google.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)
[2021-05-18 23:25:40][TRACE] netstack tcp shutdown <IP_ADDRESS>:56208
[2021-05-18 23:25:40][TRACE] active proxied tcp connections -1: 0
[2021-05-18 23:25:40][TRACE] netstack tcp drop <IP_ADDRESS>:56208
[2021-05-18 23:25:40][DEBUG] allocate <IP_ADDRESS> for beacons4.gvt2.com
[2021-05-18 23:25:40][DEBUG] added udp session <IP_ADDRESS>:63366 -> <IP_ADDRESS>:443 (1)
[2021-05-18 23:25:40][TRACE] pick route failed: no matching rules
[2021-05-18 23:25:40][DEBUG] picked default route [VMess] for <IP_ADDRESS>:63366 -> beacons4.gvt2.com:443
[2021-05-18 23:25:40][TRACE] socket bind <IP_ADDRESS>:0
[2021-05-18 23:25:40][DEBUG] dispatch udp <IP_ADDRESS>:63366 -> beacons4.gvt2.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)
[2021-05-18 23:25:40][DEBUG] added udp session <IP_ADDRESS>:63366 -> <IP_ADDRESS>:443 (1)
[2021-05-18 23:25:40][TRACE] pick route failed: no matching rules
[2021-05-18 23:25:40][DEBUG] picked default route [VMess] for <IP_ADDRESS>:63366 -> beacons4.gvt2.com:443
[2021-05-18 23:25:41][TRACE] socket bind <IP_ADDRESS>:0
[2021-05-18 23:25:41][DEBUG] dispatch udp <IP_ADDRESS>:63366 -> beacons4.gvt2.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)
[2021-05-18 23:25:41][TRACE] netstack tcp new <IP_ADDRESS>:56210
[2021-05-18 23:25:41][TRACE] pick route failed: no matching rules
[2021-05-18 23:25:41][DEBUG] picked default route [VMess] for <IP_ADDRESS>:56210 -> beacons4.gvt2.com:443
[2021-05-18 23:25:41][TRACE] active proxied tcp connections +1: 1
[2021-05-18 23:25:41][TRACE] socket bind <IP_ADDRESS>:0
[2021-05-18 23:25:41][DEBUG] dispatch tcp <IP_ADDRESS>:56210 -> beacons4.gvt2.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)
[2021-05-18 23:25:41][TRACE] netstack tcp shutdown <IP_ADDRESS>:56210
[2021-05-18 23:25:41][TRACE] active proxied tcp connections -1: 0
[2021-05-18 23:25:41][TRACE] netstack tcp drop <IP_ADDRESS>:56210
[2021-05-18 23:25:41][TRACE] netstack tcp new <IP_ADDRESS>:56211
[2021-05-18 23:25:41][TRACE] netstack tcp new <IP_ADDRESS>:56212
[2021-05-18 23:25:41][TRACE] pick route failed: no matching rules
[2021-05-18 23:25:41][TRACE] pick route failed: no matching rules
[2021-05-18 23:25:41][DEBUG] picked default route [VMess] for <IP_ADDRESS>:56212 -> beacons4.gvt2.com:443
[2021-05-18 23:25:41][DEBUG] picked default route [VMess] for <IP_ADDRESS>:56211 -> beacons4.gvt2.com:443
[2021-05-18 23:25:41][TRACE] active proxied tcp connections +1: 1
[2021-05-18 23:25:41][TRACE] active proxied tcp connections +1: 2
[2021-05-18 23:25:41][TRACE] socket bind <IP_ADDRESS>:0
[2021-05-18 23:25:41][TRACE] socket bind <IP_ADDRESS>:0
[2021-05-18 23:25:41][DEBUG] dispatch tcp <IP_ADDRESS>:56212 -> beacons4.gvt2.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)
[2021-05-18 23:25:41][DEBUG] dispatch tcp <IP_ADDRESS>:56211 -> beacons4.gvt2.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)
[2021-05-18 23:25:41][TRACE] netstack tcp shutdown <IP_ADDRESS>:56212
[2021-05-18 23:25:41][TRACE] active proxied tcp connections -1: 1
[2021-05-18 23:25:41][TRACE] netstack tcp shutdown <IP_ADDRESS>:56211
[2021-05-18 23:25:41][TRACE] active proxied tcp connections -1: 0
[2021-05-18 23:25:41][TRACE] netstack tcp drop <IP_ADDRESS>:56212
[2021-05-18 23:25:41][TRACE] netstack tcp drop <IP_ADDRESS>:56211
[2021-05-18 23:25:41][TRACE] netstack tcp new <IP_ADDRESS>:56213
[2021-05-18 23:25:41][TRACE] pick route failed: no matching rules
[2021-05-18 23:25:41][DEBUG] picked default route [VMess] for <IP_ADDRESS>:56213 -> beacons4.gvt2.com:443
[2021-05-18 23:25:41][TRACE] active proxied tcp connections +1: 1
[2021-05-18 23:25:41][TRACE] socket bind <IP_ADDRESS>:0
[2021-05-18 23:25:41][DEBUG] dispatch tcp <IP_ADDRESS>:56213 -> beacons4.gvt2.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)
[2021-05-18 23:25:41][TRACE] netstack tcp shutdown <IP_ADDRESS>:56213
[2021-05-18 23:25:41][TRACE] active proxied tcp connections -1: 0
[2021-05-18 23:25:41][DEBUG] added udp session <IP_ADDRESS>:63366 -> <IP_ADDRESS>:443 (1)
[2021-05-18 23:25:41][TRACE] netstack tcp drop <IP_ADDRESS>:56213
[2021-05-18 23:25:41][TRACE] pick route failed: no matching rules
[2021-05-18 23:25:41][DEBUG] picked default route [VMess] for <IP_ADDRESS>:63366 -> beacons4.gvt2.com:443
[2021-05-18 23:25:41][TRACE] socket bind <IP_ADDRESS>:0
[2021-05-18 23:25:41][DEBUG] dispatch udp <IP_ADDRESS>:63366 -> beacons4.gvt2.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)
[2021-05-18 23:25:41][DEBUG] added udp session <IP_ADDRESS>:52063 -> <IP_ADDRESS>:1900 (2)
[2021-05-18 23:25:41][TRACE] pick route failed: no matching rules
[2021-05-18 23:25:41][DEBUG] picked default route [VMess] for <IP_ADDRESS>:52063 -> <IP_ADDRESS>:1900
[2021-05-18 23:25:41][TRACE] socket bind <IP_ADDRESS>:0
[2021-05-18 23:25:41][DEBUG] dispatch udp <IP_ADDRESS>:52063 -> <IP_ADDRESS>:1900 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)
[2021-05-18 23:25:42][DEBUG] added udp session <IP_ADDRESS>:63366 -> <IP_ADDRESS>:443 (1)
[2021-05-18 23:25:42][TRACE] pick route failed: no matching rules
[2021-05-18 23:25:42][DEBUG] picked default route [VMess] for <IP_ADDRESS>:63366 -> beacons4.gvt2.com:443
[2021-05-18 23:25:42][TRACE] socket bind <IP_ADDRESS>:0
[2021-05-18 23:25:42][DEBUG] dispatch udp <IP_ADDRESS>:63366 -> beacons4.gvt2.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)

Added in v0.9.0.


Add support for listing KIngresses & HTTPProxies

Since using Knative & Contour in Pair by default now, it would be good to have it so when a Knative service is deployed, it shows up in Ingress list on a Pair instance page

Resolved in https://github.com/sharingio/pair/pull/147


Unable to install falco in anyother cluster other than minikube cluster

Using minikube cluster,when trying to install falco through helm with the below command
helm install falco falcosecurity/falco --set driver.kind=ebpf --namespace falco --create-namespace
my pod is in running state....But in devcluster or anyother cluster,when trying to install falco with this command getting crash loopbackoff state.Pls help me to solve this issue

Hi!
This does not belong to driverkit repo; it should be opened against Falco repository.

Duplicate of https://github.com/falcosecurity/charts/issues/485

Closing this one.
/close

@FedeDP: Closing this issue.

In response to this:

Closing this one.
/close

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


Make map2model optional using geopandas spatial joins as a replacement

Replaces the topology calculation from map2model with spatial joins in geopandas. Future idea would be to remove map2model completely as it seems to be crashing on new shapefiles for some reason.

@lachlangrose there are conflicts with this branch and v3.2;
I can't tell which portions of the code you wanted to keep/delete on map2model_wrapper; would you be able to have a look at the conflicts when you can?

Thank you,
will merge this now!


How to connect two freely floating bodies through Moordyn v2 in Matlab

Hello, I have a question about whether it is possible to connect two freely floating bodies through Moordyn v2 and calculate the cable tension. The parameters and hydrodynamic coefficients of the two floating bodies are calculated by an external program. My input file (txt) in Matlab is as follows: set one floating body as a vessel and the other as coupled, with a ballast block (set as Free) connected in the middle of the cable. Is this feasible? Should we define another floating object as the body and assign parameters in the txt file? Perhaps there are other ways to achieve this goal, thank you very much for your help, sincerely wish you all the best.
--------------------- MoorDyn Input File ------------------------------------
Mooring system for the the floater
----------------------- LINE TYPES ------------------------------------------
TypeName   Diam    Mass/m     EA         BA/-zeta    EI         Cd     Ca     CdAx    CaAx
(name)           (m)     (kg/m)     (N)         (N-s/-)     (N-m^2)   (-)    (-)      (-)           (-)
Seg1	   0.088      47.885    3.13E+08	   -0.8	  0          1     0.025    0           1.2
---------------------- POINT PROPERTIES --------------------------------
ID    Type      X       Y       Z       Mass   Volume  CdA    Ca
(#)   (-)       (m)     (m)     (m)     (kg)    (m^3)    (m^2)  (-)
1     Vessel   -0.1     0       0        0        0            0         0
2     Free     109      0       0       764     9.708      2.5      1
3     Coupled  0.1      0       0       0       0            0         0
---------------------- LINES ----------------------------------------
ID   LineType   AttachA  AttachB  UnstrLen  NumSegs  LineOutputs
(#)   (name)     (#)           (#)              (m)            (-)              (-)
1      Seg1	1	       2                50	           25	              -
2      Seg1	2	       3                50	           25	              -
---------------------- OPTIONS -----------------------------------------
2             writeLog      Write a log file
0.0001         dtM           time step to use in mooring integration (s)
3.0e6         kBot          bottom stiffness (Pa/m)
3.0e5         cBot          bottom damping (Pa-s/m)
1025.0        WtrDnsty      water density (kg/m^3)
1330           WtrDpth       water depth (m)
0.001           dtIC          time interval for analyzing convergence during IC gen (s)
1.0         TmaxIC        max time for ic gen (s)
4.0           CdScaleIC     factor by which to scale drag coefficients during dynamic relaxation (-)
0.001         threshIC      threshold for IC convergence (-)
-------------------------- OUTPUTS --------------------------------
FairTen1
FairTen2
------------------------- need this line --------------------------------------

MoorDyn is meant to solve the mooring lines. The dynamics of the bodies are your responsibility.
You can consider using OpenFAST to solve your problem (which has already MoorDyn integrated)

I want to calculate the mooring tension between two freely floating objects

I want to calculate the mooring tension between two freely floating objects

Sure. How are you planning to solve the floating objects motion?

I have already built the Cummins equation in Matlab to calculate the motion of floating bodies. I would like to know how to define the position of the mooring point in the input file (txt) if I want to calculate the cable tension between two floating bodies

In other words, I only need to solve how to calculate the mooring line tension between two floating bodies through Moordyn v2, could you provide good advice about the input file? Thank you.

OK, then you have 2 options:

Use coupled points, as you are doing now. Then you need to get those 2 points manually solving your body kinematics
Create coupled bodies, so you just report the bodies motion and MoorDyn will take care on the rigid body kinematics

A pseudo-matlab code (using points) would look like:
p1 = MoorDynM_GetPoint(system, 1)
p2 = MoorDynM_GetPoint(system, 3)
l1 = MoorDynM_GetLine(system, 1)
l2 = MoorDynM_GetLine(system, 2)
t = 0
while 1
    p1_curr = MoorDynM_GetPointPos(p1)
    p2_curr = MoorDynM_GetPointPos(p2)
    p1_next = rigid_body_kin(mybody1,  -0.1 0, 0)
    p2_next = rigid_body_kin(mybody2,  0.1 0, 0)
    u1 = (p1_next - p1_curr) / dt
    u2 = (p2_next - p2_curr) / dt
    MoorDynM_Step(system, [p1_curr p2_curr], [u1 u2], t, dt)

    % Get the forces on the line ends
    f1 = MoorDynM_GetLineNodeTen(l1, 0)
    f2 = MoorDynM_GetLineNodeTen(l2, MoorDynM_GetLineN(l2))

    t += dt
end

Thanks a lot. But if I use coupled points, how should I define the floating bodies in the input txt file? The first body is "Vessel", how to define the other body?

"Vessel" and "Coupled" means exactly the same. On that config you are letting MoorDyn know that you will provide the position and velocity of the points 1 and 3.
If you look the example, when I call MoorDynM_Step(), I am giving it the position and velocity of both points. The position I get it from Moordyn itself (calling MoorDynM_GetPointPos()), but for the velocities you need to use your computed kinematics to know them (I called that rigid_body_kin())

OK, I understand what you mean, thank you very much for your help!

Sorry, I want to know what does the result in the 3 * 1 matrix output by f1 represent? Are they the forces in the x, y, and z directions of the fairlead?

Yes

Just to clarify:
Are the forces in the global x, y, and z directions at the fairlead

The fuction  MoorDynM_Step() also output the force about a 3 * 1 matrix, are they the same result?

Nope... MoorDynM_Step() returns the sum of the forces on all the coupled entities (points in your case). I suppose we keep that for backward compatibility, but you can ignore that value.

Thanks a lot. But the force from MoorDynM_GetLineNodeTen() can not be updated with current points, even if I have a new fairlead position, how can I obtain the force on the fairlead?

Of course the force is updated... It is a staggered coupling.

Get the motions of the fairleads from your floating bodies
Provide MoorDyn with that info calling to MoorDynM_Step()
Get the new forces calling to MoorDynM_GetNodeTen()
Give those forces to your floating bodies an compute the motions for the
next step

You can alternatively use MoorDynM_GetPointForce() if you like that better
On Fri, 11 Oct 2024, 12:52 yjj, @.***> wrote:

Thanks a lot. But the force from MoorDynM_GetLineNodeTen() can not be
updated with current points, even if I have a new fairlead position, how
can I obtain the force on the fairlead?
—
Reply to this email directly, view it on GitHub
https://github.com/FloatingArrayDesign/MoorDyn/issues/254#issuecomment-2407152755,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMXKKFJTVGGL7J3UAV5MCTZ26UVNAVCNFSM6AAAAABPTVIKVKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBXGE2TENZVGU
.
You are receiving this because you commented.Message ID:
@.***>

I tried to use the MoorDynMGetPointForce() function to calculate the force on the fairlead, but the result is the same as that obtained from MoorDynM_Step (system, [p1_curr p2_curr], [u1 u2], t, dt). Is this reasonable?

@ferrari700,
Yes that is reasonable. MoorDynM_Step returns the forces on the coupled objects in their respective degree of freedom (global frame). MoorDynMGetPointForce() returns the 3 DOF forces on the specified point. Because you have coupled points, then MoorDynM_Step will return the same force as MoorDynMGetPointForce

But there are two fairleads on the coupling body, and I want to calculate the forces on both fairleads separately, rather than the coupling forces acting on the body.

If  MoorDynM_Step() is returning a 3x1 array is because there are something wrong on the Matlab code. Look here, the output has the same size than the input position ([p1_curr p2_curr]).
 Please, check that [p1_curr p2_curr] and [u1 u2] are one-dimensional arrays of 6 components each.

So if there are three cable holes, the inputs should be [p1_curr p2_curr p3_curr] and [u1 u2 u3], and the outputs should be [t, F], right?

So if there are three cable holes, the inputs should be [p1_curr p2_curr p3_curr] and [u1 u2 u3], and the outputs should be [t, F], right?

In your particular case, yes (assuming cable hole = fairlead = coupled point). In general you must provide inputs for all the coupled entities you have in your MoorDyn file.

So the F in the output is a 9 * 1 array, and the force of each fairleads  is a 3 * 1 array, right?

Yep


Overriding save in a model

Hi,
if you override the save (or update, etc.) method in a model, the save method of the Translatable trait isnt called.
perhaps it would be better to override finishSave in the Translatable or using a static bootTranslatable method ?
And:
why both update and save are defined in Translatable ?
Eloquent is using save() in its update method.
So i think it would be good to go with finishSave()
Then, you also dont have to check for $saved
What do you think ?

Any kind of optimization is welcome. I'll keep this here as an reminder. Thanks for your suggestion!

I've implemented this in #52


bump kubevirtci: sriov provider switch to self signed certificates

Signed-off-by: Or Mergi<EMAIL_ADDRESS>
What this PR does / why we need it:
This PR tests kubevirt/kubevirtci#472 with kubevirt functests
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

/test

/test pull-kubevirt-e2e-kind-1.17-sriov

/test pull-kubevirt-e2e-kind-1.17-sriov

/test pull-kubevirt-e2e-kind-1.17-sriov

/test pull-kubevirt-e2e-kind-1.17-sriov

/test pull-kubevirt-e2e-kind-1.17-sriov

/test pull-kubevirt-e2e-kind-1.17-sriov


Breaking: drop older Puppet version support, add data types, other breaking changes

This is backwards incompatible in multiple ways

Drop support for Puppet < 4.7.1
Require stdlib >= 4.13
Drop support for very old OSes like RHEL / CentOS 5, etc.

Additionally, we:

restructure class inclusion by replacing anchor pattern with 'contain' and class ordering
switch to data types from validate_. For now, I just added them to stuff that was super obvious and things that had validate_ calls.
rename $::foo to $foo (absolute classname check is not needed with newer Puppet) (sorry I didn't break these changes out into a separate commit)
switch to structured facts
move from $foo_real to $_foo pattern

I'm good with trying to rebase this if #111 gets merged, so we can definitely hold off until that at least.

@wyardley After #113 you should be good to go with the refactor.

I have rebased this, and the tests should all pass (with the one pending test from 20673eb8). I do wonder a bit if it's a little regressive to get rid of all the class params in favor of using config_hash for everything. We could reinstate some of them and build the defaults from those same values, which would allow for backwards compatibility, and allow for parameter validation.
@sts If it's not too hard, are you able to do some functional testing with this PR and make sure that it still works?

@sts: Proposed some changes to make the CHANGELOG a little terser, let me know what you think. It's in a separate commit, so could easily get taken out or reverted.
@craigwatson I don't know what your release process is, but I updated the CHANGELOG with my changes as well as reworked some of the stuff from #111. But there are probably other items that should go in there, the date might need to change, and entries might still need to be recategorized.
I may or may not have time to test this this week with our setup, but hopefully some folks will be able to test this so that we can have more confidence.

@craigwatson I rebased against your recent changes - think I got everything.

@wyardley thanks for the awesome work here - I think I'm going to put this on the back-burner for a few weeks as I'd like to get the module into a decent state before deprecating older Puppet versions.
The deprecation plan is (at the moment) to get one major release done to the Forge which is compatible with Puppet 3, and then drop in a deprecation message á la Voxpupuli - though I admit that this has been a long time coming!
Would you be happy to split the breaking changes out of this PR?

@craigwatson I can take a look, but I think the whole PR is breaking, as data types are Puppet 4 only, I think using contain pattern over anchor pattern, and the switch to structured facts, will also not work in earlier Puppet versions. While switching to $foo from $::foo and removing the absolute classname check probably would be fine in this case, that was also a workaround related to Puppet 3. That really leaves only some minor changes (though you're welcome to cherry-pick out bits  of the reworded changelog if it's helpful to you).
I can make a best effort to rebase again later if there are more changes, however, I'm moving to a job where I won't be working with Puppet and won't be using this module, so I may not have as much of an incentive to keep this updated.
Puppet 3 is already EOL, and folks who need to support it could always get the older forge release and / or the Github fork. Vox has dropped Puppet 3 support in all modules quite a while back (and any modules that have a Puppet 3 branch are no longer maintained). So, while I absolutely agree that more functional testing before a Forge release was good, I'm not sure how necessary it is to do an explicit Forge release that supports Puppet 3 first.
One thing I didn't add in this PR, but should probably happen later, is to switch to Puppet strings for docs (and review that the class params documented are still the correct ones).

@craigwatson release the current version to the forge and then lets proceed with @wyardley puppet 4 patch!
Please also get https://github.com/claranet/puppet-consul_template/pull/114 merged first, then we should be good to go for a last Puppet 3 release!

@sts you're too quick! I'm re-checking all dependencies at the moment, and will run a Forge release when done :)

@wyardley OK, now that we have a stable release to the Forge, we can merge these breaking changes and get version 2.0.0 released once we're happy. Can you rebase one last time? I've also incorporated your CHANGELOG alterations into the 1.0.0 release so it should make the PR code-only :)

@craigwatson rebased again.
btw, you left in the bit about requiring Puppet < 4.7.1 and stdlib >= 4.13 in the CHANGELOG for the last release. That isn't actually added until this is merged.

@wyardley thanks for all your help here - nice to finally get this merged!
A Forge release of 2.0.0 will be done soon 👍

@craigwatson Thanks! Let me know if you need help with changelog or anything.
BTW, since it's the same, might want to deprecate gdhbashton/consul_template in the forge, as it still shows up first in a search.


feat: Add merchant key store

Type of Change

[x] Enhancement

Description

This PR adds key store DB which stores encryption key per merchant account. The encryption key will be further encrypted by master_key which will further be KMS encrypted.
Additional Changes

[x] This PR modifies the database schema
[x] This PR modifies application configuration/environment variables

Motivation and Context

How did you test it?

Manual
Checklist

[x] I formatted the code cargo +nightly fmt --all
[x] I addressed lints thrown by cargo clippy
[x] I reviewed submitted code

All InternalServerError Should have attach_printable which explains the about the Error

Import the mod and use mod::func in the application, change all functions which is imported as crate::mod::func to mod::func

Done


Add USE_MATH_DEFINES for tests compile definitions

See https://github.com/dic-iit/bipedal-locomotion-framework/pull/85#issuecomment-686605967

I don't remember. Was this definition useful only for executables? Does it make sense also to add this definition for the libraries?

I don't remember. Was this definition useful only for executables? Does it make sense also to add this definition for the libraries?

I think it makes sense for libraries as well. In general, anything that would pertain the using math constants.

I made a mistake in copy-paste ;D and another mistake of not building before pushing.
Anyways, shall we also add the definitions for interface?

I made a mistake in copy-paste ;D and another mistake of not building before pushing.
Anyways, shall we also add the definitions for interface?

And I did not notice it :joy: In theory, interface targets are not built. So it should be handled by user classes I guess :thinking:

And I did not notice it In theory, interface targets are not built. So it should be handled by user classes I guess

Alright. we shall add those definitions only for libraries then.


_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 41s
master passed

+1 :green_heart:
compile
0m 48s
master passed

+1 :green_heart:
checkstyle
0m 23s
master passed

+1 :green_heart:
spotbugs
0m 42s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 38s
the patch passed

+1 :green_heart:
compile
0m 48s
the patch passed

-0 :warning:
javac
0m 48s
hbase-common generated 5 new + 155 unchanged - 0 fixed = 160 total (was 155)

-0 :warning:
checkstyle
0m 25s
hbase-common: The patch generated 2 new + 25 unchanged - 1 fixed = 27 total (was 26)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
18m  4s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1 3.3.0.

+1 :green_heart:
spotbugs
0m 55s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 12s
The patch does not generate ASF License warnings.

38m 31s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3586/5/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3586

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile

uname
Linux ee73a8da1c99 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / c8d9d4df80

Default Java
AdoptOpenJDK-1.8.0_282-b08

javac
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3586/5/artifact/yetus-general-check/output/diff-compile-javac-hbase-common.txt

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3586/5/artifact/yetus-general-check/output/diff-checkstyle-hbase-common.txt

Max. process+thread count
96 (vs. ulimit of 30000)

modules
C: hbase-common U: hbase-common

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3586/5/console

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

@anoopsjohn， would you please help me have a review?

Please fix the checkstyle and javac issues?

@Apache9 ， thank you for review， fixed checkstyle issues.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 25s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+1 :green_heart:
mvninstall
4m 17s
master passed

+1 :green_heart:
compile
0m 27s
master passed

+1 :green_heart:
shadedjars
8m 18s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 24s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 19s
the patch passed

+1 :green_heart:
compile
0m 25s
the patch passed

+1 :green_heart:
javac
0m 25s
the patch passed

+1 :green_heart:
shadedjars
8m 11s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 24s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
2m  6s
hbase-common in the patch passed.

30m 38s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3586/6/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3586

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 29ca4f73ef8c 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 137c7dcd3d

Default Java
AdoptOpenJDK-11.0.10+9

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3586/6/testReport/

Max. process+thread count
288 (vs. ulimit of 30000)

modules
C: hbase-common U: hbase-common

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3586/6/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 36s
Docker mode activated.

-0 :warning:
yetus
0m  4s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+1 :green_heart:
mvninstall
5m 17s
master passed

+1 :green_heart:
compile
0m 25s
master passed

+1 :green_heart:
shadedjars
9m 40s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 23s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 33s
the patch passed

+1 :green_heart:
compile
0m 26s
the patch passed

+1 :green_heart:
javac
0m 26s
the patch passed

+1 :green_heart:
shadedjars
9m 47s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 25s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
2m 13s
hbase-common in the patch passed.

36m  9s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3586/6/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3586

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 9506afb0ae67 4.15.0-147-generic #151-Ubuntu SMP Fri Jun 18 19:21:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 137c7dcd3d

Default Java
AdoptOpenJDK-1.8.0_282-b08

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3586/6/testReport/

Max. process+thread count
220 (vs. ulimit of 30000)

modules
C: hbase-common U: hbase-common

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3586/6/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Clear entry if pressing down arrow with last msg in entry

https://user-images.githubusercontent.com/76887896/147389843-2222fba7-0bdf-4e13-a19d-54e0bdc3baaa.mov

Doesn't exactly fix #103 . However, I believe it is already fixed, and this is related to it.


Multi-model/model sizing

Outline
Vehicles are currently limited to 1 model so that means that you are limited to an specific size of models.
How?
This could be changed by making it so that you can add multiple models to an vehicle and changing the x y z of it so it fits correctly or you could make it so that we can scale models to x size so that the user makes an tiny model but that the model can be scaled up with mtv
Photos, videos, sketches (optional)
Not really have any
##This is just an suggestion for the next major update

You can change the scale in blockbench right?

yeah but that also has an limit

Hello, to come back to this suggestion, I'm of the same opinion. It so happens that some modelers make rather large models, which need to be divided into several parts.
This addition would make it possible to assemble several parts into a single vehicle. For example, on an armor stand for the helmet there's the front of a truck, for the chestplate it's the beginning of the trailer, and for the leggings it's the end of the trailer, and together that makes a truck with a trailer.
And so, as @Gc-network also said, BlockBench blocks the size's limit, but it's mainly minecraft that blocks it, so there's no way of getting around this problem without splitting the models into several parts.
I think that some plugins support this type of vehicle by default, so it should of course be possible without modifying the code too much I think.
I hope we'll be able to get an answer on this addition idea, and maybe find this feature in the next update ;)


chore: update Copyright time from 2023 to 2024

Description

Additional context

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[x] Other

Before submitting the PR, please make sure you do the following

[ ] Read the Contributing Guidelines, especially the Pull Request Guidelines.
[ ] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[ ] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Update the corresponding documentation if needed.
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

we should wait some days with that file, so we don't need to regenerate this file over and over again for every single dependency

Yeah the license file is autogenerated during the local Vite build, and the years are pulled by the dependencies' license. It shouldn't be edited manually.