Socket is always reconnected after I received push notification.

Steps to reproduce

Disconnect connection of pusher
Change application status to background status.
Get push notification.

The change log of status are ...

disconnected
disconncted
connected

Expected behavior
I want to keep disconnected while the app in background.
Actual behavior
The connection is always reconnected after push notification.
...
The app performance and network usage is affected this issue.
I think the priority is very high.

@hamchapman Do you have any idea for this issue?

When I change autoReconnect to false, this issue is not reproduced.
The work-around I take is implement auto reconnect logic by myself.

@yukitoto Apologies that you didn't get a timely reply to this issue... What version of the SDK are you using? Do you still see the same behaviour on our latest release, v9.0.0?

Since the latest v9.1.0 release contains reconnection functionality improvements, and since there has been no response, I'll close this issue for now. If it's still a problem, please feel free to reopen this issue.


2.1 hotfix security

Takes the 3 separate PRs and merges them into a hotfix branch off of ODH 2.1.

#488
#501
#502

/cc @lucferbux @cfchase @jkoehler-redhat @LaVLaS

Manually merged this as it is not going into main. Reviews were done on each PR.


[SwiftLanguageRuntime] Fail when we can't retrieve the type.

This would've made diagnosing other bugs much easier because
we fail immediately instead of going on and producing an
invalid expression. It may seem very brusque to just fail here,
but I think this is good to shake out issues instead of hiding
them.

@swift-ci please test

From what I see lldbassert isn't really what we want here.
My understanding is that

lldbassert logs (but doesn't assert) in release
asserts in debug.

I'd really love to be stricter. For the bug of last week lldbassert wouldn't have helped as enabling the log causes the bug to disappear. In other words, assert is a much more reliable mechanism here.

Ah, right, we want something that asserts in release mode also. Yep, this lgtm.

We try to make a distinction between "errors on user data" and "errors on validated computed data".  It is totally appropriate to assert on the latter.  We try never to assert on the former, but instead find a way to back out and not crash.  This is DEFINITELY in the "errors on user data" category, and we have a well-established way to handle ValueObjects whose types we can't determine, we signal that by returning an invalid type, and since we always know that reconstructing the types for values is an iffy thing, we alway check that CompilerTypes are valid before using them.
This is not a change we should make.

The purpose of this is finding cases where it fails, and fix them accordingly (or decide whether we want to make them errors).
In the context of an expression being evaluated, if you have
Patatino<T> where T = String and you can't resolve it, well, you'd better stop really soon because chances are you're going to construct an invalid expression and fail with a really cryptic and spectacular error. If there are cases where it's actually legit that the type can't be resolved, then the API between compiler and debugger should be enhanced to discriminate between the two.

The general idea here is to let us operate on CompilerTypes reliably (it should never be an 'iffy' thing), and to let us kill things like CompilerType::IsValid() (which we can do by asserting on bad data -- user or otherwise -- and passing around Optional<CompilerType>).
So, fwiw, this is a change I'd be happy to have :).

@jimingham To elaborate on why I think operating on CompilerType should never be iffy, consider how types are handled in llvm/clang/swift etc.
llvm::Type can never be invalid, clang::QualType can never be invalid, swift::Type can never be invalid, etc. This is great because you can do things with types with confidence, without lots of menial double-checking of "Ty.isValid()", which you'll invariably forget to do.
Asserting early on invalid inputs and passing around only valid CompilerTypes or Optional<CompilerType> will get us to non-iffy type handling.

It is never safe to expect that you can reconstruct the type for something.  The DWARF could be screwed up.  The variable could not be initialized yet and we are relying on runtime properties to figure it out.  We also can sometimes figure out the name of a variable (from the ObjC runtime) even though we can't figure out its type.  That's still a somewhat useful object.
So the iffiness is in the behavior of the world, not in the behavior of lldb.  We just can't 100% guarantee that we can figure out the type of variables.  In lldb the clear rule is it is NOT a fatal error not to be able to reconstruct the type, and if you can't figure it out then you return an empty compiler type and if you are going to use the type of something you need to check if it is valid.

lldb types are totally different things from clang types.  A clang type is figured out from source and if you couldn't figure it out you would have had an earlier error.  OTOH, for instance, the default clang behavior is to only emit class definitions in the debug information for the module that has the vtable for the class.  So if I give you headers and a dylib that contain a class you are supposed to subclass, but DON'T give you debug information for the dylib, then lldb won't be able to construct the type for the subclass.  That's expected behavior and we have to deal with it.  Types are computed data not user data for clang.  Types are user data (from DWARF, etc) for lldb.  So it is appropriate for clang to treat types as things that always have to be valid.  It is NOT appropriate for lldb to treat them that way.

It's fine to not be able to reconstruct a type, but a CompilerType should either be valid or not exist.
If there's other useful information about a Value, like it's name, it should be moved out of the CompilerType if it isn't already.
For this particular patch: there's no test coverage for invalid CompilerType generation in this method. Until we have that test coverage (i.e, until we're really sure it happens), I don't see why we'd bother handling invalid types here. Having an assert will help us determine whether or not that happens.

(By "really sure", I mean, we have a solid understanding of it, as well as a reliable test :)

I disagree.  I don't think you will ever be able to write test cases for all the ways user data in the compiler could fail.  For instance, a newly introduced bug in clang that causes horked up data in a way you could never have thought of.  Such a thing might even get out into the field and then we would be crashing the debugger even though the users might not even care about that type.  Would you feel okay telling users "It was okay that I crash on you every time you load your binary built with a new clang: I couldn't have known to write a test case for that so I it wasn't my responsibility to handle it gracefully."
Seems to me the way you build software that actually gets up to the point where it is useful enough that you can start using it is you have to first of all have clear policies for handling errors and implement the policy everywhere.  In this case the policy is clear: "The inability to construct a CompilerType is NEVER a fatal error, and you signal that by returning an empty CompilerType."  It's not a clear policy if it is only followed when you can construct a positive test case that traverses that error.  You apply the policy everywhere, then go back and fill in with as many tests as you can manage to construct.

We use lldbasserts because then if the compiler (e.g.) gets a new bug, and we're lucky and our test suite triggers the bug, then the test will crash.  So we catch it early.  But if the bug in our user data (DWARF, RemoteAST, whatever) gets out into the field, then we DON'T want to take down a user's debug session because of a bug in other parts of the system.   And especially if you can easily see how to recover - have an invalid compiler type, and say "couldn't figure out type"...
But given that RemoteAST doesn't claim to always be able to figure out the type (that's why it returns a checkable entity) we should not claim a stronger promise by asserting here than RemoteAST was willing to assert.

We can write the tests we need if we try, and that means we need to make failure cases easy to discover, i.e using assertions.
This is what clang/swift do: e.g yes, the parser may have a bug and accept invalid code, but the response isn't to make all type handling iffy, because that would pose a high maintenance burden. Instead, the response is to test the parser thoroughly. lldb isn't different.
And, of course I don't want the debugger to crash on users :). I just think the way to achieve that is by being a bit stricter about what we consider valid internal data structures, and to ramp up testing.
I take your point about needing clear policies to build useful software, but think the policy needs a change :). To restate it: CompilerTypes should either be valid or not exist, and we should enforce that strictly (e.g with test coverage). That's where this patch is going.

@jimingham I'm worried we're talking a bit past each other at too high a level.
Perhaps we can look at removing the IsValid() method from CompilerType and propagating Optional<CompilerType> instead -- I'm hoping we can agree that it should be impossible to accidentally use an invalid CompilerType.
If you're not convinced by this patch, we can revisit the issue of test coverage / assertions later, perhaps?

Again, you give an example of clang which is not instructive.  If clang can't figure out what a type is, something has gone wrong, the compile is going to fail and it's fine to get out of there.  lldb OTOH has to cope with the fact that it can't always construct types (see the example above, but there are many others).  You can't treat a CompilerType as a non-failable thing in lldb, it isn't.
I don't want to argue that point if you don't mind, it's been true in so many ways both in gdb & lldb, you just have to take my word for it.

To be clear, I agree with you that lldb has to deal with not being able to reconstruct types, and realize that it's different from clang in that it needs to be resilient to more types of errors. I'm not disagreeing on that point at all.
I do think adding asserts and test coverage is the way to discover failure modes & avoid operating on invalid state, but am fine with discussing that later.
I was hoping to at least reach a decision on CompilerType::IsValid() (or is it ::IsInvalid()?). Are you with the following plan:

Make the CompilerType() constructors private
Add Optional<CompilerType> CompilerType::create(...) as a static method
Kill CompilerType::IsValid()

?
That would make it impossible to accidentally use an invalid CompilerType, which is what we really want here.

I am actively opposed to any patch that asserts that we can always get a compiler type from out in the world - and going through RemoteAST is definitely going out into the world.
As for whether you use a compiler enforced policy or a social policy, that I have no strong opinion on.  The dangers of not enforcing these policies have been mostly theoretical so we haven't set aside the time to go plumb through some forced-check access policy.
But if there's some compile-time way to force using code to check the validity of the object before touching it, and it doesn't make the contents of the code get obscured by the policy enforcement, and you have the time to go do this, then I have no objection to that.

Ok then, that at least gives us a path forward. Having done similar refactoring in llvm before, I'm sure we'll catch and mitigate accidental misuse of CompilerType by wrapping it in Optional (which also  tends to be more legible, in my experience).
And I am fine with discussing having asserts+coverage later :).

Sure, go for it.  If you're interested in the history of the "asserts in lldb" discussion it's come up a bunch of times previously on the lldb list.

What exactly would we still need to assert once we have CompilerType wrapped in an Optional?

Possibly asserting invariants on the CompilerType itself. It's hard to say, it's a bit too high level at the moment.

