Crashlytics shows a weird crash report for some devices related to Google ads

This is a rare case crashlytic report being shown for few devices. I would like to know what is the problem here. Is it because of webview or google ads plugin. Device is OnePlus Nord 2t 5g with android 13.
Fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError: PlatformException(error, java.lang.reflect.InvocationTargetException, null, android.util.AndroidRuntimeException: java.lang.reflect.InvocationTargetException
at android.webkit.WebViewFactory.getProvider(WebViewFactory.java:363)
at android.webkit.WebSettings.getDefaultUserAgent(WebSettings.java:1396)
at n3.b2.B(Unknown Source:76)
at com.google.android.gms.internal.ads.be0.s(Unknown Source:138)
at com.google.android.gms.internal.ads.em0.d(Unknown Source:68)
at com.google.android.gms.internal.ads.em0.e(Unknown Source:12)
at com.google.android.gms.ads.internal.ClientApi.o5(Unknown Source:6)
at l3.i.b(Unknown Source:16)
at l3.u.e(Unknown Source:5)
at l3.u.d(Unknown Source:79)
at l3.a3.p(Unknown Source:72)
at d3.l.b(Unknown Source:59)
at io.flutter.plugins.googlemobileads.q.e(Unknown Source:60)
at io.flutter.plugins.googlemobileads.h0.onMethodCall(Unknown Source:952)
at q9.k$a.a(Unknown Source:17)
at d9.c.l(Unknown Source:18)
at d9.c.m(Unknown Source:40)
at d9.c.i(Unknown Source:0)
at d9.b.run(Unknown Source:12)
at android.os.Handler.handleCallback(Handler.java:942)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:240)
at android.os.Looper.loop(Looper.java:351)
at android.app.ActivityThread.main(ActivityThread.java:8381)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:584)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1013)
Caused by: java.lang.reflect.InvocationTargetException
at java.lang.reflect.Method.invoke(Native Method)
at android.webkit.WebViewFactory.getProvider(WebViewFactory.java:355)
... 26 more
Caused by: WV.Tb0: errorCode=2
at WV.SR.f(chromium-SystemWebViewGoogle.aab-beta-579002110:84)
at WV.SR.g(chromium-SystemWebViewGoogle.aab-beta-579002110:25)
at org.chromium.android_webview.AwBrowserProcess.i(chromium-SystemWebViewGoogle.aab-beta-579002110:32)
at com.android.webview.chromium.WebViewChromiumFactoryProvider.(chromium-Syste<truncated: 639 chars>
at StandardMethodCodec.decodeEnvelope(message_codecs.dart:653)
at MethodChannel._invokeMethod(platform_channel.dart:315)
at BannerAd.load(ad_containers.dart:895)

Hi @kazeclans
Based on the stack trace, this crash seems to be reported from native sdk which is wrapped by this plugin. It could be caused by Google play service.
Moreover, I see there are some reports in google-admob-ads-sdk, see this filter. So please ask the same question there for more information if any.
Also, I would suggest you observe the percentage occurrence of the crash to see if it's increasing or only occurs sometime. Then back here with more information that may help us to verify the issue better. Thank you!


update: Alert feature added

I have created different alert types as Primary, Success, Warning, and Error alert

I would say that you create a CSS file for each component or branch. So, that it will be easy for us to review codes.

Ok I will look into it


Chef 13: Alert if someone uses Chef::Platform methods

Alert if someone uses Chef::Platform.provider_for_resource or Chef::Platform.find_provider should alert as these methods have been removed from Chef 13
https://docs.chef.io/deprecations_chef_platform_methods.html

wondering if this is necessary? chef client 12.39 will throw a warning and chef client 13 will fail in compilation phase ;)

Without a foodcritic test we have no way to analyze existing cookbooks on the Supermarket and no way for users on older chef clients to gauge the scope of work involved in an upgrade. The goal here is that every deprecation comes with a rule if it's possible to do so with static analysis.

FC087 handles these all now!


Sharp logging value "0" of type 'gint'

Sharp is logging
(sharp:24296): GLib-GObject-WARNING **: 23:51:19.397: value "0" of type 'gint' is invalid or out of range for property 'width' of type 'gint'

when we're passing an "empty" SVG.
It's technically a followup to #1

Those are the faulty lines
https://github.com/HKGx/rendertex/blob/4b5a8b7e7beed6b559b41780762eeaa0282f0b2a/src/index.ts#L86
https://github.com/HKGx/rendertex/blob/4b5a8b7e7beed6b559b41780762eeaa0282f0b2a/src/index.ts#L87
https://github.com/HKGx/rendertex/blob/4b5a8b7e7beed6b559b41780762eeaa0282f0b2a/src/index.ts#L88


Fix wolfictl dot

I'm not 100% confident that this is correct, but this has actually useful output now.
Fixes https://github.com/wolfi-dev/wolfictl/issues/344

Before:
wolfictl dot -D crane
2023/09/07 15:33:21 [DEBUG] GET https://packages.wolfi.dev/bootstrap/stage3/x86_64/APKINDEX.tar.gz
Error: package "crane" not found in graph
FATA[0001] error during command execution: package "crane" not found in graph

After:
wolfictl dot -D crane
2023/09/07 15:34:13 [DEBUG] GET https://packages.wolfi.dev/bootstrap/stage3/x86_64/APKINDEX.tar.gz
digraph images {
crane;
"binutils:2.41-r0@local";
crane -> "binutils:2.41-r0@local"
"busybox:1.36.1-r2@local";
crane -> "busybox:1.36.1-r2@local"
"ca-certificates-bundle:20230506-r0@local";
crane -> "ca-certificates-bundle:20230506-r0@local"
"go-1.21:1.21.1-r0@local";
crane -> "go-1.21:1.21.1-r0@local"
"scanelf:1.3.7-r0@local";
crane -> "scanelf:1.3.7-r0@local"
"wget:1.21.4-r0@local";
crane -> "wget:1.21.4-r0@local"
"k3s:1.27.5-r0@local";
"k3s:1.27.5-r0@local" -> crane
}


FEATURE:  Addional CSS files to load with the viewer for css variables & viewer customization

Is your feature request related to a problem? Please describe.
I'm currently working on syncing primevue's theme with tailwind. Primevue exports its entire color palette via  css variables, so all I need to do in my Tailwind Configuration is to set theme.colors to be overridden by primevue's css variables. However, when i open the viewer, it fails to show me the new colors since it doesn't have those variables set.
Describe the solution you'd like
it would be great if you could add a cssFiles option for this module so I could add primevue's css files (with the variables) and hence show the colors correctly.
In addition, it's a great chance to allow css modification to the viewer and better customization.
Describe alternatives you've considered
Disabling the viewer works because it can't really show the color palette properly
Additional context
Here's the not working version of the viewer after syncing primevue with tailwindcss:

Hi, thanks for opening an issue on this repository.
One of my Nuxt applications also uses PrimeVue along with this module, and I've worked intensely in getting the two integrated, so I'd quite like to look into this. I haven't had the chance to look at PrimeVue's latest update of allowing syncing with Tailwind (but it probably means my hours of writing custom PCSS to respect Tailwind have been made redundant), but I'm trying to understand your feature idea of cssFiles. From what I understand, Tailwind has an entry CSS file that you can specify in the configuration... within that, if you'd like to import PrimeVue's CSS (and as a layer), or use a Tailwind plugin, that would be sufficient if I'm not wrong? Perhaps you could provide a code snippet of what you'd mean. 🙂

Adding the css file through tailwind configuration is a great idea! thanks


Ambermini recipe md5 mismatch

I just realized (from looking at travis-ci errors) the updated ambermini recipe has an md5 mismatch:
Downloading https://github.com/choderalab/ambermini/archive/v.14.0.1.zip
Success
Error: MD5 mismatch: '527128edf03becedda26016a366cb9f1' != '4653df08b0f9d94a39704c10591fcd84'

Solved.


ERROR ITMS-90161: "Invalid Provisioning Profile. The provisioning profile included in the bundle com.company.app [Payload/App.app] is invalid

I have fastlane multiple times but once more I struggle with provisioning issues. I was hoping that cert and sigh would help me out here but it seems that I got something wrong again.
This is my Fastfile:
update_fastlane

fastlane_version "1.42.0"

default_platform :ios

platform :ios do

  desc "Submit a new Beta Build to Apple TestFlight"
  lane :beta do
    increment_build_number
    commit_version_bump
    push_to_git_remote
    cert(team_id: 'XXXXYYYY')
    sigh
    ENV["PROFILE_UDID"] = lane_context[SharedValues::SIGH_UDID]
    gym(scheme: 'App', use_legacy_build_api: true)
    pilot
  end
end

This is the log of my fastlane command:
https://gist.github.com/besi/2963f748d4b4130e0fcb
Essentially the output is:
[17:32:44]: ERROR ITMS-90161: "Invalid Provisioning Profile. The provisioning profile included in the bundle ch.b-labs.App [Payload/App.app] is invalid. [Missing code-signing certificate]. A Distribution Provisioning profile should be used when submitting apps to the App Store. For more information, visit the iOS Developer Portal."
[17:32:44]: Return status of iTunes Transporter was 1: ERROR ITMS-90161: "Invalid Provisioning Profile. The provisioning profile included in the bundle ch.b-labs.App [Payload/App.app] is invalid. [Missing code-signing certificate]. A Distribution Provisioning profile should be used when submitting apps to the App Store. For more information, visit the iOS Developer Portal."
[17:32:44]: ERROR ITMS-90161: "Invalid Provisioning Profile. The provisioning profile included in the bundle ch.b-labs.App [Payload/App.app] is invalid. [Missing code-signing certificate]. A Distribution Provisioning profile should be used when submitting apps to the App Store. For more information, visit the iOS Developer Portal."
Return status of iTunes Transporter was 1: ERROR ITMS-90161: "Invalid Provisioning Profile. The provisioning profile included in the bundle ch.b-labs.App [Payload/App.app] is invalid. [Missing code-signing certificate]. A Distribution Provisioning profile should be used when submitting apps to the App Store. For more information, visit the iOS Developer Portal."
[17:32:44]: Variable Dump:
[17:32:44]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios beta", :BUILD_NUMBER=>"2", :CERT_FILE_PATH=>"/Project/path/App/SSJAELD8CV.cer", :CERT_CERTIFICATE_ID=>"SSJAELD8CV", :SIGH_PROFILE_PATH=>"/Project/path/App/AppStore_ch.b-labs.App.mobileprovision", :SIGH_PROFILE_PATHS=>["/Project/path/App/AppStore_ch.b-labs.App.mobileprovision"], :SIGH_UDID=>"c14cbec9-eab3-4f4a-b5b5-6a87097d001a", :SIGH_PROFILE_TYPE=>"app-store", :IPA_OUTPUT_PATH=>"/Project/path/App/App.ipa", :DSYM_OUTPUT_PATH=>"/Project/path/App/App.app.dSYM.zip"}
[17:32:44]: Error uploading ipa file, more information see above

