vapoursynth-editor: use qt's mkDerivation

Motivation for this change
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-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)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @

This needs a backport.

Note, wrapping should happen in preFixup. Not the installPhase.

This program is already wrapped, so wrapQtAppsHook will ignore wrapping it. This is because it ignores scripts.

It does seem to work anyway, but wrapping a program twice probably isn't great.
Fixed, if it looks good I'll make a backport PR.

This program is already wrapped, so wrapQtAppsHook will ignore wrapping it. This is because it ignores scripts.

It does seem to work anyway, but wrapping a program twice probably isn't great.
Fixed, if it looks good I'll make a backport PR.

This was the content of the wrapper without using wrapQtApp
#! /nix/store/zavn4np1jvm79f0rafkv0p1mrag09qkz-bash-4.4-p23/bin/bash -e
export PYTHONPATH='/nix/store/f5fz7wa9nixd7qpzh6a1rp1ij7bxw0xq-vapoursynth-R47.2/lib/python3.7/site-packages'${PYTHONPATH:+':'}$PYTHONPATH
export LD_LIBRARY_PATH='/nix/store/f5fz7wa9nixd7qpzh6a1rp1ij7bxw0xq-vapoursynth-R47.2/lib'${LD_LIBRARY_PATH:+':'}$LD_LIBRARY_PATH
exec -a "$0" "/nix/store/mbbql8hkf5b8kplkji3h469wf5b6avk6-vapoursynth-editor-R19/bin/.vsedit-wrapped"  "$@"

so it was actually broken.
Here's the content of the wrapper in the latest commit
#! /nix/store/zavn4np1jvm79f0rafkv0p1mrag09qkz-bash-4.4-p23/bin/bash -e
export QT_PLUGIN_PATH='/nix/store/js39qrk4i5i5my3nl317dniqk4sp5dgi-qtbase-5.12.5-bin/lib/qt-5.12.5/plugins'${QT_PLUGIN_PATH:+':'}$QT_PLUGIN_PATH
export QT_PLUGIN_PATH='/nix/store/x507783mf613yhaksqcj2bpy14mrwa8l-qtsvg-5.12.5-bin/lib/qt-5.12.5/plugins'${QT_PLUGIN_PATH:+':'}$QT_PLUGIN_PATH
export QT_PLUGIN_PATH='/nix/store/phka1gjvm55kmw7jw9nmm7aa62q7anlf-qtdeclarative-5.12.5-bin/lib/qt-5.12.5/plugins'${QT_PLUGIN_PATH:+':'}$QT_PLUGIN_PATH
export QML2_IMPORT_PATH='/nix/store/phka1gjvm55kmw7jw9nmm7aa62q7anlf-qtdeclarative-5.12.5-bin/lib/qt-5.12.5/qml'${QML2_IMPORT_PATH:+':'}$QML2_IMPORT_PATH
export QML2_IMPORT_PATH='/nix/store/cl4r46fmcihpig1slcpmm1s2bx72cv5h-qtquickcontrols-5.12.5/lib/qt-5.12.5/qml'${QML2_IMPORT_PATH:+':'}$QML2_IMPORT_PATH
export QT_PLUGIN_PATH='/nix/store/ays1cry94qjil280jjh9j283f2pkb74j-qtwayland-5.12.5-bin/lib/qt-5.12.5/plugins'${QT_PLUGIN_PATH:+':'}$QT_PLUGIN_PATH
export QML2_IMPORT_PATH='/nix/store/ays1cry94qjil280jjh9j283f2pkb74j-qtwayland-5.12.5-bin/lib/qt-5.12.5/qml'${QML2_IMPORT_PATH:+':'}$QML2_IMPORT_PATH
export QML2_IMPORT_PATH='/nix/store/kq988pbxyp5pwz54k51xdg54ljlva5w2-qtwebsockets-5.12.5-bin/lib/qt-5.12.5/qml'${QML2_IMPORT_PATH:+':'}$QML2_IMPORT_PATH
export PYTHONPATH='/nix/store/f5fz7wa9nixd7qpzh6a1rp1ij7bxw0xq-vapoursynth-R47.2/lib/python3.7/site-packages'${PYTHONPATH:+':'}$PYTHONPATH
export LD_LIBRARY_PATH='/nix/store/f5fz7wa9nixd7qpzh6a1rp1ij7bxw0xq-vapoursynth-R47.2/lib'${LD_LIBRARY_PATH:+':'}$LD_LIBRARY_PATH
exec -a "$0" "/nix/store/819qdp87gc22j989vqyn8kqmwrl2q5nv-vapoursynth-editor-R19/bin/.vsedit-wrapped"  "$@"

LGTM :+1: I can perform the backport manually for you as well.

This was the content of the wrapper without using wrapQtApp

Yeah, .vsedit-wrapped actually was another wrapper script that called ..vsedit-wrapped-wrapped.

LGTM +1 I can perform the backport manually for you as well.

Thanks!

backported in 82b699861c27819b859abe28b17ebcfe4745a197.

Thanks!

No problem, thank you :sparkles:


How to turn off auto initialization for controls

Hi there
Do you have a way to turn off auto initialization of the controls? I have another UX library that I'm using that is conflicting with gijgo. Is there way to ensure that the components are not initialized automatically.
For example in my case, my date picker control uses a class named "datetimepicker" and is initialialized by calling .datetimepicker() and not necessarily .datepicker() from gijgo but this gets initialized by gijgo because I have also added gijgo in my resources because I'm using the tree component. Can you please help?

Just figured it out, the css and js files here /Areas/Development/dist/modular as per documentation work perfectly as seen in this post, https://gijgo.com/LiveEdit/Index/tree.Checkboxes.checkboxes.Bootstrap.4.html.
Perhaps updating the examples dist folder can also help as posted here. https://github.com/atatanasov/gijgo/tree/master/examples


minor: fix doctest that runs accidentally

Which issue does this PR close?

Closes #.
Fixes failing CI https://github.com/apache/arrow-datafusion/actions/runs/4685079004/jobs/8301949150
Probably broken by https://github.com/apache/arrow-datafusion/pull/5962
Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

Thanks @yjshen  and @jackwener -- I think I probably broke this with https://github.com/apache/arrow-datafusion/pull/5962


The article is not clear about the possibility for expanding a SHARE

On this part:
"The volume cannot be expanded later.
Once the volume has been created, you cannot shrink the size of the volume on StorSimple."
There is no explicit mention for File SHARES - Please consider adjusting it.

@diegoalb : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Changes look good. Please merge. #sign-off


6345 store user data size in redis

This closes #6345.
@rafatower could you take a look, please? This might not be the final version of the code, since Hubspot reporting side is not done yet but, since you helped a lot with the design, I'd like your feedback.
I considered ZADD, but I think sorting by score (db_size_in_bytes in my case) is not useful. In my original proposal (and code) I added the date to the key (rails:users:central-user-1:db_size_in_bytes:20160105) but it was not actually needed, so I removed it to avoid duplications (rails:users:central-user-1:db_size_in_bytes).
I had also recovered the original resque job for this. Originally the code had to do an http call to a third party service, so a job made sense, but now we're only storing a Redis value, the job is an unnecessary overhead and I've removed it (you can see the latest commits).
What do you think?

@rafatower hold this review. Currently there's no way for Central to read cloud Redis, so this design must be changed :(

FYI, since CartoDB Redis is not a valid communication channel with Central, I'm going to modify superadmin user api so it can be filtered by "disk_space_change", in a similar fashion than "overquota" filtering.

@rafatower , @zenitraM , could you CR this, please?

Retest this, please.

@rafatower , a final CR after your suggestions, please? @zenitraM , I'd also like you to CR this, since it involves Redis. Thank you both :-)

:+1: for me

:+1:

I'll merge & deploy after empty code deletion (60f28f36d48e0832beb0d5d7f76d860ce8cb1120) test pass, thank you both!


Update Dutch

Added Rank Role translation. Also fixed a small help message (showed the English word instead of the Dutch word)

Sorry, I just realized an issue with the text. rank_role_usage is:
rankrole <config>. Config is a set of rules for your rank roles. For example, ``playtime_20:12345678912345678, sodas_10:12345678912345679`` will give the ``20`` people with the highest ``playtime`` the role with the ID ``12345678912345678``, then the ``10`` people with the most ``sodas`` the role ``12345678912345679``.

But should be:
rankrole <config>. If you want to clear your Rank Roles, you can set config to ``none``. Config is a set of rules for your rank roles. For example, ``playtime_20:12345678912345678, sodas_10:12345678912345679`` will give the ``20`` people with the highest ``playtime`` the role with the ID ``12345678912345678``, then the ``10`` people with the most ``sodas`` the role ``12345678912345679``.

Updated


官网内容丰富

Is your feature request related to a problem? Please describe.
官网需要添加github地址
Describe the solution you'd like
建议在左上角添加一个github的图标
Additional context

The suggestion has been received and will be completed immediately

We have received the suggestion and will finish it right away
我们已经收到您的建议，马上完成

The proposal has been completed. Thank you for your participation.该建议已完成，感谢提醒。


Include PyUnusedCodeBear in .coafile to remove unused imports

difficulty/newcomer

Can you please guide me so that I can begin with the issue.

@Man-Jain are you familiar with how coala works? If not take a look coala.io .

Sorry for the late reply @nvzard. Yes I am familier with the coala. I have used in one of my projects.

@Man-Jain then you just need to include PyUnusedCodeBear in this repo's .coafile , run coala and push the changes.

Sorry, closed by mistake.

@nvzard I have done all that you said. What should I do next.

Push your code and open a pull request.

Should I run any tests? If yes, please tell how.


'Prev' bug

The 'prev' command allows one to re-enter a room otherwise not allowed.
To Reproduce:

