overlapblock Creator - Web design #28

https://images01.nicepagecdn.com/page/42/59/html-template-42590.jpg Design a overlapblock like the above image
Create a file "overlapblock_NUM_by_(YourName).html" in the modules/overlapblock folder.
Use simple HTML and CSS and JAVASCRIPT to create the overlapblock animation. You can use the interface development https://kwickerhub.com/ (This project) or you can write the lines of code yourself.
Step by Step Guide.
Fork this project(Use the 'fork' button in the top right corner) and Clone your Fork.
git clone https://github.com/YOUR_USERNAME/frontend
Open your code Editor and Create a file "overlapblock_NUM_YOUR_NAME_.html" in the "modules/overlapblock" folder of this project you just cloned. No need to create head, title and body tags, Just Add a div tag with some embedded style(i.e use the style tag) and the script tag where necessary.
If you want to add an image resource, please add it in the folder ••
"modules/overlapblock/images_and_icons"
We recommend you use an svg for your image/icon.
Push your Code: You need to push your recent changes back to the cloud. Use the command below in the main directory of this Repository
git push origin dev
or use a GUI tool to avoid mistakes or complexity. LOL.
Then make you Pull Request...
Below is a example of the code structure we need:
'''

'''
For more examples:
modules->buttons
modules->cards
for examples of contributions or Pull request accepted in to the project.
And please do not wait for this issue to be assigned to you as we have limited hands but have a lot to do/cover. Please send in your PR.
Good-luck.

Hey , I would want to work on this issue.

no problem 👍. Go right ahead and work on it ..
On Tue, Nov 21, 2023, 03:17 madhavashok @.***> wrote:

Hey , I would want to work on this issue.
—
Reply to this email directly, view it on GitHub
https://github.com/KwickerHub/frontend/issues/437#issuecomment-1820106291,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOKWIBNPU3XTQJBWJD37EYTYFQFLJAVCNFSM6AAAAAA5SWUPH2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRQGEYDMMRZGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

#820 Created a Pull Request , please do check it and review it.

#866 , Created a PR request , please review it


[mempool] Perf regression with CT burst mode

🐛 Bug
if we enable burst mode in CT, CT will do keep submitting txs without waiting commit succeed. This over submitting behavior triggered unusual behavior of mempool, which we can see a deep perf regression.
Command to run tests
with burst mode, duration 4mins:
./scripts/cti --master --run bench --burst

dashboard:
http://grafana.ct-1-k8s-testnet.aws.hlw3truzy4ls.com/d/performance/performance?orgId=1&from=1612887437000&to=1612888257000
http://grafana.ct-1-k8s-testnet.aws.hlw3truzy4ls.com/dashboard/new?panelId=2&edit&fullscreen&orgId=1&from=now-30m&to=now
with burst mode, duration 10mins:
./scripts/cti --master --run bench --burst -- --duration 600

dashboard:
http://grafana.ct-1-k8s-testnet.aws.hlw3truzy4ls.com/d/performance/performance?orgId=1&from=1612888759000&to=1612889892000
http://grafana.ct-1-k8s-testnet.aws.hlw3truzy4ls.com/dashboard/new?panelId=2&edit&fullscreen&orgId=1&from=now-30m&to=now
normal mode without --burst, duration 4mins:
./scripts/cti --master --run bench

dashboard:
http://grafana.ct-2-k8s-testnet.aws.hlw3truzy4ls.com/d/performance/performance?orgId=1&from=1612466565000&to=1612467237000
http://grafana.ct-2-k8s-testnet.aws.hlw3truzy4ls.com/dashboard/new?panelId=2&edit&fullscreen&orgId=1&from=1612466565000&to=1612467300000
Observed points:

From normal mode, we can see it does have a constant slope of committed txn, but burst mode always stops committing around 1min 30secs no matter how long of the duration
Normal mode 4 mins duration can totally commit more than 200k txn, but burst mode can only make max around 40k txn no matter how long of the duration

Normal mode, 4 mins

Burst mode, 4mins

Burst mode, 10mins

@davidiw @zekun000
To reproduce
Code snippet to reproduce
# Your code goes here
# Please make sure it does not require any external dependencies

Stack trace/error message
// Paste the output here

Expected Behavior

System information
Please complete the following information:

Additional context
Add any other context about the problem here.

Oh wow, so this becomes entirely choked?

Oh wow, so this becomes entirely choked?

seems yes

it's fun that validator mempool are empty but fullnode all have 15k

Thanks for flagging @snakech. Would it be possible to provide links to the logs? I have a few suspicions around the mempool code and hopefully the logs will shed some more light here.

Thanks for flagging @snakech. Would it be possible to provide links to the logs? I have a few suspicions around the mempool code and hopefully the logs will shed some more light here.
@zekun, one of my suspicions is around the notifications between consensus and mempool (e.g., when consensus pulls transactions from mempool). For example, if you compare the graphs of a normal run vs. a burst one, you can see:

consensus event loop idle percent is much higher (which suggests mempool has flopped, not consensus)
looking at the "pull txn" graph, the response time spikes and then there's no more data. Perhaps we're hitting a timeout, e.g., here? https://github.com/diem/diem/blob/5f5f317f4591311a28439a57a44ad684b0a74112/consensus/src/txn_manager.rs#L63

Anyway, logs should definitely help here.
will redo the test and post the logs there

http://kibana.ct-2-k8s-testnet.aws.hlw3truzy4ls.com/app/kibana#/discover?_g=(time:(from:'2021-02-11T16:49:36Z',to:'2021-02-11T17:00:15Z'))
Log is updated for 4 mins burst test

