Support for Android RGB565 bitmaps

Is it possible to load a Bitmap as RGB565 and send it through to Filament using TextureHelper.setBitmap so that it ends up as GL_RGB565 texture type?
I'm trying to find a more memory efficient way to store uncompressed opaque textures than RGBA8.

TextureHelper already supports RGB565. 4444 and HARDWARE are not supported however (and won't be). I would however recommend using compressed textures over 565.

@romainguy I'm struggling to get this working in the samples. For example in sample-textured-object, Filament crashes if I add this line to TextureLoader.loadTexture:
options.inPreferredConfig = Bitmap.Config.RGB_565
I assumed this was because there's a mismatch between the raw bytes from the imported Bitmap and the internal format of the Filament Texture, but it still crashes if I specify the format explicitly like this:
val texture = Texture.Builder()
    ...
    .format(Texture.InternalFormat.RGB565)
    ...
    .build(engine)

I take your point about preferring compressed textures over 565 format, but in my case I'm loading 3rd-party GLTF files where the texture sources are JPEG so loading into a reduced color space is a quick-and-dirty way to claw back some memory.

Looking into the crash…

I have a fix coming.


Server error when trying to depoly

Does this occur consistently?
Repro steps:

Action: postCreateWebApp
Error type: 502
Error Message: Server Error
502 - Web server received an invalid response while acting as a gateway or proxy server.
There is a problem with the page you are looking for, and it cannot be displayed. When the Web server (while acting as a gateway or proxy) contacted the upstream content server, it received an invalid response from the content server.
Version: 0.20.0
OS: darwin
OS Release: 19.6.0
Product: Visual Studio Code
Product Version: 1.51.1
Language: en

Call Stack
new RestError extension.bundle.js:46:66146
extension.bundle.js:46:496611
processTicksAndRejections task_queues.js:94:5

Could you please provide detailed repro steps?  Also are you working behind a corporate proxy of some sorts?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Mismatch in test behavior for flutter_tools/test/commands/attach_test.dart between dart1 and dart2

The attach test runs properly on Travis, but fails in the tests on the g3 roll.
We get the following error:
NoSuchMethodError: The method '_setExpected' was called on null....
NoSuchMethodError: The method '_setExpected' was called on null.
Receiver: null
Tried calling: _setExpected(Closure: (Invocation) => T)
dart:core                                                                               Object.noSuchMethod
package:mockito/src/mock.dart 354:15                                                    PostExpectation._completeWhen
package:mockito/src/mock.dart 336:12                                                    PostExpectation.thenReturn
../../tmp/archives/third_party/dart/flutter_tools/test/commands/attach_test.dart 41:37  main.<fn>.<fn>
===== asynchronous gap ===========================
dart:async                                                                              _AsyncAwaitCompleter.completeError
../../tmp/archives/third_party/dart/flutter_tools/test/commands/attach_test.dart        main.<fn>.<fn>

I spoke with @srawlins about this, and we believe this is related to package:flutter_tools using dart version < 2.0.0, while the g3 tests are using Dart 2.0.
The line that fails is:
when(portForwarder.unforward).thenReturn((ForwardedPort _) async => null);

which is using a tearoff of the unforward method instead of the method itself.
The Dart 2 approach is to do this:
when(portForwarder.unforward(any)).thenReturn(null);

This fix doesn't appear to work in the current test runner.

The solution is going to be to switch the flutter_tools package pubspec to using Dart 2.0.


Blog: Added filter by tags

Created TagField Component
File Location: src/lib/components/utils/acm-tagfield.svelte
Usage: Allows users to make selections and filter content.

Created new file utils.ts to store common functions
File Location: src/lib/common/utils.ts

Added Filter by Tags feature for Blog page.
Made some changes to these files:

In blog/index.svelte: Added TagField component.
In blog/_query.ts: Modified fetchNewsletters.
In blog/index.json.ts: Modified get function.

This PR is intended to resolve #277

I'll work on merging this in with my changes some time this week

It does not appear to be workin

I don’t know what happened. Maybe you’re in DEBUG mode or maybe there are something wrong in “.env” file.
Everything works perfectly on my PC.

@NLTN Oh that's not my local environment it's the vercel preview linked in https://github.com/EthanThatOneKid/acmcsuf.com/pull/466#issuecomment-1124441436, if you want we can try to find some time to work on this maybe this week or a week from now (the week of 7/10)? If not we can push this back to when the semester starts


Update content dependencies

Now that we have split the content into their own repositories, we need to update the site's dependencies accordingly.

@rafaparadela plz take a look.

Great 👏
LGTM, thank you @dialelo


added new flavor book to library

About the PR
Adds a new flavor book "The Lusty Reptilian Janitor" to the library.
Why / Balance
This is a parody of book "The Lusty Argonian Maid" from the Elder Scrolls series, since the reptilian species is partially based on the argonian species of Elder Scrolls.
Technical details
I added the book's content, and a new cover icon for the book.
The content is safe for work, it only hints at the romance between the two characters.
Media

Requirements

[X] I have read and am following the Pull Request and Changelog Guidelines.
[X] I have added media to this PR or it does not require an ingame showcase.

Breaking changes

Changelog

:cl:

add: A new book "The Lusty Reptilian Janitor" can now spawn on bookshelves.

 I tried to rebase, was that a bad idea? I can see there has been a submodule update in those 3 new commits.

Okay, I undid the rebase, because I've found that my indents were messed up as well, hopefully this solves the problem.

Too descriptive with the glancing and blushing part. Wizden is a 16+, i think if you want to implement this, you should bring this to a fork that’s 18+

I would rather tone it down if deemed necessary and have it on Wizden.

Isn’t this just the “lusty argonian maid” word for word?

inappropriate

change the bit about the stain on the pants
or you can cleverly tear away by having something at the end like:
The rest of the pages have been torn out.
or
The page cuts off, but the paper is too sticky to continue.

The page cuts off, but the paper is too sticky to continue.

absolutely not

The page cuts off, but the paper is too sticky to continue.

absolutely not

for sure

Plus we've got the lusty exo babes posters anyway

It's Busty Backdoor Exo Babes 6 thank you very much

It's Busty Backdoor Exo Babes 6 thank you very much ![image](https://private-user-

There is a "Lusty" poster as well, though.

If someone would get an ERP bwoink or ban for saying anything that is on an item or in a book, that item/book should be removed or reworded. This definitely falls under that category IMO.


Add vault extra audiences

enable audiences example
Example of the spec
spec:
  vault:
    path: pki/sign/sandbox
    server: https://vault.net
    auth:
      kubernetes:
        role: sandbox-issuer
        mountPath: /v1/auth/kubernetes
        serviceAccountRef:
          name: sandbox-issuer
        audiences:
        - vault

Pull Request Motivation
Motivation is elaborated in #6666
Kind
/feature
Release Note
Added option to provide additional audiences in the service account auth section for vault

@SgtCoDFish here is a new PR with corrected DCO, I had to abort another one as it was past saving...

/kind feature
/ok-to-test
Linked to #6686

/test pull-cert-manager-master-e2e-v1-28

Hey, sorry for the delay, I see that the PR has already been merged. 😅  It took me a while to test everything manually. I described how I manually tested this in this Hackmd page.
As Ash explained, I went "too deep" in the risk analysis of serviceAccountRef. I think it is OK to assume that the Issuer and ClusterIssuer resources are "safe". I think it would have been OK to have a default audience vault, or even to simply let people set their own audiences from the start...
I have a few remarks:

audiences should be under serviceAccountRef since setting the audiences only applies to the serviceAccountRef field. Example:
spec:
  vault:
    path: pki/sign/sandbox
    server: https://vault.net
    auth:
      kubernetes:
        role: sandbox-issuer
        mountPath: /v1/auth/kubernetes
        serviceAccountRef:
          name: sandbox-issuer
          audiences:
          - vault

I'm OK with the plural "audiences" since it matches the projected token API. But is there a reason for setting multiple audiences here? I struggle finding a good reason.

When someone sets something in audiences, is the default audience (e.g., vault://default/issuer overridden, or is the default audience added to the list of audiences?

In your example, the only audience is vault. Does this example work in the case of an external Vault? In my case, I had to use the following issuer:
apiVersion: cert-manager.io/v1
kind: Issuer
metadata:
  name: vault-issuer
  namespace: default
spec:
  vault:
    path: pki/sign/vault-issuer
    server: http://vault.default.svc.cluster.local:8200
    auth:
      kubernetes:
        role: vault-issuer
        mountPath: /v1/auth/kubernetes
        serviceAccountRef:
          name: vault-issuer
        audiences: [https://kubernetes.default.svc.cluster.local]

One of the theoretical use cases for having multiple audiences would be in decoupling the vault role config from the cert-manager config as if I am to change vault role aud requirement I can register new aud as additional audiences list item in the cert-manager config and make changes on the vault side without breaking things.

Other thought: since 99% of folks who will be using the audiences field will because they want to use an external Vault, why not do something better? Something like enableKubeAudience: true where the cluster's issuer URL is automatically added without having to figure out what is the issuer URL of the cluster?

Other thought: since 99% of folks who will be using the audiences field will because they want to use an external Vault, why not do something better? Something like:
kind: Issuer
spec:
  auth:
    kubernetes:
      serviceAccountRef:
        enableKubeAudience: true

The cluster's issuer URL is automatically added by cert-manager without having to figure out what is the issuer URL of the cluster, since each cluster has its own issuer URL

Probably not as I'd like to keep the option open for the audiences, at least the proposal won't meet our potential use scenarios. Cluster issuer in AUD is not what vault expects by default from what I've seen as it is looking for the kube API server as aud instead, which may change depending on what Vault or K8s teams do. If aud is flexible then user can coordinate the aud and the vault role.
I will make another PR to change the aud to be within the SA scope


More meaningful authentication errors

requirements
Before the introduction of LDAP, toctoc returned only one error: InvalidCredentials.
LDAP library has many different errors and most of them are totally not related with credentials themselves.
Therefore we should extend toctoc error module to better model different types of errors, preferably customisable by the specific login mechanism.
specs
{optional: describe technical specs to implement this feature, if not obvious}
misc
{optional: other useful info}

@gabro offsite scope?

We don't really use LDAP in any of our projects, so I wouldn't try to tackle this this week.


data

Hello, can you make your data set public

Sorry, we noted that we will publish the data upon acceptance of our paper.

Sorry, we noted that we will publish the data upon acceptance of our paper.


Can We add Map Styles option for better Visualization?

There is several Map styles from MAP API here https://docs.mapbox.com/api/maps/styles/#mapbox-styles
It would be cool if we can add it to the BigQuery Geo Viz.

@farsikogama I don't think BigQuery-geo-viz, but you can do same and more on Dekart BigQuery Playground Including changing map styles with Mabox styles


Allow Tasks API

In an attempt to make ADS development tool for Azure Functions it requires that the Tasks API be available. The Azure Functions extension integrates with it for function development.
Install the extensions for Azure Account and Azure Functions and then upon trying to activate the Azure Functions explorer you see this error:

Tasks themselves offer users the ability to automate more actions in VS Code, which I can only assume should allow the same thing for ADS. Tasks in VS Code allow you to perform multiple commands from the command palette or execute scripts/processes more seamlessly.

@abist is currently working on enabling the vscode Tasks API and integrating with the existing ads task management functionality as part of the SQL Project build feature.  The current plan is to release this in September.

Linking to related issue https://github.com/microsoft/azuredatastudio/issues/10370 so we can potentially close at the same time.


Upload Single Lambda Dir

This changes how we do things, pursuant to #2, to only upload
a single Lambda dir at a time, either the CWD or whatever
is specified by -d.
We try to take care to be careful not to upload .env files.
I've added an example for how to upload multiple Lambdas in a
CI environment.

This worked perfectly in my use case.


"watt" is not a valid unit for the device class('power'). expected one of ['W', 'kW']

Got some warnings in homeassistant.log complaining about this.
2023-09-08 11:17:33.471 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.lumi_acn017_161c_electric_power (<class 'custom_components.xiaomi_miot.sensor.MiotSensorSubEntity'>) is using native unit of measurement 'watt' which is not a v\
alid unit for the device class ('power') it is using; expected one of ['W', 'kW']; Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
2023-09-08 11:17:33.498 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.lumi_acn017_3266_electric_power (<class 'custom_components.xiaomi_miot.sensor.MiotSensorSubEntity'>) is using native unit of measurement 'watt' which is not a v\
alid unit for the device class ('power') it is using; expected one of ['W', 'kW']; Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
2023-09-08 11:17:33.513 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.lumi_acn016_51d0_electric_power (<class 'custom_components.xiaomi_miot.sensor.MiotSensorSubEntity'>) is using native unit of measurement 'watt' which is not a v\
alid unit for the device class ('power') it is using; expected one of ['W', 'kW']; Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
2023-09-08 11:17:33.530 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.lumi_acn017_f814_electric_power (<class 'custom_components.xiaomi_miot.sensor.MiotSensorSubEntity'>) is using native unit of measurement 'watt' which is not a v\
alid unit for the device class ('power') it is using; expected one of ['W', 'kW']; Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
2023-09-08 11:17:33.564 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.lumi_acn016_4319_electric_power (<class 'custom_components.xiaomi_miot.sensor.MiotSensorSubEntity'>) is using native unit of measurement 'watt' which is not a v\
alid unit for the device class ('power') it is using; expected one of ['W', 'kW']; Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
2023-09-08 11:17:33.568 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.lumi_acn017_e709_electric_power (<class 'custom_components.xiaomi_miot.sensor.MiotSensorSubEntity'>) is using native unit of measurement 'watt' which is not a v\
alid unit for the device class ('power') it is using; expected one of ['W', 'kW']; Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.

Try master branch.

Similar problems here:
3-09-10 01:53:02.989 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.lumi_weather_v1_7299_atmospheric_pressure (<class 'custom_components.xiaomi_miot.sensor.MiotSensorSubEntity'>) is using native unit of measurement 'pascal' which is not a valid unit for the device class ('pressure') it is using; expected one of ['bar', 'inHg', 'hPa', 'mmHg', 'psi', 'kPa', 'mbar', 'cbar', 'Pa']; Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
2023-09-10 01:53:03.390 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.chuangmi_212a01_e83b_electric_current (<class 'custom_components.xiaomi_miot.sensor.MiotSensorSubEntity'>) is using native unit of measurement 'None' which is not a valid unit for the device class ('current') it is using; expected one of ['mA', 'A']; Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
2023-09-10 01:53:03.391 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.chuangmi_212a01_e83b_voltage (<class 'custom_components.xiaomi_miot.sensor.MiotSensorSubEntity'>) is using native unit of measurement 'None' which is not a valid unit for the device class ('voltage') it is using; expected one of ['mV', 'V']; Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.


Feature/star rating view

Description
Fixes Bug #3 Star rating not showing correct rating
Trello card: https://trello.com/c/ZfjyNvQP/104-bug-3-star-rating-not-showing-correct-rating
Type of change

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

Change Status

[x] Complete, tested, ready to review and merge

How Has This Been Tested?

[x] Manually tested with simulator (iPhone 11 Pro Max)

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
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] There are no merge conflicts

 Bug #3 Star rating not showing correct rating

 Search

 Search


New way of inline translations without breaking layouts

Here is the new way of translations as discussed in (with animations)
https://github.com/vsch/laravel-translation-manager/issues/38
Because the old way is cumbersome and needs modifying the way laravel is doing translations...
In addition, it allows translating ALL text created by trans()/choice() functions when page is loaded/rendered. Not only those found in the view blade templates. For example if you used trans() inside the controller and passed the resulting text as a variable to blade template, you can still translate that specific key even though it was not used in the template itself!
Below are gif animations of how it works as examples:
Tooltips for remembering which button does what :)

A page with two trans() keys only...

The translator page with many keys (compare with how ugly the page looked when old inline translations were enabled).

@yurtesen, thank you for a great job. I will make a release as soon as I get a break in my schedule.

BTW I realized I forgot to update the translations.min.js, you should update that...

The delay was having to update LTM and my dev site which is my site for the Markdown Navigator plugin for JetBrains IDEs, to Laravel 5.3.
Every time Laravel updates the API it breaks a boat-load of code, real PITA. Laravel 5.3 silently breaks a lot of code due to API changes.
I will be making a release probably tomorrow, once I have tested the Web UI.

You should enlist some people to help you with your code. It may encourage people if you had some comments in your code :)
I know what you mean about incompatibilities with every new release. When I make an addition to a program, I try to keep it simple and try not to change existing code or if possible push code to the original program's repository. You could try to clean up your code and maybe they accept it as enhancement to Laravel translation package?


