TypeError: init() missing 21 required positional arguments:

I am trying to evaluate the model on a custom dataset. However, when running test.py it is unable to load the model from the given weights-
python test.py pretrained/parseq-bb5792a6.pt --data_root="/home/devesh/scratch/STR_test_datasets/"
Traceback (most recent call last):   File "test.py", line 145, in <module>     main()   File "/home/devesh/scratch/miniconda3/envs/parseq/lib/python3.7/site-packages/torch/autograd/grad_mode.py", line 27, in decorate_context     return func(*args, **kwargs)   File "test.py", line 99, in main     model = load_from_checkpoint(args.checkpoint, **kwargs).eval().to(args.device)   File "/nvme/scratch/devesh/mavi/parseq/strhub/models/utils.py", line 85, in load_from_checkpoint     model = ModelClass.load_from_checkpoint(checkpoint_path, **kwargs)   File "/home/devesh/scratch/miniconda3/envs/parseq/lib/python3.7/site-packages/pytorch_lightning/core/saving.py", line 161, in load_from_checkpoint     model = cls._load_model_state(checkpoint, strict=strict, **kwargs)   File "/home/devesh/scratch/miniconda3/envs/parseq/lib/python3.7/site-packages/pytorch_lightning/core/saving.py", line 203, in _load_model_state     model = cls(**_cls_kwargs) TypeError: __init__() missing 21 required positional arguments: 'charset_train', 'max_label_length', 'batch_size', 'lr', 'warmup_pct', 'weight_decay', 'img_size', 'patch_size', 'embed_dim', 'enc_num_heads', 'enc_mlp_ratio', 'enc_depth', 'dec_num_heads', 'dec_mlp_ratio', 'dec_depth', 'perm_num', 'perm_forward', 'perm_mirrored', 'decode_ar', 'refine_iters', and 'dropout'

As of commit b290950dad5a3dceb574cbc2d902765e1496ace2, the proper way of using pretrained weights is: ./test.py pretrained=parseq


goimapnotify: init at 2.0

Motivation for this change
goimapnotify is more reliable in my experience than the alternative currently available on nixpkgs, node-imapnotify.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

re empty output: not sure what that's about. could maybe tell you more if I saw what's in your goimapnotify.conf?
re project maintenance: not sure what's going on there either, I'm not personally involved in the project beyond packaging it here.

@doronbehar yep, i'm happy to take care of it. thanks!

Is there something else I need to do here? Sorry, this process is new to me.

LGTM, sorry for the delay

Thanks!


Convert a config file to build a dynamic module

Please refer to Converting Static Modules to Dynamic Modules | NGINX for dynamic modules.

Hello,
Is it possible to proceed with this pull request adding dynamic module support for? The module is part of nginx-full in debian/ubuntu and we are in the process of splitting the modules in separate packages.
Thank you

@ctrochalakis I confirmed that this module was built successfully with this pull request when I made it. However I have not used this module myself after that.
So you need to test it yourself.

@hnakamur with out the patch from #51 nginx just segfaults child workers. On my test centOS7 server to work as expected.


Global variables lazy load support

I'm a new pebble user. I want to inject some global variables in pebble context.
However, getting some variables is a relatively expensive operation.
I hope to get it when I really need it. It means that the pebble could increase support for lazy loading.
For example, if a variable implements a java interface named java.util.function.Supplier, pebbel should invoke it's get() method to get the actual value.

Should be easy to add Supplier support. I'll take a look

Why don't you implement this on your own? (Deliver the expensive variables as objects with a "get" method, that will fetch the result only on demand)
Pebble will become slower with that by checking each variable with "instanceof".... And we all love pebble for its speed :)

Take a look here in last section (Attribute resolver (v3 only)).
I suggest first that you add your custom attribute resolver in the chain for Supplier support and it should work.

@CodePlayer Did you try to define a custom attribute resolver ?

@ebussieres Yes, I've already done this.

OK, it works! I will close this issue later. Many thanks!


Error running WindowsContainerNetworking-LoggingAndCleanupAide.ps1 under PS6

Works fine when running under PS5. With PS6:
Script Failed:The term 'Get-WmiObject' is not recognized as the name of a cmdlet, function, script file, or operable program.

Same issue.

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


how to disable video on small devices 'phones'

how to disable video on small devices
thanks

Hi @MuhammadEid, I added a suggestion here: https://github.com/VodkaBears/Vide/issues/162

Simple Solution, This will trigger video fallback and shows image
@media screen and (max-width: 767px) {
#parent-div-name video
{
display: none
}
}

Simple Solution, This will trigger video fallback and shows image
@media screen and (max-width: 767px)
{
#parent-div-name video
{
display: none
}
}


portico: Update text of why-zulip.

A few notes:

I left Julia's picture in the codebase, even though it is not currently linked to from anywhere, since I expect we might want it for something else later (or possibly even on this page).
I compressed Grahame's quote a bit.

Merged, thanks @rishig!


How to make npy file?

Thank you for your excellent research.
https://github.com/jfzhang95/PoseAug/blob/main/data_extra/bone_length_npy/hm36s15678_bl_templates.npy
I wonder how this file was created.

Hi, thank you for the interest.
This is created by caculate the length between adjacent joint (eg, from LElbow to LWrist is the length of LElbow).

Thank you for your reply.

@Garfield-kh I have the same question about the './data_extra/bone_length_npy/hm36s15678_bl_templates.npy'.
The shape of ndarry is [5,15]. what's the meaning of it? why the row is 5?
Another question, i want to apply PoseAug on coco-wholebody dataset (133 keypoints).
Do you have some suggestions about this?
Thanks in advance and look forward for your suggestion.


t470s battery icon

Unfortunately, the battery icon is not showing on my t470s. I have the same configuration as the t460s.