please submit an issue on GitHub and attach the following number to it:

37ebb90545ac2ccc0bc9f8891c7ccab8

I have not run into this problem specifically but it seems like cert and sigh complete successfully as well as gym to do the build. I noticed on the cert github project page it mentions passing the force option to force sigh to regenerate a provisioning profile with the currently installed signing certificate. You could give that a try.
From the project page:
lane :beta do
  cert
  sigh(force: true)
end

force: true will make sure to re-generate the provisioning profile on each run. This will result in sigh always using the correct signing certificate, which is installed on the local machine.

Could be worth a try.

I did try this but still get the error:

[09:42:28]: ERROR ITMS-90161: "Invalid Provisioning Profile. The provisioning profile included in the bundle ch.b-labs.LanguageStories [Payload/LanguageStories.app] is invalid. [Missing code-signing certificate]. A Distribution Provisioning profile should be used when submitting apps to the App Store. For more information, visit the iOS Developer Portal."
[09:42:28]: Return status of iTunes Transporter was 1: ERROR ITMS-90161: "Invalid Provisioning Profile. The provisioning profile included in the bundle ch.b-labs.LanguageStories [Payload/LanguageStories.app] is invalid. [Missing code-signing certificate]. A Distribution Provisioning profile should be used when submitting apps to the App Store. For more information, visit the iOS Developer Portal."

Sorry I couldn't be of more help. I am interested to see what the solution is too.
The only other suggestion I can think of is to review the code signing and provisioning profiles under your app's Build Settings in Xcode and make sure you have selected a distribution provisioning profile/certificate combination for Release builds.

Invalid Provisioning Profile. The provisioning profile included in the bundle ch.b-labs.LanguageStories [Payload/LanguageStories.app] is invalid. [Missing code-signing certificate]. A Distribution Provisioning profile should be used when submitting apps to the App Store. For more information, visit the iOS Developer Portal

The error message basically says that you used a Development Profile instead of a Distribution Profile.
I can only assume that the project's provisioning profile setting is set to Automatic or to something static instead of using the PROFILE_UDID value.
Also, check out match for more information about how to handle code signing.

@KrauseFx Do you know where I can find documentation on how to change the provisioning profile to something dynamic rather than Automatic?
I can't seem to figure out that out from the Code Signing Guide. Step 6 comes close but no details:
6. Your Xcode project must be configured to choose the provisioning profiles automatically or define it statically. The ideal solution is to pass the UUID of the provisioning profile, via an environment variable, for each of your bundle identifiers.

Thanks!

@KrauseFx Figured it out. I'm creating multiple configurations and setting the provisioning profile explicitly in each one.

It looks like there hasn’t been any recent activity on this issue in some time, so I’m closing it. If this is still a problem, feel free to re-open a new issue and I’d be happy to help :+1:


Responsive Image Size API

It's currently pretty burdensome to dynamically render srcset when rendering attachment images (i.e. images stored as WP posts), since you have to get the src for each crop size within the srcset declaration. For example, say you had custom-large, custom-medium, and custom-small sizes. To take advantage of these in srcset, you'd have to render the URL for each size, everywhere you use that image:

It would be great if instead I could declare these srcset widths upfront when I add each image size, and get the srcset attribute from a single call:
use Conifer\Image;

Image::add_size('custom-large', 1000, 500, true, [
  'srcset_width'  => '1000w',
]);
Image::add_size('custom-medium', 700, 350, true, [
  'srcset_width'  => '700w',
]);
Image::add_size('custom-small', 400, 200, true, [
  'srcset_width'  => '400w',
]);

Would also be great if the Image::srcset() method returned all declared crops by default, but filtered by widths when passed arguments:

Alternate proposal
After doing some research, I'm rethinking this a little. The above scheme doesn't integrate well with retina sizes, since the w descriptor (e.g. in /path/to/image-custom-large.jpg 1000w) precludes the ability to also render retina sizes using the x descriptor (e.g<EMAIL_ADDRESS>2x).
The only way to get "art direction," the fancy name for custom crops of different sizes, and retina at the same time is to use a <picture> element with media queries + srcset, like this:
<picture>
  <source
    media="(min-width: 1366px)"
    srcset="/pic.png 1x<EMAIL_ADDRESS>2x" />
  <source
    srcset="/pic-small.png 1x<EMAIL_ADDRESS>2x" />

</picture>

To that end, I propose an API that allows you to actually declare your breakpoints on the backend. This would allow for both types of responsiveness (pixel ratio and viewport width).
Example Time!
<?php

ResponsiveImage::add_breakpoint('mobile');
ResponsiveImage::add_breakpoint('tablet', '(min-width: 768px)');
ResponsiveImage::add_breakpoint('desktop', '(min-width: 1366px)');

ResponsiveImage::add_size('card-large', 1500, 750, [
  'breakpoint' => 'desktop',
  'context' => ['card'],
]);

ResponsiveImage::add_size('card-medium', 800, 400, [
  'breakpoint' => 'tablet',
  'context' => ['card'],
]);

ResponsiveImage::add_size('card-small', 500, 250, [
  'breakpoint' => 'mobile',
  'context' => ['card'],
]);

A special picture Twig filter would then be responsible for rendering a Timber\Image instance in a given rendering context (here, 'card'):
{{ Image(attachment_id) | picture({context: 'card'}) }}

With retina enabled, this would render:
<picture>
  <source
    media="(min-width: 1366px)"
    srcset="/pic-card-large.png 1x<EMAIL_ADDRESS>2x">
  <source
    media="(min-width: 768px)"
    srcset="/pic-card-medium.png 1x<EMAIL_ADDRESS>2x">
  <source
    srcset="/pic-card-small.png 1x<EMAIL_ADDRESS>2x">

</picture>


Advancing 0.10.0-rc1 release to status: released

Advancing 0.10.0-rc1 release to status: released

Shouldn't there be a Shipyard release already?
https://github.com/submariner-io/submariner-operator/releases


Add MultiSelect to FluentDataGrid

🙋 Feature Request
MultiSelect in FluentDataGrid would send multiple rows of data for bulk actions. Running the same action one row at a time would take a lot of time.
🤔 Expected Behavior
A user should be able to select multiple rows or deselect a selected row and be able to save the selected rows in a list that can be passed inside a method for bulk operation.
😯 Current Behavior
Currently you can only select one row, when you select another row, the previous row is no longer selected, and the data cannot be used anymore.
🔦 Context
I am migrating an existing application from the old blazor fluent nugget package to Blazor fast. I have a few grids that have a lot of rows. The rows are passed to a function that executes actions based on information that is passed from the row. A lot of rows need to be passed every day and every action needs sometimes to finish. It is better to pass multiple rows so that the action can run multiple times without the user needing to initiate it for every row and check if the previous row action is completed.

Official row selection including multiple row selection is in development now.  I saw a demo of it yesterday myself, including full keyboard support. 😄

Will it be part of the new nugget version? When will it be released?

The PR for selection in foundation is under review here: https://github.com/microsoft/fast/pull/5786 Once that is merged in, the Fluent UI Web Components will be updated, and then the Blazor wrappers.
@vnbaaij Can you review the PR to make sure there's a path to enable this quickly for Blazor? I'm not sure if we'll need to do special interop or if it will "just work".

The PR for selection in foundation is under review here: microsoft/fast#5786 Once that is merged in, the Fluent UI Web Components will be updated, and then the Blazor wrappers.
@vnbaaij Can you review the PR to make sure there's a path to enable this quickly for Blazor? I'm not sure if we'll need to do special interop or if it will "just work".

It is merged in! 😍

When will it be officially released?

You'd need to ask in the Fluent UI Web Components repo when this will be in their script..

since 2023 we are waiting for this 🤦♂

Come on guys...bit of a lame reaction. There are more important things in the world than just a bit of software.
You can go ask in the Fluent UI repo about the status but my guess is this won't come to the v2 (which we are using) version anymore...

but @vnbaaij  this is very very important Feature! we love Blazor we love Fluent UI we want to improve it and use it instead of
other components and you need you to support it so please be kind with issues and Feature requests 🙏

Well, we don't really need to do anything. This is 'just an open source project that we are maintaining (with love) as good as we can. It is not a funded Microsoft product for which you can open a support ticket.
I don't think it is fair to say we are not open to requests and unkind to issues. We're pretty responsive I believe. And sometimes 'no' is also an answer 😉.
If you wanttthis feature, make it know to where it needs tocome from, ie the web components. It helps if other people beside us are more vocal there.

if I create a pull request to add MultiSelect for FluentDataGrid with Branch shall I use?

We always work on the dev branch. main is where we merge to to build the release packages.

hahaha ok i will try a pull request ❤😅


Ali/genrl pr

This is the implementation of GenRL algorithm in Emote.

@tgolsson and @singhblom
I updated the code by changing the structure a bit. There is no need for GenRLPolicy and GenRLQNet anymore with the new implementation. We are re-using most of SAC code by only changing the action space into the latent space. A PolicyWrapper is implemented which maps the latent actions generated by the policy into the actions in the original action space and is passed to the AgentProxy. Please take a look at the code and let me know if you have any other comments.

Poke @tgolsson


Service is unreachable from outside

Is this a bug report or a feature request?:
Question
What happened:
I have a problem with accessible my service from outside.
First of all, here is my conf yaml files:
nginx-pod.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: my-nginx
  namespace: development
spec:
  selector:
    matchLabels:
      app: my-nginx
  replicas: 2
  template:
    metadata:
      labels:
        app: my-nginx
    spec:
      containers:
      - name: my-nginx
        image: nginx:1.7.9
        ports:
        - containerPort: 80

nginx-service.yaml

apiVersion: v1
kind: Service
metadata:
  name: nginx-service
  namespace: development
spec:
  type: LoadBalancer
  selector:
    app: my-nginx
  ports:
  - name: http
    port: 80
    targetPort: 80
    protocol: TCP

metallb-config.yaml

apiVersion: v1
kind: ConfigMap
metadata:
  namespace: metallb-system
  name: config
data:
  config: |
    address-pools:
    - name: default
      protocol: layer2
      addresses:
      - <IP_ADDRESS>-<IP_ADDRESS>

Then i have created my cluster. kubectl get all -o wide command prints:

NAME                            READY   STATUS    RESTARTS   AGE   IP            NODE         NOMINATED NODE
pod/my-nginx-5796dcf6c4-rxl6k   1/1     Running   1          20h   <IP_ADDRESS>   scw-7d6c86
pod/my-nginx-5796dcf6c4-zf7vd   1/1     Running   0          20h   <IP_ADDRESS>    scw-7a7908

NAME                    TYPE           CLUSTER-IP      EXTERNAL-IP    PORT(S)        AGE   SELECTOR
service/nginx-service   LoadBalancer   <IP_ADDRESS>   <IP_ADDRESS>   80:30883/TCP   54m   app=my-nginx