Start game with no save file
Exit room (mirror, xyzzy)
You should be in home
Type 'prev'
You'll end up back in the first room.

Maybe another location parameter (like invisible=False)?

I tried that with the last commit, but it still allows it to pass through
+


Fixes the jest-haste-map mapper option

Summary
I forgot in my previous PR to forward the mapper option from the JestHasteMap options to the crawler option. It went unnoticed because the tests directly instantiate the crawler and because in Metro this logic wasn't necessary because the PnP resolution bypassed the Haste map.
I noticed the problem by removing this bypass, which highlighted that the mapper never got called 😞
Test plan
Modified my Jest copy locally, checked that the mapper was called as it should be.

Codecov Report

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

@@          Coverage Diff           @@
##           master   #8299   +/-   ##
======================================
  Coverage    62.2%   62.2%
======================================
  Files         266     266
  Lines       10673   10673
  Branches     2595    2595
======================================
  Hits         6639    6639
  Misses       3445    3445
  Partials      589     589

Impacted Files
Coverage Δ

packages/jest-haste-map/src/index.ts
81.26% <ø> (ø)
: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 151c961...525b0da. Read the comment docs.


python3 support

Current coverage is 97.14%

Merging #2 into develop will decrease coverage by -0.56% as of cfb6546

@@            develop      #2   diff @@
=======================================
  Files             6       6
  Stmts           218     245    +27
  Branches          0       0
  Methods           0       0
=======================================
+ Hit             213     238    +25
  Partial           0       0
- Missed            5       7     +2

Review entire Coverage Diff as of cfb6546

Powered by Codecov. Updated on successful CI builds.


chore(dashboard): remove password input from project creation

Codecov Report

Merging #1995 (14a2ead) into main (9b8a19a) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##             main    #1995   +/-   ##
=======================================
  Coverage   87.10%   87.10%
=======================================
  Files          85       85
  Lines        9282     9282
  Branches      550      550
=======================================
  Hits         8085     8085
  Misses       1197     1197


How to use pre-trained weights ?

Hi,
First of all, thank you for this repo!
I would like to use pre-trained weights for ResNet50 architecture in tensorflow. I have downloaded corresponding pre-trained weights in dropbox.
How should I do this ?
Build a ResNet50 and assign weights ?
wts = "./checkpoint_ResNet50/checkpoints-3"
model = ResNet50(
            include_top=True,
            weights=None,
            input_shape=(120, 120, 12),
            pooling="avg",
            classes=43
)
model.load_weights(wts)

I got about 3000 lines of warnings like these :
WARNING:tensorflow:Unresolved object in checkpoint: (root).model
WARNING:tensorflow:Unresolved object in checkpoint: (root).optimizer
WARNING:tensorflow:Unresolved object in checkpoint: (root).save_counter
WARNING:tensorflow:Unresolved object in checkpoint: (root).model.layer-0
WARNING:tensorflow:Unresolved object in checkpoint: (root).model.layer-1
WARNING:tensorflow:Unresolved object in checkpoint: (root).model.layer-2
WARNING:tensorflow:Unresolved object in checkpoint: (root).model.layer-3

and finally an error : AssertionError: Nothing except the root object matched a checkpointed value. Typically this means that the checkpoint does not match the Python program. The following objects have no matching checkpointed value

Hi @vlarmet,
It seems that you are trying to load our custom ResNet50 pre-trained weights to a ResNet50 tensorflow.keras model. You can find the correct weights for your use case here.
Please keep in mind that during pre-training we use the 19-class nomenclature and that in addition to the 10th spectral band of Sentinel-2, which was also excluded in the original BigEarthNet implementation, we also excluded the 1st and 9th spectral bands as they do not contain information regarding the Earth’s surface.
Summing up, you should download the correct checkpoint files using the link mentioned above, set the input shape to (120, 120, 10) and set the classes argument equals to 19.

Thank you, I managed to do what I want !


Reloading existing RDF Entity should save to same URL

Loading an existing Trellis URL in the Browse loads correctly into the Editor; however, when clicking on the Save & Publish button a new URI is minted instead of updating Trellis with the same Trellis URL and the updated RDF.

also should not prompt you again to choose a group, should just save to group the resource is already in


Add NumPy 2.0 linting

numpy 2.0b1 is out already. I'm not sure whether we're ready for it? Ruff has a linting rule for the transition:
https://numpy.org/devdocs/numpy_2_0_migration_guide.html#ruff-plugin
Our pre-release workflow has been failing for a long time 😅 so it does not provide us with a useful signal... 😢

Some positive news - there's not as many errors as you might expect! Only twelve errors, caused by two particular deprecations:

np.sctypes will be removed without replacement in NumPy 2.0
np.set_string_function will be removed in NumPy 2.0. Use np.set_printoptions for custom printing of NumPy objects.

ruff check napari --select NPY201

napari/_qt/_tests/test_qt_viewer.py:973:18: NPY201 `np.sctypes` will be removed without replacement in NumPy 2.0
napari/_qt/_tests/test_qt_viewer.py:973:38: NPY201 `np.sctypes` will be removed without replacement in NumPy 2.0
napari/_qt/_tests/test_qt_viewer.py:999:31: NPY201 `np.sctypes` will be removed without replacement in NumPy 2.0
napari/_qt/_tests/test_qt_viewer.py:999:51: NPY201 `np.sctypes` will be removed without replacement in NumPy 2.0
napari/_qt/_tests/test_qt_viewer.py:1029:31: NPY201 `np.sctypes` will be removed without replacement in NumPy 2.0
napari/_qt/_tests/test_qt_viewer.py:1029:51: NPY201 `np.sctypes` will be removed without replacement in NumPy 2.0
napari/utils/_tracebacks.py:37:13: NPY201 `np.set_string_function` will be removed in NumPy 2.0. Use `np.set_printoptions` for custom printing of NumPy objects.
napari/utils/_tracebacks.py:54:13: NPY201 `np.set_string_function` will be removed in NumPy 2.0. Use `np.set_printoptions` for custom printing of NumPy objects.
napari/utils/_tracebacks.py:91:17: NPY201 `np.set_string_function` will be removed in NumPy 2.0. Use `np.set_printoptions` for custom printing of NumPy objects.
napari/utils/_tracebacks.py:128:17: NPY201 `np.set_string_function` will be removed in NumPy 2.0. Use `np.set_printoptions` for custom printing of NumPy objects.
napari/utils/_tracebacks.py:137:17: NPY201 `np.set_string_function` will be removed in NumPy 2.0. Use `np.set_printoptions` for custom printing of NumPy objects.
napari/utils/_tracebacks.py:143:17: NPY201 `np.set_string_function` will be removed in NumPy 2.0. Use `np.set_printoptions` for custom printing of NumPy objects.
Found 12 errors.

I've made a PR here: https://github.com/napari/napari/pull/6776
Need help: How do I replace np.set_string_function(lambda arr: f'{type(arr)} {arr.shape} {arr.dtype}') with an equivalent np.set_printoptions command? This is the numpy.set_printoptions docs, and these are the old numpy.set_string_function docs. I can change the formatting of individual numpy array elements, but I can't figure out how to make it return a single summary string for the whole array.


Can't connect to a Redis cluster when I check the Cluster checkbox.

OS
Windows
VERSION
Another Redis Desktop Manager v1.6.4
ISSUE DESCRIPTION
I can't connect to a Redis cluster when I check the Cluster checkbox.
But if I uncheck the cluster check box, it works.
My question is it should be able to connect to a Redis cluster when we check the Cluster checkbox.

I think your moved ip is another internal ip instead of <IP_ADDRESS>
you can uncheck Cluster to connect as a single Redis, then open console to exec get xxxx, get the moved ip，then use the new ip to fill the Host config
https://github.com/qishibo/AnotherRedisDesktopManager?tab=readme-ov-file#faq

Thank you for the reply.
Yes, I think the same way because there are internal IPs for the cluster because it's a redis cluster by a docker-compose.
I was wondering if there are any options for the users to select if they want to change the host on cluster redirects.
If so, this would be convenient for the users to change the modes without modifying host config.
And it's better for the users to understand the behavior behind the scenes.


Conflict with iOS standard "swipe to go back"

Info received by mail:
Basically, it seems as though the MGSTC panGesture and the iOS standard "swipe to go back" gesture are stealing one anthers touches. Strangely, it seems like whichever is engaged first disables the other. i.e. Swipe a cell and the swipe-back gesture will never get called, it will only swipe other cells. But, if you engage the swipe-back gesture first, only part-ways and return into the view cell will no longer swipe!
At first I thought the solution would be to modify the _swipeView bounds so that the MGSTC panGesture isn't called if it initiate within the first x points (sy, 5) of the left screen edge. For some reason I can't get this to work properly and it adds strange behaviour (cells will only swipe once and then never again? weird).
Anyway, it's an unlikely situation for any of my users to find them in, but something I thought I'd bring to your attention. Any ideas?

@MortimerGoro I have a solution for this I've been using for a while, I'll create a pull request tomorrow for this. :)

@MortimerGoro This is actually a pretty common use case, and was an issue for my users. I had this working with version 1.1.1, and it was a really nice effect by adding this to MGSwipeTableCell.m.
- (BOOL)gestureRecognizer:(UIGestureRecognizer *)gestureRecognizer shouldRecognizeSimultaneouslyWithGestureRecognizer:(UIGestureRecognizer *)otherGestureRecognizer
{
    return YES;
}

- (BOOL)gestureRecognizer:(UIGestureRecognizer *)gestureRecognizer shouldRequireFailureOfGestureRecognizer:(UIGestureRecognizer *)otherGestureRecognizer
{
    return [otherGestureRecognizer isKindOfClass:[UIScreenEdgePanGestureRecognizer class]];
}