One last comment about testing  vrs. production of entities from "user data'.  The view we took with lldb was that unless you can prove that an operation can not fail, you should always assume it can fail and plan to handle that.  Even if you can't actually figure out how to generate the failure, you must assume it can fail and handle it.  After all, debuggers deal in imperfect data and SPI's and they lie and fail in unexpected ways all the time.
Then as time permits, you should go through and try to produce failures in tests, to make sure you handle them correctly.
You must not think, "that might fail, but I can't figure out how to trigger the failure, so I don't need to handle a failure here."  Then you will crash on some user somewhere and they won't have any recourse.

This particular case, however is one we should expect might fail sometimes.  After all, the API returns a fallible object...
It's perfectly reasonable to assert in the test suite, saying "all the operations we know of in the test suite should not fail here".  That's what lldbassert is for.
But it is not appropriate to assert on users - or to just do something undefined like accessing an object that the provider said was not good and then asserting if that didn't manage to crash before you got to the assert.
In this case, the error is going to be very clear.  There will be some variable somewhere that we won't be able to print because we can't recover it's type.  So you really aren't saving yourself any work figuring out the error here.  At best you might force users to report the fact that we didn't get a value for their variable because instead of just not getting the value for that one variable and leaving the debug session going along fine, we will crash.  That is NOT a win.

The assert is fine until there's test coverage for the failure case. This goes back to our general disagreement on what the error-handling policy should be, so we're rehashing things now. Let's stop while we're ahead, as we've found identified work on CompilerType that we're in agreement on :).

In this case, the error is going to be very clear. There will be some variable somewhere that we won't be able to print because we can't recover it's type. So you really aren't saving yourself any work figuring out the error here.

I'm afraid this is not the case. The bug in this case manifested in two different instances:
frame var Patatino
prints
MyClass<T> Patatino = ...
instead of
MyClass<String> Patatino = ...
so, no error, just a wrong type silently emitted.
If you instead try
print Patatino
you get an error while parsing the expression cryptic enough.
On top of that:

This only reproduces in release builds
If you enable the log, the bug goes away.
The assertion catches the bug right away.

So, I wouldn't necessarily claim "the error is very clear".

I think in the frame var case the contents of your "..." was significant.
When we thought the variable was of a generic type because we couldn't reconstruct it's real type we also didn't print a value for it.  Unable to print any value for a variable is a pretty clear error.  If you were debugging and cared about that variable you would immediately notice (e.g. in the Xcode locals window) that the variable had no value and reported it to us.  If you didn't care about the value of that variable you would be very happy we didn't crash on you.
IIRC, we also had a test case whose failure lead you down this path.  So if you had an lldbassert in the place you wanted to bail altogether, it WOULD have asserted in the testsuite and done exactly what you wanted.
If the error message in the expression parser when we can't reconstruct the type of a variable that's part of the expression is unclear, we should address that directly, since that's a pretty straight-forward error.

We had an offline conversation about a different way of handling this.
I'll probably revisit the approach later in the week. Closing this for now, and thanks to everybody involved!


multi images resizing in predict_file function

fix #429 #438

@satsin06 - looks like the tests are failing. Can you take a look and see if you can figure out what's going on?

It's seem there is problem with trainer.fit(m) function in test_callbacks.pay file, and I'm finding difficulty in resolving it. Please help!


update action to use node 16

Pre-requisites:

[ ] I looked through both open and closed issues and did not find an existing bug.

Description

The following annotations are now showing up in github actions that currently utilize this github action

Expected Behavior

Update to use node 16 and clear the warning
Actual Behavior

Steps to Reproduce

Other Information

@AmericanAirlines/preload-local-actions-action-maintainers ☝


SD Card Detection when restoring stock and backing up firmware.

I found a bug when i tried to use a SD card with one partition to restore my stock firmware.
The issue is the inbuilt SD card reader default drive letter is /dev/mmcblk0 (the internal EMMC is /dev/mmcblk1) causes it not to be detected as the firmware utility script only scans /dev/sd* for devices.

problem is script assumes mmcblk0 is internal, there's no good way to differentiate between internal/external devices AFAIK.

@MrChromebox that's what I thought was just asking if there was another way that I couldn't think of. SMART data?
Probably to big of a pain to add for the one person who decides to us a SD for onse.


[scan] Fix the default derived_data path

LGTM - is there any way we can cover this with a test?

@mfurtak Yes, updated tests to cover this change https://github.com/fastlane/fastlane/pull/5711/commits/69a25e3107d7678fcffac85b86826c54cae8513f 👍

:100: 👍


Should we replace our Next.js for Storefront?

This is not a priority until after v1.
Replace with Remix, Astro?
Create a new folder (apps/www?) for our remix version of the storefront.

Should we use Sanity instead of plain mdx?

### Tasks
- [ ] POC: Test Remix with a page from Storefront

I think it would be nice to change to using a CMS, wether we change framework or not.
Sanity supports both Next.js and Remix, and it would be nice to test this out when testing Remix.

What are the motivation to replace Next.js?


Update teams-recording-policy.md

@cabailey PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

@2kiran Apologies for missing this previously - because your GitHub profile is still not updated.  To ensure your PRs are merged efficiently as the PM owner, please update your profile.


[Button] Support "dashed" variant for buttons with dashed border

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
Add "dashed" variant as a built-in variant in Button component.
Examples 🌈
<Button variant="dashed" color="secondary">Button</Button>

Expected Behavior

Motivation 🔦
Click to open codesandbox demo
I was trying to add a custom prop "dashed" as a variant in MUI Button component.
components: {
    MuiButton: {
      variants: [
        {
          props: { variant: "dashed" },
          style: {
            borderWidth: "2px",
            borderStyle: "dashed"
          }
        }
      ]
    }
  }

However, for the code above, I have to specify the exact color code borderColor that I want to apply for this button. Instead, it would be easier if I can just pass a color prop such as primary|secondary, then the border color can change according to the color prop that I passed.
Another issue I found was that the size prop does not work with a custom variant.

Add "dashed" variant as a built-in variant in Button component.

We cannot support lots of Button variants for different use-cases. There could be many use-cases, and that's where customization comes in and you can have your own styles defined. Having multiple styles added for each and every variant will increase our bundle size.

However, for the code above, I have to specify the exact color code borderColor that I want to apply for this button. Instead, it would be easier if I can just pass a color prop such as primary|secondary, then the border color can change according to the color prop that I passed.
Another issue I found was that the size prop does not work with a custom variant.

This is related to #32427 and #34600. Those issues are for size prop, but likewise it applies for color prop.

@ZeeshanTamboli this looks like a duplicate, we even have a PR that would fix the issue: https://github.com/mui/material-ui/pull/34606


[Bug]: Issue with BiDi-powered logging

Bug expectation
I expected to get a message logged to my terminal, but I didn’t get any.
Bug behavior

[ ] Flaky
[ ] PDF

Minimal, reproducible example
import puppeteer from 'puppeteer';

const browser = await puppeteer.launch({
  protocol: 'webDriverBiDi',
});

const context = await browser.createIncognitoBrowserContext();
const page = await context.newPage();

page.on('console', (message) => {
  console.log(`Unexpected console message received: [${
    message.type()
  }] ${message.text()}`);
});

await page.goto(`data:text/html,<script>console.log('1');</script>`);

Error string
No error
Puppeteer configuration
No response
Puppeteer version
19.9.0
Node version
16.14.0
Package manager
npm
Package manager version
8.14.0
Operating system
macOS

I added the following script and run it. I get the Unexpected console message received message in console. What did I do wrong?
const puppeteer = require('puppeteer');

(async () => {

  const browser = await puppeteer.launch({
    protocol: 'webDriverBiDi',
  });

  const context = await browser.createIncognitoBrowserContext();
  const page = await context.newPage();

  page.on('console', (message) => {
    console.log(`Unexpected console message received: [${
      message.type()
    }] ${message.text()}`);
  });

  await page.goto(`data:text/html,<script>console.log('1');</script>`);
})();

First suspect is not waiting for the subscribe command to finish: https://github.com/puppeteer/puppeteer/blob/57c57274243e3e83f1fe8f8fdb37eb8d3911d32d/packages/puppeteer-core/src/common/bidi/Page.ts#L53

Closed by #10060


Error when trying to import 'mailgun-js'

Is it possible to use import syntax instead of require when using this module?
Webpack is failing to compile when I use import syntax instead of require.
Thanks!

You figured this out?

@jonathanphz I couldn't get it to work.  I ended up just doing const Mailgun = require('mailgun-js').  Sorry for not explaining that when closing.


[Enhancement]: Rabbit Rush Game

Do you want to have the enhancement of existing game ? 😀 Describe yourself..
Actually, I was playing the Rabbit Rush game, I liked it but there are some enhancements required in that game such as there is no pause, resume button in it , also there is no catchy background in it which should be there and also there is no best score feature in it .
Describe the solution you'd like
Firstly , I would like to improve the UI of the game  so that there comes a light colored background and also I want to change the distance score color from red to green and then I want to add on  some new features like Best/High score, resume, pause buttons.
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @Changingthegame !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign

Hello @kunjgit , I have done necessary changes and pull request has been approved and merged. I am closing this issue as I am unable to get assigned and work on another issue in your project.

Hey @Changingthegame ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Enable presubmit on Prow

Fix Build Issues
Create presubmit script
Update e2e framework to save logs to _artifacts folder instead of uplading them to gcloud storage since Prow already does this.

Hi @sebastienvas. Thanks for your PR.
I'm waiting for a  member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

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 kubernetes/test-infra repository. I understand the commands that are listed here.

/ok-to-test

@sebastienvas: you can't request testing unless you are a  member.

In response to this:

/ok-to-test

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 kubernetes/test-infra repository.

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
d2470b301dc1701d722c394a99df248bbc2355f0
link
@istio-testing bazel test this

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 kubernetes/test-infra repository. I understand the commands that are listed here.

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
bd4fff12b827dbb85003035035f87f2995a924e9
link
@istio-testing bazel test this

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 kubernetes/test-infra repository. I understand the commands that are listed here.

Jenkins job istio/presubmit passed

Jenkins job istio/presubmit passed

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
b8163fe1693ce0cda035a10161e89750afb3c385
link
@istio-testing bazel test this

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 kubernetes/test-infra repository. I understand the commands that are listed here.

Jenkins job istio/presubmit passed

Jenkins job istio/presubmit passed

Jenkins job istio/presubmit passed

Jenkins job istio/presubmit passed

Prow results are available here

Jenkins job istio/presubmit passed

Jenkins job istio/presubmit passed

Prow results are here. Note that artifacts were also uploaded as well.

Jenkins job istio/presubmit passed

Jenkins job istio/presubmit passed

Jenkins job istio/presubmit passed

Jenkins job istio/presubmit passed

bam!
On Fri, Jul 14, 2017 at 7:48 PM Sebastien Vas<EMAIL_ADDRESS>wrote:

Merged #464 https://github.com/istio/istio/pull/464.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/464#event-1165108472, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ACBRURzOSeYvChP9SVPA7wNp4Y4IkC_9ks5sN_48gaJpZM4OTech
.


Building/Publishing from Source Error:

Hello, I'm trying to build the source code in VS2022 and I'm getting the error "The type or namespace name 'Windows' could not be found (are you missing a using directive or an assembly reference?)". However, when doing a normal build, it works perfectly fine.
I've been trying to use my "custom" version of the code with my own loading screen but it also does the same from the original code.
I've tried to manually add in different dependencies and frameworks to try and resolve it but to no avail.

I could be missing something simple but, I'm not sure.

Yeah, I don't really know why but publishing from inside VS is broken. Publish from the command line instead.


Expose BGP metrics for Prometheus.

Description

Adding new port to calico-node-metrics service to expose BGP metrics for Prometheus.

For PR author

[ ] Tests for change.
[ ] If changing pkg/apis/, run make gen-files
[ ] If changing versions, run make gen-versions

For PR reviewers
A note for code reviewers - all pull requests must have the following:

[ ] Milestone set according to targeted release.
[ ] Appropriate labels:

kind/bug if this is a bugfix.
kind/enhancement if this is a a new feature.
enterprise if this PR applies to Calico Enterprise only.

Tested it using local version of operator and it works as expected.


Create project template?

Under the Quickstart, the first step says.

Download master to use it as the template project.

How is this set as "the template project"?

I agree, it's a little confusing. I don't really know how to add a real template project to Defold. Here we are talking about just copying the repository and taking its files as the basis of your future project.

At the moment you can't set new template projects in Defold.
I'm doing something similar for a project of mine, and the way I'm approaching it is through an editor extension with a menu to initialise what I need. I basically create the files on the fly with this.
Not sure if it works in your case because you also have the debugger and other things, but maybe it's worth a try?

Not sure if it works in your case because you also have the debugger and other things, but maybe it's worth a try?

True, unfortunately. Installing the extension is not suitable here, because the extension is installed in a separate folder and is stored as a zip archive. Here there is only one lua-file, and the rest are invisible files and folders for VSCode and git.

By the way, I just discovered the templates on github. I think this is a good option!


LibreChat / ChatGPT API issues

Hey, I wanted to ask if you have any tips regarding the following issue. We're trying to get everything running in LibreChat on Discord (https://github.com/danny-avila/LibreChat). But it seems like the ChatGPT API doesn't understand that it can execute code with this plugin.
{
    plugin: e2bcodeintepreter
    input: {"query":"execute code","code":"print('Hello, World!')"}
}

Encountered an error while attempting to respond. Error: No function_call in message [{"text":"I apologize, but I am an AI language model and I do not have access to external APIs or the ability to execute commands. However, I can help you with any questions or provide guidance on how to use the provided API's. Please let me know how I can assist you further.","message":{"lc":1,"type":"constructor","id":["langchain","schema","AIMessage"],"kwargs":{"content":"I apologize, but I am an AI language model and I do not have access to external APIs or the ability to execute commands. However, I can help you with any questions or provide guidance on how to use the provided API's. Please let me know how I can assist you further.","additional_kwargs":{}}}}]

I think that the query to the plugin is in a wrong format. You can check the openapi.yaml of the plugin - we support very specific routes that ChatGPT calls and query "execute code" is not something we can process.


Programmatically Changing Tab