NAME                       DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE   CONTAINERS   IMAGES        SELECTOR
deployment.apps/my-nginx   2         2         2            2           20h   my-nginx     nginx:1.7.9   app=my-nginx

NAME                                  DESIRED   CURRENT   READY   AGE   CONTAINERS   IMAGES        SELECTOR
replicaset.apps/my-nginx-5796dcf6c4   2         2         2       20h   my-nginx     nginx:1.7.9   app=my-nginx,pod-template-hash=5796dcf6c4

Everythink is fine, also kubectl describe service/nginx-service prints:

Name:                     nginx-service
Namespace:                development
Labels:
Annotations:
Selector:                 app=my-nginx
Type:                     LoadBalancer
IP:                       <IP_ADDRESS>
LoadBalancer Ingress:     <IP_ADDRESS>
Port:                     http  80/TCP
TargetPort:               80/TCP
NodePort:                 http  30883/TCP
Endpoints:                <IP_ADDRESS>:80,<IP_ADDRESS>:80
Session Affinity:         None
External Traffic Policy:  Cluster
Events:
  Type    Reason       Age   From                Message
  ----    ------       ----  ----                -------
  Normal  IPAllocated  56m   metallb-controller  Assigned IP "<IP_ADDRESS>"

Curl command inside master server curl <IP_ADDRESS> prints Welcome to nginx blablabla.
Next i tried to open from another network, it doesn't work, however i added node port it works curl <IP_ADDRESS>:30883.  All this i do on a bare-metal.
What did i do wrong?
What you expected to happen:
curl <IP_ADDRESS> from any host should return content. Right now it unreachable.
Thanks.
Environment:

MetalLB version: v0.7.3
Kubernetes version: v1.12.3
BGP router type/version: -
OS (e.g. from /etc/os-release): Debian GNU/Linux 9 (stretch)
Kernel (e.g. uname -a): Linux scw-7d6c86 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u6 (2018-10-08) x86_64 GNU/Linux

Your setup look correct to me. I think that your external box is not sending an ARP at all. If you access through a router it should work, but if you try to access from a Linux box attached to the k8s net you might have to do something like;
ip route add <IP_ADDRESS>/32 dev eth1

assuming yous k8s network is on eth1. This tells the Linux kernel to send arp on eth1 even though the address is not on any subnet assigned to eth1.

Sorry, but I no longer have the time to debug MetalLB deployments for people. I want to keep this tracker specifically for bugs and features, so I'm going to close this. At some point I may have time to write general troubleshooting documentation, but as a first step towards that I need to clear up the issue tracker.
You could try asking for help on the #metallb channel on the Kubernetes slack, where there are people other than me who can assist.

If it's Scaleway: Incoming traffic to VM's are sent to the private IP address, not the external one. In other words, you must use ens2 interface ip addresses. And curl to a public IP address as you did before.
thanks to this tutorial


Bolivia holidays update

Coverage: 100.0%. Remained the same when pulling 74c49983b31de0086defccc5598ac86654100827 on KJhellico:upd-bolivia into 2384bcc70618fccb41d047580abb9e8925bfba6b on dr-prodigy:beta.

Nice refactoring!

Nicely done!


| Backspace String Compare | C++

Backspace String Compare -
What will change - A new well documented and efficient code using STACKS (as Data Structure) will be added.
Type of Issue -
Please add/delete options that are not relevant.

[x] Adding New Code

Programming Language
Please add/delete options that are not relevant.

[x] C++

Self Check

Ask for issue assignment and wait to get assigned to it before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Discord server ✉ - https://discord.gg/CXksGdn
Happy Coding,

Please assign it to me

Please assign this issue to me.


Add automated builds, testing

title

oooh yeah, that's easy.

Is the current automation work for builds and what did you mean by testing? Thanks.

Hey, this is not actually completed. There are still no automated tests.

How could we go about automating testing? All we can really does is syntax tests

What do you mean by syntax tests? I believe there is nothing preventing tests to be created, I just didn't really have the time to do it yet.


create user-configuration failed

the function getAuthKeys in userconfigaction.py does not work for me. The length of my username is 7. With password the same.

Fixed. Username length not limited anymore. (could handle the NEW type usernames)


Force newer version of Eclipse core transitive dependency (resolves CVE-2023-4218)

Description
The Spotless Gradle Plugin brings in a transitive dependency on Eclipse Core Runtime 3.26.100.  That version is impacted by a CVE.
This forces the newest version, currently 3.29.0.  Note that newer versions than 3.26 require JDK17+ to run spotless.
Issues Resolved
Fixes #3688
Check List

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

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

Thanks @dbwiddis looks good to me!

FYI, the Whitesource Security check failed here: https://github.com/opensearch-project/security/pull/3737/checks?check_run_id=18799318680 which indicates the "newest" version is still vulnerable.  But that doesn't seem to be the case as the newest Eclipse version is allegedly not vulnerable....
In any case, explicitly specifying the version should allow auto-updates in the future.

The CVE entry points to this as a commit resolving it which indicates 3.29.0 "fixes" it... https://github.com/eclipse-platform/eclipse.platform.ui/commit/f243cf0a28785b89b7c50bf4e1cce48a917d89bd

Aha, here's the specific line in https://www.cve.org/CVERecord?id=CVE-2023-4218

Vendor Eclipse Foundation
Product org.eclipse.core.runtime
Versions affected from 0 before 3.29.0

I interpret "before" as < .... so I hope that failed check is a false positive and 3.29.0 is resolved.

And not only do I interpret it that way, the CVE record linked above is very clear about what the "before" syntax means:

Examples:
affected from 5.0 before 6.0 (affected version doesn’t include 6.0)

This would mean the "affected version doesn't include 3.29.0" so I do not understand why Mend is alerting on it.  (It opened a new issue here: https://github.com/opensearch-project/opensearch-ai-flow-framework/issues/177)


The paging file is too small for this operation to complete

Comment:
We have a simple test in meta.yml for running Modin on Ray.
python -c "import modin.pandas as pd, modin.config as cfg; cfg.Engine.put('Ray'); df = pd.DataFrame([])"

While it works on Linux, it raises the error on Windows in CI.
OSError: [WinError 1455] The paging file is too small for this operation to complete

Example: https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=859318&view=logs&j=171a126d-c574-5c8c-1269-ff3b989e923d&t=623c2ba8-c4f1-582d-6c78-1c7699e2e0a2&l=3403

Changing the line
python -c "import modin.pandas as pd, modin.config as cfg; cfg.Engine.put('Ray'); df = pd.DataFrame([])"

to
python -c "import ray; ray.init()"

works fine.

See this comment

Closed in #115.


Implement new existing badges

List of some emblems ->
Common Badges:

Rare Badges:

Unobtainable Badges:

Other Badges:

I ended up finding other emblems, but I don't know if it's real:

Source: https://discord.fandom.com/wiki/Badges

@Putt0 It would be a great idea, but these emblems probably already exist.

It would be a great idea!! maybe people will implement

Great idea, however this is not something Lanyard itself needs to do anything to implement, as we forward the data directly from discords gateway, so I'm gonna close this as it's not really an "issue".
If you use an integration that gets it data from the Lanyard API which doesn't support one or more of these badges, you should find the repo for it specifically (Likely it'll be listed in the projects section of the readme) and contribute or give them feedback over there!


ID tar number reverse!

Hello, thankyou to share your work!
Questions:

This lib return the number in reverse mode, (compared to other libs) for example

Wiegan 26)
Other libraries return 18DB32 and your lib return  32DB18
Its possible reverse this?

The wiegan mode, 4, 8, 26, 34 its auto? or requiere change the code?

How its the correct mode to assign  the id number into one var? Its possible write and code example?

Thankyou for all!

Hello, thank you for the feedback!

This is weeeeird!
I'll have to double check when I have a device with me, but I didn't notice any problem like that before.
Can you point me to this other library so that I can test it?

It defaults to automatically detecting the number of bits.
If you know the number of bits ahead of time, you can set it on wiegand.begin(n_bits).
Manually specifying the number of bits is a little bit more responsive, since the auto detection has to wait for while before deciding that all bits have been received.

I'm not sure I understood the question, do you want to copy the wiegand data into a global variable?

uint8_t latest_wiegand_data[Wiegand::MAX_BYTES];
uint8_t latest_wiegand_bits = 0;

void receivedData(uint8_t* data, uint8_t bits, const char* message) {
    uint8_t bytes = (bits+7)/8;
    memcpy(latest_wiegand_data, data, bytes);
    latest_wiegand_bits = bits;
}

Or, as a string:
const char* hex_chars = "01234567890ABCDEF"

uint8_t latest_wiegand_str[2*Wiegand::MAX_BYTES + 1]; //+1 for \0

void receivedData(uint8_t* data, uint8_t bits, const char* message) {
    uint8_t bytes = (bits+7)/8;
    //Print value in HEX
    uint8_t bytes = (rawBits+7)/8;
    for (int i=0; i<bytes; i++) {
        latest_wiegand_str[2*i   ] = hex_chars[rawData[i] >> 4];
        latest_wiegand_str[2*i + 1] = hex_chars[rawData[i] & 0xF];
    }
    latest_wiegand_str[bytes] = '\0';
}