same, the battery icon is not showing on my L470 (only have single battery) :(

There's nothing I can do for you guys, this project is for T460s.


chore: update build-definitions references to new org

STONEBLD-2339
The build-definitions repo has moved from github.com/redhat-appstudio to
github.com/konflux-ci. Update references accordingly.
Signed-off-by: Adam Cmiel<EMAIL_ADDRESS>

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

Please upload report for BASE (main@7caf512). Learn more about missing BASE report.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #738   +/-   ##
=======================================
  Coverage        ?   72.12%
=======================================
  Files           ?       42
  Lines           ?     4015
  Branches        ?        0
=======================================
  Hits            ?     2896
  Misses          ?      818
  Partials        ?      301

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

gitlint passed but somehow status report stuck, merged by force


DevFest Stockholm 2023

Adding DevFest Stockholm 2023 as per README.

And it's deployed! Enjoy the devfest :)
If you ever want to update the data, you can do so with
curl --data "" https://confetti-app.dev/update/devfeststockholm2023


Introduce the concept of 'null objects'

Automated message from Dropbox CLA bot
@borisyankov, it looks like you've already signed the Dropbox CLA. Thanks!


[1.2] Backport Changes into 1.2

Description
Backport the copyright header and codeowners support PRs into 1.2
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[x] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #228 (507299e) into 1.2 (1fdbadc) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##                1.2     #228   +/-   ##
=========================================
  Coverage     64.54%   64.54%
  Complexity      294      294
=========================================
  Files            97       97
  Lines          4045     4045
  Branches        620      620
=========================================
  Hits           2611     2611
  Misses         1293     1293
  Partials        141      141

Flag
Coverage Δ

dashboards-reports
74.86% <ø> (ø)

reports-scheduler
54.57% <ø> (ø)

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

Impacted Files
Coverage Δ

dashboards-reports/common/index.ts
100.00% <ø> (ø)

...main/__tests__/__utils__/main_utils_test_utils.tsx
100.00% <ø> (ø)

...ic/components/main/loading_modal/loading_modal.tsx
75.00% <ø> (ø)

dashboards-reports/public/components/main/main.tsx
57.84% <ø> (ø)

...ards-reports/public/components/main/main_utils.tsx
74.28% <ø> (ø)

...t_definition_details/report_definition_details.tsx
70.87% <ø> (ø)

...ublic/components/main/report_definitions_table.tsx
92.59% <ø> (ø)

.../components/main/report_details/report_details.tsx
73.73% <ø> (ø)

...s-reports/public/components/main/reports_table.tsx
90.00% <ø> (ø)

...omponents/report_definitions/delivery/delivery.tsx
31.19% <ø> (ø)

... and 87 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 1fdbadc...507299e. Read the comment docs.

Closing to create a new PR without the code owners PR and DCO check failure


Run a JavaScript linter on the code

Someone copied venn.js into a project and it started getting covered with ESLint that we use in our test pipeline. The linter pointed out that there's an undefined variable here: https://github.com/benfred/venn.js/blob/master/venn.js#L935
We'll import the module with npm as should have been done initially, but just want to point out that undefined variable could be a problem. Maybe it's not right now because the classicMDSLayout function gets never gets called?

Thanks for the heads up, I should probably just remove this function from the package. I'll at least patch this on the weekend so it passes eslint w/ no-undef enabled).
I think I only left it so I could easily run the comparison perf tests here http://www.benfrederickson.com/better-venn-diagrams/ (which show that the classic MDS code just doesn't work that well).

I've removed that function here: https://github.com/benfred/venn.js/commit/7b1f8c37b720abad4d8890b84d7f1db53f3ddd22
I also added a basic eslint config file there too, and verified the code in src/*.js passes (though didn't yet add to travis-ci, which still only runs jshint and the unittests).


Economy commands?

Hey Suvanl, I find your work on delet 3 pretty decent!
Would you add an economy system to it? Like, an item shop that changes every week, daily rewards with streak and more. It would be cool to see that! If possible, I would love to help you with that!

Hi, thank you!
An economy system as per your suggestion sounds like a really fun addition.
A basic points system already exists, where users get a random number of points (between 10 and 20) whenever they send a message within a specified cooldown period. So, we could use these points as the currency for the item shop in the economy system.
Do you happen to have any suggestions on how this could be implemented? Any help would be much appreciated, of course! :)

Sure, if you want to we can talk about it on Discord, my username is Shin#0484. (:

actually, I have an idea for thing if I can share :)

Of course! Feel free to outline your idea(s) here or let me know if you'd rather discuss it on Discord.

lets discuss on discord. you can add me @ DVG#6945


fix: select dropdown given bg-white color in reports

Description
This PR fixes #1568
I have followed what is being done in other Select components and added "bg-white" className to remove the transparent background.
The same pattern is being followed in components\molecules\SelectReportsFilter\select-reports-filter.tsx, pages\start.tsx and more files.

What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[x] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings

Before

After

Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[x] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

🥲🥲🫠


an npm package is able to break core functionality (Linking.getInitialURL promise never resolves)

Description
There is a npm package (json-api-normalizer) that is able to break core functionality. Just by importing it the Linking.getInitialURL() promise never resolves. I suspect the change in this commit this commit breaks this because it works with 1.0.1 but not >1.0.2. I'd like to know exactly what the problem is so that I can work with the package maintainer to fix this.
React Native version:
info Fetching system and libraries information...
System:
    OS: macOS 11.4
    CPU: (6) x64 Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz
    Memory: 434.93 MB / 64.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.15.4 - ~/.nvm/versions/node/v14.15.4/bin/node
    Yarn: 1.22.4 - ~/.nvm/versions/node/v14.15.4/bin/yarn
    npm: 6.14.10 - ~/.nvm/versions/node/v14.15.4/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.10.1 - /Users/aforty/.rvm/gems/ruby-2.7.1/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.5, DriverKit 20.4, macOS 11.3, tvOS 14.5, watchOS 7.4
    Android SDK:
      API Levels: 23, 24, 25, 26, 27, 28, 29
      Build Tools: 27.0.3, 28.0.3, 29.0.2, 29.0.3, 30.0.0, 30.0.3
      System Images: android-30 | Google APIs Intel x86 Atom, android-30 | Google Play Intel x86 Atom
      Android NDK: 22.1.7171670
  IDEs:
    Android Studio: 4.2 AI-202.76<IP_ADDRESS>22048
    Xcode: 12.5/12E262 - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_144 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.1 => 17.0.1
    react-native: 0.64.1 => 0.64.1
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

Initialize: npx react-native init JsonApiNormalizerBug && cd JsonApiNormalizerBug && yarn add json-api-normalizer
Replace App.js with the code below.
Run: npx react-native run-ios
Notice didFinish never turned true and thus it says Linking.getInitialURL() is loading.
Notice if you comment out the first line (import json-api-normalizer) then the promise resolves correctly.

// App.js

import normalize from 'json-api-normalizer';
import React, {useEffect, useState} from 'react';
import {Linking, SafeAreaView, Text, View} from 'react-native';

export default function App() {
  const [didFinish, setDidFinish] = useState(false);

  useEffect(() => {
    Linking.getInitialURL()
      .then(() => setDidFinish(true))
      .catch(() => setDidFinish(true));
  }, []);

  return (
    <SafeAreaView>
      <View>
        {didFinish ? (
          <Text>Linking.getInitialURL() finished.</Text>
        ) : (
          <Text>Linking.getInitialURL() is still loading.</Text>
        )}
      </View>
    </SafeAreaView>
  );
}

Expected Results
A compiled npm package should not be able to break react-native in this way.
If it's not a problem in react-native or unable to fix, what is should the package maintainer do to remedy this?

Also have this issue after upgrading React Native from 0.63.4 to 0.64.1, not knowing any specific NPM package, just all Promises never resolve, would it be something missing during the upgrade?

I experienced a similar issue after upgrading from 61.5 to 64.2, no promises in my app would resolve. I tracked the issue down to the change in metro.config.js (new file) - if I change inlineRequires back to false, the issue with the promises goes away.
I assume there is some conflict between one of my dependencies and the way inlineRequires works. As its only a performance optimisation I'm just going to leave that turned off for now, but would be good to understand why that's happening.


Imperative handle of input component

TuSimple/naive-ui version (版本)
2.34.3
Vue version (Vue 版本)
3.2.45
Browser and its version (浏览器及其版本)
109.0.5414.120
System and its version (系统及其版本)
Windows 10 Home
Node version (Node 版本)
v18.13.0
Reappearance link (重现链接)
https://github.com/GILREICH1/bali-bot-client/blob/main/src/views/HomeView.vue
Reappearance steps (重现步骤)
type into input. press enter to submit.
Expected results (期望的结果)
input should be focussed
Actual results (实际的结果)
input not focussed.
Remarks (补充说明)
Trying to imperative focus on input element. handleFocus() function runs but inputInstRef.value?.focus() does not focus input. Using template from here: https://www.naiveui.com/en-US/light/components/input#focus.vue

Record: Maybe the same problem as #4454

This issue does not have any recent activity. If you are still experiencing similar problems, open a new error, including a minimal copy of the problem


Feature request: Option to disable Kubernetes in Docker Desktop

Docker Desktop supports shutting down a Kubernetes cluster, which is useful when you don't need it. The cluster can then be brought back up again, with the data intact.
ctlptl docker-desktop don't currently seem to have that option.
It would be nice with a command such as ctlptl docker-desktop {disable|enable}-cluster (or {pause|upause}).

I think you can do this with:
ctlptl docker-desktop set kubernetes.enabled false

?
Tho we should add that to the docs

Ah, that works for me, thanks!
I'll change this issue to be a doc task then, so it can be closed once documented. Hope the maintainers agree. 🙂


fix(dependencies): upgrade to next majors

Current dependencies on/for this PR:

main

PR #18   👈

This comment was auto-generated by Graphite.


DFBUGS-942: csi: provide delete access to csiaddonsnode

Checklist:

[ ] Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
[ ] Reviewed the developer guide on Submitting a Pull Request
[ ] Pending release notes updated with breaking and/or notable changes for the next minor release.
[ ] Documentation has been updated, if necessary.
[ ] Unit tests have been added, if necessary.
[ ] Integration tests have been added, if necessary.

/assign @Madhu-1 @sp98


数据平面: concepts/data-plane.md

This article is waiting to be claimed. concepts/data-plane.md

/accept

#189

update: 数据平面: concepts/data-plane.md  #189

/delay-reset

/pushed

/merged


[5.9][Macros] Update plugin search options serialization

Cherry-pick #66689 and #66722 into release/5.9

https://github.com/apple/llvm-project/pull/7011
@swift-ci Please test

Does this affect any of the LLDB deserialization code in https://github.com/apple/llvm-project/blob/e2b11c251e5ef2be08e2b10bf4f0421308dcb871/lldb/source/Plugins/TypeSystem/Swift/SwiftASTContext.cpp#L1285 ?

@adrian-prantl Yes, https://github.com/apple/llvm-project/pull/7011 is the corresponding change.

https://github.com/apple/llvm-project/pull/7011
@swift-ci Please test


recent images still not published to container-registry.oracle.com?

Will there be new images or is everyone expected to build their own? I don't mind but if that is the case you should just remove all the images rather than have stale ones.

It's easier to build your own (and you get to tweak it to your own needs). The levels of approvals required to publish Oracle binaries on a (relatively) free-to-download site like the Container Registry are immense, as I'm sure you can imagine.

Is there a more protected site for license holders that has published images? I'd like to validate with a known standard well used image before I create my own.

Not that I know of, which is why we built our own.

Just saw other response, I'll get an SR raised and see where that goes. Thanks


MM-40306 : Investigate removing XRegExp

Summary

[X] Replace XRegExp.cache in components/suggestion/at_mention_provider/at_mention_provider.jsx
[X] Replace XRegExp.cache in utils/text_formatting.tsx
[x] Replace XRegExp.replace in utils/text_formatting.tsx
[x] Add updated mattermost-marked with removed XRegExp library to package.json

Ticket Link
https://mattermost.atlassian.net/browse/MM-40306
Related Pull Requests
https://github.com/mattermost/marked/pull/21
Screenshots
N/A
Release Note

Removed and replaced "XRegExp" dependency with native RegEx.

@larkox yes i will look at the blame and check. Also i am talking with @michelengelen his suggestion is to replace the email regex with

/update-branch

/e2e-test

Triggering e2e testing with options:
<nil>

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/157824

📂 E2E test report 📂
https://automation-dashboard.vercel.app/cycles/d06a8aad-b9a3-449e-8380-57829b359bc6

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/157962


[material-ui][Autocomplete] Required field validation is not working

Search keywords
Autocomplete, Required
Latest version

[X] I have tested the latest version

Steps to reproduce
There are two scenarios

If the autocomplete is for single select then I was giving the required filed to text field and it was working fine (because there was the text which we have searched).
If the autocomplete has the prop 'multiple' then giving required to text field will create an issue and will always show the text field as empty and block submit even if the option is selected.

so due scenario 2, is it possible to give required props for autocomplete instead of text field which will be even more meaningful for the application
Current behavior
Required validation not working as expected
Expected behavior
Required validation  expected to work as normal dropdown
Context
No response
Your environment

npx @mui/envinfo

@Shreyas-sonu Would you mind providing a reproduction (or demo) of the issue(s) you are describing? You can fork this template: https://mui.com/r/issue-template-latest

https://ldssgv.csb.app/
you can see the end use sample of the issue here

waiting for your response.... do you need any further description??

Duplicate of #21663. The solution is to do https://github.com/mui/material-ui/issues/21663#issuecomment-732298594.


HDDS-10111. TestListKey: Add new test cases for OFS mode.

What changes were proposed in this pull request?
Add new test cases for OFS mode.
What is the link to the Apache JIRA
HDDS-10111.
How was this patch tested?

local test
CI test: https://github.com/TaiJuWu/ozone/actions/runs/7677750808

@adoroszlai Could you take a look?
I'm not sure this CI test is related to this PR.

@adoroszlai When I try adding test for object store in this commit[https://github.com/apache/ozone/pull/5982/commits/3446af764e16bf47e76096065e1ed4930df7b7fb].
These results always show empty, is it excepted? or it's an issue?

results always show empty

can you please clarify which results you refer to?

results always show empty

can you please clarify which results you refer to?

My exception is no matter use Legacy mode or object store mode.
The results of testListKey should be same.
For example, in this testcase the results of both should be same, but in object store mode its results is [].
Expected :[a1/b2/, a1/b2/d1/, a1/b2/d2/, a1/b2/d3/]
Actual   :[]

My exception is no matter use Legacy mode or object store mode. The results of testListKey should be same. But all testcases for object store mode, all results are empty list.
For example, in this testcase the results of both should be same, but in object store mode its results is [].
Expected :[a1/b2/, a1/b2/d1/, a1/b2/d2/, a1/b2/d3/]
Actual   :[]

@sadanand48 can you please help with this?

The problem here is during creation of keys we have a slash at the beginning of all keys
  private static void buildNameSpaceTree(OzoneBucket ozoneBucket) throws Exception {
    LinkedList<String> keys = new LinkedList<>();
    keys.add("/a1/b1/c1111.tx");
    keys.add("/a1/b1/c1222.tx");
    keys.add("/a1/b1/c1333.tx");

FSO and legacy(fsenabled=true by default)  normalize the initial slash and store only the after-paths like vol/buck/a1/b1 in the
DB however in the OBS case the initial slash is also stored like vol/buck//a1/b1/.
This is causing an issue during listKeys as the seek-key that is getting constructed is vol/buck/a1/b1 and there is no such key present in the table thereby returning an empty list. When we do a listKeys we should provide initial slash only then will it get the proper results.
One solution if we want all to test this against all bucket types  is in the creation is to  remove the initial slashes of all keys.

The problem here is during creation of keys we have a slash at the beginning of all keys
  private static void buildNameSpaceTree(OzoneBucket ozoneBucket) throws Exception {
    LinkedList<String> keys = new LinkedList<>();
    keys.add("/a1/b1/c1111.tx");
    keys.add("/a1/b1/c1222.tx");
    keys.add("/a1/b1/c1333.tx");

FSO and legacy(fsenabled=true by default) normalize the initial slash and store only the after-paths like vol/buck/a1/b1 in the DB however in the OBS case the initial slash is also stored like vol/buck//a1/b1/. This is causing an issue during listKeys as the seek-key that is getting constructed is vol/buck/a1/b1 and there is no such key present in the table thereby returning an empty list. When we do a listKeys we should provide initial slash only then will it get the proper results. One solution if we want all to test this against all bucket types is in the creation is to remove the initial slashes of all keys.

Got it. Thanks for your answer. Can this issue can be fix by modifying OBS layout?
@adoroszlai Could you take a look this PR?
This PR is not related above question.
If you need to fix above issue I mentioned, maybe we can open another Jira.

@devmadhuu please review

@TaiJuWu , Pls remove System.out if not needed.

Done.

/pending conflicts

@TaiJuWu can you please resolve conflicts?

Done.

/ready conflict resolved

@sadanand48 can you please take another look?

/pending review items


Direct use await whitout async function

Hi, what possibilities exist to be able to use the await operator without the use of async?,
as it is currently done in javascript.
Example in actual javascript
const prom = new Promise((r)=> {r('Running whitout without async 🏄
')});
await prom // Running whitout without async 🏄
Regards!

as it is currently done in javascript.

@Hume83 do you mean what the node repl or chrome console does? There is some special treatment for top level await.
In regular JavaScript and TypeScript this is not valid. You can try it yourself by saving the code snippet to a file and execute that file with node.

You are right, excuse my ignorance, I have tried it fast in the console, it would be a really great feature, to avoid the unnecessary use of async function in some cases. Could this feature be available in the future of ECMAScript?
Thanks for your answer mate.


Autocomplete: Add class templates and FoundItemsCount (and improve docs mobile search dialog)

Description

Originally discussed at https://github.com/MudBlazor/MudBlazor/pull/8276#issuecomment-1987849744
Autocomplete
Exposes a FoundItemsCount property that lets consumers subscribe to the actual number of search results to allow finer control than just the templates.
Adds classes to the divs surrounding AfterItemsTemplate, BeforeItemsTemplate, MoreItemsTemplate, NoItemsTemplate for customizability. Other templates weren't included to avoid breaking changes.
Docs
Utilizing the new API, the mobile search panel now shows different messages depending on the context:
Before

After

and isn't visible behind the search results:
Before

After

and the scrollbar was naturally eliminated:
Before
https://github.com/MudBlazor/MudBlazor/assets/7112040/cc6c19fe-73b5-42ec-b8bf-a7644782e334
After
https://github.com/MudBlazor/MudBlazor/assets/7112040/625401f8-41fe-4e24-be96-efc1e2c5a4c2
And it now focuses the search box
https://github.com/MudBlazor/MudBlazor/assets/7112040/d5bdec25-694b-4e61-ab46-843be892289b
How Has This Been Tested?

unit, visually
Types of changes

[X] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

See above
Checklist:

[X] The PR is submitted to the correct branch (dev).
[X] My code follows the code style of this project.
[X] I've added relevant tests.

Initially this PR was about improving the docs search box, but it has become an improvement of MudAutocomplete.
That's why removed the docs label again because I fear with it the PR might not be added to the release change log.

Shouldn't it have [Parameter] attribute?
https://github.com/MudBlazor/MudBlazor/blob/9de9ae1454573c675d0b29cf3296b18da315b161/src/MudBlazor/Components/Autocomplete/MudAutocomplete.razor.cs#L370-L371
since we have this
https://github.com/MudBlazor/MudBlazor/blob/9de9ae1454573c675d0b29cf3296b18da315b161/src/MudBlazor/Components/Autocomplete/MudAutocomplete.razor.cs#L360-L361
so I assume it's two way bindable? But yet I see the setter is private

How's it looking now? @henon @ScarletKuro
I also changed it to "returned items" to match the rest of the code/docs

I have often thought the search box should auto focus but never gotten around to doing it. Thanks a lot!

@henon So the autofocus works great when I debug the docs (including on my actual phone, not a simulator), and yet it doesn't seem to work on mudblazor.com on my phone. Do you see this too?

Yes, I noticed. I just tried with Chrome on Desktop and it doesn't work for me.

Yes, I noticed. I just tried with Chrome on Desktop and it doesn't work for me.

@henon I think there's something wrong with dialog focus in general because look at https://mudblazor.com/components/dialog#focus-trap:
It doesn't focus the last button until you click another key liked caps lock or shift.

Maybe #8424 fixes it?
Also related: #8366


fix(input-item): limit the length of characters entered by the virtual keyboard

背景描述

当使用虚拟键盘向InputItem输入字符时，maxlength无法限制字符长度。
ps: 初始化赋值已限制字符长度
主要改动

在键盘输入事件时增加字符长度校验
需要注意

无

Codecov Report

Merging #525 into dev will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##              dev     #525      +/-   ##
==========================================
+ Coverage   81.13%   81.15%   +0.01%
==========================================
  Files          91       91
  Lines        2720     2722       +2
  Branches      521      522       +1
==========================================
+ Hits         2207     2209       +2
  Misses        367      367
  Partials      146      146

Impacted Files
Coverage Δ

components/input-item/index.vue
95.03% <100%> (+0.07%)
:arrow_up:

Continue to review full report at Codecov.

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


Create App Icon Image

Need to design and apply an app icon image for Budgy.

https://github.com/austin03/Budgy/pull/25


fix(specs): ingestion cursor for task

🧭 What and Why
🎟 JIRA Ticket: -
Changes included:
leftover of the cursor field

Seems like we are in a bad random streak and we only target failing Apple servers


fix(select): do not close the dropdown after selecting when popup bind to itself

Types of changes

[ ] New feature
[x] Bug fix
[ ] Enhancement
[ ] Component style change
[ ] Typescript definition change
[ ] Documentation change
[ ] Coding style change
[ ] Refactoring
[ ] Test cases
[ ] Continuous integration
[ ] Breaking change
[ ] Others

Background and context
fix #2564
Solution
如果挂到 <a-select> 自己，会导致用户选择后触发 MouseEvent，而正常情况下不会。
观察到 MouseEvent 的 target 是点击的选项，所以在处理 MouseEvent 时判断 target 是否 popup 的子节点。
如果是子节点，说明点击事件发生在 popup 中，也就是点击了选项，那就应该 changeVisible(false)。
如果不是子节点，说明一切正常。
How is the change tested?
see #2564
Changelog

Component
Changelog(CN)
Changelog(EN)
Related issues

select
修复 popup-container 绑定到自己时选择后不隐藏的 bug
fix the bug of not close the dropdown after selecting when popup bind to itself
#2564

Checklist:

[x] Test suite passes (npm run test)
[x] Provide changelog for relevant changes (e.g. bug fixes and new features) if applicable.
[x] Changes are submitted to the appropriate branch (e.g. features should be submitted to feature branch and others
should be submitted to main branch)

功能测试通过


Only 1 node displayed for threadripper CPUs

When using Zenmonitor it only displays the temps, voltages and from only one threadripper node.
the output from sensors
`zenpower-pci-00c3
Adapter: PCI adapter
SVI2_Core:    +1.00 V
SVI2_SoC:     +0.01 V
Tdie:         +35.6°C  (high = +70.0°C)
Tctl:         +62.6°C
SVI2_P_Core:  60.27 W
SVI2_P_SoC:    0.00 W
SVI2_C_Core: +60.27 A
SVI2_C_SoC:   +0.00 A
zenpower-pci-00cb
Adapter: PCI adapter
SVI2_Core:    +1.36 V
SVI2_SoC:     +0.01 V
Tdie:         +33.9°C  (high = +70.0°C)
Tctl:         +60.9°C
SVI2_P_Core:  14.10 W
SVI2_P_SoC:    0.00 W
SVI2_C_Core: +11.43 A
SVI2_C_SoC:   +0.00 A
`
what you see in zenmonitor

Thanks for your report, I will look at it.

@terroreek Commit 1d8cfab2924b937059fab9a15a94af410772234d should fix that. Could you try it again?

Yep working now!

I just noticed.  Don't know how I missed it.  The labels for the Tdie and Tctrl Nodes are swapped for the correct values.  Zenpower driver has them correct in sensors, but Zen Monitor does not.
The screen image in the previous post shows it too.  Here is my screen shot.


DNM Np 6778/context changes auth n crunch service

start update for using Auth.sudo when we are updating a context to a different user...

@Nauna can you think of reason to not set the group by default? So sudo(x, user) calls -> sudo(x, user, user.findGroup(x))

no not really - I like this simplification ... I'll quickly go through the other calls in the code see if there is anything Im missing then make this update...30 min - moving pr to dnm

one comment - rest lgtm


Test on prereleases in the development version tests

Summary
Previously, this workflow tested with the latest git versions of all Qiskit packages and the most recent stable release of all other packages.  This changes it to test on any eligible prerelease versions of the other packages, so that we can catch potential breakage from other sources sooner.
Details and comments

The build failure sure looks like https://github.com/yaml/pyyaml/issues/601.  The log on Actions doesn't mention installing Cython anywhere, so I can't be sure.  And everything works for me locally.


Fix #1036, Clear task data in EarlyInit and standardize name

Describe the contribution
Fix #1036 - explicity memset the task data to zero at the start of EarlyInit.  Also standardizes the global typdef/variable names.
Might need a rebase based on the name changes.
Testing performed
Build and run unit tests, passed.
Expected behavior changes
None.
System(s) tested on

Hardware: cFS Dev Server
OS: Ubuntu 18.04
Versions: Bundle main + this commit

Additional context
TBL global depends on CFE_TBL_Global.TableTaskAppId being set, which doesn't happen until the app starts (in CFE_TBL_InitData), so replaced where CFE_TBL_EarlyInit was being called to initialize the data with the test initialization function Test_CFE_TBL_ApiInit.  In the future these tests could be cleaned up by calling the initialization before each test, and ensuring there are no test configuration dependencies across tests.
Third party code
None
Contributor Info - All information REQUIRED for consideration of pull request
Jacob Hageman - NASA/GSFC

Rebased and updated SB global name (finished work).

Rebased and updated SB global name (finished work).

CCB:2021-01-27 APPROVED

There were two services that did the memset zero, this standardizes the practice
Makes global variable names consistent as: SERVICENAME_Global
Simplifies initialization
tbl_UT.c needs cleanup since they depend on the order of how things are set up

CCB:2021-01-27 APPROVED

There were two services that did the memset zero, this standardizes the practice
Makes global variable names consistent as: SERVICENAME_Global
Simplifies initialization
tbl_UT.c needs cleanup since they depend on the order of how things are set up


Better name

I'm thinking basis could use a better name, like mungulate, banzale, or spingy. These are all random names.
There could also be:

khiikh (Mongolian for 'do, make, commit or undertake')

Tentatively, "guh"


vendor: Vendoring update

Signed-off-by: Samuel Ortiz<EMAIL_ADDRESS>

Coverage remained the same at 38.264% when pulling c29bf11f443c97d165d6ce8c522b0f564420a48b on topic/vendoring-pruned into 4648b7619296f4073933408bd504ffaf116408eb on master.

Coverage remained the same at 38.264% when pulling c29bf11f443c97d165d6ce8c522b0f564420a48b on topic/vendoring-pruned into 4648b7619296f4073933408bd504ffaf116408eb on master.

lgtm


Why does problems.solve() return None when status is not optimal?

Just curious since there is additional information about what did not work in the cobrapy Solution object that could be returned. Or does it just not make sense to return a CommunitySolution object when the optimization did not work? I'm most interested in knowing what the solver status is.

Mostly because it can not run pFBA because there is no defined optimum and CommunitySolution also will choke if there are no optimal growth rates. Maybe would be better to raise an exception? Access to the solver object is still possible via Community.solver, for example community.solver.status will get you the optimization status. In my experience this usually fails if you define a minimum growth rate for one of the organisms that can not be achieved (in Community.optcom this defaults to 0.1 which I think I should change). For instance calling com.optcom(min_growth=0.0) usually fixes those problems...

That makes sense. I found what I was looking for in community.solver.status.
Maybe you could add a raise_error parameter and raise an OptimizationError when parameter is set to True.

Yeah that makes sense. Will reopen so I don't forget to make the changes...

Managed internally now by the workflows.


Update LA release branch to latest from main

Optimistically merging in so I can get a build kicked off - that'll run all the tests anyways.


Support to Delete VC

Currently, there is no support to delete the VC in user wallet. This would be helpful while verifying different scenario. As a work around, currently we login with different users.

This has been implemented in wallet.


feature(UXD): Add Markdown Supported text, update Description interactions

The Description interactions needed to be improved in order to allow users to see the full context of the Description, without scrolling. Additionally, in order to properly show the user that markdown is supported, the correct text needs to be added below the textarea.

Can one of the admins verify this patch?

[test]


Check Point CSPM Permissions fix

Describe the Issue
Some permissions are not being granted based on SCPs, but Check Point have given us some details that may fix the issue.
Additional Context
https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps_examples_general.html#example-scp-deny-region
specifically:
                "ArnNotLike": {
                    "aws:PrincipalARN": [
                        "arn:aws:iam::*:role/Role1AllowedToBypassThisSCP",
                        "arn:aws:iam::*:role/Role2AllowedToBypassThisSCP"
                    ]
                }

Acceptance Criteria

[ ] Made change in Forge based on CheckPoint feedback
[ ] Verify change in CSPM

@prabhukiran9999


[LiveComponent] LiveCollectionType does not play well without block prefix

As soon as the form type returns an empty block prefix, LiveCollectionType fails to add or remove an item in the collection:
Cannot read property "items" from an array. Maybe you intended to write the property path as "[items]" instead.
That's because the property path for the action becomes addCollectionItem(name=items) instead of addCollectionItem(name=todolist[items]).
Should it be supported out of the box?
Reproducer: https://github.com/norkunas/sfux-tests/tree/live-form-dto-collection

Thanks for the reproducer. Should be fixed by #717


Type Cleanup

Description
Please include a summary of the change relevant motivation and context. Explicitly list any dependencies that are required for this change.
Issues:
closes #51
closes #50
Resolutions

[x] Deprecate BaseModel base class abstractions and merge features into StateModel
[x] Deprecate _T type generic in State context manager API for StateModel
[x] Added copyright lines on all core lib files.

Codecov Report
Base: 97.77% // Head: 97.69% // Decreases project coverage by -0.08% :warning:

Coverage data is based on head (d01fb5a) compared to base (4b8f247).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #52      +/-   ##
==========================================
- Coverage   97.77%   97.69%   -0.09%
==========================================
  Files           8        7       -1
  Lines         225      217       -8
  Branches       30       29       -1
==========================================
- Hits          220      212       -8
  Misses          4        4
  Partials        1        1

Impacted Files
Coverage Δ

myosin/exceptions/cache.py
100.00% <ø> (ø)

myosin/exceptions/state.py
100.00% <ø> (ø)

myosin/models/state.py
100.00% <100.00%> (ø)

myosin/state/state.py
96.05% <100.00%> (-0.06%)
:arrow_down:

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

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


fix(sec): upgrade org.elasticsearch:elasticsearch to 6.8.17

What happened？
There are 6 security vulnerabilities found in org.elasticsearch:elasticsearch 2.4.4

CVE-2020-7020
CVE-2021-22144
CVE-2020-7021
CVE-2021-22137
CVE-2021-22135
CVE-2019-7614

What did I do？
Upgrade org.elasticsearch:elasticsearch from 2.4.4 to 6.8.17 for vulnerability fix
What did you expect to happen？
Ideally, no insecure libs should be used.
The specification of the pull request
PR Specification from OSCS

Probably needs some code change.
https://app.travis-ci.com/github/apache/storm/jobs/585564257 line 6680
Error in external/storm-elasticsearch/src/test/java/org/apache/storm/elasticsearch/common/EsTestUtil.java:[56,30] cannot find symbol
Breaking change with NodeBuilder: https://www.elastic.co/guide/en/elasticsearch/reference/5.5/breaking_50_java_api_changes.html

This needs more work. As the PR is stale for > 1y now, I am going to close it. Feel free to re-open.


Document experimental features

Async functions
Virtual properties
Private declarations
Async iterators

Not worthwhile unless there are other using this tool for non-experimental uses.


Single click a file, open and replace current active tab

I can not configure Visual Studio Code in a way, that when single clicking on a file in the file explorer of the project, it just opens the file in the currently active tab.
I did not find any extensions that give me that feature.
Single click open file has been setup by the following configuration.
"workbench.list.openMode": "singleClick",

I know there are Preview-tabs. But it opens in a new tab. That creates a problem that the tab vanishes when in Preview.
When I do not use Preview-tabs I get many open tabs after clicking some files, for example when checking or searching for something.
My main use case for me when using the project explorer: Switching to another file without opening new tabs. I have the navigation buttons for going back. I mainly use Xcode and it would be nice to mimic its behavior: Single click to replace current tab with the file you clicked on, double click to open file in new tab.

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

better file opening & preview (#77338)

No that is not nearly the same. It was a bug.

@bpasero not sure if it can be configurable to always be opened in the same tab.
Why don't you just disable tabs? That seems to be what you want
"workbench.editor.showTabs": false
As for your original question forwarding to @bpasero to answer

Single click to replace current tab with the file you clicked on, double click to open file in new tab.

How is that not covered by our default preview feature?

I think if you have an all non preview tabs and you open one in preview it goes into a new tab

@BinaryHammer is that it?

Having no tabs is not an option. Tabs are very useful.
@isidorn It opens in a Preview tab, not a normal tab. That means it will vanish if I change to another tab and single clicking again on an unopened file.
@bpasero No. The default feature is to open a Preview tab. A preview tab will vanish. Opening a file in with a single click will create a Preview tab, when I click on another tab and then on a file which is not yet open, the previous selection vanishes. Having the feature to replace the current tab with a single click will never vanish the tab while in another tab.
As I said, it is the default behavior of Xcode. This way I can have tabs open which represent different content and switch the content without affecting anything else but the one tab. For example every tab is for one depth or type in an architecture: One tab is for assets, one for view, one for the Controller, one for the database, while having multiple of each. If I have three controllers for a view and I am not sure in which one.
I know I could just use the preview tab, like I could just disable tabs, like I could just use no IDE at all. For my workflow, which I used and use with Xcode successfully for many years now, this feature would be beneficial for the Web Development I do more and more. Since there are many Xcode users and with the introduction of Swift on the server possible much more in the Web World, I could imagine it may be a good idea to have an option to mimic this behavior.

@BinaryHammer please explain to me how your suggested feature would work exactly, e.g. with an example where you talk about a set of files you click on one after the other. Explain how tabs are being created or not.

@bpasero Thanks for your interest. Let's say I open a project and have no files open and having some CSS, JS, PNGs and HTML files.
Example workflow where the feature would be included:
I open a project: No tabs open. Since it does not make sense for me having no tab open I immediately would just open the main HTML file with a double click. Now I have 1 tab open. That was maybe the wrong HTML file, so I single click on a specific HTML file: Still 1tab open, but the file of the tab is now the specific HTML file. Then I want to update some images. Double click on an image to open a new tab (in my head this is now my image tab): 2 tabs open, one with a HTML file one with a PNG file which is active. Since I am not sure how the images are named I just single click one some images and every time the file of the active tab will be changed to the new image: Still 2 tabs open. I single click on the HTML tab and add the path of the images I am interested in. Now I need to update a JS file. There are multiple connected to the active open HTML file. I double click on the JS file I thought would include the functionality: 3 tabs open, JS-file tab is active. But then I realize it should be in the other JS-file, I single click the other JS file and the current tab will now show the content of the new JS file. And so on.
Benefit:
If I want to have a tab for only the current image I am interested in, but do not want to manage more than one tab for it. There is a One-to-one relationship as the tabs I see, but a more complex one-to-many in the files. I want to work on a simplified view . It is easy when this feature would be included. I could just go to the image-tab select and search through the images by clicking through and am done. Every time I need to look at the current interesting image. No new tabs, no preview tabs, no tabs to close or change I have to worry about.
Feature:
Single clicking a file in the Project Explorer and if a tab is open and active would select the file in the Project Explorer and set the active open tab to the new file. So when index.html is open and active in a tab and I single click on contact.html, contact.html will be selected in the Project Explorer and the file in the active tab will be now contact.html. No new tabs.
Easiest way to understand would just be to try out Xcode.

Thanks I understand this now.


Minor fixes to the README.md

Codecov Report

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

@@            Coverage Diff            @@
##             master     #544   +/-   ##
=========================================
  Coverage     27.46%   27.46%
  Complexity      970      970
=========================================
  Files            88       88
  Lines          3331     3331
=========================================
  Hits            915      915
  Misses         2416     2416

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 7bce226...106828f. Read the comment docs.


Documentation is lacking for repo-side config

Hiya!
My perspective is perhaps a little strange, as at this stage I'm not interested in using dep to manage dependencies for my applications. The documentation does seem to cover that side of things!
In my case I've written a library which is currently following "stable-head" philosophy and has zero "releases" so far. But I have a change coming up which requires breaking the API. I want to provide tools for my users to manage this, so I came to try and figure out best practices for versioning a library to play well with dep.
So far it's apparent that semver is the way to go - here's what I'm not clear on:

Does each X.Y.Z version need to correspond to a vX.Y.Z repo tag? Can it be a repo branch?
If it must be a tag, can the tag move?

I guess my conundrum is that if I cut a version-2 tag when I break the API, then users requesting version 2 will be stuck on that commit even after I push updates, unless I continue to make new tags incrementing minor/patchlevel. With my current style of development, that would basically mean a new tag for every commit which seems silly.
It seems like dep allows branches in some contexts (eg. master) so I'm hoping that provides a way forward for me to continue with a stable-head style while clearly identifying breaking changes. But the documentation is vague as to how the candidate versions are derived from the target repo.

Dep was officially deprecated earlier this year, and the proposal to archive this repository was accepted. As such, I'm closing outstanding issues before archiving the repository. For any further comments, please use the proposal thread on the Go issue tracker. Thanks!


Refactor: remove impl Module for Box<dyn Module> in codebase

Details
See context at https://github.com/web-infra-dev/rspack/discussions/2762
Guidance

Remove following code

https://github.com/web-infra-dev/rspack/blob/2c4c1daf81d388cd4fc0b54049d9e2a762e34418/crates/rspack_core/src/module.rs#L149-L193

Fix all errors

PS:
Take this code as an example
https://github.com/web-infra-dev/rspack/blob/2c4c1daf81d388cd4fc0b54049d9e2a762e34418/crates/rspack_core/src/module_graph/mod.rs#L162-L165
There's no need for returning Box<&dyn Module> due to no use cases(so far) caring about the Box in Box<&dyn Module>. Returning Option<&dyn Module> would be enough.
The argument also applies to using &BoxModule in function parameters. So, we just need to replace all &BoxModule with &dyn Module, which would also achieve the goal: reduce boilerplate code for deref Box and avoid the traps mentioned above.
What does the proposed API of configuration look like?
.

Opened a PR for this https://github.com/web-infra-dev/rspack/pull/2831


cwp.py doesn't append to the PATH  C:\Users..\anaconda3\envs\my-env\bin... Should Spyder be looking for LIBIOMP5MD.DLL there?

Not sure if this is a bug... For sure I would not try to repeat this, but somehow after first failing with broken environments but then finally succeeding in updating to conda python 3.10 and latest Spyder 5.4.3 I found myself in the state where Spyder would launch perfectly from my environment, but would crash immediately if launched from the Start Menu. This all on Windows 10. The error message in Event Log pointed me to KERNELBASE.DLL, but that turned out to be a red herring.
If I copied the start menu command and typed it into an Anaconda terminal, then Spyder would launch. If I copied that start menu command into a regular terminal, then Spyder would immediately die with the same KERNELBASE.DLL error reported to the Event log. After hacking around in PDB, I found that the environment being created by CWP.PY was not quite the same environment that did work, specifically it was missing the ....\my-env\bin folder, which has in it LIBIOMP5MD.DLL
I changed CWP.PY to add the term   join(prefix, "bin"), to the new_paths and, amazing, Spyder now opens perfectly from the startup menu.
As I say, I don't know if I had a broken environment somehow, but if anyone else is reporting similar mysterious errors on launch then it might be appropriate to update cwp.py for everyone.

Glad you found a solution yourself. You can contact @ccordoba12 for this to be fixed since i am not a dev(kind of).
Glads
Kiamehr

Hey @Tunneller, thanks a lot for reporting and finding a solution to this problem. I think it's a duplicate of issue #21749 because it's related to the auto-generated shortcut for Spyder on Windows.
So, I'm going to close it in favor of that one but I'll post your command there because I think it contains the key piece of information we need to solve this.


Updated based on some implimentation experience from dokieli

Clarified some ideas, based on what works, doesn't, and nice to haves.

+1 these look like good improvements

Yes, that looks better.  The property relation here seems pretty important for post processing, tho it appears not (yet) to be in the upstream pingback vocab?
I find the example of friending much more natural than of remote commenting.  Because when you add a relation to your profile, saying that you know someone, you can point someone to that, and additionally ask them to add you back.
Whearas, generally when you comment on something it will normally be already discoverable in Solid via follow your nose.  I think it would be advantageous in the examples not to train people to scatter data around the web without follow your nose style linking.
Final comment, the term "pingback" is already in use.  The term "ripple" also has a meaning in the web payments group, that is something slightly different, related to cross ledger transactions.  So the choice of codename may become slightly more confusing over time.

cool.

@melvincarvalho
I think that at the moment, we are just piggybacking on (semantic) pingback. We also need to re-consider whether it makes sense to stick around purl.org which we don't have control over at the moment to make any changes, and what's there now is not dereferencing. I prefer to move on. Perhaps this something for https://github.com/solid/vocab to take up. There is nothing specific to Solid, so the vocabulary can rest anywhere.
source, property, target are equally important. They come together, and we should not lose sight over this. There is an exact statement with those three components in the data, and they are used towards the verification. The verification is not about "Something linked to you from somewhere or somehow (without giving further hints), come figure it out based on your implementation and the interpretation of the spec". Does this statement exist? True/False. Do we want it? .. The point is not how much ambiguity can we get away with so that we can write more imperative coding from one implementation to another.
Lets have another example with that you suggest about friending/following a person. I like it.
The claims/pingbacks/interactions/annotations/mentions/notifications/status/activities ... can cover a wide range of stuff. There are some semantic differences between them but high overlap. Different UCs are sufficiently well document. We don't have to have strong favourites, but just aim to describe the core concepts well.
As for scattering data on the Web, we are doing that already, but it doesn't mean that the information is not followed. If for instance I'm on your article, and it provides the interface in which I can start the annotation interaction, and have it saved to my personal space (somewhere else on the Web), and then make sure to inform the article's pingback container about it with that pingback request, this is a good thing. We can follow-our-nose with that. The article may enable the user to do this, but it is also open to agents using their own applications to drop by to leave their claims. As mentioned in the PR title, this works for https://github.com/linkeddata/dokieli .
I'm completely open to the name change. I have some preference to use concepts like 'pingback', '(inter)action', 'activity', 'status', but essentially it is about 'notifying' a claim.

I think it probably wouldn't hurt to take the terms we need from the pingback vocab to supplement what we already have for solid terms (and add extras like property) and put them at a stable w3c namespace.

I find the example of friending much more natural than of remote commenting.

Would definitely be good to have different examples of a few different types of interactions.

Whearas, generally when you comment on something it will normally be already discoverable in Solid via follow your nose.

The relation would be discoverable from the new comment, but not from the thing commented on unless the former notifies/updates the latter. The whole idea with the pingback mechanism is to enable FYN linking in both directions, which is currently missing from solid.


Added readme file

I edit your txt file in a readme file with shell format for shell commands

Hello, you are welcomed to contribute to this project.
Thank you for your contribution but before merging please fix the conflicts by pulling the latest commits, and then push your updates.
You are welcomed to push anytime.

Yes, you are right !
Now should be ok :)


add a test that broadcast use items should not eat trailing spaces

@jaybosamiya, @parno this less-opinionated one is the behavior I think would be more consistent with the other formatting rules, but I don't know how to ensure line breaks are preserved, can you folks help with this?

I agree with this style change.
Rather than "not eat trailing", it might be easier to approach this as a "always add trailing, after a broadcast use group". Will take a closer look in some time

#55 now supersedes this, imho. Please take a look if the style update there matches what you expect. Also, as I mention there, some (minor) coordination will be required with vstd, at the time of verusfmt release.

Close in favor of #55.


small-compaction-threshold and compact key

By default small-compaction-threshold is 5000, which means 5000 update/delete for a key which will trigger two CompactRange job.
What's the motivation for this feature, for speed up read or reduce space amplification. Record update statistics and trigger CompactRange is a big overhead I think.
Thank you.

It reduces the proportion of invalid data caused by complex data structure operations while reducing the impact of auto_compact on disk performance.

What does "invalid data" mean? Can you give a example. Thank you!

Data that has been deleted logically but not physically has been deleted

Data that has been deleted logically but not physically has been deleted

Ok. I got it. I met this problem also in my db system based on rocksdb.
Some user encode date in userkey, like 190618_12345678 in 2019.06.18, and
it won't physically delete because no new key startwith 190618 after 7 days,
so no compaction will trigger which can physically delete these keys.


Migration to v20 from v19 failed

Description
I have tried multiple time to migrate to the v20 of the eks module without success. I always got the same error :
module.eks.aws_eks_cluster.this[0]: Modifying... [id= xxxxx-eks]
module.eks.aws_eks_cluster.this[0]: Still modifying... [id=ico-staging-eks, 10s elapsed]
module.eks.aws_eks_cluster.this[0]: Still modifying... [id=ico-staging-eks, 20s elapsed]
module.eks.aws_eks_cluster.this[0]: Still modifying... [id=ico-staging-eks, 30s elapsed]
module.eks.aws_eks_cluster.this[0]: Still modifying... [id=ico-staging-eks, 40s elapsed]
module.eks.aws_eks_cluster.this[0]: Still modifying... [id=ico-staging-eks, 50s elapsed]
module.eks.aws_eks_cluster.this[0]: Still modifying... [id=ico-staging-eks, 1m0s elapsed]
module.eks.aws_eks_cluster.this[0]: Still modifying... [id=ico-staging-eks, 1m10s elapsed]
module.eks.aws_eks_cluster.this[0]: Still modifying... [id=ico-staging-eks, 1m20s elapsed]

│ Error: waiting for EKS Cluster (xxxxx-eks) access configuration update (4ea5528f-e4c5-49d6-ab95-c56c9bba4377): unexpected state 'Failed', wanted target 'Successful'. last error: %!s(<nil>)
│
│   with module.eks.aws_eks_cluster.this[0],
│   on .terraform/modules/eks/main.tf line 27, in resource "aws_eks_cluster" "this":
│   27: resource "aws_eks_cluster" "this" {
│

... always after 1m30

[x ] ✋ I have searched the open/closed issues and my issue is not listed.

Versions

Module version [Required]: 19.21.0

Terraform version: v1.5.7

Provider version(s):

provider registry.terraform.io/alekc/kubectl v2.0.4
provider registry.terraform.io/hashicorp/aws v5.35.0
provider registry.terraform.io/hashicorp/cloudinit v2.3.3
provider registry.terraform.io/hashicorp/kubernetes v2.25.2
provider registry.terraform.io/hashicorp/time v0.10.0
provider registry.terraform.io/hashicorp/tls v4.0.5

Reproduction Code [Required]
From:
module "eks" {
  source  = "terraform-aws-modules/eks/aws"
  version = "~> 19.21"

  cluster_name    = local.cluster_name
  cluster_version = var.cluster_version
  subnet_ids      = data.aws_subnets.public.ids
  vpc_id          = data.aws_vpc.current.id

  cluster_endpoint_private_access = true
  enable_irsa                     = true
  openid_connect_audiences        = ["sts.amazonaws.com"]

  eks_managed_node_groups = merge({
    arm-nodes = {

      desired_size = var.asg_capacity
      max_size     = var.max_capacity
      min_size     = var.min_capacity

      instance_types = [var.instance_type]
      ami_type       = "AL2_ARM_64"
      key_name       = ""
      name           = "staging_nodes-group"

      # Disk setup
      block_device_mappings = {
        xvda = {
          device_name = "/dev/xvda"
          ebs = {
            volume_size           = 150
            volume_type           = "gp3"
            encrypted             = true
            kms_key_id            = data.aws_kms_key.ebs.arn
            delete_on_termination = true
          }
        }
      }

      # Launch template
      create_launch_template            = true
      launch_template_description       = "Launch template for staging workers on EKS"

      # Tags
      tags = {
        Environment = var.account_name
        Terraform   = "true"
      }

      # Add security group
      vpc_security_group_ids = [
        aws_security_group.cluster.id
      ]

      labels = {
        node = "main"
      }
    }
  }, var.node_groups)

  cluster_enabled_log_types     = var.enabled_logs
  cloudwatch_log_group_retention_in_days = var.log_retention

  # Configmap auth
  manage_aws_auth_configmap = true
  aws_auth_roles = local.map_roles

  # Tags
  node_security_group_tags = {
    Environment = var.account_name
    Terraform   = "true"
    "karpenter.sh/discovery" = "${var.client}-${var.account_name}-eks"
  }
}

To:
module "eks" {
  source  = "terraform-aws-modules/eks/aws"
  version = "~> 20.0"

  authentication_mode = "API_AND_CONFIG_MAP"

  cluster_name    = local.cluster_name
  cluster_version = var.cluster_version
  subnet_ids      = data.aws_subnets.public.ids
  vpc_id          = data.aws_vpc.current.id

  cluster_endpoint_private_access = true
  enable_irsa                     = true
  openid_connect_audiences        = ["sts.amazonaws.com"]

  eks_managed_node_groups = merge({
    arm-nodes = {

      desired_size = var.asg_capacity
      max_size     = var.max_capacity
      min_size     = var.min_capacity

      instance_types = [var.instance_type]
      ami_type       = "AL2_ARM_64"
      key_name       = ""
      name           = "staging_nodes-group"

      # Disk setup
      block_device_mappings = {
        xvda = {
          device_name = "/dev/xvda"
          ebs = {
            volume_size           = 150
            volume_type           = "gp3"
            encrypted             = true
            kms_key_id            = data.aws_kms_key.ebs.arn
            delete_on_termination = true
          }
        }
      }

      # Launch template
      create_launch_template            = true
      launch_template_description       = "Launch template for staging workers on EKS"

      # Tags
      tags = {
        Environment = var.account_name
        Terraform   = "true"
      }

      # Add security group
      vpc_security_group_ids = [
        aws_security_group.cluster.id
      ]

      labels = {
        node = "main"
      }
    }
  }, var.node_groups)

  cluster_enabled_log_types     = var.enabled_logs
  cloudwatch_log_group_retention_in_days = var.log_retention

  #Cluster access entry
  #To add the current caller identity as an administrator
  enable_cluster_creator_admin_permissions = true

  access_entries = {
    # Admin account
    eks-admin-role = {
      kubernetes_groups = []
      principal_arn     = "arn:aws:iam::${data.aws_caller_identity.current.account_id}:role/${local.resourcePrefix}-eks-admin-role"

      policy_associations = {
        administrator = {
          policy_arn = "arn:aws:eks::aws:cluster-access-policy/AmazonEKSClusterAdminPolicy"
          access_scope = {
            type = "cluster"
          }
        }
      }
    }
  }

  # Tags
  node_security_group_tags = {
    Environment = var.account_name
    Terraform   = "true"
    "karpenter.sh/discovery" = "${var.client}-${var.account_name}-eks"
  }
}

I have also tried using https://github.com/clowdhaus/terraform-aws-eks-migrate-v19-to-v20/tree/main and the auth module with the same result.
Steps to reproduce the behavior:
Nothing special
Do you have any idea, I'm a bit stuck :(

what steps did you perform when upgrading from v19 to v20

Nothing special, I have tried from our CI and locally, with a terraform init each time and an empty .terraform.
I just made the required changes on the eks module part including :
enable_cluster_creator_admin_permissions = true
access_entries

The first time I tried, I was not using the aws-auth module (same error) and it leave me with an empty aws-auth ConfigMap (as it should be?). I succeed to fixed it and I tried using the aws-auth module with the same issue.
I also didn't set : authentication_mode = "API_AND_CONFIG_MAP" explicitly as it was the default value

I would suggest reading through the upgrade guide and ensure you are upgrading in the correct sequence of events https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/docs/UPGRADE-20.0.md

I have :) but I may misunderstand something. I will check again.
But what this error mean : unexpected state 'Failed', wanted target 'Successful'. last error: %!s()

Ok, I tried to manage it directly from the interface (API_AND_CONFIG_MAP) and it failed, the eks module is not the pb for me. Thanks for your help.


(DO NOT MERGE) Checkstyle fail fast

I am just trying something while I wait for builds to complete.

@oscerd @davsclaus what do you think about this idea? It takes about 10 minutes to fail on checkstyle violations instead of the usual 40+. The tests run in parallel.

I think it would be really useful

Thanks, @oscerd. I'll do a few more tests and will merge once it's good enough!


[FEATURE][Event Analytics] allow keywords like dateTime to be used as field names

Is your feature request related to a problem?
Create a doc
POST test-index/_doc
{
  "dateTime": "2022-06-17T00:29:17.237Z"
}

use event analytics and see error

The issue is related to https://github.com/opensearch-project/sql/issues/672, and the PPL query is not escaping fields
What solution would you like?
PPL query constructed by Observability should escape fields

not escaping:

POST _plugins/_ppl
{
  "query": "source = test-index | where dateTime = '2022-06-17 00:29:17.237'"
}
{
  "error": {
    "reason": "Invalid Query",
    "details": "Failed to parse query due to offending symbol [dateTime] at: '...

escaping

POST _plugins/_ppl
{
  "query": "source = test-index | where `dateTime` = '2022-06-17 00:29:17.237'"
}
{
  "schema": [
    {
      "name": "dateTime",
      "type": "timestamp"
    }
  ],
  "datarows": [
    [
      "2022-06-17 00:29:17.237"
    ]
  ],
  "total": 1,
  "size": 1
}

What alternatives have you considered?
A clear and concise description of any alternative solutions or features you've considered.
Do you have any additional context?
Add any other context or screenshots about the feature request here.

closed by linked PR, this is addressed on SQL side


vimPlugins.grapple.nvim: init at 2024-04-09

Description of changes
Add grapple.nvim plugin

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

Hi there, these are the steps I took. Please confirm they are correct :)

Add grapple to vim-plugin-names
nix-shell -p vimPluginsUpdater --run 'GITHUB_API_TOKEN=<token> vim-plugins-updater'
Removed all changes/updates except the grapple change


[GOBBLIN-919]Using apache commons Pair API

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[ x] My PR addresses the following GOBBLIN-919 issues and references them in the PR title. For example, "[GOBBLIN-919] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-919

Description

[ x] Here are some details about my PR, including screenshots (if applicable):
Fixing build on top of https://github.com/apache/incubator-gobblin/pull/2765

Tests

[ x] My PR adds the following unit tests OR does not need testing for this extremely good reason:
Please refer to https://github.com/apache/incubator-gobblin/pull/2765

Commits

[ x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #2773 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master    #2773      +/-   ##
============================================
+ Coverage     45.33%   45.34%   +<.01%
+ Complexity     8858     8857       -1
============================================
  Files          1894     1894
  Lines         70829    70829
  Branches       7787     7787
============================================
+ Hits          32113    32120       +7
+ Misses        35752    35746       -6
+ Partials       2964     2963       -1

Impacted Files
Coverage Δ
Complexity Δ

...nt/copy/UnixTimestampRecursiveCopyableDataset.java
85% <100%> (ø)
8 <0> (ø)
:arrow_down:

.../org/apache/gobblin/metrics/RootMetricContext.java
78.12% <0%> (-1.57%)
15% <0%> (-1%)

...e/gobblin/runtime/locks/ZookeeperBasedJobLock.java
63.33% <0%> (-1.12%)
15% <0%> (-1%)

.../org/apache/gobblin/cluster/GobblinTaskRunner.java
65.27% <0%> (+0.46%)
28% <0%> (ø)
:arrow_down:

...lin/restli/throttling/ZookeeperLeaderElection.java
72.22% <0%> (+2.22%)
13% <0%> (ø)
:arrow_down:

...lin/util/filesystem/FileSystemInstrumentation.java
92.85% <0%> (+7.14%)
3% <0%> (ø)
:arrow_down:

.../org/apache/gobblin/async/AsyncDataDispatcher.java
88.13% <0%> (+8.47%)
14% <0%> (+1%)
:arrow_up:

Continue to review full report at Codecov.

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


"Fix" GFM tasklist rendering

Resolves the issues raised in #805.
Changes html rendering for GFM tasklists from:

Old task list

<input disabled="" type="checkbox"/>do it

<input disabled="" type="checkbox" checked=""/>done

New task list

to do

done

Which renders as:

Apparently the former rendering is specified in Commonmark specs, so we should raise the question, potentially get a blessing from them.  What's that process?
I don't know when list-style-type: <string> was released in CSS.  Current Firefox, Edge and Chrome browsers support it, someone will need to try Safari.
\2612 for the "checked" marker renders as a box with an X, not a checkmark.  That's my personal preference, but it's just Unicode and there's a \2611 that has the checkmark.
This is a modestly breaking change (for code that depends on HTML output).  Should there be an old_gfm_task_render feature?

OK. Yet another enhancement request that's not quite ready for prime time.
Meantime, I've got my private repo integrated with Zola and am able to use
it for what I needed.
Is there any energy about doing a new release of the project?  Enhancements
are always nice, though the simple bug reports seem to be piling up.  I've
got some time and interest, would be willing to join the fun.
My idea would be to focus first on a bug-fix release.  That gives you more
time to design thoughtful enhancements or add ons and the confidence that
you've got a solid codebase to work from.  I could take a crack at
identifying issues that might be good candidates for such a release,
hopefully that makes it easier for others who have time to know where to
pitch in.
On Wed, Jan 10, 2024 at 12:58 PM Michael Howell @.***>
wrote:

This seems like another feature to put on the pile of #645
https://github.com/raphlinus/pulldown-cmark/issues/645
Your rendering makes more sense for non-interactive lists (like mdBook),
but the -based rendering is what GitHub uses (that way, you can
actually click the checkbox). The parser doesn't know if you're an
interactive app or not.
A more robust HTML generator than pulldown-cmark has can expose a
configuration option to pick between these modes.
—
Reply to this email directly, view it on GitHub
https://github.com/raphlinus/pulldown-cmark/pull/806#issuecomment-1885350429,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPBIZHT6PVJJQFBGA2G6WTYN3JEXAVCNFSM6AAAAABBSPTJ7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBVGM2TANBSHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hello, the 0.10 version will be released when the pending pull requests are merged, hopefully this month.
However, new contributors are welcome, and indeed I had planned creating a new issue asking for contributors after the 0.10 release. To join as contributor, it is recommended to have a meeting with @raphlinus, and it is required respecting the rule of not merging pull requests or commits to the master branch without approval from another person.
@notriddle, @ollpu and @mgeisler are good candidates, based on previous contributions, but everyone is welcome.
Thanks!

Hey, thanks for the recognition. I'm open to dedicating some on-and-off time to maintaining the project.

Hi, the project has been moved to a new organization and I have invited @ollpu and @notriddle to join as contributors of the project.
I have just created a v0.11 milestone with the most important issues for the 0.11 release, but discussion is open to add other ones.

@notriddle, @ollpu and @mgeisler are good candidates, based on previous contributions, but everyone is welcome.

I would be happy to contribute where possible, but I have to admit that I find it hard to find time for my own crates these days... I'll of course keep trying to add a comment here and there when I find time :smile:

This change is more adequate in an alternative renderer, as @notriddle said, and it is already added in the tracking issue.


upper and lower vowel in Thai Language is missing

My code ::
x = "มีหมู"
print(x)
print(len(x))
Result:

x = "มหม"
print(x)
มหม
print(len(x))
3

Following my language, it should be 5 charactors in this case.

It sounds like this might be an issue with the Python language itself. I suggest searching around to see how Python handles calculations for these types of combined characters.

I also try it in Pycharm and Google Colab and Python able to read those vowel charactor. I think it might have some bug in VS Code.


Caching UIImage with Orientation RIGHT is retrieved from Disk with Orientation UP

Hey so I'm seeing something very odd when retrieving cached images from disk via SDWebImage v_3.7.2.  I'm hoping you guys can shed some light on what is happening.
Here is the scenario.

I use UIImagePickerController to grab a UIImage *photo from the image library.  This photo from the photo library contains an image orientation RIGHT with dimensions 2448x3264.

I add the photo to a UIImageView via UIImageView setImage.  The image displays correctly.

I cache this photo via SDWebImageCache [imageCache storeImage:image forKey:key toDisk:YES];

Here's where things get weird.

When I retrieve the photo from the cache and it is pulled from SDImageCache imageFromMemoryCacheForKey everything is fine.  The image orientation is still RIGHT and the dimensions are 2448x3264.  When I display this in a UIImageView the image is correctly drawn.

However, say I suspend the app to the background and relaunch the app, the image is now pulled from SDImageCache diskImageForKey and the orientation is UP and the dimensions are 3264x2448.  When I display this in a UIImageView the image is rotated -90 degrees CCW.
I'm not sure if this is a bug in SDWebImage or just iOS is doing something to the image once pulled from cache.
My workaround for this is before I cache any images, I check if the orientation is RIGHT, if it is, I create a new UIImage context that rotates the image 90 degrees clockwise.  Then when storing the image to cache the orientation will be UP and pulling the image from cache the orientatiln will remain UP and the photo is correctly drawn in a UIImageView.
It's a little scary doing this as I'd prefer any cached images with orientation RIGHT to keep that orientation once pulled from disk cache.
However, this may be the way iOS pulls images from disk.  Any insight on this is much appreciated.
Thanks!
Here's the code for rotating an image before cacheing if anyone needs a fix for this.
UIImage *photo = //photo from UIImagePickerController
if (photo.imageOrientation == UIImageOrientationRight)
{
            CGFloat radians = M_PI * 90.0f / 180.0f;

            UIGraphicsBeginImageContext(photo.size);

            CGContextRef bitmap = UIGraphicsGetCurrentContext();

            CGContextTranslateCTM(bitmap, photo.size.width / 2.0f, photo.size.height / 2.0f);

            CGContextRotateCTM(bitmap, radians);

            CGContextScaleCTM(bitmap, 1.0f, -1.0f);

            CGContextDrawImage(bitmap, CGRectMake(photo.size.height / 2.0f * -1.0f, photo.size.width / 2.0f * -1.0f, photo.size.height, photo.size.width), photo.CGImage);

            photo = UIGraphicsGetImageFromCurrentImageContext();
            UIGraphicsEndImageContext();
}

@levieggert
i just tested with an image that has orientation uiimageorientationright and uploaded it to a server online. I tried that image and SDWebImage caches that image and keeps that orientation. The image in memory is still uiimageorientationright and the imageview shows it correctly.
When suspending the app and trying again the lib takes the image from disk like you said and still the image's orientation is right and the imageview shows it correctly.
what i suspect is this:
when you manually cache the image using the storeImage:image forKey.... method the recalculate property is set to YES whereas when downloading and caching the image automatically the recalculate is set to NO.
what the recalculate does is that is reconstructs new data from the current UIImage with this:
data = UIImageJPEGRepresentation(image, (CGFloat)1.0);
something which strips the EXIF from the image thats why you get the uiimageorientationUp when retrieving it from disk.
can you try and cache the image using this and pass NO for recalculateFromImage.
You should pass the data as well
- (void)storeImage:(UIImage *)image recalculateFromImage:(BOOL)recalculate imageData:(NSData *)imageData forKey:(NSString *)key toDisk:(BOOL)toDisk

and see if it works for you?

Hey @mythodeia
Thank you for getting back to me.  I think I see what is going on now.

I tested the same flow this time storing the NSData as UIImageJPEGRepresentation and it does keep the orientation RIGHT when retrieving from disk.

NSData *imageData = UIImageJPEGRepresentation(image, 1.0f);
[imageCache storeImage:image recalculateFromImage:NO imageData:imageData forKey:key toDisk:YES];

I also tried storing the NSData as UIImagePNGRepresentation to see what would happen like so.

NSData *imageData = UIImagePNGRepresentation(image);
[imageCache storeImage:image recalculateFromImage:NO imageData:imageData forKey:key toDisk:YES];
This gave me the original results where saving to disk the orientation is RIGHT and retrieving from disk the orientation is UP and my image is rotated -90 degrees CCW.

Finally, as a third test I rotated the image 90CW and then stored the image as UIImagePNGRepresentation like so.

NSData *imageData = UIImagePNGRepresentation(image);
[imageCache storeImage:image recalculateFromImage:NO imageData:imageData forKey:key toDisk:YES];
When retrieving the image from disk the orientation is UP, but now since I rotated the image before saving to NSFileManager, the image is correctly rotated.

So it seems it comes down to iOS interpreting the image data.  Storing UIImageJPEGRepresentation to NSFileManager will keep the orientation where as UIImagePNGRepresentation will convert the orientation to UP.  So if you want to store NSData to NSFileManager as UIImagePNGRepresentation, be sure to check the orientation before storing the image and apply any rotation as needed.

Does this appear to be the case for you?
Thanks!

when saving with UIImagePNGRepresentation the EXIF metadata are stripped.
SDWebImage checks to see if the original image is a png and then uses the appropriate method to save it to disk.
generally PNG images do not keep orientation info inside as far as i know

Okay makes sense now.
thanks for the help!

I am facing same issue with sd_webimage. Need help. I want to make it work normally though image captured in portrait or landscape it should appear in portrait if viewed in portrait and landscape if viewed in landscape.


Adding a page programatically

I'm trying to create a lot of pages at once using the following code:
public void AddFaqPage(Guid parent, string permalink)
    {
        var templateId = Guid.Parse("c16b62a7-8055-4c59-80ea-3fb0d29bf26b");
        var siteTreeId = Guid.Parse("c2f87b2b-f585-4696-8a2b-3c9df882701e");
        var siteTree = "DEFAULT_SITE";

        var em = EditModel.CreateByTemplateAndPosition(templateId, parent, 0, siteTreeId, siteTree);

        em.Permalink = new Permalink()
        {
            Id = Guid.NewGuid(),
            Type = Permalink.PermalinkType.PAGE,
            NamespaceId = Guid.Parse("8ff4a4b4-9b6c-4176-aaa2-db031d75ac03")
        };
        em.Page.IsNew = true;
        em.SaveAll();
    }

But I get an errormessage:
NullReferenceException: Object reference not set to an instance of an object.]
Piranha.Models.Permalink.Generate(String str, PermalinkType type) in c:\Proj\GitHub\Piranha-2.2\Piranha\Entities\Internal\Permalink.cs:174
Piranha.Models.Manager.PageModels.EditModel.SaveAll(Boolean draft) in c:\Proj\GitHub\Piranha-2.2\Piranha\Models\Manager\PageModels\EditModel.cs:457

Whe I look into the stacktrace, it's not the same as in the source control:
EditModel.cs:457 is this:
using (var db = new DataContext()) {

So it does't call a function in Permalink.cs at all..
What am I doing wrong?

This is a dumb way to do this :(

My guess is that the code automatically tries to generate a permalink from the page title. The page title is required in the model validation which you've bypassed. When running the regular expression on the title in Permalink.Generate it gets a null pointer exception.


Find nodes in graph

Search through the graph for where particular nodes are

In Dynamo 2.15+ we have access to the graph node manager that does this. But I can consider implementing as a search bar.

Closed as this is available in the graph node manager in modern versions of Dynamo.


Proposal to allow opting out of server reload on .env changes

Description
It would be amazing if we can provide a flag to the watch config to stop the server from restarting and reloading the browser everytime the .env file changes.
We (and I'm sure others) inject local env variables into a .env when they enter a working directory e.g. with direnv. This means when we open a new shell the browser reloads and vite dev server will reload unnecessarily.
Suggested solution
An outright ignore .env file disabling flag.
return defineConfig({
    server: {
        watch: {
            ignoreEnvUpdates: boolean;
        }
    }
})

Alternative
return defineConfig({
    server: {
        watch: {
            ignored: [
                ".env"
            ]
        }
    }
})

When .env is passed in the ignored watch list it isn't considered as part of the server reload conditions.
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

If you allow me, I can work on a solution to this problem.

You can configure this instead, which works for me:
  server: {
    watch: {
      ignored: ['**/.env*']
    }
  }

@bluwy Amazing, thank you. I had my regex all wrong.