[EPIC] Create Two New Epics based on Gnosis Chain Finality

Epic 1:
Allow Pigeons to speficy multiple RPC providers with auto-fail-over if RPC errors.  Will you create an epic that will allow pigeons to add multiple RPC providers for any of their chains. Also, that if RPC endpoints return an error, the pigeon will be able to fail over to their next endpoint?
NOTE: This may impact how long a pigeon will get a message and message assignments. We will need an epic to document the question of whether this is an issue.
EPIC 2:
Add Finality Duration for each chain when adding chain proposal. Maybe a setting in config.yaml.
So it appears that Gnosis does not reach blockchain finality (when a tx is considered as in a block) for about it's 2 epochs ~160 seconds = 2.6 MINUTES!!.  This means that if Paloma is faster than Gnosis, Validators will NOT be able to attest to a tx. It's not yet on chain for nearly 3 minutes.
We will need to allow all pigeons to specify the finality needed for each chain. This may be a setting we can set in pigeon as validator-controlled, but again, I think it will impact assignments if pigeons are too slow and Paloma expects fast attestation.  If it's easiest to just set it as a feature in pigeon, then the question is: How will such a setting affect assignments. Gnosis is a slow-finality chain
From @verabehr

I‘m not sure if this would be an issue at assignment. We fail over to another pigeon if the first doesn’t deliver. The mass hailing’s that we’ve seen is because pigeons don’t attest to a message

This is still WIP, some thoughts

I think it would make sense to combine this into one epic as the overall purpose is to prevent mass jailings and move messages through the queue quickly
There is something else going on. Validators are running out of gas on Paloma. It's not clear yet if there is also a gnosis specific issue actually happening. WIP notes here https://www.notion.so/volumefi/EPIC-05-17-Prevent-mass-jailings-due-to-lack-of-evidence-76e97b58dcc346068e906e32e3b84363?pvs=4

@taariq have we seen any evidence that finality on gnosis is an actual issue for us? I'm still wrapping my head around it, but I would think that is an issue, we should see problems far more often given the number of tx we're running on Gnosis?

https://www.notion.so/volumefi/EPIC-06-14-Pigeon-RPC-failover-920c4e7344a94da68ea3efdacc648967?pvs=4
https://www.notion.so/volumefi/EPIC-06-14-Custom-chain-finality-settings-25503197406946fa8924b44e9ca9e171?pvs=4


complaining about missing jar files during server startup

Hi,
I am using SPRING boot version v1.5.6.RELEASE. I am getting some jar file missing issues while starting up the application. I am able to do mvn:clean install

errorSpringBoot.txt

Hi,
does your project work with version 2.0.3?

Hi,
Sorry for replying late. It is not working with 2.0.3 version as well. If I add the JAR as an external dependency from eclipse I can run the project

Actually I don't support Spring. Maybe in later versions, but currently not. Sorry. But if you want, you are welcome to do a pull request and fix the problem.


unknown method PrintTabs for service dashboard.Plugin

Hi,
starboard v0.9.2 + starboard-octant-plugin v0.9.2 is not working with octant v0.19.0 / v0.18.0
Plugin Error
getting tabs from plugins: handle object: running on starboard-octant-plugin: printing tabResponse for plugin "starboard-octant-plugin": grpc client print tab: rpc error: code = Unimplemented desc = unknown method PrintTabs for service dashboard.Plugin
No problem with octant v0.16.3.
Any idea would be appreciated.
Thanks.

👋 @lechugaletal Thank you for reporting this issue. We're aware of that. Octant 0.18+ introduced a non backward compatible change in Go Plugins API in order to support a nice feature of registering multiple tab for a given GVK. To fix that we have to bump up Octant dependency in go.mod. We're going to do that along with the upcoming release of Starboard v0.10.0

Great job.


Loader gets crashed in iOS 13

The loader gets crashed in SKActivityIndicatorView.swift, inside configureActivityIndicator(withStatusMessage:, isUserInteractionEnabled:) method.
The crash is actually happened in these lines,
if activityIndicatorView?.superview == nil && userInteractionStatus == false {
backgroundView = UIView.init(frame: window!.frame)
backgroundView!.backgroundColor = backgroundViewColor
window!.addSubview(backgroundView!)
backgroundView!.addSubview(activityIndicatorView!)
} else {
window!.addSubview(activityIndicatorView!)
}
here in the first line. and I checked the backgroundView is getting nil.  Also the pod is not updated to support iOS 13. Please help.

You can resolve it to comment " var window: UIWindow?" if its not needed. But I need to use UIWindow for webview, in older version of iOS for webview I need to add "var window: UIWindow?". So I'm stuck because there is I can't add OS version check.

@SachK13 Have you any idea to resolve it. Because due to the use of WKWebView I need to add var window: UIWindow? for older version support, and It crashed for iOS 13. If I remove the var window: UIWindow? then I get the crash for WKWebView in older versions, and it solution to add var window: UIWindow? in app delegate.

@hilajqinnovation @aliwaseem72 This has been fixed 1.0.0. and code has been updated to support iOS 13 and above with Swift 5.x+.


issuereport to use commit rather than tag

Why trying to come up with the numbers for 3.0, I run into the issue that gh_issuereport.py expects a tag for a release, but that's not available before said release is done, so it would be great to be able to use either a branch (and then it takes the top of that branch as reference), or a commit hash.

Never mind, I should have read the docs more carefully...


mypets leaderboard (lb pets) broke on both bots

🐛 Bug Report
Doing the "lb pets" command brings up the unexpected error message. I assume this is related to the recent optimizations for Leaderboards, as it began to occur around the time that update went live.  I understand this isn't a top priority issue, but would be great if you could look into it when available!

title is supposed to be both bots, not both boths lol

Found two more commands that are also effected by the "Unexpected error" message. I assume they have the same issue, as they all popped up around the same time.

OSB now has the unexpected error for channel disable.

Fixed in next update.


How to install?

I'm on neovim 0.4.4-1 using pathogen and I've tried cloning it to bundle and autoload but it doesn't seem to work. What's the correct way to install it? A brief install section in the README would be handy.

Either, take a look at :help package
or use a plugin manager, like https://github.com/junegunn/vim-plug

Nothing special, same as any other plugin. Plug "lukas-reineke/indent-blankline.nvim" is correct
Only thing to note, if you are on Neovim 0.5, you should use the lua branch. In case of vim-plug, that would look like this Plug 'lukas-reineke/indent-blankline.nvim', { 'branch': 'lua' }
I will add something in the readme

I couldn't get this plugin to work, and this was the solution. Thanks!

I added install instructions to the readme now


Required loggin to view create recipe page

also added some space to the bottom of some pages to look a little better. And made a few small fixes to database.

Added login required to recipe create, a few changes to pages to make them look a little nicer. Fixed a few things in the database.


Assessed Coursework, Q2

Question 2.1 seems a bit vague to me when it comes to the results that are intended to be shown. The initial question description says "For each question, pick the answer with the highest similarity score.". My understanding would be that we should get the similarity scores for every question in each set. We then we get the similarity score of each question and find the average among them. We can the use this in the report to compare between different similarity measures. Not sure if this is the intended outcome but I think it should be a bit more clear on what the question wants. This might also be applicable to Q3,Q4,Q5.

Hi, it sounds like you may have misunderstood the question. I don't think I'll plan to reword it, as part of the task should be to figure out how to use the methods effectively to solve the QA problem. You could come to the lab / office hours. (0 points)


Ctrl+N/P/J/K navigation (#146)

Navigate down and up using Ctrl+N/P or Ctrl+J/K

Actually, I don't know why we should add this shortcuts. Is it common shortcuts?

@appetizermonster it's related to #146 and yes, it's popular for most extensions to have the ctrl+n/ctrl+p to scroll up/down the list. This is present in apps like chrome, terminal, slack and other popular apps.


Move from Microsoft.Bcl.Json.Sources to System.Text.Json

fix downgrade of CoreFx packages in AspNetCore-Tooling and EntityFrameworkCore

details:

CoreFx no longer produces the Microsoft.Bcl.Json.Sources package
System.Text.Json is now .NET Standard 2.0-compatible

/fyi @dagood @mmitche

You'll need to resolve https://github.com/aspnet/Extensions/issues/1464 too.
Create a stream and pass that into the Utf8JsonWriter

:up::date: to rebase on 'master' and resolve conflict

/bump reviewers. All checks successful

:up::date: to take @davidfowl's suggestion
All checks successful (again)


feat: delete storybook

This PR deletes the old docsite/storybook/storyshots.
It fixes documentation in a few places and should allow for gatsby to build the new docsite and deploy it to github pages. It also fixes the npm commands.
Part of this was removing snapshots, but coverage was only lost on Input and the soon-to-be-deprecated InputSelect. I've added tests for Input to make up the coverage.

Coverage increased (+0.4%) to 87.954% when pulling bb0cb72c47d0183b8413aed4e0bc45d47e43cd08 on arch-1029/delete-storybook into a22487c790c0cdaedd0d4676a27c20cb131954c6 on master.


Execution of 2-select commands fails. (MySQL)

I come from the MSSQL Studio from microsoft and still have a mysql database.
I wanted to execute:
select * from tableA;
select * from tableB;

and I assumed that the 2 tables would be displayed one below the other.
Since I am used to this in MSSQL Studio, and it doesn't work in dbeaver, I was extremely annoyed.

Hello @KevinKrueger,
Have you tried executing these queries as a script using Alt+X?

Hey @ShadelessFox,
this works but if I want to look at 2 data sets from different tables (practice from software development) then these are displayed in different tabs but not one below the other in one and the same section. This makes viewing, comparing/troubleshooting in the database model very tedious

You can enable vertical tab layout by clicking on the highlighted button on the toolbar on the left:

If it doesn't show up for you, you might need to turn it on in the preferences:

Oh, thank you @ShadelessFox :)
This is what I looking for XD

Glad I was able to help. I assume the ticked can be closed now.


Failing to find package.json on deploy

I keep getting the same error after trying to upload the application zip file to the EB console.
After zipping with zip -r eb-signup-archive.zip eb-node-express-signup-master
And uploading that zip to my elastic beanstalk environment, I always get this error during the build:
Failed to find package.json. Node.js may have issues starting. Verify package.json is valid or place code in a file named server.js or app.js.

Fixed this by runing zip ../eb-signup-archive.zip -r * .[^.]* from inside the project directory