(I haven't tested either of these, but the idea should be valid)

Hi,
The lib I refer to is this:
https://github.com/ugge75/Wiegand-V3-Library-for-all-Arduino
Thank you very much for your answers,
I will try the code that has happened to me!
Thanks again!

Hello again, as far as my first question is concerned, do not worry at all, it was not the library that my reader was configured like that. sorry!

Ah! Glad you found the issue, but really puzzled me

Hello again, with the code that happened to me, I managed to get the bits, but the ID of the card could tell me how can I store the ID of the card in a variable?
Your Lib example code return me: Card readed: 24bits / 18DB32
I need Isolate the 18DB32  in one var as String or any other inbound code whatever the bit format.
void receivedData(uint8_t* data, uint8_t bits, const char* message) {     Serial.print(message);     Serial.print(bits);     Serial.print("bits / ");     //Print value in HEX     uint8_t bytes = (bits+7)/8;     for (int i=0; i<bytes; i++) {         Serial.print(data[i] >> 4, 16);         Serial.print(data[i] & 0xF, 16);     }     Serial.println(); }
Could you help me?
Thankyou!

Hello,
I sent you a snippet to store it as a String, didn't it work?
const char* hex_chars = "01234567890ABCDEF"

uint8_t latest_wiegand_str[2*Wiegand::MAX_BYTES + 1]; //+1 for \0

void receivedData(uint8_t* data, uint8_t bits, const char* message) {
    uint8_t bytes = (bits+7)/8;
    //Print value in HEX
    uint8_t bytes = (rawBits+7)/8;
    for (int i=0; i<bytes; i++) {
        latest_wiegand_str[2*i   ] = hex_chars[rawData[i] >> 4];
        latest_wiegand_str[2*i + 1] = hex_chars[rawData[i] & 0xF];
    }
    latest_wiegand_str[bytes] = '\0';
}

I suppose I did not know how to implement it, I will insist and I will tell you something.
Thank you so much

Well, I do not get it, multiple type errors, and when I can not make mistakes, never get the card number.
I am starting from the sample code of the library's "polling" page.
void receivedData(uint8_t* data, uint8_t bits, const char* message) {
Serial.print(message);
Serial.print(bits);
Serial.print("bits / ");
uint8_t bytes = (bits+7)/8;
for (int i=0; i<bytes; i++) {
    Serial.print(data[i] >> 4, 16);
    Serial.print(data[i] & 0xF, 16);
}
Serial.println();

}

Well, even though I try it, there is no way, to be sure that the code that sent me funcioina? Could i try it?


Refs must have owner warning only triggering in production

Can you reproduce the problem with latest npm?
Yes
Description
According to the docs refs should only be assigned inside a component's render() method. I didn't know this and created a composed component inside the constructor, assigning its ref there.
Testing with npm start runs without any errors or warnings, but running the production build after
npm run build
serve -s build
Produced an error and the rest of the application stopped working.
Expected behavior
npm start should also give the same error. I expect if the development application works then the production one will as well.
Actual behavior
No error or warning under npm start.
Environment
Run these commands in the project folder and fill in their results:

npm ls react-scripts (if you haven’t ejected<EMAIL_ADDRESS>node -v: v6.9.4
npm -v: 3.10.10

Then, specify:

Operating system: Windows 10 Home Version 1607
Browser and version: Google Chrome 58.0.3029.110 (64-bit)

Reproducible Demo
See project: https://github.com/LemonPi/cra-refs-bug with a readme on what it demonstrates
See deployed version that errors out: https://lemonpi.github.io/cra-refs-bug/ or npm run build and serve -s build

Hi! Thanks so much for this bug report & reproducible demo!
This seems to be an underlying issue with React, could you please report the issue there 😄?

Going to close as unrelated to CRA.


Improve and unify image checks and allow black images as input

(This is kind of a follow-up to PR17.)
Currently, the library behaves as follows:
import urllib.request
import cv2

from retinaface import RetinaFace

urllib.request.urlretrieve("https://i.imgur.com/Xr132lX.png", "blue_ish_image.png")
urllib.request.urlretrieve("https://i.imgur.com/Tk6xrDR.png", "white_image.png")
urllib.request.urlretrieve("https://i.imgur.com/jmIMMHT.png", "dark_gray_image.png")
urllib.request.urlretrieve("https://i.imgur.com/pobfmE0.png", "black_image.png")

RetinaFace.detect_faces("blue_ish_image.png")  # OK
RetinaFace.detect_faces("white_image.png")  # OK
RetinaFace.detect_faces("dark_gray_image.png")  # OK
RetinaFace.detect_faces("black_image.png")  # OK

RetinaFace.detect_faces(cv2.imread("blue_ish_image.png"))  # OK
RetinaFace.detect_faces(cv2.imread("white_image.png"))  # OK
RetinaFace.detect_faces(cv2.imread("dark_gray_image.png"))  # OK
RetinaFace.detect_faces(cv2.imread("black_image.png"))  # ValueError: Invalid input. Accept only path to image file or a NumPy array.

To me, as a user, the last line throwing an exception instead of returning a normal ("no face found") result, is somewhat surprising, because:

Providing a pre-loaded image results in different behavior compared to letting the library load the same image.
Providing a pre-loaded black image behaves differently compared to providing a pre-loaded gray (or whatever) image.

This Pull request fixed this, by no longer treating black images differently from other images, and by unifying the image checks independently of how the image was loaded (user code or library code).
The img_path.any() check was kept after PR16, I guess because it provides a safety net for blocking empty images, i.e., images without any pixels, since numpy.any() works as follows:

numpy.any([1,2]) -> True
numpy.any([0,1]) -> True
numpy.any([]) -> False
numpy.any([0,0]) -> False

I.e., it only evaluates to False if no element in the array evaluates to True.
So case 3 is likely the intention behind its usage, but case 4 is the unwanted side effect concerning black images input.
The new check keeps the security of blocking empty images but removes the unwanted side effect. Additionally, it increases safety by checking the number of image channels matching the format needed by the model's input layer. :slightly_smiling_face:

thank you for your contribution :)


Fix nb_lines computation when multiple pages on nanos

(cherry picked from commit c9417b642481255a69afd7f9358e253f981b7e7d)
Changes include

[x] Bugfix (non-breaking change that solves an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (change that is not backwards-compatible and/or changes current functionality)
[ ] Tests
[ ] Documentation
[ ] Other (for changes that might not fit in any category)

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

Please upload report for BASE (API_LEVEL_20@f8818f0). Learn more about missing BASE report.

Additional details and impacted files
@@               Coverage Diff               @@
##             API_LEVEL_20     #695   +/-   ##
===============================================
  Coverage                ?   60.54%
===============================================
  Files                   ?       12
  Lines                   ?     1726
  Branches                ?        0
===============================================
  Hits                    ?     1045
  Misses                  ?      681
  Partials                ?        0

Flag
Coverage Δ

unittests
60.54% <ø> (?)

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

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


Block execution result: IncorrectStateMerkleTree

Description
Launch multiple nodes and sent lot of transactions continuous, and then launch one FullNode, during sync up block process, we got lot of "Incorrect merkle trees" warn message.
[2018-10-26 08:48:03.897 - Trace - Peer][8]: [<IP_ADDRESS>:6800] peer height increased: 467.
[2018-10-26 08:48:03.908 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.908 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.908 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.908 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.913 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.913 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.913 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.913 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.913 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.913 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.913 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.913 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.913 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.913 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.913 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.913 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.913 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.913 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.913 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.915 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.915 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.915 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.915 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.915 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.915 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.915 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.915 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.915 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.915 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.915 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.915 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.915 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.915 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.915 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.915 - Trace - MessageReader][10]: Received packet : 17, length : 20148.
[2018-10-26 08:48:03.915 - Trace - MessageReader][10]: Received last packet: 36, total length: 712210.
[2018-10-26 08:48:03.951 - Warn - BlockExecutor][11]: ExecuteBlock - Incorrect merkle trees.
[2018-10-26 08:48:03.959 - Trace - BlockSynchronizer][20]: Block execution result: IncorrectStateMerkleTree
[2018-10-26 08:48:03.959 - Trace - BlockValidationService][20]: Result of BlockValidationFilter: Success - da68a01d4a36d4f7387fa14f091eb9afb48d81ba32237d21870acc83a1e91722
[2018-10-26 08:48:03.959 - Trace - BlockValidationService][20]: Result of ChainContextValidationFilter: Success - da68a01d4a36d4f7387fa14f091eb9afb48d81ba32237d21870acc83a1e91722
[2018-10-26 08:48:04.133 - Trace - BlockValidationService][20]: Result of ConsensusBlockValidationFilter: Success - da68a01d4a36d4f7387fa14f091eb9afb48d81ba32237d21870acc83a1e91722
[2018-10-26 08:48:04.133 - Trace - BlockSynchronizer][20]: Valid Block da68a01d4a36d4f7387fa14f091eb9afb48d81ba32237d21870acc83a1e91722.
[2018-10-26 08:48:04.133 - Trace - BlockSet][20]: Added block da68a01d4a36d4f7387fa14f091eb9afb48d81ba32237d21870acc83a1e91722 to invalid block list.
[2018-10-26 08:48:04.137 - AElfDPoS]Update - Sync dpos info of round 305 succeed..
[2018-10-26 08:48:04.313 - Warn - BlockExecutor][13]: ExecuteBlock - Incorrect merkle trees.
[2018-10-26 08:48:04.313 - Trace - BlockSynchronizer][14]: Block execution result: IncorrectStateMerkleTree
[2018-10-26 08:48:04.313 - Trace - BlockValidationService][14]: Result of BlockValidationFilter: Success - da68a01d4a36d4f7387fa14f091eb9afb48d81ba32237d21870acc83a1e91722
[2018-10-26 08:48:04.313 - Trace - BlockValidationService][14]: Result of ChainContextValidationFilter: Success - da68a01d4a36d4f7387fa14f091eb9afb48d81ba32237d21870acc83a1e91722
[2018-10-26 08:48:04.557 - Trace - BlockValidationService][14]: Result of ConsensusBlockValidationFilter: Success - da68a01d4a36d4f7387fa14f091eb9afb48d81ba32237d21870acc83a1e91722
[2018-10-26 08:48:04.557 - Trace - BlockSynchronizer][14]: Valid Block da68a01d4a36d4f7387fa14f091eb9afb48d81ba32237d21870acc83a1e91722.
[2018-10-26 08:48:04.557 - Trace - BlockSet][14]: Added block da68a01d4a36d4f7387fa14f091eb9afb48d81ba32237d21870acc83a1e91722 to invalid block list.
[2018-10-26 08:48:04.565 - AElfDPoS]Update - Sync dpos info of round 306 succeed..
[2018-10-26 08:48:04.572 - Info - Peer][8]: Receive block 7744ce620e1bfdb65528bee71b50f435a763ce7684c6f4cd3c47872a944b0aed at height 467.
[2018-10-26 08:48:04.611 - Trace - Node][13]: Receive block of height 467 - 7744ce620e1bfdb65528bee71b50f435a763ce7684c6f4cd3c47872a944b0aed
[2018-10-26 08:48:04.657 - Trace - BlockValidationService][13]: Result of BlockValidationFilter: Success - 7744ce620e1bfdb65528bee71b50f435a763ce7684c6f4cd3c47872a944b0aed
[2018-10-26 08:48:04.661 - Trace - BlockValidationService][13]: Result of ChainContextValidationFilter: Pending - 7744ce620e1bfdb65528bee71b50f435a763ce7684c6f4cd3c47872a944b0aed
[2018-10-26 08:48:04.747 - Warn - BlockExecutor][16]: ExecuteBlock - Incorrect merkle trees.
[2018-10-26 08:48:04.747 - Trace - BlockSynchronizer][20]: Block execution result: IncorrectStateMerkleTree
[2018-10-26 08:48:04.747 - Trace - BlockValidationService][20]: Result of BlockValidationFilter: Success - da68a01d4a36d4f7387fa14f091eb9afb48d81ba32237d21870acc83a1e91722
[2018-10-26 08:48:04.747 - Trace - BlockValidationService][20]: Result of ChainContextValidationFilter: Success - da68a01d4a36d4f7387fa14f091eb9afb48d81ba32237d21870acc83a1e91722
[2018-10-26 08:48:04.935 - Trace - BlockValidationService][20]: Result of ConsensusBlockValidationFilter: Success - da68a01d4a36d4f7387fa14f091eb9afb48d81ba32237d21870acc83a1e91722
[2018-10-26 08:48:04.935 - Trace - BlockSynchronizer][20]: Valid Block da68a01d4a36d4f7387fa14f091eb9afb48d81ba32237d21870acc83a1e91722.
[2018-10-26 08:48:04.935 - Trace - BlockSet][20]: Added block da68a01d4a36d4f7387fa14f091eb9afb48d81ba32237d21870acc83a1e91722 to invalid block list.
[2018-10-26 08:48:04.943 - AElfDPoS]Update - Sync dpos info of round 307 succeed..
[2018-10-26 08:48:04.944 - Trace - BlockValidationService][13]: Result of ConsensusBlockValidationFilter: Success - 7744ce620e1bfdb65528bee71b50f435a763ce7684c6f4cd3c47872a944b0aed

It is because no transaction in block in most time.

Close due to fixed.


Version 3.4.6

Fixing allowing frozen boxes to be deep copyable (thanks to jandelgado)

Coverage increased (+0.6%) to 100.0% when pulling 0cfa5f5480acdeaf8f205fbc8accba7f65eec07a on development into f113d155631c8ade1dd98e1413dc82611c82e544 on master.


Kafka Injest: Not obeying: ioConfig.consumerProperties -> isolation.level = read_uncommitted

Affected Version
0.20.1
Description
We have an interesting issue that we've tracked to the transactional nature of production.  The real error that seems occurs (which halts the entire ingest forever, and there's no way to skip it which is unfortunate in it's own)
the back trace is
2021-02-23T22:50:44,663 ERROR [task-runner-0-priority-0] org.apache.druid.indexing.seekablestream.SeekableStreamIndexTaskRunner - Encountered exception while running task.
org.apache.kafka.common.KafkaException: Received exception when fetching the next record from test_infra_infrabus_event-50. If needed, please seek past the record to continue consumption.
	at org.apache.kafka.clients.consumer.internals.Fetcher$CompletedFetch.fetchRecords(Fetcher.java:1577) ~[?:?]
	at org.apache.kafka.clients.consumer.internals.Fetcher$CompletedFetch.access$1700(Fetcher.java:1432) ~[?:?]
	at org.apache.kafka.clients.consumer.internals.Fetcher.fetchRecords(Fetcher.java:684) ~[?:?]
	at org.apache.kafka.clients.consumer.internals.Fetcher.fetchedRecords(Fetcher.java:635) ~[?:?]
	at org.apache.kafka.clients.consumer.KafkaConsumer.pollForFetches(KafkaConsumer.java:1283) ~[?:?]
	at org.apache.kafka.clients.consumer.KafkaConsumer.poll(KafkaConsumer.java:1237) ~[?:?]
	at org.apache.kafka.clients.consumer.KafkaConsumer.poll(KafkaConsumer.java:1210) ~[?:?]
	at org.apache.druid.indexing.kafka.KafkaRecordSupplier.poll(KafkaRecordSupplier.java:124) ~[?:?]
	at org.apache.druid.indexing.kafka.IncrementalPublishingKafkaIndexTaskRunner.getRecords(IncrementalPublishingKafkaIndexTaskRunner.java:98) ~[?:?]
	at org.apache.druid.indexing.seekablestream.SeekableStreamIndexTaskRunner.runInternal(SeekableStreamIndexTaskRunner.java:603) ~[druid-indexing-service-0.20.1.jar:0.20.1]
	at org.apache.druid.indexing.seekablestream.SeekableStreamIndexTaskRunner.run(SeekableStreamIndexTaskRunner.java:267) [druid-indexing-service-0.20.1.jar:0.20.1]
	at org.apache.druid.indexing.seekablestream.SeekableStreamIndexTask.run(SeekableStreamIndexTask.java:145) [druid-indexing-service-0.20.1.jar:0.20.1]
	at org.apache.druid.indexing.overlord.SingleTaskBackgroundRunner$SingleTaskBackgroundRunnerCallable.call(SingleTaskBackgroundRunner.java:451) [druid-indexing-service-0.20.1.jar:0.20.1]
	at org.apache.druid.indexing.overlord.SingleTaskBackgroundRunner$SingleTaskBackgroundRunnerCallable.call(SingleTaskBackgroundRunner.java:423) [druid-indexing-service-0.20.1.jar:0.20.1]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_275]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_275]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_275]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_275]