I'm trying to go through what's changed, and can't seem to be able to fix it. Now when I add that, the same issue continues, and also now the table view continues to scroll while you're opening the cell.
Let me know if this helps, I'd love to figure this out and be able to upgrade to 1.3.5.

hi Joe, I can't reproduce the issue. I tried the Swipe to go back (pushing a viewController in MGSwipeDemo and MailAppDemo) and I didn't find the conflict: Swipe to go back gesture and cell swipes are compatible. It works even without adding your code. Any ideas about how to reproduce the issue?

@MortimerGoro It looks like you're right, there must be something conflicting with my code, because I can't recreate it in the demos, even after modifying it. I'm just using a regular UIViewController with a UITableView in my app, but will try and see if I can debug what circumstances are causing it to not work with 1.3.5.

Original submitter here.
I haven't had time to test extensively, but adding
- (BOOL)gestureRecognizer:(UIGestureRecognizer *)gestureRecognizer
   shouldReceiveTouch:(UITouch *)touch;
{
    CGPoint touchLocation = [touch locationInView:touch.window];
    if ([gestureRecognizer isKindOfClass:[UIPanGestureRecognizer class]] && touchLocation.x < 10) {
        return NO;
    } else {
        return  YES;
    }
}

Seems to disable the swipe gesture for enough of a margin along the left edge that the gestures no longer conflict. I've added this to the implementation file of the latest commit and everything seems to be working correctly.

@Cs55Dev That makes sense, I was setting my layoutMargins to UIEdgeInsetsZero as well. Thanks for the fix!

I tried to implement native edge swiping feature. My problem is when i swipe left edge in the Tableview it is getting stuck. I can't scroll tableview after edge swiping. Please help me!

@sameera26
How did you implement edge swiping? With my code above?
If you put that code in your tableview you might be disabling touches for the pangesturerecognizer the tableview uses to scroll. You should put it in MGSwipeTableCell.m.
You could try replacing the if statement with:
if (gestureRecognizer == _panRecognizer && touchLocation.x < 10)
Haven't tested, but that ought to work.

Thanks for the quick response I implemented edge swiping in my detail view controller. But user swipe left edge to right in Tableview its getting stuck.

Hey there,
I'm having some trouble following exactly how you have your code set up. Could you post some code?
As I said, the BOOL method I posted should be in your MGSwipeTableCell implementation file. If you have it elsewhere you are going to run into conflicts with other pan gestures.
Seeing some code will help. Thanks!
Mike
Sent from my iPhone

On Mar 26, 2015, at 7:28 AM, sameera26<EMAIL_ADDRESS>wrote:
Thanks for the quick response I implemented edge swiping in my detail view controller. But user swipe left edge to right in Tableview its getting stuck.
—
Reply to this email directly or view it on GitHub.

How can I access touchLocation.x within the (BOOL)gestureRecognizerShouldBegin:(UIGestureRecognizer *)gestureRecognizer method?
Thanks.

In the .h file add:
@property (nonatomic, assign) CGPoint touchLocation;

Then in the implementation file add the following method:
- (void)touchesBegan:(NSSet *)touches withEvent:(UIEvent *)event {
    UITouch *touch = [[event allTouches] anyObject];
    _touchLocation = [touch locationInView:self.window];
}

You can then call _touchLocation.x in your method. But I caution you, if your plan is to use the x to prevent the gestureRecognizer from beginning by returning NO i went down that route and got weird behaviour.
It's much simpler to just prevent the gestureRecognizer from receiving the touch to begin with using the code I posted originally.

I'm also having this issue, and afaik I'm not setting layoutMargins to UIEdgeInsetsZero. Or is this default? Either way, will this be fixed in a future release or do I also have to fix it myself?

I could fix this issue with using the code @Cs55Dev posted originally in this thread. And also I had to add below code in my tableview class.
override func viewWillDisappear(animated: Bool) {
    if(self.navigationController?.respondsToSelector("interactivePopGestureRecognizer") != nil) {
        self.navigationController?.interactivePopGestureRecognizer.enabled = true;
        self.navigationController?.interactivePopGestureRecognizer.delegate = nil
    }

}
override func viewDidAppear(animated: Bool) {
if(self.navigationController?.respondsToSelector("interactivePopGestureRecognizer") != nil) {
self.navigationController?.interactivePopGestureRecognizer.enabled = false;
self.navigationController?.interactivePopGestureRecognizer.delegate = self
}
}
Cheers!

