Angular 17 Compatibility

- [ ] bug report -> please search issues before submitting
- [x] feature request

Will this package be upgraded to support Angular 17?  Many thanks.

Sama question bro

I made this simple PR, @AnthonyNahas, can you please review and check If this PR an be merged?

PR: https://github.com/AnthonyNahas/ngx-long-press2/pull/7

Angular 18 has been released
As a temporal solution, one can just add this overrides section to your package.json
  "overrides": {
    "ngx-long-press2": {
      "@angular/common": "~18.0.1",
      "@angular/core": "~18.0.1"
    }
  }

is there any plan to officially support new angular versions?


In the seventh point, Microsoft Cross-Certificates for Windows Vista Kernel Mode Code Signing URL link is pointing to incorrect location

[Enter feedback here]

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

ID: 53aaa60d-e469-f26a-bc3b-8f559947559b
Version Independent ID: 164e8e13-c649-ffb6-6b2f-31ebc95f3b5f
Content: Determining an SPC's Cross-Certificate - Windows drivers
Content Source: windows-driver-docs-pr/install/determining-an-spc-s-cross-certificate.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @tedhudek
Microsoft Alias: tedhudek

Thanks @BhaskarUday for letting us know.
I just pushed an updated link - should be on the live site within 10 minutes.


Add assertsutil test

Issue

none

Overview (Required)

Add AssertUtilTest.

Links

none

Sorry, AssetsUtil was deleted by refactoring 🙇
https://github.com/DroidKaigi/conference-app-2017/pull/318/files#diff-3f041f7f4468c62b9bc5dce22ebbaa06L24
Can you close this PR and add test to ResourceResolver?
ごめんなさい！

OK, I do it later!

LGTM!


Nuget version normalization breaks private release

When publishing xCredSSP v<IP_ADDRESS> to our internal Nuget feed for subsequent consumption, Nuget version normalization trims the last zero in the version. This causes subsequent publishing to Azure Automation to fail as the manifest does not contain a normalized version.
Suggested fix: Rev xCredSSP to v1.3.1
https://docs.microsoft.com/en-us/nuget/concepts/package-versioning#normalized-version-numbers