Caused by: org.apache.kafka.common.InvalidRecordException: Incorrect declared batch size, records still remaining in file
2021-02-23T22:50:44,672 INFO [task-runner-0-priority-0] org.apache.druid.indexing.worker.executor.ExecutorLifecycle - Task completed with status: {
  "id" : "xxxx_316d619204b9ebf_bljepncn",
  "status" : "FAILED",
  "duration" : 236717,
  "errorMsg" : "org.apache.kafka.common.KafkaException: Received exception when fetching the next record from test_i...",
  "location" : {
    "host" : null,
    "port" : -1,
    "tlsPort" : -1
  }
}

The hunch is that this may be an aborted production transaction upstream.  Hard to say the exact cause (could also be some Compression issues causing some truncation of something).  In any case in an effort to see if it was a transaction sort of thing,  isolation.level = read_uncommitted was set however, it is not obeyed in the downstream peons.
... a log from the peon
the druid spec log shows

"consumerProperties" : {
      "bootstrap.servers" : "test-infra-kf.di.infra-prod.asapp.com:9092",
      "group.id" : "test-infrabus-druid-minute-1",
      "auto.offset.reset" : "earliest",
      "max.partition.fetch.bytes" : 10485760,
      "fetch.max.bytes" : 52428800,
      "isolation.level" : "read_uncommitted"
    },

.. the log of the kafka-properties of the peon shows

allow.auto.create.topics = true
	client.id = consumer-kafka-supervisor-oaiankjn-1
	client.rack =
	connections.max.idle.ms = 540000
	default.api.timeout.ms = 60000
	enable.auto.commit = false
	exclude.internal.topics = true
	fetch.max.bytes = 52428800
	fetch.max.wait.ms = 500
	fetch.min.bytes = 1
	group.id = kafka-supervisor-oaiankjn
	group.instance.id = null
	heartbeat.interval.ms = 3000
	interceptor.classes = []
	internal.leave.group.on.close = true
	internal.throw.on.fetch.stable.offset.unsupported = false
	isolation.level = read_committed
...

great ... can you point me to some way to "skip" these sorts of errors (or some config/api to skip a block of offsets, one can typically do this with pure kafka consumer groups, but in druid i'm unsure how .. i've tried manually moving the offsets in the backing DB, but that just created a hash issue and crashed everything)? At the moment the peon that has the effect partition basically is in a crash loop and never gets past things w/o a hard rest moving the offsets to the end of the topic.

I have never seen such an error thrown by Kafka. From the stack trace message, it seems that the a record stored at Kafka broker side is broken.
Since Druid manages the offsets where it consumes from Kafka, I think maybe one way is to reset supervisor to the latest offset.

Yea it's a "new one to me" as well.  We have a myriad of other consumers on that topic doing just fine, with no errors to speak of, but all of them are "read_uncommited" style consumers (which is what makes me think it's something about an aborted transaction)
Yes the reset "works" for a spell, but then it will appear again on another offset.

If your assumption is right, maybe there's some bug at Kafka broker side. I think you could seek some help from Kafka community to see what this exception is.