I'm trying to change the tab programmatically when a table view cell is being tapped
This is my current code:
func tableView(_ tableView: UITableView, didSelectRowAt indexPath: IndexPath)
{
let vc = MainViewController()
vc.didSelectItem(atIndex: 2)
}
When I do this, the app crashes in the MainViewController in the customization() method on the View Controller init. (crashes when setting the storyboard.
If I set self.viewsAreInitialized to true before I programmatically select the Item, the app crashes in TabBar.swift  on the highlightItem function.
Is there a better way I can programmatically change the tab from one of the view controllers?

Probably the easiest way to do is to use NotificationCenter.
Add observer to MainViewController with implementation and post to that Notification from didSelectRowAt method.
P.S. That delegate method vc.didSelectItem(atIndex:) will work if your ViewController has TabBarDelegate delegate object and MainViewController is confirming. However I think it will scroll to given page but tabBar will not be updated.

Hi! Thanks for your response.
I'm trying to implement the notifications but I'm getting unrecognized selector sent to instance error on the tableView:didSelectRowAtIndexPath method.
This is my didSelectItem method in MainViewController:
    func didSelectItem(atIndex: Int)
{
        self.collectionView.scrollRectToVisible(CGRect.init(origin: CGPoint.init(x: (self.view.bounds.width * CGFloat(atIndex)), y: 0), size: self.view.bounds.size), animated: true)

        let notificationName = Notification.Name("switchT")
        NotificationCenter.default.addObserver(self, selector: #selector(SearchViewController.tableView(_:didSelectRowAt:)), name: notificationName, object: nil)
        }

This is my didSelectRow method in my SearchViewController (view controller with the table view)
    func tableView(_ tableView: UITableView, didSelectRowAt indexPath: IndexPath) {

        print("item selected: \(indexPath.row)")

        let notificationName = Notification.Name("switchT")

        NotificationCenter.default.post(name: notificationName, object: nil)

    }

Do you see anything wrong with this implementation?
My errors:
-[MainViewController tableView:didSelectRowAtIndexPath:]: unrecognized selector sent to instance
Terminating app due to uncaught exception 'NSInvalidArgumentException', reason:[.MainViewController tableView:didSelectRowAtIndexPath:]: unrecognized selector sent to instance
Appreciate your assistance! :)

You should put "addObserver" when ViewController is loaded (ViewDidLoad, ViewDidAppear). So iOS will add observer and start listening. Also instead of putting "SearchViewController.tableView(_:didSelectRowAt:)" method just create a new method with implementation and add as a selector. Something like this
override viewDidLoad() {
super.viewDidLoad()
NotificationCenter.default.addObserver(self, selector: #selector(SearchViewController. doSomething()), name: NSNotification.Name("switchT"), object: nil)
}
func doSomething() {
//do something
}
P.S. Don't forget to remove observer once you finish. Otherwise you will get memory leak.

Hi-- thanks so much for the info! Sorry, but one last question of confusion. I implemented your notes and have the addObserver in the viewDidLoad() of MainViewController:
    override func viewDidLoad() {
        self.collectionView.register(UICollectionViewCell.self, forCellWithReuseIdentifier: "Cell")
        super.viewDidLoad()
        print("mainv iew controller loading in")
        customization()
        didSelectItem(atIndex: 0)
        NotificationCenter.default.addObserver(self, selector: #selector(MainViewController.hideBar(notification:)), name: NSNotification.Name("hide"), object: nil)

        let notificationName = Notification.Name("switchT")
        NotificationCenter.default.addObserver(self, selector: #selector(SearchViewController.hello()), name: notificationName, object: nil)
    }

I'm getting an error on the addObserver line since I'm using "instance member hello on type SearchViewController."
In my SearchViewController, I have
    func tableView(_ tableView: UITableView, didSelectRowAt indexPath: IndexPath) {
        print("item selected: \(indexPath.row)")
        hello()
    }

    func hello() {
        let notificationName = Notification.Name("switchT")
        NotificationCenter.default.post(name: notificationName, object: nil)
    }

How will the notification know to ever call didSelectItem?
Your help is much much appreciated!!

Hi Suraya, sorry for delay. Here is the problem:
NotificationCenter.default.addObserver(self, selector: #selector(SearchViewController.hello()), name: notificationName, object: nil)
You are adding observer you self (MainViewController) but selector is in SearchViewController. If SearchVC is not initialized posting a notification will crash. Here is how you should do

in MainVC viewDidLoad() add notificationCetner
let notificationName = Notification.Name("switchT")
NotificationCenter.default.addObserver(self, selector: #selector(MainViewController. switchT(notification:)), name: notificationName, object: nil)

You should have "switchT" method in MainViewController
func switchT(notificaion: Notification) {
if let index = notification.userInfo?["index"] as? Int {
//call method to change tab with index   (I guess didSelectItem(atIndex: index) method)
}
}

From any ViewController do this to change tab programmatically:
let data:[String: Int] = ["index": 2]
let notificationName = Notification.Name("switchT")
NotificationCenter.default.post(name: notificationName, object: data)

You need "data" dictionary to pass information.
Make sure MainViewController is initialized before posting the notification otherwise app will crash.
Also once you done with notification  or MainViewController is deinitialized you should remove notification. Best place to do this is in ViewDidDisappear() in MainViewController.
viewDidDisappear() {
NotificationCenter.default.removeObserver(self)
}
P.S. if still you are getting errors, send me the source codes to check. 😉

Thank you so much!!!!! I haven't used Notifications before and this helped a ton. The tab switching is now working 😄

Thank you so much!!!!! I haven't used Notifications before and this helped a ton. The tab switching is now working 😄


Directline speech - web socket ends with 200 response

Screenshots

Version
4.9.1
Describe the bug
I have enabled directline speech in our bot by using the following example and I am getting the error "Error during WebSocket handshake: Unexpected response code: 200". I tried both the options of passing token and passing the subscription key and facing the same issue.
https://github.com/microsoft/BotFramework-WebChat/tree/master/samples/03.speech/a.direct-line-speech
Note: Cognitive speech  approach works fine.
What could be the possible cause for this?

I have enabled directline speech in our bot

@collegewap it seems like there might be something wrong with how you configured directline speech for your bot, as for a first test, I just simply did the following successfully:
Test with the Read-Made Mockbot Sample
(mockbot is the bot that the webchat sample talks to, whose code is separate from the 03.speech/a.direct-line-speech sample)

git clone https://github.com/microsoft/BotFramework-WebChat.git
npx serve
Navigate to http://localhost:5000/
Click the microphone icon and verbally say "hello"
Mockbot replies back with audio

No idea how you got the error that you did, as you didn't provide repro steps as to what you did exactly to set up your bot...

Setting up a bot configured to DirectLineSpeech
This is just setting up an echo bot with DLS to enable speaking to your bot. It can be succinctly summarized as

Set up a bot in Azure that has Direct Line Speech channel enabled
Run sample 03.speech/a.direct-line-speech (npx serve) and speak to your DLS-enabled bot

Get a fresh clone of Echo Bot and Test Locally

git clone https://github.com/microsoft/BotBuilder-Samples.git
Navigate to 02.echo-bot
Verify that you can chat with the bot locally (npm i, npm start, open Bot Framework Emulator and just type a message and receive an echo--it's currently just a plain Echo Bot with no speech enabled yet)

Deploy your bot to Azure

You can deploy your bot many ways, however one way is via zip-deployment using AZ CLI
Once your bot is deployed to Azure, verify that it's working when you go to Bot Channels Registration > Test in Web Chat:

Note: I had just edited my bot before deploying to say "Speech Echo" so it's obvious that I deployed the right bot properly
Additionally make sure once you have your Bot's AppId and Password, to have it in your .env file that's deployed to Azure (might need to redploy, depending on the order that you did things, which you can do so easily using az webapp deployment source config-zip --resource-group "<resource-group-name>" --name "<name-of-web-app>" --src "<project-zip-path>")

Provision Speech cognitive service

Search the Marketplace for "Speech" and create a Speech cognitive service
Save one of the keys, which you'll use in your WebChat later

Enable DirectLine Speech Channel

In Azure, go to your App Service > Configuration under "Settings" on the left-hand side > For "Web sockets" select "on" > Save:

Once again in Azure, go to Bot Channels Registration > Channels > Direct Line Speech

Select the Speech cognitive service you created earlier (I believe you can only link one speech service to one bot at a time, fyi) > Save

Bot Channels Registration > Settings > check Enable Streaming Endpoint > Save

Run sample 03.speech/a.direct-line-speech and talk to the DLS-enabled bot.

Add your Speech cognitive service key and region to the HTML file for sample 3a

<!DOCTYPE html>

    <title>Web Chat: Using Direct Line Speech</title>
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />

npx serve
Navigate to localhost:5000, click the microphone, speak to the bot

The bot speaks back!

If you follow the steps above, which are similar to this tutorial on enabling speech in your bot (they use C#), then you should be able to run sample 3a just fine

Hmm, looking around there does seem to be some issue on the other layers regarding DLS.
https://github.com/microsoft/cognitive-services-speech-sdk-js/issues/221#issuecomment-673020344
What kind of browser and OS are you using @collegewap ?

@Zerryth
The bot is working fine (Tried example 1a). If I try the speech services  also, it works fine. I made sure that all the steps to enable directline speech are done correctly. Still facing the issue.
I am using Windows 10+ Chrome. Tried in Firefox as well. Same error. I tried https://compulim.github.io/webchat-loader/ with the mock bot and getting the same error.

Hmm...
@collegewap ok, I think what we need now here is painfully explicit step-by-step of what you're doing, just so that we can get a repro of your issue.
Please provide exact repro steps of at least one thing you're doing to get your error, so that we could hopefully get it too and dig down to a resolution

Here are the steps I am doing:

Open https://compulim.github.io/webchat-loader/
Select "MockBot (Direct Line Speech)"
Clear the generated token
Choose "east us 2" as the region.
Provide my speech key and click on "Generate Token".
Click on "Open Web Chat in a new window"
Click on the mic button and I would see the above-mentioned error.

My setup:

And about 3a, we have an endpoint that generates the token. Also, I have tried the example given by you in https://github.com/microsoft/BotFramework-WebChat/issues/3407#issuecomment-673130903, by passing the speech key and getting the same error.

@Zerryth We followed the same steps in another instance and it worked fine. Not sure what is the issue with this specific bot instance. Thanks for your help.


ORM 5.0.0.Final

This PR is targeting branch 5.4, but needs to be rebased and merge in master too.
https://hibernate.atlassian.net/browse/HSEARCH-1972

Jenkins, retest this, please

I've sent an email to hibernate-dev about that peculiarity with ids.

Jenkins, retest this, please

Jenkins, retest this, please

@DavideD the CI build is in trouble as it's using JDK8 now to test PRs, but this being the JDK7 branch it failed on the javadoc.. ignore him?

Or we could backport your javadoc improvements..

Ah, sorry, I thought the problem waws Byteman again ... I will merge the pull request

@Sanne Didn't we already backported  those changes?

Actually I'll fiz the errors. There are not so many

rebased and pushed again.. let's see if CI is happy now.

Merged on master and 5.4

Thanks


Watson_tts load error

Hi
My HA is newest update to 0.101.3 version.
I used the right API.
And get the net error
2019-11-07 23:31:48 ERROR (MainThread) [homeassistant.components.tts] Error setting up platform: watson_tts
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/tts/__init__.py", line 131, in async_setup_platform
    provider = await hass.async_add_job(platform.get_engine, hass, p_config)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/watson_tts/tts.py", line 97, in get_engine
    service = TextToSpeechV1(url=config[CONF_URL], iam_apikey=config[CONF_APIKEY])
  File "/usr/local/lib/python3.7/site-packages/ibm_watson/text_to_speech_v1.py", line 102, in __init__
    display_name='Text to Speech')
TypeError: __init__() got an unexpected keyword argument 'vcap_services_name'

Same problem here. Is there any workaround?

The pull request #28468 haven't been released yet which fixes the issue.


Wrong message: 'The files belonging to this database system will be owned by user "postgres".'

Set both user and db via env vars to 'root' which worked (checked within the running container) but still getting owned by user "postgres" on every initialization as message. I tested this with multiple refreshes (removed data dir and did a docker system prune -a). Also when in psql: db postgres is owned by root. No big issue , just confusing.
Is this intended?

Set both user and db via env vars to 'root' which worked

Which variables/config are you talking about here?  Please share exact docker run or docker-compose file and any relevant commands ran.

Just guessing in the dark, you set POSTGRES_USER=root and POSTGRES_DB=root?  Then that is the user within the database.  The message you mention is from postgres (or maybe initdb?) and refers to the Linux system user (from /etc/passwd in the image) that the postgres daemon runs as and so all database files have to be owned by that user id.

Which variables/config are you talking about here? Please share exact docker run or docker-compose file and any relevant commands ran.

I wrote *[I] set both user and db via env vars to 'root' * which is my exact compose-file:
...
    environment:
      POSTGRES_PASSWORD: somepassword
      POSTGRES_USER: root
      POSTGRES_DB: root
...

> Just guessing in the dark, you set `POSTGRES_USER=root` and `POSTGRES_DB=root`? Then that is the user within the database. The message you mention is from postgres (or maybe `initdb`?) and refers to the Linux system user (from `/etc/passwd` in the image) that the postgres daemon runs as and so all database files have to be owned by that user id.

Ok, think this makes sense, maybe a note in the Docker Image's README would create less confusion because the context of this message is not really clear.

@wglambert IDK if my issue was a real question or rather a rhetoric one about a confusing UI and/or docs.


kubeadm: HA documentation

this PR will update the kubeadm reference documentation regarding HA for 1.14.
xref: kubernetes/kubeadm#1422
/sig cluster-lifecycle

/sig cluster-lifecycle
/assign

in this PR we are going to have to document that there is no config filed for the copy-certs functionality yet and we have to either pass everything as flags for HA join or to only use the --config .... --certificate-key ...  mixture.
/cc @ereslibre

@kubernetes/sig-cluster-lifecycle-pr-reviews

/assign @fabriziopandini

/priority important-soon

/close
in favor of https://github.com/kubernetes/website/pull/13191


[#4558] Add option to disable directbuffer for grpc

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@3133837). Click here to learn what that means.
The diff coverage is 69.23%.

@@            Coverage Diff            @@
##             master    #6046   +/-   ##
=========================================
  Coverage          ?   40.71%
=========================================
  Files             ?     3018
  Lines             ?    90482
  Branches          ?    11813
=========================================
  Hits              ?    36839
  Misses            ?    50481
  Partials          ?     3162

Impacted Files
Coverage Δ

...int/profiler/context/grpc/GrpcTransportConfig.java
83.21% <ø> (ø)

...p/pinpoint/profiler/context/module/GrpcModule.java
0% <0%> (ø)

...rofiler/context/module/NettyPlatformDependent.java
0% <0%> (ø)

...npoint/profiler/util/PropertyRollbackTemplate.java
100% <100%> (ø)

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 3133837...2fae3ff. Read the comment docs.


[$500] Shortcut - App does not redirect to group chat when splitting bill via Shortcut

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.58-1
**Reproducible in staging?:**Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:

Go to staging.new.expensify.com
Go to FAB > Start chat
Create a group chat
Send a message and split bill in the group chat
Navigate to a different chat other than the group chat
Go to FAB > Split bill under Shortcut
Split another bill

Expected Result:
After splitting bill via Shortcut, app will open the group chat
Actual Result:
After splitting bill via Shortcut, app does not open the group chat
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/b16eb3b0-c043-430e-a4ef-6cc37d555ef9
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01e104767dd62cb7af
Upwork Job ID:<PHONE_NUMBER>253258240
Last Price Increase: 2024-04-01
Automatic offers:

akinwale | Reviewer | 0
abzokhattab | Contributor | 0

@joekaufmanexpensify  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #vip-split

Proposal
Please re-state the problem that we are trying to solve in this issue.
App does not redirect to chat report when splitting bill via Shortcut
What is the root cause of that problem?
we dont navigate to the chat report when dismissing the create split modal here:
https://github.com/Expensify/App/blob/cbb1a7bf799296271c72d9a6bc3a8411b7dc59ea/src/libs/actions/IOU.ts#L2683
What changes do you think we should make in order to solve the problem?
we need to pass the existingSplitChatReportID to the dismiss modal function.
    Navigation.dismissModal(existingSplitChatReportID);

will triage today

Yeah this feels like a bug imo. cc @Gonals as I know you're leading QAB

The PR is ready! Please let me know if you have any comments

Great. TY!

PR is on prod. Automation wasn't working, but payment is due in 2 days (2024-04-17)

All set to issue payment here. We need to pay:

@abzokhattab $500 for PR (paid via upwork).
@akinwale $500 for C+ (paid via upwork).

Noting that both payments are $500 here since this issue was opened prior to the baseline being set at $250.

@abzokhattab $500 sent and contract ended!

@akinwale $500 sent and contract ended!

Upwork job closed.

All set, thanks everyone!


THRIFT-2471

three changes as discussed in THRIFT-2471:

Update parser to use & instead of cpp.ref
Recursion depth limit, a la protobufs
shared_ptr instead of raw pointer w/deletes in the destructor.

Sorry, #1195 has nothing to do with this one.  I was off by one.


The custom cursor doesn't account for the page scrolling

the cursor in the frontend branch doesn't scroll when you scroll the page

The custom cursor has been postponed until further development on the front-end.

Resolved the custom cursor bug - it is now fully operational.
I've also implemented the custom cursor in AboutUs.jsx.


Uniformly short starts with a capital letter

Signed-off-by: Fish-pro<EMAIL_ADDRESS>
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

/approve
/lgtm


Create Example Tool landing page

@mbjoseph can you please create a dummy tool landing .md page that describes a cool tool you've built with a link to it? I'll then create a template for posting it.

@mbjoseph you will likely have more than 3 tools, correct?

Definitely. As more are added I think it just creates new rows and keeps 3
columns/row.
On Oct 19, 2016 4:47 PM, "Leah Wasser"<EMAIL_ADDRESS>wrote:

@mbjoseph https://github.com/mbjoseph you will likely have more than 3
tools, correct?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/earthlab/dev-earthlab-site/issues/6#issuecomment-254963119,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACiodDrgPcy78gfJ7Yt5PqD0vm3hezmSks5q1p3tgaJpZM4KZI2R
.

ok -- you can do it this way but it's a bit less search engine savy as we don't have landing pages for each tool with an explanation of what they do and then links to git.
https://mmistakes.github.io/minimal-mistakes/docs/layouts/
Check out the grid layout. If you create a page for each tool with a description and image in the YAML, we can generate landing pages per tool. this is a searchable thing on our site and can be placed into a grid. what do you think about that? that way we aren't curating a yaml list of things, rather pages with descriptive content about the tool.

That's nice looking - and I like that it doesn't clutter up the front matter. I'll take a stab at this and submit another PR.

Sweet.
I’m pretty happy he built that layout. I’ve always wanted it and tried several times unsuccessfully to create something that was responsive and nice !
Hipster genious.

Ok - I just merged the PR - how does this look? Can we close this issue?

this page? looks awesome!!
https://earthlab.github.io/dev-earthlab-site/tools/
How did you get the git build info for smapr to appear? that's some cool magic right there.
I think down the road I may resize some of the banner graphics for the tool landing pages. But i say let's close this issue!!! yes! :)

Badge magic:
[![Build Status](https://travis-ci.org/earthlab/smapr.svg?branch=master)](https://travis-ci.org/earthlab/smapr)
[![CRAN\_Status\_Badge](http://www.r-pkg.org/badges/version/smapr)](https://cran.r-project.org/package=smapr)
[![Licence](https://img.shields.io/badge/licence-GPL--2-blue.svg)](https://www.gnu.org/licenses/old-licenses/gpl-2.0.html)
[![Last-changedate](https://img.shields.io/badge/last%20change-2016--10--07-brightgreen.svg)](/commits/master)

Saweeeettttttt!


Usability notes

(Split into a separate issue from #7 to keep that one on-topic!) A couple usability notes I'm seeing as I get more acquainted with the app:

I find myself trying to drag and drop an image directly onto the window, like adding an attachment in gmail - this would be a handy feature!
I also find myself ctrl/cmd-Z-ing and expecting the last edit I made to be removed completely - the undo brush is very handy for trimming but sometimes I want to start over all the way.

I'd be happy to take on either or both of these in the next few days - let me know what you prefer and thanks again for the work!

Both of these would be great! The cmd-Z undo is probably what I would start on (as I do it too), but whatever you want to start first is fine with me.

Excellent! I'll plan on the cmd-Z undo first. Thanks!

Drag and drop would be cool, I'll take a look at that

Note, added my solution #20 for Drag and Drop

Along with Ctrl+Z undo functionality for desktop, it may be helpful for mobile users to have an Undo button in the top toolbar.

Agreed @lonelymaw ! That's in place in #18:

@SaFrMo Awesome work!


Cli command not available for creating the Access-key and secret-key  (Used for creating the account for nsfs service)

Environment info
NooBaa Version: 5.15
Platform: Linux
Actual behavior
Currently nsfs accounts creation is mandating the access-key and secret-key but there is no cli provided for generating the access-key and secret-key below is the cli command for reference.
node src/cmd/manage_nsfs account add --config_root ../standalon/config_root --name noobaa --email<EMAIL_ADDRESS>--new_buckets_path ../standalon/nsfs_root/ --access_key abc --secret_key abc
Expected behavior
In openshift it is observed that account creation is accepting only uid,gid,bucket path but for the standalone nsfs it is expecting the access-key and secret-key. Below is the reference of the account create api for ocp
	Api: "account_api", Method: "create_account",
                   NsfsAccountConfig: nsfsAccountConfig{
			Uid:            uid,
			Gid:            gid,
			NewBucketsPath: newBucketsPath,
			NSFSOnly:       true,

So the expectation here is by using the uid and gid we should be able to generate the access-key and secret-key post that we should be able to update the account with this generated keys.
Steps to reproduce
NA

@guymguym @romayalon . Please take a look of this issue. Thank you.

duplicate of https://github.com/noobaa/noobaa-core/issues/7580, closing


Add scripts for simplifying installation process

Suggestion details
Pyrsia is currently compiled and we utilize it through the target build.
I'd like to propose a script/MSI package/Mac Equivalent that'd simplify the installation process once we start releasing stable versions. This would make our project more complete as it'd improve the dev-ex. We can do this for any release/build version but it'd be more appropriate for stable releases. It make the Pyrsia tool better as it'd improve simplicity.
Additional details
No response

@AbhijithGanesh we are currently building installers for only Ubuntu.  The install can be done using a single command curl -sSL https://pysria.io/install.sh | sh.
We will need installers for OS/X (brew) and Windows.  Windows will be the difficult one with the dependency on openssl.

I think in one of the prior meetings, @prince-chrismc had told us that the open-ssl dep would no longer be needed as libp2p takes care of it in someway, I am not sure about it. I'd like to have more research

could be replaced it's an open point of discussion in #181

I think it'd be great to remove OpenSSL

I created smaller tickets for this
#1010  - Mac Intel
#1012  - Mac M1
#1011 - Windows

This is now split into the above tickets and will be prioritize as separate efforts. So closing this issue.


Upgrade guardrail.dev to use sbt-microsite and mdoc

Currently, https://guardrail.dev points at book.md. This (incorrectly) suggests that guardrail only works for Scala, as well as displays akka-http in all examples.

[x] Switch to sbt-microsite
[x] Convince Travis to publish docs on release
[x] Split book.md into a hierarchy, broken out by language, framework, and section
[x] Make documentation actually run guardrail with sample input to ensure that code samples don't get out of date with what users actually experience

I've got most of the upgrade to sbt-microsite up in a branch, once I figure out the project structure I'll push up a branch, but this issue is to track progress on broadly improving documentation.

This got merged a while back, closing it out.


Add borderRadius to InkWell in TabBar using provided parameter

This PR is adding splashBorderRadius to TabBar that provides borderRadius to InkWell.
Addresses Feature Request #94290
Before: https://youtu.be/S2qBpaE2wOo
After: https://youtu.be/xvK_uZXVmDc
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Requesting any recommendation regarding the parameter name.

Any recommendation on the parameter name?

This PR is adding splashBorderRadius to TabBar that provides borderRadius to InkWell.
Addresses Feature Request #94290
Before: https://youtu.be/S2qBpaE2wOo After: https://youtu.be/xvK_uZXVmDc
Pre-launch Checklist

[x]  I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x]  I read the Tree Hygiene wiki page, which explains my responsibilities.
[x]  I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x]  I signed the CLA.
[x]  I listed at least one issue that this PR fixes in the description above.
[x]  I updated/added relevant documentation (doc comments with ///).
[x]  I added new tests to check the change I am making, or this PR is test-exempt.
[x]  All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Is the plugins error related to my PR?

Could you try to rebase/merge this with the master branch? Looks like there are conflicts too.

Could you try to rebase/merge this with the master branch? Looks like there are conflicts too.

Done

can you rebase off the latest master and see if it fixes the build?

can you rebase off the latest master and see if it fixes the build?

Done, but I think the problem is internal.

/root/.pub-cache/hosted/pub.dartlang.org/platform-2.2.1/lib/src/interface/local_platform.dart:45:41: Error: Member not found: 'packageRoot'.
|   String get packageRoot => io.Platform.packageRoot;

This error is all over the place.

Looks like there is a bunch formatting error, can you fix them as well?


Verbose response

Investigate whether the output text can be made a bit more verbose by tweaking the prompt.

Addressed by PR #4


Add ERC20Channels contract with test and docs

The ERC20Channels contract is a simple implementation of state channels for ERC20 tokens. This contract allows the token holders to mediate and decide about how much the final value of a transaction is going to be.
The channel is opened by a token holder that previously approved the transfer of tokens to the ERC20Channels contract, once the channel is opened the tokens are transfered to the contract and the mediation of the funds start.
While the channel is opened the two parties can exchange signatures proving the allowance and claim of the funds to be transfered, in this case the sender will share signatures where he allows the receiver to claim certain amount of tokens and the receiver will share signatures where he is willing to claim that amount.
With those signatures the receiver and sender can reach a mutual agreement on how much the final value of the transfer is going to be and always the time to prevent the another party to close the channel with the wrong final value.
Based in LifChannels contract

@spalladino ready for another review.
Regarding the bug of microraiden I think It cannot happen here, but Im not sure, I will need to do more research.

@crypto-banana thx for the review! typos fixed ^^

@spalladino ready for another review, maybe the last one :)

Closing as stale. Also, we'd probably want to go for a more modular approach to state channels.


Add a support for reactive theme

Currently theme injection is not reactive.
Note: These changes have made the theme variable reactive, which means that we now need to use .value when accessing the theme in the Setup function.

This pull request is automatically built and testable in CodeSandbox.
To see build info of the built libraries, click here or the icon next to each commit SHA.
Latest deployment of this branch, based on commit d3b4ae5:
Sandbox	Source
affectionate-ishizaka-d58m4n	Configuration

Seems like its broken by not using the ThemeProvider from vue3-styled-components. Here we have a fix https://codesandbox.io/s/quizzical-hooks-39gq8p?file=/src/App.vue

@jkempff @liqueflies @codebender828 @alexkharech is this still maintained?


Fix #1283 Menu popover

Fixes #1283 .
Changes: src/client/components/Navigation/Topnav.js

delete old methode & put it inside new one when we can handle the event to hide the popover
define popover & visible variables that we can take effect on them.

@Sekhmet  int work on my localhost but i didn't get this error
 34:5  error  propType "onMenuItemClick" is not required, but has no corresponding defaultProp declaration  react/require-default-props
what does mean ?

https://github.com/yannickcr/eslint-plugin-react/blob/master/docs/rules/require-default-props.md

@Sekhmet this is yours

Please make sure you have up-to-date master branch and consider running yarn run prettier and then commit your changes

This message tells you everything you need to to know, and even tells you what you can do to fix the issue.
We have strict policy according code formatting. If your code is not formatted properly it will get rejected. You don't have to check it against our servers, because it can be checked locally in matter of seconds.
This messages tells you to run yarn run prettier, which will fix issues automatically.

@Sekhmet thank you :100:

We prefer to bind instead of using arrow functions. Can you apply this patch?
diff --git a/src/client/components/Navigation/Topnav.js b/src/client/components/Navigation/Topnav.js
index 16b5d49..e13ee22 100644
--- a/src/client/components/Navigation/Topnav.js
+++ b/src/client/components/Navigation/Topnav.js
@@ -49,6 +49,8 @@ class Topnav extends React.Component {
       searchBarValue: '',
     };

+    this.handleMoreMenuSelect = this.handleMoreMenuSelect.bind(this);
+    this.handleMoreMenuVisibleChange = this.handleMoreMenuVisibleChange.bind(this);
     this.handleSelectOnAutoCompleteDropdown = this.handleSelectOnAutoCompleteDropdown.bind(this);
     this.handleAutoCompleteSearch = this.handleAutoCompleteSearch.bind(this);
     this.handleSearchForInput = this.handleSearchForInput.bind(this);
@@ -56,13 +58,15 @@ class Topnav extends React.Component {
     this.hideAutoCompleteDropdown = this.hideAutoCompleteDropdown.bind(this);
   }

-  onSelect = key => {
+  handleMoreMenuSelect(key) {
     this.setState({ popoverVisible: false }, () => {
       this.props.onMenuItemClick(key);
     });
-  };
+  }

-  onVisibleChange = visible => this.setState({ popoverVisible: visible });
+  handleMoreMenuVisibleChange(visible) {
+    this.setState({ popoverVisible: visible });
+  }

   menuForLoggedOut = () => {
     const { location } = this.props;
@@ -126,10 +130,10 @@ class Topnav extends React.Component {
               placement="bottom"
               trigger="click"
               visible={popoverVisible}
-              onVisibleChange={this.onVisibleChange}
+              onVisibleChange={this.handleMoreMenuVisibleChange}
               overlayStyle={{ position: 'fixed' }}
               content={
-                <PopoverMenu onSelect={this.onSelect}>
+                <PopoverMenu onSelect={this.handleMoreMenuSelect}>
                   <PopoverMenuItem key="my-profile" fullScreenHidden>
                     <FormattedMessage id="my_profile" defaultMessage="My profile" />
                   </PopoverMenuItem>


RPLH-efficient Convergence Debug

Previously every new local agent does not take in the previous judges given by teh judge, this casuses an issue. Resolved this issue by passing judge respone into the respone dictionary:  data_local["response_list_dir"]

Instead of saving aagin, directly use data_local["agent_dict"] = response but relapse inside the for loop

Later ones one block keep gets moved around, not converging

----------RETAKE ACTION----------
HISTORY METHOD: _w_markovian_state_action_history
LESS PROMPT IN MESSAGE CONSTRUCT
Length of messages 2
API call failed: 1 validation error for HCA
actions_plan
Field required [type=missing, input_value={'attitude': ['A Good Dec..., position[0.5, 1.5])'}}, input_type=dict]
For further information visit https://errors.pydantic.dev/2.9/v/missing
Traceback (most recent call last):
File "/Users/kevinb/Desktop/dsc190/RPLH/rplh_efficient/rplh_inference.py", line 576, in
) = run_exp(
File "/Users/kevinb/Desktop/dsc190/RPLH/rplh_efficient/rplh_inference.py", line 198, in run_exp
response, token_num_count_list_add = with_action_syntactic_check_func(
File "/Users/kevinb/Desktop/dsc190/RPLH/rplh_efficient/execution_checker.py", line 204, in with_action_syntactic_check_func
response, token_num_count_list_add = retake_action(
File "/Users/kevinb/Desktop/dsc190/RPLH/rplh_efficient/execution_checker.py", line 142, in retake_action
response = json.loads(raw_response)
File "/Users/kevinb/miniforge3/envs/rplh/lib/python3.10/json/init.py", line 339, in loads
raise TypeError(f'the JSON object must be str, bytes or bytearray, '
TypeError: the JSON object must be str, bytes or bytearray, not NoneType
(rplh) (base) kevinb@Kevins-MacBook-Pro-2 RPLH %


New Theme: Robotico

Theme submission
Link to my theme repository: https://github.com/wileybaba/hugo-theme-robotico
I made sure that...

[x] an open source license has been added to LICENSE.md
[x] the repository contains a good README.md describing my theme
[x] all metadata have been added to theme.toml
[x] screenshots have been added in the images/ folder with the required dimensions
[x] in case I'm using a customized demo via the exampleSite folder that

[x] https://example.com is set as base url in exampleSite/config.{toml, yaml, json} to avoid the abuse of unused domains
[x] the site's content is as neutral as possible (contains no ads etc.) and reflects the features of my theme

[x] I tested my theme against the gohugoio/HugoBasicExample

[x] I've checked the developer tools' console in my browser for error messages

[x] in case my theme is using Hugo Pipes features like toCSS and PostCSS that I have committed the /resources directory with all generated assets, for my theme to work in the basic version of Hugo

I tested with the HugoBasicExample and with the GoHugo site build and my demo seemed to work as intended.  Let me know if I'm missing anything, thanks!

@wileybaba
Your theme's Example Site fails to render both when I execute the Hugo Themes Site Build Script and when I run hugo server at the root of the /ExampleSite/ folder.
I am getting the following console error:
Error: Error building site: "/hugoThemes/hugo-theme-robotico/exampleSite/content/about.md:1:4": EOF looking for end TOML front matter delimiter
You need to have proper line breaks in the front matter of about.md, right now everything is in a single line.
Thanks.

Hello,
I've just pushed fixes to the above.  I deleted the og:local meta property from  baseof.html .
Let me know if more attention is needed, thank you.

Thanks for making the changes @wileybaba
I have noticed the following:

In your /portfolio/list.html the lightbox no longer works because after removing the second instance if jQuery -as I instructed above- the script that fires the lightbox is placed before the link to jQuery and as a result it doesn't fire.

To fix this ordering issue please do the following:

In line 66 of your baseof.html include a new block like so:

   {{ block "lightbox" . }}{{ end }}

In your /portfolio/list.html wrap the script in the lightboscript block and move it at the bottom of your template after {{ partial "footer" }}{{ end }} like so:

{{ define "lightbox" }}
  <script>
    $(document).on("click", '[data-toggle="lightbox"]', function(event) {
      event.preventDefault();
      $(this).ekkoLightbox({
        alwaysShowClose: true
      });
    });
  </script>
{{ end }}

It is important to place the new lightbox block outside the main block because if you don't there will be an ERROR.
Finally in your theme.toml I have noticed that you have not included a link to your theme's LICENCE

Please add the following: licenselink = "https://github.com/wileybaba/hugo-theme-robotico/blob/master/LICENSE.md"

Again please do the above and let me know.
Thanks.

Great spot on that missing dot.  I've just pushed the changes you requested and testing looks good on my machine.

@wileybaba
Your theme's demo is looking good on my end now. 👍
However you didn't add the licencelink in your theme.toml
licenselink = "https://github.com/wileybaba/hugo-theme-robotico/blob/master/LICENSE.md"
Please add it and let me know:

Should be good to go now, thanks for walking me through the bugs!

Hi @digitalcraftsman,
I've added the min_version and removed the theme directory from the repo.  Let me know if anything else is necessary, thank you!

Your theme should appear soon on Hugo's theme site. Next, I'll promote your theme on Hugo's official Twitter account.

Sweet sounds good. Keep up the killer work on Hugo, one of my favorite GO projects out there!
El nov. 20, 2018, a la(s) 13:31, digitalcraftsman<EMAIL_ADDRESS>escribió:

Your theme should appear soon on Hugo's theme site. Next, I'll promote your theme on Hugo's official Twitter account.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Enable required check status for PR validation

Motivation
Currently,  there is no required workflow for the PR.
Modifications
Enable required check status for pr validation
Documentation

[ ] doc-required
(Your PR needs to update docs and you will update later)

[x] doc-not-needed
(Please explain why)

[ ] doc
(Your PR contains doc changes)

[ ] doc-complete
(Docs have been already added)

Could you take a look at the Build Alpine Linux APK Package task? It stuck at Waiting for status to be reported

In addition, these two tasks (especially the most important unit tests task) are not required.

In addition, these two tasks (especially the most important unit tests task) are not required.

The unit test is dependent by other jobs.

I found that there is no CentOS7 matrix in the CI job:

Because it was removed in #25.


Update to latest analyzer package

Hi, can you update to the latest "analyzer" package?

https://pub.dev/packages/analyzer

"dart_style" depends on "analyzer", now dartpoet depends on latest "dart_style"


Remove version: WinSCP.WinSCP version 5.21.5

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://sourceforge.net/projects/winscp/files/WinSCP/5.21.5/WinSCP-5.21.5-Setup.exe/download
OK
(Automated message - build 923)

URL: https://sourceforge.net/projects/winscp/files/WinSCP/5.21.5/WinSCP-5.21.5-Setup.exe/download
OK
(Automated message - build 923)

URL: https://sourceforge.net/projects/winscp/files/WinSCP/5.21.5/WinSCP-5.21.5-Setup.exe/download
OK
(Automated message - build 923)

URL: https://sourceforge.net/projects/winscp/files/WinSCP/5.21.5/WinSCP-5.21.5-Setup.exe/download
OK
(Automated message - build 923)

Close with reason: Package still available.;


Slack notify not work

Slack notify not work : empty message sends to server and get 500 error in response.
https://github.com/Block8/PHPCI/pull/742

This is the error that I receive:
Exception: Server error response [url] https://hooks.slack.com/services/[custom url] [status code] 500 [reason phrase] Server Error [0m {"exception":"[object] (GuzzleHttp\\Exception\\ServerException(code: 500): Server error response [url] https://hooks.slack.com/services/[custom url] [status code] 500 [reason phrase] Server Error at phpci/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:89)","buildID":"27"}

I made the changes mentioned in the issue #742 and was able to get this working.

@swilla i have same error. and thats why i create https://github.com/Block8/PHPCI/pull/742


sublime-music: 0.11.13 -> 0.11.14

Motivation for this change
Update to latest upstream release 0.11.14
Change log: https://gitlab.com/sublime-music/sublime-music/-/blob/master/CHANGELOG.rst
Fix build (https://hydra.nixos.org/build/157547926)
ZHF: #144627
Things done

Built on platform(s)

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

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

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

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

1 package built:

sublime-music


Python Unit Test

We extend algorithm unit tests to those written in Python using the existing framework.

@AlexCatarino - great stuff! Will pull down to confirm it's working, looks good though, great work!

Since this is now part of the regression tests we need the python build to happen and copy to the tests directory. Basically, there shouldn't be any manual steps required when running the regression tests.

Replaced by #301


Possibility to configure output fields format.

Hi there,
Thank you for this new wonderful application. I found for my self that it will be really great to have option to define output format for logs in configuration settings.
Like as we have for nginx or apache server.
Is it possible to implement it in new dnscollector?

great idea!
I will take a look to see if it's complicated to implement or not.

implemented in commit https://github.com/dmachard/go-dnscollector/commit/2ac93fbea2039b7e030e9398a19f43c20551ae58
the new default text format and all available directives
specific the default text log format used on all loggers supporting this mode
all directives availables:
- timestamp: timestamp rfc3339 format, with nano support
- identity: dnstap identity
- qr: query or reply flag
- operation: dnstap operation
- rcode: dns return code
- queryip: dns query ip
- queryport: dns query port
- responseip: dns response ip
- responseport: dns response port
- id: dns id
- family: ip protocol version INET or INET6
- protocol: protocol UDP, TCP
- length: the length of the query or reply
- qtype: dns qtype
- qname: dns qname
- latency: computed latency between queries and replies
- answercount: the number of answer
- country: country iso code
- ttl: answer ttl
text-format: "timestamp identity qr operation rcode queryip queryport family protocol length qname qtype latency ttl"

new release v0.6.0 available

thank you, I will test it tomorrow


Detected integration that uses deprecated

Hello,
After today's Homeassistant Core update I get the following message in the log:
Detected integration that uses deprecated async_get_registry to access entity registry, use async_get instead. Please report issue to the custom component author for midea_dehumidifier_lan using this method at custom_components/midea_dehumidifier_lan/__init__.py, line 75: entity_registry = await async_get_registry(hass)
Works but still, maybe you can take a look at it when you get a chance :)
thx

@clipse2004 can you check if problem persists in version 0.8.10?

Normally this is fixed now.


Refactor Nix Files

I needed provide the profiling tools in threadscope and hp2pretty in shell.nix and felt like the nix files grpc-mqtt needed some cleaning up.

I've also made sure to update the pinned proto3-suite package to the most recent revisions since grpc-mqtt now depends on recent option parsing fixed. This also addresses issue #23.


Showing multiple qtips on different nodes is broken

After updating to cytoscape 3 and the current cytoscape-qtip i can no longer show multiple qtips at different nodes, all are shown at the same node (the last one called)..
the problem was introduced with commit 7dbcff0995a9f3d65eb8d626943d87c6601a60fe
before that it was working correctly

I've confirmed that it's working properly.  It can be tricky to use qtip, and you have to set all its options appropriately for how you want it to behave.  The default hide.event: 'unfocus', for example, will hide the first qtip on clicking for a second one.
The demo works with this:
				cy.elements().qtip({
					content: function(){ return 'Example qTip on ele ' + this.id() },
					position: {
						my: 'top center',
						at: 'bottom center'
					},
					hide: {
						event: 'donthide'
					},
					style: {
						classes: 'qtip-bootstrap',
						tip: {
							width: 16,
							height: 8
						}
					}
				});


Feature: StrongParameters

Protect mass assignment by filtering input data using StrongParameters
$user_params = new ActiveRecord\StrongParameters($_POST['user']);
$user_params->permit('name', 'bio');
$user = new User($user_params);
$user->save();

Probably in need of some more tests.
(cc: #287)

+1

@koenpunt Could you re target this PR to the 1.1-dev?  I've added #287 into the 1.1 WIP list.


Explaining the project

Following up on https://github.com/dib-lab/osf-cli/issues/44#issuecomment-305424718 by adding some explanation of the purpose of the project.
@gedankenstuecke does this help you as an outsider? It is a bit tricky for me because I "know all" about it :-/

Codecov Report

Merging #49 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #49   +/-   ##
=======================================
  Coverage   84.35%   84.35%
=======================================
  Files          12       12
  Lines         409      409
=======================================
  Hits          345      345
  Misses         64       64

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 12fb43d...92f5aba. Read the comment docs.

Not needed anymore


In Settings, if I try to change my Description I get the error 'Error Require username, email and refId.'

In the Settings page I tried to change my Description from 'Creative expression in code. ' to 'Data engineer at Resuelve' however I receive the error 'Error Require username, email and refId.'
Screenshot attached :)

I will double check. a few months back, I asked users for emails. But then I thought I should respect users' privacy, and I will never spam them. So I removed the requirement for email. But there might be some data verification checks I forgot to remove.
Thanks a lot! will resolve ASAP.

This should be fixed now. As I suspected, the issue was due to the removal of the email requirement.
Thanks again for reporting this! I should make more tests to find this out early!


Make GCgage parameters more readily findable

Via @anyanova: It would be nice if the ?readGage page included what the potential vars are ("Discharge", "Stage", "TempC") etc so that we know what term/capitalization to use in the readGage call.
Should probably also implement this in a more sophisticated fashion than just wrapping these tables as the gageVars() and gages() functions. Embed as data? Include in help documentation as well? Maintain the subsequently deprecated functions for a while anyway too?

I just added a bit more text to the readGage help documentation to make it clearer how to find parameter names. Still need to implement in a more "sophisticated fashion" (sensu above) though.


configured default environment for cypress

Closes:  RHOAIENG-5298
Description

Need consistency within test files on how ODH_PRODUCT_NAME is used. Added an eslint rule to enforce that it is used in Cypress testing to avoid test failures.
How Has This Been Tested?

npm run test
Alternatively, you can run the test files that were changed. Run them, then change the .env var for ODH_PRODUCT_NAME, then run again, and see the name change.
Test Impact

I implemented the tests.
Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

Verified locally
/lgtm

Rebased to resolve merge conflicts

/lgtm
/approve


8.0.x (and possibly others) does not reset param to default when removed from records

If you set a value in records.config, i.e. proxy.config.http.cache.ignore_accept_encoding_mismatch=1, run with that value
Then remove that param from records.config, do a config reload, if you check the values that ATS is still running with via traffic_ctl it is still using the old 1 value instead of picking up the default 2 value.

I think the best way to help deal with this is add a revert option to traffic_ctl that would set a specific configuration variable to the built in default. Detecting an omission from "records.config" would be a bit challenging.

I think the best way to help deal with this is add a revert option to traffic_ctl that would set a specific configuration variable to the built in default. Detecting an omission from "records.config" would be a bit challenging.

+1 for the revert option.
But in parallel:
It seems to me that someone was thinking about keeping track of the status of the newrecords.configcontent:
https://github.com/apache/trafficserver/blob/57015b77d45acc7bccea5295a26168faa1d6ef52/lib/records/RecConfigParse.cc#L250
this is never used in ATS though,  it' never gets reset, so won't help tracking new content unless it's allocated in the function stack(or clean it before use), anyway I think the intention was for tracking mismatches between the old and new content.
Would it make sense having this container local and check mismatches against  g_records_ht ? then just set the default?


Harsha

What the program do ?

In what programming language it is written?

Too many additions in wrong folder please fix it and reopen


Make sure analytics work when running the app

Can we filter by Electron in Analytics?

UA should do the work here


feat: 🎸 Remove call and event handlers

Description
SQ now populates all the data using blockHandlers only. Within every block, ExtrinsicSuccess events and timestamp.set extrinsics are skipped and rest are indexed in the postgres database. This was done to decrease the overall sync time of SQ.
Breaking Changes
NA
JIRA Link
DA-922
Checklist

[ ] Updated the Readme.md (if required) ?

Do you know how much time this is going to save?
It seems like we need to switch to event handlers to be able to use SubQuery dictionaries.

Upon investigation, I found out that when it comes to block 368, it keeps waiting for new blocks to be created - INDEXING: Fully synced, waiting for new blocks  and then starts erring as 2023-11-02T11:04:51.197Z <health> ERROR undefined  subquery-node_1   | Error: Endpoint is not healthy.
Is there a way to apply the snapshot on the chain and still keep producing blocks?

:tada: This PR is included in version 10.0.0-alpha.8 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 10.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Use the chartutil package to validate release names in linter

closes #10537
What this PR does / why we need it:
The chartutil package has a ValidateReleaseName function. This PR allows the linter to use it in order to improve validation of chart's name.
If applicable:

[ ] this PR contains documentation
[x] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

hey @smaftoul may i go ahead with this
and please eleborate the issue as i'm new to this project.

@Vivek-Prajapatii all necessary work on this issue is done, the issue is approved, it's only waiting for a merge ;)
@EHER is this right ? any idea when it will be merged ?

Would be nice to have a message a bit more friendly here. But overall looks good to me.
I'm new on the project so would be nice to have a review and approval from someone else to be sure.

Validation should definitely be improved.
I hope don't to oversee something, but I see multiple issues in this PR:

a) the code looks confusing now, as validating the chart name is calling a function that belongs to validating release names. So the validation function should be renamed to something more general, if it should be used in a more general use case.
b) By reusing the function, someone could easily break validating the chart name if he touches validating the release name, as the connection and different scope usages are not visible inside the ValidateReleaseName() function by not changing the name
The given error message "invalid release name" is not correct.
Even this PR name looks strange to me, as it claims "to validate release names" where it is in fact adding more validation to the chart name

Close in favor of: https://github.com/helm/helm/pull/11298 ?


Error message missing value

Unable to execute error template:
        Kind: github.com/JosiahWitt/ensure/ensurepkg:erkTableInvalid
        Template: Mocks.{{.mocksFieldName}} should be a pointer to a struct, got {{type .mockEntry}}
        Params: map[mocksFieldName:S3]
        Error: template: :1:70: executing "" at <.mockEntry>: map has no entry for key "mockEntry"

Closing as stale, since I haven't encountered this recently.


Bugfix: prevent crashing when opening second document

This is a fix for https://github.com/xi-editor/xi-mac/issues/272

Good catch! The code looks good, but I can't reproduce the crash for testing. Does this also fix #273 or #261?

The other issues seem unrelated.

The larger question here seems to be, "when should we assign the config?". To my mind, we shouldn't need to call configChanged when creating the view controller; it should start with access to a config, which it uses for initial setup; and then configChanged should only be called when things need to be updated after the fact; that lets us avoid this race altogether.

I am not sure if I understand the code entirely, but it seems to me that the changeConfig in makeWindowControllers Document.swift is unnecessary. It basically loads the cached config and sets is again.

this is a recent change, introduced in #257. It's about making sure the client has config information for the view at initial draw time.

I'll probably have some time next week for a proper fix. I'll create an issue for it.

And merging this is great if it prevents an existing crash.


[Feature Request] CurseForge API Support

Related to a problem?
Currently Rin doesn't have CurseForge API support, but this is planned in either v2.0.0 or v2.1.0.
Solution
Add CurseForge API support. All keys are ready to go
Describe the Alternatives
N/A
Anything else?
No response
Is there an existing feature request for this?

[X] I have searched the existing feature requests

not possible, since all of the keys don't work anymore


Support for #x... constructions to be able to collect groups of children (2nd stage)

Subj.

Codecov Report

Merging #45 (9d624c1) into master (9f9424f) will decrease coverage by 0.00%.
The diff coverage is 93.22%.

@@             Coverage Diff              @@
##             master      #45      +/-   ##
============================================
- Coverage     80.36%   80.36%   -0.01%
- Complexity      914      917       +3
============================================
  Files           179      179
  Lines          4167     4191      +24
  Branches        467      467
============================================
+ Hits           3349     3368      +19
- Misses          637      641       +4
- Partials        181      182       +1

Impacted Files
Coverage Δ

src/main/java/org/uast/astgen/base/ListUtils.java
28.57% <50.00%> (ø)

...uast/astgen/codegen/java/ConverterClassFiller.java
95.27% <90.62%> (-3.87%)
:arrow_down:

...g/uast/astgen/codegen/java/ConverterGenerator.java
92.85% <100.00%> (+0.54%)
:arrow_up:

...g/uast/astgen/codegen/java/MatcherClassFiller.java
100.00% <100.00%> (ø)

...org/uast/astgen/codegen/java/MatcherGenerator.java
91.66% <100.00%> (+1.66%)
:arrow_up:

...n/codegen/java/OrdinaryNodeBuilderConstructor.java
90.00% <100.00%> (+0.23%)
:arrow_up:

...ast/astgen/codegen/java/OrdinaryNodeGenerator.java
82.35% <100.00%> (+0.53%)
:arrow_up:

...main/java/org/uast/astgen/interpreter/Creator.java
46.66% <100.00%> (ø)

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 9f9424f...9d624c1. Read the comment docs.


[Question]: How to use "only subbar" theme

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Id like to get my vscode like your screenshot - without titlebar.

What should I install and configure to achieve the result like in your Readme?
Expected Behavior
No response
Steps To Reproduce
No response
Environment
- OS: macOS
- VSCode: latest
- Extension: latest
- Theme: Dark (subbar only)

Anything else?
No response

I tried some plugins that could remove the titlebar, but all of them where incompatible with Vibrancy, so I have to choose between Vibrancy and disabled Titlebar.


Please add a license so that others can use this package

Could you please add a license so that others can use this package? Publishing software without a license means that anyone attempting to use it would be in violation of copyright. If you could please add a MIT or other distribution-friendly license, that would be appreciated!
Thanks

Please submit a PR with MIT and I will accept it.
On Sun, Nov 13, 2016, 2:59 PM Erik Levinson<EMAIL_ADDRESS>wrote:

Could you please add a license so that others can use this package?
Publishing software without a license means that anyone attempting to use
it would be in violation of copyright. If you could please add a MIT or
other distribution-friendly license, that would be appreciated!
Thanks
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mizzao/meteor-jqueryui/issues/12, or mute the thread
https://github.com/notifications/unsubscribe-auth/AB-9VPy_VoGWyiHfeJbf7lFTs_csGMBsks5q97J9gaJpZM4Kw3bz
.

Thanks for submitting #13.


Container Spacing issue

In 1280px width laptop device no space coming from left and right side of page.

Done @samk43564


Cache pbxobject references during project writing

This is an alternative to the reference changes in #136.
This doesn't change the public API and simply generates an internal cache of reference that can be looked up while writing, improving performance.
It's a temporary internal solution while we lock down the final public API for pbx objects.
At the moment it's a generic function that requires a type. This could be changed to seperate typed caches for all the required types.

Just a couple of comments, great idea @yonaskolb. I'd check the memory consumption just in case.


add warnings, deprecations, or document them otherwise

This error keeps coming up from anyone not using Ansible 2.3.1:
The conditional check 'ansible_distribution == 'Fedora'' failed. The error was: error while evaluating conditional (ansible_distribution == 'Fedora'): 'ansible_distribution' is undefined

There is nothing here that says the Ansible version is wrong. Something needs to clearly state what versions are needed for ceph-ansible to work properly.

like this? https://github.com/ceph/ceph-ansible/pull/1862