I have added the following delegate method in 1.5.1:
-(BOOL) swipeTableCell:(MGSwipeTableCell*) cell canSwipe:(MGSwipeDirection) direction fromPoint:(CGPoint) point;
```

Now you can return false if point.x is too close to the edge

Thanks for the addition! I'm just not sure if this is the right way to go. It seems far easier to subclass MGSwipeTableCell and just override the gestureRecognizer:shouldReceiveTouch: method as described above. Otherwise I'd have to add the same code in every view controller that conforms to MGSwipeTableCellDelegate.
But I guess that's okay to have it anyway, it probably depends on the use case.

I would vote to keep this addition because I'd rather structure my code via composition and delegation rather than a subclass hierarchy. It also allows someone to set different x values, which is good because I actually don't have the same x values everywhere. With this solution in place you can still subclass if you do so choose to though.


Updated README to include 2020-2021 Honda Civic Hatchback

2020-2021 Honda Civic hatchbacks are currently working based on some user feedback.
2021 hatchback:
https://discordapp.com/channels/469524606043160576/469532500335656972/779774528539983872
2020 hatchback:
https://discordapp.com/channels/469524606043160576/469532500335656972/771192621049053195
Clarified OP support doesn't include the Civic hatchback Type R trim since it only comes in 6 speed manual.

We don't support any manual cars, so you can remove "excludes type r" from the readme.

Removed the "excludes Type R" from the README.

Confirmed working with discord members without changes to fw versions, merging now.


[Feature] Request: offer scrolling in case the content doesn't fit 100% to the same resolution as the device

Is your feature request related to a problem? Please describe.
When we use center-crop scaling, we can't reach the other parts of the wallpaper by scrolling in the launcher.
Describe the solution you'd like
Please offer a way to reach this content.
Describe alternatives you've considered
Other wallpapers and wallpaper apps offer it.
Additional context
Example of even a video/image wallpaper app that has it, but sadly it has a bug sometimes when changing orientation and when scrolling to the edges:
https://github.com/SCratORS/ImageWallpaperSC

This is an interesting idea. No promises if I'll work on it or not, as this app is right now mostly in maintenance mode as I have little time to dedicate to it.


Improve cache Poetry install instructions

In #150, I described a usecase were caching the Poetry installation was causing the dependency cache step to break when the .lock was updated.
In summary, if some action used a cached poetry install (skips running snok/install-poetry), the configurations set in with would not be done, which caused any new dependency installs to not be cached, as Poetry by default installs venvs not in the .venv path (so the cache step can't find the .venv directory to cache).
This PR adds a section in the docs to clarify this and guide users to a fix.

Thanks for the help here @sebastian-correa! 🙇


Add Reference Tools

https://github.com/willhoag/awesome-reference-tools

The list is not very comprehensive. Awesome lists are hard work. Put some more work into it. Take a look at some other lists and see how they do it. E.g. https://github.com/sindresorhus/awesome-electron https://github.com/sindresorhus/awesome-npm
Would be happy to reconsider in a month when the list has gotten some more work.
It's also missing a license. Please read the awesome manifest.

Yep, sounds good. I'll be sure to invest some more time into it and will come back when it is ready. And, add a license. Thanks!


feat: support amplify codegen models without initialized amplify backend

Description of changes
WIP PR refactoring modelgen in order to support executing commands like amplify codegen models --target android --model-schema src/schema.graphql without needing to have an initialized amplify project locally.
Issue #, if available
N/A
Description of how you validated changes
Unit tests, + E2E Tests (To be written), and manual exploratory testing, test cases TB added.
Checklist

[ ] PR description included
[ ] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] Breaking changes to existing customers are released behind a feature flag or major version update
[ ] Changes are tested using sample applications for all relevant platforms (iOS/android/flutter/Javascript) that use the feature added/modified

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Discarding in favor of https://github.com/aws-amplify/amplify-codegen/pull/694


Don't Merge! Regression PR perf testing with metadata validation

Docs Build status updates of commit f83097c:
:clock10: Pending: waiting for processors (6 builds ahead of you)
:warning: Docs Build is busy, currently there are 6 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit f83097c:
:clock10: Full build: the average full build time is 33 min(s) 19 sec(s), this is based on the last 3 build(s) for this repository.

Docs Build status updates of commit f83097c:
:clock10: Full build: the average full build time is 33 min(s) 19 sec(s), this is based on the last 3 build(s) for this repository.

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

File
Status
Preview URL
Details

TestingPullRequest.md
:white_check_mark:Succeeded

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.


im stuck getting this to work

having issues getting this configured... don't know what I'm missing. is there any way i could get help?

It is relatively easy to do. All you need to do is install the programs and import the scripts you download from here. I don't know anything about programming and I got it to work by doing this.


Nickname validation

Validation of Nickname in HOME.jsx

@khrm how are you handling client side part??


中文文档中实际显示为英文文档

ByConity 简介中第三节实际显示依然是英文文档
![image](https://github.com/ByConity/ByConity/assets/156054018/985241b3-d188-4f8e-90e8-82e16ad4c178

hi! @tigerwangyb, can help take a look? thanks!

PR #221


FEATURE: Automatically open assignee chooser

Automatically expand the assignee user chooser when showing the assign modal.

This will only work for newest discourse instance, and do nothing for older installs. I guess you know this, but just noting it.


Last minute API additions for Gthree

Gthree has some in tree functionality that really belongs to Graphene.
Proposed changes:

add graphene_triangle_init_from_float() initializer; this is useful for buffer objects with lots of triangles stored as vectors of floating point values
add intersection methods for graphene_ray_t; this is used for hit testing objects like spheres, boxes, and triangles

Would be nice if @alexlarsson could do a review so I can merge it in time for next week's GNOME 3.34.0 release.

So, this looks overall good to me, but there is something weird with the triangle intersection kind.
I ported gthree to use this new API here:
https://github.com/alexlarsson/gthree/tree/use-graphene-intersection
However, with this PR as-is, it gets the tri intersection kind wrong here: https://github.com/alexlarsson/gthree/blob/use-graphene-intersection/gthree/gthreemesh.c#L217 as can be seen in the interactive demo. If i switch SIDE_FRONT/BACK around it works, but otherwise it doesn't.
The fix for this is to switch the two kinds in intersect_triangle like so:

diff --git a/src/graphene-ray.c b/src/graphene-ray.c
index 56bc051..b0bf411 100644
--- a/src/graphene-ray.c
+++ b/src/graphene-ray.c
@@ -661,13 +661,13 @@ graphene_ray_intersect_triangle (const graphene_ray_t      *r,
     }
   else if (DdN > 0)
     {
-      kind = GRAPHENE_RAY_INTERSECTION_KIND_ENTER;
+      kind = GRAPHENE_RAY_INTERSECTION_KIND_LEAVE;
       sign = 1.f;

     }
   else
     {
-      kind = GRAPHENE_RAY_INTERSECTION_KIND_LEAVE;
+      kind = GRAPHENE_RAY_INTERSECTION_KIND_ENTER;
       sign = -1.f;
       DdN = -DdN;
     }

This actually matches what three.js does here:
https://github.com/alexlarsson/gthree/blob/use-graphene-intersection/gthree/gthreemesh.c#L217
Where if DdN > 0 and we're backface culling then we have no intersection, which totally smells like a LEAVE kind of intersection to me.
This was actually how I coded the gthree version of the intersector initially, but I had to switch it around to make the code work. Reverting this to what three.js does is nice, but I don't understand what the difference is. Why did I have to revert it to make the previous version in gthree code work???

Ah, i found the difference:
-  kind = ray_intersect_triangle (local_ray, vC, vB, vA, &t);
+  kind = graphene_ray_intersect_triangle (local_ray, triangle, &t);

I.e. the old gthree code passed the vertices in the wrong order, effectively flipping the triangle.
So, the patch about is right and should be applied.

So, this looks good. I thought there were some issue with the sign of the v coord initially, but that was just due to some weirdness in how the graphene box primitive sets up the uv coords.


Add Envelope From and Recipient metadata

I needed to keep track of SMTP recipients, which is not stored in the actual e-mail headers. This is useful for e.g. newsletters and other mailing lists, which might have a not-personal To header set. (Envelope From and Recipients from the SMTP transaction is the actual information, and headers From and To are only for human consumption)
I also added the info on the frontend:

For what it is worth:  I have build mailcrab with the patch of the envelope feature applied.
Now I am reporting "I don't see any envelope information" in the web interface.

I tested with swaks  (get it by sudo apt install swaks).  Screenshot follows, note the difference in envelope from and From:
$ cat mailcrab.test
export<EMAIL_ADDRESS>export SWAKS_OPT_h_From='"Fred Example"<EMAIL_ADDRESS>$ source mailcrab.test
$ swaks --to foo@bar --server mailcrab.vincent.mig:1025
=== Trying mailcrab.vincent.mig:1025...
=== Connected to mailcrab.vincent.mig.
<-  220 mailcrab-backend ESMTP
 -> EHLO redacted.blur
<-  250-server offers extensions:
<-  250 8BITMIME
 -> MAIL<EMAIL_ADDRESS><-  250 OK
 -> RCPT TO:<foo@bar>
<-  250 OK
 -> DATA
<-  354 Start mail input; end with <CRLF>.<CRLF>
 -> Date: Sun, 02 Apr 2023 15:15:36 +0200
 -> To: foo@bar
 -> From: "Fred Example"<EMAIL_ADDRESS> -> Subject: test Sun, 02 Apr 2023 15:15:36 +0200
 -> Message-Id<EMAIL_ADDRESS> -> X-Mailer: swaks v20181104.0 jetmore.org/john/code/swaks/
 ->
 -> This is a test mailing
 ->
 ->
 -> .
<-  250 OK
 -> QUIT
<-  221 Goodbye
=== Connection closed with remote host.
$

Challenge:  Those who can provide a picture of envelope information in the mailcrab webview, please do. Just telling where to see the envelope information is also fine.

Envelope is the SMTP transaction, so its metadata is not visible inside the e-mail headers. I have provided a screenshot in the PR description showing the Envelope data in the frontend list entries.

I have provided a screenshot in the PR description showing the Envelope data in the frontend list entries.

When to know where to look, it is much easier to see.

Thank you @epilys! Seems really useful. I'll release this in v0.13.0


using Yarn in the "run" phase

Recently, yarn was removed from our base node image, and instead we are doing npx yarn install in the assemble phase.  So for this image we've updated our assemble phase to do a similar thing, if yarn in enabled.
In the run script, a user is allowed to override what is run with the $NPM_RUN environment variable.  In the Using For development section of the readme, we show overriding that variable with yarn start.  this will actually fail since yarn is no longer installed.
We have some options here.

We update the README to use npx, NPM_RUN="npx yarn start"

We could add npx to the run script, so that might look like npx $NPM_RUN

We are going to go with Option 1,  just adding in some readme updates


All windows tile temporarily on reload

When I reload my yabai configuration with launchctl kickstart -k "gui/${UID}/homebrew.mxcl.yabai", all of my windows tile, then the ones that are set to manage=off float again. This is annoying though because it destroys the existing window layout and leaves me with a bunch of irregularly shaped windows that look tiled (the sizing and position) but are actually floating. Is this intended behavior?

The configuration file is loaded asynchronously. Move the line that sets the default space layout to bsp after the lines configuring the window rules, that should solve your issue.

Thank you! That fixed it 😁


Package won't install on Windows

I am using Windows 7 with version 1.0.7 of Atom .
I have tried to install the package several different ways and for some reason it won't install.
Please advice.

Hi @rwatts3,
There's nothing particularly advanced about this theme; it's just another ordinary syntax theme. So if other themes install just fine then it might be something really simple.
First, can you please provide more information? What does it do? Does it hang half-way through the install? Does it install fully but then doesn't show up in the syntax theme dropdown list? Do you get a red Atom error popup? If so, what does the error message say?
Some additional troubleshooting:
• Remember this is a syntax theme not a UI theme. Could you be looking in the UI theme dropdown instead of the syntax theme dropdown which would make you think it didn't install?
• Will other syntax themes install properly?
• Are you having any Internet connection issues?

I'm on Mac OS X 10.11 Beta (15A262e),
I've uninstalled the theme and am trying to reinstall it and it's hanging on the installing button animation. Other themes install just fine.
I'll keep looking into this!

Hi. Actually. It installs perfectly on my Mac. Not in Windows. Yes I'm
certain I am following the install procedure correctly. When you click
install. It will hang and never install.
On Fri, Aug 21, 2015 at 11:05 PM Nathan Buchar<EMAIL_ADDRESS>wrote:

I'm on Mac OS X 10.11 Beta (15A262e),
I've uninstalled the theme and am trying to reinstall it and it's hanging
on the installing button animation. Other themes install just fine.
I'll keep looking into this!
—
Reply to this email directly or view it on GitHub
https://github.com/nathanbuchar/atom-peacocks-in-space-syntax/issues/1#issuecomment-133643328
.

As I don't have a Windows machine, this is difficult for me to test; However if anyone else coming to this thread is having the same issue, please add a :+1:

Hi,
I'm trying to install this theme in atom under windows 7 SP1 and I get the following error:
Installing<EMAIL_ADDRESS>failed.Hide output…

><EMAIL_ADDRESS>install C:\Users\user\AppData\Local\Temp\apm-install-dir-116627-100400-kph38y\node_modules\peacocks-in-space-syntax\node_modules\gulp-sass\node_modules\node-sass
> node scripts/install.js

Binary downloaded and installed at C:\Users\user\AppData\Local\Temp\apm-install-dir-116627-100400-kph38y\node_modules\peacocks-in-space-syntax\node_modules\gulp-sass\node_modules\node-sass\vendor\win32-ia32-11\binding.node

'C:\Users\user\.atom\.node-gyp\aliases.cmd' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Users\\user\\AppData\\Local\\atom\\app-1.8.0\\resources\\app\\apm\\bin\\node.exe" "C:\\Users\\user\\AppData\\Local\\atom\\app-1.8.0\\resources\\app\\apm\\node_modules\\npm\\bin\\npm-cli.js" "--globalconfig" "C:\\Users\\user\\.atom\\.apm\\.apmrc" "--userconfig" "C:\\Users\\user\\.atom\\.apmrc" "install" "C:\\Users\\user\\AppData\\Local\\Temp\\d-116627-100400-bj3anv\\package.tgz" "--target=0.36.8" "--arch=ia32"
npm ERR! node v0.10.40
npm ERR! npm  v2.13.3
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node scripts/install.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node scripts/install.js'.
npm ERR! This is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node scripts/install.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls node-sass
npm ERR! There is likely additional logging output above.

Is there any way this issue can be solved? I'd really love to be able to use this theme!

Hi @nickelozz,
This looks like it might be an issue with node sass. More interestingly: why am I requiring gulp-sass? I'll remove those dependencies tonight. In the mean time, you should be able to add the syntax theme to Atom's "packages" directory manually.
Simply download this repo and unzip it. Rename the folder to peacocks-in-space-syntax, drag this folder into C:\Users\<user>\.atom\packages, then restart Atom to make it available :)

Should be fixed now.

Hello @nathanbuchar I can confirm it's working now and is looking dandy!
Unless someone else notices any odd behavour I think it's safe to close this issue. Thanks a bunch!


Speech to text examples not recognizing speech but "try it out" page does  - both from file and from mic.

output.zip
speechlog.log
Hi there,
zip of .wav file and log file attached.
SDK version: 1.38.0

OS: Windows 10 Enterprise
Hardware: x64
Language: Python 3.11.9
Browser: Chrome

Bug description:
I am using the two examples of recognizing speech from either a file or a microphone from: https://learn.microsoft.com/en-us/azure/ai-services/speech-service/how-to-recognize-speech?pivots=programming-language-python .
From file: I have recorded a .wav file using pyaudio, using the following code:
import wave
import pyaudio

CHUNK = 1024
FORMAT = pyaudio.paInt16
CHANNELS = 1
RATE = 44100
RECORD_SECONDS = 5

with wave.open('C:/Users/DKSEBT/AIR/output.wav', 'wb') as wf:
    p = pyaudio.PyAudio()
    wf.setnchannels(CHANNELS)
    wf.setsampwidth(p.get_sample_size(FORMAT))
    wf.setframerate(RATE)

    stream = p.open(format=FORMAT, channels=CHANNELS, rate=RATE, input=True,input_device_index=2)

    print('Recording...')
    for _ in range(0, RATE // CHUNK * RECORD_SECONDS):
        wf.writeframes(stream.read(CHUNK))
    print('Done')

    stream.close()
    p.terminate()

I attempt to recognize the speech in the wav file with the following code:
def from_file():
    audio_config = speechsdk.AudioConfig(filename="C:/Users/DKSEBT/AIR/output.wav")
    speech_recognizer = speechsdk.SpeechRecognizer(speech_config=speech_config, audio_config=audio_config)
    result = speech_recognizer.recognize_once_async().get()
    print(result.text)
    return result

result = from_file()

The audio file plays fine. The "Try it out" recognizes the speech perfectly if I upload the file.
I get a result file with no text after 80 seconds of running, with properties:
{<PropertyId.SpeechServiceResponse_JsonErrorDetails: 5001>: 'Timeout: no recognition result received SessionId: 982e4c8b0871444db51a166649c8a1d3'}
Text to speech works fine with the config with the same endpoint and subscription key. If i change a character in either, corrupting my keys, the function exits quickly with reason: cancelled.
With the from microphone function:
I am using the following code:
def from_mic():
    audio_config = speechsdk.AudioConfig(device_name ="{<IP_ADDRESS>00000}.{6e85290b-2520-4a95-8563-13c0d2479c45}",use_default_microphone=False)
    speech_recognizer = speechsdk.SpeechRecognizer(audio_config = audio_config,speech_config=speech_config)

    print("Speak into your microphone.")
    result = speech_recognizer.recognize_once_async().get()
    print(result.text)
    return result

This function finishes after 70 seconds with properties:
{<PropertyId.SpeechServiceResponse_JsonErrorDetails: 5001>: 'Timeout: no recognition result received SessionId: 81a4e63ef38d44568d3ae992ac974248'}
And with an empty string in .text.
I am quite sure I have the correct device name (i got it via this method:https://stackoverflow.com/questions/67501540/while-working-with-azure-speech-sdk-on-windows-how-to-get-device-name-for-crea ), as I can hear the noise-cancellation change in the headphones when I run the function. I have tried the same with default microphone when headphones are not connected. Using the "Try it out" page, both microphones work fine and the speech is recognized perfectly.
Cheers for the efforts.

try changing RATE = 44100 to RATE = 16000 as the service only supports a few input formats, and that is what stands our at first glance, as everything I've seem before was either 16k or 8k, 16 bit, mono pcm...

Thanks for the quick reply Brian!
I have tested:
Rates 16000 and 8000. Int16 and Int8 formats, chunk size 264, 512,1024 and 2048.
Still works fine on the "Try it out" page, but not using the API.
Again its the same with microphone input. Works fine on the page, not via the API.
Thanks


This project only support std = c++17. Is there any other version?

I want to deploy keras model to embedded linux system.
I need use arm tool chain to build source code.
Currently, arm tool chain can not support  C++17.
Is there c++14 version code?

You cat try to compile it!

thanks
i will try it .

在 2019年6月26日，20:29，Georgy Perevozchikov<EMAIL_ADDRESS>写道：
You cat try to compile it!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

It doesn't seem to work with C++11 but I am constrained to use it as of now because of firewall issues. Any work around?

Thank you. Now I am working on another project. I need not it any more.

在 2020年7月14日，04:17，SundarRamanP2000<EMAIL_ADDRESS>写道：
It doesn't seem to work with C++11 but I am constrained to use it as of now because of firewall issues. Any work around?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Thanks! I installed gcc5

I had the same issue, so I added C++11 capabilities to go along with the C++17 capabilities (switchable in the CMake).  Runs fine visual studio 2015 and gcc 4.8.5.  I can push it if someone else needs it.


Feature Request: .md extractor

Feature Request, a short description related to extractors, result items
As a admin, i need a markdown format, similar to the existing readability format,
to catch .md  items for further, external downstream processes
the ideal specific solution
As a user, i can define MD as (additional) format for my (to be archived) items,
to get these items in our publishing worklow and as a result,
back to our commonly used MD based knowledge base.
Good for Applications like MkDocs, Trilium or similar other MD based Applications.
actual solution
At the moment a MD Webclipper as browser extension do the job, with some additional options also.
https://github.com/deathau/markdownload  (MIT and Apache2 licenses only)
how important
as i can (not clear) see, a twin from the readability extractor, paired with great stuff, e.g. from mentioned .md Webclipper, could have potential for a low hanging fruit!? :-)
edit: if primary focus on converting, then an info.json could solve it. (like yt-download doing)
low code performer like me can work better with lightweight formats :)
personally i'll say its an improvement that can increase (not only) effiecenty in downstream processes

[x] I'm willing to contribute dev time / money to fix this issue
[x] I like ArchiveBox so far / would recommend it to a friend
[x] I've had a lot of difficulty getting ArchiveBox set up (i´ll describe it outside this feature request)

The mercury extractor has --format=markdown. In archivebox the option is set to --format=text You just need a way to change the argument.
(MERCURY_ARGS config option when? 😄 (I could work on that actually)


Multiple title options

Added support for multiple --reject-title and --match-title options. Added test test_options.py.

What's the point actually? Both are regexes, you can just pass arbitrary regex in single command.

I think if it's going to accept multiples of these options it should handle them in some way, rather than just throw away all but the last. Even if it's to fail and say it only accepts one and advise the user.
While I was in there I accidently noticed it accepted --reject without thowing up an "unrecognized option" error and exiting.


Error while running on colab

Traceback (most recent call last):
File "/content/replit-3B-inference/ctransformers/../inference.py", line 3, in
from ctransformers import AutoModelForCausalLM, AutoConfig
ImportError: cannot import name 'AutoModelForCausalLM' from 'ctransformers' (unknown location)

worked for me now..

worked for me now..

can you share what commands you have used?


Popover problem when scrolling page

Bug report
Current Behavior

https://github.com/radix-ui/primitives/assets/129002577/6a1d9717-7eca-42f6-8b93-958d79161c1c

I expect popup to be closed while scrolling

Close popover when user scrolls page

Software
Name(s)
Version

Radix Package(s)
@radix-ui/react-popover
1.0.7

React
n/a
18.2.0

Browser

Chrome

Assistive tech

-

Node
n/a
n o

npm/yarn

yarn

Operating System
Mac

@chertik77 if you're not working on this issue can you assign it to me ? I am willing to contribute.

I think you are looking for hideWhenDetached prop?

Doesn't work

I think you are looking for hideWhenDetached prop?

Doesn't work

@chertik77
you can add scroll event, check if direction is up and close the popover manually right?
https://stackoverflow.com/a/62497293
const [open, setOpen] = useState(false)

const [scrollDir, setScrollDir] = useState("scrolling down");

useEffect(() => {
  const threshold = 0;
  let lastScrollY = window.pageYOffset;
  let ticking = false;

  const updateScrollDir = () => {
    const scrollY = window.pageYOffset;

    if (Math.abs(scrollY - lastScrollY) < threshold) {
      ticking = false;
      return;
    }
    setScrollDir(scrollY > lastScrollY ? "scrolling down" : "scrolling up");
    lastScrollY = scrollY > 0 ? scrollY : 0;
    ticking = false;
  };

  const onScroll = () => {
    if (!ticking) {
      window.requestAnimationFrame(updateScrollDir);
      ticking = true;
    }
  };

  window.addEventListener("scroll", onScroll);
  console.log(scrollDir);

  return () => window.removeEventListener("scroll", onScroll);
}, [scrollDir]);

useEffect(() => {
  if (scrollDir === "scrolling up") {
	setOpen(false)
  }
}, [scrollDir])

...


Signup page throws 404 Not found error

Signup page throws 404 Not found error
URL: https://unitaryhack.dev/signup/

Thanks for the issue! Where did you find a link to this page? It's not used on the current website, so we removed it.

It's in the After the Hack section of https://unitaryhack.dev/hacker-guide/


Bug when going in a subview of a tab having an url name contained in another tab url.

Here is a codepen describing the bug: http://codepen.io/mvidailhet/pen/azEjWL
I have 3 states:

tabs.home: url = "/home"
tabs.subview: url = "/addlist"
tabs.add: url = "/add"

tabs.home and tabs.add are both tabs roots. tabs.subview is a subview of tabs.home.
If I click on the "Add list" button on the home tab, the app will select the Add tab and go to the add list subview without showing the content of the add list view. If you click on the home tab, it will "go back" to the add list view.
The problem comes from the url "/addlist" that contains the url of the tabs.add state. If you rename the url to "test" for example, it works as expected.
Hope this helped.
Love your work

Greetings @mvidailhet!
My sensors indicate that you need to update your issue through our custom issue form. We are now requiring all issues to be submitted this way, to ensure that we have all of the information necessary to fix them as quickly as possible.
Click Here To Update Your Issue
I will have no choice but to close this issue if it is not resubmitted through the form. Please fill out the rest of the form, so that I may use my friendly robot powers to assist you.
Thank you!

Greetings @mvidailhet!
I've closed this issue because my sensors indicated it was old and inactive, and may have already been fixed in recent versions of Ionic. However, if you are still experiencing this issue, please feel free to reopen this issue by creating a new one, and include any examples and other necessary information, so that we can look into it further.
Thank you for allowing me to assist you.


Remove Cargo.lock because this is a library package.

Let the applications decide on specific versions. Specify dependencies with only Cargo.toml.
https://doc.rust-lang.org/cargo/guide/cargo-toml-vs-cargo-lock.html
https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
Tests still pass with:
$cargo --version
cargo 1.56.0 (4ed5d137b 2021-10-04)
$rustc --version
rustc 1.56.1 (59eed8a2a 2021-11-01)

I agree. I have added a commit to this PR to add Cargo.lock to .gitignore


Inquiry of robustness of model with humanoid robot

Has the model been trained for use with humanoid robots with the ability to walk and hold objects?

No, the RT-*-X models have not been trained with humanoids. That being
said, the models are trained with end-effector delta as the action space.
So if you have the data from humanoids, it will be very useful if you share
it with the community or try finetuning the model with your data.
On Sun, Mar 24, 2024 at 2:38 PM 'Philip Amadasun' via Open X-Embodiment
Core @.***> wrote:

Has the model been trained for use with humanoid robots with the ability
to walk and hold objects?
—
Reply to this email directly, view it on GitHub
https://github.com/google-deepmind/open_x_embodiment/issues/51, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BDPTRVMAQU737WEV4XKSCPLYZ5BUBAVCNFSM6AAAAABFGAIBVGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIYDINJWG42TEMY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>
--
You received this message because you are subscribed to the Google Groups
"Open X-Embodiment Core" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to @.***
To view this discussion on the web visit
https://groups.google.com/d/msgid/open-x-embodiment/google-deepmind/open_x_embodiment/issues/51%40github.com
https://groups.google.com/d/msgid/open-x-embodiment/google-deepmind/open_x_embodiment/issues/51%40github.com?utm_medium=email&utm_source=footer
.

@open-x-embodiment Thanks for the feedback. Would you happen to know of any models that already have some pretraining on this?

Couldn't one create synthetic data using computer models of various robots?


WIP: CHG lock down container security

This PR covers the two issues under the container security milestone.

Removing root containers
Adding security contexts

We are removing root containers where ever possible from Anubis. While I am not worried about most of the services ever getting popped, there are several places that run student code. Those places have been in desperate need for k8s security contexts that disable things like priv esc.

This PR is still in WIP status because the changes have not yet been tested. We are going to need to verify that the new submissions pipeline unix permissions work. We also will need to make sure that the theia pods get started ok.


Autocomplete across files

I switched to VSC from Atom and one very useful feature I miss is autocomplete across opened documents. So for example, I have 3 files opened and in file 1 I have a variable called "thisIsExample". I switch to File 2 and start typing thisI... and VSC would auto-complete from the other file.
This currently works, but the auto-compete, AFAIK only works within the opened file, but it is extremely useful when you can do this with all the opened files in the editor because if for example you have files that work together and use the same variables you dont have to switch to the other one just to check what you called it. In Atom this was possible.

dupe of #20886


Actions must be plain objects. Use custom middleware for async actions

A student ran into this error while working on his React app:

Error: Actions must be plain objects. Use custom middleware for async actions.
dispatch
node_modules/redux/es/createStore.js:152
RegistrationForm.onSubmit
src/components/RegistrationForm.js:16
  13 | 	const user = {username, password, firstName, lastName};
  14 | 	console.log(values);
  15 | 	alert('info received');
> 16 | 	return this.props
  17 | 	.dispatch(registerUser(user))
  18 | 	.then(() => this.props.dispatch(login(username, password)));
  19 | }
View compiled
(anonymous function)
src/components/RegistrationForm.js:22
  19 | }
  20 | render() {
  21 | 	return (
> 22 | 		<form className="registration-form" onSubmit={this.props.handleSubmit(values =>
  23 | 			this.onSubmit(values))}>
  24 | 			<fieldset>
  25 | 				<label htmlFor="first-name"></label>
View compiled
▶ 23 stack frames were collapsed.

restaurant-schedule-app

@yh2n what was the resolution for this problem?

Hey,
How are you?
The issue was that I had forgotten to add redux-thunk, so my asynchronous
actions were not being processed...
On Wed, Feb 21, 2018 at 3:53 PM, Mark Nyon<EMAIL_ADDRESS>wrote:

@yh2n https://github.com/yh2n what was the resolution for this problem?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/trystant/dev-error-messages/issues/3#issuecomment-367468293,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXsyzztUDb41Kpr66tQPPAgbXFWdwra6ks5tXIIpgaJpZM4QnujR
.


Copy kubectl from docker container

Nearly the last stage of source all components to containers.
Kubectl will be called from hyperkube image.
Remaining tasks:

Move kube_version variable to kubernetes/preinstall
Drop placeholder download.nothing requirement

+1


Feat upgrade edition

upgrade cargo edition to 2021
upgrade some crate's version
producer auto create topic when it not exists.

Please run cargo fmt to format the code.

Thanks!


Tests fail to compile on GHC 8.6.1

cuckoo-filter's test suite currently fails to compile on GHC 8.6.1 with the following error:
test/Spec.hs:23:9: error:
    • No instance for (Control.Monad.Fail.MonadFail
                         Data.Functor.Identity.Identity)
        arising from a do statement
        with the failable pattern ‘Just f’
    • In a stmt of a 'do' block: Just f <- insert defaultFilter s
      In the second argument of ‘($)’, namely
        ‘do Just f <- insert defaultFilter s
            f' <- delete f s
            not <$> member s f'’
      In the expression:
        runIdentity
          $ do Just f <- insert defaultFilter s
               f' <- delete f s
               not <$> member s f'
   |
23 |         Just f <- insert defaultFilter s
   |

I believe this is for ChrisCoffey/cuckoo-filter rather than this repo.


New: November fundraising blog post update

This is a blog post update about fundraising. I'd like to get this out tomorrow (07 November), so please take a look!

LGTM, thanks! I think we should also cross-post those updates in OpenCollective.

Might be nice to tweet it too!

I'll do both! Thanks everyone.


fix: comments added on the blank canvas do not show up in the deployed version

Description
Will render base canvas even if there are no children and show the empty page graphics on top
Fixes #5812
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

manual

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes


ISOTROPIC_COS_SCALING in mom_vi_hdissip.F

When I look at the ISOTROPIC_COS_SCALING implementation in mom_vi_hdissip.F (from pkg/mom_vecinv), I have the impression that these additional "cosFacU/V" are not applied in the same way in the useVariableViscosity part and the other part (corresponding to constant viscosity), and this would be the case for both harmonic and biharmonic viscosity.

For harmonic-visc with useVariableViscosity=T
"cosFacU" (line 63) applies to both "uD2" contributions (parenthesis at the end of line 61) ; and "cosFacV" (line 70) also applies to both "vD2" contributions (parenthesis at the end of line 68).

For harmonic-visc with useVariableViscosity=F
"cosFacU" (line 94) only applies to "uD2" second term  (i.e., difference "Zip - Zij") ; and "cosFacV" (line 100) also applies to "vD2" second term  (i.e., difference "Dij - Dim").

The same differences are also there for the biharmonic viscosity but only when MOM_VI_ORIGINAL_VISCA4 is left "#undef", which is the default.

At this point, I did not run a test that demonstrates the differences; and not completely sure which version of this ISOTROPIC_COS_SCALING is the right one.

This happened here. And this is the corresponding message in doc/tag-index (checkpoint58d_post):
mom_vecinv: add ISOTROPIC_COS_SCALING flags to mom_vi_hdissip for completeness
From the tag-index entry (and the inconsistent code), it is safe to assume that I didn't know what I was doing when I added this. Additional notes:

With ISOTROPIC_COS_SCALING undefined, the mom_fluxform version scales only the I-part of the gradient with cosFac, with ISOTROPIC_COS_SCALING defined cosFac is used for both parts. This discimination is not possible for the mom_vecinv version because hDiv and vort3 mix differentiation in I and J direction. I think that any application of cosFacU/V is wrong in this context and should be removed, that is, mom_vi_hdissip for spherical-polar grids gives the wrong derivatives in the horizontal Laplacian terms if cosPower>0 and cosFacU/V<1 (default is cosPower=0).
why do we differentiate between useVariableViscosity=T and F? The 3D fields are always defined (and filled with the constant values if there is no variable viscosity).
a quick search showed that ISOTROPIC_COS_SCALING is never defined in verification.

I suggest to simplify mom_vi_hdissip.F to

remove all cosFacU/V (and corresponding cpp-flag ISOTROPIC_COS_SCALING), because I think they are all wrong.
remove case useVariableViscosity=F

needless to say, that my suggestion (that is, the second point of removing the useVariableViscosity=F part) modifies some verification experiments on my MacBook (exf.nlfs, all global_ocean.cs32x15, shelfice_2d_remesh), interestingly some experiments (e.g. global_ocean.cs32x15.seaice) improve relative to the reference.

@mjlosch I think it's good to keep a separated block for useVariableViscosity=F : in this case the model does not call at all MOM_CALC_VISC, code is simpler and probably faster.
Regarding the cosFacU/V :

the first set (outside "#ifdef ISOTROPIC_COS_SCALING") looks safe to me, will not have the same effect as in pkg/mom_fluxform, but it could help to get a stable viscosity/time-step e.g., on lat-long grid. Also seems like it was there in the first version of this routine. So I would prefer to keep it and could add a WARNING if cosPower is used with Vector-Inv and  useStrainTensionVisc=F ? (but I don't see any cosFacU/V in pkg/mom_common/mom_hdissip.F).
for the ISOTROPIC_COS_SCALING part, it's less clear that this is really useful (or may be I am missing something) as you mentionned above.

Anyway, I would not rush to submitt a new PR before PR #817 is merged in since it affects significantly this S/R (and since the Pb has been there since 2006 it could wait a little bit).

There is also a little issue with how ISOTROPIC_COS_SCALING is set:
I think it's confusing when a CPP option is set AND unset in 2 distinct header files that can be included in the same source file, in this case ISOTROPIC_COS_SCALING could be set/unset in GAD_OPTIONS.h and in CPP_OPTIONS.h.
It would be cleaner to have it in  GAD_OPTIONS.h and in MOM_COMMON_OPTIONS.h (except that this does not work for pkg/ggl90, pkg/gmredi, and pkg/seaice).

I am going to fix this in a new PR.


API Documentation Comments

[ ] Some code snippets are missing syntax highlighting or have inconsistent indentation. i.e. the box example has inconsistent spacing between = and values.
[ ] `FLCInterfaceCollisionWorld code snippet could use consistent comments and formatting
[ ] Add usage examples for every major class or function. While some classes, like FCLInterfaceCollisionWorld, include examples in their descriptions, others, like FCLInterfaceCollisionObject, do not. Providing at least one usage example per key type or function will make the API more approachable.
[ ] Some assumptions are not immediately obvious. These assumptions should be stated explicitly near the relevant sections. e.g. "objects are in the same reference frame.
[ ] You reference test files like interface_test.cpp but don’t describe their contents. Add brief notes about what each test demonstrates (e.g., “tests collision between a box and sphere in the same frame”).
[ ] add some comment on error handling, state how errors are reported across the API. i.e.  what happens if nullptr is passed to addCollisionObject