docs(testing-mongoose): Updating testing API docs for mongoose

Information

Type
Breaking change

Doc
No

Description
Updating testing-mongoose doc

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

v6.17.2
GitHub release

Your semantic-release bot :package::rocket:


[Event Request] Codeunit 414 Release Sales Document - Function Code

Dear ALAppExtensions Team,
We would like to request the following event publisher in codeunit 414 Release Sales Document - Function Code
        if PrepaymentMgt.TestSalesPrepayment(SalesHeader) and ("Document Type" = "Document Type"::Order) then begin
            Status := Status::"Pending Prepayment";
            Modify(true);
            OnAfterReleaseSalesDoc(SalesHeader, PreviewMode, LinesWereModified);
            exit;
        end;
        // DINNL <<
        DINOnRelease(SalesHeader, DINCalledFromManualRelease);
        // DINNL >>
        Status := Status::Released;

local procedure DINOnRelease(var SalesHeader: Record "Sales Header"; DINCalledFromManualRelease: Boolean)

What is the DINCalledFromManualRelease parameter that you want the event to expose?

Also there are two event in 5 lines of code before: OnBeforeModifySalesDoc and OnAfterReleaseSalesDoc, what is the usecase where you can't use those instead?


HAML Support

Support for HAML in the HTML view?

There's an open PR. My concerns are based around security, and I don't
believe they can be addressed.
On 26 Feb 2015 23:38, "Adam Foster"<EMAIL_ADDRESS>wrote:

Support for HAML in the HTML view?
—
Reply to this email directly or view it on GitHub
https://github.com/jsbin/jsbin/issues/2286.

