Brewfile ordering is non-deterministic

I version control my Brewfile and the non-deterministic ordering makes the diffs a bit noisy. This seems to happen on and off with the<EMAIL_ADDRESS>formula.
I'd expect all the brew "..." entries in the Brewfile to be ordered alphabetically.
For example, some time ago, I upgraded from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>ran brew bundle dump --force, and this was the Brewfile diff:
diff --git a/Brewfile b/Brewfile
index f8cad37..78ed7c8 100644
--- a/Brewfile
+++ b/Brewfile
@@ -3,7 +3,6 @@ tap "homebrew/bundle"
 tap "indirect/tap"
 tap "nrlquaker/createzap"
 tap "oven-sh/bun"
-brew<EMAIL_ADDRESS> brew "asciinema"
 brew "bat"
 brew "croc"
@@ -47,6 +46,7 @@ brew "openssh"
 brew "p7zip"
 brew "pre-commit"
 brew "pv"
+brew<EMAIL_ADDRESS> brew "ripgrep"
 brew "starship"
 brew "unar"

Later on, I installed the whatsapp cask, ran brew bundle dump --force again, and this was the diff:
diff --git a/Brewfile b/Brewfile
index 45bcca5..3a44757 100644
--- a/Brewfile
+++ b/Brewfile
@@ -5,6 +5,7 @@ tap "nrlquaker/createzap"
 tap "oven-sh/bun"
 brew "asciinema"
 brew "bat", args: ["HEAD"]
+brew<EMAIL_ADDRESS> brew "croc"
 brew "ctags"
 brew "curl"
@@ -46,7 +47,6 @@ brew "openssh"
 brew "p7zip"
 brew "pre-commit"
 brew "pv"
-brew<EMAIL_ADDRESS> brew "ripgrep"
 brew "starship"
 brew "unar"
@@ -80,6 +80,7 @@ cask "spotify"
 cask "tetrio"
 cask "transmission"
 cask "visual-studio-code"
+cask "whatsapp"
 cask "zed"
 mas "Command X", id:<PHONE_NUMBER>
 vscode "bmalehorn.vscode-fish"

It's not non-deterministic. In this case it will be because croc or or similar gained a<EMAIL_ADDRESS>dependency which means it had to be installed before.

Okay, that kind of makes sense, but I'm still confused. My Brewfile only lists the leaves and not their dependencies. So let's assume that<EMAIL_ADDRESS>is a dependency for an earlier formula -- why does that have to impact the order?

@injust because otherwise it will be installed when written and, if it fails, it will be confusing as to why it was installed in between bat and croc and not in between pv and ripgrep.

Fair enough.

It's not non-deterministic. In this case it will be because croc or or similar gained a<EMAIL_ADDRESS>dependency which means it had to be installed before.

Is this direct dependencies only, or does it include transitive dependencies too?
If I try brew uninstall<EMAIL_ADDRESS>it errors and tells me that it's a dependency of glib (not in the Brewfile because it's a dependency) and yt-dlp. yt-dlp is down near the bottom of the list.
Also, croc doesn't have any non-build dependencies. So I still don't see why it<EMAIL_ADDRESS>got moved to that line in the Brewfile specifically.

Is this direct dependencies only, or does it include transitive dependencies too?

It includes recursive dependencies.

So I still don't see why<EMAIL_ADDRESS>got moved to that line in the Brewfile specifically.

You can step through the code if you want to figure it out, it's all open source.

Turns out (in my case) this was caused by the dependency chain: ffmpeg -> cairo -> glib -><EMAIL_ADDRESS>glib recently updated its dependencies from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>That moved<EMAIL_ADDRESS>"above" the (invisible) cairo entry in the Brewfile, hence its position between bat and croc.

because otherwise it will be installed when written and, if it fails, it will be confusing as to why it was installed in between bat and croc and not in between pv and ripgrep.

In this case, it feels like the toposort causes more confusion (but I haven't thought about cases where it would help).

In this case, it feels like the toposort causes more confusion (but I haven't thought about cases where it would help).

I have thought about cases where it would help which is why we have it. It causes less confusion (and I can state this as I've read every issue and comment ever made on this repository).


Changing effect Brightness Tapo L920

Brightness change of a single colour is working, favourite colours is working & colour wheel select is working, brightness change is working for these. Still has the issue of selecting an effect, appears to be every effect, jumping to full brightness when selected & when you adjust the brightness for the effect it jumps back to the last full colour at the brightness that was selected.
Brightness can be changed in the app for an effect but does not update in home assistant, if a solid colour is selected via the app or home assistant both are updated and show the correct info.
Firmware: 1.0.9 Build 220422 Rel.150004
Hardware: 1.0
With v2.3.1 Release

Fixed in 2.5.0


vibration of hmd at 'test tracking',  what happen?

To link with ps move controller 1 & phone 1 (using vridge & riftcat , ps move controller 3, ps3 camera 3, phone 1)
when I run freepie.exe with freepie example script.py default setting , (phone & ps move controller attached to a headset) two units don't be connected together.
For this reason, I found out this contents as below and then maked it translate [0] to [2].

If tracking single controller:
freePieIO[1].x/y/z = Accelerometer data
freePieIO[1].pitch/roll/yaw = Gyroscope data
freePieIO[2].x/y/z = Magnetometer data
Based on vridge tracking mode setting : use magnetometer stability ,I translated this sentences as below

def update():
#Right now, you can only use one axis at a time.
freeTrack.pitch = 0 #freePieIO[0].pitch
freeTrack.roll = 0 #freePieIO[0].roll
freeTrack.yaw = freePieIO[0].yaw
#Multiply by 10 for SteamVR use
freeTrack.x = (freePieIO[0].x * 10) ----------------------------->[0] to [2]
freeTrack.y = (freePieIO[0].y * 10) ----------------------------->[0] to [2]
freeTrack.z = (freePieIO[0].z * 10) ----------------------------->[0] to [2]
if starting:
freePieIO[0].update += update
In this case, this work make it possible to proceed positional x,y,z movement of right and left nearly & up and down nearly positional tracking.
But it cause terrible vibration of hmd at psmove configtool 'test tracking' setting (steam vr scene similarly).
Please let me know the way to stop this vibration.

This question is probably better asked over here: https://groups.google.com/forum/#!forum/psmoveservice
This issue list is meant specifically for internal problems with PSMoveService and not external plugins like FreePIE. I personally have no experience with the FreePIE plugin so I won't be much help but @zelmon64 or @hawinkse might be able to provide some insight.
If it turns out that the problem with FreePIE is in fact happening due to some internal issue with PSMoveService then we'll open an issue here.


Android Studio Arctic Fox | 2020.3.1 Canary 7

Updates

Android Studio Arctic Fox | 2020.3.1 Canary 7
Readme update

Please don't merge those yet, Canary 8 was just released today.


chore(logger): Update error message when we dont find any log messages

Fixes #42 (incidentally)

Heres what it looks like -
╰─± deis logs
Error: There are currently no log messages. Please check the following things:
1) Logger and fluentd pods are running.
2) The application is writing logs to the logger component by checking that an entry in the ring buffer was created: kubectl logs <logger pod> --namespace=deis
3) Making sure that the container logs were mounted properly into the fluentd pod: kubectl exec <fluentd pod> --namespace=deis ls /var/log/containers


student.txt

"pull request from forked repository" as per the "add school" application procedure on JetBrains Educate license

@dhanijitu I have to close this request without merging, because you requested to add a non-existent domain to this repository: Host student.ppns.ac not found: 3(NXDOMAIN) Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with the correct information. Thank you for your understanding!

i request add school with my email domain is :
<EMAIL_ADDRESS>(with ".id" in the end)
not just student.ppns.ac


Update documentation website link

I noticed the url for the documentation site in the readme resulted in a 404 not found. This pr should update it with the real url

Oh hi bigtimebuddy.
-- Susan Pedicini
On Wed, Oct 24, 2018 at 1:47 PM Matt Karl<EMAIL_ADDRESS>wrote:

@bigtimebuddy approved this pull request.
Thank you!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pixijs/pixi-animate/pull/83#pullrequestreview-168037097,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AP6rxeI9oFj2VT3opw27g7JX99ZEV0FUks5uoKebgaJpZM4X4XCQ
.


Refactor prefetch method to use async/await

This commit refactors the prefetch method in prefetch-on-demand_controller to use async/await for better error handling. The response from the workbox.messageSW method call is now awaited, and an event is dispatched based on the result, informing whether prefetching was successful or not.
Target branch: 1.2.x
Resolves issue #192

[ ] It is a Bug fix
[x] It is a New feature
[ ] Breaks BC
[ ] Includes Deprecations

Please be aware that Workbox will consistently return 'true', regardless of whether any of the URLs failed.
Essentially, the task is marked as completed, though there's no assurance it's stored in the cache.


fix: support build targets with different name than its path filename

I ran into some errors when upgrading to 4.0.0-beta.0. I was able to
boil it down (I think) to the fact that I have multiple API paths that
have the same entrypath filename (e.g. /api/user/[id].rs and
/api/group/[id].rs). What happens currently is that this runtime
will try to build these binaries by their filename (e.g. _id_), but
this introduces ambiguity because only one of these build targets can
occupy that name.
I feel like I might've missed something, but figured I'd open a PR
anyway, hope you don't mind!

I've been unable to actually test this out so far, and the test case fails (I assume because it pulls the runtime from npm instead of locally?). Any pointers on how to actually test this locally in a vercel project would be appreciated!

hope you don't mind!
Wow didn't expect to receive feedback and even a fix so quickly. Any help is more than welcome!

Any pointers on how to actually test this locally in a vercel project would be appreciated!

Good point. The old tests used builds in vercel.json, however this usage is currently broken in the latest Vercel CLI. I could only get that to work for<EMAIL_ADDRESS>and below, hence I dropped it. I think we'd want to use https://github.com/TooTallNate/vercel-dev-builder to get past the package publishing restrictions. I'll look into migrating to that one instead.
In the long term we want to roll out a solution where handlers will be deployed as one lambda with internal routing, which would get rid of the [[bin]] annotating annoyance. This fix is definitely the way to go for now. Thank you.

Published 4.0.0.beta.1

Published 4.0.0.beta.1

Awesome, thanks for the quick response! https://github.com/mason-org/mason-registry-api/pull/22 happily deployed now :)

Nice! Can we reach out to you regarding feedback on merged handlers?

Nice! Can we reach out to you regarding feedback on merged handlers?

Sure!

Nice! Can we reach out to you regarding feedback on merged handlers?

Sure!

Thoughts on https://github.com/vercel-community/rust/pull/86? This should get rid of https://github.com/mason-org/mason-registry-api/blob/main/Cargo.toml#L25-L115.


How can I increase 75000 hard coded limit?