This issue is part of a JOSS review.

Hi @Aravind-Sundararajan, can you be more specific about "consistent" or "inconsistent" comments/formatting? For example, I cannot see how the box example has inconsistent spacing. Please provide more complete snippets, thank you.

@mazrk7
For the first question, I thought on my initial review that there were inconsistent spaces and that there were missing syntax highlighting; however upon a second review I can see these review comments are erroneous or I can't see the error.  Feel free to mark this as completed.
Second, I noticed that the  example for FCLInterfaceCollisionWorld is the only section in the api documentation where you have inline comments, you may want to change it so these are not inline.
std::string frame_;  // Collision world reference frame
std::vector<FCLInterfaceCollisionObjectPtr> fcl_collision_objects_;  // List of collision objects in the world
unsigned int obj_counter_;  // Counter for object IDs


Broken model run tests

I think the gmake file wasn't updated somewhere along the way, so the new NGen.cpp fails to build.
[ 97%] Building CXX object CMakeFiles/ngen.dir/src/NGen.cpp.o
714
/ngen/src/NGen.cpp: In function 'int main(int, char**)':
715
/ngen/src/NGen.cpp:241:55: error: 'time_step' was not declared in this scope
716
         catchment_outfiles[formulation_pair.first] << time_step << "," << current_timestamp << "," << output_str << std::endl;