If this repo is moved to new continuous pipeline (tracked in issue #25) the version vill follow semantic versioning.

Next release will use semantic versioning.


Consider replacing wizard dialog with a generic dialog

Re-implement the DIALOG in wizard() as a generic dialog using ui.Dialog methods

If this was to go into production, would need to consdier rewriting using Dynamic Dialog techniques.  This is so that the datatype and widget exactly match the widget/datatype from calling program


Separating software from courses

To make it easier for people to find courses, we are going to separate out the edtech software - we could make a new table for that later maybe, but for now thinking of dropping these from the table and showing icons and links to the major software websites instead: loqui, ottr, metricminer (maybe others if they have websites).
To do so I (and Kate) am adding the tag edtech-software on all repos that are about edtech-software so we can split these out from the course table.

also added hutch-course as a tag for hutch branded courses

Add icons to brand anvil, itcr, hutch, etc
https://www.opencasestudies.org/OCS_search/

This is done!


build-essential recipe not included in execution when git:source is included in a wrapper cookbook

Cookbook version
4.4.1
Chef-client version
12.9.38 & 12.6.0
Platform Details
CentOS 6.7
Scenario:
Wrapper cookbook that include git::source
Steps to Reproduce:
Create a wrapper cookbook that has more than 1 cookbook dependent on 'build-essential'
Expected Result:
Compilation fails because 'cc' cannot be found.
Actual Result:
https://gist.github.com/Sauraus/d7f97bc674b472aa9abb058bcfc12e45#file-git-source-compilation-error-L77
Take note in the above log, the entire call to 'build-essential' as defined here: https://github.com/chef-cookbooks/git/blob/master/libraries/provider_git_client_source.rb#L10 is missing from the log. It looks like the chef-client decided to not execute the 'build-essential' recipe at that point because most likely it is being included in another recipe further down the chain.

I also have this issue.

Anyone from Chef around to look at this?

Is this still a problem with the current version of the cookbook and current version of chef-client?


[masterbots.ai] feat: update ChatChatbotDetails

https://github.com/user-attachments/assets/ce012940-4bf8-4e5c-b60d-d6f64c267675

Note: BotMessageSquare Error
The BotMessageSquare from https://lucide.dev/icons/bot-message-square its not working. I am using MessageSquare instead in the meantime
Summary by Sourcery
Update the ChatChatbotDetails component with a new UI layout, including a card header, floating avatar, and enhanced description section. Refactor the component for improved readability and maintainability.
New Features:

Introduce a new UI layout for the ChatChatbotDetails component, including a card header, floating avatar, and enhanced description section.

Enhancements:

Refactor the ChatChatbotDetails component to improve readability and maintainability by reorganizing the JSX structure and updating class names for styling consistency.

Summary by CodeRabbit
Summary by CodeRabbit

New Features

Improved user interface with a welcoming message in the card header.
Enhanced responsiveness and visual appeal of the component.
Added descriptive text to assist users in creating new threads.
Styled button for starting a new chat for better visual integration.
Introduced a new loading skeleton for the chatbot details interface.

Documentation

Expanded documentation detailing features like responsive design and theme support.

Refactor

Restructured the return statement for improved layout and styling.
Updated import paths for better modularity and organization.

 Fix Browse Sidebar & Page Navigation


Re-add purgeRequireCache

Right now we're using nodemon for the server, which works fine. But for faster server side HMR we should exclude the server from nodemon and re-add it.
Read more about it here: https://github.com/MoSattler/repay/blob/main/server.ts#L93-L97

Make the change when the new Remix dev server becomes stable?
https://github.com/remix-run/remix/releases/tag/remix%401.12.0

Thanks for the nice template! Hasn't the new dev server landed in 1.14 so we can re-add purgeRequiredCache?

I haven't had any luck with getting the new dev server to work due to ts-node server.ts.
Please share if you managed to get them to play nice together!


adding support to ignore permission errors

This is a simple implementation to ignore permission errors that was mentioned in this issue https://github.com/lingrino/vaku/issues/402
I'm not a Go developer so code might not be great, but happy to update it based on feedback.

👋 Hello @sbarbeau-od thank you for this PR and sorry I am so slow to respond! I've been out for the last few weeks. I saw your PR and I had a bit of time today and ended up adding a version of this in a new PR at https://github.com/lingrino/vaku/pull/1584. Let me know if this covers what you're looking for.


Output redundant "&" in x-www-form-urlencoded

In FormDataSet.AsUrlEncoded(), requireAmpersand is always true except first time. so it is possible output redundant "&" like "?foo=&&bar=".
I've not faced server error by this behavior yet, but if fixed this my comparing work makes easy.
I think the code should like below,
            while (offset < _entries.Count)
            {
                if (_entries[offset].HasName)
                {
                    if (requireAmpersand)
                        tw.Write('&');

                    //_entries[offset].AsUrlEncoded(tw);
                    //requireAmpersand = true;
                    requireAmpersand = _entries[offset].AsUrlEncoded(tw);    // return true if output something
                }

                offset++;
            }

In a way that is the level of control that is offered by HasName. Maybe an additional HasValue would be useful. I'll make the enhancement.

Can you please post a sample form where this happened? The test cases I've come up with are already covered.

Reproduction environment didn't saved, but I think it certainly looked like:
<form method="POST" action="/item/confirm">
  <input type="hidden" name="status" value="1">
  <input type="file" name="photo">
  <input type="hidden" name="status2" value="1">
  <input type="submit" name="send" value="Send">
</from>

html body is
status=1&&status2=1&send=Send

Thanks!


scale images to fit frame (events)

From @jhil on April 26, 2015 22:1
currently only scaling horizontally. should scale vertically if the aspect ratio is too wide for the frame
Copied from original issue: StartupShell/web-2015#31

Undergoing redesign soon. Tabled.


Add rubocop-cask to the list of known custom cops

rubocop-cask is a RuboCop plugin for linting Homebrew-Cask cask definition files, and is now live on Homebrew-Cask.

:+1: Nice!


Setup wizard confusing question

Description

This is not a YES | NO question so the correct option to select is down to guesswork
Version
latest
Environment
No response
Steps to Reproduce
Follow initial steps in this quick start documentation https://resoto.com/docs/getting-started/install-resoto/docker
Logs
No response
Additional Context
No response

Thanks for the report, this was fixed with the following PR:
https://github.com/someengineering/resoto/issues/1379


Funding rate might confuse people

The way how funding rate is depicted at the moment might be confusing.
I know that a positive funding rate means, long pays short but this is not really visible nor described anywhere.
Right now, it looks like that both, longs and shorts will need to pay this rate:

isn't this the case in the above pictures that both long and short need to pay, ie. it's not a negative funding rate? (just double-checking as the rates are quite different in long and short tab)

isn't this the case in the above pictures that both long and short need to pay, ie. it's not a negative funding rate? (just double-checking as the rates are quite different in long and short tab)

mhm... good that it even confuses us 😅 Imho it means: positive means long pay, negative means short pay. So in this case, when shorting, and it says 0.00026, it means that the shorts would receive this amount.

It appears to me that we should fix this in the daemon and return fields like:
{
	"you_pay_hourly": "0.000026%"
}

and
{
	"you_receive_hourly": "0.000026%"
}

Actual names subject to bike-shedding. The main point being: The daemon knows, which role it is in and thus, could map this directly to an unambiguous representation. I would suggest to have a think about what we want to display in the UI and then make the API resemble this as closely as possible.


Porting to Teensy 3.6

Would porting to the Teensy 3.6 be doable? Or would this require a complete reimplementation? I'd be willing to take a swing at this if it would be somewhat doable.
With 16x as much RAM as the Teensy 3.0 (256K), more DMA channels and a lot more CPU power I'd say it would be a big improvement, at least in the number of supported LEDs and strips.

I haven’t been interested in porting Fadecandy because more ram or CPU
doesn’t necessarily help. The number of LEDs per strip has always been
limited mostly by the refresh rate necessary for fadecandy’s color
dithering.
-micah
On Thu, Dec 20, 2018 at 12:48 AM Sanne Bregman<EMAIL_ADDRESS>wrote:

Would porting to the Teensy 3.6 https://www.pjrc.com/store/teensy36.html
be doable? Or would this require a complete reimplementation? I'd be
willing to take a swing at this if it would be somewhat doable.
With 16x as much RAM as the Teensy 3.0 (256K), more DMA channels and a lot
more CPU power I'd say it would be a big improvement, at least in the
number of supported LEDs and strips.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/scanlime/fadecandy/issues/123, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA4YpIQsFo_ixO8Yb_mZjVIGuLjJdj9Gks5u607rgaJpZM4Zbv20
.

Okay, understandable. But wouldn't the extra DMA channels enable more simultaneous strips per FadeCandy? I mean, I have a project planned that would require somewhere between 2500 and 4092 pixels per panel and I was hoping to get a bit less controllers than 7 or 8 FadeCandies it would need with the current hardware.
I'm still trying to get my head around how this actually works, so my apologies if this is a stupid question.

sure, it might make more channels per device possible- that’s just not even
the most compelling reason to do a hardware and firmware revision at this
point, and i’m not sure anything actually crosses the threshold for me
personally where it’s worth adding a firmware update process or additional
hardware models at this point. there are just so many other ways to drive
addressable LEDs that if Fadecandy isn’t right maybe something else is.
-m
On Thu, Dec 20, 2018 at 9:31 AM Sanne Bregman<EMAIL_ADDRESS>wrote:

Okay, understandable. But wouldn't the extra DMA channels enable more
simultaneous strips per FadeCandy? I mean, I have a project planned that
would require somewhere between 2500 and 4092 pixels per panel and I was
hoping to get a bit less controllers than 7 or 8 FadeCandies it would need
with the current hardware.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/scanlime/fadecandy/issues/123#issuecomment-449075793,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA4YpEtYnMoPJtVAUAvhf9Vp5NJfkz1Dks5u68lXgaJpZM4Zbv20
.

Fair enough. Thanks!


Update deeplinks

📲 What
Delete unused deeplink subdomains, update tests, and add support for kickstarter.com without the www..
🤔 Why
Becca and Ali confirmed in slack that the only email redirect domains we need are clicks. and emails..
Note: If anyone tries to test this locally, www.kickstarter.com and kickstarter.com deeplinks might not work today. This is expected; it takes the apple-app-site-association file info about 24 hours to propagate through apple's servers. In the meanwhile, this can be tested by updating the entitlement to applinks:www.kickstarter.com?mode=developer
♿ Accessibility

[x] Works with VoiceOver

✅ Acceptance criteria

[x] staging.kickstarter.com deeplinks work for the beta version of the app
[x] www.kickstarter.com and kickstarter.com deeplinks work for the release version of the app
[x] email deeplinks (emails. and clicks.) work for the release version of the app

⏰ TODO

[x] Double-check that deeplinks from Braze are not affected
[ ] Test non-email deeplinks once the app site association file has time to propagate.

Nice to see all this cleanup. My only suggestion would be to add some documentation to AppDelegateViewModel or another deeplink related location in the code. (Either a comment linking to a Confluence page, or just tossing some notes inline.) I think it will be easy for us to forget what these links do and when they were last audited, so it might help us from ending up in the same position in another year or two.

My plan is to update the guru cards we already have, but I added a couple extra comments, including a link to one of them.


AttributeError: 'list' object has no attribute 'copy'

I run the finetune.py
I get a error AttributeError: 'list' object has no attribute 'copy'
`File "/usr/local/lib/python2.7/dist-packages/spyder/utils/site/sitecustomize.py", line 880, in runfile
execfile(filename, namespace)
File "/usr/local/lib/python2.7/dist-packages/spyder/utils/site/sitecustomize.py", line 94, in execfile
builtins.execfile(filename, *where)
File "/home/lan/tensorflow/finetune_alexnet_with_tensorflow-5d751d62eb4d7149f4e3fd465febf8f07d4cea9d/finetune.py", line 109, in
horizontal_flip = True, shuffle = True)
File "datagenerator.py", line 31, in init
self.shuffle_data()
File "datagenerator.py", line 53, in shuffle_data
images = self.images.copy()
AttributeError: 'list' object has no attribute 'copy'`

This is because your are not using Python 3, as listed in the requirements. Make sure to have everything setup as listed in the requirements section and you wont run into this error.
Also make sure next time you run into a problem, that this question was not already answered. See Issue #9


Update azure-pipelines.yml for Azure Pipelines

Coverage increased (+0.04%) to 74.06% when pulling 1053c59466f3ef77d08aebda9945d458a350f135 on azpipelines into 7e0bf91eecb9a81f4dc489e07015311d9b6c8d63 on dev.

Codecov Report

Merging #994 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #994   +/-   ##
=======================================
  Coverage   78.71%   78.71%
=======================================
  Files          25       25
  Lines        8133     8133
=======================================
  Hits         6402     6402
  Misses       1731     1731

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 7e0bf91...1053c59. Read the comment docs.


Perfect for my 840 G5

Dear Chris,
I just wanted to express my sincere appreciation for your work put into this amazing repo. It has been an invaluable resource for me. With a few small adjustments, I was able to get my 840 G5 working perfectly, even with the Kaby Lake refresh and 4k internal display. It even pairs seamlessly with my USB-C dock.
I was unable to achieve such success with any of the EFIs specific to my model, even when following the Dortania guide to build from scratch. Your repository has been a game-changer and has helped me greatly. While my camera is not yet working, it is a minor inconvenience compared to the incredible progress I've made thanks to your efforts.
Thank you so much for sharing your work with the community. Your contribution is greatly appreciated.
Let me know should you want more details on the hardware or changes I've made for myself. I'm not a professional developer, so I'm not planning to fork the repo.
Sincerely,
Miro

Changes I did for my G5:

Replaced the problematic NVME Samsung SM981. It was booting into installation, but crashing/freezing randomly. I only had Samsung SM961 from a broken laptop lying around, but that one has worked.
Wifi I had to use AirportItlwm kext.
Battery indication didn’t work, so I dropped SSDT-BATT and added ECEnabler kext instead. I also had to clean up plist hacks under ACPI/Patch. I just googled what each does and removed those related to battery.
I fixed trackpad issues by redoing all Voodoo kext and config using Dortania guide.
Upgraded to OpenCore 0.8.8, replaced with latest SSDTs, used SSDT-EC-USBX-LAPTOP and SSDT-PLUG-DRTNIA as per guide. Also replaced all remaining kexts with latest versions. I believe that helped stabilize the whole setup.

Cheers!


Fixes 2823, zip files not loaded by ImageLoaderPygame.

Must be tested on all other platforms. Was developed with python 2.7.9, Windows 7 Home 64-bit.
See #2823 for details.

Works on Linux with pygame. :+1:

Okay, I'm setting up a VM for SDL2. I don't know how much time it takes though, don't hold your breath.


buf: 0.43.2 -> 0.44.0

Motivation for this change
Bump buf to 0.44.0
@raboof
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 nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

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

[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 130091 run on x86_64-linux 1

1 package built:

buf

Result of nixpkgs-review pr 130091 at 852af2e8 run on aarch64-linux 1

1 package built successfully:

buf

1 suggestion:

warning: missing-patch-comment
Consider adding a comment explaining the purpose of this patch on the line preceeding.
Near pkgs/development/tools/buf/default.nix:22:5:
   |
22 |     ./skip_test_requiring_network.patch
   |     ^

warning: missing-patch-comment
Consider adding a comment explaining the purpose of this patch on the line preceeding.
Near pkgs/development/tools/buf/default.nix:22:5:   |
22 |     ./skip_test_requiring_network.patch
   |     ^

Submitted #130102


Measure : Insert/Remove Methods

This solves issue #27.

You need to download Xcode 8 beta 6 and merge changes from master, because I just merged Rob's commit to make the build work for beta 6.

Current coverage is 84.18% (diff: 49.15%)

Merging #37 into master will decrease coverage by 1.74%

@@             master        #37   diff @@
==========================================
  Files            12         12
  Lines           661        708    +47
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            568        596    +28
- Misses           93        112    +19
  Partials          0          0

Powered by Codecov. Last update e59636b...1dd2941


hello guys  after i use this package it work smothly .. but i need help plizz :: how can i read my saved data from API after i hav saved

Hi @youssefApliman , you can use http package to fetch data from api


I have submitted assignment 2

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Adding code
What did you learn from the changes you have made?
using numpy and importing csv
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
None
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
How were these changes tested?
A reference to a related issue in your repository (if applicable)
Checklist

[ ] I can confirm that my changes are working as intended

Assignment marked.


Revert "Fix arg cleanup for objc continuations"

Reverts apple/swift#38556
As per discussion in https://github.com/apple/swift/pull/37695#issuecomment-887693275
Check if reverting this fixes the issue.

@swift-ci Please ASAN test

@swift-ci Please smoke test

We don't think the PR being reverted here is the issue. It's likely a flaky test. Please don't merge this revert PR without further investigation.


[PROPOSAL] Reorganize Branches to Follow OpenSearch CI

What/Why
What are you proposing?
The pattern for most OpenSearch projects in terms of branching is:
main is the next major release (3.0 right now)
2.x is the next minor release (2.10 at the moment)
as releases are created, we cut a branch for each. I'm working on building 2.6, 2.7, 2.8 now. I will also branch from main to create 2.5. From there, most PRs should be merged to main and then backported to 2.x; some may need to be backported to other branches as well.
I see that some of the mechanisms for cutting a new release will need to change (release.yml, docker.yml). We also want to remove direct dependencies on libraries in the repo.
@gsingers what challenges do you see here from the way the build works?

[ ] create 2.6 branch
[ ] create 2.6 release
[ ] create 2.7 branch
[ ] create 2.7 release
[ ] create 2.8 branch
[ ] create 2.8 release
[ ] create 2.9 branch
[ ] create 2.9 release
[ ] update main to 3.0 and sync with 2.9 branch
[ ] create 2.x branch for 2.10 release

This should result in a self install plugin for each version of OpenSearch.

I'm closing this in favor of individual issues for each release.


Parameter list missing in reconfigure/dynamic if any parameter was declared without a default value under ROS2

System: Ubuntu 22.04
Version: ROS 2 Iron Irwini - Patch Release 4
Following the parameter tutorial on the ROS2 docs, I can see the following result in rqt/ rqt_reconfigure

However, if I add a parameter without default value using the type-specifying version of the declare_parameter() API, the entire parameter list for the node will disappear without any error message:
this->declare_parameter("an_int_param", 0); // The original demo
this->declare_parameter("an_int_param_without_val", rclcpp::PARAMETER_INTEGER);  // THIS CAUSE PROBLEMS

This problem disappears if that specific parameter is supplied with the command line:
ros2 run cpp_parameter_event_handler parameter_event_handler --ros-args -p an_int_param_without_val:=22

I should add that all other ros2 param and ros2 service command line tools are fine as far as I've tested.
This behavior is not mentioned anywhere in the documentation and I also couldn't find any similar problems on the internet. It took me a few hours of trial-and-error to figure-out the pattern.

This is related to https://github.com/ros2/rclcpp/issues/2512


PLAT-1861 Upgrade to pyfilesystem2

The old version of the fs package we've been using is throwing out enough spurious errors at test shutdown that it's interfering with pytest's ability to output legitimate warnings.  This PR does the following:

Switches us to the latest release of the fs package
Uses the new fs-s3fs package to add the S3 support that the default fs package no longer includes
Cleans up the requirements handling (updating the old files as configured triggered a duplicate package problem in tox)

There are a few API changes from the fs upgrade that impact edx-platform, but the scope seems manageable so far; I already have all the xmodule tests passing locally.

Codecov Report

Merging #12 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #12   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           2      1    -1
  Lines          95     60   -35
  Branches       12     10    -2
=====================================
- Hits           95     60   -35

Impacted Files
Coverage Δ

djpyfs/djpyfs.py
100% <100%> (ø)
:arrow_up:

djpyfs/models.py

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 59a472a...5296382. Read the comment docs.


add view tags for speeding up scanning

hey I'm looking at your protocol, from your docs "The final consideration has to do with scanning. Because every single Announcement needs to be scanned, it can take a long time to find your finds."
have you considered something like view tags (implemented in monero) for speeding up this process? it should work w your protocol as far as I can tell. you'd only need to calculate the ECDH key for each Announcement instead of having to decrypt the secret, calculate the shared private key, and derive a_stealth each time. you'd have to add 1 byte to the Announcement event that is the first byte of the ECDH key, so for each announcement, you'd only need to derive the ECDH key and 255/256 times skip the rest of the steps.
here's the original idea: https://github.com/monero-project/research-lab/issues/73

Ah this is really clever, thanks! Haven't seen that before.
Adding the 1 byte of the ECDH key to the Announcement would reduce security by 1 byte though, right? In the linked issue they suggest hashing the ECDH key and including the first n bytes (where n was up for discussion), which is interesting:

I think hashing is a lot faster than elliptic curve multiplication, so that seems like a worthwhile tradeoff to keep that extra 1 byte of security.
Then if you're hashing it, you could safely emit between more than just 1 byte of info and improve the speedup from only computing 1/256 addresses to something even smaller. We have to emit a full 32 byte param in the event anyway, so we get the extra bytes here roughly for free (I don't think LOG costs differentiate zero vs. non-zero bytes).

The main downside is that we need to deploy a new contract which would be a bit of a pain since indexing/scanning now needs to track two contracts, but definitely like the idea.

@mds1 yep, hashing it and emitting more than 1 byte seems like a good idea, like you said it'll get packed to 32 bytes anyways. would reduce potentially a lot of scanning :)

Going to close this since view tags will not be implemented in this version of Umbra, but will be implemented once the stealth address EIP is finalized and we upgrade to support it:

EIP itself can be found here
Most recent version, not yet upstreamed, can be found in the open PR in this repo

Thanks again for the suggestion @noot!


Update EO to 0.35.2

PR-Codex overview
This PR updates the versions of various dependencies and adds home and package URLs. It also adds new objects and tests.
Detailed summary

Updated eo.version to 0.35.2 in pom.xml
Added home and package URLs for various objects
Updated rt jvm and version in various objects
Added new objects and tests

The following files were skipped due to too many changes: tests/org/eolang/goto-tests.eo, tests/org/eolang/seq-tests.eo, tests/org/eolang/ram-tests.eo, objects/org/eolang/nan.eo, tests/org/eolang/try-tests.eo, objects/org/eolang/int.eo, tests/org/eolang/switch-tests.eo, objects/org/eolang/tuple.eo, objects/org/eolang/float.eo, tests/org/eolang/heap-tests.eo, tests/org/eolang/memory-tests.eo, objects/org/eolang/bytes.eo, tests/org/eolang/cage-tests.eo, tests/org/eolang/rust-tests.eo, tests/org/eolang/tuple-tests.eo, objects/org/eolang/negative-infinity.eo, objects/org/eolang/positive-infinity.eo, tests/org/eolang/nan-tests.eo, tests/org/eolang/int-tests.eo, tests/org/eolang/bool-tests.eo, tests/org/eolang/string-tests.eo, tests/org/eolang/negative-infinity-tests.eo, tests/org/eolang/positive-infinity-tests.eo, tests/org/eolang/runtime-tests.eo, tests/org/eolang/bytes-tests.eo, tests/org/eolang/float-tests.eo

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@yegor256 please check

@maxonfjvipon thanks!


Remove dependency-review pipeline

Summary
This is already done by minder's integration with trusty, no need to do
it twice.
Change Type
Mark the type of change your PR introduces:

[x] Bug fix (resolves an issue without affecting existing features)
[ ] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[x] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 49.418% (+0.01%) from 49.407%
when pulling 0b0e57a3783659fa894a30b7d4591678300e31bd on rm-dep
into 4a868e3ea1e3ade0b87b6e8142e66a26db780361 on main.


Transparent mac-titlebar-tabs flash / tear when opening new tabs

I have the following config.
background-opacity = 0.8
macos-titlebar-tabs = true

Now when i try to open some new tabs, there is a flash / tearing effect.
https://github.com/mitchellh/ghostty/assets/1562523/04b6198f-f65e-49d2-801a-ff0fe073b712
OS: macOS 14.2.1 (23C71)
Ghostty: 1e6cffac

I think this issue is also present with splits, I still see noticeable flickering with splits. Disabling transparency is my current workaround.
https://github.com/user-attachments/assets/3f6d124e-2762-4699-a982-2a2c413365ec
Here's some info / my config for details:
OS: macOS 15.2 (24C101)
Ghostty: 4b4d4062

config
font-size = 14
font-thicken = true

theme = "tokyonight-storm"

background-opacity = 0.985
background-blur-radius = 20

window-height = 35
window-width = 115
window-padding-x = 20
window-padding-y = 15
window-step-resize = true

bold-is-bright = true

macos-titlebar-style = "tabs"

@JesseFarebro did you mean disabling transparency by setting background-opacity = 1? flickering still happens for me after setting that. (most notably new tabs)


Better label merging

Sequences of or() parsers that all fail have their combined errors reported using the label of the first alternative in the list. Similarly, sequences of then(xyz.or_not()) parsers have their combined errors reported using the last in the sequence.
I wanted these cases to be reported using none of their respective labels, so that a higher level label could be applied to their collective failure. However my first attempt to fix this just in error::Simple::merge() using something like Option::xor failed, because when processing three .or() branches in a row, the first two would have their label collapsed to None and then the third would replace the None with its own.
To address this issue I added a new type, SimpleLabel, which captures the difference between merging with an error with no label, or merging with an error that's already had multiple other labels merged into it.
While debugging this PR I found another issue with .labelled("...") branches seemingly not being applied correctly, it turns out that an error can sneak through the Label<_, _> parser as an "alternate error", so I've added a second commit to fix this.

Thanks, this seems like a broadly desirable change. Just one comment about the current implementation.
It's worth noting that when zero-copy is merged, I think I'll probably be moving things like labels into a series of non-default extension traits in order to keep the core of the crate as simple as possible.

Thanks!


Prebuilt 34

Hi there,
I'd like to contribute the pre built bindings for the new 3.4 version of GDAL.

I'd like to merge this tomorrow unless anyone objects.

bors r+

i guess we have to adapt these tests first

Is anyone opposed to dropping the trybuild thing? It very fragile, especially when trying to support multiple compiler versions, because the error messages sometimes change.

there is already a discussion here: https://github.com/georust/gdal/pull/234
i'm not against dropping it if we can't make it work

now we have both options #237

we should first try to adapt the test. if it is not maintainable,, e.g. if it fails again ext week, then we can drop it.

bors r+


DT-706 fixing SystemException: Failed to generate a unique parameter name

Due to the random number generate call randomNumberGenerator.nextInt(100) we were running into errors when listing all participants in review if the review contains a large amount of participants.
The easiest fix is to just tack integer on the end of the param name that is the size of the map.
String paramName = paramBaseName + params.size();

Most of the noise is the update of the SQL Golden Files.


fixed typo in readme

Found a typo in our open source repository.

@Marre69 wow thanks a lot for contribute, I appreciate that


need a easy way to fetch current component and name serverside.

current the only way I can fetch the current component and its name from the current route is as following.
match({routes, location: request.url.path }, (error, redirectLocation, renderProps) => {
    var componentName = renderProps.components[1].displayName.replace(/Connect\(|\)/g, '');
    var componentObj = renderProps.components[1].WrappedComponent;
});

is there a simpler way I can do this? or can one be made?

my main reason to do this is to prefetch data for rendering serverside, its works fairly well as above but looks quite hacky.

Thanks for your question!
We want to make sure that the GitHub issue tracker remains the best place to track bug reports and feature requests that affect the development of React Router.
Questions like yours deserve a purpose-built Q&A forum. Would you like to post this question to Stack Overflow with the tag #react-router? https://stackoverflow.com/questions/ask?tags=react-router.
We also have an active and helpful React Router community on Reactiflux, which is a great place to get fast help with React Router and with the rest of the React ecosystem. You can join at https://discord.gg/0ZcbPKXt5bYaNQ46.

@taion similarly sent me. I wrote a question on stackowerflow and to React Router community on Reactiflux, but the response and who didn't give, didn't even try to help (and by the way @taion on the react-router channel is and is silent, it is seen the politician such to send where far away).


Added crossy road game : Issue no #867

Solved :
Issue no #867

Hey @iamrahulmahato
Please grant level 2 for this PR because this issue required lot of Java Script code Its not easy.

i am closing it as it is duplicate


'Connection aborted.', RemoteDisconnected('Remote end closed connection without response'

Hi,
I was trying to transfer some files/folders from "nird" to p33. Now, I am getting the following error:
(base) [mohammadzr@login1-nird-tos scz-norcloz1]$ tacl p33 --upload-sync job-20220522-212725-381-scznorcloz2
uploading directory job-20220522-212725-381-scznorcloz2
fetching information about directory: job-20220522-212725-381-scznorcloz2
('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',))
You probably do not have access to the TSD API from this network - contact TSD for help: https://www.uio.no/english/services/it/research/sensitive-data/contact/index.html
(base) [mohammadzr@login1-nird-tos scz-norcloz1]$ tacl p33 --upload-sync job-20220522-212725-381-scznorcloz2
uploading directory job-20220522-212725-381-scznorcloz2
fetching information about directory: job-20220522-212725-381-scznorcloz2
fetching information about directory: job-20220522-212725-381-scznorcloz2/logfile
('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',))
You probably do not have access to the TSD API from this network - contact TSD for help: https://www.uio.no/english/services/it/research/sensitive-data/contact/index.html
(base) [mohammadzr@login1-nird-tos scz-norcloz1]$