for example in this file
https://github.com/linvi/tweetinvi/blob/905b1cbc8674b718c3e64cbeb2fc96cc6cb4efbd/Tweetinvi.Controllers/Friendship/FriendshipController.cs
public IEnumerable GetUsersYouRequestedToFollow(int maximumUsersToRetrieve = 75000)

This is not a limit, this is a default value. Also if I remember properly it should be 7500 and not 75000.

@linvi my account has about 77.000 followers and i am able to fetch maximum 75.000 even though i provide higher value
how do you explain?
it fetches exactly 75.000

Hi.
I guess that the problem you are experiencing is due to RateLimits even though I can see in your code that you properly set the RateLimitTrackerMode .
I looked at the code and everything is supposed to work.
I never had an account with more than 75k users to test my code against.
If you can share the credentials temporarily for me to debug the issue I will be happy to do so.
You can contact me privately on gitter : https://gitter.im/linvi/
Cheers,
Linvi

Probably at some point parameter is not passed so default 75.000 is used
After i have increased entire solution all 75.000 to 1.000.000 and recompiled and replaced new DLLs, now it works as supposed to be

Thanks, this will be taken care of as part of release 4.0 or 5.0.

Hi @MonsterMMORPG,
I've opened a PR (#764) with a fix for this. Can you try it out and see if your issue is fixed?
Here's a build:
netstandard1.4.zip

hi it wasnt after all 75000 but the delay issue
so after 75000 (which is - 15*5000) your quote fills
and the application has to wait
i cant remember now where i changed but i have added extra wait to the consquent actions and that problem gone away
so the problem was definitely about waiting
since it doesnt wait properly, it was causing no action quote query and un-caught error

I wrote the following as a quick repro:
ExceptionHandler.SwallowWebExceptions = false;
RateLimit.RateLimitTrackerMode = RateLimitTrackerMode.TrackAndAwait;

IEnumerable<long> followerIds = User.GetFollowerIds("justinbeiber", 100000);
Console.WriteLine("Fetched {0} follower IDs", followerIds.Count());

and I got an exception!
It looks like the problem was that Tweetinvi was waiting the exact number of milliseconds that Twitter told us to wait, but due to timing differences between our machine, the server that served the last response (telling us how long to wait) and the server we send the request to (after waiting), you might end up sending your request marginally too early for Twitter to accept it. To compensate, I've increased the wait time by an extra 5s (I first tried 1s, but still got an error), which should be sufficient to allow for any reasonable timing discrepancy without slowing things down too much :).
You can also override the 5s additional wait time with your own preferred value:
TweetinviConfig.CurrentThreadSettings.RateLimitWaitFudgeMs = 10000;

The PR has been updated, and here's another build:
netstandard1.4.zip
Can you see if this works for you?

@JoshKeegan yep this was the problem i have discovered :)
i have added if i remember correctly 5000 ms dealy and never had problem since then (it has been months)
i can try later your update thank you

Hello there,
This has now been merged into 5.0.
Thanks for all your work and help.
Linvi


chore(deps): upgrade ESLint to v9

Update ESLint before migration to ESM.

Config file is ready to handle JS Modules (if .mjs is used)
Should be merged after https://github.com/absolute-version/commit-and-tag-version/pull/199.

PS: Wasn't sure what to do with error on index.js, so I omitted it

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 92.80%. Comparing base (7ebdacd) to head (f051e79).
Report is 33 commits behind head on master.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #200      +/-   ##
==========================================
- Coverage   94.11%   92.80%   -1.32%
==========================================
  Files          26       29       +3
  Lines         493      542      +49
==========================================
+ Hits          464      503      +39
- Misses         29       39      +10

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


Fix missing annotation in http_uri.proto

The file level equal_all annotation was missing in one of the files and failed to compile in go-control-plane.
https://github.com/envoyproxy/go-control-plane/pull/201
Signed-off-by: Shriram Rajagopalan<EMAIL_ADDRESS>For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md
Description: Fix missing gogo annotation
Risk Level: Low
Testing: Go control plane
Docs Changes: None
Release Notes: None
[Optional Fixes #Issue]
[Optional Deprecated:]

cc @kyessenov / @yangminzhu .. needed to get go-cp to take in the new updated protos without the nullable thing.

I thought you are removing gogoproto annotations, not adding them :P
/lgtm

Yeah but you have to be consistent. equal_all missing in one file triggered compilation errors when nullable was removed. equal_all is a top level annotation, like what we hve for java/etc. Not field level thingy like nullable that pollutes struct types.


Add logos to Supporters page

Add attached logos to Supporters page
Sponsors:
Add sponsor logo & link

link to: http://www.boldisbeautiful.com/us
Add sponsor logo & link

link to: http://www.qualcomm.com
Add sponsor logo & link

link to: http://www.salesforce.com
Add sponsor logo & link

link to: http://www.ge.com/
Add sponsor logo & link

http://bloc.io

@corinnepw how's this?


fix packages installation

Description
This change used the now only method to install go packages using go install
Issues Resolved

https://github.com/sous-chefs/golang/issues/104

Check List

[x] A summary of changes made is included in the CHANGELOG under ## Unreleased
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable.

@visheyra looks like you need to fix the logic so that this works with pre 1.18. Can you do that please?

@visheyra any chance you can fix the logic for the one please?


256k DISK

Adds 256k variant of the DISK to supplement https://github.com/AppliedEnergistics/Applied-Energistics-2/pull/6252. As such, requires that to be accepted and released first as the 256k component is not yet present in the base mod.
Will not go any higher into the millions.

The original author of AE2Things said he doesn't want 256k DISKs, so I'm not going to be adding them to this fork,


short/long photoreceptor outer segment term nomenclature error

MP:0008587 short photoreceptor outer segment
MP:0020812 long photoreceptor outer segment
This refers to a layer of the retina. I've never heard anybody call a layer short or long ("My driveway was covered in a long layer of snow." I don't thinks so...). Shouldn't that be thin or thick?
MP:0008587 thin photoreceptor outer segment
MP:0020812 thick photoreceptor outer segment
All the other instances of short I can find in the ontology make sense (bones, tubes, cilia, cells, etc.). Conversely, other layers in the ontology are called thin (thin dermal layer, thin endoderm, thin external granule cell layer, etc.).
Thanks.
Laurens

Looking at the notes for annotations to MP:0008587 term (95 annotations total)
44 use short*
5 use thick*/thin
20 use length
So I think using short/long makes sense based on the language used by researchers. We should probably add thick and thin synonyms.


Attempt to fix Arm OSX migrator with native build

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

hi Matt, reminder to please see my comments on PR #13 .  Even if you can get the ARM native build compiling I believe there will be issues due to lack of precision (ie, long doubles only have double precision), unless larger changes are made to the tempo2 code.


Beginners guide to APIs in Flutter

Proposed title of the article
Beginners guide to APIs in Flutter
Introduction paragraph (2-3 paragraphs):
Application Programming Interface(API) is a communication portal that allows two or more applications to connect for data sharing. It acts as an intermediary for delivering requests to service providers and returning the responses. Generally, an API enables seamless communication between different platforms by ensuring that data is shared without sharing the entire system codebase.
The use of APIs has been pervasive in the programming world, as most developers use pre-existing scaffoldings. Through APIs, developers can focus on other vital components of their applications instead of writing the entire code from scratch. Programmers can efficiently develop dynamic applications that easily integrate with existing data-sharing systems.
Most applications use APIs to fetch the mobile data from the back end. Flutter provides an efficient way of consuming HTTP resources in mobile applications with the HTTP package. The HTTP package contains classes and function that enables easy consumption of HTTP resources in a web, android or desktop application. In most cases, the HTTP resources returned by the APIs are in Javascript Object Notation (JSON) format, this article will explain how to fetch and consume data in JSON format from an API with an example of the GitHub REST API.
In the implementation, this article will build a mini android application using the folder organization structure explained in flutter-folder-organization article.
Key takeaways:

Understanding the Flutter HTTP package
Converting JSON objects to custom Dart objects using JSON serialization
Using await and async methods
Using the GitHub REST API to fetch a user's repositories and consume the results in a flutter application
5

References:
https://flutter.dev/docs/cookbook/networking/fetch-data
https://flutter.dev/docs/development/data-and-backend/json
https://pub.dev/packages/http
https://docs.github.com/en/rest

@jerimkaura  seems like a great topic - do you have a type of application in mind?
We want to make sure the article goes beyond the basic implementation (or something the reader could find in the docs).
It may be useful to add the type of app in the title.


Update README.md

fixing the navigation for "Secure the Workloads"

Thanks for your contribution @jithinks8


feat(grid): export grid constants

export grid constants to be consumed
fix #149

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Kubefwd stopped working