717
                                                       ^~~~~~~~~
718
/ngen/src/NGen.cpp:241:55: note: suggested alternative: 'time_step_t'
719
         catchment_outfiles[formulation_pair.first] << time_step << "," << current_timestamp << "," << output_str << std::endl;
720
                                                       ^~~~~~~~~
721
                                                       time_step_t
722
gmake[3]: *** [CMakeFiles/ngen.dir/build.make:63: CMakeFiles/ngen.dir/src/NGen.cpp.o] Error 1
723
gmake[2]: *** [CMakeFiles/Makefile2:75: CMakeFiles/ngen.dir/all] Error 2
724
gmake[1]: *** [CMakeFiles/Makefile2:87: CMakeFiles/ngen.dir/rule] Error 2
725
gmake: *** [Makefile:175: ngen] Error 2
726
The command '/bin/sh -c cmake --build /ngen --target ngen' returned a non-zero code: 2
727

Current behavior
Model runs are failing at the build, and need to be fixed.
Expected behavior
Every time the action is triggered with new PRs the model should run
Steps to replicate behavior (include URLs)

https://github.com/NOAA-OWP/ngen/runs/1299970026?check_suite_focus=true

Screenshots

This happens because the CI container is building from master (see line 579 below):

So a previous bug in the driver snuck through the PR test because it was running the BASE, not the branch of the PR.  The next PR fails because it runs the base with the bug from the previous PR.