I've caused similar bugs in the past while testing failure handling with Flink and similar systems. The default Kafka consumer, which Druid and most other projects use under the hood, intentionally blocks forever when it encounters invalid records. I've worked around this in the past by just blindly advancing offsets until we re-encountered parseable offsets, but that was in a context without strict guarantees. Druid could implement a similar solution (probably in SeekableStreamIndexTaskRunner, judging by the stack trace, but I haven't looked at the code). The tricky part will be supporting multiple different delivery semantics. Hopefully your intuition is right and standardizing the isolation level works for you, but until then manually advancing the offsets (either by resetting the supervisor to the latest offsets and thus dropping data or by altering the backing offsets in the metadata store) is probably your only option.

Hi @JulianJaffePinterest , do you know why and when this exception comes out ? I don't know whether it's a bug of Kafka broker.

When I've seen similar errors, it was while testing killing or partitioning consumers mid-write. Those errors were mostly invalid offsets and the like, not this incorrect declared batch size error. There's almost certainly something that's a bug here, but I'm not sure if it's in Wyndham's producer code (and the bug just wasn't noticed before because the consumers were reading uncommitted), Kafka itself, or Druid. I'd guess 1 and 3 are more likely than 2 but you never know.

Yes i don't think this is a druid issue, as the error originates in the kafka client itself.  However if the issue is in the producer or brokers, is harder to say.  I was looking for a way to "skip" the offending offsets.  The issue being that if there are multiple peons (say 8) consuming the stream it only effects one of of the peons, and one of the partitions in that peon group, meaning the partitions it has been assigned get very far behind very fast, while the others move along.  Resetting the offsets to "latest" is the only option current, but that will mean 1/8th of the partitions are basically very far behind while the others are not, and of course a slew of data i missed depending on the message rate.
I was looking for a way to manually "skip" offsets, i tried the suggestion of altering the backing offsets in the metadata store from @JulianJaffePinterest, however there's a lock and a hash associated w/ the values stored, and so resetting them by hand caused even more trouble (all peons crashed and i was forced to move reset everything).
So aside from wanting isolation.level = read_uncommitted perhaps another thing that's needed is a easy way to properly move offsets.  I can see this being a useful thing in general, especially if producers make "other mistakes" (like KF message version that are incorrect, bad encodings, using compression that's unsupported, etc)

Ah yeah trying to adjust offsets while ingestion is running would be difficult. I do it by suspending the supervisor, adjusting the offsets, and restarting the supervisor (e.g. delaying across all partitions, but avoids data loss). Druid could automate some of this (even to the level of having the seekable stream seek over corrupt partitions automatically), but that violates some of the guarantees Druid makes around delivery.


bug: reconcile loop with replicasets

Let's say I want to update the template for a replicaset:
When(a.ReplicaSet)
  .IsCreated()
  .Then(async req => {
    req.Raw.spec.template.metadata.annotations["spanny"] = "test";
  });

Kubernetes will keep creating new replicasets. The use case for this is to have the same flow for daemonsets, statefulsets, and deployments

version 0.9.0

not really best practices, should be done at the pod level. I'm going to close this.


move fernet creation to helper method

This change moves the fernet creation to a helper method in order to make it easier to either encrypt or decrypt values in the config/cache file. The motivation for this change is to make it easier to debug issues or to re-use OAuth tokens obtained outside the proxy.

The added commit should address https://github.com/simonrob/email-oauth2-proxy/pull/198#discussion_r1359926540, but I left it as a separate commit in case the change should be backed out from this PR.

One thing that may not be obvious is that you can actually set the token_iteration in the config to a value larger than what the script provides. As is, as long as the original iterations value is either Cryptographer.ITERATIONS or Cryptographer.LEGACY_ITERATIONS then they will be tried as fallbacks and the value in the config would be re-written since it would be the primary fernet.
This could support a previous iterations value by allowing the Cryptographer to have a fallback_iterations passed to its constructor, and one could rotate the config manually but even that could be moved to its own function to allow a user to easily force higher values and move between them.

I edited a few comments and removed an unnecessary ValueError check (if fallback is specified this doesn't happen). I think this is good to go?


Feat/ce 310

Description
Please provide a summary of the change and the issue fixed. Please include relevant context. List dependency changes.
Fixes # (issue)
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist

[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Further comments

Thanks for the PR!
Any successful deployments (not always required) will be available below.
Backend available
Frontend available
Once merged, code will be promoted and handed off to following workflow run.
Main Merge Workflow

@cnesmithsalus - I'm able to introduce a bug via the following:

Add 2 Animals
Delete Animal 1
Add a new animal
Delete Animal 1

At this point both animals 1 and 2 are removed

@cnesmithsalus - I'm able to introduce a bug via the following:

Add 2 Animals
Delete Animal 1
Add a new animal
Delete Animal 1

At this point both animals 1 and 2 are removed

Back to you once github actions done

@cnesmithsalus - One regression item... after you add two ear tags the 'Add Ear Tag' button should no longer be available
One new item... the label on the button for the confirmation says "Equipment" instead of "animal outcome"

@afwilcox Regression fixes complete


Update cli-build-system.md

Fix some wording/typos.
Signed-off-by: Feanil Patel<EMAIL_ADDRESS>

Hi! CI is complaining about formatting, you may want to run yarn prettier --write docs/local-dev/cli-build-system.md in your project root.

Ah, sorry about that, did the edit in the github UI so missed that check. Should be resolved now.

Thanks for your contribution @feanil 🙌 Please let me know if you’d like some help to contribute further.


Can't migrate from Docker Compose setup to Portainer

Hello,
I've been successfully running an ARK server using the azixus/ark-ascended-docker image with Docker Compose for several months. However, for simplicity, I've been trying to migrate my setup to Portainer.
I have adapted my docker-compose.yml for use in Portainer as follows:
version: '3'

services:
  asa_server:
    tty: true
    restart: unless-stopped
    image: azixus/ark-ascended-docker
    volumes:
      - ${ARK_DATA_VOLUME}:/opt/arkserver
      - ${ARK_BACKUP_VOLUME}:/var/backups/asa-server
    ports:
      - "${SERVER_PORT}:${SERVER_PORT}/udp"
    environment:
      - PUID=1000
      - PGID=1000
    networks:
      - default
    stop_grace_period: 45s
    deploy:
      resources:
        limits:
          memory: 12g
    memswap_limit: 12g

volumes:
    steam_data:

In this process, I've encountered a similar issue to the one reported in issue #23, where the logs show the following error:
mkdir: cannot create directory '': No such file or directory
I've followed the suggestions regarding permissions without success. I have not made any changes to the original .env file except for server-specific information like session name, password, and startup rules. Paths for STEAM_COMPAT_DATA_PATH and STEAM_COMPAT_CLIENT_INSTALL_PATH have not been altered.
Is there anything else I should consider in this migration process that could be causing this error? Any advice or suggestions would be greatly appreciated.
Thank you for your assistance.

After further investigation and with some helpful pointers, I realized that the error was due to a misunderstanding on my part regarding the environment variable setup in Portainer. I initially placed the environment variables only in the "Environment Variables" section without properly defining them in the main environment section of my docker-compose configuration.
Once I adjusted my docker-compose.yml file to include the environment variables directly within the service definition and ensured that all variables were correctly defined and passed to the container, the error was resolved.
Here's the adjusted snippet of my docker-compose.yml:
version: '3'

services:
  asa_server:
    container_name: asa_server
    tty: true
    restart: unless-stopped
    image: azixus/ark-ascended-docker
    volumes:
      - ${ARK_DATA_VOLUME}:/opt/arkserver
      - ${ARK_BACKUP_VOLUME}:/var/backups/asa-server
    ports:
      - "7791:7791/udp"
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - ASA_APPID=${ASA_APPID}
      - SERVER_MAP=${SERVER_MAP}
      - SESSION_NAME=${SESSION_NAME}
      - SERVER_PORT=${SERVER_PORT}
      - MAX_PLAYERS=${MAX_PLAYERS}
      - SERVER_SHUTDOWN_TIMEOUT=${SERVER_SHUTDOWN_TIMEOUT}
      - SERVER_PASSWORD=${SERVER_PASSWORD}
      - ARK_ADMIN_PASSWORD=${ARK_ADMIN_PASSWORD}
      - RCON_PORT=${RCON_PORT}
      - DISABLE_BATTLEYE=${DISABLE_BATTLEYE}
      - MODS=${MODS}
      - ARK_EXTRA_OPTS=${ARK_EXTRA_OPTS}
      - ARK_EXTRA_DASH_OPTS=${ARK_EXTRA_DASH_OPTS}
      - TINI_VERSION=${TINI_VERSION}
      - LOG_FILE=${LOG_FILE}
      - PID_FILE=${PID_FILE}
      - STEAM_COMPAT_CLIENT_INSTALL_PATH=${STEAM_COMPAT_CLIENT_INSTALL_PATH}
      - STEAM_COMPAT_DATA_PATH=${STEAM_COMPAT_DATA_PATH}
    networks:
      - default
    stop_grace_period: 45s
    deploy:
      resources:
        limits:
          memory: 12g
    memswap_limit: 12g

volumes:
  steam_data:

I hope this clarification helps others who might face similar issues.


fix: @DSTransactional rollback judgment, cannot write dead

Signed-off-by: old Cao<EMAIL_ADDRESS>What kind of change does this PR introduce? (check at least one)

[x] Bugfix
[ ] Feature
[ ] Code style
[ ] Refactor
[ ] Doc
[ ] Other, please describe:

The description of the PR:
Transaction rollback is nonjudgment. if noRollbackFor is configured, the expected inconsistency will occur
Other information:

在干啥？


Add CI pipeline to check for outdated dependencies

This action will run once per month, and check for outdated project dependencies. This won't affect pull requests, and instead the results can be found in the Actions tab.
Results are displayed in a chart that shows the outdated version being used, and the new version.
Indirect dependencies are not included (since we have no control over them).

Is there any way to notify us if there are any outdated dependencies, as going into the actions tab to check this will be easily forgotten. If there isn't we can just setup internally some kind of reminder to check the status of the job

The only thing I can think of would be to set up an email account for this and use this action to email the results: https://github.com/marketplace/actions/send-email
We would also need to setup GitHub Secrets for this, which I don't think I can do for this repo. Do you think it's worth doing @rokn? Setting up a reminder would probably be easier.

Is there any way to notify us if there are any outdated dependencies, as going into the actions tab to check this will be easily forgotten. If there isn't we can just setup internally some kind of reminder to check the status of the job

The only thing I can think of would be to set up an email account for this and use this action to email the results: https://github.com/marketplace/actions/send-email
We would also need to setup GitHub Secrets for this, which I don't think I can do for this repo. Do you think it's worth doing @rokn? Setting up a reminder would probably be easier.

Yeah I also saw this but it seems to be unnecessary hard to setup. Okay we'll just setup some remainders to check the job every month. Thanks!

Could you please verify the comment and rebase with the main?

@svetlio8 Both are fixed now. Looks like my commit signing was setup for<EMAIL_ADDRESS>instead of<EMAIL_ADDRESS>


Added a missing py.typed file for wheel

Hi. Types and a py.typed marker have been added in PR #109.
The marker was also specified in MANIFEST.in
Unfortunately MANIFEST.in does not affect binary distributions such as wheels.
This is the structure of the RECORD file during the installation of the package from wheel
aiodns-3.1.1.dist-info/INSTALLER,sha256=zuuue4knoyJ-UwPPXg8fezS7VCrXJQrAP7zeNuwvFQg,4
aiodns-3.1.1.dist-info/LICENSE,sha256=6wRV01EpQl7TmYg81xCSPePiRqUQ4uuE2fAAMtC77Jc,1070
aiodns-3.1.1.dist-info/METADATA,sha256=qM6KoP0Ot6pFAF-izMoNBgmGsIlTQfieU4X0nN5lobI,3994
aiodns-3.1.1.dist-info/RECORD,,
aiodns-3.1.1.dist-info/REQUESTED,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
aiodns-3.1.1.dist-info/WHEEL,sha256=yQN5g4mg4AybRjkgi-9yy4iQEFibGQmlz78Pik5Or-A,92
aiodns-3.1.1.dist-info/top_level.txt,sha256=5J2m3NWP4dezFZNpQoHaj8mv472iPcUzFboQoqWcEe4,7
aiodns/__init__.py,sha256=8uXR1WHCoHlToHl4AH_EaxAxpsA4oIiyor8DABjsvq4,5742
aiodns/__pycache__/__init__.cpython-312.pyc,,
aiodns/__pycache__/error.cpython-312.pyc,,
aiodns/error.py,sha256=fnNPLc8ceLk9drumwt-6Un5iiowyWApTe_VIoJ5gT5U,134

Thank you!


Eq 381 create new schema

Changes

Adds functionality for an author to create and save a new schema

How to test

Click 'Add new Schema button'
Enter a valid schema
Click 'Save'
Click 'List Schemas'
Verify schema has been added

Who can test
anyone

LGTM 👍


Support insertSnippet action

See also https://github.com/pokey/cursorless-vscode/pull/304
Still todo:

[ ] Add docs
[ ] Check DFA
[ ] Support "strict" mode for phrasal snippets

Merged into https://github.com/pokey/cursorless-vscode/pull/304 as part of monorepo


Update deploy.sh for docker

Update deploy.sh to run kruize in docker containers.  Routine docker() needs to be renamed to docker_container or as appropriate as it recursively gets called when docker commands are run from docker_prereq().

The deploy.sh script does not yet have support for docker, will be shortly adding a PR for that.

This is now available from PRs #22 and #23, you can use it as below
# Start kruize in docker mode
$ ./deploy.sh -c docker

# Terminate kruize in docker mode
$ ./deploy.sh -c docker -t

Documentation PR coming up later.


Options in hidden under SHaguTweaks "Advanced Options" + Lua error

hi!
The options button is hidden under the advanced options button when i press escape.  Help pls!

Don't use with ShaguTweaks. tDF is built on ShaguTweaks.


Floating bar instead of attaching to the edges of screen

Is your feature request related to a problem? Please describe.
A floating bar instead of bar attaching to the edges of screen and also the ability to decrease left and right margin
Describe the solution you'd like
Have an option to switch between the floating and fixed bar and also manage the spacing
Describe alternatives you've considered
Waybar has similar features
Additional context
Waybar :

Hyprpanel:

Implemented: Options to enable floating are in Configuration > Bar > Spacing.
Please open a new feature request when you have time for the spacing of icons in the bar as you suggested.


Refactor Plugin API

Background
See @drwpow's writeup here on the current limitations we face in our current build engine: https://github.com/pikapkg/snowpack/pull/562. These issues affects everyone: maintainers, plugin authors, and users.
New Plugin API

Based on @drwpow's original writeup in #562

export interface SnowpackPlugin {
  /** name of the plugin */
  name: string;
  /** file extensions this plugin takes as input (e.g. [".jsx", ".js", …]) */
  input: string[];
  /** file extensions this plugin outputs (e.g. [".js", ".css"]) */
  output: string[];
  /** transform input to output */
  build?(BuildOptions): Promise<BuildResult>;
  /** bundle  */
  bundle?(BundleOptions): Promise<void>;
}

Significant changes/features:

Plugins control inputs and outputs.

Examples:

Babel plugin: input: ['.js', '.jsx', '.ts', .tsx'], output: ['.js']
Svelte: input: ['.svelte'], output: ['.js', '.css']
Vue: input: ['.vue'], output: ['.js', '.css']

This allows Snowpack to deterministically predict the build pipeline in synchronous time without having to wait for any plugins to execute. It also lets plugins output multiple files, if they need to.
This also empowers plugins to resolve files in the dev server (e.g. the Svelte plugin can tell Snowpack that a .css file might come from a .svelte file, and how to access that). This takes a ton of resolution responsibility away from Snowpack, and onto the plugins that know how to handle these files.

Plugins can chain together. Now, multiple plugins can handle .js files, and we’ll process them in the order in which they appear in the plugins array in Snowpack config.
Build scripts expressed as plugins. Our custom syntax for "build:" & "run:" required more mental overhead than anticipated. This new change sets the stage to unify everything in the "plugins" array and introduce new plugins for connecting Bash commands (existing build scripts) via plugin.
It’s backwards-compatible. This doesn’t break existing script API for Snowpack, which we’ll need to support through 2.x. It also doesn’t break the current plugin API, though we will work through upgrading our own plugins, updating docs, and reaching out to third-party plugin authors to make this change.

There are also some QoL changes as well:

transform() has been removed. Just for simplicity—now everything’s a build() (except for bundle(), but that’ll only apply to bundling plugins like webpack’s and Parcel’s). This just helps plugin authors deal with less complexity.
Bug fixes and perf improvements uncovered in all this cleanup, especially related to large dependencies like react-dom. - The dev/build dashboard has been simplified to reflect this new unified approach to plugins.

Overall, we’re hoping this change makes Snowpack more powerful, more accurate, and more fun to write plugins for.
Testing
Existing tests cover everything that we're aware of. Drew is working on better Snapshot testing in CSA, which should help test this as well (given how big of a change this is).

@FredKSchott @drwpow As I understand the point of the plugin API refactor is to have build, bundle, and optimize stages for plugins to handle files?
When you brought up the plugin refactoring, I was curious if there would be interest in making some kind of "dev middleware" plugin stage where we could move the proxying solution into a plugin that would have its logging contained by the new logging solution and would remove the logic from the core dev server?
This was just one of my initial thoughts, I haven't fully thought it through and will keep following the changes to see if something like this would be aligned with the direction you're looking for.

Just ran this build against the CSA template snapshots. Out of them:

✅ working as expected: 11ty, blank.
👍 insignificant diffs: preact, react, react-typescript
❌ broken:  lit-element, lit-element-typescript, svelte, vue

Out of the broken templates, it seems like a combo of old plugin API + missing files. lit-element is just missing its src/ files, it seems. And svelte and vue seem to be missing App.css and App.js (only index.js is present). It just seems like something is getting dropped between the plugin -> new output map.
The good news is that the dev server seems to follow the same story—the dev has the same working-ness as build. So if we can figure out what’s happening between lit-element, svelte, and vue, we should be in pretty good shape! 🎉

@FredKSchott @drwpow As I understand the point of the plugin API refactor is to have build, bundle, and optimize stages for plugins to handle files?

Yeah that was a goal—do this now to establish a more permanent plugin API that authors can rely on. Which includes removing transform() for simplicity. And maybe optimize() is just an alternate bundler (e.g. have some concept of a default “unbundled” bundler?)?
But again—goal is to outline plugin authoring better, and settle on a more future-proof API. And in pursuit of that process, we wanted to tackle problems with ordering and conflict with scripts.

I was curious if there would be interest in making some kind of "dev middleware" plugin stage where we could move the proxying solution into a plugin that would have its logging contained by the new logging solution and would remove the logic from the core dev server?

Maybe this is a different subject, but when we explored exposing the dev server resolution to plugins, it seemed to open a whole can of worms. We realized that there’s not a 1:1 mapping between inputs -> outputs (.svelte becomes .js and .css). So when you think about the idea of building (input -> outputs), it’s distinct from dev server resolving in memory (output -> input). And because dev server resolution is different, if we put that on plugins, then that means now plugins have 2 responsibilities—build and dev—rather than just the 1 build. So it’s more work on plugin authors, and more work on Snowpack to resolve all that different plugin logic (e.g. which gets a .css file—PostCSS or Svelte?).
So instead we decided to own that logic within Snowpack, and Snowpack resolves requests in the dev server. Then Snowpack passes the source file to plugins, the same as the build process, so plugins have 1 main concern: building. But we don’t completely blackbox plugins out of control, and that’s what the input: [] and output: [] extensions are for: plugins still handle some degree of resolution with inputs (building) and outputs (resolving). They just can’t completely rename/remap files, but we think that’s a good restriction for everyone.

@drwpow great catch, I haven't tested this against lit-element templates. I can confirm that it works with updated Svelte & Vue plugins, but you're right that we still need to get working with the old plugins as well. Will test that now.

@stramel thanks for the detailed review!!! 😻

@drwpow All CSA templates are confirmed working now, as are a bunch of the community templates.


hashmap with null key crashes serializer

https://pub.beakernotebook.com/publications/3f67efa4-924a-11e6-b39d-5ba823359cba

https://github.com/twosigma/beaker-notebook/blob/master/plugin/jvm/src/main/java/com/twosigma/beaker/jvm/serialization/BasicObjectSerializer.java#L549
k may be null here


Auctex installs on Linux, but not on Windows

Using the same configuration on both Linux and Windows, and setting (setq straight-recipes-gnu-elpa-use-mirror t), the configuration
(straight-use-package 'auctex)

has no problems on my Linux computer: the package builds without error. On my windows machine, the same configuration results in a failed build and produces this error
autoload-generate-file-autoloads: tex-jp.el:0:0: error: error: (Local variables entry is missing the suffix)

I've tried a few different straight incantations, but the same error keeps popping up on Windows.

Could you paste the contents of the *straight-process-buffer* for the failed build?

Hmm, that's not in my buffer list.

possibly related:
https://github.com/hlissner/doom-emacs/issues/2637

Yes, very likely, I noticed that the offending file, tex-jp.el, is using an odd coding system.

If I manually change the coding in tex-jp.el to utf-8, Auctex installs without error on Windows using straight.

Thanks for the info.
I don't think there's anything we can do on straight's side to fix this.
You may be able to automate a workaround via the :pre-build recipe keyword, but I would recommend asking/reporting this upstream.


chore: revert back to using node-sass

Purpose
dart-sass does not currently handle the IE CSS hacks present in bootstrap-sass.
broccoliBuilderErrorStack: CssSyntaxError: /path/to/ember-osf-web/assets/ember-osf-web.css:5:55309: Missed semicolon

...caret{width:0;height:0;margin-left:2px;border-top:4px dashed;border-top:4px solid \;border-right:4px solid transparent;border-left:4px solid transparent}...
                                                                                ^ offending character

(note: this only causes an error for production builds because minification)
See: https://github.com/sass/sass/issues/2590
Summary of Changes

added explicit dependency on node-sass
configure ember-cli-sass to use node-sass

Side Effects
Dependency on node-sass.
(but we still were anyways because ember-cli-addon-docs -><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>Feature Flags
n/a
QA Notes
n/a
Ticket
n/a
Reviewer Checklist

[ ] meets requirements
[ ] easy to understand
[ ] DRY
[ ] testable and includes test(s)
[ ] changes described in CHANGELOG.md

Pull Request Test Coverage Report for Build 2208

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 69.266%

Totals

Change from base Build 2207:
0.0%

Covered Lines:
4885

Relevant Lines:
6418

💛  - Coveralls

That's weird. It looks like it's proooobably calculating the typography percentages a little different?


Implement Remote Configuration for Chat Screen

I'm sorry for such a big PR. For the next screens, I will split them into small ones.
MOB 1623
Jira issue:
https://glia.atlassian.net/browse/MOB-1623
Additional info:
• Implement Remote Configuration for Chat Screen
• Add extension functions to ease work with resources in views
• Migrate most of Chat Screen related classes to Kotlin
• Deprecate old Configuration classes(Runtime Configuration)
• Minor code cleanup
• Change Remote Config mapping logic

I'd like to propose taking sample configuration from this repo - https://github.com/salemove/mobile-sdk-unified/blob/master/ios-sdk-widgets/Samples/LibertyMutual.json
and compare with these screenshots - https://github.com/salemove/mobile-sdk-unified/pull/9#issuecomment-1262138259 https://github.com/salemove/mobile-sdk-unified/pull/9#issuecomment-1265480521
It will simplify the process of aligning between iOS and Android.

!squash

!merge


Decouple hasOne/belongsTo and hasMany association resolvers from their implementation

Consider how we solved the part of resolvers of many-to-many associations in Issue #64 .
Implement the same delegation of the GraphQL resolver to the data model layer. This means for hasMany associations the resolver should look something like the following example. Consider Dog has-many Fleas:
Dog.fleaFilter( {search, pagination, order}, context ) {
   return dogDataModel.fleaFilterImpl( {search, pagination, order} )
}

// Dog Data Model
fleaFilterImpl( {search, pagination, order} ) {
   // default implementation is to use our resolvers:
   let extSearch = search.merge( /* where dogId = this.id */ )
   return Flea.readAll( { extSearch, pagination, order } )
}

The same must be done for hasOne or belongsTo associations. Considering the above Dog and Flea example the inverse association would look like this:
Flea.dog({ search }, context) {
   return fleaDataModel.dogImpl( {search} )
}

// Flea Data Model
dogImpl( {search} ) {
   // current default implementation
   return Dog.readOne( this.dogId )
}

Done.  #81766c #d6e78f #19b994 #22b87f


Not working well or at all with DuckDuckGo search on Safari / macOS Sonoma

Neither blocks the page (or full site), nor shows the "Block this site" link. However, when you go to that page/site, clicking the uBlacklist extension icon shows "Unblock", so it's definitely recognizing it
It works with Google searches, though

I just installed uBlacklist for Safari on Sonoma 14.2.1 and was wondering why it wasn't behaving as expected for DDG. Looking through the back issues, this seems to be a recurring problem as DDG changes its CSS.
Thanks for the extension. I look forward to using it successfully.

I have yet to reproduce this issue.
Safari 17.1.2 (macOS Sonoma 14.1.2), uBlacklist 8.4.0

i'm also seeing this issue on Firefox on Windows 11. sites not blocked in search results, and the link to block sites is not visible although DDG is checked in the "other search engines" config. i could have sworn this used to work, as little as a couple of months ago.


auth0 integrated in App.js

Description
auth0 integrated in App.js
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

Change Status

[ ] Complete, tested, ready to review and merge
[x] Complete, but not tested (may need new tests)
[ ] Incomplete/work-in-progress, PR is for discussion/feedback

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My code has been reviewed by at least one peer -taylor
[X] New and existing unit tests pass locally with my changes
[ ] There are no merge conflicts

Description
Type of change
Please delete options that are not relevant.

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

Change Status

[x] Complete, tested, ready to review and merge
[ ] Complete, but not tested (may need new tests)
[ ] Incomplete/work-in-progress, PR is for discussion/feedback

How Has This Been Tested?

[x] Test A
[ ] Test B

Checklist

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


statement in documentation incorrect/inaccurate?

In the "Requirements for configuring AKV" section, the document states, "Soft-delete feature is off by default..."
As far as I can see, it is actually on by default - at least when creating vaults via the Portal.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 7600c6cf-0b4d-1ffa-c1bb-ebf23adafc1f
Version Independent ID: 1ae4f15b-b978-882e-c5f4-d23522a53bb4
Content: Customer-managed transparent data encryption (TDE) - Azure SQL Database & SQL Managed Instance & Azure Synapse Analytics
Content Source: articles/azure-sql/database/transparent-data-encryption-byok-overview.md
Service: sql-db-mi
Sub-service: security
GitHub Login: @jaszymas
Microsoft Alias: jaszymas

@DrEnnui Thank you for the feedback. We are actively investigating and will get back to you soon.

@DrEnnui Thanks for bringing this to our notice. Enable Soft Delete feature is on by default through Azure Portal or even when I tried through the Azure CLI. However as per the article The ability to opt out of soft-delete will be deprecated soon. In any case, this article has to updated accordingly.
This is being assigned to the content author to evaluate and update as appropriate.

#reassign:shohamMSFT
Hey @shohamMSFT - Can you please confirm this statement in the doc and if we need to update it? Thanks!

@DrEnnui Thanks for the feedback! Soft-delete on key vault is indeed enabled by default for newly created vaults.
I will update this section of our documentation accordingly.

#please-close


Constrain number of inputs a task can process

We should impose some cap (maybe 500 files?) to prevent large directories from bogging down the server
Maybe should also apply quotas to files as well as compute time

Unnecessary if the server is not a bottleneck (e.g., due to file previews)


the model trained by SDG optimizer is too bad

I want to know why the mAp is about 15 percentage worse when use SGD optimizer, how does set the parameter for SGD? The mAP result obtined by default Adam optimizer is match with the paper report. Do you study the parameters for SGD optimizer?

@chenxu93 Did you use SGD with warmup? I did not try SGD.

@chenxu93 Have you set the appropriate learning rate？

@chenxu93 If you use SGD, you need to set a larger lr than Adam. But we don't recommend to use SGD, because it's a little bit tricky for tuning lr.

@michuanhaohao @L1aoXingyu Thanks, maybe the SGD is more useful for the detection task, and Adam is more suitable for the classify task.


authenticateSession() test helper must be called after a visit() call

As per the issue I initially raised on the ember.js repository: https://github.com/emberjs/ember.js/issues/10263
The authenticateSession() helper returns a call to wait(), however this causes an infinite loop crash if there has not been a previous visit() call as that method sets up the router which wait() relies upon.
Is this simply a documentation issue for the ember-simple-auth-testing package or can the helper be updated to work around the problem?

The tests in the example project work and they don't call visit before calling authenticateSesison. Is this sth. introduced in a later Ember version maybe?

Ah, yes. Digging a little deeper it appears to be something that has changed between the latest beta and current canary.

I'd say that should be fixed in Ember as it doesn't make sense to have to visit a route only to setup the router so that the authenticateSession can work.

Fixed in Ember.


Changed path in 'Update cloud config'

Path pointed to ~/workspace/bosh-env/... instead of ~/bosh-env/...

Thanks! I shortened your corrected path a bit further.


Regional Radiation Centres (RRC)

It should be investigated if not all of the Regional Radiation Centres (RRC) designated by the WMO make continuous solar surface irradiance measurements and can be added to the list. Some of the RRCs are already included in the list, e.g., Lindenberg, Norrköping, and Carpentras.
Description from the WMO:

A Regional Radiation Centre is a centre designated by a Regional Association to serve as a centre for interregional comparisons of radiation instruments within the Region and to maintain the standard instruments necessary for this purpose.

Melbourne
Cairo

For Sudan, a number of stations exist measuring only GHI, described here. I could not find information about stations measuring more components.

In Central Africa, there seems to be a station network called FAOCLIM 2 that has solar irradiance data, but only measuring GHI. A list of stations is described here.

@IoannisSifnaios Thanks for leaving these bread crumb trails even though we aren't including them. It will be highly useful in case anybody ever starts searching for Africa specific data.

In Tunisia, the National Institute of Meteorology (NIM) operates stations that measure the GHI. A number of articles also mention stations that measure GHI (e.g., 1, 2, 3).
The GEBA network mentions a station in Tunis that operated from 1964-2008, but only measuring GHI.

Some info on Pune here and here

In Peru, there is a network measuring only GHI. It is described here.
In a document from SENAMHI (National Meteorological and Hydrological Service) there is a photo of a tracker, but no more information could be found about it. The photo is in this report.

Information on Toronto here.

@AdamRJensen in Russia, there is a netwrok of stations described here that only measure GHI and DHI.
The RRC station in St. Petersburg is also measuring GHI and DHI, as described here.
There is this network called "The World Network" that is coordinated by Russia and collaborated with stations in many countries (described here). However, it seems that they don't measure DNI and they don't give information on how they measure the diffuse.
I am inclined not to include them, however, we have very little coverage in Russia. Thoughts?

With that information i suggest we also don't include them


Fetch latest citation no longer working

relaton fetch -t ISO -y 2010 'ISO 2146' works
relaton fetch -t ISO 'ISO 2146' is meant to fetch a version of the spec with the year taken away, and the latest version as a related document. Instead, it fails to retrieve any documents.
This breaks rspec:
 1) Relaton Fetch relaton fetch fetch code with a type prints out the document for valid code and type
     Failure/Error: expect(output.stdout).to include('<relation type="obsoletes">')

       expected "No matching bibliographic entry found\n[relaton] Info: detecting backends:\n[relaton] processor \"re...d\n[relaton] processor \"relaton_gb\" registered\n[relaton] processor \"relaton_nist\" registered\n" to include "<relation type=\"obsoletes\">"
       Diff:
       @@ -1,2 +1,8 @@
       -<relation type="obsoletes">
       +No matching bibliographic entry found
       +[relaton] Info: detecting backends:
       +[relaton] processor "relaton_iec" registered
       +[relaton] processor "relaton_iso" registered
       +[relaton] processor "relaton_ietf" registered
       +[relaton] processor "relaton_gb" registered
       +[relaton] processor "relaton_nist" registered

     # ./spec/acceptance/relaton_fetch_spec.rb:9:in `block (4 levels) in <top (required)>'
     # /Users/nickn/.rvm/gems/ruby-2.4.0/gems/rspec-command-1.0.3/lib/rspec_command.rb:47:in `block (2 levels) in <module:RSpecCommand>'
     # /Users/nickn/.rvm/gems/ruby-2.4.0/gems/rspec-command-1.0.3/lib/rspec_command.rb:45:in `block in <module:RSpecCommand>'

@opoudjis I'm not able to reproduce the issue. What does relaton fetch -t ISO 'ISO 2146' give you?

What I've pasted above: "No matching bibliographic entry found"

@opoudjis It works o my comp and Travis. I noticed the Gemfile.lock isn't included in this repo. So you may have different Gemfile.lock with old versions of dependencies. Try to run bundle update. And I think it is a bad idea not include Gemfile.lock into repo.

Gemfile.lock had ended up much more trouble for travis than it was worth.
OK, I will debug :(

Huh. I cleared my relaton cache, and it worked.
I think I know what happened, and it's a different bug.
I was running rspec on relaton-cli when I temporarily lost internet connectivity. I think the attempt to fetch ISO 2146 undated aborted, and relaton ended up storing a "not found" entry under ISO 2146 in the global cache. Is that possible?
If so (a) no entry should be cached if internet connectivity is aborted, and (b) the rspec for relaton-cli should temporarily move the global cache to a different directory, like the metanorma-standoc rspec does, so that the cache can be ignored.
Could you please check both?

I’ve had this sort of issue with the cache too. Maybe we need to make a new issue in ensuring that cache read failures don’t crash the application — instead it should try to refetch.

Gemfile.lock had ended up much more trouble for travis than it was worth.
bundle update made no difference. OK, I will debug :(

@opoudjis Gemfile.lock will cause trouble for users who update the gem. They will have a new version of the gem with old dependency.
Concerning Travis. When you run Rspec before push commit it updates Gemfile.lock. So pushing the updated Gemfile.lock to GitHub prevent any trouble.

I was running rspec on relaton-cli yesterday when I temporarily lost internet connectivity. (I was on the train.) I think the attempt to fetch ISO 2146 undated aborted, and relaton ended up storing a "not found" entry under ISO 2146 in the global cache. Is that possible?

Yes, relaton-iso returns nil if request ended with an error. In this case, relaton saves not found in the cache. We need to return something other than nil in case network error to solve the problem. Maybe we should raise an error and catch it in the relaton. We need to do implement it in all relaton-iec, relaton-iso, relaton-ietf,relaton-gb, and relaton-nist gems.


plugins: python version safe ElementTree usage

On hosts where lxml is not installed, fallback to cElementTree or
ElementTree implementations that should be available in python 2.5+
standard libraries.
Helps with errors like:
(<type 'exceptions.ImportError'>, ImportError('No module named lxml',), <traceback object at 0x7fd3b4934f80>)
(<type 'exceptions.ImportError'>, ImportError('No module named lxml',), <traceback object at 0x7fd3b4934ab8>)
(<type 'exceptions.ImportError'>, ImportError('No module named lxml',), <traceback object at 0x7fd3b4934248>)

retest this please


Remove impossible selectors

I use partial selectors in SASS which sometimes produces impossible selectors if you're not careful. These selectors are valid syntax but can never match an element, so, can safely be removed.
A few examples I thought of:

tag:not(tag.stuff)
html html (assuming well-formed HTML)
p div (again, assuming well-formed HTML)
...

Interesting idea @clarcharr - if we ever have it I can imagine it'd be useful to see a warning that such selectors were removed.

Not pseudo selectors containing complex selectors (e.g. tag:not(tag.stuff)) will be supported in Selectors Level 4.

Won't fix as clean-css is going into maintenance mode.