Previously, I used "tacl" to transfer files/folders from "nird" to p33 but never faced such issues. Any help?
Best, Zillur

The issue is resolved. It seems a temporary problem.


Added missing source files.

[Short description explaining the high-level reason for the pull request]
Add the missing implementation files to the repository.
Additions

Removals

Changes

Testing

Screenshots
Notes
Addresses issue #16
Todos

Checklist

[ ] PR has an informative and human-readable title
[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows project standards (link if applicable)
[ ] Passes all existing automated tests
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future todos are captured in comments
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
[ ] Reviewers requested with the Reviewers tool :arrow_right:

Testing checklist (automated report can be put here)

Target Environment support

[ ] Linux

closes #16


Picovoice Console Issue: Porcupine Custom Wake Word Not Downloading File

I tried using Porcupine on the console. It detected my wake word and I trained the model. But when I clicked download for MacOS on Chrome browser, it did not trigger a download. I attempted twice but no use.

@denizulcay - we're not seeing issues downloading files on our end and our system hasn't alerted us to any failures related to this functionality. Is it possible you were at your Porcupine model download limit? Was something on your browser blocking downloads?

closed due to inactivity


Add end-to-end tests of monitor aggregation

[ ] Monitor aggregation level = none
[ ] Monitor aggergation level = low
[ ] Monitor aggregation level = medium

[ ] Per-direction ratelimiting
[ ] Per-connection ratelimiting

We already have some end-to-end tests for cilium monitor with monitor-aggregation to medium, but we don't check the rate limiting.
Any of the subitems in this issue can be tackled as a good-first-issue.


Docs/deep dive improvements

Fixing issue found while going through the deep dive docs.
I went through the deep dive on an intel macOS, and it worked fine. I didn't add macOS-specific instructions since I do not have an arm machine, and I wasn't sure if it would work there.

On fire!

BTW, let me squash these changes into a single commit before merging it


ARROW-4699: [C++] remove json chunker's requirement of null terminated buffers

Re-enable json chunker test. This was failing valgrind but that is not currently happening locally

@bkietz Tests are now failing in Travis.

I don't know what caused the test failure. I have rebased and the remaining Travis failures seem unrelated:
R, GCC 4.8

Restarted them.


Issue

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:

Steps to Reproduce:

Yes


Flutter stable3.0 , Get Cli 报一堆错，什么时候适配Flutter Stable 3.0 ？

same question

175

it's windows ? !!!!!!!!


add fix for notification role, also fix typing for install task

Fixes #7

@davidkarlsen Is there a good reason not to create the role within the module?

@davidkarlsen Is there a good reason not to create the role within the module?

that's maybe a tad busy. there are probably things to be done outside of the module anyways, like key-grants etc.

I'ma get this merge in, we can add IAM stuff later if need be

Yeah, this is definitely the minimal change to fix the bug.


Automated Package Upgrade

:tada: This PR is included in version 21.0.14 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[flash_ctrl] flash_macro_err leads to fatal alert although it can be triggered by SW misuse.

Consider changing flash_macro_err assignment to non-fatal alert.
Reference lines:
https://github.com/lowRISC/opentitan/blob/7a7139c8af345f423ac27a0186febdda027f7127/hw/ip/flash_ctrl/data/flash_ctrl.hjson#L1883
https://github.com/lowRISC/opentitan/blob/7a7139c8af345f423ac27a0186febdda027f7127/hw/ip/flash_ctrl/data/flash_ctrl.hjson#L1931

@eshapira


Split picard markdup in 2

Breaks Picard Markdup and Samtools view into distinct steps, within the same batch job.
Despite setting set -x and pipefail, the error messages being created at this stage are not useful - Picard's random termination is read as a samtools reading error, or a missing EOF. Decoupling these two steps is marginally 'less efficient', but we're getting desperate. A useful error message here may be helpful in diagnosing.
Picard also complains about having insufficient memory, so it resorts to an unbuffered mode prior to many of the crashes. A higher memory limit could mitigate this, but we don't want to just keep doubling it. I've added a config option workflow. exceptional_markdup_mem_gb  to boost memory provision, hopefully able to clean up these instances where there are only a few samples failing but they're failing consistently. The default remains the same as it is now.
Please review critically, I've no idea if this is a good idea or not.
ref: https://batch.hail.populationgenomics.org.au/batches/424719?q=failed

Nothing in practice at present, but a new category might be better instead of lumping everything directly under 'workflow'.
I should have mentioned this in the other PR too, but can we add this new param to the defaults.toml file with a comment on what it's for.

can we add this new param to the defaults.toml file

I've added a section to the seqr_loader.toml default for resource_overrides. The changes from this and #381 are both moved to there


cicd: tag version only from release

The pipeline runs twice for releases, that had undesirable side-effects.

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

Project coverage is 12.14%. Comparing base (0b27b80) to head (dd81ca0).
Report is 24 commits behind head on develop.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #975      +/-   ##
===========================================
- Coverage    12.15%   12.14%   -0.01%
===========================================
  Files          279      278       -1
  Lines         9866     9914      +48
  Branches      1042     1047       +5
===========================================
+ Hits          1199     1204       +5
- Misses        8642     8685      +43
  Partials        25       25

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


issue #637: Prompt user if using incompatible chars in repository ID

Signed-off-by: James Leigh<EMAIL_ADDRESS>This PR addresses GitHub issue: #637 .

Travis build failed but it looks like it was a problem with the cloud instance, not an actual test failure. If you push a change it should restart the build automatically, and (hopefully) succeed.


There is no event before each file send?

All I find is opts.preprocess but no flow.Events

You can use the event of progress to check for Events of Chunk. That is called whenever a new Chunk is started or a new chunk is finished uploading.

And if you want to check for the file, then you can check the uploadStart event.

@AidasK
It's an old issue and can be resolved using the functions. I would suggest closing this...


🐛 Bug Report: "TypeError: graphql.command is not a function"

👟 Reproduction steps
After installation on MacOS I type the following
appwrite -v

and get this error report:
/opt/homebrew/Cellar/appwrite/HEAD-9007d34/libexec/lib/node_modules/appwrite-cli/lib/commands/graphql.js:67
    .command(`query`)
     ^

TypeError: graphql.command is not a function
    at Object.<anonymous> (/opt/homebrew/Cellar/appwrite/HEAD-9007d34/libexec/lib/node_modules/appwrite-cli/lib/commands/graphql.js:67:6)
    at Module._compile (node:internal/modules/cjs/loader:1246:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1300:10)
    at Module.load (node:internal/modules/cjs/loader:1103:32)
    at Module._load (node:internal/modules/cjs/loader:942:12)
    at Module.require (node:internal/modules/cjs/loader:1127:19)
    at require (node:internal/modules/helpers:112:18)
    at Object.<anonymous> (/opt/homebrew/Cellar/appwrite/HEAD-9007d34/libexec/lib/node_modules/appwrite-cli/index.js:14:21)
    at Module._compile (node:internal/modules/cjs/loader:1246:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1300:10)

Node.js v19.5.0

I tried installing it using all the methods provided: NPM, Homebrew and terminal. Outcome is the same.
👍 Expected behavior
It should show the version number.
👎 Actual Behavior
/opt/homebrew/Cellar/appwrite/HEAD-9007d34/libexec/lib/node_modules/appwrite-cli/lib/commands/graphql.js:67
    .command(`query`)
     ^

TypeError: graphql.command is not a function
    at Object.<anonymous> (/opt/homebrew/Cellar/appwrite/HEAD-9007d34/libexec/lib/node_modules/appwrite-cli/lib/commands/graphql.js:67:6)
    at Module._compile (node:internal/modules/cjs/loader:1246:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1300:10)
    at Module.load (node:internal/modules/cjs/loader:1103:32)
    at Module._load (node:internal/modules/cjs/loader:942:12)
    at Module.require (node:internal/modules/cjs/loader:1127:19)
    at require (node:internal/modules/helpers:112:18)
    at Object.<anonymous> (/opt/homebrew/Cellar/appwrite/HEAD-9007d34/libexec/lib/node_modules/appwrite-cli/index.js:14:21)
    at Module._compile (node:internal/modules/cjs/loader:1246:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1300:10)

Node.js v19.5.0

🎲 Appwrite version
Version 1.2.x
💻 Operating system
MacOS
🧱 Your Environment
No response
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

@juzo thanks for creating this issue! 🙏🏼 We'll look into this right away.
As a workaround, I would suggest uninstalling it from homebrew and installing it via NPM.

I tried installing it using all the methods provided: NPM, Homebrew and terminal. Outcome is the same.

Make sure the homebrew version is not being used when you're testing with other installation methods.

Thanks for the reply. I uninstalled everything and tried installing it again but only using the terminal version (curl). This time it worked.
appwrite -v
1.1.1


chore: migrate to microbundle

Continuing to get issues with long build times. Will put this aside for the future.


Guide for type conversions

Closes #607
A guide for performing type conversions in different programming languages.

Thank you for your contribution! We'll get it assigned and reviewed and let you know if we have any questions. FYI, we've given reviewers a couple of weeks to review submissions but we'll try to get to it sooner!

Hi @Mackenzie-OO7! Can you fix the conflicting files? Once you do we can get this merged and talk award information! Thank you!

Hi @Mackenzie-OO7! Can you fix the conflicting files? Once you do we can get this merged and talk award information! Thank you!

Fixed it!

Nicely done! This is a great addition to the how to guides!

Thank you😁😁


Add pull request trigger to yaml

Please add pull request triggers to yaml (currently not supported).

I believe this is now supported. See docs.

I agree, at least per the docs this is now supported.


after server upgrade no hyperion

I am running hyperion on a raspberry (raspbian 2014-09-09) . After i ran yesterday rpi-update, hyperion does not start anymore. i got a error message. No such...

@ghost
can be closed?

Closed due to age. Please open a new one, if problems still exists.
Thank you


Upgrading from 1.0.1 to 1.0.2 results in requestContext.get('key') returning undefined

Hi,
After upgrading asynchronous-local-storage from 1.0.1 to 1.0.2 any call to requestContext.get('key') to return undefinded.
I was able to reproduce the issue with the following snippet:
import fastify from 'fastify';
import { fastifyRequestContextPlugin, requestContext } from 'fastify-request-context';

const ALS_KEY = 'my-key';

const server = fastify();

//    server.register(fastifyRequestContextPlugin);

server.addHook('onRequest', (req, reply, done) => {
    requestContext.set(ALS_KEY, { value: 42, });
    done();
});

server.get('/', async () => {
    const stored = requestContext.get(ALS_KEY);
    console.log(`stored = ${JSON.stringify(stored, null, 2)}`);
    return { status: 'ok?', got: stored };
});

server.listen(3000, (err, address) => {
    if (err) {
        console.error(err);
        process.exit(1);
    }
    console.log(`Server listening at ${address}`);
});

Note that this might be due to a wrong usage of the library that manifest itself after the upgrade.
I noticed that if I uncomment server.register(fastifyRequestContextPlugin); that the ALS then works as expected.
I have an app that doesn't register the plugin fastifyRequestContextPlugin and works fine when using requestContext in 1.0.1 but fails and always gets undefined once we upgrade to 1.0.2.
Do we need to register the plugin fastifyRequestContextPlugin ?
Is there a regression in 1.0.2 that we're hitting?

@potyl Can't put my finger immediately on why that would be working previously, but I don't understand your use-case either. Why are you trying to use a part of plugin without using plugin itself? Hooks generated by fastifyRequestContextPlugin are responsible for ensuring that correct context is preserved within correct request. Most likely you are hitting https://github.com/fastify/fastify-request-context/pull/12 which fastify-request-context handles for you. If you want to consume requestContext directly, you would need to do the same context syncing that plugin does for you (see the PR linked).

@kibertoad the use-case is a simplification of what's happening on my application.
Thanks for pointing out the issue that we're hitting. I see that we're not using the plugin properly.
In my case I have a library that's agnostic to any web framework, the library is being used inside a fastify server but from the point of view of the library it doesn't require any dependency to fastify. The library does expose an "initialization" function that is expected to be used by a fastify app so that it can pass a context. That function uses a ALS to work.
Then later on during the development ALS was needed inside the actual fastify app and the plugin was used without registering it. Somehow it worked fine with 1.0.1 and only during the upgrade did we notice a strange behavior.
I will register the plugin for the bits in the fastify app that rely on requestContext.

Actually, ignore my last comment. I do see in the code that we are registering the plugin fastifyRequestContextPlugin.
Although the upgrade to 1.0.2 does break our fastify app as all calls to requestContext.get() now return undefined.

I see that if I upgrade fastify-request-context from 2.1.1 to 2.1.3 then asynchronous-local-storage will be upgraded too (from 1.0.1 to 1.0.2) and requestContext.get() is now working as expected!


docs(v2): fix misc styling

@lex111 we should remember to follow the commit conventions and add the necessary tags.

Sorry about that! :((

No problem, not a huge deal at all 😄


CMake 3.18+ Device Link Xcompiler option fix for Warnings as Errors

Fix cmake related issue for passing multiple options to xcompiler at device linking.
In the process of opening a cmake bug about the unexpected behaviour.

CMake 3.16.1, VS 2015 is giving me this on configure (multiple times)
CMake Warning (dev) at cmake/common.cmake:287:
  Syntax Warning in cmake code at column 93

  Argument not separated from preceding token by whitespace.
Call Stack (most recent call first):
  src/CMakeLists.txt:26 (include)
This warning is for project developers.  Use -Wno-dev to suppress it.

Does not build under visual studio 2015 with Werror on.
e.g. main lib files LayerDescription.cpp,ModelData.cpp, AgentData.cpp, AgentFunctionData.cpp, AgentDescription.cpp, AgentFunctionDescription.cpp, curve_rtc.cpp have these errors (all the same error, the include to blame isn't immediately obvious):
1>C:\Program Files (x86)\Windows Kits\8.1\Include\um\DbgHelp.h(1544): error C2220: warning treated as error - no 'object' file generated (compiling source file C:\Users\Robadob\Desktop\fgpu2\src\flamegpu\runtime\cuRVE\curve_rtc.cpp)
1>C:\Program Files (x86)\Windows Kits\8.1\Include\um\DbgHelp.h(1544): warning C4091: 'typedef ': ignored on left of '' when no variable is declared (compiling source file C:\Users\Robadob\Desktop\fgpu2\src\flamegpu\runtime\cuRVE\curve_rtc.cpp)
1>C:\Program Files (x86)\Windows Kits\8.1\Include\um\DbgHelp.h(3190): warning C4091: 'typedef ': ignored on left of '' when no variable is declared (compiling source file C:\Users\Robadob\Desktop\fgpu2\src\flamegpu\runtime\cuRVE\curve_rtc.cpp)
1

e.g. gtest has these reorder errors
4>C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\include\xlocbuf(324): error : the initialization of member "std::wstring_convert<_Codecvt, _Elem, _Walloc, _Balloc>::_Has_state [with _Codecvt=wchar_codecvt, _Elem=__wchar_t, _Walloc=std::allocator<__wchar_t>, _Balloc=std::allocator<char>]" will be done before that of member "std::wstring_convert<_Codecvt, _Elem, _Walloc, _Balloc>::_Has_werr [with _Codecvt=wchar_codecvt, _Elem=__wchar_t, _Walloc=std::allocator<__wchar_t>, _Balloc=std::allocator<char>]"
4>            detected during instantiation of "std::wstring_convert<_Codecvt, _Elem, _Walloc, _Balloc>::wstring_convert() [with _Codecvt=wchar_codecvt, _Elem=__wchar_t, _Walloc=std::allocator<__wchar_t>, _Balloc=std::allocator<char>]"
4>  C:\Users\Robadob\Desktop\fgpu2\build\tests\googletest-src\googletest\include\gtest/internal/gtest-port.h(2060): here
4>

I have neither Windows kit 8.1, nor VS2015 installed so can't reproduce these (would rather not have to wait several hours to install both and reinstall CUDA etc.)
Given the C4091 is from an include named DbgHelp I assume this is debug mode only, which I probably didn't test, really not clear what header / change must be causing that.
I assume this can't be specific to this branch either - as those are certainly not device link related.
The wreorder issue should dissapear thanks to one of the other PRs, which removes  Wreorder from MSVC.

Yeah it's not the end of the world, being vs2015 (it does work in less strict mode). I'd like to see how it performs after the other branches are merged though. So i'll wait on this one.

@Robadob to test this locally and if happy it can be merged.


The feature list to deserialize is specified at compile time.

Though features can be defined any time in an application, only those defined at compile time are deserialized properly.
I had a hard time understanding what was going on, and I think that this is linked to the fact that some features are handled in static initializers and in static methods
Here is roughly the code flow for deserialization of a Model:

a Model instance is created. At this line (https://github.com/fiji/TrackMate3/blob/model-edit-actions/src/main/java/org/mastodon/revised/model/mamut/Model.java#L55) the ModelFeatures class is referenced.

In the static initializer of this class, an ObjFeature is created for vertex labels (https://github.com/fiji/TrackMate3/blob/model-edit-actions/src/main/java/org/mastodon/revised/model/mamut/ModelFeatures.java#L11).

Doing so, this feature is registered in a static field of FeatureRegistry.

The feature serializer is registered in a static field of FeatureSerializers (https://github.com/fiji/TrackMate3/blob/model-edit-actions/src/main/java/org/mastodon/revised/model/mamut/ModelFeatures.java#L15)

Now the model is instantiated and empty.

Calling `'loadRaw' will deserialize the graph (vertices and edges) and then call 'RawFeatureIO.readFeatureMaps( fileIdMap.vertices(), vertexFeatures, ois );' to deserialize features.

This method relies on the FeatureRegistry to get the Feature instance corresponding to the String key stored in the raw file. If the feature with said key is not in the registry - i.e was not declared before the call to loadRaw - the registry will return null.

This happens for all features created after the model was instantiated or/and loaded.

Example in two classes:
Class that saves a model with an added feature:
package org.mastodon.revised.mamut;

import java.io.File;
import java.io.IOException;
import java.lang.reflect.InvocationTargetException;

import org.mastodon.features.DoubleFeature;
import org.mastodon.revised.model.mamut.Model;
import org.mastodon.revised.model.mamut.Spot;

import mpicbg.spim.data.SpimDataException;

public class TestSaveFeature
{

	public static final String KEY = "TEST_FEATURE";

	public static final File TEST_FILE = new File( "samples/test_features.raw" );

	public static void main( final String[] args ) throws IOException, SpimDataException, InvocationTargetException, InterruptedException
	{
		final String bdvFile = "samples/datasethdf5.xml";
		final String modelFile = "samples/model_revised.raw";
		final MamutProject project = new MamutProject( new File( "." ), new File( bdvFile ), new File( modelFile ) );
		/*
		 * Load Model
		 */
		final Model model = new Model();
		if ( project.getRawModelFile() != null )
			model.loadRaw( project.getRawModelFile() );

		System.out.println( String.format( "Loaded a graph with %d vertices and %d edges.",
				model.getGraph().vertices().size(), model.getGraph().edges().size() ) );

		final DoubleFeature< Spot > test = new DoubleFeature<>( KEY, 10. );
		for ( final Spot s : model.getGraph().vertices() )
			s.feature( test ).set( 3.14 );

		model.saveRaw( TEST_FILE );
		System.out.println( "Saved to " + TEST_FILE );
	}

}

Class that reloads this model:
package org.mastodon.revised.mamut;

import java.io.IOException;
import java.lang.reflect.InvocationTargetException;

import org.mastodon.features.Feature;
import org.mastodon.features.FeatureRegistry;
import org.mastodon.revised.model.mamut.Model;
import org.mastodon.revised.model.mamut.Spot;

import mpicbg.spim.data.SpimDataException;

public class TestLoadFeatures
{
	public static void main( final String[] args ) throws IOException, SpimDataException, InvocationTargetException, InterruptedException
	{
		/*
		 * Load Model
		 */
		final Model model = new Model();
		model.loadRaw( TestSaveFeature.TEST_FILE );

		System.out.println( String.format( "Loaded a graph with %d vertices and %d edges.",
				model.getGraph().vertices().size(), model.getGraph().edges().size() ) );

		final Feature feature = FeatureRegistry.getFeature( TestSaveFeature.KEY );
		System.out.println( "Feature with key " + TestSaveFeature.KEY + " is " + feature );

		for ( final Spot s : model.getGraph().vertices() )
			System.out.println( s + " feature " + s.feature( feature ).get() );

	}

}

Results of the latest:
UndoRecorder.graphRebuilt()
TODO!!!!
Loaded a graph with 3087 vertices and 2981 edges.
Feature with key TEST_FEATURE is null
Exception in thread "main" java.lang.NullPointerException
	at org.mastodon.graph.ref.AbstractVertexWithFeatures.feature(AbstractVertexWithFeatures.java:50)
	at org.mastodon.revised.mamut.TestLoadFeatures.main(TestLoadFeatures.java:32)

A solution would be maybe to change the way features are handled via static methods, and have a Model carry with it declarations of the features it has and their type.
These declarations could be saved and deserialized before the actual features are deserialized.
The application could modify these declarations at runtime, adding or removing features at will.

This is fixed by #36 (among others).


feat: android should intercept request

Initial attempts at implement the shouldInterceptRequest method of Android Webview Client.
Results:

Current implementation only supports returning a string from React Native to Android, where it will be converted to a InputStream in the form of a byte array
Areas of improvement:

Refactor the Java Android method that react native calls to include status code, mime type, reason, headers, and other relevant WebResourceResponse parameters

Refactor the native event being passed to the onShouldInterceptRequest to include values from WebResourceRequest

Concerns

Should there be a size limit on what React Native can pass through JSI? Would the 1 second timeout be enough?

What are the limitations of JSI? What can be passed through it? Is it only primitive data types?

Is there a way to implement other forms of InputStream? Below is a list of InputStream subclasses

[ ] AssetInputStream

[ ] BackupDataInputStream

[ ] ByteArrayInputStream

[ ] FileInputStream

[ ] ObjectInputStream

[ ] PipedInputStream

[ ] SequenceInputStream

[ ] StringBufferInputStream

Gave a quick read to the PR:

it seems that there is a lot of thing that are copy/pasted from shouldOverrideUrlLoading, could we imagine sharing most of the code?
1000 ms seems like forever to block the main thread, did you encounter cases that were that slow during your testing ?
You are talking about JSI, but (at least for now) this module is also compatible with the old arch so we cannot go that way I think.

I'm not an expert regarding all the points you made within your concerns (that are very much valid)

Gave a quick read to the PR:

it seems that there is a lot of thing that are copy/pasted from shouldOverrideUrlLoading, could we imagine sharing most of the code?
1000 ms seems like forever to block the main thread, did you encounter cases that were that slow during your testing ?
You are talking about JSI, but (at least for now) this module is also compatible with the old arch so we cannot go that way I think.

I'm not an expert regarding all the points you made within your concerns (that are very much valid)

Hey Titozzz, thanks for your reply. I'll look to refactor the code for reusability with shouldOverrideUrlLoading and will do some testing on the timeouts
Do you know who I should ask for more information on JSI, or Native to React native communication? I have taken a look at this page https://reactnative.dev/docs/communication-ios, but it doesn't go in depth on the limitations

The part you linked is using the old arch. So it is mainly outdated

Several observations during testing:

shouldInterceptRequest is never called on the main thread (checked using Looper.myLooper() == Looper.getMainLooper())
This would mean we will not be able to utilize createWebViewEvent, as it populates the WebviewEvent object with the following:

event.putBoolean("loading", !mLastLoadFailed && webView.getProgress() != 100);
        event.putString("title", webView.getTitle());
        event.putBoolean("canGoBack", webView.canGoBack());
        event.putBoolean("canGoForward", webView.canGoForward());

Thus, shouldInterceptRequest should have its own event object which will be a subset of WebviewEvent

Since shouldInterceptRequest is never called on the main thread, the timeout imposed for this function does not refer to how long the main thread is blocked, rather how long should the function wait before resorting to the default request
The current implementation only allows for a static intercepting of a request. This can be changed to allow dynamic page interception by changing the callback to be asynchronous
Using the infinitered website, we perform the following test and notice that it would usually take 80 - 300ms to intercept a request (with the bottleneck in downloading the url)

onShouldInterceptRequest={async (event) => {
            if (event.url === 'https://infinite.red/') {
              const start = new Date().getTime();
              const response = await fetch('https://infinite.red/');
              const html = await response.text();
              const modifiedHtml = html.replace('', '
Request succesfully intercepted!
');
              console.log("onShouldInterceptRequest end", new Date().getTime() - start)
              return modifiedHtml
            }
          }}

Hi @Titozzz, would appreciate it if you can take another look at this pull request. I have fixed the build error, cleaned up the code and done further testing on this feature.
Also would help if we could have this PR changed from draft to ready for review.
Thank you
PS: This account has the same owner as the original poster of the pull request

this is the feature my teams are desired for  : )


Formatting stops when encountering - > tokens in a macro call that is longer than the line length limit

The code
macro_rules! foo_bar_baz {
    (() - > FillTheLineSomehow_AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA) => {
        Some(5)
    };
}

fn main() {
    foo_bar_baz!(() - > FillTheLineSomehow_AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA)
    .map(|_|
        "hello"     .to_string() // note this bad formatting here
    );
}

gets formatted to exactly the same output, using default options.
Statements after this one get formatted correctly.
The code compiles successfully using rustc.
Rustfmt version: rustfmt 1.4.38-nightly (30b3f35 2022-02-17) (latest version right now)
Some things I tried thatmade rustfmt format the code correctly:

Removing the - or > from the macro
Making the line shorter

#1128 seems to be related to this.
The issue was discovered by @Super-Pizza, I found this minimal example.

Thanks for reaching out, but going to close as this is a duplicate of #3863


WASM Blazor Error: RAZORGENERATE : error RZ3008: Tag helpers cannot target tag name '.

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
Essentially duplicate of the dotnet/aspnetcore#13881
I create tag helper in Program.cs to play with custom component and have less ceremony, and this is what I got for mu curiosity.
CSC : error RZ3008: Tag helpers cannot target tag name '<global namespace>.НазваСторінки' because it contains a '<' character.

Expected Behavior
I would like to be able define components without namespaces and let Razor compiler use such classes.
Steps To Reproduce
No response
Exceptions (if any)
No response
.NET Version
No response
Anything else?
No response

@kant2002 Could you please provide a simplified project in a GitHub repo that reproduces the issue you're seeing? This will help with the investigation.

I create tag helper in Program.cs to play with custom component and have less ceremony

@kant2002 Tag helpers are typically used in .cshtml files, like in an MVC View or Razor Page. They aren't typically used in Blazor apps. We do use some of the tag helper infrastructure for Blazor components, but that's mostly an implementation detail. Can you clarify what you're really trying to accomplish?

@jjonescz We did some work recently about allowing namespace-less components right?

We did some work recently about allowing namespace-less components right?

@chsienki Yes, it's waiting for reviews: https://github.com/dotnet/razor/pull/10086 :)

@kant2002 Could you please provide a simplified project in a GitHub repo that reproduces the issue you're seeing? This will help with the investigation.

I basically try to create my own "copy" of PageTitle. so I decide to borrow code, and place it while experimenting into Program.cs to test idea.


Update binod.py

Comment always helps us to understand code in fast. I am also a beginner, like us, many friends are there, it will help full for them.
Thank you...

Currently, I am learning how GitHub works it will be thankful if you will help me. thank you


Simultaneous sweep of multiple parameters for steady-state solutions

Hi,
I'm wondering if the current package implementation supports simultaneous sweep of multiple parameters for the steady-state solver.
What I'm trying to do is essentially have the coefficients of my ODE parametrized by a single index, and find the steady-state solutions for all the values of such index. Can this be mimicked by using time "T" as a parameter in the ODESolver? I see some examples doing such a thing.
The naive option is to run the steady-state solver in a for loop and updating the parameters at each iteration, but I'd like to use the multithreading feature embedded in homotopycontinuation.jl rather than having to nest threading commands (which maybe is still ok?).
Thanks!

The current solver does support multiparametric sweeps, see e.g here this example
You can define a new symbol, c, use it to parameterize your equations and then solve for different values of c separately. T is the independent ‘slow time’ variable. While in reality, a sweep is a time-dependent process, here we are investigating steady-state solutions only. These are a function of c. How these are traversed is a separate issue - a time-dependent problem in T.
Does this help?

My doubt arises from the fact that my coefficients are only known numerically as a function of a parameter, so I have them stored in arrays. Do I understand correctly that, for each coefficient, I can define a function
fn(i)
that takes the index i as input and returns the list value, and then write the polynomial part of my ODE as
\sum{fn(i) * x^n}
where the index "i" has been defined as a swept variable?
Or can I directly give the indexed arrays in the ODE?

I see, in this case the intended usage is to simply leave the parameters are they are and substitute numerical values at the point of solving, i.e., as an argument to the function get_steady_states . This will then return a set of solutions corresponding to the parameter values.

I see, in this case the intended usage is to simply leave the parameters are they are and substitute numerical values at the point of solving, i.e., as an argument to the function get_steady_states . This will then return a set of solutions corresponding to the parameter values.

Ah I see, thanks alot! I'll look a little more in detail in the "get_steady_states" source code, will let you know if I succeed or not! :)

Hi Jan,
I tried playing around with it, but couldn't find the correct way of entering my numerically defined ODE parameters.
I'll share a simple example of what I'm trying to do.
_Let's say my ODE has three parameters: a1, a2, b; a1 and a2 are only known numerically, have same length and are to be swept simultaneously, let's say
a1 = [1,3,7]
a2 = [2,5,4]
while
b = [8,9,10,11]
is a parameter independent from a1 and a2.
I would like to perform a 2D sweep where a1 and a2 are swept simultaneously, for every value of b._
How should I organize these parameters and what would be the syntax to feed them into the get_steady_states function?
By going thru the source code of get_steady_states I understand that n-dimensional sweeps are handled by flattening some sort of meshgrid to 1D arrays, which are in the input_array argument of the _get_raw_solutions function. Correct me if I'm wrong.
Thanks,
Sandro

This is correct, there really is no more you can do than doing an effective 1D scan in a parameter space of your choice. For your problem, you could just call get_steady_states 3 times, once with each value of (a1, a2), and sweep over b.


Router bugfix - Default target for back button

Fixes #1131
Don't know if this has any other side effects though. Currently the fix seems to work fine for me.

Looks good, thanks!


Allow adhoc explorers [APE-1151]

Overview
one step we can take to help lessen the debt of adding new networks:
allow setting arbitrary explorer URLS for networks that may or not exists:
Specification
etherscan:
  host_map:
    foo_net: "https://mainnet-fooscan.io"

Dependencies
Include links to any open issues that must be resolved before this feature can be implemented.

custom networks works now


Invalid version

Hi there.
I have problem with compatibility 1.19.2

There is range in description 1.19.2 to 1.19.4
Please fix if possible or change description.
Cheers :)

ill fix with the next update


[GUI NX ] v-guinx-18.01.22 - Error messages - Not intuitive for the user

I'm submitting a ...

[ ] bug report
[ ] feature request
[ ] support request
[x] improvement

When using non-acceptable characters (space) in the attribute name, the template is not created, but the message is not intuitive for the user.

Please tell us about your environment:

Version: v-guinx-18.01.22
Environment: [docker-compose]
Operating system: [Ubuntu 16.04]

Version tested: Version: DEV-220816
The behavior repeats.


Remove snackbar element from DOM when closed

This library adds a new snackbar every time the $toast method is called. When this method is used extensively, it creates a lot of snackbar elements that just end up sitting in the DOM.
Maybe these should be removed, for performance reasons?

@Nikey646 can you please provide an example or more details to reproduce this behaviour?

@Nikey646 Ok, I still don't see the component sitting in DOM since it's replaced with empty comment when VSnackbar value is false, but I did check some memory snapshots and I can see that number of VueComponent was growing with each toast call. This commit fixes that by calling $destroy() for each instance. But empty comments are still there and I didn't find a way to remove them yet.

It seems that you found something.
As far as my own personal use case, i had a scenario where user interaction caused an Ajax Request, and i was using a toast to show both successful and error responses. When the user did a large number of those interactions, without reloading the page, the whole page would crawl to a stop quite quickly.
I went to check something in the Vue Dev Tools, and noticed multiple  elements, and under every single one except for the first, was a single VSnackbar. When i removed the toast showing on success, and performed that interaction in bulk, there was no noticable slow down.
These tests were done in vue.js dev mode, which may not have helped performance.

A quick google later, and it appears to completely remove a vue.js object from the dom, you need to first call .$destroy() and then .$remove() forum thread, api docs. You can also optionally do .$destroy(true) to have it remove at the same time.

@Nikey646 docs seems to be from older versions. Vue 2.6 don't have params for .$destroy() and there is no .$remove(). Can you please test if you see components in Vue Dev Tools after updating to 0.6?

Ahh poop, I didn't realize that I was viewing older versions of the docs... That's annoying.
I'll check it out when i next get a chance!

This appears to at least reduce how badly the impact is. I no longer see multiple <Root> elements in Vue devtools either. I'll close this issue for now, thanks for the prompt fix!

Thanks for your assistance!


Upgrade to v8+ cause infinite loop

Hi,
We started to upgrade our app libs and faced with issue with your lib. When we upgraded  from v7.3.0 to 8.2.6 we get infinite loop from redux form. We are isolated this  issue and we know that it caused by redux form.
Below provided our code example from one of our redux form:
render() { const { t, handleSubmit, theme: { axisPalette }, submitting, pristine, } = this.props; return (
<form autoCapitalize="none" autoCorrect="off" onSubmit={handleSubmit(this.submitForm)}>

        <Field label={`${t(`${FULL_NAME}`)}*`} name={FULL_NAME} component={renderInput} disabled={submitting} />

        <Field label={`${t(`${EMAIL}`)}*`} name={EMAIL} component={renderInput} disabled={submitting} nativeInputProps={{ style: isRtl ? { textAlign: 'left', direction: 'ltr' } : {}, }} type="email" />

        <Field label={`${t(`${ABOUT_YOU}`)}`} name={ABOUT_YOU} component={renderTextArea} disabled={submitting} showMultilineUnderline={true} focusedUnderlineColor={axisPalette.accentColor} rows={1} enableInputTopMargin={true} />

        <Field name={NEWSLETTER} component={renderCheckBox} //disabled={submitting} withError={true} />
        {t(`${NEWSLETTER}`)}

    <Field component={renderInput} type="hidden" name={HIDDEN_INPUT} style={{ display: 'none' }} />
</form>

const enhance = compose(
  translate(),
  withTheme(),
  reduxForm({
    form: 'EditUserForm',
    validate: (values, props) => {
      const errors = {};
      const { t } = props;

      errors[`${EMAIL}`] = t(validateEmailField(values[`${EMAIL}`]));
      errors[`${ABOUT_YOU}`] = t(verifyInputLength(values[`${ABOUT_YOU}`], MAX_LENGTH_ABOUT_YOU));
      errors[`${FULL_NAME}`] = t(verifyInputLength(values[`${FULL_NAME}`], MAX_LENGTH_FULL_NAME));
      if (!values[`${FULL_NAME}`]) errors[`${FULL_NAME}`] = t('requiredField');

      return errors;
    },
    onSubmitFail: (errors) => scrollToError(requiredFieldList)(errors),
    onSubmitSuccess: (result, dispatch, props) => {
      props.handleSubmitSuccess(true);
    },
    enableReinitialize: true,
    destroyOnUnmount: false,
  })
);

To this form passed initalValues from upper component
    let initialValuesMyDetails = {
      [`fullName`]: fullName,
      [`email`]: email,
      [`aboutYou`]: locale.iso === 'lv' ? currentUser.oldAboutMe : currentUser.oldAboutMeEn,
      [`newsletter`]: isSubscribedToNewsletter || false,
    };

The error that we get is:

Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate

And the stack trace points to disabled={submitting}prop in first Field
What's your environment?
"react": "16.9.0",
"react-redux": "7.1.0",
"redux": "4.0.4",
"redux-form": "8.2.6",
If you need any another information we will glad to provide it to you in order to solve this, as we  think, issue

@sashberd could help us providing a codesandbox that reproduce this problem?

I've also experienced the same error/exception on:
"react": "16.8.6",
"react-redux": "7.1.0",
"redux": "4.0.4",
"redux-form": "8.2.6",

@x8lucas8x Could u help and provide a sandbox? I need an code example so I could work in a fix.

@eldar-gamisoniya I wasn't able to get any error from your sandbox.

I'm closing this issue since I couldn't reproduce, if someone returns with some workable sandbox example I'll be happy to reopen it.

@renatoagds it doesn't throw any errors, the test is just running indefinitely, unable to finish.

@eldar-gamisoniya Thanks for your example, but I couldn't extract any idea about what is happening from it. If you could create something more reachable I'll be awesome.

@renatoagds
HI after deep investigation and help from our third party partner we found that this infinite loop was the result of our programming. However, this code did not provided such infinite loop with old lib version.
Our old configuration was:
"redux": "^4.0.0",
"redux-form": "^7.3.0",
Our new configuration is:
"redux": "^4.0.4",
"redux-form": "^8.2.6",
The code issue was in next pattern:
<SwipeableViews
          index={this.state.slideIndex}
          onChangeIndex={this.handleChange}
          enableMouseEvents={true}
          disableLazyLoading={true}>
          {sections.map((section, index) => (

              {React.cloneElement(section.content,)}

          ))}
        </SwipeableViews>

Let me explain some of vars here:
sections - is an array of Components that has content prop with Component to render
The issue was in parent div with its key property (bolded) that is defined as Date.now() + index.
I understand that such key is not acceptable anyway and such code is beneath every review, however, in version 7.3.0 it did not provide any loop and worked perfect.
May be in old version you had some defence from such coding errors that in new version was removed or upgraded.
FYI guys
Hope this will help to someone

I'm also encountering this with the same example provided by  @eldar-gamisoniya
I think the issue here is caused by forwardRef having circular structure. Similar to using JSON.stringify on it (at least stringify will throw an error), the default serializer config will try to serialize an infinite loop.
**Work-around when using 'enzyme-to-json' **
I modified the enzyme serializer instead to remove forwardedRef on certain json.type patterns
`
import { createSerializer } from 'enzyme-to-json';
function mapJson(json) {
// Fix snapshot error when mounting redux-form components due to circular structure
if (json.type === 'Connect(ConnectedField)' || /Connect(Form(\w+))/.test(json.type)) {
return {
...json,
props: {
...json.props,
forwardedRef: undefined
}
};
}
return json;
}
expect.addSnapshotSerializer(createSerializer({ map: mapJson }));
`


Games crash on proton-experimental when using DXVK_FILTER_DEVICE_NAME

I'm experiencing this issue after upgrading to proton-experimental, or proton-ge 7.30 (7.26 works fine).
When I launch any game with the parameter:
DXVK_FILTER_DEVICE_NAME="AMD Radeon RX 6700 XT" %command%

the game crashes. If I either disable the parameter, or I go back to protonge 7.26, the games work fine. Did you guys touched something related to this parameter? How could I provide you more info to debug this? Thank you.

We haven't changed anything. I don't know why changing Proton versions would break anything here.
Anyway, DXVK_FILTER_DEVICE_NAME ONLY works if the name you enter matches what your Vulkan driver returns, and if the driver in question also supports the feature set required by DXVK. Since you're probably trying to use AMDVLK or the proprietary driver, make sure to use the latest versions for Vulkan 1.3 support.
I also don't know which DXVK versions the respective proton-ge versions are shipping so I can't even tell you if an outdated driver would even be the issue here.

Yes as Doitsujin said make sure your drivers are up to date. Proton experimental and any GE version from 27 and up have bumped them. So I'm guessing this is that. 22.0 being the minimum for mesa radv now.
Remember that steam flatpak includes its own drivers if you use that.
If you want some more specifics then you need to post a dxvk log from a crashing game.

@Blisto91 was right on the money, I needed 'mesa-git' from AUR instead of 'mesa' from arch repos this time. It seems I got overconfident about the freshness of the packages just for being using arch lol. Thank you so much guys.

Regular mesa (radv) from the arch repos should work. I use that myself.
mesa-git installs everything in one package so you most likely had something that wasn't up to date in a individual package. Or something was semi broken, who knows.
But glad you got it working


Correctly evaluate variable types passed with -var

Fix [DT-1601]

Pull Request Test Coverage Report for Build 573

14 of 14 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 56.451%

Totals

Change from base Build 565:
0.1%

Covered Lines:
3334

Relevant Lines:
5906

💛  - Coveralls


Performance problems with tf.nn.embedding_lookup in eager mode

System information

Have I written custom code: Yes - I condensed it to a self-contained example and attach it to the issue.
OS Platform and Distribution: Ubuntu 18.04.3 LTS
TensorFlow installed from: binary (pip)
TensorFlow version: 2.0.0
Python version: 3.6.8
CUDA/cuDNN version: CPU only
GPU model and memory: CPU only

Describe the current behavior
tf.nn.embedding_lookup with eager mode enabled is so slow for me that it is practically unusable. Falling back to Numpy is faster by an order of magnitude.
Describe the expected behavior
The embedding lookup should perform well enough to be used. Or the information on how to use it properly should be improved.
Code to reproduce the issue
Below is my benchmarking code. It simulates a static word2vec (3M, 300d) lookup with artificial data under different configurations. I use a static document length of 500 tokens which I found to be the average of my dataset (OpenWebText sample).
tf-embedding-benchmark.zip
Other info / logs
Below is a plot of my benchmarks. I did the benchmarks with little data and therefore there's a bit of variance in the charts. I'm currently running them with some more data, but it takes time because it is so slow. As far I can tell already, the results do not look significantly different though. embedding_type refers to the embedding lookup: numpy means Numpy indexing using tf.py_func. The TensorFlow variants refer to the underlying embedding data structure: tf.constant and tf.Variable with and without the trainable flag set.

@jjedele,
Could you please update TensorFlow to the latest stable version v2.4 and check if you are facing the same issue. Thanks!

@jjedele,
Could you please update TensorFlow to the latest stable version v2.4 and check if you are facing the same issue. Thanks!

@amahendrakar , sorry, in the meantime I do not have access to the system anymore. We worked around the problem back then. We can close the issue since apparently it's not something other people ran into.

@jjedele,
Thank you for the update. Closing this issue, please feel free to re-open if necessary.


KIC 2.0 - additional watcher flexibility (e.g. namespaces)

The scope of this issue is to identify what other (potentially useful) knobs we might expose to the user to configure watching behavior, and implement them.
KIC 1.x was capable of watching all namespaces or a single namespace. It looks like a low hanging fruit to make it possible to watch multiple namespaces.

The 1.x behavior stems from a limitation in go-client, and the maintainers have indicated that they do not intend to change it.
controller-runtime provides a wrapper to automate (AFAIK) management of multiple go-client instances and aggregation of their results: https://github.com/kubernetes/kubernetes/issues/74415#issuecomment-662448739

make it possible to watch multiple namespaces

this part of the scope resolved by https://github.com/Kong/kubernetes-ingress-controller/pull/1317


⚠ LPDM Handbook (hosted on Divio) has degraded performance

In f28df97, LPDM Handbook (hosted on Divio) (https://repohubdev.tk) experienced degraded performance:

HTTP code: 500
Response time: 5125 ms

Resolved: LPDM Handbook (hosted on Divio) performance has improved in 39a6584.


not support rails 4

i use rails 4.1 or 4.0
but nested_scaffold gem maybe support rails 3.2.2
i want nested_scaffold support rails 4

same here...

@hackerwins / @x1wins hey guys, simple workaround is to simply VIM into the offending file (stylesheet generator) and remove the 'require' line.
Here's an example on my machine:
cd /Users/YOUR_USER_NAME/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/nested_scaffold-0.1.0/lib/generators/stylesheets
Obviously you may not use rbenv, etc but the exact path will show up in the stack trace when you try to run the nested_scaffold command on a rails 4 app.
Simply go into the file and neutralize the content so it looks like this:
  module Generators
  end
end```

This gem supports Rails 4.2 and 5.0 now. Thanks!