#209 doesn't fix the root cause, which is the action runs master on ngen, not the PR.

Right, it runs master, but now this variable is fixed in master, so we should not get the error that Zach pasted at the top whenever the CI clones and runs master.

This test PR now passes the CI:
https://github.com/NOAA-OWP/ngen/pull/211


Fix: Accept only option flags in CRYSTAL_OPTS

Fixes #11164. CRYSTAL_OPTS is processed before the command-line arguments, the two sets of options more or less sharing the same OptionParser. Note however that crystal eval has never supported the full set of compiler options (e.g. CRYSTAL_OPTS=--prelude=empty crystal eval will not work).
With this patch CRYSTAL_OPTS never interferes with the original command line, so they can be safely applied to every compiler command backed by an OptionParser. The exceptions are crystal env (a parser is added in #11720) and The only exception is crystal interactive.

Love this change.  This almost make me think something like this could be built-in to OptionsParser.  For example, in my app I'd love to have a FOO_OPTS set of overrides to my CLI, and somewhere in my usage of OptionsParser, it would be cool to just say something like opts.env_override = "FOO_OPTS" or opts.env_override = ENV["FOO_OPTS"]

This PR was reverted in #11920 and a fixed version eventually merged in #11922


How To Install It On Macbook

Hi,
Please include steps to install your app on Macbook and a few examples of commands to scan .IPA files to find vulnerabilities.

Hi @kpratik9 you can download pre compiled binaries and install on your machine like any other OS. We don't support analysis on IPA or APK files on Open Source version.


Provide accessor functions with checks?

Currently the functions to access the pbf encoded data don't check whether it has the right format. Should we add functions that do?
auto a = pbf.varint(); // what if it is not a varint?
auto a = pbf.checked_varint(); // throws if it is not

Or should all functions check? This would add some overhead but make everything more robust.
We can add assert()s, but this will not solve the problem of intentionally or unintentionally corrupted data in production systems.
/cc @springmeyer @artemp @kkaefer

My proposal: pbf.varint() should check, and pbf.unchecked_varint() would not.
What does libprotobuf and https://github.com/haberman/upb do?

From a short experiment it looks like Google libprotobuf does an assert().

:+1: to assert in debug mode (so -DNDEBUG).

As per voice discussion we'll use assert() in the code. I have already implemented that in the current code base. We can later benchmark the code and see whether enabling the checks makes the code significantly slower.


[SourceKit] use "inproc" variant of SourceKit on Linux

What's in this pull request?
Set the SWIFT_SOURCEKIT_USE_INPROC_LIBRARY cmake variable to TRUE when building on Linux because the interprocess version likely won't be available for quite some time given that libXPC hasn't yet been ported, and the in process version nearly works.
This is NFC since SourceKit still isn't built by default on Linux.
cc @akyrtzi @briancroom @modocache
Resolved bug number: (SR-1676)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

@swift-ci please test


Applying most common MTL material properties in 3D preview

Implement shaders supporting most common MTL material elements in 3D preview: color maps, normalmap, roughness, displacement, etc.

DONE:

Color maps are supported.
Normal maps are supported as bump (map_bump) elements.
Roughness maps are supported as specular exponent.

TODO:

Support for displacement maps should still be implemented in the material shader.
PBR shader could be implemented as a custom shader in #65 (future release).


Support Right-to-Left localization

For some symbols such as arrow.up.backward.and.arrow.down.forward.circle, SF Symbol suggests to use Right-to-Left localization to flip the symbol horizontally.
But .arrowUpBackwardAndArrowDownForwardCircle.localized(to: .rtl) will return nil.
Is Right-to-Left not supported?

We do support localizing to RTL, but it's only possible if that symbol supports explicit localization. Unfortunately, Apple did not add support for that symbol, it will only be implicit (when the whole app is using a RTL locale).
If you are using UIKit, you can force it using imgView.semanticContentAttribute = .forceRightToLeft

It works great! Thank you!


[TS migration] Migrate RoomInvitePage to typescript

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/31993
PROPOSAL: N/A
Tests

[x] Test main flows of the app(sending messages, logging, requesting money)
[x] Create room and try to invite users, verify that everything works on invite page.

Offline tests

N/A
QA Steps

Same as tests
PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/88395093/244cc268-d035-42c8-a24a-bce08765f5cf

Android: mWeb Chrome

https://github.com/Expensify/App/assets/88395093/633652ec-c155-4434-9c39-d010c129b1ab

iOS: Native

https://github.com/Expensify/App/assets/88395093/6791feac-2d7e-4189-ac53-0d03abd377b4

iOS: mWeb Safari
https://github.com/Expensify/App/assets/88395093/29308e65-e385-4e4e-ae07-4e4259a7c632

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/88395093/f209203e-37d9-4516-93f3-d1f5c7607daf

MacOS: Desktop

https://github.com/Expensify/App/assets/88395093/ccf5b1be-a637-4dbd-9b9a-0c191645a328

@kubabutkiewicz fixed comments 😅

@kubabutkiewicz fixed comments

I’ll check this once I am online. Quick question, is the unit test failure related to this PR?

@mananjadhav tests failure was related to this PR but I've already fixed them

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native
https://github.com/Expensify/App/assets/3069065/b16b6576-a7ec-4932-86fc-3a956b6d5dae

Android: mWeb Chrome
https://github.com/Expensify/App/assets/3069065/2655f9ef-843a-42ab-b048-d98fc419d97c

iOS: Native
https://github.com/Expensify/App/assets/3069065/c4a3e0a9-9c0b-4a36-babd-c00205503b0b

iOS: mWeb Safari
https://github.com/Expensify/App/assets/3069065/cf398d4a-d6fa-4b6b-b003-180c639e541a

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/3069065/a9fd0e74-9ace-4845-ae0d-6ea7644175b4

MacOS: Desktop
https://github.com/Expensify/App/assets/3069065/776a28b2-b160-4f7f-a2cc-4873eba9ab8d

@mananjadhav fixed comments

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to production by https://github.com/thienlnam in version: 1.4.41-12 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


Remote device editor not working on local install

Current Behavior
Noticed while working on https://github.com/flowforge/flowforge/issues/2323 that I could not connect via tunnel:

was working in previous release
Expected Behavior
Tunnel should auto connect user to remote device's editor
Steps To Reproduce
Running localfs, on windows, enable developer mode, turn on Editor Access, launch remote editor from the FF link.
Environment

FlowForge version: 1.8.x-github
Agent version: 1.9.2-github
Node.js version: 16
Platform/OS: windows
Browser: Chrome latest

@Steve-Mcl we need the device agent logs (in verbose mode) to go with this

ok, will get that shortly.
wish we could turn on logs via a remote command - would make this much easier.
will raise a issue/feature request on that too.

Pretty sure this was down to my system Ben.
I will close it for now.


test: use structuredClone polyfill in tests as well

Small refactor to fix JSRPC tests later.

Do we need this polyfill anymore? Vitest doesn't support Node versions below 18

I think you are right. Now that we are testing on Node 18.
I'll leave this open but not land it until I have confirmed.

Closing as our vitest integration requires Node 18 and so this polyfill is not needed.


Parameter 'permissive_ssl' not working on LeapHybridCQMSampler

Description
Trying to sample a CQM through the LeapHybridCQMSampler returns a SSLCertVerificationError, even after setting the parameter 'permissive_ssl' to True when instantiating the LeapHybridCQMSampler. Full traceback attached: traceback.txt
To Reproduce
import os
import dwave.system
from dimod import Integer, ConstrainedQuadraticModel

with open(os.path.join('..', 'dwave_token.txt'), 'r') as file:
    os.environ['DWAVE_API_TOKEN'] = file.read()

x = [Integer(f'x_{i}') for i in range(4)]

cqm = ConstrainedQuadraticModel()

H_Objective = -5*x[0] - x[1] + x[2] - x[3]

cqm.set_objective(H_Objective)

cqm.add_constraint(20 - 10*x[0] - x[1] - x[2] - x[3] >=0)

sampler = dwave.system.LeapHybridCQMSampler(permissive_ssl=True)
sampleset = sampler.sample_cqm(cqm)

Error message:
SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1108)
Environments:

Python 3.8.0 on Windows 10 Enterprise 21H2 19044.2364
Python 3.8.10 on Ubuntu 20.04.5 LTS

@rafamartinc, just to confirm, you are behind a proxy that intercepts and inspects/rewrites your https requests?

Hi @randomir. Not that I know of... But shouldn't the validation be skipped entirely when using the permissive_ssl parameter?

@rafamartinc, you are right, we do have a known issue with permissive_ssl, see https://github.com/dwavesystems/dwave-cloud-client/issues/507. But the fact you're seeing an SSLCertVerificationError means some proxy on your route to D-Wave is rewriting requests and spoofing D-Wave API responses/certificates (in order to inspect the SSL traffic in plain text).
For that reason the use of permissive_ssl is not recommended. (Maybe a "good" actor is rewriting your traffic in your enterprise, but you can't distinguish that from a "bad" actor stealing your API token and/or other private data.)
We'll prioritize fixing this issue (although, we would rather just remove the flag/feature), but in the meantime you can try one of the two known workarounds:

Explicitly specify endpoint in calls to the sampler (either in the D-Wave config file, or as a keyword argument to LeapHybridCQMSampler()). The default endpoint is "https://cloud.dwavesys.com/sapi/", also available as dwave.cloud.Client.DEFAULT_API_ENDPOINT (requires import dwave.cloud). This still requires permissive_ssl=True for SAPI requests.
Provide proxy CA cert, if your network admin can share it with you. See here. This would be a preferred solution since you are explicitly authorizing your local network proxy to modify the certificate (but not others). Also, this option does not require the use of permissive_ssl.

Hi @randomir,
Workaround #2 was very closely related to the issue here. It was a specific configuration in our network, so we finally managed to get it solved - for now at least. It would be great to have issue #507 solved though, to avoid further issues, so we'll keep an eye on that one as well.
Thank you so much!


[OSD-24207] Updated logic to delete oldest image of each type per region

What does this PR do? / Related Issues / Jira
Cleanup script makes sure to delete the oldest image of each type per region, not just the oldest image
Checklist

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have made corresponding change to the default configuration files
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have tested the functionality against gcp / aws, it doesn't cause any regression
[ ] I have added execution results to the PR's readme

Reviewer's Checklist

[ ] (This needs to be done after technical review) I've run the branch on my local, verified that the functionality is ok

How to test this PR locally / Special Instructions

Logs

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

Project coverage is 26.32%. Comparing base (820bf4e) to head (c9c32a2).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #244   +/-   ##
=======================================
  Coverage   26.32%   26.32%
=======================================
  Files          11       11
  Lines        1056     1056
=======================================
  Hits          278      278
  Misses        764      764
  Partials       14       14

/lgtm
/approve


Added a Contributors File on Root Directory

Description

Added a contributors file on the root directory to add new contributors.

Screenshots :

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Changes Reviewed and PR Approved


Crash on CentOS 7 when opening fresh user data dir

Create a fresh user data directory.
Open code-insiders with --user-data-dir pointed to that directory.
Wait a bit.
:bug: VS Code Insiders crashes.

One of the last messages in the verbose output is "MainThreadSecretState#getPassword: Trying migration for:  github.auth".

Can you attach the crash dump following the steps at https://github.com/microsoft/vscode/wiki/Native-Crash-Issues#creating-and-symbolicating-local-crash-reports

Got it
crash.zip


[Fix] Update manager.py and index.html login route

Coverage remained the same at 80.114% when pulling 4d5511c2fb12ea1d25fc491048fc581d51600fce on subhankarb:master into 70adf10607a2a08c3fd1617b7b02a6b902246574 on frictionlessdata:master.


feat: add stable-video-diffusion model

Summary

added stable video diffusion model.
changed deploy model script to enginev2

-- try the model at:
https://replicate.com/christophy/stable-video-diffusion
-- register model tx at:
https://nova.arbiscan.io/tx/0xe620f27ea2aa85dd8b4c7457e6abca63282bb2c64066f436bd59f820bf946166
Test

Sorry this has taken me a while to review, will try to do later today


"no-shadowed-variable": vars shouldn't be shadowed by later declared vars

Bug Report

TSLint version: 5.5.0
TypeScript version: 2.4.2
Running TSLint via: CLI

TypeScript code being linted
export function foo(wam: boolean) {
    if (wam) {
        const now = new Date();
        return now.getTime();
    }

    const now = new Date();
    return now.getTime() + 1000;
}

with tslint.json configuration:
{
    "no-shadowed-variable": true
}

Actual behavior
ERROR: 3:15     no-shadowed-variable  Shadowed name: 'now'

Expected behavior
Even though the inner now variable is inside an inner scope where a variable of the same name resides, I don't believe that there is actually any shadowing.
Indeed the inner block cannot access the outer now variable. If we try (by commenting out line 3) then we get this tsc compile error:
error TS2448: Block-scoped variable 'now' used before its declaration

Code in the style above is pretty common IMHO and is readable, and should not trigger "no-shadowed-variable" (as I have shown there is technically no shadowing)

You're right that it doesn't make much sense in your example.
As soon as you have a closure in your block, that a different story:
export function foo(wam: boolean) {
    if (wam) {
        const now = new Date(); // if you remove this line, the next line will use `now` from the outer scope
        setTimeout(() => console.log(now));
    }

    const now = new Date();
    setTimeout(() => console.log(now));
}

If there is enough demand from the community, we could add an option to ignore variables that are shadowed in their temporal dead zone, i.e. shadowed before the declaration.

If you remove that line, then the code won't pass tslint due to "no-use-before-declare"

I think, this is valid concern. Please add option that take temporal dead zone into account. We have such great keywords like let and const, but they are devalued by this rule.

If you remove that line, then the code won't pass tslint due to "no-use-before-declare"

Note that we don't really take this rule into account when making TSLint design decisions; it's not very useful with let / const syntax, it's slow to compute, and it's not enabled in the built-in configuration presets.


Virtual Arabic Keybpard in Reacct

Is your feature request related to a problem? Please describe.
I would like to know how to implement simple keyboard layouts in react in multiple languages, specifically Arabic.
Describe the solution you'd like
A keyboard like a virtual keyboard this in react

Nevermind, I figured it out, going to leave this here incase anyone wants to know how to do it.