Playback Speed

The playback speed doesn't seem to work

It only support in newer Android 9+.
On firestick and lower version, the playback speed will crash the app

New nightly 4.1.0+ will allow some older Android version to use playback speed. Below it just not possible currently.


Support for

From @ApiSecRay on March 27, 2015 12:1

Extraction should turn a JAX-B or Spring Data bean into a <data-model>.
Generation should turn a <data-model> into a Spring Data bean

Copied from original issue: restful-api-description-language/radl-java#1

I assume that our use cases for data models are almost always JSON?
Spring Data seems to have support for JSON Schema (http://spring.io/blog/2015/03/26/what-s-new-in-spring-data-fowler).  Could we get rid of data models by adding support for an external data schema specified using JSON Schema?

Our media types (not data models) will most often be JSON-based, but we also want to support XML-based and other formats.
We also want to support non-Java technologies and non-Spring Java technologies, like JAX-RS, so whatever we decide should work outside a Spring-based environment as well.

Some terms turn to be a bit more confusing today. Data models, resource models, representations, etc. What are these different with each other? I assume that data model in RADL is not revelant with any particular message formats. Is this right?

A good first step would be to support data-model in the doc generation.  I guess the other tooling stages could be helpful in some cases, but they seem less critical.
The main attraction I see for data-model is that it gives us a way to document the data returned by self-describing media types, where the media type is just a generic protocol and the eventual object will include a type link.  And it does it in a way that could be directly converted into HTML documentation, instead of just including a link to some external resource (which is pretty unhelpful for the API consumer).


Android wrong display when using custom scrollInterpolator, slideInterpolatedStyle (ios is fine)

Is this a bug report or a feature request?
Bug report
Have you read the guidelines regarding bug report?
Yes!
Have you read the documentation in its entirety?
yes, and tip/tricks, and know issues (while it seems that it could be related to its)
Have you made sure that your issue hasn't already been reported/solved?
Checked issues list, didnt' find exactly this one.
may be something similar: https://github.com/archriss/react-native-snap-carousel/issues/262
but actually I use code from there to customize animation
Is the bug specific to iOS or Android? Or can it be reproduced on both platforms?
only on android
Is the bug reproductible in a production environment (not a debug one)?
yes
Have you been able to reproduce the bug in the provided example?
Reproduce in expo https://snack.expo.io/@ejohnf/android-wrong-display-problem
Environment
Environment:
"react": "16.2.0",
"react-native": "0.53.3",
"react-native-snap-carousel": "https://github.com/archriss/react-native-snap-carousel#1eaf0c0",
Target Platform:
Android API_25
Steps to Reproduce

Make Item object - as a square 309x309
carousel setting:

<Carousel
          ref={(c) => { this.carousel = c; }}
          containerCustomStyle={styles.carousel}
          data={this.props.activities}
          firstItem={this.props.position}
          initialNumToRender={this.props.position + 1}
          renderItem={({ item, index }) => <Card {...item} index={index} />}
          onSnapToItem={changeCurrentDayPosition}
          vertical
          scrollInterpolator={stackScrollInterpolator}
          slideInterpolatedStyle={stackAnimatedStyles}
          itemHeight={309}
          sliderHeight={509}
          itemWidth={309}
          layout="stack"
        />

Implement custom interpolation:

// 2 methods to fix swipe problem on IOS, for more info see: https://github.com/archriss/react-native-snap-carousel/issues/262
// also to make animation
export const stackScrollInterpolator = (index, carouselProps) => {
  const range = [0, -1, -2, -3, -4, -5, -6, -7];
  const inputRange = getInputRangeFromIndexes(range, index, carouselProps);
  const outputRange = range;
  return { inputRange, outputRange };
};

// method to make a nice stack animation
export const stackAnimatedStyles = (index, animatedValue, carouselProps) => {
  const sizeRef = carouselProps.vertical ? carouselProps.itemHeight : carouselProps.itemWidth;
  const translateProp = carouselProps.vertical ? 'translateY' : 'translateX';

  const cardOffset = 12.0;
  const scaleFactor = 1 - (cardOffset / sizeRef);

  const getTranslateFromScale = (ind, scale) => {
    const centerFactor = (1 / scale) * ind;
    const centeredPosition = -Math.round(sizeRef * centerFactor);
    const edgeAlignment = Math.round((sizeRef - (sizeRef * scale)) / 2);
    const offset = Math.round((cardOffset * Math.abs(ind)) / scale);

    return centeredPosition - edgeAlignment - offset;
  };

  return {
    opacity: animatedValue.interpolate({
      inputRange: [-7, -6, -5, -4, -3, -2, -1, 0, 1],
      outputRange: [0, 1, 1, 1, 1, 1, 1, 1, 0],
      extrapolate: 'clamp'
    }),
    transform: [{
      scale: animatedValue.interpolate({
        inputRange: [-7, -6, -5, -4, -3, -2, -1, 0],
        outputRange: [
          /* eslint no-restricted-properties:0 */
          Math.pow(scaleFactor, 6),
          Math.pow(scaleFactor, 6),
          Math.pow(scaleFactor, 5),
          Math.pow(scaleFactor, 4),
          Math.pow(scaleFactor, 3),
          Math.pow(scaleFactor, 2),
          scaleFactor,
          1],
        extrapolate: 'clamp'
      })
    }, {
      [translateProp]: animatedValue.interpolate({
        inputRange: [-7, -6, -5, -4, -3, -2, -1, 0],
        outputRange: [
          getTranslateFromScale(-7, Math.pow(scaleFactor, 6)),
          getTranslateFromScale(-6, Math.pow(scaleFactor, 6)),
          getTranslateFromScale(-5, Math.pow(scaleFactor, 5)),
          getTranslateFromScale(-4, Math.pow(scaleFactor, 4)),
          getTranslateFromScale(-3, Math.pow(scaleFactor, 3)),
          getTranslateFromScale(-2, Math.pow(scaleFactor, 2)),
          getTranslateFromScale(-1, scaleFactor),
          getTranslateFromScale(0, 1)
        ],
        extrapolate: 'clamp'
      })
    }]
  };
};

Expected Behavior
I'm trying to achive that design:

on IOS is looks perfect:

(and all other cards looks good, and animation cool)
Actual Behavior
Last item on Android:

All other items:

Reproducible Demo
https://snack.expo.io/@ejohnf/android-wrong-display-problem

also there are problems with swiping on android - after one gesture several cards channged, then scroll back to the one, which should be actually shown

Hey @EJohnF,
Thanks for the detailed and illustrated issue! It would really help if you could manage to get the Snack example working on Android.
I might be able to try out your code later this week, but I could give it a look sooner with a working example ;-)
In the meantime, can you confirm that you've read the "Custom interpolations" section of the doc, and particularly the "caveats"?

Read it now once again - but this Caveats section not really help - bcs I don't use zIndex style
inverted and useScrollView also tried - helps a bit with second (overscroll) problem

@bd-arc fixed snack: https://snack.expo.io/@ejohnf/android-wrong-display-problem
(also update link in issue)

Hey @EJohnF,
I've taken a look a the example. The fact that only the first item is affected and that it happens only on Android reminds me of an issue I had with a previous version of React Native.
If you take a look at these lines, you'll see that the first slide is centered thanks to some custom padding. A few months ago, this padding was ignored on Android and was throwing off slide's centering. I hope there wasn't a recent regression in React Native...
Could you try to override the value locally and see if it allows you to properly center the last item ?

Hum... Just created a quick example from scratch: apparently, there is a centering issue with vertical carousels on Android.
I need to look into it.

@bd-arc when I've changed these rows to
vertical ? {
                paddingTop: this._getContainerInnerMargin(),
                paddingBottom: 300, //this._getContainerInnerMargin(true)
            } : {

And then last item looks better:

Thanks!
Now problems that all cards show only 2 cards in the stack (instead of 6 in IOS)

I think I've found how to solve displaying problem:

change paddingBottom as above
change props removeClippedSubviews to false

and it looks like https://yadi.sk/i/cB5-fZsO3TnyEw

@EJohnF Good finding :-)
But a workaround was already mentioned in the doc. I didn't think about telling you because I was assuming that you were already aware of the need to set useScrollView to true in order to avoid rendering bugs.
I would recommend this solution over removeClippedSubviews={false}, since it has the same effect but might still provide a bit of optimization. :warning: Bear in mind that either solutions are not suited for large data sets since all items will be rendered upfront.
I still need to look into that bottom padding on Android though...

I've tried to use useScrollView: true
And it doesn't help with required stack view (checked once again right now)
And removeClippedSubviews={false} may be will not be a big problem, since in 0.54 added support to loading items in both directions...
Anyways thanks for your time and warning!!
But now get the problem with some overscrolling on Android (while overScrollMode: 'never',)
Within one gesture 1,5-2 items can be scrolled, which leads to some flashing or item missing

Regarding your Android issue, have you tried on a device with a production build? I can't emphasize what's being said in this note enough :-)
To provide more context, you need to know that despite being one of the most wanted feature, the React Native team have not implement yet a proper equivalent of the iOS snapToAlignment/snapToInterval combo on Android. Therefore, we are left with a bunch of hacks, workarounds and debug mode issues... I've done my best to tackle it, but some core things are either missing or buggy and I have no control at all over it.
Still, ideas and PR are always welcome ;-)

FYI: updated to the last version of you library - and now it works fine!! Thanks!
(used a heavily customized fork before)


i686 Clang Cross Compilation fixes: Tracker

Describe the bug
This is a tracking issue for several bugfixes on different derivations when cross-compiling for i686 or with a clang-only toolchain.
cc/ @Ericson2314