11:38
so the it’s possible that one txn with seqnum X expired before committed (the expiration is 50s) resulting all the subsequent txns to never be ready``` by @zekun000, thx for your find.

fully explanation here: https://toroeng.slack.com/archives/G01MAKL02UX


Question:  Is this going to be official support of React native for tvos?

In official react native 0.60.5, I am unable to compile RN code for TVOS. Is this repo official one for AppleTV support?

From README.md: “Going forward, Apple TV support for React Native will be maintained here and in the corresponding react-native-tvos NPM package, and not in the core repo. This is a full fork of the main repository, with only the changes needed to support Apple TV.”
Note that at this time, we have only 0.60.4-based releases.

Hey @dlowder-salesforce, how could we have it for React Native 0.59.10?. Thanks

@stevengiraldo you could try https://www.npmjs.com/package/react-native-tvos/v/0.59.8-1

Works fine. But I'd like to contribute with a release for 0.59.10
is there a particular process to do that?
Thanks!

@stevengiraldo there isn't a well defined process yet.  Currently the process is manually selecting the exact commit for a particular core version, then cherry-picking just the commits needed to get tvOS working.  There are always merge issues since RN changes pretty quickly.
In having a look at core, it seems that 0.59.8 and 0.59.10 differ by just 14 commits, so having a release should be possible.

@stevengiraldo please try 0.59.10-2 -- that should give you everything in core 0.59.10 plus all tvOS fixes.

Hey, @dlowder-salesforce it works perfectly, thanks for the support.


How do I add "Window Manager\Window Manager Group" back into the "Increase Scheduling Priority" (Local Policies \ User Rights Assignment"

Hello @LPonten. To which article does your question apply? This will help us route it to the right writers/team.

https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/increase-scheduling-priority
From: Denise Vangel-MSFT<EMAIL_ADDRESS>Sent: April 13, 2020 10:55 AM
To: MicrosoftDocs/windows-itpro-docs<EMAIL_ADDRESS>Cc: Loren Ponten (H10 Capital<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/windows-itpro-docs] How do I add "Window Manager\Window Manager Group" back into the "Increase Scheduling Priority" (Local Policies \ User Rights Assignment" (#6471)
Hello @LPontenhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FLPonten&data=02|01|v-lopont%40microsoft.com|7ae75428dc014d0d715408d7dfd3d322|72f988bf86f141af91ab2d7cd011db47|1|0|637223973188589988&sdata=WvGtBWKBYqfmQI%2FuULHu0NrdRbCObwOVNs2h9mgnOLk%3D&reserved=0. To which article does your question apply? This will help us route it to the right writers/team.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fwindows-itpro-docs%2Fissues%2F6471%23issuecomment-613013795&data=02|01|v-lopont%40microsoft.com|7ae75428dc014d0d715408d7dfd3d322|72f988bf86f141af91ab2d7cd011db47|1|0|637223973188589988&sdata=cAz8NDDg8mU%2B44M54wa9gF6%2BZmonHa0NV8YSQik4ciA%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALDSKV4RBOLIFXJVXWOSHV3RMNGYJANCNFSM4MGFQLYA&data=02|01|v-lopont%40microsoft.com|7ae75428dc014d0d715408d7dfd3d322|72f988bf86f141af91ab2d7cd011db47|1|0|637223973188599942&sdata=z63NOuE6eGq82xboGLVkPyA14jX0MdwpYrJRE4fLfo4%3D&reserved=0.

hello, @LPonten,
you could do it by performing following steps:

go to the policy where you removed "Window Manager\Window Manager Group" from
go to computer configuration>windows settings, right click on security settings and select export policy

save the file, open it using notepad
find the string called SeIncreaseBasePriorityPrivilege and append *S-1-5-90-0 to it (*S-1-5-90-0 is Window Manager\Window Manager Group)

save the file, import it back to the policy

Thank you

@LPonten  - Thank you for submitting feedback.
From our understanding, the issue you raised has been answered by @MaratMussabekov so we will close this issue.
Thank you for your contribution to make the docs better! Much appreciated!


Refactored QuadTree

The name of the class was changed from Index to QuadTree.
The __init__ method of the former Index is now a classmethod called from_bbox, so the normal __init__ now takes x, y, width, height, max_items, max_depth as arguments.
The countmembers was renamed to the standard __len__. (One can now do len(qt).)
The _split method was made more efficient.
Code was reformatted to conform more to PEP8 and a doctest was added.

What's still missing? Methods for updating / relocating and removing items (both could have a prune=False parameter). The QuadTree also needs methods for clearing and pruning the tree (i.e. removing empty nodes).

@karimbahgat Cool that you've merged my PR. Btw. I just noticed that I forgot to update the README.rst. It still references the old name.

@CreamyCookie Well I really liked the changes you made, appreciate that. Updated the README and the html docs too.
However, I decided to make a commit that reverses some of your changes, see 2520b65965a80965ce165f62dbfd27b650b36727
Mostly I wanted to keep the class name as "Index" since I want pyqtree to be comparable and as similar as possible to the Rtree and Pyrtree packages. Also, I prefer the default initiation of the Index to be using a bbox which is common to know in GIS work (I can't think of a scenario where setting the x, y, width, and height is the most intuitive way) and  I'm not a big fan of classmethods either. Regardless, I kept the x, y, width, and height args as an optional way of initiating the Index for users that might prefer that.
And regarding the "still missing" that you mention, I won't have time to do that for a while, and I'm not that well versed in the QuadTree algorithm (since I just forked an existing implementation). But if you know how and have time implement them, I will for sure welcome any additional pull requests.


Inference on remote host

Could not connect to display
Hey guys I am trying to run the inference example remote on a ubuntu 18.04 server.
and I am getting the following error
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "/home/dan/miniconda3/envs/anomalib-3.8/lib/python3.8/site-pa
ckages/cv2/qt/plugins" even though it was found.

This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix
this problem.

Available platform plugins are: xcb.
Aborted (core dumped)

Is there a way how I can save the results or port forward the display?

I ran into the same issue when trying to run tools/train.py on Ubuntu 20.04 Desktop with anomalib installed in a conda virtual environment as stated in the readme.

Hi @patzaa and @LukasBommes, sounds like this is more related to opencv and qt installation. Perhaps you could refer to the issue created in opencv. This comment seems to address it.

Thanks for your reply! I have PyQt installed, so that could indeed be the issue. I will run anomlib in a Docker container to circumvent this issue.

hi @patzaa and @LukasBommes, as you pointed out this is more like an issue with opencv not anomalib. I'm closing this issue for now. Feel free to reopen it if you still have issues regarding anomalib.


Non-String x-examples

We have some swagger documents that define x-examples fields as objects and not strings in body parameters.  Seems that the code merged to resolve #1500 adds specific handling for x-examples field and assumes the value is a string.  We cannot parse our swagger files (which are valid according to the spec since x-* values should be allowed to be any type).

Follow #1107


Create The Messages Schema and Its Associated Controllers

This entity represents the messages that users send or receive on our platform. Determine the required attributes and relationships.

@Marrwan you've been inactive and I have assigned this task to someone else for progress' sake

@SirSanctified I have been working on it, just not completed that's why. I'll push the ones I've done now.
Thank you for your ptience. I'm sorry for the delay.

I'll wait for you then to push and open a pull request by day end. After that I'll work on it because we have to start the new milestone on Monday and we can't do so with other tasks pending.
Thanks for the feedback

@SirSanctified I haven't done a pull request yet, but I have pushed what I have done. I should complete it by the end of today


Update front-door-diagnostics.md

Fix: "activity log" should be "access log".
Also use WAF acronym to be consistant with the preceding paragraph.

@duongau
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Update dependencies; fix ts-jest config to support ESM-only dependencies

Update jest configuration to allow us to update some dependencies for which recent versions are published as esm-only.

Merged pre-review to simplify further branch merges.


Large OS pages support

Hi,
I'm trying to make snmalloc use large OS pages in my application. My use case has been mentioned in https://github.com/microsoft/snmalloc/issues/484#issuecomment-1073236187. My application is targeting Windows. It is memory bottlenecked and I want to reduce page faults. On Linux, 4KB pages can be merged into 2MB large pages implicitly and automatically, but on Windows large page allocation is explicit.
I have tried to modify the PAL to use large pages. The key modifications are:
static SNMALLOC_CONSTINIT_STATIC size_t minimum_alloc_size = 0x200000;    // 2MB
static constexpr size_t page_size = 0x200000;                             // 2MB

// in `notify_using`
void* r = VirtualAlloc(p, size, MEM_COMMIT | MEM_LARGE_PAGES, PAGE_READWRITE);

This PAL works well with snmalloc1, except the need of some small patches (alignas(OS_PAGE_SIZE) not possible, and need to check rsize > OS_PAGE_SIZE before rsize - OS_PAGE_SIZE). I don't know there are flaws or not but it can just run.
snmalloc2 cannot work with this PAL. It crashes at:
https://github.com/microsoft/snmalloc/blob/26324e8bfc28eda735a3335f83f3f1d8f21cc4a0/src/mem/corealloc.h#L690
I'm wondering whether I can use PAL to enable large os page support and expect snmalloc1 to work perfectly, and why this don't work with snmalloc2.

Sorry, may be duplicate with  #222

Would you be able to post the precise commit you used on snmalloc2?  I would have expected snmalloc2 to work better with Large Pages than snmalloc1.  A lot of the redesign was specifically for that, and getting this working is on my list.

Here is the PAL I used with snmalloc2
diff --git a/src/pal/pal_windows.h b/src/pal/pal_windows.h
index 6d64a25..98f9759 100644
--- a/src/pal/pal_windows.h
+++ b/src/pal/pal_windows.h
@@ -15,13 +15,6 @@
 #  include <windows.h>
 #  pragma comment(lib, "bcrypt.lib")
 #  include <bcrypt.h>
-// VirtualAlloc2 is exposed in RS5 headers.
-#  ifdef NTDDI_WIN10_RS5
-#    if (NTDDI_VERSION >= NTDDI_WIN10_RS5) && \
-      (WINVER >= _WIN32_WINNT_WIN10) && !defined(USE_SYSTEMATIC_TESTING)
-#      define PLATFORM_HAS_VIRTUALALLOC2
-#    endif
-#  endif

 #  include <chrono>

@@ -55,16 +48,11 @@ namespace snmalloc
      * Bitmap of PalFeatures flags indicating the optional features that this
      * PAL supports.  This PAL supports low-memory notifications.
      */
-    static constexpr uint64_t pal_features = LowMemoryNotification | Entropy |
-      Time
-#  if defined(PLATFORM_HAS_VIRTUALALLOC2) && !defined(USE_SYSTEMATIC_TESTING)
-      | AlignedAllocation
-#  endif
-      ;
+    static constexpr uint64_t pal_features = LowMemoryNotification | Entropy | Time | AlignedAllocation;

-    static SNMALLOC_CONSTINIT_STATIC size_t minimum_alloc_size = 0x10000;
+    static SNMALLOC_CONSTINIT_STATIC size_t minimum_alloc_size = 0x200000;

-    static constexpr size_t page_size = 0x1000;
+    static constexpr size_t page_size = 0x200000;

     /**
      * Windows always inherits its underlying architecture's full address range.
@@ -144,10 +132,26 @@ namespace snmalloc
     template<ZeroMem zero_mem>
     static void notify_using(void* p, size_t size) noexcept
     {
+      static struct PrivilegeBegger {
+        PrivilegeBegger() {
+          HANDLE hToken;
+          TOKEN_PRIVILEGES tp;
+          BOOL status;
+          OpenProcessToken(GetCurrentProcess(), TOKEN_ADJUST_PRIVILEGES | TOKEN_QUERY, &hToken);
+          LookupPrivilegeValueW(nullptr, L"SeLockMemoryPrivilege", &tp.Privileges[0].Luid);
+          tp.PrivilegeCount = 1;
+          tp.Privileges[0].Attributes = SE_PRIVILEGE_ENABLED;
+          status = AdjustTokenPrivileges(hToken, FALSE, &tp, 0, (PTOKEN_PRIVILEGES)nullptr, 0);
+          if (!status)
+            error("Failed to gain privilege");
+          CloseHandle(hToken);
+        }
+      } begger [[maybe_unused]];
+
       SNMALLOC_ASSERT(
         is_aligned_block<page_size>(p, size) || (zero_mem == NoZero));

-      void* r = VirtualAlloc(p, size, MEM_COMMIT, PAGE_READWRITE);
+      void* r = VirtualAlloc(p, size, MEM_COMMIT | MEM_LARGE_PAGES, PAGE_READWRITE);

       if (r == nullptr)
         report_fatal_error(
@@ -158,31 +162,21 @@ namespace snmalloc
     template<bool page_aligned = false>
     static void zero(void* p, size_t size) noexcept
     {
-      if (page_aligned || is_aligned_block<page_size>(p, size))
-      {
-        SNMALLOC_ASSERT(is_aligned_block<page_size>(p, size));
-        notify_not_using(p, size);
-        notify_using<YesZero>(p, size);
-      }
-      else
-        ::memset(p, 0, size);
+      ::memset(p, 0, size);
     }

-#  ifdef PLATFORM_HAS_VIRTUALALLOC2
     template<bool state_using>
-    static void* reserve_aligned(size_t size) noexcept
+    static void* reserve_aligned(size_t size, size_t alignment = 0) noexcept
     {
       SNMALLOC_ASSERT(bits::is_pow2(size));
       SNMALLOC_ASSERT(size >= minimum_alloc_size);

+      if (alignment == 0) alignment = size;
+
       DWORD flags = MEM_RESERVE;

-      if (state_using)
-        flags |= MEM_COMMIT;
+      static_assert(!state_using, "not implemented");

-      // If we're on Windows 10 or newer, we can use the VirtualAlloc2
-      // function.  The FromApp variant is useable by UWP applications and
-      // cannot allocate executable memory.
       MEM_ADDRESS_REQUIREMENTS addressReqs = {NULL, NULL, size};

       MEM_EXTENDED_PARAMETER param = {
@@ -191,20 +185,16 @@ namespace snmalloc
       // initialisation list.
       param.Pointer = &addressReqs;

-      void* ret = VirtualAlloc2FromApp(
+      void* ret = VirtualAlloc2(
         nullptr, nullptr, size, flags, PAGE_READWRITE, &param, 1);
       if (ret == nullptr)
         errno = ENOMEM;
       return ret;
     }
-#  endif

     static void* reserve(size_t size) noexcept
     {
-      void* ret = VirtualAlloc(nullptr, size, MEM_RESERVE, PAGE_READWRITE);
-      if (ret == nullptr)
-        errno = ENOMEM;
-      return ret;
+      return reserve_aligned<false>(size, page_size);
     }

     /**

Thanks, I have pushed a branch inspired by your code change: https://github.com/mjp41/snmalloc/commit/13ddd507b1912b38acf74a6a151a2130a573cd3c .
This passes the test harness.  What is the workload that was causing your crash?
The code needs proper fall back paths for failing to initialize large pages, and also for handling when there are no more large pages.

It is related to page_size. I have modified both minimum_alloc_size and page_size to 2MB and it crashes.


Update index.ts

Thank you for the detailed feedback Hena, and the thoughtful improvements! I have reviewed your PR, aligned it with the project requirements, and merged it.


Create installation chapter in getting started guide

will be re-opened later and expectations will be added

will be re-opened later and expectations will be added


powerplatform_enterprise_policy

This pull request introduces significant updates to the Terraform configuration for managing Power Platform enterprise policies, including encryption and network injection policies. It also adds a new enterprise policy resource to the provider.
Terraform Configuration Updates:

Added new Terraform configuration for managing Power Platform enterprise policies, including setting up required providers and defining various variables and resources in main.tf files for encryption and network injection policies. [1] [2]
Introduced a new resource.tf file to manage Power Platform environments and link enterprise policies.
Added a new variable subscription_id in variables.tf for specifying the Azure subscription ID.

Provider Code Updates:

Added the enterprise_policy service to the provider's resource list and imports. [1] [2]
Updated provider tests to include the new enterprise_policy resource. [1] [2]

Enterprise Policy Service Implementation:

Implemented the enterprise_policy service with methods to link and unlink enterprise policies.
Defined DTOs and models for the enterprise_policy service. [1] [2]

Codecov Report
Attention: Patch coverage is 69.89247% with 112 lines in your changes missing coverage. Please review.

Project coverage is 73.46%. Comparing base (754f7a0) to head (5f3b0cc).
Report is 6 commits behind head on main.

Files with missing lines
Patch %
Lines

...es/enterprise_policy/resource_enterprise_policy.go
69.62%
40 Missing and 8 partials :warning:

internal/services/environment/models.go
40.57%
40 Missing and 1 partial :warning:

...ervices/enterprise_policy/api_enterprise_policy.go
78.94%
8 Missing and 4 partials :warning:

internal/services/environment/api_environment.go
50.00%
8 Missing and 2 partials :warning:

internal/customerrors/url_format_error.go
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #519      +/-   ##
==========================================
- Coverage   73.84%   73.46%   -0.38%
==========================================
  Files         102      105       +3
  Lines       14454    14947     +493
==========================================
+ Hits        10673    10981     +308
- Misses       3121     3292     +171
- Partials      660      674      +14

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


Add link to rustdoc in README

I often come past here, and a quick link to the docs would be helpful!

Thanks!


[1.19.2 Forge] Server crashes on startup, mod isn't detecting forge or something

https://gist.github.com/BugmanBugman/09c70c3b04ca459e87a51ab5d3a059f1

Hi ... just seeing this after thanks giving.  Which mod is having this issue?  I can't see from the log.  I'll try to get it fixed asap once i know.
Thanks!

Oh wait- I see.  ExperienceBugFix.
I'll get on it.

Okay, this has already been fixed.  I think someone (maybe you) put in a bug report about it on discord or curseforge before the holidays.
Sorry for the delay via the github issue channel.  Rough Holidays.
With Best Regards,
Two Guys,
MacTso

Appreciate it man, no worries. Hope you had a good holiday
Get Outlook for iOShttps://aka.ms/o0ukef

From: MacTso @.>
Sent: Wednesday, November 30, 2022 9:53:19 AM
To: mactso/ExperienceBugFix @.>
Cc: BugmanBugman @.>; Author @.>
Subject: Re: [mactso/ExperienceBugFix] [1.19.2 Forge] Server crashes on startup, mod isn't detecting forge or something (Issue #5)
Okay, this has already been fixed. I think someone (maybe you) put in a bug report about it on discord or curseforge before the holidays.
Sorry for the delay via the github issue channel. Rough Holidays.
With Best Regards,
Two Guys,
MacTso
—
Reply to this email directly, view it on GitHubhttps://github.com/mactso/ExperienceBugFix/issues/5#issuecomment-1332380918, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJWX3OTEH5TIH4W3JUB7PMDWK5Z67ANCNFSM6AAAAAASEF27ZQ.
You are receiving this because you authored the thread.Message ID: @.***>

Actually, it truly doesn't load on the server. It's not detecting any Forge version at all in 1.19.2
crash-2022-12-11_14.11.50-fml.txt
Removing this mod allows the server to continue. Any ideas?

@aking4125 I was able to open the ExperienceBugFix-1.19-<IP_ADDRESS>.jar file in 7zip and edit META-INF/mods.toml to match the one line changed in #7 and it worked. It's a workaround until a new patch is released.

Thank you.  I'll fix this (and test it in 1.19.3 as well).
I've been focused SBU and missed this.


Correct architecture for lots of small objects?

Hello,
I have a question regarding the architecture.
I have images like this example, and want to do image segmentation for the white spots.

Do I understand it correctly, that in your architecture there are no limitations about the number of objects that can be detected? Are there limitations about the size of the objects?
If not, I think for a beginner it would be a good start to use your architecture...
Thanks for a short answer!

Hello,
You are correct that the architecture can be used for any segmentation task. In fact, the U-Net architecture was first used for biomedical image segmentation.

Ok thanks! but is there a limit about the number of different areas that can be detected?
In the examples I’ve found most of the times there are less than 10 areas. So I’ve wondered if there is a limit inside the architecture..

The limiting factor is that the model must be expressive enough to solve a task with an accuracy you deem acceptable. If the architecture doesn't perform as well as you need in your segmentation task then you'll have to improve upon it or use a different architecture.


It would be nice to have an handy bottom to select file order in the explorer instead of going to settings

related to:
Add option to sort files in Explorer side-bar by date modified · Issue #11823 · microsoft/vscode

\duplicate https://github.com/microsoft/vscode/issues/108271

Actually a better duplicate of https://github.com/microsoft/vscode/issues/149393


requestAnimationFrame instead of setTimeout

You might want to use requestAnimationFrame for better performance..

@asvd if you're open to this I can send a PR

Interesting, but I don't really get what is the point. On my opinion this might make sence, if someone faces performance issues resolved wiht this approach (do you have an example?), or if this would save 10 more bytes out of the library size :-)

The point is that requestAnimationFrame is made for this purpose while setTimeout(fn,1) is most definitely fired more often than once per frame, and perhaps not at the right time to do so, pushing a frame duration long enough to be missed for the next screen update rate.
More info: https://www.paulirish.com/2011/requestanimationframe-for-smart-animating/
The good news since that article is that it doesn't need a polyfill anymore so simply swapping out setTimeout(fn,1) for requestAnimationFrame(fn) would be enough for IE10+
Since you probably want this to be supported in more browsers, it's just a few more bytes in #5

https://www.google.fi/search?q=requestAnimationFrame+vs+setTimeout

I know that requestAnimationFrame is generally better than setTimeout, my point is that there is no serious reason for using it, because it does not solve any issue (there are no known performance issues to be solved). At the same time reusing requestAnimationFrame would require testing it again in many browsers.
If I would write naturalScroll now from scratch, I would use requestAnimationFrame of course, but previously I was not aware of this.
Hopefully, I will find some time soon to review the PR, merge and test it. For this reason I keep this issue open for now. Thanks for the contribution.

After some tests, it appeared that usage of requestAnimationFrame() has lower FPS comparing to setTimeout(). I guess this is because the animation frames frequency is limited by browser at 60 FPS, whereas setTimout() is capable of firing as fast as performace allows.
The CPU usage was also a bit decreased by requestAnimationFrame(), but not that much. In my case, the FPS of setTimeout() was about 120, and CPU usage was about 60% for every of 4 cores. With requestAnimationFrame() the FPS is 60, and CPU is 50% loaded. Maybe this can be explained by the fact that actual heavy redraw frames are more rare than invocations of the callback of setTimeout(). At least I cannot notice the difference with eyes.

requestAnimationFrame is locked to the refresh rate of the screen, which is usually 60FPS. Even if you call something more frequently than that the user won't see any updates because literally the screen won't paint them.
Glad you noticed the lower CPU usage and less frequent calls, that's what RAF offers (while still being as smooth as it can be)

Released in v0.2.2


WIP: UART DMA

Add DMA support for UART peripheral.
Tested with basic loopback example - works fine for single characters but explodes if you send many at once (you can reproduce this by holding a key, so it's not even that fast)

Now it's not even doing as well as before - it either sends nothing or gibberish.

Okay, the swapped dreq is what was causing the failures.
I think we're still not clearing some fault state on startup though - once things go weird they stay that way until the reset button is pressed.

Yep, while this code works we're definitely hitting some DMA issues with it.
If you run the example from a hard reset it works fine.
If you then launch it again via probe-run, it stops at the first DMA write.
If you break, then then launch it yet again via probe-run, it starts spitting out the binary (which makes all my terminal programs very upset.

We weren't resetting the DMA peripheral during init.
It worked the first time because the peripheral was in reset after hard-reset, but not after a soft reset.

We weren't resetting the DMA peripheral during init.
It worked the first time because the peripheral was in reset after hard-reset, but not after a soft reset.

IIRC probe-run doesn't reset the device after flashing, it just jumps to the entry point. This may be a bug in probe-run.

All the other peripherals were already doing
self.reset_bring_down(resets);
self.reset_bring_up(resets);

on startup to ensure they're in a good state.
DMA and PLL are presently the only exceptions.

All the other peripherals were already doing
self.reset_bring_down(resets);
self.reset_bring_up(resets);

Just a side note: I wonder if we need a way to skip this reset. After all, the watchdog can be configured to not reset the whole chip but only parts of it. There are probably applications where you'd want to keep some peripherals running when the watchdog fires.
For now, I'd prefer to keep things consistent and reset all peripherals on initialization. (PLL might be tricky - is it possible to get to that point while some clocks are already configured to run from PLL?)

Just a side note: I wonder if we need a way to skip this reset

The C SDK and examples do not reset most of the peripherals, which suggests that this should be possible.
The only use-case I can think of currently is the dapper-mime 2nd core mode, where you need to avoid reinitialising the entire chip in order to keep core1 communicating via USB.


downloads should open filedialog less often

not?
only once?

save to downloadfolder via:
https://www.electronjs.org/docs/latest/api/download-item
allow override in editor preferences
show notification with actual path


⚠ Bofrost.es has degraded performance

In 1a97a2c, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1573 ms

Resolved: Bofrost.es performance has improved in 412ff17 after 9 minutes.


Update to tensorflow2.16 and tf probability0.24

To use Keras 2 while using tensorflow2.16+ I followed: this and switched to tf-keras.
Dependency constraints for pandas, scipy, xarray, dask, numba and zarr have been relaxed.

Looking at the warnings from the unit tests, I wonder if we could cleanup a bit... can you have a quick look?


#3340 Connection settings can be an async function only for PG client

This relates to issue https://github.com/tgriesser/knex/issues/3340

@Ali-Dalal Any updates?

@kibertoad I haven't gotten the chance to modify the PR yet. for now, I am using Knex from my account's repo which I completely don't agree with.
I will try to modify the PR tomorrow and ask for the feed back again

closing this PR as it is a duplication of #3403
https://github.com/tgriesser/knex/pull/3403


Update VersionChanged of Lint/ConstantDefinitionInBlock

Follow https://github.com/rubocop-hq/rubocop/pull/9033#issuecomment-726588888
VersionChanged has been updated to 1.4 by #9036, but if the next release is 1.3.1 it will be 1.3 correctly.
So I think #9036 change can be included in the 1.3.1 bugfix release :-)

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[ ] Added tests.
[ ] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.
[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Run bundle exec rake default. It executes all tests and RuboCop for itself, and generates the documentation.

I was thinking of having a magic <<next_release>> and have our cut_release:* tasks take care of that.
At the same time, it could take care of updating the cops doc and we wouldn't have to always think about doing it. What about that @bbatsov ?

I've just thinking about similar thing. This idea looks good to me!

At the same time, it could take care of updating the cops doc and we wouldn't have to always think about doing it. What about that @bbatsov ?

Funny enough I was thinking about the same thing last time I was pointing out to someone to change the version. :-) It's a great idea!

Cool, I'm on it


nixos/display-managers: add option to disable starting graphical-session

Description of changes
Add a new option to allow to disable starting the
graphical-session.target automatically. This might be useful to disable to let the window manager starting the session itself rather than letting the display manager doing it before the window manager is actually started. Setting this to false can fix issues with systemd services starting too early on Wayland.

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

If this new option is disabled this should fix this home-manager issue https://github.com/nix-community/home-manager/issues/3599 (as pointed by @berbiche in https://github.com/nix-community/home-manager/issues/3599#issuecomment-1387233002 which I am merely upstreaming his patch, thanks to him very much!).

Hi @flokli, sorry to ping you that way but I don't think there is technically a maintainer for this specific file (IIUC) and you are show as suggested reviewer on Github :see_no_evil:. If you are able to review this at some point in time that would be awesome :heart: :pray:.

Hey @MrFreezeex, I don't really have a strong opinion about this. I'm mostly using gnome these days, and their login screen seem to be able to start an X gnome-shell and a wayland gnome-shell just fine.
You might want to ping some of the maintainers of the sway package, or people tinkering with wayland in general (git history of wayland packages).

Hi @primeos @Synthetica9, as sway package maintainers, would you be able to review PR (or any suggestions on other possible reviewers)? :pray:

Just a drive-by comment since I'm currently trying to untangle this myself, but this would make having both Wayland and Xorg sessions more difficult.
I feel like the whole xinit stack in NixOS may need a review from ground up to make it support Wayland sessions, rather than little patches for specific issues like this one, with a clear flow for which scripts are expected to be run at what time for each compositor.

Just a drive-by comment since I'm currently trying to untangle this myself, but this would make having both Wayland and Xorg sessions more difficult.
I feel like the whole xinit stack in NixOS may need a review from ground up to make it support Wayland sessions, rather than little patches for specific issues like this one, with a clear flow for which scripts are expected to be run at what time for each compositor.

I don't have a lot of experience with this part of the code but I guess it should be possible to start the session inside whatever display manager wether it is xorg or Wayland based maybe? You would still have to do this across all your sessions though this is true.
While I agree that there is probably some larger refactor to do but maybe there would be some more short term options for making this works without having to patch nixpkgs?

While I agree that there is probably some larger refactor to do maybe there would be some shorter term options for making this works without having to patch nixpkgs while a longer term option has been decided/developed?

Probably, I just have long-term concerns with this patch, it'd be a pity if this was the last word in wayland session support ;)
As long as there is a proper tracking ticket for the refactor somewhere, and there's some active work towards it, this patch shouldn't cause any issues, and will make running wayland much easier in the short term.

Sorry for never responding btw. Unfortunately I cannot review this as I've switched to Sway to avoid graphical login/display managers but I should've still responded. If there are no meta.maintainers, like in this case, I usually use git log to check who frequently made relevant changes (but in this case it doesn't look that good... :o). Might be worth a try to ask via Matrix and/or Discord but I'm not sure. I guess you could also look for similar PRs and issues to see who handled them. We'd really need maintainers for this module or a team for that area (maintainers/team-list.nix).

Hey @primeos, no worries! I will try to ask around... I'm not quite sure of what you are implying by "I've switched to Sway to avoid graphical login/display managers" though, I am on sway too and this problem occurs with basically any systemd service that have a target on graphical-session. Like many services from home-manager are like that (wlsunset for instance, waybar if you set systemd.enable). This problem never occurs if you have no systemd service with that kind of target and you have everything in your sway config with some exec`.