Ok I see it, and I see the points for concern. Makes me wonder how Codepen.io are doing it.
JSbin is a great site btw.

I believe they're stripping a lot of functionality. Which is (I think) the way to go, but I also think (and I could be wrong) that their site is written in Ruby, so they're a more versed with the language and the exploits, whereas jsbin is node/JavaScript based, so my knowledge isn't as strong in Ruby (in fact, I've never had to write a single production site using it, so it's utterly lacking!).


add visualizations

Adding the following visualizations

ttft per request (box plot)
total output time (box plot)
ttft v input prompt size (scatter plot)
itl v token position (scatter plot)
input tokens vs output tokens (heat map)

Additionally,

Added plot manager
Added parquet outputs for all dataframes and full metrics data
Reorganized outputs into an artifacts directory to not clutter the user's workspace

Great work on this! The visualizations look really good. Do we want to schedule adding unit testing for this? Would it be possible to mock a few datapoints, then override the file writing calls to instead mock writing to a file? We could check the file count, values, etc. to make sure we get what's expected.
It would take some time, so that should probably be in its own ticket. Especially if this may change based on feedback, though getting that structure up and counting things like file count would be good to do early and can easily be changed or added to later.


Silent push notification in a closed React Native app

Have a question about silent push notification in React Native app.
In our app we send data about an event in push notification. I want to use silent push notification to update data in the app that is closed. Is it possible for the closed app to receive the silent push notification? How to implement it into the React Native code? In other words, how to transfer the silent notification data into the React Native for the closed app? Any instructions, documentations, and links will be great to have.
RN version 0.45.1
content_available is set to true