musl (#195969)
libvorbis (#195968)
cc-wrapper (#195976, #196013)
audiofile (#195971)
apparmor (#195972)
gnu-efi (#195974)
libnftnl (#195975)
LLVM (#196006, #196008, #196023)
dbus (#195977)
pulseaudio (#195979)
SDL(#195981)
elfutils (#195980)
pkgsi686Linux (#195983)

Perhaps related: #97688

Hi @peperunas, I've looked through a few of these PRs now, and I've found that most of them are missing detailed explanations for the changes in the commit message bodies.  This makes it difficult for reviewers to understand why the changes are required, and it means that if something goes wrong with one of the changes (e.g. https://github.com/NixOS/nixpkgs/pull/200587) it's more likely to get reverted rather than fixed, as it's difficult for the person who notices the changes to try to fix it if they don't know how they should be testing they haven't broken your use case.
(When adding these explanations, please make sure they're in the commit message bodies rather than just the PR comments, so that they show up in git log etc.)


demo page not working

having some port issues because i switched ISP. so the demo page is not working atm :)
The screenshot should give you a good idea nevertheless

This issue seems to be resolved now :)


Add files via upload

Your project looks almost complete! I see testing functions and you have a very detailed vignette.
I agree with Magda's suggestions and I have two small suggestions for the vignette:

I think it could be cool to move the conclusion (currently at the end of the vignette) to the top. Similar to an abstract, it would be a nice pitch that gives the reader an idea of your app at the first glance.
You could remove the knitr calls that generate the screenshots in the vignette.


Erase elastic index on depoy'n'wipe

the colplus-deploy-n-wipe script should erase all data from the ES index as it also inits a new database.

well, alternatively we could include it into the InitCmd code.
That might be a better integration in case you call the init command without the wipe script


Update index.html

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

ikeda pipelinetest


More-Windows construction category QoL problem

Window category seems to be added after FILTER category and causes it to be shown when searching constructions. I tried adding filter back to the end of constructions as in :
[   {     "type": "construction_category",     "id": "WINDOWS",     "name": "Windows"   },   {     "//": "Should be last in the list",     "type": "construction_category",     "id": "FILTER",     "name": "Filter"   } ]
which did not work thus I am leaving its fixing to the more code savy people

thank you for the reply this is actually my mod ill look into it

I think it's because it adds mod data basically to the end of the json files so this is how its added in and i think adding the filter will add two filter categories, this cant be fixed as a mod I don't think if someone can fix it I wouldn't mind seeing the code.
it's fixed in experimental. as my mod is now vanilla content.


Can the Secrets Store CSI driver be used to access the Azure Key Vault REST API?

Hi,
I have a legacy application that pulls secrets from an Azure Key Vault by making HTTP requests to its API (using the URL https://<keyvaultname>.vault.azure.net). The application is deployed in Azure and uses managed identities to do this. We're moving the application into Kubernetes, and as a first step I would like to change the current implementation as little as possible.
So my question is this: Can the Secrets Store CSI driver be used to access the Azure Key Vault REST API  via its url? Or is it only used to mount secrets into pods in different ways?

@joelnotified Thank you for reaching out.
The Secrets Store CSI Driver makes the HTTP requests to Keyvault, fetches the contents and writes to the pod mount. This means the application can just read the secret from the filesystem or if it relies on env variables, then also do so by leveraging the Sync as Kubernetes secrets and then using that as env variable.
However if the application is already making API requests to Keyvault, then the Secrets Store CSI Driver will not be required.

@joelnotified Thank you for reaching out.
The Secrets Store CSI Driver makes the HTTP requests to Keyvault, fetches the contents and writes to the pod mount. This means the application can just read the secret from the filesystem or if it relies on env variables, then also do so by leveraging the Sync as Kubernetes secrets and then using that as env variable.
However if the application is already making API requests to Keyvault, then the Secrets Store CSI Driver will not be required.

@aramase Thanks for the reply!
Ok, I think I'm starting to understand how it works. I see now that Secrets Store CSI Driver uses AAD Pod Identity. And it looks like having AAD Pod Identity setup is what's required to access the keyvault from within the cluster.
Thanks for clarifying! 👍

@aramase Thanks for the reply!
Ok, I think I'm starting to understand how it works. I see now that Secrets Store CSI Driver uses AAD Pod Identity. And it looks like having AAD Pod Identity setup is what's required to access the keyvault from within the cluster.
Thanks for clarifying! 👍


Add PAL Talos MJCF description from Menagerie.

Thanks for everything @stephane-caron!

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

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

Totals

Change from base Build<PHONE_NUMBER>5:
0.02%

Covered Lines:
933

Relevant Lines:
958

💛  - Coveralls

LGTM, thanks! :+1:


Allow debugging Selector expressions interactively in the browser

What is your Test Scenario?
Execute selector expressions and examine their results during test execution without modifying the test code.
What are you suggesting?

[x] Expressions should be executed in the context where t.debug() was called. This means it should have access to test's local variables, especially page models.

[x] A call to t.debug() should allow for executing selector expressions through a built-in CLI/IDE debugger

To add to this issue, it would be nice if other imported selectors, like ReactSelector were also available.
I don't know exactly how you would be able to achieve this (perhaps via eval'ing the string in the context of the test code).

I just want to let you know that we are working on this issue now, but initially we are going to implement debugging in IDE terminal without UI.
We will consider to support React Selectors (and others) in future either.

How this would be even more of an help:
You could run test in debug mode, and whenever some selector was not found during test execution, the runner would pause and display input where You could test selectors.
After inputing into this input value Selector('.some-improper-class') TestCafe would inform that no elements were found.
After that, if You would input Selector('.good-class') and TestCafe would be able to find this element on page, You could update this selector in Code, press Continue button in TestCafe toolbar in browser and TestCafe would execute current step with this new Selector You have provided in input, and pause again next time it won't find another Selector.
Why:
For some reason, Live run does not run sometimes when I change the code, of does not use updated Selectors, so I am using debug run with pauseOnError. And as some of my tests take like 15 min to execute, and you can have like 100 broken selectors in one test after refactor of app, then updating those takes a lot of runs and time.

Any idea when this feature will be worked on or if an acceptable workaround exists?
I'm finding it hard to believe something like this is not possible coming from Python and Java where in both languages you can run arbitrary code at a breakpoint to find out if your selector or code needs modifying.

Hi @joywave
I'm unable to provide you with any time frame for this feature.
At present, TestCafe allows you to debug selectors by outputting the call site information about the problematic selector. See more information in this help topic.

Any update on this ticket? It would be great to have this. This would make the selection of selectors so easy and tests can be created way faster.

@amal-architrave
Hello,
No, we don't have updates yet.

Hi guys,
is there any ETA for this feature?

Hi @aurelienlair, this feature is included in our 2021 Roadmap, and we are working on it. Any estimates may be misleading at the moment. As soon as we have any results, we will post them here.

Since TestCafe 1.18.0 release it's possible to use the --experimental-debug options to execute Selectors or ClientFunctions and get their results during server-side debugging.


Don't update CMS preview on a CMS redirect

The CMS preview causes unnecessary browser processing by loading a URL which
should be considered "in transit" when a CMS redirect is set through the
X-ControllerURL HTTP header. The CMS history processing will load this new
URL, and cause a new preview URL to be loaded.
Fixes https://github.com/silverstripe/silverstripe-translatable/issues/158

Fixed in 3 branch.


Create end-user docs

We need end-user documentation for the installation and usage of the software.

With https://aws.github.io/aws-controllers-k8s/ online, I declare this bootstrapping done. From now on we should create individual issues on a page/section level.


Midjourney - AI chatbot for Midjourney-style image creation

https://chat.openai.com/g/g-MD9ZplW7q-midjourney

Merged


flag: add support for int32 and uint32 options

This PR will be imported into Gerrit with the title and first
comment (this text) used to generate the subject and body of
the Gerrit change.
Please ensure you adhere to every item in this list.
More info can be found at https://github.com/golang/go/wiki/CommitMessage

The PR title is formatted as follows: net/http: frob the quux before blarfing

The package name goes before the colon
The part after the colon uses the verb tense + phrase that completes the blank in,
"This change modifies Go to ___________"
Lowercase verb after the colon
No trailing period
Keep the title as short as possible. ideally under 76 characters or shorter

No Markdown
The first PR comment (this one) is wrapped at 76 characters, unless it's
really needed (ASCII art, table, or long link)
If there is a corresponding issue, add either Fixes #1234 or Updates #1234
(the latter if this is not a complete fix) to this comment
If referring to a repo other than golang/go you can use the
owner/repo#issue_number syntax: Fixes golang/tools#1234
We do not use Signed-off-by lines in Go. Please don't add them.
Our Gerrit server & GitHub bots enforce CLA compliance instead.
Delete these instructions once you have read and applied them

It's usually a good idea to discuss feature requests in a proposal on the issue tracker before submitting pull requests.

Thanks for the patch. Since the proposal (#26545) was not accepted, I'm gonna close this Pull Request.


Fixed root path since moving to PSR-4 autoloading.

In the current master and also in tags ~5.0.0 I get:
$ ./vendor/sensio/distribution-bundle/Resources/bin/build_bootstrap.php app/
Looks like you don't have a standard layout.

Because build_bootstrap.php is located in /vendor/sensio/distribution-bundle/Resources/bin/build_bootstrap.php and not in /vendor/sensio/distribution-bundle/Sensio/Bundle/DistributionBundle/Resources/bin/build_bootstrap.php as in <=4.0

:+1:

Any news?)

+1

Thank you @korotovsky.


Where to find trigger_msgs package?

System Description
Camera Name and Model: Blackfly S Gige
Operating System: Ubuntu 18.04 arm64
Spinnaker Version: <IP_ADDRESS>
ROS Version: melodic
Computer details
Jetson Xavier AGX
Do the cameras work with SpinView?
Yes
Describe the bug
Successfully running external triggering, but I want to set the the timestamps of each image to the timestamp of the external trigger-signal, seems to me that by understanding how to use the trigger_msgs package this issue is fixed. But I wonder where the trigger_msgs package is defined and how to use it?

I think https://github.com/jpsnir/trigger_msgs should be the right package.
On Tue, Feb 22, 2022, 4:36 AM maghauke @.***> wrote:

System Description
Camera Name and Model: Blackfly S Gige
Operating System: Ubuntu 18.04 arm64
Spinnaker Version: <IP_ADDRESS>
ROS Version: melodic
Computer details
Jetson Xavier AGX
Do the cameras work with SpinView?
Yes
Describe the bug
Successfully running external triggering, but I want to set the the
timestamps of each image to the timestamp of the external trigger-signal,
seems to me that by understanding how to use the trigger_msgs package this
issue is fixed. But I wonder where the trigger_msgs package is defined and
how to use it?
—
Reply to this email directly, view it on GitHub
https://github.com/neufieldrobotics/spinnaker_sdk_camera_driver/issues/146,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF63GIGR3PKJCXNOI6EYZHDU4N7MTANCNFSM5PBILQSA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

but that package doesn't include sync_trigger.h, so I meet error again

It's a message definition. The .h file is created when the messages are compiled.


Change DockerSurfer to dead

The website for the project is not longer up (http://dockersurfer.com/) and it didn't receive commits for almost a year. I would suggest moving it to dead or even remove it entirely.

I just browsed the awesome list and didn't try it. Don't have a custom registry either.

OK Thank you @SuperSandro2000


JNI

java: 写入de.kherud.llama.LlamaModel时出错: com.sun.tools.javac.jvm.JNIWriter$TypeSignature$SignatureException: (@org.jetbrains.annotations.Nullable :: java.util.function.BiConsumer
环境 macOS  M3，jdk1.8

Hey @ys2940 do you have to use Java 1.8 or can you upgrade to a newer version?

Ok, the jetbrains annotations aren't extensively used in the current version anyway, so I think I can remove them for backwards compatibility. I'll do this later today.


Remove trailing slash from /databases endpoint

Pinecone replies 404 if the databases endpoint contains a trailing slash.
(I've modified the code manually as I haven't been able to run the generator)
cc @walsha2

I'm using the free plan (gcp-starter), maybe it behaves differently than the paid one?

I'm using the free plan (gcp-starter), maybe it behaves differently than the paid one?

Really weird. I cannot recreate this behavior. It works with and without the trailing slash on both a free and paid instance:
# PAID

curl https://controller.us-central1-gcp.pinecone.io/databases/ \
	--header 'API-KEY: XYZ' \
	--header 'ACCEPT: application/json; charset=utf-8'

curl https://controller.us-central1-gcp.pinecone.io/databases \
	--header 'API-KEY: XYZ' \
	--header 'ACCEPT: application/json; charset=utf-8'

# FREE

curl https://controller.us-west1-gcp-free.pinecone.io/databases \
	--header 'API-KEY: XYZ' \
	--header 'ACCEPT: application/json; charset=utf-8'

curl https://controller.us-west1-gcp-free.pinecone.io/databases/ \
	--header 'API-KEY: XYZ' \
	--header 'ACCEPT: application/json; charset=utf-8'

In any case, let me make sure your manual changes match the generated code. If so I will get this merged in. The trailing slash in main.dart should probably be removed anyway... just as you have done in this PR.
https://github.com/tazatechnology/pinecone/blob/76c300f4ec3dcc7cdfcb0eafad61a1803a524991/oas/main.dart#L45

@davidmigloz v0.5.1 has now been released
https://pub.dev/packages/pinecone


Dropdown on fixed/stiky elements are buged

OS : windows
Node.js : v12.14.1
Vuesax : v3.0.1
Browser : Firefox v74.0
package manager : npm 6.13.4
I have a dropdown used to show a disconnect button when you click on your profile picture in a top fixed navbar. The problem is that when I open the dropdown and scroll the page, the navbar doesn't move (as it's fixed) but the dropdown move with the rest of the page.
I think this issue comes by the position of the dropdown in the dom (at the top level of ) while the element it's 'bound' to is way down the hierarchy. If the dropdown container was at the same DOM level as the element it's bound to, there would be no problem.
I tested moving the container near its bound element when the page is running (simply open the dom explorer and dragging the element in place) and it works, but I don't see how to do the same in the template (without moving the element in mounted() )

I am struggling with the same problem here, have you find any solution yet ? also if resize the page it holds it location, it;s super buggy.

sadly no, I haven't found any effective fix


Connects to #238. Connects to #239. Connects to #236. Mitochondria-specific graphical analysis.

Key Changes:

Added mitochondria-specific graphical analysis to the landscape graphical clustering page.
Added Google Analytics stats and metrics tracking for events pertinent to users downloading bundle datasets.
Fixed bug in which the click event does not respond after initial QC data fetch.
Updated members' titles on the Team page.

@cteng585 The navigational items in the sidebar of any given graphical analysis report are dynamically populated, based on the heading elements in the HTML doc, after the DOM nodes have completed loaded in the HTML doc.
The preference is to convert the HTML doc to native DOM nodes in the frontend app rather than using iframe. Would you be interested in taking on this task?


Facebook One-time Notification

Hello,
from the recent documentation on Facebook we found out that it's allowed to send a one time notification after the 24hrs window if the user has given his permission.
https://developers.facebook.com/docs/messenger-platform/send-messages/one-time-notification
For sending such proactive message we should set in the API call the token gathered from the user, in the following way:
"recipient": {
  "one_time_notif_token":"<ONE_TIME_TOKEN>"
}

We tried to add this value in channelData like we did for example for notification_type, but it seems that the recipient value is being ignored when sending the request to Facebook, and it returns a 400 Bad Request error ("This message is sent outside of allowed window.").
I cannot be sure that the value is being ignored though, because I didn't find a way to inspect the real JSON body sent to the Facebook API.
This is the code we tried (C#):
var reply = context.Activity.CreateReply("Notification");

reply.ChannelData = JObject.FromObject(
    new
    {
        recipient = new
        {
            one_time_notif_token = token,
        },
        notification_type = "REGULAR",
    });

await context.SendActivityAsync(reply);

For now we're sending the notification by calling Facebook API natively, but is there a way to achieve this with Bot Builder or is there any chance that will be added as a feature?
Thank you.

@sombe - Facebook is a third-party channel, and it's unlikely that the Bot Builder SDK will be updated to have built-in support for more Facebook Messenger features. However, the Bot Builder SDK does have a Facebook adapter. Have you tried that?

@sombe - Are you still working on this?

Hello @v-kydela,
yeah sorry for the delay. We've seen the Facebook adapter but One-time Notification would be the only feature that would force us to use the dedicated adapter. Given what has been done for the notification_type we thought there was a possibility for this too, but since you pointed out that this will unlikely happen, we will continue calling the API natively.
Thank you for the clarification.


Add OriginZip to USPS

@Shopify/shipping
Pulls https://github.com/RichardBlair/active_shipping/pull/1 and https://github.com/RichardBlair/active_shipping/pull/2 into master.
Bumps version to 1.2.1.
The change is described here in the USPS Web Tools API May release (warning: .RTF for some reason):
https://www.usps.com/business/web-tools-apis/2015-may-webtools-release-notes.rtf

+1 for this patch.
Without it, Spree sites are returning $0 Priority Mail International shipping from the US to Canada.
How soon can we see this merged?

This patch doesn't even fix it. I'll create a new PR with the real patch that we developed yesterday.


[REEF-310] Improve memory efficiency of the Driver bridge.

This change introduces the ActiveContextBridgeFactory to instantiate and cache ActiveContextBridge instances:

Removed unused instances of ActiveContextBridge.
Replaced the remaining constructor calls with calls to ActiveContextBridgeFactory.getActiveContextBridge.

ActiveContextBridge instances are removed from the cache in ActiveContextBridgeFactory by the ClosedContextBridge. This should limit the
size of the cache.
JIRA: REEF-310

Closing this, as @yingdachen found a bug in it. Thanks!

I believe I addressed the issues mentioned. Also, I merged in current master

@yingdachen @jwang98052 do you think this is safe to merge now?

@yingdachen @jwang98052 I removed the cache from the PR. Please have another look.

looks good to me.

@yingdachen Can you merge it, then?

Let me test and merge it.


[Issue]: Observability Blog Post Image Sizing Issues

Describe the issue
Due to the way Docusaurus renders images, I undersized several of the photos in the blog post.
Before (40% width)

Proposed (100% width)

By updating the MDX to change back to 100% width, this will make the images much easier to read.
Steps to reproduce
See: https://microsoft.github.io/autogen/blog/2024/07/25/AgentOps
Screenshots and logs
No response
Additional Information
No response

@qingyun-wu, @areibman has updated the blog post in regards to the image sizes and it's now rending images full-width. If you could merge that would be great! #3234
I'll close this issue.


Document gif generation

We should have instructions on generating gif with asciicast2gif in:

[ ] Share / Embed popup
[x] when someone requests https://asciinema.org/a/<recording-id>.gif URL.

https://github.com/asciinema/asciinema-server/issues/171#issuecomment-402264869 also references termtosvg. Should we re-open issue #171, track that suggestion in this issue’s list, or file a new issue altogother? I’d hate to see that fall through the cracks.


TypeError when iterating through headshots output on train-webhook

If the output from train-webhook endpoint doesn't have enough items to fill headshots_part_2, headshots_part_3 or headshots_part_4, a TypeError will be thrown, because it's trying to iterate on undefined to create allHeadshots const.
This behavior makes the function execution to stop, and images are not saved on the database.
Output

Error message on Vercel console

I'll make a PR to fix this issue.

@GGalupo Hey, so I don't think this is an issue since if you use the headshots template 1:1 and the template workflow this will work.
If someone edits their workflow to not have those outputs then it would be up to them to update their code to show that too


Add filters for which interfaces should be projected two-way

Not a big deal, can revisit when needed.


chore: import repository https://github.com/keskad/jx3-test-golang.git

this commit will trigger a pipeline to generate the CI/CD configuration which will create a second commit on this Pull Request before it auto merges

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@keskad: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

verify
041f15bed6fa73d87d8c2f76fc628d810930793b
link
/test verify

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

/retest

@keskad: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

verify
041f15bed6fa73d87d8c2f76fc628d810930793b
link
/test verify

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


Scaffold CLI tool for creating new projects

Fuels CLI integration requires fuels.config.ts file generation — #1291

Create a scaffolding tool for generating ready-to-go Fullstack Fuel dApps.
It should support templates and provide a single-command frictionless entry point for newcomers.
npx create fuels@latest my-fuel-dapp
npx create fuels@latest my-fuel-dapp -t <template-name>

Companion frameworks example:
npx create fuels@latest my-fuel-dapp -t next
npx create fuels@latest my-fuel-dapp -t nuxt
npx create fuels@latest my-fuel-dapp -t sveltekit
npx create fuels@latest my-fuel-dapp -t astro
npx create fuels@latest my-fuel-dapp -t qwik

Dead-simple instant quickstart:
npx create fuels@latest my-fuel-quickstart

End goal:

Single-command, no-brainer, frictionless entry point for Fullstack dApp engineers
Get users prototyping Fuel dApps in seconds
Fast development cycle

Can I take up this one? @arboleya :)

Sure!
I'd say let's try to have a first minimal draft template structure considering the quickstart/counter that we can brainstorm over, review, and expand from there. Also, most "companion" frameworks I mentioned in the issue description have excellent interactive scaffolding tools from which we can look and draw inspiration — if we need interactivity, meaning that a first version with only CLI flags like -t, --template may work just fine.
The output of this task should also align with #1291/fuels.config.ts, so you'll need to use that branch as the base branch for moving in parallel. Remember that the former PR is fresh and subject to changes, so it's wise to be flexible and keep some open ends to avoid over-refactoring as we approach the end.

@arboleya @FuelLabs/sdk-ts I have created the first draft for the template here if you want to have a look: https://github.com/Dhaiwat10/fuel-cli-starter-template

@Dhaiwat10 I wonder if keeping the whole contracts directory inside src is the best option—more here.

@luizstacio What do you think about a hybrid approach, like a mix of built-in and community templates? My concern is that having all built-in templates scattered around in different repos could add unwanted maintenance complexity for us.

@arboleya I see. I agree about the nomenclature decision you took there. Do you want me to move the directory one level out to the root of the project?

Agreed @arboleya, I think we should only have two or three 'official' templates at most - covering the most popular frontend frameworks. This would be sufficient for 99% of our users.

Can we tie it in with the frameworks in the apps directory, that way we ensure they are kept up to date.

@danielbate good idea. Let me see if I can pull that together.

btw one thing that I found when working on this issue was that npx create fuels won't work. That syntax only works with pnpm. Let's take the example of create-next-app.
As you can see in the package.json, the package's name is create-next-app. This means that the syntax for it would work like this:
npm - npx create-next-app
pnpm - pnpm create next-app
create has to be a part of the name of the package. npx create next-app doesn't work.
For our tool, I think we should just add another command called create so it works like this:
npx fuels create and pnpm fuels create
Thoughts?

Just leaving a ref. of what we spoke here.

I believe all these may work:

npx create-next-app
npm create next-app
pnpm create next-app

I think it is the other way around, but by allowing the community to build the templates, we can reduce our management coverage. We just need to ensure on the install to use the lock inside the template etc...
Also, we incentivise people to build templates for other languages otherwise is going to be in our hands only to create these templates.

I propose we create a repo similar to this one by Next.js where we can store our templates. To start with, we can add two or three 'official' templates. The community can then keep adding templates to this repo via PRs.

That makes sense.
Should we also move our demos to this repo? It could remove a lot of the bloat.

demo-nextjs
demo-nodejs-esm
demo-react-cra
demo-react-vite

My only concern is that these demos are currently used to validate that the SDK compiles correctly using each tool. If we move them outside, it'd be great to keep these validations. Perhaps some CI automation could do it.
Have you thought about it?

@arboleya
Definitely doable. I think the demos would also become redundant. The templates and demos both serve the same purpose. The only difference is that the templates will also include integrations with the fuels CLI and maybe the wallet SDK.
Maybe it would be a good idea to tackle this transition separately after this PR?

Yes, it might be better to do it in separate PRs.

@digorithm Is there any procedure we need to follow for creating new repos?


App logged out and asked for log in credentials after enabling the camera access in the settings

Describe the bug
After Clicking Allow access to camera and activating the camera access in the settings, going back to the app results to logging again.
To Reproduce
Steps to reproduce the behavior:
Prerequisite (sharing device): Bluetooth, location, location access: enabled. Camera access: disabled

Disable camera access of the app in the settings
Open app and go to the second icon from the left (SCAN)
Click “Allow access to camera” – taken to settings
Allow access to camera
Go back to the app
SEE ERROR

Expected behavior
Go back to app - should land on "SCAN" page with camera displayed
Device:
iPhone11 - iOS 15.5
iPhone SE - iOS 15.4
MOSIP server: QA4
Screenshots
https://user-images.githubusercontent.com/102940764/191890799-e2b28d73-64f3-4e47-8fa6-3eb545c268d2.MP4

@jannahadlaon this is standard at least in IOS whenever you change an app's settings
tried it on Doctor Anywhere app
https://streamable.com/gi8sb2

Thanks for the update @danicaerediano
We can close this ticket after noting it in this document: https://docs.google.com/document/d/1KFoDK0s6tmy3erafPzHaSBGn-L7Rb--UW9Y_3KGUMq8/edit#heading=h.una0vopyp7lh
@pmigueld @kyanthony

@jannahadlaon can you verify this behavior in Android as well? I tested with my Slack app (changed permission and it also restarted). If so we don't need to add this to the doc since it seems to be standard behavior for mobile apps.

@pmigueld i tried it on the Resident app (see attached video)
For slack, it did not restart on my end.
Steps:

Go to Settings >> App >> Slack
Disable camera access for Slack
Open slack
Go back to App settings and enable camera access for Slack
Switch back to Slack
Verified that Slack did not restart

https://user-images.githubusercontent.com/102940764/193183526-aa2bad0c-2873-4a65-b1ad-a1c3ad721684.mp4

verified as fixed in the build with commit id in the below screenshot.
https://drive.google.com/file/d/15uWjasH2tRj0qCau8Ljj8YFEoSXi6mfd/view?usp=drivesdk


terraform error for eks-d

What happened:  terraform plan fails to prepare EKS-D plan and return errors regarding the os variable
Error: Invalid index
│
│   on main.tf line 52, in data "aws_ami" "ami":
│   52:     values = var.ami_filters[var.os].image_name
│     ├────────────────
│     │ var.ami_filters is map of object with 5 elements
│     │ var.os is "amazon_linux2"
│
│ The given key does not identify an element in this collection value.
What is the expected behavior:
plan to be successfully build
How to reproduce the issue:
follow tutorial https://docs.kubermatic.com/kubeone/v1.3/tutorials/creating_clusters_eks_d/#prerequisites
run terraform plan
Anything else we need to know?
Information about the environment:
KubeOne version (kubeone version): 1.3.0-rc.0
Operating system:  ubuntu 20.04
Provider you're deploying cluster on: AWS
Operating system you're deploying on: n/a

replacing  amazon_linux2  with amzn2 in terraform.tfvars made it work

@nicohouillon it's not about vpc not found, it's about not having an internet gateway attache to your VPC.
data "aws_internet_gateway" "default" {
  filter {
    name   = "attachment.vpc-id"
    values = [data.aws_vpc.selected.id]
  }
}

our example terraform configuration of course doesn't suppose such thing, you will need to take our example and adjust it to your needs.


Better alternative to #137

Very useful to see! I noticed this is removing the examples/cross-chain-extension which I've found to be an extremely helpful reference example. Is there some reason for this?

I asked the same question in the original PR #137 . I think this can be a separate example by keeping the removed one.


chore: add versioning info

This adds some version info the compass source and also performs a bit of house cleaning. Once this is through, we can cut a release on this repo and attach ABI & byte code to it.
https://github.com/VolumeFi/paloma/issues/1686

I will disable the workflows I think, since they'll fail all the time now.

@webelf101 Will you please run a build on the v1.1.0 tag and then attach bytecode and ABI to the release?


Update bower package

Can you please update the bower package to include the latest commits, among which is the fix for multiple instances?
Thanks.

Done


Fixes enum store when SymbolTable is replaced while setting up config.

This PR fixes the issue where inbuilt enums are no longer part of the config if the symbol table is replaced after initialization.
After initializing the config if SymbolTable was replaced, we were loosing the enums attached to the previous default symbol table. This PR will again attach the enums if SymbolTable is replaced.

✅ No public API change.


Why is the "Using Persistent Disks with WordPress and MySQL" section using v1beta1?

I don't see how this version relates to the rest of the versions - which is my main concern here.

@chrissound Hello, are you referring to apiVersion: extensions/v1beta1 of mysql.yaml or wordpress.yaml files?
If so, this is about the kind: Deployment field. The Deployment resource type in Kubernetes is currently in beta status. Therefore it has to be referred to as its API group (i.e. extensions) and its version in there (i.e. v1beta1).

Yes, I'm referring to that section.
Just seems a bit odd to have a beta version for an API on the official docs. None the less, thank you for the explanation!

I recommend following up the material with documentation on https://kubernetes.io/docs/ you'll see that the apiVersion: extensions/v1beta1 is used there too as that’s what's available.


Silent Login/authentication

Describe the solution you'd like
Would like a way to silently login if the user has logged in previous session.  If the user has not, then it should fail and should not bring up a login for the user.  When new users come in, don't want them to see a login first off, but rather show them why the app is so great that they'd want to log in.  At the same time, would like the existing users to not have to see login.

saw this is repeat of  #1151

Hey @curelom, thanks for reaching out!
For your scenario, you can do that today, but it's not exactly elegant.
To do so,
call the signIn() method (for example, in the Auth Andriod SDK)
In the else statement of the signIn() method, you can edit the code to modify the user experience when the user has signed in to show an alternate screen, etc. The signIn UI wouldn't appear again: if the app calls signIn again, the SDK shows the sign-in UI again only if the saved sign-in information expired or was revoked by the authentication server.
The feature you requested is on our backlog, but ETA so far, unfortunately.


[Feature Request] Allow functions in directive parameters

I have a use case where I would like to be able to pass more than just a string as a directive argument. For example, if I have a directive designed to enforce uniqueness on arrays (in Zod), I would want to use the refine() method like so:
z.array(z.string()).refine(items => new Set(items).size === items.length);

Translating this to typescript-validation-schema:
directive @array(
  unique: Boolean = false
) on INPUT_FIELD_DEFINITION | FIELD_DEFINITION | ARGUMENT_DEFINITION

input TestInput {
	userIds: [Int] @array(unique: true)
}

With my CodegenConfig defined in a TypeScript file: (https://the-guild.dev/graphql/codegen/docs/config-reference/codegen-config)
import type { CodegenConfig } from '@graphql-codegen/cli';

const config: CodegenConfig = {
  overwrite: true,
  watch: false,
  // ... other config ...
  generates: {
    'graphql/typings.ts': {
      plugins: [
        'typescript',
        'typescript-validation-schema',
      ],
      config: {
        strictScalars: true,
        schema: 'zod',
        directives: {
          array: {
            unique: ['refine', (items) => new Set(items).size === items.length],	// function passed as argument
          },
        },
      },
    },
  },
};

export default config;

However, that directive configuration yields the following error:

My request is that the typescript-validation-schema package can support receiving functions as arguments for custom directive definitions.

@elijaholmos Thanks for your suggestion!
I agree to accept this feature request. but this feature is difficult to treat in YAML configuration. Do you have any ideas?

graphql-codegen encourages the use of a typescript-based configuration by default, which naturally offers substantially more features than its yaml counterpart. We could perhaps simply not support this feature if a yaml configuration is present, as that would indeed be cumbersome to work with.

@elijaholmos Could you give me PR for this implementation? Thanks!


ResourceAttributes look wrong for authorization

While evaluating kubelet-rubber-stamp for use on my team's product I noticed the following:

https://github.com/kontena/kubelet-rubber-stamp/blob/602e5db20e5d251fbc8e4d4dfcff0aeb34cc9b46/pkg/controller/certificatesigningrequest/certificatesigningrequest_controller.go#L33

This looks wrong to me since it seems to be rubber stamping if the service account has permission to create certificatesigningrequests rather than certificatesigningrequests/approval -- we implicitly know that the service account has permission to create certificatesigningrequests based on the fact that the CSR exists in the first place, what we should really care about when auto-approving is whether the service account has permission to approve CSRs.
I guess the problem may be that the system:node cluster role doesn't have any certificatesigningrequests/approval permissions (at least not be default in my cluster) so maybe there's nothing to do here, but I thought I'd see what y'all think.

As the repo name suggests, it is sort of a "rubber stamper". :D The logic, and bit's of code, are borrowed from kube core for automated approval for kubelet client certs, see https://github.com/kubernetes/kubernetes/blob/master/pkg/controller/certificates/approver/sarapprove.go
By design the CSRApprovingController will not handle kubelet serving certs, so we adapted the same logic to serving certs for kubelet.
You are correct in the sense that it is merely a rubber stamp, we really do not have any better ways to validate the CSRs. Currently the verification only kinda checks that we cannot get a serving certificate for a node not existing in the cluster as it uses the node identity in the subject access review.
IMO using certificatesigningrequests/approval would be slightly "wrong" as it's not the node itself actually approving the CSR. And with quick thinking it would not improve the situation at all. You'd still end up having rubber stamping in place as all the nodes will (need to) have the permissions to certificatesigningrequests/approval. I think it might be possible to require this "elevated" permission and then bind it only on specific nodes by administrative process (manual or automated). But that makes cases such as autoscaling PITA. I guess this boils down to thinking like: "If a node is able to authenticate and authorize on API, we need to trust it anyway. Why not trust it enough to give a serving cert for it as kube core has already approved a client cert too for it."
And yes, part of the problem is the fact that by default system:node role does not have any "elevated" permissions on CSRs. So we wanted kubelet-rubber-stamp to have the least changes needed to "standard" node permissions for it to be applicable on any cluster.

Hey @jnummelin thanks for the quick response! You make a bunch of great points that I hadn't really thought about, thanks too for that.
I think I filed this issue while kind of blindly stumbling my way through the implications of kubelet-rubber-stamp while writing some e2e test cases to develop a better practical understanding of the security implications of deploying it in the product my team supports. Here's a rough outline of how my test cases work:

For various service accounts in a cluster:

obtain a service account token
construct a client set using bearer token auth with the service account token
craft a CSR that looks exactly like the kubelet's CSR

Regardless of which service account I use for this purpose, even the default service account in the default namespace, I am able to get the CSR approved. This violated my intuition, so I reached out and filed this ticket mistakenly thinking it was a problem of incorrect RBAC permissions since it seems tautological to validate that the account which created the CSR has the permissions to create CSRs.
However, taking a closer look at the built-in client cert approver that you linked I see one major difference which is that the CSR spec username is in some cases checked against the CommonName of the CSR itself.
It seems to me like using information that we can be reasonably certain about at this point in the lifecycle of the cluster (the kubelet is presumably authenticated with the apiserver using its client cert) such as the name of the account that created the CSR is probably a good idea to prevent auto-approving arbitrary Kubelet serving certificates to any service account that has the permission to create a CSR. In fact, this is exactly how Kubernetes itself did it in the past.
What would you think if I submitted a PR to add this restriction to kubelet-rubber-stamp?

Another difference I noticed with the client cert auto approver is that they do actually rely on a different resource permission than what I see in kubelet-rubber-stamp. Specifically, they match against the nodeclient or selfnodeclient subresources of the certificatesigningrequests resource.
I see the PR that I mentioned in my previous comment removing auto-approving server cert rotation also removed a selfnodeserver subresource from certificatesigningrequests so that wouldn't be an option for kubelet-rubber-stamp, but what do you think about piggybacking off of selfnodeclient?

I think just validating better the source being really kubelet might be enough. With a quick testing API seems to always put the user info (coming from auth layers) properly into the CSR details. We already verify that it's a serving cert we're approving, so limiting those to be coming from kubelet should be enough IMO.

By the way, I found a bug in some of my test code around building a clientset for service accounts which gave that test code the appearance of allowing arbitrary service accounts to create CSRs, but it was actually still authenticated using the admin kubeconfig -- I had been confused about how the clientset overrides work.
But I think this issue and the related PR are still valid in terms of preventing arbitrary service accounts with permission to create CSRs from getting a kubelet-like CSR auto-approved.

fixed in #11


Adapter name conflict with tuner prefix leads to unclear warning during model loading

System Info

peft=0.13.3.dev0
transformers=4.46.3
Python=3.12.6

Who can help?
@BenjaminBossan
@stevhliu
Information

[ ] The official example scripts
[X] My own modified scripts

Tasks

[ ] An officially supported task in the examples folder
[X] My own task or dataset (give details below)

Reproduction
import peft
import torch
from pathlib import Path
from transformers import AutoModelForCausalLM, AutoTokenizer
from peft import LoraConfig, TaskType
from tempfile import TemporaryDirectory

def get_adapter_state_dict(model, adapter_name):
    adapter_state_dict = model.state_dict()
    adapter_weights = {key: value for key, value in adapter_state_dict.items() if adapter_name in key}
    return adapter_weights

def test_adapter_name():
    MODEL_ID = "openai-community/gpt2"
    ADAPTER_NAME = "lora"

    # Load the base model
    base_model = AutoModelForCausalLM.from_pretrained(MODEL_ID)

    # Define LoraConfig without base_model_name_or_path
    peft_config = LoraConfig(
        task_type=TaskType.CAUSAL_LM,
        inference_mode=False,
        r=8
    )

    # Get the PEFT model with the adapter name
    peft_model = peft.get_peft_model(base_model, peft_config, adapter_name=ADAPTER_NAME)

    # Saving and loading the model
    with TemporaryDirectory() as temp_dir:
        temp_dir = Path(temp_dir)

        adapter_weights = get_adapter_state_dict(peft_model, ADAPTER_NAME)
        peft_model.save_pretrained(temp_dir)

        loaded_peft_model = peft.PeftModel.from_pretrained(model=base_model,
                                                            model_id= temp_dir / ADAPTER_NAME,
                                                            adapter_name=ADAPTER_NAME)
        loaded_adapter_weights = get_adapter_state_dict(loaded_peft_model, ADAPTER_NAME)

        # Assertion fails due to adapter weights been newly intialized
        for key in adapter_weights:
            assert torch.isclose(adapter_weights[key], loaded_adapter_weights[key]).all()

Expected behavior
A clear error or warning message indicating that the adapter_name and tuner_prefix should not be the same.

 I suggest to raise when both adapter name and tuner prefix are the same when loading the peft model in the first place.

Ah yes, this is a bit of an unfortunate situation. You should have gotten a warning:

UserWarning: Found missing adapter keys while loading the checkpoint: [...]

But I agree that we could give another warning when we detect that the adapter name is a substring of the PEFT method prefix.
Btw. you may want to use peft.get_peft_model_state_dict in situations like this.

@BenjaminBossan I see, I have added a PR for this, but maybe the problem is so minor that it doesn't matter.


vimPlugins.ansible-vim: init at 2.0

[*] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[*] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[*] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[*] Tested execution of all binary files (usually in ./result/bin/)
[*] Determined the impact on package closure size (by running nix path-info -S before and after)
[*] Assured whether relevant documentation is up to date
[*] Fits CONTRIBUTING.md.

Okay. Force-pushed to my branch. Should I create new PR?


Rolling up main to beta

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: greens:white_check_mark: tpmanley:x: NikitaKuchtaYou have signed the CLA already but the status is still pending? Let us recheck it.


Fix on-premise typo

A letter that turns a notion into a building. Thanks for the typo fix @DevSecNinja.


Karma system may promote bad feedback behavior

I saw talk on discord that there are users who give low quality feedback, and still have very good karma. I'm thinking that it could be that even low quality feedback picks up a love here and there and so if you blast it across the page you might gain more than if you write high quality appreciated feedback.
I have an idea on how to deal with this, but I need to investigate the current code

I had someone mail me complaining about users that "liked everything" in a
post, and how this could be used to cheat.
On Wed., Aug. 22, 2018, 03:01 Martin Zackrisson<EMAIL_ADDRESS>wrote:

I saw talk on discord that there are users who give low quality feedback,
and still have very good karma. I'm thinking that it could be that even low
quality feedback picks up a love here and there and so if you blast it
across the page you might gain more than if you write high quality
appreciated feedback.
I have an idea on how to deal with this, but I need to investigate the
current code
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ludumdare/ludumdare/issues/1748, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABf2CYlPgE5SwccZOIXIgzkAUSArTLoIks5uTQGwgaJpZM4WHGnq
.

Simple fix would be
raw_feedback = min(42, love_total / comments_count *  10)

This would cap karma at 42, it's the general quality of your comments up to the cap of 4.2 hearts per comment.

 Only thing this doesn't do is give you credit for having written many comments. But on the other hand, the other aspects of smart does that already in part because it tracks grades given, and so it would be open to only commenting really good on a few games and earning a whole bunch.

I think eventually my intent with the smart filter was to make karma from
previous participants worth more, as a means of offsetting abuse, as it is
most likely come from first-timer accounts.
Anyway, in general I think this needs more research. I'll try to remember
to post a more useful transcript of the reported issue in the morning.

Only thing this doesn't do is give you credit for having written many
comments. But on the other hand, the other aspects of smart does that
already in part because it tracks grades given, and so it would be open to
only commenting really good on a few games and earning a whole bunch.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ludumdare/ludumdare/issues/1748#issuecomment-414936244,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABf2CfhKDcmQq8uibLOfFVTyHSoWIvU5ks5uTQXXgaJpZM4WHGnq
.

@mikekasprzak Our team's game was affected by someone abusing the system and I think we sent you that e-mail.
I think the current smart balance system can be abused by griefers to target specific games.
Especially this line:
$raw_given_feedback = commentLove_CountBySuperNodeNotAuthorKnownNotAuthor($node['parent'], $node['id'], $authors);
Lets say a griefing team has 3 people. If that team of were to specifically target another game, they could each leave a feedback then like every other feedback.
That would add 31.5 to the targeted game's smart_against balance.
(3 * 20 + 3) / 2.0 = 31.5.
Lets' assume that the targeted team has 20 feedback received and 40 given feedback, their initial smart balance would be:
(sqrt(40 * 100 / 20) * 10) - 100 = 41.42;
Then lets have our greifers come and like every comment and leave 3 dummy comments.
(sqrt(40 * 100 / (20 + 31.5) * 10) - 100 = -72.13;
So effectively that team of only 3 people can successfully reduce another team's smart balance by more than 100 by simply liking their feedback comments. And since we cannot find who liked the feedbacks (likes are anonymous?), we cannot track the offenders and kindly ask them to revoke their likes.
There's a cap for smart_against, but since there's also a cap for smart_for, the targeted team in this example will not expect to see a high smart balance for a long time.
Fortunately our game got the required amount of feedback before the arrival of the lone griefer, but it still has impacted us a lot. We have now given more than twice the feedback and rating than what we received but our smart balance is barely positive.

Sorry to hear and this does highlight for me at least that we have to run some simulations on this. I don't know the particulars of your case but the sad thing is that the griefer may well be unaware of what they did. They might have just liked your game and the feedback. And even if that was not the case, it is quite possible that someone accidentally destroys someone else's visibility.

Is it possible to find who liked our comments so we can ask him to remove those likes? I hope it was unintentional and it would be nice for us to get some more reviews for the ongoing Ludum jam. Our game entry is submitted by me, the Ludum Dare account has the same name as my Github account (bloc97).

Mike is out in the woods and the only one who could check since they are only accessible in the DB. As intended. But I'm not really sure what the good/right procedure could be in fixing that short of changing the algorithm

Again, like @local-minimum said, many people are probably doing this unaware. This also falls under the Education aspect of the site as I'm not sure many first-time jammers know what the algorithm really is, much less how hearts affect it.

Bringing back a trophy/badge system could also help incentivize helpful feedback.

It would be nice if we could get a cap on this soon, I can't upvote good feedback on the games I play unless I want it to be near-impossible for them to get any more ratings.
I can affect the smart score by about 13 smart points by upvoting the good feedback on one game, which is a huge difference

Why does liking someone's comments reduce the smartness of a game? What even is smart score? A way to show games with higher smart score? So the algorithm thinks a game has gotten enough reviews if many comments are liked, and thus reduces its smart score?

"Smart" is just the name given to the game prioritization algorithm. The
original algorithm was essentially "number_of_scores_received -
number_of_scores_given". Put another way, it wasn't very smart. 😉
Admittedly making the data public and calling it a score probably causes
more confusion than necessary, but we're rather trusting. 😉
On Thu, Apr 20, 2023, 22:31 Carlonn Rivers @.***> wrote:

Why does liking someone's comments reduce the smartness of a game? What
even is smart score? A way to show games with higher smart score? So the
algorithm thinks a game has gotten enough reviews if many comments are
liked, and thus reduces its smart score?
—
Reply to this email directly, view it on GitHub
https://github.com/JammerCore/JammerCore/issues/1748#issuecomment-1517171722,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAL7MCP4XITVHX3XDGZAVDLXCHWQLANCNFSM4FQ4NHVA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Good point. I'll dive into the algorithm over the weekend. Initially were
making a hard pivot to get folks to prioritize commenting (since it was way
too easy to get priority from giving ratings). That can most certainly be
cleaned up.
On Fri, Jan 20, 2023, 17:19 LoneWolfHT @.***> wrote:

It would be nice if we could get a cap on this soon, I can't upvote good
feedback on the games I play unless I want it to be near-impossible for
them to get any more ratings.
I can affect the smart score by about 13 smart points by upvoting the good
feedback on one game, which is a huge difference
—
Reply to this email directly, view it on GitHub
https://github.com/JammerCore/JammerCore/issues/1748#issuecomment-1399022179,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAL7MCMI7LCI5YISGVKFAJ3WTMFP5ANCNFSM4FQ4NHVA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Will this be fixed for Ludum Dare 54? I have quite honestly had a much harder time participating in Ludum Dare ever since Ludum Dare 51 when I was hit really hard by this bug.
It simply gives me a lot of anxiety knowing that, at any time, my game's karma could be tanked by anyone, anonymously, with no way to reverse it. When it happens to you, playing and rating games barely moves the karma meter, and it feels really bad, and it then requires the person affected to find other ways to reach 20 ratings, which is very stressful.
I would definitely appreciate it if it was fixed in time for play & rate for Ludum Dare 54. From what I've looked at in the source code it seems like it should be a pretty straightforward change, but I can't tell exactly what all the different variables mean for the rating formula, otherwise I would have opened a pull request by now.

Well, I don't actually know if I understand the code correctly, but I've created a pull request for this anyways. If I'm right that the "given_feedback" variable corresponds to the hearts left on comments on somebody's game, then my change should work.
Again I'm hoping this can be merged before Ludum Dare 54 (if the changes are correct).

Just to add on to this, here is another user already affected by this system for Ludum Dare 54: scroll down to the comment by cymusi
@mikekasprzak IDK what the best way to contact you is, but I definitely hope you take a look at this soon.


Release

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

v1.42.3
GitHub release

Your semantic-release bot :package::rocket:


Issue Cannot read property '_withTask' of undefined

Version
2.2.1
Vue.js version
2.5.2
What is expected?
I expected to have the same result as the 'Basic use' of the module documentation
https://peachscript.github.io/vue-infinite-loading/#!/getting-started/basic
What is actually happening?
The spinner doesn't disappear and the error message 'TypeError: Cannot read property '_withTask' of undefined' show up in the console of the browser (I use Chrome)
How to reproduce this problem?
I have install the module with npm and i use webpack for compiling my application. Did i need an extra configuration in webpack for the module ?
(Sorry for my bad english, i'm french ;))

Sorry for late, I don't think this problem was caused by this component, could you provide the error stacks that output to the console of Chrome browser?

I also encountered this problem, you now solve Well, if solved, is how to solve, urgent

@PeachScript
@mtibbo

@MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM it is still has not been solved, I need your help to reproduce this problem.

Thanks for the solution @PeachScript . I fixed it by adding that startProgress() method.

What?
The entire code is an exercise.

        <button @click="startEffect">Start Effect</button>

I run the code when Ass#1 is done, but get this

What is the property or method "startProgress"? Is that a built-in function of VueJS that I don't know?
Search on Internet..............Come here..................

        <button v-on:click="startProgress">Start Progress</button>

Ok, the HOLY startProcess() method is called in the DAMN Ass#6. Could have read the warn message more carefully. (Believe it or not, it takes me at least half an hour to figure out).

@PeachScript Thank you so mush.

This problem is the version of VUE, the version of VUE down to the 2.3 version of the good, the 2.5 version of the revision of the VUE source of one of the attributes, forget what property, can Google query
@PeachScript

If you are keeping empty method in the script file
or undefined event in the template it's giving "Cannot read property '_withTask' of undefined" error. I resolved this error by removing undefined events.

@yedidisatya thanks for your comment. I would like to implement your solution. The problem is that I cannot find any empty function nor any undefined events.
I think the problem is, that I maybe understand you wrong. Can you give me some example whats would be a wrong approach and what would be the solution?
kind regards,
Fabian

Possible solution for other people with the same issue:
In my case I defined functions in the computed-properties section of Vue, and tried to use them FROM WITHIN a function in the methods section. This will also lead to the _withTask error. Just move the functions from your computed section to your methods section to fix this.

If you are keeping empty method in the script file or undefined event in the template it's giving "Cannot read property '_withTask' of undefined" error. I resolved this error by removing undefined events.

it is work for me .

Possible solution for other people with the same issue:
In my case I defined functions in the computed-properties section of Vue, and tried to use them FROM WITHIN a function in the methods section. This will also lead to the _withTask error. Just move the functions from your computed section to your methods section to fix this.

VueJs Version :"2.5.21"
This works.  Note: you will get the _withTask error if the function is in with 'computed' or 'watch'


Push upstream changes into main trunk

One conflict because of a comment. Pfaugh.

This was supposed to be local.  :D


STORM-1616: Add RAS API for Trident

arunmahadevan added a note 3 days ago

Actually naming the operations wherever specific config needs to be applied looks cleaner and it separates out the streaming operations from the config specification.

TridentTopology topo = new TridentTopology();
TridentState wordCounts =
    topology.newStream("spout1", spout)
        .name("spout1")
        .each(new Fields("sentence"), new Split(), new Fields("word"))
        .name("split_operation")
        .groupBy(new Fields("word"))
        .persistentAggregate(new MemorymapState.Factory(), new Count(), new Fields("count"))
        .name("aggregate");

And then

topology.setConfig("spout1", Config.cpuLoad(20).memoryLoad(1024))
             .setConfig("split_operation", Config.cpuLoad(20).memoryLoad(256))
             .setConfig("aggregate", Config.parallelismHint(6));

The concern with directly adding each config api in Stream is that we might want to add more configs in future and then it would mess up the Stream api.'

This does not work, and would require an overhaul of the way naming works right now. First off, your example won't compile. persistentAggregate returns a TridentState, which doesn't have a name method. Okay, well we can move the name call up to just below the groupBy. It's a little confusing being right in the middle, but groupBy returns a GroupedStream, which has a name method. Unfortunately, you end up with all your bolts being named "b-*-aggregate" because 'GroupedStream' just renames the stream before it. In fact, except for differentiating between the spout and body, I don't see any existing way to give different sections different names, and doing so is not a simple change, and not one that is going to be backwards-compatible.
I agree with your point in principle, but how much do we want to change the existing API to accommodate it?

I lean toward making this part of the Stream API, just like parallelismHint(). In both cases it is about requesting cluster resources, (I.e. Threads/CPU/Memory).
I'm strongly against (though open to new ideas) of making this a topology-level API as proposed earlier. That approach involves a lot of "magic strings" and feels to me like a violation of the Trident API. If there's a better way to do it, I'm open to it, but let's not use strings as identifiers.

@knusbaum @ptgoetz in the proposed name based approach, the naming needs to be done only when one wants to pass specific configs to the node executing the streaming operation, not always. Agree it has magic strings which needs to be matched, but it keeps the configuration and streaming operations separate. The main concern with adding the apis to the Stream is that as we add new config apis to the stream, the stream api gets messy.
Understand the current limitations, so for now I think we may make it as a part of the stream api, but do evaluate directly adding all the methods to the stream vs adding a single config method taking params.

@arunmahadevan @ptgoetz Okay, good. We'll leave it in the Stream API then.
I don't really agree that it's better to have one method and a LoadConfig object. It seems like over-engineering just in case someday we add more things.
It seems like a reasonable compromise, though, so I'll add that stuff in.

I am not really sure that we are going to need a Builder interface for setting resources, and for me consistency between the trident and regular storm APIs is more important than the number of methods in Stream.  Right now we only support CPU and Memory as resources.  If we ever add in more resources, or especially generic resources we can add in the Builder API or some other more Generic API to both trident and storm.  For now I think this current API is relatively simple and consistent with the rest of trident/storm.
I am +1 for the current API, but I do have a few comments about the code.

As the original author for RAS, I am +1 for the current API.  The most important thing for me is to maintain consistency between the API to set resource load in Trident and Storm

@arunmahadevan @satishd @ptgoetz,
Would like your comments on the builder pattern. There are +1's but I believe there were some concerns.

@knusbaum I guess the main concern against builder is that we want to maintain compatibility between core and trident. If so I am fine to change both the apis together and/or explore some other way to pass the config (load, parallelism etc) in trident as a followup. In my opinion, separating the config and the streaming operations would make the trident stream api less cluttered.

@arunmahadevan Thanks, that sounds good to me.

+1

@knusbaum Technically this should have waited another ~24 hrs. after the last code change, but I'm not worried because the last change was minor.
Are you planning to pull this into 1.x-branch as well?

@ptgoetz Bylaws say "1 day from initial patch." I think it makes sense wait longer in general.
I can pull this into 1.x if you want. I thought we were freezing features on that branch, though. I've been a little unclear on what should go in and what shouldn't.

@knusbaum Yeah, you're right. :) I always try to wait based on last patch. We should think about changing that.
As far as pulling it into 1.x, I am +1 for it. Although it is a new feature, it builds on top of the core storm RAS feature and I feel it would round out the release. I'd rather 1.x have RAS support for both APIs than just core storm.

@ptgoetz Makes sense to me. I'll merge it into 1.x.
I'd be +1 for changing the wording in the bylaws, too, if you want to start a [DISCUSSION] or [VOTE], etc.

@knusbaum Looks like the clojure tests diverged, I haven't looked at how much. When I think about trident I usually think "not clojure" and forget about the integration tests. :)
I'll start a discussion for the bylaw change.

@ptgoetz The clojure tests diverged, but it's just import statements. If you want me to create a PR for that, I will, or if you trust me to resolve the imports, I'll just fix them and merge.

@knusbaum Yeah, just looked at the conflicts. Not to bad.
Go for it.


Hi Team, Can you please help where we have defined this key "DbPassword" in the code

https://github.com/aspnet/Docs/blob/f567d0328efe25696d7cdd23ec50c0cf4328d0a6/aspnetcore/security/app-secrets/samples/2.1/UserSecrets/Startup2.cs#L26

Hi @gagandeepp ... It's not defined in the code. It's defined on the command line. See: https://docs.microsoft.com/aspnet/core/security/app-secrets#string-replacement-with-secrets
dotnet user-secrets set "DbPassword" "pass123"

@gagandeepp Also see the following section, which explains where the Secret Manager tool stores the secrets on your machine: https://docs.microsoft.com/aspnet/core/security/app-secrets?view=aspnetcore-2.0&tabs=windows#how-the-secret-manager-tool-works. The command provided above by @guardrex stores the DbPassword key-value pair in a secrets.json file.


running sandbox with an expired sso session prints error twice

Environment information
System:
  OS: macOS 14.4.1
  CPU: (10) arm64 Apple M1 Pro
  Memory: 182.30 MB / 32.00 GB
  Shell: /opt/homebrew/bin/fish
Binaries:
  Node: 20.12.2 - ~/Library/Caches/fnm_multishells/72748_1715201332327/bin/node
  Yarn: 1.22.19 - ~/Library/Caches/fnm_multishells/72748_1715201332327/bin/yarn
  npm: 10.5.0 - ~/Library/Caches/fnm_multishells/72748_1715201332327/bin/npm
  pnpm: 9.1.0 - ~/Library/Caches/fnm_multishells/72748_1715201332327/bin/pnpm
NPM Packages:
  @aws-amplify/backend: 1.0.0
  @aws-amplify/backend-cli: 1.0.1
  aws-amplify: 6.2.0
  aws-cdk: 2.140.0
  aws-cdk-lib: 2.140.0
  typescript: 5.4.5
AWS environment variables:
  AWS_PROFILE = josef-gen2
  AWS_STS_REGIONAL_ENDPOINTS = regional
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
No CDK environment variables

Description
➜  p amplify sandbox

ampx sandbox

Starts sandbox, watch mode for Amplify backend deployments

Commands:
  ampx sandbox delete            Deletes sandbox environment
  ampx sandbox secret <command>  Manage sandbox secrets

Options:
  --debug            Print debug logs to the console
                                                [boolean] [default: false]
  --help             Show help                                   [boolean]
  --dir-to-watch     Directory to watch for file changes. All subdirectori
                     es and files will be included. Defaults to the amplif
                     y directory.                                 [string]
  --exclude          An array of paths or glob patterns to ignore. Paths c
                     an be relative or absolute and can either be files or
                      directories                                  [array]
  --identifier       An optional identifier to distinguish between differe
                     nt sandboxes. Default is the name of the system user
                     executing the process                        [string]
  --outputs-format   amplify_outputs file format
            [string] [choices: "mjs", "json", "json-mobile", "ts", "dart"]
  --outputs-version  Version of the configuration. Version 0 represents cl
                     assic amplify-cli config file amplify-configuration a
                     nd 1 represents newer config file amplify_outputs
                               [string] [choices: "0", "1"] [default: "1"]
  --outputs-out-dir  A path to directory where amplify_outputs is written.
                      If not provided defaults to current process working
                     directory.                                   [string]
  --profile          An AWS profile name.                         [string]
  --once             Execute a single sandbox deployment without watching
                     for future file changes                     [boolean]

InvalidCredentialError: Failed to load default AWS credentials
Resolution: To configure a new Amplify profile, use pnpm ampx configure profile.
Cause: Token is expired. To refresh this SSO session run 'aws sso login' with the corresponding profile.
InvalidCredentialError: Failed to load default AWS credentials
Resolution: To configure a new Amplify profile, use pnpm ampx configure profile.
Cause: Token is expired. To refresh this SSO session run 'aws sso login' with the corresponding profile.

was able to reproduce the duplicated message, marking this as bug.


Question: Remove extra spaces between sentences

I wonder if there is a setting to remove extra spaces between sentences. I noticed some Americans make 2 spaces after the period.
Thank you!

This is an example of the text: https://answers.uillinois.edu/uic/111138
I had that setting enabled, but it still left double spaces between sentences.

Is that a PDF? Or am I missing something about which piece of text you are referring to?

The main article text.

Everything I am seeing from a casual attempt to do a regex match shows that those should be affected by remove multiple spaces, but I will have to take a closer look at a later time.


bug in swift-algorithm-club/Queue/Queue-Optimized.swift

Queue algorithm fails here
public mutating func enqueue(_ element: T) {
        array.append(element)
}

on the following test with error "EXC_BAD_ACCESS", "Heap buffer overflow" or "Use of deallocated memory"
var test_queue = Queue<Int>()
var temp = 1;
for _ in 0..<10000{
    self.test_queue.enqueue(temp);
    temp = self.test_queue.dequeue();
}

Now I'm not the author of the Queue example but I can't reproduce your issue. Also dequeue is returning an optional which you should unwrap with self.test_queue.dequeue()! or do it with a guard let - statement

Also gave this a check - no problems here.


Implementing minimum accept XRB value from GUI

By default desktop wallet do POW for every incoming transactions and it can be targeted by penny transactions that requires huge amount of pow this may crash the node or make's the user computer rendering unstable. To avoid doing pow for every transaction irrespective of the amount received. If we implement minimum accept value this will prevent unnecessary pow and protect the desktop wallet users.

The option should be configurable in the gui.


Suggestion: Add Fibratus tool

Hi,
Would you find it beneficial adding Fibratus in the list of available tools?
Fibratus is a tool for Windows kernel tracing and observability. It includes a powerful filter engine, the ability to generate capture files ala pcap, craft Python scriplets on top of kernel event stream, transport events to output sinks and much more.

Thank you for your feedback! We've been working on major updates to FLARE VM over the last year.
The now revamped FLARE VM has just been released and will make the project more open and maintainable.
Please check out our blog post at https://www.mandiant.com/resources/blog/flarevm-open-to-public and give the new installation a try.
If this problem still persists with the new installation, please report:

new tools or tool-related issues at https://github.com/mandiant/VM-Packages/issues
ideas and issues related to the installer script and configuration at https://github.com/mandiant/flare-vm/issues

Please note that we use this message to close all legacy issues in this repository. We look forward to your feedback and support for the next generation of FLARE VM.


Refactor code

fixes #16.
Started working on it. The app currently is an horrendous state. Adding EF 7 and SQLite is not possible with current architecture.

Fixes #16

Fixes #22
Fixes #21


Enable GCP on OpenShift

Enable GCP on OpenShift
https://issues.redhat.com/browse/COST-2245

Codecov Report

Merging #2334 (37e46ca) into master (91a1bbd) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 37e46ca differs from pull request most recent head 5cc05b1. Consider uploading reports for the commit 5cc05b1 to get more accurate results

@@           Coverage Diff            @@
##           master    #2334    +/-   ##
========================================
  Coverage   68.89%   68.89%
========================================
  Files         410      410
  Lines        7818     7818
  Branches     1857     1734   -123
========================================
  Hits         5386     5386
  Misses       2428     2428
  Partials        4        4

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 91a1bbd...5cc05b1. Read the comment docs.


About the 'advent' module.

The 'advent' module is used in the code to get the discriminators and losses. But I don't find the module in your code. Could you let me know if you've released this module yet?

I have found it in readme. Sorry.