@MrFreezeex I mean that I start Sway from a tty/VT (which is the recommended / only supported approach btw: https://github.com/swaywm/sway/#running; it's also the only approach that we officially support in Nixpkgs/NixOS) and not via a login/display manager that executes that xsession-wrapper script (so I basically (intentionally) "bypass" the whole script anyway; I never really liked that script much tbh).
Plus I don't use any systemd user units that depend on that target (then again there might be some on my system that NixOS installs by default that I didn't notice).
Anyway, therefore this change shouldn't affect my setup at all (and I cannot (properly) review it).


Fix trailing tabs

Fixes trailing tabs in comments.
(See #17 which this PR is replacing).

@stefanwalther Thank you for this PR :sparkles:


monitor: 0.7.1 -> 0.7.2

Motivation for this change
see: https://github.com/stsdc/monitor/releases/tag/0.7.2
(As a side note, I changed my GitHub username without thinking about the side effect it would have on the nixpkgs I maintain. Should I make a pull request to update it, or leave it as it is now ? As I've understood, people can always find me through my GitHub id anyway)
Things done

[ ] 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/)
[ ] 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.

(As a side note, I changed my GitHub username without thinking about the side effect it would have on the nixpkgs I maintain. Should I make a pull request to update it, or leave it as it is now ?

It would be great if that attribute was the same as your github username.

Can i do this in this PR or is it cleaner if I open a new one specifically for that and then update this one once it's merged ?

@xiorcale It is okay to do it in this PR, but it should be a separate commit.


Discussion: Creating a C Interface

This is my first attempt of a proof-of-concept Rust -> C -> Julia roundtrip that was discussed in #381 where I just wrapped the first function calls of the basic example that create a repository and adds some groups. Whoever is interested, maybe you can have a quick look and let me know your opinions. A C header file is generated, but currently the c wrapper in icechunk-julia is manually generated. Of course, if one wants to roll out a full c lib for the storage interface there would be a few design decisions to make. The most burning questions I would have are the following:

To what extent would one expose rust structs through the C API as well. For example things like RepositoryConfig could be marked with [repr(C)] to get C memory layout which would make sharing them much more convenient. In the end only things wrapped in Arcs actually need to be hidden behind opaque pointers.
Some system of automated error code translation would be nice, in the example here I only return a generic -1 in case of any error
Also important to note that any panic on the rust side leads to a segmentation fault on the caller side, to it is crucial to carefully unwrap every result
In this example I use calls to block_on to get out of the async machinery. However I have no idea how this would interact if a calling site actually tried to perform async calls into the library (probably it would just break?)

@meggart - just wanted to drop a note to say THANK YOU for working on this. We are planning to give you some feedback very soon.


fix(android): settings data getting reset bug

Settings got reset in Eugene scenario due to conflict between code that sets the configuration with default values, and the code that restores previously stored values.
I have implemented the same solution as for RN iOS some time ago, and testes myself (seems to work fine).

The PR will be re-opened in simplified version


Players should not lose more henchmen than they have

Saw this during testing:

Didn't read the output right. 😑


How to delete events/videos or how to actove person detection without video capture

Hello,
first I tried to activate (via api and APP) person detection without video catupture. Without success.
So my next idea was so delete "old" events/video via this api like in the app... but found nothing
Any hint ?
Thank you

@guny74

first I tried to activate (via api and APP) person detection without video catupture. Without success.

What did you try?

So my next idea was so delete "old" events/video via this api like in the app... but found nothing
Any hint ?

This functionality has not yet been implemented. Thus, it is not possible today.

I want to get the event "person detected" to my smarhome system  (Node red <-->eufy-security-ws) the hole day and  decide there based on the "alarm level". So I want to protocol if persons are detected, e.g. to switch light on (not for other motions) or something else.... but I want not to span the "event log in the app" or the video storage.

but I want not to span the "event log in the app" or the video storage.

This functionality has not yet been implemented. Thus, it is not possible today.

Ok, Thank you for the response


[23.05] dotnet-sdk: 6.0.410 -> 6.0.411, dotnet-sdk_7: 7.0.304 -> 7.0.305

Description of changes
Backport of https://github.com/NixOS/nixpkgs/pull/239426

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

27 packages failed to build:

BeatSaberModManager
alttpr-opentracker
audiobookshelf
boogie
btcpayserver
btcpayserver-altcoins
dafny
depotdownloader
discordchatexporter-cli
eventstore
formula
galaxy-buds-client
inklecate
jackett
jellyfin
kavita
marksman
msbuild
nbxplorer
omnisharp-roslyn
opentabletdriver
osu-lazer
ps3-disc-dumper
roslyn
scarab
tone
xivlauncher

26 packages built:

ArchiSteamFarm
azure-functions-core-tools
commitizen
commitizen.dist
denaro
dotnet-aspnetcore
dotnet-aspnetcore_7
dotnet-runtime
dotnet-runtime_7
dotnet-sdk
dotnet-sdk_7
jetbrains.rider
lidarr
netcoredbg
nuget-to-nix
pinta
pre-commit
pre-commit.dist
prowlarr
radarr
readarr
ryujinx
slskd
space-station-14-launcher
wasabibackend
wasabiwallet


Change uses of .k8s.io to .kudo.dev

The .k8s.io suffix is reserved for use by the Kubernetes project. Please change your API groups, labels, and annotations to use a domain that you own, such as .kudo.dev.
Work is underway to prevent accidental misuse in the apiserver:
https://github.com/kubernetes/enhancements/pull/1111
We are also adding more easily discoverable documentation regarding this.
Thanks.

Thanks @bgrant0607! These CRDs are out of date anyway and should be pointed at kudo.dev anyway.


[Bugfix] Third Party Css files needs updated font name

src/assets/theme/index.ts

Yeah I believe I got that one too?

src/assets/theme/index.ts

Yeah I believe I got that one too?

Oh yeah duh, idk how i missed that lol


LoveServers order link is wrong

Link is to LET box instead of loveservers order page.

Thanks for the heads up!
Has been fixed with 02c186f


fix: provide correct link for Activation steps

Fixes https://github.com/redkubes/otomi-core/issues/1039
Checklist - Not relevant here

[ ] Architecture Design Records have been added as adr/*.md and appended to list in adr/_index.md, if applicable.
[ ] The values-schema.yaml file and test/** fixtures have been updated to reflect code changes, if applicable.
[ ] The OpenApi Schema from redkubes/otomi-api project is compatible with definitions from values-schema.yaml file, if applicable.
[ ] Helm releases are meeting otomi's baseline security policies, if applicable.
[ ] Helm chart and helmfile changes are tested against upgrade scenario, if applicable.

Thanks for your contribution. I did not see the PR, so I already fixed the link.


edited events redirections to work with quick replies

I edited the reception endpoint: quick replies were processed as a regular message (they have a "message" key in the JSON), but they should be processed as postbacks. I've added some conditions, and if the object received is a quick reply, I've saved it in event["postback"] to have the same events no matter the type of postbacks

Thank you.
👍


Add client certificates option to cargo registries

Problem
Currently when using a private registry, it will pull down the assets via http(s) from a public facing registry, however in the context of a company we don't want such public facing registry to be left unauthentificated.
One way to mitigate the problem is to implement what is call mutual TLS or client certificate. The client come with a certificate which is derived from a CA known to the server and the proxy such as NGINX, Apache, Haproxy or squid will serve either a 403 or the registry.
Proposed Solution
Fortunately for us curl (the backend used by cargo to make its request) already support client ssl certificates. Such certificates are composed of 2(3) parts, a certificate (public key), a private key and optionally a password protecting the private key.
I propose to use the curl::easy::Easy::ssl_cert curl::easy::Easy::ssl_key and curl::easy::Easy::key_password which are well tested methods in curl source code :

https://github.com/curl/curl/blob/master/docs/libcurl/opts/CURLOPT_KEYPASSWD.3
https://github.com/curl/curl/blob/master/docs/libcurl/opts/CURLOPT_SSLKEY.3
https://github.com/curl/curl/blob/master/docs/libcurl/opts/CURLOPT_SSLKEYTYPE.3
https://github.com/curl/curl/blob/master/docs/libcurl/opts/CURLOPT_SSLCERT.3

I would then expose those options inside the [http] section of the $HOME/.cargo/config.toml :
[http]
client-ssl-cert = "/etc/ssl/client.pem"
client-ssl-key = "/etc/ssl/key.pem"
client-ssl-key-password = "<password>"

Here is the PR : https://github.com/rust-lang/cargo/pull/10630
Notes
The certificate public and private key must be accessible by the user, so anyone accessing this user account has access to those information, we can optionally encrypt the private key with a password, this mitigate such broad access however here we would store it as plain text.
The password will be stored as plain text, the issue could be that it can then be read by anyone, but let me remind you that the registry token is also stored as plain text inside credentials.toml in the .cargo home directory.
We can not securely store it as asking it each time that you make a request to the registry would be counter productive for the user. In my threat model I assumed that the user would have the specific config with the plain password only in its home directory and that the home security would be assumed by the user.
Testing such real world scenario would need a mocking framework for a server with a client certificate authentication, however as these options are well tested in libcurl, I don't see the point of testing such feature. A regression in such area would likely mean also that all TLS exchange are broken as well.
In the PR, I set the key type to PEM, however it's already the default : https://github.com/curl/curl/blob/master/docs/libcurl/opts/CURLOPT_SSLKEYTYPE.3#L44 , I made this change so its explicit and fixed from an usage perspective. We could also provide the option to support DER format but since changing from DER to PEM is a one liner, having it as a constant would help to fix it once and for all.

How does this proposal interact with the two excepted RFCs (RFC 3139 and RFC 3231) related to securing registries?
Why is secret material stored in config.toml and not in credentials.toml?
Similarly, how will this integrate with credential-process RFC 2730?

I made an issue explaining the design decisions, but to be honest the password one is impossible to solve without building a proper password manager in cargo.

You are not the first to use this language, in what way is credential-process not an interface for a "proper password manager"? What is improper about that design? It is unstable because we are not yet happy with the design. Genuinely, how do we make it a better design?

You are not the first to use this language, in what way is credential-process not an interface for a "proper password manager"? What is improper about that design? It is unstable because we are not yet happy with the design. Genuinely, how do we make it a better design?

Some organizations are not using passwords and rely mainly on client certificates for authentication. Because mTLS is not supported in Cargo we are unable to deploy our internal crate registry (or rather reuse the existing artifact repository).


Speed of FFMLP

Hi, thanks for your valuable work!
~When I updated my code to the newest version, I found that FFMLP does not work anymore. Specifically, the program stuck when I specify -ff parameters. Here is the error when I use ctrl c to cancel the program:~
Traceback (most recent call last):
  File "/data/jianglong/deploy/nerf/torch-ngp/main_nerf.py", line 63, in <module>
    from nerf.network_ff import NeRFNetwork
  File "/data/jianglong/deploy/nerf/torch-ngp/nerf/network_ff.py", line 7, in <module>
    from ffmlp import FFMLP
  File "/data/jianglong/deploy/nerf/torch-ngp/ffmlp/__init__.py", line 1, in <module>
    from .ffmlp import FFMLP
  File "/data/jianglong/deploy/nerf/torch-ngp/ffmlp/ffmlp.py", line 10, in <module>
    from .backend import _backend
  File "/data/jianglong/deploy/nerf/torch-ngp/ffmlp/backend.py", line 33, in <module>
    _backend = load(name='_ffmlp',
  File "/data/jianglong/miniconda3/envs/nerf_torch/lib/python3.9/site-packages/torch/utils/cpp_extension.py", line 1124, in load
    return _jit_compile(
  File "/data/jianglong/miniconda3/envs/nerf_torch/lib/python3.9/site-packages/torch/utils/cpp_extension.py", line 1337, in _jit_compile
    _write_ninja_file_and_build_library(
  File "/data/jianglong/miniconda3/envs/nerf_torch/lib/python3.9/site-packages/torch/utils/cpp_extension.py", line 1449, in _write_ninja_file_and_build_library
    _run_ninja_build(
  File "/data/jianglong/miniconda3/envs/nerf_torch/lib/python3.9/site-packages/torch/utils/cpp_extension.py", line 1717, in _run_ninja_build
    subprocess.run(
  File "/data/jianglong/miniconda3/envs/nerf_torch/lib/python3.9/subprocess.py", line 507, in run
    stdout, stderr = process.communicate(input, timeout=timeout)
  File "/data/jianglong/miniconda3/envs/nerf_torch/lib/python3.9/subprocess.py", line 1121, in communicate
    stdout = self.stdout.read()
KeyboardInterrupt

~The ffmlp works when I use old version code (maybe 20 days ago).~ My platform is 3090, cuda 11.2, torch 1.10.
~Although I can use tiny-cuda-nn instead, I still want to know is there any change of ffmlp which may cause this issue?~
Thanks again!

Update:
After trying more times, suddenly the ffmlp works again. But the speed (35 iter/s) is much worse than tiny-cuda-nn (75 iter/s), is this expected?

It takes a long time (maybe 1-3 minutes) to compile the extension at first time run.
The speed may depend on your GPU and CUDA environment, you can choose the fastest backbone (--fp16 /  --ff / --tcnn) according to your experiments.

Thanks for your quick response.
It indeed takes a long time (> 10 min) for me to compile. I believe this is platform dependent.
For me, --fp16, --tcnn and --cuda-ray lead to the fastest running speed.
Thanks again. I will close this issue.


net/relayd:  /var/etc/relayd.conf generation error

Issue
I have just recently built relayd on another instance of OPNsense 17.7.8 and have noticed that the relayd configuration file  /var/etc/relayd.conf was incorrectly generated which prevents relayd from starting.
Replicating

Install relayd plugin version 1.1_1
Install new patch opnsense-patch -c plugins cfda7cd
Configure pool entry with

Name: SMTP
Mode: Manual Failover
Port: 25
Monitor: SMTP
Server IP Address: <IP_ADDRESS>

Configure Virtual Server entry with

Name: SMTP
IP Address: <IP_ADDRESS>
Port: 25
Mode: Relay

relayd fails to start
/var/etc/relayd.conf looks like:

log updates
timeout 1000
table <SMTP> {
        <IP_ADDRESS>
}
protocol "tcp" {
        tcp { nodelay, socket buffer 65536 }
}

relay "SMTP" {
  listen on <IP_ADDRESS> port 25
  protocol "tcp"
  forward to <> port
}

Change Virtual Server mode from Relay to Redirect
/var/etc/relayd.conf looks like:

log updates
timeout 1000
table <SMTP> {
        <IP_ADDRESS>
}
redirect "SMTP" {
  listen on <IP_ADDRESS> port 25
  forward to <SMTP> port 25 check send "" expect "220 *"
}

Change Virtual Server mode from Redirect back to Relay
Relayd STARTS
/var/etc/relayd.conf looks like:

log updates
timeout 1000
table <SMTP> {
        <IP_ADDRESS>
}
protocol "tcp" {
        tcp { nodelay, socket buffer 65536 }
}

relay "SMTP" {
  listen on <IP_ADDRESS> port 25
  protocol "tcp"
  forward to <SMTP> port 25  check send "" expect "220 *"
}

It's true that relayd fails to start in step 5, but it also prompts to apply the configuration after which it seemed to work without doing 7 and 9 ?
BTW, why are you not using the better maintained HAProxy plugin? :)
Cheers,
Franco

Hmm, I could not get it to work after applying the configuration, I applied when prompted so maybe that caused the issue?  I will need to check my own steps to replicate.
This is not the first time I have seen this problem, I saw it on my other test box where I found the first problem.
I actually started to use relayd for three reasons:

I noticed you were the plugin maintainer so I thought that it would be rock solid;
I only need it to relay SMTP; and
I liked relayd's project goals (mainly "lean" "clean" and "secure")

I can change to HAProxy if recommended.

Sorry when I mean "caused the issue", should I make all the config changes and then apply the configuration rather than apply them every time prompted?

It looks like it did not save correctly for another reason in the form, maybe the configuration wasn't written correctly, but that seems to be a problem of the GUI page, not a problem of the code writing the config file with invalid data. That would explain why I did not see it and saving again from your end helped as well. But what triggered the faulty save in the form is not clear?
I only maintain this because it used to be core functionality and we wanted to remove it there but still keep it around for users. There are no plans to modernise the code or add new features, but all bug reports are still welcome.
I agree on the lean, clean and secure front. It's perfectly viable for use, just want to note that this plugin is not something that will make huge leaps forward anymore without a maintainer who uses it in real world deployments.
For anyone reading this now or in the future: If anybody wants the job, just let me know. :)
Cheers,
Franco

Sorry when I mean "caused the issue", should I make all the config changes and then apply the configuration rather than apply them every time prompted?

It doesn't matter. It probably saves a bit of time to not hit apply until all is done, but that's it. :)

Thanks for the tips.
I think I will stick with relayd as it fits my requirements as HAProxy is way overkill when I just tested it out.
I might have to fire up a few VMs and test a bit more as this was the second time I saw this and the resolution I performed was the same.

@shezzski when you hit this issue, please go to System: Configuration: History and try to diff the last changes made in the virtual server page. It will give hints as to if the settings were written correctly to the config.xml prior to reload.

@shezzski
I have heard that someone is going to rewrite relayd in MVC in 2018, which would make this issue obsolete.
Did this happen again? Should we close?

For reference: #451


Practice: IPMs

@BrianMMcClain ready to go

OOps hit the wrong button... feel free to review @BrianMMcClain


OT API Target endpoint is returning wrong ChEMBL_id

@ckongEbi commented on Thu May 03 2018
This drug LUMILIXIMAB http://www.targetvalidation.org/summary?drug=CHEMBL2109151 , the target associated is FCER2.
But if we looked at the API http://api.opentargets.io/v3/platform/private/target/ENSG00000104921 the synonyms is fine but the id (CHEMBL_2940) is wrong.

If we looked at the the ChEMBL endpoint it returns

It looks like the target_chembl_id is used instead of the molecule_chembl_id in our data_pipeline ChEMBL plugin https://github.com/opentargets/data_pipeline/blob/master/mrtarget/plugins/gene/chembl.py
@gkos-bio any immediate thoughts?
Cc: @iandunham @mkarmona @elipapa

@ElaineMcA commented on Tue Aug 28 2018
@MichaelaEBI : Could you please confirm which Chembl ID should ultimately be used here so we can action accordingly?

I think this was confusion between parent molecules and child molecules. We've decided to use parent ids, which is what the API is correctly returning. Therefore, this is a non-issue and I'm closing it.


Wet bulb temperature integral

#195
Testing:

[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

I am happy with these latest changes, although I haven't actually tried running the tests.


support minikube with --vm-driver=none

Currently, if you start minikube with --vm-driver=none, Tilt does not work properly.
Seems to be some problem with how it's using minikube docker-env, needs investigation
Reported by Jonas in the k8s.slack.io #tilt channel

Just to shed some more light here:
When running tilt doctor, this is the output with a vm-driver=none cluster:
➜ tilt doctor
Tilt: v0.8.9, built 2019-06-07
System: linux-amd64
---
Docker
- Host: Error: ProvideDockerEnv: Could not read docker env from minikube.
Did you forget to run `minikube start`?
X The docker host is currently not running

- Version: Error: ProvideDockerEnv: Could not read docker env from minikube.
Did you forget to run `minikube start`?
X The docker host is currently not running

- Builder: Error: ProvideDockerEnv: Could not read docker env from minikube.
Did you forget to run `minikube start`?
X The docker host is currently not running

---
Kubernetes
- Env: minikube
- Context: minikube
- Cluster Name: minikube
- Namespace: default
- Container Runtime: docker
- Version: v1.14.2
---
Thanks for seeing the Tilt Doctor!
Please send this info along when filing bug reports. 💗

Two problems have to be solved:

With vmdriver=none, minikube has to be started with elevated rights sudo. Thus, running just minikube docker-env will not find the running cluster. I'm not entirely sure how we could solve this one...
sudo minikube docker-env reports 'none' driver does not support 'minikube docker-env' command. In this case, tilt should fall back to the hosts docker installation IMO?

a simple thing to do might be to check if the machine id in kubectl get nodes -o json matches the current machine id. And if that's true, we skip the minikube docker-env call because we know it has to be the current env.

If someone wants to contribute a PR for this, we'd accept it.
I'm concerned that --vm-driver=none is designed for the case "I built my own VM", NOT "I want to do local k8s development without a VM". And that the minikube team may make changes that break the second case. See:
https://github.com/kubernetes/minikube/blob/master/docs/vmdriver-none.md#can-the-none-driver-be-used-outside-of-a-vm
I wonder if we should be endorsing microk8s more strongly for the second case in the Tilt documentation

In the meantime.... Is there any way around this issue? I'm having difficulty on my development hardware getting Minikube with either KVM or VirtualBox to perform well enough to get anything done. And since Microk8s dropped Docker, Argo doesn't seem to work well with it anymore. So at this point, it really seems like developing using Minikube without a VM is the best setup for me.
Thanks.

Yea I got around it using a custom_build script, basically this:
custom_build('api',
  'docker build -t $EXPECTED_REF backend -f backend/dev.Dockerfile',
  ['backend'],
  ignore=[
    './backend/deps', './backend/_build', './backend/.git'
  ],
  disable_push=True,
  live_update=[
    fall_back_on(['./backend/mix.exs', './backend/mix.lock', './backend/config/']),
    sync('./backend', '/code')
  ]
)

Small hint regarding dev setup, I'm currently running a very good setup with k3d/k3s. Runs in docker, no vm required, persistency supported and low memory/cpu footprint. Have a look if you're not statisfied with minikube.

How do I rename it?   Sorry, still relatively new to  the Kubernetes world.

How do I rename it? Sorry, still relatively new to the Kubernetes world.

Open your ~/.kube/config file and rename the respective keys of context, cluster and current-context.


Add Video Doc

Added the video documentation #360

Hi @HimanshuNarware Please review the PR

Hi @HimanshuNarware Please assign me the require level


Data assets feature

Problems:

Flutter has an assets system, Dart does not. This is problematic when wanting to access bytes at runtime in a platform independent way.
Various types of assets could benefit from minifying and/or tree-shaking. For example a translation package might only want include translations in a translations.json asset with keys that are actually reachable from Dart code after Dart AOT optimizations.

High level outline:

Bring AssetBundle to dart:
Make build.dart (from https://github.com/dart-lang/sdk/issues/50565) be able to output data assets besides code assets.
Introduce a link.dart that runs after dart AOT compilation that can do minifying and tree-shaking for data assets.

More details to follow. Filing an issue so we have somewhere to point to.

If we introduce something to support a featuire like AssetBundle, we should consider doing something fairly simple and low-level, that a more complicated class like AssetBundle can be designed on top of.
We used to have Resource, which was removed because it didn't work with AoT compilation. It was a way to access files through package: URIs, which only makes sense when running in the same environment as compilation.
We'll need some abstraction between (location of) the raw bytes and the runtime system, which allows for including the resources in the deployment unit, and which can be tree-shaken to avoid including unnecessary resources.
If it's something that independent packages can use to get their own resources included in programs that use the package, then there also needs to be some kind of name-spacing — which is where using package: URIs worked so well, it clearly assigns a unique prefix to any resource introduced by a package.

@lrhn : Yes, the idea is to introduce an interface which other frameworks can implement themselves, such as the already existing implementation from Flutter. The implementation to allow dart build to ship assets can be (hopefully) fairly simple.
Regarding the package: URIs, this is also how Flutter does it I believe, at least for images.

That would be SO cool if we could tree-shake assets in flutter (https://github.com/flutter/flutter/issues/64106)
It's probably requires to use a generated id in the code instead of a dynamic string to reference the asset (this is also a win btw).
// Use a generated id to reference assets (cfr Android way)
Image.asset(R.images.my_icon);

// instead of
Image.asset('assets/images/icon.svg');

So what could be a solution?
For example when I compile my project using dart compile exe project.dart and add files that are used in the project these files are not added to the compiled file, it is a problem if I want my executable to work as a service on any computer

My, very simplistic, suggestion would be:
Introduce a Resource super-class:
abstract final class Resource<T> {
  external const Resource(String url);
  Future<T> load();
}

Introduce a set of specialized resource kinds:
/// A resource contanining a sequence of bytes.
abstract final class ByteResource implements Resource<Uint8List> {
  external const factory BytesResource(String url);

  /// The length in bytes of this resource.
  Future<int> get length;

  /// An unmodifiable view of the bytes of the resource.
  Future<Uint8List> load();

  /// An unmodifiable buffer of the bytes of the resource.
  ///
  /// Can then be viewed as any type of typed data, like
  /// ```dart
  /// var doubles = (await res.loadBuffer()).asFloat64List();
  /// ```
  Future<ByteBuffer> loadBuffer();

  /// Read the resource into an existing byte list.
  Future<Uint8List> loadInto(Uint8List target, [int offset = 0]);

  /// Read a range of the resource into an existing byte list.
  Future<Uint8List> loadRangeInto(int start, int end, Uint8List target, [int offset = 0]);
}

/// A resource containing a Dart [String].
abstract final class StringResource implements Resource<String> {
  /// A string resource, loaded from [url] and decoded using [encoding].
  ///
  /// Encoding *must* be one of [utf8], [latin1] or [ascii].
  // (TODO: Add `utf16` decoder, then also allow `utf16`, `utf16.littleEndian` and `utf16.bigEndian`.)
  external const factory StringResource(String url, [Encoding encoding = utf8]);
  /// Length of the string, in UTF-16 code units.
  Future<int> get length;
  /// Load the content of the string.
  Future<String> load();
}

/// A resource containing JSON data.
abstract final class JsonResource implements Resource<Object?> {
  /// The [url] must refer to a file contining JSON source, which must be UTF-8 encoded.
  external const factory JsonResource(String url);

  /// Read the JSON file into an unmodifiable Dart JSON value.
  ///
  /// A JSON value is either a `List` of JSON values, a `Map` from strings to JSON values,
  /// or a simple [String], [num], [bool] or `null` value.
  Future<Object?> load();
}

Then you specify a resource by declaring a constant:
const myStringFromFile = StringResource('package:my_package/src/res/text_file.txt');

It'll be a compile-time error to use the constructor in a non-const way. The constants can be tree-shaken as any other constant.
Whichever constanta are still left after compilation, the files their urls point to are included in the distributable, in a way such that myStringFromFile.load can load it. The compiler and runtime gets to decide how and where. Data can be put into the .data segment of the executable, as unmodifiable, if that helps.
It's up to the runtime to decide whether to cache the file contents on first load or not, or for how long, which format the content is stored in. For example, it can be compressed. JSON can be massively compressed if it has the same structure many times, and since we control the format, we can parse the file as JSON at compile time, store it in a specialized binary format, and read it back from there (possibly even providing a cheap view on top of the compressed structure, instead of building a a structure using normal Dart objects.)
The one thing I'd consider is whether to support synchronous access. I'd probably have separate resource classes like StringSyncResource for that, with a synchronous load method. Then the compiler/linker can decide how that's best implemented. For the web, async resources can be lazy-loaded, while sync resources must be part of the initial deployment.

I think it is the same as Isolate

Data asset as (Pointer<Void>, int lengthInBytes)
@mosuem I believe we should not only have Uint8List as a type, but also (Pointer<Void>, int lengthInBytes). (And Future<Uint8List> and Future<(Pointer<Void>, int)>.
Reasoning: One might want to pass a data asset to native code. And if the Dart type is Uint8List, we can't see that it's an external typed data (and we must assume that it could be in the Dart heap and be moved by GC).
Data asset as File ?
Some C APIs actually want a file path instead of the buffer of bytes. I'm not entirely sure if we are able to support this. We could give a file path if, and only if the embedder actually has the file on disk. If the asset is embedded in something else (a zip file, a data section in assembly, ...) there wont be a file path. So the only thing someone could possibly do is write the file manually to disk with File.writeFromBytes. Also, if we ever get data assets on the web backends, then there is no File type at all.
Of course, having to manually write the file to disk if the embedder already has the file on disk is maybe also undesirable. So maybe we should consider allowing File and Future<File>. And the embedder API should then have DataAsset_fopen and char* DataAsset_file_path. With the latter one returning the symlink resolved absolute path if it exists and otherwise nullptr.
(And then for the web backends we might be interested in somehow exposing a file to C code compiled to WASM via the WASI interface.)
API options
Just to pen down the thoughts about the API @mosuem and I have discussed the last couple of days. We have two options:
class AssetBundle {
  external Uint8List loadBytesSync(assetId);

  external Future<Uint8List> loadBytes(assetId);

  external (Pointer<Void>, int) loadBytesAsPointerSync(assetId);

  external Future<(Pointer<Void>, int)> loadBytesAsPointer(assetId);

  external bool availableAsFile(assetId);

  // No need for a sync and async variant.
  // Non-null if `availableAsFile` returns true.
  external File? asFile(assetId);
}

pro: discoverability (auto complete on methods)
pro: enables dynamic assetIds (the link hook writer has to make sure that these assets are bundled)
con: not aligned with @Native external functions/symbols
con: File in the API makes it incompatible with non-VM

@Data(assetId)
external UInt8List loadMyAsset()

@Data(assetId)
external Future<UInt8List> loadMyAsset()

@Data(assetId)
external (Pointer<Void>, int) loadMyAsset()

@Data(assetId)
external Future<(Pointer<Void>, int)> loadMyAsset()

@Data(assetId)
external File? myAsset()

// On the web backends ?
@Data(assetId)
external Blob? myAsset()

pro: aligned with @Native external functions/symbols
pro: does not conflict with data assets on the web.
con: does not enable dynamic asset Ids
con: discoverability

We can have option 3, which patches up requirement for having dynamic assets by making assetId optional in the @Data annotation, and allowing an argument on the definition:
@Data()
external UInt8List loadMyAsset(String assetId)

@Data()
external File? myAsset(String assetId)

// ...

pro: aligned with @Native external functions/symbols
pro: does not conflict with data assets on the web.
pro: enables dynamic asset Ids
con: discoverability

con: File in the API makes it incompatible with non-VM

That could be helped by having different AssetBundles with different APIs
class AssetBundle {
  external Uint8List loadBytesSync(assetId);

  external Future<Uint8List> loadBytes(assetId);
}

class PointerAssetBundle {
  external (Pointer<Void>, int) loadBytesAsPointerSync(assetId);

  external Future<(Pointer<Void>, int)> loadBytesAsPointer(assetId);
}

class FileAssetBundle {
  external bool availableAsFile(assetId);

  // No need for a sync and async variant.
  // Non-null if `availableAsFile` returns true.
  external File? asFile(assetId);
}

Another possible API is:
abstract interface class Asset {
  const Asset(String key) = _SystemAsset;
  Future<ByteBuffer> loadBytes({bool readOnly = true});
}

Then you need to invoke the Asset constructor to have an asset, and const invocations are easily found.
But that's not much different from just a top-level external ByteBuffer loadAssetBytes(String key, {bool readOnly = true});
The loadBytes -> ByteBuffer is the only operation we need, assuming all assets are byte sequences.
However, consider if assets could be typed:

a "byte asset" is a (well-aligned) chunk of memory, but
a "string asset" is something the system can load as a string, without you needing to know how it's stored, that's between the linker and the runtime system doing what's most efficient. (Fx, store as UTF-16, load by creating external string backed by loaded bytes.)

Then we will need a load-function per asset kind.
I'm a little worried that the keys are just strings, but I guess the linker will complain if two assets have the same name, and any statically detectable asset access can be checked against available assets at compile-time.

I'm a little worried that the keys are just strings, but I guess the linker will complain if two assets have the same name, and any statically detectable asset access can be checked against available assets at compile-time.

I would also like typed keys, something like an enum, but this would require codegen when adding an asset to be able to use it in the application. Having typed keys with a const constructor would help in finding usages of asset loading for tracking in resources.json... :)

I'm a little worried that the keys are just strings,

The are namespaces per package package:my_package/foo.txt.

any statically detectable asset access can be checked against available assets at compile-time.

That is a good idea, we should do that once we have the resources.json integration.

namespaces per package

Is that optional, or does the framework providing the assets enforce that the string has that form?
If the latter, can you compile a file with assets, if that file doesn't have a package:URI, or is not in a package directory?
(Still means that someone can access an asset of another package if they know the name. Probably no way to avoid that without some trickery.)

Still means that someone can access an asset of another package if they know the name.

That is a feature for native code assets. We want to avoid bundling two identical dynamic libraries. Also for native code, if static linking is used, all code lives in the same namespace. So trying to create encapsulation would start to create weird behavior when a different linking mode is used.
I am not entirely sure if we should have the same goal with data assets or not.
Maybe we should consider making an asset with id package:my_package/foo.txt accessible from all code, but an asset with id package:my_package:_foo.txt only accessible from Dart code in package:my_package.

Is that optional, or does the framework providing the assets enforce that the string has that form?

Declaring assets in build and link hooks does enforce this. The usage from Dart does not (yet).

only accessible from Dart code in package:my_package

That would require a loadBytes(String key) to check where it's called from. Let's just not do that.
(I'd argue that it's not enough to check the top of the stack, you'd have to check the entire stack to see if the call was initiated by code from that package, otherwise you cant use helper libraries. And that's assuming you can even say which package code comes from after compiling.)
Giving a warning for a constant key string is fine. Trying to enforce runtime security is not worth it.


fix broken through_association from addition of build_record method in rails

fixes #53
@rafaelfranca I noticed when I first commented on #53 that I was running from rails 4.2.0.beta2 locally and that was why there was 119 failures. I updated to Rails 4.2.0 and all tests were passing. I then set my Gemfile to Rails 4-2-stable and saw the test_has_many_through_build_with_attr_accessible_attributes fail with the same error as @dandlezzz:
ArgumentError (wrong number of arguments (2 for 1))
I looked back at Rails 3.2 to see how the ThroughAssociation was handling build_record and saw that it was just using the base Association class implementation so I copied that over into a monkey patch for ThroughAssociation. This fixes the failure and all tests now pass again. Let me know if this is good for you, happy to make updates.

@jGRUBBS thanks, I will test it out.

@rafaelfranca what do you think about this? Also, when do you think a Rails 4.2 compatible release can be made? Especially, considering 1.0.8 definitely breaks with Rails 4.2.

@jGRUBBS  The tests in protected_attributes itself pass without this patch. Perhaps you should add a test that breaks without this PR?

@mcfiredrill this breaks using the 4.2 Gemfile. To see it fail run this:
BUNDLE_GEMFILE=gemfiles/Gemfile-rails-4.2 bundle
BUNDLE_GEMFILE=gemfiles/Gemfile-rails-4.2 rake

You should get something like this:
Finished in 2.510086s, 69.7187 runs/s, 248.9955 assertions/s.

  1) Error:
MassAssignmentSecurityHasManyRelationsTest#test_has_many_through_build_with_attr_accessible_attributes:
ArgumentError: wrong number of arguments (2 for 1)
    /Users/justin/.rvm/gems/ruby-2.0.0-p247/bundler/gems/rails-62e9e61f2d1b/activerecord/lib/active_record/associations/through_association.rb:95:in `build_record'
    /Users/justin/Sites/PA/lib/active_record/mass_assignment_security/associations.rb:72:in `build_record'
    /Users/justin/Sites/PA/lib/active_record/mass_assignment_security/associations.rb:19:in `build'
    /Users/justin/Sites/PA/lib/active_record/mass_assignment_security/associations.rb:55:in `build'
    /Users/justin/Sites/PA/test/attribute_sanitization_test.rb:687:in `test_has_many_through_build_with_attr_accessible_attributes'

175 runs, 625 assertions, 0 failures, 1 errors, 0 skips

To clarify this will be an issue whenever Rails 4.2.1 is released.

Ah ok got it, assumed the default Gemfile was for 4.2. :+1:

@rafaelfranca any update on a new release of protected_attributes? I'm especially curious as you announced that rails 4.2.1 will be released march 2nd:
http://weblog.rubyonrails.org/2015/2/25/Rails-4-2-1-rc2-and-4-1-10-rc2-have-been-released/?utm_source=rubyweekly&utm_medium=email

@jGRUBBS thanks for the PR , I decided to merge #64 , as that code is more close to the actual AR-core code.
thanks anyways


[docs/misc] documentation overhaul, config format changes, removing periods from bucket names

to: @chunyong-lin / @Ryxias
cc: @airbnb/streamalert-maintainers
resolves: #1086
Background
On the road up to release of v3, the documentation is wildly out of date and there are other nonsensical issues that need to be addressed.
Changes

Major config formatting changes to remove the usage of the streamalert module from cluster config (for the most part).. because why TF was that a thing in the first place. "Modules" should be optional, with the streamalert module contains the non-optional classifier_config. Thus, classifier_config has been migrated to a top-level config item in the <cluster-name>.json config files.
All buckets previously hard-coded bucket names are now configurable, with the exception of the <prefix>-streamalert-secrets bucket.  Fixed buckets:

terraform-state (small enough to not need backwards compat for, but support still added)
s3-logging
athena-results
streamalerts
streamalert-data

removal of ridiculous prefix formatting trash. The prefix is now stored once and interpolated everywhere it is needed (resolves: #1086)
complete overhaul of documentation, including an entire restructure/format change, along with actual documentation of config settings (particularly related to global config settings)

includes major consistency updates to align with reST suggestions

updating secrets bucket name to remove periods
updating s3-logging bucket name to remove periods
updating athena-results bucket name to remove periods
updating streamalerts bucket name to remove periods
updating terraform-state bucket name to remove periods
updating streamalert-data bucket name to remove periods
fixing misc places that were missed regarding periods in bucket names

Context on S3 Bucket Name Change
While periods (.) are technically allowed in bucket names, they prevent enabling S3 Transfer Acceleration. We do not currently use the acceleration_status setting on our buckets, but we could in the future and should be compliant with this features requirements.
Testing
Updates to all unit tests in response to above changes.

Coverage remained the same at 96.144% when pulling 48468049a19609ba0c3b3c028e45f08ce4f140fb on ryandeivert-fix-bucket-names into 616c8ff4ada443bb4e1e54f28264b30e22f4622a on release-3-0-0.

@chunyong-lin I'm not sure if it helps with firehose tbh - that depends how the firehose logic on the AWS backend is implemented
It's worth noting that this only helps if "virtual style requests" are used. See the section at the bottom of this page.

Transfer Acceleration is only supported on virtual style requests. For more information about virtual style requests, see Making Requests Using the REST API.

The boto3 docs suggest you can set the style to virtual or path, but auto is used (not sure what "auth" really means for us though)

I was also thinking this might speed up athena under the hood, but I can't find anything that confirms that at all (so I'm suspecting it would not).
S3 Transfer Acceleration is also significantly more expensive:

I actually think we should do this. I can't come up with reasons not to. marking ready for review @chunyong-lin

@chunyong-lin I'll be making some config changes to support overriding defaults :)

okay @chunyong-lin / @Ryxias I know this has ballooned a bit, and taken on a completely different form, but this is now ready for official review

@ryandeivert any possibility to prefix commits with the [core] tags etc that are suggested by the CONTRIBUTING File?

These all will get squashed on merge so there’s really no point...

On Feb 14, 2020, at 11:33 PM, jack1902<EMAIL_ADDRESS>wrote:

@ryandeivert any possibility to prefix commits with the [core] tags etc that are suggested by the CONTRIBUTING File?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@jack1902 addressed your comments FYI

@ryandeivert is this good to merge or are there additional bits inbound?


test: add test for dns.rcode v2

Feature #6621
Redmine ticket: https://redmine.openinfosecfoundation.org/issues/6621
Previous PR: https://github.com/OISF/suricata-verify/pull/1563
Suricata PR: https://github.com/OISF/suricata/pull/10097
Output from stdout file:
Notice: suricata: This is Suricata version 8.0.0-dev (8e0535dc2 2023-12-21) running in USER mode [LogVersion:suricata.c:1147]
Warning: threshold-config: Error opening file: "/usr/local/etc/suricata//threshold.config": Permission denied [SCThresholdConfInitContext:util-threshold-config.c:177]
Notice: threads: Threads created -> RX: 1 W: 12 FM: 1 FR: 1   Engine started. [TmThreadWaitOnThreadRunning:tm-threads.c:1891]
Notice: suricata: Signal Received.  Stopping engine. [SuricataMainLoop:suricata.c:2805]
Notice: pcap: read 1 file, 2 packets, 259 bytes [ReceivePcapFileThreadExitStats:source-pcap-file.c:389]

Should add a negation test now that the PR has support for it.

New PR: https://github.com/OISF/suricata-verify/pull/1574


Typescript typings of array elements may be off?

🐛 Bug Report
In Typescript typings, Drafts of arrays seem to refer to original types, not to drafts of elements.
To Reproduce
Install immer. Create a draft of an array, and try to pop an element. The returned type is off.
import * as React from "react";
import produce from "immer";

type undoRedoState<S> = {
  present: S;
  past: S[];
};

export function useUndoRedo<S>(initialState: S) {
  const [state, setState] = React.useState<undoRedoState<S>>(() => ({
    past: [],
    present: initialState
  }));

  return {
    undo: () =>
      setState(
        produce<undoRedoState<S>>(state, draft => {
          const x = draft.past.pop();
          draft.present = x;            <<<<<<< ERROR IS HERE
        })
      )
  };
}

Errors with Type 'S' is not assignable to type 'Draft<S>'.ts(2322)
Expected behavior
Array<S>.pop should return Draft<S>, not S
Link to repro (highly encouraged)
https://codesandbox.io/s/intelligent-nightingale-c2ufc?from-embed
Environment

Immer version: 3.1.2
[ ] Occurs with setUseProxies(true)
[ ] Occurs with setUseProxies(false) (ES5 only)

CodeSandbox currently uses TypeScript 3.3, which is not supported by Immer 3 and up.

castDraft can be used in the future for these kind of issues, from Immer 5.3 and up


How do I deploy a bot use webhook on Heroku?

Hi! You can use Webhook struct which is implemented Poller interface.
Simple example:
package main

import (
	"log"
	"os"

	tb "github.com/tucnak/telebot"
)

func main() {
	var (
		port      = os.Getenv("PORT")
		publicURL = os.Getenv("PUBLIC_URL") // you must add it to your config vars
		token     = os.Getenv("TOKEN")      // you must add it to your config vars
	)

	webhook := &tb.Webhook{
		Listen:   ":" + port,
		Endpoint: &tb.WebhookEndpoint{PublicURL: publicURL},
	}

	pref := tb.Settings{
		Token:  token,
		Poller: webhook,
	}

	b, err := tb.NewBot(pref)
	if err != nil {
		log.Fatalln(err)
	}

	b.Handle("/start", func(m *tb.Message) {
		b.Send(m.Sender, "Hi!")
	})

	b.Start()
}

thank you very much

What about adding this to README?

Hi! You can use Webhook type that is implementing Poller interface.
Simple example:
package main

import (
	"log"
	"os"

	tb "github.com/tucnak/telebot"
)

func main() {
	var (
		port      = os.Getenv("PORT")
		publicURL = os.Getenv("PUBLIC_URL") // you must add it to your config vars
		token     = os.Getenv("TOKEN")      // you must add it to your config vars
	)

	webhook := &tb.Webhook{
		Listen:   ":" + port,
		Endpoint: &tb.WebhookEndpoint{PublicURL: publicURL},
	}

	pref := tb.Settings{
		Token:  token,
		Poller: webhook,
	}

	b, err := tb.NewBot(pref)
	if err != nil {
		log.Fatalln(err)
	}

	b.Handle("/start", func(m *tb.Message) {
		b.Send(m.Sender, "Hi!")
	})

	b.Start()
}

Where can I get heroku port? and public URL is app's url?

Where can I get heroku port? and public URL is app's url?

PORT variable sets by Heroku automatically. PUBLIC_URL is your application's url, for example https://yourbot.herokuapp.com

Where can I get heroku port? and public URL is app's url?

PORT variable sets by Heroku automatically. PUBLIC_URL is your application's url, for example https://yourbot.herokuapp.com

Thank you for response :)

Would be great to put this into README

I would be very happy in contributing to the project, but it seems that the author of repository hadn't any activity on it for a long time. So, there is only one way to make telebot better - fork it and improve the package yourself.


Use complex data type info provided to RetDec

Make it possible for 3rd party applications and other sources (e.g. debug info) to pass information on complex data types (i.e. structures and arrays) to RetDec. And implement and algorithm that uses this info in RetDec - i.e. it sets the types to objects, and it aggregates all operations with individual objects's members to operations on the object with the given complex type.
Write unit and regression tests and link them here.

This issue is being worked on and as I work on this quite chaotically I thought that a list of what needs to be finished to the end and merged (in steps) would help me to concentrate on the goal better:

[ ] Refactorization of bin2llvmir cast utils.
[ ] Refactorization of stack analysis type modifications.
[ ] Refactorization of parameter analysis argument placement.
[ ] Unit and integration tests.
[ ] https://github.com/avast/retdec-r2plugin/issues/9


Almalinux 8.5 images

Almalinux 8.5 is out. When can we expect the newer images?

@navjotjsingh main images are alreay in dockerhub https://hub.docker.com/_/almalinux?tab=tags ready to use.

imm over looked, team is working on it

Today i looked up on the official images and in Azure 8.5 is finaly there.
Get-AzVMImageSku -Location westeurope -PublisherName almalinux -Offer almalinux | Select Skus
Skus
8_4
8_4-gen2
8_5
8_5-gen2
Is there a reason why #14 is still open? for me everything looks good.

Closing. See: https://azuremarketplace.microsoft.com/en-us/marketplace/apps/almalinux.almalinux


Check that input files are OpenAPI 3.0.x

PR summary
The validator does not provide useful output for Swagger 2 or OpenAPI 3.1.x files, so throw an error if an input file is not OpenAPI 3.0.x.
PR Checklist
General checklist
Please make sure that your PR fulfills the following requirements:

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

:tada: This PR is included in version 1.1.2 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.2.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.2.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


[CERT-TEST-FAILURE]-TC-WASHERCTRL-2.2 - Test failed

Feature Area
Area:Dishwashers
Test Case
TC-WASHERCTRL-2.2
Reproduction steps
All-clusters-app has to be enabled with below mentioned commands :

[ ]  spin-speeds

Bug prevalence
Everytime
GitHub hash of the SDK that was being used
d55f68526864b2986404d1da9c2ccd8b64735b6e - master
Platform
raspi
Anything else?
No response

Issue resolved in 55327986b373b50a5aaa030deeaf05d5eef3317e


feat: Added duration filter

Handled in Core by https://github.com/aneoconsulting/ArmoniK.Core/pull/515