It seems you need to use remote notification, without showing any local notification to the user.
AFAIK, for simple processing the javascript listener this.notificationListener = FCM.on(FCMEvent.Notification,  is enough; for complex operations you can extend didReceiveRemoteNotification
When your app receives the remote notif, you can process specific actions in the background (network calls...)

Is there any update on this. @evollu said here  that after update to v7.5.1 this is supposed to work, but the code is not calling the callback on FCMEvent.Notification when the app is closed.

I have checked the solution suggested by @lfallet.
I started the following iOS realization for Swift: https://www.raywenderlich.com/156966/push-notifications-tutorial-getting-started
This suggestion did not work.
When the app is closed, and push notification is received , then any handler does not work. I checked this in the code, by showing local notification.
All the suggested solutions from Stackoverflow end up using didReceiveRemoteNotification with fetchCompletionHandler But it does NOT work as I said earlier.
Guys, if you know what I do incorrectly, or you had the problem as well and can recommend the working example of this problem, I would be grateful for any help, advise or link.
BTW there is a comment from @evollu about the iOs.
https://github.com/evollu/react-native-fcm/issues/435#issuecomment-319081391

what OS is not working? It should work for Android and iOS (except when app is killed by user)

Thank you for the comment.
Handlers are not called on iOS when the app is killed (closed)  by user. There are sources where they say :
didReceiveRemoteNotification with fetchCompletionHandler should be called but they are not. If it is the normal behavior for the iOS, then is there any documentation  that proves that.

https://developer.apple.com/documentation/uikit/uiapplicationdelegate/1623013-application
However, the system does not automatically launch your app if the user has force-quit it. In that situation, the user must relaunch your app or restart the device before the system attempts to launch your app automatically again.

Thank you for your answer and for the link, probably this issue can be closed.

@evollu, is this impossible now to start up in background when push arrives ?
I tried to add "content_available": true but it does not helped.
Also I tried different version of plugin: 8, 9.1.2 and also v7.5.1 as bhosle-git advised in this thread
https://github.com/evollu/react-native-fcm/issues/435
and nothing happens after dropped the app from process.
I tested on iOS: 10.33
react-native: 0.47.2

@Vetalyo if user drops app from process, then yes, it is impossible. reference
https://developer.apple.com/documentation/uikit/uiapplicationdelegate/1623013-application
However, the system does not automatically launch your app if the user has force-quit it. In that situation, the user must relaunch your app or restart the device before the system attempts to launch your app automatically again.

If user restarted their phone, app should be waken automatically.

evollu, thank you!

This is possible with VOIP notifications; this is a capability you can register for. These notifications can wake the application, even if it has been force quit.


Swift 2.0 support

Thanks for the request! Support for Swift 2.0 has been added in the latest release.


Support for first-class JSON types broken for optional arguments

As the title says, the support for first-class JSON types is broken when using optional arguments.
Taking the example in the documentation
params do
  requires :json, type: JSON do
    requires :int, type: Integer, values: [1, 2, 3]
  end
end
get '/' do
  params[:json].inspect
end

and modifying it to
params do
  optional :json, type: JSON do
    requires :int, type: Integer, values: [1, 2, 3]
  end
end
get '/' do
  params[:json].inspect
end

gets me a

/home/knuckles/.rvm/gems/ruby-2.2.3/bundler/gems/grape-b3c51df71dca/lib/grape/dsl/parameters.rb:125:in `optional': group type must be Array, Hash, JSON or Array[JSON] (Grape::Exceptions::UnsupportedGroupTypeError)

It seems to me that the issue is that the check added to https://github.com/ruby-grape/grape/blob/80a46ba086697ddd8326e4b6292ff0b65cde81b5/lib/grape/validations/params_scope.rb#L140 should also be replicated to https://github.com/ruby-grape/grape/blob/80a46ba086697ddd8326e4b6292ff0b65cde81b5/lib/grape/dsl/parameters.rb#L121 , but I'm not confortable enough with the codebase to know if that's enough or the right thing to do (TM) :smile:

Looks legit. Try to write a spec for this.

:+1: I think you've got it, I didn't see that when I was adding the feature. Probably a good thing to do would be to declare, say, GROUPS = [Array, Hash, JSON, Array[JSON]] in types.rb and use it in both locations.

Existing spec: https://github.com/ruby-grape/grape/blob/master/spec/grape/validations/validators/coerce_spec.rb#L335

@ivoanjo Can you send a pull request?

I will try to refresh my branch and submit a PR. I didn't submit at the time as I wasn't sure that my fix was the right approach for the issue.

I can confirm that patching in fail Grape::Exceptions::UnsupportedGroupTypeError.new unless [Array, Hash, JSON, Array[JSON]].include?(type) fixed this. I can't work on the spec but just wanted to confirm that @ivoanjo's solution worked for me. 👍

Closing via #1290.


Add [SCAM ACCOUNT] #wallet #unsafe GBMAMH…ISNEPI

Address: GBMAMHV43UZ6XFVOHIKVZ7M3FHYA55FAQMNWN2HP7AYSWYRE27ISNEPI
Tags: wallet unsafe
Title: SCAM ACCOUNT
Requested by @mjginfo

ASSHOLE hacked your email addresses and reversed engineered Send with Received and takes all your XLM as a promotional Staking contest

The first thing you should do it to check and make sure your devices are not infected.
If you gave anyone your private key or recovery phrase it would be best to create a new Stellar Wallet and transfer any remaining assets.
Can you please give more details about this address as to its fraudulent activities.
Can you supply transaction numbers or screen shots? A chain of transactions is the most helpful. Do they have a website? assets to that.

@MJGinfo do you have any more information or details about this account and what happened?

@MJGinfo Please feel free to give updates and reopen this issue if you have more information.


Add support for variable expansion in .env files

Added dotenv-expand so that variables can be expanded in .env files.

@jaredpalmer thoughts?

nice 😍
thanks for your contribution


Add support for appveyor CI (windows)

Description
Add support for appveyor CI (windows)

Initial work at https://github.com/repejota/issues2markdown/tree/46-appveyor-support
TODO:

How to use GNU Makefiles?


Disabled MultiSelect Not Showing Previous Selected Chips After Being Disabled

Hi,
Is there a way to disable the MultiSelect but still show the items/chips that have been selected? I tried using disable with the alwaysRenderItemSelected prop. The dropdown is disabled but not showing any of the selected items before its disabled.
Thanks
Expected Result - I need to show what has been selected previously but not allow edits

Actual result - Dropdown is disabled but does not show chips

const [selected, setSelected] = useState([]);
const handleMultiSelectChange = (selectedItems) => {
        setState({ ...state, carType: selectedItems })
        setSelected(selectedItems);
        // Update the selected state when the user makes a selection
        console.log("called in multiselect");
      };

<View style={styles.container}>
    {carTypes ?
            <MultiSelect
                disable={car && car.id ? true : false}
                style={styles.dropdown}
                placeholderStyle={styles.placeholderStyle}
                selectedTextStyle={styles.selectedTextStyle}
                iconStyle={styles.iconStyle}
                data={carTypes}
                labelField="label"
                valueField="value"
                activeColor="#91A3B0"
                placeholder="Select The Services You Will Provide"
                value={selected}
                onChange={handleMultiSelectChange}
                mode='modal'
                renderLeftIcon={() => (
                        <MaterialCommunityIcons name="road" size={20} color={ colors.HEADER}  style {{paddingRight:35}} />
                )}
                selectedStyle={styles.selectedStyle}
                alwaysRenderItemSelected={true}
            />

        : null}
</View>

Any help is appreciated! thanks @hoaphantn7604


Instructions for registering package are out of date

From the RN docs
https://facebook.github.io/react-native/docs/native-modules-android.html
protected List<ReactPackage> getPackages() {
 return Arrays.<ReactPackage>asList(
   new MainReactPackage(),
   new AnExampleReactPackage()); // <-- Add this line with your package name.
}

thanks for reporting, but it's duplicated with #93


Updated configs to use list format for 'inherits_from'

I got the unit tests to pass with the following diff.
diff --git a/statick_tool/config.py b/statick_tool/config.py
index 2f207fd..a6fd41f 100644
--- a/statick_tool/config.py
+++ b/statick_tool/config.py
@@ -135,11 +135,12 @@ class Config:
                 )
             configs = ""
             for inherited_level in self.config["levels"][level]["inherits_from"]:
-                config = self.get_plugin_config(
-                    plugin_type, plugin, inherited_level, key, default
-                )
-                if config is not None:
-                    configs += config
+                if level is not inherited_level:
+                    config = self.get_plugin_config(
+                        plugin_type, plugin, inherited_level, key, default
+                    )
+                    if config is not None:
+                        configs += config
             if configs:
                 return configs
         return default

Looks like you need to merge in main again. Main now has your fix to the mypy issue causing workflow issues in this PR.

@denewiler, your diff caused a drop in coverage...I'll take a look at that later, but feel free to push another diff if you feel you can do it quicker, being more familiar with the testing.

Unfortunately every time I revisit this there's something new broken....any insight with the tox failure?   I ran the the Statick check on the main branch too, and get the same thing, so it's probably unrelated to this PR.

The tox errors are new for the main branch. I'll take a look. Note that there is an open PR that fixes coverage for the update_inherits branch. The PR is at https://github.com/gregtkogut/statick/pull/1 and is waiting on permission for actions to run.

Found the culprit at https://github.com/tholo/pytest-flake8/issues/87. The upgrade to flake8 v5 broke pytest-flake8 to give the error we are seeing.
AttributeError: module 'flake8.options.config' has no attribute 'ConfigFileFinder'

I have a one-line fix working in Windows, will PR soon if Actions pass.

The tox errors are new for the main branch. I'll take a look. Note that there is an open PR that fixes coverage for the update_inherits branch. The PR is at gregtkogut#1 and is waiting on permission for actions to run.

Thanks, hadn't seen that PR.  Waiting on your 1-line fix to pass the Action for both that PR and then eventually this one.

Thanks for the help,  I think this is finally ready.


sui_getEventsByObject docs

For start_time and end_time, the doc doesn't mention the unit. Can you please add more details?

Closing stale issues, please reopen if the issue still exists


Continuous integration

tests + coverage (coveralls) run on each commit

Changes Unknown when pulling e8f7137a9818f6546915d3777ffdaf0f1cb745d6 on continuous-integration into ** on master**.


[zh] sync concepts/architecture/cgroups.md

PR Summary

EN upstream: content/en/docs/concepts/architecture/cgroups.md
Sync to: content/zh-cn/docs/concepts/architecture/cgroups.md

Sync check by scripts/lsync.sh on main branch:
$ scripts/lsync.sh content/zh-cn/docs/concepts/architecture/cgroups.md
diff --git a/content/en/docs/concepts/architecture/cgroups.md b/content/en/docs/concepts/architecture/cgroups.md
index b0a98af660..b96d89e0d6 100644
--- a/content/en/docs/concepts/architecture/cgroups.md
+++ b/content/en/docs/concepts/architecture/cgroups.md
@@ -104,8 +104,8 @@ updated to newer versions that support cgroup v2. For example:
  DaemonSet for monitoring pods and containers, update it to v0.43.0 or later.
 * If you deploy Java applications, prefer to use versions which fully support cgroup v2:
     * [OpenJDK / HotSpot](https://bugs.openjdk.org/browse/JDK-8230305): jdk8u372, 11.0.16, 15 and later
-    * [IBM Semeru Runtimes](https://www.eclipse.org/openj9/docs/version0.33/#control-groups-v2-support): jdk8u345-b01, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS> and later
-    * [IBM Java](https://www.ibm.com/docs/en/sdk-java-technology/8?topic=new-service-refresh-7#whatsnew_sr7__fp15): <IP_ADDRESS> and later
+    * [IBM Semeru Runtimes](https://www.ibm.com/support/pages/apar/IJ46681): 8.0.382.0, <IP_ADDRESS>, <IP_ADDRESS>, and later
+    * [IBM Java](https://www.ibm.com/support/pages/apar/IJ46681): <IP_ADDRESS> and later
 * If you are using the [uber-go/automaxprocs](https://github.com/uber-go/automaxprocs) package, make sure
   the version you use is v1.5.1 or higher.

Sync check byscripts/lsync.sh on sync/cgroup_20231022 branch:
$ scripts/lsync.sh content/zh-cn/docs/concepts/architecture/cgroups.md
content/zh-cn/docs/concepts/architecture/cgroups.md is still in sync

Thanks to the reviewers in advance.
Best Regards,
Kivinsae Fang

/retest

/lgtm

/approve


python310Packages.reportengine: 0.30.dev0 -> 0.31

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.reportengine is: A framework for declarative data analysis
meta.homepage for python310Packages.reportengine is: https://github.com/NNPDF/reportengine/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.31 with grep in /nix/store/jg0a63qr1785bjq2dj7kfprqp2q846yv-python3.10-reportengine-0.31
found 0.31 in filename of file in /nix/store/jg0a63qr1785bjq2dj7kfprqp2q846yv-python3.10-reportengine-0.31

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.reportengine
python310Packages.validphys2
python311Packages.reportengine
python311Packages.validphys2
validphys2

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/jg0a63qr1785bjq2dj7kfprqp2q846yv-python3.10-reportengine-0.31 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.reportengine https://github.com/r-ryantm/nixpkgs/archive/bad6902c337a52a910e3b0f3a68e447765074c91.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/jg0a63qr1785bjq2dj7kfprqp2q846yv-python3.10-reportengine-0.31
ls -la /nix/store/jg0a63qr1785bjq2dj7kfprqp2q846yv-python3.10-reportengine-0.31/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package failed to build:

python311Packages.validphys2

3 packages built:

python310Packages.reportengine
validphys2 (python310Packages.validphys2)
python311Packages.reportengine

Maintainer pings
cc @veprbl for testing.

@GrahamcOfBorg build validphys2

The failure was propagated from seaborn, so LGTM.


Fixed Transfer Amount bug and made some improvements

@marco-ragusa it is an honour that someone found this script and was interested enough to actually edit it a bit. I appreciate it, mate!


Refactor and Test Cases

Added multi-column indexing
Added test cases
Update docstrings
Add Index Stats Function

Could you and @theyorubayesian add yourselves to the pyproject.toml file maintainers section? :smiley_cat:


Add a shallow copy method to AddressList

Address is immutable but AddressList is not. I needed copy to fix a bug in our api where we call add/remove while iterating over the AddressList. This way we can iterate over the copy will mutating the source list.

Sorry, missed that the change is for the AddressList. But would not just calling addr_list_copy = AddressList(addr_list) work?

It would. That's pretty much what the copy method is doing. I just thought that copy was more clear and intuitive, especially since AddressList already duplicates some other list functions like append, remove, __getitem__, etc.

IMHO the thinner interface the better. Fewer things to test and maintain.

Fair enough.


:label:  Album genre menu snd preserve data :memo:

This PR contains the following:

[ ]     List all music albums
[ ]     List all genres (e.g 'Comedy', 'Thriller')
[ ]     Add a music album
[ ] - [ ] All data should be preserved by saving collections in .json files.

Thanks for your review :slightly_smiling_face:

@enoqueJonas Thanks for your review.


update recording form

The form should include start; endmilage; isPrivate you shoud be capable of chainging it maybe provide also provide a discription


felte.dev docs svelte validation async-validations mentions useForm instead of createForm

Describe the bug
It looks like useForm is not part of svelte (it would be createForm instead).  Not clear because it is mentioned here in the svelte validation page.  I only saw code and doc references to useForm in other packages (react, preact, solid).
https://felte.dev/docs/svelte/validation#async-validations
I see debounced in create-form.ts in packages/core so it looks like this may simple be the wrong name in the documentation.
Which package/s are you using?
felte (Svelte)
Environment

OS:
Browser:
Version:

To reproduce
No response
Small reproduction example
No response
Screenshots
No response
Additional context
No response

Whoops! Nice catch! I just updated it. Thanks a lot 🎉


[TRACKING] Phase 1 - Basic Create/Delete

Description
For phase 1, we will focus on creating a CLI with basic creation/deletion for adding an Arkime installation into an existing AWS Account with existing VPCs/traffic sources.  Issue will be used to outline the overall progress of phase 1.
Still need to add the code/command to tear the demo traffic stacks down.
Tasks

DONE: Create CDK stacks for demo traffic generation (https://github.com/arkime/cloud-demo/pull/1)
https://github.com/arkime/cloud-demo/issues/4
https://github.com/arkime/cloud-demo/issues/5
https://github.com/arkime/cloud-demo/issues/6
https://github.com/arkime/cloud-demo/issues/7

Follow-up Items

https://github.com/arkime/cloud-demo/issues/12
https://github.com/arkime/cloud-demo/issues/18

Follow-up Work (CLI):

add-vpc: Add unit tests
create-cluster: Update to provide uses with viewer URL/username/password when finished
destroy-cluster: Update to check if the cluster is monitoring VPCs, abort if it is
remove-vpc: Add unit tests

Follow-up Work (CDK):

Capture Nodes Stack: Configure Auto-Scaling; currently wonky/broken
Mirror Stack: Get the user's VPC cidr and use for filter rules instead of hardcoding
Single Quotes: Action this open issue to change to a consistent quote style (https://github.com/arkime/cloud-demo/issues/18)

Follow-up Work (Workstreams):

Mirroring Resilience: Create mechanisms to make traffic mirroring more resilient to changes in user traffic load, network configuration (changes in subnets), and traffic soruces (changes in ENIs, short-lived ENIs)
Configurable Capture: Create mechanisms to surface capture process configuration to the user and enable updates of that configuration
Centralized Viewer: Create mechanisms to enable a single Viewer to surface details from many Arkime Clusters
Viewer HTTPS: Create mechanisms (either code or a written guide) to enable HTTPS for the Viewer Nodes
Cross-Account Capture: Create mechanisms to enable users to capture traffic from VPCs they own in other accounts (but the same region)
Global Viewer: Create mechanisms to enable Viewers to surface details from Arkime Clusters in other regions
User Management: Create mechanisms to enable better user management/AuthN/AuthZ than just the basic version provided by the Viewer

couple other thoughts

viewer https support with maybe user provided dns name should probably be higher than centralized
with capture auto scaling would like to see ability to optionally specify min/max as cli params
add cli ability to set/update the s3 lifecycle policy for pcap files with a X (90?) day default
I think it would be nice if there was a cli command to get the viewer password (assuming the user has the perm)

Would also like to figure out how we should represent capture node names, since using the ip is kind of useless. Maybe something like "--". Although if we share capture nodes across vpcs maybe just "-<instanceid"

Acceptance criteria met for this phase; follow-up work tracked in a new issue (https://github.com/arkime/cloud-demo/issues/20).  Resolving.


Admin UI Overhaul

More admin features to be added to built-in site UI.

[ ] Deleting/moderating forum posts/users
[ ] Stickying forum posts
[ ] Moving forum posts
[ ] Editing pages
[ ] Gallery management
[ ] Marking old events as completed (rpgs.change_rpg permission)

Probably never going to do many of these, I'm generally quite happy using the admin panel for most tasks of this kind.


Restart a pce node

Add new page to the Managing Anypoint Private Cloud section for stop/start/restart a PCE node.  Relocating this content from the PCE Operations Manual.

LGTM.


Update quickstart-protected-material.md

@PatrickFarley
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

@patrickfarley - The article articles/ai-services/content-safety/quickstart-protected-material.md might benefit from a copy edit. An editor will notify the listed author and recent contributors.


Idea: reprioritize the timeline

Recently I read this article describing an app that shows your feed in terms of the people you follow, not in terms of the quantity of tweets produced by their combined network. I know it would be a lot of work, but is there interest in having similar functionality in Refined Twitter?
Off the top of my head, you could organize the timeline:

by people (the way Florian's design concept does)
by lists
chronologically
maybe allow people to set a "weight" for each account, store it in localStorage, then sort by weight/recency similarly to Reddit posts?

I'm not sure how feasible some of these would be because I haven't looked at Twitter's API, but at the very least there might be some interesting discussion leading to an unrelated feature.

I like the idea, but I'm afraid that would be nearly impossible to maintain this as an extension. Requiring the user to login via twitter so we can use the API and re-order the timeline is basically writing a twitter client, and I'm not sure this is this extension is aiming for that. We want to make twitter itself more pleasant to use, yes, but I'm not sure that's the direction we're aiming for.

Ah, that makes sense 😃 I love what you're doing with this extension by the way!

I came across this because I was looking for similar. I like to follow people but some people just retweet or tweet wayyy to much and often flood my stream with just them. Before this extension I used Tweetbot, and a few times I marked some people as "disable retweets" to hide their retweets and my whole feed became a completely new feed as 27 retweets disappeared.
I'd like to see something that we can add say weight, and that weight can determine some things, like if my current stream has 50 tweets, and 10 of those are retweets by one person, weights could say "This person isn't as important to me, so hide some of those tweets/retweets so more important peoples stuff isn't drowned out"


more package metadata

also fixing npm warning about missing license identifier

Thank you, let's add them.
Did you see a warning that these fields are missing? If so, which command were you running?

I guess npm audit could have been the one that show the license issue. I think the other fields are used by vscode / market places, if I remember correctly.


CLI call setup if not setup

Vorpal allows you to call another one of it's actions from inside an action. https://github.com/dthree/vorpal/wiki/API-|-vorpal#vorpalexecsynccommand-options
When "run" is called, we should check and see if a "setup" is needed, and then run a "setup".
This would be one less command to get the project running.

This should be even easier to implement when we monolith


Add support for choosing a date range

It should be possible from the views that show the list of measurements to select a range for which to search for measurements.
The most basic implementation can just be something where you choose a start date and end date, but ideally it would be something prettier such as a timeline where you can brush the beginning and end (similar to the date selector here: http://square.github.io/crossfilter/)
cc @simonv3

So some thoughts:

[ ] When clicking on a bar in the view-country tab it'd be nice if the measurements below were filtered by that.
[ ] An actual date range picker for angular would be a good input field for now

I'm not sure whether our data updates fast enough for crossfilter to work very quickly, but I can investigate what would need to happen for it.

This is implemented as MVP


Delete query on model with soft_delete field throws panic

The panic occurs in method updateSoftDeleteField of the structTableModel struct. For some reason m.strct param has a nil pointer. I did not investigate it further.

Please show the stacktrace and the model.

The model:
type AliasToGroup struct {
	bun.BaseModel `bun:"entity_subtype_aliases_to_alias_group,alias:estatag"`

	Id        uuid.UUID `bun:"type:uuid,default:uuid_generate_v4(),pk"`
	AliasId   uuid.UUID `bun:"type:uuid,notnull"`
	GroupId   uuid.UUID `bun:"type:uuid,notnull"`
	CreatedAt time.Time `bun:",nullzero,notnull,default:current_timestamp"`
	DeletedAt time.Time `bun:",soft_delete"`
}

I will provide stacktrace from the part, when RunInTx method called. Some paths details rewritten since project under NDA.
Stacktrace:
runtime.gopanic at panic.go:971
reflect.Value.Field at value.go:850
github.com/uptrace/bun/schema.fieldByIndexAlloc at reflect.go:50
github.com/uptrace/bun/schema.(*Field).Value at field.go:51
github.com/uptrace/bun.(*structTableModel).updateSoftDeleteField at model_table_struct.go:219
github.com/uptrace/bun.(*DeleteQuery).AppendQuery at query_delete.go:145
github.com/uptrace/bun.(*DeleteQuery).Exec at query_delete.go:225
db.(*entitySubtypeAliasToGroupRepo).DeleteByAliasId at entity_subtype_alias_to_group_repo.go:94
entity_subtype_alias.(*updater).runUpdateTransaction.func1 at updater.go:92
github.com/uptrace/bun.(*DB).RunInTx at db.go:367

There is no enough info to reproduce this. Similar code works fine in tests - https://github.com/uptrace/bun/blob/master/internal/dbtest/soft_delete_test.go#L61-L114

Hum, what if you try to make delete query in Model((*Model)(nil))?

My query is:
conn.NewDelete().Model((*pgmodel.AliasToGroup)(nil)).Where("alias_id = ?", alias).Where("group_id in (?)", bun.In(groups.Ids())).Exec(ctx)

I guess it is wrong query since I'm trying to perform bulk delete query, but specify single model in .Model method.
Probably correct query should be:
conn.NewDelete().Model(groups).Where("alias_id = ?", alias).Exec(ctx)

or
conn.NewDelete().Model(([]pgmodel.AliasToGroup)(nil)).Where("alias_id = ?", alias).Where("group_id in (?)", bun.In(groups.Ids())).Exec(ctx)

Will test both.

The query works fine:
conn.NewDelete().Model(&[]pgmodel.AliasToGroup{}).Where("alias_id = ?", alias).Where("group_id in (?)", bun.In(groups.Ids())).Exec(ctx)

If it possible - may be make sense to add check for bulk deletes to throw error (instead of panic) if single model ptr specified in Model method instead of ptr of models slice.

Update:
Query also works fine:
conn.NewDelete().Model(&pgmodel.AliasToGroup{}).Where("alias_id = ?", alias).Where("group_id IN (?)", bun.In(groups.Ids())).Exec(ctx)

So no need to specify slice of models in Model method.
Seems like the problem definitely with NewDelete().Model((*Model)(nil)) approach. For some reason delete query does not allow such way of model specification.


Mimic polaris popover placement

Hi there!
I've extracted the popover placement from my earlier PR (#195) and fixed the bug that was causing the autocomplete to close when selecting an item.
https://user-images.githubusercontent.com/64841/153929739-bc6b1bd9-63e2-4ad2-9ab4-d69cfd47584a.mp4

@kirillplatonov I've updated the PR based on your system tests changes. I had to update the autocomplete a bit because now the popover it not a child of the autocomplete anymore. But just an element that lives in <body>.
Curious what you think 😄

@kirillplatonov Thanks for the review! And finding that bug.
I've got the polaris-autocomplete:change event working now but its not pretty. The input elements from Autocomplete::OptionComponent are not children anymore for the autocomplete so we have to look them up using this.popoverController.popoverTarget.querySelectorAll (like with the other targets).
But, this.popoverController is not directly available when connect() is fired. So I've created a "wait until this condition is true" function before trying to use this.popoverController and finding the elements to bind the click event on. It works but I'm not sure if this is the best way to go.
Alternatively I was thinking to dispatch a custom event from the option-list-controller but it would be hard to tell inside of which autocomplete the option was clicked.
I'm gonna try to see if there are different approaches. If you might have some ideas let me know 😄

I like the idea of a custom event. We could have a separate autocomplete_option_controller that will handle click, find relevant autocomplete, and dispatch the event.
As for detecting which popover belongs to which autocomplete - we could add data-ref attribute to autocomplete and popover. And put some random generated ID to ref on the server-side (should be easy since we render both autocomplete and popover together in the same component).

@kirillplatonov I've implemented the CustomEvent approach and I'm curious what you think.
Let me know if you'd want me to change something!
Otherwise I can squash the branch into a few sensible commits and merge :)

@kirillplatonov hi! would you possibly have some time to have a look at this PR? would love to hear your feedback 😄

Hey @yourivdlans!
I've installed your forked gem version and, when I load the app in Shopify admin, I get the following error:

The first error appears immediately on page/form load, the second one appears when I click inside the autocomplete input field.
Here's my autocomplete erb:
<%= polaris_autocomplete do |autocomplete| %>
  <% autocomplete.text_field(label: "Artisan", placeholder: "Start typing to search for artisan...") do |c| %>
    <% c.prefix do %>
      <%= polaris_icon(name: "IllustrationMajor") %>
    <% end %>
  <% end %>
  <% autocomplete.section do |section| %>
    <% @vendors.each do |vendor| %>
      <% section.option(label: vendor, value: vendor) %>
    <% end %>
  <% end %>
<% end %>

On polaris_view_components v0.10.1 the autocomplete popover appears as expected and clicking on an element doesn't close the popover.
However, I don't know how to catch that event and how can I populate the input field value as stated here: https://github.com/baoagency/polaris_view_components/issues/242
If you could help me with this probably simple solution for you, I can help you with further autocomplete component testing. :D 🙏

@yourivdlans yeah, I will take a look this weekend  👀

@vfonic thanks for taking a look!

I've installed your forked gem version and, when I load the app in Shopify admin, I get the following error:

I got the same error but when I was looking where the error came from it looked like the source was outdated. What I did to solve this was import registerPolarisControllers from my local polaris_view_components repo.
import { registerPolarisControllers } from "../../../../polaris_view_components"
registerPolarisControllers(Stimulus)

After this the autocomplete seemed to be working nicely from the shopify admin. There might be a more elegant way to solve this for local development, maybe @kirillplatonov has some suggestions 😄

On polaris_view_components v0.10.1 the autocomplete popover appears as expected and clicking on an element doesn't close the popover.
However, I don't know how to catch that event and how can I populate the input field value as stated here: https://github.com/baoagency/polaris_view_components/issues/242
If you could help me with this probably simple solution for you, I can help you with further autocomplete component testing. :D 🙏

Good one! I've looked at your PR (#244) and copied over a basic implementation of the way you handle the autocomplete closing and filling the input with the selected item.

There might be a more elegant way to solve this for local development

Of course we could also just update our package.json to refer to the local version of the npm package 😅
{
  "polaris-view-components": "file:./../polaris_view_components",
}

@vfonic actually, it seems like changes from this PR have been ported to https://github.com/baoagency/polaris_view_components/pull/204. Let's go with https://github.com/baoagency/polaris_view_components/pull/204 for these changes, since it also includes big popover refactoring. But we still need hidden input to submit the selected value, so feel free to open PR for that.

That's awesome! Thank you @yourivdlans for working on this!
@kirillplatonov the project I started, that was supposed to use this gem, has been moved to another team and they will build the app in Node.js. I won't be using polaris_view_components at this point, maybe in the future. That being said, I won't have the time to work on adding the hidden field for autocomplete component. :/

@vfonic no problem. Added an issue for that #252. Me or someone else will take a look at that.
Thanks for your help and code review! 🙏

That's awesome! Thank you @yourivdlans for working on this!

No problem! Thank you for the review 😄

Looks good. Added a few minor comments. And it seems like some old popover unit tests have been removed. Can we migrate them to system tests instead?

Thanks! I believe I already migrated those to test/system/popover_component_test.rb or was there something I missed?

Awesome thanks!


[Doc] Add missing info to building/testing section of README

Today, the README is missing a few minor requirements (install Nuget, e.g.) and doesn't explain in detail how to setup your dev environment with IntelliSense.
This change adds that missing documentation, including specific steps to create a .sln file with IntelliSense.

LGTM 👍. @jonwis if you have no additional comments or requests, we can go ahead and merge. No need to wait for a build to complete for this.


Inconsistent FD radius?

Compare
https://github.com/poldracklab/mriqc/blob/ab49505f4379be576e5ed923fb3fbe9186562b14/mriqc/interfaces/viz_utils.py#L313
with
https://github.com/poldracklab/mriqc/blob/ab49505f4379be576e5ed923fb3fbe9186562b14/mriqc/qc/functional.py#L179

Yes, looks like an error. Thanks for spotting it.


[BUG] - error TS2322: Type 'string' is not assignable to type 'number'.

Describe the bug
When trying out the 24h example (https://tonysamperi.github.io/ngx-mat-timepicker/) with format="24" I get the error
- error TS2322: Type 'string' is not assignable to type 'number'

To Reproduce
https://angular-1rz8wv.stackblitz.io
Expected behavior
format should accept string instead of number
Desktop (if execution):

OS: Ubuntu 22.04
Browser: chrome

** Versions

ngx-mat-timepicker version 15.1.+
@angular/core version 15.2.8
@angular/material version 15.2.8

Ok fixing the example!


Add combat-indicators

Show highlight of Player and NPCs when in combat

In violation of "Indicates which player an NPC is focused on"? Otherwise this could be merged with the interaction highlighter?

@LeikvollE - Yeah, I did consider that text before I started with this plugin. I ended up interpreting the spirit of that guidance as not allowing an NPC to show highlighting to various players (including players other than local). If the consensus is that this violates Jagex guidance, I can rework to only show what the local player is targeting.
I also saw the Interaction Highlighter plugin PR yesterday right before I submitted this pull request. I agree, it makes sense to group similar highlighting functionality together, so I'm ok with it being merged.

@dekuScrub731 I don't know if you have read the discord discussion about the interaction highlighter, but it will be included in core and Adam has added functionality somewhat similar to this plugin.

Closing this PR as most of "player initiated" actions are covered under interaction highlighter changes. NPC initiated highlighting may be a gray area in terms of Jagex permitted actions.


Editable List item

I'll really like to use a list with editable items when I'll do double click in an item I can edit this item

I'm doing an application where I have a list of items and I want to edit some items, I thought this functionality is essential to some apps.

Hi, I would like to work on this issue


Add multiple recipients support

Feature Request
Is your feature request related to a problem? Please describe:
You can only send a message to one user each time the program is ran.
Describe the solution you'd like:
The program should allow for various users chat ids and user names to be input as environment variables.

Multiple users and chat IDS are now supported. There still needs to be multiple stock ticker support.


Undefined symbols for x86_64 when using resolver="2"

Problem
I was running into a strange dependency management issue that seemed like it might be solved with the resolver, however when I tried it out, it causes the linker to spit out a huge Undefined symbols for x86_64 error for symbols from core . I assume it's a bug in resolver="2" because it compiles when that isn't set.
Steps

Clone https://github.com/EmbarkStudios/rust-gpu
Checkout resolver-error
cargo build

Notes
Output of cargo version: cargo 1.52.0-nightly (c68432f1e 2021-03-02)
Error Message
(Gist because it exceed's GitHub's character limit for issues)

One issue is that it looks like it is building the dylib multiple times.  Cargo is issuing a warning about this:
warning: output filename collision.
The lib target `rustc_codegen_spirv` in package `rustc_codegen_spirv v0.4.0-alpha.0 (/Users/eric/Proj/rust/cargo/scratch/rust-gpu/crates/rustc_codegen_spirv)` has the same output filename as the lib target `rustc_codegen_spirv` in package `rustc_codegen_spirv v0.4.0-alpha.0 (/Users/eric/Proj/rust/cargo/scratch/rust-gpu/crates/rustc_codegen_spirv)`.
Colliding filename is: /Users/eric/Proj/rust/cargo/scratch/rust-gpu/target/debug/deps/librustc_codegen_spirv.dylib
The targets should have unique names.
Consider changing their names to be unique or compiling them separately.
This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
warning: output filename collision.
The lib target `rustc_codegen_spirv` in package `rustc_codegen_spirv v0.4.0-alpha.0 (/Users/eric/Proj/rust/cargo/scratch/rust-gpu/crates/rustc_codegen_spirv)` has the same output filename as the lib target `rustc_codegen_spirv` in package `rustc_codegen_spirv v0.4.0-alpha.0 (/Users/eric/Proj/rust/cargo/scratch/rust-gpu/crates/rustc_codegen_spirv)`.
Colliding filename is: /Users/eric/Proj/rust/cargo/scratch/rust-gpu/target/debug/librustc_codegen_spirv.dylib
The targets should have unique names.
Consider changing their names to be unique or compiling them separately.
This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
warning: output filename collision.
The lib target `rustc_codegen_spirv` in package `rustc_codegen_spirv v0.4.0-alpha.0 (/Users/eric/Proj/rust/cargo/scratch/rust-gpu/crates/rustc_codegen_spirv)` has the same output filename as the lib target `rustc_codegen_spirv` in package `rustc_codegen_spirv v0.4.0-alpha.0 (/Users/eric/Proj/rust/cargo/scratch/rust-gpu/crates/rustc_codegen_spirv)`.
Colliding filename is: /Users/eric/Proj/rust/cargo/scratch/rust-gpu/target/debug/deps/librustc_codegen_spirv.dylib.dSYM
The targets should have unique names.
Consider changing their names to be unique or compiling them separately.
This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
warning: output filename collision.
The lib target `rustc_codegen_spirv` in package `rustc_codegen_spirv v0.4.0-alpha.0 (/Users/eric/Proj/rust/cargo/scratch/rust-gpu/crates/rustc_codegen_spirv)` has the same output filename as the lib target `rustc_codegen_spirv` in package `rustc_codegen_spirv v0.4.0-alpha.0 (/Users/eric/Proj/rust/cargo/scratch/rust-gpu/crates/rustc_codegen_spirv)`.
Colliding filename is: /Users/eric/Proj/rust/cargo/scratch/rust-gpu/target/debug/librustc_codegen_spirv.dylib.dSYM
The targets should have unique names.
Consider changing their names to be unique or compiling them separately.
This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.

You can run cargo tree -i rustc_codegen_spirv -e features to get an explanation why it is being built multiple times.
Alternatively, you can run with the --target flag to ensure that build-scripts aren't shared.
I was able to successfully build that branch using --target and the latest nightly (nightly-2021-03-17) on both apple and linux.  Can you try that?
Also, there are some known issues with dylib linking (for example, see https://github.com/rust-lang/rust/issues/82151).  In general, dylibs are poorly supported, so using them may have a rough experience.

In general, dylibs are poorly supported, so using them may have a rough experience.

Yeah, sadly this is the only main legitimate usecase for dylib (a rustc plugin), though long-term we may be able to build a custom driver, like clippy and miri have (or "just" upstream the backend, though that has other tricky implications).

I'm going to close this as a duplicate of #6313 which is tracking the general problem of duplicate artifact naming.  Unfortunately dylibs are particularly difficult to handle since they are sensitive to the path and filename, which generally can't contain cargo hashes.  Cargo definitely needs to do better here, especially with the error messages.
As for the greater issue of having a story for supporting dylibs, I think that's a little bigger than what can be dealt with in a cargo issue.

As for the greater issue of having a story for supporting dylibs, I think that's a little bigger than what can be dealt with in a cargo issue.

I'm not sure I agree with this being a dylib issue so much as it is a resolver="2" issue. The project builds, compiles, and links successfully with resolver="1", it's only when resolver="2" is added do these linker errors appear.


Optimize memory usage on Mac by pooling memory passed to sysctl

The sysctl implementation allocates 256 KiB for every invocation.
In go-sysinfo a sync.Pool is used to minimize the amount of memory that is allocated for each call. It uses a buffer from the pool to make the call then allocates only the size required rather than ARG_MAX.
Port this same optimization to the system metrics package. Here is one example where it would apply:
https://github.com/elastic/elastic-agent-system-metrics/blob/5f485743a1d0c95db81e19ab554aba536a201da5/metric/system/process/process_darwin.go#L154-L161
We could avoid allocating a new slice for every process with this optimization.

Something else to consider: Instead of allocating a single, large chunk of memory ahead of time, we can use sysctl's own memory allocation...thing to make sure we only allocate what memory we need. For example, on MacOS 12, it will allocate ARG_MAX bytes, which is 1048576 but the average process will actually need something closer to only 600.


Enable creation of multiple connections of same integration type

Allow multiple databases and other sources be connected instead of one per integration type.

+1

Changes for this issue can be tracked in this PR: https://github.com/DrDroidLab/PlayBooks/pull/139

This is released, closing the ticket.


Feature: Addition of Job Section Page

Related Issues

#408

Proposed Changes

Addition of Job section portal Page

Additional Information

Any additional information or context

Checklist

[ ] Tests
[ ] Translations
[ ] Documentations

Screenshots
Original

Updated

Great Work @devasyarajguru
Please keep this page updated as your find new sources

Great Work @devasyarajguru
Please keep this page updated as your find new sources

I have added 10 websites, i can add more. Tell me how many websites you want to add? @AnirudhPanda . Thank you for merging my PR


Uncaught TypeError: Cannot read property 'ThemeManager' of undefined in the example

I checkout the example, but I can't see anything on the browser
The error on the console log is:
Uncaught TypeError: Cannot read property 'ThemeManager' of undefined

I'm not familiar with the project but checking out at v0.7.5 solved the issue for me.
git checkout tags/v0.7.5.
Hope this helps.

Dup of #609 which has been fixed by #652

@ivanceras The example currently uses the v0.8.0 prerelease. Instructions on how it can be are included in #652


unit test template

A unit test bench template. It intends to help new users create unit tests.
Three components, Src, Sink, Dut. Handles json and stf input test types.
Conforms to coding style through clang-formt.
I created this for myself a while back to help learning the concepts, updated for coding style.
It was useful to me when learning sparta/map/olympia.

this fails for MAC OS but I do not see a connection between my PR and the mac failure. I believe it fails due to the warning installing conda.
Warning: Future Miniforge releases will NOT build Mambaforge installers. We advise you switch to Miniforge at your earliest convenience. More details at https://conda-forge.org/news/2024/07/29/sunsetting-mambaforge/.
Warning: ERROR: executing pre_install.sh failed

re-running the checks with change, it now works.

Hi Knute.
Yes, moving it to sparta is fine with me.  Couple questions.
Does this collide with SkeletonPipeline? Honestly I'm only now noticing
that sparta example and the similarities, my bad.
If moved into sparta should it be only there, or in both olympia and sparta
?
Your call.
Jeff
On Mon, Dec 16, 2024 at 11:18 AM Knute @.***> wrote:

@.**** approved this pull request.
This is super awesome. What are your thoughts about moving this into
Sparta?
—
Reply to this email directly, view it on GitHub
https://github.com/riscv-software-src/riscv-perf-model/pull/236#pullrequestreview-2506818897,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A25MMC62VWSVG4PLNPTBPMD2F4DMXAVCNFSM6AAAAABTCVXQYGVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDKMBWHAYTQOBZG4
.
You are receiving this because you were assigned.Message ID:
@.***
com>

I don't think it collides with anything in Sparta, really.  If we do put this in sparta, a set of cool scripts would be nice to set up a unit.  But I think here is fine.


Create/manage extended namespace names for epinio organizations

When creating an org in epinio, we create a namespace with the very same name - and esp. fail, if that namespace already exists.
E.g. users can't create an organization named "quarks", aso.
It would be nice, if we could e.g. just extend the resulting namespace names, in order to give more freedom with organazition names to users:
e.g. creating org "quarks" would result in a namespace "epinio-quarks", and just be managed accordingly
That would still, or even be more user readable from the operator side.

... and of course, it would start with workspace -> epinio-workspace :)

One thing to consider is the maximum allowed length for Kubernetes objects. In most cases, the Epinio user will see an error if they try to create an object with a name that exceeds that limit. Prefixing resource names reduces the number of allowed characters for the user. We could untie ourselves from those limitations if we consistently generated valid UIDs (<63 characters) for all objects and used annotations for the human readable name. Annotations don't have a character limit afaict (labels do: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set).
On the other hand, finding objects by annotation is not going to be very efficient (that's what labels are for and that's why their length is limited). Also it's going to complicate the code in many different places. E.g. anywhere an org name is used, we will need to do a lookup to find the actual namespace name.
Another option is to only support org names which are 63-16 in length (16 is the number of characters in epinio-workspace).

True, it would restrict max. characters to 63-7 (epinio-) - I just meant we should start to make the default workspace epinio-workspace. An org called quarks should end up in a namespace epinio-quarks, so 63-7 ...

Just for comparison - a cf org could hold 255 chars.
Also a bit similar is https://github.com/cloudfoundry-incubator/eirini/issues/62.
So one (let's make the code more complicated) solution could be

Allow 63, or up to 255 chars for epinio ORG names
make the related kubernetes namespace start with "epinio-", to sort the output of ORG around 'epinio-'
if an ORG name exceeds 63-7 chars, it will get cut at char 49 and extended by "-<random 6 digit>"

That would mean, epinio ORG would support e.g.:

"grouped listing" in kubernetes
ORG names that exceed 63 chars, e.g. up to 255
up to 56 chars human readable as kube namespace
49 chars human readable if the ORG name exceeds 56 chars

This would totally support human readable style, until someone decides to create multiple ORGs, where the name starts varying after the 49th char, only.

Another way to go would be to rename orgs to namespaces and stop pretending they are anything other than that. Then we could simply say "namespace already exists" without implying it's a namespace where applications are deployed. Depending on how we implement authorization in the future this may be a good thing. E.g. if we define Epinio user permissions as native kubernetes RBAC rules then there is no need for an abstraction (e.g. orgs). If we do a custom thing, then maybe it makes sense to handle Epinio namespaces as a special kind.

See also #544 and #611

Fixed via #544


bpf: Improve MTU, IP fragment, TCP connection tracker handling

The individual commits provide more detail on the motivations of each aspect of this PR, but overall it aims to improve the interaction with external services by:

Reducing fragmentation when receiving regular-sized packets from the outside world;

Previously, large TCP responses would be fragmented when transmitting into cilium_host due to its low 1450 MTU. It was set this way to prevent fragmentation into the container veth device.
A better approach to allowing such packets to go through to the containers is just to raise the MTU on the host side of the container's veth pair.
Longer term, it would be good to configure cilium_host MTU the same as the underlying device for external access. Not addressed in this PR.

Setting the MTU for routes within the node vs within the cluster according to reasonable expectations;

Within the node, ~64K.
Within the cluster, 1450 (to allow tunneling).

Restoring #3629 now that MTU issues are fixed with the above;

Only allow SYN packets to create conntrack entries.

Explicitly dropping fragmented packets on ingress when policy is enabled.

Such packets can't be handled reasonably by the connection tracker, it has no fragment awareness and therefore isn't able to derive L4 ports / policy for later fragments.
Future work will plan to route such packets via a reassembly interface so this should not end up being hit.

Todo:

[x] Test external access manually once more
[ ] Test intra-cluster connectivity with netperf or similar to ensure we haven't introduced any regression in node-to-node connectivity

test-me-please

test-me-please

Unfortunately it looks like I was wrong about receive-side MTU being ignored in a veth device. I've just reproduced connectivity failure behaviour with this PR where a frame of size 1476 is seen via tcpdump on the host-side of a veth pair, but not seen on the container side of the same veth pair. MTU was 1500 on host-side, 1450 inside. Raising the MTU inside container relieved the issue.


Remove "weatherLocation"

Companion to https://github.com/arduino/library-registry/pull/2486

Done here https://github.com/arduino/library-registry/pull/2486#issuecomment-1440444114


Makefile: exclude .git/.smoketest+no deb on Darwin

Excluding .git and .smoketest speeds up makefile initialisation.
Excluding attempted .deb build when not on Linux means we can run make release on Darwin.

LGTM!
No errors, no warnings. :shipit:

  Generated by :no_entry_sign: Danger


Fix build on Ubuntu 18.04

These changes get the code building for me on stock Ubuntu 18.04 using gcc 7.4. The most invasive part is changing the SphericalTriangle class to contain the A, B and C Pos structs directly rather than in an anonymous union, which is allowed on MSVC and Clang but not GCC. Since the ABC variant of the union doesn't appear to be used anywhere this looks fine to me.
There also appears to be a racy bug where sometimes the isnan assert in rand_toward_sphericaltri() is triggered, but I haven't been able to debug that because it's not triggered in gdb for me currently (and adding prints to check the values stops it from occurring).

Thanks for the contribution; I'll have some comments first, though:

I don't see any particular reason to allow earlier CMake versions, but it's fine.
Thanks for pthreads fix.
Thanks for the sqrt fix. However, instead of using sqrtf, should use std::sqrt, as this is C++.
Thanks for anonymous unions fix. MSVC is a lot more-flexible than other compilers in this regard—GCC also supports it, but has rules on the types contained which seem bogus to me. But you're correct that this wasn't used, so removing it is fine—and makes the code simpler besides!
The +1 is not necessary when seeding the RNG. When thread_index is 0 (as it will be on every platform, not just Linux), it still gets hashed, so the resultant RNG state is quite nonzero.
I'm not able to pin down the assert trip on this end. I may be able to look at it more later.

Personally I think it's better to specify the actual minimum required version of cmake to get your code to build correctly so people don't have to break out of their package manager or add more repos unless it's necessary. Ubuntu 18.04 has 3.10, 16.04 has 3.5 and Centos 7 is all the way back at 2.8 (though I wouldn't recommend going <3.0). It's trivial of course to modify the cmake version oneself, but then you're left wondering if there's something in 3.14 the build was actually using and has the thing built correctly? If you're really not using anything more recent in cmake then I would prefer setting the minimum version to 3.5.
Regarding the thread_index offset - the issue isn't with the thread_id but the fact that std::hasher() returns 0 for a 0 input on gcc and clang (which you can verify here: https://wandbox.org/permlink/Lq8lAXx58EcbGGDY). I assume MSVC does something more sensible.
I'll close this and make a new PR with std::sqrt().

Re: CMake, for me, I see an out-of-date build tool as a problem with the build environment. (Wherefore also C++17, Ubuntu 19.04, etc.)
Re: thread_index; ah, I see the problem now. Yeah, the output of get_hashed(...) needs to never be 0, and there's no particular guarantee imposed by the standard there. +1 works, but there's no particular reason it should, and I'd prefer something less-arbitrary that fixes the underlying problem. Maybe something like this?
//Seed the RNG with the thread index (hashed to increase variance).  The seed must be nonzero,
//	so we enforce that explicitly.
uint32_t seed = get_hashed(thread_index);
if (seed==0u) ++seed;
rng.seed(static_cast<Math::RNG::result_type>(seed));

Not everyone can change their build environment that easliy :) Lots of production environments in visual effects are locked into stable (i.e. old) versions of linux. The VFX Reference Platform is only just mandating C++14, for example. Anyway, it's not a big deal in this case.
After doing a bit more digging, the problem with the hash is actually a bit worse than I first realized - on GCC and Clang, std::hash of an integral type is the identity function! https://stackoverflow.com/questions/38304877/why-stdhashint-seems-to-be-identity-function
In which case, simply incrementing if the seed is 0 will cause the first two threads to have the same seed. Offsetting might be the best idea after all.

Oof. Identity is a terrible hash function for avalanching (and that's the main reason for doing this). I had heard of identity being used, but didn't expect it to be in the standard library. But if it's that way on Linux, then I guess one cannot use std::hash at all.
What do you think about having the hashing be done "manually"? Thinking some simple public-domain hash specialization for get_hashed<[Integral]>(...). This would allow better consistency between platforms as-well.
Did you want to open a new PR for the other changes (first three commits, except using std::sqrt) while we, ah, hash this out? (N.B. I'm a bit new to collaborating on Github, but maybe a separate PR for each would be clearest . . . ?)

Sure thing I'll make a separate PR for the first chunk.
For the RNG - I'm not too familiar with PCG, but should't using incrementing seeds be fine?

Unsure. Most RNGs produce similar or correlated starting numbers for similar seeds (and incrementing clearly produces very similar seeds). I haven't, however, specifically tested if PCG suffers from this problem.

Maybe Bob Jenkin's hash or a few rounds of TEA to initialize the seed?

(The rest of the changes have been merged; thanks.)
I went ahead and implemented the hashing scheme myself "manually", so it should now work regardless of platform. I did some cursory tests to make sure it works, but I'm currently traveling from the conferences so some kind of sanity check would be welcome.
The solution I went with is basically that of my previous message, except I also implemented the hash directly instead of relying on std::hash. Note that the increment from 0 happens after the hashing, and the hashing itself will definitely do some scrambling, so the chance of two threads both being seeded with 1 is low.

Great! I can confirm a clean checkout, build and run now works from your
repo.
Cheers,
Anders
On Mon, 15 Jul 2019 at 22:11, Ian Mallett<EMAIL_ADDRESS>wrote:

(The rest of the changes have been merged
https://github.com/imallett/simple-spectral/pull/3; thanks.)
I went ahead and implemented the hashing scheme myself "manually", so it
should now work regardless of platform. I did some cursory tests to make
sure it works, but I'm currently traveling from the conferences so some
kind of sanity check would be welcome.
The solution I went with is basically that of my previous message
https://github.com/imallett/simple-spectral/pull/2#issuecomment-508970004,
except I also implemented the hash directly instead of relying on
std::hash. Note that the increment from 0 happens after the hashing, and
the hashing itself will definitely do some scrambling, so the chance of two
threads both being seeded with 1 is low.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/imallett/simple-spectral/pull/2?email_source=notifications&email_token=AAOYQXK2GAZ5537H6VP2WFLP7REN7A5CNFSM4H6IITGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ5IGPI#issuecomment-511345469,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOYQXP5MUUD5CKJWYPE6RTP7REN7ANCNFSM4H6IITGA
.


Add network to monitoring

Keys in goca call have no effect on the data. By I've added filter (disabled if no keys provided) that provides data only for given keys, because full monitoring request is something like 12k json...