I have been using kubefwd just find for the last few weeks.  Now all of the sudden when I launch it, the app says its changing the hosts fine then stops the app.  Here is the output from my console.
2019/02/07 11:56:12  _          _           __             _
2019/02/07 11:56:12 | | ___   _| |__   ___ / _|_      ____| |
2019/02/07 11:56:12 | |/ / | | | '_ \ / _ \ |_\ \ /\ / / _  |
2019/02/07 11:56:12 |   <| |_| | |_) |  __/  _|\ V  V / (_| |
2019/02/07 11:56:12 |_|\_\\__,_|_.__/ \___|_|   \_/\_/ \__,_|
2019/02/07 11:56:12
2019/02/07 11:56:12 Version 1.4.10
2019/02/07 11:56:12 https://github.com/txn2/kubefwd
2019/02/07 11:56:12
2019/02/07 11:56:12 Press [Ctrl-C] to stop forwarding.
2019/02/07 11:56:12 'cat /etc/hosts' to see all host entries.
2019/02/07 11:56:12 Loaded hosts file C:\Windows\System32\drivers\etc\hosts
2019/02/07 11:56:12 Hostfile management: Original hosts backup already exists at C:\Windows\System32\drivers\etc\hosts.o
riginal
2019/02/07 11:56:12 Done...```

Any ideas?

That will teach me to not work on things late at night when I forget which cluster context I am currently on.
Maybe a feature request in the output?  Add the current cluster context?

I have similar issue. The below command works but after getting timeout after sometime of idle usage, and when i invoke command again it doesn't work.  i have services in my namespace as against the above issue.
sumanth@projects: sudo kubefwd svc -n my-ns --kubeconfig ~/.kube/config-np -v
INFO[12:39:21]  _          _           __             _
INFO[12:39:21] | | ___   _| |__   ___ / _|_      ____| |
INFO[12:39:21] | |/ / | | | '_ \ / _ \ |_\ \ /\ / / _  |
INFO[12:39:21] |   <| |_| | |_) |  __/  _|\ V  V / (_| |
INFO[12:39:21] |_|\_\\__,_|_.__/ \___|_|   \_/\_/ \__,_|
INFO[12:39:21]
INFO[12:39:21] Version 1.11.1
INFO[12:39:21] https://github.com/txn2/kubefwd
INFO[12:39:21]
INFO[12:39:21] Press [Ctrl-C] to stop forwarding.
INFO[12:39:21] 'cat /etc/hosts' to see all host entries.
INFO[12:39:21] Loaded hosts file /etc/hosts
INFO[12:39:21] Hostfile management: Original hosts backup already exists at /home/sumanth/hosts.original
INFO[12:39:23] Done...
sumanth@projects: k get services -n my-ns
NAME            TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)              AGE
backend         ClusterIP   None            <none>        80/TCP               18d
elasticsearch   ClusterIP   None            <none>        9300/TCP,9200/TCP    18d
kibana          ClusterIP   <IP_ADDRESS>   <none>        5601/TCP,80/TCP      18d
memcached       ClusterIP   None            <none>        11211/TCP            18d
rabbitmq        ClusterIP   None            <none>        15672/TCP,5672/TCP   18d
web             ClusterIP   None            <none>        80/TCP               18d

@sumanthkumarc does this command work?
KUBECONFIG=~/.kube/config-np kubectl port-forward svc/elasticsearch 9200:9200 -n my-ns

When i remove all entries from hosts file and run the command sudo kubefwd svc -n my-ns --kubeconfig ~/.kube/config-np -v and it worked again. FYI, i had the KUBECONFIG var set already.


fix: Changed contentId to content_id for correct type

Fixes
In order for the 'Content-ID' header to be set for the attachment, the parameter 'content_id' has to be set. 'contentId' isn't registered as the header, and the header is not provided in the email. The only workaround is to not use types, which defeats the purpose.
This should fix the type
Checklist

[x] I acknowledge that all my contributions will be made under the project's license
[x] I have made a material change to the repo (functionality, testing, spelling, grammar)
[x] I have read the Contribution Guidelines and my PR follows them
[x] I have titled the PR appropriately
[x] I have updated my branch with the main branch
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added the necessary documentation about the functionality in the appropriate .md file
[ ] I have added inline documentation to the code I modified

If you have questions, please file a support ticket.

Please merge.

omg, really...

if anyone needs a hand...
attachments: <(AttachmentData & { content_id: string })[]>[{
      disposition: 'inline',
      filename: 'image.jpg',
      content: base64Content,
      content_id: "inlineimage",
      type: 'image/jpeg'
}]

Wow I just spent a good chunk of time trying to figure out why SendGrid wasn't setting the Content-ID header. This really should be merged ASAP @twilio-dx

@SendGridDX: can we merge this.  It's insane that the field is misnamed in the official node package.


Allow iteration of Mutec

Need to make it so that we can iterate through the inner values of the Mutec while locking before and unlocking after.

Functionally done with a7f7065


Version 2.3.2 use $l10n For Translation.

Issue description:
I have just download the version 2.3.2 version of kikri. The previous had checkbox unchecked problem. Now check box is working but when I check my theme with theme checker, it gives the old error of $l10n variable for theme translation text.
Version used:
(Did you try using the develop branch from github? There's a chance your issue has already been adressed there)
Yes I use the latest version.
Using theme_mods or options?
theme_mods
Code to reproduce the issue (config + field(s))
RECOMMENDED: Possible variable $l10n found in translation function in class-kirki-controls-repeater-control.php. Translation function calls must NOT contain PHP variables.
thank's :)

👍 fixed in the latest develop branch.

Thank's hero,
one line remaining, :)
class-kirki-controls-repeater-control.php line 411. The Text-domain.

Oops you're right... I missed that one. Fixed now 👍


What is best rule type in my case?

My case :
I have log collect infomation (username, IP, location, device) ..
I want check when user login from new IP -> Alert ; when user login from new device -> Alert; time period is 3 days. (like warning login in facebook).
My question:

What rule should I use?
If i use rule CHANGE. i check data in field change only. If field has new value -> alert ( field {IP} has new IP -> alert. But if i hava two IP - in this case, alert is not good) . But rule CHANGE can be run maximum 10k query only. How can increase ? "use_count_query" dont work in rule CHANGE.

Thanks!
P/s: My EL is not good !

http://elastalert.readthedocs.io/en/latest/ruletypes.html#new-term
type: new_term
fields:
 - [username, IP]
 - [username, device]
terms_window_size:
  days: 3

This is almost exactly what you want. This will alert on a new combination of (username, ip/device). When elastalert starts, it will look for everything from the last 3 days and consider those "known" values. Once a combination causes an alert, it will not alert again, until elastalert restarts.
Alternative, if you really want 3 day realerting.
type: any
query_key: [username, IP, device]
realert:
  days: 3

This will alert on everything first, but then will wait for 3 days before alerting on that (username, ip, device) combination again.

Also, the maximum 10k query_hit_size only apply to a single query (Sorry documentation is not clear about this!). Elastalert will make additional queries to get all documents. You should see
"Queried rule ...: 10,000 / 10,000 hits"
"Queried rule ...: 20,000 / 10,000 hits (scrolling)"
"Queried rule ...: 30,000 / 10,000 hits (scrolling)"

Thank for suggestion.
Here is my config
index: fb-mail*

# (Required, new_term specific)
# Monitor the field ip_address
fields:
 - [user, client_ip]
 - [user, device]

# (Optional, new_term specific)
# This means that we will query 90 days worth of data when ElastAlert starts to find which values of ip_address already exist
# If they existed in the last 90 days, no alerts will be triggered for them when they appear
terms_window_size:
  days: 1

# (Required)
# A list of Elasticsearch filters used for find events
# These filters are joined with AND and nested in a filtered query
# For more info: http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl.html
# We are filtering for only "login_event" type documents with username "admin"
filter:
- term:
    _type: "iis-access"
- and:
    - term:
        user: "test"

And when i run with this rule, i got warning. Is it problem?
WARNING:elastalert:No results were found from all sub-aggregations.  This can either indicate that there is no baseline data OR that a non-primitive field was used in a composite key.

It just means there were no results. For the 1 day, the user "test" did not have any matching documents cotaining client_ip or device. Do you get the same warning if you changed terms_window_size to a higher number?

I got same result when change hanged terms_window_size to a higher number.
I change filter to get all user
filter:
- term:
    _type: "iis-access"

and got same results too.

Hmm.. What version of Elasticsearch are you using? Can you show me the JSON of one these documents with user + device. It's possible there is a bug.


Unreachable OpenRPC rpc.discover method

Description
json-rpc completely prevents the usage of rpc. method namespace, aimed at system extensions, preventing any user or library from implementing said extensions.
https://github.com/pavlov99/json-rpc/blob/00b24a9e811d9ca89ec3b1570195c881687bbef4/jsonrpc/jsonrpc2.py#L74
Nowhere in the JSON-RPC specification it is said that the usage of rpc. methods must be unconditionally forbidden, the restriction is reserved for system extensions, and MUST NOT be used for anything else, so its usage for system extensions is explicitly stated.
Blocking that namespace for system extensions is an explicit violation of the specification, and that fact impacts OpenRPC, which makes uses that namespace for its rpc.discover method (spec specification) (albeit OpenRPC rpc.discover being really a system extension or not is debatable, just like what a system extension itself really means).
Steps to Reproduce

Declare a rpc.discover on a test application testrpc.py (and pip install werkzeug jsonrpc).

import json

from wsgiref.simple_server import make_server

from jsonrpc import JSONRPCResponseManager, dispatcher
from werkzeug.wrappers import Request, Response

@dispatcher.add_method(name='rpc.discover')
def rpc_discover():
    """Get OpenRPC spec."""
    return openrpc

@Request.application
def application(request):
    """Serve the response."""
    response = JSONRPCResponseManager.handle(request.get_data(cache=False, as_text=True), dispatcher)
    return Response(response.json, mimetype='application/json')

openrpc = json.loads('''
{
  "openrpc": "1.2.6",
  "info": {
    "title": "OpenRPC API",
    "version": "0.0.1"
  },
  "methods": [
    {
      "name": "rpc.discover",
      "description": "Returns an OpenRPC schema as a description of this service",
      "result": {
        "name": "OpenRPC Schema",
        "schema": {
          "$ref": "https://raw.githubusercontent.com/open-rpc/meta-schema/master/schema.json"
        }
      }
    }
  ]
}
''')

if __name__ == '__main__':
    with make_server('', 8000, application) as httpd:
        print("Serving HTTP on port 8000...")
        httpd.serve_forever()

Run application:

python testrpc.py

Call endpoint

curl localhost:8000 -d '{"jsonrpc":"2.0","method":"rpc.discover","id":0,"params":{}}'

Expected behavior:
{
  "result": {
    "openrpc": "1.2.6",
    "info": {
      "title": "OpenRPC API",
      "version": "0.0.1"
    },
    "methods": [
      {
        "name": "rpc.discover",
        "description": "Returns an OpenRPC schema as a description of this service",
        "result": {
          "name": "OpenRPC Schema",
          "schema": {
            "$ref": "https://raw.githubusercontent.com/open-rpc/meta-schema/master/schema.json"
          }
        }
      }
    ]
  },
  "id": 0,
  "jsonrpc": "2.0"
}

Actual behavior:
{
  "error": {
    "code": -32600,
    "message": "Invalid Request"
  },
  "id": null,
  "jsonrpc": "2.0"
}

Reproduces how often: happens every time.
Versions
All python versions, json-rpc-1.13.0.

Workaround (overriding method property):
import jsonrpc.jsonrpc2
jsonrpc.jsonrpc2.JSONRPC20Request.method = None


(#66) - add test for $gt:null

Looks broken in both Firefox and Phantom: https://travis-ci.org/nolanlawson/pouchdb-find/builds/84427365

So to be clear, this PR demonstrates the issue but does not fix it. Help wanted! :)

this is actually fixed now, merged: 12ecc0e697d8be57c983c1a63783f7b434010d20


Instructions reference gradlew/mvnw which are not included

The instructions for this guide mention compiling with ./mvnw, but that script is not included.
The thing was not built with spring initializr...

Almost all of the Spring guides include two projects, one in /initial and one in /complete. Each contains a .mvnw and a .gradlew file.


[Bug] Raise error when call tvmc.run whose arg tvmc_package compiled by vm

https://github.com/apache/tvm/blob/36b30974a9e7c5f2244c8fade392af1570db3c1d/python/tvm/driver/tvmc/runner.py#L641
should be:
if not isinstance(exe_outputs, (list, tvm.runtime.container.ADT)):

Here is error detail:
2023-03-21 11:46:37.694 INFO load_module /tmp/tmpws1rwd_s/lib.so
Traceback (most recent call last):
  File "run_pkg_vm.py", line 9, in <module>
    result = tvmc.run(package, device="cuda", repeat=10, number=10, benchmark=True, end_to_end=True, inputs=inputs)
  File "/home/haoke/.local/lib/python3.7/site-packages/tvm/driver/tvmc/runner.py", line 646, in run_module
    outputs[output_name] = val.numpy()
  File "/home/haoke/.local/lib/python3.7/site-packages/tvm/runtime/object.py", line 67, in __getattr__
    raise AttributeError("%s has no attribute %s" % (str(type(self)), name)) from None
AttributeError: <class 'tvm.runtime.container.ADT'> has no attribute numpy

Hello @lxiongh - would you be able to push a PR with that fix?


Kafka ingestion lag spikes up whenever tasks are rolling

Affected Version
0.21
Description
We have a druid cluster in which we are ingesting about 2.5M events/second. We have 90 ingestion tasks for 1 of our data sources with task duration set to 1 hr. Whenever the tasks roll every hour, Kafka ingestion lag spikes up anywhere from 3M to even 15M druid.ingest.kafka.lag. On further analysis, we noted that while tasks are rolling, some of the active ingestion tasks are stuck in pause state for a long time (sometimes up to 1.5-2 minutes) during which those tasks aren't ingesting any data resulting in ingestion lag spike.
Logs from MM tasks with a huge gap between pause and resume
{"@timestamp":"2021-06-21T17:34:51.628Z", "log.level":"DEBUG", "message":"Received pause command, pausing ingestion until resumed.", "service.name":"druid/middleManager","event.dataset":"druid/middleManager.log","process.thread.name":"task-runner-0-priority-0","log.logger":"org.apache.druid.indexing.seekablestream.SeekableStreamIndexTaskRunner"}
{"@timestamp":"2021-06-21T17:36:27.089Z", "log.level":"DEBUG", "message":"Received pause command, pausing ingestion until resumed.", "service.name":"druid/middleManager","event.dataset":"druid/middleManager.log","process.thread.name":"task-runner-0-priority-0","log.logger":"org.apache.druid.indexing.seekablestream.SeekableStreamIndexTaskRunner"}
{"@timestamp":"2021-06-21T17:36:27.097Z", "log.level":"DEBUG", "message":"Received resume command, resuming ingestion.", "service.name":"druid/middleManager","event.dataset":"druid/middleManager.log","process.thread.name":"task-runner-0-priority-0","log.logger":"org.apache.druid.indexing.seekablestream.SeekableStreamIndexTaskRunner"}

In the above loglines, we can see that that task was in pause state from 17:34:51 to 17:36:27.
On further analysis, we figured out that the MM taskRunner goes to a pause state when it is requesting a checkpoint notice here.
From the time the taskRunner submits the checkpoint notice, it actually takes around 1.5 minutes for the coordinator to actually process this checkpoint notice.  We can see it in the coordinator logs below for a specific task.
 Not during other times.
Our guess here is that, while tasks are rolling, the notices queue has a lot of notices in them and each notice takes a long time to be processed thus causing significant delay in the checkpoint notice as well to be processed once its added to the queue.
Currently, we do not have logs in place to figure out how many notices are there in this queue at any point and how long does each notice takes to get executed.
Spent some more time analyzing further and we saw that some of the following functions here are taking multiple seconds when tasks are rolling as opposed to few milliseconds when tasks aren't.
      discoverTasks();

      updateTaskStatus();

      checkTaskDuration();

      checkPendingCompletionTasks();

      checkCurrentTaskState();

Some of the above functions require checking task status and that seems to be taking a long time.

Hi @harinirajendran, thank you for your report. Was it only one task being paused or all tasks for the same datasource? If the first is the case, then maybe your guess is correct that there were lots of notices in the queue. If the second is the case, it means the supervisor was already in processing of the checkpoint notice but hadn't finished it yet. It was probably waiting for all tasks to respond to the pause request or waiting for tasks to respond to the setEndOffset request (see SeekableStreamSupervisor.checkpointTaskGroup(). One of our customers had a similar issue at Imply before and the cause was frequent HTTP communication failures which were retried with backoff.

Hi @harinirajendran, thank you for your report. Was it only one task being paused or all tasks for the same datasource? If it's the first case, then maybe your guess is correct that there were lots of notices in the queue because the task who initiated the checkpoint process pauses itself after it sends the checkpoint request to the supervisor. If it's the second case, it means the supervisor was already in processing of the checkpoint notice but hadn't finished it yet. It was probably waiting for all tasks to respond to the pause request or waiting for tasks to respond to the setEndOffset request (see SeekableStreamSupervisor.checkpointTaskGroup(). One of our customers had a similar issue at Imply before and the cause was frequent HTTP communication failures which were retried with backoff.

@jihoonson : This long pause happens whenever a task requests a checkpoint notice while task roll is happening for the same data source. So it happens with all tasks requesting checkpoint notice while task roll is going on. In our case, the tasks roll happens over a span of 5-6 minutes. Also, this ingestion lag spike consistently only happens around task rolls which makes me think these aren't because of HTTP communication issues.
Also, the timeline is as follows
time t1:                     task x pauses itself and initiates a checkpoint request to the coordinator
time t1:                     coordinator receives the checkpoint notice and adds it to the notices queue
time t1+2 minutes: coordinator sends a pause to the task
time t1+2 minutes: coordinator gets response to pause and then calls setEndOffset(which in turn resumes the task)
So the coordinator processes the checkpoint notice and sends a pause only after about 2 minutes.
 Are any logs omitted between the second and the third lines (checkpointing and pause)? Or Is there no log between those two? If there is no log between them, it seems a bit strange to me because I think the overlord usually prints something unless it is stuck especially when you have debug logging enabled. If the overlord was processing other notices for 2 min before it sent pause requests, it would likely print something in the logs.

@harinirajendran interesting. Are any logs omitted between the second and the third lines (checkpointing and pause)? Or Is there no log between those two? If there is no log between them, it seems a bit strange to me because I think the overlord usually prints something unless it is stuck especially when you have debug logging enabled. If the overlord was processing other notices for 2 min before it sent pause requests, it would likely print something in the logs.

@jihoonson oh yeah. there are lots of log lines between the 2 timestamps. The coordinator continues to process other notices and spews out lots of logs. Here, I explicitly filtered out the log lines for this specific task which was paused for about 2 minutes.

I see. Thank you for confirming it. Your analysis seems correct to me. Now I'm curious what notices the supervisor was processing :slightly_smiling_face:

I see. Thank you for confirming it. Your analysis seems correct to me. Now I'm curious what notices the supervisor was processing 🙂

I am working on a couple small PRs to add more visibility into this. hopefully that helps us get to the bottom of this 🤞
https://github.com/apache/druid/pull/11415

We have a similar problem in our cluster. There's a topic with 12 partitions, and its peak incoming message rate is up to 120K/s. Once it reaches the peak message rate, Druid ingestion tasks seems stuck temporarily. I have not investigated the problem if it's related to this issue, but leave a comment here so that I could find this issue once I needed it.

@harinirajendran I recommend you experiment running the overlord with these three PRs pulled to your code: #12096 #12097 #12099, and let us know how it goes.
I reviewed your analysis, and some of the code, and took a profile on our cluster here.
You are correct that during task rollover the overlord gets busy processing RunNotice notices. I can identify two codepaths where RunNotice hits the TaskQueue (in purple):
On our system, with above fixes, TaskQueue is only a fraction of the time

SeekableStreamSupervisor.RunNotice::handle -> SeekableStreamSupervisor::runInternal -> SeekableStreamSupervisor::createNewTasks -> SeekableStreamSupervisor::createTasksForGroup -> TaskQueue::add
SeekableStreamSupervisor.RunNotice::handle -> SeekableStreamSupervisor::runInternal -> SeekableStreamSupervisor::checkPendingCompletionTasks -> SeekableStreamSupervisor::killTasksInGroup -> SeekableStreamSupervisor::killTask -> TaskQueue::shutdown

Both of these paths hit the lock in TaskQueue; the fixes I present above have improved scalability of TaskQueue on our system.
It might also help if you can share which metadata task storage engine you are using (SQL vs heap).

I see. Thank you for confirming it. Your analysis seems correct to me. Now I'm curious what notices the supervisor was processing 🙂

@jihoonson @jasonk000 : I have some more updates wrt this issue. The supervisor actually is spending a lot of time in processing runNotices which is causing the checkpointNotice to wait in notices queue for a long time causing tasks to be stuck which results in ingestion lag. In our case
In our case, we have seen run notices take ~7s as shown in the graph below.

As a result of this, the notices queue gets backed up when the number of tasks are huge resulting in more runNotices every hour.

On further analysis, we realized that the bulk of 7s in run_notice processing is being spent in the getAsyncStatus() call in discoverTasks function. When the task boots up, it roughly takes ~5s to start the JVM and start the HTTP server. So, as a result this Futures take about ~6s to get the status of tasks that are just bootstrapping with retries resulting in runNotice taking such a long time.
So, it's the tasks bootstrap time and hence its inability to respond to /status call from the supervisor that is causing run_notice to take ~6s causing notices queue to be backed up causing starvation of checkpoint_ notice causing ingestion lag. Does it make sense?
Have you seen something similar on your end? How long do Kafka real-time tasks take to bootstrap on your deployments? (Also, we use Middle Managers as of today instead of Indexers).

I'm not sure whether the proposed PRs would fix your issue. I'd have to see stack traces during the 1.5-2mins pause time you refer, is that how you determined they were waiting on the future?

I'm not sure whether the proposed PRs would fix your issue. I'd have to see stack traces during the 1.5-2mins pause time you refer, is that how you determined they were waiting on the future?

I determined it is the task bootstrap time that's causing run_notice to take ~8s by reading through the run_notice handle code and also correlating the timestamps in the logs.

For example, here you can see that the kafkasupervisor_ thread was stuck for 13 seconds without logging anything. So I went through the code path between these 2 log statements and that's where I hit the futures. And I found logs from other async threads in that gap trying to get task_status but were stuck in a retry loop as the tasks were bootstrapping and hence wasn't accepting connections for 5-6s.
To prove this theory, I switched one of our lab environments to use indexers instead of MMs for real-time ingestion tasks and as I doubted, the run_notice handle time fell down from 8s to under 2s as there are no jvm restarts involved for every task bootstrap with indexers.

It seems like you're on the right path. If you can run jstack $pid during the period of concern, and capture what's happening to the thread, or even introduce some extra logging lines, this might narrow it down more quickly.

@harinirajendran I went looking for this, and I agree with your analysis. Stack traces showed that majority of wall clock time in the KafkaSupervisor thread was waiting on SQL queries executing as part of the RunNotice. I backported the changes in https://github.com/apache/druid/pull/12018 to our environment and they worked perfectly. A class histogram showed ~500 CheckpointNotice tasks sitting idle and ~2500 RunNotice tasks.
There are two ways you can confirm this is happening at any time you have slow checkpoint. Replace $pid and $supervisorname as appropriate.

Look for a count of class instances that are SeekableStreamSupervisor$RunNotice

jcmd $pid GC.class_histogram | grep SeekableStreamSupervisor

Look for supervisor thread performing RunNotice calls

jstack $pid | grep -A60 KafkaSupervisor-$supervisorname\"

Thank you to @gianm, your solution was simple and worked perfectly.

majority of wall clock time in the KafkaSupervisor thread was waiting on SQL queries executing as part of the RunNotice

In our case, it wasn't the SQL queries that were causing RunNotice to take more time. But rather, the tasks bootstrap time(~5s). @gianm's fix certainly helped bring this down. But with time as task rollovers started getting spread out over a few minutes, there weren't many runNotices next to each other to coalesce, resulting in the same problem again. To bring the time for task bootstrap down, we switched from MMs to Indexers as it doesn't involve jvm restart for every task and actually helped.
@jasonk000: Do you use MMs or indexers for your ingestion tasks? How long does it take for the ingestion tasks to bootstrap in your environment?

Our ingestion tasks run on MM nodes, I haven't investigated bootstrap time at this point.

Our ingestion tasks run on MM nodes - I had a look, and it seems to take about 8-10 seconds to go from JVM start to reading Kafka.

Our ingestion tasks run on MM nodes - I had a look, and it seems to take about 8-10 seconds to go from JVM start to reading Kafka.

Great! In my case, I looked at the point when the httpServer was started by the task so that it can respond to /status calls from overlord.
The log line I searched was something like Started<EMAIL_ADDRESS>(http/1.1)}{<IP_ADDRESS>:8102}  which happens roughly at the 4th second after the tasks start. And runNotice at the overlord gets stuck here for that duration until task can respond to the /status call. This is my observation. Does it make sense?

We solved this problem by switching from Middle Managers to Indexers. The hourly spikes don't happen anymore.

The log line I searched was something like Started<EMAIL_ADDRESS>(http/1.1)}{<IP_ADDRESS>:8102} which happens roughly at the 4th second after the tasks start. And runNotice at the overlord gets stuck here for that duration until task can respond to the /status call. This is my observation. Does it make sense?

It does make sense. Out of curiosity -- what did you have chatThreads set to? I wonder if your number of tasks is much higher than your number of chat threads, and that caused the delays to compound.

The log line I searched was something like Started<EMAIL_ADDRESS>(http/1.1)}{<IP_ADDRESS>:8102} which happens roughly at the 4th second after the tasks start. And runNotice at the overlord gets stuck here for that duration until task can respond to the /status call. This is my observation. Does it make sense?

@harinirajendran It does make sense. Out of curiosity -- what did you have chatThreads set to? I wonder if your number of tasks is much higher than your number of chat threads, and that caused the delays to compound.

The log line I searched was something like Started<EMAIL_ADDRESS>(http/1.1)}{<IP_ADDRESS>:8102} which happens roughly at the 4th second after the tasks start. And runNotice at the overlord gets stuck here for that duration until task can respond to the /status call. This is my observation. Does it make sense?

@harinirajendran It does make sense. Out of curiosity -- what did you have chatThreads set to? I wonder if your number of tasks is much higher than your number of chat threads, and that caused the delays to compound.

@gianm : We just use the default value for chatThreads. The document says default == min(10, taskCount * replicas) . So, it should be 10 in our case.

Some recent work in this area of SeekableStreamSupervisor:

Eliminate some unnecessary metadata calls: https://github.com/apache/druid/pull/13328
Don't ever queue more than one RunNotice at a time: https://github.com/apache/druid/pull/13334
Contact tasks asynchronously, eliminate chatThreads, reduce load on workerThreads: https://github.com/apache/druid/pull/13354

We are targeting Druid 25 for all of these. If anyone has a chance to try these patches out in advance of the release, please let us know!

@harinirajendran , can you confirm if this is still an issue with Druid 25?

FYI this is still an issue on Druid 27.0.0. I had set a task duration of 10 min (to reduce querying load on MMs peons) and you can see avg lag spikes matches the task roll period.

This is currently not a big deal because we have low traffic but when testing but higher volumes the spikes become a real burden because the lag spikes cannot be reduced within the 10 min period so the lag keeps increasing.
And like the OP, the Kafka tasks reports the highest avg pending time.


Module disappears after a few minutes

Strange problem just started. After a few minutes the entire module disappears. Anyone else having this problem?

My fault. Didn't read the Config. Set updateOnWarning: 0.


String values cannot contain $

Minimal example:
from confection import Config

config_str = """[section]
value='^test$'
"""

Config().from_str(config_str)

Would love to be able to have regex strings in my config, e.g. for using polars.exclude to filter columns.
Raises:
InterpolationSyntaxError
'$' must be followed by '$' or '{', found: '$'
  File "C:\Users\adminmanber\Desktop\psycop-common\psycop\common\model_training_v2\config\config_utils.py", line 33, in <module>
    Config().from_str(config_str)
configparser.InterpolationSyntaxError: '$' must be followed by '$' or '{', found: '$'

Thanks for the report!
If it worked as intended, I think that $$ should work here as the escaped form of $ in the configparser format.
I haven't looked into the gory details, but it initially looks like it's being interpolated more than once, which causes problems with $$.
A terrible hacky workaround for this one specific problem:
[section]
value="^test$$$$"

The interpolated config then looks like this, where this string does still work as the intended regex:
[section]
value = "^test$$"

Ah, I see, thanks! Hadn't noticed that configparser was part of stdlib, glad to see it!
This appears to be a bug in configparser, then?

No, we've overridden some of the interpolation with custom methods, so I think it's a bug in confection.

Ah, the problem isn't directly in the parsing/interpolation, it's in the to_str conversion that doesn't re-escape $ in its own output.


How to increase FPS while running Yolo-v3 example.

Hi
so I have trained a custom yolo-v3 model trained on voc dataset in darknet and then converted it into caffe. I'm using the old vitis version for some reason that gave me a complied elf file.
I'm using this code mentioned below for deployment in python on pynq v2.5 image on Ultra96 v2 board
https://github.com/Xilinx/Vitis-AI/blob/1.1/demo/DNNDK/tf_yolov3_voc_py/tf_yolov3_voc.py.
Everything is working fine, I just need to know how can I implement multithreading to increase the output FPS as suggested here
https://www.xilinx.com/html_docs/vitis_ai/1_3/running_examples.html#ariaid-title2

Hey!
I think you can follow this example https://github.com/Xilinx/Vitis-AI/blob/1.1/demo/VART/resnet50_mt_py/resnet50.py, try creating different threads for the DPU process, and make sure you are running different threads for i/o image processes, consider this C++ example (https://github.com/Xilinx/Vitis-AI/blob/1.1/demo/VART/video_analysis/src/main.cc).
Let me know if you need further help :)

Hi, thankyou so much, that helped a lot. I can now use multithreading.
But there is another issue I ran into. Now I'm converting a yolo-v4 model into tensorflow. The conversion, quantization and compilation was sucessful. I got the elf file and the kernal info. The kernal name in kernal info is "dpu_yolov4" but as soon as I put this kernal name in n2cube.dpuLoadKernal("dpu_yolov4"), the jupyter kernal of pynq 2.5 image crashes. Can you help me resolve it?
Also I tried same model for caffe with kernal name "yolov4_voc" and everything ran smoothly.
I don't think the issue is related to elf file. I think it's n2cube library issue as loading kernal name is 1st step that does not require any model file.

Hi, @daivikbhatia
Has the problem been solved? If not, please refer to:
Or you provide the model with the problem, we will reproduce the problem.

Hi, @daivikbhatia
Has the problem been solved? If not, please refer to:https://github.com/Xilinx/Vitis-AI-Tutorials/tree/master/Design_Tutorials/07-yolov4-tutorial
Or you provide the model with the problem, we will reproduce the problem.

Hi @daivikbhatia
Since we haven't received your reply for a long time, we assume you have solved this issue and I'm going to close it. If you still have any questions, please feel free to reopen it. Thank you very much.


Stuck when returning from a background task

Occasionally, kiwi returns from the background to the foreground, the application is stuck, the screen is blank, and it cannot be operated, so I have to cross out the task and reopen kiwi.
redmi k40(POCO f3) Android11 MIUI12.5/21.8.10

Have you tried recent release? https://github.com/kiwibrowser/src.next/releases

Have you tried recent release? https://github.com/kiwibrowser/src.next/releases

Yes now it's getting better


[docs] Update docs with support for SecurityManager

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-12-05T14:49:41.318+0000

Duration: 4 min 46 sec

:grey_exclamation: Flaky test report
No test was executed to be analysed.
:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run benchmark tests : Run the benchmark tests.

run jdk compatibility tests : Run the JDK Compatibility tests.

run integration tests : Run the Agent Integration tests.

run end-to-end tests : Run the APM-ITs.

run windows tests : Build & tests on windows.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)


Debug Endpoints

Hello,
While http://localhost:9325/ is a great debug feature to see the queue details, but I was wondering if there easy curable endpoints (without having to deal w/ aws features) to enqueue objects, or flush a queue.
Sorry if this question is redundant.
Really appreciate this project!

@charlie-cho-carbon unfortunately the UI bundled with ElasticMQ is limited to displaying queue metadata and stats.
You can check out this project https://github.com/roribio/alpine-sqs which uses ElasticMQ inside.


fix: fix WebGL compilation error

Queueing does not work for WebGL. It doesn't compile. This is a fair solution to at least make it work.

Fixes #722

MTT-636

Library\PackageCache\com.unity.multiplayer.mlapi@94d5dbac7a\Runtime\Transports\UNET\UNetTransport.cs(83,17): error CS0103: The name 'Debug' does not exist in the current context
Library\PackageCache\com.unity.multiplayer.mlapi@94d5dbac7a\Runtime\Transports\UNET\UNetTransport.cs(154,17): error CS0103: The name 'Debug' does not exist in the current context

Library\PackageCache\com.unity.multiplayer.mlapi@2e1415e971\Runtime\Transports\UNET\RelayTransport.cs(322,64): error CS0117: 'NetworkTransport' does not contain a definition for 'QueueMessageForSending'
Library\PackageCache\com.unity.multiplayer.mlapi@2e1415e971\Runtime\Transports\UNET\RelayTransport.cs(341,60): error CS0117: 'NetworkTransport' does not contain a definition for 'QueueMessageForSending'
Library\PackageCache\com.unity.multiplayer.mlapi@2e1415e971\Runtime\Transports\UNET\RelayTransport.cs(348,64): error CS0117: 'NetworkTransport' does not contain a definition for 'SendQueuedMessages'
Library\PackageCache\com.unity.multiplayer.mlapi@2e1415e971\Runtime\Transports\UNET\RelayTransport.cs(351,60): error CS0117: 'NetworkTransport' does not contain a definition for 'SendQueuedMessages'

Library\PackageCache\com.unity.multiplayer.mlapi@db8c4e2b07\Runtime\Transports\UNET\UNetTransport.cs(176,28): error CS0117: 'RelayTransport' does not contain a definition for 'SendQueuedMessages'

hey just keep coming ;)

Holding this off until #726 is merged with this one.

It looks like #726 has been closed, can an equivalent change be added here?


Demo site animation css missing

vue-sonner.vercel.app animation css missing

Not reproduced

After I updated my browser, the animation appeared


split screen support with the help of scaling value to min 1

/// The ratio of actual width to UI design
double get scaleWidth => max(_screenWidth / uiSize.width, 1);
///  /// The ratio of actual height to UI design
double get scaleHeight => max(_screenHeight / uiSize.height, 1);
double get scaleText => min(scaleWidth, scaleHeight) ;

This way we don't need boolean splitScreenMode and minTextAdapt.

On Laptops and other devices where the screen device width is large, there text will scale based on HEIGHT on mobile devices it will be scaled based on WIDTH.  (Whatever is minimum).

max(_screenWidth / uiSize.width, 1); it will limit the  Width scaling minimum to given design size Width by user(developer).

max(_screenHeight / uiSize.height, 1); it will limit the Height scaling minimum to given design size Height by user(developer).

Height only depends on device size, not on window size. So it works like most websites and therefore supports split-screen.

Please test and let me know if anything I can improve here.


Added a simple guard that prevents an exception being thrown on application exit

Locally I kept getting the same exception over and over when closing the program.
It turns out that the server log entry was still firing slightly after the app had quit, leaving webContents undefined.
Just needed a simple guard  return out once the app has been exited.

Great catch! Thank you so much for fixing this.

No problem! Keep up the good work, your roguelikes look awesome!


Adding support for the OpenSCAD language

I added a syntax file for the language, plus a comment identifier for line commenting.

More or less a duplicate of #3410?

Apologies for the duplicate—I'm new to this. I noticed that the previous
pull request was merged about two months ago, but I’m not seeing the
changes reflected on my instance. Could you please guide me on how to
proceed with the PR process? I’d also appreciate any tips on how to
contribute more effectively. Thanks
On Tue, 5 Nov 2024, 01:00 Jöran Karl, @.***> wrote:

More or less a duplicate of #3410
https://github.com/zyedidia/micro/pull/3410?
—
Reply to this email directly, view it on GitHub
https://github.com/zyedidia/micro/pull/3532#issuecomment-2455873586, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ARP3OUEQ5HKKMFIOIC4H4J3Z674AFAVCNFSM6AAAAABRE7T5EOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJVHA3TGNJYGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thank you for all your comments, I fixed the issues raised above.

Could you please guide me on how to proceed with the PR process?

Maybe you have a look into the following two GitHub documentations:

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork

Afterwards you edit the already existing scad.yaml and add the things you miss there. Then you can update this PR or close it and create a new one...depends what is easier for you to handle.

Thank you for the references, @JoeKar. I was asking about a specific issue here: as you mentioned, this seems to be a duplicate of a previous one that was resolved and merged to master, but the changes don't appear to be reflected in the repo.
@zyedidia, with your approval, I believe it's ready for merge now. Thank you for your time and consideration.

@BenSiv It is definitely in the repo, maybe you missed it because the file is called scad.yaml instead of openscad.yaml like in this pull request? (Which is also why I didn't realize the syntax already exists when reviewing the PR.) Renaming it to openscad.yaml might be a good idea to be consistent with the other syntax files (nearly all of which are named after the language, not the file extension).

@Andriamanitra  Thank you for your comment; you are absolutely right. I have merged the two files to the naming convention.

@BenSiv It is definitely in the repo, maybe you missed it because the file is called scad.yaml instead of openscad.yaml like in this pull request?

That was the reason, why I referred to:

Afterwards you edit the already existing scad.yaml and add the things you miss there.

:wink:

Renaming it to openscad.yaml might be a good idea to be consistent with the other syntax files (nearly all of which are named after the language, not the file extension).

@jmcorey:
Does something speak against a rename of scad.yaml -> openscad.yaml, since you initially created the scad.yaml for #3410?
Furthermore it would be helpful if you can through your eyes on this PR for a review too, since you seem to use this language.

Thanks for the heads up!  I hadn't noticed the conversation.  I have no preference for whether the file is named openscad.yaml or scad.yaml.  The actual files end in .scad rather than .openscad, though to be honest openscad is the main program that parses and recognizes these files, so I guess it reflects poorly on me that I couldn't figure out whether to call it scad or openscad.  Probably just scad, but I'm fine either way.

As for whether it's ready to merge, there might be still more cleanup that could be done.
For example, I remember when I did my patch, I was encouraged to put all the statement keywords on one single line, rather than splitting it out based on abstract groupings, to reduce the overall number of rules in the file for the sake of efficiency.  Right now, it looks like in the proposed file there are multiple different "statements" lines, and there is even duplication between them, for example see the "else" keyword.
It's also interesting that there's a numbers section in the middle of the file and one towards the end--suspect some duplication there as well, and am wondering if it's necessary to have them so far apart in the file.

When it's looking more like finished draft material, I'd be happy to help test.  I assume there's no way to
do any kind of automated tests for these files...


--advertise-address should apply to mesh gossiping as well as peer discovery

This flag was added for the Cloud-based peer discovery feature, but users may expect to use it independently.
Requires https://github.com/weaveworks/mesh/issues/83

It would be good to be able to set it for the Weave Net Docker plugin as well. Something like docker plugin set weaveworks/net-plugin:latest_release ADVERTISE-ADDRESS=<ip1>,<ip2>.
Thanks for opening this issue!


Fix #307, update outdated searxng/settings.yml

@return42 I've post a MR to update the outdated searxng/settings.yml file: #309, please review it and provide feedback or instructions for any necessary actions. Thank you for all your excellent works.

LGTM :+1:

Thanks!


Consider simplifying Python code within snakemake rules

Some snakemake rules (e.g., rule rule summarize_contigs_by_coverage in polish.smk) currently include long Python code blocks that contain functions etc. Would it be better to simplify the code included in the Snakefile, e.g., by calling a separate Python script, for such code?

Previous discussion for rule summarize_contigs_by_coverage in #114:
@jmtsuji

Thanks for improving the function definition here. How do you think we should handle such functions? Might it be better to move functions like this into a different part of the snakefile (or to a different file in the repo) rather than keep it nested inside the rule?

@LeeBergstrand

@jmtsuji, do you have to move imports inside the run block as if it's a script? I suspect everything outside the run block can't be seen inside unless it is a particular variable created by Snakemake. That is my suspicion, but I am unsure; it could be injecting it differently than expected. If we wanted to move it, I would move it to utils.py (most of utils.py would be moved to its library, but we can have two util files) or a dedicated coverage so as not to clutter up to code.

@LeeBergstrand Regarding your comment above, I think you are probably right... I also suspect that everything outside the code block can't be seen inside. We will probably need to import the code via an import command or just write a Python script that we can call for the rule.

Given that we don't have very many rules with long Python code blocks at the moment, I think it's not a high priority to try to move around the code at this point. However, it might be something we could consider in the future, especially if we create more rules like summarize_contigs_by_coverage that have complex Python code. OK to table this issue for now? Or do you think it could be worthwhile to explore simplifying the code in the snakefile for this rule?

Given that we don't have very many rules with long Python code blocks at the moment, I think it's not a high priority to try to move around the code at this point. However, it might be something we could consider in the future, especially if we create more rules like summarize_contigs_by_coverage that have complex Python code. OK to table this issue for now? Or do you think it could be worthwhile to explore simplifying the code in the snakefile for this rule?

I would table the issue for now. I would probably move the code to utils.py but after we pull the code out into its own library.

OK, sounds good -- let's table this for now.

Update: as discussed in #126 , the logic for rule summarize_contigs_by_coverage is getting complex enough that it might make sense to move the code into its own script in future:
From #126:

In the long term, I think it might make sense to move the code in summarize_contigs_by_coverage into a Python utility script -- this would make it easier to write/run tests on some of the logic being performed in this code.


Header is defaulting to column ID, when header prop is not provided in column definiiton

Describe the bug
According to docs:
https://tanstack.com/table/v8/docs/api/core/column-def#header
header is an optional parameter. I would expect that, if it is not provided, nothing will be shown in header. Current behaviour is that header is filled with column id.
Your minimal, reproducible example

Steps to reproduce
Define column without header prop.
Expected behavior
Header should be empty.
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform

react-table version
8.1.3
TypeScript version
No response
Additional context
No response
Terms & Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

You can change the default behavior for this:
useReactTable({
  defaultColumn: {
    header: null // or ''
  }
})

You can change the default behavior for this:
useReactTable({
  defaultColumn: {
    header: null // or ''
  }
})

@tannerlinsley Yeah, I know that. I wonder if this should not be documented somehow. In v it worked differently.


Unpublish and Delete buttons in backoffice content edit page

https://github.com/OrchardCMS/Orchard/blob/0973810c0998ee567d53507bbb0171cc4c04f6b2/src/Orchard.Web/Core/Contents/Drivers/ContentsDriver.cs#L22
The idea is to extend the options of a backoffice operator when managing contents, adding "unpublish" and "delete" content buttons in the edit view, where standard "save" and "publish" buttons are present. I am adding shapes to the referenced driver, shapes are going to be very similar to the ones already present in the "Core/Contents/Views" folder (e.g. "Content.PublishButton.cshtml") Controller actions will be inspired by already existing unpublish and remove actions in AdminController.
On top of that, a little adjustment to the Placement.info is likely going to be needed.

PR not ready yet, working to make other drivers and controllers (e.g. Orchard.Blogs') compatible / aligned with new backoffice buttons.


PPC 2.0 Feature Flag & POC

With the update to the PPC (moving, reorganizing, adding more nuanced checks), we would be well served to refactor the structure of the checklist code base to make it easier to digest and start making perf improvements that can be gradually bettered.
This means the 2.0 version of the checklist can be feature flagged which will make for a better release candidate as everything for the 1.9. release of PPC is tied together and impossible really to do in isolation.
This ticket is for the feature flag of PPC 2.0 as well as proof of concept/starter code and new architecture of the revamped checklist.
Acceptance criteria:
new feature flag
poc of ppc update structure

gonna add the feature flag here and initial popup to pull the checks into, then will move this into review


wallet-ext: update max height

Description

now wallet can expand to 680px if there is available room

https://github.com/MystenLabs/sui/assets/10210143/b9e7ed20-e618-4fcf-b181-da91e150bdc9
closes APPS-1637
Test Plan
👀

If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process.
Type of Change (Check all that apply)

[ ] protocol change
[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

Looking good.
If there was a way to keep the graphic center aligned vertically in the space between top/bottom that would be preferable.

@mystie711  I updated it, added new video in the description


noseedbackup param does not need an arg in command line

When starting lnd_ltc on simnet, we were getting an error where noseedbackup had an unexpected argument. This came from moving the noseedbackup flag from the conf file to the bash file. In the conf file the noseedbackup needed to be set to 1 where in the command line, it is just a flag (no argument).

 bugfix, noseedbackup should not have argument

@martineehrlich this was only occuring with LTC?


Use go 1.20 in dockerfile

#98  👈
feature/proof-of-stake

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @lazynina and the rest of your teammates on  Graphite


Add .Net 7 target

fixes #4219
fixes #4194

global.json probably should be updated as well
https://github.com/RicoSuter/NSwag/blob/master/global.json#L3

Also need to update the npm js file:
https://github.com/RicoSuter/NSwag/blob/master/src/NSwag.Npm/bin/nswag.js#L11

Hi,
Some of the 7.0.0 libraries support Net6 and Net7, as example EF Core libraries.
NSwag overlaps on Net6 as
NSwag.AspNetCore -> NSwag.Generation.AspNetCore -> Microsoft.Extensions.DependencyInjection.Abstractions (>= 6.0.0 && < 7.0.0)
Where EF Core dependencies are 7.0.0.
Also with Microsoft.Extensions.Options.
for the Generation should be next may be?
  <ItemGroup Condition="'$(TargetFramework)' == 'net6.0'">
    <FrameworkReference Include="Microsoft.AspNetCore.App" />
    <PackageReference Include="Microsoft.Extensions.DependencyInjection.Abstractions" Version="[6, 8)" />
    <PackageReference Include="Microsoft.Extensions.Options" Version="[6, 8)" />
  </ItemGroup>

We tend to use Net6, but since it's a Target 7 updated, could uptake also these changes.

What can possibly go wrong :D
The constraints relaxed

Do you have an idea of release schedule

This fails if your project is net 7 and have <PlatformTarget>x64</PlatformTarget> in your csproj with the following message:
 Detected package downgrade: System.Collections from 4.3.0 to 4.0.11. Reference the package directly from the project to select a different version.
 MiSystems.GeoServices -> NSwag.AspNetCore 13.17.1 -> NSwag.Core 13.17.1 -> Newtonsoft.Json 9.0.1 -> System.Xml.ReaderWriter 4.0.11 -> System.IO.FileSystem 4.0.1 -> runtime.win.System.IO.FileSystem 4.3.0 -> System.Collections (>= 4.3.0)
 MiSystems.GeoServices -> NSwag.AspNetCore 13.17.1 -> NSwag.Core 13.17.1 -> Newtonsoft.Json 9.0.1 -> System.Collections (>= 4.0.11)	MiSystems.GeoServices	C:\Work\MiSystems\MiSystems.GeoServices\MiSystems.GeoServices.csproj

Hello @r-work and thanks.
It should be solvable in your code by declaring a dependency on System.Xml.ReaderWriter=4.3.0 and System.Collection=4.3.0, or better on a higher Newtonsoft.Json. Which you should do anyway, there are some security issues.
At the same time, I bumped the minimal version in this library to 10.0.1, which is still vulnerable to the security issues mentioned above, but it should resolve without help.

Aye that’s right. Anything below 13.0.1 synk or another Analyzers will raise CWE-755

Hi @trejjam, sorry had to delete my previous comment as I realized it contained internal info.
Our project does not reference Newtonsoft.Json as we've migrated to System.Text.Json.
So the issue might just be NSwag referencing an old Newtonsoft.Json version.

Original message:

This fails if your project is net 7 and have x64 in your csproj with the following message:
Detected package downgrade: System.Collections from 4.3.0 to 4.0.11. Reference the package directly from the project to select a different version.
A.Project -> NSwag.AspNetCore 13.17.1 -> NSwag.Core 13.17.1 -> Newtonsoft.Json 9.0.1 -> System.Xml.ReaderWriter 4.0.11 ->  System.IO.FileSystem 4.0.1 -> runtime.win.System.IO.FileSystem 4.3.0 -> System.Collections (>= 4.3.0)
A.Project -> NSwag.AspNetCore 13.17.1 -> NSwag.Core 13.17.1 -> Newtonsoft.Json 9.0.1 -> System.Collections (>= 4.0.11)	A.Project	C:\A.Project\A.Project.csproj

Our project does not reference Newtonsoft.Json as we've migrated to System.Text.Json.

Since you are using NSwag you are using Newtonsoft.Json, so you should upgrade it. Lower-bound dependencies are kinda a habit here :) (They permit you to upgrade when you want, instead of forcing you)

I meant it's not referencing it directly.
Got it, thanks.

Thank you @RicoSuter  for the release !

v13.18.0 is now released with .NET 7... please report if it works as expected

I'm able to upgrade to .NET 7 now using NSwag 13.18.0. All seems to work as expected. Thank you for the release. 🚀

@trejjam can you tell me why the BodyParametersTests are invalid in .NET 7 (Skip = "Wrong in .Net 7")?

Hi @RicoSuter,
The test says When_primitive_body_parameter_has_default_value_then_it_is_optional but it's tested to be required in .Net6. In .Net 7 IsRequired result is false for BodyParameters_RequiredPrimitiveWithDefault (as it should be, based on the test description)

"Correct" solution, in my opinion, is probably to remove *before_net7 with conditional Skip definition !NET7_0_OR_GREATER and then fix the parser for .Net6. The question is if it's worthy/possible.

Ok, will think about it. Now working on the bigger v14 release itself...


Access-Control-Allow-Origin

Looked for an solutions - didnt find one (after 20min..xD)
Tested via

file://
localhost
online Server
Mobile App
and Node-Webkit App

Everywhere same error.
Tested on localhost and online Server with modified .htaccess File
Header add Access-Control-Allow-Origin "*"
Header add Access-Control-Allow-Headers "origin, x-requested-with, content-type"
Header add Access-Control-Allow-Methods "PUT, GET, POST, DELETE, OPTIONS"
Header add Access-Control-Max-Age: 86400

Maybe u should tell more about this client. (Tested with your Demo, and 2 own servers)

@devmexx were you ever successful with that project? I'm experimenting with the exact same thing... I posted a little bit on the LoL developer forums about it. shoot me an email maybe if you're interested in working together<EMAIL_ADDRESS>


Erisc Compile Cleanup Items

Some cleanup items:

[ ] generate linkers
[ ] delete eth_l1 map and consume from UMD
[ ] make base and kernel FW data and code sections non-static
[ ] load iram

@aliuTT is this still relevant?

yea, but there are probably other items that we can open to track this

Closing, I opened new items for relevant TODOs


add access to fit / predicted values

Is your feature request related to a problem? Please describe.
Can pmdarima provide a method to access the fit (predicted) values of the time series?
Describe the solution you'd like
would be nice to have an attribute that can return the fit values as a series.
Describe alternatives you've considered
none
Additional context
this is useful when visualizing plots of the time series, to see both the original series, and the values predicted by the algorithm

already implemented


fix "NameError: undefined local variable "package"

I don't know if the failure is related. I wouldn't think so.

Restarted travis jobs. Not sure if these are related or not.

It's related to PDK.
$ be rake build
rake aborted!
NoMethodError: undefined method `package_install?' for PDK::Util:Module
/home/ekohl/.gem/ruby/gems/pdk-1.14.0/lib/pdk/module/metadata.rb:111:in `from_file'
/home/ekohl/.gem/ruby/gems/pdk-1.14.0/lib/pdk/module/build.rb:23:in `metadata'
/home/ekohl/.gem/ruby/gems/pdk-1.14.0/lib/pdk/module/build.rb:90:in `release_name'
/home/ekohl/.gem/ruby/gems/pdk-1.14.0/lib/pdk/module/build.rb:60:in `build_dir'
/home/ekohl/.gem/ruby/gems/pdk-1.14.0/lib/pdk/module/build.rb:81:in `cleanup_build_dir'
/home/ekohl/.gem/ruby/gems/pdk-1.14.0/lib/pdk/module/build.rb:42:in `ensure in build'
/home/ekohl/.gem/ruby/gems/pdk-1.14.0/lib/pdk/module/build.rb:42:in `build'
/home/ekohl/.gem/ruby/gems/pdk-1.14.0/lib/pdk/module/build.rb:5:in `invoke'
/home/ekohl/.gem/ruby/gems/puppetlabs_spec_helper-2.14.1/lib/puppetlabs_spec_helper/rake_tasks.rb:147:in `block (2 levels) in <top (required)>'
/home/ekohl/.gem/ruby/gems/puppetlabs_spec_helper-2.14.1/lib/puppetlabs_spec_helper/rake_tasks.rb:129:in `block in <top (required)>'
/home/ekohl/.gem/ruby/gems/rake-13.0.0/exe/rake:27:in `<top (required)>'
/usr/share/gems/gems/bundler-1.17.2/lib/bundler/cli/exec.rb:74:in `load'
/usr/share/gems/gems/bundler-1.17.2/lib/bundler/cli/exec.rb:74:in `kernel_load'
/usr/share/gems/gems/bundler-1.17.2/lib/bundler/cli/exec.rb:28:in `run'
/usr/share/gems/gems/bundler-1.17.2/lib/bundler/cli.rb:463:in `exec'
/usr/share/gems/gems/bundler-1.17.2/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/usr/share/gems/gems/bundler-1.17.2/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
/usr/share/gems/gems/bundler-1.17.2/lib/bundler/vendor/thor/lib/thor.rb:387:in `dispatch'
/usr/share/gems/gems/bundler-1.17.2/lib/bundler/cli.rb:27:in `dispatch'
/usr/share/gems/gems/bundler-1.17.2/lib/bundler/vendor/thor/lib/thor/base.rb:466:in `start'
/usr/share/gems/gems/bundler-1.17.2/lib/bundler/cli.rb:18:in `start'
/usr/share/gems/gems/bundler-1.17.2/exe/bundle:30:in `block in <top (required)>'
/usr/share/gems/gems/bundler-1.17.2/lib/bundler/friendly_errors.rb:124:in `with_friendly_errors'
/usr/share/gems/gems/bundler-1.17.2/exe/bundle:22:in `<top (required)>'
/usr/bin/bundle:23:in `load'
/usr/bin/bundle:23:in `<main>'

IMHO it's still very annoying that this gem pulls in PDK and I'd really like to avoid that. Personally I still install Puppet 5 to release my modules just to avoid PDK.


[modify] event node search sort

coverage: 71.029%. first build
when pulling 9f11bcccb567cfbc594e64ede62623f894e960e0 on pr-event-search-sort
into 71189f2931f6619e735ce31a3806e940d5408749 on master.


fix: add debug logs for unresolvable plugins

This moves the isImportable function into registerPlugin where it belongs. This lets us warn users (via debug log) when a plugin is missing its main module.
Also, the lib/isPlugin.js module is no longer necessary.
Lastly, add a test for the undefined $NODE_PATH edge case.

@mateodelnorte Nope. That check is now in registerPlugin.
I edited the OP yesterday with:

This moves the isImportable function into registerPlugin where it belongs. This lets us warn users (via debug log) when a plugin is missing its main module.

Maybe worth just letting registerPlugin throw instead of catching and printing to the debug log.

There's always the potential that somebody names a node_modules meta-something-or-other and it's not actually a meta plugin. :P

@mateodelnorte Alright, good point. LGTM!

Actually, that point is irrelevant, because the chances are practically none that you have a meta- package that (1) isn't a Meta plugin and (2) has no entry module (which is what the require.resolve check protects against)

s'merged!

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


rxvt-unicode: 9.30 -> 9.31

Description of changes
Bug fix release
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

[x] Tested rxvt-unicode and rxvt-unicode-emoji
[x] Tested basic functionality of all binary files
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.

I'm experiencing some regressions likely since this bump. Most importantly unicode symbols are no longer working for me which also makes my prompt broken. Also in xmonad my the prompt is is located in bad place because it badly reacts to xmonad resizing the window immediately after it's been open.
Am I the only one experiencing these weird regressions?

Most importantly unicode symbols are no longer working for me which also makes my prompt broken.

This is new to me, open an issue and share your configuration.

Also in xmonad my the prompt is is located in bad place because it badly reacts to xmonad resizing the window immediately after it's been open.

See https://github.com/NixOS/nixpkgs/issues/241646#issuecomment-1621482863

This is new to me, open an issue and share your configuration.

I just did an update (unstable) and the issue went away. So I won't be opening the issue for this in the end.


Fixed #32383 -- Added source map support to ManifestStaticFilesStorage

ticket-32383

buildbot, test this please.

@adamchainz test_js_source_map doesn't work on Windows. Can you take a look?

Thanks for your updates.
I can't work out why it's failing - it's coming up with a different hash on windows for apparently no good reason? I checked with hexdump and there are no weird characters such as CRLF line endings in source_map.js. And the file should be opened in binary mode too.
I'm pushing a commit with

@adamchainz I tried to investigate this and it's related with HashedFilesMixin._stored_name(), for the same value i.e. cached/source_map.js.map it returns different values on Linux and Windows :thinking:

OK I found :confetti_ball: file_hash() creates a hash from a different content:

b'{}\n' on Linux
b'{}\r\n' on Windows

Let's try with no newline at the end of file :detective:

@adamchainz Fixed :partying_face:

buildbot, test this please.

Great, thanks.


SQL Assessment runs infinitely for some SQL Server instances

Azure Data Studio Version: 1.23.0

Steps to Reproduce:

Install SQL Assessment extension to ADS
Connect to a SQL Server 2008 R2 instance
Right-click the instance and select Manage
Click SQL Assessment
Click Invoke Assessment
Assessment runs forever

For Azure Data Studio Version 1.24.0-insider

On a SQL Server instance (any version) disable xp_cmdshell
Install SQL Assessment extension to ADS
Connect to the instance configured at step 1
Right-click the instance name on the left pane and select Manage
Click SQL Assessment
Click Invoke Assessment
Assessment runs forever

@aguzev this should be fixed in release/1.24.  Could you please verify on the latest RC1 build?


[issue#52] Added unit tests to check some files exist

Description of the change:
This PR fulfill the request from issue #52 , which asked to create tests to validate if some files exist
Reason for the change:
The reason behind the request is guarantee that some basic files like README.MD will always be present int he project, so, if it is erased by mistake, the tests will not pass and it will be explicit the problem, without any human manual validation
Link to original source:
The actual source https://github.com/sendgrid/nodejs-http-client/blob/90ca4ebb6e0e6b59bd554908105f66114ad5a8f6/test/test.js
Checklist
Make sure all of these items are complete, or else the PR will be ineligible for a code review.

[x] Code passes all existing tests the new tests do not pass as it is expected mentioned in #52
[x] Any new functionality added includes new unit tests in test/test.js
[x] Create or update example code to show the new functionality in action.
[x] All code, branch, and git naming and style conventions are followed (see CONTRIBUTING.md)
[x] Feature branch has been rebased off of the latest master branch. ( see CONTRIBUTING.md ).

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

BEAUTIFULLY done!
This is awesome. Thank you so much!!
Just so you know, we have this same issue on another Node library if you're interested:

https://github.com/sendgrid/sendgrid-nodejs/issues/565

Hello @luan-cestari,Thanks again for the PR! We want to show our appreciation by sending                                              you some swag. Could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX

Thank you guys =) I hope I can help with other issues in the future


Add jekyll website to covidcaremap.org

I am implementing a visual design made by Alex Lash for the COVIDCareMap website. I set this up on a separate repo, temporarily, so it wouldn't conflict with @hectcastro's on #76.
Original design: https://share.goabstract.com/a25857d2-832a-43b2-8ded-8fe496cec2aa?mode=design&sha=59f74eb547d1057e22bd48acc9135378c242b3b4
Temporary website repo: https://github.com/jfrankl/covidcaremap-website
Todo:

[ ] @daveluo needs to update the copy on the site
[ ] @jfrankl needs to enhance the site to look better on mobile (right now it looks super busted)
[ ] Someone needs to connect this to the covidcaremap repo and the work @hectcastro is doing on #76 / put it in the right place in the repo

Happy to take the last task on. I'll leave it up to you all on whether that should happen before or after the copy updates and mobile enhancements. FWIW, I don't anticipate the merge to be too bad since the root of the site in https://github.com/covidcaremap/covid19-healthsystemcapacity/pull/76 retains its Jekyll roots.

@hectcastro thanks for offering to take that on. That would be great. We should wait until the copy is updated before we publish it, at least, because right now it's lorem ipsum in a lot of places. But if there are ways for you to get started before then, you are welcome to do that.


Objective-C button close not works

Hello,
I use only Objective-C version, not Swift.

I integrate PopUpViewController.h and PopUpViewController.m.
I create a .xib with button close like your exemple.
I code it to open :

- (void)openPopup
{
    PopUpViewController *popViewController = [[PopUpViewController alloc] initWithNibName:@"NbArticlesPopUpViewController" bundle:nil];

    [popViewController setTitle:@"This is a popup view"];
     [popViewController showInView:self.parentViewController.view
     withImage:[UIImage imageNamed:@"yourImage"]
     withMessage:@"Message" animated:YES];
}

The popup launch but the button close crash application.…
Thanks for help....

@Paul75 are you using the Swift version of my code or the Objective-C version?

The objective c
Sur 13 févr. 2015 09:55, à 09:55, Nikos Maounis<EMAIL_ADDRESS>a écrit:

@Paul75 are you using the Swift version of my code or the Objective-C
version?

Reply to this email directly or view it on GitHub:
https://github.com/psy2k/NMPopUpView/issues/8#issuecomment-74223078

Did you try the .xibs available in the repo? You have to wire the close action to the xib file. Also you may find the solution for issue #7 useful. Let me know if you still have issue with this and post the crash message if you can.

I use the xibs Who are un thé package version ...
Sur 13 févr. 2015 11:02, à 11:02, Nikos Maounis<EMAIL_ADDRESS>a écrit:

Did you try the .xibs available in the repo? You have to wire the close
action to the xib file. Also you may find the solution for issue #7
useful. Let me know if you still have issue with this and post the
crash message if you can.

Reply to this email directly or view it on GitHub:
https://github.com/psy2k/NMPopUpView/issues/8#issuecomment-74230621

@Paul75 I've just tested it and it works properly on both the Swift and the Objective-C version (as long as you set the file owner to the .xib files to the version you want to use -ObjC or Swift-. Post the crash log please so I can help you further.

I test it with the exemple and it not found the import -swift.h
Sur 14 févr. 2015 09:54, à 09:54, Nikos Maounis<EMAIL_ADDRESS>a écrit:

@Paul75 I've just tested it and it works properly on both the Swift and
the Objective-C version (as long as you set the file owner to the .xib
files to the version you want to use -ObjC or Swift-. Post the crash
log please so I can help you further.

Reply to this email directly or view it on GitHub:
https://github.com/psy2k/NMPopUpView/issues/8#issuecomment-74367615

@Paul75 are you using Xcode 6? -swift.h file is an auto-generated file for using Swift classes in Objective-C. Also your project should target iOS 7 and above.

But i must configure the project specially ?
Sur 14 févr. 2015 10:07, à 10:07, Nikos Maounis<EMAIL_ADDRESS>a écrit:

@Paul75 are you using Xcode 6? -swift.h file is an auto-generated file
for using Swift classes in Objective-C. Also your project should target
iOS 7 and above.

Reply to this email directly or view it on GitHub:
https://github.com/psy2k/NMPopUpView/issues/8#issuecomment-74367917

But i must incorpore the swift version if file ?
Sur 14 févr. 2015 10:07, à 10:07, Nikos Maounis<EMAIL_ADDRESS>a écrit:

@Paul75 are you using Xcode 6? -swift.h file is an auto-generated file
for using Swift classes in Objective-C. Also your project should target
iOS 7 and above.

Reply to this email directly or view it on GitHub:
https://github.com/psy2k/NMPopUpView/issues/8#issuecomment-74367917

@Paul75 if you want to use the Objective-C version, just add to your project only the Objective-C classes and change the file owner of the .xibs to PopUpViewController (the default is PopUpViewControllerSwift) as described here #7.

Okay it works...
I have a another question : I can do a form (add textfield, others.…) and
add button validate ?
Thanks
2015-02-14 10:20 GMT+01:00 Nikos Maounis<EMAIL_ADDRESS>
@Paul75 https://github.com/Paul75 if you want to use the Objective-C
version, just add to your project only the Objective-C classes and change
the file owner of the .xibs to PopUpViewController (the default is
PopUpViewControllerSwift) as described here #7
https://github.com/psy2k/NMPopUpView/issues/7.
—
Reply to this email directly or view it on GitHub
https://github.com/psy2k/NMPopUpView/issues/8#issuecomment-74368206.

--
Paul

@Paul75 you can customize the popup as you like and add any UI element you want. It is just like any other iOS view.

Thanks.
To modify I must hange functions to send datas ? change
PopUpViewController.h and PopUpViewController.m ?
Thanks a lot :)
2015-02-15 14:00 GMT+01:00 Nikos Maounis<EMAIL_ADDRESS>
Closed #8 https://github.com/psy2k/NMPopUpView/issues/8.
—
Reply to this email directly or view it on GitHub
https://github.com/psy2k/NMPopUpView/issues/8#event-235971838.

--
Paul

@Paul75 Yes you can add any IBOutlet and the corresponding actions and functions in PopUpViewController.h and .m files like you do with any other class or view.

Thanks a lot :)
2015-02-15 17:08 GMT+01:00 Nikos Maounis<EMAIL_ADDRESS>
@Paul75 https://github.com/Paul75 Yes you can add any IBOutlet and the
corresponding actions and functions in PopUpViewController.h and .m files
like you do with any other class or view.
—
Reply to this email directly or view it on GitHub
https://github.com/psy2k/NMPopUpView/issues/8#issuecomment-74423373.

--
Paul

More info on a similar issue are provided here #9

Hiii I'm not getting response to the button.
please help me.
i'm using objective C

@sai487 make sure that you keep a strong reference to the popup in your code. See the readme file for more information.